edifact contrl d - benteler-suppliers.com nao edi implementation guidelines edifact contrl contrl...

BENTELER NAO EDI IMPLEMENTATION GUIDELINES EDIFACT CONTRL

Contrl Message EDIFACT CONTRL D.97A

Version 1.0

Implementation Guideline CONTRL Version 1.0 – 30-JAN-2006 1


Document Change Log

Version Date Description

1.0 30-JAN-2006 Document Issued



0. TABLE OF CONTENT

0. TABLE OF CONTENT...........................................................................................................3

1. INTRODUCTION....................................................................................................................4

2. MESSAGE DEFINITION........................................................................................................4

2.1. FUNCTIONAL DEFINITION.................................................................................................4 2.2. PRINCIPLES .......................................................................................................................4 2.3. REFERENCES ....................................................................................................................4 2.4. FIELD OF APPLICATION ....................................................................................................4

3. MESSAGE DESCRIPTION....................................................................................................5

3.1. INTRODUCTION .......................................................................................................................5 3.1.1. How to read the documentation........................................................................................5 3.2. SEGMENT TABLE...............................................................................................................7 3.3. MESSAGE STANDARD DESCRIPTION ...........................................................................................7 3.4. MESSAGE STRUCTURE .............................................................................................................7 3.5. DATA SEGMENTS DESCRIPTION ...................................................................................11 3.6. MESSAGE EXAMPLE ........................................................................................................12



1. INTRODUCTION

This document provides the specific description of a subset of the EDIFACT CONTRL D97.A message to be used between a Trading Partner and Benteler Automotive, NAO.

2. MESSAGE DEFINITION

This document provides the definition of an Acknowledgement/Rejection Advice Message, based on the EDIFACT CONTRL D97.A, to be used in Electronic Data Interchange (EDI) between a Trading Partner and Benteler Automotive, NAO.

2.1. FUNCTIONAL DEFINITION

The Acknowledgement/Rejection Advice message is a message from a Benteler NAO Supplier to the relevant Benteler application to confirm receipt of the transmitted DELFOR/DELJIT. It is also sent by Benteler Automotive NAO to a Supplier to confirms the receipt of a DESADV that was transmitted to Benteler Automotive NAO

2.2. PRINCIPLES

The Acknowledgement/Rejection Advice message intends to:

• advise the recipient that the ASN/Despatch Advice message was received by Benteler.

• advise Benteler NAO that the DELFOR/DELJIT message was received by the recipient.

2.3. REFERENCES

The content of this message is based on:

• the message structure as defined by EDIFACT for the UNSM Acknowledgement/Rejection Advice Message, CONTRL as published in the UN/EDIFACT D97.A Directory.

• the agreement between the Trading Partners on the data elements to be used, their unique definition, their representation and their values (coded or clear form) as identified in this document.

Benteler NAO has opted for the EDIFACT D97.A Directory and consistently uses this directory for all its EDIFACT messages. Although the AVIEXP subset defined by ODETTE has been based on the EDIFACT D96.A Directory, the subset defined by Benteler NAO and described in this document follows as close as possible the structure of the ODETTE subset.

2.4. FIELD OF APPLICATION

The following definition of an Acknowledgement/Rejection Advice Message in EDIFACT format is applicable for the interchange of receiving advice messages sent by and received by Benteler Automotive, NAO.



3. MESSAGE DESCRIPTION

The following pages contain a full description of the EDIFACT CONTRL D.97A message as implemented by Benteler Automotive, NAO. The official EDIFACT segment description is complemented with remarks pertaining to the specific requirements for an interchange with Benteler Automotive, NAO. Those remarks contain specific code values used, additional information on the values shown in a specific field, etc.

3.1. INTRODUCTION

3.1.1. How to read the documentation

All segments in the subset used by Benteler Automotive, NAO are described in the following pages. The segment description is to be read as follows:

‹ 0020 BGM - BEGINNING OF MESSAGE

› Segment group: none. Level: 1. fi EDIFACT status: mandatory. Benteler status: mandatory. fl Maximum use: 1 per message. Benteler

occurrences: 1 per message.

‒ Function: segment for the unique identification of the delivery schedule document, by means of its name and its number.

‒ Benteler interchange:

see remarks.

† Example: BGM+241+12+5’ A B C

‡ EDIFACT STANDARD DEFINITION BENTELER IMPLEMENTATION

· REF TAG NAME ST FT SP ST FT REMARKS

C002 DOCUMENT/MESSAGE NAME C C A 1001 Document/message name, coded C an..3 : M an..3 '241’ = Delivery Schedule ¶ 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 : 1000 Document/message name C an..35 +

C106 DOCUMENT/MESSAGE IDENTIFICATION

C

B 1004 Document/message number C an..35 : M an..35 Benteler assigned number 1056 Version C an..9 : 1060 Revision number C an..6 +

C 1225 MESSAGE FUNCTION, CODED C an..3 + M an..3 Function of the message. For code values see below.

4343 RESPONSE TYPE, CODED C an..3 ‘

• COMMENTS

• CODE VALUES

LEGEND

‹ segment position in the message structure, segment tag and segment name.

› identification (when applicable) of the segment group in which the segment is situated and indication at which level the segment is in the message.

fi status of the segment: as defined by EDIFACT and by Benteler Automotive, NAO

fl number of occurrences of the segment: as defined by EDIFACT and as used by Benteler Automotive, NAO.

‒ description of the function of the segment as defined by EDIFACT and as used by Benteler Automotive, NAO



† example of the segment as it may appear in an interchange. This example is only illustrative and does not necessarily represent an actual situation. It should NOT be used as a basis to implement this message.

‡ definition of the segment content as defined by EDIFACT and as implemented by BENTELER.

· identification of the data elements in the segment

• reference to the example.

• data element tag - data elements with a ‘C’ denote a composite data element.

• data element name - italic CAPITALS denote a composite data element.

• ST - the status of the data element.

• FT - the format of the data element, i.e. the indication of the number of characters (numerical or alphabetical) for this data element.

• SP - the separator used between the data elements.

• remarks on the specific use of the data element in the interchange with BENTELER AUTOMOTIVE, NAO.

¶ shaded areas in the BENTELER AUTOMOTIVE, NAO description mean that the data element is not used by BENTELER AUTOMOTIVE, NAO.

• the segment description can be followed by:

• comments providing more information regarding specific data elements and how they must be used and/or understood in messages from BENTELER AUTOMOTIVE, NAO.

• code values to be used for data elements contained in the message.



3.2. SEGMENT TABLE

The following table shows the segments defined for the EDIFACT UNSM CONTRL D97.A message. Shaded areas identify the segments that are not used in the subset of CONTRL used by Benteler

POS. TAG NAME ST REPEATS

0010 UNH Message Header M 1 0020 UCI Interchange response M 1 0030 UCM Message response C 1

0040 UCS Segment error Indication C 1 0050 UCD Data element error indication C 1 0060 UCF Functional group response C 1 0070 UCM Message Response C 1

0080 UCS Segment Error Indication C 1 0090 UCD Data Element Error Identification C 1 1040 UNT Message trailer M 1

3.3. MESSAGE STANDARD DESCRIPTION

This section provides the description of the UN Standard Message CONTRL as defined in the 97A Directory. These segments used in the subset defined by Benteler Automotive, NAO and will be further explained in section 3.6.

3.3.1 Header section

Information to be provided in the Header section:

0010 UNH, Message header A service segment starting and uniquely identifying a message. The message type code for the Despatch advice message is DESADV.

0020 UCI, Interchange Response A segment for unique identification of the Despatch Advice document, by means of its name and its number.

0100 UNT, Message trailer A service segment ending a message, giving the total number of segments in the message and the control reference number of the message.

3.4. MESSAGE STRUCTURE

The message structure illustrates how the segments will be repeated in the Shipping Schedule message to accommodate the requirements identified by Benteler Automotive, NAO.

0010.UNH Start of Acknowledgement Message

0020.UCI Interchange Response

0500.UNT End of Message



0000 UNB - INTERCHANGE HEADER

Segment Group: none Level: 0 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 1 per interchange Benteler occurrences: 1 per interchange Function service segment providing the unique identification of an interchange. It allows the identification of the

sender and the receiver of the interchange gives date and time of preparation as well as the interchange control reference and the application reference.

Benteler interchange: see remarks.

Example: UNB+UNOA:2+112836044:01+002345983:01+051212:1057+39++BENTELERNAO’ A B C D E F G H

EDIFACT STANDARD DEFINITION Benteler Automotive, NAO IMPLEMENTATION REF TAG NAME ST FT SP ST FT REMARKS

S001 SYNTAX IDENTIFIER M M A 0001 Syntax identifier M a4 : M A4 “UNOA”. B 0002 Syntax version number M n1 + M N1 Indication of the syntax version used for this

message.

S002 INTERCHANGE SENDER M M C 0004 Sender identification M an..35 : M an..35 112836044 Benteler Communication Code 0007 Identification code qualifier C an..4 : M Qualifiers to be determined by trading partner

relationship. 0008 Address for Reverse Routing C an..14 +

S003 INTERCHANGE RECIPIENT M M D 0010 Recipient identification M an..35 : M an..35 Code of the party receiving the message. 0007 Identification code qualifier C an..4 : M Qualifiers to be determined by trading partner

relationship. 0014 Routing address C an..14 +

S004 DATE / TIME OF PREPARATION M M E 0017 Date of preparation M n6 : M N6 YYMMDD Format. F 0019 Time of preparation M n4 + M N4 HHMM Format.

G 0020 INTERCHANGE CONTROL REFERENCE

M an..14 + M an..14 A UNIQUE number within an inventory year.

S005 RECIPIENTS REFERENCE PASSWORD

C

0022 Recipient's reference / password M an..14 : 0025 Recipient's reference / password

qualifier C an2 +

H 0026 APPLICATION REFERENCE C an..14 + C an..14 “BENTELERNAO”

0029 PROCESSING PRIORITY CODE C a1 +

0031 ACKNOWLEDGEMENT REQUEST C n1 +

0032 COMMUNICATIONS AGREEMENT ID C an..35 +

0035 TEST INDICATOR C n1 '



0010 UNH - MESSAGE HEADER

Segment group: none Level: 0 EDIFACT status: mandatory. Benteler status: mandatory. Maximum use: 1 per message. Benteler occurrences: 1 per message. Function: service segment starting and uniquely identifying a message. The message type code is CONTRL. Benteler interchange:

Example: UNH+1+CONTRL:D:97A:UN’ A B C D E


A 0062 MESSAGE REFERENCE NUMBER M an..14 + M an..14 Message Control number assigned by the sender to the message.

S009 MESSAGE IDENTIFIER M M B 0065 Message type M an..6 : M an..6 “CONTRL”. C 0052 Message version number M an..3 : M an..3 “D”. D 0054 Message release number M an..3 : M an..3 “97A”. E 0051 Controlling agency M an..2 : M an..2 “UN”. 0057 Association assigned code C an..6 +

0068 COMMON ACCESS REFERENCE C an..35 +

S010 STATUS OF TRANSFER C 0070 Sequence of transfer M n..2 : 0073 First and last transfer C a1 ‘



0500 UNT - MESSAGE TRAILER

Segment group: none Level: 0 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 1 per message Benteler occurrences: 1 per message Function: service segment ending a message, giving the total number of segments in the message and the

control reference number of the message. Benteler interchange: see remarks.

Example: UNT+99+1’ A B


A 0074 NUMBER OF SEGMENTS IN THE MESSAGE

M n..6 M n..6 Control count of the number of segments in the message, including UNH and UNT.

B 0062 MESSAGE REFERENCE NUMBER M an..14 M an..14 Number must be identical to UNH - tag 0062

0510 UNZ - INTERCHANGE TRAILER

Segment Group: none Level: 0 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 1 Benteler occurrences: 1 per interchange Function: service segment ending an interchange and giving the number of messages contained in the

interchange as well as the Interchange Control Reference number. Benteler interchange: see remarks.

Example: UNZ+1+39’ A B

EDIFACT STANDARD DEFINITION Benteler IMPLEMENTATION REF TAG NAME ST FT SP ST FT REMARKS

A 0036 INTERCHANGE CONTROL COUNT M n..6 + M n..6 Number of messages in an interchange.

B 0020 INTERCHANGE CONTROL REFERENCE

M an..14 ‘ M an..14 Value must be the same as 0020 - Interchange Control Reference in UNB.



3.5. DATA SEGMENTS DESCRIPTION

This part includes only the segments defined in the standard and used in the subset exchanged between Benteler and its Trading Partners. The segments are described in the same sequence as they appear in the message.

0020 UCI – INTERCHANGE RESPONSE

Segment group: none Level: 1 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 1 per message Benteler occurrences: 1 per message Function: segment for unique identification of the Despatch Advice document, by means of its name and its

number. Benteler interchange: see remarks.

Example: UCI+12345+123456789:01+988776654:01+7’ A B C D E F

EDIFACT STANDARD DEFINITION BENTELER IMPLEMENTATION

REF TAG NAME ST FT SP ST FT REMARKS

M A 0020 Interchange Control Reference M An..14 + M An..14 Sender Interchange reference number S002 Interchange Sender M :

B 0004 Sender Identification C An..35 + M An..35 Sender Identification C 0007 Sender Identification code qualifier C An..4 : M An..4 Sender Identification Qualifier

0008 Address for reverse routing C An..14 S003 Interchange Recpient C : M

D 0010 Recipient Identification C An..35 : M An..35 Recipient identification

E 0007 Identification code qualifier C An.4 + M An..4 Recipient identification qualifier

0014 Routing address C An..14 +

F 0083 Action code C An..3 ‘ M An..3 Acknowledgement/Rejection Code

CODE VALUES

0083 - Action codes

4 Rejected 7 Accepted



3.6. MESSAGE EXAMPLE

Following example is only illustrative and does not necessarily reflect an existing situation. It MAY NEVER be used as a basis for programming or implementing this message.

UNB+UNOA:2+003456789+112836044+2050305:1600+1234++BENTELERNAO’ UNH+1+CONTRL:D:97A:UN’ UCI+4+123456789:01+112836044:01+7’ Interchange status UNT+23+1’ UNZ+1+1234’

For ease of reading the message has been shown with each segment type on a separate line, which will not be the case when the message is normally transmitted.


BENTELER NAO EDI IMPLEMENTATION GUIDELINES EDIFACT DELJIT

NAO_LO-023 Implementation Guideline DELJIT Version 1.2 – 30-NOV-2009 1

Ship Schedule EDIFACT DELJIT D.97A

Version 1.2



Document Change Log



1.1 19-MAR-2009 Add additional elements to the PIA segment – PD Add Benteler Mexico plant codes

1.2 30-NON-2009 Update Benteler plant codes in the NAD ST segment Added comment to the PIA segment, PD element usage



0. TABLE OF CONTENT

0. TABLE OF CONTENT ...........................................................................................................3

