DELFOR Delivery Forecast Delivery Schedule Message

Transcription

1 DELFOR Delivery Forecast Delivery Schedule Message Document : EDI-Guideline_DELFOR_V2.2.docx Date : 12 July 2016 Version : 2.3 Author : Rainer Jungton

2 Table of Contents. 1 INTRODUCTION SEGMENT/SEGMENT-GROUP OVERVIEW GENERATED BY LN PLANTS DELFOR D.97A GENERATED BY JDE PLANTS DELFOR D.97A GENERATED BY XPERT PLANTS DELFOR D.96A Message structure SEGMENT DETAILS SEGMENT: UNH MESSAGE HEADER SEGMENT: BGM BEGINNING OF MESSAGE SEGMENT: DTM DATE/TIME/PERIOD GROUP: NAD SEGMENT GROUP 2: NAME AND ADDRESS Segment: NAD and Address GROUP: GIS SEGMENT GROUP 6: GENERAL INDICATOR Segment: GIS General Indicator GROUP: NAD SEGMENT GROUP 7: NAME AND ADDRESS Segment: NAD and Address GROUP: LIN SEGMENT GROUP 12: LINE ITEM Segment: LIN Line Item Segment: IMD Item Description Segment: LOC Place/Location Identification GROUP: RFF SEGMENT GROUP 13: REFERENCE Segment: RFF Reference Segment: DTM Date/Time/Period GROUP: QTY SEGMENT GROUP 15: QUANTITY Segment: QTY Quantity Segment: DTM Date/Time/Period GROUP: SCC SEGMENT GROUP 17: SCHEDULING CONDITIONS Segment: SCC Scheduling Conditions GROUP: QTY SEGMENT GROUP 18: QUANTITY Segment: QTY Quantity Segment: DTM Date/Time/Period SEGMENT: UNS SECTION CONTROL SEGMENT: UNT MESSAGE TRAILER EXAMPLE MESSAGE (LN PLANT) EXAMPLE MESSAGE (JDE PLANT) EXAMPLE MESSAGE (XPERT PLANT) CHANGE LOG Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 2 of 35

3 1 Introduction This version of the DELFOR is not upward compatible with versions prior to D96B. DELFOR is a message which is sent from a party who is planning the use or consumption of products to a party who has to plan for the supply of the products. The message gives the requirements regarding details for short term delivery and/or medium to long scheduling for products. The scheduling can be used to authorize manufacturing and or the provision of materials. This is based on the terms and conditions defined in a purchase order or contract. Because of Bosal is using different IT systems, there are different DELFOR standards used: There are: LN plants JDE plants Xpert plants Please check below the variances. Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 3 of 35

4 2 Segment/Segment-Group Overview 2.1 Generated by LN plants DELFOR D.97A Pos. No. Seg. ID Req. Des. Max. Use Group Repeat Note and comments 0010 UNH Message Header M BGM Beginning of Message M DTM Date/Time/Period M Segment Group 2: NAD C NAD and Address M Segment Group 6: GIS-SG7-SG12 C GIS General Indicator M Segment Group 7: NAD NAD and Address M Segment Group 12: LIN-IMD-LOC- SG13-SG15-SG17 C LIN Line Item M IMD Item Description C LOC Place/Location Identification C Segment Group 13: RFF-DTM C RFF Reference M DTM Date/Time/Period C Segment Group 15: QTY-DTM C QTY Quantity M DTM Date/Time/Period C Segment Group 17: SCC-SG18 C SCC Scheduling Conditions M Segment Group 18: QTY-DTM C QTY Quantity M DTM Date/Time/Period C UNT Final segment of message M 1 M = Mandatory C = Conditional N = Not used Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 4 of 35

