5 Use of EDIFACT Messages (for Sea Cargo and Arrival/Departure)
5.1 Update Manifest Information(1) Correction before Manifest Submission (DMF)[1] Done by procedure "Update Manifest Information (Before the Manifest Submission
procedure) (CMF01)"[2] A single B/L message can be corrected in the case of a single message and a multimessage. A multi B/L message can be corrected only in the case of a single
message.
Table 14-5-1 Method of Correction before Manifest Submission (DMF)
Sending by a single
Sending by a multimessagemessage
Correction of single B/LΟΟmessage
Correction of multi B/LΟX
message
Provided below are examples of the correction of manifest information registered by amulti B/L message using procedure "Manifest Information Registration (MFR)."
Example 1) Correction in a single B/L message(1) Key items[1] Erroneous B/L information or container information is deleted by procedure"Update Manifest Information (CMF01)." （Message function： 1 = Cancellation)[2] Correct B/L information or container information is registered by procedure"Manifest Information Registration (MFR)." (Possible for a single message and amulti message)(Message function: 9 = Original)(See Figure 14-5-1.)(2) Items other than keys
[1] Correct B/L information or container information is corrected by procedure"Update Manifest Information (CMF01)." (Possible for a single message and a multimessage)(Message function: 5 = Replace)(See Figure 14-5-2.)
Example 2) Correction in a multi B/L message(1) Key item
[1] All B/L information and container information registered by procedure "Manifest
Information Registration (MFR)" are deleted by procedure "Update Manifest
Information (CMF01)." （Message function： 1 = Cancellation）[2] Correct B/L information or container information is registered by procedure"Manifest Information Registration (MFR)." (Possible only for a single message)(Message function: 9 = Original)(See Figure 14-5-3.)(2) Items other than keys
[1] All B/L information and container information registered by procedure "Manifest
Information Registration (MFR)" are replaced with correct information by procedure"Update Manifest Information (CMF01)." (Possible only for a single message)(Message function: 5 = Replace)(See Figure 14-5-4.)
Appendix 14-5-1

(Note) Key items of manifest: Vessel code, carrier code,
port of discharge code, port of discharge suffix,
container operator code,
B/L Number, and container number
The table below summarizes correction before Manifest Submission (DMF).
Table 14-5-2 Possibility of Correction before Manifest Submission (DMF) Depending on
Presence/Absence of Key Items
Sending by a single Sending by a multimessagemessage
Key itemPresent
AbsentPresent
AbsentCorrection of single B/Lmessage
Correction of multi B/Lmessage

Ο

Ο

Ο

Ο

Ο

Ο

X

X

