ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.
COPRAR D.96A

COPRAR — EDIFACT Container Discharge / Loading Order Message (D.96A)

The COPRAR message is the order from a carrier to a port terminal to load or discharge a precise list of containers onto or from a seagoing vessel: it identifies the vessel, the voyage, the containers concerned and the booking references. The related report is CODECO (or CASRES in some flows). This page summarises the segment structure as published by UN/CEFACT for directory D.96A.

Purpose

The COPRAR message is the order from a carrier to a port terminal to load or discharge a precise list of containers onto or from a seagoing vessel: it identifies the vessel, the voyage, the containers concerned and the booking references. The related report is CODECO (or CASRES in some flows).

This page focuses on the structure published by UN/CEFACT for directory D.96A. The segments listed, their status (M / C), position and repetition factor are extracted from the official file coprar_s.htm hosted on service.unece.org.

Segment structure

The COPRAR D.96A message has 36 header entries, 0 detail entries and 0 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.

Pos.TagNameSRep.
0010UNHMessage headerM1
0020BGMBeginning of messageM1
0030FTXFree textC×9
0040RFFReferenceM×9
0050  SG1Group (×1)M1
0060  TDTDetails of transportM1
0070  RFFReferenceC×9
0080  LOCPlace/location identificationC×9
0090  DTMDate/time/periodC×9
0100  FTXFree textC×9
0110    SG2Group (×9)M×9
0120    NADName and addressM1
0130    CTAContact informationC×9
0140      SG3Group (×9999)M×9999
0150      EQDEquipment detailsM1
0160      RFFReferenceC×9
0170      EQNNumber of unitsC1
0180      TMDTransport movement detailsC×9
0190      DTMDate/time/periodC×9
0200      LOCPlace/location identificationC×9
0210      MEAMeasurementsC×9
0220      DIMDimensionsC×9
0230      TMPTemperatureC×9
0240      RNGRange detailsC×9
0250      SELSeal numberC×9
0260      FTXFree textC×9
0270      DGSDangerous goodsC×9
0280      EQAAttached equipmentC×9
0290        SG4Group (×1)C1
0300        TDTDetails of transportM1
0310        RFFReferenceC×9
0320        LOCPlace/location identificationC×9
0330        DTMDate/time/periodC×9
0340        NADName and addressC1
0350        CNTControl totalM1
0360UNTMessage trailerM1

Detail

No segment in this section.

Summary

No segment in this section.

Changes vs D.96A

This page documents directory D.96A itself: it serves as the reference for every other version of the message. The synthesis below describes the structural changes that later directories will introduce relative to it.

No top-level differences detected between D.96A and D.96A for this message. Differences are then limited to nested groups and code lists.

Structural example

Minimal example of an COPRAR D.96A message with mandatory segments only. The goal is to show the exact version declared in UNH (COPRAR:D:96A:UN) — not to replicate a full business case.

edifact coprar-d96a-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL096001'
UNH+1+COPRAR:D:96A:UN'
BGM+750+COPRAR-2026-MSC1234+9'
DTM+137:202605141430:203'
TDT+20+MSC1234W+1++MSC::ZZZ+++9301234:103:::MSC OSCAR'
LOC+11+FRLEH::6'
LOC+13+NLRTM::6'
NAD+CA+5410000000123::9'
EQD+CN+MSCU1234567+45G1+++5'
RFF+BN:BKG-2026-MSC-7811'
UNT+10+1'
UNZ+1+CTRL096001'

Common errors

  • Misaligned UNH tokens — The UNH+...+COPRAR:D:96A:UN token must reflect exactly the directory in use — a mismatch between the UNH release and the release agreed with the partner is rejected by every strict validator.
  • Wrong UNT segment count — The value after UNT+ must include UNH and UNT themselves. By far the most common sender-side error, regardless of the directory in use.
  • Stale code lists — Between D.96A and D.96A, several code lists received new qualifiers (DTM status, RFF qualifier, NAD codes…). Reusing an older directory’s code tables triggers warnings or even rejections depending on the partner’s strict-conformance mode.

Other versions of this message available on ediverse.io: COPRAR D.10A, COPRAR D.16B, COPRAR D.21B, COPRAR D.24A.

← All EDIFACT versions