Automotive Experience Division. EDI Implementation Guideline. Delivery Schedule (DELFOR)

Transcription

1 Based on EDIFACT D96A DELFOR Public Standard Automotive Experience Division EDI Implementation Guideline Delivery Schedule (DELFOR) Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 1 of 96

2 Table of Contents Document Change Log... 4 Requirement Designations in Guide... 5 AD96AENVDELFOR Adient D96A DELFOR Envelope Structure... 6 Segment: UNA Service String advice... 7 Segment: UNB Interchange Header... 8 Segment: UNG Functional Group Header Segment: UNE Functional Group Trailer Segment: UNZ Interchange Trailer DELFOR Delivery Schedule Message Introduction Branching Diagram Loop/Segment Table Segment: UNH Message Header Segment: BGM Beginning of Message Segment: DTM Date/Time/Period Message Creation Date Segment: DTM Date/Time/Period Horizon Start Date Segment: DTM Date/Time/Period Horizon End Date Segment: RFF Reference Segment: NAD Name and Address Seller (Supplier) Segment: NAD Name and Address Buyer (Adient Plant) Segment: UNS Section Control Segment: NAD Name and Address Consignee (Ship To) Segment: LIN Line Item Segment: PIA Additional Product Id Segment: IMD Item Description Segment: LOC Place/Location Identification Adient Dock Code Segment: LOC Place/Location Identification Other Internal Adient Location Segment: DTM Date/Time/Period Calculation Date Segment: DTM Date/Time/Period Finished Goods Go Ahead End Date Segment: DTM Date/Time/Period Raw Materials Go Ahead End Date Segment: RFF Reference Purchase Order Number Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 2 of 96

3 Segment: QTY Quantity (12) Receipt Discrete Quantity Segment: RFF Reference Receipt Despatch Advice Number Segment: DTM Date/Time/Period Receipt Date Segment: QTY Quantity (70) Last Receipt Cumulative Quantity Segment: QTY Quantity (78) Scheduled Cumulative Quantity Segment: QTY Quantity (83) Backorder Quantity Segment: SCC Scheduling Conditions Segment: DTM Date/Time/Period Latest Delivery or Pickup Date/Time Segment: DTM Date/Time/Period Earliest Delivery or Pickup Date/Time Segment: QTY Quantity (84) Urgent Delivery Quantity Segment: SCC Scheduling Conditions Segment: DTM Date/Time/Period Latest Delivery or Pickup Date/Time Segment: DTM Date/Time/Period Earliest Delivery or Pickup Date/Time Segment: QTY Quantity (113) Delivery Quantity Segment: SCC Scheduling Conditions Segment: DTM Date/Time/Period Latest Delivery or Pickup Date/Time Segment: DTM Date/Time/Period Earliest Delivery or Pickup Date/Time Segment: PAC Package Segment: QTY Quantity (52) Per Pack Segment: UNS Section Control Segment: UNT Message Trailer DELFOR Delivery Schedule Examples Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 3 of 96

4 Document Change Log Version Date Description Author Creation Hans-Ulrich Berger Revision and change of CI Marc Tillmann Enhancement Hans-Ulrich Berger Changed RFF+ON 1156 to mandatory Tim Diedershagen Added qualifier 153 and 154 to DTM, Position Ralf Größle 0120 (now position 0360) Added option for SCC 2017 plus description and Ralf Größle example Detailed NAD segment for qualifier SU (supplier Ralf Größle DUNS) segment now removed from spec L. Kreimes UNB.0020 is hardcoded to 1. This has been Ralf Größle replaced in the description. The GXS translator is generating an interchange control number other than 1 L. Kreimes PAC segment updated Raghava Bandarupalli PAC segment updated Raghava Bandarupalli PAC segment updated Raghava Bandarupalli SCC segment updated Raghava Bandarupalli PIA segment updated with Engineering Change Stijn Daerden Level Changed DTM+63 and DTM+64 segments date Stijn Daerden format to include pickup times Added qualifiers 158 & 159 to DTM Position Stijn Daerden 0030; modified description of DTM+154 Position 0360; added QTY+84 Position Recreated DELFOR guide using EDISIM which Laurie Kreimes caused segment position numbers to be reordered; placed the PAC segment in the proper location in the guide; modified LOC segment Position 0350 to be optional; modified description for DTM+153 segment Position 0360; updated data examples to have more recent dates Modified the data example on each segment page to match the Example 1 data. Modified the segment table reference for the SG12(78) segment, removing the reference to Prior Cum Qty Required. Modified the SG12(78) segment page, removing the reference to Prior Cum Qty Required and modified the Notes to Trading Partner to reflect the correct information for this segment. Modified the Example 1 data to reflect the QTY(70) and QTY(78) quantities. Modified the Example 2 data to reflect the correct QTY(78) quantity and corrected the last 3 QTY(113) quantities to be a multiple of the standard pack quantity. Modified the UNA Data Example to reflect a Laurie Kreimes Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 4 of 96

5 properly formatted UNA segment Modified JCI or Johnson Controls references to be Adient. Removed Johnson Controls logo and added Adient logo. Laurie Kreimes Requirement Designations in Guide C M R = Conditional = Mandatory = Required Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 5 of 96

6 AD96AENVDELFOR Adient D96A DELFOR Envelope Structure Introduction: The Service String Advice, UNA, and the service segments UNB to UNZ shall appear in the below stated order in an interchange. There may be several functional groups or messages within an interchange and several messages in a functional group. A message consists of segments. Adient Pos. Seg. Base Group Notes and Attributes No. ID Name Attributes Max.Use Repeat Comments 0005 UNA Service String advice C 1 M 0010 UNB Interchange Header M UNG Functional Group Header C UNE Functional Group Trailer C 1 M 0040 UNZ Interchange Trailer M 1 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 6 of 96

