IFTMBP — EDIFACT Booking Provisional Message (D.21B)

The IFTMBP message is the provisional booking request for a multimodal transport service, sent by a principal, shipper or forwarder to a carrier: it describes the intended goods, the pick-up and delivery points, the requested time windows and any special constraints. It prepares the firm booking carried by IFTMBF and confirmed by IFTMBC. This page summarises the segment structure as published by UN/CEFACT for directory D.21B.

Purpose

The IFTMBP message is the provisional booking request for a multimodal transport service, sent by a principal, shipper or forwarder to a carrier: it describes the intended goods, the pick-up and delivery points, the requested time windows and any special constraints. It prepares the firm booking carried by IFTMBF and confirmed by IFTMBC.

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

Segment structure

The IFTMBP D.21B message has 124 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.21B for the IFTMBP 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

• SCC in the header section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.

Max-repeat changes

• TMP (header): repeat ×1 in D.96A → ×9 in D.21B.
• RNG (header): repeat ×1 in D.96A → ×9 in D.21B.

Structural example

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

UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL021001'
UNH+1+IFTMBP:D:21B:UN'
BGM+270+IFTMBP-2026-BP-0211+9'
DTM+137:20260514:102'
DTM+200:20260518:102'
LOC+9+FRLEH::6'
LOC+11+NLRTM::6'
RFF+CN:CMR-9981'
NAD+CZ+5410000000123::9'
NAD+CN+5410000000456::9'
NAD+CA+5410000000456::9'
TDT+20++1++MSC::ZZZ'
GID+1+1:CT'
MEA+AAE+G+KGM:24500'
UNT+13+1'
UNZ+1+CTRL021001'

Common errors

• Misaligned UNH tokens — The UNH+...+IFTMBP:D:21B: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.21B, 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: IFTMBP D.96A, IFTMBP D.10A, IFTMBP D.16B, IFTMBP D.24A.

X12 functional equivalent: X12 300.

← All EDIFACT versions