IFTSTA — EDIFACT Multimodal Transport Status Message (D.00B)
The IFTSTA message conveys multimodal-shipment statuses from a carrier or 3PL to the trade parties: key events (departure, arrival, hub, customs), geolocation and exceptions. This page summarises the segment structure as published by UN/CEFACT for directory D.00B.
Purpose
The IFTSTA message conveys multimodal-shipment statuses from a carrier or 3PL to the trade parties: key events (departure, arrival, hub, customs), geolocation and exceptions.
This page focuses on the structure published by UN/CEFACT for directory D.00B. The segments listed, their status (M / C), position and repetition factor are extracted from the official file iftsta_c.htm hosted on service.unece.org.
Segment structure
The IFTSTA D.00B message has 62 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
| Pos. | Tag | Name | S | Rep. |
|---|---|---|---|---|
0010 | UNH | Message header | M | 1 |
0020 | BGM | Beginning of message | M | 1 |
0030 | DTM | Date/time/period | C | ×9 |
0040 | TSR | Transport service requirements | C | 1 |
0050 | SG1 | Group (×9) | C | ×9 |
0060 | NAD | Name and address | M | 1 |
0070 | SG2 | Group (×9) | C | ×9 |
0080 | CTA | Contact information | M | 1 |
0090 | COM | Communication contact | C | ×9 |
0100 | SG3 | Group (×9) | C | ×9 |
0110 | RFF | Reference | M | 1 |
0120 | DTM | Date/time/period | C | 1 |
0130 | LOC | Place/location identification | C | ×9 |
0140 | FTX | Free text | C | ×9 |
0150 | CNT | Control total | C | ×9 |
0160 | SG4 | Group (×99999) | C | ×99999 |
0170 | CNI | Consignment information | M | 1 |
0180 | LOC | Place/location identification | C | ×9 |
0190 | CNT | Control total | C | ×9 |
0200 | SG5 | Group (×99) | M | ×99 |
0210 | STS | Status | M | 1 |
0220 | RFF | Reference | C | ×999 |
0230 | DTM | Date/time/period | C | ×9 |
0240 | DOC | Document/message details | C | 1 |
0250 | FTX | Free text | C | ×9 |
0260 | NAD | Name and address | C | ×9 |
0270 | LOC | Place/location identification | C | 1 |
0280 | PCI | Package identification | C | ×99 |
0290 | SG6 | Group (×99) | C | ×99 |
0300 | TDT | Details of transport | M | 1 |
0310 | DTM | Date/time/period | C | ×9 |
0320 | RFF | Reference | C | ×9 |
0330 | SG7 | Group (×9) | C | ×9 |
0340 | LOC | Place/location identification | M | 1 |
0350 | DTM | Date/time/period | C | ×9 |
0360 | SG8 | Group (×99) | C | ×99 |
0370 | EQD | Equipment details | M | 1 |
0380 | MEA | Measurements | C | ×9 |
0390 | DIM | Dimensions | C | ×9 |
0400 | SEL | Seal number | C | ×9 |
0410 | RFF | Reference | C | ×9 |
0420 | TPL | Transport placement | C | ×9 |
0430 | TMD | Transport movement details | C | 1 |
0440 | SG9 | Group (×99) | C | ×99 |
0450 | EQA | Attached equipment | M | 1 |
0460 | SEL | Seal number | C | ×9 |
0470 | SG10 | Group (×99) | C | ×99 |
0480 | GID | Goods item details | M | 1 |
0490 | HAN | Handling instructions | C | ×9 |
0500 | SGP | Split goods placement | C | ×99 |
0510 | DGS | Dangerous goods | C | ×9 |
0520 | FTX | Free text | C | ×9 |
0530 | SG11 | Group (×99) | C | ×99 |
0540 | MEA | Measurements | M | 1 |
0550 | EQN | Number of units | C | 1 |
0560 | SG12 | Group (×99) | C | ×99 |
0570 | DIM | Dimensions | M | 1 |
0580 | EQN | Number of units | C | 1 |
0590 | SG13 | Group (×99) | C | ×99 |
0600 | PCI | Package identification | M | 1 |
0610 | GIN | Goods identity number | C | ×9 |
0620 | UNT | Message trailer | M | 1 |
Detail
No segment in this section.
Summary
No segment in this section.
Changes vs D.96A
Top-level differences between D.96A and D.00B for the IFTSTA 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
TPLin the header section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.TMDin the header section (status C, repeat ×1) — not present at the top of the corresponding D.96A section.SGPin the header section (status C, repeat ×99) — not present at the top of the corresponding D.96A section.DGSin the header section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.
Structural example
Minimal example of an IFTSTA D.00B message with mandatory segments only. The goal is to show the exact version declared in UNH (IFTSTA:D:00B:UN) — not to replicate a full business case (see the IFTSTA D.96A page for an annotated example).
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL000001'
UNH+1+IFTSTA:D:00B:UN'
BGM+77+STA-2026-1042+9'
DTM+137:202605141430:203'
NAD+CA+5410000000123::9'
CNI+1'
STS+1++1'
RFF+CN:CMR-9981'
DTM+334:202605141000:203'
LOC+175+FRPAR::6'
UNT+10+1'
UNZ+1+CTRL000001'Common errors
- Misaligned UNH tokens — The
UNH+...+IFTSTA:D:00B:UNtoken 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.00B, 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: IFTSTA D.96A, IFTSTA D.01B, IFTSTA D.10A, IFTSTA D.16B, IFTSTA D.21B, IFTSTA D.24A, IFTSTA D.97A, IFTSTA D.99B, IFTSTA D.02B, IFTSTA D.05A, IFTSTA D.08A, IFTSTA D.13B, IFTSTA D.18B, IFTSTA D.20B.
X12 functional equivalent: X12 214.