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
The segment always indicates a replacement of the delivery schedule for the material number on the specified order number. The entire schedule of dates and quantities is sent and should replace other previously transmitted delivery plans for the material number and associated order number. (NOTE: Suppliers must not adjust any other order number or any other part number than what is contained in the data transmitted. Do not assume that a part number not contained has been deleted; or that an order number not sent is to be deleted. Those items not transmitted are still valid, they just do not have any revisions to be processed for this transmission of information.)
The dates in the BFR have little significance to John Deere, but the standard requires the dates in the transaction.
The codes of "DL"/"SH" and "A" are sent to indicate actual discrete quantity expected delivered/shipped.
- When BFR04 is "DL", the enclosed dates are the expected date of delivery at the customer's dock, so suppliers must consider transportation time in order to determine the required ship date from their facility.
- When BFR04 is "SH", the enclosed dates are the expected date of shipment.
Code identifying purpose of transaction set
- If BFR01 contains the value "04" (Net Change), BFR09 is required.
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.
Deere uses Julian Date or Date/Time Stamp
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.
Date expressed as CCYYMMDD
- BFR07 is the forecast horizon end date: The date when the forecast horizon (envelope) ends.
Deere will send this date.
Date expressed as CCYYMMDD
- BFR08 is the date forecast generated: The date the forecast data was generated.
F.O.B. Related Instructions
To specify transportation instructions relating to shipment
Code identifying payment terms for transportation charges
- FOB01 indicates which party will pay the carrier.
- DE
- Per Contract
Code identifying the trade terms which apply to the shipment transportation responsibility
- CFR
- Cost and Freight
- CIF
- Cost, Insurance, and Freight
- CIP
- Carriage and Insurance Paid To
- CPT
- Carriage Paid To
- DAP
- Delivered at Place
John Deere preferred
- DAT
- Delivered at Terminal
John Deere preferred
- DDP
- Delivered Duty Paid
- EXW
- Ex Works
- FAS
- Free Alongside Ship
- FCA
- Free Carrier
John Deere preferred
- FOB
- Free on Board
Code identifying type of location
- FOB06 is the code specifying the title passage location.
- PD
- Place of Delivery
A free-form description to clarify the related data elements and their content
Name Loop (N1-N4) can have multiple occurrences. At least one N1 segment will always contain an indicator ("ST") for the ship to location.
There will be an associated DUNS number or another John Deere unique number to cross reference all the address information. If the code "92" is used to indicate a Deere unique number, the supplier must be sure there is associated address information in the supplier data base or in the 830 data being transmitted
Name
To identify a party by type of organization, name, and code
There will be an associated DUNS number or another John Deere unique number to cross reference all the address information. If the code "92" is used to indicate a Deere unique number, the supplier must be sure there is associated address information in the supplier data base or in the 830 data being transmitted.
Code identifying an organizational entity, a physical location, property or an individual
- FS
- Final Scheduled Destination
Code designating the system/method of code structure used for Identification Code (67)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 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
Geographic Location
To specify the geographic place of the named party
The optional data contained in N405/N406 is the John Deere unloading (possibly receiving gate and dept) storage location. This information is required on the material's shipping documents to insure delivery at the intended location.
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)
Name Loop (N1-N4) can have multiple occurrences. At least one N1 segment will always contain an indicator ("ST") for the ship to location.
There will be an associated DUNS number or another John Deere unique number to cross reference all the address information. If the code "92" is used to indicate a Deere unique number, the supplier must be sure there is associated address information in the supplier data base or in the 830 data being transmitted
Name
To identify a party by type of organization, name, and code
There will be an associated DUNS number or another John Deere unique number to cross reference all the address information. If the code "92" is used to indicate a Deere unique number, the supplier must be sure there is associated address information in the supplier data base or in the 830 data being transmitted.
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)
- 1
- D-U-N-S Number, Dun & Bradstreet
- 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
Geographic Location
To specify the geographic place of the named party
The optional data contained in N405/N406 is the John Deere unloading (possibly receiving gate and dept) storage location. This information is required on the material's shipping documents to insure delivery at the intended location.
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)
Detail
Item Identification
To specify basic item identification data
This segment contains the Deere material number being ordered, and possibly some other information related to the part (see the code definitions in the guideline). The Deere PO number will also be included on this segment
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
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CR
- Contract Number
- EC
- Engineering Change Level
- HD
- International Harmonized Commodity Code
- MF
- Manufacturer
- RC
- Returnable Container Number
non-SAP units only
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Paired elements LIN04/LIIN05 thru LIN10/LIN11 will be sent based on the dynamic existence of data. The qualifier must be used in identifying the
business relevance of the value.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CR
- Contract Number
- EC
- Engineering Change Level
- HD
- International Harmonized Commodity Code
- MF
- Manufacturer
- RC
- Returnable Container Number
non-SAP units only
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Paired elements LIN04/LIIN05 thru LIN10/LIN11 will be sent based on the dynamic existence of data. The qualifier must be used in identifying the business relevance of the value
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CR
- Contract Number
- EC
- Engineering Change Level
- HD
- International Harmonized Commodity Code
- MF
- Manufacturer
- RC
- Returnable Container Number
non-SAP units only
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Paired elements LIN04/LIIN05 thru LIN10/LIN11 will be sent based on the dynamic existence of data. The qualifier must be used in identifying the
business relevance of the value.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CR
- Contract Number
- EC
- Engineering Change Level
- HD
- International Harmonized Commodity Code
- MF
- Manufacturer
- PD
- Part Number Description
- RC
- Returnable Container Number
non-SAP units only
- VP
- Vendor's (Seller's) Part Number
Identifying number for a product or service
Paired elements LIN04/LIIN05 thru LIN10/LIN11 will be sent based on the dynamic existence of data. The qualifier must be used in identifying the business relevance of the value.
Unit Detail
To specify item unit data
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
(Example PC = Pieces)
Code identifying the type of unit price for an item
Date of Last Update
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 636
- Date of Last Update
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)
Effective Date of Change
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 152
- Effective Date of Change
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)
Currency
To specify the currency (dollars, pounds, francs, etc.) used in a transaction
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
Code (Standard ISO) for country in whose currency the charges are specified
(Example: USD = US Dollars)
Marking, Packaging, Loading
To describe marking, packaging, loading, and unloading requirements
Code indicating the format of a description
- If PKG01 equals "F", then PKG05 is used. If PKG01 equals "S", then PKG04 is used. If PKG01 equals "X", then both PKG04 and PKG05 are used.
- F
- Free-form
Code specifying the marking, packaging, loading and related characteristics being described
- CB
- Container Type
- CUD
- Cushioning and Dunnage
A free-form description to clarify the related data elements and their content
- Special marking or tagging data can be given in PKG05 (description).
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
This optional segment may be included to indicate John Deere's packaging expectations.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack (PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the carton contains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element 357 = "12"; Data element 355 = "OZ".
- PC
- Piece
Reference Identification
To specify identifying information
Optional segment REF (reference information)
This segment may be included to provide additional delivery location information. The "DK" qualifier indicates a particular factory location beyond the receiving gate which the receiving customer would expect to be attached to the shipping information, so that material can be routed efficiently to the correct internal location.
Code qualifying the Reference Identification
- 5M
- Previous Sequence
- 55
- Sequence Number
- DK
- Dock Number
- DP
- Department Number
- KB
- Beginning Kanban Serial Number
- LF
- Assembly Line Feed Location
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
More discrete location than defined in N4 segment, element 06, at the header level
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.
This segment contains the date (refer to BFR04 for meaning) and required quantity. The field following the quantity is the indicator of firm, committed ("C") requirements, versus only forecasted or planning ("D") requirements. There will one FST line for every date and quantity combination.
If a supplier is not able to provide the material as expected on these segments, contacting a John Deere representative is required
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
Code qualifying the Reference Identification
- SH
- Sender Defined Clause
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Date/Quantity was previously confirmed by phone
Shipped/Received Information
To specify shipment and/or receipt information
The SHP segment may appear twice. If present, this data is intended to help the supplier determine if material was shipped but not yet receipted at the time of the customer requirement generation activity. If material was in fact in transit at that time, then the supplier deducts the quantity in transit from the earliest delivery date(s) provided in the FST segments.
most recent date of receipt activity may be provided, and associated quantity is the total receipt quantity for the material on the specified date.
a second occurrence may be provided with the accumulated receipts since the beginning of the order.
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
- 050
- Received
- 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).
Reference Identification
To specify identifying information
This optional REF segment may contain the ship ID number associated with the most recent receipt referenced in the SHP segment.
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
Ship ID of last receipt.
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
Number of line items (CTT01) is the accumulation of the number of LIN segments.
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.
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
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 from Deere
GS*PS*DEEREID*SUPPLIERID*20171122*0042*33959*X*004010
ST*830*339590001
BFR*05*20171122004241*20171122004241*SH*A*20170923*20190626*20171122
FOB*DE****DAP*PD*FREE-FORM DATA ELEMENT
N1*ST*JOHN DEERE PARTS DIST CENTER*1*789603131
N2*XPAC
N3*525 E 10TH AVE BLDG 4
N4*MILAN*IL*61264*US
LIN*00010*BP*DEEREPART*VP*VENDPART*EC*C*CR*5500999999*PD*PART DESCRIPTION
UIT*PC*558*TC
DTM*152*20170812*235624
DTM*636*20170801*224411
CUR*BY*USD
PKG*F*CB***RCG25
PKG*F*CUD***DUNNAGE
PO4**44*PC
REF*DK*Z11
REF*DP*035
REF*LF*DRFA2
REF*KB*008908730010
REF*55*REFERENCE INFO
REF*5M*REFERENCE INFO
FST*100*C*D*20171117
FST*0*C*D*20171129
FST*100*D*D*20180503
FST*100*D*D*20180628
FST*100*D*D*20180802
SHP*01*100*050*20170720
REF*SI*5134-69
SHP*02*4582*051*20081008
CTT*1*500
SE*21*339590001
GE*1*33959
IEA*1*000033939
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.