DELFOR Delivery Schedule Message - Eurofer
DELFOR Delivery Schedule Message - Eurofer
DELFOR Delivery Schedule Message - Eurofer
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
UN/EDIFACT D97.A <strong>DELFOR</strong> - <strong>Delivery</strong> schedule message<br />
4.4 General description of the message - subset of <strong>Eurofer</strong><br />
4.4.1 <strong>Message</strong> definition and segment clarification<br />
This section is provided to give clarification and further explanation to the usage of the<br />
segments within the message defined by <strong>Eurofer</strong>. The message consists of two sections, a<br />
heading section and a detail section.<br />
The heading section is representing the corresponding references and the parties involved.<br />
Some detail information which applies or relates to all the line items of the detail section can<br />
also be given in the heading section.<br />
This section should be read in conjunction with the segment usage and the branching<br />
diagram (chapter 4.3.) which indicates the required (R) and optional (O) segments and<br />
segment groups.<br />
The following guidelines and principles apply to the whole message of <strong>Eurofer</strong> and are<br />
intended to facilitate the understanding and the implementation of the message.<br />
All the specified data/times (segment DTM) should be in the format 'CCYYMMDD'/'hhmm'<br />
unless all parties involved in the transaction agree that there is a functional requirement for<br />
an alternative format.<br />
Periods should be specified as whole numbers representing the required period as indicated<br />
in the format qualifier (weeks, month, etc)<br />
Where a choice of code or text is given, only the code element should be used if possible.<br />
Optional (conditional) data that are not required in the message should not be included.<br />
Care must be taken that the segment qualifier in dependent segments do not conflict with the<br />
segment qualifier of the trigger segment of the group.<br />
4.4.2 <strong>Message</strong> description - Heading section<br />
Information to be or which can be provided in the heading section of the message.<br />
Segment UNH, <strong>Message</strong> Header<br />
A service segment starting and uniquely identifying a message. The message type code for<br />
the <strong>Delivery</strong> schedule message is <strong>DELFOR</strong>.<br />
Note: <strong>Delivery</strong> schedule messages conforming to this document must contain the following<br />
data in segment UNH, composite data element S009 :<br />
Data elements ; - 0065 <strong>DELFOR</strong><br />
- 0052 D<br />
- 0054 97A<br />
- 0051 UN<br />
Page 31