7 Segment: UNA Service String advice Position: 0005 Group: Level: 0 Usage: Conditional (Optional) Purpose: To define the characters selected for use as delimiters and indicators in the rest of the interchange that follows: The specifications in the Service string advice take precedence over the specifications for delimiters etc. in segment UNB. See clause 4. Dependency Notes: Semantic Notes: Comments: Notes: When transmitted, the Service string advice must appear immediately before the Interchange Header (UNB) segment and begin with the upper case characters UNA immediately followed by the six characters selected by the sender to indicate, in sequence, the following functions: Notes to Trading Partner The UNA segment is optional in an EDIFACT interchange. The specifications in the UNA segment define the characters used as separators and indicators for the interchange. This segment will only be sent if the interchange contains non-standard separator characters. Data Examples UNA+>+*+.+\++~ Data Element Summary User Data Component Attribute Element Element Name Attributes M UNA1 COMPONENT DATA ELEMENT SEPARATOR M an1 M UNA2 DATA ELEMENT SEPARATOR M an1 M UNA3 DECIMAL NOTATION M an1 Comma or full stop M UNA4 RELEASE INDICATOR M an1 If not used, insert space character M UNA5 RESERVED FOR FUTURE USE M an1 Insert space character M UNA6 SEGMENT TERMINATOR M an1 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 7 of 96

8 Segment: UNB Interchange Header Position: 0010 Group: Level: 0 Usage: Mandatory Purpose: To start, identify and specify an interchange Dependency Notes: Semantic Notes: Comments: Business Rules: Variable Name: UNB Notes: Data Examples UNB+UNOA:3+SENDER-ID+RECEIVER-ID : DELFOR Data Element Summary User Data Component Attribute Element Element Name Attributes M S001 SYNTAX IDENTIFIER M Identification of the agency controlling the syntax and indication of syntax level. M 0001 Syntax identifier M a4 Coded identification of the agency controlling a syntax and syntax level used in an interchange. M 0002 Syntax version number M n1 Version number of the syntax identified in the syntax identifier (0001). M S002 INTERCHANGE SENDER M Identification of the sender of the interchange. M 0004 Sender identification M an..35 Name or coded representation of the sender of a data interchange. The sender identification can be the company EAN or DUNS code or a company-specific code Partner identification code qualifier C an..4 Qualifier referring to the source of codes for the identifiers of interchanging partners. Qualifiers to be determined by trading partner relationship Address for reverse routing C an..14 Address specified by the sender of an interchange to be included by the recipient in the response interchanges to facilitate internal routing. M S003 INTERCHANGE RECIPIENT M Identification of the recipient of the interchange. M 0010 Recipient identification M an..35 Name or coded representation of the recipient of a data interchange. The receiver identification can be the company EAN or DUNS code or a company specific code Partner identification code qualifier C an..4 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 8 of 96

9 Qualifier referring to the source of codes for the identifiers of interchanging partners. Qualifiers to be determined by trading partner relationship Routing address C an..14 Address specified by the recipient of an interchange to be included by the sender and used by the recipient for routing of received interchanges inside his organization. M S004 DATE AND TIME OF PREPARATION M Date and time of preparation of the interchange. M 0017 Date of preparation M n6 Local date when an interchange or a functional group was prepared. Format: YYMMDD M 0019 Time of preparation M n4 Local time of day when an interchange or a functional group was prepared. Format: HHMM M 0020 INTERCHANGE CONTROL REFERENCE M an..14 Unique reference assigned by the sender to an interchange. S005 RECIPIENTS REFERENCE PASSWORD C Reference or password as agreed between the communicating partners. M 0022 Recipient reference/password M an..14 Unique reference assigned by the recipient to the data interchange or a password to the recipient's system or to a third party network as specified in the partners interchange agreement Recipient reference/password qualifier C an2 Qualifier for the recipient's reference or password. Must Use 0026 APPLICATION REFERENCE C an..14 Identification of the application area assigned by the sender, to which the messages in the interchange relate e.g. the message identifier if all the messages in the interchange are of the same type PROCESSING PRIORITY CODE C a1 Code determined by the sender requesting processing priority for the interchange ACKNOWLEDGEMENT REQUEST C n1 Code determined by the sender for acknowledgement of the interchange COMMUNICATIONS AGREEMENT ID C an..35 Identification by name or code of the type of agreement under which the interchange takes place TEST INDICATOR C n1 Indication that the interchange is a test. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 9 of 96

10 Segment: UNG Functional Group Header Position: 0020 Group: Level: 0 Usage: Conditional (Optional) Purpose: To head, identify and specify a Functional Group Dependency Notes: Semantic Notes: Comments: Business Rules: Variable Name: UNG Notes: Notes to Trading Partner This segment is optional and is used to send additional sender/receiver ID information. Data Examples UNG+DELFOR+SNDRGRPID+RCVRGRPID : UN+D:96A' Data Element Summary User Data Component Attribute Element Element Name Attributes M 0038 FUNCTIONAL GROUP IDENTIFICATION M an..6 Identification of the one type of messages in a functional group. M S006 APPLICATION SENDER IDENTIFICATION M Identification of the sender's division, department etc. from which a group of messages is sent. M 0040 Application sender identification M an..35 Name or code identifying the originating division, department etc. within the sender's organization. The sender identification can be the company EAN or DUNS code or a company specific code Partner identification code qualifier C an..4 Qualifier referring to the source of codes for the identifiers of interchanging partners. Qualifiers to be determined by trading partner relationship. M S007 APPLICATION RECIPIENTS IDENTIFICATION M Identification of the recipient's division, department etc. for which a group of messages is intended. M 0044 Application recipient's identification M an..35 Name or code identifying the division, department etc. within the recipient's organization for which the group of messages is intended. The receiver identification can be the company EAN or DUNS code or a company specific code. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 10 of 96

