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'

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".