INVOIC Invoice Message



|-[pic] | |

| |Federale |

| |Overheidsdienst |

| |FINANCIEN |

| | |

| |

|BELASTINGEN EN INVORDERING |

|Administratie van Douane en Accijnzen |

| |

| |

| |

CODECO IN

Announcement of the arrival of the goods

Version 1.12

1 March 2012

Message Name: EDIFACT CUSREP Message – Belgian Customs

Message Version: 1.12

Date Released: 1 March 2012

Responsible Agency: Belgian Customs.

Message Description:

Message Type: CODECO IN

Directory Name: TDID D95B

Directory Version: D.95B

REVISIONS

|Version |Date |Author |comment |

|1.0 |1 April 2007 |Seagha | |

|1.1 |1 September 2007 |R. Beeckman |Changes in SG5/RFF /1154 to recognize the type of the |

| | | |declaration. |

|1.2 |4 September 2007 |R. Beeckman |Changes in SG5/RFF/1153 and 1154: qualifiers for type |

| | | |of declaration are added |

|1.3 |6 September 2007 |R. Beeckman |SF5/RFF occurs 999 |

|1.5 |1 November 2007 |R. Beeckman |CUSREP vervangen door CODECO IN |

|1 6 |14 December 2007 |R. Beeckman |Aanpassing door te sturen info. Enkel elektroniische |

| | | |aangiften dienen te worden ingestuurd. |

|1.8 |20 mai 2009 |M. Vico |Ajout d’exemples (point 5) |

|1.10 |19 october 2009 |R. Beeckman |Additional info for BGM + some other changes due to |

| | | |meeting with port community |

|1.11 |1 March 2012 |M.De Doncker |Revisie van het ganse document |

|1.12 |13 August 2012 |M.De Doncker |Internal review |

1. General Comments

This document describes the CODECO IN message as it is used by the Belgian Customs to receive the arrival notification of the goods. The message is used in relation with containers.

1. Introduction

A message by which a terminal, depot, etc. confirms that the containers specified have been delivered or picked up by the inland carrier (road, rail or barge). This message can also be used to report internal terminal container movements (excluding loading and discharging the vessel).

This message is part of a total set of container-related messages. These messages serve to facilitate the intermodal handling of containers by streamlining the information exchange. The business scenario for the container messages is clarified in a separate document, called: 'Guide to the scenario of EDIFACT container messages'.

Important Notes:

- The segments in bold are used by Customs.

- The segments in italic can be sent to Customs, but they are not necessary for the Customs data set.

- The repetition factor of the RFF segment in the EQD group has been extended to 99 in order to refer to more than 9 Customs documents per container.

2. Practical information

This message is used for the announcement of the arrival of containers. To avoid that the PLDA system will be overloaded with arrival announcements for which no information is available in PLDA, it was agreed that only the information of the electronic declarations (ECS, NCTS and PLDA) will be given by the responsible agent.

1. Service segments

1. Interchange envelop – UNB segment

|UNB - M 1 - | INTERCHANGE HEADER |

|Function : |To start, identify and specify an interchange. |

|Segment number : | |

| | EDIFACT |BE Customs | * |Description |

|S001 |SYNTAX IDENTIFIER | M | R | | |

|0001 |Syntax identifier | M a4 | R | * | UNOC |

|0002 |Syntax version number | M n1 | R | * | 3 = Syntax version number 3 |

|S002 |INTERCHANGE SENDER | M | R | | |

|0004 |Sender identification | M an..35 | R | |It is recommended to use the EORI number (see also |

| | | | | |SG-2 – NAD – C082/3039 for details); if not, parties|

| | | | | |have to agree an identification with the Central |

| | | | | |Administration of the Belgian Customs |

|0007 |Partner Identification code qualifier | C an..4 | X | | “ZZZ”= mutually defined |

|0008 |Address for reverse routing | C an..14 | X | | |

|S003 |INTERCHANGE RECIPIENT | M | R | | |

|0010 |Recipient identification | M an..35 | R | | The following codes are used: |

| | | | | |DOUANR = port of Antwerp |

| | | | | |DOUZEE = port of Zeebrugge |

| | | | | |DOUGEN = port of Gent. |

|0007 |Partner Identification code qualifier | C an..4 | X | | |

|0014 |Routing address | C an..14 | X | | |

|S004 |DATE / TIME OF | M | R | | |

