COPARN, showing the second on-carriage transport

That's a sample to state into a Full-In COPARN the second on-carriage transport:

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090730:1323+1'
UNH+2+COPARN:D:00B:UN:SMDG20'
BGM+126+3+9'
DTM+137:200907301523:203'
RFF+BN:SAL/01'
DTM+36:200908101200:203'
TDT+20+00018N+1++GEK:172:87+++47AVS:103::SALERNO PRIDE'
RFF+VON:GKS01A'
LOC+9+ITSAL:139:6'
DTM+132:200908091200:203'
NAD+FW+0001+FORWARDING PARTY'
NAD+CA+GEK:172:ZZZ'
NAD+MS+GEK:172:ZZZ'
CTA+IC+:GEKSEPPE'
COM+0039089230550:TE'
EQD+CN+GEKS1504090+45G1:102:5+2+2+5'
RFF+BN:SAL/01'
EQN+1'
TMD+3++2'
LOC+8+GWOXB:139:6'
LOC+98+ITSAL:139:6'
LOC+11+ESALG:139:6'
MEA+AAE+AET+KGM:10474'
MEA+AAE+T+KGM:4200'
SEL+00214784+SH+1'
FTX+AAA+++VARIOUS, NOS'
TDT+30+09+1++XXX:172:87+++478AWD:103::WET OCEAN'
DTM+132:200908130600:203'
LOC+11+GWOXB:139:6'
CNT+16:1'
UNT+30+2'
UNZ+1+1'

COPARN

Formal Definition: The message contains an order to release, to make available, to accept, to call down containers or to announce the impending arrival of containers.

Some samples of message usage:

• Requesting or authorising acceptance of an empty container;
• Requesting or authorising acceptance of a full container;
• Releasing an empty container for packing;
  
• Requesting or authorising an on/off hire transaction.

In any case, COPARN message will be 'answered' by a CODECO message confirming that the equipment movement or status change has been taken place.

Here below a very basic COPARN sample used to release an empty container expected to be loaded on vessel:

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090722:0800+1'
UNH+2+COPARN:D:95B:UN:ITG11'
BGM+12:::RELEASE ORDER+3+9'
RFF+BN:SAL/01'
TDT+20+00018N+1++GEK:172:87+++47AVS:103::SALERNO PRIDE'
RFF+VON:GKS01A'
LOC+165+ITSAL:139:6'
DTM+132:200907251430:203'
NAD+MR+RECEIVER-ID:160:87'
NAD+CF+GEK::172:87'
CTA+IC+BOOKING DPT:TEL.?+39 000 0000000'
EQD+CN++42G1:102:5++2+4'
RFF+CN:SAL/01'
EQN+1'
LOC+11+ITGIT:139:6'
MEA+AAE+G+KGM:4200'
TDT+1++3+31'
CNT+16:1'
UNT+18+2'
UNZ+1+1'

COPRAR, loading empty container(s) based on type

