Saturday 1 September 2012

Main carriage transport in COPARN

An error that often I have to handle manually in my EDI environment concerns the 'Main Carriage Transport' declared in the H.TDT.TDT segment of some COPARN messages.

Let’s have a look at the following sample:

(...)
TDT+20+2036+1++XXX:172:166+++XXX:103::VESSEL NAME'
LOC+9+ITGOA:139:6:GENOA'
LOC+11+AUMEL:139:6:MELBOURNE'
DTM+133:201209030000:203'
NAD+CF+XXX:172:166'
NAD+MR+ITSALSCT’
EQD+CN++22GP:102:5++2+4'
RFF+SQ:001'
EQN+1'
LOC+163+AUMEL:139:6:MELBOURNE'
MEA+AAE+X+KGM:19250'
TDT+1+TRANSPORTER+3'
LOC+165+ITSAL:139:6:SALERNO'
(...)


That’s a COPARN concerning a container with the following characteristics:
  1. To be loaded onto a vessel qualified as 'Main Carriage Transport';
  2. Loading port: Genoa (ITGOA);
  3. Place/Port of discharge: Melbourne (AUMEL);
  4. Place/Port of destination for stowage purposes: Melbourne (AUMEL);
  5. Activity Location: Salerno (ITSAL).
So here is the final container route:
  1. Collected/Deivered at Salerno port;  
  2. Loaded from Salerno to Genoa Port by a feeder vessel;  
  3. Transhipped from Genoa to Melbourne Port by the mother vessel declared in the TDT segment.
Of course not always mother vessels, operational on external quays,  are stored into my system and unfortunately affected COPARN messages get rejected due to missing valid vessel call.

No comments:

Post a Comment