Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment: Level: Loop: Usage: Max Use: Purpose:
830 004010
DATE: PAGE:
10/28/05
1
ISA Interchange Control Header N/A _______ Mandatory 1 per interchange 1 To start and identify an interchange of one or more functional groups and interchangerelated control segments.
Notes:
Data Element Summary
REF. DATA DESC. ELEM
NAME
ISA01
I01
Authorization Information Qualifier
M
ID
ISA02
I02
Authorization Information
M
AN 10/10
Use ten spaces
ISA03
I03
Security Information Qualifier
M
ID
Use "00" for password
ISA04
I04
Security Information
M
AD 10/10
Use ten spaces.
ISA05
I05
Interchange ID Qualifier
M
ID
2/2
Use "01" or other applicable codes.
ISA 06
I06
Interchange Sender ID
M
ID
15/15
DUNS number. Left justify, space fill. DUNS Number
ISA07
I05
Interchange ID Qualifier
M
ID
2/2
Use "01" or other applicable codes.
ISA08
I07
Interchange Receiver ID
M
ID
15/15
DUNS number. Left justify, space fill.
ISA09
I08
Interchange Date
M
DT 6/6
Date of creation
ISA10
I09
Interchange Time
M
TM 4/4
Time of creation
ISA11
I10
Interchange Control Standards Identifier
M
ID
1/1
Use "U" for U.S.
ISA12
I11
Interchange Control Version Number
M
ID
5/5
Use "00400"
ISA13
I12
Interchange Control Number
M
N0
9/9
A number that cannot be repeated within a 1-year period at a time.
ISA14
I13
Acknowledgment Requested
M
ID
1/1
Use "0" for no Ack. Req., use "1" for Ack. Req.
AIAG ATTRIBUTES 2/2
2/2
COMMENTS Use "00"
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
830 004010
DATE: PAGE:
10/28/05
2
Data Element Summary
REF. DATA DESC. ELEM
NAME
AIAG ATTRIBUTES
ISA15
I14
Test Indicator
M
ID
ISA16
I15
Subelement Separator
M
AN 1/1
1/1
COMMENTS Use "T" for test data of "P" for production data.
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment: Level: Loop: Usage: Max Use: Purpose: Notes:
830 004010
DATE: PAGE:
10/28/05
3
GS Functional Group Header N/A as required Mandatory 1 per functional group 1 To indicate the beginning of a functional group and to provide control information. See the ASC X12 segment directory for rules and notes. Strict compliance and agreement on content by trading partners is required. Data Element Summary
REF. DATA DESC. ELEM
NAME
AIAG ATTRIBUTES
GS01
479
Functional Identifier Code
M
ID
2/2
PS
GS02
142
Application Sender’s Code
M
ID
2/15
Use DUNS number.
GS03
124
Application Receiver’s Code
M
ID
2/15
Use DUNS number
GS04
29
Data Interchange Date
M
DT 8/8
Date created
GS05
30
Data Interchange Time
M
TM 4/4
Time created
GS06
28
Data Interchange Control Number
M
N0
1/9
Start with 1 and increment by 1 for each subsequent GS segment.
GS07
455
Responsible Agency Code
M
N0
1/2
Enter "X" for ASC X12 formats
GS08
480
Version/Release/Industry ID Code
M
ID
1/12
Use "004010" for this version/release.
COMMENTS
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment: Level: Loop: Usage: Max Use: Purpose: Notes:
830 004010
DATE: PAGE:
10/28/05
4
GE Functional Group Trailer N/A _______ Mandatory 1 per functional group 1 To indicate the end of a functional group and to provide control information. The data interchange control number (GE02) in this trailer must be identical to the same data element in the associated functional group header (GS06). Data Element Summary
REF. DATA DESC. ELEM
NAME
AIAG ATTRIBUTES
GE01
97
Number of Transaction Sets Included
M
N0
1/6
Total number of ST segments in group
GE02
28
Data Interchange Control Number
M
N0
1/9
Must be identical to the same data element in the associated group header (GS06)
COMMENTS
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment: Level: Loop: Usage: Max Use: Purpose: Notes:
830 004010
DATE: PAGE:
10/28/05
5
IEA Interchange Control Trailer N/A _______ Mandatory 1 per interchange 1 To define the end of an interchange of one or more functional groups and interchange-related control segments. The interchange control number IEA02 in this trailer must match the value in ISA13.
Data Element Summary
REF. DATA DESC. ELEM
NAME
IEA01
I16
Number of Included Functional Groups
M
N0
1/5
Number of GS segments included between ISA and this IEA.
IEA02
I12
Interchange Control Number
M
N0
9/9
Must match ISA13
AIAG ATTRIBUTES
COMMENTS
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
830 004010
DATE: PAGE:
10/28/05
6
PLANNING SCHEDULE WITH RELEASE CAPABILITY TRANSACTION SET (830) Data Segment Sequence for the Heading Area Page Ref. Table 1 8 9 11
Seq. ID ST BFR N1
Name Transaction Set Header Beginning Segment (Planning Schedule) LOOP ID – N1 Name
Req. AIAG
Des US
Max Use
M M
M M
1 1
O
M
1
Loop Repeat
200
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
830 004010
DATE: PAGE:
10/28/05
7
PLANNING SCHEDULE WITH RELEASE CAPABILITY TRANSACTION SET (830) Data Segment Sequence for the Detail Area Page Ref. Table 2
Seq. ID
12 13 14 15 16
LIN UIT PRS ATH FST
17 18
SHP REF
Name LOOP ID – LIN Item Identifier Unit Detail Part Release Status Resource Authorization Forecast Schedule LOOP ID – LIN/SHP Shipped/Received Information Reference Numbers
Req. AIAG
Des US
Max Use
M M O O O
M M O O O
1 1 1 20 260
O O
O O
1 5
Req. AIAG
Des US
M M
M M
Loop Repeat 10000
2
Data Segment Sequence for the Summary Area Page Ref. Table 3 19 20
Seq. ID
Name
CTT SE
Transaction Totals Transaction Set Trailer
Max Use 1 1
Loop Repeat
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment: Level: Loop: Usage: Max Use: Purpose: General Info: Example:
830 004010
DATE: PAGE:
10/28/05
8
ST Transaction Set Header Header ______ Mandatory 1 To indicate the start of a transaction set and to assign a control number. The transaction set control number (ST02) in the header must match the transaction set control number (SE02) in the transaction set trailer (SE). ST*830*0001 N/L
Data Element Summary
REF. DATA DESC. ELEM
NAME
AIAG ATTRIBUTES
ST01
143
Transaction Set ID Code
M
ID
ST02
329
Transaction Set Control Number
M
AN 04/09
03/03
COMMENTS Use "830" A unique control number assigned to each transaction set within a functional group starting with 0001 and incrementing by 1 for each subsequent transaction set.
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
830 004010
Segment: Level: Loop: Usage: Max Use: Purpose: General Info:
Examples:
DATE: PAGE:
10/28/05
9
BFR Beginning Segment Planning Schedule Header ______ Mandatory 1 To indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast; and related forecast envelope dates. The intent of this segment is to provide information for the entire transaction. Some of this information may be overridden by subsequent segments in the transaction. BFR*05*02001**DL*A*20020830*20020914*20020830 N/L
Data Element Summary
REF. DATA DESC. ELEM
NAME
AIAG ATTRIBUTES
BFR01
353
Transaction Set Purpose Code
M
ID
BFR02
127
Release Number
C
AN 01/30
First two characters are the year. The next three characters are an incrementing sequence number.
BFR03
328
Reference Number
O
AN 01/30
Not used
BFR04
675
Schedule Type Qualifier
M
ID
02/02
See note below. "DL"
BFR05
676
Schedule Quantity Qualifier
M
ID
01/01
See note below "A"
BFR06
373
Date
M
DT 08/08
Horizon start date: the date when the forecast horizon (envelope) begins (YYYYMMDD)
BFR07
373
Date
M
DT 08/08
Horizon end date: the date when the forecast horizon (envelope) ends (YYYYMMDD)
BFR08
373
Date
M
DT 08/08
Date forecast generated (YYYYMMDD)
BFR09
373
Date
O
DT 08/08
Not used
BFR10
367
Contract Number
O
AN 01/30
Not used
02/02
COMMENTS "05" = Replace
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment:
BFR
830 004010
DATE: PAGE:
10/28/05
10
Beginning Segment Planning Schedule (Cont'd)
Data Element Summary
REF. DATA DESC. ELEM
NAME
BFR11
P.O. Number
324
AIAG ATTRIBUTES O
AN 01/22
COMMENTS Not used PO# is indicated on LIN segment.
The following codes for element #675 are acceptable: SH = Shipment dates and times are indicated in the FST segments. DL = Delivery dates and times are indicated in the FST segments.
The following codes for element #676 are acceptable: A = C =
Actual discrete (net) quantities are indicated in the FST segments. Cumulative quantities are indicated in the FST segments.
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
830 004010
Segment: Level: Loop: Usage: Max Use: Purpose: General Info:
Examples:
DATE: PAGE:
10/28/05
11
N1 Name Header N1 Repeat: 200 Mandatory 1 To identify a party by type of organization, name and code. This N1 loop in the header area can be used to identify the supplier, and ship to and ship from locations. There will always be at least two iterations of the N1 loop. The ship-to and supplier identification will always be sent. N1*SU**92*123456 N/L N1*ST**92*123456789N/L N1*MI**92*123456789N/L
Data Element Summary
REF. DATA DESC. ELEM
AIAG ATTRIBUTES
NAME
N101
98
Entity Identifier Code
M
ID
N102
93
Name
O
AN 01/35
Not used
N103
66
ID Code Qualifier
C
ID
01/02
"01" = DUNS Number “92” = Assigned by Buyer
N104
67
ID Code
C
ID
02/17
"ST" = Assigned ship-to number "SU" = suppliers assigned Number. “MI” = Material Issuer number if different from “ST”
02/02
COMMENTS "ST" = Ship to location "SU" = Supplier "MI" = Material Issuer
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
830 004010
Segment: Level: Loop: Usage: Max Use: Purpose: General Info: Examples:
DATE: PAGE:
10/28/05
12
LIN Item Identification Detail LIN Repeat: 10,000 Mandatory 1 To specify basic item identification data. Used to identify customer/supplier information. This segment begins the detail loop. LIN**BP*425966C1*PO*P12345 N/L
Data Element Summary
REF. DATA DESC. ELEM
AIAG ATTRIBUTES
NAME
LIN01
350
Assigned Identification
O
AN 01/06
Not used
LIN02
235
Product/Services ID Qualifier
M
ID
The first pair of Product/Service ID Qualifier and Product Service ID (data elements 235 and 234) is used to indicate the Part Number. .
LIN03
234
Product/Service ID
M
AN 01/30
NOTE:
02/02
COMMENTS
Identifying number for product or service
LIN04 thru LIN31 provide 14 additional pairs of Product/Service ID Qualifier (235) Product/Service ID (234).
The following codes for element #235 are acceptable: BP = Buyer's Part Number PO = Purchase Order Number
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment: Level: Loop: Usage: Max Use: Purpose: General Info: Examples:
830 004010
DATE: PAGE:
10/28/05
13
UIT Unit Detail Detail LIN Mandatory 1 To specify item unit data. This is a mandatory segment and indicates the unit of measure for all Quantities relating to the line item UIT*PC N/L
Data Element Summary
REF. DATA DESC. ELEM
NAME
AIAG ATTRIBUTES
UIT01
355
Unit of Measurement Code
M
ID
02/02
See ANSI Acceptable Code list
UIT02
212
Unit Price
O
R
01/14
Not used
UIT03
639
Basis of Unit Price Code
O
ID
02/02
Not used
COMMENTS
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment: Level: Loop: Usage: Max Use: Purpose: General Info: Examples:
830 004010
DATE: PAGE:
10/28/05
14
PRS Part Release Status Detail LIN Optional 1 To indicate the status of the part being ordered of forecast with respect to this material release or planning document. Used to notify of final release. PRS*7 N/L
Data Element Summary
REF. DATA DESC. ELEM
NAME
AIAG ATTRIBUTES
PRS01
682
Part Release Status Code
M
ID
PRS02
352
Description
O
AN 01/80
01/02
COMMENTS "7" = Final Release Not used
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment: Level: Loop: Usage: Max Use: Purpose: General Info: Examples:
830 004010
DATE: PAGE:
10/28/05
15
ATH Resource Authorization Detail LIN Optional 20 To specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule. The quantity fields in this segment are always cumulative quantities (CQ). ATH*FI*20020830*10000**20020101 N/L ATH*MT*20020830*15000**20020101 N/L ATH*PQ*20020830*9000**20020101 N/L
Data Element Summary
REF. DATA DESC. ELEM
NAME
AIAG ATTRIBUTES
ATH01
672
Resource Authorization Code
M
ID
ATH02
373
Date
C
DT 08/08
Resource authorization end date
ATH03
380
Quantity
C
R
01/10
Cumulative Quantity authorized to date
ATH04
380
Quantity
O
R
01/10
Not used
ATH05
373
Date
C
DT 08/08
02/02
COMMENTS See acceptable code list below
Cumulative Start Date
The following codes for element ATH01 are acceptable: FI = Finished (fabrication) MT = Material (raw) PQ = Previous CUM required
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
830 004010
Segment: Level: Loop: Usage: Max Use: Purpose: General Info:
Examples:
DATE: PAGE:
10/28/05
16
FST Forecast Schedule Detail LIN Optional 260 To specify the forecasted dates and quantities. At least one FST loop is required. Although the FST segment allows for time to be specified in addition to date, locations using that level of scheduling will use the shipping schedule transaction set to convey this information. FST*1352*C*D*20020902****RE*0001 N/L FST*15000*D*W*20020910 N/L
Data Element Summary
REF. DATA DESC. ELEM
NAME
AIAG ATTRIBUTES
FST01
380
Quantity
M
R
01/10
Nets only
FST02
680
Forecast Qualifier
M
ID
01/10
"C" = Firm "D" = Planning
FST03
681
Forecast Timing Qualifier
M
ID
01/10
"D" = Discrete "W" = Weekly Bucket
FST04
373
Date
M
DT 08/08
FST04 represents a Discrete Forecast Date or Forecast Bucket
FST05
373
Date
O
DT 08/08
Not used
FST06
374
Date/Time Qualifier
O
ID
03/03
Not used
FST07
337
Time
O
TM 04/04
Not used
FST08
128
Reference Number Qualifier
O
ID
“RE” = Release Number
FST09
127
Reference Number
O
AN 01/30
02/02
COMMENTS
Release Number If release number is sent it will be required on the label and ASN.
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
830 004010
Segment: Level: Loop: Usage: Max Use: Purpose: General Info:
Examples:
DATE: PAGE:
10/28/05
17
SHP Shipped/Received Information Detail LIN/SHP Repeat: 25 Optional 1 To specify shipment and/or receipt information. This segment is used to give information on either the last shipment received/shipped, the Cumulative Quantity (CQ) received/shipped to date, or the CQ rejected the date. SHP*01*200*050*20020525 N/L (last shipment received/shipped) SHP*02*18300*051*20020101**20020830 N/L (Cumulative Qty received YTD)
Received date if SHP03 is "050", otherwise, Cum start date if SHP03 is "051"
SHP05
337
Time
O
TM 04/04
Not used
SHP06
373
Date
C
DT 08/08
Cumulative quantity end date is SHP01 is "02"
SHP07
337
Time
O
TM 04/04
Not used
COMMENTS
The following codes for element #374 are acceptable: 050 = Received Date 051 = Cumulative Quantity Start Date. If SHP01 is "01" then "050" If SHP01 is "02" then "051"
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
830 004010
Segment: Level: Loop: Usage: Max Use: Purpose: General Info: Examples:
DATE: PAGE:
10/28/05
18
REF Reference Numbers Detail LIN/SHP Optional 5 To specify identifying numbers Will be used within the SHP loop to notify last shipment received. REF*SI*SHIPID N/L Data Element Summary
REF. DATA DESC. ELEM
NAME
REF01
128
Reference Number Qualifier
M
ID
REF02
127
Reference Number
M
AN 1/30
Reference Number as qualified by REF01
REF03
352
Description
O
AN 1/80
Not used
AIAG ATTRIBUTES 2/2
COMMENTS SI - Shipper's Identifying Number for Shipment
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment: Level: Loop: Usage: Max Use: Purpose: Example:
830 004010
DATE: PAGE:
10/28/05
19
CTT Transaction Totals Summary ________ Mandatory 1 To transmit a hash total for a specific element in the transaction set. CTT*4 N/L
Data Element Summary
REF. DATA DESC. ELEM
NAME
CTT01
Number of Line Items
354
AIAG ATTRIBUTES M
NO 01/06
COMMENTS Total number of LIN segments
Implementation Guidelines for AIAG EDI Conventions TRANSACTION: VERSION:
Segment: Level: Loop: Usage: Max Use: Purpose: General Info: Example:
830 004010
DATE: PAGE:
10/28/05
20
SE Transaction Set Trailer Summary ________ Mandatory 1 To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments). The transaction set control number value in this trailer (SE02) must match the Same element value in the transaction set header (ST02). SE*18*0001 N/L