5 2.2 Generated by JDE plants DELFOR D.97A Pos. No. Seg. ID Req. Des. Max. Use Group Repeat Note and comments 0010 UNH Message Header M BGM Beginning of Message M DTM Date/Time/Period M Segment Group 2: NAD C NAD and Address M Segment Group 6: GIS-SG7-SG12 C GIS General Indicator M Segment Group 7: NAD M NAD and Address M Segment Group 12: LIN-IMD-LOC- SG13-SG15-SG17 C LIN Line Item M IMD Item Description C LOC Place/Location Identification C Segment Group 13: RFF-DTM C RFF Reference M DTM Date/Time/Period C Segment Group 15: QTY-DTM C QTY Quantity M DTM Date/Time/Period C Segment Group 17: SCC-SG18 C SCC Scheduling Conditions M Segment Group 18: QTY-DTM C QTY Quantity M DTM Date/Time/Period C UNT Final segment of message M 1 M = Mandatory C = Conditional N = Not used Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 5 of 35

6 2.3 Generated by Xpert plants DELFOR D.96A Pos. No. Seg. ID Req. Des. Max. Use 0000 UNB Interchange Header M UNH Message Header M BGM Beginning of Message M DTM Date/Time/Period M 0070 Segment Group 2: NAD-LOC-SG3 C 0080 NAD and Address M Segment Group 3: CTA-COM C 0110 CTA Contact information C 0130 UNS Section control M 0140 Segment Group 4: NAD-LOC-FTX-SG5-SG6-SG7-SG NAD and Address M Segment group 8: C LIN-PIA-IMD-MEA-ALI-GIN-GIR-LOC- DTM-FTX-SG9-SG10-SG11-SG12-SG LIN Line Item M 0290 PIA Additional product id 0300 IMD Item Description C 0350 LOC Place/Location Identification C 0410 Segment Group 10: C RFF-DTM 0420 RFF Reference M 0430 DTM Date/Time/Period C 0470 Segment group 12: C QTY-SCC-DTM-SG QTY Quantity M 0490 SCC Scheduling conditions M 0500 DTM Date/Time/Period M 1220 UNS Section Control C 1250 UNT Message Trailer M 1 Group Repeat Note and comments M = Mandatory C = Conditional N = Not used Remark: The content for D96A is used in the same way as for D97A. Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 6 of 35

7 2.3.1 Message structure UNH Message header 1 (M) BGM Beginning of message 1 (M) DTM Date/time/period 10 (M) Segment Group 1 10 (C) RFF Reference 1 (M) DTM Date/time/period 1 (C) Segment Group 2 20 (C) NAD and address 1 (M) LOC Place/location identification 10 (C) Segment Group 3 5 (C) CTA Contact information 1 (M) COM Communication contact 5 (C) UNS Section control 1 (M) Segment Group (C) NAD and address 1 (M) LOC Place/location identification 10 (C) FTX Free text 5 (C) Segment Group 5 10 (C) DOC Document/message details 1 (M) DTM Date/time/period 10 (C) Segment Group 6 5 (C) CTA Contact information 1 (M) COM Communication contact 5 (C) Segment Group 7 10 (C) TDT Details of transport 1 (M) DTM Date/time/period 5 (C) Segment Group (C) LIN Line item 1 (M) PIA Additional product id 10 (C) IMD Item description 10 (C) MEA Measurements 5 (C) ALI Additional information 5 (C) GIN Goods identity number 100 (C) GIR Related identification numbers 100 (C) LOC Place/location identification 100 (C) DTM Date/time/period 5 (C) FTX Free text 5 (C) Segment Group 9 5 (C) CTA Contact information 1 (M) COM Communication contact 5 (C) Segment Group (C) RFF Reference 1 (M) DTM Date/time/period 1 (C) Segment Group (C) TDT Details of transport 1 (M) DTM Date/time/period 5 (C) Segment Group (C) QTY Quantity 1 (M) SCC Scheduling conditions 1 (C) DTM Date/time/period 2 (C) Segment Group (C) RFF Reference 1 (M) DTM Date/time/period 1 (C) Segment Group (C) PAC Package 1 (M) MEA Measurements 10 (C) QTY Quantity 5 (C) DTM Date/time/period 5 (C) Segment Group (C) PCI Package identification 1 (M) GIN Goods identity number 10 (C) Segment Group (C) QVR Quantity variances 1 (M) DTM Date/time/period 5 (C) Segment Group (C) RFF Reference 1 (M) DTM Date/time/period 1 (C) The segment details (below/next page) is referring to D97A!!! Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 7 of 35

