ELECTRONIC DATA INTERCHANGE (EDI) IMPLEMENTATION GUIDE PHASE 1 VERSION AIAG TRANSACTION SETS 830 & 997

Transcription

1 ELECTRONIC INTERCHANGE (EDI) IMPLEMENTATION GUIDE PHASE 1 VERSION AIAG TRANSACTION S 830 & 997 Version AIAG

2 TABLE CONTENTS Page No. EDI OVERVIEW... 1 CONTACTS... 3 IMPLEMENTATION PROCESS... 4 DEFINITIONS AND CONTROL STRUCTURES Data Element Types... 5 Data Element Requirement Designators... 5 Data Delimiters... 5 Interchange Envelope... 6 Functional Group... 6 Transaction Set... 6 Interchange Structure... 7 ISA Interchange Control Header... 8 IEA Interchange Control Trailer GS Functional Group Header GE Functional Group Trailer TRANSACTION 830 PLANNING SCHEDULE WITH RELEASE CAPABILITY Transaction Set Description Transaction Set Diagram Sample 830 Document Transaction Set Table 1 (Heading Area) Segments ST Transaction Set Header BFR Beginning Segment for Planning Schedule DTM Date/Time Reference N1 Name N3 Address Information N4 Geographic Location Transaction Set Table 2 (Detail Area) Segments LIN Item Identification UIT Unit Detail REF Reference Identification PER Administrative Communications Contact ATH Resource Authorization N1 Name N3 Address Information N4 Geographic Location SDP Ship/Delivery Pattern FST Forecast Schedule SHP Shipped/Received Information REF Reference Identification Transaction Set Table 3 (Summary Area) Segments CTT Transaction Totals SE Transaction Set Trailer Version AIAG i

3 TABLE CONTENTS (continued) Page No. TRANSACTION 997 FUNCTIONAL ACKNOWLEDGMENT Transaction Set Description & Diagram Sample 997 Document Transaction Set Table 1 (Heading Area) Segments ST Transaction Set Header AK1 Functional Group Response Header AK2 Transaction Set Response Header AK3 Data Segment Note AK4 Data Element Note AK5 Transaction Set Response Trailer AK9 Functional Group Response Trailer SE Transaction Set Trailer APPENDIX A GLOSSARY TERMS Version AIAG ii

4 EDI OVERVIEW Electronic Data Interchange (EDI) is the computer-to-computer exchange of routine business data in an approved standard format. The following are some of the benefits that can be realized from an EDI implementation: Streamlined and improved business processes Data accuracy and timeliness Increased information availability Reduced mail and paper costs Reduced clerical effort Reduced lead times/inventories Reduced spending on premium freight Less frequent schedule adjustments Competitive advantage Increased productivity User satisfaction In order to meet the OEM Supply Chain EDI Requirements, as well as to remain competitive, Key Plastics, Inc. (Key) has decided to implement an EDI program with our suppliers. The standardized format Key has chosen to use is AIAG Version 003, Release 060 (003060). Note: As of November 2001, Key Plastics is now capable of using (004010) Version AIAG 1

5 EDI OVERVIEW (continued) The following indicates the purpose of each of the transaction sets and the parties responsible for sending and receiving: 830 Planning Schedule with Release Capability (Material Release) Generated by Key and sent to the supplier to support the supplier s planning for component requirements and shipments to meet Key s requirements. 997 Functional Acknowledgment Generated in response to receipt of a transaction set other than another 997. This acknowledges that the transaction set has been received and translated. To help Key meet its EDI implementation goals, Key has enlisted the help of GE Information Services (GEIS) to work with Key and our suppliers during the implementation process. For additional information or help during the implementation process, see the Contacts section of this EDI Implementation Guide. Version AIAG 2

6 CONTACTS Perot Systems/Key Plastics, L.L.C. Maria Stombaugh GE Information Services, Inc. AIAG 401 N. Washington Street (Automotive Industry Action Group) Rockville, MD Lahser Road, Suite 200 EDI Information: Southfield, MI Trading Partner Setup: Phone: Dun & Bradstreet 1 Diamond Hill Road Murray Hill, NJ Phone: (USA) x 7090 (Int l) Version AIAG 3

7 IMPLEMENTATION PROCESS Obtain, install, and configure appropriate hardware. Obtain, install and configure an EDI translation software product. Obtain a Value Added Network Service (VAN), preferably GE Information Services (see the Contacts section for information on GEIS). GE Information Services provides EDI solutions and services that can help an organization implement EDI. Obtain a DUNS number from Dun & Bradstreet (see the Contacts section of this EDI Implementation Guide). Dun & Bradstreet can provide DUNS numbers as well as a Family Tree that lists the DUNS numbers of an organization s multiple locations. Review Key s EDI Implementation Guide and become familiar with the Planning Schedule with Release Capability document (transaction set 830) and the Functional Acknowledgment document (transaction set 997). Configure your EDI software package to receive an 830 document and send back a 997 document. If GEIS is the VAN service provider you currently use or have arranged to use, GEIS will be contacting you to perform connectivity testing. If you use or plan to use another VAN service, then Terry Schrieber, Key s EDI Coordinator, will be contacting you to arrange connectivity testing between Key, your company, and your VAN service provider. Receive and process the 830 document. Generate and send the 997 document. Key will then contact you to schedule parallel testing. During the testing phases, all current business processes (paper documents) will remain in effect until all testing is complete and approved. Note that during this testing phase, the ISA15 element in the 830 and 997 documents will be set to T to indicate testing mode. Once connectivity and parallel testing have successfully been completed and approved by both Key and our supplier, faxed or paper releases will no longer be an acceptable form of communication. Note that during the production phase, the ISA15 element in the 830 and 997 documents will be set to P for production mode. Version AIAG 4