1. INTRODUCTION ....................................................................................................................4

2. MESSAGE DEFINITION ........................................................................................................4

2.1. FUNCTIONAL DEFINITION .................................................................................................4 2.2. PRINCIPLES........................................................................................................................4 2.3. REFERENCES.....................................................................................................................4 2.4. FIELD OF APPLICATION.....................................................................................................4

3. MESSAGE DESCRIPTION ....................................................................................................5

3.1. INTRODUCTION...................................................................................................................5 3.1.1. How to read the documentation .......................................................................................5 3.1.2. General remarks...............................................................................................................6 3.2. SEGMENT TABLE................................................................................................................7 3.3. MESSAGE STANDARD DESCRIPTION ..............................................................................8 3.4. MESSAGE STRUCTURE.....................................................................................................9 3.5. DATA SEGMENTS DESCRIPTION....................................................................................13 3.6. EXAMPLE OF MESSAGE ..................................................................................................26



1. INTRODUCTION

This specification provides the definition of the EDIFACT DELJIT D97.A Ship schedule message (DELJIT). This guideline is specifically designed to outline the requirements for the Ship Schedule used by Benteler Automotive NAO.


This document provides the definition of a Ship Schedule Message, based on the EDIFACT DELJIT D.97A, to be used in Electronic Data Interchange (EDI) between Benteler Automotive, NAO and its Trading Partners.


The Ship Schedule message is a message from Benteler Automotive, NAO to a Benteler Automotive, NAO Supplier giving details on specific quantities to be delivered to specific delivery points on specific dates and times.

2.2. PRINCIPLES

The Ship Schedule message is intended to:

• specify requirements based on the delivery conditions.

• define the aspects that guarantee synchronization between Benteler Automotive, NAO and the Supplier.

2.3. REFERENCES


• the message structure as defined by EDIFACT for the Ship Schedule Message DELJIT as published in the UN/EDIFACT D.97A Directory.


Benteler Automotive, NAO has chosen for the EDIFACT D.97A Directory and consistently uses this directory for all its EDIFACT messages.


The following definition of a Ship Schedule Message in EDIFACT format is applicable for the interchange of shipping instructions issued by Benteler Automotive, NAO for material deliveries to one or more Benteler Automotive, NAO Operations.




The following pages contain a full description of the EDIFACT DELJIT D.97A message as implemented by Benteler Automotive, NAO. The official EDIFACT segment description is complemented with remarks pertaining to the specific requirements for an interchange with Benteler Automotive, NAO. Those remarks contain specific code values used, additional information on the values shown in a specific field, etc.

3.1. INTRODUCTION


All segments in the subset used by Benteler Automotive, NAO are described in the following pages. The segment description is to be read as follows:

� 0020 BGM - BEGINNING OF MESSAGE

� Segment group: none. Level: 1. � EDIFACT status: mandatory. Benteler status: mandatory. � Maximum use: 1 per message. Benteler


� Function: segment for the unique identification of the delivery schedule document, by means of its name and its number.

� Benteler interchange:

see remarks.

� Example: BGM+241+12+5’ A B C

� EDIFACT STANDARD DEFINITION BENTELER IMPLEMENTATION

� REF TAG NAME ST FT SP ST FT REMARKS

C002 DOCUMENT/MESSAGE NAME C C

A 1001 Document/message name, coded C An..3 : M an..3 '241’ = Delivery Schedule 1131 Code list qualifier C An..3 : 3055 Code list responsible agency,

coded C An..3 :

1000 Document/message name C An..35 +


C

B 1004 Document/message number C An..35 : M an..35 Benteler assigned number 1056 Version C An..9 : 1060 Revision number C An..6 +

C 1225 MESSAGE FUNCTION, CODED C An..3 + M an..3 Function of the message. For code values see below.

4343 RESPONSE TYPE, CODED C An..3 ‘

COMMENTS

CODE VALUES

LEGEND

� segment position in the message structure, segment tag and segment name.

� identification (when applicable) of the segment group in which the segment is situated and indication at which level the segment is in the message.

� status of the segment: as defined by EDIFACT and by Benteler Automotive, NAO

� number of occurrences of the segment: as defined by EDIFACT and as used by Benteler Automotive, NAO.

� description of the function of the segment as defined by EDIFACT and as used by Benteler Automotive, NAO



� example of the segment as it may appear in an interchange. This example is only

illustrative and does not necessarily represent an actual situation. It should NOT be used as a basis to implement this message.

� definition of the segment content as defined by EDIFACT and as implemented by BENTELER.

� identification of the data elements in the segment







• remarks on the specific use of the data element in the interchange with BENTELER AUTOMOTIVE, NAO.

shaded areas in the BENTELER AUTOMOTIVE, NAO description mean that the data element is not used by BENTELER AUTOMOTIVE, NAO.

the segment description can be followed by:

• comments providing more information regarding specific data elements and how they must be used and/or understood in messages from BENTELER AUTOMOTIVE, NAO.


3.1.2. General remarks

Following remarks are applicable for the complete documentation:

Dates Unless otherwise specified in the field explanation in the documentation, dates are

always expressed as CCYYMMDD (qualifier 2379 = 102).

Times

Unless otherwise specified in the field explanation in the documentation, times are

always expressed as HHMM.



3.2. SEGMENT TABLE

The following table shows the segments defined for the EDIFACT DELJIT D.97A Delivery Just-in-Time message. Shaded areas identify the segments that are not used in the subset of DELJIT used by BENTELER AUTOMOTIVE, NAO.


0010 UNH Message header M 1 0020 BGM Beginning of message M 1 0030 DTM Date/time/period M 10 0040 FTX Free text C 5

0050 Segment group 1 C 10

0060 RFF Reference M 1 0070 DTM Date/time/period C 1

0080 Segment group 2 M 20

0090 NAD Name and address M 1 0100 LOC Place/location identification C 10 0110 FTX Free text C 5


0130 CTA Contact information M 1 0140 COM Communication contact C 5


0160 SEQ Sequence details M 1 0170 DTM Date/time/period C 5 0180 GIR Related identification numbers C 99 0190 LOC Place/location identification C 5


0210 PAC Package identification M 1


0230 PCI Package identification M 1 0240 GIN Goods identity number C 10


0260 LIN Line item M 1 0270 PIA Additional product id M 10 0280 IMD Item description C 10 0290 ALI Additional information C 5 0300 GIR Related identification numbers C 5 0310 TDT Details of transport C 5 0320 FTX Free text C 5 0330 PAC Package identification C 5 0340 DTM Date/time/period C 5




0390 LOC Place/location identification M 1




0440 QTY Quantity M 1 0450 SCC Scheduling conditions C 1 0460 DTM Date/time/period C 2


0480 RFF Reference C 1 0490 DTM Date/time/period C 1

0500 UNT Message trailer M 1




This section provides the description of the UN Standard Message DELJIT as defined in the 97A Directory. These segments are used in the subset defined by Benteler Automotive, NAO.



0010 UNH, Message header A service segment starting and uniquely identifying a message. The message type code for the Delivery just in time message is DELJIT.

0020 BGM, Beginning of message A segment for unique identification of the document name and its number.

0030 DTM, Date/time/period A segment specifying the date and, when relevant, the time/period for delivery of that sequence, relating to the whole message. The DTM segment must be specified at least once to identify the Delivery Just In Time document date.

0080 Segment group 2: NAD-LOC-FTX-SG3 A group of segments identifying names and addresses and their functions relevant for the whole Delivery Just In Time Message.

0090 NAD, Name and address A segment for identifying names and addresses and their functions relevant for the whole Delivery Just In Time Message.

3.3.2 Detail section

Information to be provided in the Detail section:

0150 Segment group 4: SEQ-DTM-GIR-LOC-SG5-SG7 A group of segments providing details related to the delivery sequence. All other segments in this Segment Group 4 following the SEQ segment refer to that sequence.

0160 SEQ, Sequence details A segment providing specific details related to the delivery sequence requested by the buyer or recipient of the product.

0250 Segment group 7: LIN-PIA-IMD-ALI-GIR-TDT-FTX-PAC-DTM-SG8-SG9-SG11 A group of segments providing details of the individual line items to be delivered.

0260 LIN, Line item A segment identifying the details of the product/service being delivered e.g. product identification. All other segments in the detail section following the LIN segment refer to the line item.

0270 PIA, Additional product id

A segment providing additional product identification.

0350 Segment group 8: RFF-DTM A group of segments giving references and where necessary, their dates, relating to the line item.

0360 RFF, Reference A segment for referencing document and other numbers related to the line item as specified in the LIN segment.

0430 Segment group 11: QTY-SCC-DTM-SG12 A group of segments specifying quantity related information for actual delivery.

0440 QTY, Quantity A segment to specify pertinent quantities relating to the line item.

0460 DTM, Date/time/period A segment indicating the date/time/period details relating to the quantity and schedule details in the line item.

0470 Segment group 12: RFF-DTM A group of segments giving references relating to the quantities.



0480 RFF, Reference A segment for referencing the specific product release information e.g. appointment.

0490 DTM, Date/time/period Date/time/period as applied to the referred document.



The message structure illustrates how the segments will be repeated in the Ship Schedule message to accommodate the requirements identified by Benteler Automotive, NAO.

0010.UNH Start of Shipping Schedule Message

0020.BGM Message identification

0030-1.DTM Message generation date

0090-1.NAD Supplier identification

0090-2.NAD Ship to destination identification

0160.SEQ Start of detail section

0260.[SEQ].LIN Part number identification

0270.[SEQ.LIN].PIA Customer part Engineering change level, Part Desc.

0360.[SEQ.LIN].RFF Purchase order number : line item number

0360.[SEQ.LIN].RFF Release number

0440-1.[SEQ.LIN].QTY Cumulative quantity received

0460-1.[SEQ.LIN.QTY].DTM Cumulative quantity date

0440-2.[SEQ.LIN].QTY Quantity received as of the last ASN

0480.2[SEQ.LIN.QTY].RFF SID number of last ASN received

0490.2[SEQ.LIN.QTY.RFF].DTM Date material on last ASN was received

0440-1.[SEQ.LIN].QTY Quantity to be shipped date 1

0460.[SEQ.LIN.QTY].DTM Date 1





...

0440-n.[SEQ.LIN].QTY Quantity to be shipped date n

0460.[SEQ.LIN.QTY].DTM Date n

0500.UNT End of message







Example: UNB+UNOA:2+112836044:01+002345983:01+051212:1057+39++BENTELERNAO’ A B C D E F G H


S001 SYNTAX IDENTIFIER M M A 0001 Syntax identifier M a4 : M a4 “UNOA”. B 0002 Syntax version number M n1 + M n1 Indication of the syntax version used for this

message.

S002 INTERCHANGE SENDER M M C 0004 Sender identification M an..35 : M an..35 112836044 Benteler Communication Code 0007 Identification code qualifier C an..4 : M Qualifiers to be determined by trading partner


S003 INTERCHANGE RECIPIENT M M D 0010 Recipient identification M an..35 : M an..35 Communication Code/number of the party

receiving the message. 0007 Identification code qualifier C an..4 : M Qualifiers to be determined by trading partner


S004 DATE / TIME OF PREPARATION M M E 0017 Date of preparation M n6 : M n6 YYMMDD Format. F 0019 Time of preparation M n4 + M n4 HHMM Format.


M an..14 + M an..14 A UNIQUE number within an inventory year.


C


qualifier C an2 +

H 0026 APPLICATION REFERENCE C an..14 + C an..14 “BENTELERNAO”








Segment group: none Level: 0 EDIFACT status: mandatory. Benteler status: mandatory. Maximum use: 1 per message. Benteler occurrences: 1 per message. Function: service segment starting and uniquely identifying a message. The message type code for the Delivery

just in time message is DELJIT. Benteler interchange: see remarks.

Example: UNH+1+DELJIT:D:97A:UN’ A B C D E



S009 MESSAGE IDENTIFIER M M

B 0065 Message type M an..6 : M an..6 “DELJIT”. C 0052 Message version number M an..3 : M an..3 “D”. D 0054 Message release number M an..3 : M an..3 “97A”. E 0051 Controlling agency M an..2 : M an..2 “UN”.

0057 Association assigned code C an..6 +






This part includes only the segments defined in the standard and used in the subset exchanged between Benteler and its Trading Partners. The segments are described in the same sequence as they appear in the message.

0020 BGM - BEGINNING OF MESSAGE

Segment group: none Level: 1 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 1 per message Benteler occurrences: 1 per message Function: segment for unique identification of the document name and its number. Benteler interchange: see remarks.

Example: BGM+242:::SH+002112511+9’ A B C D


C002 DOCUMENT/MESSAGE NAME C M A 1001 Document/message name, coded C an..3 : M an..3 ‘242’ = Shipping Instructions 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 :

B 1000 Document/message name C an..35 + M an..35 “SH” = Shipment based


C M

C 1004 Document/message number C an..35 : M an..35 Benteler assigned number.

1056 Version C an..9 :

1060 Revision number C an.6 +

D 1225 MESSAGE FUNCTION, CODED C an..3 + M an..3 Function of the message. For code value see below.


COMMENTS

1000 - Document message/name

SH Shipment Based - actual ship date/time is calculated by Benteler. No calculation is required on the part of the receiver. (SH = Indication for “Ship Schedule”)

1225 - Message function, coded

9 Original - This schedule replaces any previous schedule



0030 DTM - DATE/TIME/PERIOD

Segment group: none Level: 1 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 10 per message at level 1 Benteler occurrences: max. 1 per message Function: segment specifying the date and, when relevant, the time/period for delivery of that sequence, relating

to the whole message. The DTM segment is specified once to identify the document date. The date/time/period segment within other segment group(s) is only used whenever the date/time/period requires it to be logically related to another specified data item.

Benteler interchange: there will be 1 occurrences of DTM in position 0030: to specify the message issue date.

Example: DTM+137:200512120611:203’ document generation date and time A B C


C507 DATE/TIME/PERIOD M M A 2005 Date/time/period qualifier M an..3 : M an..3 “137” = Document message date B 2380 Date/time/period C an..35 : M an..35 Actual issue date of the document. C 2379 Date/time/period format qualifier C an..3 “ M an..3 “203” = CCYYMMDDHHMM.



Segment group 2: NAD-LOC-FTX-SG3

Segment group: 2 Level: 1 EDIFACT status: conditional Benteler status: mandatory Maximum use: 20 per message at level 1 Benteler occurrences: maximum 2 per message Function: group of segments identifying names and addresses and their functions relevant for the whole

Message. Benteler interchange: segment LOC is not transmitted in segment group 2.

0090 NAD - NAME AND ADDRESS

Segment group: 2 [NAD] Level: 1 EDIFACT status: mandatory if segment group 2 is used Benteler status: mandatory Maximum use: 1 per segment group 2 (max. 20) Benteler occurrences: maximum 2 per message Function: segment identifying names and addresses and their functions relevant for the whole Delivery Just In