(2) Correction after Manifest Submission (DMF)[1] Done by procedure " Update Manifest Information (After the Manifest Submission
procedure) (CMF02)"[2] A single B/L message can be corrected in the case of a single message and a multimessage.
[3] A multi B/L message cannot be corrected in the case of a single message or multimessages.
Table 14-5-3 Method of Correction after Manifest Submission (DMF)
Sending by a single
Sending by a multimessagemessage
Correction of single B/LΟΟmessage
Correction of multi B/LXXmessage
Provided below are examples of the correction of manifest information registered by amulti B/L message using procedure "Manifest Information Registration (MFR)."
Example 1) Correction in a single B/L message(1) Key item[1] Erroneous B/L information or container information is deleted by procedure "Update Manifest Information (After the Manifest Submission procedure) (CMF02)."(Message function: 1= Cancellation）[2] Correct B/L information or container information is registered by procedure "Update Manifest Information (After the Manifest Submission procedure) (CMF02)."(Possible for a single message and a multi message)(Message function: 9 = Original)(See Figure 14-5-1.)(2) Items other than keys
[1] Correct B/L information or container information is corrected by procedure "Update Manifest Information (After the Manifest Submission procedure) (CMF02)."(Possible for a single message and a multi message)(Message function: 5 = Replace)(See Figure 14-5-2.)

Appendix 14-5-2

The table below summarizes correction after Manifest Submission (DMF).
Table 14-5-4 Possibility of Correction after Manifest Submission (DMF) Depending on
Presence/Absence of Key Items
Sending by a single Sending by a multimessagemessage
Key itemPresent
AbsentPresent
AbsentCorrection of single B/Lmessage
Correction of multi B/Lmessage

Ο

Ο

Ο

Ο

X

X

X

X

Appendix 14-5-3

5.2 Vessel Operation Information Registration (VTX01) and correction(1) Vessel Operation Information Registration (VTX01)
Procedure "Vessel Operation Information Registration (VTX01)" uses the CUSREP
message.
Each CUSREP message stores the information of one voyage.
(See Figure 14-5-5.)(Note) In NACCS, "one voyage" means the period from the arrival to a domestic port
(or external qualification change) to the exit from a domestic port toward a foreign port
(or internal qualification change).
(2) Correction of vessel operation information (correction of all information)
The vessel operation information registered in the system is corrected to the correct
vessel operation information by procedure "Vessel Operation Information Registration(VTX01)." As part of the correction of all information, domestic ports of call can be
added.
(See Figure 14-5-6.)(3) Correction of vessel operation information (for one port)
Correction of one port can be made with or without restriction on vessel operation
information.
[1] Without restriction on vessel operation information
In this method, correction is made for the information of one port registered byprocedure "Vessel Operation Information Registration (VTX01)", the common
information, and information of foreign ports of call.
[2] With restriction on vessel operation information
In this method, correction is made for the information of one port registered byprocedure "Vessel Operation Information Registration (VTX01)." (Common informationand foreign ports of call cannot be corrected.)(See Figure 14-5-7.)

Appendix 14-5-4

5.3 Registration and correction of ACL Information Registration (ACL)
Procedure "ACL Information Registration (ACL)" includes procedure "ACL Information
Registration (For Container Vessels) (ACL01)" and procedure "ACL Information Registration(For Conventional Vessels/Car Carriers) (ACL02)." Procedure "ACL Information Registration(For Container Vessels) (ACL01)" can register and change the container vessel information,
the information on marks and numbers and the goods description.
Procedure "ACL Information Registration (For Conventional Vessels/Car Carriers) (ACL02)
can register and change the conventional vessels/car carriers information, the information on
marks and numbers, the goods description, the chassis No., and so forth.
(See Figure 14-5-8.)
For the relationship between procedure codes and output information codes for different
procedures, see the list of subset names of procedures supported by EDIFACT (Appendix
14-4).

Appendix 14-5-5

5.4 Message structures for Unified Application Before Vessel Arrival (VPX),
Vessel Entry Notice (VIX), and Vessel Departure Notice (VOX)

Vessel Entrance
NoticeDeparture
information

Entry Report

Quarantine notice

Declaration ofhealthAdvance notice

Route information

Report on the
security
information of ship

Discharged cargo
information

Cargo・
Dangerous goods
information

The table below shows the difference between EDIFACT messages of procedures "Unified
Application Before Vessel Arrival (VPX)", "Vessel Entry Notice (VIX)", and "Vessel
Departure Notice (VOX)."
Table 14-5-5 Difference of Message Structures between VPX, VIX, and VOX

-

-

Ο

Ο

-

Ο

Ο

Ο

Ο

Ο

Vessel Entry
Notice (VIX)
VesselDeparture
Notice (VOX)

Ο

-

-

-

Ο

-

-

-

-

-

-

Ο

-

-

-

Ο

Ο

-

-

Ο

Mapping
position
Identifier

SG8

SG8

SG8

SG8

SG8

SG8

SG8

SG8

SG8

20

20

20

QIF

MDH

SG
8
HMI

MTI

CGI

LDC

DGI

Information
Name

UnifiedApplication
BeforeVessel Arrival(VPX)

Appendix 14-5-6

(Figure 14-5-1)
Cargo manifest registered by a multi B/L message.
Correction in a single B/L message (key item)
NACCS center server
User system

Mail server

Main core processing

The EDIFACT conversion processing
converts the EDIFACT message sentfrom the user to an NACCS EDI
message, segments it to processing
units of the main core processing (B/L
units and container units), and then send
them to the main processing part.

The main core processing performs registrationfor each of the messages (B/L units andcontainer units) segmented by the mail server.

[1] Registering B/L information andcontainer information(Multi B/L message)
The user uses procedure "manifest Information
registration (MFR)" to send a multi B/L message
containing B/L information and container
information to the NACCS center server.
UN H
Common inf ormation

Co rrect C NT1

UNBWrong C NT2SMTP(MIME)

Wrong C NT3
Wrong C NT4

Co rrect B/L1

CUSCAR

Conversion
processing

Wrong B/L2

UNZ

Wrong B/L3

Messagesegmentation
processing

Common inf ormation
Common inf ormation
CNT1
Common inf ormation
CNT2
Common inf ormation
NACCS
CNT3
Common inf ormation
CNT4
Common inf ormation
EDI messa ge
B/L1
Common inf ormation

B/L2

B/L3

UN T

The linkage between B/L numbers andcontainer numbers:
Correct B/L1
CNT1
Wrong B/L2
CNT2
CBT3
Wrong B/L3
CNT4

Procedure processing(registration)[2] Deleting B/L information and container
information(Single B/L message)
The user uses procedure "manifest Information
correction (CMF01, 02)" to send a single B/Lmessage containing B/L information andcontainer information with processing type"deletion" to the NACCS center server.

The EDIFACT conversion processing
converts the EDIFACT message sent fromthe user to an NACCS EDI message,
segments it to messages (each for one B/L), and then send them to the main core
processing.

The main core processing performs deletion foreach of the segmented messages (each for
one B/L) made by the mail server.

Processing type "deletion"
Common info rmati on

UN H
Common inf ormation

Wrong C NT2

UNBWrong C NT3
Wrong B/L2

CUSCARSMTP(MIME)UN T
UN H
Common inf ormation

Wrong C NT4
Wrong B/L3

CUSCAR

Conversion
processing

Messagesegmentation
processing

NACCS
EDI messa ge

B/L2
CNT2
CNT3

Common info rmati on

B/L3
CNT4

UNZ

UN T

Procedure processing(deletion)[3] Registering B/L information andcontainer information(Single B/L message)
The user uses procedure "manifest Information
registration (MFR, CMF02)" to send a single B/Lmessage containing B/L information and container
information to the NACCS center server.
UN H
Common inf ormation
Co rrect C NT2

UNB

Co rrect C NT3
Co rrect B/L2

CUSCARSMTP(MIME)UN T

UN H
Common inf ormation
Co rrect C NT4
Co rrect B/L3

The EDIFACT conversion processing
converts the EDIFACT message sent fromthe user to an NACCS EDI message,
segments it to messages (each for one B/L), and then send them to the main core
processing.

CUSCAR

Conversion
processing

Messagesegmentation
processing

The main core processing performs registrationfor each of the segmented messages (each for
one B/L) made by the mail server.

Common info rmati on

NACCS
EDI messa ge

B/L2
CNT2
CNT3

Common info rmati on

B/L3
CNT4

UNZ

UN T

Procedure processing(registration)(Note) A maximum of 99 messages are sentby one interchange.

Appendix 14-5-7

(Figure 14-5-2)
Cargo manifest registered by a multi B/L message.
Correction in a single B/L message (not a key item)
NACCS center server
User system

Mail server

Main core processing

The EDIFACT conversion processing
converts the EDIFACT message sentfrom the user to an NACCS EDI
message, segments it to processing
units of the main core processing (B/L
units and container units), and then send
them to the main core processing.

The main core processing performs registrationfor each of the messages (B/L units andcontainer units) segmented by the mail server.

[1] Registering B/L information andcontainer information(Multi B/L message)
The user uses procedure "manifest Information
registration (MFR)" to send a multi B/L message
containing B/L information and container
information to the NACCS center server.
UNH
Co mmon in fo rmation

Correct CNT1

UNB
SMTP
(MIME)

Wrong CNT2
Wrong CNT3
Wrong CNT4

Conversion
processing

CUSCAR

Correct B/L1
Wrong B/L2

Messagesegmentation
processing

Common inf ormation
Common inf ormation
CNT1
Common inf ormation
CNT2
Common inf ormation
CNT3
Common inf ormation
NACCS
CNT4
Common inf ormation
B/L1
Common inf ormation
EDI messa ge

B/L2

B/L3

UNZ

Wrong B/L3
UNT

Procedure processing(registration)

The linkage between B/L numbers andcontainer numbers:
Correct B/L1
CNT1
Wrong B/L2
CNT2
CNT3
Wrong B/L3
CNT4[2] Correcting B/L information andcontainer information(Single B/L message)

The user uses procedure "manifest Information
correction (CMF01, 02)" to send a single B/Lmessage containing B/L information andcontainer information with processing type"correction" to the NACCS center server.

The EDIFACT conversion processing
converts the EDIFACT message sent fromthe user to an NACCS EDI message,
segments it to messages (each for one B/L), and then send them to the main core
processing.

The main core processing performs overwriting
correction for each of the segmented
messages (each for one B/L) made by the mailserver.

Processing type "correction"
UNH
Common info rmati on

Co mmon in fo rmation

Correct CNT2

UNB

Correct CNT3
Correct B/L2
UNT

CUSCARSMTP(MIME)

UNH
Common info rmati on

Conversion
processing

Messagesegmentation
processing

NACCS
EDI messa ge

B/L2
CNT2
CNT3

Common info rmati on

B/L3
CNT4

CUSCAR

Correct CNT4
Correct B/L3

UNZ

UNT

Procedure processing(correction)(Note) A maximum of 99 messages are sentby one interchange.

Appendix 14-5-8

(Figure 14-5-3)
Cargo manifest registered by a multi B/L message.
Correction in a multi B/L message (key item)
NACCS center server
User system
Mail server

Main core processing

The EDIFACT conversion processing
converts the EDIFACT message sentfrom the user to an NACCS EDI
message, segments it to processing
units of the main core processing (B/L
units and container units), and then send
them to the main core processing.

The main core processing performs registrationfor each of the messages (B/L units andcontainer units) segmented by the mail server.

[1] Registering B/L information andcontainer information(Multi B/L message)
The user uses procedure "manifest Information
registration (MFR)" to send a multi B/L message
containing B/L information and container
information to the NACCS center server.
UNH
Common inf ormation

Correct CNT1
Wrong CNT2
Wrong CNT3
Wrong CNT4
Correct B/L1
Wrong B/L2
Wrong B/L3
UNT

UNB

SMTP
(MIME)

Conversion
processing

CUSCAR
UNZ

Common inf ormation
Common inf ormation
CNT1
Common inf ormation
CNT2
Common inf ormation
NACCS
CNT3
Common inf ormation
CNT4
Common inf ormation
EDI messa ge
B/L1
Common inf ormation

Messagesegmentation
processing

B/L2

B/L3

The linkage between B/L numbers
and container numbers:
Correct B/L1
CNT1
Wrong B/L2
CNT2
CNT3
Wrong B/L3
CNT4

Procedure processing(registration)[2] Deleting B/L information and container
information(Multi B/L message)
The user uses procedure "manifest
Information correction (CMF01)" to send a
multi B/L message containing B/L informationand container information with processing
type "deletion" to the NACCS center server.

The EDIFACT conversion processing
converts the EDIFACT message sentfrom the user to an NACCS EDI
message, segments it to processing
units of the main core processing (B/L
units and container units), and then send
them to the main core processing.

The main core processing performs deletion foreach of the messages (B/L units and container
units) segmented by the mail server.

Processing type "deletion"
UNH

Common inf ormation
Common inf ormation
CNT1
Common inf ormation
CNT2
Common inf ormation
NACCS
CNT3
Common inf ormation
CNT4
Common inf ormation
EDI messa ge
B/L1
Common inf ormation

Common inf ormation

Correct CNT1
Wrong CNT2
Wrong CNT3
Wrong CNT4
Correct B/L1
Wrong B/L2
Wrong B/L3
UNT

UNB

CUSCARSMTP(MIME)

Conversion
processing

UNZ

Messagesegmentation
processing

B/L2

B/L3

Procedure processing(deletion)[3] Registering B/L information andcontainer information(Multi B/L message)
The user uses procedure "manifest Information
registration (MFR)" to send a multi B/L message
containing B/L information and container
information to the NACCS center server.
UNH
Common inf ormation

Correct CNT1
Correct CNT2
Correct CNT3
Correct CNT4
Correct B/L1
Correct B/L2
Correct B/L3
UNT

UNB

CUSCARUNZ

The EDIFACT conversion processing
converts the EDIFACT message sentfrom the user to an NACCS EDI
message, segments it to processing
units of the main core processing (B/L
units and container units), and then send
them to the main core processing.

SMTP(MIME)

Conversion
processing

Messagesegmentation
processing

The main core processing performs registrationfor each of the messages (B/L units andcontainer units) segmented by the mail server.

Common inf ormation
Common inf ormation
CNT1
Common inf ormation
NACCS
CNT2
Common inf ormation
CNT3
Common inf ormation
EDI messa ge
CNT4
Common inf ormation
B/L1
Common inf ormation

B/L2

B/L3

Procedure processing(registration)(Note) A multi B/L message is always
sent by a single message.

Appendix 14-5-9

(Figure 14-5-4)
Cargo manifest registered by a multi B/L message.
Correction in a multi B/L message (not a key item)
NACCS center server
User system
Mail server

Main core processing

The EDIFACT conversion processing
converts the EDIFACT message sentfrom the user to an NACCS EDI
message, segments it to processing
units of the main core processing (B/L
units and container units), and then send
them to the main core processing.

The main core processing performs registrationfor each of the messages (B/L units andcontainer units) segmented by the mail server.

[1] Registering B/L information andcontainer information(Multi B/L message)
The user uses procedure "manifest Information
registration (MFR)" to send a multi B/L message
containing B/L information and container
information to the NACCS center server.
UNH
Co mmon in fo rmation

Correct CNT1

UNB
SMTP
(MIME)

Wrong CNT2
Wrong CNT3
Wrong CNT4

Conversion
processing

CUSCAR

Correct B/L１
Wrong B/L２

Messagesegmentation
processing

Common inf ormation
Common inf ormation
CNT1
Common inf ormation
CNT2
Common inf ormation
CNT3
Common inf ormation
NACCS
CNT4
Common inf ormation
B/L1
Common inf ormation
EDI messa ge

B/L2

B/L3

UNZ

Wrong B/L３
UNT

Procedure processing(registration)

The linkage between B/L numbers andcontainer numbers:
Correct B/L1
CNT1
Wrong B/L2
CNT2
CNT3
Wrong B/L3
CNT4[2] Correcting B/L information andcontainer information(Multi B/L message)

The user uses procedure "manifest Information
correction (CMF01)" to send a multi B/L message
containing B/L information and container
information with processing type "correction" to
the NACCS center server.
Processing type "correction"

The EDIFACT conversion processing
converts the EDIFACT message sent fromthe user to an NACCS EDI message,
segments it to processing units of the maincore processing (B/L units and container
units), and then send them to the maincore processing.

UNH
Co mmon in fo rmation

Correct CNT1

UNB

Correct CNT2
Correct CNT3

CUSCAR

Correct CNT4SMTP
(MIME)

Conversion
processing

Messagesegmentation
processing

The main core processing performs overwriting
correction for each of the segmented
messages (B/L units and container units) madeby the mail server.

Common inf ormation
Common inf ormation
CNT1
Common inf ormation
CNT2
Common inf ormation
CNT3
Common inf ormation
CNT4
Common inf ormation
B/L1
Common inf ormation

NACCS
EDI messa ge

B/L2

B/L3

Correct B/L1
Correct B/L2

UNZ

Correct B/L3
UNT

Procedure processing(correction)(Note) A multi B/L message is always sent
by a single message.

Appendix 14-5-10

(Figure 14-5-5)
EDIFACT message of vessel operation information registration

CUSREP

UNH

BGM
Procedure Code=VTX01
Processing type =9SG9(1):
Port ofembarkation

Commoninformation

SG9(2):Before entry todomestic port
Foreign ports of call
(Repeated from 0 to 30)

SG8(1): Foreign ports of call
Vessel CodeSG8(2) :Domestic ports of call
(Repeated from 1 to 9)

SG9:Foreign portsof call

SG9:Domestic portsof callSG9(3):First foreign port ofcall after embarkation froma domestic port

SG9(1):
Port of call(1)UNT

SG9(4):
Final destination

SG9(2):
ports of call(2)SG9(3):Discharged
cargo information(Repeated from 0 to3)

SG9(4):Cargo on
board information(Repeated from 0 to
3)

The figure above illustrates the structure of EDIFACT messages of procedure "vessel
operation information registration (VTX01)." Foreign ports of call are registered in SG8 (1), anddomestic ports of call are registered in SG8 (2) (maximum of 9 records).

Appendix 14-5-11

(Figure 14-5-6)
Correction of vessel operation information
Information registered by procedure "vessel operation information registration (VTX01)" iscorrected in the procedure below.
The vessel code cannot be changed. (To correct the vessel code, you need to register the vessel
operation information again.)[1] Vessel operation
information registration

UNH

BGM
Procedure code =VTX01
Processing type =9[2] Correction of vessel
operation information

UNH

BGM
Procedure code=VTX01
Processing type =5

Register vessel operation information by "vessel operation information
registration (VTX01)" procedure.
The common information is assumed to have an error.

(Error)Commoninformation

SG8(1) :Foreign ports of call
Vessel Code

SG9:Foreign portsof call

SG8(2): Domestic ports ofcall(Repeated from 1 to 9)

SG9:Domestic portsof call

UNT

Correct the vessel operation information by "vessel operation information
registration (VTX01)" procedure.
Correct the "common information" here.

(Correct)(Error)Commoninformation

SG8(1): Foreign ports of call
Vessel CodeSG8(2): Domestic ports of call
(Repeated from 1 to 9)

SG9:Foreign portsof call

SG9:Domestic portsof call

Appendix 14-5-12

UNT

To add a domestic port of call to the information registered by procedure "vessel operation
information registration (VTX01)", follow the procedure illustrated below. (Maximum of 9
domestic ports of call can be registered.)[1] Vessel operation
information registration

