electronic data interchange (edi) i g mplementation
TRANSCRIPT
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG Transaction Sets 830 and 997
ELECTRONIC DATA INTERCHANGE (EDI)
IMPLEMENTATION GUIDE
PHASE 1
VERSION 003060AIAG
TRANSACTION SETS 830 & 997
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG i Transaction Sets 830 and 997
TABLE OF 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 .................................................................................. 10 GS – Functional Group Header ..................................................................................... 11 GE – Functional Group Trailer ...................................................................................... 12
TRANSACTION SET 830 – PLANNING SCHEDULE WITH RELEASE CAPABILITY Transaction Set Description ........................................................................................... 13 Transaction Set Diagram ............................................................................................... 15 Sample 830 Document .................................................................................................. 16 Transaction Set Table 1 (Heading Area) Segments
ST – Transaction Set Header ................................................................................ 17 BFR – Beginning Segment for Planning Schedule ................................................ 18 DTM – Date/Time Reference ................................................................................. 20 N1 – Name ............................................................................................................. 21 N3 – Address Information ...................................................................................... 22 N4 – Geographic Location ..................................................................................... 23
Transaction Set Table 2 (Detail Area) Segments LIN – Item Identification ......................................................................................... 24 UIT – Unit Detail ..................................................................................................... 26 REF – Reference Identification .............................................................................. 27 PER – Administrative Communications Contact .................................................... 28 ATH – Resource Authorization .............................................................................. 29 N1 – Name ............................................................................................................. 31 N3 – Address Information ...................................................................................... 32 N4 – Geographic Location ..................................................................................... 33 SDP – Ship/Delivery Pattern .................................................................................. 34 FST – Forecast Schedule ...................................................................................... 35 SHP – Shipped/Received Information ................................................................... 36 REF – Reference Identification .............................................................................. 38
Transaction Set Table 3 (Summary Area) Segments CTT – Transaction Totals ...................................................................................... 39 SE – Transaction Set Trailer .................................................................................. 40
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG ii Transaction Sets 830 and 997
TABLE OF CONTENTS (continued)
Page No.
TRANSACTION SET 997 – FUNCTIONAL ACKNOWLEDGMENT Transaction Set Description & Diagram ........................................................................ 41 Sample 997 Document .................................................................................................. 42 Transaction Set Table 1 (Heading Area) Segments
ST – Transaction Set Header ................................................................................ 43 AK1 – Functional Group Response Header .......................................................... 44 AK2 – Transaction Set Response Header ............................................................. 45 AK3 – Data Segment Note ..................................................................................... 46 AK4 – Data Element Note ...................................................................................... 47 AK5 – Transaction Set Response Trailer .............................................................. 48 AK9 – Functional Group Response Trailer ............................................................ 49 SE – Transaction Set Trailer .................................................................................. 51
APPENDIX A – GLOSSARY OF TERMS ............................................................... 52
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 1 Transaction Sets 830 and 997
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)
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 2 Transaction Sets 830 and 997
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.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 3 Transaction Sets 830 and 997
CONTACTS
Perot Systems/Key Plastics, L.L.C. Maria Stombaugh Email: [email protected] GE Information Services, Inc. AIAG 401 N. Washington Street (Automotive Industry Action Group) Rockville, MD 20850 26200 Lahser Road, Suite 200 EDI Information: 800-334-5669 Southfield, MI 48034 Trading Partner Setup: 800-334-2255 Phone: 248-358-3570 www.support.geis.com Email: www.aiag.org Dun & Bradstreet 1 Diamond Hill Road Murray Hill, NJ 07974-0027 Phone: 800-333-0505 (USA) 800-999-3867 x 7090 (Int’l) Email: http://www.dnb.com/dbis/dnbhome.htm
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 4 Transaction Sets 830 and 997
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.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 5 Transaction Sets 830 and 997
DEFINITIONS AND CONTROL STRUCTURES DATA ELEMENT TYPES
TYPE DESCRIPTION FORMAT 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: “+” “-”
DATA ELEMENT REQUIREMENT DESIGNATORS
DESIGNATOR 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.
DATA DELIMITERS
TYPE EBCDIC VALUE HEX VALUE
Terminator ~ (HEX A1)
Element Separator * (HEX 5C)
Sub-element Separator : (HEX 7A)
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 6 Transaction Sets 830 and 997
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 SET
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.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 7 Transaction Sets 830 and 997
INTERCHANGE STRUCTURE
IEA – Interchange Control Trailer
ISA – Interchange Control Header
GE – Functional Group Trailer
GS – Functional Group Header
SE – Transaction Set Trailer
ST – Transaction Set Header
Detail Segments
SE – Transaction Set Trailer
ST – Transaction Set Header
Detail Segments
GE – Functional Group Trailer
GS – Functional Group Header
SE – Transaction Set Trailer
ST – Transaction Set Header
Detail Segments
SE – Transaction Set Trailer
ST – Transaction Set Header
Detail Segments
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 8 Transaction Sets 830 and 997
ISA (Interchange Control Header)
SEGMENT REQUIREMENT
MAX ISA SEGMENTS
ALLOWED PER INTERCHANGE
SEGMENT 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
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 I01 M 2/2 ID Authorization
Information Qualifier “00” 00 = No
Authorization Information Present
02 I02 M 10/10 AN Authorization Information
“bbbbbbbbbb” This element will contain ten spaces.
03 I03 M 2/2 ID Security Information Qualifier
“00” 00 = No Security Information Present
04 I04 M 10/10 AN Security Information “bbbbbbbbbb” This element will contain ten spaces.
05 I05 M 2/2 ID Interchange ID Qualifier “01” 01 = DUNS Number
06 I06 M 15/15 AN Interchange Sender ID “xxxxxxxxxxxxxxx” This element will contain the Sender’s DUNS number.
07 I05 M 2/2 ID Interchange ID Qualifier “01” 01 = DUNS Number
08 I07 M 15/15 AN Interchange Receiver ID “xxxxxxxxxxxxxxx” This element will contain the Receiver’s DUNS number.
09 I08 M 6/6 DT Interchange Date “yymmdd” This element will contain the date the interchange was generated. (Example: 980501)
10 I09 M 4/4 TM Interchange Time “hhmm” This element will 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
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 9 Transaction Sets 830 and 997
ISA (Interchange Control Header)
(continued)
SEGMENT REQUIREMENT
MAX ISA SEGMENTS
ALLOWED PER INTERCHANGE
SEGMENT 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
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 12 I11 M 5/5 ID Interchange Control
Version Number “00306” 00306 = Draft Std.
For Trial Use Approved by ASC X12 Through Oct. 1995
13 I12 M 9/9 N0 Interchange Control Number
“xxxxxxxxx” This element will contain an identifying control number that is assigned by the sender and is unique for the interchange.
14 I13 M 1/1 ID Acknowledgement Requested
“0” This element will 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” This element will contain a “T” in the testing phase, and a “P” in the production phase.
16 I15 M 1/1 AN Sub-element Separator “:” This element will contain the value used to separate composite elements.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 10 Transaction Sets 830 and 997
IEA (Interchange Control Trailer)
SEGMENT REQUIREMENT
MAX IEA SEGMENTS
ALLOWED PER INTERCHANGE
SEGMENT PURPOSE
Mandatory 1 This segment is used to indicate the end of an interchange and to provide control information.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 I16 M 1/5 N0 Number of Included
Functional Groups “xxxxx” This element will
contain the number of functional groups contained within the interchange.
02 I12 M 9/9 N0 Interchange Control Number
“xxxxxxxxx” This element will contain the same control number used in the corresponding ISA13 element.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 11 Transaction Sets 830 and 997
GS (Functional Group Header)
SEGMENT REQUIREMENT
MAX GS SEGMENTS
ALLOWED PER FUNC. GROUP
SEGMENT 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.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 479 M 2/2 ID Functional Identifier
Code “FA” or “PS” FA = Functional
Acknowledg- ment PS = Planning Schedule with Release Capability
02 142 M 9/9 AN Application Sender’s Code
“xxxxxxxxx” This element will contain the Sender’s DUNS number.
03 124 M 9/9 AN Application Receiver’s Code
“xxxxxxxxx” This element will contain the Receiver’s DUNS number.
04 29 M 6/6 DT Group Date “yymmdd” This element will contain the date the functional group was generated.
05 30 M 4/4 TM Group Time “hhmm” This element will contain the time the functional group was generated.
06 28 M 1/9 N0 Group Control Number “xxxxxxxxx” This element will contain an identifying control number that is assigned by the sender and is unique for the functional group.
07 455 M 1/2 ID Responsible Agency Code
“X” X = Accredited Standards Committee X12
08 480 M 1/12 AN Version/Release Indicator Code
“003060” 003060 = ASC X12 Standards Approved by ANSI in 1997
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 12 Transaction Sets 830 and 997
GE (Functional Group Trailer)
SEGMENT REQUIREMENT
MAX GE SEGMENTS
ALLOWED PER FUNC. GROUP
SEGMENT PURPOSE
Mandatory 1 This segment is used to indicate the end of a functional group and to provide control information.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 97 M 1/6 N0 Number of Included
Sets “xxxxxx” This element will
contain the number of transaction sets (documents) contained within the functional group.
02 28 M 1/9 N0 Group Control Number “xxxxxxxxx” This element will contain the same control number used in the corresponding GS06 element.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 13 Transaction Sets 830 and 997
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.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 14 Transaction Sets 830 and 997
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.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 15 Transaction Sets 830 and 997
830 PLANNING SCHEDULE WITH RELEASE CAPABILITY
TABLE 1 – HEADING AREA USAGE
POS. NO.
SE
G. ID
NAME
AIAG REQ. DES.
KEY REQ. DES.
MAX. USE
LOOP
REPEAT
PAGE NO.
010 ST Transaction Set Header M M 1 17 020 BF
R Beginning Segment for Planning Schedule M M 1 18
130 DTM
Date/Time Reference O O 10 20
LOOP ID – N1 200 21 230 N1 Name O M 1 21 250 N3 Address Information O O 2 22 260 N4 Geographic Location O O 1 23
TABLE 2 – DETAIL AREA USAGE
POS. NO.
SE
G. ID
NAME
AIAG REQ. DES.
KEY REQ. DES.
MAX. USE
LOOP
REPEAT
PAGE NO.
LOOP ID – LIN > 1 24 010 LI
N Item Identification M M 1 24
020 UIT
Unit Detail O M 1 26
140 REF
Reference Identification O O 12 27
150 PER
Administrative Communications Contact O O 3 28
230 ATH
Resource Authorization O M 20 29
LOOP ID – N1 200 31 320 N1 Name O O 1 31 340 N3 Address Information O O 2 32 350 N4 Geographic Location O O 1 33
LOOP ID – SDP 260 34 450 SD
P Ship/Delivery Pattern O O 1 34
460 FST
Forecast Schedule O O 260 35
LOOP ID – SHP 25 36 470 SH
P Shipped/Received Information O M 1 36
480 REF
Reference Identification O O 5 38
TABLE 3 – SUMMARY AREA
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 16 Transaction Sets 830 and 997
USAGE
POS. NO.
SE
G. ID
NAME
AIAG REQ. DES.
KEY REQ. DES.
MAX. USE
LOOP
REPEAT
PAGE NO.
010 CTT
Transaction Totals O O 1 39
020 SE Transaction Set Trailer M M 1 40
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 17 Transaction Sets 830 and 997
SAMPLE 830 DOCUMENT
ISA*00* *00* *01*603446881 *01*123456789 *980501*0930*U*00306*000002318*0*T*:~
GS*PS*603446881*123456789*980501*0930*12*X*003060~ ST*830*000000012~ BFR*05*00014**SH*A*980501*980820*980501***A12345~ DTM*168*980501***19~ N1*BT*Key Plastics Plymouth Div*1*603446881~ N3*40300 Plymouth Rd.~ N4*Plymouth*MI*48170~ N1*SU*ABC Company*1*164859051~ N3*123 Anywhere St.~ N4*Anytown*IN*138619391~ N1*ST*Key Plastics*1*603446881~ 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*2061936~ 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*1003663~ SHP*02*110*051*980101**980428~ CTT*2*37750~ SE*41*000000012~ GE*1*12~ IEA*1*000002318~
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 18 Transaction Sets 830 and 997
ST (Transaction Set Header)
SEGMENT REQUIREMENT
MAX ST SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1
010 Heading This segment is used to indicate the beginning of a transaction set and to provide control information.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 143 M 3/3 ID Transaction Set
Identifier Code “830” 830 = X12.14
Planning Schedule with Release Capability
02 329 M 4/9 AN Transaction Set Control Number
“xxxxxxxxx” This element will contain an identifying control number that is assigned by the sender and is unique for the transaction set.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 19 Transaction Sets 830 and 997
BFR (Beginning Segment for Planning Schedule)
SEGMENT REQUIREMENT
MAX BFR SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1 020 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.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 353 M 2/2 ID Transaction Set
Purpose Code “05” 05 = Replace
02 127 C 1/30 AN Reference Identification “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”
This element will contain the Release Number.
03 328 C 1/30 AN Release Number Not Used
04 675 M 2/2 ID Schedule Type Qualifier “DL” or “SH” DL = Delivery Based (when materials must be delivered to Key Plastics’ receiving location) SH = Shipment Based (when materials must leave the supplier’s shipping location)
05 676 M 1/1 ID Schedule Quantity Qualifier
“A” A = Actual Discreet Quantities (type of quantities used when defining a schedule or forecast)
06 373 M 6/6 DT Date “yymmdd” This element will contain the forecast horizon start date.
07 373 O 6/6 DT Date “yymmdd” This element will contain the forecast horizon end date.
08 373 M 6/6 DT Date “yymmdd” This element will contain the date the forecast was generated.
09 373 O 6/6 DT Date Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 20 Transaction Sets 830 and 997
BFR (Beginning Segment for Planning Schedule)
(continued)
SEGMENT REQUIREMENT
MAX BFR SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1 020 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.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 10 367 O 1/30 AN Contract Number Not Used
11 324 O 1/22 AN Purchase Order Number
“xxxxxxxxxxxxxxxxxxxxxx”
This element will contain the Purchase Order Number.
12 783 O 2/2 ID Planning Schedule Type Code
Not Used
13 306 O 1/2 ID Action Code Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 21 Transaction Sets 830 and 997
DTM (Date/Time Reference)
SEGMENT REQUIREMENT
MAX DTM SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional 10 130 Heading This segment is used to specify pertinent dates and times.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 374 M 3/3 ID Date/Time Qualifier “168” 168 = Release
02 373 C 6/6 DT Date “yymmdd” This element will contain the date the forecast was generated.
03 337 C 4/8 AN Time Not Used
04 623 O 2/2 ID Time Code Not Used
05 624 O 2/2 N0 Century “19” or “20” This element will contain the first two characters in the designation of the year (CCYY).
06 1250 C 2/3 ID Date Time Period Format Qualifier
Not Used
07 1251 C 1/35 AN Date Time Period Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 22 Transaction Sets 830 and 997
N1 (Name)
(N1 Loop is Mandatory)
SEGMENT
REQUIREMENT
MAX N1 SEGMENTS
ALLOWED PER N1 LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1 Max N1 Loops = 200
230 N1 Heading This segment is used to identify a party by type of organization, name and code.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 98 M 2/2 ID Entity Identifier Code “BT” or “SF”
or “ST” or “SU” 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.
02 93 C 1/35 AN Name “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxx”
This element will contain the free-form name of the identified party. At least one of N102 or N103 is required.
03 66 C 1/2 ID Identification Code Qualifier
“1” 1 = DUNS Number If either N103 or N104 is present, then the other is required.
04 67 C 2/20 AN Identification Code “xxxxxxxxxxxxxxxxx”
This element will contain the DUNS number of the identified party. (The DUNS number will not contain embedded spaces or dashes.)
05 706 O 2/2 ID Entity Relationship Code
Not Used
06 98 O 2/2 AN Entity Identifier Code Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 23 Transaction Sets 830 and 997
N3 (Address Information)
SEGMENT REQUIREMENT
MAX N3 SEGMENTS
ALLOWED PER N1 LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional 2 Max N1 Loops = 200
250 N1 Heading This segment is used to specify the location of the named party.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 166 M 1/35 AN Address Information “xxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxx”
02 166 O 1/35 AN Address Information “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxx”
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 24 Transaction Sets 830 and 997
N4 (Geographic Location)
SEGMENT REQUIREMENT
MAX N4 SEGMENTS
ALLOWED PER N1 LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional 1 Max N1 Loops = 200
260 N1 Heading This segment is used to specify the geographic place of the named party.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 19 O 2/30 AN City Name “xxxxxxxxxxxxxxx
xxxxxxxxxxxxxxx” At least one of N401 or N405 must be present.
02 156 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.
03 116 O 3/15 ID Postal Code “xxxxxxxxxxxxxxx”
04 26 O 2/3 ID Country Code Not Used
05 309 C 1/2 ID Location Qualifier Not Used
06 310 O 1/30 AN Location Identifier Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 25 Transaction Sets 830 and 997
LIN (Item Identification)
(LIN Loop is Mandatory)
SEGMENT
REQUIREMENT
MAX LIN SEGMENTS
ALLOWED PER LIN LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1
Max LIN Loops = 999,999
010 LIN Detail This segment is used to specify basic item identification data.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 350 O 1/20 AN Assigned Identification Not Used
02 235 M 2/2 ID Product/Service ID Qualifier
“BP” BP = Buyer’s Part Number
03 234 M 1/40 AN Product/Service ID “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxx”
This element will contain the buyer’s part number.
04 235 C 2/2 ID Product/Service ID Qualifier
“VP” VP = Vendor’s (Seller’s) Part Number
05 234 C 1/40 AN Product/Service ID “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxx”
This element will contain the vendor’s part number. If LIN04 or LIN05 is present, then the other is required.
06 235 C 2/2 ID Product/Service ID Qualifier
“EC” EC = Engineering Change Level
07 234 C 1/40 AN Product/Service ID “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxxxxxxx”
This element will contain the engineering change level. If LIN06 or LIN07 is present, then the other is required.
08 235 C 2/2 ID Product/Service ID Qualifier
Not Used
09 234 C 1/40 AN Product/Service ID Not Used
10 235 C 2/2 ID Product/Service ID Qualifier
Not Used
11 234 C 1/40 AN Product/Service ID Not Used
12 235 C 2/2 ID Product/Service ID Qualifier
Not Used
13 234 C 1/40 AN Product/Service ID Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 26 Transaction Sets 830 and 997
LIN (Item Identification)
(continued)
SEGMENT REQUIREMENT
MAX LIN SEGMENTS
ALLOWED PER LIN LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1
Max LIN Loops = 999,999
010 LIN Detail This segment is used to specify basic item identification data.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 14 235 C 2/2 ID Product/Service ID
Qualifier Not Used
15 234 C 1/40 AN Product/Service ID Not Used
16 235 C 2/2 ID Product/Service ID Qualifier
Not Used
17 234 C 1/40 AN Product/Service ID Not Used
18 235 C 2/2 ID Product/Service ID Qualifier
Not Used
19 234 C 1/40 AN Product/Service ID Not Used
20 235 C 2/2 ID Product/Service ID Qualifier
Not Used
21 234 C 1/40 AN Product/Service ID Not Used
22 235 C 2/2 ID Product/Service ID Qualifier
Not Used
23 234 C 1/40 AN Product/Service ID Not Used
24 235 C 2/2 ID Product/Service ID Qualifier
Not Used
25 234 C 1/40 AN Product/Service ID Not Used
26 235 C 2/2 ID Product/Service ID Qualifier
Not Used
27 234 C 1/40 AN Product/Service ID Not Used
28 235 C 2/2 ID Product/Service ID Qualifier
Not Used
29 234 C 1/40 AN Product/Service ID Not Used
30 235 C 2/2 ID Product/Service ID Qualifier
Not Used
31 234 C 1/40 AN Product/Service ID Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 27 Transaction Sets 830 and 997
UIT (Unit Detail)
SEGMENT
REQUIREMENT
MAX UIT SEGMENTS
ALLOWED PER LIN LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
S ET
LEVEL
SEGMENT PURPOSE
Mandatory 1
Max LIN Loops = 999,999
020 LIN Detail This segment is used to specify item unit data.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 355 M 2/2 ID Unit or Basis for
Measurement Code “xx” 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.
02 212 C 1/17 R Unit Price Not Used
03 639 O 2/2 ID Basis of Unit Price Code
Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 28 Transaction Sets 830 and 997
REF (Reference Identification)
SEGMENT REQUIREMENT
MAX REF SEGMENTS
ALLOWED PER LIN LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional 12
Max LIN Loops = 999,999
140 LIN Detail This segment is used to specify identifying information.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 128 M 2/3 ID Reference Identification
Qualifier “DK” DK = Dock Number
02 127 C 1/30 AN Reference Identification “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”
This element will contain the Dock Number.
03 352 C 1/80 AN Description Not Used
04 C040 O Reference Number Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 29 Transaction Sets 830 and 997
PER (Administrative Communications Contact)
SEGMENT REQUIREMENT
MAX PER SEGMENTS
ALLOWED PER LIN LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional 3
Max LIN Loops = 999,999
150 LIN Detail This segment is used to identify a person or office to whom administrative communications should be directed.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 366 M 2/2 ID Contact Function Code “BD” or “EX” BD = Buyer Name
or Department EX = Expeditor
02 93 O 1/35 AN Name “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxx”
This element will contain the Buyer Name or Department or the name of the Expeditor.
03 365 C 2/2 ID Communication Number Qualifier
Not Used
04 364 C 1/80 AN Communication Number Not Used
05 365 C 2/2 ID Communication Number Qualifier
Not Used
06 364 C 1/80 AN Communication Number Not Used
07 365 C 2/2 ID Communication Number Qualifier
Not Used
08 364 C 1/80 AN Communication Number Not Used
09 443 O 1/20 AN Contact Inquiry Reference
Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 30 Transaction Sets 830 and 997
ATH (Resource Authorization)
SEGMENT REQUIREMENT
MAX ATH SEGMENTS
ALLOWED PER LIN LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional 20
Max LIN Loops = 999,999
230 LIN Detail This segment is used to specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 672 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”.
02 373 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.
03 380 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.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 31 Transaction Sets 830 and 997
ATH (Resource Authorization)
(continued)
SEGMENT REQUIREMENT
MAX ATH SEGMENTS
ALLOWED PER LIN LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 20
Max LIN Loops = 999,999
230 LIN Detail This segment is used to specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 03 380 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.
04 380 O 1/15 R Quantity Not Used
05 373 C 6/6 DT Date “yymmdd” This element will contain the cumulative quantity start date.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 32 Transaction Sets 830 and 997
N1 (Name)
(N1 Loop is Optional)
SEGMENT
REQUIREMENT
MAX N1 SEGMENTS
ALLOWED PER N1 LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1
Max N1 Loops per LIN Loop = 200 Max LIN Loops = 999,999
320 N1 &
LIN
Detail This segment is used to identify a party by type of organization, name and code. (The N1(320) loop is used only if the Ship To location varies for the different part numbers.)
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 98 M 2/2 ID Entity Identifier Code “ST” ST = Ship To
02 93 C 1/35 AN Name “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxx”
This element will contain the free-form name of the identified party. At least one of N102 or N103 is required.
03 66 C 1/2 ID Identification Code Qualifier
“1” 1 = DUNS Number If either N103 or N104 is present, then the other is required.
04 67 C 2/20 ID Identification Code “xxxxxxxxxxxxxxxxxxxx”
This element will contain the DUNS number of the identified party. (The DUNS number will not contain embedded spaces or dashes.)
05 706 O 2/2 ID Entity Relationship Code
Not Used
06 98 O 2/2 AN Entity Identifier Code Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 33 Transaction Sets 830 and 997
N3 (Address Information)
SEGMENT REQUIREMENT
MAX N3 SEGMENTS
ALLOWED PER N1 LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional 2
Max N1 Loops per LIN Loop = 200 Max LIN Loops = 999,999
340 N1 &
LIN
Detail This segment is used to specify the location of the named party.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 166 M 1/35 AN Address Information “xxxxxxxxxxxxxxx
xxxxxxxxxxxxxxxxxxxx”
02 166 O 1/35 AN Address Information “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxx”
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 34 Transaction Sets 830 and 997
N4 (Geographic Location)
SEGMENT REQUIREMENT
MAX N4 SEGMENTS
ALLOWED PER N1 LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional 1
Max N1 Loops per LIN Loop = 200 Max LIN Loops = 999,999
350 N1 &
LIN
Detail This segment is used to specify the geographic place of the named party.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 19 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 N405.
02 156 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.
03 116 O 3/15 ID Postal Code “xxxxxxxxxxxxxxx”
04 26 O 2/3 ID Country Code Not Used
05 309 C 1/2 ID Location Qualifier Not Used
06 310 O 1/30 AN Location Identifier Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 35 Transaction Sets 830 and 997
SDP (Ship/Delivery Pattern) (SDP Loop is Optional)
SEGMENT REQUIREMENT
MAX SDP SEGMENTS
ALLOWED PER SDP LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory
1
Max SDP Loops per LIN Loop = 260 Max LIN Loops = 999,999
450 SDP &
LIN
Detail This segment is used to identify specific ship/delivery requirements.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 678 M 1/2 ID Ship/Delivery or
Calendar Pattern Code “xx” This element will
contain a code that specifies the routine shipments, deliveries, or calendar pattern. See the chapter entitled “Data Element Dictionary” in the ANSI X12 3060 guide for a complete code list.
02 679 M 1/1 ID Ship/Delivery Pattern Time Code
“x” This element will contain a code that specifies the time for routine shipments or deliveries. See the chapter entitled “Data Element Dictionary” in the ANSI X12 3060 guide for a complete code list.
03 678 O 1/2 ID Ship/Delivery or Calendar Pattern Code
Not Used
04 679 O 1/1 ID Ship/Delivery Pattern Time Code
Not Used
05 678 O 1/2 ID Ship/Delivery or Calendar Pattern Code
Not Used
06 679 O 1/1 ID Ship/Delivery Pattern Time Code
Not Used
07 678 O 1/2 ID Ship/Delivery or Calendar Pattern Code
Not Used
08 679 O 1/1 ID Ship/Delivery Pattern Time Code
Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 36 Transaction Sets 830 and 997
FST (Forecast Schedule)
SEGMENT REQUIREMENT
MAX FST SEGMENTS
ALLOWED PER SDP LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional
260
Max SDP Loops per LIN Loop = 260 Max LIN Loops = 999,999
460 SDP &
LIN
Detail This segment is used to specify the forecasted dates and quantities.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 380 M 1/15 R Quantity “xxxxxxxxxxxxxxx” This element will
contain the forecast quantity.
02 680 M 1/1 ID Forecast Qualifier “A” or “B” or “C” or “D” or “Z”
A = Immediate B = Pilot/ Pre-Volume C = Firm D = Planning Z = Mutually Defined
03 681 M 1/1 ID Forecast Timing Qualifier
“D” or “W” D = Discrete W = Weekly Bucket (Monday through Sunday)
04 373 M 6/6 DT Date “yymmdd” This element will contain the forecast begin date.
05 373 O 6/6 DT Date Not Used
06 374 C 3/3 AN Date/Time Qualifier Not Used
07 337 C 4/8 AN Time Not Used
08 128 C 2/3 AN Reference Identification Qualifier
Not Used
09 127 C 1/30 AN Reference Identification Not Used
10 783 O 2/2 ID Planning Schedule Type Code
Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 37 Transaction Sets 830 and 997
SHP (Shipped/Received Information)
(SHP Loop is Mandatory)
SEGMENT
REQUIREMENT
MAX SHP SEGMENTS
ALLOWED PER SHP LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory
1
Max SHP Loops per LIN Loop = 25 Max LIN Loops = 999,999
470 SHP &
LIN
Detail This segment is used to specify shipment and/or receipt information.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 673 O 2/2 ID Quantity Qualifier “01” or “02” 01 = Discrete
Quantity 02 = Cumulative Quantity
02 380 C 1/15 R Quantity “xxxxxxxxxxxxxxx” This element will contain the discrete or cumulative quantity, depending upon the code in the SHP01 element. If SHP01 is present, then SHP02 is required.
03 374 C 3/3 AN Date/Time Qualifier “011” or “050” or “051”
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.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 38 Transaction Sets 830 and 997
SHP (Shipped/Received Information)
(SHP Loop is Mandatory) (continued)
SEGMENT REQUIREMENT
MAX SHP SEGMENTS
ALLOWED PER SHP LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory
1
Max SHP Loops per LIN Loop = 25 Max LIN Loops = 999,999
470 SHP &
LIN
Detail This segment is used to specify shipment and/or receipt information.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 04 373 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.
05 337 C 4/8 AN Time Not Used
06 373 O 6/6 DT Date “yymmdd” If SHP01 is equal to “02”, then this element will contain the cumulative quantity end date.
07 337 O 4/8 AN Time Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 39 Transaction Sets 830 and 997
REF (Reference Identification)
SEGMENT REQUIREMENT
MAX REF SEGMENTS
ALLOWED PER SHP LOOP
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional
5
Max SHP Loops Per LIN Loop = 25 Max LIN Loops = 999,999
480 SHP &
LIN
Detail This segment is used to specify identifying information.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 128 M 2/3 AN Reference Identification
Qualifier “SI” SI = Shipper’s
Identifying Number for Shipment (SID)
02 127 C 1/30 AN Reference Identification “xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx”
This element will contain the shipper’s identifying number for shipment (SID). At least one of REF02 or REF03 is required.
03 352 C 1/80 AN Description Not Used
04 128 C 2/3 AN Reference Identification Qualifier
Not Used
05 127 C 1/30 AN Reference Identification Not Used
06 128 C 2/3 AN Reference Identification Qualifier
Not Used
07 127 C 1/30 AN Reference Identification Not Used
08 128 C 2/3 AN Reference Identification Qualifier
Not Used
09 127 C 1/30 AN Reference Identification Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 40 Transaction Sets 830 and 997
CTT (Transaction Totals)
SEGMENT REQUIREMENT
MAX CTT SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional
1 010 Summary This segment is used to transmit a hash total for a specific element in the transaction set.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 354 M 1/6 N0 Number of Line Items “xxxxxx” This element will
contain the number of line items (LIN segments) in the transaction set.
02 347 O 1/10 R Hash Total “xxxxxxxxxx” This element will contain the sum of the FST01 elements.
03 81 C 1/10 R Weight Not Used
04 355 C 2/2 AN Unit or Basis for Measurement Code
Not Used
05 183 C 1/8 R Volume Not Used
06 355 C 2/2 AN Unit or Basis for Measurement Code
Not Used
07 352 O 1/80 AN Description Not Used
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 41 Transaction Sets 830 and 997
SE (Transaction Set Trailer)
SEGMENT REQUIREMENT
MAX SE SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1
020 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).
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 96 M 1/10 N0 Number of Included
Segments “xxxxxxxxxx” This element will
contain the total number of transmitted segments within the transaction set, including the ST and SE segments.
02 329 M 4/9 AN Transaction Set Control Number
“xxxxxxxxx” This number will be the same as the number in the corresponding ST02 element.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 42 Transaction Sets 830 and 997
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 USAGE
POS. NO.
SE
G. ID
NAME
AIAG REQ. DES.
KEY REQ. DES.
MAX. USE
LOOP
REPEAT
PAGE NO.
010 ST Transaction Set Header M M 1 43
020 AK1
Functional Group Response Header M M 1 44
LOOP ID – AK2 999999 45
030 AK2
Transaction Set Response Header O M 1 45
LOOP ID – AK3 999999 46
040 AK3
Data Segment Note O O 1 46
050 AK4
Data Element Note O O 99 47
060 AK5
Transaction Set Response Trailer M M 1 48
070 AK9
Functional Group Response Trailer M M 1 49
080 SE Transaction Set Trailer M M 1 51
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 43 Transaction Sets 830 and 997
SAMPLE 997 DOCUMENT
ISA*00* *00* *01*123456789 *01*603446881 *980501*1000*U*00306*000000023*0*T*:~
GS*FA*123456789*603446881*980501*1000*1000*X*003060~ ST*997*000010000~ AK1*PS*12~ AK2*830*000000012~ AK5*A~ AK9*A*1*1*1~ SE*6*000010000~ GE*1*1000~ IEA*1*000000023~
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 44 Transaction Sets 830 and 997
ST (Transaction Set Header)
SEGMENT REQUIREMENT
MAX ST SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1
010 Heading This segment is used to indicate the beginning of a transaction set and to provide control information.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 143 M 3/3 ID Transaction Set
Identifier Code “997” 997 = X12.20
Functional Acknowledg- ment
02 329 M 4/9 AN Transaction Set Control Number
“xxxxxxxxx” This element will contain an identifying control number that is assigned by the sender and is unique for the transaction set.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 45 Transaction Sets 830 and 997
AK1 (Functional Group Response Header)
SEGMENT REQUIREMENT
MAX AK1 SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1
020 Heading This segment is used to start acknowledgment of a functional group.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 479 M 2/2 ID Functional Identifier
Code “xx” This element will
contain the code value of the GS01 element of the functional group being acknowledged.
02 28 M 1/9 N0 Group Control Number “xxxxxxxxx” This element will contain the value of the GS06 element of the functional group being acknowledged.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 46 Transaction Sets 830 and 997
AK2 (Transaction Set Response Header)
SEGMENT REQUIREMENT
MAX AK2 SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1 Max AK2 Loops = 999,999
030 AK2 Heading This segment is used to start acknowledgment of a single transaction set.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 143 M 3/3 ID Transaction Set
Identifier Code “xxx” This element will
contain the code value of the ST01 element of the transaction set being acknowledged.
02 329 M 4/9 AN Transaction Set Control Number
“xxxxxxxxx” This element will contain the value of the ST02 element of the transaction set being acknowledged.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 47 Transaction Sets 830 and 997
AK3 (Data Segment Note)
SEGMENT REQUIREMENT
MAX AK3 SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional 1 Max AK3 Loops = 999,999 Max AK2 Loops = 999,999
040 AK3 &
AK2
Heading This segment is used to report errors in a data segment and to identify the location of the data segment.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 721 M 2/3 ID Segment ID Code “xxx” This element will
contain a code identifying the data segment in error.
02 719 M 1/6 N0 Segment Position in Transaction Set
“xxxxxx” This element will contain the numerical count position of this data segment within the transaction set, with count position 1 being the ST segment.
03 447 O 1/4 AN Loop Identifier Code “xxxx” This element will 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.
04 720 O 1/3 ID Segment Syntax Error Code
“xxx” This element will 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 X12 3060 guide for a complete code list.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 48 Transaction Sets 830 and 997
AK4 (Data Element Note)
SEGMENT REQUIREMENT
MAX AK4 SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Optional 99 Max AK3 Loops = 999,999 Max AK2 Loops = 999,999
050 AK3 &
AK2
Heading This segment is used to report errors in a data element and to identify the location of the data element.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 722 M 1/2 N0 Element Position in
Segment “xx” This element will
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.
02 725 O 1/4 N0 Data Element Reference Number
“xxxx” This element will contain the reference number used to locate the data element in the Data Element Dictionary.
03 723 M 1/3 ID Data Element Syntax Error Code
“xxx” This element will contain a code indicating the error found after syntax editing of a data element. See the chapter entitled “Data Element Dictionary” in the ANSI X12 3060 guide for a complete code list.
04 724 O 1/99 AN Copy of Bad Data Element
“xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
xxxx”
This element will contain a copy of the data element in error.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 49 Transaction Sets 830 and 997
AK5 (Transaction Set Response Trailer)
SEGMENT REQUIREMENT
MAX AK5 SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1 Max AK2 Loops = 999,999
060 AK2 Heading This segment is used to acknowledge acceptance or rejection and to report errors in a transaction set.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 717 M 1/1 ID Transaction Set
Acknowledgment Code “x” This element will
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 X12 3060 guide for a complete code list.
02 718 O 1/3 ID Transaction Set Syntax Error Code
“xxx” This element will 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 X12 3060 guide for a complete code list.
03 718 O 1/3 ID Transaction Set Syntax Error Code
“xxx” See Notes/ Comments for element AK502.
04 718 O 1/3 ID Transaction Set Syntax Error Code
“xxx” See Notes/ Comments for element AK502.
05 718 O 1/3 ID Transaction Set Syntax Error Code
“xxx” See Notes/ Comments for element AK502.
06 718 O 1/3 ID Transaction Set Syntax Error Code
“xxx” See Notes/ Comments for element AK502.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 50 Transaction Sets 830 and 997
AK9 (Functional Group Response Trailer)
SEGMENT REQUIREMENT
MAX AK9 SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1
070 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.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 715 M 1/1 ID Functional Group
Acknowledge Code “x” This element will
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 X12 3060 guide for a complete code list.
02 97 M 1/6 N0 Number of Transaction Sets Included
“xxxxxx” This element will contain the total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element.
03 123 M 1/6 N0 Number of Received Transaction Sets
“xxxxxx” This element will contain the number of transaction sets received.
04 2 M 1/6 N0 Number of Accepted Transaction Sets
“xxxxxx” This element will contain the number of accepted transaction sets in a functional group.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 51 Transaction Sets 830 and 997
AK9 (Functional Group Response Trailer)
(continued)
SEGMENT REQUIREMENT
MAX AK9 SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1
070 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.
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 05 716 O 1/3 ID Functional Group
Syntax Error Code “xxx” This element will
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 X12 3060 guide for a complete code list.
06 716 O 1/3 ID Functional Group Syntax Error Code
“xxx” See Notes/ Comments for element AK905.
07 716 O 1/3 ID Functional Group Syntax Error Code
“xxx” See Notes/ Comments for element AK905.
08 716 O 1/3 ID Functional Group Syntax Error Code
“xxx” See Notes/ Comments for element AK905.
09 716 O 1/3 ID Functional Group Syntax Error Code
“xxx” See Notes/ Comments for element AK905.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 52 Transaction Sets 830 and 997
SE (Transaction Set Trailer)
SEGMENT REQUIREMENT
MAX SE SEGMENTS
ALLOWED PER TRANS. SET
POSITION # WITHIN TRANS.
SET
PART
OF LOOP
TRANS.
SET LEVEL
SEGMENT PURPOSE
Mandatory 1
080 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).
b = space C = Conditional M = Mandatory O = Optional x = Alphanumeric character
ELE. SEQ. NO.
ELE. ID
REQ.
MIN/MAX LENGTH
DATA TYPE
DESCRIPTION
FORMAT OR
VALUE
NOTES/
COMMENTS 01 96 M 1/10 N0 Number of Included
Segments “xxxxxxxxxx” This element will
contain the total number of transmitted segments within the transaction set, including the ST and SE segments.
02 329 M 4/9 AN Transaction Set Control Number
“xxxxxxxxx” This number will be the same as the number in the corresponding ST02 element.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 53 Transaction Sets 830 and 997
APPENDIX A
GLOSSARY OF TERMS
AIAG 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.
ANSI ASC X12 American National Standards Institute Accredited Standards
Committee X12. This committee develops and maintains U.S. generic standards for Electronic Data Interchange.
COMPOSITE DATA In the EDI standards, a grouping of related sub-elements, such as the ELEMENT elements that make up a name and address. CONTROL STRUCTURE The beginning and end (header and trailer) segments for entities in
Electronic Data Interchange. DATA ELEMENT 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.
DATA ELEMENT A separating character, such as an asterisk (*), that precedes each DELIMITER data element within a segment. DATA 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.
DUNS NUMBER 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.
EBCDIC Extended Binary Code for Decimal InterChange. EBCDIC is an 8-bit
code used to define character representations for IBM mainframe computers.
EDI 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.
EDI Implementation Guide Key Plastics, Inc. Version 1.0 – June 1,1998
Version 003060AIAG 54 Transaction Sets 830 and 997
APPENDIX A
GLOSSARY OF TERMS (continued)
FUNCTIONAL In X12 standards, a 997 transaction set which a receiver returns to the ACKNOWLEDGMENT sender to indicate that a transmission has been received, that the content of the transmission has been validated with the standard, and the results of that validation. FUNCTIONAL GROUP One or more transaction sets of the same or similar type with a
common send/receive point. INTERCHANGE The exchange of information from one company to another. A set of
transaction sets or messages sent from one sender to one receiver at one time.
LOOP A repetition of a group of segments in a transaction set. OEM Original Equipment Manufacturer. An assembler of automobiles,
trucks, and/or off-road equipment. PARALLEL TEST The process of comparing the output of two processes to determine if
they produce the same result. Specifically, the comparison of an EDI versus a paper process to validate the EDI system.
QUALIFIER A data element that gives a generic segment or a generic data
element a specific meaning. SEGMENT A special character inserted in the segment immediately following the TERMINATOR last data element transmitted, indicating the end of the segment. SUB-ELEMENT A data element that is used as part of a composite data element. TRADING PARTNERS Two companies who agree to trade with each other using EDI. TRANSACTION SET A group of segments, in a predefined sequence, that provides all the
data required to define a complete business transaction. The transaction set is roughly equivalent to a document in a paperwork system, such as a purchase order, an invoice, or a freight bill.
VAN Value Added Network. A network that provides services that go
beyond the pure switching function.