| |PREPARATION | | | | |

|0017 |Date | M n6 | R | | YYMMDD |

|0019 |Time | M n4 | R | | HHMM |

|0020 |Interchange control reference | M an..14 | R | |Unique reference identifying the interchange. |

| | | | | |Created by the interchange sender. |

|S005 |RECIPIENT’S REFERENCE PASSWORD | C | X | | |

|0022 |Recipient’s reference/password | M an..14 | X | | |

|0025 |Recipient’s reference/password qualifier | C an2 | X | | |

|0026 |Application reference | C an..14 | X | |Message identification if the interchange contains |

| | | | | |only one type of message. |

|0029 |Processing priority code | C a1 | X | | |

|0031 |Acknowledgement request | C n1 | X | | |

|0032 |Communications agreement identification | C an..35 | R | * | “CUSREP” |

|0035 |Test indicator | C n1 | O | | 1 = Interchange is a test |

2. Interchange envelop – UNZ segment

|UNZ - M 1 - |INTERCHANGE TRAILER |

|Function : |To end and check the completeness of an interchange. |

|Segment number : | |

| | EDIFACT |BE Customs | * |Description |

|0036 |Interchange control count | M n..6 | R | |Number of messages within the interchange. |

|0020 |Interchange control reference | M an..14 | R | | Identical to DE 0020 in UNB segment. |

| | | | | | |

2. Segment table

Pos. Seg. Req. Group Notes and

No. ID Name Des. Max.Use Repeat Comments

|M |0010 |UNH |Message Header |M |1| |

| |Unique message reference assigned by the sender. |

|M |S009 | |MESSAGE IDENTIFIER |M | | |

| |Identification of the type, version etc. of the message being interchanged. |

|M | |0065 |Message type identifier |M | |an..6 |

| |Code identifying a type of message and assigned by its controlling agency. |

| |CODECO | |Container gate-in/gate-out report message |

|M | |0052 |Message type version number |M | |an..3 |

| |Version number of a message type. |

| |D | |Draft Version/UN/EDIFACT Directory |

|M | |0054 |Message type release number |M | |an..3 |

| |Release number within the current message type version number (0052). |

| |95B | |Release 1995 - B |

|M | |0051 |Controlling agency |M | |an..2 |

| |Code identifying the agency controlling the specification, maintenance and publication of the |

| |message type. |

| |UN | |UN/ECE/TRADE/WP.4, United Nations Standard Messages (UNSM) |

| | |0057 |Association assigned code |C | |an..6 |

| |Code, assigned by the association responsible for the design and maintenance of the message type|

| |concerned, which further identifies the message. |

| |ITG14 | |ITIGG Version 1.4 |

| |0068 | |COMMON ACCESS REFERENCE |C | |an..35 |

| |Reference serving as a key to relate all subsequent transfers of data to the same business case |

| |or file. |

|X |S010 | |STATUS OF THE TRANSFER |C | | |

| |Statement that the message is one in a sequence of transfers relating to the same topic. |

|X | |0070 |Sequence message transfer number |M | |n..2 |

| |Number assigned by the sender indicating that the message is an addition or change of a |

| |previously sent message relating to the same topic. |

|X | |0073 |First/last sequence message transfer indication |C | |a1 |

| |Indication used for the first and last message in a sequence of the same type of message |

| |relating to the same topic. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

| | |

1. BGM Beginning of message

Segment: BGM Beginning of Message

Position: 0020

Group:

Level: 0

Usage: Mandatory

Max Use: 1

Purpose: A segment to indicate the beginning of a message and to transmit identifying number and the further specification of the message type (in data element 1001: Document/message name, coded), such as Gate-in report, Gate-out report.

Data Element Summary

Data Component

Element Element Name Attributes

|M |C002 | |DOCUMENT/MESSAGE NAME |M | | |

| |Identification of a type of document/message by code or name. Code preferred. |

|M | |1001 |Document/message name, coded |M | |an..3 |

| |Document/message identifier expressed in code. |

| |NOTE: The codes 36 and 999 are not used with Customs |

| |34 | |Cargo status |

| |Message identifying the status of cargo. |

| |Transport Equipment Gate In Report. |

|X | |1131 |Code list qualifier |C | |an..3 |

| |Identification of a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |3055 |Code list responsible agency, coded |C | |an..3 |