UNH

BGM
Procedure code =VTX01
Processing type =9Register vessel operation information by "vessel operation information registration(VTX01)" procedure.
The
common information is assumed to have an error.
Port A is added to the domestic port of call (1) and port B is added to the domestic port of call (2).

Commoninformation

SG8(1): Foreign ports of call
Vessel CodeSG8(2): Domestic ports of call
(Repeated from 1 to 9)

SG9:Foreign portsof call

SG9:Domestic portsof callSG9(3):Discharged
SG9(4):Cargo on
SG9(1):
SG9(2):
board information
ports of call(1) ports of call(2) cargo information
SG9(3):Discharged
SG9(4):Cargo on board
SG9(1):
SG9(2):(Repeatedfrom 0 to cargo(Repeatedfrom 0information
information
寄港地情報(1)寄港地情報(2)3)
to 3)

Port A(Repeated from 0 to 3)

Port B[2] Addition of a domestic portof call

UNH

BGM
Procedure code=VTX01
Processing type =5

UNT(Repeated from 0 to 3)

Add a domestic port of call by "vessel operation information registration (VTX01)"
procedure.
Add port C as a domestic port of call (3).
* Resend the common information, foreign ports of call, port A information, and port B
information.

Commoninformation

SG8(1):Foreign ports of call
Vessel CodeSG8(2):Domestic ports of call
(Repeated from 1 to 9)

