DELJIT — EDIFACT Delivery Just-In-Time Message (D.16B)

The DELJIT message is the very short-term firm call-off sent by a buyer — typically an automotive OEM or Tier 1 supplier — to a just-in-time supplier: it carries quantities, time windows and delivery locations sequenced over a few hours or days. It directly triggers picking and shipping on the supplier side in a JIT/JIS context. This page summarises the segment structure as published by UN/CEFACT for directory D.16B.

Purpose

The DELJIT message is the very short-term firm call-off sent by a buyer — typically an automotive OEM or Tier 1 supplier — to a just-in-time supplier: it carries quantities, time windows and delivery locations sequenced over a few hours or days. It directly triggers picking and shipping on the supplier side in a JIT/JIS context.

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

Segment structure

The DELJIT D.16B message has 14 header entries, 45 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

Summary

No segment in this section.

Changes vs D.96A

Top-level differences between D.96A and D.16B for the DELJIT 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

• TMD in the detail section (status C, repeat ×1) — not present at the top of the corresponding D.96A section.
• PRI in the detail section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.
• CUX in the detail section (status C, repeat ×1) — not present at the top of the corresponding D.96A section.

Status changes (M ↔ C)

• TDT (detail): status C in D.96A → M in D.16B.

Max-repeat changes

• IMD (detail): repeat ×10 in D.96A → ×99 in D.16B.
• TDT (detail): repeat ×5 in D.96A → ×1 in D.16B.

Structural example

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

UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL016001'
UNH+1+DELJIT:D:16B:UN'
BGM+251+DELJIT-2026-05-13-A+9'
DTM+137:20260514:102'
NAD+BY+5410000000123::9'
NAD+SU+5410000000456::9'
SEQ++1'
DTM+2:202605200800:203'
LIN+1++3520000001234:EN'
QTY+1:120'
SEQ++2'
DTM+2:202605201200:203'
LIN+2++3520000001234:EN'
QTY+1:120'
UNT+14+1'
UNZ+1+CTRL016001'

Common errors

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

X12 functional equivalent: X12 862.

← All EDIFACT versions