| |Code identifying the agency responsible for a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |1000 |Document/message name |C | |an..35 |

| |Plain language identifier specifying the function of a document/message. |

|M |1004 | |DOCUMENT/MESSAGE NUMBER |M | |an..35 |

| |Reference number assigned to the document/message by the issuer. |

| |Unique report number, assigned by the sender. |

|M |1225 | |MESSAGE FUNCTION, CODED |M | |an..3 |

| |Code indicating the function of the message. |

| |5 | |Replace |

| |Message replacing a previous message. |

| |9 | |Original |

| |Initial transmission related to a given transaction. |

|X |4343 | |RESPONSE TYPE, CODED |C | |an..3 |

| |Code specifying the type of acknowledgement required or transmitted. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

6.2.1 Use of the qualifiers in BGM/1225

o For each container which will be exported out of the European Community at least one CODECO IN has to be sent by the terminal operator.

o Qualifiers 9 (original) and, 5 (replace) are always on container level, not on MRN/declaration level. The first CODECO IN message for a container has always the qualifier “9” in BGM/1225.

o Within the ECS-application the qualifiers 9 (original) and 5 (replace) will be treated at the same level. This means that in case, the ECS-application received a container number/MRN linked to the qualifier 5 and this container number/MRN is not arrived at the office of exit within the ECS-application, this application will accept this container number/MRN otherwise when the ECS-application received a container number/MRN linked to the qualifier 5 and this container number/MRN is already arrived at the office of exit within the ECS-application, this application will ignore this container number/MRN. When the ECS-application received a container number/MRN linked to the qualifier 9 and this container number/MRN is already arrived at an office of exit within the ECS-application but for a location which is situated at another office of exit, this application will accept this container number/MRN and will modify the location linked to the combination container number/MRN (crossbooking).

o For a replacement the full information is resent. For example when an extra MRN is provided to the terminal operator for a specific container, a replace message for this container will be sent, including the MRN of the previous message(s) and the new one.

o Multiple MRN for the same container: If information is not available in one time, the terminal operator has to send a first CODECO IN with Qualifier ”9” and subsequently he has to send replacements including the previous MRN and the new one (s).

2. Segment Group 2

Group: NAD Segment Group 2: Name and Address

Position: 0100

Group:

Level: 1

Usage: Mandatory

Max Use: 9

Purpose: A group of segments to identify a party and/or addresses and related contacts.

Segment Summary

Pos. Seg. Req. Max. Group:

No. ID Name Des. Use Repeat

|M |0110 |NAD |Name and Address |M |1 | |

1. NAD name and address

Segment: NAD Name and Address

Position: 0110 (Trigger Segment)

Group: Segment Group 2 (Name and Address) Mandatory

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment to identify the party's name and address, and function, such as: - message recipient - message sender - ordering customer - ordering customer agent

Data Element Summary

Data Component

Element Element Name Attributes

|M |3035 | |PARTY QUALIFIER |M | |an..3 |

| |Code giving specific meaning to a party. |

| |AG | |Agent/representative |

| |(3196) Party authorized to act on behalf of another party. This |

| |qualifier is used to indicate the shipping line. |

| |CF | |Container operator/lessee |

| |Party to whom the possession of specified property (e.g. container) has|

| |been conveyed for a period of time in return for rental payments. This |

| |qualifier is used to indicate the terminal operator |

|M |C082 | |PARTY IDENTIFICATION DETAILS |M | | |

| |Identification of a transaction party by code. |

| |EORI number of the shipping line or his agent |

|M | |3039 |Party id. identification |M | |an..35 |

| |Code identifying a party involved in a transaction. |

| | |1131 |Code list qualifier |C | |an..3 |

| |Identification of a code list. Identification of parties, corporates, etc. |

| |EOR | |EORI number |

| | |3055 |Code list responsible agency, coded |C | |an..3 |

| |Code identifying the agency responsible for a code list. |

| |147 | |Belgian Customs |

|X |C058 | |NAME AND ADDRESS |C | | |

| |Unstructured name and address: one to five lines. |

|X | |3124 |Name and address line |M | |an..35 |

| |Free form name and address description. |

|X | |3124 |Name and address line |C | |an..35 |

| |Free form name and address description. |

|X | |3124 |Name and address line |C | |an..35 |

| |Free form name and address description. |

|X | |3124 |Name and address line |C | |an..35 |