SG9:Foreign portsof call

SG9:Domestic portsof call

Port APort B

UNT

SG9(3):Discharged SG9(4):Cargo on
SG9(1):
SG9(2):
cargo information
board information
Port of call(1)Port of call(2)SG9(3):Discharged cargo SG9(4):Cargo on board
SG9(1):
SG9(2):
from 0(Repeatedfrom 0 to (Repeated
information
information
寄港地情報(1)寄港地情報(2)3)
to cargo3)
SG9(3):Discharged
SG9(4):Cargo on board
SG9(1):
SG9(2):
information
information(Repeated from 0 to 3)
寄港地情報(1)寄港地情報(2)(Repeated from 0 to 3)

Port CAppendix 14-5-13(Repeated from 0 to 3)(Repeated from 0 to 3)

(Figure 14-5-7)
Correction of vessel operation information (for one port)[1] Without restriction on vessel operation information
Follow the procedure below to correct the common information, foreign ports of call, and port C
among domestic ports of call (3) registered by procedure "vessel operation information
registration (VTX01)."(When registered)
SG8(1): Foreign ports of call(Error)
UNH

BGM
Procedure code =VTX01
Processing type =9

Commoninformation(Error)

Vessel CodeSG8(2): Domestic ports of call
(Repeated from 1 to 9)

