Message Implementation Guide CUSREP-D94A



|[pic] | |

| |Federal |

| |Public Service |

| |FINANCE |

| | |

| |

|TAXES AND TAX COLLECTION |

|Administration of Customs and Excise |

| |

| |

| |

Message implementation Guide CUSREP-D94A

Data exchange between the port authority and the PLCE

Paperless Customs and Excise

Version 1.2 3

30/07/201521/01/2016

Use of the model:

• Above all, the document shall be saved under a name pursuant to the following naming guidelines. To this end, the following menu option shall be used: “File, Save as”

• Adjust the “Properties” of the document. To this end, use the following menu option: “File, Properties”

o Tab “Summary”

▪ Title

▪ Subject

▪ Author

o Tab “Adjusted”

▪ The complete section “Properties”

• This part of the document is not included in the page numeration. You can start to work on the next page.

• Keep this page in your document until it is sent to the steering group. It may serve as a useful reminder for all persons working with you on this document.

Naming guidelines:

Projectcode_Phase_DeliverableCode_Title_(AuthorInitials)_Version_(LanguageCode)

|Naming |Obligatory /Optional |Specifications |

|Projectcode |Obligatory |Decision taken by the steering group at kick-off |

|Phase |Obligatory |According to the planning which has been approved by the steering group |

|DeliverableCode |Obligatory |According to the planning which has been approved by the steering group. |

| | |A decimal coding can be applied if more than one working document leads to the |

| | |execution of the final delivery. In this case, the code 00 will be used for the |

| | |final delivery and the working group will agree on the sub codes that will be |

| | |assigned to the working documents when drawing up the planning. |

|Title |Obligatory |Assigned by the author |

| | |Restrict the length to no more than 30 characters. Avoid spaces. A separation of the|

| | |words cannot be indicated by means of an alternation of lowercase and uppercase. |

| | |Do not use underlining, it is used to introduce a new part of the document name. |

|AuthorInitials |Optional | |

|Version |Obligatory |First part: status |

| | |0: subject |

| | |1: approved by the partners |

| | |2: approved for test version |

| | |3: approved for operational version |

| | |Separator: space |

| | | |

| | |Second part: version start at 1 for the draft version and restart at 0 for each |

| | |subsequent status. |

| | | |

| | |Exemples: |

| | |PLD_01_01_ApplicationArchitecture_0 1 |

| | |PLD_01_01.00_ApplicationArchitecture_ET_0 1_EN |

| | |PLD_01_01.01_RelevantProcesDescr_PR_0 1_NL |

|LanguageCode |Optional |NL for Dutch |

| | |FR for French |

| | |EN for English |

| | |DU for German |

Please follow the above-mentioned guidelines and to not forget to:

- adjust the version number

o in the name of your file,

o in the “Properties” of the document Tab “Adjusted”;

- complete the version history of the document at the first page.

Stop at this paragraph in case of removal of this text before the document is sent to the steering group. If not, the section end will be removed and as a result also the page layout.

Document control

1. Version history of the document

|Version |Date |Author |Remark |

|0 1 |20/11/2004 |Roger Beeckman |First draft |

|1 0 |01/04/2005 |Roger Beeckman |Final |

|1.1 |07/04/2014 |Martine De Doncker |Addition of additional elements with regard to the exit confirmation|

| | | |of an ocean vessel and revision of full MIG |

|1.2 |30/07/2015 |Klara Pasgang |Adding rule to p29 to enforce the sending of only one location |

| | | |within the message instead of 99. |

|1.3 |21/01/16 |Klara Pasgang |Adding remark 2 (p32) to 5.5 GROUP 5 (NAD data) concerning |

| | | |modification of the CUSREP message |

Table of contents

1 Introduction 5

2 Format of the message 6

2.1 Version of the message 6

2.2. Initial scope of the message 6

2.2.1 Functional definition 6

2.2.2 Field application 6

2.2.3 Principles 6

2.2.4 References 6

2.2.5 Terms and definitions 6

2.2.6 Message definition 8

3 Use of the message 15

3.1 Introduction 15

3.1.1 Aim 15

3.1.2 Time of sending of the message – import movement (document name in code = 933) 15

3.1.4 Erroneous CUSREP message 15

3.2 Content of the message 15

3.2.1 Number of the document 15

3.2.2 Notification of a passage 16

3.2.3 Notification of mooring 16

3.2.4 Identification of the responsible shipping agent 17

3.2.5 Transport data 17

3.3 Data modification, extension or cancellation 17

3.3.1 Data modification 17

3.3.2 Data extension 17

3.3.3 Data cancellation 18

4 Technical description of the message 19

4.1 Used segments 19

4.2 Structure diagram 19

4.3 Description of the used segments 20

4.3.1 BGM – Beginning of message 20

4.3.2 Group 1/RFF – Reference 20

4.3.3 Group 2/LOC Identification of a place 21

4.3.4 Group 2/DTM Date and Time 22

4.3.5 Group 5/NAD Details with regard to the responsible shipping agent 23

4.3.6 Group 8/TDT details of the transport 24

5 Program specifications 26

5.1 The segment BGM 26

5.2 Group 1 27

5.2.1 Segment RFF 27

5.3 Group 2 28

5.3.1 Group 2 segment LOC 30

5.4 Group2/DTM Date and time 31

5.5 Group 5 32

5.5.1 Group 5/NAD Data with regard to the responsible shipping agent 32

5.6 Group 8 33

5.6.1 Group 8 segment TDT 33

6 Examples 34

6.1 Example of the (first) passage upon arrival 34

