DELFOR Delivery Schedule Message - Eurofer

More documents

Recommendations

Info

UN/EDIFACT D97.A DELFOR - Delivery schedule message 4.4 General description of the message - subset of Eurofer 4.4.1 Message definition and segment clarification This section is provided to give clarification and further explanation to the usage of the segments within the message defined by Eurofer. The message consists of two sections, a heading section and a detail section. The heading section is representing the corresponding references and the parties involved. Some detail information which applies or relates to all the line items of the detail section can also be given in the heading section. This section should be read in conjunction with the segment usage and the branching diagram (chapter 4.3.) which indicates the required (R) and optional (O) segments and segment groups. The following guidelines and principles apply to the whole message of Eurofer and are intended to facilitate the understanding and the implementation of the message. All the specified data/times (segment DTM) should be in the format 'CCYYMMDD'/'hhmm' unless all parties involved in the transaction agree that there is a functional requirement for an alternative format. Periods should be specified as whole numbers representing the required period as indicated in the format qualifier (weeks, month, etc) Where a choice of code or text is given, only the code element should be used if possible. Optional (conditional) data that are not required in the message should not be included. Care must be taken that the segment qualifier in dependent segments do not conflict with the segment qualifier of the trigger segment of the group. 4.4.2 Message description - Heading section Information to be or which can be provided in the heading section of the message. Segment UNH, Message Header A service segment starting and uniquely identifying a message. The message type code for the Delivery schedule message is DELFOR. Note: Delivery schedule messages conforming to this document must contain the following data in segment UNH, composite data element S009 : Data elements ; - 0065 DELFOR - 0052 D - 0054 97A - 0051 UN Page 31
UN/EDIFACT D97.A DELFOR - Delivery schedule message Segment BGM, Beginning of message A segment for unique identification of the Delivery schedule message by means of its type (e.g. firm, forecast, delivery schedule), its number and its function (original, replacement). Segment DTM, Date/time/period The DTM segment shall be specified at least once to identify the Delivery schedule message date. This segment can be included to indicate the beginning and the end date of the schedule. Segment FTX, Free text A segment with free text in coded or clear form to give further clarification when required. In computer to computer exchanges such text will normally require the receiver to process this segment manually. Eurofer recommends not to use this segment. Segment group 1: RFF-DTM A group of segments giving references and where necessary, their dates relating to the whole message, e.g. contract number. Segment RFF, Reference A segment for giving references to the whole Delivery schedule message, e.g. contract, original message number, previous message number. Segment DTM, Date/time/period Date or time, or date and time of the reference. Segment group 2: NAD-SG3-SG4 A group of segments identifying parties by their names, addresses, references and contacts relevant to the whole Delivery schedule message. Eurofer has decided not to use the segment group 3 for giving references related to the party specified in the NAD segment. Page 32
Page 1 and 2: DELFOR Delivery Schedule Message Su
Page 3 and 4: UN/EDIFACT D97.A DELFOR - Delivery
Page 31: UN/EDIFACT D97.A DELFOR - Delivery
Page 83 and 84:
UN/EDIFACT D97.A DELFOR - Delivery
Page 85 and 86:
UN/EDIFACT D97.A DELFOR - Delivery
show all

DELFOR Delivery Schedule Message - Eurofer

Create successful ePaper yourself

Delete template?

Save as template?