830 Planning Schedule with Release Capability
830 Planning Schedule with
Release Capability
Version 004010
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
1 / 18
830 Planning Schedule with Release Capability
IMPLEMENTING EDI COMMUNICATIONS
EDI Communications must be accomplished using a Value Added Network (VAN) to provide
storage and retrieval mailbox services. ThyssenKrupp Bilstein of America, referred to as
Bilstein in this document, has selected Sterling Information Broker as its VAN. If your company
uses another VAN, an interconnect will be established with your VAN. The VAN cost will be
split. The supplier pays sending charges, and Bilstein pays receiving charges.
IMPLEMENTATION PROCESS
1) If you do not have a VAN, you may contact Sterling Information Broker at 1-877-432-4300.
2) Define a Trading Partner Relationship that relates your company to Bilstein.
Pertinent data:
1. ISA Sender Qualifier is 01.
2. ISA Sender ID is 874376676, Production System.
3. ISA Sender ID is 874376676T, Test System.
3) Send an email to EDI_BIA@ThyssenKrupp.com when you are ready for a test file. All EDI
questions should be sent to this email address.
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
2 / 18
830 Planning Schedule with Release Capability
Functional Group ID=
PS
Introduction:
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.
Heading:
Pos.
No.
010
020
Seg.
ID
ST
BFR
Pos.
No.
Seg.
ID
M
M
Must Use
010
020
230
Must Use
M
M
Name
Transaction Set Header
Beginning Segment for Planning Schedule
Req.
Des.
M
M
Max.Use
Loop
Repeat
Notes and
Comments
Loop
Repeat
10000
Notes and
Comments
1
1
Detail:
Req.
Des.
LIN
UIT
ATH
Name
LOOP ID - LIN
Item Identification
Unit Detail
Resource Authorization
Max.Use
M
M
O
1
1
20
210
N1
LOOP ID - N1
Name
O
1
Must Use
Must Use
290
300
SDP
FST
LOOP ID - SDP
Ship/Delivery Pattern
Forecast Schedule
O
O
1
260
Must Use
330
SHP
LOOP ID - SHP
Shipped/Received Information
O
1
M
340
REF
O
200
200
260
25
Summary:
M
M
Pos.
No.
010
020
Seg.
ID
CTT
SE
Name
Transaction Totals
Transaction Set Trailer
Req.
Des.
M
M
Loop
Repeat
Max.Use
1
1
Notes and
Comments
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.
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
3 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
M
M
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 intended for use by the translation
routines of the interchange partners to select the appropriate transaction set
definition (e.g., 810 selects the invoice transaction set).
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
ST01
143
Transaction Set Identifier Code
M ID 3/3
Code uniquely identifying a Transaction Set
830
X12.14 Planning Schedule
ST02
329
Transaction Set Control Number
M AN 4/9
Identifying control number assigned by the originator for a transaction set.
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
4 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
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
2
3
4
5
M
X
>>
M
M
M
M
M
If BFR01 equals "04" (Net Change) - BFR09 is required.
BFR02 is the identifying number for a forecast assigned by the
orderer/purchaser.
BFR06 - Forecast Horizon Start Date: The date when the forecast horizon
(envelope) begins.
BFR07 - Forecast Horizon End Date: The date when the forecast horizon
(envelope) ends.
BFR08 - Date Forecast Generated: The date the forecast data was generated.
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
BFR01
353
Transaction Set Purpose Code
M ID 2/2
Code identifying purpose of transaction set
Replace
05
Reference Number
C AN 1/30
BFR02
127
Reference number or identification number as defined for a particular Transaction Set,
or as specified by the Reference Number Qualifier.
Release Number
C AN 1/30
BFR03
328
Number identifying a release against a Purchase Order previously placed by the parties
involved in the transaction
Schedule Type Qualifier
M ID 2/2
BFR04
675
Code identifying the type of dates used when defining a shipping or delivery time in a
schedule or forecast
DL
Delivery Based
Schedule Quantity Qualifier
M ID 1/1
BFR05
676
Code identifying the type of quantities used when defining a schedule or forecast
A
Actual Discrete Quantities
BFR06
373
Horizon Start Date
M DT 8/8
Date (CCYYMMDD)
BFR07
373
Horizon End Date
M DT 8/8
Date (CCYYMMDD)
BFR08
373
Creation Date
M DT 8/8
Date (CCYYMMDD)
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
5 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
LIN
Item Identification
010
LIN
Mandatory
Detail
Mandatory
1
To specify basic item identification data
1 If LIN04 is present, then LIN05 is required.
2 If LIN06 is present, then LIN07 is required.
1
2
3
See the Data Dictionary for a complete list of ID's.
LIN01 is the line item identification
LIN02 through LIN31 provide for fifteen (15) different product/service ID's for
each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model
No., SKU.
Data Element Summary
Data
Element
Name
X
Ref.
Des.
Attributes
LIN01
M
LIN02
235
M
LIN03
234
M
LIN04
235
M
LIN05
234
M
LIN06
235
M
LIN07
234
350
Assigned Identification
O AN 1/6
Alphanumeric characters assigned for differentiation within a transaction set
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
Bilstein’s Part Number
M AN 1/30
Identifying number for a product or service
Product/Service ID Qualifier
O ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID
(234)
PO
Purchase Order Number
Bilstein's P.O. Number
C AN 1/30
Identifying number for a product or service
Product/Service ID Qualifier
O ID 2/2
Code identifying the type/source of the descriptive number used in Product/Service ID
(234)
Purchaser's Order Line Number
PL
P.O. Line Number for Bilstein's P.O. Number
C AN 1/30
Identifying number for a product or service
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
6 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
M
UIT
Unit Detail
020
LIN
Mandatory
Detail
Mandatory
1
To specify item unit data
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
UIT01
355
Unit or Basis for Measurement Code
Code identifying the basic unit of measurement.
KG
Kilogram
Pound
LB
PC
Piece
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
M
ID 2/2
7 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
ATH
Resource Authorization
320
LIN
Mandatory
Detail
Optional (Must Use)
20
To specify resource authorizations (i.e., finished labor, material, etc.) in the planning
schedule
1 At least one of ATH02 or ATH03 is required.
2 If ATH03 is present, then ATH05 is required.
3 If ATH04 is present, then ATH05 is required.
1
2
3
4
5
M
>>
>>
X
>>
It is imperative that negotiations defining financial commitment have previously
occurred and are agreed to by both buyer and seller.
ATH02 - Resource Authorization Thru-Date: The date through which the buyer
authorizes the seller to commit the resource defined in element ATH01.
ATH03 - Current Cumulative Requirements Quantity: The cumulative quantity
that has been authorized to-date from the cumulative start-date (ATH05)
through the resource authorization thru-date (ATH02).
ATH04 - Maximum Cumulative Requirements Quantity: The maximum
cumulative quantity that has been authorized to-date from the cumulative startdate (ATH05) through the resource authorization thru-date (ATH02). This is a
high water mark. If the forecast decreases, the current cumulative requirements
quantity also decreases, but the maximum cumulative requirements quantity
does not decrease.
ATH05 - Cumulative Start-Date: The date where the cumulative quantity count
starts. This date might be the start-date of a contract period, a calendar or fiscal
year, or other.
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
ATH01
672
Resource Authorization Code
M ID 2/2
Code identifying the resource which the buyer is authorizing the seller to commit to
PQ
Cumulative Quantity Required Prior to First Schedule Period
ATH02
373
Date
C DT 8/8
Date (CCYYMMDD)
Last Receipt Date (PQ)
ATH03
380
Quantity
C R 1/10
Numeric value of quantity
Cumulative Quantity (PQ)
ATH04
380
Quantity
O R 1/10
Numeric value of quantity
ATH05
373
Cumulative Period Start Date
C DT 8/8
Date (CCYYMMDD)
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
8 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
N1
Name
210
Optional (Must Use)
N1
Detail
Optional (Must Use)
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.
Semantic Notes:
Comments: 1
M
X
>>
>>
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.
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
N101
98
Entity Identifier Code
M ID 2/2
Code identifying an organizational entity or a physical location.
SF
Ship From
Ship To
ST
N102
93
Name
C AN 1/35
Free-form name
Identification Code Qualifier
C ID 1/2
N103
66
Code designating the system/method of code structure used for Identification Code (67)
Dun and Bradstreet (Credit Reporting) (DUNS)
01
Identification Code
C ID 2/17
N104
67
Code identifying a party.
DUNS number of the plant receiving material.
ThyssenKrupp Bilstein of America
874376676 – Hamilton, OH USA
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
9 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
M
M
SDP
Ship/Delivery Pattern
290
Optional (Must Use)
SDP
Detail
Optional (Must Use)
1
To identify specific ship/delivery requirements
1
The intent of this segment is to define the routine ship or delivery patterns, as
required, when order quantities are in "buckets", such as weekly, monthly.
Ship/delivery patterns eliminate the need to transmit discrete quantities and
dates for each required shipment or delivery. It is assumed that a "bucketed"
quantity is to be divided equally by the ship/delivery pattern. For example, a
weekly quantity of 100 with a delivery pattern of Monday and Wednesday would
result in 50 to be delivered on Monday and 50 to be delivered on Wednesday.
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
SDP01
678
Ship/Delivery or Calendar Pattern Code
M ID 1/2
Code which specifies the days for routine shipments or deliveries.
None (Also Used to Cancel or Override a Previous Pattern)
Y
Ship/Delivery Pattern Time Code
M ID 1/1
SDP02
679
Code which specifies the time for routine shipments or deliveries
Y
None (Also Used to Cancel or Override a Previous Pattern)
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
10 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
FST
Forecast Schedule
300
Optional (Must Use)
SDP
Detail
Optional (Must Use)
260
To specify the forecasted dates and quantities
1
2
M
M
M
M
As qualified by FST02 and FST03, FST04 represents either a discrete forecast
date, the first date of a forecasted bucket (weekly, monthly, quarterly, etc.) or
the start date of a flexible interval.
If FST03 - "F" (indicating flexible interval), then FST04 and FST05 are required.
FST04 would be used for the start date of the flexible interval and FST05 would
be used for the end date of the flexible interval.
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
FST01
380
Quantity
Numeric value of quantity
FST02
680
Forecast Qualifier
Code specifying the sender's confidence level of the forecast data.
C
Firm
D
Planning
Forecast Timing Qualifier
FST03
681
Code specifying interval grouping of the forecast
D
Discrete
Delivery Date
FST04
373
Date (CCYYMMDD)
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
M
R 1/10
M
ID 1/1
M
ID 1/1
M
DT 8/8
11 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
ATH
Resource Authorization
320
LIN
Mandatory
Detail
Optional (Must Use)
20
To specify resource authorizations (i.e., finished labor, material, etc.) in the planning
schedule
1 At least one of ATH02 or ATH03 is required.
2 If ATH03 is present, then ATH05 is required.
3 If ATH04 is present, then ATH05 is required.
1
2
3
4
5
M
>>
>>
X
>>
It is imperative that negotiations defining financial commitment have previously
occurred and are agreed to by both buyer and seller.
ATH02 - Resource Authorization Thru-Date: The date through which the buyer
authorizes the seller to commit the resource defined in element ATH01.
ATH03 - Current Cumulative Requirements Quantity: The cumulative quantity
that has been authorized to-date from the cumulative start-date (ATH05)
through the resource authorization thru-date (ATH02).
ATH04 - Maximum Cumulative Requirements Quantity: The maximum
cumulative quantity that has been authorized to-date from the cumulative startdate (ATH05) through the resource authorization thru-date (ATH02). This is a
high water mark. If the forecast decreases, the current cumulative requirements
quantity also decreases, but the maximum cumulative requirements quantity
does not decrease.
ATH05 - Cumulative Start-Date: The date where the cumulative quantity count
starts. This date might be the start-date of a contract period, a calendar or fiscal
year, or other.
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
ATH01
672
Resource Authorization Code
M ID 2/2
Code identifying the resource which the buyer is authorizing the seller to commit to
PQ
Cumulative Quantity Required Prior to First Schedule Period
ATH02
373
Date
C DT 8/8
Date (CCYYMMDD)
Last Receipt Date (PQ)
ATH03
380
Quantity
C R 1/10
Numeric value of quantity
Cumulative Quantity (PQ)
ATH04
380
Quantity
O R 1/10
Numeric value of quantity
ATH05
373
Cumulative Period Start Date
C DT 8/8
Date (CCYYMMDD)
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
12 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
SHP
Shipped/Received Information
330
Optional (Must Use)
SHP
Detail
Mandatory
1
To specify shipment and/or receipt information
1 If SHP01 is present, then SHP02 is required.
2 If SHP03 is present, then SHP04 is required.
1
2
3
4
>>
>>
M
>>
X
>>
The SHP segment is used to communicate shipment, delivery, or receipt
information and may include discrete or cumulative quantities, dates, and times.
If SHP01 = "02", "07", "08", "09", or "10" (indicating cumulative quantities), then
SHP04 and SHP06 are required to identify the start and end dates of the
quantity count.
SHP04 - The date shipped, delivered, received, or the cumulative quantity start
date (as qualified by SHP03).
SHP06 - The cumulative quantity end date.
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
SHP01
673
Quantity Qualifier
O ID 2/2
Code specifying the type of quantity
Discrete Quantity
01
02
Cumulative Quantity
SHP02
380
Quantity
C R 1/10
Numeric value of quantity
Cumulative quantity of the last shipment received.
Date/Time Qualifier
M ID 3/3
SHP03
374
Code specifying type of date or time, or both date and time
050
Received
Start Receipt Date
C DT 8/8
SHP04
373
Date (CCYYMMDD)
SHP05
337
Time
O TM 4/8
Time expressed in 24-hour clock time (HHMMSS) (Time range: 000000 through
235959)
End Receipt Date
C DT 8/8
SHP06
373
Date (CCYYMMDD)
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
13 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
REF
Reference Identification
180
CLD
Optional
Detail
Optional
200
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.
Semantic Notes:
Comments:
M
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
REF01
128
Reference Identification Qualifier
M ID 2/3
Code qualifying the Reference Identification
Shipper’s Identifying Number for Shipment
SI
Reference Identification
X AN 1/30
REF02
127
Reference information as defined for a particular Transaction Set or as specified by the
Reference Identification Qualifier
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
14 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
CTT Transaction Totals
010
Summary
Mandatory
1
To transmit a hash total for a specific element in the transaction set
1 If CTT03 is present, then CTT04 is required.
2 If CTT05 is present, then CTT06 is required.
Semantic Notes:
Comments: 1
M
This segment is intended to provide hash totals to validate transaction
completeness and correctness.
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
CTT01
354
Number of Line Items
Total number of line items in the transaction set
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
M
N0 1/6
15 / 18
830 Planning Schedule with Release Capability
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
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).
Syntax Notes:
Semantic Notes:
Comments: 1
M
M
SE is the last segment of each transaction set.
Data Element Summary
Ref.
Data
Des.
Element
Name
Attributes
SE01
96
Number of Included Segments
M N0 1/6
Total number of segments included in a transaction set including ST and SE segments
Transaction Set Control Number
M AN 4/9
SE02
329
Identifying control number assigned by the originator for a transaction set.
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
16 / 18
830 Planning Schedule with Release Capability
1 Sample Data
ST*830*0230
BFR*05**20*DL*A*20080107*20081110*20080107
LIN**BP*E4-FT6-Z030A01*PO*5500001689*PL*00010
UIT*PC
ATH*PQ*20080107*13800**20071201
N1*SF**1*123456789
N1*ST**1*874376676
SDP*Y*Y
FST*2100*C*D*20080107
FST*1500*D*D*20080114
FST*2700*D*D*20080122
FST*600*D*D*20080122
FST*2400*D*D*20080128
FST*2400*D*D*20080204
FST*2700*D*D*20080211
FST*1200*D*D*20080218
FST*2700*D*D*20080225
FST*3300*D*D*20080303
FST*3600*D*D*20080310
FST*3900*D*D*20080317
FST*3600*D*D*20080324
FST*3600*D*D*20080331
FST*3300*D*D*20080407
FST*3000*D*D*20080414
FST*3900*D*D*20080421
FST*3300*D*D*20080428
FST*2700*D*D*20080505
FST*900*D*D*20080512
FST*300*D*D*20080527
FST*1800*D*D*20080602
FST*2100*D*D*20080609
FST*2100*D*D*20080616
FST*300*D*D*20080623
FST*1500*D*D*20080630
FST*2700*D*D*20080707
FST*1800*D*D*20080714
FST*2400*D*D*20080721
FST*2400*D*D*20080728
FST*2100*D*D*20080804
FST*2400*D*D*20080811
FST*3600*D*D*20080818
FST*2400*D*D*20080902
FST*2700*D*D*20080908
FST*1200*D*D*20080915
FST*300*D*D*20080929
FST*300*D*D*20081110
ThyssenKrupp Bilstein of America, Hamilton
830 (004010)
17 / 18
830 Planning Schedule with Release Capability
SHP*02*13800*050*20071227**20071201
SHP*01*1500*050*20071227
REF*SI*043935-06
CTT*1
SE*32*0230
ThyssenKrupp Bilstein of America, Hamilton
830 {004010)
18/ 18