Time Message. Identification of seller and buyer parties is recommended for the Delivery Just In Time. Benteler interchange: the message will contain 2 NAD segments as detailed below. Benteler will always transmit the

'SU' and 'ST'.

Example: NAD+SU+084559798::16’ Supplier

NAD+ST+0449::92++Opelika Plant+4401 North Park Drive+Opelika+AL+26801+US’ Ship To A B C D E F G H I

EDIFACT STANDARD DEFINITION BENTELER IMPLEMENTATION REF TAG NAME ST FT SP ST FT REMARKS

A 3035 PARTY QUALIFIER M an..3 + M an..3 “SU” = Supplier.

C082 PARTY IDENTIFICATION DETAILS C M

B 3039 Party id. Identification M an..35 : M an..35 Code identifying the supplier. 1131 Code list qualifier C an..3 :

C 3055 Code list responsible agency, coded C an..3 + M an..3 For code values see below.

C058 NAME AND ADDRESS C

C080 PARTY NAME C C

D 3036 Party name M an..35 : C an..35 Name of the party. Not always transmitted.

REST OF SEGMENT NOT USED.

Ship To


A 3035 PARTY QUALIFIER M an..3 + M an..3 “ST” = Ship To.

C082 PARTY IDENTIFICATION DETAILS C M B 3039 Party id. Identification M an..35 : M an..35 Code identifying the plant where the material

must be delivered. For code values see below. 1131 Code list qualifier C an..3 :

C 3055 Code list responsible agency, coded C an..3 + M an..3 For code values see below.


3124 Name and address line M an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 +

D C080 PARTY NAME C M 3036 Party name M an..35 : M an..35 Name of the party 3036 Party name C an..35 : 3036 Party name C an..35 : 3036 Party name C an..35 : 3036 Party name C an..35 : 3045 Party name format, coded C an..3 +

E C059 STREET C M

3042 Street and number/p.o. box M an..35 : M an..25 Address 3042 Street and number/p.o. box C an..35 : 3042 Street and number/p.o. box C an..35 : 3042 Street and number/p.o. box C an..35 +

F 3164 CITY NAME C an..35 + M an..35 City Name



G 3229 COUNTRY SUB-ENTITY IDENTIFICATION

C an..9 + M an..9

H 3251 POSTCODE IDENTIFICATION C an..9 + M an..9 Postal Code, Zip code…

I 3207 COUNTRY, CODED C an..3 “ M an..3 Country Code

CODE VALUES

3039 - Party id. identification

0442 - Hall Street 0443 - Hagen Drive 0445 - Kalamazoo 0446 - Goshen 0449 - Opelika 0452 - Spartanburg 0471 - Brampton 0585 - Hermosillo 0586 - Puebla 0587 - Saltillo

3055 - Code list responsible agency, coded

16 DUN & Bradstreet (DUNS) 92 Assigned by buyer or buyer’s agent.



Segment group 4: SEQ-DTM-GIR-LOC-SG5-SG7

Segment group: 4 Level: 1 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 9999 per message Benteler occurrences: as required Function: group of segments providing details related to the delivery sequence. All other segments in this

segment group 4 following the SEQ segment refer to that sequence. Benteler interchange: see segment description.

0160 SEQ - SEQUENCE DETAILS

Segment group: 4 [SEQ] Level: 1 EDIFACT status: mandatory when segment group is used Benteler status: mandatory Maximum use: 1 per segment group 4 (max. 9999) Benteler occurrences: 1 per segment group 4 Function: segment providing specific details related to the delivery sequence requested by the buyer or recipient

of the product. Benteler interchange: SEQ contains a value which has no further meaning for the following segments, it is only used to

allow the access to the following segments since SEQ is the trigger segment for the detail section.

Example: SEQ+6’ A


A 1245 STATUS INDICATOR, CODED C an..3 + M an..3 “6” = Agreement.

C286 SEQUENCE INFORMATION C 1050 Sequence number M an..10 : 1159 Sequence number source, coded C an..3 : 1131 Code list qualifier C an..3 : 3055 Code list responsible agency,

coded C an..3 ‘



Segment group 7: LIN-PIA-IMD-ALI-GIR-TDT-FTX-PAC-DTM-SG8-

SG9-SG11

Segment group: 7 [SEQ.SG7] Level: 2 EDIFACT status: conditional Benteler status: mandatory Maximum use: 9999 per SEQ in segment group 6 Benteler occurrences: as required Function: group of segments providing details of the individual line items to be delivered. Benteler interchange: see segment description.

0260 LIN - LINE ITEM

Segment group: 7 [SEQ.LIN] Level: 2 EDIFACT status: mandatory if segment group 7 is used Benteler status: mandatory Maximum use: 1 per segment group 7 (max. 9999 per SEQ) Benteler occurrences: 1 per segment group 7 Function: segment identifying the details of the product/service being delivered e.g. product identification. All

other segments in the detail section following the LIN segment refer to the line item. Benteler interchange: see remarks.

Example: LIN+++612876:IN’ A B


1082 LINE ITEM NUMBER C n..6 +

1229 ACTION REQUEST/ NOTIFICATION, CODED

C an..3 +

C212 ITEM NUMBER IDENTIFICATION C M A 7140 Item number C an..35 : M an..35 Benteler assigned part number. B 7143 Item number type, coded C an..3 : M an..3 “IN” = Buyer’s item number. 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +

C829 SUB-LINE INFORMATION C 5495 Sub-line indicator, coded C an..3 : 1082 Line item number C n..6 +

1222 CONFIGURATION LEVEL C n..2 +

7083 CONFIGURATION, CODED C an..3 ‘



0270 PIA - ADDITIONAL PRODUCT ID

Segment group: 7 [SEQ.LIN.PIA] Level: 3 EDIFACT status: conditional Benteler status: mandatory Maximum use: 10 per LIN in segment group 7 Benteler occurrences: 1 per preceding LIN Function: segment providing additional product identification. Benteler interchange: see remarks.

Example: PIA+1+A:EC+60758-AD GM-15874928:PD’ Change Level

PIA+1+--:EC +60758-AD GM-15874928:PD’ No Change Level

