ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.
HANMOV D.00B

HANMOV — EDIFACT Cargo / Goods Handling and Movement Message (D.00B)

The HANMOV message describes the cargo handling and movement operations within a logistics site — terminal, warehouse, port or airport hub: lifting orders, internal moves, inter-terminal transfers. It bridges WMS / TOS systems with their operational resources. This page summarises the segment structure as published by UN/CEFACT for directory D.00B.

Purpose

The HANMOV message describes the cargo handling and movement operations within a logistics site — terminal, warehouse, port or airport hub: lifting orders, internal moves, inter-terminal transfers. It bridges WMS / TOS systems with their operational resources.

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 hanmov_c.htm hosted on service.unece.org.

Segment structure

The HANMOV D.00B message has 92 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.

Pos.TagNameSRep.
0010UNHMessage headerM1
0020BGMBeginning of messageM1
0030DTMDate/time/periodC×9
0040HANHandling instructionsC×9
0050FTXFree textC×9
0060CNTControl totalC×9
0070CUXCurrenciesC×9
0080  SG1Group (×9)C×9
0090  TCCTransport charge/rate calculationsM1
0100  LOCPlace/location identificationC×9
0110  FTXFree textC×9
0120  CUXCurrenciesC×9
0130    SG2Group (×9)C×9
0140    RFFReferenceM1
0150    DTMDate/time/periodC×9
0160      SG3Group (×9)C×9
0170      NADName and addressM1
0180      LOCPlace/location identificationC×9
0190      DOCDocument/message detailsC×9
0200        SG4Group (×9)C×9
0210        RFFReferenceM1
0220        DTMDate/time/periodC×9
0230          SG5Group (×9)C×9
0240          CTAContact informationM1
0250          COMCommunication contactC×9
0260            SG6Group (×9)C×9
0270            TDTDetails of transportM1
0280            DTMDate/time/periodC×9
0290            LOCPlace/location identificationC×9
0300            RFFReferenceC×9
0310              SG7Group (×9)C×9
0320              TODTerms of delivery or transportM1
0330              LOCPlace/location identificationC×9
0340                SG8Group (×99)C×99
0350                LINLine itemM1
0360                PIAAdditional product idC×9
0370                IMDItem descriptionC×99
0380                HANHandling instructionsC×9
0390                TCCTransport charge/rate calculationsC×9
0400                  SG9Group (×9)C×9
0410                  NADName and addressM1
0420                    SG10Group (×1)C1
0430                    CTAContact informationM1
0440                    COMCommunication contactC×9
0450                    MEAMeasurementsC×9
0460                    QTYQuantityC×9
0470                    GINGoods identity numberC×99
0480                    GIRRelated identification numbersC×99
0490                    DTMDate/time/periodC×9
0500                    FTXFree textC×9
0510                      SG11Group (×9)C×9
0520                      RFFReferenceM1
0530                      DTMDate/time/periodC1
0540                      LOCPlace/location identificationC×9
0550                        SG12Group (×99)C×99
0560                        PACPackageM1
0570                        MEAMeasurementsC×9
0580                        QTYQuantityC×9
0590                          SG13Group (×9)C×9
0600                          PCIPackage identificationM1
0610                          GINGoods identity numberC×9
0620                            SG14Group (×99)C×99
0630                            GIDGoods item detailsM1
0640                            HANHandling instructionsC1
0650                            CSTCustoms status of goodsC1
0660                            TMPTemperatureC1
0670                            RNGRange detailsC1
0680                            LOCPlace/location identificationC×9
0690                            MOAMonetary amountC×9
0700                            PIAAdditional product idC×9
0710                            FTXFree textC×9
0720                            NADName and addressC×9
0730                            MEAMeasurementsC×9
0740                            DIMDimensionsC×9
0750                            RFFReferenceC×9
0760                            PCIPackage identificationC×9
0770                              SG15Group (×9)C×9
0780                              DOCDocument/message detailsM1
0790                              DTMDate/time/periodC×9
0800                              SGPSplit goods placementC×9
0810                              TCCTransport charge/rate calculationsC×9
0820                                SG16Group (×9)C×9
0830                                DGSDangerous goodsM1
0840                                FTXFree textC×9
0850                                MEAMeasurementsC×9
0860                                  SG17Group (×9)C×9
0870                                  EQDEquipment detailsM1
0880                                  EQNNumber of unitsC1
0890                                  SELSeal numberC1
0900                                  EQAAttached equipmentC×99
0910                                  RFFReferenceC×9
0920UNTMessage trailerM1

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 HANMOV 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

  • TOD in the header section (status M, repeat ×1) — not present at the top of the corresponding D.96A section.

Structural example

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

edifact hanmov-d00b-example.edi
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL000001'
UNH+1+HANMOV:D:00B:UN'
BGM+266+HANMOV-2026-1004+9'
DTM+137:202605141430:203'
HAN+L:::Lifting and inland transfer'
FTX+AAI+++Move 24 containers from yard Block A to rail siding R2'
LOC+5+FRLEH::6'
LOC+11+FRTGV::6'
UNT+8+1'
UNZ+1+CTRL000001'

Common errors

  • Misaligned UNH tokens — The UNH+...+HANMOV:D:00B: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.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.

Other versions of this message available on ediverse.io: HANMOV D.96A, HANMOV D.01B, HANMOV D.10A, HANMOV D.16B, HANMOV D.21B, HANMOV D.24A, HANMOV D.97A, HANMOV D.99B, HANMOV D.02B, HANMOV D.05A, HANMOV D.08A, HANMOV D.13B, HANMOV D.18B, HANMOV D.20B.

← All EDIFACT versions