8 DEFINITIONS AND CONTROL STRUCTURES ELEMENT TYPES CHARACTERS INCLUDED AN Alphanumeric N/A Uppercase letters A to Z Lowercase letters a to z Space Special characters as follows:! & ( ) * +, -. / : ;? = ] [ _ { } \ < > ~ Note: Special characters are removed from this category when used as delimiters. DT Date yymmdd Numeric digits 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 ID ID Code N/A Uppercase letters A to Z Numeric digits 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 TM Time hhmm Numeric digits 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 N0 Numeric (zero decimal positions) N/A Numeric digits 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 Special characters as follows: + - ELEMENT DESIGNATS DESIGNAT DESCRIPTION DEFINITION C Conditional The presence of a value for this simple data element is dependent on the presence or absence of other simple data elements in the same segment. O Optional The presence of the value for this simple data element or the presence of a value for any of the component data elements of the composite data structure is at the option of the sender. M Mandatory The value for this simple data element or at least one value of a component data element in the composite data structure shall be included in the data segment. DELIMITERS TYPE EBCDIC HEX Terminator ~ (HEX A1) Element Separator * (HEX 5C) Sub-element Separator : (HEX 7A) Version AIAG 5

9 DEFINITIONS AND CONTROL STRUCTURES (continued) INTERCHANGE ENVELOPE An EDI envelope performs the same functions as the envelope used to mail paper business documents. Envelopes start with the Interchange Control Segment (ISA). The ISA identifies the sending and receiving parties, has a date and time stamp like a postmark, and shows whether or not the sender wants a return receipt. The segment also provides additional information required for the proper processing of the data inside the envelope. The additional details include authorization and security information what applications should have access to this transmission and whether the receiver needs a password or some other security key to open the envelope. The ISA also shows what standard and version the envelope conforms to, whether the transactions inside the envelope are for testing or production purposes, and has a control number for the envelope. The ISA also shows what characters the sender used for Element Separator, Sub-element Separator, and Segment Terminator for the transactions inside the envelope. The receiver s translator uses these characters to parse the data for reformatting to the output file. The EDI envelope ends with the Interchange Control Trailer (IEA) segment. The IEA appears at the end of all the functional groups inside the envelope. The IEA contains a count of the functional groups and a control number that matches the ISA s control number. Matching on the group count and control numbers confirms the receipt of the complete envelope. FUNCTIONAL GROUP A Functional Group is a collection of particular transaction sets which allows you to send multiple instances of a transaction set (example the 830 Planning Schedule with Release Capability) within the group. The Functional Group Header (GS) segment identifies the start of the group and also serves as an inside envelope for the transmission. It identifies the group type, the sending and receiving parties, date and time stamps, a control number, and the standards agency and version/release of the transactions that follow. Some receivers of transactions use this information to route the translated data to a particular business application. The Functional Group Trailer (GE) segment occurs after all the transaction sets within the group. It contains a count of the transactions and repeats the control number in the GS segment to aid in verifying the complete receipt of the functional group. Functional groups are placed inside an envelope. TRANSACTION Transaction Sets are the representations of standard business documents. All transaction sets start with a Transaction Set Header (ST) segment and end with a Transaction Set Trailer (SE) segment. The ST segment gives the identifier for the transaction (e.g., 830 for Planning Schedule with Release Capability) and a control number. The SE gives the total segment count for the transaction and repeats the control number from the ST. Translators use these segments to recognize the start and end of the transaction, check for the receipt of all the segments, and ensure transactions are not missing or out of sequence. Version AIAG 6

10 INTERCHANGE STRUCTURE ISA Interchange Control Header GS Functional Group Header ST Transaction Set Header Detail Segments SE Transaction Set Trailer ST Transaction Set Header Detail Segments SE Transaction Set Trailer GE Functional Group Trailer GS Functional Group Header ST Transaction Set Header Detail Segments SE Transaction Set Trailer ST Transaction Set Header Detail Segments SE Transaction Set Trailer GE Functional Group Trailer IEA Interchange Control Trailer Version AIAG 7

11 ISA (Interchange Control Header) MAX ISA S INTERCHANGE PURPOSE Mandatory 1 This segment is used to indicate the beginning of an interchange containing one or more functional groups, and to provide control information. b = space C = Conditional M = Mandatory O = Optional x = alphanumeric character 01 I01 M 2/2 ID Authorization Information 02 I02 M 10/10 AN Authorization Information 03 I03 M 2/2 ID Security Information = No Authorization Information Present bbbbbbbbbb contain ten spaces = No Security Information Present 04 I04 M 10/10 AN Security Information bbbbbbbbbb contain ten spaces. 05 I05 M 2/2 ID Interchange ID = DUNS Number 06 I06 M 15/15 AN Interchange Sender ID xxxxxxxxxxxxxxx contain the Sender s DUNS number. 07 I05 M 2/2 ID Interchange ID = DUNS Number 08 I07 M 15/15 AN Interchange Receiver ID xxxxxxxxxxxxxxx contain the Receiver s DUNS number. 09 I08 M 6/6 DT Interchange Date yymmdd contain the date the interchange was generated. (Example: ) 10 I09 M 4/4 TM Interchange Time hhmm contain the time the interchange was generated. (Example: 1400, which is equal to 2:00 pm) 11 I10 M 1/1 ID Interchange Standard ID U U = U.S. EDI Community of ASC X12, TDCC, and UCS Version AIAG 8

12 ISA (Interchange Control Header) (continued) MAX ISA S INTERCHANGE PURPOSE Mandatory 1 This segment is used to indicate the beginning of an interchange containing one or more functional groups, and to provide control information. b = space C = Conditional M = Mandatory O = Optional x = alphanumeric character 12 I11 M 5/5 ID Interchange Control Version Number 13 I12 M 9/9 N0 Interchange Control Number 14 I13 M 1/1 ID Acknowledgement Requested = Draft Std. For Trial Use Approved by ASC X12 Through Oct xxxxxxxxx contain an identifying control number that is assigned by the sender and is unique for the interchange. 0 contain a 0 which indicates that an interchange acknowledgment is not required. Note: A functional group acknowledgment is required. 15 I14 M 1/1 ID Test Indicator T contain a T in the testing phase, and a P in the production phase. 16 I15 M 1/1 AN Sub-element Separator : contain the value used to separate composite elements. Version AIAG 9

13 MAX IEA S INTERCHANGE IEA (Interchange Control Trailer) PURPOSE Mandatory 1 This segment is used to indicate the end of an interchange and to provide control information. 01 I16 M 1/5 N0 Number of Included Functional Groups 02 I12 M 9/9 N0 Interchange Control Number xxxxx xxxxxxxxx contain the number of functional groups contained within the interchange. contain the same control number used in the corresponding ISA13 element. Version AIAG 10

14 MAX GS S FUNC. GROUP GS (Functional Group Header) PURPOSE Mandatory 1 This segment is used to indicate the beginning of a functional group containing one or more transaction sets of the same type, and to provide control information M 2/2 ID Functional Identifier Code M 9/9 AN Application Sender s Code M 9/9 AN Application Receiver s Code FA or PS xxxxxxxxx xxxxxxxxx FA = Functional Acknowledgment PS = Planning Schedule with Release Capability contain the Sender s DUNS number. contain the Receiver s DUNS number M 6/6 DT Group Date yymmdd contain the date the functional group was generated M 4/4 TM Group Time hhmm contain the time the functional group was generated M 1/9 N0 Group Control Number xxxxxxxxx contain an identifying control number that is assigned by the sender and is unique for the functional group M 1/2 ID Responsible Agency Code M 1/12 AN Version/Release Indicator Code X X = Accredited Standards Committee X = ASC X12 Standards Approved by ANSI in 1997 Version AIAG 11

15 MAX GE S FUNC. GROUP GE (Functional Group Trailer) PURPOSE Mandatory 1 This segment is used to indicate the end of a functional group and to provide control information M 1/6 N0 Number of Included Sets xxxxxx contain the number of transaction sets (documents) contained within the functional group M 1/9 N0 Group Control Number xxxxxxxxx contain the same control number used in the corresponding GS06 element. Version AIAG 12

16 830 PLANNING SCHEDULE WITH RELEASE CAPABILITY FUNCTIONAL GROUP ID = PS This standard provides the format and establishes the data contents of a Planning Schedule with Release Capability transaction set. The planning schedule with release capability transaction set provides for customary and established business practice relative to the transfer of forecasting/material release information between organizations. The planning schedule transaction may be used in various ways or in a combination of ways, such as: (1) a simple forecast; (2) a forecast with the buyer s authorization for the seller to commit to resources, such as labor or material; (3) a forecast that is also used as an order release mechanism, containing such elements as resource authorizations, period-to-date cumulative quantities, and specific ship/delivery patterns for requirements that have been represented in buckets, such as weekly, monthly or quarterly. The order release forecast may also contain all data related to purchase orders, as required, because the order release capability eliminates the need for discrete generation of purchase orders. Note: The basic assumption of requirements forecasting is that a purchase order exists which describes the contractual agreement between Key and the supplier. The Purchase Order type normally used is a blanket purchase order. RECOMMENDED PRACTICES: (taken from the AIAG Supply Chain: Recommended Practices for EDI Implementation Manual) All previously transmitted forecast/released quantities for a customer, part/purchase order/engineering change, and ship to combination are being replaced by the latest transmission. An 830 should be released regularly, as close to the same time as possible. This allows the supplier receiving releases to schedule system processing time more efficiently. However, if changes are made or new parts are added outside of the normal processing time, then only changed or new parts should be transmitted. All receipts increase the part cumulative received quantity. Received cums are not reduced by rejected or returned parts. Received cums do not necessarily reflect the inventory level because a receipt is only one type of inventory transaction. When using the forecast timing qualifier of W, the time period indicated begins on Monday and ends on Sunday. A planning schedule can only be replaced. Originals or cancellations are not allowed. For final release, balance out parts, and pilot parts, the customer should define for the supplier how these conditions will be handled. This becomes especially important when standard pack processing is required. All parts/purchase orders/engineering changes for a single Material Release Issuer, Supplier or Ship From, and Ship To combination should be sent in a single ST/SE loop. If fabrication and material authorization quantities are sent, they will include the prior cum required plus the number of forecast quantities based on the contractual agreement. If the customer is not using an ATH segment with a qualifier of PQ, and SHP shows year-to-date received, then the FST segments must include requirements for material in-transit. If the SHP shows year-to-date shipped, then the FST segments should not include requirements for material in-transit. Version AIAG 13

17 830 PLANNING SCHEDULE WITH RELEASE CAPABILITY (continued) Functional Group ID = PS RECOMMENDED PRACTICES: (continued) The following are ways to determine ahead, behind, or in-transit conditions: Behind conditions can be identified by a delinquent due date (a date between the horizon start in the BFR06 and the current date) and quantity in the FST segment. If the customer is using an ATH segment with a qualifier of PQ, then the supplier should calculate the past due quantity by comparing the ATH03 quantity and their own internal cum shipped, adjusted by in-transit quantities, since last cum reset. Otherwise, the supplier should calculate the past due quantity by comparing the customer s cumulative shipped quantity in the SHP segment to their own internal cum shipped, adjusted by in-transit quantities, since last cum reset. In-transit quantities can be determined by using the SHP segment identifying the last received or shipped quantity considered by the customer and determining if any shipments have been made since the shipment referenced. If the customer s and the supplier s cums are equal, then the quantity in the FST is due. If the customer s cum is greater, then the supplier is in a behind schedule condition. The supplier must ship the difference plus any other requirements due. If the supplier s cum is greater, then the supplier is in an ahead condition. The supplier must subtract the difference plus any other requirements due. Any discrepancies in cums should be resolved immediately. Version AIAG 14

18 830 PLANNING SCHEDULE WITH RELEASE CAPABILITY TABLE 1 HEADING AREA POS. SE G. ID NAME AIAG REQ. DES. USAGE KEY REQ. DES. MAX. USE REPEAT 010 ST Transaction Set Header M M BF Beginning Segment for Planning Schedule M M 1 18 R 130 DT M Date/Time Reference O O ID N N1 Name O M N3 Address Information O O N4 Geographic Location O O 1 23 PAGE TABLE 2 DETAIL AREA POS. SE G. ID NAME AIAG REQ. DES. USAGE KEY REQ. DES. MAX. USE REPEAT ID LIN > LI Item Identification M M 1 24 N 020 UI Unit Detail O M 1 26 T 140 RE Reference Identification O O F 150 PE Administrative Communications Contact O O 3 28 R 230 AT H Resource Authorization O M ID N N1 Name O O N3 Address Information O O N4 Geographic Location O O 1 33 ID SDP SD Ship/Delivery Pattern O O 1 34 P 460 FS T Forecast Schedule O O ID SHP SH Shipped/Received Information O M 1 36 P 480 RE F Reference Identification O O 5 38 PAGE TABLE 3 SUMMARY AREA Version AIAG 15

19 POS. SE G. ID NAME AIAG REQ. DES. USAGE KEY REQ. DES. MAX. USE REPEAT 010 CT T Transaction Totals O O SE Transaction Set Trailer M M 1 40 PAGE Version AIAG 16

20 SAMPLE 830 DOCUMENT ISA*00* *00* *01* *01* *980501*0930*U*00306* *0*T*:~ GS*PS* * *980501*0930*12*X*003060~ ST*830* ~ BFR*05*00014**SH*A*980501*980820*980501***A12345~ DTM*168*980501***19~ N1*BT*Key Plastics Plymouth Div*1* ~ N3*40300 Plymouth Rd.~ N4*Plymouth*MI*48170~ N1*SU*ABC Company*1* ~ N3*123 Anywhere St.~ N4*Anytown*IN* ~ N1*ST*Key Plastics*1* ~ N3*40300 Plymouth Rd.~ N4*Plymouth*MI*48170~ LIN**BP*KPL-001*VP*ABC0369~ UIT*LB~ REF*DK*Dock 4~ PER*BD*Anne Gilbert~ ATH*PQ*980501*70000**980101~ ATH*FI**105000**980101~ ATH*MT**105000**980101~ SDP*G*Y~ FST*6000*D*D*980528~ FST*8000*D*D*980611~ FST*7000*D*D*980625~ FST*5000*D*D*980709~ FST*1000*D*D*980723~ FST*8000*D*D*980820~ SHP*01*7700*050*980428~ REF*SI* ~ SHP*02*70000*051*980101**980428~ LIN**BP*KPL-002***EC*A5~ UIT*PC~ PER*EX*Thomas Diablo~ SDP*Y*Y~ FST*1550*D*D*980501~ FST*200*D*D*980707~ FST*1000*D*D*980811~ SHP*01*110*050*980420~ REF*SI* ~ SHP*02*110*051*980101**980428~ CTT*2*37750~ SE*41* ~ GE*1*12~ IEA*1* ~ Version AIAG 17

21 MAX ST S ST (Transaction Set Header) PURPOSE Mandatory Heading This segment is used to indicate the beginning of a transaction set and to provide control information M 3/3 ID Transaction Set Identifier Code M 4/9 AN Transaction Set Control Number = X12.14 Planning Schedule with Release Capability xxxxxxxxx contain an identifying control number that is assigned by the sender and is unique for the transaction set. Version AIAG 18

22 BFR (Beginning Segment for Planning Schedule) MAX BFR S PURPOSE Mandatory Heading This segment is used to indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast, and related forecast envelope dates M 2/2 ID Transaction Set Purpose Code C 1/30 AN Reference Identification xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx = Replace C 1/30 AN Release Number contain the Release Number M 2/2 ID Schedule Type DL or SH DL = Delivery Based (when materials must be delivered to Key Plastics receiving location) M 1/1 ID Schedule Quantity A SH = Shipment Based (when materials must leave the supplier s shipping location) A = Actual Discreet Quantities (type of quantities used when defining a schedule or forecast) M 6/6 DT Date yymmdd contain the forecast horizon start date O 6/6 DT Date yymmdd contain the forecast horizon end date M 6/6 DT Date yymmdd contain the date the forecast was generated O 6/6 DT Date Version AIAG 19

23 BFR (Beginning Segment for Planning Schedule) (continued) MAX BFR S PURPOSE Mandatory Heading This segment is used to indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast, and related forecast envelope dates O 1/30 AN Contract Number O 1/22 AN Purchase Order Number xxxxxxxxxxxxxxx xxxxxxx contain the Purchase Order Number O 2/2 ID Planning Schedule Type Code O 1/2 ID Action Code Version AIAG 20

24 MAX DTM S DTM (Date/Time Reference) PURPOSE Optional Heading This segment is used to specify pertinent dates and times M 3/3 ID Date/Time = Release C 6/6 DT Date yymmdd contain the date the forecast was generated C 4/8 AN Time O 2/2 ID Time Code O 2/2 N0 Century 19 or 20 contain the first two characters in the designation of the year (CCYY) C 2/3 ID Date Time Period Format C 1/35 AN Date Time Period Version AIAG 21

25 N1 (Name) (N1 Loop is Mandatory) MAX N1 S N1 Mandatory 1 Max N1 Loops = 200 PURPOSE 230 N1 Heading This segment is used to identify a party by type of organization, name and code M 2/2 ID Entity Identifier Code BT or SF or ST or SU C 1/35 AN Name xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxx BT = Bill-To-Party SF = Ship From ST = Ship To SU = Supplier/ Manufacturer If the Ship To location is different for each part on the release, then the Ship To information will be provided in an N1 segment in the Detail Area. contain the free-form name of the identified party C 1/2 ID Identification Code C 2/20 AN Identification Code xxxxxxxxxxxxxxx xx At least one of N102 or N103 is required. 1 1 = DUNS Number If either N103 or N104 is present, then the other is required. contain the DUNS number of the identified party. (The DUNS number will not contain embedded spaces or dashes.) O 2/2 ID Entity Relationship Code O 2/2 AN Entity Identifier Code Version AIAG 22

26 N3 (Address Information) MAX N3 S N1 Optional 2 Max N1 Loops = 200 PURPOSE 250 N1 Heading This segment is used to specify the location of the named party M 1/35 AN Address Information xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxx O 1/35 AN Address Information xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxx Version AIAG 23

27 N4 (Geographic Location) MAX N4 S N1 Optional 1 Max N1 Loops = 200 PURPOSE 260 N1 Heading This segment is used to specify the geographic place of the named party O 2/30 AN City Name xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx At least one of N401 or N405 must be present O 2/2 ID State or Province Code xx If N401 is present, and N401 is a city located in the U.S. or Canada, then N402 is required O 3/15 ID Postal Code xxxxxxxxxxxxxxx O 2/3 ID Country Code C 1/2 ID Location O 1/30 AN Location Identifier Version AIAG 24

28 LIN (Item Identification) (LIN Loop is Mandatory) MAX LIN S LIN Mandatory 1 Max LIN Loops = 999,999 PURPOSE 010 LIN Detail This segment is used to specify basic item identification data O 1/20 AN Assigned Identification M 2/2 ID Product/Service ID BP M 1/40 AN Product/Service ID xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxxxxxxx C 2/2 ID Product/Service ID VP C 1/40 AN Product/Service ID xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxxxxxxx C 2/2 ID Product/Service ID EC C 1/40 AN Product/Service ID xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxxxxxxx BP = Buyer s Part Number contain the buyer s part number. VP = Vendor s (Seller s) Part Number contain the vendor s part number. If LIN04 or LIN05 is present, then the other is required. EC = Engineering Change Level contain the engineering change level. If LIN06 or LIN07 is present, then the other is required C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID Version AIAG 25

29 LIN (Item Identification) (continued) MAX LIN S LIN Mandatory 1 Max LIN Loops = 999,999 PURPOSE 010 LIN Detail This segment is used to specify basic item identification data C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID C 2/2 ID Product/Service ID C 1/40 AN Product/Service ID Version AIAG 26

30 UIT (Unit Detail) MAX UIT S LIN Mandatory 1 Max LIN Loops = 999,999 S ET PURPOSE 020 LIN Detail This segment is used to specify item unit data M 2/2 ID Unit or Basis for Measurement Code xx C 1/17 R Unit Price Element UIT01 is a composite data element, C001, which contains 15 simple data elements. Key Plastics only utilizes the first component of the composite, data element 355. This implementation guide reflects that decision by substituting 355 for C001 in the Ele. ID field, which is syntactically correct O 2/2 ID Basis of Unit Price Code Version AIAG 27

31 REF (Reference Identification) MAX REF S LIN Optional 12 Max LIN Loops = 999,999 PURPOSE 140 LIN Detail This segment is used to specify identifying information M 2/3 ID Reference Identification DK C 1/30 AN Reference Identification xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx DK = Dock Number contain the Dock Number C 1/80 AN Description 04 C040 O Reference Number Version AIAG 28

32 PER (Administrative Communications Contact) MAX PER S LIN Optional 3 Max LIN Loops = 999,999 PURPOSE 150 LIN Detail This segment is used to identify a person or office to whom administrative communications should be directed M 2/2 ID Contact Function Code BD or EX BD = Buyer Name or Department EX = Expeditor O 1/35 AN Name xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxx contain the Buyer Name or Department or the name of the Expeditor C 2/2 ID Communication Number C 1/80 AN Communication Number C 2/2 ID Communication Number C 1/80 AN Communication Number C 2/2 ID Communication Number C 1/80 AN Communication Number O 1/20 AN Contact Inquiry Reference Version AIAG 29

33 ATH (Resource Authorization) MAX ATH S LIN Optional 20 Max LIN Loops = 999,999 PURPOSE 230 LIN Detail This segment is used to specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule M 2/2 ID Resource Authorization Code FI, MT or PQ FI = Finished (Labor, Material, & Overhead/ Burden) MT = Material PQ = Cumulative Quantity Required Prior to First Schedule Period The ATH02 element is mandatory when ATH01 is equal to PQ C 6/6 DT Date yymmdd If ATH01 is equal to PQ, then this element will contain the date through which the cumulative quantity is authorized. At least one of ATH02 or ATH03 is required C 1/15 R Quantity xxxxxxxxxxxxxxx If ATH03 is present, then ATH05 is required. If the ATH01 element is equal to FI or MT, then this element will contain the cumulative quantity that has been authorized from the start date. Version AIAG 30

34 ATH (Resource Authorization) (continued) MAX ATH S LIN Mandatory 20 Max LIN Loops = 999,999 PURPOSE 230 LIN Detail This segment is used to specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule C 1/15 R Quantity xxxxxxxxxxxxxxx (continued from previous page) If the ATH01 element is equal to PQ, then this element will contain the cumulative quantity that has been authorized from the start date through the end date O 1/15 R Quantity C 6/6 DT Date yymmdd contain the cumulative quantity start date. Version AIAG 31

35 N1 (Name) (N1 Loop is Optional) MAX N1 S N1 Mandatory 1 Max N1 Loops per LIN Loop = N1 & LIN Detail PURPOSE This segment is used to identify a party by type of organization, name and code. Max LIN Loops = 999,999 (The N1(320) loop is used only if the Ship To location varies for the different part numbers.) M 2/2 ID Entity Identifier Code ST ST = Ship To C 1/35 AN Name xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxx contain the free-form name of the identified party C 1/2 ID Identification Code C 2/20 ID Identification Code xxxxxxxxxxxxxxx xxxxx At least one of N102 or N103 is required. 1 1 = DUNS Number If either N103 or N104 is present, then the other is required. contain the DUNS number of the identified party. (The DUNS number will not contain embedded spaces or dashes.) O 2/2 ID Entity Relationship Code O 2/2 AN Entity Identifier Code Version AIAG 32

36 N3 (Address Information) MAX N3 S N1 Optional 2 Max N1 Loops per LIN Loop = N1 & LIN Detail PURPOSE This segment is used to specify the location of the named party. Max LIN Loops = 999, M 1/35 AN Address Information xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxx O 1/35 AN Address Information xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxx Version AIAG 33

37 N4 (Geographic Location) MAX N4 S N1 Optional 1 Max N1 Loops per LIN Loop = N1 & LIN Detail PURPOSE This segment is used to specify the geographic place of the named party. Max LIN Loops = 999, O 2/30 AN City Name xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx This element must be present since at least one of N401 or N405 must be present, and Key will not be using N O 2/2 ID State or Province Code xx If N401 is present, and N401 is a city located in the U.S. or Canada, then N402 is required O 3/15 ID Postal Code xxxxxxxxxxxxxxx O 2/3 ID Country Code C 1/2 ID Location O 1/30 AN Location Identifier Version AIAG 34

38 SDP (Ship/Delivery Pattern) (SDP Loop is Optional) MAX SDP S SDP Mandatory 1 Max SDP Loops per LIN Loop = SDP & LIN Detail PURPOSE This segment is used to identify specific ship/delivery requirements. Max LIN Loops = 999, M 1/2 ID Ship/Delivery or Calendar Pattern Code M 1/1 ID Ship/Delivery Pattern Time Code O 1/2 ID Ship/Delivery or Calendar Pattern Code O 1/1 ID Ship/Delivery Pattern Time Code O 1/2 ID Ship/Delivery or Calendar Pattern Code O 1/1 ID Ship/Delivery Pattern Time Code O 1/2 ID Ship/Delivery or Calendar Pattern Code O 1/1 ID Ship/Delivery Pattern Time Code xx x contain a code that specifies the routine shipments, deliveries, or calendar pattern. See the chapter entitled Data Element Dictionary in the ANSI X guide for a complete code list. contain a code that specifies the time for routine shipments or deliveries. See the chapter entitled Data Element Dictionary in the ANSI X guide for a complete code list. Version AIAG 35

39 FST (Forecast Schedule) MAX FST S SDP Optional 260 Max SDP Loops per LIN Loop = SDP & LIN Detail PURPOSE This segment is used to specify the forecasted dates and quantities. Max LIN Loops = 999, M 1/15 R Quantity xxxxxxxxxxxxxxx contain the forecast quantity M 1/1 ID Forecast A or B or C or D or Z M 1/1 ID Forecast Timing D or W A = Immediate B = Pilot/ Pre-Volume C = Firm D = Planning Z = Mutually Defined D = Discrete W = Weekly Bucket (Monday through Sunday) M 6/6 DT Date yymmdd contain the forecast begin date O 6/6 DT Date C 3/3 AN Date/Time C 4/8 AN Time C 2/3 AN Reference Identification C 1/30 AN Reference Identification O 2/2 ID Planning Schedule Type Code Version AIAG 36

40 SHP (Shipped/Received Information) (SHP Loop is Mandatory) MAX SHP S SHP Mandatory 1 Max SHP Loops per LIN Loop = SHP & LIN Detail PURPOSE This segment is used to specify shipment and/or receipt information. Max LIN Loops = 999, O 2/2 ID Quantity 01 or = Discrete Quantity 02 = Cumulative Quantity C 1/15 R Quantity xxxxxxxxxxxxxxx contain the discrete or cumulative quantity, depending upon the code in the SHP01 element C 3/3 AN Date/Time 011 or 050 or 051 If SHP01 is present, then SHP02 is required. 011 = Shipped 050 = Received 051 = Cumulative Quantity Start If SHP01 is equal to 01, then this element will contain code 011 for the date shipped, or 050 to indicate the date received. If SHP01 is equal to 02, then this element will contain code 051 to indicate the cumulative quantity start date. If SHP03 is present, then at least one of SHP04 or SHP05 are required. Version AIAG 37

41 SHP (Shipped/Received Information) (SHP Loop is Mandatory) (continued) MAX SHP S SHP Mandatory 1 Max SHP Loops per LIN Loop = SHP & LIN Detail PURPOSE This segment is used to specify shipment and/or receipt information. Max LIN Loops = 999, C 6/6 DT Date yymmdd If SHP01 is equal to 01, then this element will contain the shipped date if SHP03 is equal to 011 or the received date if SHP03 is equal to 050. If SHP01 is equal to 02, then this element will contain the cumulative quantity start date C 4/8 AN Time O 6/6 DT Date yymmdd If SHP01 is equal to 02, then this element will contain the cumulative quantity end date O 4/8 AN Time Version AIAG 38

42 REF (Reference Identification) MAX REF S SHP Optional 5 Max SHP Loops Per LIN Loop = SHP & LIN Detail PURPOSE This segment is used to specify identifying information. Max LIN Loops = 999, M 2/3 AN Reference Identification SI C 1/30 AN Reference Identification xxxxxxxxxxxxxxx xxxxxxxxxxxxxxx SI = Shipper s Identifying Number for Shipment (SID) contain the shipper s identifying number for shipment (SID). At least one of REF02 or REF03 is required C 1/80 AN Description C 2/3 AN Reference Identification C 1/30 AN Reference Identification C 2/3 AN Reference Identification C 1/30 AN Reference Identification C 2/3 AN Reference Identification C 1/30 AN Reference Identification Version AIAG 39

43 MAX CTT S CTT (Transaction Totals) PURPOSE Optional Summary This segment is used to transmit a hash total for a specific element in the transaction set M 1/6 N0 Number of Line Items xxxxxx contain the number of line items (LIN segments) in the transaction set O 1/10 R Hash Total xxxxxxxxxx contain the sum of the FST01 elements C 1/10 R Weight C 2/2 AN Unit or Basis for Measurement Code C 1/8 R Volume C 2/2 AN Unit or Basis for Measurement Code O 1/80 AN Description Version AIAG 40

44 MAX SE S SE (Transaction Set Trailer) PURPOSE Mandatory Summary This segment is used to indicate the end of a transaction set and to provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) M 1/10 N0 Number of Included Segments M 4/9 AN Transaction Set Control Number xxxxxxxxxx xxxxxxxxx contain the total number of transmitted segments within the transaction set, including the ST and SE segments. This number will be the same as the number in the corresponding ST02 element. Version AIAG 41