PIA+1+A:EC` Change Level, No additional description A B C D E


A 4347 PRODUCT ID. FUNCTION QUALIFIER

M an..3 + M an..3 “1” = Additional identification

C212 ITEM NUMBER IDENTIFICATION M M B 7140 Item number C an..35 : M an..35 Identification of the change level C 7143 Item number type, coded C an..3 : M an..3 “EC” = Engineering change level. 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +

C212 ITEM NUMBER IDENTIFICATION C

D 7140 Item number C an..35 : O an..22 Part Number Description E 7143 Item number type, coded C an..3 : O an..3 ‘PD’ Additional Part Description 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +

C212 ITEM NUMBER IDENTIFICATION C 7140 Item number C an..35 : 7143 Item number type, coded C an..3 : 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +


7140 Item number C an..35 : 7143 Item number type, coded C an..3 : 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +

C212 ITEM NUMBER IDENTIFICATION C 7140 Item number C an..35 : 7143 Item number type, coded C an..3 : 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 ‘

COMMENTS

7140 - Item number – ‘EC’

Depending on the circumstances the composite may contain a – if a change level has not yet been assigned to the part

7140 - Item number – ‘PD’

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.



Segment group 8: RFF-DTM

Segment group: 8 Level: 3 EDIFACT status: conditional Benteler status: mandatory Maximum use: 10 per message at level 1 Benteler occurrences: 2 per message Function: group of segments giving references only relevant to the specified party rather than the whole

message, e.g. order number. Benteler interchange: only RFF is transmitted in segment group 8

0360 RFF - REFERENCE

Segment group: 8 [SEQ,LIN,RFF] Level: 3 EDIFACT status: mandatory if segment group 08 is used Benteler status: mandatory Maximum use: 1 per segment group 8 (max. 5) Benteler occurrences: 1 per segment group 8 Function: segment for referencing document and other numbers related to the line item as specified in the LIN

segment. Benteler interchange: see segment group description

Example: RFF+ON:5500001950:20’ A B C


C506 REFERENCE M M

A 1153 Reference qualifier M an..3 : M an..3 “ON” = Order number.

B 1154 Reference number C an..35 : M an..35 Purchase Order number relevant for the article defined in the preceding LIN.

C 1156 Line number C an..6 : M An..5 Purchase Order line item Number 4000 Reference version number C an..35 ‘


Description: see description of 1st occurrence of segment group 8.

Example: RFF+AAN:35’ A B

EDIFACT STANDARD DEFINITION GM IMPLEMENTATION


C506 REFERENCE M M A 1153 Reference qualifier M an..3 : M an..3 “AAN” = Release number. B 1154 Reference number C an..35 : M an..35 This number corresponds to the release

number in the DELFOR. 1156 Line number C an..6 : 4000 Reference version number C an..35 ‘



Use of segment group 11 in message from Benteler

There may be up to 3 different occurrences of segment group 11:

CALCULATION INFORMATION Cumulative quantity received [qualifier 6063 = 70] Quantity received on the last ASN [qualifier 6063 = 48]

SHIPPING INFORMATION Quantity to be shipped [qualifier 6063 = 1]

Each type of occurrence will be detailed separately.



CALCULATION INFORMATION

Segment group 11: QTY-SCC-DTM-SG12

Segment group: 11 [SEQ.LIN.SG11] Level: 3 EDIFACT status: conditional Benteler status: mandatory Maximum use: 100 per LIN in segment group 07 Benteler occurrences: as required. Function: group of segments specifying quantity related information for actual delivery. Benteler interchange: see description of different occurrences of segment group 11.

SEGMENT GROUP 11

CUMULATIVE QUANTITY RECEIVED

0440.[SEQ.LIN].QTY Cumulative quantity received

0460.[SEQ.LIN.QTY].DTM Cumulative quantity start date

0440 QTY - QUANTITY

Segment group: 11 [SEQ.LIN.QTY] Level: 3 EDIFACT status: mandatory when segment group 11 is used Benteler status: mandatory Maximum use: 1 per segment group 11 (max. 100 per LIN) Benteler occurrences: 1 per segment group 11 Function: segment to specify pertinent quantities relating to the line item. Benteler interchange:

Example: QTY+70:99999:C62’ A B C


C186 QUANTITY DETAILS M M A 6063 Quantity qualifier M an..3 : M an..3 ‘70’ = Cumulative quantity received. B 6060 Quantity M n..15 : M n..15 Cumulative quantity received C 6411 Measure unit qualifier C an..3 ‘ M an..3 For code value see UN/ECE Recommendation

no. 20. (e.g. piece = C62)


Segment group: 11 [SEQ.LIN.QTY.DTM] Level: 4 EDIFACT status: conditional Benteler status: mandatory Maximum use: 2 per QTY Benteler occurrences: 1 per QTY Function: segment providing the date/time/period of the reference. Benteler interchange:

Example: DTM+51:20051101:102’ Start date A B C

EDIFACT STANDARD DEFINITION Benteler IMPLEMENTATION


Start date

C507 DATE/TIME/PERIOD M M A 2005 Date/time/period qualifier M an..3 : M an..3 “51” = Cumulative quantity date.

B 2380 Date/time/period C an..35 : M an..35 Date of cumulative quantity C 2379 Date/time/period format qualifier C an..3 ‘ M an..3 “102” = CCYYMMDD.



SEGMENT GROUP 11

LAST QUANTITY RECEIVED

0440.[SEQ.LIN].QTY Last quantity received

0480.[SEQ.LIN.QTY].RFF Document reference number

0490.[SEQ.LIN.QTY.RFF].DTM Document date

0440 QTY - QUANTITY

Description: see description of 1st occurrence of segment group 11.



C186 QUANTITY DETAILS M M A 6063 Quantity qualifier M an..3 : M an..3 “48” = Last quantity received.

B 6060 Quantity M n..15 : M n..12 Quantity received C 6411 Measure unit qualifier C an..3 ‘ M an..3 For code value see UN/ECE Recommendation

no. 20.


Segment group: 12 [SEQ.LIN.QTY,SG11] Level: 4 EDIFACT status: conditional Benteler status: conditional Maximum use: 5 per QTY in segment group 11 Benteler occurrences: as required. Function: group of segments to identify person, function, department and appropriate numbers to whom

communication should be directed Benteler interchange:


Segment group: 12 [RFF] Level: 4 EDIFACT status: mandatory if segment group 12 is used Benteler status: conditional Maximum use: 1 per segment group 1 (max. 10) Benteler occurrences: 1 per segment group 12 Function: segment for referencing the specific product release information e.g. SID number. Benteler interchange:

Example: RFF+SI:20303’ A B


C506 REFERENCE M M A 1153 Reference qualifier M an..3 : M an..3 “SI” = SID number. B 1154 Reference number C an..35 : M an..35 SID number of the last ASN received. 1156 Line number C an..6 : 4000 Reference version number C an..35 ‘




EDIFACT status: mandatory if segment group 1 is used Benteler status: conditional Description: see description of 1

st occurrence of segment group 11.

Example: DTM+50:20051101:102’ Received date A B C


C507 DATE/TIME/PERIOD M M A 2005 Date/time/period qualifier M an..3 : M an..3 “50” = Date received B 2380 Date/time/period C an..35 : M an..35 Date material for SID in preceeding RFF was

received C 2379 Date/time/period format qualifier C an..3 ‘ M an..3 “102” = CCYYMMDD.



SHIPPING INFORMATION

SEGMENT GROUP 11

QUANTITY TO BE SHIPPED

0440.[SEQ.LIN].QTY Quantity to be shipped

0460.[SEQ.LIN.QTY].DTM Requested shipment date/time

0440 QTY - QUANTITY

Segment group: 11 [SEQ.LIN.QTY] Level: 3 EDIFACT status: mandatory when segment group 11 is used Benteler status: mandatory Maximum use: 1 per segment group 11 (max. 100 per LIN) Benteler occurrences: 1 per segment group 11 Function: segment to specify pertinent quantities relating to the line item. Benteler interchange:




C186 QUANTITY DETAILS M M

A 6063 Quantity qualifier M an..3 : M an..3 “1” = Discrete Quantity

B 6060 Quantity M n..15 : M n..12 Actual quantity to be shipped of the product identified in the preceding LIN.

C 6411 Measure unit qualifier C an..3 ‘ M an..3 For code value see UN/ECE Recommendation no. 20.


Segment group: 11 [SEQ.LIN.QTY.DTM] Level: 4 EDIFACT status: conditional Benteler status: mandatory Maximum use: 2 per QTY Benteler occurrences: 1 per preceding QTY Function: segment providing the date/time/period of the reference. Benteler interchange:

Example: DTM+10:199701010600:203’ A B C



C507 DATE/TIME/PERIOD M M A 2005 Date/time/period qualifier M an..3 : M an..3 “10” = Shipment date/time, requested.

B 2380 Date/time/period C an..35 : M an..35 Requested shipment date. C 2379 Date/time/period format qualifier C an..3 ‘ M an..3 “203” = CCYYMMDDHHMM.



3.6. EXAMPLE OF MESSAGE

Following example is only illustrative and does not necessarily reflect an existing situation. It

MAY NEVER be used as a basis for programming or implementing this message.

UNB+UNOA:2+112836044:01+150146817:01+051212:0735+66++BENTELERNAO’ UNH+1+DELJIT:D:97A:UN’ BGM+242+:::SH+002111795+9’ DTM+137:200512120733:203’ Document issue date and time NAD+SU+150146817::16’ Supplier ID

NAD+ST+0446::92++Goshen Plant+635 Sprucewood+Goshen+IN+48326+US’ Ship to Destination SEQ+6’

LIN+++35674:IN’ Buyers Part Number PIA+1+F:EC+60758-AD GM-15874928:PD’ Engineering Change Level, Part description RFF+ON+5500001822:10’ Purchase Order number : Line item Number RFF+AAN+21’ Release Number

QTY+70:15000:C62’ Cum. quantity received DTM+51:20051201:102’ Date of cum. quantity QTY+48:2000:C62’ Quantity Receive on the last ASN

RFF+SI+20303’ Last SID/ASN number received DTM+50:20051201:102’ Date material on last ASN received QTY+1:2000:C62’ Quantity to be delivered

DTM+10:200512120700:203’ Requested shipment date and time 1 QTY+1:2500:C62’ Quantity to be delivered DTM+10:200512130700:203’ Requested shipment date and time 2

QTY+1:3000:C62’ Quantity to be delivered DTM+10:200512140700:203’ Requested shipment date and time 3 QTY+1:3500:C62’ Quantity to be delivered

DTM+10:200512150700:203’ Requested shipment date and time 4 UNT+24+1’ UNZ+1+66’

For ease of reading the message has been shown with each segment type on a separate line, which will not be the case when the message is normally transmitted

BENTELER AUTOMOTIVE NAO EDI IMPLEMENTATION GUIDELINES EDIFACT DESADV

NAO_LO-023 Implementation Guideline DESADV Version 1.1 30-NOV-2009 1

Despatch Advice EDIFACT DESADV D.97A

Version 1.1



Document Change Log Version Date Description


1.1 30-NOV-2009 Remove reference to unique in a year in the BGM remarks for TAG 1004.



0. TABLE OF CONTENT

0. TABLE OF CONTENT ......................................................................................................3

1. INTRODUCTION....................................................................................................................4

2. MESSAGE DEFINITION ........................................................................................................4

2.1. FUNCTIONAL DEFINITION .................................................................................................4 2.2. PRINCIPLES........................................................................................................................4 2.3. REFERENCES.....................................................................................................................4 2.4. FIELD OF APPLICATION.....................................................................................................5

3. MESSAGE DESCRIPTION ....................................................................................................6

3.1. INTRODUCTION..................................................................................................................6 3.1.1. How to read the documentation .......................................................................................6 3.1.2. General remarks...............................................................................................................7 3.2. SEGMENT TABLE ...............................................................................................................7 3.3. MESSAGE STANDARD DESCRIPTION .............................................................................9 3.4. MESSAGE STRUCTURE...................................................................................................11 3.5. DATA SEGMENTS DESCRIPTION....................................................................................15 3.6. EXAMPLE OF MESSAGE ..................................................................................................28



1. INTRODUCTION

This document provides the specific description of a subset of the EDIFACT DESADV D97.A message to be used between a Trading Partner and Benteler Automotive, NAO.


This document provides the definition of an Advanced Shipping Notification (ASN) or Despatch Advice Message, based on the EDIFACT DESADV D97.A, to be used in Electronic Data Interchange (EDI) between a Trading Partner and Benteler Automotive, NAO.


The ASN/Despatch Advice message is a message from a Benteler NAO Supplier to the relevant Benteler application. It gives information concerning material despatched to a Benteler NAO location as instructed by a previously received Delivery Instruction or Shipping Schedule message and in line with the conditions set out in the contract or order.

2.2. PRINCIPLES

The ASN/Despatch Advice message intends to:

• advise the recipient (Consignee) of the despatch of goods and to provide the details regarding the content of the consignment.

• allow the recipient (Consignee) to track material shipments and to prepare the physical receipt of the consignment.

An ASN/Despatch Advice message can relate to:

• different articles which may be packed differently (as instructed or agreed).

The ASN/Despatch Advice message must always include the transportation information (e.g., means of transport, etc.) related to the load advised.

As the information transmitted in the ASN/Despatch Advice is vital to ensure an efficient receipt of

the material at the receiving plant. Therefore it is mandatory that the ASN/Despatch Advice is

sent immediately after the departure of the material.

2.3. REFERENCES


• the message structure as defined by EDIFACT for the UNSM Despatch Advice Message DESADV as published in the UN/EDIFACT D97.A Directory.


Benteler NAO has opted for the EDIFACT D97.A Directory and consistently uses this directory for all its EDIFACT messages. Although the AVIEXP subset defined by ODETTE has been based on the EDIFACT D96.A Directory, the subset defined by Benteler NAO and described in this document follows as close as possible the structure of the ODETTE subset.




The following definition of an ASN/Despatch Advice Message in EDIFACT format is applicable for the interchange of shipping instructions issued by Benteler Automotive, NAO for material deliveries to one or more Benteler Automotive, NAO Operations.




Following pages contain a full description of the EDIFACT DESADV D97.A message as implemented by Benteler NAO. The official EDIFACT segment description is complemented with remarks pertaining to the specific requirements for an interchange with Benteler NAO. Those remarks contain specific code values used, additional information on the values shown in a specific field, etc.

3.1. INTRODUCTION


All segments in the subset used by Benteler NAO are described in the following pages. The segment description is to be read as follows:






see remarks.


� EDIFACT STANDARD DEFINITION BENTELER IMPLEMENTATION


C002 DOCUMENT/MESSAGE NAME C C A 1001 Document/message name, coded C an..3 : C an..3 '351’ = Despatch Advice 1131 Code list qualifier C an..3 : 3055 Code list responsible agency,

coded C an..3 :

1000 Document/message name C an..35 +


C

B 1004 Document/message number C an..35 : C an..35 Benteler assigned release number 1056 Version C an..9 : 1060 Revision number C an..6 +

C 1225 MESSAGE FUNCTION, CODED C an..3 + C an..3 Function of the message. For code values see below.


COMMENTS

CODE VALUES

LEGEND



� status of the segment: as defined by EDIFACT and by Benteler .

� number of occurrences of the segment: as defined by EDIFACT and as used by Benteler .

� description of the function of the segment as defined by EDIFACT and as used by Benteler .



� example of the segment as it may appear in an interchange. This example is only illustrative

and does not necessarily represent an actual situation. It should NOT be used as a basis to implement this message.

� definition of the segment content as defined by EDIFACT and as implemented by Benteler .








• remarks on the specific use of the data element in the interchange with Benteler .

Shaded areas in the Benteler description mean that the data elements is not used by Benteler

the segment description can be followed by:

• comments providing more information regarding specific data elements and how they must be used and/or understood in messages from Benteler .




Dates Unless otherwise specified in the field explanation in the documentation, dates are always

expressed as CCYYMMDD (qualifier 2379 = 102).

Times

Unless otherwise specified in the field explanation in the documentation, times are always

expressed as HHMM.

3.2. SEGMENT TABLE

The following table shows the segments defined for the EDIFACT UNSM DESADV D97.A Despatch Advice message. Shaded areas identify the segments that are not used in the subset of DESADV used by Benteler.


0010 UNH Message header M 1 0020 BGM Beginning of message M 1 0030 DTM Date/time/period C 10 0040 ALI Additional information C 5 0050 MEA Measurements C 5 0060 MOA Monetary amount C 5




0110 NAD Name and address M 1 0120 LOC Place/location identification C 10








0200 TOD Terms of delivery or transport M 1 0210 LOC Place/location identification C 5 0220 FTX Free text C 5


0240 TDT Details of transport M 1 0250 PCD Percentage details C 6


0270 LOC Place/location identification M 1 0280 DTM Date/time/period C 10


0300 EQD Equipment details M 1 0310 MEA Measurements C 5 0320 SEL Seal number C 25 0330 EQA Attached equipment C 5


0350 HAN Handling instructions M 1 0360 FTX Free text C 10


0380 CPS Consignment packing sequence M 1 0390 FTX Free text C 5


0410 PAC Package M 1 0420 MEA Measurements C 10 0430 QTY Quantity C 10


0450 HAN Handling instructions M 1 0460 FTX Free text C 10


0480 PCI Package identification M 1 0490 RFF Reference C 1 0500 DTM Date/time/period C 5 0510 GIR Related identification numbers C 99


0530 GIN Goods identity number M 1 0540 DLM Delivery limitations C 10


0560 LIN Line item M 1 0570 PIA Additional product id. C 10 0580 IMD Item description C 25 0590 MEA Monetary amount C 10 0600 QTY Quantity C 10 0610 ALI Additional information C 10 0620 GIN Goods identity number C 100 0630 GIR Related identification numbers C 100 0640 DLM Delivery limitations C 100 0650 DTM Date/time/period C 5 0660 NAD Name and address C 5 0670 TDT Details of transport C 1 0680 HAN Handling instructions C 20 0690 FTX Free text C 99 0700 MOA Monetary amount C 5




0720 RFF Reference M 1 0730 NAD Name and address C 1 0740 CTA Contact information C 1 0750 DTM Date/time/period C 1


0770 DGS Dangerous goods M 1 0780 QTY Quantity C 1 0790 FTX Free text C 5


0810 LOC Place/location identification M 1 0820 NAD Name and address C 1 0830 DTM Date/time/period C 1 0840 QTY Quantity C 1


0860 SGP Split goods placement M 1 0870 QTY Quantity C 10


0890 PCI Package identification M 1 0900 DTM Date/time/period C 5 0910 MEA Measurements C 10 0920 QTY Quantity C 1


0940 GIN Goods identity number M 1 0950 DLM Delivery limitations C 100


0970 HAN Handling instructions M 1 0980 FTX Free text C 5 0990 GIN Goods identity number C 1000


1010 QVR Quantity variances M 1 1020 DTM Date/time/period C 5

1030 CNT Control total C 5 1040 UNT Message trailer M 1


This section provides the description of the UN Standard Message DESADV as defined in the 97.A Directory. These segments are used in the subset defined by Benteler Automotive NAO.



0010 UNH, Message header A service segment starting and uniquely identifying a message. The message type code for the Despatch advice message is DESADV.

0020 BGM, Beginning of message A segment for unique identification of the Despatch Advice document, by means of its name and its number.

0030 DTM, Date/time/period Date/time/period related to the whole message. The DTM segment must be specified at least once to identify the Despatch Advice date.

0050 MEA, Measurements A segment specifying the weight and volume of the consignment.



0100 Segment group 2: NAD-LOC-SG3-SG4 A group of segments identifying names, addresses, locations, and required supporting documents relevant to the whole Despatch Advice.

0110 NAD, Name and address A segment for identifying names, addresses, and their functions relevant to the whole Despatch Advice. Identification of the parties involved is recommended for the Despatch Advice message, and is to be given in the NAD segment.

0230 Segment group 6: TDT-PCD-SG7 A group of segments specifying details of the mode and means of transport and date/time of departure and destination relevant to the whole despatch advice.

0240 TDT, Details of transport A segment specifying the carriage, and the mode and means of transport of the goods being despatched.

0290 Segment group 8: EQD-MEA-SEL-EQA-SG9 A group of segments providing information relative to the equipment used for the transportation of goods relevant to the whole despatch advice.

0300 EQD, Equipment details A segment to define fixed information regarding equipment used in conjunction with the whole despatch advice, and if required, to indicate responsibility for supply of the equipment.



0370 Segment group 10: CPS-FTX-SG11-SG15 A group of segments providing details of all package levels and of the individual despatched items contained in the consignment. This segment group provides the capability to give the hierarchical packing relationships. The group defines a logical top-down order structure. The lowest level package information of the hierarchy is followed by the detail product information.

0380 CPS, Consignment packing sequence A segment identifying the sequence in which packing of the consignment occurs, e.g. boxes loaded onto a pallet.

0550 Segment group 15: LIN-PIA-IMD-MEA-QTY-ALI-GIN-GIR-DLM-DTM-NAD-TDT-HAN-FTX-MOA-

SG16-SG17-SG18-SG19-SG20-SG23 A group of segments providing details of the individual despatched items.

0560 LIN, Line item A segment identifying the product being despatched. All other segments in the detail section following the LIN segment refer to that line item.

0570 PIA, Additional product id A segment providing additional product identification.

0600 QTY, Quantity A segment to give quantity information concerning the product.

0710 Segment group 16: RFF-NAD-CTA-DTM A group of segments to give reference numbers and dates.

0720 RFF, Reference A segment identifying documents related to the line item.

3.3.3 Summary section

Information to be provided in the Summary section:





The message structure illustrates how the segments can be repeated in the Despatch Advice message to accommodate the requirements identified by Benteler NAO.

0010.UNH Start of Despatch Advice Message


0030.DTM Message generation date/time

0050.MEA Number of lading units

0110-1.NAD Ship To destination Identification

0110-2.NAD Supplier identification

0240.TDT Transport details

0300.EQD Equipment details

0380-1.CPS Detail trigger segment 1

0560.1[CPS].LIN Part number 1

0570.[CPS.LIN].PIA Customer part Engineering Change Level

0600.[CPS.LIN].QTY Despatched quantity for part number 1

0720.[CPS.LIN].RFF Purchase order and Line item number for part 1


0560.[CPS].LIN Part number 2

0570.[CPS.LIN].PIA Customer part Engineering Change Level

0600.[CPS.LIN].QTY Despatched quantity for part number 2

0720.[CPS.LIN].RFF Purchase order and Line item number for part 2


... Details for part number 3


NOTE:

All data elements marked ”M” for Mandatory in the ”ST” field of the Benteler implementation

must be included in the message. Missing or incorrect entries will result in the rejection of

the message.







Example: UNB+UNOA:2+003123789:01+112836044:01+051212:0735+1234’ A B C D E F G


S001 SYNTAX IDENTIFIER M M A 0001 Syntax identifier M a4 : M a4 ”UNOA”. B 0002 Syntax version number M n1 + M n1 Indication of the syntax version used for this

message. Benteler uses EDIFACT syntax version 2

S002 INTERCHANGE SENDER M M C 0004 Sender identification M an..35 : M an..35 Communication Code/Mailbox number of the

party originating the message. 0007 Identification code qualifier C an..4 : C an..4 Qualifiers to be determined by trading partner


S003 INTERCHANGE RECIPIENT M M D 0010 Recipient identification M an..35 : M an..35 ‘112836044’ Benteler Communication Code 0007 Identification code qualifier C an..4 : C an..4 ‘01’ Qualifier. 0014 Routing address C an..14 +

S004 DATE / TIME OF PREPARATION M M E 0017 Date of preparation M n6 : M n6 YYMMDD Format.

F 0019 Time of preparation M n4 + M n4 HHMM Format.


M an..14 + M an..14 Reference number assigned by the sender of the message. This number must uniquely

identify each interface and must be UNIQUE within an inventory year.


C


qualifier C an2 +

0026 APPLICATION REFERENCE C an..14 +








Segment group: none Level: 0 EDIFACT status: mandatory. Benteler status: mandatory. Maximum use: 1 per message. Benteler occurrences: 1 per message. Function: service segment starting and uniquely identifying a message. The message type code for the Despatch

Advice message is DESADV. Benteler interchange: see remarks.

Example: UNH+1+DESADV:D:97A:UN’ A B C D E



S009 MESSAGE IDENTIFIER M M B 0065 Message type M an..6 : M an..6 ”DESADV” C 0052 Message version number M an..3 : M an..3 ”D” D 0054 Message release number M an..3 : M an..3 ”97A” E 0051 Controlling agency M an..2 : M an..2 ”UN” 0057 Association assigned code C an..6 +




Segment group: none Level: 0 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 1 per message Benteler occurrences: 1 per message Function: service segment ending a message, giving the total number of segments in the message and the control

reference number of the message. Benteler interchange:









Segment Group: none Level: 0 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 1 Benteler occurrences: 1 per interchange Function: service segment ending an interchange and giving the number of messages contained in the interchange

as well as the Interchange Control Reference number. Benteler interchange:





M An..14 ‘ M an..14 Value must be the same as 0020 - Interchange Control Reference in UNB.




This part includes only the segments defined in the standard and used in the subset exchanged between the Trading Partners and Benteler. The segments are described in the same sequence as they appear in the message.

NOTE:

All data elements marked ”M” for Mandatory in the ”ST” field of the Benteler implementation

must be included in the message. Missing or incorrect entries will result in the rejection of

the message.


Segment group: none Level: 1 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 1 per message Benteler occurrences: 1 per message Function: segment for unique identification of the Despatch Advice document, by means of its name and its number. Benteler interchange:

Example: BGM++123456789+9’ A B



C002 DOCUMENT/MESSAGE NAME C 1001 Document/message name, coded C An..3 : 1131 Code list qualifier C An..3 : 3055 Code list responsible agency, coded C An..3 : 1000 Document/message name C An..35 +


C M

A 1004 Document/message number C An..35 : M an..35 A unique control number, commonly called a Shipment Identification Number (SID), assigned by the original shipper to identify a specific shipment. This unique control number cannot be repeated. This number must be referenced on both the packing list and the bill of lading as the Shipment Identification

Number (SID). Maximum length is 9

characters

1056 Version C An..9 :

1060 Revision number C An.6 +

B 1225 MESSAGE FUNCTION, CODED C An..3 + M an..3 Function of the message. For code values see below.

4343 RESPONSE TYPE, CODED C An..3 ‘

CODE VALUES

1225 - Message function, coded

9 Original Initial transmission related to a given transaction. The issuer's first transmission of a message for a particular SID (1004). Benteler does not support the replace or cancel function codes.

NOTE: THE TIMING OF ASN TRANSMISSION IS CRITICAL. DELETIONS, CORRECTIONS, AND ADDITIONS

CAN ONLY BE PROCESSED PRIOR TO THE RECEIPT OF SHIPMENT. WHEN IN DOUBT, CHECK

WITH YOUR MATERIAL CONTACT.




Segment group: none Level: 1 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 10 per message at level 1 Benteler occurrences: max. 2 per message Function: segment specifying the date/time/period related to the whole message. The DTM segment must be

specified at least once to identify the Despatch Advice date. Benteler interchange: there may be max. 2 occurrences of DTM in position 0030: to specify the message issue date, and to

specify the despatch date. Two occurrences are mandatory in the messages exchanged with

Benteler.

Example: DTM+137:200503051400:203’ Document generation

DTM+11 :200503051500:203’ Despatch date/time A B C


Document generation date. MANDATORY - must be transmitted.

C507 DATE/TIME/PERIOD M M A 2005 Date/time/period qualifier M an..3 : M an..3 ”137” = Document/message date/time. B 2380 Date/time/period C an..35 : M an..35 Date/time when the document is sent to the

customer / receiver. . C 2379 Date/time/period format qualifier C an..3 ” M an..3 ”203” = CCYYMMDDHHMM.

Despatch date/time. MANDATORY - must be transmitted.

C507 DATE/TIME/PERIOD M M A 2005 Date/time/period qualifier M an..3 : M an..3 ”11” = Despatch date and or time. B 2380 Date/time/period C an..35 : M an..35 Date/time when the pick-up carrier leaves the

supplier / sender’s ship location with the goods.

C 2379 Date/time/period format qualifier C an..3 ‘ M an..3 ”203” = CCYYMMDDHHMM.



0050 MEA - MEASUREMENTS

Segment group: none Level: 1 EDIFACT status: conditional Benteler status: mandatory Maximum use: 5 per message at level 1 Benteler occurrences: max. 1 per message Function: segment specifying the weight and volume of the consignment.

Benteler interchange: there MUST be 1 occurrence of MEA in position 0050 to specify the number of lading units with the qualifier of C62 in data element 6411.

Example: MEA+AAX+SQ+C62:99’ Number of lading units A B C D


Shipped Quantity MANDATORY - must be transmitted.

A 6311 MEASUREMENT PURPOSE QUALIFIER

M an..3 + M an..3 ”AAX” = Consignment measurements.

C502 MEASUREMENT DETAILS C C B 6313 Property measured, coded C an..3 : M an..3 ”SQ” = Total number of Lading units. 6321 Measurement significance, coded C an..3 : 6155 Measurement attribute identification C an..17 : 6154 Measurement attribute C an..70 +

C174 VALUE/RANGE C C 6411 Measure unit qualifier M an..3 : M an..3 For code see UN/ECE Recommendation Nr 20

D 6314 Measurement value C an..18 : M an..18 Quantity


NOTE: The recommended value for data element 6411 is C62, when code value in data element 6313 is SQ.



Segment group 2: NAD-LOC-SG3-SG4

Segment group: 2 Level: 1 EDIFACT status: conditional Benteler status: mandatory Maximum use: 10 per message at level 1 Benteler occurrences: maximum 2 per message Function: group of segments identifying names, addresses, locations, and required supporting documents relevant

to the whole Despatch Advice. Benteler interchange: see segment description.


Segment group: 02 [NAD] Level: 1 EDIFACT status: mandatory if segment group 02 is used Benteler status: mandatory Maximum use: 1 per segment group 02 (max. 10) Benteler occurrences: 2 per segment group 2 Function: segment for identifying names, addresses, and their functions relevant to the whole Despatch Advice. Benteler interchange: Benteler always requires the transmission of the two occurrences detailed below. This information

was also included in the DELFOR and/or DELJIT previously transmitted by Benteler.

Example: NAD+ST+0452::92’ Ship To

NAD+SU+876543210::16’ Supplier A B C


Ship To. MANDATORY - must always be transmitted.

A 3035 PARTY QUALIFIER M an..3 + M an..3 ”ST” = Ship To


B 3039 Party id. Identification M an..35 : M an..35 Code identifying the plant where the material must be delivered. For code value, see below.

1131 Code list qualifier C an..3 : C 3055 Code list responsible agency, coded C an..3 + M an..3 For code value, see below.

C058 NAME AND ADDRESS C 3124 Name and address line M an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 +

C080 PARTY NAME C 3036 Party name M an..35 : 3036 Party name C an..35 : 3036 Party name C an..35 : 3036 Party name C an..35 : 3036 Party name C an..35 : 3045 Party name format, coded C an..3 +

C059 STREET C 3042 Street and number/p.o. box M an..35 : 3042 Street and number/p.o. box C an..35 : 3042 Street and number/p.o. box C an..35 : 3042 Street and number/p.o. box C an..35 +

3164 CITY NAME C an..35 +

3229 COUNTRY SUB-ENTITY IDENTIFICATION

C an..9 +

3251 POSTCODE IDENTIFICATION C an..9 +

3207 COUNTRY, CODED C an..3 ‘



0110 NAD - CONTINUED

Supplier MANDATORY - must always be transmitted.

A 3035 PARTY QUALIFIER M an..3 + M an..3 ”SU” = Supplier.


B 3039 Party id. Identification M an..35 : M an..35 Code identifying the supplier.

1131 Code list qualifier C an..3 :

C 3055 Code list responsible agency, coded C an..3 + M an..3 For code value, see below.

C058 NAME AND ADDRESS C +

C080 PARTY NAME C +

C059 STREET C +



C an..9 +


3207 COUNTRY, CODED C an..3 ‘

CODE VALUES

3039 - Party id. identification [NAD 1st and 2

nd occurrence]

Code Value has to be in line with the information given in DELFOR/DELJIT.


16 DUN & Bradstreet (DUNS)

92 Assigned by buyer or buyer’s agent.



Segment group 6: TDT-PCD-SG7

Segment group: 6 Level: 1 EDIFACT status: conditional Benteler status: mandatory Maximum use: 10 per message at level 1 Benteler occurrences: max. 2 per message Function: group of segments specifying details of the mode and means of transport and date/time of departure and

destination relevant to the whole despatch advice. Benteler interchange: only segment TDT is used in segment group 6.

0240 TDT - DETAILS OF TRANSPORT

Segment group: 6 [TDT] Level: 1 EDIFACT status: mandatory if segment group 6 is used Benteler status: mandatory Maximum use: 1 per segment group 6 (max. 10) Benteler occurrences: 1 per segment group 6 Function: segment specifying the carriage, and the mode and means of transport of the goods being despatched. Benteler interchange:

Example: TDT+12++M++RYDD::182’ A B C D


A 8051 TRANSPORT STAGE QUALIFIER M an..3 + M an..3 For code value, see below.

8028 CONVEYANCE REFERENCE NR C an..17 +

C220 MODE OF TRANSPORT C M

B 8067 Mode of transport, coded C an..3 : M an..3 For code value, see below.

8066 Mode of transport C an..17 +

C228 TRANSPORT MEANS C

8179 Type of means of transport id. C an..8 :

8178 Type of means of transport C an..17 +

C040 CARRIER C M

C 3127 Carrier identification C an..17 : M an..17 Code identifying the carrier. The 4 character SCAC-code is mandatory.

1131 Code list qualifier C an..3 : D 3055 Code list responsible agency, coded C an..3 : M an..3 For code value, see below.

3128 Carrier name C an..35 +

8101 TRANSIT DIRECTION, CODED C an..3 +

C401 EXCESS TRANSPORTATION INFORMATION

C

8457 Excess transportation reason, coded M an..3 :

8459 Excess transportation responsibility, coded

M an..3 :

7130 Customer authorization number C an..17 +

C222 TRANSPORT IDENTIFICATION C 8213 Id. of means of transport

identification C an..9 :

1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 : 8212 Id. of the means of transport C an..35 :

8453 Nationality of means of transport, coded

C an..3 +

8281 TRANSPORT OWNERSHIP, CODED

C an..3 ‘

CODE VALUES

8051 - Transport stage qualifier

12 At departure Transport by which goods are moved from the place of departure. Pick-up SCAC.




182 Standard Carrier Alpha Code (SCAC)

8067 - Mode of transport, coded

General Codes to be used for Benteler, more detailed codes may need to be implemented on request of Benteler Implementation Plant: General codes used by Benteler listed below. To verify mode of transport, contact the Benteler Plant directly.

A Air

AC Air Charter

AE Air Express

C Consolidation

D Parcel Post

E Expedited Truck

G Piggyback

GS Progressive pick-up (milk run)

H Customer Pick-up

LT Less than trailer load

M Motor (full truck)

R Rail

SE Sea/Air

SR Supplier Truck

SS Steamship

T Best way

TC (Taxi) Cab

U Private Parcel Service

VE Vessel, Ocean

W Inland Waterway



Segment group 8: EQD-MEA-SEL-EQA-SG9

Segment group: 8 Level: 1 EDIFACT status: conditional Benteler status: mandatory Maximum use: 10 per message at level 1 Benteler occurrences: max. 10 per message Function: group of segments providing information relative to the equipment used for the transportation of goods

relevant to the whole despatch advice. Benteler interchange: only segment EQD is used in segment group 8.

0300 EQD - EQUIPMENT DETAILS

Segment group: 8 [EQD] Level: 1 EDIFACT status: mandatory if segment group 08 is used Benteler status: mandatory Maximum use: 1 per segment group 8 (max. 10) Benteler occurrences: 1 per segment group 8 Function: segment to define fixed information regarding equipment used in conjunction with the whole despatch

advice, and if required, to indicate responsibility for supply of the equipment. Benteler interchange: see remarks.

Example: EQD+TE+A123456’ A B


A 8053 EQUIPMENT QUALIFIER M an..3 + M an..3 For code value see below.

C237 EQUIPMENT IDENTIFICATION C M

B 8260 Equipment identification number C an..17 : M an..17 Used to identify equipment number, such as railcar or trailer number including initials.

1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 : 3207 Country, coded C an..3 +

C224 EQUIPMENT SIZE AND TYPE C 8155 Equipment size and type id. C an..10 : 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 : 8154 Equipment size and type C an..35 +

8077 EQUIPMENT SUPPLIER, CODED C an..3 +

8249 EQUIPMENT STATUS, CODED C an..3 +

8169 FULL/EMPTY INDICATOR, CODED C an..3 ‘

CODE VALUES

8053 - Equipment qualifier

.

TE Trailer A vehicle without motive power, designed for the carriage of cargo and to be towed by a motor vehicle.



Segment group 10: CPS-FTX-SG11-SG15

Segment group: 10 [CPS] Level: 1 EDIFACT status: conditional Benteler status: mandatory Maximum use: 9999 per message Benteler occurrences: as required Function: group of segments providing details of all package levels and of the individual despatched items contained

in the consignment. This segment group provides the capability to give the hierarchical packing relationships. The group defines a logical top-down order structure. The lowest level package information of the hierarchy is followed by the detail product information.

Benteler interchange: only segment CPS is used in segment group 10. NOTE: Benteler requires each single part number (LIN-segment) to be preceded by a new CPS segment.

0380 CPS - CONSIGNMENT PACKING SEQUENCE (7075 = 1)

Segment group: 10 [CPS] Level: 1 EDIFACT status: mandatory if segment group 10 is used Benteler status: mandatory Maximum use: 1 per segment group 10 (max. 9999) Benteler occurrences: as required Function: segment identifying the sequence in which packing of the consignment occurs, e.g. boxes loaded onto a

pallet. Benteler interchange: see remarks.

Example: CPS+1++4’ A B


A 7164 HIERARCHICAL ID. NUMBER M an..12 + M an..12 A unique number assigned by the sender to identify a level within a hierarchical structure. Begins with the number 1 and increments by one for each occurrence within the message. Numbers are not to be repeated within the same message.

7166 HIERARCHICAL PARENT ID. C an..12 +

B 7075 PACKAGING LEVEL, CODED C an..3 ‘ M an..3 For code value, see below.

CODE VALUES

7075 - Packaging Level, Coded

1 Inner Level of packing, if it exists, that is immediately subordinate to the intermediate packaging level. Must be used when sending returnable packaging.

3 Outer For packed merchandise, outermost level of packaging for a shipment. For Benteler this includes the cover(s) and pallet(s).

4 No packaging hierarchy. There is no specifiable level of packaging: packaging is inner and outer level as well. For Benteler this includes containers used as transportation and handling unit and which are not put on a pallet.



Segment group 15: LIN-PIA-IMD-MEA-QTY-ALI-GIN-GIR-DLM-DTM-

NAD-TDT-HAN-FTX-MOA-SG16-SG17-SG18-SG19-SG20-SG23

Segment group: 15 [CPS.SG15] Level: 2 EDIFACT status: conditional Benteler status: mandatory Maximum use: 9999 per CPS in segment group 10 Benteler occurrences: as required Function: group of segments providing details of the individual despatched items. Benteler interchange: only LIN, PIA, QTY and TDT are used in segment group 15.


Segment group: 15 [CPS.LIN] Level: 2 EDIFACT status: mandatory if segment group 15 is used Benteler status: mandatory Maximum use: 1 per segment group 15 (max. 9999 per CPS) Benteler occurrences: 1 per segment group 15 Function: segment identifying the product being despatched. All other segments in the detail section following the

LIN segment refer to that line item. Benteler interchange: see remarks.

Example: LIN+++561296:IN’ A B




C an..3 +

C212 ITEM NUMBER IDENTIFICATION C M

A 7140 Item number C an..35 : M an..35 Benteler assigned part number.

B 7143 Item number type, coded C an..3 : M an..3 ”IN” = Buyer’s item number. 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +

C829 SUB-LINE INFORMATION C 5495 Sub-line indicator, coded C an..3 : 1082 Line item number C n..6 +






Segment group: 15 [CPS.LIN.PIA] Level: 3 EDIFACT status: conditional Benteler status: mandatory Maximum use: 10 per LIN in segment group 15 Benteler occurrences: 1 per preceding LIN Function: segment providing additional product identification. Benteler interchange: At least one iteration is mandatory

Example: PIA+1+R:EC’ A B C



M an..3 + M an..3 ”1” = Additional identification

C212 ITEM NUMBER IDENTIFICATION M M

B 7140 Item number C an..35 : M an..35 Identification of customer’s part Engineering Change level

C 7143 Item number type, coded C an..3 : M an..3 EC = Engineering Change Level

1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +

C212 ITEM NUMBER IDENTIFICATION C 7140 Item number C an..35 : C an..35 7143 Item number type, coded C an..3 : C an..3 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +

C212 ITEM NUMBER IDENTIFICATION C 7140 Item number C an..35 : C an..35 7143 Item number type, coded C an..3 : C an..3 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +





0600 QTY - QUANTITY

Segment group: 15 [CPS.LIN.QTY] Level: 3 EDIFACT status: conditional Benteler status: mandatory Maximum use: 10 per preceding LIN Benteler occurrences: max.1 per segment group 15 Function: segment to give quantity information concerning the product. Benteler interchange: see remarks.




Despatch quantity Mandatory

C186 QUANTITY DETAILS M M A 6063 Quantity qualifier M an..3 : M an..3 ”12” = Despatch quantity B 6060 Quantity M n..15 : M n..12 Actual quantity as defined in 6063 above. C 6411 Measure unit qualifier C an..3 ‘ M an..3 For code value see UN/ECE Recommendation

no. 20. (This must be the same Unit of

Measure provided on the corresponding

shipment authorization document.)



Segment group 16: RFF-NAD-CTA-DTM

Segment group: 16 [CPS.LIN.SG16] Level: 3 EDIFACT status: conditional Benteler status: mandatory Maximum use: 99 per LIN in segment group 15 Benteler occurrences: 2 per segment group 15 Function: group of segments to give reference numbers and dates. Benteler interchange: only RFF is used in segment group 16.


Segment group: 16 [SEQ.LIN.RFF] Level: 3 EDIFACT status: mandatory if segment group 16 is used Benteler status: mandatory Maximum use: 1 per segment group 16 (max.99 per LIN) Benteler occurrences: 2 per segment group 16 Function: segment identifying documents related to the line item. Benteler interchange: see remarks.

Example: RFF+ON:5500001122:00040’

RFF+AAN:16’ A B C



C506 REFERENCE M M A 1153 Reference qualifier M an..3 : M an..3 ”ON” = Order number. B 1154 Reference number C an..35 : M an..35 Number of the Purchase Order relevant for the

article defined in the preceding LIN. C 1156 Line number C an..6 : M an..5 Line item Number 4000 Reference version number C an..35 ‘



C506 REFERENCE M M A 1153 Reference qualifier M an..3 : M an..3 ”AAN” = Release number. B 1154 Reference number C an..35 : M an..35 Release number for the part described in the

preceding LIN segment. 1156 Line number C an..6 : 4000 Reference version number C an..35 ‘




Following example is only illustrative and does not necessarily reflect an existing situation. It MAY

NEVER be used as a basis for programming or implementing this message.

UNB+UNOA:2+003456789+112836044+2050305:1600+1234’ UNH+1+DESADV:D:97A:UN’ BGM++0011836+9’ Shipment Identification Number DTM+137:200503051500:203’ Document issue date/time DTM+11:200503051400:203’ Despatch date/time MEA+AAX+SQ+C62+15 Number of ladling units NAD+ST+0452::92’ Ship to identification NAD+SU+003456789::16’ Supplier DUNS Number TDT+12++ M++RYDD::92’ Transport details EQD+TE+ABC001998’ Equipment identification CPS+1++1’ Detail trigger segment 1 LIN+++12345678:IN’ Part number 1 PIA+1+B:EC’ Engineering change level for part number 1 QTY+12:18997:C62’ Despatched quantity part number 1 RFF+ON:5500001122:00010’ Purchase order: Line item number part 1 RFF+AAN:21:C62’ Release number part number 1 CPS+2++1’ Detail trigger segment 2 LIN+++23456789:IN’ Part number 2 PIA+1+C:EC’ Engineering change level for part number 2 QTY+12:18997:C62’ Despatched quantity part number 2 RFF+ON:5500001122:00020’ Purchase order: Line item number part 2 RFF+AAN:21:C62’ Release number part number 2 UNT+22+1’ UNZ+1+1234’


BENTELER NAO EDI IMPLEMENTATION GUIDELINES EDIFACT DELFOR

NAO_O-023 Implementation Guideline DELFOR Version 1.2 - 30-NOV-2009 1

Delivery Forecast EDIFACT DELFOR D97.A

Version 1.2



Document Change Log


1.0 30-JAN-2006 Document issued.

1.1 19-MAR-2009 Add additional elements to the PIA segment – PD Add Benteler Mexico Plant codes

1.2 30-NOV-2009 Update Benteler plant codess in the NAD ST segment Added comment to the PIA segment, PD element usage



0. TABLE OF CONTENT

0. TABLE OF CONTENT ........................................................................................................................................................3

1. INTRODUCTION .................................................................................................................................................................4

2. MESSAGE DEFINITION .....................................................................................................................................................4

2.1. FUNCTIONAL DEFINITION ..........................................................................................................................................4 2.2. PRINCIPLES.................................................................................................................................................................4 2.3. REFERENCES..............................................................................................................................................................4 2.4. FIELD OF APPLICATION..............................................................................................................................................4

3. MESSAGE DESCRIPTION .................................................................................................................................................5

3.1. INTRODUCTION...........................................................................................................................................................5 3.1.1. How to read the documentation.............................................................................................................................5 3.1.2. General remarks....................................................................................................................................................6

3.2. SEGMENT TABLE.........................................................................................................................................................6 3.3. MESSAGE STANDARD DESCRIPTION .......................................................................................................................9 3.4. MESSAGE STRUCTURE............................................................................................................................................11 3.5. DATA SEGMENTS DESCRIPTION.............................................................................................................................15 3.6. EXAMPLE OF MESSAGE ...........................................................................................................................................32



1. INTRODUCTION

This specification provides the definition of the EDIFACT DELFOR D97.A Delivery schedule message (DELFOR). This guideline is specifically designed to outline the requirements for the Delivery Schedule used by Benteler Automotive NAO


This document provides the definition of a Delivery Instruction Message, based on the EDIFACT DELFOR D97.A, to be used in Electronic Data Interchange (EDI) between a Benteler NAO Operating Company and its Trading Partners.


The Delivery Instruction message is a message from Benteler NAO to a Benteler Supplier giving details for both short and long term material requirements in line with the conditions set out in the purchase contract.

This message may only be used as planning forecast; shipping instruction will be provided in an additional call-off message.

2.2. PRINCIPLES

The Delivery Instruction message is intended to:

• Specify requirements based on the delivery conditions.

• Define the aspects that guarantee synchronization between Benteler and the Supplier.

• Provide information allowing the Supplier to plan for future requirements, to purchase raw materials.

2.3. REFERENCES


• the message structure as defined by EDIFACT for the Delivery Schedule Message DELFOR as published in the UN/EDIFACT D97.A Directory.


• although the DELINS subset defined by ODETTE has been based on the EDIFACT D96.A Directory which is not upward compatible with the D97.A Directory, the subset defined by Benteler Automotive and described in this document follows as close as possible the structure of the ODETTE subset.


The following definition of a Delivery Instruction Message in EDIFACT format is applicable for the interchange of delivery instructions issued by Benteler NAO for material deliveries to one or more Benteler NAO Operations.




The following pages contain a full description of the EDIFACT DELFOR D97.A message as implemented by Benteler Automotive, NAO. The official EDIFACT segment description is complemented with remarks pertaining to the specific requirements for an interchange with Benteler Automotive, NAO. Those remarks contain specific code values used, additional information on the values shown in a specific field, etc. The aim of those remarks is to simplify the implementation of the message.

3.1. INTRODUCTION


All segments in the subset used by Benteler Automotive are described in the following pages. The segment description is to be read as follows:






see remarks.


� EDIFACT STANDARD DEFINITION Benteler IMPLEMENTATION


C002 DOCUMENT/MESSAGE NAME C C A 1001 Document/message name, coded C an..3 : M an..3 '241’ = Delivery Schedule 1131 Code list qualifier C an..3 : 3055 Code list responsible agency,

coded C an..3 :

1000 Document/message name C an..35 +


C

B 1004 Document/message number C an..35 : M an..35 Benteler assigned release number 1056 Version C an..9 : 1060 Revision number C an..6 +

C 1225 MESSAGE FUNCTION, CODED C an..3 + C an..3 Function of the message. For code values see below.


COMMENTS

CODE VALUES

LEGEND



� status of the segment: as defined by EDIFACT and by Benteler.

� number of occurrences of the segment: as defined by EDIFACT and as used by Benteler.

� description of the function of the segment as defined by EDIFACT and as used by Benteler.



� example of the segment as it may appear in an interchange. This example is only illustrative and does not necessarily represent an actual situation. It should NOT be used as a basis to implement this message.

� definition of the segment content as defined by EDIFACT and as implemented by Benteler.








• remarks on the specific use of the data element in the interchange with Benteler.

Shaded areas in the Benteler description mean that the data element is not used by Benteler.

The segment description can be followed by:

• comments providing more information regarding specific data elements and how they must be used and/or understood in messages from Benteler.




• Dates Unless otherwise specified in the field explanation in the documentation, dates are

always expressed as CCYYMMDD (qualifier 2379 = 102).

• Times

Unless otherwise specified in the field explanation in the documentation, times are

always expressed as HHMM.

3.2. SEGMENT TABLE

The following table shows the segments defined for the EDIFACT UNSM DELFOR D97.A Delivery Forecast message. Shaded areas identify the segments that are not used in the subset of DELFOR used by Benteler.


0010 UNH Message header M 1 0020 BGM Beginning of message M 1 0030 DTM Date/time/period M 10 0040 FTX Free text C 5




0090 NAD Name and address M 1









0170 TDT Details of transport M 1 0180 DTM Date/time/period C 5


0200 GIS General Indicator M 1


0220 NAD Name and Address M 1 0230 LOC Place/location identification C 10 0240 FTX Free text C 5




0290 DOC Document/message details M 1 0300 DTM Date/time/period C 10






0380 LIN Line item M 1 0390 PIA Additional product id M 10 0400 IMD Item description C 10 0410 MEA Measurements C 5 0420 ALI Additional information C 5 0430 GIN Goods identity number C 999 0440 GIR Related identification numbers C 999 0450 LOC Place/location identification C 999 0460 DTM Date/time/period C 5 0470 FTX Free text C 5






0550 QTY Quantity M 1 0560 DTM Date/time/period C 2


0580 RFF Reference C 1 0590 DTM Date/time/period C 1


0610 SCC Scheduling conditions M 1









0690 PAC Package M 1 0700 MEA Measurements C 10 0710 QTY Quantity C 5 0720 DTM Date/time/period C 5


0740 PCI Package identification M 1 0750 GIN Goods identity number C 10


0770 NAD Name and address M 1 0780 LOC Place/location identification C 10 0790 FTX Free text C 5


0810 DOC Document/message details M 1 0820 DTM Date/time/period C 1








0930 SCC Scheduling conditions M 1



0970

Segment group 29 C 10




1030 UNT Message trailer M 1




This section provides the description of the UN Standard Message DELFOR as defined in the 97.A Directory. These segments are used in the subset defined by Benteler and will be further explained in section 3.6. 3.3.1 Header section


0010 UNH, Message header A service segment starting and uniquely identifying a message. The message type code for the Delivery schedule message is DELFOR.

0020 BGM, Beginning of message A segment for unique identification of the Delivery schedule message by means of its name and its number and its function (original, replacement, change).

0030 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.

0080 Segment group 2: NAD-SG3-SG4 A group of segments identifying parties by their names, addresses, locations, references and contacts relevant to the whole delivery schedule.

0090 NAD, Name and address 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.



0190 Segment group 6: GIS-SG7-SG12 A group of segments providing details on delivery points and products and related information using one of both scheduling methods.

0200 GIS, General indicator A segment to indicate which method is used by the relevant processing indicator code.

0210 Segment group 7: NAD-LOC-FTX-SG8-SG9-SG10-SG11 A group of segments needed to identify a delivery point and its attached information when the delivery point method is used.

0220 NAD, Name and address A segment for identifying the consignee.

0370 Segment group 12: LIN-PIA-IMD-MEA-ALI-GIN-GIR-LOC-DTM-FTX-SG13-SG14-SG15-

SG17-SG20-SG22 A group of segments providing details of the individual line items for both methods.

0380 LIN, Line item 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.

0390 PIA, Additional product id A segment providing additional product identification.

0480 Segment group 13: RFF-DTM A group of segments giving references related to the line item and where necessary, their dates.

0490 RFF, Reference 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.

0540 Segment group 15: QTY-DTM-SG16 A group of segments specifying product quantities and associated dates not related to schedules and where relevant, references.

0550 QTY, Quantity



A segment to specify pertinent quantities not related to schedule(s) e.g. cumulative quantity, last quantity considered.

0560 DTM, Date/time/period A segment indicating the date/time/period details relating to the quantity.

0570 Segment group 16: RFF-DTM A group of segments giving references related to the quantity and where necessary, their dates.

0580 RFF, Reference A segment for identifying references to the quantity, e.g. dispatch advice number.

0590 DTM, Date/time/period Date/time/period of the reference.

0600 Segment group 17: SCC-SG18 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.

0610 SCC, Scheduling conditions A segment specifying the status of the schedule. Optionally a delivery pattern can be established, e.g. firm or proposed delivery pattern.

0620 Segment group 18: QTY-DTM-SG19 A group of segments specifying product quantities and associated dates.

0630 QTY, Quantity 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.

0640 DTM, Date/time/period A segment indicating date/time/period details relating to the given quantity.





The message structure illustrates how the segments will be repeated in the Delivery Forecast message to accommodate the requirements identified by Benteler Automotive.

0010.UNH Start of Delivery Schedule Message


0030.DTM Message generation date

0090.NAD Supplier Identification

0200.GIS Start of detail section

0220.[GIS].NAD Ship To destination identification

0380.[GIS.NAD].LIN Part number identification

0390.[GIS.NAD.LIN].PIA Customer part Engineering Change Level, Part Desc.

0490-1.(GIS.NAD.LIN),RFF Purchase Order number : Line Item Number

0490-2.[GIS.NAD.LIN].RFF Release number

0550.[GIS.NAD.LIN].QTY Cumulative quantity received

0560.[GIS.NAD.LIN.QTY].DTM Cumulative quantity date

0550.[GIS.NAD.LIN].QTY Quantity received as of the last ASN

0580.[GIS.NAD.LIN.QTY].RFF SID number of last ASN received

0590.[GIS.NAD.LIN.QTY.RFF].DTM Date material on last ASN received

0610-1.[GIS.NAD.LIN].SCC Schedule status

0630.[GIS.NAD.LIN.SCC].QTY Quantity to be delivered week 1

0640.[GIS.NAD.LIN.SCC.QTY].DTM Date of planned delivery week 1

0630.[GIS.NAD.LIN.SCC].QTY Quantity to be delivered week 2

0640.[GIS.NAD.LIN.SCC.QTY].DTM Date of planned delivery week 2

0630.[GIS.NAD.LIN.SCC].QTY Quantity to be delivered week n

0640.[GIS.NAD.LIN.SCC.QTY].DTM Date of planned delivery week n

0610-2.[GIS.NAD.LIN].SCC Authorization code

0630.[GIS.NAD.LIN.SCC].QTY Cumulative fabrication authorization

0640-1.[NAD.LIN.SCC.QTY].DTM Fabrication date

0610-3.[GIS.NAD.LIN].SCC Authorization code

0630.[GIS.NAD.LIN.SCC].QTY Cumulative material authorization

0640-1.[NAD.LIN.SCC.QTY].DTM Material date







Benteler interchange see remarks

Example: UNB+UNOA:2+BENTUSA:ZZ+9876652901+051206:1011+101++BENTELERNAO’ A B C D E F G H


S001 SYNTAX IDENTIFIER M M A 0001 Syntax identifier M a4 : M A4 “UNOA”. B 0002 Syntax version number M n1 + M N1 Indication of the syntax version used for this

message. Benteler uses EDIFACT syntax version 2

S002 INTERCHANGE SENDER M M C 0004 Sender identification M an..35 : M an..35 ‘BENTUSA’ Benteler ID

0007 Identification code qualifier C an..4 : M An..4 ‘ZZ’

0008 Address for Reverse Routing C an..14 +

S003 INTERCHANGE RECIPIENT M M D 0010 Recipient identification M an..35 : M an..35 Communication code/of the party receiving the

message. 0007 Identification code qualifier C an..4 : M An..4 Qualifiers to be determined by trading partner


S004 DATE / TIME OF PREPARATION M M E 0017 Date of preparation M n6 : M N6 YYMMDD format F 0019 Time of preparation M n4 + M n4 HHMM format


M an..14 + M an..14 This number is UNIQUE


C


qualifier C an2 +

H 0026 APPLICATION REFERENCE C an..14 + C an..14 “BENTELERNAO”.








Segment group: none Level: 0 EDIFACT status: mandatory. Benteler status: mandatory. Maximum use: 1 per message. Benteler occurrences: 1 per message. Function: service segment starting and uniquely identifying a message. The message type code for the Delivery

schedule message is DELFOR. Benteler interchange: see remarks.

Example: UNH+1+DELFOR:D:97A:UN’ A B C D E



S009 MESSAGE IDENTIFIER M M B 0065 Message type M an..6 : M an..6 “DELFOR”. C 0052 Message version number M an..3 : M an..3 “D”. D 0054 Message release number M an..3 : M an..3 “97A”.

E 0051 Controlling agency M an..2 : M an..2 “UN”. 0057 Association assigned code C an..6 +















This part includes only the segments defined in the standard and used in the subset exchanged between Benteler NAO and its Trading Partners. The segments are described in the same sequence as they appear in the message.


Segment group: none Level: 1 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 1 per message Benteler occurrences: 1 per message Function: segment for the unique identification of the delivery schedule document, by means of its name and its

number. Benteler interchange: see remarks.

Example: BGM+241::PS+00203520+9’ A B C D


C002 DOCUMENT/MESSAGE NAME C C A 1001 Document/message name, coded C an..3 : M an..3 “241” = Delivery Schedule. This means that the

quantities must be planned for shipment during the week indicated. Actual shipping authorization will be provided by a DELJIT message.

1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 :

B 1000 Document/message name C an..35 + C an..35 “PS” = Planned Shipment Based - no

authorization to ship.


C

C 1004 Document/message number C an..35 : M an..35 Benteler assigned number. .

1056 Version C an..9 :

1060 Revision number C an..6 +

D 1225 MESSAGE FUNCTION, CODED C an..3 + M an..3 Function of the message. For code value, see below.


CODE VALUES

1225 - Message Function, coded

9 Original only

Benteler NAO does not support change or replace




Segment group: none Level: 1 EDIFACT status: mandatory Benteler status: mandatory Maximum use: 10 per message at level 1 Benteler occurrences: max. 1 per message Function: segment specifying the date when the document was generated. The DTM must be specified at least

once to identify the Delivery Schedule document date. Benteler interchange: there will be only one occurrence of the DTM in position 0030: to specify the message

issue date.

Example: DTM+137:200512060611:203’ document generation A B C



C507 DATE/TIME/PERIOD M M A 2005 Date/time/period qualifier M an..3 : M an..3 “137” = Document message date/time. B 2380 Date/time/period C an..35 : M an..35 Actual issue date of the document. C 2379 Date/time/period format qualifier C an..3 “ M an..3 “203” = CCYYMMDDHHMM



Segment group 2: NAD-SG3-SG4

Segment group: 2 [SG2] Level: 1 EDIFACT status: conditional Benteler status: mandatory Maximum use: 99 per message at level 1 Benteler occurrences: max. 1 per message Function: group of segments identifying names, addresses, locations, and contacts relevant to the whole

Delivery Schedule. Benteler interchange: see segment description.


Segment group: 2 [NAD] Level: 1 EDIFACT status: mandatory if segment group 2 is used Benteler status: mandatory Maximum use: 1 per segment group 2 (max. 99) Benteler occurrences: 1 per segment group 2 Function: segment for identifying names and addresses and their functions relevant for the whole Delivery

Schedule. Benteler interchange: Benteler will always transmit one occurrence in position 0090 as detailed below.

Example: NAD+SU+084559798::16’ Supplier A B C


A 3035 PARTY QUALIFIER M an..3 + M an..3 “SU” = Supplier.

C082 PARTY IDENTIFICATION DETAILS C M B 3039 Party id. Identification M an..35 : M an..35 Code identifying the supplier. 1131 Code list qualifier C an..3 :

C 3055 Code list responsible agency, coded C an..3 + M an..3 For code value, see below.


3124 Name and address line M an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 +

C080 PARTY NAME C D 3036 Party name M an..35 : 3036 Party name C an..35 : 3036 Party name C an..35 : 3036 Party name C an..35 : 3036 Party name C an..35 : 3045 Party name format, coded C an..3 +

C059 STREET C

3042 Street and number/p.o. box M an..35 : 3042 Street and number/p.o. box C an..35 : 3042 Street and number/p.o. box C an..35 : 3042 Street and number/p.o. box C an..35 +



C an..9 +


3207 COUNTRY, CODED C an..3 “

CODE VALUES

3039 - Party Id. Identification

The Supplier DUNS number unless otherwise specified

3055 - Code List Responsible Agency, coded

16 DUN & Bradstreet (DUNS) - (currently used by Benteler, 9 digits) 92 Assigned by buyer



Segment group 6: GIS-SG7-SG12

Segment group: 6 [SG6] Level: 1 EDIFACT status: conditional Benteler status: mandatory Maximum use: 9999 per message Benteler occurrences: max. 9999 per message Function: group of segments providing details on delivery points and products and related information using one

of both scheduling methods. Benteler interchange: see segment description.

0200 GIS - GENERAL INDICATOR

Segment group: 6 [GIS] Level: 1 EDIFACT status: mandatory if segment group 6 is used Benteler status: mandatory Maximum use: 1 per segment group 6 Benteler occurrences: 1 per segment group 6 Function: segment to indicate which method is used by the relevant processing indicator code. Benteler interchange: see remarks.

Example: GIS+37’ A


C529 PROCESSING INDICATOR M M A 7365 Processing indicator, coded M an..3 : M an..3 For code value, see below. 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 7187 Process type identification C an..17 ‘

CODE VALUES

7365 - Processing indicator, coded

37 Complete information



Segment group 7: NAD-LOC-FTX-SG8-SG9-SG10-SG11

Segment group: 7 [GIS.SG7] Level: 2 EDIFACT status: conditional Benteler status: mandatory Maximum use: 1 per segment group 6 Benteler occurrences: 1 per segment group 6 Function: group of segments needed to identify a delivery point and its attached information when the delivery

point method is used Benteler interchange: see segment description.


Segment group: 7 [GIS.NAD] Level: 2 EDIFACT status: mandatory if segment group 7 is used Benteler status: mandatory Maximum use: 1 per segment group 7 Benteler occurrences: 1 per segment group 7 Function: segment for identifying names and addresses and their functions relevant to the delivery point. All

other segments in this segment group 7 following the NAD segment refer to that delivery point. Benteler interchange: see remarks.

Example: NAD+ST+0449::92++Opelika, Alabama Plant+4401 North Park Drive+Opelika+AL+26801+US’ A B C D E F G H I


A 3035 PARTY QUALIFIER M an..3 + M an..3 “ST” = Ship To.


B 3039 Party id. Identification M an..35 : M an..35 Code identifying the plant where the material must be delivered. For code values see below.

1131 Code list qualifier C an..3 : C 3055 Code list responsible agency, coded C an..3 + M an..3 For code values see below.

C058 NAME AND ADDRESS C 3124 Name and address line M an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 : 3124 Name and address line C an..35 +

D C080 PARTY NAME C M 3036 Party name M an..35 : M an..35 Name of the party 3036 Party name C an..35 : 3036 Party name C an..35 : 3036 Party name C an..35 : 3036 Party name C an..35 : 3045 Party name format, coded C an..3 +

E C059 STREET C M 3042 Street and number/p.o. box M an..35 : M an..25 Address 3042 Street and number/p.o. box C an..35 : 3042 Street and number/p.o. box C an..35 : 3042 Street and number/p.o. box C an..35 +

F 3164 CITY NAME C an..35 + M an..35 City Name

G 3229 COUNTRY SUB-ENTITY IDENTIFICATION

C an..9 + M an..9

H 3251 POSTCODE IDENTIFICATION C an..9 + M an..9 Postal Code, Zip code…

I 3207 COUNTRY, CODED C an..3 “ M an..3 Country Code

CODE VALUES

3039 - Party Id. Identification

0442 - Hall Street 0443 - Hagen Drive 0445 - Kalamazoo 0446 - Goshen 0449 - Opelika 0452 - Spartanburg 0471 - Brampton 0585 - Hermosillo 0586 - Puebla 0587 - Saltillo



3055 - Code List Responsible Agency, coded

92 Assigned by buyer



Segment group 12: LIN-PIA-IMD-MEA-ALI-GIN-GIR-LOC-DTM-

FTX-SG13-SG14-SG15-SG17-SG20-SG22

Segment group: 12 [GIS.SG12] Level: 2 EDIFACT status: conditional Benteler status: mandatory Maximum use: 9999 per GIS in segment group 06 Benteler occurrences: max. 9999 per SG6 Function: group of segments providing details of the individual line items for the specified delivery point. Benteler interchange: see segment description.


Segment group: 12 [GIS.LIN] Level: 2 EDIFACT status: mandatory if segment group 12 is used Benteler status: mandatory Maximum use: 1 per segment group 12 (max. 9999 per GIS) Benteler occurrences: 1 per segment group 12 Function: 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. Benteler interchange: see remarks.

Example: LIN+++123456B-01:IN’ A B





C an..3 +

C212 ITEM NUMBER IDENTIFICATION C M A 7140 Item number C an..35 : M an..35 Benteler assigned part number.

B 7143 Item number type, coded C an..3 : M an..3 “IN” = Buyer’s item number. 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +

C829 SUB-LINE INFORMATION C

5495 Sub-line indicator, coded C an..3 : 1082 Line item number C an..6 +






Segment group: 12 [GIS.LIN.PIA] Level: 3 EDIFACT status: conditional Benteler status: mandatory Maximum use: 10 per LIN in segment group 12 Benteler occurrences: 1 per segment group 12 Function: segment providing additional product identification. Benteler interchange: see remarks.

Example: PIA+1+A:EC+60758-AD GM-15874928:PD’ Change Level

PIA+1+--:EC +60758-AD GM-15874928:PD’ No Change Level

PIA+1+A:EC` Change Level, No additional description A B C D E



