Charge IMPORT STORAGE in a container terminal based on UN/EDIFACT files

If you work in a container terminal and you are in charge for invoicing processes, that's a very handy flow chart about where to retrieve sensitive info to charge import storage.

Hope it can be useful to you!

Standardization problems

Standardization is definitely a complicated process: tons of MIGs are available on the web but end users always find the way to create unpredictable variables to prevent a correct data processing.  

Recently, I'm struggling with an issue about the VAT number of freight forwarders/custom brokers reported into COREOR D00B: apparently, it's unclear if the nation code has to be included, as NAD02, in NAD segment when reporting the VAT number. 

In terms of message structure, that's the issue: 

NAD+FW+IT03450730100:160:ZZZ'

OR

NAD+FW+03450730100:160:ZZZ'

Value reported in NAD02, is the target value to transcoding hence the prefix 'IT' makes a big difference when applying the mapping rules and the translation rules.

I'm quite interested in collecting feed-back about this topic: in case you are experiencing the same issue in your EDI environment, you can drop a comment here!

COPINO case of study: ECT Terminal

The below snapshot comes from ECT web site and offers a very interesting overview about the procedures currently implemented to deliver import containers by means of UN/EDIFACT messages COREOR and COPINO.

Parties involved in the procedure are:

- Box Operator (ie. Line, Liner Agent etc) which is in charge for COREOR;

- Inland Carrier (ie. Trucking Company or Barge) which is in charge for COPINO.

Basically containers will be released from the Terminal only in case the PIN number declared by Inland Carrier in COPINO will match with PIN number declared in COREOR by Box Operator.

Look here about how to declare a PIN number into COREOR.

COREOR, start/end validity date

It's very common to define, in COREOR message, a start/end validity date.

Here below you can find related sample:

(...)
EQD+CN+GEKU1234567:102:5+22G1:102:5++3+5'
RFF+SQ:1'
RFF+BM:123456'
DTM+7:20101012:102'
DTM+36:20101020:102'
(...)

COREOR, PIN number

For security issues, you might wish to add a PIN number to your COREOR message.

PIN number can be stored in RFF segment; in the above sample, I used qualifier RE (Release Number) as c506.1153 in order to assign to my container a PIN number:

(...)
EQD+CN+GEKU1234567+22G1:102:5++3+5'
RFF+CN:SAL/01' 
RFF+RE:QY879' 
RFF+SQ:0001'
MEA+AAE+G+KGM:23817'
(...)

COREOR, general infos

Purpose of the message: COREOR is used to release full import/export containers.

Parties involved: the message is normally sent by Carrier/Liner Agent to Terminal Operator.

I have seen several Carriers to use the COREOR to release empty transport equipment prior to packing but, based on ITIGG recommendations, COPARN should be used.

Here below a very basic sample of COREOR message:

UNB+UNOA:1+SENDER-ID+RECEIVER-ID+100920:1000+1'
UNH+2+COREOR:D:95B:UN'
BGM+12+3+9'
RFF+BM:SAL/01'
TDT+20+00018N+1++GEK:172:20+++47AVS:103::SALERNO PRIDE'
RFF+VON:0123N'
NAD+CA+GEK:172:20'
EQD+CN+GEKU1234567+22R1:102:5++3+5'
RFF+SQ:1'
CNT+16:1'
UNT+10+2'
UNZ+1+1'