COHAOR — EDIFACT Container Special Handling Order Message (D.10A)

The COHAOR message is the order for a special handling or specific service to perform on one or more containers, sent by a carrier, forwarder or principal to a terminal or depot: inspection, weighing, repositioning, reefer treatment, sealing. It complements COPRAR and COREOR for everything that is neither a standard load/discharge nor a standard release. This page summarises the segment structure as published by UN/CEFACT for directory D.10A.

Purpose

The COHAOR message is the order for a special handling or specific service to perform on one or more containers, sent by a carrier, forwarder or principal to a terminal or depot: inspection, weighing, repositioning, reefer treatment, sealing. It complements COPRAR and COREOR for everything that is neither a standard load/discharge nor a standard release.

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

Segment structure

The COHAOR D.10A message has 46 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.

Header

Detail

No segment in this section.

Summary

No segment in this section.

Changes vs D.96A

Top-level differences between D.96A and D.10A for the COHAOR message (segments directly inside header / detail / summary, ignoring nested groups). The comparison is indicative: a given tag may have evolved inside nested groups without showing up in this synthesis.

Segments added vs D.96A

• COM in the header section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.
• MEA in the header section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.
• PCD in the header section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.
• DGS in the header section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.
• TMP in the header section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.
• RNG in the header section (status C, repeat ×1) — not present at the top of the corresponding D.96A section.

Status changes (M ↔ C)

• CTA (header): status C in D.96A → M in D.10A.
• CNT (header): status M in D.96A → C in D.10A.

Max-repeat changes

• CTA (header): repeat ×9 in D.96A → ×1 in D.10A.

Structural example

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

UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL010001'
UNH+1+COHAOR:D:10A:UN'
BGM+266+COHAOR-2026-HAN-0033+9'
DTM+137:202605141430:203'
TDT+20+MSC1234W+1++MSC::ZZZ+++9301234:103:::MSC OSCAR'
LOC+11+FRLEH::6'
NAD+CA+5410000000123::9'
EQD+CN+MSCU1234567+45G1+++5'
HAN+L:::Reefer pre-trip inspection'
UNT+9+1'
UNZ+1+CTRL010001'

Common errors

• Misaligned UNH tokens — The UNH+...+COHAOR:D:10A: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.10A, 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.

Related messages

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

← All EDIFACT versions