ESG Appendix H: EDIFACT Message Structure
ESG User Guide - Table of Contents
Required message structure (EDIFACT)
S/MIME SMTP E-mail Header
Example: UNB+UNOB:1+016968919:01+FDA:ZZ+060310:0127+37' ----> Header
SGML document----------------------------------------------------------> SGML Document
'UNZ+1+37' --------------------------------------------------------------> Trailer
EDIFACT UNB Header Information
| Description | Code | Comments |
|---|---|---|
|
Identification of the start of the UNB header |
UNB |
The code for the start of the UNB header should be UNB in upper case letters |
|
Version of the standard of the UNB header |
UNOB:1 |
The current version code should be UNOB in upper case letters |
|
Interchange sender identification code and sender code qualifier |
xxxxxxx:01 (for AS2 submissions this should match the routing ID) |
xxxxxxx should be the number assigned to your company by Dun and Bradstreet Information Services. (For industry sending to the FDA, the sender code qualifier is 01.) |
|
Interchange recipient |
FDA:zz |
xxxx should be the code for the receiving center (CDER, CBER, CDRH, CVM, CFSAN) |
|
Date and time of preparation |
yymmdd:hhmm |
For now, a two-digit designation should be used for the year |
|
Interchange control reference |
Up to 14 alphanumeric characters |
You should assign a unique reference number for each interchange. Otherwise the system will not recognize the transmission as new |
UNZ Trailer Information
| Description | Code | Comments |
|---|---|---|
|
Identification of the start of the trailer |
UNZ |
The code for the start of the trailer is UNZ in upper case letters |
|
Interchange control count |
Up to 6 numerical characters |
Counts either the number of messages or the number of functional groups within the interchange. Usually, this is 1 |
|
Interchange control reference |
Up to 14 alphanumeric characters |
This should be the same as the interchange control reference in the UNB header |
EDI headers and trailers are made up of a series of data elements separated by plus (+) signs. A colon should separate segments of the individual data elements. An apostrophe should be used to terminate the header, body of the message, and the trailer.