M an..3 + M an..3 “1” = Additional identification

C212 ITEM NUMBER IDENTIFICATION M M B 7140 Item number C an..35 : M an..35 Change Level. Identification C 7143 Item number type, coded C an..3 : M an..3 ‘EC’= Engineering Change Level. 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +


D 7140 Item number C an..35 : O an..22 Part number Description E 7143 Item number type, coded C an..3 : O an..3 ‘PD’ = Additionl part description 1131 Code list qualifier C an..3 : 3055 Code list responsible agency, coded C an..3 +




Comments

7140 – Item Number – ‘EC’

Benteler will send a – if a change level has not yet been assigned for a part

7140 – Item Number – ‘PD’

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




Segment group: 13 [GIS.LIN.SG13] Level: 3 EDIFACT status: conditional Benteler status: mandatory Maximum use: 10 per LIN in segment group 12 Benteler occurrences: 2 per segment group 12 Function: group of segments giving references related to the line item and where necessary, their dates. Benteler interchange: see segment description.


Segment group: 13 [GIS.LIN.RFF] Level: 3 EDIFACT status: mandatory if segment group 13 is used Benteler status: mandatory Maximum use: 1 per segment group 13 (max. 10) Benteler occurrences: 1 per segment group 13 Function: segment for identifying documents relating to the line item, e.g. a contract and its appropriate line item. Benteler interchange: see remarks.