| |Free form name and address description. |

|X | |3124 |Name and address line |C | |an..35 |

| |Free form name and address description. |

|X |C080 | |PARTY NAME |C | | |

| |Identification of a transaction party by name, one to five lines. Party name may be formatted. |

|X | |3036 |Party name |M | |an..35 |

| |Name of a party involved in a transaction. |

|X | |3036 |Party name |C | |an..35 |

| |Name of a party involved in a transaction. |

|X | |3036 |Party name |C | |an..35 |

| |Name of a party involved in a transaction. |

|X | |3036 |Party name |C | |an..35 |

| |Name of a party involved in a transaction. |

|X | |3036 |Party name |C | |an..35 |

| |Name of a party involved in a transaction. |

|X | |3045 |Party name format, coded |C | |an..3 |

| |Specification of the representation of a party name. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X |C059 | |STREET |C | | |

| |Street address and/or PO Box number in a structured address: one to three lines. |

|X | |3042 |Street and number/p.o. box |M | |an..35 |

| |Street and number in plain language, or Post Office Box No. |

|X | |3042 |Street and number/p.o. box |C | |an..35 |

| |Street and number in plain language, or Post Office Box No. |

|X | |3042 |Street and number/p.o. box |C | |an..35 |

| |Street and number in plain language, or Post Office Box No. |

|X |3164 | |CITY NAME |C | |an..35 |

| |Name of a city (a town, a village) for addressing purposes. |

|X |3229 | |COUNTRY SUB-ENTITY IDENTIFICATION |C | |an..9 |

| |Identification of the name of sub-entities (state, province) defined by appropriate governmental|

| |agencies. |

|X |3251 | |POSTCODE IDENTIFICATION |C | |an..9 |

| |Code defining postal zones or addresses. |

|X |3207 | |COUNTRY, CODED |C | |an..3 |

| |Identification of the name of a country or other geographical entity as specified in ISO 3166. |

3. Segment Group 5

Group: EQD Segment Group 5: Equipment Details

Position: 0250

Group:

Level: 1

Usage: Mandatory

Max Use: 999

Purpose: A group of segments to specify containers in which goods are transported.

Segment Summary

Pos. Seg. Req. Max. Group:

No. ID Name Des. Use Repeat

|M |0260 |EQD |Equipment Details |M |1 | |

|M |0270 |RFF |Reference |M |99 | |

|M |0290 |DTM |Date/Time/Period |M |1 | |

|M |0300 |LOC |Place/Location Identification |M |1 | |

|M |0310 |MEA |Measurements |O |9 | |

|O |0330 |SEL |Seal Number |O |9 | |

| |0390 | |Segment Group 7: Details of Transport |O | |9 |

1. Segment EQD

Segment: EQD Equipment Details

Position: 0260 (Trigger Segment)

Group: Segment Group 5 (Equipment Details) Mandatory

Level: 1

Usage: Mandatory

Max Use: 1

Purpose: A segment to specify a container, container size and type used in the transport, and full/empty indication.

Data Element Summary

Data Component

Element Element Name Attributes

|M |8053 | |EQUIPMENT QUALIFIER |M | |an..3 |

| |Code identifying type of equipment. |

| |CN | |Container |

|M |C237 | |EQUIPMENT IDENTIFICATION |M | | |

| |Marks (letters and/or numbers) identifying equipment used for transport such as a container. |

|M | |8260 |Equipment identification number |M | |an..17 |

| |Marks (letters and/or numbers) which identify equipment e.g. unit load device. |

| |Container number. |

|X | |1131 |Code list qualifier |C | |an..3 |

| |Identification of a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |3055 |Code list responsible agency, coded |C | |an..3 |

| |Code identifying the agency responsible for a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |3207 |Country, coded |C | |an..3 |

| |Identification of the name of a country or other geographical entity as specified in ISO 3166. |

|M |C224 | |EQUIPMENT SIZE AND TYPE |M | | |

| |Code and/or name identifying size and type of equipment used in transport. Code preferred. |

| | |8155 |Equipment size and type identification |M | |an..10 |

| |Coded description of the size and type of equipment e.g. unit load device. |

| |Container size / type - ISO. |

|X | |1131 |Code list qualifier |C | |an..3 |

| |Identification of a code list. |

| | |3055 |Code list responsible agency, coded |C | |an..3 |

