EDI IMPLEMENTATION GUIDE
830 ANSI X12 V4010
Planning Schedule with
Release Capability
Vendor EDI Specifications v1.01
1
ANSI X12 version 4010
830 Planning Schedule with Release Capability
PS
Functional Group ID=
Introduction:
This Draft Standard for Trial Use contains the format and establishes the data contents of the Planning Schedule
with Release Capability Transaction Set (830) for use within the context of an Electronic Data Interchange (EDI)
environment. The transaction set can be used to provide 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.
ANSI standards and AIAG guidelines list many optional segments and elements in the v4010 830. Segments and
elements not listed below will not be used by TI Automotive. The supplier’s software must be able to process all
segments and elements listed. The left-hand column provides information on TI Automotive’s normal usage.
“Always” means that the segment or element will always be sent by TI Automotive. ”Optional” indicates that this
segment is usually sent. “
Heading:
TI AUTO
Usage
Pos
No.
010
Seg.
ID
ST
Name
Transaction Set Header
AIAG
Usage
M
Always
020
BFR
Beginning Segment for Planning Schedule
M
Loop
Notes and
Max.UseRepeat Comments
Always
1
1
LOOP ID - N1
Always
230
N1
TI AUTO
Usage
Pos.
No.
Seg.
ID
Always
010
LIN
Item Identification
Optional
410
FST
Forecast Schedule
Optional
470
SHP
Optional
480
REF
200
Name
O
1
Detail:
AIAG
Usage
Name
LOOP ID – LIN
Loop
Repeat
>1
Max.Use
M
1
O
1
Shipped/Received Information
O
1
Reference Identification
O
5
LOOP ID – LIN/FST
Notes and
Comments
>1
LOOP ID – LIN/SHP
25
Summary:
Always
010
CTT
Transaction Totals
O
1
Always
020
SE
Transaction Set Trailer
M
1
n1
Transaction Set Notes
1.
Number of line items (CTT01) is the accumulation of the number of LIN segments. If used, hash total
(CTT02) is the sum of the values of the quantities (FST01) for each FST segment.
Vendor EDI Specifications v1.01
2
ANSI X12 version 4010
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
ST Transaction Set Header
010
Heading
Mandatory
1
To indicate the start of a transaction set and to assign a control number
1
The transaction set identifier (ST01) is used by the translation routines of the
interchange partners to select the appropriate transaction set definition (e.g., 810
selects the Invoice Transaction Set).
Comments:
TI AUTO
Usage
Always
Ref.
Des.
ST01
Always
ST02
Data Element Summary
Data
Element Name
Attributes
143
Transaction Set Identifier Code
M ID 3/3
Code uniquely identifying a Transaction Set
830
Planning Schedule with Release Capability
329
Transaction Set Control Number
M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
Vendor EDI Specifications v1.01
3
ANSI X12 version 4010
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
BFR Beginning Segment for Planning Schedule
020
Heading
Mandatory
1
To indicate the beginning of a planning schedule transaction set; whether a ship or
delivery based forecast; and related forecast envelope dates
1 At least one of BFR02 or BFR03 is required.
1 BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.
2 BFR06 is the forecast horizon start date: The date when the forecast horizon
(envelope) begins.
3 BFR07 is not used by TI Automotive.
4
5
6
TI Auto
Usage
Always
Ref.
Des.
BFR01
Always
BFR02
Always
BFR03
Always
BFR04
Always
BFR05
Always
BFR06
Always
BFR08
BFR08 is the date forecast generated: The date the forecast data was generated.
BFR09 is not used by TI Automotive.
BFR11 is not used by TI Automotive.
Data Element Summary
Data
Element Name
Attributes
353
Transaction Set Purpose Code
M ID 2/2
Code identifying purpose of transaction set
04
Change
05
Replace
127
Reference Identification
X AN 1/30
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
328
Release Number
X AN 1/30
Number identifying a release against a Purchase Order previously placed by
the parties involved in the transaction
675
Schedule Type Qualifier
M ID 2/2
Code identifying the type of dates used when defining a shipping or delivery
time in a schedule or forecast
DL
Delivery Based
676
Schedule Quantity Qualifier
M ID 1/1
Code identifying the type of quantities used when defining a schedule or
forecast
A
Actual Discrete Quantities
373
Forecast Horizon Start Date
M DT 8/8
Date expressed as CCYYMMDD
373
Vendor EDI Specifications v1.01
Generation Date
Date expressed as CCYYMMDD
4
M
DT 8/8
ANSI X12 version 4010
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
N1 Name
230
N1
Optional
Heading
Optional
1
To identify a party by type of organization, name, and code
1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
1
2
TI Auto
Usage
Always
Ref.
Des.
N101
Always
Always
Always
N102
Always
N103
Always
N104
This segment, used alone, provides the most efficient method of providing
organizational identification. To obtain this efficiency the "ID Code" (N104) must
provide a key to the table maintained by the transaction processing party.
The N1*ST will be used at either the header level or at the detail level, but never at
both levels. If all parts in a transaction set have the same ship to destination, the
header level N1*ST will be used. If parts have different destinations, the detail level
segment will be used within every LIN loop.
Data Element Summary
Data
Element Name
Attributes
98
Entity Identifier Code
M ID 2/3
Code identifying an organizational entity, a physical location, property or an
individual
ST
Ship To
SF
Supplier/Manufacturer
93
Name
X AN 1/60
Free-form name
66
Identification Code Qualifier
X ID 1/2
Code designating the system/method of code structure used for Identification
Code (67)
92
Assigned by buyer or buyer’s agent
67
Identification Code
X AN 2/80
Code identifying a party or other code
Suppress internal dashes and spaces.
Vendor EDI Specifications v1.01
5
ANSI X12 version 4010
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
TI Auto
Usage
Always
Ref.
Des.
LIN02
Always
LIN03
Always
LIN04
Always
LIN05
LIN Item Identification
010
LIN
Mandatory
Detail
Mandatory
1
To specify basic item identification data
1 If either LIN04 or LIN05 is present, then the other is required.
1
LIN01 is the line item identification
Data Element Summary
Data
Element Name
Attributes
235
Product/Service ID Qualifier
M ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
BP
Buyer's Part Number
234
Product/Service ID
M AN 1/48
Identifying number for a product or service
235
X ID 2/2
Product/Service ID Qualifier
Code identifying the type/source of the descriptive number used in
Product/Service ID (234)
PO
Purchase Order Number
234
Product/Service ID
X AN 1/48
Identifying number for a product or service
Vendor EDI Specifications v1.01
6
ANSI X12 version 4010
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Comments:
TI Auto
Usage
Always
Ref.
Des.
FST01
Always
FST02
Always
FST03
Always
FST04
FST Forecast Schedule
460
LIN/FST
Optional
Detail
Optional
260
To specify the forecasted dates and quantities
1 As qualified by FST02 and FST03, FST04 represents either a discrete forecast date,
or the first date of a forecasted bucket (weekly, monthly)
Data Element Summary
Data
Element Name
Attributes
380
Quantity
M R 1/15
Numeric value of quantity
680
Forecast Qualifier
M ID 1/1
Code specifying the sender's confidence level of the forecast data or an action
associated with a forecast
C
Firm
D
Planning
681
Forecast Timing Qualifier
M ID 1/1
Code specifying interval grouping of the forecast
D
Discrete
373
Vendor EDI Specifications v1.01
M
Monthly Bucket (Calendar Months)
W
Weekly Bucket
Forecast Begin Date
Date expressed as YYMMDD
7
M DT 8/8
ANSI X12 version 4010
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Always
Ref.
Des.
SHP01
Always
SHP02
Always
SHP03
Always
SHP04
SHP Shipped/Received Information
470
LIN/SHP
Optional
Detail
Optional
1
To specify shipment and/or receipt information
1 If SHP01 is present, then SHP02 is required.
2 If SHP03 is present, then at least one of SHP04 or SHP05 is required.
3 If SHP04 is present, then SHP03 is required.
1 SHP04 is the date shipped, delivered, received, or the cumulative quantity start date
(as qualified by SHP03).
1 The SHP segment is used to communicate shipment, delivery, or receipt information
and may include discrete or cumulative quantities, dates, and times.
Data Element Summary
Data
Element Name
673
Quantity Qualifier
Code specifying the type of quantity
01
Discrete Quantity
02
Cumulative Quantity
380
Quantity
Numeric value of quantity
374
Date/Time Qualifier
Code specifying type of date or time, or both date and time
050
Received
373
Vendor EDI Specifications v1.01
Date
Date expressed as CCYYMMDD
8
Attributes
O ID 2/2
X
R 1/15
X
ID 3/3
X
DT 8/8
ANSI X12 version 4010
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Always
Ref.
Des.
REF01
Always
REF02
REF Reference Identification
480
SHP
Optional
Detail
Optional
5
To specify identifying information
1 At least one of REF02 or REF03 is required.
2 If either C04003 or C04004 is present, then the other is required.
3 If either C04005 or C04006 is present, then the other is required.
1 REF04 contains data relating to the value cited in REF02.
Data Element Summary
Data
Element Name
Attributes
128
Reference Identification Qualifier
M ID 2/3
Code qualifying the Reference Identification
SI
Shipper's Identifying Number for Shipment (SID)
A unique number (to the shipper) assigned by the
shipper to identify the shipment
127
Reference Identification
X AN 1/30
Reference information as defined for a particular Transaction Set or as
specified by the Reference Identification Qualifier
Vendor EDI Specifications v1.01
9
ANSI X12 version 4010
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Comments:
Always
Ref.
Des.
CTT01
CTT Transaction Totals
010
Summary
Optional
1
To transmit a hash total for a specific element in the transaction set
1
This segment is intended to provide hash totals to validate transaction completeness
and correctness.
Data Element Summary
Data
Element Name
354
Number of Line Items
Total number of line items in the transaction set
Total number of LIN segments
Vendor EDI Specifications v1.01
10
Attributes
M N0 1/6
ANSI X12 version 4010
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Always
Ref.
Des.
SE01
> Always
SE02
SE Transaction Set Trailer
020
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)
1
SE is the last segment of each transaction set.
Data Element Summary
Data
Element Name
Attributes
96
Number of Included Segments
M N0 1/10
Total number of segments included in a transaction set including ST and SE
segments
329
Transaction Set Control Number
M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
Vendor EDI Specifications v1.01
11
ANSI X12 version 4010
Sample 830
ISA*00* *00* *ZZ*OTIGROUPIN05 *ZZ*609623566SAP
*111222*1900*U*00401*000000024*1*P*:
GS*PS*OTIGROUPIN05*609623566SAP*20111222*1900*24*X*004010
ST*830*0001
BFR*05**24*DL*A*20111222**20111222
N1*ST**92*3420
N1*SF**92*7250317
LIN**BP*EU000215AAF00*PO*00303959
SHP*01*-550*050
SHP*02*0*050
REF*SI*SUPPLIER CODE#2
LIN**BP*EU000215ABF00*PO*00303935
FST*240*C*D*20111228
FST*280*C*D*20120104
FST*120*D*D*20120213
FST*240*D*D*20120227
FST*200*D*D*20120305
FST*200*D*D*20120312
FST*200*D*D*20120319
FST*280*D*W*20120326
FST*240*D*W*20120402
FST*280*D*W*20120409
FST*280*D*W*20120416
FST*320*D*W*20120423
FST*360*D*W*20120430
FST*240*D*W*20120507
FST*920*D*W*20120514
FST*800*D*W*20120528
FST*12000*D*M*20120529
SHP*01*40*050
SHP*02*28480*050
REF*SI*27030156
LIN**BP*EU001057AAF00*PO*00304240
FST*760*C*D*20111228
FST*760*C*D*20120104
FST*400*C*D*20120111
FST*240*D*D*20120116
FST*560*D*D*20120118
FST*600*D*D*20120123
FST*560*D*D*20120130
FST*600*D*D*20120206
FST*600*D*D*20120213
FST*760*D*D*20120220
FST*1120*D*D*20120227
FST*1120*D*D*20120305
FST*1160*D*D*20120312
FST*1040*D*D*20120319
FST*880*D*W*20120326
FST*1080*D*W*20120402
FST*1080*D*W*20120409
FST*1080*D*W*20120416
FST*1120*D*W*20120423
FST*1080*D*W*20120430
FST*1080*D*W*20120507
FST*1520*D*W*20120514
FST*400*D*W*20120528
FST*960*D*M*20120529
SHP*01*40*050
SHP*02*1180*050
REF*SI*27066757
CTT*3
SE*59*0001
GE*1*24
IEA*1*000000024
Vendor EDI Specifications v1.01
12
ANSI X12 version 4010