8 3 Segment details 3.1 Segment: UNH Message Header Position 0010 Group Level 0 Usage Mandatory Max Use 1 Purpose Dependency Notes: Semantic Notes: 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 S009: Data element 0065 DELFOR 0052 D A 0051 UN Data Component M 0062 MESSAGE REFERENCE NUMBER Unique message reference assigned by the sender. M S009 MESSAGE IDENTIFIER Identification of the type, version etc. of the message being interchanged. M 0065 Message type identifier Code identifying a type of message and assigned by its controlling agency. DELFOR Delivery schedule message A code to identify the delivery schedule message. M 0052 Message type version number Version number of a message type. D Draft version/un/edifact Directory Message approved and issued as a draft message (Valid for directories published after March 1993 and prior to March 1997). Message approved as a standard message (Valid for directories published after March 1997). M 0054 Message type release number Release number within the current message type version number (0052). 97A Release 1997 A Message approved and issued in the first 1997 release of the UNTDID (United Nations Trade Data Interchange Directory). 96A Release 1996 A M 0051 Controlling agency Code identifying the agency controlling the specification, maintenance and publication of the message type. UN UN/ECE/TRADE/WP.4 United Nations Economic UN Economic Commission for Europe (UN/ECE), Committee on the development of trade (TRADE), Working Party on facilitation of international trade procedures (WP.4). Attributes M an..14 M M an..6 M an..3 M an..3 M an..2 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 8 of 35

9 3.2 Segment: BGM Beginning of Message Position 0020 Group Level 0 Usage Mandatory Max Use 1 Purpose A segment for unique identification of the Delivery schedule message by means of its name and its number and its function (original, replacement, change). Data element Component C002 C106 DOCUMENT/MESSAGE NAME Identification of a type of document/message by code or name. Code preferred 1001 Document/message name, coded Document/message identifier expressed in code. 241 = Delivery schedule Usage of DELFOR-message. DOCUMENT/MESSAGE IDENTIFICATION Identification of a document/message by its number and eventually its version or revision Document/message number Reference number assigned to the document/message by the issuer. MESSAGE FUNCTION, CODED Code indicating the function of the message 5 = Replace Message replacing a previous message. Attributes C C an..3 C C an..35 C an..3 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 9 of 35

10 3.3 Segment: DTM Date/Time/Period Position 0030 Group Level 1 Usage Mandatory Max Use 10 Purpose Dependency Notes: Semantic Notes: 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. Data element Component M C507 DATE/TIME/PERIOD Date and/or time, or period relevant to the specified date/time/period type. M 2005 Date/time/period qualifier Code giving specific meaning to a date, time or period. 137 Document/message date/time (2006) Date/time when a document/message is issued.this may include authentication 2380 Date/time/period The value of a date, a date and time, a time or of a period in a specified representation Date/time/period format qualifier Specification of the representation of a date, a date and time or of a period. 203 CCYYMMDDHHMM Calendar date including time with minutes: C=Century; Y=Year; M=Month; D=Day; H=Hour; M=Minutes. Attributes M M an..3 C an..35 C an..3 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 10 of 35

11 3.4 Group: NAD Segment Group 2: and Address Position 0080 Group Level 1 Usage Conditional (Optional) Max Use 99 Purpose A group of segments identifying parties by their names, addresses, locations, references and contacts relevant to the whole delivery schedule. Pos. Segment ID Req NAD and Address Max use Desired M 1 Group (repeat): Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 11 of 35