6.2 Example of mooring 34

6.2.1 The passage has not been notified 34

6.2.2 The passage has already been notified 34

6.3 Cancellation of all data of a message upon arrival 34

6.4 Cancellation of all data of a message upon departure 34

6.5 Cancellation of a passage upon arrival 34

6.6 Cancellation of a passage upon departure 35

6.7 Cancellation of the last passage upon departure 35

6.8 Cancellation of a mooring place 35

6.9 Cancellation of a mooring place 35

6.10 Modification of a passage place upon arrival 35

6.11 Modification of a passage place upon departure 35

6.12 Modification of a place code upon arrival 35

6.13 Modification of a passage place upon departure 36

6.14 Modification of the date and/or hour of passage upon arrival 36

6.15 Modification of the date and/or hour of passage upon departure 36

6.16 Modification of a shipping agent (at quay) upon arrival 36

6.17 Modification of a shipping agent (at quay) upon departure 36

6.18 Modification of the data of an ocean vessel upon arrival 36

6.19 Modification of the data of an ocean vessel upon departure 36

6.20 Addition of a quay 37

6.21 Addition of a country of destination upon departure 37

7 Enclosures 38

7.1 Enclosure 1: codes passages 38

7.1.1 Passages port of Antwerp 38

7.1.2 Passages port of Ghent 38

7.1.3 Passages port of Zeebrugge 38

7.2 Enclosure 2: codes of the quays 38

7.2.1 Quays in Antwerp 38

7.2.2 Quays in Ghent 38

7.2.3 Quays in Zeebrugge 38

7.3 Enclosure 3: the Iso alpha-II codes 38

Overview of the figures

Figure 1 : Title Fout! Bladwijzer niet gedefinieerd.

Overview of the tables

Table 1 : Title Fout! Bladwijzer niet gedefinieerd.

Introduction

This document is the Message Implementation Guide (MIG) for data exchange with regard to the notification of the places of passage and the final date of arrival and departure of an ocean vessel by the port authorities. The following message is the EDIFACT message CUSREP - version D94A.

In chapter 2 you will find an overview of the full message.

In chapter 3 you will find a brief explanation with regard to the use of the message.

In chapter 4 you will find a description of the segments and data elements which are required - compulsorily or not - by the Administration.

In chapter 5 the specifications with regard to the internal programming are listed.

In chapter 6 a few examples of the messages are given on the basis of the function of the message.

In chapter 7 the codes to be used are listed. If these codes are applied by multiple messages, reference is made to a separate document:

PLDA_05_codes messages_V0 1.doc

In case of international codes and if the code list is too extended, reference is made to the applicable website.

Format of the message

1 Version of the message

Message Type: CUSREP

Version: D

Release: 94A

Contr. Agency: UN

Status: 2

Revision: 1

Date: 94-09-21

2 Initial scope of the message

2.2.1 Functional definition

This Customs Conveyance Report Message (CUSREP) permits the transfer of data from a carrier to a Customs administration for the purpose of meeting Customs reporting requirements in respect of the means of transport on which cargo is carried.

2.2.2 Field application

This message may be applied for both national and international trade. It is based on universal practice and is not dependent on the type of business or industry.

2.2.3 Principles

It is envisaged that the Customs Conveyance Report Message may be initiated by the carrier to report details of the means of transport on which cargo is conveyed to a Customs administration. The message is transmitted upon arrival of the vessel, flight, etc., or where national legislation permits, prior to arrival. The data provides a means of establishing the basis of a cargo inventory report for the conveyance in question. Details of individual consignments carried on the conveyance will be subsequently transmitted to Customs using a CUSCAR message or a series of such messages. It also allows Customs to undertake selectivity processing in order to select high risk conveyances and shipments requiring examination. The message embodies reporting requirements of all modes of transport. Each message covers the data requirements for one conveyance. The message may be used for reporting empty containers as well as numbers of passengers and crew.

2.2.4 References

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - General Introduction, Section 1. The full text of the references can be consulted via trade/untdid/welcome.htm.

2.2.5 Terms and definitions

See UNTDID, Part 4, Chapter 2.6 UN/ECE UNSM - GeneralIntroduction, Section 2.

The terms and definitions can be consulted via trade/untdid/welcome.htm.

2.2.6 Message definition

2.2.6.1 Data segment clarification

0010 UNH, Message header

A service segment starting and uniquely identifying a message. The message type code for the Customs conveyance report message is CUSREP.

Note: Customs conveyance report messages conforming to this document must contain the following data in segment UNH, composite S009:

Data element:

0065 CUSREP

0052 D

0054 94A

0051 UN

0020 BGM, Beginning of message

A segment to identify the report/voyage number, type of message (e.g. amendment) and date/time of message of creation.

0030 DTM, Date/time/period

A segment to indicate date/time of conveyance report to Customs.

0040 QTY, Quantity

A segment to identify the number of passengers, number of crew, number of bills.

0050 FTX, Free text

A segment to provide observations, remarks and reason for change.

0060 MEA, Measurements

A segment to specify the conveyance's gross tonnage, net tonnage, summer dead weight tonnage, containerized/non-containerized tonnage and overall length.

0070 GIS, General indicator

A segment to specify the import/export/transit indicator, prohibited/restricted goods indicator and unregistered spaces indicator.

0080 Segment group 1: RFF-DTM

A group of segments to specify references and dates/times related to the conveyance.

0090 RFF, Reference

A segment to specify reference numbers associated with the conveyance.

0100 DTM, Date/time/period

A segment to specify dates/times associated with the conveyance's reference numbers.