Example: RFF+ON:5500001950:20’ A B C


C506 REFERENCE M M A 1153 Reference qualifier M an..3 : M an..3 “ON” = Order number.

B 1154 Reference number C an..35 : M an..35 The Purchase Order number relevant for the article defined in the preceding LIN.

C 1156 Line number C an..6 : M An..5 Purchase Order line item Number 4000 Reference version number C an..35 ‘


Segment group: 13 [GIS.LIN.RFF] Level: 3 EDIFACT status: mandatory if segment group 13 is used Benteler status: mandatory Maximum use: 1 per segment group 13 (max. 10) Benteler occurrences: 1 per segment group 13 Function: segment for identifying documents relating to the line item, e.g. a contract and its appropriate line item. Benteler interchange: see remarks.

Example: RFF+AAN:23’ A B


C506 REFERENCE M M A 1153 Reference qualifier M an..3 : M an..3 “AAN” = Release Number

B 1154 Reference number C an..35 : M an..35 Release number relevant to the article defined in the preceding LIN.



Use of segment groups 15 and 17 in message from Benteler

Segment groups 15 and 17 are used to provide 4 different kinds of quantity information, i.e.:

CALCULATION INFORMATION Cumulative quantity received [qualifier 6063 = 70] SG15 Quantity received on the last ASN [qualifier 6063 = 48] SG15

