Transaction 856. Benteler Automotive Electronic Data Interchange Specifications. Version 2.2 November 30, 2009

Transcription

1 Benteler Automotive Electronic Data Interchange Specifications Transaction 856 Version 2.2 November 30, 2009 NAO_LO-023 Benteler Automotive 1 November 30, Version 4010 Version 2.2

2 Changes from Version Update the list of active Benteler Plants in the N1 segment 2. Removed reference to BOL number being unique within a one year period in the BSN segment. 3. Removed Contact and VAN Information NAO_LO-023 Benteler Automotive 2 November 30, Version 4010 Version 2.2

3 BENTELER AUTOMOTIVE 856 Ship Notice/Manifest Functional Group ID=SH Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information. The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment. Heading: Detail: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments 010 ST Transaction Set Header M BSN Beginning Segment for Ship Notice M DTM Date/Time Reference M 1 Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - HL (SHIPMENT LEVEL) HL Hierarchical Level M TD1 Carrier Details (Quantity and Weight) M TD5 Carrier Details (Routing Sequence/Transit M 1 Time) 130 TD3 Carrier Details (Equipment) M 1 LOOP ID - N N1 Name M 1 Summary: LOOP ID - HL (ITEM LEVEL) HL Hierarchical Level M LIN Item Identification M SN1 Item Detail (Shipment) M 1 Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments 010 CTT Transaction Totals M SE Transaction Set Trailer M 1 NAO_LO-023 Benteler Automotive 3 November 30, Version 4010 Version 2.2

4 Segment: ISA Interchange Control Header Position: 005 Loop: Level: Heading Purpose: To start and identify an interchange of zero or more functional groups and interchangerelated control segments Semantic Notes: Example: ISA~00~ ~00~ ~01~ ~01~ ~021105~0832~U~ 00400~ ~0~P~< ISA01 I01 Authorization Information Qualifier M ID 2/2 Use "00" ISA02 I02 Authorization Information M AN 10/10 Use Ten Spaces ISA03 I03 Security Information Qualifier M ID 2/2 Use "00" ISA04 I04 Security Information M AN 10/10 Use Ten Spaces ISA05 I05 Interchange ID Qualifier M ID 2/2 Use "01" or other applicable codes ISA06 I06 Interchange Sender ID M AN 15/15 DUNS Number. Left Justify, Space Fill ISA07 I05 Interchange ID Qualifier M ID 2/2 Use "01" or other applicable codes ISA08 I07 Interchange Receiver ID M AN 15/15 DUNS Number. Left Justify, Space Fill ISA09 I08 Interchange Date M DT 6/6 Date of Creation ISA10 I09 Interchange Time M TM 4/4 Time Of Creation ISA11 I10 Interchange Control Standards Identifier M ID 1/1 Use "U" for U.S. ISA12 I11 Interchange Control Version Number M ID 5/5 Use "00401" ISA13 I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender ISA14 I13 Acknowledgment Requested M ID 1/1 Use "0" for no Ack. Req., Use "1" for Ack. Req ISA15 I14 Usage Indicator M ID 1/1 Use "T" For Test or "P" For Production Refer to Data Element Dictionary for acceptable code values. ISA16 I15 Component Element Separator M AN 1/1 Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator NAO_LO-023 Benteler Automotive 4 November 30, Version 4010 Version 2.2

5 Segment: GS Functional Group Header Position: 007 Loop: Level: Heading Purpose: To indicate the beginning of a functional group and to provide control information Semantic Notes: 1 GS04 is the group date. 2 GS05 is the group time. 3 The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. Example: GS~SH~ ~ ~ ~0832~159~X~ GS Functional Identifier Code M ID 2/2 Use "SH" for Advanced Ship Notice GS Application Sender's Code M AN 2/15 Use Duns Number GS Application Receiver's Code M AN 2/15 Use Duns Number GS Date M DT 8/8 Creation Date GS Time M TM 4/8 Creation Time GS06 28 Group Control Number M N0 1/9 Start with 1 and increment by 1 for each subsequent GS Segment GS Responsible Agency Code M ID 1/2 Use "X" GS Version / Release / Industry Identifier Code M AN 6/6 Use "004010" NAO_LO-023 Benteler Automotive 5 November 30, Version 4010 Version 2.2

6 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Purpose: To indicate the start of a transaction set and to assign a control number Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Example: ST~856~0001 ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set Refer to Data Element Dictionary for acceptable code values. ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set NAO_LO-023 Benteler Automotive 6 November 30, Version 4010 Version 2.2

7 Segment: BSN Beginning Segment for Ship Notice Position: 020 Loop: Level: Heading Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set Semantic Notes: Example: BSN~00~ ~ ~1245 BSN Transaction Set Purpose Code M ID 2/2 Use "00" (Original) BSN Shipment Identification M AN 1/9 A unique control number assigned by the original shipper to identify a specific shipment. Must not repeat. BSN Date M DT 8/8 ASN Creation Date. Format: CCYYMMDD BSN Time M TM 4/4 ASN Creation Time. Format: HHMM NAO_LO-023 Benteler Automotive 7 November 30, Version 4010 Version 2.2

8 Segment: DTM Date/Time Reference Position: 040 Loop: Level: Heading Purpose: To specify pertinent dates and times Semantic Notes: Example: DTM~011~ ~1246 DTM Date/Time Qualifier M ID 3/3 Use '011' (Shipped Date) DTM Date M DT 8/8 Shipment Date. Format: CCYYMMDD DTM Time M TM 4/4 Shipment Time. Format: HHMM NAO_LO-023 Benteler Automotive 8 November 30, Version 4010 Version 2.2

