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
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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.
- 05
- Replace
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.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast
- DL
- Delivery Based
- SH
- Shipment 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.
Forecast Horizon Start Date
Date expressed as CCYYMMDD
- BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends.
Forecast Horizon End Date
Date expressed as CCYYMMDD
- BFR08 is the date forecast generated: The date the forecast data was generated.
Forecast Generation Date
Identifying number for Purchase Order assigned by the orderer/purchaser
Blanket Order
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- ST
- Ship To
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- DK
- Dock Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SU
- Supplier/Manufacturer
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.
Additional Name Information
To specify additional names or those longer than 35 characters in length
Address Information
To specify the location of the named party
Geographic Location
To specify the geographic place of the named party
Free-form text for city name
- A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.
Code (Standard State/Province) as defined by appropriate government agency
- N402 is required only if city name (N401) is in the U.S. or Canada.
Code defining international postal zone code excluding punctuation and blanks (zip code for United States)
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- DK
- Dock Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
A free-form description to clarify the related data elements and their content
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.
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
Identifying number for a product or service
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Resource Authorization
To specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule
Code identifying the resource which the buyer is authorizing the seller to commit to
- It is imperative that negotiations defining financial commitment have previously occurred and are agreed to by both buyer and seller.
Date expressed as CCYYMMDD
- ATH02 is the resource authorization through date: The date through which the buyer authorizes the seller to commit the resource defined in element ATH01.
Numeric value of quantity
- ATH03 is the current cumulative requirements quantity: The cumulative quantity that has been authorized to date from the cumulative start date (ATH05) through the resource authorization through date (ATH02).
Numeric value of quantity
- ATH04 is the maximum cumulative requirements quantity: The maximum cumulative quantity that has been authorized to date from the cumulative start date (ATH05) through the resource authorization through 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.
Date expressed as CCYYMMDD
- ATH05 is the 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.
Ship/Delivery Pattern
To identify specific ship/delivery requirements
Forecast Schedule
To specify the forecasted dates and quantities
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
- C
- Firm
- D
- Planning
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
- F
- Flexible Interval (from Date X through Date Y)
- M
- Monthly Bucket (Calendar Months)
- W
- Weekly Bucket (Monday through Sunday)
Code qualifying the Reference Identification
- RE
- Release Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Shipped/Received Information
To specify shipment and/or receipt information
Code specifying the type of quantity
- If SHP01 equals "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.
- 01
- Discrete Quantity
- 02
- Cumulative Quantity
Code specifying type of date or time, or both date and time
- 011
- Shipped
- 051
- Cumulative Quantity Start
Date expressed as CCYYMMDD
- SHP04 is the date shipped, delivered, received, or the cumulative quantity start date (as qualified by SHP03).
Date expressed as CCYYMMDD
- SHP06 is the cumulative quantity end date.
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- SI
- Shipper's Identifying Number for Shipment (SID)
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample 1
GS*PS*SENDERGS*RECEIVERGS*20231120*230152*000000001*X*004010~
ST*830*0003~
BFR*05*1804261**SH*A*20180101*20181015*20180426***PO116337~
N1*ST**92*2000~
N1*SU**92*10005085~
LIN**BP*A2300166-001*PO*PO116337~
UIT*EA~
PER*EX*ANALYST-X26~
ATH*FI*20180502*17**20180101~
ATH*MT*20180512*17**20180101~
ATH*PQ*20180425*16**20180101~
SDP*Y*Y~
FST*4*A*D*20180424~
FST*0*C*D*20180426~
FST*0*C*D*20180427~
FST*0*C*D*20180428~
FST*0*C*D*20180429~
FST*0*C*D*20180430~
FST*0*C*D*20180501~
FST*1*C*D*20180502~
FST*0*C*D*20180503~
FST*0*C*D*20180504~
FST*0*C*D*20180505~
FST*0*C*D*20180506~
FST*0*C*D*20180507~
FST*0*C*D*20180508~
FST*0*C*D*20180509~
FST*0*C*D*20180510~
FST*0*C*D*20180511~
FST*0*C*D*20180512~
FST*0*C*D*20180513~
FST*0*C*D*20180514~
FST*0*C*D*20180515~
FST*2*C*D*20180516~
FST*0*C*D*20180517~
FST*0*C*D*20180518~
FST*0*C*D*20180519~
FST*0*C*D*20180520~
FST*0*C*D*20180521~
FST*0*C*D*20180522~
FST*0*C*D*20180523~
FST*0*C*D*20180524~
FST*0*C*D*20180525~
FST*0*C*D*20180526~
FST*0*C*D*20180527~
FST*0*C*D*20180528~
FST*0*C*D*20180529~
FST*0*C*D*20180530~
FST*0*C*D*20180531~
FST*0*C*D*20180601~
FST*0*C*D*20180602~
FST*0*C*D*20180603~
FST*0*C*D*20180604~
SHP*01*2*011*20180416~
REF*SI*149632~
SHP*02*12*011*20180101**20180416~
LIN**BP*A2300167-001*PO*PO116337~
UIT*EA~
PER*EX*ANALYST-X26~
ATH*FI*20180101*3**20180502~
ATH*MT*20180101*3**20180509~
ATH*PQ*20180101*3**20180425~
SDP*Y*Y~
FST*0*C*D*20180426~
FST*0*C*D*20180427~
FST*0*C*D*20180428~
FST*0*C*D*20180429~
FST*0*C*D*20180430~
FST*0*C*D*20180501~
FST*0*C*D*20180502~
FST*0*C*D*20180503~
FST*0*C*D*20180504~
FST*0*C*D*20180505~
FST*0*C*D*20180506~
FST*0*C*D*20180507~
SHP*01*7*011*20180411~
REF*SI*149137~
SHP*02*114*011*20180101**20180411~
CTT*5*283~
SE*79*0003~
GE*1*000000001~
IEA*1*000000001~
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.