45 997 FUNCTIONAL ACKNOWLEDGMENT FUNCTIONAL GROUP ID = FA This standard provides the format and establishes the data contents of a functional acknowledgment transaction set. The purpose of this standard is to define the control structures for a set of acknowledgments to indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are the transaction sets, which are grouped in functional groups, used in defining transactions for business data interchange. This standard does not cover the semantic meaning of the information encoded in the transaction sets. RECOMMENDED PRACTICES: (taken from the AIAG Supply Chain: Recommended Practices for EDI Implementation Manual) A 997 should be created and sent for all transaction sets received except another 997. A 997 should always be used to confirm that all transactions sets sent have been received. A 997 only acknowledges the receipt of data in accordance with AIAG standards and does not acknowledge specific data content such as purchase order number, location, or part number. TABLE 1 HEADING AREA POS. SE G. ID NAME AIAG REQ. DES. USAGE KEY REQ. DES. MAX. USE REPEAT 010 ST Transaction Set Header M M AK AK AK AK AK AK 9 Functional Group Response Header M M 1 44 ID AK Transaction Set Response Header O M 1 45 ID AK Data Segment Note O O 1 46 Data Element Note O O Transaction Set Response Trailer M M 1 48 Functional Group Response Trailer M M SE Transaction Set Trailer M M 1 51 PAGE Version AIAG 42