0110 Segment group 2: LOC-DTM

A group of segments to identify voyage itinerary.

0120 LOC, Place/location identification

A segment to specify the conveyance's voyage itinerary - ports of call/places.

0130 DTM, Date/time/period

A segment to specify dates/time associated with the itinerary.

0140 Segment group 3: DOC-RFF-DTM-LOC

A group of segments to specify supporting documentary requirements and associated reference numbers, dates/times and locations.

0150 DOC, Document/message details

A segment to specify supporting documentary requirements, including Certificate of Registry, Safety of Life at Sea Certificate, Maritime Health Declaration, Ship's Stores Declaration (FAL 3), Crew's Effects Declaration (FAL 4), Crew's List Declaration (FAL 5), Passenger List (FAL 6).

0160 RFF, Reference

A segment to specify reference numbers associated with a supporting documentary requirement.

0170 DTM, Date/time/period

A segment to specify dates/times/periods associated with a supporting documentary requirement.

0180 LOC, Place/location identification

A segment to specify locations associated with a supporting documentary requirement.

0190 Segment group 4: TAX-MOA-GIS

A group of segments to indicate duty/tax/fee details and monetary amounts payable related to the conveyance.

0200 TAX, Duty/tax/fee details

A segment to specify relevant duty/tax/fee information.

0210 MOA, Monetary amount

A segment to specify monetary amount.

0220 GIS, General indicator

A segment to transmit a processing indicator.

0230 Segment group 5: NAD-SG6-SG7

A group of segments to identify names, addresses, contacts and references relating to the message.

0240 NAD, Name and address

A segment to specify declarant's name and address, ship's agent name and address, and master's name.

0250 Segment group 6: CTA-COM

A group of segments specifying persons/departments and communication numbers associated with the party identified in NAD, group 5.

0260 CTA, Contact information

A segment to identify the person or department to whom communication should be directed.

0270 COM, Communication contact

A segment to identify communication numbers (i.e. telephone/ fax numbers) of departments or persons to whom communication should be directed.

0280 Segment group 7: RFF-DTM

A group of segments specifying persons/departments and communication numbers associated with the party identified in NAD, group 5.

0290 RFF, Reference

A segment to identify numbers associated with the named party or transaction.

0300 DTM, Date/time/period

A segment to specify dates/times associated with references.

0310 Segment group 8: TDT-TPL-DTM-SG9

A group of segments to indicate details related to each leg of transport.

0320 TDT, Details of transport

A segment to specify details of transport related to each leg, including name/number of vessel/vehicle/flight, nationality of ship, conveyance reference number, type of service identifier and carrier.

0330 TPL, Transport placement

A segment to specify placement of goods or equipment in relation to the transport used.

0340 DTM, Date/time/period

A segment to specify associated dates/times as required related to details of transport.

0350 Segment group 9: LOC-DTM-QTY

A group of segments to specify locations related to each leg of transport, associated dates/times and quantity (tonnage) of cargo loaded/unloaded at each port.

0360 LOC, Place/location identification

A segment to specify port of initial arrival, place/station of last foreign port of call (last departure), place/port of loading, place/port of discharge, quay location/position of ship in port.

0370 DTM, Date/time/period

A segment to specify associated dates/times as required related to locations.

0380 QTY, Quantity

A segment to specify tonnage of cargo loaded/unloaded at each port.

0390 Segment group 10: EQD-EQN

A group of segments to identify equipment details and number of equipment units.

0400 EQD, Equipment details

A segment to identify the size of containers and whether empty/loaded.

0410 EQN, Number of units

A segment to identify number of containers.

0420 Segment group 11: AUT-DTM

A group of segments to specify results and date/time of the application of an authentication procedure.

0430 AUT, Authentication result

A segment to specify results of the application of an authentication procedure.

0440 DTM, Date/time/period

A segment to specify associated dates/times as required related to an authentication procedure.

0450 UNT, Message trailer

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

2.2.6.2 Data segment index (alphabetical sequence)

AUT Authentication result

BGM Beginning of message

COM Communication contact

CTA Contact information

DOC Document/message details

DTM Date/time/period

EQD Equipment details

EQN Number of units

FTX Free text

GIS General indicator

LOC Place/location identification

MEA Measurements

MOA Monetary amount

NAD Name and address

QTY Quantity

RFF Reference

TAX Duty/tax/fee details

TDT Details of transport

TPL Transport placement

UNH Message header

UNT Message trailer

2.2.6.3 Message structure

|Pos |Tag |Name |Availability seg |Availability groups |

|0010 |UNH |Message header |M1 | |

|0020 |BGM |Beginning of message |M1 | |

|0030 |DTM |Date/time period |C9 | |

|0040 |QTY |Quantity |C9 | |

|0050 |FTX |Free text |C9 | |

|0060 |MEA |Measurements |C9 | |

|0070 |GIS |General indicator |C9 | |

|0080 | |Segment group1 | |C99 |

|0090 |RFF |Reference |M1 | |

|0100 |DTM |Date/time period |C1 | |

|0110 | |Segment group 2 | |C99 |

|0120 |LOC |Place/location identification |M1 | |

|0130 |DTM |Date/time period |C1 | |

|0140 | |Segment group 3 | |C9 |

|0150 |DOC |Document/message details |M1 | |

|0160 |RFF |Reference |C1 | |

|0170 |DTM |Date/time period |C1 | |

|0180 |LOC |Place/location identification |C1 | |

|0190 | |Segment group 4 | |C9 |

|0200 |TAX |Duty/tax/fee details |M1 | |

