0% found this document useful (0 votes)
155 views31 pages

EDI Implementation Guidelines Delins Od3 Page 1 of 31

This document provides EDI implementation guidelines for the ODETTE DELINS Version 3 message. It details each segment in the message, including segment tag, status, occurrences, description, data element tags, names, formats, and any implementation details specific to Adient. It provides an example message structure and explains the envelope segments that make up an EDI interchange.

Uploaded by

Pandu Sathya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
155 views31 pages

EDI Implementation Guidelines Delins Od3 Page 1 of 31

This document provides EDI implementation guidelines for the ODETTE DELINS Version 3 message. It details each segment in the message, including segment tag, status, occurrences, description, data element tags, names, formats, and any implementation details specific to Adient. It provides an example message structure and explains the envelope segments that make up an EDI interchange.

Uploaded by

Pandu Sathya
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 31

EDI Implementation Guidelines

DELINS OD 3

EDI Implementation Guidelines


DELINS OD3 Page 1 of 31
1 How to read this document
Following pages contain a full description of the ODETTE DELINS Version 3 message. All segments have
been included regardless whether used in the interchange with Adient or not. The official ODETTE segment
description has been extended with remarks pertaining to the specific requirements for an interchange with
Adient. Those remarks contain specific code values to be used, additional information on the values shown
or to be shown in a specific field, etc. The aim of those remarks being to simplify the implementation of the
message. Example:.
SDT SELLER DETAILS 1
ODETTE status : Mandatory2 Adient status : Mandatory
Level : 03 Occurrences : One per message
Segment providing the identification of the seller (Supplier) by means of his vendor code. 4
5
ODETTE STANDARD Adient IMPLEMENTATION 12
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

SELLER M9 M
3347 Seller, coded8 C an..20 :11 M an..9
7 10

3036 Party name14 C an..35 :

Example 15
SDT+0020115'
(the SDT segment identifies the recipient of the Delivery Instruction message as the seller/Supplier with vendor-code
0020115)

1 segment tag and segment name


2 segment status : indication of the segment status as defined by ODETTE and as requested by Adient.
Bold entries in the Adient status indicate a deviation from the standard, i.e. the segment is Mandatory
or the segment is Not used in the interchange with Adient Europe.
3 indication at which level segment is situated and number of occurrences of the segment.
4 description of the use of the segment in this message.
5 segment description as defined by ODETTE. This description contains :
7 the data element tag;
8 its name;
Italic entries under the data element name reflect comments included in the official ODETTE documentation
9 its status - ST :
C Conditional - the segment or the data element is only transmitted if agreed by the
interchanging parties.
M Mandatory - the segment or the data element must always be transmitted.
10 its format - FT : indication of the representation and length of the value entered for a data
element :
a indicates an alphabetical data element whereby a3 means it has a fixed length of 3
alphabetical digits, whereas a..3 indicates a variable length with a maximum of 3
alphabetical digits.
n indicates a numerical data element whereby n6 means it has a fixed length of 6
numerical digits, whereas n..6 indicates a variable length with a maximum of 6
numerical digits.
an indicates an alpha-numerical data element whereby an5 means it has a fixed length of
5 alpha-numerical digits, whereas an..35 indicates a variable length with a maximum
of 35 alpha-numerical digits.
11 the separators to be used - SP : indication of the end of a composite data element; a single
data element or a segment:
: indicates the end of one of the data elements that are part of a composite data
element.
+ indicates the end of a single or composite data element.
' indicates the end of a segment.

EDI Implementation Guidelines


DELINS OD3 Page 2 of 31
12 specifications for the use of this segment in an interchange with Adient. This specification consists of :
the status indication (ST - see under for details)
the format indication (FT - see under for details)
specific remarks
13 the bordered areas contain specific (code) values to be used and, when required, additional information
regarding those values.
14 shaded areas in a segment description reflect data elements which are not used in the interchange with
Adient
15 example on how the segment will appear in the interchange with Adient.

EDI Implementation Guidelines


DELINS OD3 Page 3 of 31
2 Messages Covert

2.1 Odette DELINS Version 3

2.1.1 EDI Interchange Segments Odette DELINS

Following service segments are as defined by UN/EDIFACT and presented under ISO 9735.
The UNB, UNH, UNT and UNZ segments are the envelope of any message, enclosing all the data that is
being transmitted.
The UNB (Interchange header) and UNZ (Interchange trailer) segments mark respectively the beginning and
the end of an interchange thereby providing a unique interchange control reference.
Within the interchange the UNH (Message header) and UNT (Message trailer) segments uniquely begin and
end the various messages contained in an interchange.

EXAMPLE OF AN INTERCHANGE
STRUCTURE

UNB

UNH

MESSAGE
1

UNT

UNH

MESSAGE
2

UNT

...
...
...

UNH

MESSAGE
N

UNT

UNZ

EDI Implementation Guidelines