11 0007 Partner identification code qualifier C an..4 Qualifier referring to the source of codes for the identifiers of interchanging partners. Qualifiers to be determined by trading partner relationship. M S004 DATE AND TIME OF PREPARATION M Date and time of preparation of the interchange. M 0017 Date of preparation M n6 Local date when an interchange or a functional group was prepared. Format: YYMMDD M 0019 Time of preparation M n4 Local time of day when an interchange or a functional group was prepared. Format: HHMM M 0048 FUNCTIONAL GROUP REFERENCE NUMBER M an..14 Reference number for the functional group assigned by and unique within the sender's division, department etc. M 0051 CONTROLLING AGENCY M an..2 Code identifying the agency controlling the specification, maintenance and publication of the message type. M S008 MESSAGE VERSION M Specification of the type of messages in the functional group. M 0052 Message type version number M an..3 Version number of a message type. M 0054 Message type release number M an..3 Release number within the current message type version number (0052) Association assigned code C an..6 Code, assigned by the association responsible for the design and maintenance of the message type concerned, which further identifies the message APPLICATION PASSWORD C an..14 Password to the recipient's division, department or sectional system. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 11 of 96

12 Segment: UNE Functional Group Trailer Position: 0030 Group: Level: 0 Usage: Conditional (Optional) Purpose: To end and check the completeness of a Functional Group Dependency Notes: Semantic Notes: Comments: Notes: Data Examples UNE+1+562' Data Element Summary User Data Component Attribute Element Element Name Attributes M 0060 NUMBER OF MESSAGES M n..6 A count of the number of messages in a functional group. This field will contain the count of the number of messages present in the data file. M 0048 FUNCTIONAL GROUP REFERENCE NUMBER M an..14 Reference number for the functional group assigned by and unique within the sender's division, department etc. This value will match what is sent in the UNG_0048 element. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 12 of 96

13 Segment: UNZ Interchange Trailer Position: 0040 Group: Level: 0 Usage: Mandatory Purpose: To end and check the completeness of an interchange. Dependency Notes: Semantic Notes: Comments: Notes: Data Examples UNZ+1+562' Data Element Summary User Data Component Attribute Element Element Name Attributes M 0036 INTERCHANGE CONTROL COUNT M n..6 Count either of the number of messages or, if used, of the number of functional groups in an interchange. This field will contain the count of the number of interchanges present in the data file. M 0020 INTERCHANGE CONTROL REFERENCE M an..14 Unique reference assigned by the sender to an interchange. This value will match what is sent in the UNB_0020 element. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 13 of 96

14 DELFOR Delivery Schedule Message Introduction A message from buyer to supplier giving product requirements regarding details for short term delivery instructions and/or medium to long term product/service forecast for planning purposes according to conditions set out in a contract or order. The message can be used to authorize the commitment of labour and materials resources. Branching Diagram Legend Segment Group Number Segment Group Requirement : M = Mandatory C = Conditional R = Required 2R 1 NAD (BY) M 1 Segment Group Max Occurence Segment Name Code Qualifier Segment Requirement: M = Mandatory C = Conditional R = Required Segment Max Occurence Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 14 of 96

15 Branching Diagram (continued) LEVEL 0 UNH M 1 BGM (241) M 1 DTM DTM DTM (137) (158) (159) M 1 O 1 O 1 1C 10 2R 1 2R 1 1 RFF (ADE) M 1 NAD (SE) M 1 NAD (BY) M Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 15 of 96

16 Branching Diagram (continued) LEVEL 0 UNS (D) M 1 4R 1 1 NAD (CN) M 1 8R LIN M 1 10R 1 3 PIA C 1 IMD C 1 LOC LOC DTM DTM DTM RFF (11) (159) (257) (153) (154) (ON) C 1 C 1 C 1 C 1 C 1 M Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 16 of 96

17 Branching Diagram (continued) Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 17 of 96

18 Branching Diagram (continued) LEVEL 0 M UNS (S) 1 UNT M C C 50 4 QTY (113) M 1 PAC M 1 5 SCC R 1 DTM DTM (63) (64) R 1 R 1 QTY R (52) Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 18 of 96

19 Loop/Segment Table Heading Section: Adient Pos. Seg. Base Group Notes and Attributes No. ID Name Attributes Max.Use Repeat Comments M 0010 UNH Message Header M 1 M 0020 BGM Beginning of Message M 1 M 0030 DTM Date/Time/Period - Message Creation Date M DTM Date/Time/Period - Horizon Start Date O DTM Date/Time/Period - Horizon End Date O Segment Group 1: RFF-DTM C 10 M 0050 RFF Reference M 1 Not Used 0060 DTM Date/Time/Period C 1 Must Use 0070 Segment Group 2: NAD-LOC-SG3 C 1 M 0080 NAD Name and Address - Seller (Supplier) M 1 Not Used 0090 LOC Place/Location Identification C 10 Not Used 0100 Segment Group 3: CTA-COM C 5 Not Used 0110 CTA Contact Information M 1 Not Used 0120 COM Communication Contact C 5 Must Use 0070 Segment Group 2: NAD-LOC-SG3 C 1 M 0080 NAD Name and Address - Buyer (Adient Plant) M 1 Not Used 0090 LOC Place/Location Identification C 10 Not Used 0100 Segment Group 3: CTA-COM C 5 Not Used 0110 CTA Contact Information M 1 Not Used 0120 COM Communication Contact C 5 Section Control: Adient Pos. Seg. Base Group Notes and Attributes No. ID Name Attributes Max.Use Repeat Comments M 0130 UNS Section Control M 1 Detail Section: Adient Pos. Seg. Base Group Notes and Attributes No. ID Name Attributes Max.Use Repeat Comments Must Use 0140 Segment Group 4: NAD-LOC-FTX-SG5-SG6- C 1 SG7-SG8 M 0150 NAD Name and Address - Consignee (Ship To) M 1 Not Used 0160 LOC Place/Location Identification C 10 Not Used 0170 FTX Free Text C 5 Not Used 0180 Segment Group 5: DOC-DTM C 10 Not Used 0190 DOC Document/Message Details M 1 Not Used 0200 DTM Date/Time/Period C 10 Not Used 0210 Segment Group 6: CTA-COM C 5 Not Used 0220 CTA Contact Information M 1 Not Used 0230 COM Communication Contact C 5 Not Used 0240 Segment Group 7: TDT-DTM C 10 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 19 of 96