SG9:Foreign portsof call

PortACPort

SG9:Domestic portsof callUNT

SG9(3):Discharged SG9(4):Cargo on
SG9(1):
SG9(2):
cargo information
board information
Port of call(1)Port of call(2)SG9(3):Discharged cargo SG9(4):Cargo on board
SG9(1):
SG9(2):
information
information(Repeatedfrom 0 to 3)(Repeatedfrom 0 to 3)
寄港地情報(1)寄港地情報(2)SG9(3):Discharged cargo SG9(4):Cargo on board
SG9(1):
SG9(2):
information
information(Repeated from 0 to 3)
寄港地情報(1)寄港地情報(2)(Repeated from 0 to 3)

Port B
Port C(Error)(Repeated from 0 to 3)(Repeated from 0 to 3)

With a single port correction by processing type = 4 (without restriction on vessel(When
operation information), common information, foreign ports of call, and a domestic port ofcorrected)
call (one item) can be corrected.

UNH

BGM
Procedure code=VTX01
Processing type =4

Commoninformation(Correct)Order of domestic
ports of call whencorrecting one
port = (order ofport C)

SG8(2):
SG8(2): Domestic
Domesticports
portsofofcall
call(Repeated from 1 to 9)

SG8(1): Foreign ports of call(Correct)
Vessel Code