DELINS OD3 Page 4 of 31
UNB INTERCHANGE HEADER
EDIFACT status : Mandatory Adient: Mandatory
Level : 0 Occurrences : One per interchange
Mandatory, single occurrence 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.
EDIFACT STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

S001 SYNTAX IDENTIFIER M M M


0001 Syntax identifier M M : M a4 Always : 'UNOA'
0002 Syntax version number M M + M n1 Always : '1'
S002 INTERCHANGE SENDER M M
0004 Sender identification M an..35 : M an..35 Adient ODETTE ID An..4
0007 Identification code qualifier C an..4 : C
0008 Address for reverse routing C an..14 + M an..9 ID of initiating Adient plant
S003 INTERCHANGE RECIPIENT M M
0010 Recipient identification M an..35 : M an..35 Odette Code of Recipient
0007 Identification code qualifier C an..4 :
0014 Routing address C an..14 +
S004 DATE/TIME OF PREPARATION M M
0017 Date of preparation M n6 : M n6 Format: ‘YYMMDD'
0019 Time of preparation M n4 + M n4 Format: ‘HHMM’
0020 INTERCHANGE CONTROL M an..14 + M An13 Value : characters 'DEL' concatenated
REFERENCE with first five digits referring to the
creation date number. Second five digits
referring to a sequential Number.
Example :
First interchange :
'DEL0009070001'
second interchange :
'DEL0000070002'
The Interchange control reference
number will be unique.
S005 RECIPIENTS REFERENCE C
PASSWORD
0022 Recipient's reference/password M an..14 :
0025 Recipient's reference/password qualifier C an2 +
0026 APPLICATION REFERENCE C an..14 + M a6 Always : 'DELINS'
0029 PROCESSING PRIORITY CODE C a1 +
0031 ACKNOWLEDGEMENT REQUEST C n1 +
0032 COMMUNICATIONS AGREEMENT ID C an..35 +
0035 TEST INDICATOR C n1 '

EXAMPLES

UNB+UNOA:1+O0013007096JCIEUAG::0341+1946150505GA01+000907:0947+DEL0009070001’

EDI Implementation Guidelines


DELINS OD3 Page 5 of 31
UNH MESSAGE HEADER
EDIFACT status : Mandatory Adient status : Mandatory
Level : 0 Occurrences : One per message
Mandatory, single occurrence service segment starting and uniquely identifying the message.
EDIFACT STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

0062 MESSAGE REFERENCE NUMBER M an..14 + M an..14 Number identifying uniquely each
message, not to be repeated during the
record keeping year and transmitted
without leading zeroes.
S009 MESSAGE IDENTIFIER M M
0065 Message type identifier M an..6 : M a6 Always : 'DELINS'
0052 Message type version number M an..3 : M n1 Always : '3'
0054 Message type release number M an..3 : M n3 Always : '000'
0051 Controlling agency M an..2 : M a2 Always : 'OD'
0057 Association assigned code C an..6 +
0068 COMMON ACCESS REFERENCE C an..35 +
S010 STATUS OF THE TRANSFER C
0070 Sequence message transfer number M n..2 :
0073 First/last message indicator C a1 '

EXAMPLE
UNH+1+DELINS:3::OD'
This UNH segments identifies the message as a DELINS version 3 as maintained by ODETTE.

UNT MESSAGE TRAILER


EDIFACT status : Mandatory Adient status : Mandatory
Level : 0 Occurrences : One per message
Mandatory, single occurrence service segment ending the message and giving the total number of segments
contained in the message as well as the Control Reference number of the message.
EDIFACT STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

0074 NUMBER OF SEGMENTS IN M n..6 + M n..6


MESSAGE
Control count including the UNH & UNT
segments.
0062 MESSAGE REFERENCE NUMBER M an..14 ' M an..14
Value must be the same as in the Mes-
sage Reference Number (0062) in UNH

EXAMPLE
UNT+22+1'
This UNT segment indicates that the message contains 22 segments including the UNH and UNT segments.

UNZ INTERCHANGE TRAILER


EDIFACT status : Mandatory Adient status : Mandatory
Level : 0 Occurrences : One per interchange
Mandatory, single occurrence service segment ending an interchange and giving the number of messages contained
in the interchange as well as the Interchange Control Reference number.
EDIFACT STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

0036 INTERCHANGE CONTROL COUNT M n..6 + M n..6


Number of messages in an interchange
0020 INTERCHANGE CONTROL M an..14 ' M an..14
REFERENCE
The value must be the same as in Inter-
change Control Reference (020) in seg-
ment UNB

EDI Implementation Guidelines


DELINS OD3 Page 6 of 31
EXAMPLE
UNZ+35+DEL0009070001
This UNZ segment indicates that the interchange with Control Reference DEL0009070001 contains 35 messages.

EDI Implementation Guidelines


