SAFHAZ — EDIFACT Safety / Hazard Notification Message (D.96A)
The SAFHAZ message carries the safety and hazard information for a substance or chemical product: CAS / UN identification, risk phrases, storage conditions, emergency measures, protective equipment. It is the structured-EDI counterpart of safety data sheets (SDS). This page summarises the segment structure as published by UN/CEFACT for directory D.96A.
Purpose
The SAFHAZ message carries the safety and hazard information for a substance or chemical product: CAS / UN identification, risk phrases, storage conditions, emergency measures, protective equipment. It is the structured-EDI counterpart of safety data sheets (SDS).
This page focuses on the structure published by UN/CEFACT for directory D.96A. The segments listed, their status (M / C), position and repetition factor are extracted from the official file safhaz_s.htm hosted on service.unece.org.
Segment structure
The SAFHAZ D.96A message has 68 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 | RFF | Reference | C | ×10 |
0040 | DTM | Date/time/period | C | ×10 |
0050 | FTX | Free text | C | ×99 |
0060 | SG1 | Group (×10) | C | ×10 |
0070 | NAD | Name and address | M | 1 |
0080 | RFF | Reference | C | ×10 |
0090 | SG2 | Group (×10) | C | ×10 |
0100 | CTA | Contact information | M | 1 |
0110 | COM | Communication contact | C | ×5 |
0120 | SG3 | Group (×1000) | M | ×1000 |
0130 | DOC | Document/message details | M | 1 |
0140 | IMD | Item description | C | ×10 |
0150 | PIA | Additional product id | C | ×10 |
0160 | MEA | Measurements | C | ×10 |
0170 | RCS | Requirements and conditions | C | ×10 |
0180 | RFF | Reference | C | ×10 |
0190 | DTM | Date/time/period | C | ×10 |
0200 | FTX | Free text | C | ×99 |
0210 | SG4 | Group (×10) | C | ×10 |
0220 | NAD | Name and address | M | 1 |
0230 | RFF | Reference | C | ×10 |
0240 | SG5 | Group (×10) | C | ×10 |
0250 | CTA | Contact information | M | 1 |
0260 | COM | Communication contact | C | ×5 |
0270 | SG6 | Group (×20) | C | ×20 |
0280 | SFI | Safety information | M | 1 |
0290 | PIA | Additional product id | C | ×10 |
0300 | EQD | Equipment details | C | ×99 |
0310 | FTX | Free text | C | ×99 |
0320 | SG7 | Group (×10) | C | ×10 |
0330 | NAD | Name and address | M | 1 |
0340 | RFF | Reference | C | ×10 |
0350 | SG8 | Group (×10) | C | ×10 |
0360 | CTA | Contact information | M | 1 |
0370 | COM | Communication contact | C | ×5 |
0380 | SG9 | Group (×10) | C | ×10 |
0390 | HAN | Handling instructions | M | 1 |
0400 | FTX | Free text | C | ×99 |
0410 | SG10 | Group (×10) | C | ×10 |
0420 | IMD | Item description | M | 1 |
0430 | MEA | Measurements | C | ×10 |
0440 | PCD | Percentage details | C | ×10 |
0450 | RFF | Reference | C | ×10 |
0460 | FTX | Free text | C | ×99 |
0470 | SG11 | Group (×10) | C | ×10 |
0480 | DGS | Dangerous goods | M | 1 |
0490 | RFF | Reference | C | ×10 |
0500 | FTX | Free text | C | ×99 |
0510 | SG12 | Group (×10) | C | ×10 |
0520 | PAC | Package | M | 1 |
0530 | PCI | Package identification | C | ×10 |
0540 | SG13 | Group (×999) | C | ×999 |
0550 | CCI | Characteristic/class id | M | 1 |
0560 | IMD | Item description | C | ×10 |
0570 | FTX | Free text | C | ×99 |
0580 | CAV | Characteristic value | C | ×10 |
0590 | SG14 | Group (×10) | C | ×10 |
0600 | RFF | Reference | M | 1 |
0610 | DTM | Date/time/period | C | ×10 |
0620 | SG15 | Group (×10) | C | ×10 |
0630 | MEA | Measurements | M | 1 |
0640 | TEM | Test method | C | ×10 |
0650 | DTM | Date/time/period | C | ×10 |
0660 | RFF | Reference | C | ×10 |
0670 | FTX | Free text | C | ×99 |
0680 | UNT | Message trailer | M | 1 |
Detail
No segment in this section.
Summary
No segment in this section.
Changes vs D.96A
This page documents directory D.96A itself: it serves as the reference for every other version of the message. The synthesis below describes the structural changes that later directories will introduce relative to it.
No top-level differences detected between D.96A and D.96A for this message. Differences are then limited to nested groups and code lists.
Structural example
Minimal example of an SAFHAZ D.96A message with mandatory segments only. The goal is to show the exact version declared in UNH (SAFHAZ:D:96A:UN) — not to replicate a full business case.
UNB+UNOC:3+5410000000123:14+5410000000456:14+260514:1430+CTRL096001'
UNH+1+SAFHAZ:D:96A:UN'
BGM+270+SAFHAZ-2026-SDS-0007+9'
RFF+ACE:CAS-67-64-1'
DTM+137:20260514:102'
FTX+AAI+++UN 1090 Acetone - IMDG class 3 - PG II - flash point -20 C'
UNT+6+1'
UNZ+1+CTRL096001'Common errors
- Misaligned UNH tokens — The
UNH+...+SAFHAZ:D:96A: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.96A, 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: SAFHAZ D.10A, SAFHAZ D.16B, SAFHAZ D.21B, SAFHAZ D.24A.