| |Code identifying the agency responsible for a code list. |

|X | |8154 |Equipment size and type |C | |an..35 |

| |Plain language description of the size and type of equipment e.g. unit load device. |

|X |8077 | |EQUIPMENT SUPPLIER, CODED |C | |an..3 |

| |To indicate the party that is the supplier of the equipment. |

|X |8249 | |EQUIPMENT STATUS, CODED |M | |an..3 |

| |Indication of the action related to the equipment. |

|X |8169 | |FULL/EMPTY INDICATOR, CODED |M | |an..3 |

| |To indicate the extent to which the equipment is full or empty. |

2. Segment RFF

Segment: RFF Reference

Position: 0270

Group: Segment Group 5 (Equipment Details) Conditional

Level: 2

Usage: Conditional

Max Use: 99

Purpose: A segment to specify the identifying number associated with the container, such as: - container sequence number - booking reference number (sea)

|Notes: | |This segment is conditional if BGM/1225 = “9” or “1” |

| | |For full gate in containers the qualifier BN will be used (booking reference). |

| | |Unique Consignment Reference will only be used if available (optional). |

| | | |

| | |In this segment, reference is also made to the Customs document(s) with different qualifiers. Multiple |

| | |occurrences of the RFF are possible. |

Data Element Summary

Data Component

Element Element Name Attributes

|M |C506 | |REFERENCE |M | | |

| |Identification of a reference. |

|M | |1153 |Reference qualifier |M | |an..3 |

| |Code giving specific meaning to a reference segment or a reference number. |

| | |

| |EXS Exit Summary Declaration |

| |ABT | |Custo Customs export declaration number (PLDA + ECS) |

| | | | |

| |XTR | |Customs Transit declaration (NCTS) - destination = BE |

| | | | |

| |XTT | |Customs Transit declaration (NCTS) – destination Transit |

| | | | |

| |XSE | |Manual SAD export declaration |

| | | | |

| |XAG | |AGD declaration (excise) |

| | | | |

| |XT5 | |T5 |

| | | | |

| |XSP | |Railway waybill |

| | | | |

| |XMA | |Other non SAD declarations |

| | | | |

| |AIO | |Transshipment number |

| | |

| |AHI | |Transport contract reference number |

| |Reference number of a transport contract. |

| |Carrier's agent release number. |

| |ANN | |Transport Equipment Announcement Number |

| |BN | |Booking reference number |

| |[1016] Reference number assigned by the carrier or his agent when cargo space is |

| |reserved prior to loading. |

| |CN | |Carrier's reference number |

| |Reference number assigned by carrier to a consignment. |

| |UCN | |Unique consignment reference number |

| |(1202) Unique reference of a consignment (UCRN) used for identification purposes in|

| |documents and messages exchanged between parties in international trade. See also: |

| |Unique Identifier Code (UNIC) in UN/ECE Recommendation No. 8, March 1992. |

|M | |1154 |Reference number |M | |an..35 |

| |MRN of the declaration or other document reference |

|X | |1156 |Line number |C | |an..6 |

| |Number of the line in the document/message referenced in 1154 Reference number. |

|X | |4000 |Reference version number |C | |an..35 |

| |To uniquely identify a reference by its revision number. |

3. Segment DTM

Segment: DTM Date/Time/Period

Position: 0290

Group: Segment Group 5 (Equipment Details) Mandatory

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment to indicate date and time relating to pick-up and delivery of a container, such as: - actual equipment collection/pick-up date/time - actual delivery date/time

|Notes: | |Date and time the container entered the gate in (move in), left the gate out (move out) or was subject of a |

| | |logistic move. |

Data Element Summary

Data Component

Element Element Name Attributes

|M |C507 | |DATE/TIME/PERIOD |M | | |

| |Date and/or time, or period relevant to the specified date/time/period type. |

|M | |2005 |Date/time/period qualifier |M | |an..3 |

| |Code giving specific meaning to a date, time or period. |

| |7 | |Effective date/time |

| |Date and/or time at which specified event or document becomes |

| |effective. |

|M | |2380 |Date/time/period |M | |an..35 |

| |The value of a date, a date and time, a time or of a period in a specified representation. |

|M | |2379 |Date/time/period format qualifier |M | |an..3 |

| |Specification of the representation of a date, a date and time or of a period. |

| |203 | |CCYYMMDDHHMM |