REQUIREMENTS INFORMATION Quantity to be delivered [qualifier 6063 = 1] SG17

AUTHORIZATION INFORMATION Cumulative fabrication autorization [qualifier 6063 = 2] SG17 Cumulative material autorization [qualifier 6063 = 3] SG17

Each use of segment group 15 and 17 is described separately in the following pages.



CALCULATION INFORMATION

Segment group 15: QTY-DTM-SG16

Segment group: 15 [GIS.LIN.SG15] Level: 3 EDIFACT status: conditional Benteler status: mandatory Maximum use: 10 per LIN in segment group 12 Benteler occurrences: max.10 per segment group

12 Function: group of segments specifying product quantities and associated dates not related to schedules and

where relevant references. Benteler interchange: see description of different occurrences of segment group 15.

SEGMENT GROUP 15

CUMULATIVE QUANTITY RECEIVED

0550.[GIS.LIN].QTY Cumulative quantity received

0560.[GIS.LIN.QTY].DTM Cumulative calculation start date

0550 QTY - QUANTITY

Segment group: 15 [GIS.LIN.QTY] Level: 3 EDIFACT status: mandatory when segment group 15 is used Benteler status: mandatory Maximum use: 1 per segment group 15 (max. 10) Benteler occurrences: 1 per segment group 15 Function: segment to specify pertinent quantities not related to schedule(s), e.g. cumulative quantity, last