46 SAMPLE 997 DOCUMENT ISA*00* *00* *01* *01* *980501*1000*U*00306* *0*T*:~ GS*FA* * *980501*1000*1000*X*003060~ ST*997* ~ AK1*PS*12~ AK2*830* ~ AK5*A~ AK9*A*1*1*1~ SE*6* ~ GE*1*1000~ IEA*1* ~ Version AIAG 43

47 MAX ST S ST (Transaction Set Header) PURPOSE Mandatory Heading This segment is used to indicate the beginning of a transaction set and to provide control information M 3/3 ID Transaction Set Identifier Code M 4/9 AN Transaction Set Control Number = X12.20 Functional Acknowledgment xxxxxxxxx contain an identifying control number that is assigned by the sender and is unique for the transaction set. Version AIAG 44

48 MAX AK1 S AK1 (Functional Group Response Header) PURPOSE Mandatory Heading This segment is used to start acknowledgment of a functional group M 2/2 ID Functional Identifier Code xx contain the code value of the GS01 element of the functional group being acknowledged M 1/9 N0 Group Control Number xxxxxxxxx contain the value of the GS06 element of the functional group being acknowledged. Version AIAG 45

49 AK2 (Transaction Set Response Header) MAX AK2 S Mandatory 1 Max AK2 Loops = 999,999 PURPOSE 030 AK2 Heading This segment is used to start acknowledgment of a single transaction set M 3/3 ID Transaction Set Identifier Code M 4/9 AN Transaction Set Control Number xxx xxxxxxxxx contain the code value of the ST01 element of the transaction set being acknowledged. contain the value of the ST02 element of the transaction set being acknowledged. Version AIAG 46