Here below you can find a sample of a COPRAR used to load 5 empty containers with the same characteristics (i.e. 20/DV/8'6). Note the usage of EQN segment (Nr. of units) in EQD segment group.

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090525:1601+1'
UNH+2+COPRAR:D:95B:UN:ITG12'
BGM+45+2+9'
FTX+OSI++L'
RFF+XXX:1'
TDT+20+00018N+1++GEK:172:87+++47AVS:103::SALERNO PRIDE'
RFF+VON:GKS01A'
LOC+9+ITSAL:139:6+SCT:TER:ZZZ'
DTM+132:200905271900:203'
DTM+133:200905281900:203'
NAD+CA+GEK:160:ZZZ'
EQD+CN++22G1:102:5++2+4'
RFF+BN:SAL/01'
EQN+5'
TMD+2'
LOC+11+CATOR:139:6'
MEA+AAE+G+KGM:2200'
FTX+ABS++67::184'
CNT+1:1'
UNT+19+2'
UNZ+1+1'

Replacing the previous COPRAR

Let's suppose that something in the previous COPRAR sample has to be amended (i.e. the reefer temperature set point). Here below the updated COPRAR:

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090525:1701+1'
UNH+3+COPRAR:D:95B:UN:ITG12'
BGM+45+3+5'
FTX+OSI++L'
RFF+ACW:2'
TDT+20+00018N+1++GEK:172:87+++47AVS:103::SALERNO PRIDE'
RFF+VON:GKS01A'
LOC+9+ITSAL:139:6+SCT:TER:ZZZ'
DTM+132:200905271900:203'
DTM+133:200905281900:203'
NAD+CA+GEK:160:ZZZ'
EQD+CN+GEKS1504090+22R1:102:5++2+5'
RFF+BN:SAL/01'
TMD+3'
LOC+11+CATOR:139:6'
LOC+7+CABUB:139:6'
MEA+AAE+G+KGM:22500'
TMP+2+010:CEL'
SEL+3667786+CA'
FTX+HAN++AB::184'
FTX+AAA+++MOZZARELLA'
EQA+RG+GEKS0001'
CNT+1:1'
UNT+23+3'
UNZ+1+1'

The following requirements are needed:

• 1225=5 (Replace previous message) on H.BGM;
• c506.1153=ACW on H.RFF;
• c506.1154 = Document message number of the previous message to replace (BGM 1004) on H.RFF.

COPRAR: adding a stowage instruction

Here below a Loading COPRAR with the instruction to stow the container away from boiler (i.e. EQD.FTX level with 4441='AB'):

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090525:1601+1'
UNH+2+COPRAR:D:95B:UN:ITG12'
BGM+45+2+9'
FTX+OSI++L'
RFF+XXX:1'
TDT+20+00018N+1++GEK:172:87+++47AVS:103::SALERNO PRIDE'
RFF+VON:GKS01A'
LOC+9+ITSAL:139:6+SCT:TER:ZZZ'
DTM+132:200905271900:203'
DTM+133:200905281900:203'
NAD+CA+GEK:160:ZZZ'
EQD+CN+GEKS1504090+22R1:102:5++2+5'
RFF+BN:SAL/01'
TMD+3'
LOC+11+CATOR:139:6'
LOC+7+CABUB:139:6'
MEA+AAE+G+KGM:22500'
TMP+2+015:CEL'
SEL+3667786+CA'
FTX+HAN++AB::184'
FTX+AAA+++MOZZARELLA'
EQA+RG+GEKS0001'
CNT+1:1'
UNT+23+2'
UNZ+1+1'

COPRAR, Load

Here below a sample concerning an operational reefer plus reefer generator to be loaded on vessel.

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090525:1601+1'
UNH+2+COPRAR:D:95B:UN:ITG12'
BGM+45+2+9'
FTX+OSI++L'
RFF+XXX:1'
TDT+20+00018N+1++GEK:172:87+++47AVS:103::SALERNO PRIDE'
RFF+VON:GKS01A'
LOC+9+ITSAL:139:6+SCT:TER:ZZZ'
DTM+132:200905271900:203'
DTM+133:200905281900:203'
NAD+CA+GEK:160:ZZZ'
EQD+CN+GEKS1504090+22R1:102:5++2+5'
RFF+BN:SAL/01'
TMD+3'
LOC+11+CATOR:139:6'
LOC+7+CABUB:139:6'
MEA+AAE+G+KGM:22500'
TMP+2+015:CEL'
SEL+3667786+CA'
FTX+AAA+++MOZZARELLA'
EQA+RG+GEKS0001'
CNT+1:1'
UNT+22+2'
UNZ+1+1'

Use of DGS segment within EQD group (ITIGG recommendation JM4/273)

Some other remarks about IMDG infos and DGS segment.

Function of the segment: The DGS segment at this level is used to specify any dangerous goods details for the transport equipment identified in the precedent EQD segment.

Segment usage: The use of the DGS segment within this group is dependant. If the cargo within the transport equipment has hazardous characteristics then its use is required otherwise is not used. At this level the segment can also be used to identify any hazardous cargo residues which may remain in the container after unpacking.

Sample: DGS+IMD+8:135+1733+140:CEL+2'

COPRAR discharge with IMDG infos

Here below you can find a new COPRAR discharge sample where I have added infos about Dangerous Goods; you can note several new segments about:

• Container Operator's reference number to be used for DG reference number according to DG reference number in stowage instructions (EQD.RFF with c506.1153 = 'CV');
• Hazard Code infos (DGS segment);
• Dangerous Goods Technical Name (EQD.FTX with 4451 = 'AAD').

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090525:1601+1'
UNH+2+COPRAR:D:95B:UN:ITG12'
BGM+43+2+9'
FTX+OSI++D'
RFF+XXX:1'
TDT+20+00018N+1++GEK:172:87+++47AVS:103::SALERNO PRIDE'
RFF+VON:GKS01A'
LOC+11+ITSAL:139:6+SCT:TER:ZZZ'
DTM+132:200905271900:203'
DTM+133:200905281900:203'
NAD+CA+GEK:160:ZZZ'
EQD+CN+GEKS1504090+22G1:102:5++3+5'
RFF+AAY:00123456'
RFF+BN:SAL/01'
RFF+CV:XXX009/MCA'
TMD+3'
LOC+9+CAMTR:139:6'
LOC+7+ITSAL:139:6+SCT:TER:ZZZ'
MEA+AAE+G+KGM:22500'
SEL+3667786+CA'
FTX+AAA+++ENVIRONMENTALLY HAZARDOUS SUBSTANCE'
FTX+AAD+++ENVIRONMENTALLY HAZARDOUS, SUBSTANC:E, SOLID, N.O.S. (CARBOXIN 97%)'
DGS+IMD+9+3077++3+++++9'
CNT+1:1'
UNT+24+2'
UNZ+1+1'

COPRAR, discharge

Purpose of the message: discharge COPRAR is used to transmit an order to discharge container(s) from a seagoing vessel;
Parties involved: Shipping Line sends the message to the Terminal Operator which handles the vessel.

In addition to container(s) to be discharged, message can also transmit infos about:

• Container(s) to be shifted on board the vessel;
• Container(s) to be discharged and reloaded onto vessel.

Here below a sample based on ITIGG user manual vers. ITG12.

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090525:1601+1'

UNH+2+COPRAR:D:95B:UN:ITG12'

BGM+43+2+9'

FTX+OSI++D'

RFF+XXX:1'

TDT+20+00018N+1++GEK:172:87+++47AVS:103::SALERNO PRIDE'

RFF+VON:GKS01A'

LOC+11+ITSAL:139:6+SCT:TER:ZZZ'

DTM+132:200905271900:203'

DTM+133:200905281900:203'

NAD+CA+GEK:160:ZZZ'

EQD+CN+GEKS1504090+22G1:102:5++3+5'

RFF+AAY:00123456'

RFF+BN:SAL/01'

TMD+3'

LOC+9+CAMTR:139:6'

LOC+7+ITSAL:139:6+SCT:TER:ZZZ'

MEA+AAE+G+KGM:22500'

SEL+3667786+CA'

FTX+AAA+++TOMATOES'

CNT+1:1'

UNT+21+2'

UNZ+1+1'

BAPLIE for rail

In North Europe BAPLIE is also used to transmit, to the Rail Terminal Operator, infos about all railway wagons in a train.

Here below you can find a message sample based on SMDG's MIG (Version 0.1): that's a DRAFT version (still to be discussed) but, in my opinion, it's the right way to start !

UNB+UNOA:2+SENDER-ID+RECEIVER-ID+090211:0300+0001'
UNH+0001+BAPLIE:D:95B:UN:SMDG10'
BGM+746+0001+9'
DTM+137:0902110500:201'
TDT+20+11E+++GEK:172:ZZZ+++GTS01:ZZZ:ZZZ:POLAR EXPRESS:IT'
LOC+5+ITNOL:139:6'
LOC+8+ITSAL:139:6'
DTM+132:0902110730:201'
DTM+136:0902110500:201'
LOC+147+01+218333585907+01'
FTX+AAA+++TOMATOES'
MEA+WT++KGM:22500'
LOC+9+ITNOL:139:6'
LOC+11+ITSAL:139:6'
RFF+BM:1'
EQD+CN+GEKS1504090+22G1++3+5'
NAD+CA+GEK:172:ZZZ'
UNT+17+0001'
UNZ+1+0001'

Some comments about 'Stowage Cell':

• C517.3225: That's the first wagon in the train after the locomotive (01);
• C519.3223: That's the wagon numer as painted on the wagon (218333585907);
• C553.3233: On the wagon each 20FT slot has a number (01, 02...). In the sample container is allocated in the first slot (close to the locomotive).

BAPLIE: further comments

In the previous BAPLIE sample there is the following Stowage Instruction:

• Container: GEKS1504090 (LOC.EQD segment as c237.8260);
• Stowage Position: 0010112 (LOC.LOC segment as c517.3225);
• Main-Carrige Transport: Vessel SALERNO PRIDE (TDT.TDT segment);
• Loading Port: Cagliari (LOC.LOC segment as c517.3225);
• Discharging Port: Salerno (LOC.LOC segment as c517.3225).

There are also other interesting infos into the file and I would suggest to use the BAPLIE Viewer in order to retrieve them.

BAPLIE is also used to give infos about Breakbulk cargo loaded onto vessels; let's have a look at the next sample to understand the way it works:

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'
FTX+AAA+++LARGE VEHICLE'
MEA+WT++KGM:32500'
DIM+1+CMT:890:250:220'
LOC+9+ITCAG:139:6'
LOC+11+ITSAL:139:6'
RFF+BM:1'
EQD+BB+NY20978ZZ'
NAD+CA+GEK:172:ZZZ'
UNT+20+0001'
UNZ+1+0001'

I have added a couple of extra infos in order to deal properly the Breakbulk:

• Element 8053 on LOC.EQD segment now is BB (Breakbulk);
• On LOC.DIM segment there are off-standard Breakbulk dimensions; in detail:
  890 cm over-length, 250 cm over-width and 220 cm over-height.

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'

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'

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:

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.

UN/EDIFACT message sample

Here below an INVOIC D97B sample:

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'

Now, let's try to locate all the items mentioned in the previous post:

Simple Data Element: It's a single piece of data which cannot be reduced in smaller pieces of data. Each simple data element has a type (Alphanumeric, Alpha or Numeric Lenght) and can be Fixed or Variable Lenght and Mandatory or Conditional. In the sample, you can find a simple data element on BGM segment level as 1001:

BGM+380+342459+9'

Composite Data Element: It's a group of related simple elements; the simple elements, are separated using the simple element separator which is ':'. In the sample, you can find a Composite Data Element on UNH segment level as S009 which is the result of four Simple Data Elements (0065, 0052, 0054, 0051):

UNH+00000000000117+INVOIC:D:97B:UN'

Segment: It's a mixture of simple and composite elements. Each segment has a name and can contain three separator characters: ':', '+', '''. We have already discussed about ':'; the apostrophe (') indicates the end of a segment; The '+' separates data fields, which can be both simple or composite elements. Here below, segment NAD (Name and Address) from our INVOIC sample:

NAD+BY+792820524::16++CUMMINS MID-RANGE ENGINE PLANT

Segment Group: Segments can be grouped together to form a block of related data; here below, segment group nr.2, where you can figure out the buyer and the seller of the transaction:

NAD+BY+792820524::16++CUMMINS MID-RANGE ENGINE PLANT'
NAD+SE+005435656::16++GENERAL WIDGET COMPANY'

Message: An EDI transmission can have multiple messages; in our INVOIC sample, this basically means that you could find several block of data between segments UNH / UNT;

Functional Group: There can be multiple messages in one transmission, however all the messages should be of the same type (i.e. INVOIC) unless Functional Groups are used; Functional Groups are not commonly used;

Interchage: It's the complete EDI document.

In the next post, we will discuss again about our INVOIC sample.

EDIFACT message format

Before approaching any UN/EDIFACT message, it's necessary to have a look at the basic EDIFACT message structure.

Message contains a hierarchical structure of data, from the (bottom) Simple Data Element to the full Interchange, which can contain multiple messages:

Interchange (Highest Level)
|
Functional Groups
|
Message
|
Segment Groups
|
Segment
|
Composite Element
|
Simple Data Element (Lowest Level)

In the next post we will try to locate, in a real UN/EDIFACT message sample, each mentionned item.

UN/EDIFACT standard

It's the international EDI standard developed under the United Nations.

The maintenance and development of UN/EDIFACT standard, is done through the United Nations Centre for Trade Facilitation and Electronic Business (UN/CEFACT).

The main goal of the UN/CEFACT, is to contribute to the growth of global commerce, by developing some e-business standards that can:

• cross all international boundaries;
• help lower transaction costs;
• simplify data flow;
• reduce bureaucracy.

What EDI is

Electronic Data Interchange (EDI) can be formally defined as 'The transfer of structured data, by agreed message standards, from one computer system to another without human intervention'.

There are four major sets of EDI standards:

• The UN-recommended UN/EDIFACT is the only international standard and is predominant outside of North America;
• The US standard ANSI ASC X12 (X12) is predominant in North America;
• The TRADACOMS standard developed by the ANA (Article Numbering Association) is predominant in the UK retail industry;
• The ODETTE standard used within the European automotive industry.

Based on the standard, there are specific rules to build a document: some info can be mandatory and some not.

The aim of this blog is to discuss about the most used UN/EDIFACT messages in the transport industry.