|0210 |MOA |Monetary amount |C1 | |

|0220 |GIS |General indicator |C1 | |

|0230 | |Segment group 5 | |C9 |

|0240 |NAD |Name and address |M1 | |

|0250 | |Segment group 6 | |C9 |

|0260 |CTA |Contact information |M1 | |

|0270 |COM |Communication contact |C5 | |

|0280 | |Segment group 7 | |C9 |

|0290 |RFF |Reference |M1 | |

|0300 |DTM |Date/time period |C1 | |

|0310 | |Segment group 8 | |C99 |

|0320 |TDT |Details of transport |M1 | |

|0330 |TPL |Transport placement |C1 | |

|0340 |DTM |Date/time period |C1 | |

|0350 | |Segment group 9 | |C99 |

|0360 |LOC |Place/location identification |M1 | |

|0370 |DTM |Date/time period |C9 | |

|0380 |QTY |Quantity |C9 | |

|0390 | |Segment group 10 | |C999 |

|0400 |EQD |Equipment details |M1 | |

|0410 |EQN |Number of units |C1 | |

|0420 | |Segment group 11 | |C1 |

|0430 |AUT |Authentication result |M1 | |

|0440 |DTM |Date/time period |C1 | |

|0450 |UNT |Message trailer |M1 | |

Use of the message

1 Introduction

3.1.1 Aim

This message is used for the electronic notification of the first passage of the ocean vessel in the computer system of the port authority, for the electronic registration of the final date and hour of arrival of the ocean vessel at each quay in the port of Antwerp, Zeebrugge or Ghent, regardless of the fact whether the goods are being unloaded, as well as for the electronic deregistration at any quay, the potential notification of the locking operations and the entry of the date and hour of the last passage in order to confirm the final export movement.

3.1.2 Time of sending of the message – import movement (document name in code = 933)

Firstly, the CUSREP message is sent upon the first passage of the ocean vessel. Subsequently, the second CUSREP message is sent upon mooring at each quay in the port of Antwerp, Zeebrugge or Ghent.

As long as no CUSREP message has been sent to the port authority by the central computer of the General Administration of Customs and Excise, no declarations for customs procedures can be accepted.

3.1.3 Time of sending of the message – export movement (document name in code = 833)

Each mooring movement from a quay is notified by means of a CUSREP message and the potential passage to the different locks. Upon mooring, it should also be notified whether or not goods have been loaded there. The place codes 9 (place of loading), 90 (place of loading and unloading) or 60 (no unloading/loading in the port) shall be used to that end.

The last CUSREP message is sent at the moment of the passage of the point which is considered as the passage point for the confirmation of the final export movement. Place code 17 (place border crossing) shall be used to that end.

3.1.4 Erroneous CUSREP message

If one or more errors with regard to the content and/or the format should be established upon receipt of the message, the complete CUSREP message shall be refused and a fitted error message shall be returned through the G.C. system. After the message has been rectified, it shall be returned in its entirety.

2 Content of the message

3.2.1 Number of the document

The number of the document is composed of:

- the number of the declaration (14 an);

- the reference number of the message (max. 21 an).

3.2.1.1 Number of the declaration

This number is composed of the port call number and the IMO number of the ocean vessel:

- positions 1 up to and including 6: port call number. The port call number is assigned by the port authority and consists of 6 numerical characters.

- positions 1 up to and including 14: IMO number. An official IMO number starts with the letter L and a provisional IMO numbers starts with the letter N.

A provisional IMO number is a temporary number that is assigned by the port authority if a ship has not yet been assigned an official IMO number. This number will continue to exist until the ship is assigned an official IMO number.

Remark:

The following letters are also possible in the port of Ghent. H, Y, S and Z as provisional IMO number

3.2.1.2 Reference number of the message

The serial number of the message given by the port authorities. The serial number consists of a maximum of 21 an characters. PLDA does not carry out any verification on this number.

3.2.2 Notification of a passage

3.2.2.1 Passage

With regard to import, passage shall mean the first registration point of an ocean vessel.

With regard to export, passage shall mean the potential locking operations of a departing ocean vessel.

For the use of the codes, reference is made to chapter 7, 7.1.

3.2.2.2 Date and hour of the passage

Notification of the date and hour of the passages.

3.2.3 Notification of mooring

3.2.3.1 Mooring place

Mooring place shall mean the number of the mooring place in the seaport. In order to notify the mooring place, the codes mentioned in chapter 7, 7.2 shall be applied.

3.2.3.2 Date and hour of mooring

Notification of the date and hour of mooring.

3.2.4 Identification of the responsible shipping agent

This regards the shipping agent who is responsible to the port authority for the ocean vessel at the quay/mooring place. Reference is made to enclosure 1 of part 4 in order to consult the applicable codes.

3.2.5 Transport data

The name and nationality of the ocean vessel shall be given. The name of the ocean vessel shall be given in free text, the nationality of the ocean vessel shall be introduced by means of the ISO alpha-2 country code (see chapter 7,7.3).

3 Data modification, extension or cancellation

3.3.1 Data modification

Data that cannot be modified:

- the number of the declaration;

- the reference number of the message;

- the mooring date and hour;

- the mooring date and hour;

- the date and hour of leaving the port (last passage);

- the number of the mooring place;

- the quay number;

- the country of destination

Data that can be modified:

- the name of the ocean vessel;

- the nationality of the ocean vessel;

- the responsible shipping agent;

- the quay code;

- the code of the mooring place;

- the place of passage;

- date and hour of the passage.