12 3.4.1 Segment: NAD and Address Position 0090 (Trigger Segment) Group Segment Group 2 ( and Address) Conditional (Optional) Level 1 Usage Mandatory Max Use 1 Purpose A segment for identifying names and addresses and their functions relevant for the whole Delivery schedule. The principal parties for the Delivery schedule message shall be identified. The identification of the recipient of the goods must be given in the NAD segment in the detail section. It is recommended that where possible only the coded form of the party ID should be specified. Data element Component 3035 PARTY QUALIFIER. Code giving specific meaning to a party. Attributes M an..3 BY SE SU Buyer (3002) Party to which merchandise is sold. Seller (3346) Party selling merchandise to a buyer. Supplier (3280) Party which manufactures or otherwise has possession of goods, and consigns or makes them available in trade. C082 PARTY IDENTIFICATION DETAILS Identification of a transaction party by code Party id. Identification Code identifying a party involved in a transaction Code list qualifier Identification of a code list. Refer to D.97A Data Dictionary for acceptable code values Code list responsible agency, coded Code identifying the agency responsible for a code list. Refer to D.97A Data Dictionary for acceptable code values 92 Assigned by buyer or buyer's agent C M an 35 Not used C an..3 C080 PARTY NAME Identification of a transaction party by name, one to five lines. Party name may be formatted 3036 Party name of a party involved in a transaction. C059 STREET Street address and/or PO Box number in a structured address: one to three lines Street and number/p.o. box Street and number in plain language, or Post Office Box No CITY NAME of a city for addressing purposes COUNTRY SUB-ENTITY IDENTIFICATION Identification of the name of sub-entities (state, province) defined by appropriate governmental agencies. C M an..35 C M an..35 C an..35 C an..9 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 12 of 35

13 Data element Component 3251 POSTCODE IDENTIFICATION Code defining postal zones or addresses COUNTRY, CODED Identification of the name of a country or other geographical entity as specified in ISO Attributes C an..9 C an..3 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 13 of 35

14 3.5 Group: GIS Segment Group 6: General Indicator Position 0190 Group Segment Group 6 (General Indicator) Conditional (Optional) Level 1 Usage Conditional (Optional) Max Use 9999 Purpose A group of segments providing details on delivery points and products and related information using one of both scheduling methods (as described in 1.3 Principles). Position No. Segment ID Req. Max use Group (repeat): Desired 0200 GIS General M 1 Indicator 0210 Segment C 1 Group 7: and Address 0370 Segment Group 12: Line Item C Segment: GIS General Indicator Position Group 0200 (Trigger Segment) Segment Group 6 (General Indicator) Conditional (Optional) Level 1 Usage Conditional (Optional) Max Use 1 Purpose A segment to indicate which method is used by the relevant processing indicator Data element Component C529 PROCESSING INDICATOR Type of process indication Processing indicator, coded Identifies the value to be attributed to indicators required by the processing system. 37 Complete information Processing of information to note that complete data details (not just changes) are transmitted. Attributes M M an..3 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 14 of 35

15 3.6 Group: NAD Segment Group 7: and Address Position 0210 Group Segment Group 6 (General Indicator) Conditional (Optional) Level 2 Usage Conditional (Optional) Max Use 1 Purpose A group of segments needed to identify a delivery point and its attached information when the delivery point method is used. Position No. Segment ID Req NAD and Address Max use Desired M 1 Group (repeat): Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 15 of 35

16 3.6.1 Segment: NAD and Address Position 0220 (Trigger Segment) Group Segment Group 7 ( and Address) Conditional (Optional) Level 2 Usage Mandatory Max Use 1 Purpose A segment for identifying the consignee. Group Data/ Component Attributes Example PARTY QUALIFIER Code giving specific meaning to a party. M an..3 ST ST Ship to Identification of the party to where goods will be or have been shipped. 020 C082 PARTY IDENTIFICATION DETAILS Identification of a transaction party by code Party id. Identification Code identifying a party involved in a transaction Code list qualifier Identification of a code list. Refer to D.97A Data Dictionary for acceptable code values Code list responsible agency, coded Code identifying the agency responsible for a code list. Refer to D.97A Data Dictionary for acceptable code values. 030 C058 NAME AND ADDRESS Unstructured name and address: one to five lines and address line Free form name and address description. 040 C080 PARTY NAME Identification of a transaction party by name, one to five lines. Party name may be formatted Party name of a party involved in a transaction. 050 C059 STREET Street address and/or PO Box number in a structured address: one to three lines Street and number/p.o. box Street and number in plain language, or Post Office Box No CITY NAME of a city (a town, a village) for addressing purposes COUNTRY SUB-ENTITY IDENTIFICATION Identification of the name of sub-entities (state, province) defined by appropriate governmental agencies POSTCODE IDENTIFICATION Code defining postal zones or addresses COUNTRY, CODED Identification of the name of a country or other geographical entity as specified in ISO Example: NAD+ST ::92+BOSAL Addr#1:BOSAL Addr#2++Street RU C M an N an..3 C an C M an..35 BOSAL:BELGIUM C M an..35 Czech Warehouse C M an..35 Dellestraat 20 C an..35 C an C an C an..3 RU Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 16 of 35