50 AK3 (Data Segment Note) MAX AK3 S Optional 1 Max AK3 Loops = 999, AK3 & AK2 Heading PURPOSE This segment is used to report errors in a data segment and to identify the location of the data segment. Max AK2 Loops = 999,999 Version AIAG M 2/3 ID Segment ID Code xxx contain a code identifying the data segment in error M 1/6 N0 Segment Position in Transaction Set xxxxxx contain the numerical count position of this data segment within the transaction set, with count position 1 being the ST segment O 1/4 AN Loop Identifier Code xxxx contain a code identifying a loop within the transaction set that is bounded by the related LS and LE segments. The loop ID number given on the transaction set diagram is recommended as the value for this data element in segments LS and LE O 1/3 ID Segment Syntax Error Code xxx contain a code indicating the error found based on the syntax editing of a segment. See the chapter entitled Data Element Dictionary in the ANSI X guide for a complete code list.

51 AK4 (Data Element Note) MAX AK4 S Optional 99 Max AK3 Loops = 999, AK3 & AK2 Heading PURPOSE This segment is used to report errors in a data element and to identify the location of the data element. Max AK2 Loops = 999, M 1/2 N0 Element Position in Segment O 1/4 N0 Data Element Reference Number M 1/3 ID Data Element Syntax Error Code O 1/99 AN Copy of Bad Data Element xx xxxx xxx xxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxxxxxxxxxxxxxx xxxx contain the relative position of the data element in error in this data segment. The count starts with 1 for the data element immediately following the segment ID. contain the reference number used to locate the data element in the Data Element Dictionary. contain a code indicating the error found after syntax editing of a data element. See the chapter entitled Data Element Dictionary in the ANSI X guide for a complete code list. contain a copy of the data element in error. Version AIAG 48