REMARK: A modification of the date and the hour of the last place of passage (place code 17) for a departing ocean vessel (document name in code 833) shall only be implemented up to 5 days after the initial border crossing of the ocean vessel (place code 17).

3.3.2 Data extension

Only quay numbers and mooring place numbers connected to the date and hour of the mooring and of locking operations and the (last) passage connected to the date and hour of the locking operation or the (last) passage can be added, as well as the country of destination upon departure from the port of the ocean vessel.

3.3.3 Data cancellation

- The number of the declaration can be cancelled upon arrival as well as upon departure. This implies that all CUSREP messages sent by the port authority that are related to the number of the declaration which should be cancelled upon arrival or departure (depending on the document name in code), shall be removed from the G.C. system.

REMARK: if the number of the declaration should be cancelled with the document name in code 833 (departure), this cancellation can be implemented up to 5 days after the border crossing of the ocean vessel (place code 17).

- The place of passage, including the last passage export.

REMARK: if the passage place should be cancelled with the document name in code 833 (departure), this cancellation can be implemented up to 5 days after the initial border crossing notification of the ocean vessel (place code 17). - Quay/mooring place numbers connected to the date and hour of the mooring.

REMARK: if a quay/mooring place number should be cancelled with the document name in code 833 (departure), this cancellation can be implemented up to 5 days after the initial border crossing notification of the ocean vessel (place code 17).

Technical description of the message

1 Used segments

For the electronic exchange of the data with regard to the ocean vessel between the port authority and the customs, only the following segments in the CUSREP message shall be taken into consideration:

BGM : identification of the declaration/the message and the function of the message

GROUP 1: RFF identification of the previous message

GROUP 2: LOC identification of the quay place and/or passage place and the country of destination

DTM date and hour of mooring/passage

GROUP 5: NAD identification of the shipping agent

GROUP 8: TDT identification of the ocean vessel

2 Structure diagram

┌─────────┬──────────┬──────────┬──────────┐

┌──┴──┐ │ │ │ │

│ BGM │ │ │ │ │

LEVEL 0 ├──┬──┤ │ │ │ │

│M │ 1│ │ │ │ │

└──┴──┘ │ │ │ │

┌──┴──┐ ┌──┴──┐ ┌──┴──┐ ┌──┴──┐

│ GR1 │ │ GR2 │ │ GR5 │ │ GR8 │

├──┬──┤ ├──┬──┤ ├──┬──┤ ├──┬──┤

│C │99│ │C │99│ * │C │ 5│ │C │99│ *

LEVEL 1 ├──┴──┤ ├──┴──┤ ├──┴──┤ ├──┴──┤

│ RFF │ │ LOC │ │ NAD │ │ TDT │

├──┬──┤ ├──┬──┤ ├──┬──┤ ├──┬──┤

│M │ 1│ │M │ 1│ │M │ 1│ │M │ 1│

└──┴──┘ └──┼──┘ └──┴──┘ └──┴──┘

│

┌──┴──┐

│ DTM │

LEVEL 2 ├──┬──┤

│C │ 1│

└──┴──┘

(*) in case of a first sending, these segment(group)s are obligatory

3 Description of the used segments

4.3.1 BGM – Beginning of message

Function: identification of the declaration/the message and function of the message

010 C002 M : name document

1001 M : document name in code an..3

933 = declaration (arrival)

833 = declaration (departure)

1131 C : not used

3055 C : not used

1000 C : not used

020 1004 M : number declaration an...35

030 1225 M : function of this message an...3

2 = addition of data of the message

3 = cancellation of data of the message

4 = modification of data already sent

9 = first sending of basic data

040 4343 C : not used

SYNTAX : BGM+933+100000L9999999001+9'

4.3.2 Group 1/RFF – Reference

Function: the unique reference of the previous message

010 C506 M : reference

1153 M : reference code an...3

ACW= number of the declaration and reference number of the previous message

1154 C : reference number an...35

1156 C : not used

4000 C : not used

SYNTAX : RFF+ACW:100000L9999999001'

4.3.3 Group 2/LOC Identification of a place

Function: identification country/place/location

010 3227 M : place code an...3

5 = mooring of an ocean vessel

9 = place of loading

11 = place of unloading

15 = lock passage

17 = place border crossing

60 = in case of no unloading/loading in the port

90 = place of loading and unloading

92 = place of passage/locking operation

28 = country of destination

If the ocean vessel does not contain any goods that will be unloaded or loaded in the port, place code "60" shall be sent .

If the ocean vessel is leaving the harbour, the country to which the ocean vessel is sailing, shall be mentioned by means of place code "28".

020 C517 M : place identification

3225 M : quay an...25

The codes mentioned in Chapter 7,7.2. shall be applied.

passage place

The codes mentioned in Chapter 7,?? shall be applied.

country code

The ISO alpha-2 codes mentioned in Chapter 7 (point 7.3) shall be applied.

1131 C : code list an...3

140 = quay

ZZZ = mutual agreement (passage place and country codes)

3055 C : code responsible organism an...3

ZZZ = mutual agreement

3224 C : not used

030 C519 C : not used

040 C553 C : not used

050 5479 C : not used

SYNTAX : LOC+9+quay:140:ZZZ'

LOC+92+passage place:ZZZ:ZZZ'

LOC+28+country of destination:ZZZ:ZZZ'

4.3.4 Group 2/DTM Date and Time

Function: specification date, and/or time, or period

Remark: Group 2/DTM date and time shall not be used in case the country of destination (place code "28") has been mentioned in Group 2/LOC Identification of a place.

010 C507 M : date/time/period