17 3.7 Group: LIN Segment Group 12: Line Item Position 0370 Group Segment Group 6 (General Indicator) Conditional (Optional) Level 2 Usage Conditional (Optional) Max Use 9999 Purpose A group of segments providing details of the individual line items for both methods. Position No. Segment ID Req. Desired Max use 0380 LIN Line Item M IMD Item C 10 Discription 0450 LOC Place/Location C 999 Identification 0480 Segment C 10 Group 13: Reference 0540 Segment C 10 Group 15: Quantity 0600 Segment C 999 Group 17: Scheduling Conditions Group (repeat): Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 17 of 35

18 3.7.1 Segment: LIN Line Item Position 0380 (Trigger Segment) Group Segment Group 12 (Line Item) Conditional (Optional) Level 2 Usage Mandatory Max Use 1 Purpose A segment identifying the details of the product or service to be delivered, e.g. product identification. All other segments in the detail section following the LIN segment refer to the line item. Data element Component 1082 LINE ITEM NUMBER Serial number designating each separate item within a series of articles. Attributes C an..6 C212 ITEM NUMBER IDENTIFICATION Goods identification for a specified source Item number A number allocated to a group or item Item number type, coded Identification of the type of item number. C C an..35 C an..3 IN Buyer's item number Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 18 of 35

19 3.7.2 Segment: IMD Item Description Position 0400 Group Segment Group 12 (Line Item) Conditional (Optional) Level 3 Usage Conditional (Optional) Max Use 10 Purpose A segment for describing the product or the service to be delivered. This segment should be used for products that cannot be identified by a product code or article number. Dependency Notes Semantic Notes Data element Component Attributes C273 ITEM DESCRIPTION C Description of an item. X 7009 Item description identification C an Item description C an..35 Plain language description of articles or products Item description Plain language description of articles or products. C an..35 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 19 of 35

20 3.7.3 Segment: LOC Place/Location Identification Position 0450 Group Segment Group 12 (Line Item) Conditional (Optional) Level 3 Usage Conditional (Optional) Max Use 9999 Purpose A segment identifying a specific location to which products, as specified in the LIN-Segment group, should be placed after delivery. This function should only be used with the delivery point driven method. Data element Component 3227 PLACE/LOCATION QUALIFIER Code identifying the function of a location. 11 Place/port of discharge Attributes C an..3 C517 ( ) Seaport, airport, freight terminal, rail station or other place at which the goods (cargo) are unloaded from the means of transport having been used for their carriage. LOCATION IDENTIFICATION Identification of a location by code or name Place/location identification Identification of the name of place/location, other than 3164 City name. C C an..25 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 20 of 35

21 3.8 Group: RFF Segment Group 13: Reference Position 0480 Group Segment Group 12 (Line Item) Conditional (Optional) Level 3 Usage Conditional (Optional) Max Use 10 Purpose A group of segments giving references related to the line item and where necessary, their dates. Position No. Segment ID Req. Desired Max use M 0490 RFF Reference M DTM Date/Time/Period C 1 Group (repeat): Segment: RFF Reference Position 0490 (Trigger Segment) Group Segment Group 13 (Reference) Conditional (Optional) Level 3 Usage Conditional (Optional) Max Use 1 Purpose A segment for identifying references to the line item, e.g. a contract and its appropriate line item, original message number, previous message number if different per line item. For JDE plants the dispatch advice number is not used! Data element Component C506 REFERENCE Identification of a reference. Attributes M 1153 REFERENCE QUALIFIER Code giving specific meaning to a reference segment or a reference number. M an..3 AAK ON Dispatch advice number Reference number assigned by issuing party to a dispatch advice. Order number (purchase) [1022] Reference number assigned by the buyer to an order Reference number Identification number the nature and function of which can be qualified by an entry in data element 1153 Reference qualifier. C an..35 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 21 of 35

