|
|
| Function: |
| To indicate the type and function of a message and to transmit the identifying number. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Document/message name, coded |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code list responsible agency, coded |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Confirmation number assigned by the document sender. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Segment Notes: |
This segment is used to indicate the type and function of a message and to transmit the identifying number.
All references other than the document number DE 1004 are to be put in the RFF segment.
DE 1004: It is recommended that the length of the document number be restricted to a maximum of 17 characters.
DE 1225: The message function, coded is a critical data element in this segment. It applies to all data indicated in the message. The following definitions apply for the restricted codes:
9 = Original - An original transmission of a Booking Confirmation.
31 = Copy - Copy of the booking confirmation for a third party for information purposes.
Example :
BGM+770+31041+9+AP'
Note 1: Accepted - The previously sent firm booking has been fully accepted.
Note 2: Conditionally accepted - The previously sent firm booking has been conditionally accepted subject to some minor amendments, e.g. no room on the requested sailing. Details of the amendments only may be specified at the header level of the message.
Note 3: Pending - The previously sent firm booking message has been received but has not yet been processed and is pending final confirmation.
Note 4 = Rejected - The previously sent firm booking has not been accepted by the forwarder or carrier. Only those goods items responsible for non-acceptance of the booking may be detailed in group 6. |
|