Try it now Login

Message type

UN/EDIFACT SAFHAZ

Safety hazardous goods message. It is published in 58 directory versions of the UN/EDIFACT standard, each defining its own segment structure.

Open the D24A SAFHAZ specification
Message
SAFHAZ
Directory versions
58
Latest
D24A

Sending and receiving

Exchange SAFHAZ with your trading partners

The specification tells you what a valid SAFHAZ 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 SAFHAZ to your ERP, WMS or accounting system Find your trading partner Document requirements by partner Talk to an EDI specialist Scope a SAFHAZ flow with us

Specifications

SAFHAZ in every directory version

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

58 directory versions

Frequently asked questions

What is the SAFHAZ message?

Safety hazardous goods message. It is one of the UN/EDIFACT message types, identified by the six-letter name SAFHAZ in every directory version that publishes it.

Which directory version of SAFHAZ do I need?

The one your trading partner specifies. SAFHAZ is published in 58 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 SAFHAZ 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