SG9:Foreign portsof call

Port C(correct)SG9(1):
Port of call(1)SG9:Domestic portsof callSG9(2):
Port of call(2)Appendix 14-5-14

SG9(3):Discharged
cargo information(Repeated from 0
to 3)

UNT

SG9(4):Cargo on
board information(Repeated from 0
to 3)

[2] With restriction on vessel operation information
Follow the procedure below to correct port C among domestic ports of call (3) registered byprocedure "vessel operation information registration (VTX01)."(When registered)

UNH

BGM
Procedure code =VTX01
Processing type =9

Commoninformation

SG8(1): Foreign ports of call
Vessel CodeSG8(2): Domestic ports of call
(Repeated from 1 to 9)

SG9:Foreign portsof call

SG9:Domestic portsof callPort
PortAC

SG9(3):Discharged SG9(4):Cargo on
SG9(1):
SG9(2):
cargo information
board information
Port of call(1)Port of call(2)SG9(3):Discharged cargo SG9(4):Cargo on board
SG9(1):
SG9(2):(Repeatedfrom 0(Repeatedfrom 0information
information
寄港地情報(1)寄港地情報(2)to 3)
to cargo3)
SG9(3):Discharged
SG9(4):Cargoon board
SG9(1):
SG9(2):
information
information(Repeated from 0 to 3)
寄港地情報(1)寄港地情報(2)(Repeated from 0 to 3)