2005 M : code date/hour an...3

178 = date and hour of mooring

186 = date and hour of mooring

219 = date of (border) passage

2380 M : date (yyyymmddhhmm) an...35

2379 C : not used

SYNTAX : DTM+178:199501010001'

DTM+219:199501010001'

DTM+186:200101010001'

4.3.5 Group 5/NAD Details with regard to the responsible shipping agent

Function: name of the shipping agent

010 3035 M : party code an...3

CG = shipping agent

020 C082 C : identity of the party

3039 M : code of the shipping agent an...17

(see enclosure 1, part 4)

1131 M : code list an...3

172 = code shipping agent

3055 M : code responsible organism an...3

ZZZ = mutual agreement

030 C058 C : not used

040 C080 C : not used

050 C059 C : not used

060 3164 C : not used

070 3229 C : not used

080 3251 C : not used

090 3207 C : not used

SYNTAX : NAD+CG+code shipping agent:172:ZZZ'

4.3.6 Group 8/TDT details of the transport

Function: specification of the details of the transport such as the mode of transport, the nature of the transport and the identification of the transport

010 8051 M : transport code an...3

11 = at (border) passage

12 = at departure

13 = at destination

020 8028 C : not used

030 C220 C : not used

040 C228 C : not used

050 C040 C : not used

060 8101 C : not used

070 C401 C : not used

080 C222 C : identification of the transport

8213 C : not used

1131 C : not used

3055 C : not used

8212 C* : name of the ocean vessel an...35

8453 C* : nationality of the ocean vessel an...3

= the ISO alpha-2 code

(*) in case of a first sending always obligatory, as well as in case of the notification of the country of destination upon departure

SYNTAX : TDT+13+++++++:::name:nat'

TDT+12+++++++:::name:nat'

Program specifications

1 The segment BGM

FUNCTION: identification of the declaration and its function

USE: M

| | | | | | | |

|C002 | |M | |NAME DOCUMENT | | |

| | | | | | | |

| |1001 |M |n3 |DOCUMENT CODE |933 |Declaration upon arrival |

| | | | | |833 |Declaration upon departure |

| | | | | | | |

|C106 | |M | |DOCUMENT IDENT | | |

| | | | | | | |

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

| | | | | | | |

|1225 | |M |n1 |FUNCTION OF THE MESSAGE |2 |Add |

| | | | | |3 |Cancel |

| | | | | |4 |Modify |

| | | | | |9 |First sending[1] |

| |

|SYNTAX : BGM+933+100000L9999999001+9' |

2 Group 1

FUNCTION: identification of the previous message

USE: C

CONTENT GROUP 1:

- segment RFF : M: reference

5.2.1 Segment RFF

FUNCTION: identification of the previous message

USE: M

| | | | | | | |

|C506 | |M | |REFERENCE | | |

| | | | | | | |

| |1153 |M |a3 |REFERENCE CODE |ACW |REFERENCE NUMBER |

| | | | | | | |

| |1154 |M |an...35 |REFERENCE NUMBER | | |

| |

|SYNTAX : RFF+ACW:100000L9999999001' |

3 Group 2

In the BGM segment, the function of the message shall be:

2 : addition of a quay number / mooring place number / connected to the date and hour of mooring and the locking operations and (last passage) connected to the date and hour of the locking operation or (last passage) may be added. As well as the country of destination upon departure of the ocean vessel from the port.

3 : cancellation of a declaration as well as the cancellation of a quay number / mooring place number connected to the date and hour of mooring and the passage places / locking operations including the last passage export (place code 17) connected to the date and hour of the passage / locking operation.

REMARK: if the number of the declaration or a quay number / mooring place number or passage places / locking operations is cancelled with the document name in code 833 (departure), the cancellation can be implemented up to 5 days after the border crossing of the ocean vessel (place code 17). The same regulation is applied in case of cancellation of the last passage export (place code 17).

4 : modification of the name and nationality of the vessel, shipping agent, a quay / mooring place code, a passage place and the date and hour of the passage.

REMARK: A modification of the date and hour of the last passage place (place code 17) for a departing ocean vessel (document name in code 833) can only be implemented up to 5 days after the initial border crossing of the ocean vessel (place code 17).

9 : Sending of the first passage (import), in case it is not known in time, the first quay number

REMARK 1:

GROUP 2 shall always be sent in its entirety in the following cases:

- function code (1225 of BGM) = 9 and 2.

- function code (1225 of BGM) = 3: in case of cancellation of the quay/mooring place or passage place/locking operation.

- function code (1225 of BGM) = 4: in case of modification of the date and/or hour of passage/locking operation,

quay/mooring place code and agent of a quay.

REMARK 2:

Despite the number of locations (GR2/99) as mentioned in the structure diagram described in this MIG, the use of only ONE location per message will be allowed. You will receive an error message when sending multiple locations, the message will have to be resubmitted correctly. This rule will be enforced as a Technical Rule.

USE: C (see above)

CONTENT GROUP 2:

- segment LOC : M : identification passage, quay or mooring place or country of destination

- segment DTM : C : date and hour of passage, mooring

5.3.1 Group 2 segment LOC

FUNCTION: specification of the passage place, quay place or mooring place, locking operation of country of destination

USE: M (see above)

| | | | | | | |

|3227 | |M |n...2 |PLACE CODE |5 |MOORING |

| | | | | |9 |PLACE OF LOADING |

| | | | | |11 |PLACE OF UNLOADING |

| | | | | |15 |LOCK PASSAGE |

| | | | | |17 |PLACE OF THE BORDER CROSSING |