20 Not Used 0250 TDT Details of Transport M 1 Not Used 0260 DTM Date/Time/Period C 5 Must Use 0270 Segment Group 8: LIN-PIA-IMD-MEA-ALI- C 9999 GIN-GIR-LOC-DTM-FTX-SG9-SG10-SG11- SG12-SG14 M 0280 LIN Line Item M PIA Additional Product Id C IMD Item Description C 1 Not Used 0310 MEA Measurements C 5 Not Used 0320 ALI Additional Information C 5 Not Used 0330 GIN Goods Identity Number C 100 Not Used 0340 GIR Related Identification Numbers C LOC Place/Location Identification - Adient Dock C 1 Code 0350 LOC Place/Location Identification - Other Internal C 1 Adient Location 0360 DTM Date/Time/Period - Calculation Date C DTM Date/Time/Period - Finished Goods Go-Ahead C 1 End Date 0360 DTM Date/Time/Period - Raw Materials Go-Ahead C 1 End Date Not Used 0370 FTX Free Text C 5 Not Used 0380 Segment Group 9: CTA-COM C 5 Not Used 0390 CTA Contact Information M 1 Not Used 0400 COM Communication Contact C 5 Must Use 0410 Segment Group 10: RFF-DTM C 1 M 0420 RFF Reference - Purchase Order Number M 1 Not Used 0430 DTM Date/Time/Period C 1 Not Used 0440 Segment Group 11: TDT-DTM C 10 Not Used 0450 TDT Details of Transport M 1 Not Used 0460 DTM Date/Time/Period C Segment Group 12: QTY-SCC-DTM-SG13 C 3 M 0480 QTY Quantity (12) - Receipt Discrete Quantity M 1 Not Used 0490 SCC Scheduling Conditions C 1 Not Used 0500 DTM Date/Time/Period C Segment Group 13: RFF-DTM C 1 M 0520 RFF Reference - Receipt Despatch Advice Number M 1 Must Use 0530 DTM Date/Time/Period - Receipt Date C Segment Group 12: QTY-SCC-DTM-SG13 C 1 M 0480 QTY Quantity (70) - Last Receipt Cumulative M 1 Quantity Not Used 0490 SCC Scheduling Conditions C 1 Not Used 0500 DTM Date/Time/Period C 2 Not Used 0510 Segment Group 13: RFF-DTM C 10 Not Used 0520 RFF Reference M 1 Not Used 0530 DTM Date/Time/Period C Segment Group 12: QTY-SCC-DTM-SG13 C 1 M 0480 QTY Quantity (78) - Scheduled Cumulative Quantity M 1 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 20 of 96

21 Not Used 0490 SCC Scheduling Conditions C 1 Not Used 0500 DTM Date/Time/Period C 2 Not Used 0510 Segment Group 13: RFF-DTM C 10 Not Used 0520 RFF Reference M 1 Not Used 0530 DTM Date/Time/Period C Segment Group 12: QTY-SCC-DTM-SG13 C 1 M 0480 QTY Quantity (83) - Backorder Quantity M 1 Must Use 0490 SCC Scheduling Conditions C 1 Must Use 0500 DTM Date/Time/Period - Latest Delivery or Pickup C 1 Date/Time Must Use 0500 DTM Date/Time/Period - Earliest Delivery or Pickup C 1 Date/Time Not Used 0510 Segment Group 13: RFF-DTM C 10 Not Used 0520 RFF Reference M 1 Not Used 0530 DTM Date/Time/Period C Segment Group 12: QTY-SCC-DTM-SG13 C 1 M 0480 QTY Quantity (84) - Urgent Delivery Quantity M 1 Must Use 0490 SCC Scheduling Conditions C 1 Must Use 0500 DTM Date/Time/Period - Latest Delivery or Pickup C 1 Date/Time Must Use 0500 DTM Date/Time/Period - Earliest Delivery or Pickup C 1 Date/Time Not Used 0510 Segment Group 13: RFF-DTM C 10 Not Used 0520 RFF Reference M 1 Not Used 0530 DTM Date/Time/Period C Segment Group 12: QTY-SCC-DTM-SG13 C 200 M 0480 QTY Quantity (113) - Delivery Quantity M 1 Must Use 0490 SCC Scheduling Conditions C 1 Must Use 0500 DTM Date/Time/Period - Latest Delivery or Pickup C 1 Date/Time Must Use 0500 DTM Date/Time/Period - Earliest Delivery or Pickup C 1 Date/Time Not Used 0510 Segment Group 13: RFF-DTM C 10 Not Used 0520 RFF Reference M 1 Not Used 0530 DTM Date/Time/Period C Segment Group 14: PAC-MEA-QTY-DTM- C 50 SG15-SG16 M 0550 PAC Package M 1 Not Used 0560 MEA Measurements C 10 Must Use 0570 QTY Quantity (52) - Per Pack C 1 Not Used 0580 DTM Date/Time/Period C 5 Not Used 0590 Segment Group 15: PCI-GIN C 10 Not Used 0600 PCI Package Identification M 1 Not Used 0610 GIN Goods Identity Number C 10 Not Used 0620 Segment Group 16: QVR-DTM-SG17 C 10 Not Used 0630 QVR Quantity Variances M 1 Not Used 0640 DTM Date/Time/Period C 5 Not Used 0650 Segment Group 17: RFF-DTM C 10 Not Used 0660 RFF Reference M 1 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 21 of 96

