How to navigate the Header Details

Use the Header Details screen to see and edit the header information of your BAPLIE file. BAPLIE Viewer Online checks the header against the SMDG specification for BAPLIE when the page opens. Errors in the header are highlighted for you.

Steps

1. In the Function Menu on the left, open Validation and click Header Details. The header information opens in segments. A segment is one line of the header, for example Details of Transport. The check starts when the page opens.

2. If the check fails, a message appears at the top of the screen (1 in the picture). Fields with errors are shown in red.
3. To see the fields of a segment, click the arrow on the right side of the segment (2 in the picture). Click it again to close the segment.

4. Click into the red fields and correct the errors.
5. Point to the ? icon next to a field name. A short text explains what the field needs.

Edit the header details

You can edit all fields on the Header Details screen.

1. Open a segment. Change the fields in its text boxes and drop-downs (1 in the picture).
2. In the Function Menu, click Save Changes (2 in the picture). The page reloads. Fields that you fixed are no longer red.

Field value explanations

The SMDG specification defines these fields. The explanations are for the current BAPLIE 2.2 specification. Each segment starts with an example line from a file.

Interchange Header

Example: UNB + UNOA : 2 + RON + HAM + 200915 : 0858 + 0 + + + + +

1. Syntax Identifier: this value is always UNOA
2. Syntax Version: this value is always 2
3. Sender ID: name code of the sender of the message
4. Recipient ID: name code of the receiver of the message
5. Date of Preparation: preparation date of the message
6. Time of Preparation: preparation time of the message
7. Interchange Control Reference: a reference by the sender that identifies the message. It must also be sent in the Interchange Trailer segment UNZ
8. Recipients Reference Password: not used
9. Application Reference: not used
10. Processing Priority Code: not used
11. Acknowledgement Request: not used
12. Communications Agreement ID: code of the shipping line of the vessel (BIC or SCAC code). With this code the receiver can route the message correctly, even if the sender is not the shipping line (for example a container terminal in the previous port)

Message Header

Example: UNH + 1 + BAPLIE : D : 95B : UN : SMDG22

1. Message Reference: a reference from the sender that identifies the message. It must also be sent in the Message Trailer segment UNT
2. Message Type ID: the name of the UNSM or EDIFACT message, here BAPLIE
3. Message Type Version #: the version number of the message, now “D”
4. Message Type Release #: the release number of the message, now “95B”
5. Controlling Agency: the code of the controlling agency, for this message use “UN”
6. Association Assigned Code: the version number of the SMDG user manual, use “SMDG22”. With this the receiver can read the message correctly, even if older versions are in use

Beginning of Message

Example: BGM + + 0 + 9

1. Document Message Name: not used
2. Document/Message #: a reference that the sender gives to the message, taken from the application
3. Message Function: code for the function of the message. Use 2 for add to previous message, 3 to delete from previous message, 4 to change previous message, 5 to replace previous message, 9 for original message and 22 for final message

Date/Time/Period

Example: DTM + 137 : 202009150858 : 201

1. Date/Time/Period Qualifier Code: use 137 for the date and time of the document or message
2. Date/Time compiled: date or date and time when the message was made
3. Format Qualifier Code: use 101 for YYMMDD, 210 for YYMMDDHHMM, 301 for YMMDDHHMMZZZ where ZZZ is the time zone, for example GMT

Details of Transport

Example: TDT + 20 + 002W + + + BVO : 172 : 20 + + + H4318 : 103 : 11 : BVO DEMO SHIP :

1. Transport Stage Qualifier: use code 20 for main carriage
2. Conveyance Reference #: use the discharge voyage number from the operating carrier or agent. The trade route can be part of the voyage number
3. Mode Of Transport: not used
4. Transport Means: not used
5. Carrier ID: carrier name as a code: agreed code or standard carrier alpha code (SCAC)
6. Code List Qualifier: use code 172 for the carrier code
7. Code List Responsible Agency: use 20 for BIC (Bureaus International des Containeurs), 166 for US National Motor Freight Classification Association (SCAC) or ZZZ for mutually defined
8. Transit Direction Coded: not used
9. Excess Transportation Information: not used
10. ID of Means of Transport ID: use the Lloyds vessel code (IMO number), the call sign or a vessel code that both sides agreed on
11. Code List Qualifier: use 103 for call sign directory, 146 for means of transport identification Lloyds code or IMO number, or ZZZ for mutually defined or IMO number
12. Code List Responsible Agency: use 11 for Lloyds register of shipping when a Lloyds code is used for the vessel or barge, or ZZZ for mutually defined
13. ID of Means of Transport: vessel name, if required
14. Nationality of Means of Transport: code from the UN Country Code ISO 3166

Location Identification

Example: LOC + 5+DEHAM:139:6

1. Place/Location Qualifier: use 5 for the place of departure or 61 for the next port of call
2. Place/Location ID: location code of the real place of departure, normally the sender of the message. If possible, use UN/LOC codes of 5 characters
3. Code list qualifier: use 139 for port
4. Code List Responsible Agency: use 112 for US, US Census Bureau, Schedule D for US locations, Schedule K for foreign port locations, or 6 for UN/ECE (United Nations Economic Commission for Europe, UN/LOC codes)
5. Related Place/Location 1 ID: the ISO country code
6. Code list qualifier: use 162 for country
7. Code List Responsible Agency: use 5 for ISO
8. Related Place/Location 2 ID: the state or province code, postal abbreviations
9. Code list qualifier: use 163 for country sub entity, state or province

Date/Time/Period (second segment)

Example: DTM + 178 : 2009150858 : 201

1. Date/Time/Period Qualifier Code: use “178” for the real date and time of arrival at the sender’s port, “132” for the estimated date or date and time of arrival at the next port of call, “133” for the estimated date or date and time of departure at the sender’s port, or “136” for the real date and time of departure at the sender’s port
2. Date/Time: date or date and time, in local time, when the means of transport arrived or left, or is expected to leave the sender’s port or to arrive at the next port of call
3. Format Qualifier Code: use “101” for YYMMDD, “201” for YYMMDDHHMM or “301” for YYMMDDHHMMZZZ where ZZZ is the time zone, for example GMT

Message Trailer

Example: UNT + 61558 + 1

1. Number of Segments: number of segments in the message, including the UNH and UNT segments but not the UNA, UNB and UNZ segments
2. Message Reference #: this reference must be the same as the reference in the UNH segment

Interchange Trailer

Example: UNZ + 1 + 0

1. Interchange Control Count: the number of messages in the interchange
2. Interchange Control Reference: this reference must be the same as the reference in the UNB segment