| |Calendar date including time with minutes: C=Century; Y=Year; M=Month; |

| |D=Day; H=Hour; M=Minutes. |

4. Segment LOC

Segment: LOC Place/Location Identification

Position: 0300

Group: Segment Group 5 (Equipment Details) Mandatory

Level: 2

Usage: Mandatory

Max Use: 1

Purpose: A segment to specify ports/locations associated with the transport of a container, such as: - stowage cell - place of discharge

Data Element Summary

Data Component

Element Element Name Attributes

|M |3227 | |PLACE/LOCATION QUALIFIER |M | |an..3 |

| |Code identifying the function of a location. |

| |165 | |Activity location |

| |Location (coded) where the container is stocked |

|M |C517 | |LOCATION IDENTIFICATION |M | | |

| |Identification of a location by code or name. |

|M | |3225 |Place/location identification |M | |an..25 |

| |Identification of the name of place/location, other than 3164 City name. |

| |Location code (UN/LOCODE + national code). |

| |These codes can be founded via URL : |

| | |1131 |Code list qualifier |C | |an..3 |

| |Identification of a code list. |

| |139 | |Port |

| |A location having facilities for means of transport to load or |

| |discharge cargo. |

| | |3055 |Code list responsible agency, coded |C | |an..3 |

| |Code identifying the agency responsible for a code list. |

| |147 | |Belgian customs |

|X | |3224 |Place/location |C | |an..17 |

| |Name of place/location, other than 3164 City name. |

|X |C519 | |RELATED LOCATION ONE IDENTIFICATION |M | | |

| |Identification the first related location by code or name. |

| | |3223 |Related place/location one identification |M | |an..25 |

| |Specification of the first related place/location by code. |

| | |1131 |Code list qualifier |C | |an..3 |

| |Identification of a code list. |

| | |3055 |Code list responsible agency, coded |C | |an..3 |

| |Code identifying the agency responsible for a code list. |

| | |3222 |Related place/location one |C | |an..70 |

| |Specification of the first related place/location by name. |

|X |C553 | |RELATED LOCATION TWO IDENTIFICATION |C | | |

| |Identification of second related location by code or name. |

| | |3233 |Related place/location two identification |C | |an..25 |

| |Specification of a second related place/location by code. |

| | |1131 |Code list qualifier |C | |an..3 |

| |Identification of a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

| | |3055 |Code list responsible agency, coded |C | |an..3 |

| |Code identifying the agency responsible for a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

| | |3232 |Related place/location two |C | |an..70 |

| |Specification of a second related place/location by name. |

|x |5479 | |RELATION, CODED |C | |an..3 |

| |To specify the relationship between two or more items. |

5. Segment MEA

Segment: MEA Measurements

Position: 0310

Group: Segment Group 5 (Equipment Details) Mandatory

Level: 2

Usage: Optional

Max Use: 9

Purpose: A segment to specify measurement, other than dimensions, associated with the container, such as: - gross weight

Comments: This segment is not required by customs

Data Element Summary

Data Component

Element Element Name Attributes

|M |6311 | |MEASUREMENT APPLICATION QUALIFIER |M | |an..3 |

| |Specification of the application of the physical measurement used. |

| |AAE | |Measurement |

| |[6314] Value of the measured unit. |

|M |C502 | |MEASUREMENT DETAILS |M | | |

| |Identification of measurement type. |

| | |6313 |Measurement dimension, coded |C | |an..3 |

| |Specification of the type of dimension to be measured. |

| |G | |Gross weight |

| |[6292] Weight (mass) of goods including packing but excluding the |

| |carrier's equipment. |

|X | |6321 |Measurement significance, coded |C | |an..3 |

| |Code specifying the significance of a measurement value. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |6155 |Measurement attribute, coded |C | |an..3 |

| |Code used to specify non-discrete measurement values. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |6154 |Measurement attribute |C | |an..70 |

| |To specify non-discrete measurement values. |

|M |C174 | |VALUE/RANGE |M | | |

| |Measurement value and relevant minimum and maximum tolerances in that order. |

|M | |6411 |Measure unit qualifier |M | |an..3 |

| |Indication of the unit of measurement in which weight (mass), capacity, length, area, volume or |

| |other quantity is expressed. |

| |KGM | |Kilograms |

|M | |6314 |Measurement value |M | |n..18 |