22 3.8.2 Segment: DTM Date/Time/Period Position 0500 Group Segment Group 13 (Reference) Conditional (Optional) Level 4 Usage Conditional (Optional) Max Use 1 Purpose Date/time/period of the reference. Dependency Notes: Semantic Notes: Data element Component M C507 DATE/TIME/PERIOD Date and/or time, or period relevant to the specified date/time/period type. M 2005 Date/time/period qualifier Code giving specific meaning to a date, time or period. Attributes M M an Reference date/time Date/time on which the reference was issued Date/time/period The value of a date, a date and time, a time or of a period in a specified representation Date/time/period format qualifier Specification of the representation of a date, a date and time or of a period. C an..35 C an CCYYMMDD Calendar date: C = Century Y = Year M = Month D = Day Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 22 of 35

23 3.9 Group: QTY Segment Group 15: Quantity Position 0540 Group Segment Group 12 (Line Item) Conditional (Optional) Level 3 Usage Conditional (Optional) Max Use 10 Purpose A group of segments specifying product quantities and associated dates not related to schedules and where relevant, references. Position No. Segment ID Req. Desired Max use 0550 QTY Quantity M DTM Date/Time/Period C 2 Group (repeat): Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 23 of 35

24 3.9.1 Segment: QTY Quantity Position 0550 (Trigger Segment) Group Segment Group 15 (Quantity) Conditional (Optional) Level 3 Usage Mandatory Max Use 1 Purpose Dependency Notes: Semantic Notes: A segment to specify pertinent quantities not related to schedule(s) e.g. cumulative quantity, last quantity considered. Data element Component Attributes M C186 QUANTITY DETAILS Quantity information in a transaction, qualified when relevant. M M 6063 Quantity qualifier Code giving specific meaning to a quantity. M an Cumulative quantity received Cumulative quantity of all deliveries of this article received by the buyer. 79 Previous cumulative quantity Cumulative quantity prior the actual order. 83 Backorder quantity 194 Received and accepted Quantity which has been received and accepted at a given location M 6060 Quantity Numeric value of a quantity Measure unit qualifier Indication of the unit of measurement in which weight (mass), capacity, length, area, volume or other quantity is expressed. M n..15 C an..3 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 24 of 35

25 3.9.2 Segment: DTM Date/Time/Period Position 0560 Group Segment Group 17 (Scheduling Conditions) Conditional (Optional) Level 3 Usage Mandatory Max Use 1 Purpose A segment specifying the status of the schedule. Optionally a delivery pattern can be established, e.g. firm or proposed delivery pattern. Position 0560 Group Segment Group 15 (Quantity) Conditional (Optional) Level 4 Usage Conditional (Optional) Max Use 2 Purpose A segment indicating the date/time/period details relating to the quantity. Dependency Notes: Semantic Notes: Data element Component M C507 DATE/TIME/PERIOD Date and/or time, or period relevant to the specified date/time/period type. M 2005 Date/time/period qualifier Code giving specific meaning to a date, time or period. Attributes M M an Cumulative quantity start date First Date for accumulation of delivery quantities Date/time/period The value of a date, a date and time, a time or of a period in a specified representation Date/time/period format qualifier Specification of the representation of a date, a date and time or of a period. C an..35 C an CCYYMMDD Calendar date: C = Century Y = Year M= Month D = Day Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 25 of 35

26 3.10 Group: SCC Segment Group 17: Scheduling Conditions Position 0600 Group Segment Group 12 (Line Item) Conditional (Optional) Level 3 Usage Conditional (Optional) Max Use 999 Purpose A group of segments specifying the schedule information for the product identified in the LIN segment. With the delivery point driven method this segment group provides the schedule for the identified delivery point and product. With the product driven method this segment group can be used to summarize all schedules provided with the subsequent delivery point information given in segment group 22. Position No. Segment ID Req. Desired Max use 0610 SCC Scheduling M 1 Conditions 0620 Segment Group 18: Quantity Group (repeat): C 999 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 26 of 35