52 AK5 (Transaction Set Response Trailer) MAX AK5 S Mandatory 1 Max AK2 Loops = 999,999 PURPOSE 060 AK2 Heading This segment is used to acknowledge acceptance or rejection and to report errors in a transaction set M 1/1 ID Transaction Set Acknowledgment Code O 1/3 ID Transaction Set Syntax Error Code O 1/3 ID Transaction Set Syntax Error Code O 1/3 ID Transaction Set Syntax Error Code O 1/3 ID Transaction Set Syntax Error Code O 1/3 ID Transaction Set Syntax Error Code x xxx xxx xxx xxx xxx contain a code indicating the acceptance or rejection of the transaction set based on the syntax editing of the transaction set. See the chapter entitled Data Element Dictionary in the ANSI X guide for a complete code list. contain a code indicating the error found based on the syntax editing of the transaction set. See the chapter entitled Data Element Dictionary in the ANSI X guide for a complete code list. See Notes/ Comments for element AK502. See Notes/ Comments for element AK502. See Notes/ Comments for element AK502. See Notes/ Comments for element AK502. Version AIAG 49

53 MAX AK9 S AK9 (Functional Group Response Trailer) PURPOSE Mandatory Heading This segment is used to acknowledge acceptance or rejection of a functional group and to report the number of included transaction sets from the original trailer, the accepted sets, and the received sets in this functional group M 1/1 ID Functional Group Acknowledge Code M 1/6 N0 Number of Transaction Sets Included M 1/6 N0 Number of Received Transaction Sets 04 2 M 1/6 N0 Number of Accepted Transaction Sets x xxxxxx xxxxxx xxxxxx contain a code indicating the acceptance or rejection of the functional group based on the syntax editing of the functional group. See the chapter entitled Data Element Dictionary in the ANSI X guide for a complete code list. contain the total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element. contain the number of transaction sets received. contain the number of accepted transaction sets in a functional group. Version AIAG 50