22 Not Used 0670 DTM Date/Time/Period C 1 Not Used 0680 Segment Group 18: LIN-PIA-IMD-MEA-ALI- C 9999 GIN-GIR-DTM-FTX-SG19-SG20-SG22-SG24 Not Used 0690 LIN Line Item M 1 Not Used 0700 PIA Additional Product Id C 10 Not Used 0710 IMD Item Description C 10 Not Used 0720 MEA Measurements C 5 Not Used 0730 ALI Additional Information C 5 Not Used 0740 GIN Goods Identity Number C 100 Not Used 0750 GIR Related Identification Numbers C 100 Not Used 0760 DTM Date/Time/Period C 5 Not Used 0770 FTX Free Text C 5 Not Used 0780 Segment Group 19: RFF-DTM C 10 Not Used 0790 RFF Reference M 1 Not Used 0800 DTM Date/Time/Period C 1 Not Used 0810 Segment Group 20: QTY-SCC-DTM-SG21 C 50 Not Used 0820 QTY Quantity M 1 Not Used 0830 SCC Scheduling Conditions C 1 Not Used 0840 DTM Date/Time/Period C 2 Not Used 0850 Segment Group 21: RFF-DTM C 10 Not Used 0860 RFF Reference M 1 Not Used 0870 DTM Date/Time/Period C 1 Not Used 0880 Segment Group 22: PAC-MEA-QTY-DTM- C 10 SG23 Not Used 0890 PAC Package M 1 Not Used 0900 MEA Measurements C 10 Not Used 0910 QTY Quantity C 5 Not Used 0920 DTM Date/Time/Period C 5 Not Used 0930 Segment Group 23: PCI-GIN C 10 Not Used 0940 PCI Package Identification M 1 Not Used 0950 GIN Goods Identity Number C 10 Not Used 0960 Segment Group 24: NAD-LOC-FTX-SG25- C 500 SG26-SG27-SG29-SG31 Not Used 0970 NAD Name and Address M 1 Not Used 0980 LOC Place/Location Identification C 10 Not Used 0990 FTX Free Text C 5 Not Used 1000 Segment Group 25: DOC-DTM C 10 Not Used 1010 DOC Document/Message Details M 1 Not Used 1020 DTM Date/Time/Period C 1 Not Used 1030 Segment Group 26: CTA-COM C 5 Not Used 1040 CTA Contact Information M 1 Not Used 1050 COM Communication Contact C 5 Not Used 1060 Segment Group 27: QTY-SCC-DTM-SG28 C 50 Not Used 1070 QTY Quantity M 1 Not Used 1080 SCC Scheduling Conditions C 1 Not Used 1090 DTM Date/Time/Period C 2 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 22 of 96

23 Not Used 1100 Segment Group 28: RFF-DTM C 10 Not Used 1110 RFF Reference M 1 Not Used 1120 DTM Date/Time/Period C 1 Not Used 1130 Segment Group 29: QVR-DTM-SG30 C 10 Not Used 1140 QVR Quantity Variances M 1 Not Used 1150 DTM Date/Time/Period C 5 Not Used 1160 Segment Group 30: RFF-DTM C 10 Not Used 1170 RFF Reference M 1 Not Used 1180 DTM Date/Time/Period C 1 Not Used 1190 Segment Group 31: TDT-DTM C 10 Not Used 1200 TDT Details of Transport M 1 Not Used 1210 DTM Date/Time/Period C 5 Section Control: Adient Pos. Seg. Base Group Notes and Attributes No. ID Name Attributes Max.Use Repeat Comments M 1220 UNS Section Control M 1 Summary Section: Adient Pos. Seg. Base Group Notes and Attributes No. ID Name Attributes Max.Use Repeat Comments Not Used 1230 CNT Control Total C 5 Not Used 1240 FTX Free Text C 5 M 1250 UNT Message Trailer M 1 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 23 of 96

24 Segment: UNH Message Header Position: 0010 Group: Level: 0 Usage: Mandatory Purpose: Dependency Notes: Semantic Notes: Comments: Business Rules: Notes: A service segment starting and uniquely identifying a message. The message type code for the Delivery schedule message is DELFOR. Note: Delivery schedule messages conforming to this document must contain the following data in segment UNH, composite S009: Data element 0065 DELFOR 0052 D A 0051 UN Variable Name: UNH1 Notes to Trading Partner This segment is used to begin the DELFOR message. Composite S009, data elements 0065, 0052, 0054, and 0051 indicate that the message is a UNSM Delivery Schedule message based on the D.96A directory under the control of the United Nations. Data Examples UNH DELFOR:D:96A:UN' Data Element Summary User Data Component Attribute Element Element Name Attributes M 0062 MESSAGE REFERENCE NUMBER M an..14 Unique message reference assigned by the sender. M S009 MESSAGE IDENTIFIER M Identification of the type, version etc. of the message being interchanged. M 0065 Message type identifier M an..6 Code identifying a type of message and assigned by its controlling agency. DELFOR Delivery schedule message Message from buyer to supplier giving product requirements regarding details for short term delivery instructions and/or medium to long term product/service forecast for planning purposes according to conditions set out in a contract or order. The message can be used to authorize the commitment of labour and materials resources. M 0052 Message type version number M an..3 Version number of a message type. D Draft version/un/edifact Directory M 0054 Message type release number M an..3 Release number within the current message type version number (0052). 96A Version 96A M 0051 Controlling agency M an..2 Code identifying the agency controlling the specification, maintenance and publication of the message type. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 24 of 96

25 UN UN/ECE/TRADE/WP.4, United Nations Standard Messages (UNSM) UN Economic Commission for Europe (UN/ECE), Committee on the development of trade (TRADE), Working Party on facilitation of international trade procedures (WP.4) Association assigned code C an..6 Code, assigned by the association responsible for the design and maintenance of the message type concerned, which further identifies the message COMMON ACCESS REFERENCE C an..35 Reference serving as a key to relate all subsequent transfers of data to the same business case or file. S010 STATUS OF THE TRANSFER C Statement that the message is one in a sequence of transfers relating to the same topic. M 0070 Sequence message transfer number M n..2 Number assigned by the sender indicating that the message is an addition or change of a previously sent message relating to the same topic First/last sequence message transfer indication C a1 Indication used for the first and last message in a sequence of the same type of message relating to the same topic. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 25 of 96