27 Segment: SCC Scheduling Conditions Position 0610 (Trigger Segment) Group Segment Group 17 (Scheduling Conditions) Conditional (Optional) Level 3 Usage Mandatory Max Use 1 Purpose A segment specifying the status of the schedule. Optionally a delivery pattern can be established, e.g. firm or proposed delivery pattern. Data element Component 4017 DELIVERY PLAN STATUS INDICATOR, CODED Code indicating the level of commitment of schedule information. Attributes M an..3 C329 1 Firm Indicates that the scheduling information is a firm commitment. 10 Immediate Indicates that the scheduling information is for immediate execution (backlog) 4 Planning/forecast Self-explanatory PATTERN DESCRIPTION Shipment, delivery or production interval pattern and timing Frequency, coded Code specifying interval grouping of the delivery, production, etc. of the schedule. C C an..3 W Y D Weekly Code defining a forecast for weekly intervals. Daily Code defining a forecast for yearly intervals. Discrete Flexible frequency according to planning process. Example: QTY+113:1000:PCE' Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 27 of 35

28 3.11 Group: QTY Segment Group 18: Quantity Position 0620 Group Segment Group 17 (Scheduling Conditions) Conditional (Optional) Level 4 Usage Conditional (Optional) Max Use 999 Purpose A group of segments specifying product quantities and associated dates. Position No. Segment ID Req. Desired Max use 0630 QTY Quantity M DTM Date/Time/Period C 2 Group (repeat): Segment: QTY Quantity Position 0630 (Trigger Segment) Group Segment Group 18 (Quantity) Conditional (Optional) Level 4 Usage Mandatory Max Use 1 Purpose A segment to specify scheduled quantities which may be related to schedule(s) and, or pattern established in the following DTM segment, e.g. delivery quantity for a specified date. Data element Component C186 QUANTITY DETAILS Quantity information in a transaction, qualified when relevant. Attributes M 6063 Quantity qualifier Code giving specific meaning to a quantity. M an Quantity to be delivered The quantity to be delivered Quantity Numeric value of a quantity Measure unit qualifier Indication of the unit of measurement in which weight (mass), capacity, length, area, volume or other quantity is expressed. M n 15 C an 3 PCE Piece Example: QTY+113:1000:PCE' Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 28 of 35

29 Segment: DTM Date/Time/Period Position 0640 Group Segment Group 18 (Quantity) Conditional (Optional) Level 5 Usage Conditional (Optional) Max Use 2 Purpose A segment indicating date/time/period details relating to the given quantity. Data Component M C507 DATE/TIME/PERIOD Date and/or time, or period relevant to the specified date/time/period type. M 2005 Date/time/period qualifier Code giving specific meaning to a date, time or period. 2 Delivery date/time, requested Date on which buyer requests goods to be delivered Date/time/period The value of a date, a date and time, a time or of a period in a specified 2379 Date/time/period format qualifier Specification of the representation of a date, a date and time or of a period. 102 CCYYMMDD Calendar date: C = Century ; Y = Year ; M = Month ; D = Day. Attributes M M an..3 C an..35 C an..3 Example: DTM+2: :102' Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 29 of 35

30 3.12 Segment: UNS Section Control Position Group Level 0 Usage Conditional Max Use Purpose A character identifying the next section in a message. Data Component M 0081 D Header/detail section separation To qualify the segment UNS, when separating the header from the detail section of a message. Attributes M an 1 S Detail/summary section separation To qualify the segment UNS, when separating the detail from the summary section of a message. Example: UNS+D' UNS+S' Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 30 of 35

31 3.13 Segment: UNT Message Trailer Position 1030 Group Level 0 Usage Mandatory Max Use 1 Purpose A service segment ending a message, giving the total number of segments in the message and the control reference number of the message Data Component M 0074 NUMBER OF SEGMENTS IN A MESSAGE Control count of number of segments in a message. M 0062 MESSAGE REFERENCE NUMBER Unique message reference assigned by the sender. Attributes M n..6 M n..14 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 31 of 35

32 4 Example message (LN Plant) UNB+UNOC:1+O0013BOSALSFID+O0013TESTSUPPLIER : UNH+1+DELFOR:D:97A:UN BGM DTM+137: :203 NAD+SU ::92++Test Supplier GmbH NAD+BY+BOSAL::92 GIS+37 NAD+ST ::92+:+Raw Material++Nizhny Novgorod+48++RU LIN :IN IMD+++:::Tube B LOC RFF+ON: QTY+70:0:PCE DTM+51: :102 SCC+1++D QTY+113:1002:PCE DTM+2: :102 SCC+1++D QTY+113:25:PCE DTM+2: :102 SCC+1++D QTY+113:25:PCE DTM+2: :102 UNT+23+1 UNZ+1+4 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 32 of 35