54 MAX AK9 S AK9 (Functional Group Response Trailer) (continued) PURPOSE Mandatory Heading This segment is used to acknowledge acceptance or rejection of a functional group and to report the number of included transaction sets from the original trailer, the accepted sets, and the received sets in this functional group O 1/3 ID Functional Group Syntax Error Code O 1/3 ID Functional Group Syntax Error Code O 1/3 ID Functional Group Syntax Error Code O 1/3 ID Functional Group Syntax Error Code O 1/3 ID Functional Group Syntax Error Code xxx xxx xxx xxx xxx contain a code indicating the error found based on the syntax editing of the functional group header and/or trailer. See the chapter entitled Data Element Dictionary in the ANSI X guide for a complete code list. See Notes/ Comments for element AK905. See Notes/ Comments for element AK905. See Notes/ Comments for element AK905. See Notes/ Comments for element AK905. Version AIAG 51

55 MAX SE S SE (Transaction Set Trailer) PURPOSE Mandatory Heading This segment is used to indicate the end of a transaction set and to provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments) M 1/10 N0 Number of Included Segments M 4/9 AN Transaction Set Control Number xxxxxxxxxx xxxxxxxxx contain the total number of transmitted segments within the transaction set, including the ST and SE segments. This number will be the same as the number in the corresponding ST02 element. Version AIAG 52

