FOD Financiën · Web view2016/02/01 · PART3/48 PART7/1 PART7/9 PART7/17 PART3/17 PART3/33...
Transcript of FOD Financiën · Web view2016/02/01 · PART3/48 PART7/1 PART7/9 PART7/17 PART3/17 PART3/33...
USER IMPLEMENTATION GUIDE
G.C.-SYSTEM
BELGIAN CUSTOMS
Brussels, January 1997Customs HeadquartersAutomation Division
FOREWORD
The purpose of this User Implementation Guide is to help new and existing users of the GCA-system to implement Customs UN/EDIFACT messages.
The messages described in this document are :
CUSREP : CUSTOMS CONVEYANCE REPORT MESSAGE
CUSCAR : CUSTOMS CARGO REPORT MESSAGE
CUSRES : CUSTOMS RESPONSE MESSAGE.
These messages are based on the following rules and guidelines :
UN/EDIFACT Syntax rules
UN/EDIFACT Syntax Implementation Guidelines
UN Trade Data Interchange Directory issue D96b (CUSREP,CUSCAR,CUSRES, CUSCAR-TRANSHIPMENT)
The various code sets.
TABLE OF CONTENTS
INTRODUCTION
PART 1 : The service segments
Chapter 1 : The segment UNBChapter 2 : The segment UNZChapter 3 : The segment UNHChapter 4 : The segment UNT
PART 2 : The CUSREP message
Chapter 1 : General descriptionChapter 2 : Program specifications
PART 3 : The CUSCAR message
Chapter 1 : General descriptionChapter 2 : Program specifications
PART 4 : The CUSCAR-TRANSHIPMENT message
Chapter 1 : General descriptionChapter 2 : Program specifications
PART 5 : The CUSRES message
Chapter 1 : General descriptionChapter 2 : Program specifications
PART 7 : A summary of the used segments
INTRODUCTION
The purpose of this section is to help system designers and implementers to understand and use the guide efficiently.
The central parts of this guide are the Chapters “ Program Specifications”.
Each Customs UN/EDIFACT message is identified separately. The mapping is done by means of a table which is divided into a number of COLUMNS.
The COLUMNS are used to structure the presentation of the information. The usage of the COLUMNS are outlined below.
1 2 3 4 5 6 7
COLUMN 1 ELEMENT/COMPOSITE
This COLUMN identifies the stand alone data element or the composite data element, within the UN/EDIFACT segment structure, onto which the specific data item in COLUMN 5 is to be mapped.
COLUMN 2 COMPONENT
Where a data item is mapped onto a composite data element, this COLUMN identifies the component elements of that composite used to identify the Customs data.
COLUMN 3
M : mandatory
C : conditional
COLUMN 4 DATA REPRESENTATION
This COLUMN identifies the UN/EDIFACT structure of all data elements used to identify the Customs data in COLUMN 5. The maximum field lenght and the character type (i.e. alp-ha/numeric, numeric) is identified.
COLUMN 5 DATA NAME
This COLUMN describes the stand alone data element, the composite data element or the component data element within the UN/EDIFACT structure.
COLUMN 6 CODE
This COLUMN identifies the used qualifiers, coded.
COLUMN 7 DESCRIPTION
This COLUMN gives the description of the data needed by Customs.
PART 1
THE SERVICE SEGMENTS
CHAPTER 1 : The segment UNB
1. GENERAL INFORMATION
An interchange always starts with the segment UNB. This segment contains data concerning:- character set- sender- recipient- date/time of the transmission- reference number of the transmission- test indicator.
2. SEGMENT DESCRIPTION
UNB M : specification of the beginning of a message interchange
001 S001 M : syntax identifier
0001 M : syntax identifier a4
UNO : control organisationA : level
0002 M : syntax version number a1
2 : today's version
002 S002 M : interchange sender
0004 M : sender identification an...35
Each sender (carrier) needs a separate identification. The codes (max. 6 characters) already used in the community of a Belgian seaport are obligatory.
0007 C : not used an...4
0008 C : not used an...14
003 S003 M : interchange recipient
0010 M : identification of the recipient by the code: an...35 DOUANE
0007 C : not used an...4
0014 C : not used an...14
004 S004 M : date/time of preparation
0017 M : the date of the interchange: n6YYMMDD
0019 M : the relevant time of the day at which the interchange was prepared in: n4HHMM
005 0020 M : interchange control reference n...14
A unique reference number assigned by the sender to identify the interchange.
006 S005 C : not used
0022 M : not used an...14
0025 C : not used an2
007 0026 C : not used an...14
008 0029 C : not used a1
009 0031 C : not used n1
010 0032 C : not used an...35
0011 0035 C : test indicator n1
1 : testBlank : operational (see example below)
SYNTAX:
Test : UNB+UNOA:2+ASECO+DOUANE+950101:1245+A143++++++1'Operational : UNB+UNOA:2+ASECO+DOUANE+950101:1245+A143'
CHAPTER 2 : The segment UNZ
1. GENERAL INFORMATION
This segment identifies the end of an interchange. This segment contains the count of the separate messages within one interchange and the repetition of the reference number of the interchange given by the sender in the segment UNB.
2. SEGMENT DESCRIPTION
UNZ M : identifies the end of each interchange
001 0036 M : contains the count of the messages within the interchange n...6
0012 0020 M : contains the reference number used in the same componentelement in the UNB segment an...14
SYNTAX: UNZ+1+A143'
CHAPTER 3 : The segment UNH
1. GENERAL INFORMATION
Specification of the beginning of each individual message. This message contains data concerning:
- the name of the message- the message version number- the message release number- the controlling agency- reference number of the message assigned by the sender.
2. SEGMENT DESCRIPTION
UNH M : the beginning of the message
001 0062 M : unique reference number an...14
002 S009 M : identification of the message
0065 M : name of the message an...6
Possible values : CUSREP: CUSCAR: CUSCAR-TRANSHIPMENT: CUSRES
0052 M : message type version number an...3
D : CUSREP, CUSCAR, CUSCAR-TRANSHIPMENT, CUSRES
Restriction:The version number must be the same for all parties.
0054 M : message type release number an...3
96B : CUSREP,CUSCAR, CUSCAR-TRANSHIPMENT , CUSRES
Restriction:The release number must be the same for all parties.
0051 M : controlling agency an...2
UN : the agency responsible for the maintenance of the message type
0057 C : not used an...6
003 0068 C : common access reference an..35
CUSRES : the number of the document of the received CUSCAR/CUSREP/CUSCAR-TRANSHIP-MENT (segment BGM, data element 1004).
CUSREP, CUSCAR, CUSCAR-TRANSHIPMENT :not used
004 S010 C : not used
0070 M : not used n...2
0073 C : not used a1
SYNTAX : UNH+100001+CUSCAR:D:96B:UN’
CHAPTER 4 : The segment UNT
1. GENERAL INFORMATION
This segment identifies the end of an individual message. It contains the number of segments in the message and confirms the reference number identified in the UNH segment.
2. SEGMENT DESCRIPTION
UNT M : identifies the end of the message
001 0074 M : number of segments in the message, n...6including UNH and UNT
002 0062 M : message reference number an...14 (must be the same as the reference number in UNH)
SYNTAX : UNT+NUMBER+100001'
PART 2
CUSREPCustoms Conveyance Report Message
CHAPTER 1 : General description
1. INTRODUCTION
1.1. Scope
This message permits the transfer of general data, related to each vessel coming into a Belgian seaport, from the responsible carrier to the Belgian Customs Administration, regardless of whether there will be a discharge of goods.
The CUSREP message should be considered as the general declaration Benelux 20 = registration for Customs (hereafter called SUMMARY DECLARATION FOR TEMPORARY STORAGE).
1.2. Time of sending the message CUSREP
The CUSREP message can be sent to the computer system of the Customs 5 days prior to the estimated date of arrival of the vessel into a Belgian seaport. This message will be accepted up to 24 hours after the arrival of the vessel in the port.
It is recommended to send the CUSREP message at least two days before the estimated date of arrival of the vessel.
The CUSCAR message will not be accepted as long as the CUSREP message is not received and accepted by the computer system of the Belgian Customs.
1.3. Incorrect CUSREP-message
When the computer system of the Belgian Customs detects one or more errors, concerning format and/or content , the complete CUSREP message will be rejected and an error message (CUSRES) will be sent to the carrier.
The CUSREP message has to be re-transmitted after correction of the error(s).
2. CONTENTS
2.1. Number of the document
The number of the document is composed of :- the number of the declaration (an14);- the reference number assigned to the message by the issuer (an..21).
2.1.1. Number of the declaration
The number of the declaration is composed of the registration number and the IMO number of the vessel.
- Pos. 1 until 6 : registration number
The registration number is attributed by the port authorities and is composed of 6 digits. There are three series:
- 100000 to 799999 : manual numbering- 800000 to 899999 : automatic numbering- 900000 to 999999 : test
- Pos. 7 until 14 : IMO number
The IMO number is composed of an 8 characters.
The IMO number can be either definitive or provisional.
A provisional IMO number is a temporary number given by the port authorities, where the official IMO number has not yet been distributed. This provisional number will be used until the official IMO number is available.
A definitive IMO number begins with the letter “L”.
A provisional IMO number begins with the letter “N”.
This unique number given by the carrier will be considered as the number of the SUMMARY DECLARATION FOR TEMPORARY STORAGE and has therefore to be mentioned on all the documents and papers related to the vessel.
This unique number must be made available by the carrier to the whole port community.
2.1.2. Reference number of the message
The technical sequence number of the message is given by the issuer. The reference number is composed of maximum an..21 characters. The GCA-system accepts this reference number without any control.
2.2. Number of the declaration and reference number of a previous message
This number can be sent by the carrier in case of modification or cancellation of a previous message or replacement of the itinerary.
The number must be sent when it is an initial transmission of the CUSREP message.
The GC-system does not control this number.
2.3. The itinerary
For the purposes of the GC-system the itinerary comprises all the ports of call where the vessel has loaded (or should have loaded) excluding the original port of departure and first place of arrival in the Belgian seaport of destination.
For the initial transmission of the CUSREP the complete journey must be specified. This includes:
- original port of departure- the full itinerary- the first place of arrival in the Belgian seaport of destination.
For goods to be discharged in this seaport : the port of original departure is the first port where goods are loaded with a destination of that Belgian seaport.
The UNLOCODE (ISO ALPHA 2 code and abbreviation of the port) is used for the announcement of the different ports. For certain pre-determined EU-ports, the following indication is needed: “free zone”.
The first place of arrival in the Belgian seaports are coded on a national basis.
2.4. Details of transport
The following information is needed:- name and nationality of the vessel- estimated time of arrival of the vessel.
The name of the vessel has to be written in plain text.
The nationality of the vessel is indicated by the ISO ALPHA 2 code.
If the vessel navigates on an itinerary wherefore a licence of a ‘line service’ has been issued, the number of this licence must be reported.
3. MODIFICATION, REPLACEMENT OR CANCELLATION
3.1. Modification of accepted data
Data which must not be modified :- the document number- the itinerary , with exception of the port of departure and the (first) place of
arrival in the Belgian seaport of destination.
Data which can be modified :- the name of the vessel- the nationality of the vessel- the (first) place of arrival in the Belgian seaport of destination- the port of departure- the estimated date of arrival - licence number of the ‘line service’.
Modifications can only be accepted when:1. the period of temporary storage (warehousing) is not expired2. the SUMMARY DECLARATION FOR TEMPORARY STORAGE is not
presented3. the modification is done by the responsible carrier.
3.2. Cancellation of accepted data
The cancellation of the data of the message can only be accepted when:1. no CUSCAR message has been received2. the SUMMARY DECLARATION FOR TEMPORARY STORAGE has not
been presented3. the period of temporary storage (warehousing) has not expired4. the cancellation is done by the responsible carrier.
The local customs can intervene when these conditions are not fulfilled (e.g. when the vessel is not landed in the port of Antwerp and CUSCAR messages have been transmitted).
3.3. Modification of an itinerary
When a modification to the itinerary is needed, the whole itinerary must be re-transmitted. A change of the (first) place of arrival in the port of Antwerp and /or the place of departure will not be considered as a replacement but rather as a modification.
The replacement of the itinerary can only be accepted when:1. the period of temporary storage (warehousing) is not expired2. the IMO FAL 1 is not presented3. the replacement is done by the responsible carrier.
CHAPTER 2 : Program specifications
1. VERSION
Release : 96BVersion : DDate : 09/96
2. THE DATA SEGMENTS
Only the following segments are used within the CUSREP message:
BGM : beginning of the message
GROUP 1 : RFF : reference
GROUP 2 : LOC : place/location identification
GROUP 8 : TDT : details of the transport
DTM : date/time/period
3. BRANCHING DIAGRAM
┌─────────┬──────────┬──────────┐ │ │ │ │ ┌──┴──┐ │ │ │ │ BGM │ │ │ │LEVEL 0 ├──┬──┤ │ │ │ │M │ 1│ │ │ │ └──┴──┘ │ │ │ ┌──┴──┐ ┌──┴──┐ ┌──┴──┐ │ GR1 │ │ GR2 │ │ GR8 │ ├──┬──┤ ├──┬──┤ ├──┬──┤ │C │ 1│ │C │99│ * │C │ 1│ *LEVEL 1 ├──┴──┤ ├──┴──┤ ├──┴──┤ │ RFF │ │ LOC │ │ TDT │ ├──┬──┤ ├──┬──┤ ├──┬──┤ │M │ 1│ │M │ 1│ │M │ 1│ └──┴──┘ └──┴──┘ └──┼──┘ │ ┌──┴──┐ │ DTM │ LEVEL 2 ├──┬──┤ │C │ 1│ └──┴──┘
(*) When it is an initial transmission then these segments are Mandatory
4. SEGMENTS and SEGMENT GROUPS
4.1. The segment BGM
BGM : beginning of message
FUNCTION : to indicate the type and function of a message and to transmit the identifying number
USAGE : M
C002 M document/message name
C106 M document/message identification
1001 M n3 document/message name, coded
933 declaration (arrival)
1004 M an...35 document/message number
the number of the document
1225 M n1 message function, coded 1459
cancellationchangereplaceinitial transmission
SYNTAX :BGM+933+100000L9999999001+9'
4.2. The GROUP 1
The segment RFF within the GROUP 1
RFF : reference
FUNCTION : to identify a previous message
USAGE : C
C506 M reference
1153 M a3 reference qualifier
ACW reference number previous message
1154 M an...35 reference number
SYNTAX : RFF+ACW+100000L9999999001'
4.3. The GROUP 2
The segment LOC within the GROUP 2
LOC : place/location identification
CONDITION LOC WITHIN THE GROUP 2:
The function qualifier in the segment BGM has to be equal to 4 (modification of the place of departure and/or first place of arrival) or 5 (the replacement of the itinerary with exception of the place of departure and/or the first place of arrival) or 9 (initial transmission of the itinerary).
FUNCTION : to identify the place/port of departure, loading, destination, place of first entry in the BLEU and (first) place of arrival in the port ofAntwerp (= itinerary)
USAGE : C (see above)
3227 M n...3 place/location qualifier 591356064
place of departureport of loadingport of entry in the BLEU (**)place of arrival without dischargefirst place of discharge
C517 M location identification
3225 M an...5 place/location identification
see (***)
1131 C n3 code list qualifier 131139140
free zone (****)no UN/LOCODE (*****)berth place (*****)
3055 C n3 responsible agency, coded
147ZZZ
Belgian Customs (*****)mutually defined (******)
SYNTAX : LOC+5+country-port of departure’ LOC+9+country-port of loading’ LOC+9+country-port of loading:131:147' LOC+135+country-port of entry’ LOC+64+berth place:140:ZZZ’
(**) For the GCA-system the default port of first arrival is Antwerp.When Antwerp is the first port of entry in the BLEU the LOC-segment with the qualifier 135 within the simple data-element 3227 is not needed.
(***) When the qualifier 135 is used in the simple data-element 3227, the UN/LOCODE (UN/ECE recommendation n° 16 ) is used in the data-element 3225.
When the qualifiers 5 or 9 are used in the simple data-element 3227, the UN/LOCODE (UN/ECE recommendation n° 16) is used in the data-element 3225 if the goods are not loaded in a free zone of an EC-port. If the goods are loaded in such a free zone then the codes mentioned in annex 1 are used.
When the qualifiers 60 or 64 are used in the simple data-element 3227, the local codes of the berth places are used.
(****) When the qualifiers 5 or 9 are used in the simple data-element 3227 in combination with the code of a free zone in an EC-port then the qualifier 131 in the component data-element 1131 and the code 147 in the component data-element 3055 are used.
(*****) When the UN/LOCODE for a place/port (UN/ECE recommendation n° 16) is not registered then the qualifier 139 in the component data-element 1131 and the code ZZZ in the component data-element 3055 are used.
When the qualifiers 60 or 64 are used in the simple data-element 3227 then the qualifier 140 in the component data-element 1131 and the code ZZZ in the component data-element 3055 are used.
In all the other cases the component data-elements 1131 and 3055 are not used.
REMARK : Within the GROUP 2 only 97 repetitions of the segment LOC are possible with the place/port qualifiers 9 or 135 in the simple data-element 3227.
4.4. The GROUP 8
CONDITION GROUP 8 :
The function qualifier in the segment BGM has to be equal to 4 (modification of the name, nationality, estimated date of arrival) or 9 (initial transmission of the basic data).
FUNCTION : a group of segments to indicate details of the means of transport
USAGE : C (see above)
CONTENT GROUP 8 :
- the segment TDT : M : details of transport- the segment DTM : C : associated date/time of arrival
REMARK:
When the function qualifier in the segment BGM is equal to 4 and only the estimated date/time of arrival has to be changed then both segments (TDT and DTM) have to be present in the GROUP 8.
4.4.1. The segment TDT within the GROUP 8
TDT : details of the transport
FUNCTION : to specify the transport details such as mode of transport, means of transport and identification of the means of transport
USAGE : M
8051 M n2 transport stage qualifier 13 at destination
8028 C an...7 licence n° of the ‘line service’
C222 M transport identification
8212 C* an...35 name of the vessel
8453 C* a2 nationality of the vessel,coded
iso 3166 - alpha 2 code
SYNTAX : TDT+13+++++++:::name:nat’TDT+13+BE001++++++:::name:nat
(*) When it is an initial transmission always M(andatory) (see also remark above).
4.4.2. The segment DTM within the GROUP 8
DTM : date/time/period
FUNCTION : to specify date, and/or time, or period
USAGE : C
C507 M date/time/period
2005 M n3 date/time/period qualifier 132 estimated date of arrival
2380 M n8 date of arrival CCJJMMDD
SYNTAX : DTM+132:19960101'
PART 3
CUSCAR
Customs Cargo Report Message
CHAPTER 1 : General description
1. INTRODUCTION
1.1. Scope
This message permits the transfer of the consignments details of each incoming vessel in the port of Antwerp for which a CUSREP message has already been sent by the responsible carrier and was accepted by the computer system of the Belgian Customs. The CUSCAR message should be considered as the manifest 126.
The GCA-system accepts CUSCAR messages from different carriers for one received and accepted CUSREP message.
1.2. Time of sending the CUSCAR message
As long as the related CUSREP message is not received and accepted by the computer system of the Belgian Customs the CUSCAR messages will not be accepted.
The CUSCAR message can be sent to the computer system of the Customs 5 days prior to the estimated arrival of the vessel in the port of Antwerp.
It is recommended to transmit the CUSCAR message at least 2 days before the estimated time of arrival of the vessel in the port of Antwerp.
The CUSCAR message will be accepted until 24 hours after the arrival of the vessel in the port of Antwerp.
All the related declarations will be rejected when the CUSCAR messages are not received and accepted by the GCA-system.
1.3. Incorrect CUSCAR message
When the computer system of the Belgian Customs detects one or more format errors, the complete CUSCAR message will be rejected and will have to be re-transmitted after correction of the error(s).
When the computer system of the Belgian Customs detects one or more errors within the general data of the containers, the CUSCAR message will be accepted1. A suitable error response will be given and the general data of the erroneous container(s) will have to be re-transmitted after correction. Two procedures are possible:
1 Only the correct general data per container will be stored
a. all general data for the containers can be re-transmitted ( see 3.1.)
b. only the general data for the rejected containers is re-transmitted as an initial transmission (after correction of the errors).
A distinction is made between errors concerning parties (shipper, notifier, consignee) and errors concerning details of the goods :
- When an error is made on the level of the involved parties, the CUSCAR message is accepted2, an error message (CUSRES) is given and the erroneous data has to be re-transmitted after correction. Two procedures are possible:
a. all the data of the consignment (b/l) can be re-transmitted ( see 3.1)
b. Only the erroneous data concerning the involved parties are re-transmitted after correction (see 3.2).
- When an error is made on the level of the details of the goods (b/l) the CUSCAR message is accepted3, an error message (CUSRES) is given and all data (including the data of the involved parties) from the rejected consignment must be re-transmitted after correction. This correction will be considered as an initial transmission.
2. CONTENTS
2.1. Document number
The document number is composed of :- the number of the declaration (14 an characters);- the reference number assigned to the message by the issuer (max.
an..21 characters).
2.1.1. Number of the declaration
The number of the declaration is composed of the registration number and the IMO number of the vessel.
- Pos. 1 to 6 : registration number .
The registration number is attributed by the port authorities and is composed of 6 digits. There are three series:
2 Only the correct details of the goods and the correct involved parties are stored
3 Only the details of the correct consignments (b/l) are stored
- 100000 to 799999 : manual numbering- 800000 to 899999 : automatic numbering- 900000 to 999999 : test
- Pos. 7 to 14 : IMO number
The IMO number is composed of an 8 characters.
The IMO number can be either definitive or provisional.
A provisional IMO number is a temporary number given by the port authori-ties, if the official IMO number has not yet been distributed. This provisional number will be used until the official IMO number is available.
A definitive IMO number begins with the letter “L”.
A provisional IMO number begins with the letter “N”.
This unique number is considered as the unique reference number of the Summary Declaration for Temporary Storage. This unique number must be made available by the carrier to the whole port community.
2.1.2. Reference number of the message
The technical sequence number of the message given by the Carrier. The sequence number is composed of maximum an..21 characters. The GCA-system accepts this sequence number without any control.
2.2. Document number and reference number of a previous message
This number can be given by the carrier in case of modification, replacement or cancellation of a previous CUSCAR message. The GC-system does not control this number.
2.3. General data of the containers
The following data has to be given:
- number of the container- kind, type and measurements- gross weight: total weight of the goods including the packages within
one container (without the weight of the container).- Transhipment identifier- In case of Green lanes the affixed seals
2.4. Consignment data
2.4.1. Identification of the consignment
- Number of the consignment : continuous numbering per carrier, starting with the number one ( 1 B/l = 1 article number)
- B/l number .
The number of the consignment (article) in combination with the unique identification code of the carrier (firm-code) gives a unique reference to the consignment within the CUSCAR messages.
2.4.2. Contents of the consignment
- the total amount of units- the total gross weight in kg- the port of loading, the port of destination and the
place of discharge = RTO/terminalcode in port of arrival,- The RTO of destination - the data of the shipper, the consignee, the notifier, the broker and the
importer- for green lanes : Approved consignor, ultimate consignee.
The data of the involved parties has to be announced via the unique identification code of the carrier (firm-code). If none, name and address of the form is needed.The usage of the unique identification code of the carrier (firm-code) is obliged for the brokers and the importers dealing with Customs declarations.The data is important in case of none clearance of the consignment.
In case of “Green lanes” the EORI number has to be mentioned for the following parties : Approved consignor, ultimate consignee.
In case of RTO - place of discharge and of destination – the EORI number has to be given in NAD.
- continious item number within the consignment starting from 1.The following data has to be given for each item :
- number of packages/containers mentioned on the B/l. Initially the expected totals. The carrier has to correct these totals in conformity with the report of discharge.
- kind of packages (can be a container). The international codes have to be used. The qualifier “CN” is used for container
- description of the goods (business name)- gross weight in kg (when it is a container, the weight of the container is
excluded)- Customs status of the goods.
The following data applies only to a container transport:
- for each item within an article only one container number is allowed and the total number of packages has to be mentioned as well. This principle will not be applicable from the start of the CCRM system.
2.5. Control data
Total number of consignments within the CUSCAR message.
3. REPLACEMENT, CANCELLATION OR ADDITION
3.1. Replacement of accepted of data
The replacement of data has to be seen in the scope of the result of the report of discharge. When differences are found between the already stored information and the results of the discharging, the complete data of the consignment has to be sent as a replacement. In other words, only the consignments with differences have to be re-transmitted as a replacement.
Data which can not be replaced:- the document number- the container number in itself or with it’s content- the consignment number in itself.
Data which can be replaced:- the complete data mentioned in 2.3.- the complete data of a consignment.
The replacement of general container data will only be accepted when the replacement is done by the responsible carrier within 10 days after the actual arrival of the vessel in the port of Antwerp.
The replacement of a consignment can only be accepted when:
1. the replacement is done by the responsible carrier2. it is within 20 days after the arrival of the vessel in the port of Antwerp3. it is in line with the already accepted customs declarations.
3.2. Addition of data
The involved parties for a consignment.The RTO of destination together with the EORI number of the holder of the RTO.
3.3. Cancellation of accepted data
Data which can not be cancelled:- the number of the declaration/the message- a part of the general data of a container- a part of a consignment
Data which can be cancelled:- a container number itself (general data of the
container) - the involved parties of a consignment- the consignment itself.
The cancellation of a container number with complete data set can only be accepted if the transmission is done by the responsible carrier within 20 days after the actual arrival of the vessel in the port of Antwerp.
The cancellation of an involved party can only be accepted when the transmission is done by the responsible carrier.
The cancellation can only be accepted when :
1. the transmission is done by the responsible carrier2. within 10 days after the actual arrival of the vessel in the port of Antwerp3. no customs declarations are validated against the
manifest.
If any of these conditions are not fulfilled an intervention of the local customs is needed.
3.4. Movements between RTO’s
Due to the UCC the movement of goods between RTO’s is a new feature.
PROCESS:
The place of discharge is always considered as the RTO of arrival. If an RTO of destination is available in the first CUSCAR it means that the goods are moved to the RTO of (first) destination. The RTO of (first) destination can be added afterwards. If a RTO of destination is added and in the system a RTO of destination was already available this means that the goods are moved from the RTO already available in the system to the new given RTO.The following controls have to be done (based on EORI):
MS Customs involved RTO holders involved ConditionsBE One No special conditionsBE + other MS ° One RTO holder is AEO CBE Two Both RTO holders are
AEOCBE + other MS ° Two Both RTO holders are
AEO C
° no yet applicable
CHAPTER 2 : Programming specifications
1. VERSION
Release : 96Bversion : Ddate : 09/96
2. THE DATA SEGMENTS
Only the following segments are used within the CUSCAR message:
BGM: beginning of the message
GROUP 1 : RFF : reference
GROUP 5 : EQD : equipment detailsTSR : transport requirementsMEA : measurements
CNT : control total
GROUP 7 : CNI :consignment information
GROUP 8 : RFF referenceCNT control totalLOC place/location identification
GROUP 11: NAD name and address
GROUP 13: QTY quantity
GROUP 14: GID goods item detailsFTX free text (description)MEA measurements SGP split goods placement CST status of the goods
3. BRANCHING DIAGRAM
┌─────────┬──────────┬──────────┬──────────┐ │ │ │ │ │ ┌──┴──┐ │ │ │ │ │ BGM │ │ │ │ │LEVEL 0 ├──┬──┤ │ │ │ │ │M │ 1│ │ │ │ │ └──┴──┘ │ │ │ │ ┌──┴──┐ ┌───┴───┐ ┌──┴──┐ ┌───┴───┐ │ GR1 │ │ GR5 │ │ CNT │ │ GR7 │ LEVEL 1 ├──┬──┤ ├──┬────┤ ├──┬──┤ ├──┬────┤ │C │ 1│ │C │9999│ │C │ 1│ │C │9999│ ├──┴──┤ ├──┴────┤ └──┴──┘ ├──┴────┤ │ RFF │ │ EQD │ **** │ CNI │ ├──┬──┤ ├──┬────┤ ├──┬────┤ │M │ 1│ │M │ 1│ │M │ 1│ └──┴──┘ └──┼────┘ └──┼────┘ ┌───────────┤ │ │ │ │ ┌──┴──┐ ┌──┴──┐ ┌──┴────┐ │ TSR │** │ MEA │ ** │ GR8 │ LEVEL 2 ├──┬──┤ ├──┬──┤ ├──┬────┤ │C │ 1│ │C │ 1│ │M │ 1│ └──┴──┘ └──┴──┘ ├──┴────┤ │ RFF │ ├──┬────┤ │M │ 1│ └──┼────┘ ┌─────────┬─────────┬─────────┬───────────┤ │ │ │ │ │ ┌──┴──┐ ┌──┴──┐ ┌──┴──┐ ┌──┴──┐ ┌──┴────┐ │ CNT │ │ LOC │ │ GR11│ │ GR13│ │ GR14 │ ***LEVEL 3 ├──┬──┤ ├──┬──┤ ├──┬──┤ ├──┬──┤ ├──┬────┤ │C │ 2│ │C │ 3│ │C │ 5│ │C │ 1│ │C │9999│ └──┴──┘ └──┴──┘ ├──┴──┤ ├──┴──┤ ├──┴────┤ *** *** │ NAD │ │ QTY │ │ GID │ ├──┬──┤ ├──┬──┤ ├──┬────┤ │M │ 1│ │M │ 1│ │M │ 1│ └──┴──┘ └──┴──┘ └──┼────┘ │ │ ┌─────────┬─────────┬─────┴───┐ │ │ │ │ ┌──┴──┐ ┌──┴──┐ ┌──┴──┐ ┌──┴──┐ │ FTX │ │ MEA │ │ SGP │* │ CST │LEVEL 4 ├──┬──┤ ├──┬──┤ ├──┬──┤ ├──┬──┤ │M │ 1│ │M │ 1│ │C │99│ │M │ 1│ └──┴──┘ └──┴──┘ └──┴──┘ └──┴──┘ * When it concerns container transport then always
Mandatory** When it concerns a cancellation then Conditional*** When it concerns not an addition then Mandatory**** When it concerns the GR7 then always Mandatory
SEL
C 1
REMARK : The GR5 and GR7 can be transmitted separately when it concerns initial transmissions.
4. SEGMENTS and GROUPS of SEGMENTS
4.1. The segment BGM
BGM : beginning of message
FUNCTION : to indicate the type and function of a message and to transmit the identifying number
USAGE : M
C002 M document/message name
1001 M n3 document/message name, coded
933 declaration (arrival)
C106 M document/message identification
1004 M an..35 document/message number
1225 M n1 message function, coded
2359
additioncancellationreplaceinitial transmission
SYNTAX :BGM+933+100000L9999999001+9'
4.2. The GROUP 1
FUNCTION : identification of the previous message
USAGE : C
CONTENT GROUP 1:
- the segment RFF : M : reference
4.2.1. The segment RFF within the GROUP 1
RFF : reference
FUNCTION : identification of the previous message
USAGE : C
C506 M reference
1153 M a3 reference qualifier
ACW reference number previous message
1154 M an..35 reference number
SYNTAX : RFF+ACW+100000L9999999001'
4.3. The GROUP 5
CONDITION GROUP 5:
The function qualifier in the segment BGM has to be equal to :
3 = cancellation of ONE container(number) i.e. only the EQD segment
5 = replacement of all the stored details of the container(s) in the GCA-system related to the manifest. In other words all the stored details of the container(s) will be removed from the GCA-system and the new details of the container(s) will be stored i.e. GROUP 5
9 = initial transmission of the details of a container i.e. GROUP 5
REMARK:
The re-transmissions of a rectified container(number) has to be considered as an initial transmission.
FUNCTION : a group of segments to identify the details of the equipment, including information related to measurements
USAGE : C (see above)
CONTENT GROUP 5:
- the segment EQD : M : equipment details- the segment TSR : C : transport service
requirements- the segment MEA : C : measurements
4.3.1. The segment EQD in the GROUP 5
EQD : equipment details
FUNCTION : to identify a unit of equipment
USAGE : M
8053 M a2 equipment qualifier CN
container
C237 M equipment identification
8260 M an..17 equipment identification number
number of the contai-ner
C224 M equipment size and type
8155 M n4 equipment size and type identification
ISO 6346
8077 C *
8249 C Equipment status 6 Transhipment
8169 M n1 full/empty indicator, coded 4578
empty **not emptyFCL + LCLFCL + FCL
SYNTAX : EQD+CN+mart123456+2010+++5'
** 4 empty container (shipper owned = only for the investigation service of theBelgian Customs)
4.3.2. The segment TSR within the GROUP 5
TSR : transport requirements
FUNCTION : to specify the contract, carriage conditions, service and priority requirements for the transport
USAGE : C : When the function qualifier in the segment BGM of the message is equal to 3 (cancellation of one container number) then the segment TSR is not required.
M : When the function qualifier in the segment BGM of the message is equal to 5 (replacement of all the stored details of the container(s) related to the manifest126 in the GCA-system) or equal to 9 (initial transmission) then the segment TSR is required.
C536 C *
C233 M service
7273 M n1 service requirement, coded
2 3
FCL (full loads)LCL (less than full loads)
1131 C *
3055 C *
7273 M n1 service requirement, coded
23
FCL (full loads)LCL (less than full loads)
SYNTAX : TSR++2:::2'
4.3.3. The segment MEA within the GROUP 5
MEA : measurements
FUNCTION : to specify physical measurements, includingweights
USAGE : C : When the function qualifier within the segment BGM of the message is equal to 3 (cancellation of the details of a container) then the segment MEA is not required.
M : When the function qualifier within the segment BGM of the CUSCAR message is equal to 5 (replacement of all the stored details of the container(s) in the GCA-system) or equal to 9 (initial transmission) then the segment MEA is required.
6331 M a2 measurement application qualifier
WT weight
C502 M measurement details
6313 M a1 measurement dimension, coded
G see **
C174 M value/range
6411 M a3 measurement unit qualifier KGM weight in Kg (UN/ECE recommendation n° 20)
6314 M n...9 measurement value see **
SYNTAX : MEA+WT+G+KGM:12540'
** The gross weight is the total weight without decimals of the goods in the container including the weight of the packages but without the weight of the container itself.
4.3.4. The segment SEL within the GROUP 5
SEL : Seal number
FUNCTION : to specify the seal number or a range of sealnumbers.
USAGE : C : When the function qualifier within the segment BGM of the message is equal to 3 (cancellation of the details of a container) then the segment SEL is not required.
M : for green lanes
9308 C An..35 Transport unit seal identifier
Number of the seal
C215 M Seal issuer
9303 M An..3 Sealing party name,code
AB UnknownAC Quarantine agencyCA CarrierCU CustomsSH ShipperTO Terminal operator
4517 CAn..3
Seal condition code
C208 Identity number range
4525 C An..3 Seal type code 1 = mechanical2 = electronic
Only 9308 and C215/9303 are mandatory.If Green lanes at least one seal number has to be mentioned.
4.4. The segment CNT
CNT : control total
CONDITION CNT WITHIN THE CUSCAR MESSAGE:
The segment CNT has to be followed by one or more GROUP(S) 7 in the CUSCAR message.
FUNCTION : to provide message (consignments) control total
USAGE : C (see above)
C270 M control
6069 M n2 control qualifier
10 total number of consignments
6066 M n...4 control value Number of consignments
SYNTAX : CNT+10:20'
4.5. The GROUP 7
CONDITION GROUP 7:
The function qualifier in the segment BGM has to be equal to:
2 = addition of involved parties of a consignment ==> CNI + RFF+GR11(N-AD)
3 = - cancellation of a consignment ==> CNI +RFF- cancellation of one or more involved parties of a
Consignment ==>CNI + RFF+ GR11(NAD)
5 = replacement of already stored details of a consignment in the GCA-system. This means that the stored details of the consignment will be replaced by the data of the received message ==> GROUP 7
9 = initial transmission of a consignment ==> GROUP 7
REMARK:
The retransmissions of a consignment after correction of the error(s) has to be considered as an initial transmission.
FUNCTION : a group of segments to provide details of theconsignment(s)
USAGE : C (see above)
CONTENT GROUP 7:
- the segment CNI : M : consignment information- the GROUP 8 : M : a group of segments
specifying the details of each consignment.
4.5.1. The segment CNI within the GROUP 7
CNI : consignment information
FUNCTION : to identify one consignment
USAGE : M
1490 M N ...4 Consolidation item number = article number
Unique within the manifest per carrier
C5O3 C Document/message details1004 C an..35 Document/message number1373 C an..3 Document/message
status,coded
SYNTAX : CNI+1’
4.5.2. The GROUP 8 within the GROUP 7:
FUNCTION : a group of segments to specify the heading of a consignment
USAGE : M
CONTENT OF THE GROUP 8 :
- the segment RFF : M : reference- the segment CNT : C : control totals on detail level of the
consignment- the segment LOC : C : place/location- the GROUP 11 : C : NAD: name and address- the GROUP 13 : C : QTY : measurements- the GROUP 14 : C : a group of segments to
specify the details of a consignment
4.5.2.1. The segment RFF within the GROUP 7/GROUP 8
RFF : reference
FUNCTION : identification of the b/l
USAGE : M
C506 M reference
1153 M a2 reference qualifier MBBM
master b/lb/l
1154 M an..14 reference number number b/l
SYNTAX : RFF+BM:b/l’RFF+MB:b/l’
4.5.2.2. The segment CNT within the GROUP 7/GROUP 8
CNT : control total
CONDITION CNT WITHIN THE GROUP 7/GROUP 8:
The function qualifier in the BGM segment has to be equal to 5 (replacement of a consignment) or 9 (initial transmission of a consignment).
FUNCTION : to specify total consignment quantity and weight
USAGE : C (see above)
C270 M control
6069 M n1 control qualifier
78
total gross weighttotal amount of pieces
6066 M n..9 control value number of pieces/weight
SYNTAX : CNT+7:158524'and CNT+8:12'
REMARK :
If the segment CNT is needed - in accordance with the above condition - then it must appear twice within the GROUP 7/GROUP 8:
- once with the control qualifier 7 and- once with the control qualifier 8.
If bulk and for both qualifiers, the content of the component data element 6069 and 6066 has to be the same and it concerns a net weight in kg.
4.5.2.3. The segment LOC within the GROUP 7/GROUP 8
LOC : identification place/location
CONDITION LOC WITHIN THE GROUP 7/GROUP 8:
The function qualifier in the BGM segment has to be equal to 5 (replacement of a consignment) or 9 (initial transmission of a consignment).
FUNCTION : to specify a place/port of loading, destination and the place of discharge.
USAGE : C (see above)
3227 M n..2 place/location qualifier 891118
port of destinationport of loadingplace of discharge (RTO location (*))RTO of (first) destination (*)
C517 M location identification
3225 M an..35 place/location identification
see **
1131 C n3 code list qualifier 131139140
free zone (see ***)no UN/LOCODE (see ****)berth place (see ****)
3055 C n3 code responsible agency, coded
147ZZZ
Belgian Customs (see ***)mutually defined (see ****)
SYNTAX : LOC+8+country-port of destination’ LOC+9+country-port of loading’ LOC+9+country-port of loading:131:147' LOC+11+RTO:140:ZZZ’ LOC+18+RTO:139:147’
* The location code of the RTO where goods are placed under Temporary Storage.If code 18 in LOC/3227 the terminalcode of LOC/3225 is also used for CCRM.
** The UN/LOCODE of the UN/ECE recommendation n° 16 in the simple data-element 3225 is used in combination with the place/port qualifier 8 in the simple data-element 3227.
When the goods are not loaded in a free zone of a determined EC-port then the UN/LOCODE of the UN/ECE recommendation n° 16 in the simple data-element 3225 is used in combination with the place/port qualifier 9 in the simple data-element 3227.
When the qualifier 11 or 18 is used in the simple data-element 3227 then the location codes of the terminal (RTO) are used in the simple data-element 3225.
*** When the qualifier 9 in the simple data-element 3227 is used in combination with a code of a free zone in a determined EC-port in the component data-element 3225 then the qualifier 131 in the component data-element 1131 and the code 147 in the component data-element 3055 are used.
**** When the UN/LOCODE is not known within the GCA system then the qualifier 131 in the component data-element 1131 and the code ZZZ in the component data-element 3055 are used.
When the qualifier 11 is used in the simple data-element 3227 then the qualifier 140 in the component data-element 1131 and the code ZZZ in the component data-element 3055 are used.
When the qualifier 18 is used in the simple data-element 3227 the the qualifier 139 in Component data-element 1131 and the code 147 in component data-element 3055 are used
In all the other cases the component data-elements 1131 and 3055 are not used.
REMARK :
When the segment LOC is needed in the GROUP 7/GROUP 8 it has to appear at least three times:
- once with the place/location qualifier 8 and - once with the place/location qualifier 9 and- once with the place/location qualifier 11.
4.5.2.4. The GROUP 11 within the GROUP 7/GROUP 8
FUNCTION : to identify the involved parties
USAGE : C : When the function qualifier in the segment BGM of the message is equal to 5 (replacement of all data already stored in the GCA-system) or 9 (initial transmission of a consignment) then GROUP 7/GROUP 8/GROUP 11 is conditional.
M : When the function qualifier in the segment BGM of the message is equal to 2 (addition of involved parties to a consignment) then GROUP 7/GROUP 8/GROUP 11 is mandatory.
4.5.2.4.1. The segment NAD within the GROUP 7/GROUP 8/ GROUP 11
NAD : name and address
FUNCTION : name and address of the shipper, the consignee, the notifier, the broker or the importer.
USAGE : M
3035 M a2 party qualifier AQUCCGCACBCNCXCZIMTR*AP*
Approved consignorUltimate consigneeCarriers agentcarrierCustoms brokerconsigneenotifiershipperimporterTerminal(RTO) of destination ***Terminal (RTO) of discharge ****
C082 C party identification details
see **
3039 M an..35 party id. identification If CB or IM in 3035 = code Customs brokerIf AQ, UC, = or EORI number or not usedIF TR = EORI of the holder of the RTO of destination*****If AP = EORI of the holder of the RTO of discharge*****
1131 M a3 code list qualifier ZZZ mutually defined
3055 M n3 responsible agency,coded
147 BE Customs
C058 C name and address see **
3124 M an..35 name and address line
3124 C an..35 name and address line
3124 C an..35 name and address line
3124 C an..35 name and address line
3124 C an..35 name and address line
SYNTAX : NAD+CX++customs:street 12:antwerp’ NAD+CB+customs:zzz:147'
** If the code value in data element 3035 is CB or IM, data element 3039 of composite C082 must be used to identify the customs broker or importer. In these cases the component data-element 3039 is filled in, in combination with the qualifier ZZZ in the component data-element 1131 and the code 147 in the component data-element 3055.If in 3035 code = AQ,UC and in 3039 = EORI Number “Green Lanes is applicable”.
Condition EORI number is existing and has the according AEO or MRA status. If this condition is not applicable for one of the codes AQ,UC in 3035 no status “Green Lanes” is granted and no error is given.
In all the other cases the composite data-element C082 is not used.
Additional tests for the status “green lanes”:
- The following parties have to be AEO with status AEOS ( ultimate consignee , approved consignor).
- Within Group7/Group8/Group14/SPG at least one container number has to be mentioned.
*** TR is only used together with code 18 in the GROUP 7/GROUP 8/LOC/3227.
**** AP is only used together with code 11 in LOC/3227
***** Based on EORI number the AEO status C will be verified. If no AEOC error code has to be given because no movement between RTO’s is possible. Both EORI numbers do need the AEOC status. Exception : if the RTO holder is the same no AEOC status is needed.
4.5.2.5. The segment QTY within the GROUP 7/GROUP 8/GROUP 13
QTY : quantity
CONDITION QTY WITHIN THE GROUP 7/GROUP 8/GROUP 13:
The segment QTY can only be used when it is an overlanded consignment
FUNCTION : to specify a pertinent quantity
USAGE : C (see above)
C186 M quantity details
6063 M n3 quantity qualifier 121 overlanded
6060 M n1 quantity 0
SYNTAX : QTY+121:0'
4.5.2.6. The GROUP 14 within the GROUP 7/GROUP 8
CONDITION GROUP 14 WITHIN THE GROUP 7/GROUP 8
The function qualifier in the segment BGM has to be equal to 5 (replacement of a consignment) or 9 (initial transmission of a consignment).
FUNCTION : to specify the item details including number and type of packages, goods description, measurements, indicator for split goods placement, etc. .
USAGE : C (see above)
CONTENTS OF GROUP 14:
- the segment GID : M : goods item details- the segment FTX : M : free text (description of goods)- the segment MEA : M : measurements- the segment SGP : C : split goods placement- the segment CST : M : Customs status of the goods
REMARK :When the function qualifier in the segment BGM is equal to 5 (replacement of a consignment) then the item numbering has to be the same as the initial item numbering.
Example :A b/l containing 3 item numbers was transmitted with the function qualifier 9 in the segment BGM:...........GID+1+10:CN’...........GID+2+20:CN’...........GID+3+15:CN’
After discharge there were only two items found with item numbers 2 and 3:The replacement is as follows:...........GID+2+20:CN’...........GID+3+15:CN’
4.5.2.6.1. The segment GID within the GROUP7/GROUP8/GROUP14
GID : goods item details
FUNCTION : to indicate totals of a goods item.
USAGE : M
1496 M n..4 goods item number sequence number of the goods within the b/l. The numbering always begins with number 1.
C213 M number and type of packages
7224 M n..8 number of packages see **
7065 M a2 type of packages UN/ECE recommendation n 21 ***
SYNTAX : GID+1+10:CN’
** If bulk : in component data element 7224 always “0”.
***If bulk only the following codas are applicable: VG, VL, VO, VQ,, VR en VY (only for those codes a margin of 10% is applicable.
REMARK:
Within one article no mix of bulk en conventional goods is allowed
4.5.2.6.2. The segment FTX within the GROUP7/GROUP8/GROUP14
FTX : free text
FUNCTION : description of the goods
USAGE : M
4451 M a3 free text qualifier AAA description of the goods
4453 C *
C107 C *
C108 M free text see **
4440 M an..26 description of the goods
4440 C an..26 description of the goods
4440 C an..26 description of the goods
SYNTAX : FTX+AAA+++description’
** The component data-element 4440 has a maximum number of repetitions of 3.The maximum field length permitted for each repetition is a26.
4.5.2.6.3. The segment MEA within the GROUP7/GROUP8/GROUP14
MEA : measurements
FUNCTION : to specify physical measurements, including weights and counts
USAGE : M
6311 M a2 measurement application qualifier
WT weight
C502 M measurement details
6313 M a1 measurement dimension, coded
G see **
C174 M value/range
6411 M a3 measurement unit qualifier KGM weight in kg (UN/ECErecommendation nr. 20)
6314 M n..9 measurement value gross weight without deci-mals
SYNTAX : MEA+WT+G+KGM:12345'
** The gross weight is the total weight without decimals of the goods in the container, including the weight of the packages, but without the weight of the container itself.
If bulk : expected net weight without decimals
4.5.2.6.4. The segment SGP within the GROUP7/GROUP8/GROUP14
SGP : containers
FUNCTION : to specify the placement of goods in relation to equipment.
USAGE : C : When the goods are not loaded in a container
M : When the goods are loaded in a container.
C237 M equipment identification
8260 M an..17 equipment identification
container number
7224 C n..6 number of packages see **
SYNTAX : SGP+mart1234566777+500'
** When the content of the container is known then the number of pieces must be indicated in the simple data-element 7224,
Otherwise, this simple data-element is not used.
4.5.2.6.5. The segment CST within the GROUP7/GROUP8/GROUP14
CST : Customs status of goods
FUNCTION : to specify goods in terms of Customs identities, status and intended use.
USAGE : M
1496 C *
C246 M Customs identity codes
7361 M an..3 Customs code identification
T1T2TF
CTDT2LT2F
T1 formT2 formT2 form in relation with non-fiscal areascommunity goodswith official documentproof of the community statusproof of the community status in relation with non-fiscal areas
1131 M n3 code list qualifier 120 status of the goods
3055 M n3 code responsible agency, coded
147 Belgian Customs
SYNTAX : CST++T1:120:147'
PART 4
CUSCARTRANSHIPMENTS
CHAPTER 1 : General description
1. INTRODUCTION
1.1. Scope
This message permits the transfer of the data related to a transhipment.
1.2. Time of sending the CUSCAR-TRANSHIPMENT message
As long as the details of the consignment(s) are not received and accepted by the computer system of the Belgian Customs, the related CUSCAR-TRANSHIPMENT message will not be accepted.
1.3. Incorrect CUSCAR-TRANSHIPMENT message
When the computer system of the Belgian Customs detects one or more syntax and/or format errors, the complete CUSCAR-TRANSHIPMENT message will be refused and must be re-transmitted after correction of the error(s).
When the computer system of the Belgian Customs detects one or more errors on the details of the transhipment, the CUSCAR-TRANSHIPMENT will be refused and a suitable error(s) (CUSRES) will be given. The complete message must be re-transmitted.
2. CONTENTS
2.1. Document number
The document number is composed of:
- the number of the declaration (14 an characters);- the reference number of the message (max. 21 an characters).
2.1.1. Number of the declaration
The declaration number is composed of the registration number and the IMO num-ber.
The registration number :
This number is given by the port authorities and is composed of 6 digits. There are three series:
- 100000 to 799999 : manual numbering- 800000 to 899999 : automatic numbering- 900000 to 999999 : test
The IMO number : The IMO number is composed of 8 characters.
It can be either a definitive or a provisional IMO number.
A provisional IMO number is a temporary number given by the port authorities, where the official IMO number has not yet been distributed. This provisional number will be used until the official IMO number is available.
A definitive IMO number starts with the letter “L”.
A provisional IMO number starts with the letter “N”.
2.1.2. Reference number of the message
The technical sequence number of the message given by the carrier. The sequence number is composed of maximum an...21 characters. The GCA-system accepts this sequence number without any control.
2.2. Carrier code
When the issuer of the CUSCAR-TRANSHIPMENT message is not the issuer of the CUSCAR message related to the consignment(s), the code of the carrier must be indicated.
2.3. Consignment details
2.3.1. Consignment identification
- the consignment number (CNI number)- the b/l number.
2.3.2. Item identification within the consignment
- the item number within the consignment
2.3.3. Write off identification
- the date of the transhipment- the transhipment number, this is : the sequence number of the internal
document
2.3.4. Contents of the write off action
- the number of pieces to write off- the gross weight to write off
3. CANCELLATION OF ACCEPTED CUSCAR-TRANSHIPMENT MESSAGE
Only the cancellation of the complete CUSCAR-TRANSHIPMENT is allowed.
CHAPTER 2 : Programming specifications
1. VERSION
Release : 96BVersion : DDate : 09/96
2. THE DATA SEGMENTS
Only the following segments are used within the CUSCAR-TRANSHIPMENT message.
BGM: beginning of the message
GROUP 1: RFF : reference
GROUP 2: NAD : to identify the carrier
CNT : control total
GROUP 7: CNI : consignment information
GROUP 8: RFF : reference
GROUP 14 : GID: item goods details
GROUP 15: GIS general indicatorDTM date/time/periodDOCdocument/message
detailsPAC packagesMEA measurements
3. BRANCHING DIAGRAM ┌─────────┬─────────┬────────┬─────────┐ │ │ │ │ │ ┌──┴──┐ ┌──┴──┐ ┌──┴──┐ │ │ │ BGM │ │ GR1 │ │ GR2 │ │ │LEVEL 0 ├──┬──┤ ├─────┤ ├─────┤ │ │ │M │ 1│ │ RFF │ │ NAD │ │ │ └──┴──┘ ├──┬──┤ ├──┬──┤ │ │ │C │ 1│ │C │ 1│ ┌──┴──┐ ┌──┴────┐ └──┴──┘ └──┴──┘ │ CNT │ │ GR7 │ ├──┬──┤ ├──┬────┤ │M │ 1│ │M │9999│LEVEL 1 └──┴──┘ ├──┴────┤ │ CNI │ ├──┬────┤ │M │ 1│ └──┼────┘ ┌──┴────┐ │ GR8 │LEVEL 2 ├──┬────┤ │M │ 1│ ├──┴────┤ │ RFF │ ├──┬────┤ │M │ 1│ └──┼────┘ ┌──┴────┐ │ GR14 │ ├──┬────┤ │M │9999│ LEVEL 3 ├──┴────┤ │ GID │ ├──┬────┤ │M │ 1│ └──┼────┘ ┌──┴────┐
GR15 ├───┬───┤ │ M │99 │LEVEL 4 ├───┴───┤ │ GIS │ ├───┬───┤ │ M │ 1 │ └───┼───┘ │ ┌─────────────┬────────────┬───────┴───────┐ │ │ │ │ │ │ │ │ ┌───┴───┐ ┌───┴───┐ ┌───┴───┐ ┌───┴───┐ │ DOC │ │ DTM │ │ PAC │ │ MEA │LEVEL 5 ├───┬───┤ ├───┬───┤ ├───┬───┤ ├───┬───┤ │ M │ 1 │ │ M │ 1 │ │ M │ 1 │ │ M │ 1 │ └───┴───┘ └───┴───┘ └───┴───┘ └───┴───┘
4. SEGMENTS and GROUPS of SEGMENTS
4.1. The segment BGM
BGM : beginning of message
FUNCTION : to indicate the type and function of a message and to transmit the identifying number
USAGE : M
C002 M document/message name
1001 M n3 document/message name, coded
933 declaration (arrival)
C106 M document/message identification
1004 M an..35 document/message number
1225 M n2 message function, coded 4043
request for deletionadditional transmission (**)
SYNTAX :BGM+933+100000L9999999001+40'
** 40 : request for deletion of an accepted transhipment43 : addition of a transhipment
4.2. The Group 1
4.2.1. The segment RFF within the group 1
RFF : reference
FUNCTION : to identify the previous message
USAGE : C
C506 M reference
1153 M a3 reference qualifier
ACW reference number previous message
1154 M an..35 reference number
SYNTAX : RFF+ACW+100000L9999999001'
4.3. The Group 2
4.3.1. The segment NAD within the group 2
NAD : name and address
CONDITION NAD WITHIN THE MESSAGE CUSCAR-TRANSHIPMENT:
The issuer of the transhipment is not the responsible carrier of the consignments related to the transhipment.
FUNCTION : to specify the name/address and their related function
USAGE : C
3035 M a2 party qualifier CG carrier
C082 M party identification details
3039 M an..6 party id identification see **
1131 M n3 code list qualifier 172 carrier code
3055 M a3 code list responsible agency, coded
ZZZ mutually defined
SYNTAX : NAD+CG+aseco:172:ZZZ’
** The unique reference code for the carrier (firm-code) used within the port community of Antwerp.
4.4. The segment CNT
CNT : control total
FUNCTION : to provide message control total (CNI)
USAGE : M
C270 M control
6069 M n2 control code 10 number of CNI’s
6066 M n...4 control value
SYNTAX : CNT+10:20'
4.5. The GROUP 7
FUNCTION : a group of segments to provide details of theconsignment(s)
USAGE : M
CONTENT GROUP 7:
- the segment CNI : M : consignment information - the GROUP 8 : M : a group of segments
specifying the details ofeach consignment.
4.5.1. The segment CNI within the GROUP 7
CNI : consignment information
FUNCTION : to identify one consignment
USAGE : M
1490 M n..4 consolidation item number = article number
unique within the manifest per carrier
SYNTAX : CNI+1’
4.5.2. The GROUP 8 within the GROUP 7:
FUNCTION : a group of segments to specify the heading of a consignment
USAGE : M
CONTENT OF THE GROUP 8 :
- the segment RFF : M : reference- the GROUP 14 : M : a group of segments to
specify the detail of aconsignment
4.5.2.1. The segment RFF within the GROUP 7/GROUP 8
RFF : reference
FUNCTION : to identify the b/l
USAGE : M
C506 M reference
1153 M a2 reference qualifier MBBM
master b/lb/l
1154 M an..14 reference number number b/l
SYNTAX : RFF+BM:b/l’or RFF+MB:b/l’
4.5.2.2. The GROUP 14 within the GROUP 7/GROUP 8
FUNCTION : a group of segments to identify the details of a goods item
USAGE : M
CONTENT OF GROUP 14:
- the segment GID : M : goods item details- the GROUP 15 : M : details of transhipment
The segment GID within the GROUP7/GROUP8/GROUP14
GID : goods item details
FUNCTION : to indicate totals of a goods item.
USAGE : M
1496 M n..4 goods item number
sequence number of the goods within the b/l
SYNTAX : GID+1'
4.5.2.3. The GROUP 15 within the GROUP 7/GROUP 8/GROUP 14
FUNCTION : a group of segments to identify the details of the transhipment
USAGE : M
CONTENT OF GROUP 15:
- the segment GIS : M : general indicator- the segment DTM : M : date/time/period- the segment DOC : M : document/message details- the segment PAC : M : packages- the segment MEA : M : measurements
4.5.2.3.1 The segment GIS within the GROUP 7 /GROUP 8/GROUP 14/GROUP 15
GIS : general indicator
FUNCTION : to transmit a processing indicator
USAGE : M
C529 M processing indicator
7365 M n2 processing indicator, coded 28 transhipment
SYNTAX : GIS+28'
4.5.2.3.2. The segment DTM within the GROUP 7/GROUP8/GROUP 14/GROUP 15
DTM : date/time/period
FUNCTION : to specify date, and/or time, or period
USAGE : M
C507 M date/time/period
2005 M date/time/period qualifier 190 date transhipment
2380 M date/time/period yymmdd **
SYNTAX : DTM+190:970101'
** The date must always be presented in this format.
4.5.2.3.3. The segment DOC within the GROUP 7/GROUP 8/GROUP 14/GROUP 15
DOC : document/message details
FUNCTION : to specify documents, electronicallytransferred
USAGE : M
C002 M document/message name
1001 M n3 document/message name, coded
701821822931
internal transport documentmodel T1model T2Customs release document
C503 M document/message/details
1004 M an..35 document/message number
document number (see **)
SYNTAX : DOC+701:002101'
** The document number is equal to:
- the number of the internal document (code 701)composed of:
- a unique identification code of the carrier (firm-code)
- an uninterrupted sequence number starting each year from 1.
4.5.2.3.4. The segment PAC within the GROUP 7/GROUP8/GROUP 14/GROUP 15
PAC : packages
FUNCTION : to describe the number and type ofpackages/physical units
USAGE : M
7224 M n..8 number of packages
C531 C *
C202 M package type
7065 M a2 type of packages identification
UN/ ECE recommendation nr. 21
SYNTAX : PAC+1++CN’
4.5.2.3.5. The segment MEA within the GROUP 7/GROUP8/GROUP 14/GROUP 15
MEA : measurements
FUNCTION : to specify physical measurements, including weights and counts
USAGE : M
6311 M a2 measurement application qualifier
WT weight
C502 M measurement details
6313 M a1 measurement dimension, coded
G see **
C174 M value/range
6411 M a3 measurement unit qualifier KGM weight in kg (UN/ ECE re-commendation nr. 20)
6314 M n..9 measurement value gross weight without deci-mals
SYNTAX : MEA+WT+G+KGM:12345'
** The gross weight is the total weight without decimals ofthe goods in the container, including the weight of thepackages, but without the weight of the container itself.
PART 5
CUSRES
CUSTOMS RESPONSE MESSAGE
CHAPTER 1 : General description
1. INTRODUCTION
1.1. Scope
The CUSRES message permits the Customs to respond to each received CUSREP and/or CUSCAR message from the responsible carrier.
EXCEPTION:
If syntax errors within the service segment UNB, a CUSRES message for the whole interchange will be generated.
If syntax errors on message level then one CUSRES message for each received message.
1.2. Time of transmission of the CUSRES message
The CUSRES message will be sent to the carrier immediately after the processing of each received CUSREP and/or CUSCAR message.
1.3. Errors on application level
1.3.1. Within the CUSREP message
GENERAL RULE
The CUSREP message will be rejected when the GCA-system has found one or more errors on the application level. In this case a CUSRES message with a suitable error code will be transmitted to the carrier. The complete CUSREP message has to be re-transmitted after correction of the error(s).
THE PROCESSING WITHIN THE GCA-SYSTEM
The initial transmission of CUSREP data will not be stored in the GCA- system when errors are found. The CUSREP message must be re-transmitted as an initial transmission after correction of the error(s).The data of an original CUSREP message already stored in the GCA-system will not be modified when error(s) are found in:
- the cancellation of a CUSREP-message- the modification of some data of a CUSREP message- the replacement of the itinerary.
1.3.2. Within the CUSCAR message
IN THE SEGMENT BGM4:
The processing of the CUSCAR message will be stopped when one or more errors on application level are found in the segment BGM of the CUSCAR message. After correction of the error(s) in the segment BGM, the complete CUSCAR message has to be re-transmitted with the original function qualifier in the simple data-element 1225 of the segment BGM.
IN THE GENERAL DATA OF THE CONTAINERS (GROUP 5)5 :
The CUSCAR message will be accepted6 when errors are found in the general data related to the containers (GROUP5) and a suitable error message (CUSRES) will be transmitted to the carrier. The general data related to the rejected container(s) (GROUP5) has to be re-transmitted. Two options are possible:
a. the complete general data of the containers can be re-transmitted (i.e. re-transmit all of GROUP5)
b. only the general data of the rejected container(s) (GROUP 5) can be re-transmitted after correction. These re-transmissions will be considered as an initial transmission.
IN THE CNT SEGMENT :
The processing of the CUSCAR message will be stopped immediately7 when the control qualifier in the component data-element 6069 of the segment CNT is not equal to 10.
The complete details of the goods related to the consignments must be re-transmitted with the original function qualifier in the simple data-element 1225 of the segment BGM, after correction of the control qualifier in the component data-element 6069 of the segment CNT.
When the total amount of the consignments in the component data-element 6066 of the segment CNT does not correspond with the addition of the consignments (GROUP 7) of the CUSCAR message then:
- all the correct consignment data will be stored in the GCA-system- a suitable error code8 will be given.
4 These errors will be found in the GROUP4 of the CUSRES message
5 See 4
6 Only the data related to the accepted container numbers will be stored
7 Only the accepted data related to the container numbers will be stored
8 These errors will be found in the GROUP 6 of the CUSRES message
It is recommended that the carrier examines the stored data of the manifest 126 in the GCA-system before he sends a new additional message.
IN THE DETAILS OF THE CONSIGNMENT(S) (GROUP 7)9 :
When one or more application errors are found on the level of a consignment (GROUP 7), the CUSCAR message will be accepted10 and a suitable error code will be given. All the details of the incorrect consignment(s) and the involved parties must be re-transmitted after correction.
EXTENSION
When it is an initial transmission and errors are only found in the segment(s) NAD then the other details related to the consignment(s) will be accepted, with the exception of the data in the segment(s) NAD.
IN THE DETAILS OF A TRANSHIPMENT (GROUP 7/GROUP 8/GROUP 14/GROUP 15:
The processing of the CUSCAR-TRANSHIPMENT message will be stopped when one or more errors on application level are found within the message.After correction of the error the complete CUSCAR-TRANSHIPMENT message has to be re-transmitted to the GCA-system.
THE PROCESSING WITHIN THE GCA-SYSTEM:
When errors are found in an initial transmission on the level of the segment BGM , the GCA-system will not store any data from this message. After correction, the complete CUSCAR message must be re-transmitted as an original message.
The data related to the consignment(s) already stored in the GCA-system remains unchanged when errors are found in the following actions:
- the cancellation of the GROUP 5 (general data related to a container)- the cancellation of the GROUP 7 (consignment)- the replacement of the already stored details of a consignment (GROUP 7)- the addition of the involved parties to a consignment (GROUP 7).
With regard to the replacement of all GROUP(S) 5 data and if errors are found in one or more GROUP(s) 5, it should be noted that the incorrect GROUP(s) 5 will not be stored in the GCA-system. In this case the correct GROUP(s) 5 will be stored in the GCA-system after cancellation of all the existing stored general container data. When all the replacement GROUP 5 data is incorrect then the existing stored data related to the container(s) remains in the GCA-system.
9 See 8
10 Only the accepted consignments will be stored
2. CONTENTS
2.1. Unique reference number of the message
Each CUSRES created by the GCA-system has a unique reference number of 8 digits. This reference number is unique within a period of twenty-four hours.
2.2. Document number
The document number given by the carrier in the simple data-element 1004 of the segment BGM in the CUSREP/CUSCAR message. This number contains :
- the number of the declaration (an..14 characters);- the reference number assigned to the message by the issuer (max. an..21
characters).
2.2.1. Number of the declaration
The number of the declaration is a unique number given by the carrier and is composed of:
The registration number
This number is given by the port authorities and is composed of 6 digits. There are three series:
- 100000 to 799999 : manual numbering- 800000 to 899999 : automatic numbering- 900000 to 999999 : test- X0000000 : IMO number
The IMO number is composed of an 8 characters.
It can be either a definitive or a provisional IMO number.
A definitive IMO number starts with the letter “L”.
A provisional IMO number starts with the letter “N”.
2.2.2. Reference number of the message
The technical sequence number of the message given by the carrier. The sequence number is composed of maximum an...21 characters.
2.3. Processing indicator
An indication related to the acceptance of the received message.
2.4. Error data
2.4.1. Error location
The location of any errors found (if possible to the lowest level).
2.4.2. Error code
The meaning of the error code is only available in the Dutch language.
CHAPTER 2 : Programming specifications
1. VERSION
Release : 96B Version : DDate : 09.96
2. THE DATA SEGMENTS
Only the following segments are used in the CUSRES message:
BGM: beginning of the message
GROUP 3 : RFF : reference
GROUP 4 : ERP : error point detailsERC : application error informationFTX : free text (description of the error)
GROUP 6 : DOC: identification of the consignment (b/l) RFF : identification of the sequence number of the
consignment (CNI)
GROUP 12: ERP : error point detailsERC : application error informationFTX : free text (description of the error).
3. BRANCHING DIAGRAM
┌─────────┬────────────┬───────────┐ │ │ │ │ ┌──┴──┐ │ │ │ │ BGM │ │ │ │LEVEL 0 ├──┬──┤ │ │ │ │M │ 1│ │ │ │ └──┴──┘ │ │ │ ┌──────┐ ┌──┴──┐ ┌──┴────┐ │ GR3 │ │ GR4 │ │ GR6 │ ├──┬───┤ ├──┬──┤ ├──┬────┤ │M │ 1│ │C │99│ │C │9999│LEVEL 1 ├──┴───┤ ├──┴──┤ ├──┴────┤ │ RFF │ │ ERP │ │ DOC │ ├──┬───┤ ├──┬──┤ ├──┬────┤ │M │ 1│ │M │ 1│ │M │ 1│ └──┴───┘ └──┼──┘ └──┼────┘ ┌──────────┬────────────┘ │ │ │ ┌───────────┤ ┌──┴──┐ ┌──┴──┐ ┌───┴──┐ ┌──┴────┐ │ ERC │ │ FTX │ │ RFF │ │ GR12 │LEVEL 2 ├──┬──┤ ├──┬──┤ ├──┬───┤ ├──┬────┤ │M │ 1│ │C │ 1│ │M │ 1│ │M │9999│ └──┴──┘ └──┴──┘ └──┴───┘ ├──┴────┤ │ ERP │ ├──┬────┤ │M │ 1│ └──┼────┘ ┌─────────────┤ │ │ ┌──┴──┐ ┌──┴────┐ │ ERC │ │ FTX │ ├──┬──┤ ├──┬────┤ │M │ 1│ │C │ 1│ LEVEL 3 └──┴──┘ └──┴────┘
4. SEGMENTS and GROUPS of SEGMENTS
4.1. The segment BGM
BGM : beginning of message
FUNCTION : to indicate the type and function of a message and to tran-smit the identifying number
USAGE : M
C002 C *
C106 M document/message identification
1004 M n8 document/message number
see **
1225 M n2 message function, coded 12444548
see ***
SYNTAX :BGM+933+10000001+44'
** unique reference number given by the GCA-system
***12 syntax-error
44 message accepted and processed
45 message accepted, some data is not processed
48 message accepted, but content not processed
4.2. The GROUP 3
The segment RFF within the GROUP 3
RFF : reference
FUNCTION : to identify the message on which the CUSRES is an answer.
USAGE : M
C506 M reference
1153 M a2 reference qualifier
MRZZ
number received messagenumber of the received interchange control reference
1154 M an..35 reference number
see **
SYNTAX : RFF+MR:123456L1234567001' RFF+ZZ:A143'
** The document number given by the carrier in the segment BGM of the CUSREP/ CUSCAR message.
4.3. The GROUP 4
CONDITIONS GROUP 4:
Only the following errors are handled in GROUP 4:
1. all errors within the CUSREP message
2. in the CUSCAR message the errors related to:
- the segment BGM- the GROUP 5 (containers)- the segment CNT (control information on consignment
level).
FUNCTION : a group of segments to identify the errors onlevel 1
USAGE : C (see above)
CONTENT GROUP 4 :
- the segment ERP : M : error point details- the segment ERC : M : application error
information- the segment FTX : C : description of the error
4.3.1. The segment ERP within the GROUP 4
ERP : error point details
FUNCTION : to identify the location and type of application error within a message
USAGE : M
C701 M error point details
1049 M n1 message section, coded 1 hea-ding
C853 M error details segment
9166 M a3 tag of the segment see **
1050 M n...4 sequence number within the repetition of the segment within the received message
SYNTAX : ERP+1+BGM:1'
** Tags of the segments within:
A. CUSREP: BGMLOCTDTDTM
B. CUSCAR: BGMGROEP 5 : EQD
TSRMEA
CNT
C. CUSCAR-TRANSHIPMENT : BGMCNT
REMARKWhen errors are found in the general data related to either a previous validated and received SADBEL-document or a previous received CUSCAR-TRANSHIPMENT message (in case of cancellation) then the component data element 9166 is filled with “BGM” and the component data element 1050 is filled with “000" (see remark in point 2.3.3.).
4.3.2 The segment ERC within the GROUP 4
ERP : application error information
FUNCTION : to identify the type of application error within a message
USAGE : M
C901 M application error detail
9321 M an3 application error, coded not translated
1131 M n3 code list qualifier 109 Customs indicator
3055 M n3 code list responsible agency, coded
147 Belgian Customs
SYNTAX : ERC+001:109:147'
4.3.3. The segment FTX within the GROUP 4
FTX : free text
USAGE OF THE SEGMENT FTX WITHIN THE GROUP 4:
The segment FTX is only used to identify the error location in the LOC-segment within the CUSREP message and the EQD-segment within the CUSCAR message.
FUNCTION : to identify the error location
USAGE : M
4451 M a3 text subject qualifier, coded
AAO description of the error
4453 C *
C107 C *
C108 M text literal
4440 M an..17 error location see **
SYNTAX : FTX+AAO+++klmn12345678' FTX+AAO+++9/bjc00’
** CUSREP : place code/unlocode ( =3227/3225)CUSCAR : number of the container (=8260)
REMARK
When errors are found in the general data related to either a previous received and validated SADBEL-document or a previous received CUSCAR-TRANSHIPMENT message (in case of cancellation) then the component data element 4440 is filled with “the number of the transhipment document” (see GROUP 7/GROUP 8/ GROUP 14/ GROUP 15/DOC:1004).
4.4. The GROUP 6
CONDITION GROUP 6:
The GROUP 6 is only used when errors are found within the GROUP 7 of the CUSCAR message.
FUNCTION : a group of segments to identify the errors on consignment level
USAGE : C (see above)
CONTENT GROUP 6 :
- the segment DOC : M : identification of theconsignment (b/l)
- the segment RFF : M : identification of thesequence number of the consignment (b/l)
- the GROUP 12 : M : description of the error(s)
4.4.1. The segment DOC within the GROUP 6
DOC : document/message details
FUNCTION : to identify documents electronically transferred (identification of a consignment (b/l) in which error(s) is/are found)
USAGE : M
C002 M document/message name
1001 M n3 document/message name, coded
704 master b/l
C503 M document/message details
1004 M an..35 document/message number
b/l number
SYNTAX : DOC+704+an123456789'
4.4.2. The segment RFF within the GROUP 6
RFF : reference
FUNCTION : to identify the sequence number (CNI-number) of the consignment within the CUSCAR message
USAGE : M
C506 M reference
1153 M a3 reference qua-lifier
UCN reference
1154 M n..4 reference num-ber
CNI number (consignment num-ber)
SYNTAX : RFF+UCN:12'
4.4.3. The GROUP 12 within the GROUP 6
FUNCTION : a group of segments to identify the errors on consignment level
USAGE : C (see above)
CONTENT GROUP 12 :
- the segment ERP : M : error point details- the segment ERC : M : application error
information- the segment FTX : M : description of the error
4.4.3.1. The segment ERP within the GROUP 6/GROUP 12
ERP : error point details
FUNCTION : to identify the location and type of application error within a message
USAGE : M
C701 M error point details
1049 M n2 message section, coded 1214
bill of ladingitem bill of lading
1052 C *
1054 C n..4 message sub-item number
number of item level within a consignment see **
C853 M error detail segment see **
9166 M a3 tag of the segment see ***
1050 M n..4 sequence number of the segment within the message
SYNTAX : ERP+12+CNI:2' ERP+14::2+MEA:2'
** The composite data-element C702 is mandatory when errors are found on item level of the b/L
*** Tags of the segments within CUSCARGROUP7:CNIGROUP8:RFF,CNT,LOCGROUP11:NAD GROUP13:QTYGROUP14:GID,FTX,MEA,SGP,CSTGROUP15:GIS,DOC,DTM,PAC,MEA
4.4.3.2. The segment ERC within the GROUP 6/GROUP 12
ERP : application error information
FUNCTION : to identify the type of application error within a message
USAGE : M
C901 M application error detail
9321 M an3 application error, coded not translated
1131 M n3 code list qualifier 109 Customs indi-cator
3055 M n3 code list responsible agency, coded
147 Belgian Customs
SYNTAX : ERC+001:109:147'
4.4.3.3. The segment FTX within the GROUP 6/GROUP 12
FTX : free text
USAGE OF THE SEGMENT FTX WITHIN THE GROUP 12 :
The segment FTX is only used to identify the error location in the segments LOC - NAD - SGP within the CUSCAR message.
FUNCTION : to identify the error location
USAGE : C (see above)
4451 M a3 text issue co-ded
AAO description of the error
4453 C *
C107 C *
C108 M free text
4440 M an..17 error location see **
SYNTAX : FTX+AAO+++KLMN12345678' FTX+AAO+++9/BJCOO’
** CUSCAR : place code/unlocode/sequence number LOC withinGROUP 7/GROUP 8(=3227/3225)
: party coded (= 3035/NAD): number of container/ sequence number SGP within
the GROUP 7/GROUP 8(= 8260/SGP)
PART 7
Summary of the used segments
BGM BEGINNING OF MESSAGE
Function : To indicate the type and function of a message and to transmit the identifying number.
010 C002 DOCUMENT/MESSAGE NAME C1001 Document/message name, coded C an..31131 Code list qualifier C an..33055 Code list responsible agency, coded C an..31000 Document/message name C an..35
020 C106 DOCUMENT/MESSAGE IDENTIFICATION1004 Document/message number C an..351056 Version C an..91060 Reversion number C an..3
030 1225 MESSAGE FUNCTION, CODED C an..3
4343 RESPONSE TYPE, CODED C an..3
CNI CONSIGNMENT INFORMATION
Function: To indicate consignments loaded in a consolidation using the reference number of the transport document of the relevant consignment.
010 1490 CONSOLIDATION ITEM NUMBER C n..4 020 C503 DOCUMENT/MESSAGE DETAILS C
1004 Document/message number C an..351373 Document/message status, coded C an..31366 Document/message source C an..353453 Language, coded C an..3
030 1312 CONSIGNMENT LOAD SEQUENCE NUMBER C n..4
CNT CONTROL TOTAL
Function: To provide message control total. 010 C270 CONTROL M
6069 Control qualifier M an..36066 Control value M n..186411 Measure unit qualifier C an..3
CST CUSTOMS STATUS OF GOODS
Function: To specify goods in terms of customs identities, status and intended use.
010 1496 GOODS ITEM NUMBER C n..5 020 C246 CUSTOMS IDENTITY CODES C
7361 Customs code identification M an..181131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3
030 C246 CUSTOMS IDENTITY CODES C
7361 Customs code identification M an..181131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3
040 C246 CUSTOMS IDENTITY CODES
7361 Customs code identification M an..181131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3
050 C246 CUSTOMS IDENTITY CODES C
7361 Customs code identification M an..181131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3
060 C246 CUSTOMS IDENTITY CODES C
7361 Customs code identification M an..181131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3
DOC DOCUMENT/MESSAGE DETAILS
Function: to identify documents, either printed, electronically transferred or referenced as specified in message description, including, where relevant, the identification of the type of transaction that will result from this message
010 C002 DOCUMENT/MESSAGE NAME M1001 Document/message name, coded C an...31131 Code list qualifier C an...33055 Code list responsible agency, coded C an...31000 Document/message name C an...35
020 C503 DOCUMENT/MESSAGE DETAILS C
1004 Document/message number C an...351373 Document/message status, coded C an...31366 Document/message source C an...353453 Language, coded C an...3
030 3153 COMMUNICATION CHANNEL IDENTIFIER,CODED C an...3
040 1220 NUMBER OF COPIES OF DOCUMENT REQUIRED C n...2
050 1218 NUMBER OF ORIGINALS OF DOCUMENTREQUIRED C n...2
DTM DATE/TIME/PERIOD
Function: To specify date, time, period.
010 C507 DATE/TIME/PERIOD M
2005 Date/time/period qualifier M an..32380 Date/time/period C an..352379 Date/time/period format qualifier C an..3
EQD EQUIPMENT DETAILS
Function: To identify a unit of equipment.
010 8053 EQUIPMENT QUALIFIER M an..3
020 C237 EQUIPMENT IDENTIFICATION C
8260 Equipment identification number C an..171131 Code list qualifier C an..33055 Code list responsible agency, coded C an..33207 Country,coded C an..3
030 C224 EQUIPMENT SIZE AND TYPE C
8155 Equipment size and type identification C an..101131 Code list qualifier C an..33055 Code list responsible agency, coded C an..38154 Equipment size and type C an..35
040 8077 EQUIPMENT SUPPLIER, CODED C an..3
050 8249 EQUIPMENT STATUS, CODED C an..3
060 8169 FULL/EMPTY INDICATOR, CODED C an..3
ERC APPLICATION ERROR INFORMATION
Function: to identify the type of application error within a message
010 C901 APPLICATION ERROR DETAIL M
9321 Application error identification M an...81131 Code list qualifier C an...33055 Code list responsible agency, coded C an...3
ERP ERROR POINT DETAILS
Function: a segment to identify the location of an application error within a message
010 C701 ERROR POINT DETAILS C
1049 Message section, coded C an...31052 Message item number C an...351054 Message sub-item number C n...6
020 C853 ERROR SEGMENT POINT DETAILS C
9166 Segment TAG C an...31050 Sequence number C an...101159 Sequence number source, coded C an...3
FTX FREE TEXT
Function: To provide free form or coded text information.
010 4451 TEXT SUBJECT QUALIFIER M an..3
020 4453 TEXT FUNCTION, CODED C an..3
030 C107 TEXT REFERENCE C4441 Free text, coded M an..171131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3
040 C108 TEXT LITERAL C
4440 Free text M an..704440 Free text C an..704440 Free text C an..704440 Free text C an..704440 Free text C an..70
050 3453 LANGUAGE, CODED C an..3
GID GOODS ITEM DETAILS
Function: To indicate totals of a goods item.
010 1496 GOODS ITEM NUMBER C n..5
020 C213 NUMBER AND TYPE OF PACKAGES C
7224 Number of packages C n..87065 Type of packages identification C an..171131 Code list qualifier C an..33055 Code list responsible agency, coded C an..37064 Type of packages C an..35
030 C213 NUMBER AND TYPE OF PACKAGES C
7224 Number of packages C n..87065 Type of packages identification C an..171131 Code list qualifier C an..33055 Code list responsible agency, coded C an..37064 Type of packages C an..35
040 C213 NUMBER AND TYPE OF PACKAGES C
7224 Number of packages C n..87065 Type of packages identification C an..171131 Code list qualifier C an..33055 Code list responsible agency, coded C an..37064 Type of packages C an..35
GIS GENERAL INDICATOR
Function: to transmit a processing indicator
010 C529 PROCESSING INDICATOR M
7365 Processing indicator, coded M an...31131 Code list Qualifier C an...33055 Code list responsible agency, code C an...37187 Process type identification C an...17
LOC PLACE/LOCATION IDENTIFICATION
Function: To identify a country/place/location/related location one/related location two. 010 3227 PLACE/LOCATION QUALIFIER M an..3 020 C517 LOCATION IDENTIFICATION C
3225 Place/location identification C an..251131 Code list qualifier C an..33055 Code list responsible agency, coded C an..33224 Place/location C an..70
030 C519 RELATED LOCATION ONE IDENTIFICATION C
3223 Related place/location one identification C an..25
1131 Code list qualifier C an..33055 Code list responsible agency, coded C an..33222 Related place/location one C an..70
040 C553 RELATED LOCATION TWO IDENTIFICATION C
3233 Related place/location two identification C an..25
1131 Code list qualifier C an..33055 Code list responsible agency, coded C an..33232 Related place/location two C an..70
050 5479 RELATION, CODED C an..3
MEA MEASUREMENTS
Function: To specify physical measurements, including dimension tolerances, weights
and counts.
010 6311 MEASUREMENT APPLICATION QUALIFIER M an..3
020 C502 MEASUREMENT DETAILS C
6313 Measurement dimension, coded C an..36321 Measurement significance, coded C an..36155 Measurement attribute, coded C an..36154 Measurement attribute C an..70
030 C174 VALUE/RANGE C
6411 Measure unit qualifier M an..36314 Measurement value C an..186162 Range minimum C n..186152 Range maximum C n..18
6432Significant digits C n..2 040 7383 SURFACE/LAYER INDICATOR, CODED C an..3
NAD NAME AND ADDRESS
Function: To specify the name/address and their related function, either by C082 only and/or unstructured by C058 or structured by C080 up to 3207.
010 3035 PARTY QUALIFIER M an..3
020 C082 PARTY IDENTIFICATION DETAILS C
3039 Party id identification M an.351131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3
040 C058 NAME AND ADDRESS C
3124 Name and address line M an..353124 Name and address line C an..353124 Name and address line C an..353124 Name and address line C an..353124 Name and address line C an..35
050 C080 PARTY NAME C3036 Party name M an..353036 Party name C an..353036 Party name C an..353036 Party name C an..353036 Party name C an..353045 Party name format, coded C an..3
060 C059 STREET C
3042 Street and number/P.O. Box M an..353042 Street and number/P.O. Box C an..353042 Street and number/P.O. Box C an..353042 Street and number/P.O. Box C an..35
060 3164 CITY NAME C an..35
070 3229 COUNTRY SUB-ENTITY IDENTIFICATION C an..9
080 3251 POSTCODE IDENTIFICATION C an..9090 3207 COUNTRY, CODED C an..3
PAC Package
Function: to describe the number and type of packages/physical units
010 7224 NUMBER OF PACKAGES C n..8
020 C531 PACKAGE DETAILS C
7075 Packaging level, coded C an..37233 Packaging related information, coded C an..37073 Packaging terms and conditions, coded C an..3
030 C202 PACKAGE TYPE C
7065 Type of packages identification C an..17 1131 Code list qualifier C an..33055 Code list responsible agency, coded C an..37064 Type of packages C an..35
040 C402 PACKAGE TYPE IDENTIFICATION C
7077 Item description type, coded M an..3 7064 Type of packages M an..357143 Item number type, coded C an..37064 Type of packages C an..357143 Item number type, coded C an..3
050 C532 RETURNABLE PACKAGE DETAILS C
8395 Returnable package freight payment resp., coded C an..3
8393 Returnable package load contents, coded C an..3
QTY QUANTITY
Function: To specify a pertinent quantity.
010 C186 QUANTITY DETAILS M
6063 Quantity qualifier M an..3 6060 Quantity M n..156411 Measure unit qualifier C an..3
RFF REFERENCE
Function: To specify a reference. 010 C506 REFERENCE M
1153 Reference qualifier M an..31154 Reference number C an..351156 Line number C an..64000 Reference version number C an..35
SEL SEAL NUMBER
Function: To specify a seal number related to equipment.
010 9308 SEAL NUMBER M an..10
020 C215 SEAL ISSUER C 9303 Sealing party, coded C an..3 1131 Code list qualifier C an..3 3055 Code list responsible agency, coded C an..3 9302 Sealing party C an..35
030 4517 SEAL CONDITION, CODED C an..3
SGP SPLIT GOODS PLACEMENT
Function: To specify the placement of goods in relation to equipment. 010 C237 EQUIPMENT IDENTIFICATION M
8260 Equipment identification number C an..171131 Code list qualifier C an..33055 Code list responsible agency, coded C an..33207 Country,coded C an..3
020 7224 NUMBER OF PACKAGES C n..8
TDT DETAILS OF TRANSPORT
Function: To specify the transport details such as mode of transport, means of transport, its conveyance reference number and the identification of the means of transport. The segment may be pointed to by the TPL segment.
010 8051 TRANSPORT STAGE QUALIFIER M an..3
020 8028 CONVEYANCE REFERENCE NUMBER C an..17
030 C220 MODE OF TRANSPORT C
8067 Mode of transport, coded C an..38066 Mode of transport C an..17
040 C228 TRANSPORT MEANS C
8179 Type of means of transport identification C an..8
8178 Type of means of transport C an..17
050 C040 CARRIER C
3127 Carrier identification C an..171131 Code list qualifier C an..33055 Code list responsible agency, coded C an..33128 Carrier name C an..35
060 8101 TRANSIT DIRECTION, CODED C an..3
070 C401 EXCESS TRANSPORTATION INFORMATION C
8457 Excess transportation reason, coded M an..38459 Excess transportation responsibility,
coded M an..37130 Customer authorization number C an..17
080 C222 TRANSPORT IDENTIFICATION C
8213 Id of means of transport identification C an..91131 Code list qualifier C an..33055 Code list responsible agency, coded C an..38212 Identification of the means
of transport C an..178453 Nationality of means of transport,
coded C an..3
090 8281 TRANSPORT OWNERSHIP, CODED C an..3
TSR TRANSPORT SERVICE REQUIREMENTS
Function: To specify the contract and carriage conditions and service and priority requirements for the transport.
010 C536 CONTRACT AND CARRIAGE CONDITION C
4065 Contract and carriage condition,coded M an..31131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3
020 C233 SERVICE C
7273 Service requirement, coded M an..31131 Code list qualifier C an..33055 Code list responsible agency, coded C an..37273 Service requirement, coded C an..31131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3
030 C537 TRANSPORT PRIORITY C
4219 Transport priority, coded M an..31131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3
040 C703 NATURE OF CARGO C
7085 Nature of cargo, coded M an..31131 Code list qualifier C an..33055 Code list responsible agency, coded C an..3