ORDERS — EDIFACT Purchase Order (D.97A)

The ORDERS message conveys a buyer’s intent to purchase goods or services from a seller under terms agreed upstream. It supports spot orders, call-offs against blanket contracts, and replenishment flows alike. This page summarises the segment structure as published by UN/CEFACT for directory D.97A.

Purpose

The ORDERS message conveys a buyer’s intent to purchase goods or services from a seller under terms agreed upstream. It supports spot orders, call-offs against blanket contracts, and replenishment flows alike.

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

Segment structure

The ORDERS D.97A message has 100 header entries, 125 detail entries and 8 summary entries (segments and groups combined). Groups are shown in bold and their members are indented by actual nesting depth.

Header

Detail

Summary

Changes vs D.96A

Top-level differences between D.96A and D.97A for the ORDERS 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

• GIR 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.
• DGS in the detail section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.

Max-repeat changes

• IMD (header): repeat ×1 in D.96A → ×999 in D.97A.
• MEA (detail): repeat ×5 in D.96A → ×99 in D.97A.
• QTY (detail): repeat ×10 in D.96A → ×99 in D.97A.
• DOC (detail): repeat ×5 in D.96A → ×99 in D.97A.

Structural example

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

UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL097001'
UNH+1+ORDERS:D:97A:UN'
BGM+220+ORDER789+9'
DTM+137:20260514:102'
DTM+2:20260520:102'
NAD+BY+5410000000123::9'
NAD+SU+5410000000456::9'
LIN+1++3520000001234:EN'
QTY+21:10'
PRI+AAA:42.00'
UNS+S'
CNT+2:1'
UNT+11+1'
UNZ+1+CTRL097001'

Common errors

• Misaligned UNH tokens — The UNH+...+ORDERS:D:97A: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.97A, 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: ORDERS D.96A, ORDERS D.01B, ORDERS D.10A, ORDERS D.16B, ORDERS D.21B, ORDERS D.24A, ORDERS D.99B, ORDERS D.00B, ORDERS D.02B, ORDERS D.05A, ORDERS D.08A, ORDERS D.13B, ORDERS D.18B, ORDERS D.20B.

X12 functional equivalent: X12 850.

← All EDIFACT versions