Waterside EDI scenario #1

 I have uploaded here below  a sample of waterside EDI scenario.

What do you think about it ?

VESDEP, general infos

Purpose of the message: To provide information about the closing of a vessel and giving information about the actual containers operation.

Parties involved: it's mainly sent from Stevedore or Terminal Operator to Liner Agent.

Each VESDEP message should contain information only about one means of transport/conveyance.

Updates may be subsequently sent.

Here below a sample of the message:

UNB+UNOA:2+SENDER+RECEIVER+120104:1011+1'
UNH+2+VESDEP:D:95B:UN:ITG12'
BGM+630+3+9'
NAD+CA+XXX:160:ZZZ'
TDT+20+1234+1+13+XXX:172:87+++ABCD:103::VESSEL NAME’
RFF+VON:ABCD1234'
DTM+136:201201040830:203'
QTY+DIS:105'
QTY+LOA:200'
QTY+RES:8'
QTY+SHI:2'
UNT+14+2'
UNZ+1+1'

Here you can find a .sef file (version D.00B).

Merry Christmas !!!

In the past I never took care about such stuff: maybe I'm getting old or maybe not...
Anyway, best wishes to everybody who's following me here !

CALINF, general infos

Purpose of the message: To provide information about the planned arrival of a vessel (ie. E.T.A.) and the expected container operations.

Parties involved: It's mainly sent by Liner Agent to Terminal.

Each CALINF message should contain information only about one means of transport/conveyance.

Updates may be subsequently sent.

Here below a sample based on D99B.

UNB+UNOA:2+SENDER+RECEIVER+030627:1224+000000281++CALINF+++XXX'
UNH+000000385+CALINF:D:99B:UN'
BGM+96+000000385+9'
DTM+137:200306271224:203'
NAD+MS+XXX:172:166'
TDT+20+023N+1++XXX:172:166:NIPPON YUSEN KAISHA+++3FVSB:103::IRIS'
LOC+5+ARBUE:139:6'
DTM+136:200306040600:203'
LOC+153+BRRIG:139:6'
DTM+132:200306060600:203'
LOC+153+BRPNG:139:6'
DTM+132:200306070600:203'
LOC+153+BRRIO:139:6'
DTM+132:200306090600:203'
LOC+153+BRSSZ:139:6'
DTM+132:200306100600:203'
LOC+153+ZADUR:139:6'
DTM+132:200306250600:203'
LOC+153+SGSIN:139:6'
DTM+132:200307080600:203'
LOC+153+HKHKG:139:6'
DTM+132:200307120600:203'
LOC+153+JPNGO:139:6'
DTM+132:200307190600:203'
LOC+153+JPYOK:139:6'
DTM+132:200307250600:203'
UNT+26+000000385'
UNZ+1+000000281'

Container messages set

Most of the messages handled till now belong to the container messages set (ie. CO**** ).

Here below the full set of container messages:

CALINF Call information ( vessel ) / advice of expected container operations 
COARRI Container discharge / loading report 
CODECO Container gate in gate out report 
CODENO Document expiration / clearance ready notice 
COEDOR Container stock report 
COHAOR Container special handling order 
COPARN Container announcement 
COPINO Container pre notification 
COPRAR Container discharge / loading order 
COREOR Container release order 
COSTCO Container stuffing / stripping confirmation 
COSTOR Container stuffing / stripping order 
DESTIM Equipment damage /  repair estimate 
VESDEP Vessel departure

Here, under the label  miscellaneous document, you can find a very interesting document by the ITIGG. This document is referred to in the formal message documentation of all the CO**** messages as the "Guide to the Scenario of EDIFACT Container Messages".

In the next post I'll handle the remaining messages of the set.

APERAK request

The use of the APERAK, of course, must be agreed between EDI partners.

Anyway an EDI partner can ask for an acknowledgement, relating the receipt of the message sent, by means of data element 4343 on the BGM segment level.

Here below the sample of a BGM segment in a COREOR message requiring for an APERAK:

(...)
BGM+12:::TRANSPORT CARGO RELEASE ORDER+1234+9+AB'
RFF+REO:ORDER-ID'
(...)

The qualifier AB stands for Message Acknowledgement and indicates that an acknowledgement relating to receipt of message is required.

Using APERAK to confirm a truck appointment

In the previous scenario the Container Terminal, whenever agreed, can respond to the COPINO sent by the Inland Carrier with an APERAK.

The function of this message is: 

1. To inform a message issuer that his message has been received by the addressee's application and has  been rejected due to errors encountered during its processing in the application;
2. To acknowledge to a message issuer the receipt of his message by the addressee's application.

I have drafted an APERAK sample where the following data are available:

1. The reference to the COPINO previously acknowledged;
2. The reference of the truck appointment;
3. Start/End time slot for the truck appointment; 
4. The information related to the specified application error or acknowledgement.

UNB+UNOA:1+SENDER:ZZ+RECEIVER+110908:1130+1'

UNH+2+APERAK:D:96B:UN:ITG13'

BGM+11+3+9+AP'

DTM+137:201109081130:203'

DTM+64:201109091000:203'

DTM+63:201109091200:203'

RFF+ACW:00000001'

ERC+OK'

RFF+AEL:APPOINTMENT-ID'

FTX+AAO+++APPOINTMENT NR ?:APPOINTMENT-ID'

UNT+10+2'

UNZ+1+1'