X12 830 Planning Schedule
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.
- Segment
- * Element
- > Component
- None included
Interchange Control Header
To start and identify an interchange of zero or more functional groups and interchange-related control segments
Code to identify the type of information in the Authorization Information
- 00
- No Authorization Information Present (No Meaningful Information in I02)
Information used for additional identification or authorization of the interchange sender or the data in the interchange; the type of information is set by the Authorization Information Qualifier (I01)
Code to identify the type of information in the Security Information
- 00
- No Security Information Present (No Meaningful Information in I04)
This is used for identifying the security information about the interchange sender or the data in the interchange; the type of information is set by the Security Information Qualifier (I03)
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the sender for other parties to use as the receiver ID to route data to them; the sender always codes this value in the sender ID element
Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified
Identification code published by the receiver of the data; When sending, it is used by the sender as their sending ID, thus other parties sending to them will use this as a receiving ID to route data to them
Code to identify the agency responsible for the control standard used by the message that is enclosed by the interchange header and trailer
- U
- U.S. EDI Community of ASC X12, TDCC, and UCS
This version number covers the interchange control segments
- 00401
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
A control number assigned by the interchange sender
Code sent by the sender to request an interchange acknowledgment (TA1)
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test, production or information
- I
- Information
- P
- Production Data
- T
- Test Data
Type is not applicable; the component element separator is a delimiter and not a data element; this field provides the delimiter used to separate component data elements within a composite data structure; this value must be different than the data element separator and the segment terminator
- >
- Component Element Separator
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 Capability (830)
Code identifying party sending transmission; codes agreed to by trading partners
Code identifying party receiving transmission. Codes agreed to by trading partners
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59), S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
Assigned number originated and maintained by the sender
Code used in conjunction with Data Element 480 to identify the issuer of the standard
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, subrelease, and industry identifier of the EDI standard being used, including the GS and GE segments; if code in DE455 in GS segment is X, then in DE 480 positions 1-3 are the version number; positions 4-6 are the release and subrelease, level of the version; and positions 7-12 are the industry or trade association identifiers (optionally assigned by user); if code in DE455 in GS segment is T, then other formats are allowed
- 004010
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997
Heading
Transaction Set Header
To indicate the start of a transaction set and to assign a control number
Code uniquely identifying a Transaction Set
- The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set definition (e.g., 810 selects the Invoice Transaction Set).
- 830
- Planning Schedule with Release Capability
Beginning Segment for 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 transaction set
- If BFR01 contains the value "04" (Net Change), BFR09 is required.
- 00
- Original
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BFR02 is the identifying number for a forecast assigned by the orderer/purchaser.
Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast
- BB
- Customer Production (Consumption) Based
Code identifying the type of quantities used when defining a schedule or forecast
- A
- Actual Discrete Quantities
Date expressed as CCYYMMDD
- BFR06 is the forecast horizon start date: The date when the forecast horizon (envelope) begins.
Date expressed as CCYYMMDD
- BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends.
Department Number
To specify identifying information
Two iterations of the REF segment are required; one to specify the vendor number and a second to specify the department number.
The vendor number that will be specified in REF02 (when REF01 contains code IA) must be agreed to by Sears before testing can begin.
Code qualifying the Reference Identification
- DP
- Department Number
Internal Vendor Number
To specify identifying information
Two iterations of the REF segment are required; one to specify the vendor number and a second to specify the department number.
The vendor number that will be specified in REF02 (when REF01 contains code IA) must be agreed to by Sears before testing can begin.
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Name
To identify a party by type of organization, name, and code
Detail
Item Identification
To specify basic item identification data
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- IN
- Buyer's Item Number
Identifying number for a product or service
4 - 5 Sears’ item number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- IZ
- Buyer's Size Code
Unit Detail
To specify item unit data
The unit of measure for all forecast quantities is each.
Product/Item Description
To describe a product or process in coded or free-form format
As predetermined between trading partners, PID05 will provide a forecast ranking for the item/SKU and location referenced in the associated LIN and N1 segments. This ranking is tied to the item/SKU and location, not the forecast quantities for the item/SKU.
The number in the first position (PID05) identifies the ranking (e.g., future forecast, forecast error using standard deviation, etc.) and the alpha character in the second position indicates the inventory stratification for that ranking.
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
The value sent in N104 identifies the reporting location for the item/SKU referenced in the associated LIN segment for which forecast quantities are being sent. This location may be either a Sears’ location or vendor location as predetermined between trading partners.
Location codes must be agreed to by Sears before testing can begin.
If N104 contains code NATL, national level data is being transmitted.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- RL
- Reporting Location
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- 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.
4 - 7 Location code.
Forecast Schedule
To specify the forecasted dates and quantities
- At least one occurrence of segment FST is required, either in the FST loop or within the SDP loop. These two loops are mutually exclusive.
The forecast start date is the Sunday run date. The forecast end date is required for 830 transactions sent to Sears.
The Forecast Quantity Qualifier code in FST02 represents a DRP Order Planning Type within Sears’ DRP application. Some codes are used in transactions Sears receives (inbound) and some codes are used in transactions Sears sends (outbound). E.g., code A (Immediate) may be used on inbound transactions to Sears. Code A is equivalent to the DRP Order Planning Type 3 (quantity available to ship).
Code specifying the sender's confidence level of the forecast data or an action associated with a forecast
- 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.
- A
- Immediate
DRP Order Planning Type/Code = Quantity
Available to Ship (DRP internal code 3) - B
- Pilot/Prevolume
DRP Order Planning Type/Code = Shipment
Forecast Actual (DRP internal code D) - C
- Firm
DRP Order Planning Type/Code = Firm
Production Schedule Quantity (DRP internal
code 1) - D
- Planning
DRP Order Planning Type/Code =
Recommended Order Receipt (DRP internal
code P) - N
- Normal Tooling Capacity
DRP Order Planning Type/Code = Projected
Inventory Needs (DRP internal code Q) - S
- Strike Protection
DRP Order Planning Type/Code = Safety
Stock Build-Up (DRP internal code A) - T
- Required Tooling Capacity
DRP Order Planning Type/Code = Planned
Inventory Needs (DRP internal code R) - Z
- Mutually Defined
DRP Order Planning Type/Code = Customer
Orders (DRP internal code 2)
Code specifying interval grouping of the forecast
- If FST03 equals "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.
- D
- Discrete
Date expressed as CCYYMMDD
Forecast start date
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- 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.
Transaction Set Trailer
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Total number of segments included in a transaction set including ST and SE segments
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
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.