56 APPENDIX A GLOSSARY TERMS AIAG ANSI ASC X12 COMPOSITE ELEMENT Automotive Industry Action Group. A not-for-profit trade association for automobile, heavy truck, and off-road vehicle manufacturers and suppliers. The AIAG s mission is to improve the productivity of its members and the North American Automotive Industry. American National Standards Institute Accredited Standards Committee X12. This committee develops and maintains U.S. generic standards for Electronic Data Interchange. In the EDI standards, a grouping of related sub-elements, such as the elements that make up a name and address. CONTROL STRUCTURE The beginning and end (header and trailer) segments for entities in Electronic Data Interchange. ELEMENT ELEMENT DELIMITER DUNS NUMBER EBCDIC EDI The smallest named item in the standard. It can represent a qualifier, a value, or text (such as a description). A data element has two primary attributes: length and type. Each data element is identified by a number used for reference in the data element dictionary. A separating character, such as an asterisk (*), that precedes each data element within a segment. A data segment is the intermediate unit of information in a message. A segment consists of a predefined set of functionally related data elements that are identified by their sequential positions within the set. Each segment has a unique segment identifier a combination of two or three uppercase letters and/or digits that serves as a name for the segment and occupies the first character positions of the segment. When data segments are combined to form a message, their relation to the message is specified by a data segment requirement designator and a data segment sequence. Dun & Bradstreet Universal Numbering System. A 9-digit number assigned by the Dun & Bradstreet Corporation to identify a business enterprise. The ninth digit is a check sum, which can be calculated to ensure there were no transposition errors in the transmission. Extended Binary Code for Decimal InterChange. EBCDIC is an 8-bit code used to define character representations for IBM mainframe computers. Electronic Data Interchange. The computer-to-computer exchange of routine business data in an approved standard format. The information is stored electronically in an organization s computer. The second organization s computer then responds to the content of the information it has received. Version AIAG 53