9 Segment: HL Hierarchical Level Position: 010 Loop: HL Mandatory Level: Shipment Purpose: Semantic Notes: Example: To identify dependencies among and the content of hierarchically related groups of data segments HL~1~~S HL Hierarchical ID Number M AN 1/12 A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL Hierarchical Level Code M ID 1/1 Use S - Shipment Level NAO_LO-023 Benteler Automotive 9 November 30, Version 4010 Version 2.2

10 Segment: TD1 Carrier Details (Quantity and Weight) Position: 110 Loop: HL Mandatory Level: Shipment Purpose: To specify the transportation details relative to commodity, weight, and quantity Semantic Notes: Example: TD1~~150 TD Lading Quantity M N0 1/7 Number of units (pieces) of the lading commodity NAO_LO-023 Benteler Automotive 10 November 30, Version 4010 Version 2.2

11 Segment: TD5 Carrier Details (Routing Sequence/Transit Time) Position: 120 Loop: HL Mandatory Level: Shipment Purpose: To specify the carrier and sequence of routing and provide transit time information Example: TD5~B~2~VEND~LT TD Routing Sequence Code M ID 1/2 Use "B" (Origin/Delivery Carrier (Any Mode)) TD Identification Code Qualifier M ID 1/2 Use "2" (SCAC Code Qualifier) TD Identification Code M AN 2/80 Code identifying a party or other code TD Transportation Method/Type Code M ID 1/2 Code specifying the method or type of transportation for the shipment Any valid X12 code value except "ZZ" (Mutually Defined) NAO_LO-023 Benteler Automotive 11 November 30, Version 4010 Version 2.2