| | | | | |60 |PLACE WITHOUT UNLOADING OR LOADING° |

| | | | | |90 |PLACE OF UNLOADING AND LOADING |

| | | | | |92 |PLACE OF PASSAGE / LOCKING OPERATION |

| | | | | |28 |COUNTRY OF DESTINATION |

| | | | | | | |

|C517 | |M | |PLACE IDENT | | |

| | | | | | | |

| |3225 |M |an...5 |PASSAGE PLACE OR QUAY OR COUNTRY OF | | |

| | | | |DESTINATION | | |

| | | | | | | |

| |1131 |C |n3 |CODE LIST |140 |QUAY or |

| | | | | | |MOORING PLACE NUMBER |

| | | | | |ZZZ |MUTUAL AGREEMENT (PASSAGE PLACE OR COUNTRY OF |

| | | | | | |DESTINATION) |

| | | | | | | |

| |3055 |C |n3 |CODE RESP. BODY |ZZZ |MUTUAL AGREEMENT |

| |

|SYNTAX : LOC+9+quay:140:ZZZ' |

|LOC+92+passage place:ZZZ:ZZZ' |

|LOC+28+country of destination:ZZZ:ZZZ' |

4 Group2/DTM Date and time

FUNCTION: specification date, and/or time, or period

REMARK: Group 2/DTM date and time shall not be used in case the country of destination (place code "28") has been mentioned in Group 2/LOC Identification of a place.

USE: C

| | | | | | | |

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

| | | | | | | |

| |2005 |M |n3 |DATE AND HOUR OF MOORING |178 | |

| | | | |DATE AND HOUR OF MOORING |186 | |

| | | | |DATE/HOUR (BORDER) PASSAGE |219 | |

| | | | | | | |

| |2380 |M |n12 |DATE - HOUR | |YYYYMMDDHHMM |

| |

|SYNTAX : DTM+178:199501010001' |

|DTM+219:199501010001' |

|DTM+186:200101010001’ |

5 Group 5

FUNCTION: Notification of the different parties.

CONDITIONS NAD IN GROUP 5:

The function code should be 2 (addition of a quay-mooring place number) or

4 (modification responsible shipping agent) or 9 (first sending of basic data, on the condition that the passage could not be/has not been sent).

REMARK:

The NAD segment shall always be sent in combination with GROUP 2 with the exception of the notification of the country of destination (place code 28) and the locking operations (place code 15, 17 and 92) in GROUP 2.

REMARK 2:

In case of modification (function of the message = 4) of the CUSREP message, the NAD segment is not mandatory.

USE: C (see above)

CONTENT GROUP 5:

- segment NAD : M : name/address parties

5.5.1 Group 5/NAD Data with regard to the responsible shipping agent

FUNCTION: code of the responsible shipping agent with regard to the port authority.

USE: M (see above)

| | | | | | | |

|3035 | |M |a2 |PARTY CODE |CG |SHIPPING AGENT |

| | | | | | | |

|C082 | |M | |PARTY IDENT | | |

| | | | | | | |

| |3039 |M |an...6 |CODE SHIPPING AGENT | | |

| | | | | | | |

| |1131 |M |a3 |CODE LIST |172 |CODE SHIPPING AGENT |

| | | | | | | |

| |3055 |M |n3 |CODE RESP. |ZZZ |MUTUAL AGREEMENT |

| | | | |BODY | | |

| |

|SYNTAX : NAD+CG+ASECO:172:ZZZ' |

6 Group 8

FUNCTION: identification of the general data concerning the vessel

CONDITIONS NAD IN GROUP 8:

This function code in the BGM segment shall be 4 (modification of the name, nationality of the ocean vessel), or 9 (first sending of the basic data) or 2 (notification of the country of destination upon departure of the ocean vessel).

USE: C (see above)

CONTENT GROUP 8:

- segment TDT : M : transport data

5.6.1 Group 8 segment TDT

FUNCTION: specification of the details of the transport such as the mode of transport, the nature of the transport and the identification of the transport.

USE: M (see above)

| | | | | | | |

|8051 | |M |n2 |TRANSPORT CODE |11 |AT (BORDER) PASSAGE |

| | | | | |12 |AT DEPARTURE |

| | | | | |13 |AT DESTINATION |

| | | | | | | |

|C222 | |M | |IDENT. TRANSPORT | | |

| | | | | | | |

| |8212 |C* |an...17 |NAME OCEAN VESSEL | | |

| | | | | | | |

| |8453 |C* |an2 |NATIONAL. OCEAN VESSEL | |ISO ALPHA-2 code |

| |

|SYNTAX : TDT+11+++++++:::name:nat' |

