COHAOR, inspection confirmation

In the previous sample a Local Forwarder was requesting to Terminal Operator to handle an inspection.

Here below here is Terminal Operator confirmation: container will be put aside, at a certain date/time, in order to be inspected.

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+100713:1200+1'
UNH+2+COHAOR:D:95B:UN:ITG13'
BGM+702+2+9'
DTM+137:201007131200:203'
FTX+AAI+++INSPECTION CONFIRMATION'
NAD+MS+SCT:160'
NAD+CF+GEK:172:87'
EQD+CN+GEKU1234567+4210:102:5++3+5'
RFF+CN:SAL/01'
DTM+7:201007140900:203'
LOC+165+ITSAL:139:6+SCT:TER:ZZZ'
FTX+AAA++GENERAL CARGO'
HAN+SP:130:184:EQUIPMENT PUT ASIDE FOR INSPECTION'
TDT+20+00018N+1+13+GEK:172:87+++47AVS:103::SALERNO PRIDE'
NAD+SLS+GEK:172:87'
CNT+1:1'
UNT+16+2'
UNZ+1+1'

COHAOR, general infos and inspection request

Purpose of the message: COHAOR is an order to perform specified special handlings and/or services on items of transport equipment.

Parties involved: message can be sent by Liner Agent / Local Forwarders to Terminal and vice versa.

I have drafted a sample based on:

• ITIGG Guideline 
• JM4/ITIGG/120/v.16.

 In this sample a Local Forwarder is requesting to the Terminal to handle a Custom Inspection on a certain date.

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+100713:1000+1'

UNH+2+COHAOR:D:95B:UN:ITG13'
BGM+702+2+9'
DTM+137:201007131000:203'
FTX+AAI+++INSPECTION REQUEST'
NAD+MS+LOCAL AGENT:160:87'
NAD+CF+GEK:172:87'
EQD+CN+GEKU1234567+4210:102:5++3+5'
RFF+CN:SAL/01'
DTM+7:20100714:102'
LOC+165+ITSAL:139:6+SCT:TER:ZZZ'
FTX+AAA++GENERAL CARGO'
HAN+63:130:184:TO BE INSPECTED'
TDT+20+00018N+1+13+GEK:172:87+++47AVS:103::SALERNO PRIDE'
NAD+SLS+GEK:172:87'
CNT+1:1'
UNT+16+2'
UNZ+1+1'

COARRI, over-height container to be transhippend onto feeder

That's a sample about an over-height container to be transhipped onto a feeder vessel.

(...)
EQD+CN+GSLM1506100+22U1:102:5++6+5'
RFF+BN:SAL/01'
DTM+203:201006151030:203'
LOC+9+SGSIN:139:6'
LOC+147+0330406::5’
MEA+WT+G+KGM:11490'
DIM+9+CMT:::55'
SEL+6789+CA'
FTX+AAA+++MACHINE PARTS'
TDT+30+00019N+1+11+GEK:172:87+++47AVS:103'
LOC+7+ITGIT:139:6'
DTM+133:201006161400:203'
(...)

COARRI, brief indication about container repair condition

In some circumstances it may be useful to state, into COARRI, a brief indication about the container repair condition. Let's see a sample:

(...)
MEA+AAE+T+KGM:3800'
MEA+AAE+G+KGM:23870'
SEL+0068856+CA+1'

FTX+DAR++5:ZZZ:184+AWAITING INSPECTION'
CNT+16:1'

(...)

A detailed documentation about the usage of the Indication of Damage Condition (DAR) is provided by ITIGG (International Transport Implementation Guidelines Group) here under the section "Code List for the FTX Segment".

COARRI, trigger time

As mentioned in the previous post, COARRI are normally sent by Terminal Operator to Line or Liner Agent.

Basically a Terminal Operator has two options when sending COARRI:

• Set-up a trigger time-interval (i.e. every x minutes);
• Wait till vessel departure.

Both the ways have pros and cons so I have prepared the below poll for everyone who wants to join:

COARRI, general infos

Purpose of the message: the COARRI message is used to confirm that containers have been discharged/loaded from/on a sea going vessel. COARRI is also used to confirm that containers have been shifted or restowed on board a vessel.

Parties involved: message is normally sent by Terminal Operator to Line or Liner Agent.

Here below a sample of COARRI, loading:

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+100414:1014+1269953057176'
UNH+1269953057162+COARRI:D:95B:UN:ITG12'
BGM+270:::LOADING REPORT+06806003300003+9'
FTX+OSI++L'
TDT+20+00018N+1+13+GEK:172:87+++47AVS:103::SALERNO PRIDE'
LOC+9+ITSAL:139:6'
DTM+132:201004140600:203'
DTM+133:201004141400:203'
NAD+CA+GEK:172:ZZZ'
EQD+CN+GEKU1234567+4210:102:5++2+5'
RFF+BN:SAL/01'
DTM+203:201004141010:203'
LOC+11+ILHFA:139:6'
LOC+7+ILHFA:139:6'
LOC+147+200414::5'
MEA+AAE+T+KGM:3500'
MEA+AAE+G+KGM:23000'
SEL+5178170+TO+1'
FTX+DAR++6:ZZZ:184+NOT DAMAGED'
CNT+16:1'
UNT+21+1269953057162'
UNZ+1+1269953057176'

My EDI Notes forum

Hi everybody !

I have to admit to be very surprised about the number of the access to my blog: it seems that, all around, there are a lot of people involved in EDI issues !

That's because, I decided to add a forum (http://gekseppe.blogspot.com/p/my-edi-notes-forum.html) where everybody can:

• Post EDI samples;
• Share infos;
• Open any kind of topic about EDI.

Feel free to join and to contribute with your experience !