33 5 Example message (JDE Plant) UNB+UNOC:1+OSENDER:OD+ORECEIVER:OD : ' UNH+1+DELFOR:D:97A:UN' BGM ' DTM+137: :203' NAD+SU+50944::92' NAD+BY+00045::92++BOSAL CZ, spol. s r.o.' GIS+37' NAD+ST+BCZB::92++BOSAL CZ, spol. s r.o.++brandys nad Labem Brandys nad Labem+++CZ ' LIN :IN' IMD+++:::KLAPPEELEKTRISCH-4H H' LOC+11+BCZB' RFF+ON:460' SCC+1++D' QTY+113:120:PCE' DTM+2: :102' SCC+10++D' QTY+113:27:PCE' DTM+2: :102' SCC+4++D' QTY+113:0:PCE' DTM+2: :102' SCC+4++D' QTY+113:0:PCE' DTM+2: :102' UNT+24+1' UNZ+1+13' Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 33 of 35

34 6 Example message (Xpert Plant) UNB+UNOA:2+O A04Cxxxx+ORECEIVERID : ' UNH+1+DELFOR:D:96A:UN:A09041' BGM ' DTM+137: :203' DTM+158: :102' DTM+159: :102' NAD+SE+20088:: HU' NAD+BY+::92' CTA+PD+:Mr. Contact' UNS+D' NAD+CN+O ORIS::92' LIN :IN' IMD+++:::Test item' LOC+159+RE' RFF+ON: ' RFF+AIF:10' DTM+171: :102' RFF+AAN:11' DTM+171: :102' QTY+70:400:PCE' QTY+78:400:PCE' QTY+12:100:PCE' RFF+AAK: ' DTM+171: :102' QTY+48:100:PCE' DTM+171: :102' QTY+113:0:PCE' SCC+1++D' DTM+2: :102' QTY+113:26:PCE' SCC+1++D' DTM+2: :102' QTY+113:55:PCE' SCC+1++D' DTM+2: :102' QTY+113:55:PCE' SCC+1++D' DTM+2: :102' QTY+113:0:PCE' SCC+1++D' DTM+2: :102' QTY+113:55:PCE' SCC+1++D' DTM+2: :102' QTY+113:0:PCE' SCC+1++D' DTM+2: :102' UNS+S' UNT+48+1' UNZ ' Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 34 of 35

35 7 Change log Version Reason Release date Change Page 1.0 Layout Some reformatting of text Several 1.1 Layout 1.2 Change Additional chapter: change log 21 chapter 1.3 Add table Difference between DELFOR messages sent Layout Change chapter from BOSAL plants (LN or JDE) Some reformatting of text/tables Delete not used information for JDE plants 1.5 Add table 31/3/2014 New BOSAL plants (Xpert) added 5 Layout changes 1.6 Layout Some reformatting of text/tables 11 Change 1.7 Change table NAD+ST table examples added 14 several 5 Page margin changed from Standard to All Medium 1.8 Add table UNS (only for Xpert plants) 24 Change Xpert plant segment overview 6 table 1.9 Content 10/11/2015 Changed cover page: DELFOR Delivery Forecast Delivery Schedule Message removed: DELFOR D.97A DELFOR D.96A). Added Generated by Added format: DELFOR D.97A for JDE plants 1 4/5/ Layout 19/05/2016 Different tables standardized Several Changed index Add QTY QTY+83 = Backlog Quantity 22 variance Add SCC SCC+10 = immediate demand Layout 02/06/2016 Some layout changes on the NAD segment 11 02/06/2016 QTY+194 added (last received DN quantity) Content 12/07/2016 Added Example message for Xpert Deleted GIS segment for Xpert plants 2.3 Content 12/07/2016 Changed Example message for Xpert plants Changed message structure for Xpert plants because of different message version/release number (D96A instead of D97A) /7 Last saved : 12 July 2016 EDI-Guideline_DELFOR_V2.3.docx Page 35 of 35