Pages

Wednesday, 22 April 2009

BAPLIE

Purpose of the message: BAPLIE is used to transmit infos about all occupied places onboard of a vessel. Although the message can also transmit infos about 'empty places', this feature is not generally used.
Parties involved: Tonnage Center, Shipowner, Terminal operator.
The way it works: Generally BAPLIE is transmitted to the terminal operator of the next vessel call to retrieve all the relevant infos. Subsequently:
  • Infos about equipment discharged will be removed;
  • Infos about equipment loded will be added;
  • Location about equipment shifted will be changed.
At vessel's sailing time, updated BAPLIE will be transmitted to: shipowner, tonange center and terminal operator of the next vessel call. Generally message is also transmitted to the vessel in order to replace the 'paper' master-bayplan.
Infos about 'Remain On Board' (i.e. equipment not handled during discharge/load operations) must remain unchanged and then transmitted to the next vessel call.
Here below a sample of a BAPLIE file 2.0.7. Here you can download the corresponding MIG.

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090211:0811+0001+++++GEKU'
UNH+0001+BAPLIE:D:95B:UN:SMDG20'
BGM++0001+9'
DTM+137:0902110811:201'
TDT+20+00018NB+++GEK:172:ZZZ+++47AVS:103:ZZZ:SALERNO PRIDE:IT'
LOC+5+ITCAG:139:6'
LOC+61+ITSAL:139:6'
DTM+132:090211:101'
DTM+178:0902111230:201'
DTM+136:0902112330:201'
RFF+VON:GKS01A'
LOC+147+0010112::5'
MEA+WT++KGM:22500'
LOC+9+ITCAG:139:6'
LOC+11+ITSAL:139:6'
RFF+BM:1'
EQD+CN+GEKS1504090+22G1+++5'
NAD+CA+GEK:172:ZZZ'
UNT+18+0001'
UNZ+1+0001'

Saturday, 18 April 2009

Carriage Returns (CR) and/or Line Feeds (LF)

All the segments into our INVOIC sample are shown on separate lines. Anyway, in accordance with EDIFACT Syntax Rules, no Carriage Returns (CR) and/or Line Feeds (LF) must be used in a real data transaction.

Here is how our INVOIC sample now looks like:
UNB+UNOA:1+005435656:1+006415160:1+060515:1434+00000000000778'
UNH+00000000000117+INVOIC:D:97B:UN'BGM+380+342459+9'DTM+3:20060515:102'
RFF+ON:521052'NAD+BY+792820524::16++CUMMINS MID-RANGE ENGINE PLANT'NAD+SE+005435656::16++GENERAL WIDGET COMPANY'CUX+1:USD'LIN+1++157870:IN'IMD+F++:::WIDGET'QTY+47:1020:EA'ALI+US'
MOA+203:1202.58'PRI+INV:1.179'LIN+2++157871:IN'IMD+F++:::DIFFERENT WIDGET'
QTY+47:20:EA'ALI+JP'MOA+203:410'PRI+INV:20.5'UNS+S'MOA+39:2137.58'ALC+C+ABG'
MOA+8:525'UNT+23+00000000000117'UNZ+1+00000000000778'

Tuesday, 14 April 2009

UN/EDIFACT message sample: further comments

Let's have a closest look at the contents of our INVOIC sample. By EDI Notepad I took a snap shot of the Interchage details:









Then, a snap shot of the Message general infos:
















And a snap shot of the Items of the Transaction:






Dimensione carattere


All the data are stored into a segment with the proper qualifier; so if , for instance we need to figure out the buyer, we have to deal with the Name and Adress segment (NAD):
NAD+BY+792820524::16++CUMMINS MID-RANGE ENGINE PLANT'
Here we can find the buyer details (qualifier BY is used to give to the party the Buyer role) with the corresponding D-U-N-S code (792820524) and its description (CUMMINS MID-RANGE ENGINE PLANT).

If we want to refer to INVOIC D97B implementation guide, then we can summarize NAD infos as follow:

(click to enalrge)


The same can be done with the remaining segments of the message.