UN/EDIFACT Message Data Mapping Guide (continued)
The guidelines given below refer to each UN/EDIFACT message used in SARS EDI business communication. The first two portions were given in the previous blog posts. Find below the descriptions of more data elements.
UNH MESSAGE HEADER (Mandatory 1)
Specification of the beginning of each individual message and unique identification of the message. This segment also specifies the message type version and release numbers used in formatting the information and identifies any references common to the parties to the transaction. The segment must always be used in a message and must begin the message. Below follows a description of each data element mentioned above. Please note that not all data elements are required as per the table above.
UNT, MESSAGE TRAILER (Mandatory, 1)
Identifies the end of the message. It specifies the number of segments in the message (including the UNH and UNT segments) and confirms the message reference number identified in the UNH segment. Must be used to end each message.
UNZ, INTERCHANGE TRAILER (Mandatory)
Identifies the end of each transmission/interchange. Must be used to end each transmission/interchange.
UNS, SECTION CONTROL (Conditional)
To separate the header, detail and summary sections of a message. Conditional, but if specified in a message structure, it must be Mandatory.