|(TDT+13+++++++:::name:nat') |

|TDT+12+++++++:::name:nat' |

Examples

1 Example of the (first) passage upon arrival

BGM+933+100000L9999999001+9'

LOC+92+S2:ZZZ:ZZZ'

DTM+219:199501010001'

NAD+CG+ASECO:172:ZZZ'

TDT+11+++++++:::SEAWOLF:BE'

2 Example of mooring

6.2.1 The passage has not been notified

BGM+933+800000L5000000002+9'

LOC+11+S869:140:ZZZ'

DTM+178:199501010001'

NAD+CG+ASECO:172:ZZZ'

TDT+13+++++++:::SEAWOLF:BE'

6.2.2 The passage has already been notified

BGM+933+800000L5000000002+2'

(RFF+ACW:800000L5000000001')

LOC+11+S869:140:ZZZ'

DTM+178:199501010001'

NAD+CG+ASECO:172:ZZZ'

3 Cancellation of all data of a message upon arrival

The elimination shall be notified in the segment BGM, simple data element 1225 with code "3".

BGM+933+800000L5000000002+3'

(RFF+ACW:800000L5000000001')

4 Cancellation of all data of a message upon departure

The elimination shall be notified in the segment BGM, simple data element 1225 with code "3".

BGM+833+800000L5000000002+3'

(RFF+ACW:800000L5000000001')

5 Cancellation of a passage upon arrival

BGM+933+800000L5000000002+3'

(RFF+ACW:800000L5000000001')

LOC+92+S2:ZZZ:ZZZ'

6 Cancellation of a passage upon departure

BGM+833+800000L5000000002+3'

(RFF+ACW:800000L5000000001')

LOC+92+S2:ZZZ:ZZZ'

7 Cancellation of the last passage upon departure

This cancellation shall be implemented within 5 days after the initial receipt of the last passage upon departure.

BGM+833+800000L5000000002+3'

(RFF+ACW:800000L5000000001')

LOC+17+S2:ZZZ:ZZZ'

8 Cancellation of a mooring place

BGM+933+800000L5000000002+3'

(RFF+ACW:800000L5000000001')

LOC+11+S869:140:ZZZ'

DTM+178:199501010001'

9 Cancellation of a mooring place

BGM+833+800000L5000000002+3'

(RFF+ACW:800000L5000000001')

LOC+9+S869:140:ZZZ'

DTM+186:199501010001'

10 Modification of a passage place upon arrival

BGM+933+800000L5000000002+4'

(RFF+ACW:800000L5000000001')

LOC+92+8:ZZZ:ZZZ'

11 Modification of a passage place upon departure

BGM+833+800000L5000000002+4'

(RFF+ACW:800000L5000000001')

LOC+92+8:ZZZ:ZZZ'

12 Modification of a place code upon arrival

BGM+933+800000L5000000002+4'

(RFF+ACW:800000L5000000001')

LOC+11+S869:140:ZZZ'

DTM+178:199501010001'

13 Modification of a passage place upon departure

BGM+833+800000L5000000002+4'

(RFF+ACW:800000L5000000001')

LOC+9+S869:140:ZZZ'

DTM+186:199501010001'

14 Modification of the date and/or hour of passage upon arrival

BGM+933+800000L5000000002+4'

(RFF+ACW:800000L5000000001')

LOC+92+S2:ZZZ:ZZZ'

DTM+219:199501020002'

15 Modification of the date and/or hour of passage upon departure

This modification shall be implemented within 5 days after the initial receipt of the last passage upon departure.

BGM+833+800000L5000000002+4'

(RFF+ACW:800000L5000000001')

LOC+17+S2:ZZZ:ZZZ'

DTM+219:199501020002'

16 Modification of a shipping agent (at quay) upon arrival

BGM+933+800000L5000000002+4'

(RFF+ACW:800000L5000000001')

LOC+11+S869:140:ZZZ'

DTM+178:199501010001'

NAD+CG+ASECO:172:ZZZ'

17 Modification of a shipping agent (at quay) upon departure

BGM+833+800000L5000000002+4'

(RFF+ACW:800000L5000000001')

LOC+9+S869:140:ZZZ'

DTM+186:199501010001'

NAD+CG+ASECO:172:ZZZ'

18 Modification of the data of an ocean vessel upon arrival

BGM+933+800000L5000000002+4'

(RFF+ACW:800000L5000000001')

TDT+13+++++++:::SEAWOLF:BE'

19 Modification of the data of an ocean vessel upon departure

BGM+833+800000L5000000002+4'

(RFF+ACW:800000L5000000001')

TDT+13+++++++:::SEAWOLF:BE'

20 Addition of a quay

BGM+933+800000L5000000002+2'

(RFF+ACW:800000L5000000001')

LOC+11+S869:140:ZZZ'

DTM+178:199501010001'

NAD+CG+ASECO:172:ZZZ'

21 Addition of a country of destination upon departure

BGM+933+800000L5000000002+2'

LOC+28+US:ZZZ:ZZZ'

TDT+12+++++++:::SEAWOLF:BE'

Enclosures

1 Enclosure 1: codes passages

7.1.1 Passages port of Antwerp

The codes to be used to indicate the passages in the port of Antwerp are listed in the document:

PLDA_05_coderingen berichten_V0 1.doc

7.1.2 Passages port of Ghent

The codes to be used to indicate the passages in the port of Ghent are listed in the document:

PLDA_05_coderingen berichten_V0 1.doc

7.1.3 Passages port of Zeebrugge

Enclosure The codes to be used to indicate the passages in the port of Zeebrugge are listed in the document:

PLDA_05_coderingen berichten_V0 1.doc

2 Enclosure 2: codes of the quays

7.2.1 Quays in Antwerp

The codes to be used to indicate the quays in the port of Antwerp are listed in the document:

PLDA_05_coderingen berichten_V0 1.doc

7.2.2 Quays in Ghent

The codes to be used to indicate the quays in the port of Ghent are listed in the document:

PLDA_05_coderingen berichten_V0 1.doc

7.2.3 Quays in Zeebrugge

The codes to be used to indicate the quays in the port of Zeebrugge are listed in the document:

PLDA_05_coderingen berichten_V0 1.doc

3 Enclosure 3: the Iso alpha-II codes

The Iso alpha-II codes can be consulted via the following website:



-----------------------

[1] This code cannot be used in case of qualifier 833 in data element 1001.

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

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

Google Online Preview   Download