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
- 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.
This number links all line items (LIN loops) on this 830 together. It is also
used to link to the 864 text transaction.
Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast
- PR
- Planned Requirement Based
The qualifier will be used for Production 830's.
- ZZ
- Mutually Defined
This qualifier will be used for Flex Forecast 830's.
Code identifying the type of quantities used when defining a schedule or forecast
- R
- Replacement Quantities
Date expressed as CCYYMMDD
- BFR06 is the forecast horizon start date: The date when the forecast horizon (envelope) begins.
Date expressed as CCYYMMDD
- BFR08 is the date forecast generated: The date the forecast data was generated.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
This segment will only be used if there is a corresponding text message for this document.
Code identifying the major duty or responsibility of the person or group named
- ZZ
- Mutually Defined
Free-form name
"Comments in EDI 864" When this message appears, it indicates that an
applicable 864 Text message has also been transmitted.
Date/Time Reference
To specify pertinent dates and times
Code specifying type of date or time, or both date and time
- 167
- Most Recent Revision (or Initial Version)
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)
HHMM Format
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
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.
- 2
- Standard Carrier Alpha Code (SCAC)
Code identifying a party or other code
The Standard Carrier Alpha Code (SCAC) of the planned carrier
Exception: Some Honda plants do not use the SCAC code. They will
transmit “XXXX”.
Honda suppliers must return the SCAC code of the trucking company picking up the freight on the 856 (Advance Ship Notice), unless otherwise specified by your Purchasing contact. This will usually match the SCAC found in the ordering document.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- 16
- Plant
Code designating the system/method of code structure used for Identification Code (67)
- 98
- Purchasing Office
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.
This is the Honda code number for each logistical company.
For example: (May not be an all-inclusive list.)
AEP = Anna Engine Plant
AHM = American Honda Motor Co., Inc.
ELP = East Liberty Auto Plant
GDL = Honda de México, Guadalajara Plant (Ending ~ TBD 2019)
HCL = Honda de México, Celaya Plant
HCM = Honda of Canada Mfg.
HDM = Honda de México, Guadalajara Plant (Starting ~ TBD 2019)
HMA = Honda Manufacturing of Alabama
HMI = Honda Manufacturing of Indiana
HMS = Honda México Sales
HPE = Honda Power Equipment
HPG = Honda Precision Parts Georgia
HSC = Honda of South Carolina
HSP = Honda Supply Parts
HTM = Honda Transmission
IPS = Int’l Operating Office (IOO), aka Int’l Parts Supply
MAP = Marysville Auto Plant
MPS = Honda de México Parts Supply
MSP = Mexico Supply Parts
MTP = Mexican Transmission Plant
PMC = Performance Manufacturing Center
T(XX) = Honda Trading [The “(XX)” will be replaced with two digits signifying the Honda Trading location]
Additional Name Information
To specify additional names or those longer than 35 characters in length
Free-form name
The corporate name for the Honda facility issuing this document.
For example: (May not be an all-inclusive list.)
“American Honda Motor Co., Inc.”
“Honda of America Mfg., Inc.”
“Honda of Canada Mfg.”
“Honda Manufacturing of Alabama, LLC”
“Honda Manufacturing of Indiana”
“Honda de México, S.A. de C.V.”
“Honda de México, Celaya Plant”
“Honda México Sales”
“Honda de México Parts Supply”
“Honda de México Supply Parts”
“Honda de México Transmission Plant”
“Honda Power Equipment”
“Honda Power Train Georgia”
“Honda Trading”
“Honda Transmission”
“Honda of South Carolina”
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
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.
An 8-digit code assigned by Honda to identify a specific supplier and location. The first 6 digits are the supplier number and the last 2 digits are the location code (which may be 00).
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)
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
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.
- BP
- Buyer's Part Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- BE
- Buyer's Engineering Change Level Number
Indicates the part must be shipped at this Design change level.
- EC
- Engineering Change Level
For reference only, parts may be shipped at another level. To determine the correct design
level to ship, follow the Honda Specification Change "Instruction Sheet" or Instruction Summary from your Honda planner.KEY POINT: ALWAYS LABEL THE PARTS WITH
THE ACTUAL DESIGN LEVEL.
Identifying number for a product or service
This field (and the corresponding qualifier) will be present for a
Manufacturing Base Part Number that begins with a number less than 92.
Exceptions:
AHM: This field (and qualifier) will not be present.
HTA: This field (and qualifier) may be present.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PD
- Part Number Description
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- RN
- Release Number
Identifying number for a product or service
This number is a Honda application reference number. Suppliers will not return this data to Honda in any EDI document.
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- L1
- Program Level
Identifying number for a product or service
The business purpose for the project number will be defined at a later date. (Future Honda system enhancement).
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
Date/Time Reference
To specify pertinent dates and times
This segment is optional. (Currently Honda is not sending this segment.)
Code specifying type of date or time, or both date and time
- 311
- Latest Receiving Date/Cutoff Date
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)
HHMM Format
Quantity
To specify quantity information
- QTY is used to specify supplemental quantities relevant to the forecast function. However, QTY is not related to the actual forecast quantity in the FST segments.
This segment is optional. (Currently Honda is not sending this segment.)
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight, and quantity
Number of units (pieces) of the lading commodity
Description of an item as required for rating and billing purposes
Container type as designated by Honda
"XX" will be used for non-returnable containers
Name
To identify a party by type of organization, name, and code
AHM will not provide ship to information in the 830. For AHM, "Ship To Name" will be filled with “XX” and "Ship To Code" will be filled with "XX" or “YY”.
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.
This is the code assigned by Honda for this ship to location
- For OEM forecasts, this will be a ship to code
- For DSPS forecasts, this will be the supplier number and location code
- Ship To codes and/or addresses could duplicate between plants
Address Information
To specify the location of the named party
AHM will not provide ship to information in the 830. The mandatory field will be filled with "XX".
Geographic Location
To specify the geographic place of the named party
AHM will not provide ship to information in the 830. The mandatory fields will contain "X"'s.
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)
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.
Shipment information will be included in the 862 Ship Schedule.
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.
Only one Forecast Qualifier can be used per time bucket.
- C
- Firm
For Production 830's this will be immediate or past due demand.
For Flex Forecast 830's this will not be present. - D
- Planning
For Production 830's this will be a forecast of future demand.
For Flex Forecast 830's this will not be present. - F
- Potential Order Increase
For Production 830's this will not be present.
For Flex Forecast 830's this will represent the potential increase in quantity in addition to the Production 830 quantity. - X
- Modification
For Production 830's this will not be present.
For Flex Forecast 830's this will represent the actual change in production for that period compared to the Production 830. This could be a positive or negative value.
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.
- C
- Daily
- M
- Monthly Bucket (Calendar Months)
AHM & HDM will use "Monthly Bucket" versus "Four Week Bucket"
- T
- Four week bucket (13 buckets per year)
When used, the manufacturing plants will use "Four Week Bucket" versus "Monthly Bucket"
- W
- Weekly Bucket (Monday through Sunday)
Date expressed as CCYYMMDD
This is the forecast start date.
- Beginning date of period if weekly, four week or monthly buckets. Actual date of period if daily.
- For weekly and four week buckets, the periods are calculated sequentially on a weekly basis, always starting on a Monday.
- Daily buckets will start on the first business day of the week. (Example: If there is a holiday on Monday, the first daily bucket will be Tuesday.)
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
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.
Sum of the values of the quantities (FST01) for each 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
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.