CODECO, pre-carriage info

Here is the definition of "pre-carriage" based on ITIGG documentation: "physical movement of a container before arrival at a place/port for loading on the primary means of transport."

In the below sample of EQD.TDT segment group you can find detailed infos (ie. Trucking Company-id, Truck Plate) related to the pre-carriage of a Full-In container:

(...) 

TDT+1++3+31+GKP0001:172+++NA098WY:146:ZZZ'
LOC+7+ITSAL:139:6+SCT:TER:ZZZ'
(...)

CODECO, goods info

Normally cargo details should been given by messages belonging to IFTM-set but, where agreed by users, CODECO can also provide brief cargo details.

Here below a sample:

(...)

GID+1+785:CT:::CARTON(S)'
FTX+AAA+++VARIOUS, NOS'
MEA+AAE+G+KGM:21080'
MEA+AAE+T+KGM:2200'
(...)

I have used Package Code List based on JMA/ITIGG/121/v.11 that you can find here under the directory Documents / Downloads.

CODECO, general infos

Purpose of the message: CODECO is used to confirm that a container was delivered or picked up by an inland carrier (ie. road, rail or barge). Message is also used to report:

• In/Out moves from/to the Repair Location; 
• Change of the lease status of the container in Leasing Industry (ie. on/off hire transactions). 

Parties involved: CODECO in mainly sent by Terminal Operator to Carrier / Liner Agent.

Here below a sample of CODECO concerning the report of a Full-In move by Terminal Operator.

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+110117:1401+1292528559464'
UNH+1292528559355+CODECO:D:95B:UN:ITG14'
BGM+34:::TRANSPORT EQUIPMENT GATE IN REPORT+07470574000001+9'
TDT+20+00018N+1+13+GEK:172:87+++47AVS:103::SALERNO PRIDE'
LOC+9+ITSAL:139:6+SCT:TER:ZZZ'
DTM+132:201101241000:203'
NAD+CF+GEK:172:87'
NAD+AG+LINER AGENT:160'
GID+1'
FTX+AAA+++VARIOUS, NOS'
EQD+CN+GEKU1234567+22G1:102:5++2+5'
RFF+BN:SAL/01'
DTM+7:201101171359:203'
LOC+11+CAMTR:139:6'
LOC+165+ITSAL::6+SCT:TER:ZZZ'
MEA+AAE+G+KGM:21080'
MEA+AAE+T+KGM:2000'
SEL+A154+CA'
SEL+133726+SH'
FTX+DAR++6:ZZZ:184+NOT DAMAGED'
TDT+1++3+31+XXX0001:172+++XX098WY:146:ZZZ'
LOC+7+ITSAL:139:6+SCT:TER:ZZZ'
CNT+16:1'
UNT+23+1292528559355'
UNZ+1+1292528559464'

Import Scenario #1

Till now we have covered several UN/EDIFACT messages and now it's time to create a sample EDI Flow-Chart !

That's a very basic import scenario which is used almost everywhere.

Check it out and let me know in case of  any questions.

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'
(...)

UN/LOCODE

UN/LOCODE is a geographic coding scheme developed and maintained by UNECE a unit of the United Nations. 

It assigns aproximatly 40.000 code elements to locations names of ports, airports, rail and road terminals, postal exchange offices, border crossing points and other locations used in trade and transport in 234 countries.

UN/LOCODE typically have 5 characters. The first 2 are letters, and come from the ISO 3166-1 country codes. Normally 3 letters will follow, but if there are not enough combinations, also numbers can be used.

Some samples: 

• DEBER for Berlin in Germany (DE) 
• NLAMS for Amsterdam in NL 
• USNYC for New York City in US

In order to browse through LOCODEs you can use the useful web services developed by UNECE or Antwerp Port Authority.

I would like to thanks www.knowledgerush.com as source for this post.