X12 830 Planning Schedule with Release Capability
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
- 00400
- Standard Issued as ANSI X12.5-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.
- C
- D
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
- 001
Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast
- DL
- Delivery 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.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- This Segment Is Not Used By TMMK
- Will Only Send Code MI
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- 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. - N105 and N106 further define the type of entity in N101.
- SU
- Supplier/Manufacturer
Free-form name
- This Segment Is Not Used By TMMK
- Will Only Send Code MI
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Detail
Item Identification
To specify basic item identification data
Alphanumeric characters assigned for differentiation within a transaction set
- LIN01 is the line item identification
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.
- BP
- Buyer's Part Number
Identifying number for a product or service
The LIN03 Element As Found Here Will Be Used In The PRF01 Element of The 856 Transaction.
The First 8 Bytes Of The LIN03 Will Be Used In The REF02 Element Of The
810 Transaction.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Not Sent For TMMNA Export Parts
- RC
- Returnable Container Number
Identifying number for a product or service
Not Sent For TMMNA Export Parts
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ZZ
- Mutually Defined
Product/Item Description
To describe a product or process in coded or free-form format
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.
This Segment Is Not Used By TMMK.
- F
- Free-form
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Part Release Status
To indicate the status of the part being ordered or forecast with respect to this material release or planning document
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
IF REF-01 = DK:
- This Segment Is Not Sent For TMMNA Export Parts
- The Dock Code Will Be Used In the IT111 Element Of The 810
Transaction.
IF REF-01 = LU:
- This Segment Is Not Sent For TMMNA Export Parts
or TMMK.
IF REF-01 = MR:
- This Segment Is Not Sent For TMMNA Export Parts Or TMMK
- DK
- Dock Number
- LU
- Location Number
- MR
- Merchandise Type Code
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
IF REF-01 = MR:
Toyota Card Code.
The REF02 Element Will Be Used In The IT101 Element Of The 810
Transaction.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
This Segment Is Not Sent for TMMNA Export Parts.
- SC
- Schedule Contact
Code identifying the type of communication number
- TE
- Telephone
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Code describing the relationship of a carrier to a specific shipment movement
- Not Sent For Parts And Components.
This Segment Will Only Appear If There Is A Sub-Route.
This Segment Is Not Used By TMMK - Not Sent For TMMNA Export Parts
- 1
- 1st Carrier after Origin Carrier
Code designating the system/method of code structure used for Identification Code (67)
- When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence, specified by the party identified in TD502.
Code specifying the method or type of transportation for the shipment
- ZZ
- Mutually defined
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction
Code identifying type of location
Not Sent For TMMNA Export Parts.
This Segment Is Optional. It Will Only Appear If There Is A
Sub-Route.
- DE
- Destination (Shipping)
- IT
- Intermediate FOB Point
Ship/Delivery Pattern
To identify specific ship/delivery requirements
Code which specifies the routine shipments, deliveries, or calendar pattern
This Segment Is Not Sent For TMMNA Export Parts.
- N
- As Directed
Forecast Schedule
To specify the forecasted dates and quantities
Numeric value of quantity
BUILD OUT Quantities Will Always Be In The FST Segment Between The FIRM And FORECAST Segments For A Part Number.
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.
- C
- Firm
- D
- Pre-Notice OR Build Out
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.
- The Only Codes That Will Be Sent Are:
D - “DAILY”
W - “WEEKLY”
F - “BUILD OUT”
- D
- Daily
- F
- Build Out
- W
- Weekly
Date expressed as CCYYMMDD
FST05 Date Value Descriptions:
If FST02 is “FIRM” Then This Date Represents "Will Be Blank"
If FST02 is “PRE-NOTICE” Then This Date Represents "Last Workday Of Week"
If FST02 is “BUILD OUT” Then This Date Represents "Will Be Value 19910816"
If FST02 is “TMMNA EXPORT PARTS” Then This Date Represents "Due Date"
Code specifying type of date or time, or both date and time
- FST06 qualifies the time in FST07. The purpose of the FST07 element is to express the specific time of day in a 24-hour clock to satisfy "just-in-time" requirements. As an alternative, the ship/delivery pattern segment (SDP) may be used to define an approximate time, such as a.m. or p.m.
Will Only Send For FIRM Orders
- 010
- Requested Ship
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)
Will Only Send For FIRM Orders
Code qualifying the Reference Identification
- DO
- Pre-Notice
- MA
- Firm Or Build-Out
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- Format Will Be In The Form Of:
XXXXXXXX-ZZZZZZZZ – Where XXXXXXXX Is The Manifest Number, And ZZZZZZZZ Is The Receiver Number, Separated By A Dash (-). The Manifest Number Is Always Listed First. Or YYWW – Where YY Is The Year, And WW Is The Week. - The FST09 Element, For FIRM Orders Only, Will Be Used In The PRF01 Element Of The 856 Transaction. The First 8 Characters Of The FST09 Element Will Be Used In The REF02 Element Of The 810 Transaction.
- For TMMK Only, Will Only Contain Either The Manifest Number Or The Year/Week.
- BUILD OUT Quantities Will Always Be In The FST Segment Between The FIRM And FORECAST Segments For A Part Number.
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.
Total number of line items in the transaction set
Sum of values of the specified data element. All values in the data element will be summed without regard to decimal points (explicit or implicit) or signs. Truncation will occur on the left most digits if the sum is greater than the maximum size of the hash total of the data element.
-.0018 First occurrence of value being hashed.
.18 Second occurrence of value being hashed.
1.8 Third occurrence of value being hashed.
18.01 Fourth occurrence of value being hashed.
1855 Hash total prior to truncation.
855 Hash total after truncation to three-digit field.
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.