quantity considered. Benteler interchange: see description of different occurrences of segment group 15.



C186 QUANTITY DETAILS M M A 6063 Quantile qualifier M An..3 : M an..3 “70” = Cumulative quantity received.

B 6060 Quantity M n..15 : M n..15 Cumulative quantity received C 6411 Measure unit qualifier C An..3 ‘ M an..3 For code value see UN/ECE Recommendation

No. 20.


Segment group: 15 [GIS.LIN.QTY.DTM] Level: 4 EDIFACT status: conditional Benteler status: mandatory Maximum use: 2 per QTY Benteler occurrences: 1 per segment group 15 Function: segment providing the date/time/period of the reference. Benteler interchange: see remarks.



C507 DATE/TIME/PERIOD M M A 2005 Date/time/period qualifier M An..3 : M an..3 “51” = Cumulative quantity date. B 2380 Date/time/period C An..35 : M an..35 Date of cumulative quantity calculation. C 2379 Date/time/period format qualifier C An..3 ‘ M an..3 “102” = CCYYMMDD.



SEGMENT GROUP 15

REFERENCE INFORMATION

0550.[GIS.LIN].QTY Quantity of the referenced message

0570.[GIS.LIN.QTY.SG16].RFF Identifying number of referenced message

0580.[GIS.LIN.QTY.SG16].DTM Date of last referenced message

0550 QTY - QUANTITY

Description: See quantity information 1

Example:


C186 QUANTITY DETAILS M M A 6063 Quantile qualifier M An..3 : M an..3 “48” = Last received quantity. B 6060 Quantity M n..15 : M n..15 Quantity received as of the SID in the following

RFF segment. C 6411 Measure unit qualifier C An..3 ‘ M an..3 For code value see UN/ECE Recommendation

No. 20.


Segment group: 16 [GIS.LIN.QTY.SG16] Level: 4 EDIFACT status: conditional Benteler status: conditional Maximum use: 10 per QTY in segment group 15 Benteler occurrences: 1 per segment group 16 Function: group of segments giving references related to the quantity and where necessary, their dates. Benteler interchange: see segment description.


Segment group: 16 [GIS.LIN.QTY.RFF] Level: 4 EDIFACT status: mandatory if segment group 16 is used Benteler status: conditional Maximum use: 1 per segment group 16 (max. 10) Benteler occurrences: 1 per segment group 16 Function: segment for identifying reference to the quantity, e.g. despatch advice number. Benteler interchange: see segment group description.

Example: RFF+SI:9634’ A B


C506 REFERENCE M M

A 1153 Reference qualifier M An..3 : M an..3 “SI” = Shipper Identification number.

B 1154 Reference number C An..35 : M an..35 Shipper Identification Number of the last shipment received




Segment group: 16 [GIS.LIN.QTY.RFF.DTM] Level: 5 EDIFACT status: conditional Benteler status: conditional Maximum use: 1 per RFF Benteler occurrences: 1 per RFF Function: segment providing the date/time/period of the reference. Benteler interchange: see segment group description.

Example: DTM+50:20051212:102’ Start date

A B C


C507 DATE/TIME/PERIOD M M A 2005 Date/time/period qualifier M an..3 : M an..3 “50’ Goods receipt date B 2380 Date/time/period C an..35 : M an..35 Date that material was received C 2379 Date/time/period format qualifier C an..3 ‘ M an..3 “102” = CCYYMMDD.



REQUIREMENT INFORMATION

Segment group 17: SCC-SG18

Segment group: 17 [GIS.LIN.SG17] Level: 3 EDIFACT status: conditional Benteler status: mandatory Maximum use: 999 per LIN in segment group 12 Benteler occurrences: max. 999 per SG12 Function: group of segments specifying the schedule information for the product identified in the LIN segment.

This segment group provides the schedule for the identified delivery point and product. Benteler interchange: see description of different occurrences of segment group 17.

SEGMENT GROUP 17

QUANTITY TO BE DELIVERED

0610.[GIS.LIN].SCC Schedule status & delivery frequency

0630.[GIS.LIN.SCC].QTY Quantity to be delivered

0640.[GIS.LIN.SCC.QTY].DTM Delivery date/time

0610 SCC - SCHEDULING CONDITIONS

Segment group: 17 [GIS.LIN.SCC] Level: 3 EDIFACT status: mandatory if segment group 17 is used Benteler status: mandatory Maximum use: 1 per segment group 17 Benteler occurrences: 1 per segment group 17 Function: segment specifying the status of the schedule. Optionally a delivery pattern can be established, e.g.

firm or proposed delivery pattern. Benteler interchange: see remarks.

Example: SCC+4++W’ Weekly quantities A B


A 4017 DELIVERY PLAN STATUS INDICATOR, CODED

M an..3 + M an..3 Code value qualifying the quantity defined in the following QTY. For code value, see below.

4493 DELIVERY REQUIREMENTS, CODED

C an..3 +

C329 PATTERN DESCRIPTION C M

B 2013 Frequency, coded C an..3 : M an..3 Definition of the time unit for the quantity defined in the preceding QTY. For code value, see below.

2015 Despatch pattern, coded C an..3 : 2017 Despatch pattern timing, coded C an..3 ‘

CODE VALUES

4017 - Delivery Plan Status Indicator, coded

4 Planning quantity

2013 - Frequency, coded

W Weekly



Segment group 18: QTY-DTM-SG19

Segment group: 18 [GIS.LIN.SCC.SG17] Level: 4 EDIFACT status: conditional Benteler status: mandatory Maximum use: 999 per SCC in segment group 17 Benteler occurrences: max. 999 per SG17 Function: group of segments specifying product quantities and associated dates. Benteler interchange: see description of different occurrences of segment group 17.

0630 QTY - QUANTITY

Segment group: 18 [GIS.LIN.SCC.QTY] Level: 4 EDIFACT status: mandatory if segment group 18 is used Benteler status: mandatory Maximum use: 1 per segment group 18 (max. 999 per SCC) Benteler occurrences: 1 per segment group 18 Function: 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. Benteler interchange: see remarks.



C186 QUANTITY DETAILS M M A 6063 Quantity qualifier M an..3 : M an..3 “1” = Discrete Quantity. B 6060 Quantity M n..15 : M n..15 Forecasted quantity for the time period defined

by the preceding SCC. C 6411 Measure unit qualifier C an..3 ‘ M an..3 For code value see UN/ECE Recommendation

No. 20.


Segment group: 18 [GIS.LIN.SCC.QTY.DTM] Level: 5 EDIFACT status: conditional Benteler status: mandatory Maximum use: 1 per QTY in segment group 18 Benteler occurrences: 1 per segment group 18 Function: segment indicating date/time/period details relating to the given quantity. Benteler interchange: see remarks.

Example: DTM+10:20051216:102 Ship Date A B C

EDIFACT STANDARD DEFINITION BENTELER IMPLEMENTATION TAG NAME ST FT SP ST FT REMARKS

REF C507 DATE/TIME/PERIOD M M A 2005 Date/time/period qualifier M an..3 : M an..3 “10” = Ship date . B 2380 Date/time/period C an..35 : M an..35 Monday of the week/period associated with the

quantity defined in the preceding QTY. C 2379 Date/time/period format qualifier C an..3 ‘ M an..3 “102” = CCYYMMDD.



AUTHORIZATION INFORMATION

SEGMENT GROUP 17

CUMULATIVE FABRICATION AUTHORIZATION

0610.[GIS.LIN].SCC Cumulative fabrication authorization quantity

0630.[GIS.LIN.SCC].QTY Authorization code

0640.[GIS.LIN.SCC.QTY].DTM Cumulative calculation period start date


Description: see quantity information 1.

Example: SCC+2’ A



M an..3 + M an..3 “2” = Commitment for manufacturing and material. (Fabrication Authorization)


0630 QTY - QUANTITY




C186 QUANTITY DETAILS M M A 6063 Quantity qualifier M an..3 : M an..3 “3” = Cumulative quantity. B 6060 Quantity M n..15 : M n..15 Cumulative fabrication authorization quantity

for the period defined in the following DTM C 6411 Measure unit qualifier C an..3 ‘ C an..3 For code value see UN/ECE Recommendation

No. 20.





C507 DATE/TIME/PERIOD M M

A 2005 Date/time/period qualifier M an..3 : M an..3 “51” = Cumulative quantity date. B 2380 Date/time/period C an..35 : M an..35 Date of cumulative quantity calculation. C 2379 Date/time/period format qualifier C an..3 ‘ M an..3 “102” = CCYYMMDD.



SEGMENT GROUP 17

CUMULATIVE MATERIAL AUTHORIZATION

0610.[GIS.LIN].SCC Authorization code

0630.[GIS.LIN.SCC].QTY Cumulative material autorization quantity

0640.[GIS.LIN.SCC.QTY].DTM Cumulative calculation period start date



Example: SCC+3’ A



M an..3 + M an..3 “3” = Commitment for material.

(Material Authorization)


0630 QTY - QUANTITY




C186 QUANTITY DETAILS M M

A 6063 Quantity qualifier M an..3 : M an..3 “3” = Cumulative quantity.

B 6060 Quantity M n..15 : M n..15 Cumulative material authorization quantity for the period defined in the following DTM

C 6411 Measure unit qualifier C an..3 ‘ M an..3 For code value see UN/ECE Recommendation No. 20.



Example: DTM+51:20051212:102’ Start date

A B C


C507 DATE/TIME/PERIOD M M

A 2005 Date/time/period qualifier M an..3 : M an..3 “51” = Cumulative quantity date.

B 2380 Date/time/period C an..35 : M an..35 Date of cumulative quantity calculation. C 2379 Date/time/period format qualifier C an..3 ‘ M an..3 “102” = CCYYMMDD.




Following example is only illustrative and does not necessarily reflect an existing situation. It

MAY NEVER be used as a basis for programming or implementing this message.

UNB+UNOA:2+112836044:01+003456098:01+20051212:1001+12++BENTELERNAO’ UNH+1+DELFOR:D:97A:UN’ BGM+241::PS+002112512+9’ DTM+137:200512120608:203’ Document issue date NAD+SU+084559798::16’ Supplier ID GIS+37’ NAD+ST+0449::92++ Opelika+4401 Park Street+Opelika+AL+36801+US’ Ship To

LIN+++35674:IN’ Buyers part number PIA+1+B:EC+60758-AD GM-15874928:PD` Engineering change level; Part Description RFF+ON:5500007652:10’ Purchase Order and Line item number RFF+AAN:21’ Release number

QTY+70:99999:C62’ Cum. quantity received DTM+51:20051212:102’ Cum quantity date QTY+48:99999:C62’ Last received quantity

RFF+SI:9634’ Last ASN/Shipper ID received DTM+50:20051212:102’ Date that material was received SCC+4++W’ Quantity to be delivered (weekly quantity)

QTY+1:9999:C62’ Quantity for week 1 DTM+10:20051219:102’ Week 1 identification QTY+1:9999:C62’ Quantity for week 2

DTM+10:20051226:102’ Week 2 identification QTY … Quantity for week n DTM… Week n identification

SCC+2’ Fabrication authorization QTY+3:99999:C62’ Authorization quantity DTM+51:20051231:102’ Authorization date

SCC+3’ Material authorization QTY+3:99999:C62’ Authorization quantity DTM+51:200501231:102’ Authorization date UNT+30+1’ UNZ+1+12’


edifact contrl d - benteler-suppliers.com nao edi implementation guidelines edifact contrl contrl...

Documents