Port B
Port C(Error)(Whencorrected)

UNH

UNT

(Repeated from 0 to 3)(Repeated from 0 to 3)

With a single port correction by processing type =3 (without restriction on vessel
operation information), common information, foreign ports of call, and a domestic port ofcall (one item) can be corrected.

BGM
Procedure code =VTX01
Processing type =3

Order ofdomestic portsof call whencorrecting one
port = (order ofport C)

SG8(2): Domestic ports of call・・・Port C(correct)SG9(1):
ports of call(1)Appendix 14-5-15

SG9:Domestic portsof callSG9(2):
ports of call(2)SG9(3):Discharged
cargo information(Repeated from 0
to 3)

UNT

SG9(4):Cargo on
board information(Repeated from 0
to 3)

(Figure 14-5-8)
Correction of ACL information
When correction is made in marks and numbers registered by "ACL information registration (forcontainer vessels) (ACL01)" and "ACL information registration (for conventional vessels andautomobile vessels) (ACL02)", they are output to EDIFACT as shown below.

[1]
Registration ofof marks
marks and[1]Correction
andnumbers
numbers

BGM
UNH

Output information code =SAT1411
Number of times of correction = no
outputRegister marks and numbers by "ACL information registration (for container
vessel) (ACL01)" procedure. (3) of marks and numbers is assumed to have anerror.
SG18:Marks and numbers

DTM
Registration date =20171009

・・・

Registration time =1300

SG23:Marks and nu mb ers(Repea ted from 0 to 18)(1) and nu mb ers
SG23:Marks(Repea ted from 0 to 90)
SG23:Marks(2) and nu mb ers(Repea ted from 0 to 90)

UNT(3)(Erro r)
SG23:Marks and nu mb ers
・・・(Repea ted from 0 to 90)(N)[2] Correction of marks andnumbers

Correct marks
marks andandnumbers
numbers(3)(3)byby"ACL
information
registration
container"ACL
information
registration(for (forcontainer
vessel)vessel) (ACL01)"(ACL01)" procedure.
procedure.

SG18:Marks and numbers (correct)
UNH

BGM

DTM

Output information code =SAT1411
Number of times of correction=1

Correction date =20171010

・・・

Correction time =1000

SG23:Marks and nu mb ers(Repea ted from 0 to 18)(1) and nu mb ers
SG23:Marks(Repea ted from 0 to 90)
SG23:Marks(2) and nu mb ers(Repea ted from 0 to 90)(3)(Correct)
SG23:Marks and nu mb ers
・・・(Repea ted from 0 to 90)(N)

Appendix 14-5-16

UNT