26 Segment: BGM Beginning of Message Position: 0020 Group: Level: 0 Usage: Mandatory Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment for the unique identification of the delivery schedule document, by means of its name and its number. Notes to Trading Partner All references other than the Document/Message Number in data element 1004 will be in an RFF segment. Data element 1004: It is recommended that the length of the Document/Message Number be restricted to a maximum of 17 characters. Data Examples BGM ' Data Element Summary User Data Component Attribute Element Element Name Attributes Must Use C002 DOCUMENT/MESSAGE NAME C Identification of a type of document/message by code or name. Code preferred. Must Use 1001 Document/message name, coded C an..3 Document/message identifier expressed in code. 241 Delivery schedule Usage of DELFOR-message. Not Used 1131 Code list qualifier C an..3 Identification of a code list. Not Used 3055 Code list responsible agency, coded C an..3 Code identifying the agency responsible for a code list. Not Used 1000 Document/message name C an..35 Plain language identifier specifying the function of a document/message. Must Use 1004 DOCUMENT/MESSAGE NUMBER C an..35 Reference number assigned to the document/message by the issuer. Delivery Schedule number assigned by the document sender. Must Use 1225 MESSAGE FUNCTION, CODED C an..3 Code indicating the function of the message. 9 Original Initial transmission related to a given transaction. Not Used 4343 RESPONSE TYPE, CODED C an..3 Code specifying the type of acknowledgement required or transmitted. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 26 of 96

27 Segment: DTM Date/Time/Period - Message Creation Date Position: 0030 Group: Level: 0 Usage: Mandatory Purpose: A segment specifying the date, and when relevant, the time/period of the beginning and ending of the validity period of the document. The DTM must be specified at least once to identify the Delivery Schedule document date. The date/time/period segment within other Segment group should be used whenever the date/time/period is logically related to another specified data item. Dependency Notes: Semantic Notes: Comments: Notes: Notes to Trading Partner This segment is used to specify the message creation date. Data Examples DTM+137: :102' Data Element Summary User Data Component Attribute Element Element Name Attributes M C507 DATE/TIME/PERIOD M Date and/or time, or period relevant to the specified date/time/period type. M 2005 Date/time/period qualifier M an..3 Code giving specific meaning to a date, time or period. 137 Document/message date/time (2006) Date/time when a document/message is issued. This may include authentication. Must Use 2380 Date/time/period C an..35 The value of a date, a date and time, a time or of a period in a specified representation. Must Use 2379 Date/time/period format qualifier C an..3 Specification of the representation of a date, a date and time or of a period. 102 CCYYMMDD Calendar date: C = Century ; Y = Year ; M = Month ; D = Day. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 27 of 96

28 Segment: DTM Date/Time/Period - Horizon Start Date Position: 0030 Group: Level: 0 Usage: Optional (Optional) Purpose: A segment specifying the date, and when relevant, the time/period of the beginning and ending of the validity period of the document. The DTM must be specified at least once to identify the Delivery Schedule document date. The date/time/period segment within other Segment group should be used whenever the date/time/period is logically related to another specified data item. Dependency Notes: Semantic Notes: Comments: Notes: Notes to Trading Partner This segment is used to provide the start date of the demand horizon period. Data Examples DTM+158: :102' Data Element Summary User Data Component Attribute Element Element Name Attributes M C507 DATE/TIME/PERIOD M Date and/or time, or period relevant to the specified date/time/period type. M 2005 Date/time/period qualifier M an..3 Code giving specific meaning to a date, time or period. 158 Horizon start date The first date of a period forming a horizon. Must Use 2380 Date/time/period C an..35 The value of a date, a date and time, a time or of a period in a specified representation. Must Use 2379 Date/time/period format qualifier C an..3 Specification of the representation of a date, a date and time or of a period. 102 CCYYMMDD Calendar date: C = Century ; Y = Year ; M = Month ; D = Day. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 28 of 96

29 Segment: DTM Date/Time/Period - Horizon End Date Position: 0030 Group: Level: 0 Usage: Optional (Optional) Purpose: A segment specifying the date, and when relevant, the time/period of the beginning and ending of the validity period of the document. The DTM must be specified at least once to identify the Delivery Schedule document date. The date/time/period segment within other Segment group should be used whenever the date/time/period is logically related to another specified data item. Dependency Notes: Semantic Notes: Comments: Notes: Notes to Trading Partner This segment is used to provide the end date of the demand horizon period. Data Examples DTM+159: :102' Data Element Summary User Data Component Attribute Element Element Name Attributes M C507 DATE/TIME/PERIOD M Date and/or time, or period relevant to the specified date/time/period type. M 2005 Date/time/period qualifier M an..3 Code giving specific meaning to a date, time or period. 159 Horizon end date The last date of a period forming a horizon. Must Use 2380 Date/time/period C an..35 The value of a date, a date and time, a time or of a period in a specified representation. Must Use 2379 Date/time/period format qualifier C an..3 Specification of the representation of a date, a date and time or of a period. 102 CCYYMMDD Calendar date: C = Century ; Y = Year ; M = Month ; D = Day. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 29 of 96

30 Group: RFF Segment Group 1: Reference Position: 0040 Group: Level: 1 Usage: Conditional (Optional) 0 Purpose: A group of segments giving references relevant to the whole message, e.g. contract number. Segment Summary User Pos. Seg. Req. Max. Group: Attribute No. ID Name Des. Use Repeat M 0050 RFF Reference M 1 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 30 of 96

31 Segment: RFF Reference Position: 0050 (Trigger Segment) Group: Segment Group 1 (Reference) Conditional (Optional) Level: 1 Usage: Mandatory Purpose: Dependency Notes: Semantic Notes: Comments: Notes: A segment for referencing documents relating to the whole Delivery Schedule Message, e.g. contract, import/export license. Notes to Trading Partner This segment is used to provide references that apply to the whole message, e.g., purchase order number, delivery instructions, import/export license. Data Examples RFF+ADE: ' Data Element Summary User Data Component Attribute Element Element Name Attributes M C506 REFERENCE M Identification of a reference. M 1153 Reference qualifier M an..3 Code giving specific meaning to a reference segment or a reference number. ADE Account number Identification number of an account. Must Use 1154 Reference number C an..35 Identification number the nature and function of which can be qualified by an entry in data element 1153 Reference qualifier. Not Used 1156 Line number C an..6 Number of the line in the document/message referenced in 1154 Reference number. Not Used 4000 Reference version number C an..35 To uniquely identify a reference by its revision number. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 31 of 96