| |Value of the measured unit. |

|X | |6162 |Range minimum |C | |n..18 |

| |Minimum of a range. |

|X | |6152 |Range maximum |C | |n..18 |

| |Maximum of a range. |

|X | |6432 |Significant digits |C | |n..2 |

| |To specify the number of significant digits. |

|X |7383 | |SURFACE/LAYER INDICATOR, CODED |C | |an..3 |

| |Code indicating the surface or layer of a product that is being described. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

6. Segment SEL

Segment: SEL Seal Number

Position: 0330

Group: Segment Group 5 (Equipment Details) Mandatory

Level: 2

Usage: Optional

Max Use: 9

Purpose: A segment to identify seal and seal issuer associated with the container, such as shipper, consolidator, carrier (sea), Customs or terminal operator.

Data Element Summary

Data Component

Element Element Name Attributes

|M |9308 | |SEAL NUMBER |M | |an..10 |

| |The number of a custom seal or another seal affixed to the containers or other transport unit. |

| |C215 | |SEAL ISSUER |C | | |

| |Identification of the issuer of a seal on equipment either by code or by name. |

| | |9303 |Sealing party, coded |C | |an..3 |

| |Identification of the issuer of the seal number. |

| |CA | |Carrier |

| |Party undertaking or arranging transport of goods between named points.|

| |CU | |Customs |

| |NS | |No seal on the container |

| |SH | |Shipper |

| |Party which, by contract with a carrier, consigns or sends goods with |

| |the carrier, or has them conveyed by him. |

| |TO | |Terminal operator |

| |Party which handles the loading and unloading of marine vessels. |

| |X | |Seal on left door |

|X | |1131 |Code list qualifier |C | |an..3 |

| |Identification of a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |3055 |Code list responsible agency, coded |C | |an..3 |

| |Code identifying the agency responsible for a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |9302 |Sealing party |C | |an..35 |

| |Clear text, representing the name of the issuer of the seal number. |

|X |4517 | |SEAL CONDITION, CODED |C | |an..3 |

| |To indicate the condition of a seal. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

7. Segment group 7

Group: TDT Segment Group 7: Details of Transport

Position: 0390

Group: Segment Group 5 (Equipment Details) Mandatory

Level: 2

Usage: Conditional (Optional)

Max Use: 9

Purpose: A group of segments to indicate details of the movement of containers by sea and by inland carriers, such as mode and means of transport and locations.

Comment: This group is not required by customs.

Segment Summary

Pos. Seg. Req. Max. Group:

No. ID Name Des. Use Repeat

|O |0400 |TDT |Details of Transport |M |1 | |

1. Segment TDT

Segment: TDT Details of Transport

Position: 0400 (Trigger Segment)

Group: Segment Group 7 (Details of Transport) Conditional (Optional)

Level: 2

Usage: optional

Max Use: 1

Purpose: A segment to indicate information related to the inland transport stage (road, rail or inland water), such as mode of transport, identification of the means of transport and inland carrier.

Comments: This segment is not required by customs

Data Element Summary

Data Component

Element Element Name Attributes

|X |8051 | |TRANSPORT STAGE QUALIFIER |M | |an..3 |

| |Qualifier giving a specific meaning to the transport details. |

| |1 | |Inland transport |

| |Transport by which goods are moved from or to the frontier, or between |

| |inland points. |

|X |8028 | |CONVEYANCE REFERENCE NUMBER |C | |an..17 |

| |Unique reference given by the carrier to a certain journey or departure of a means of transport |

| |(generic term). |

|X |C220 | |MODE OF TRANSPORT |C | | |

| |Method of transport code or name. Code preferred. |

| | |8067 |Mode of transport, coded |C | |an..3 |

| |Coded method of transport used for the carriage of the goods. |

| |2 | |Rail |

| |3 | |Road |

| |8 | |Inland water |

| | | | |

|X | |8066 |Mode of transport |C | |an..17 |

| |Method of transport used for the carriage of the goods. |

| |C228 | |TRANSPORT MEANS |C | | |

| |Code and/or name identifying the type of means of transport. |

| | |8179 |Type of means of transport identification |C | |an..8 |

| |Code defining the type of the means of transport being utilized. |

| |11 | |Ship |

| |31 | |Truck |

| |LM | |Logistic Move |

|X | |8178 |Type of means of transport |C | |an..17 |

