Try it now Login

Message type

UN/EDIFACT HANMOV

Handling instructions and movement advice. It is published in 60 directory versions of the UN/EDIFACT standard, each defining its own segment structure.

Open the D24A HANMOV specification
Message
HANMOV
Directory versions
60
Latest
D24A

Sending and receiving

Exchange HANMOV with your trading partners

The specification tells you what a valid HANMOV looks like. Sending and receiving one means mapping it to the system that holds the data, agreeing the format with each partner, and handling the messages that come back when something is rejected. XEDI does the mapping, validation and transport.

Browse integrations Connect HANMOV to your ERP, WMS or accounting system Find your trading partner Document requirements by partner Talk to an EDI specialist Scope a HANMOV flow with us

Specifications

HANMOV in every directory version

A trading partner names both the message and the directory, for example D00A HANMOV, because the segments differ between versions. Open the one your partner specified.

60 directory versions

Frequently asked questions

What is the HANMOV message?

Handling instructions and movement advice. It is one of the UN/EDIFACT message types, identified by the six-letter name HANMOV in every directory version that publishes it.

Which directory version of HANMOV do I need?

The one your trading partner specifies. HANMOV is published in 60 directory versions and the segment detail differs between them, so a mapping built for one version is not automatically valid for another.

How do I send a HANMOV message?

Map the data from the system that holds it into the segment structure the agreed directory version defines, then transport it by the route the partner uses, commonly AS2 or SFTP. XEDI handles the mapping, validation and transport, and surfaces the acknowledgements and errors that come back.

Sources and further reading