32 Group: NAD Segment Group 2: Name and Address Position: 0070 Group: Level: 1 Usage: Conditional (Required) Purpose: A group of segments identifying names, addresses, locations, and contacts relevant to the whole Delivery Schedule. Segment Summary User Pos. Seg. Req. Max. Group: Attribute No. ID Name Des. Use Repeat M 0080 NAD Name and Address - Seller (Supplier) M 1 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 32 of 96

33 Segment: NAD Name and Address - Seller (Supplier) Position: 0080 (Trigger Segment) Group: Segment Group 2 (Name and Address) Conditional (Required) Level: 1 Usage: Mandatory Purpose: A segment for identifying names and addresses and their functions relevant for the whole Delivery Schedule. Identification of the seller and buyer parties is recommended for the Delivery Schedule message. Exception: the identification of the recipient of the goods must be given in the NAD segment in the detail section when required. It is recommended that where possible only the coded form of the party ID should be specified, e.g. the buyer and seller are known to each other, thus only the coded ID is required. The consignee or delivery address may vary and would have to be clearly specified, preferably in structured format. Dependency Notes: Semantic Notes: Comments: Notes: Notes to Trading Partner This segment is used to identify the seller (supplier) involved in the Delivery Schedule message. Identification of the seller is mandatory in the Delivery Schedule. Data Examples NAE+SE ::92++SELLER NAME' Data Element Summary User Data Component Attribute Element Element Name Attributes M 3035 PARTY QUALIFIER M an..3 Code giving specific meaning to a party. SE Seller (3346) Party selling merchandise to a buyer. Must Use C082 PARTY IDENTIFICATION DETAILS C Identification of a transaction party by code. M 3039 Party id. identification M an..35 Code identifying a party involved in a transaction. Adient-assigned supplier code Not Used 1131 Code list qualifier C an..3 Identification of a code list. Must Use 3055 Code list responsible agency, coded C an..3 Code identifying the agency responsible for a code list. 92 Assigned by buyer or buyer's agent Not Used C058 NAME AND ADDRESS C Unstructured name and address: one to five lines. Not Used 3124 Name and address line M an..35 Free form name and address description. Not Used 3124 Name and address line C an..35 Free form name and address description. Not Used 3124 Name and address line C an..35 Free form name and address description. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 33 of 96

34 Not Used 3124 Name and address line C an..35 Free form name and address description. Not Used 3124 Name and address line C an..35 Free form name and address description. C080 PARTY NAME C Identification of a transaction party by name, one to five lines. Party name may be formatted. M 3036 Party name M an..35 Name of a party involved in a transaction Party name C an..35 Name of a party involved in a transaction. Not Used 3036 Party name C an..35 Name of a party involved in a transaction. Not Used 3036 Party name C an..35 Name of a party involved in a transaction. Not Used 3036 Party name C an..35 Name of a party involved in a transaction. Not Used 3045 Party name format, coded C an..3 Specification of the representation of a party name. Not Used C059 STREET C Street address and/or PO Box number in a structured address: one to three lines. Not Used 3042 Street and number/p.o. box M an..35 Street and number in plain language, or Post Office Box No. Not Used 3042 Street and number/p.o. box C an..35 Street and number in plain language, or Post Office Box No. Not Used 3042 Street and number/p.o. box C an..35 Street and number in plain language, or Post Office Box No. Not Used 3042 Street and number/p.o. box C an..35 Street and number in plain language, or Post Office Box No. Not Used 3164 CITY NAME C an..35 Name of a city (a town, a village) for addressing purposes. Not Used 3229 COUNTRY SUB-ENTITY IDENTIFICATION C an..9 Identification of the name of sub-entities (state, province) defined by appropriate governmental agencies. Not Used 3251 POSTCODE IDENTIFICATION C an..9 Code defining postal zones or addresses. Not Used 3207 COUNTRY, CODED C an..3 Identification of the name of a country or other geographical entity as specified in ISO Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 34 of 96

35 Group: NAD Segment Group 2: Name and Address Position: 0070 Group: Level: 1 Usage: Conditional (Required) Purpose: Segment Summary User Pos. Seg. Req. Max. Group: Attribute No. ID Name Des. Use Repeat M 0080 NAD Name and Address - Buyer (Adient Plant) M 1 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 35 of 96

36 Segment: NAD Name and Address - Buyer (Adient Plant) Position: 0080 (Trigger Segment) Group: Segment Group 2 (Name and Address) Conditional (Required) Level: 1 Usage: Mandatory Purpose: A segment for identifying names and addresses and their functions relevant for the whole Delivery Schedule. Identification of the seller and buyer parties is recommended for the Delivery Schedule message. Exception: the identification of the recipient of the goods must be given in the NAD segment in the detail section when required. It is recommended that where possible only the coded form of the party ID should be specified, e.g. the buyer and seller are known to each other, thus only the coded ID is required. The consignee or delivery address may vary and would have to be clearly specified, preferably in structured format. Dependency Notes: Semantic Notes: Comments: Notes: Notes to Trading Partner This segment is used to identify the buyer (Adient plant) involved in the Delivery Schedule message. Identification of the buyer is mandatory in the Delivery Schedule. Data Examples NAD+BY+1449::92++ADIENT PLANT NAME' Data Element Summary User Data Component Attribute Element Element Name Attributes M 3035 PARTY QUALIFIER M an..3 Code giving specific meaning to a party. BY Buyer (3002) Party to which merchandise is sold. Must Use C082 PARTY IDENTIFICATION DETAILS C Identification of a transaction party by code. M 3039 Party id. identification M an..35 Code identifying a party involved in a transaction. Adient 4-digit site code - e.g Not Used 1131 Code list qualifier C an..3 Identification of a code list Code list responsible agency, coded C an..3 Code identifying the agency responsible for a code list. 92 Assigned by buyer or buyer's agent Not Used C058 NAME AND ADDRESS C Unstructured name and address: one to five lines. Not Used 3124 Name and address line M an..35 Free form name and address description. Not Used 3124 Name and address line C an..35 Free form name and address description. Not Used 3124 Name and address line C an..35 Free form name and address description. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 36 of 96