DELINS OD3 Page 7 of 31
2.1.2 Branching diagram
The branching diagram shows the structure of the message. It is a combination of various segments
that are organised in a certain hierarchical order. A segment is a pre-defined set of functionally related
values (e.g. segment SDT groups all values that relate to a Seller : name - address - contact person -
etc.)
Each segment within the branching diagram is broken down into one or multiple data elements. Within
a segment, only those data elements that contain data must appear.

Level

(0) MID SDT MDT BDT ARI DLP


3 3 3 3 3 3
M 1 M 1 C 1 C 1 C 1 C 1

(1) CSG FTX


3 3
M R C R

(2) ITA ARD


3 3
C 1 M R

(3) PDI SAD FTX DST PDN SID DEL TCO ADI
3 3 3 3 3 3 3 3 1
C 1 C 1 C R C 1 C R C R M R C R C 1

Legend
CSG Name of the segment
2 Version number of segment
M R Number of occurrences (R = more than one occurrence)

Status (M = Mandatory - C = Conditional

NOTE : shaded areas in the branching diagram indicate that the segment is not used in the interchange described in this
documentation

EDI Implementation Guidelines


DELINS OD3 Page 8 of 31
2.1.3 DELINS Version 3 Segment description
This part includes all the segments defined in the standard whether used or not used in the
interchange between Adient and its Trading Partners. The segments are described in the same
sequence as they appear in the message.

MID MESSAGE IDENTIFICATION


ODETTE status : Mandatory Adient status : Mandatory
Level : 0 Occurrences : One per message
Mandatory, single occurrence segment which must contain the unique identification of a Delivery Instruction by
means of its number, date and time of issuance and its authentication, according to a mutually agreed system, if
there is any concern about the validity of the Delivery Instruction.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

1004 Document number M an..17 + M an..17 Contains the Delivery Instruction number
assigned by the Adient system. This is
the Schedule Release ID and it is
unique for one items schedule.
Document Date and Time C M
2007 Document Date, coded M n6 : M n6 Format: ‘YYMMDD’
2002 Time C n4 +
4426 Authentication C an..35 '

EXAMPLE
MID+000033+000907'
This MID segment identifies the message as Delivery Instruction No. 000033 issued on September 07, 2000.

EDI Implementation Guidelines


DELINS OD3 Page 9 of 31
SDT SELLER DETAILS
ODETTE status : Mandatory Adient status : Mandatory
Level : 0 Occurrences : One per message
Mandatory, single occurrence segment providing the identification of the seller (Supplier) by means of his
vendor code. Commercial, accounting and/or other contact details may be added when required for future
contact.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Seller M M
3347 Seller, coded C an..20 : M an..20 Contains Supplier Code issued by Adient
Code of the legal company. system.
3036 Party Name C an..35 : 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 :
3124 Name and Address Line C an..35 :
3296 Internal Id. No allocated to a Trading C an..17 +
Partner
Commercial Department or Employee C
3413 Department or Employee, coded C an..17 :
3412 Department or Employee 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 :
3124 Name and Address Line C an..35 +
Accounting Department or Employee C
3413 Department or Employee, coded C an..17 :
3412 Department or Employee 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 :
3124 Name and Address Line C an..35 +
3808 VAT registration number C an..17 +
3207 Country, coded C a2 +
Contact details C
3412 Department or Employee C an..35 :
3928 Telephone number C an..17 :
3929 Telephone Extension C an..17 :
3927 Telex Number C an..17 :
3926 Fax Number C an..17 :
3920 Teletex Number C an..17 '

EXAMPLES

SDT+31804:BERTRAND FAURE EQUIP/FAURECI'


This SDT segment identifies the recipient of the Delivery Instruction message as the seller/Supplier with vendor-code 31804.

EDI Implementation Guidelines


DELINS OD3 Page 10 of 31
MDT MANUFACTURER DETAILS
ODETTE status : Conditional Adient status : Not used
Level : 0 Occurrences : One per message
Conditional, single occurrence segment giving details of the manufacturer if different from the seller of the articles
defined in the following ARD segments.
The MDT segment is not used in the interchange described in this documentation.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Supplier M
3281 Supplier Coded C an..20 :
3036 Party Name 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 :
3124 Name and Address Line C an..35 :
3296 Internal Id. No. allocated to a Trading C an..35 +
Partner
Supplier Department or Employee C
3413 Department or Employee, coded. C an..17 :
3412 Department or Employee 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 :
3124 Name and Address Line C an..35 +
Country, coded C a2 +
3207
Contact details C
3412 Department or Employee C an..35 :
3928 Telephone number C an..17 :
3929 Telephone Extension C an..17 :
3927 Telex Number C an..17 :
3926 Fax Number C an..17 :
Teletex Number C an..17 '
3920

EDI Implementation Guidelines


DELINS OD3 Page 11 of 31
BDT BUYER DETAILS
ODETTE status : Mandatory Adient status : Mandatory
Level : 0 Occurrences : One per message
Mandatory, single occurrence segment giving details of the buyer. A coded or uncoded name and
address must be included.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Buyer M M
3003 Buyer, coded C an..20 : M an..20 Contains Customer Code of Adient at
Supplier
3036 Party Name C an..35 : C an..35
3124 Name and Address Line C an..35 : C an..35
3124 Name and Address Line C an..35 : C an..35
3124 Name and Address Line C an..35 :
3124 Name and Address Line C an..35 :
3296 Internal Id. No. allocated to a Trading C an..17
Partner C an..35 +
Commercial Department or Employee C
3413 Department or Employee, coded C an..17 :
3412 Department or Employee 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 :
3124 Name and Address Line C an..35 +
Accounting Department or Employee C
3413 Department or Employee, coded C an..17 :
3412 Department or Employee 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 :
3124 Name and Address Line C an..35 +
3808 VAT Registration number C an..17 +
3835 Country, coded C a2 +
Contact details C
3412 Department or Employee C an..35 :
3928 Telephone number C an..17 :
3929 Telephone Extension C an..17 :
3927 Telex Number C an..17 :
3926 Fax Number C an..17 :
3920 Teletex Number C an..17 '

EXAMPLE
BDT+3410:Adient ROTH SA:Adient ROTH SA'
This BDT segment identifies JC as the sender of the Delivery Instruction message.

EDI Implementation Guidelines


DELINS OD3 Page 12 of 31
ARI ADDITIONAL RELEASE INFORMATION
ODETTE status : Conditional Adient status : Not used
Level : 0 Occurrences : One per message
Conditional, single occurrence segment providing effective from/to dates indicating the validity period of the
whole message, and which indicates what action should be taken by the dates given in specific schedules.
Effective from/to dates must be used when previous instructions are to be amended and a matching key is not
available for use within the DEL segment..
The ARI segment is not used in the interchange described in this documentation.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

7903 Release type code C n1 +


Required to clarify date/time shown in
DEL if not stated in contract/order.
Delivery Instruction Validity C
2069 Effective From Date, coded M n6 :
2073 Effective To Date, coded C n6 +
7808 Schedule Release Frequency C an..2 '

EDI Implementation Guidelines


DELINS OD3 Page 13 of 31
CSG CONSIGNEE DETAILS
ODETTE status : Mandatory Adient status : Mandatory
Level : 1 Occurrences : Several per message
Mandatory, repeatable segment providing details of the consignee (delivery destination). A coded or uncoded
name and/or address must be included. The segment is used to provide delivery location details. All segments
below the CSG segment relate to the consignee identified in the preceding CSG segment and may appear at
least once before the CSG is repeated to give details of another consignee (1 CSG segment per consignee).
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Consignee M M
3133 Consignee, coded C an..20 : M an..17 Contains Customer Code of Adient at
Supplier
3036 Party Name C an..35 : 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 :
3124 Name and Address Line C an..35 :
3296 Internal Id. No. allocated to a Trading C an..17 +
Partner
Final Delivery Point C M
3921 Final Delivery Point, coded C an..17 : M an..17 Adient final delivery plant
3920 Final Delivery Point C an..35 : C codes. 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 an..35 +
Additional Destination Details C M
3923 Additional Destination Details, coded C an..17 : M an..5 Dock code identification provided by
BGE.
3922 Additional Destination Details 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 :
Name and Address Line an..35 +
3124
3207 Country, coded C a2 +
Contact details C
3412 Department or Employee C an..35 :
3928 Telephone number C an..17 :
3929 Telephone Extension C an..17 :
3927 Telex Number C an..17 :
3926 Fax Number C an..17 :
Teletex Number C an..17 '
3920

EXAMPLE
CSG+3410:Adient ROTH SA+34101:Adient ROTH'
This CSG segment indicates that the material must be delivered to Adient ROTH (3410).

EDI Implementation Guidelines


DELINS OD3 Page 14 of 31
ITA INVOICE TO ADDRESS
ODETTE status : Conditional Adient status : Not used
Level : 2 Occurrences : One per CSG segment
Conditional, single occurrence segment containing details of the Accounting Department or Employee to which
invoices must be sent for goods delivered to the consignee identified in the preceding CSG segment. If the
segment is used a coded or uncoded name and/or address must be included.
The ITA segment is not used in the interchange described in this documentation.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Accounting Department or Employee M


3413 Department or Employee, coded C an..17 :
3412 Department or Employee 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 :
3124 Name and Address Line C an..35 '

EDI Implementation Guidelines


DELINS OD3 Page 15 of 31
ARD ARTICLE DETAILS
ODETTE status : Mandatory Adient status : Mandatory
Level : 2 Occurrences : Several per message
Mandatory, repeatable segment identifying an article for which Delivery Instructions are being transmitted. It
must contain the Adient assigned part number and the reference to the applicable Purchase Order/Contract
authorising the delivery. If for one Delivery Instruction an article is related to two different orders, two
occurrences of the ARD segment are required : one for each order number. All segments below the ARD
segment relate to the article specified in the preceding ARD segment and may all appear at least once before
the ARD segment is repeated to give details of another article (1 ARD segment per article/part number per CSG
segment).
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Article Identification M M
7304 Buyer's Article Number M an..35 : M an..35 Number assigned by Adient
7194 Seller's Article Number C an..35 :
an..35
7008 Article Description C an..35 : C
7008 Article Description C an..35 : C an..35
7008 Article Description C an..35 :
7008 Article Description C an..35 :
7008 Article Description C an..35 +
Quantity and Unit C C
6270 Quantity Delivered C n..10 :
6410 Measure Unit Specifier C an..3 + C an..3 See code list to be used with Adient on
Chapter 3.1.3 of this document (ARD
Article Details - tag 6410).
Order or Contract Identification M M
1022 Order Number M an..17 : M an..17 Always Purchase Order Number .
2001 Date, coded C n6 +
Country of Origin C
3239 Country of Origin, coded C a2 :
3238 Country of Origin C an..17 +
Free Text C C
4440 Free Text M an..70 : M CHANGED STATUS VERSUS
STANDARD
Warehouse Coordinates
4440 Free Text C an..70 :
4440 Free Text C an..70 +
Technical Status C
7860 Design Revision Number C an..35 :
1376 Engineering Change Number C an..17 :
2001 Date, coded C n6 '

EXAMPLES

ARD+IM00537::ARMAT.ARTIC.9626173880/B+:PI+PO334242'
This ARD segment identifies the article to be delivered as part number IM00537 covered by Purchase Order Nr PO334242.

EDI Implementation Guidelines


DELINS OD3 Page 16 of 31
PDI REFERENCE TO PREVIOUS DELIVERY INSTRUCTION
ODETTE status : Conditional Adient status : Mandatory
Level : 3 Occurrences : One per ARD segment
Conditional, single occurrence segment containing a reference to the previous Delivery Instruction number in
which the last schedule information for this article was transmitted and which enables the recipient to update
previous schedules accurately. In data exchange with Adient it is used to give details regarding previously
send Delivery Instructions related to the article (part number) defined in the preceding ARD segment.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

1004 Document Number M an..17 + M an..17 Identification of the previously send


Delivery instruction number Delivery Instruction.
Document Date and time C M
2007 Document Date, coded M n6 : M n6
2002 Time C n4 +
4426 Authentication C an..35 '

EXAMPLE
PDI+000031+000824'
This PDI segment refers to a previously send Delivery Instruction i.e. Nr 000031 dated August 24, 2000.

EDI Implementation Guidelines


DELINS OD3 Page 17 of 31
SAD SUPPLEMENTARY ARTICLE DETAILS
ODETTE status : Conditional Adient status : Mandatory
Level : 3 Occurrences : One per ARD segment
Conditional, single occurrence segment providing additional information on the article identified in the preceding
ARD segment.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

7807 Instruction Update Action Code M n1 + M n1 Always '1' = Schedule


Material Control Department C C
3413 Department or Employee, coded C an..17 : M an..17 Code assigned by Adient .
3412 Department or Employee 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 :
3124 Name and Address Line C an..35 +
7153 Article Status, coded C n2 + C n2
2025 Delivery Last Date, coded C n6 +
2013 Frequency, coded C an..2 +
7424 Transport Group Number C an..17 +
Supplier Department or Employee C
3413 Department or Employee, coded C an..17 :
3412 Department or Employee 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 :
3124 Name and Address Line C an..35 '

EXAMPLE
SAD+1+34101+03'
This SAD segment indicates that the message is a schedule.

EDI Implementation Guidelines


DELINS OD3 Page 18 of 31
FTX FREE TEXT
ODETTE status : Conditional Adient status : Not Used
Level : 3 Occurrences : Several per ARD segment
Segment giving the possibility to transmit clear form messages related to the article defined in the preceding
ARD segment.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Free Text M
4440 Free Text M an..70 : M an..70
4440 Free Text C an..70 : C an..70
4440 Free Text C an..70 ' C an..70

EDI Implementation Guidelines


DELINS OD3 Page 19 of 31
DST DELIVERY STATUS
ODETTE status : Conditional Adient status : Mandatory
Level : 3 Occurrences : One per ARD segment
Conditional, single occurrence segment containing reconciliation data necessary for the buyer and seller to
have a common understanding of the quantities received/scheduled for the article identified in the preceding
ARD segment. Quantitative information and its date/time of calculation are available. In the data exchange
with Adient this segment is Mandatory and identifies the cumulative quantity received for the part number
identified in the preceding ARD segment as well as the date on which this quantity was calculated.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Calculation Date and Time M M


2253 Calculation Date, coded M n6 : M n6 The Adient-application has booked all
deliveries taken in until now and included
them in the material scheduling.
Format: ‘YYMMDD’
2002 Time C n4 +
Cumulative Quantity C M
6802 Actual Cumulative Quantity Scheduled C n..10 : M n..10
6804 Actual Cumulative Quantity Received C n..10 : M n..10 At the time of inventory, the cumulative
Net received quantities recommended quantity is set to zero.
6806 Delivery Quantity Balance C n..10 :
Under deliveries with a +;
Over deliveries with a -.
2121 Quantities Accumulation Start Date, C n6 +
coded
To be used if not stated in the contract
6812 Quantity Balance C n..10 +
6905 Cumulative Quantity Scheduled up to
Accumulation Start Date C n..10 +
6909 Quantity in Stock C n..10 '

EXAMPLE
DST+000907+48300:48300'
This DST segment indicates that the actual cumulative quantity received, for the part number defined in the preceding ARD
segment, as calculated on September 07, 2000 was 48300 pieces.

EDI Implementation Guidelines


DELINS OD3 Page 20 of 31
PDN PREVIOUS DESPATCH NOTE
ODETTE status : Conditional Adient status : Conditional
Level : 3 Occurrences : Several per ARD segment
Conditional segment which occurs once and which contains Despatch Note references for deliveries received
and processed by the consignee up to the date/time of calculation by the buyer for the article identified in the
preceding ARD segment. This information can be used by the seller to clarify which deliveries have been
included in the quantities calculated by the buyer.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Despatch Note M M
1128 Despatch Note Number C an..17 : M an..17 Number is always the Despatch Advice =
(Lieferschein) number.
2219 Despatch Note Date, coded C n6 + M n6 Format: ‘YYMMDD’
Quantity Delivered/Received C C
6270 Quantity Delivered C n..10 : C n..10 The field length is limited to 9 characters
Quantity specified on the despatch note and is allowing up to 3 decimal digits.
Since quantities are usually expressed in
pieces there is no need to transmit
decimals.
6872 Actual Quantity Received C n..10 +
Recommended to be used if received
quantity differs from that specified in the
Despatch Advice.
Reception Date and Time C C
2441 Goods Receipt Date, coded M n6 : C n6 Format: YYMMDD
2002 Time C n4 '

EXAMPLE
PDN+6095025:000425+1050+000425'
This PDN segment indicates that the last recorded Despatch Advice, related to the delivery of the part number defined in the
preceding ARD segment, was the document with number 6095025 for 425 pieces received on April 25, 2000.

EDI Implementation Guidelines


DELINS OD3 Page 21 of 31
SID SCHEDULE INDICATOR DETAILS
ODETTE status : Conditional Adient status : Mandatory
Level : 3 Occurrences : Several per ARD segment
Conditional segment which can be repeated up to five times for the article identified in the preceding ARD
segment, one for each code value of tag '6811 - Schedule Status Indicator'. In the data exchange with Adient
this segment is Mandatory and is used to provide to the seller details regarding the kind of authorisation
(fabrication and/or material) and the type of period involved. The segment is usually only repeated twice per
ARD segment.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

6811 Schedule Status Indicator M n1 + M n1 Contains different Indicators: See


Chapter 3.1.3.
Periods C M
2151 Type of Period, coded C an..3 : M an1 'D' = days,
'W' = weeks,
'M' = monthly
2152 Number of periods C n..3 : M n..3 Number of month, weeks and month.
6906 Latest Cumulative Quantity Scheduled C n..10 :
Relative to data element 6811
6907 Highest Quantity Previously Scheduled C n..10 :
Relative to data element 6811
1430 Reference to Highest Quantity C an..17 :
Previously Scheduled
Delivery instruction number relating to
previous highest cumulative quantity.
6272 Number of Working Days C n..3 +
2829 Authorisation Date, coded C n6 '
EXAMPLE
SID+1+D:17'SID+4+D:13'SID+4+W:0'SID+4+M:0'
This SID segments indicate that the Material is firm for 17 days with 13 daily, 4 weekly and 0 monthly planning.
The Shipping Code is according to the agreement.

EDI Implementation Guidelines


DELINS OD3 Page 22 of 31
DEL DELIVERY DETAILS
ODETTE status : Mandatory Adient status : Mandatory
Level : 3 Occurrences : Several per ARD segment
Mandatory, repeatable segment containing the main data of the DELINS message. In this segment the buyer
specifies, for the article identified in the preceding ARD segment, the quantity required with associated dates
and times. A specific date or a time interval as well as a quantity must be given.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Date, Time , Periods M M


2803 First Date, coded C n6 : M n6 Format : always YYMMDD.
2002 Time C n4 :

2805 Last Date, coded C n6 :


To be used if an interval is valid for the
specified quantity.
2002 Time C n4 :
Only used if 2805 is used and time also
neRATIO LTD. to be specified.
2836 Time Period, coded C n8 :
Mandatory if data elements 2803 and
2805 are not used.

6272 Number of Working Days C n..3 +


Quantities, Status and Delivery Date M M
6060 Quantity M n..15 : M n..15 Quantity to be delivered, released for
fabrication or for material.
1310 Part Consignment Number C an..17 :
Specifically identifies a schedule
quantity for replacement parts
7803 Delivery Instruction Reason, coded C n1 : C n1
6811 Schedule Status Indicator C n1 : C n1
Mandatory if segment SID is not used.
6903 Cumulative Quantity Scheduled C n..10 : C n..10
Since agreed Accumulation. Start Date
given in DST segment.
6904 Cumulative Quantity Previously Sched- C n..10 '
uled
At the same point in time on the
previous schedule.

EXAMPLE
DEL+000906+0:::1:48300'
These DEL segments indicate the quantity required.

EDI Implementation Guidelines


DELINS OD3 Page 23 of 31
TCO TYPE OF PACKAGES
ODETTE status : Conditional Adient status : Not user
Level : 3 Occurrences : Several per ARD segment
Conditional, repeatable segment containing data specifying the packaging requirements for the article identified
in the preceding ARD segment. This segment can repeat to provide details of different packaging
requirements for the same article. In the data exchange with Adient this segment will normally appear only
once per ARD segment and it will provide the identification of the packaging requested by Adient for the article
defined in the preceding ARD segment as well as the quantity in the identified package.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Package data M M
7064 Type of Packages C an..35 :
1906 Package Reference Number C an..35 : M an..22 Internal package code given by Adient and
to be agreed upon.
1131 Code List Identifier, coded C an2 +
7224 Number of Packages C n..6 +
Quantity C C
6853 Quantity of Articles in Package M n..10 : M n..7 Filling quantity of announced packaging
device.
6410 Measure Unit Specifier C an..3 +
Default value : pieces
Dimensions C
6168 Length Dimension C n..5 :
6140 Width Dimension C n..5 :
6008 Height Dimension C n..5 :
6410 Measure Unit Specifier C an..3 +
Default value : meters
Weight C
6292 Gross Weight C n..11 :
6160 Net Weight C n..11 :
6410 Measure Unit Specifier C an..3 +
Default value : kilos
2069 Effective From Date, coded C n6 '

EDI Implementation Guidelines


DELINS OD3 Page 24 of 31
ADI ARTICLE DELIVERY INSTRUCTION
ODETTE status : Conditional Adient status : Not used
Level : 3 Occurrences : One per ARD segment
Conditional, single occurrence segment allowing a specific and unique Delivery Instruction reference number to
be allocated for the article identified in the preceding ARD segment.
The ADI segment is not used in the interchange described in this documentation.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

1004 Document Number M an..17 +


Document Date and Time C
2007 Document Date, coded M n6 :
2002 Time C n4 +
4426 Authentication C an..35 '

EDI Implementation Guidelines


DELINS OD3 Page 25 of 31
DLP DELIVERY PARTY DETAILS
ODETTE status : Conditional Adient status : Not used
Level : 0 Occurrences : One per message
Conditional, single occurrence segment containing the name and address of a third party which is to be involved
in the physical flow of goods from seller to buyer.
The DLP segment is not used in the interchange described in this documentation.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Delivery Party M
3145 Delivery Party, coded C an..20 :
3036 Party Name 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 :
3124 Name and Address Line C an..35 :
3296 Internal Id. No. allocated to a Trading C an..17 +
Partner
Delivery Party Department or Employee C
3413 Department or Employee, coded C an..17 :
3412 Department or Employee 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 :
3124 Name and Address Line C an..35 +
3835 Country, coded C a2 +
Contact details C
3412 Department or Employee C an..35 :
3928 Telephone number C an..17 :
3929 Telephone Extension C an..17 :
3927 Telex Number C an..17 :
3926 Fax Number C an..17 :
Teletex Number C an..17 '
3920

EDI Implementation Guidelines


DELINS OD3 Page 26 of 31
FTX FREE TEXT
ODETTE status : Conditional Adient status : Conditional
Level : 1 Occurrences : Several per message
Conditional, repeatable segment allowing the transmission of clear text format related to the entire message.
ODETTE STANDARD Adient IMPLEMENTATION
TAG DATA ELEMENT NAME ST FT SP ST FT Adient REMARKS

Free text M M
4440 Free Text M an..70 : M an..70
4440 Free Text C an..70 : C an..70
4440 Free Text C an..70 ' C an..70

EXAMPLES
FTX+DATES SHOWN ARE FOR RECEIPT IN PLANT:CHEQUE 90 JOURS FIN DE MOIS LE 10' This FTX segment is used
for additional information.

EDI Implementation Guidelines


DELINS OD3 Page 27 of 31
2.1.4 Code Description

Segment ARD - Article Details

6410 - Measure Unit Specifier

Indication of the unit of measurement in which weight (mass), capacity, length, area, volume or other quantity is
expressed.
Source : ISO-Code - only a limited number of values are indicated in this list. If other, less commonly used, code
values are required please contact ypur local EDI Co-ordinator.

PCE Piece/decimal piece


KGM Kilogram
KMT Kilometre
LTR Litre
MTR Metre
MTK Square metre
TNE Ton

Segment SID - Schedule Indicator Details

2151 - Type of Period


Shipping code used to indicate the delivery frequency as well as the specific day in the week on which delivery
should be done.
Source : Adient assigned codes.

Blank No special shipping instruction.


1 Firm Qty.
4 Planed Delivery according to agreement.

Segment DEL - Delivery Details

7803 – Delivery Instruction Reason


Delivery code used to indicate the as a planned
requirement Source : Adient assigned codes.

Blank No special shipping instruction.


3 Planned and/or Firm Qty.

EDI Implementation Guidelines


DELINS OD3 Page 28 of 31
2.1.5 Odette DELINS Version 3 Example

UNB+UNOA:1+O0013007096JCIEUAG::0341+13388256490001+000907:0948+DEL000907000
0'
UNH+211+DELINS:3::OD'
MID+000033+000907'
SDT+31804:BERTRAND FAURE EQUIP/FAURECI'
BDT+3410:Adient ROTH SA:Adient ROTH SA'
CSG+3410:Adient ROTH SA+34101:Adient ROTH'
ARD+IM00359::INS 9610147180/C ACC AR+:PI+PO334242'
PDI+000031+000824'
SAD+1+34101+03'
DST+000907+14360:13760'
PDN+30070534:000905+410+000905'
SID+1+D:17'
SID+4+D:13'
SID+4+W:0'
SID+4+M:0'
DEL+000906+600::3'
DEL+000906+0:::1:14360'
DEL+000907+0:::1:14360'
DEL+000908+0:::1:14360'
DEL+000911+0:::1:14360'
DEL+000912+0:::1:14360'
DEL+000913+0:::1:14360'
DEL+000914+0:::1:14360'
DEL+000915+0:::1:14360'
DEL+000918+0:::1:14360'
DEL+000919+0:::1:14360'
DEL+000920+0:::1:14360'
DEL+000921+0:::1:14360'
DEL+000922+0:::1:14360'
FTX+DATES SHOWN ARE FOR RECEIPT IN PLANT:CHEQUE 90 JOURS FIN DE MOIS LE 10'
UNT+33+211'
UNH+211+DELINS:3::OD'
MID+000033+000907'
SDT+31804:BERTRAND FAURE EQUIP/FAURECI'
BDT+3410:Adient ROTH SA:Adient ROTH SA'
CSG+3410:Adient ROTH SA+34101:Adient ROTH'
ARD+IM00537::ARMAT.ARTIC.9626173880/B+:PI+PO334242'
PDI+000031+000824'
SAD+1+34101+03'
DST+000907+48300:48300'
PDN+6095025:000425+1050+000425'
SID+1+D:17'
SID+4+D:13'
SID+4+W:0'
SID+4+M:0'
DEL+000906+0:::1:48300'
DEL+000907+0:::1:48300'
DEL+000908+0:::1:48300'
DEL+000911+0:::1:48300'
DEL+000912+0:::1:48300'

EDI Implementation Guidelines


DELINS OD3 Page 29 of 31
DEL+000913+0:::1:48300'
DEL+000914+0:::1:48300'
DEL+000915+0:::1:48300'
DEL+000918+0:::1:48300'
DEL+000919+0:::1:48300'
DEL+000920+0:::1:48300'
DEL+000921+0:::1:48300'
DEL+000922+0:::1:48300'
FTX+DATES SHOWN ARE FOR RECEIPT IN PLANT:CHEQUE 90 JOURS FIN DE MOIS LE 10'
UNT+29+211'
UNZ+2+DEL0009070000'

EDI Implementation Guidelines


DELINS OD3 Page 30 of 31
Document Revision

Version Date Description Author


1.0 2000-09-07 Creation Dirk Mueller
2.0 2000-10-31 Enhancement Dirk Mueller
2.1 2002-03-31 Added additional Fields in AVIEXP Dirk Mueller
2.2 2003-02-04 Enabled ARD 7008 2nd Group Andreas Hausdorf
2.3 2003-05-02 Changed DST 6806 to ODETTE Standard Marc Tillmann
2.4 2003-07-02 Made UNB 0007-1 conditional Andreas Hausdorf
2.5 2007-10-02 Revision and change of CI Marc Tillmann
2.6 2009-04-14 Changed ARD:6410 Hans-Ulrich Berger
2.7 2016-Aug-10 Modified JCI or Johnson Controls references to be Hemant Bhardwaj
Adient. Removed JCI logo and added Adient logo.

EDI Implementation Guidelines


DELINS OD3 Page 31 of 31

You might also like