MOVINS — EDIFACT Stowage Instruction Message (D.02B)
The MOVINS message conveys container loading and discharge instructions sent by a carrier to a port terminal: which containers to load, discharge or re-stow on which vessel, at which position and under which constraints. This page summarises the segment structure as published by UN/CEFACT for directory D.02B.
Purpose
The MOVINS message conveys container loading and discharge instructions sent by a carrier to a port terminal: which containers to load, discharge or re-stow on which vessel, at which position and under which constraints.
This page focuses on the structure published by UN/CEFACT for directory D.02B. The segments listed, their status (M / C), position and repetition factor are extracted from the official file movins_c.htm hosted on service.unece.org.
Segment structure
The MOVINS D.02B message has 45 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 | M | 1 |
0040 | SG1 | Group (×9) | C | ×9 |
0050 | RFF | Reference | M | 1 |
0060 | DTM | Date/time/period | C | ×9 |
0070 | SG2 | Group (×9) | C | ×9 |
0080 | NAD | Name and address | M | 1 |
0090 | SG3 | Group (×9) | C | ×9 |
0100 | CTA | Contact information | M | 1 |
0110 | COM | Communication contact | C | ×9 |
0120 | SG4 | Group (×3) | M | ×3 |
0130 | TDT | Transport information | M | 1 |
0140 | LOC | Place/location identification | M | 1 |
0150 | DTM | Date/time/period | M | ×99 |
0160 | RFF | Reference | C | 1 |
0170 | FTX | Free text | C | 1 |
0180 | SG5 | Group (×9999) | M | ×9999 |
0190 | HAN | Handling instructions | M | 1 |
0200 | SG6 | Group (×9999) | M | ×9999 |
0210 | LOC | Place/location identification | M | 1 |
0220 | RFF | Reference | M | ×99 |
0230 | FTX | Free text | C | ×9 |
0240 | MEA | Measurements | C | ×9 |
0250 | DIM | Dimensions | C | ×9 |
0260 | LOC | Place/location identification | C | ×9 |
0270 | NAD | Name and address | M | ×99 |
0280 | SG7 | Group (×1) | C | 1 |
0290 | TMP | Temperature | M | 1 |
0300 | RNG | Range details | C | 1 |
0310 | SG8 | Group (×99) | C | ×99 |
0320 | EQD | Equipment details | M | 1 |
0330 | EQN | Number of units | C | 1 |
0340 | SG9 | Group (×99) | C | ×99 |
0350 | EQA | Attached equipment | M | 1 |
0360 | EQN | Number of units | C | 1 |
0370 | SG10 | Group (×9999) | C | ×9999 |
0380 | GID | Goods item details | M | 1 |
0390 | GDS | Nature of cargo | C | 1 |
0400 | SG11 | Group (×999) | C | ×999 |
0410 | RFF | Reference | M | 1 |
0420 | SG12 | Group (×99) | M | ×99 |
0430 | DGS | Dangerous goods | M | 1 |
0440 | FTX | Free text | C | 1 |
0450 | 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.02B for the MOVINS 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
CTAin the header section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.COMin the header section (status C, repeat ×9) — not present at the top of the corresponding D.96A section.
Status changes (M ↔ C)
NAD(header): status C in D.96A → M in D.02B.
Max-repeat changes
NAD(header): repeat ×3 in D.96A → ×1 in D.02B.
Structural example
Minimal example of an MOVINS D.02B message with mandatory segments only. The goal is to show the exact version declared in UNH (MOVINS:D:02B:UN) — not to replicate a full business case (see the MOVINS D.96A page for an annotated example).
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL002001'
UNH+1+MOVINS:D:02B:UN'
BGM+244+MOVINS-2026-0188+9'
DTM+137:202605141430:203'
TDT+20+MSC1234W+1++MSC::ZZZ+++9301234:103:::MSC OSCAR'
LOC+11+FRLEH::6'
LOC+13+NLRTM::6'
EQD+CN+MSCU1234567+45G1+++5'
HAN+L'
LOC+147+0010186::ZZZ'
UNT+9+1'
UNZ+1+CTRL002001'Common errors
- Misaligned UNH tokens — The
UNH+...+MOVINS:D:02B: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.02B, 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: MOVINS D.96A, MOVINS D.01B, MOVINS D.10A, MOVINS D.16B, MOVINS D.21B, MOVINS D.24A, MOVINS D.97A, MOVINS D.99B, MOVINS D.00B, MOVINS D.05A, MOVINS D.08A, MOVINS D.13B, MOVINS D.18B, MOVINS D.20B.