X12 830 Planning Schedule with Release Capability
This Standard 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.
- ~ Segment
- * Element
- > Component
Functional Group Header
To indicate the beginning of a functional group and to provide control information
Code identifying a group of application related Transaction Sets.
- PS
- Planning Schedule with Release Capacity
Code identifying party sending transmission.
Code identifying party receiving transmission.
Date sender generated a functional group of transaction sets.
Time (HHMM) expressed in 24-hour clock time when the sender generated a functional group of transaction sets (local time at sender's location).
(Time range: 0000 through 2359.)
Assigned number originated and maintained by the sender.
Code used in conjunction with the version data element to identify the issuer of the standard.
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
The Version Code is used in conjunction with the Functional Identifier to specify an exact version of an EBDI standard. Format of the version is: Positions Content
1 - 3 Major Version Number
4 - 6 Release Level of Version
7 - 12 Industry or Trade Assoc. ID (Optionally assigned by user)
- 002001FORD
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set.
- 830
- X12.14 Planning Schedule
Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)
Beginning Segment (Planning Schedule)
To indicate the beginning of a planning schedule transaction set; whether a ship or delivery based forecast; and related forecast envelope dates
Code identifying purpose of transmitted set.
00 - first release after annual cumulative reset.
- 00
- Original
- 05
- Replace
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.
Ford Program Number
Code which qualifies the type of dates used in the forecast.
- BB
- Broadcast Based
- DL
- Delivery Based
- SH
- Shipment Based
Code which qualifies the types of quantities.
"C" = cumulative quantitie are indicated in the FST segments EXCEPT when overridden in the FST segment.
- C
- Cumulative Quantities
Date (YYMMDD). Also see: Date Qualifier (432).
Date from which part quantity accumulations begin.
Date (YYMMDD). Also see: Date Qualifier (432).
Horizon End Date - Last Sunday of the Period in the Forecast.
Date (YYMMDD). Also see: Date Qualifier (432).
Release Issue Date.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Reference Numbers
To transmit identifying numbers associated with the named party
Code qualifying the Reference Number.
Release Product Group
- PG
- Product Group
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Name
To identify a party by type of organization, name and code
This N1 loop in the heading area will be used to identify the release issuer (buyer), the seller (supplier) and the bill-to, ship-to and ship-from locations.
Code identifying the type of party being defined.
- BT
- Bill-to-Party
- BY
- Buying Party (Purchaser)
- IC
- Intermediate Consignee
- SE
- Selling Party
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer
Code identifying one of the parties in the transaction. See Identification Code Qualifier (66).
Detail
Item Identification Detail
To specify basic item identification data.
Used for Ford part number. This segment begins the detail loop. Ford part number my consist of a prefix, base, suffix and control code. Any of these, except the base, may or may not be present. The portions of the part are delimited by spaces. In addition, LIN04 and LIN05 may be used to transmit a purchase order number.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- BP
- Buyer's Part Number
Identifying number for a product or service.
Ford Part Number.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- PO
- Purchase Order Number
Identifying number for a product or service.
Ford Purchase Order Number.
Code identifying the basic unit measurement.
Part Release Status
To indicate the status of the part being ordered with respect to this material release (only use if the planning schedule is considered to be an order/material release).
Only used when the part is to be coded "Balanced Out' or "Final Release".
Code identifying the status of the specific part number being released.
- 3
- Part will be Canceled at the Material Quantity
- 7
- Final Release for this Cancelled Part
A free-form description to clarify the related data elements and their content.
Reference Numbers
To transmit identifying numbers associated with the named party
Used to convey the dock code, line feed location or reserve line feed location where the item is to be delivered.
Code qualifying the Reference Number.
- DK
- Dock Number
- LF
- Assembly Line Feed Location
- RL
- Reserve Assembly Line Feed Location
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
This segment relates to interpersonal communications, not network or telecommunications contacts. It can be used to convey a contact person's name and telephone number.
Code identifying the major duty or responsibility of the person or group named.
- EX
- Expeditor
- RD
- Receiving Dock
Free-form organization name, official title, or related information.
Code identifying the type of communications used in Communication Number (364). Also see: Communication Number (364).
- TE
- Telephone
Complete communications number including country or area code when applicable. Also see: Communications Number Qualifier (365).
Ship/Delivery Pattern
To identify specific ship/delivery requirements
Forecast Schedule
To specify the forecasted dates and quantities
This FST segment will show cumulative quantities for all discrete forecast qualifiers ("D"). For strike protection and Kentucky Truck frim orders, the FST segment will show discrete (net) quantities.
When FST02 identifies strike protection ("S") or firm ("C") quantity, the quantities in the FST01 element will be discrete (net) quantities.
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
Normally cumulative quantity. Net only when FST02="S" or "C".
Code specifying the sender's confidence level of the forecast data.
- C
- Firm
- D
- Planning
- S
- Strike Protection
Code specifying interval grouping of the forecast.
- D
- Discrete
- F
- Flexible Interval (from Date X through Date Y)
- W
- Weekly Bucket (Monday through Sunday)
Code specifying type of date or time.
- 002
- Delivery Requested on this Date/Time
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 though 2359).
Also see: Time Qualifier (176).
Resource Authorization
To specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule.
The quantity fields in this segment are always cumulative quantities. There will always be at most one ATHFI and one ATHMT for each LIN.
Code identifying the resource which the buyer is authorizing the seller to commit to.
- FI
- Finished (Labor, Material, and Overhead/Burden)
- MT
- Material
Date (YYMMDD). Also see: Date Qualifier (432).
Last day of the week.
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
Cumulative quantity authorized through date in ATH02.
Date (YYMMDD). Also see: Date Qualifier (432).
Cumulative quantity start date. (Beginning inventory date.)
Shipped/Received Information
To specify shipment and/or receipt information
This is based on ASN information transceived for the last shipment, and the model year cumulative shipped value. The CUM quantity is equal to CUM receipts plus in-transit through last transceived ASN.
Code specifying the type of quantity.
- 01
- Discrete Quantity
- 02
- Cumulative Quantity
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
Code specifying type of date or time.
- 011
- Shipped on this Date/Time
Date (YYMMDD). Also see: Date Qualifier (432).
Shipped date or beginning inventory date.
Date (YYMMDD). Also see: Date Qualifier (432).
If present, will contain date of last shipment.
Reference Numbers
To transmit identifying numbers associated with the named party
Used to convey the shipment ID (ASN) number of the last shipment transceived -as much, it will follow the SHP segment with "01" in SHP01, and will occur only once.
Code qualifying the Reference Number.
- SI
- Shipper's Identifying Number for Shipment (SID)
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning and ending (SE) segment)
Total number of segments included in a transaction set including ST and SE segments.
Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)
Functional Group Trailer
To indicate the end of a functional group and to provide control information
Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element.
Assigned number originated and maintained by the sender.
sample 1
GS~PS~AP10A~BTCXA~231224~0057~000011832~X~002001FORD
ST~830~0001
BFR~05~~924-1~SH~C~230101~241229~231224
REF~PG~RPG04
N1~ST~~92~AP10A
N1~SF~~92~BTCXA
N1~IC~~92~GZ7WL
LIN~~BP~AMPC3J 17B820 AC~PO~5700020090
UNT~EA
PER~EX~JP006 GGOWRIS1@FORD.COM~TE~-313-2065633
SDP~Y~Y
FST~5136~D~W~231225
FST~5280~D~W~240101
FST~5496~D~W~240108
FST~5592~D~W~240115
FST~5784~D~W~240122
FST~6096~D~W~240129
FST~6456~D~W~240205
FST~6744~D~W~240212
FST~6984~D~W~240219
FST~7296~D~W~240226
FST~7704~D~W~240304
FST~8112~D~W~240311
FST~8280~D~W~240318
FST~8544~D~W~240325
FST~8760~D~W~240401
FST~9168~D~W~240408
FST~9456~D~W~240415
FST~9720~D~W~240422
FST~9912~D~W~240429
FST~10272~D~W~240506
FST~10416~D~W~240513
FST~10704~D~W~240520
FST~10992~D~W~240527
FST~11328~D~W~240603
FST~11688~D~W~240610
FST~11688~D~W~240617
FST~11976~D~W~240624
FST~12240~D~W~240701
FST~12552~D~W~240708
FST~12864~D~W~240715
FST~13104~D~W~240722
FST~13488~D~W~240729
FST~13776~D~W~240805
FST~14280~D~W~240812
FST~14472~D~W~240819
FST~14904~D~W~240826
FST~15120~D~W~240902
FST~15360~D~W~240909
FST~15720~D~W~240916
FST~16032~D~W~240923
FST~16320~D~W~240930
FST~16464~D~W~241007
FST~16632~D~W~241014
FST~16872~D~W~241021
FST~17088~D~W~241028
FST~17328~D~W~241104
FST~17417~D~W~241111
FST~17679~D~W~241118
FST~17941~D~W~241125
FST~18203~D~W~241202
FST~18465~D~W~241209
FST~18727~D~W~241216
FST~18989~D~W~241223
ATH~FI~240114~5496~~230101
ATH~MT~240225~6984~~230101
SHP~01~48~011~231220
REF~SI~0007417004
SHP~02~6336~011~230101~~231220
CTT~1~641621
SE~70~0001
GE~1~000011832
IEA~00001~000011832
Stedi is a registered trademark of Stedi, Inc. All names, logos, and brands of third parties listed on this page are trademarks of their respective owners (including “X12”, which is a trademark of X12 Incorporated). Stedi, Inc. and its products and services are not endorsed by, sponsored by, or affiliated with these third parties. Use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.