| |Description of the type of the means of transport being utilized. |

| |C040 | |CARRIER |C | | |

| |Identification of a carrier by code and/or by name. Code preferred. |

| | |3127 |Carrier identification |C | |an..17 |

| |Identification of party undertaking or arranging transport of goods between named points. |

|X | |1131 |Code list qualifier |C | |an..3 |

| |Identification of a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |3055 |Code list responsible agency, coded |C | |an..3 |

| |Code identifying the agency responsible for a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

| | |3128 |Carrier name |C | |an..35 |

| |Name of party undertaking or arranging transport of goods between named points. |

|X |8101 | |TRANSIT DIRECTION, CODED |C | |an..3 |

| |Identification of the point of origin and point of direction. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X |C401 | |EXCESS TRANSPORTATION INFORMATION |C | | |

| |To provide details of reason for, and responsibility for, use of transportation other than |

| |normally utilized. |

|X | |8457 |Excess transportation reason, coded |M | |an..3 |

| |Indication of reason for excess transportation. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |8459 |Excess transportation responsibility, coded |M | |an..3 |

| |Indication of responsibility for excess transportation. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |7130 |Customer authorization number |C | |an..17 |

| |Customer provided authorization number to allow supplier to ship goods under specific freight |

| |conditions. This number will be transmitted back to customer in the dispatch advice message. |

| |C222 | |TRANSPORT IDENTIFICATION |C | | |

| |Code and/or name identifying the means of transport. |

| | |8213 |Id. of means of transport identification |C | |an..9 |

| |Identification of the means of transport by name or number. |

| |Truck ID, Train ID, Barge ID. |

|X | |1131 |Code list qualifier |C | |an..3 |

| |Identification of a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |3055 |Code list responsible agency, coded |C | |an..3 |

| |Code identifying the agency responsible for a code list. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

|X | |8212 |Id. of the means of transport |C | |an..35 |

| |Identification of the means of transport by name or number. |

|X | |8453 |Nationality of means of transport, coded |C | |an..3 |

| |Coded name of the country in which a means of transport is registered. |

|X |8281 | |TRANSPORT OWNERSHIP, CODED |C | |an..3 |

| |Code indicating the ownership of the means of transport. |

| |Refer to D.95B Data Element Dictionary for acceptable code values. |

5.5 Segment CNT

Segment: CNT Control Total

Position: 0440

Group:

Level: 0

Usage: Mandatory

Max Use: 1

Purpose: A segment to specify the number of containers in the message.

|Notes: | |Total number of containers. |

Data Element Summary

Data Component

Element Element Name Attributes

|M |C270 | |CONTROL |M | | |

| |Control total for checking integrity of a message or part of a message. |

| |Total number of containers. |

|M | |6069 |Control qualifier |M | |an..3 |

| |Determines the source data elements in the message which forms the basis for 6066 Control value.|

| |16 | |Total number of equipment |

| |Total number of equipment mentioned in the message. |

|M | |6066 |Control value |M | |n..18 |

| |Value obtained from summing the values specified by the Control Qualifier throughout the message|

| |(Hash total). |

|X | |6411 |Measure unit qualifier |C | |an..3 |

| |Indication of the unit of measurement in which weight (mass), capacity, length, area, volume or |

| |other quantity is expressed. |

5.6 Segment UNT

Segment: UNT Message Trailer

Position: 0450

Group:

Level: 0

Usage: Mandatory

Max Use: 1

Purpose: A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.

Data Element Summary

Data Component

Element Element Name Attributes

|M |0074 | |NUMBER OF SEGMENTS IN A MESSAGE |M | |n..6 |

| |Control count of number of segments in a message. |

|M |0062 | |MESSAGE REFERENCE NUMBER |M | |an..14 |

| |Unique message reference assigned by the sender. |

6. Example

UNB+UNOC:3+BE0308357159+HNTESTSMTP+100408:0946+375994+CUSREP'

UNH+375994+CODECO:D:95B:UN:ITG14+TND0000338'

BGM+34+TND00003386JBH+9'

NAD+AG+BE0308357159:EOR:147'

EQD+CN+JBH21+22G1'

RFF+ABT:11NL11234567891234'

DTM+7:201103210936:203'

LOC+165+BEANR1125:139:147'

SEL+ +NS'

CNT+16:1'

UNT+10+375994'

UNZ+1+375994'

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download