37 Not Used 3124 Name and address line C an..35 Free form name and address description. Not Used 3124 Name and address line C an..35 Free form name and address description. C080 PARTY NAME C Identification of a transaction party by name, one to five lines. Party name may be formatted. M 3036 Party name M an..35 Name of a party involved in a transaction Party name C an..35 Name of a party involved in a transaction. Not Used 3036 Party name C an..35 Name of a party involved in a transaction. Not Used 3036 Party name C an..35 Name of a party involved in a transaction. Not Used 3036 Party name C an..35 Name of a party involved in a transaction. Not Used 3045 Party name format, coded C an..3 Specification of the representation of a party name. Not Used C059 STREET C Street address and/or PO Box number in a structured address: one to three lines. Not Used 3042 Street and number/p.o. box M an..35 Street and number in plain language, or Post Office Box No. Not Used 3042 Street and number/p.o. box C an..35 Street and number in plain language, or Post Office Box No. Not Used 3042 Street and number/p.o. box C an..35 Street and number in plain language, or Post Office Box No. Not Used 3042 Street and number/p.o. box C an..35 Street and number in plain language, or Post Office Box No. Not Used 3164 CITY NAME C an..35 Name of a city (a town, a village) for addressing purposes. Not Used 3229 COUNTRY SUB-ENTITY IDENTIFICATION C an..9 Identification of the name of sub-entities (state, province) defined by appropriate governmental agencies. Not Used 3251 POSTCODE IDENTIFICATION C an..9 Code defining postal zones or addresses. Not Used 3207 COUNTRY, CODED C an..3 Identification of the name of a country or other geographical entity as specified in ISO Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 37 of 96

38 Segment: UNS Section Control Position: 0130 Group: Level: 0 Usage: Mandatory Purpose: A service segment placed at the start of the detail section to avoid segment collision. The detail section consists of two main Segment groups: Segment group 4 and Segment group 18. The use of one of the Segment groups assumes that the other group will not be used. There are two methods of conveying Product Delivery forecast information. First method is by delivery point (Segment groups 4-17), the second is product driven (Segment group 18-31). Dependency Notes: Semantic Notes: Comments: Notes: Notes to Trading Partner This segment is used to separate the detail section from the header section. Data Examples UNS+D' Data Element Summary User Data Component Attribute Element Element Name Attributes M 0081 SECTION IDENTIFIER M a1 A character identifying the next section in a message. D Header/detail section separation To qualify the segment UNS, when separating the header from the detail section of a message. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 38 of 96

39 Group: NAD Segment Group 4: Name and Address Position: 0140 Group: Level: 1 Usage: Conditional (Required) Purpose: A group containing delivery names and addresses, related information and details of line items to be consigned to the delivery points. Segment Summary User Pos. Seg. Req. Max. Group: Attribute No. ID Name Des. Use Repeat M 0150 NAD Name and Address - Consignee (Ship To) M Segment Group 8: Line Item C 9999 Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 39 of 96

40 Segment: NAD Name and Address - Consignee (Ship To) Position: 0150 (Trigger Segment) Group: Segment Group 4 (Name and Address) Conditional (Required) Level: 1 Usage: Mandatory Purpose: A segment for identifying names and addresses and their functions relevant to the delivery point. All other segments in this segment group 4 following the NAD segment refer to that delivery point. Dependency Notes: Semantic Notes: Comments: Notes: Notes to Trading Partner This segment is used to identify the consignee (Ship To) involved in the Delivery Schedule message. Identification of the ship-to is mandatory in the Delivery Schedule Message. Data Examples NAD+CN+1449::92++ADIENT SHIP-TO NAME' Data Element Summary User Data Component Attribute Element Element Name Attributes M 3035 PARTY QUALIFIER M an..3 Code giving specific meaning to a party. CN Consignee (3132) Party to which goods are consigned. Must Use C082 PARTY IDENTIFICATION DETAILS C Identification of a transaction party by code. M 3039 Party id. identification M an..35 Code identifying a party involved in a transaction. Adient 4-digit site code - e.g Not Used 1131 Code list qualifier C an..3 Identification of a code list. Must Use 3055 Code list responsible agency, coded C an..3 Code identifying the agency responsible for a code list. 92 Assigned by buyer or buyer's agent Not Used C058 NAME AND ADDRESS C Unstructured name and address: one to five lines. Not Used 3124 Name and address line M an..35 Free form name and address description. Not Used 3124 Name and address line C an..35 Free form name and address description. Not Used 3124 Name and address line C an..35 Free form name and address description. Not Used 3124 Name and address line C an..35 Free form name and address description. Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 40 of 96

41 Not Used 3124 Name and address line C an..35 Free form name and address description. C080 PARTY NAME C Identification of a transaction party by name, one to five lines. Party name may be formatted. M 3036 Party name M an..35 Name of a party involved in a transaction Party name C an..35 Name of a party involved in a transaction. Not Used 3036 Party name C an..35 Name of a party involved in a transaction. Not Used 3036 Party name C an..35 Name of a party involved in a transaction. Not Used 3036 Party name C an..35 Name of a party involved in a transaction. Not Used 3045 Party name format, coded C an..3 Specification of the representation of a party name. Not Used C059 STREET C Street address and/or PO Box number in a structured address: one to three lines. Not Used 3042 Street and number/p.o. box M an..35 Street and number in plain language, or Post Office Box No. Not Used 3042 Street and number/p.o. box C an..35 Street and number in plain language, or Post Office Box No. Not Used 3042 Street and number/p.o. box C an..35 Street and number in plain language, or Post Office Box No. Not Used 3042 Street and number/p.o. box C an..35 Street and number in plain language, or Post Office Box No. Not Used 3164 CITY NAME C an..35 Name of a city (a town, a village) for addressing purposes. Not Used 3229 COUNTRY SUB-ENTITY IDENTIFICATION C an..9 Identification of the name of sub-entities (state, province) defined by appropriate governmental agencies. Not Used 3251 POSTCODE IDENTIFICATION C an..9 Code defining postal zones or addresses. Not Used 3207 COUNTRY, CODED C an..3 Identification of the name of a country or other geographical entity as specified in ISO Adient DELFOR Implementation Guideline Version 2.11/October 2016 Page 41 of 96