Mapping a remark field into FTX segment

Mapping an internal remark field, from the source data base to a FTX segment of an out-coming EDI transaction, may be  an issue.

First of all you should wonder which kind of data the end user could store into the source data base as remark and if it is appropriate to send it to an external customer: while debugging some EDI transactions it happened me to find very funny data and even some telephone numbers to contact, at the transport stage of the container, in case of problems. 

Furthermore, piece of data into FTX segment, are often incompatible with the character set adopted in the interchange and, although unnecessary, prevent message to be properly processed. 

Here below some very common errors which happen in my EDI environment mainly based on the UNOA character set:

Lowercase characters

FTX+AAI+++clean container foodstuff quality'

Missing escape character "?" in conjunction with ":"

FTX+AAI+++RELEASE DATE FROM: 19/09/2012'  

 Not allowed character "\"

FTX+AAI+++CLEAN CONTAINER \ FOODSTUFF QUALITY'

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.

Restow in BAPLIE file

Some days ago I received the following complaint from an EDI customer:

"However everytime we receive a departure BAPLIE from your Terminal, where we have performed restows, we always get the restowed units showing as loaded from your port which clashes with the restowed unit."

In the beginning, I thought to have messed up some mapping rules but after having a look at the config file I realised that, at my end, everything was set-up properly. 

Here is the EQD segment group concerning a unit restowed by my Terminal:

(...)

LOC+147+0250208::5'
MEA+WT++KGM:6960'
LOC+9+ITSAL'  >> Place/port of loading
LOC+11+PTLEI' >> Place/port of discharge
LOC+83+PTLEI' >> Place of delivery (by on carriage)
LOC+76+ILHFA' >> Original port of loading
RFF+BM:1'

EQD+CN+ABCD1234567+22G1+++5'
(...)

I guess that customer's EDI translator has some issues in handling OPOL (Original Port of Loading) in conjunction with POL (Port of Loading): of course that's not up to me and, at least once, I was happy to close the support request without changing anything ! 

Call sign and Lloyd's number

One of the most frequent error that I have to handle in my EDI environment, while processing incoming EDI transactions, relates to wrong Call Sign / Lloyd's Number stated into the TDT segment as c222.8213.

Here is some useful sites where you can check about vessels Call Sign, Lloyd's Number and other interesting stuff about ships/boats: 

• Equasis (registration required);
• Marine Traffic;
• Vessel Tracker.