12 Segment: TD3 Carrier Details (Equipment) Position: 130 Loop: HL Mandatory Level: Shipment Purpose: To specify transportation details relating to the equipment used by the carrier Semantic Notes: Example: TD3~TL~~ TD Equipment Description Code M ID 2/2 Code identifying type of equipment used for shipment Any valid X12 code value except "ZZ" (Mutually Defined) TD Equipment Number M AN 1/10 Trailer Number` NAO_LO-023 Benteler Automotive 12 November 30, Version 4010 Version 2.2

13 Segment: N1 Name Position: 220 Loop: N1 Mandatory Level: Shipment Purpose: To identify the ship to party Semantic Notes: Comments: 1 Ship To N1 Segment MUST be the first N1 segment in the 856. Example: N1~ST~Windsor Plant~98~0470 N Entity Identifier Code M ID 2/3 Use "ST" (Ship To) N Name M AN 1/60 Name of Benteler Plant to which material is to be shipped N Identification Code Qualifier M ID 2/2 Use "98" (Benteler Plant Code) N Identification Code M AN 4/4 The Benteler Plant Code Defined as Follows Corporate Hall Street Plant Hagen Drive Plant Kalamazoo Plant Goshen Plant Opelika Plant Brampton Plant Hermosillo Puebla 0587 Saltillio Comment: Should return the Identification code that was sent in 830/862 N1 Segment 1st Occurrence of te N1 Loop NAO_LO-023 Benteler Automotive 13 November 30, Version 4010 Version 2.2

14 Segment: N1 Name Position: 220 Loop: N1 Mandatory Level: Shipment Purpose: To identify supplier/ship from party. Semantic Notes: Example: N1~SU~~16~DUNS Number N Entity Identifier Code M ID 2/3 Use "SU" (Supplier) N Identification Code Qualifier M ID 2/2 Use "16" (DUNS Number) N Identification Code M AN 2/17 The supplier DUNS number. Comment: Should return the Identification code that was sent in the 830/862 N1 Segment 2nd Occurrence of the N1 Loop NAO_LO-023 Benteler Automotive 14 November 30, Version 4010 Version 2.2

15 Segment: HL Hierarchical Level Position: 010 Loop: HL Mandatory Level: Item Purpose: Semantic Notes: Example: To identify dependencies among and the content of hierarchically related groups of data segments HL~2~1~I HL Hierarchical ID Number M AN 1/12 A unique number assigned by the sender to identify a particular data segment in a hierarchical structure HL Hierarchical Parent ID Number M AN 1/12 Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to HL Hierarchical Level Code M ID 1/2 Use "I" (Item Level) NAO_LO-023 Benteler Automotive 15 November 30, Version 4010 Version 2.2

16 Segment: LIN Item Identification Position: 020 Loop: HL Mandatory Level: Item Purpose: To specify basic item identification data Semantic Notes: Example: LIN~~BP~20939~EC~A~PL~00070~PO~ ~RN~12 LIN Product/Service ID Qualifier M ID 2/2 Use "BP" (Buyer's Part Number) LIN Product/Service ID M AN 1/18 Benteler's Material Number LIN Product/Service ID Qualifier M ID 2/2 Use "EC" LIN Product/Service ID M AN 1/2 Engineering Change Level LIN Product/Service ID Qualifier M ID 2/2 Use "PL" (P.O. Line Item Number) LIN Product/Service ID M AN 1/5 Purchase order line number LIN Product/Service ID Qualifier M ID 2/2 Use "PO" (Purchase Order Number) LIN Product/Service ID M AN 1/10 Number Used To Uniquely Identify The Purchasing Document. LIN Product/Service ID Qualifier M ID 2/2 Use "RN" LIN Product/Service ID M AN 1/9 Release Number Of The Purchasing Document. Comment: Should return what was sent in the 830/862 LIN Segment NAO_LO-023 Benteler Automotive 16 November 30, Version 4010 Version 2.2

17 Segment: SN1 Item Detail (Shipment) Position: 030 Loop: HL Mandatory Level: Item Purpose: To specify line-item detail relative to shipment Semantic Notes: Example: SN1~~12000~EA SN Number of Units Shipped M R 1/10 Numeric value of units shipped in manufacturer's shipping units for a line item or transaction set SN Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken This Must Be The Same Unit Of Measure Provided On The Corresponding Releasing Document. Comment: For the SN103, You should return the value that was sent in the 830/862 UIT Segment NAO_LO-023 Benteler Automotive 17 November 30, Version 4010 Version 2.2

18 Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Purpose: To transmit a hash total for a specific element in the transaction set Semantic Notes: Example: CTT~1 CTT Number of Line Items M N0 1/6 Total number of line items in the transaction set. (Total Number Of LIN Segments) NAO_LO-023 Benteler Automotive 18 November 30, Version 4010 Version 2.2

19 Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary Purpose: Semantic Notes: Example: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) SE~14~0001 SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set NAO_LO-023 Benteler Automotive 19 November 30, Version 4010 Version 2.2

20 Segment: GE Functional Group Trailer Position: 030 Loop: Level: Summary Usage: Optional Purpose: To indicate the end of a functional group and to provide control information Semantic Notes: 1 The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06. Example: GE~1~159 GE01 97 Number of Transaction Sets Included M N0 1/6 Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element GE02 28 Group Control Number M N0 1/9 Assigned number originated and maintained by the sender NAO_LO-023 Benteler Automotive 20 November 30, Version 4010 Version 2.2

21 Segment: IEA Interchange Control Trailer Position: 040 Loop: Level: Summary Usage: Optional Purpose: Semantic Notes: Example: To define the end of an interchange of zero or more functional groups and interchangerelated control segments IEA~1~ IEA01 I16 Number of Included Functional Groups M N0 1/5 A count of the number of functional groups included in an interchange IEA02 I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender NAO_LO-023 Benteler Automotive 21 November 30, Version 4010 Version 2.2

22 EXAMPLE 856 ISA~00~ ~00~ ~01~ ~01~ ~021105~0832~U~00400~ ~0~P~<* GS~SH~ ~ ~ ~0832~159~X~004010* ST~856~0001 BSN~00~ ~ ~1245 DTM~011~ ~1246 HL~1~~S TD1~~150 TD5~B~2~VEND~LT TD3~TL~~ N1~ST~Brampton Plant~98~0471 N1~SU~~16~DUNS Number HL~2~1~I LIN~~BP~ ~EC~A~PL~00070~PO~ ~RN~12 SN1~~12000~EA HL~3~1~I LIN~~BP~ ~EC~A~PL~00080~PO~ ~RN~12 SN1~~12000~EA CTT~2 SE~17~0001 GE~1~159 IEA~1~ NAO_LO-023 Benteler Automotive 22 November 30, Version 4010 Version 2.2

23 Benteler Automotive Electronic Data Interchange Specifications Transaction 862 Version 3.2 November 30, 2009 NAO_LO-023 Benteler Automotive 1 30-NOV Version 4010 Version 3.2

24 Changes from Version Updated Bemteler Plant codes in the N1 ST segment 2. Added Notes: to the LIN segment for PD element Changes from Version Added elements 12 and 13 to the LIN segment 2. Updated the example 3. Removed Contact and VAN information 4. Add Benteler Mexico Plant codes Changes from Version Added SHP Loop 2. Added the SHP Segment - Page Added the REF Segment - Page Added the SHP Loop to Page 2 NAO_LO-023 Benteler Automotive 2 30-NOV Version 4010 Version 3.2

25 Benteler Automotive 862 Shipping Schedule Functional Group ID=SS Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Shipping Schedule Transaction Set (862) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a customer to convey precise shipping schedule requirements to a supplier, and is intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will supersede certain shipping and delivery information transmitted in a previous planning schedule transaction, but it does not replace the 830 transaction set. The shipping schedule transaction set shall not be used to authorize labor, materials or other resources. The use of this transaction set will facilitate the practice of Just-In-Time (JIT) manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the issuance of a planning schedule transaction, e.g., daily shipping schedules versus weekly planning schedules. The shipping schedule transaction also provides the ability for a customer location to issue shipping requirements independe of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization. Heading: Detail: Summary: Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments 010 ST Transaction Set Header M BSS Beginning Segment for Shipping M 1 Schedule/Production Sequence LOOP ID - N N1 Name M N3 Address Information O N4 Geographic Location O 1 Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments LOOP ID - LIN LIN Item Identification M UIT Unit Detail M 1 LOOP ID - FST FST Forecast Schedule M 1 LOOP ID - SHP SHP Shipped/Received Information M REF Reference Identification O 5 Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments 010 CTT Transaction Totals M 1 n1 020 SE Transaction Set Trailer M 1 Segment: ISA Interchange Control Header NAO_LO-023 Benteler Automotive 3 30-NOV Version 4010 Version 3.2

26 Position: 005 Loop: Level: Heading Purpose: To start and identify an interchange of zero or more functional groups and interchangerelated control segments Semantic Notes: Example: ISA~00~ ~00~ ~01~ ~01~ ~021105~0832~U~ 00400~ ~0~P~<* ISA01 I01 Authorization Information Qualifier M ID 2/2 Use "00" ISA02 I02 Authorization Information M AN 10/10 Use Ten Spaces ISA03 I03 Security Information Qualifier M ID 2/2 Use "00" ISA04 I04 Security Information M AN 10/10 Use Ten Spaces ISA05 I05 Interchange ID Qualifier M ID 2/2 Use "01" or other applicable codes ISA06 I06 Interchange Sender ID M AN 15/15 DUNS Number. Left Justify, Space Fill ISA07 I05 Interchange ID Qualifier M ID 2/2 Use "01" or other applicable codes ISA08 I07 Interchange Receiver ID M AN 15/15 DUNS Number. Left Justify, Space Fill ISA09 I08 Interchange Date M DT 6/6 Date of Creation ISA10 I09 Interchange Time M TM 4/4 Time Of Creation ISA11 I10 Interchange Control Standards Identifier M ID 1/1 Use "U" for U.S. ISA12 I11 Interchange Control Version Number M ID 5/5 Use "00401" ISA13 I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender ISA14 I13 Acknowledgment Requested M ID 1/1 Use "0" for no Ack. Req., Use "1" for Ack. Req ISA15 I14 Usage Indicator M ID 1/1 Use "T" For Test or "P" For Production Refer to Data Element Dictionary for acceptable code values. ISA16 I15 Component Element Separator M AN 1/1 Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator NAO_LO-023 Benteler Automotive 4 30-NOV Version 4010 Version 3.2

27 Segment: GS Functional Group Header Position: 007 Loop: Level: Heading Purpose: To indicate the beginning of a functional group and to provide control information Semantic Notes: 1 GS04 is the group date. 2 GS05 is the group time. 3 The data interchange control number GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. Example: GS~SS~ ~ ~ ~0832~159~X~004010* GS Functional Identifier Code M ID 2/2 Use "SS" for Shipping Schedule GS Application Sender's Code M AN 2/15 Use Duns Number GS Application Receiver's Code M AN 2/15 Use Duns Number GS Date M DT 8/8 Creation Date GS Time M TM 4/8 Creation Time GS06 28 Group Control Number M N0 1/9 Start with 1 and increment by 1 for each subsequent GS Segment GS Responsible Agency Code M ID 1/2 Use "X" GS Version / Release / Industry Identifier Code M AN 6/6 Use "004010" NAO_LO-023 Benteler Automotive 5 30-NOV Version 4010 Version 3.2

28 Segment: ST Transaction Set Header Position: 010 Loop: Level: Heading Purpose: To indicate the start of a transaction set and to assign a control number Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Comments: ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set Refer to Data Element Dictionary for acceptable code values. ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set NAO_LO-023 Benteler Automotive 6 30-NOV Version 4010 Version 3.2

29 Segment: BSS Beginning Segment for Shipping Schedule/Production Sequence Position: 020 Loop: Level: Heading Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set Semantic Notes: Example: BSS~00~ ~ ~DL~ ~ ~~ ~~ ~A* BSS Transaction Set Purpose Code M ID 2/2 Use "00" For Original BSS Reference Identification O AN 1/30 Reference information BSS Date M DT 8/8 Date expressed as CCYYMMDD BSS Schedule Type Qualifier M ID 2/2 Benteler uses Ship Dates Refer to FST04 BSS Date O DT 8/8 Date expressed as CCYYMMDD BSS Date O DT 8/8 Date expressed as CCYYMMDD BSS Reference Identification O AN 1/30 Reference information BSS Purchase Order Number M AN 10/10 Identifying number for Purchase Order assigned by the orderer/purchaser BSS Schedule Quantity Qualifier M ID 1/1 Use "A" for Actual Discrete Quantities NAO_LO-023 Benteler Automotive 7 30-NOV Version 4010 Version 3.2

30 Segment: N1 Name Position: 050 Loop: N1 Mandatory Level: Heading Purpose: To identify the Ship To Party Example: N1~ST~Windsor~98~0470* N Entity Identifier Code M ID 2/3 Use "ST" (Ship To) N Name M AN 1/60 Name of Benteler plant to which material is to be shipped N Identification Code Qualifier M ID 2/2 Use "98" (Benteler Plant Code) N Identification Code M AN 4/4 The Benteler Plant Code, Defined as Follows Corporate Hall Street Plant Hagen Drive Plant Kalamazoo Plant Goshen Plant Opelika Plant Brampton Plant Hermosillo Puebla Saltillo 1 st Occurrence of the N1 Loop NAO_LO-023 Benteler Automotive 8 30-NOV Version 4010 Version 3.2

31 Segment: N3 Address Information Position: 070 Loop: N1 Mandatory Level: Heading Usage: Optional Purpose: To specify the location of the Benteler Plant Semantic Notes: Example: N3~3721 Kalamazoo* N Address Information M AN 1/55 Address information N Address Information O AN 1/55 Address information NAO_LO-023 Benteler Automotive 9 30-NOV Version 4010 Version 3.2

32 Segment: N4 Geographic Location Position: 080 Loop: N1 Mandatory Level: Heading Usage: Optional Purpose: To specify the geographic place of the named party Semantic Notes: Example: N4~Windor~ON~49548~US* N City Name M AN 2/30 City name of Benteler ship-to plant N State or Province Code M ID 2/2 State code for Benteler ship-to plant N Postal Code M ID 3/15 Postal code of Benteler ship-to plant N Country Code M ID 2/3 Country code of Benteler ship-to plant NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

33 Segment: N1 Name Position: 050 Loop: N1 Mandatory Level: Detail Purpose: To identify a party by type of organization, name, and code Semantic Notes: Example: N1~SU~~16~ * N Entity Identifier Code M ID 2/3 Use "SU" (Supplier) N Identification Code Qualifier M ID 2/2 Use "16" (DUNS Number) N Identification Code M AN 2/80 The Supplier DUNS number. 2 nd Occurrence of the N1 Loop NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

34 Segment: LIN Item Identification Position: 010 Loop: LIN Mandatory Level: Detail Purpose: To specify basic item identification data Semantic Notes: Example: LIN~~BP~ ~EC~--~PL~10~PO~ ~RN~48~PD~60758-AD GM * LIN Product/Service ID Qualifier M ID 2/2 Use "BP" (Buyer's Part Number) LIN Product/Service ID M AN 1/18 Benteler Material Number LIN Product/Service ID Qualifier M ID 2/2 Use "EC" (Engineering Change Level) LIN Product/Service ID M AN 1/2 Benteler Engineering Change Level LIN Product/Service ID Qualifier M ID 2/2 Use "PL" (Purchase Order Line Number) LIN Product/Service ID M AN 1/5 Purchase Order Line Number (Must be returned on 856) LIN Product/Service ID Qualifier M ID 2/2 Use "PO" (Purchase Order Number) LIN Product/Service ID M AN 1/10 Number used to uniquely identify the Benteler Purchasing Document LIN Product/Service ID Qualifier M ID 2/2 Use "RN" (Release Number) LIN Product/Service ID M ID 1/9 Release Number of the Purchasing Document LIN Product/Service ID Qualifier O ID 2/2 Use PD Part Description LIN Product/Service ID O AN 1/22 Additional Part description Notes: Element 13, if sent, needs to be on the container label in the Reference number block or on the Primary metals tag in the Special Data block NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

35 Segment: UIT Unit Detail Position: 020 Loop: LIN Mandatory Level: Detail Purpose: To specify item unit data Semantic Notes: Example: UIT~PC* UIT Unit or Basis for Measurement Code M ID 2/2 Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

36 Segment: FST Forecast Schedule Position: 080 Loop: FST Mandatory Level: Detail Purpose: To specify the forecasted dates and quantities Semantic Notes: Example: FST~10~C~D~ ~~002~1830* FST Quantity M R 1/15 Numeric value of quantity FST Forecast Qualifier M ID 1/1 Code specifying the sender's confidence level of the forecast data or an action associated with a forecast C - Firm D - Planning FST Forecast Timing Qualifier M ID 1/1 Code specifying interval grouping of the forecast D - Discrete W - Weekly Bucket FST Date M DT 8/8 Date expressed as CCYYMMDD (Ship Date) FST Date/Time Qualifier O ID 3/3 Code specifying type of date or time, or both date and time FST Time O TM 4/8 Time expressed as HHMM (Ship Time) NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

37 Segment: SHP Shipped/Received Information Position: 470 Loop: SHP Optional Level: Detail Purpose: To specify shipment and/or receipt information Comments: 1 The SHP segment is used to communicate shipment, delivery, or receipt information and may include discrete or cumulative quantities, dates, and times. Example: SHP~01~5400~050~ * SHP Quantity Qualifier M ID 2/2 Code specifying the type of quantity 01 - Discrete Quantity 02 - Cumulative Quantity SHP Quantity M R 1/15 Numeric value of quantity SHP Date/Time Qualifier M ID 3/3 Use " 050" Receipt SHP Date M DT 8/8 Date Received/Cumulative Start Date Format: CCYYMMDD NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

38 Segment: REF Reference Identification Position: 480 Loop: SHP Optional Level: Detail Max Use: 5 Purpose: To specify identifying information Comments: Example: REF~SI~V * REF Reference Identification Qualifier M ID 2/3 Use "SI" For Shipper Number REF Reference Identification M AN 1/30 Shipper Number NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

39 Segment: CTT Transaction Totals Position: 010 Loop: Level: Summary Purpose: To transmit a hash total for a specific element in the transaction set Semantic Notes: Example: CTT~4* CTT Number of Line Items M N0 1/6 Total number of LIN segments NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

40 Segment: SE Transaction Set Trailer Position: 020 Loop: Level: Summary Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Semantic Notes: Comments: 1 SE is the last segment of each transaction set. SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

41 Segment: GE Functional Group Trailer Position: 030 Loop: Level: Summary Usage: Optional Purpose: To indicate the end of a functional group and to provide control information Semantic Notes: 1 The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06. Example: GE~1~159* GE01 97 Number of Transaction Sets Included M N0 1/6 Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element GE02 28 Group Control Number M N0 1/9 Assigned number originated and maintained by the sender NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

42 Segment: IEA Interchange Control Trailer Position: 040 Loop: Level: Summary Usage: Optional Purpose: Semantic Notes: Example: To define the end of an interchange of zero or more functional groups and interchangerelated control segments IEA~1~ * IEA01 I16 Number of Included Functional Groups M N0 1/5 A count of the number of functional groups included in an interchange IEA02 I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

43 Sample 862 EDI ISA~00~ ~00~ ~01~ ~01~ ~021105~0832~U~00400~ ~0~P~<* GS~SS~ ~ ~ ~0832~159~X~004010* ST~862~0001* BSS~00~ ~ ~DL~ ~ ~~ ~~ ~A* N1~ST~Windsor~98~0470* N3~3721 kalamazoo* N4~Windor~ON~49548~US* N1~SU~~16~ * LIN~~BP~ ~EC~--~PL~10~PO~ ~RN~48~PD~60758-AD GM * UIT~PC* FST~10~C~D~ ~~002~1830* FST~10~C~D~ ~~002~1800* FST~10~C~D~ ~~002~1830* FST~10~C~D~ ~~002~1830* SHP~01~5400~050~ * REF~SI~V * SHP~02~631800~050~ * LIN~~BP~ ~EC~ND~PL~20~PO~ ~RN~48~PD~60758-AD GM * UIT~PC* FST~10~C~D~ ~~002~1830* FST~10~C~D~ ~~002~1800* FST~10~C~D~ ~~002~1830* FST~10~C~D~ ~~002~1830* SHP~01~5400~050~ * REF~SI~V * SHP~02~631800~050~ * LIN~~BP~ ~EC~--~PL~30~PO~ ~RN~49~PD~60758-AD GM * UIT~PC* FST~10~C~D~ ~~002~1830* FST~10~C~D~ ~~002~1800* FST~10~C~D~ ~~002~1830* FST~10~C~D~ ~~002~1830* SHP~01~5400~050~ * REF~SI~V * SHP~02~631800~050~ * LIN~~BP~ ~EC~--~PL~40~PO~ ~RN~49* UIT~PC* FST~10~C~D~ ~~002~1830* FST~10~C~D~ ~~002~1800* FST~10~C~D~ ~~002~1830* FST~10~C~D~ ~~002~1830* SHP~01~5400~050~ * REF~SI~V * SHP~02~631800~050~ * CTT~4* SE~44~0001* GE~1~159* IEA~1~ * NAO_LO-023 Benteler Automotive NOV Version 4010 Version 3.2

44 Benteler Automotive Electronic Data Interchange Specifications Transaction 997 Version 2.1 Feb 1, 2003 Benteler Automotive 1 Feb 1, Version 4010 Version 2.11

45 BENTELER AUTOMOTIVE 997 Functional Acknowledgment Functional Group ID=FA Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional Acknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets. Pos. Seg. Req. Loop Notes and No. ID Name Des. Max.Use Repeat Comments 010 ST Transaction Set Header M 1 n1 020 AK1 Functional Group Response Header M 1 n2 LOOP ID - AK AK2 Transaction Set Response Header M 1 n3 060 AK5 Transaction Set Response Trailer M AK9 Functional Group Response Trailer M SE Transaction Set Trailer M 1 Transaction Set Notes 1. These acknowledgments shall not be acknowledged, thereby preventing an endless cycle of acknowledgments of acknowledgments. Nor shall a Functional Acknowledgment be sent to report errors in a previous Functional Acknowledgment. The Functional Group Header Segment (GS) is used to start the envelope for the Functional Acknowledgment Transaction Sets. In preparing the functional group of acknowledgments, the application sender's code and the application receiver's code, taken from the functional group being acknowledged, are exchanged; therefore, one acknowledgment functional group responds to only those functional groups from one application receiver's code to one application sender's code. There is only one Functional Acknowledgment Transaction Set per acknowledged functional group. 2. AK1 is used to respond to the functional group header and to start the acknowledgement for a functional group. There shall be one AK1 segment for the functional group that is being acknowledged. 3. AK2 is used to start the acknowledgement of a transaction set within the received functional group. The AK2 segments shall appear in the same order as the transaction sets in the functional group that has been received and is being acknowledged. Benteler Automotive 2 Feb 1, Version 4010 Version 2.11

46 Segment: ISA Interchange Control Header Position: 005 Loop: Level: Heading Purpose: To start and identify an interchange of zero or more functional groups and interchangerelated control segments Example: ISA~00~ ~00~ ~01~ ~ZZ~ ~030131~1650~U~ 00400~ ~0~P~> ISA01 I01 Authorization Information Qualifier M ID 2/2 Use "00" ISA02 I02 Authorization Information M AN 10/10 Use Ten Spaces ISA03 I03 Security Information Qualifier M ID 2/2 Use "00" ISA04 I04 Security Information M AN 10/10 Use Ten Spaces ISA05 I05 Interchange ID Qualifier M ID 2/2 Use "01" or other applicable codes ISA06 I06 Interchange Sender ID M AN 15/15 DUNS Number. Left Justify, Space Fill ISA07 I05 Interchange ID Qualifier M ID 2/2 Use "01" or other applicable codes ISA08 I07 Interchange Receiver ID M AN 15/15 DUNS Number. Left Justify, Space Fill ISA09 I08 Interchange Date M DT 6/6 Date of Creation ISA10 I09 Interchange Time M TM 4/4 Time Of Creation ISA11 I10 Interchange Control Standards Identifier M ID 1/1 Use "U" for U.S. ISA12 I11 Interchange Control Version Number M ID 5/5 Use "00401" ISA13 I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender ISA14 I13 Acknowledgment Requested M ID 1/1 Use "0" for no Ack. Req., Use "1" for Ack. Req ISA15 I14 Usage Indicator M ID 1/1 Use "T" For Test or "P" For Production Refer to Data Element Dictionary for acceptable code values. ISA16 I15 Component Element Separator M AN 1/1 Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component Benteler Automotive 3 Feb 1, Version 4010 Version 2.11

47 data elements within a composite data structure; this value must be different than the data element separator and the segment terminator Benteler Automotive 4 Feb 1, Version 4010 Version 2.11

48 Segment: GS Functional Group Header Position: 007 Loop: Level: Heading Purpose: To indicate the beginning of a functional group and to provide control information Semantic Notes: 1 GS04 is the group date. 3 GS06 in this header must be identical to the same data element in the associated functional group trailer, GE02. Example: GS~FA~ ~ ~ ~1650~11~X~ GS Functional Identifier Code M ID 2/2 Use "FA" for Functional Acknowledgement GS Application Sender's Code M AN 2/15 Use Duns Number GS Application Receiver's Code M AN 2/15 Use Duns Number GS Date M DT 8/8 Creation Date GS Time M TM 4/8 Creation Time GS06 28 Group Control Number M N0 1/9 Start with 1 and increment by 1 for each subsequent GS Segment GS Responsible Agency Code M ID 1/2 Use "X" GS Version / Release / Industry Identifier Code M AN 6/6 Use "004010" Benteler Automotive 5 Feb 1, Version 4010 Version 2.11

49 Segment: ST Transaction Set Header Position: 010 Loop: Level: Purpose: To indicate the start of a transaction set and to assign a control number Semantic Notes: 1 The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set). Example: ST~997~0001 ST Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set Refer to Data Element Dictionary for acceptable code values. ST Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Benteler Automotive 6 Feb 1, Version 4010 Version 2.11

50 Segment: AK1 Functional Group Response Header Position: 020 Loop: Level: Purpose: To start acknowledgment of a functional group Semantic Notes: 1 AK101 is the functional ID found in the GS segment (GS01) in the functional group being acknowledged. 2 AK102 is the functional group control number found in the GS segment in the functional group being acknowledged. Example: AK1~SH~22 AK Functional Identifier Code M ID 2/2 Code Identifying a group of application related transaction sets AK Group Control Number M N0 1/9 Assigned number originated and maintained by the sender Benteler Automotive 7 Feb 1, Version 4010 Version 2.11

51 Segment: AK2 Transaction Set Response Header Position: 030 Loop: AK2 Mandatory Level: Purpose: To start acknowledgment of a single transaction set Semantic Notes: 1 AK201 is the transaction set ID found in the ST segment (ST01) in the transaction set being acknowledged. 2 AK202 is the transaction set control number found in the ST segment in the transaction set being acknowledged. Example: AK2~856~ AK Transaction Set Identifier Code M ID 3/3 Code uniquely identifying a Transaction Set AK Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Benteler Automotive 8 Feb 1, Version 4010 Version 2.11

52 Segment: AK5 Transaction Set Response Trailer Position: 060 Loop: AK2 Mandatory Level: Purpose: To acknowledge acceptance or rejection and report errors in a transaction set Semantic Notes: Example: AK5~A AK Transaction Set Acknowledgment Code M ID 1/1 Code indicating accept or reject condition based on the syntax editing of the transaction set AK Transaction Set Syntax Error Code O ID 1/3 Code indicating error found based on the syntax editing of a transaction set Benteler Automotive 9 Feb 1, Version 4010 Version 2.11

53 Segment: AK9 Functional Group Response Trailer Position: 070 Loop: Level: Purpose: To acknowledge acceptance or rejection of a functional group and report the number of included transaction sets from the original trailer, the accepted sets, and the received sets in this functional group Example: AK9~A~1~1~1 AK Functional Group Acknowledge Code M ID 1/1 Code indicating accept or reject condition based on the syntax editing of the functional group AK Number of Transaction Sets Included M N0 1/6 Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element AK Number of Received Transaction Sets M N0 1/6 Number of Transaction Sets received AK904 2 Number of Accepted Transaction Sets M N0 1/6 Number of accepted Transaction Sets in a Functional Group AK Functional Group Syntax Error Code O ID 1/3 Code indicating error found based on the syntax editing of the functional group header and/or trailer Benteler Automotive 10 Feb 1, Version 4010 Version 2.11

54 Segment: SE Transaction Set Trailer Position: 080 Loop: Level: Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) Example: SE~6~0001 SE01 96 Number of Included Segments M N0 1/10 Total number of segments included in a transaction set including ST and SE segments SE Transaction Set Control Number M AN 4/9 Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set Benteler Automotive 11 Feb 1, Version 4010 Version 2.11

55 Segment: GE Functional Group Trailer Position: 030 Loop: Level: Summary Usage: Optional Purpose: To indicate the end of a functional group and to provide control information Semantic Notes: 1 The data interchange control number GE02 in this trailer must be identical to the same data element in the associated functional group header, GS06. Example: GE~1~11 GE01 97 Number of Transaction Sets Included M N0 1/6 Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element GE02 28 Group Control Number M N0 1/9 Assigned number originated and maintained by the sender Benteler Automotive 12 Feb 1, Version 4010 Version 2.11

56 Segment: IEA Interchange Control Trailer Position: 040 Loop: Level: Summary Usage: Optional Purpose: Semantic Notes: Example: To define the end of an interchange of zero or more functional groups and interchangerelated control segments IEA~1~ IEA01 I16 Number of Included Functional Groups M N0 1/5 A count of the number of functional groups included in an interchange IEA02 I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender Benteler Automotive 13 Feb 1, Version 4010 Version 2.11

57 SAMPLE 830 EDI Benteler to Vendor ISA~00~ ~00~ ~01~ ~ZZ~ ~030131~1650~U~00400~ ~0~P~> GS~FA~ ~ ~ ~1650~11~X~ ST~997~0001 AK1~SH~22 AK2~856~ AK5~A AK9~A~1~1~1 SE~6~0001 GE~1~11 IEA~1~ Vendor to Benteler ISA*00* *00* *01* *01* *030131*1319*U*00400* *0*P*> GS*FA* * * *1319*596015*X* ST*997* AK1*SS*522 AK2*862*0001 AK5*A AK9*A*1*1*1 SE*6* GE*1* IEA*1* Benteler Automotive 14 Feb 1, Version 4010 Version 2.11

58 CONTACT INFORMATION Primary EDI & Barcode Contact Joe Osmialowski Phone 1(248) Fax 1(248) Pond Run Auburn Hills, MI Secondary EDI & Barcode Contact Bob Green Phone 1(248) Fax 1(248) Pond Run Auburn Hills, MI Secondary EDI & Barcode Contact Tiann Schmidt Phone 1(248) Fax 1(248) Pond Run Auburn Hills, MI EDI VAN INFORMATION Transaction Set X.12 Version Number Transmitted From Transmitted To Frequency Advantis Account and Userid Benteler ISA/GS DUNS Number 830 Release Benteler Supplier Weekly Ship Benteler Supplier As Needed Functional Acknowledgement Supplier Benteler Upon receipt of 830/862 BENT BENT Advance Ship Notice 997 Functional Acknowledgement Supplier Benteler Upon Truck Departure Benteler Supplier Upon receipt of ASN BENT BENT Benteler Automotive 15 Feb 1, Version 4010 Version 2.11

59 Benteler Automotive Electronic Data Interchange Specifications Transaction 830 Version 2.3 November 30, 2009 NAO_LO-023 Benteler Automotive 1 Version NOV Version 4010

60 Changes from Version Updated Benteler plant codes in the N1 ST segment 2. Added Notes: to the LIN segment for PD element Changes from Version Added elements 12 and 13 to the LIN segment 2. Updated the example 3. Removed Contact and VAN information 4. Add Benteler Mexico Plant codes NAO_LO-023 Benteler Automotive 2 Version NOV Version 4010

61 Benteler Automotive 830 Planning Schedule with Release Capability Introduction: Functional Group ID=PS This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule with Release Capability Transaction Set (830) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to provide for customary and established business practice relative to the transfer of forecasting/material release information between organizations. The planning schedule transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the buyer's authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in "buckets," such as weekly, monthly, or quarterly. The order release forecast may also contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders. Heading: Detail: Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat 010 ST Transaction Set Header M BFR Beginning Segment for Planning Schedule M 1 LOOP ID - N N1 Name M N3 Address Information O N4 Geographic Location O 1 Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat LOOP ID - LIN >1 010 LIN Item Identification M UIT Unit Detail M ATH Resource Authorization M 20 LOOP ID - FST >1 460 FST Forecast Schedule M 1 Summary: LOOP ID - SHP SHP Shipped/Received Information M REF Reference Identification O 5 Pos. Seg. Req. Loop No. ID Name Des. Max.Use Repeat 010 CTT Transaction Totals M SE Transaction Set Trailer M 1 NAO_LO-023 Benteler Automotive 3 Version NOV Version 4010

62 Segment: ISA Interchange Control Header Position: 005 Loop: Level: Heading Purpose: To start and identify an interchange of zero or more functional groups and interchangerelated control segments Example: ISA~00~ ~00~ ~01~ ~01~ ~021105~0832~U~ 00400~ ~0~P~<* ISA01 I01 Authorization Information Qualifier M ID 2/2 Use "00" ISA02 I02 Authorization Information M AN 10/10 Use Ten Spaces ISA03 I03 Security Information Qualifier M ID 2/2 Use "00" ISA04 I04 Security Information M AN 10/10 Use Ten Spaces ISA05 I05 Interchange ID Qualifier M ID 2/2 Use "01" or other applicable codes ISA06 I06 Interchange Sender ID M AN 15/15 DUNS Number. Left Justify, Space Fill ISA07 I05 Interchange ID Qualifier M ID 2/2 Use "01" or other applicable codes ISA08 I07 Interchange Receiver ID M AN 15/15 DUNS Number. Left Justify, Space Fill ISA09 I08 Interchange Date M DT 6/6 Date of Creation ISA10 I09 Interchange Time M TM 4/4 Time Of Creation ISA11 I10 Interchange Control Standards Identifier M ID 1/1 Use "U" for U.S. ISA12 I11 Interchange Control Version Number M ID 5/5 Use "00401" ISA13 I12 Interchange Control Number M N0 9/9 A control number assigned by the interchange sender ISA14 I13 Acknowledgment Requested M ID 1/1 Use "0" for no Ack. Req., Use "1" for Ack. Req ISA15 I14 Usage Indicator M ID 1/1 Use "T" For Test or "P" For Production Refer to Data Element Dictionary for acceptable code values. ISA16 I15 Component Element Separator M AN 1/1 Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator NAO_LO-023 Benteler Automotive 4 Version NOV Version 4010