X12 862 Shipping Schedule
This Draft Standard for Trial Use contains the format and establishes the data contents of the Shipping Schedule Transaction Set (862) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used by a customer to convey precise shipping schedule requirements to a supplier, and is intended to supplement the planning schedule transaction set (830). The shipping schedule transaction set will supersede certain shipping and delivery information transmitted in a previous planning schedule transaction, but it does not replace the 830 transaction set. The shipping schedule transaction set shall not be used to authorize labor, materials or other resources.
The use of this transaction set will facilitate the practice of Just-In-Time (JIT) manufacturing by providing the customer with a mechanism to issue precise shipping schedule requirements on a more frequent basis than with the issuance of a planning schedule transaction, e.g., daily shipping schedules versus weekly planning schedules. The shipping schedule transaction also provides the ability for a customer location to issue shipping requirements independent of other customer locations when planning schedule transactions are issued by a consolidated scheduling organization.
- ~ 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
- SS
- Shipping Schedule (862)
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).
- 862
- Shipping Schedule
Beginning Segment for Shipping Schedule/Production Sequence
To transmit identifying numbers, dates, and other basic data relating to the transaction set
BSS08 is the forecast reference number (BFR02 from 830).
When BSS04 contains code PS, FST02 (in the Detail area) will contain code C or D. When the Forecast Qualifier is 'D', it indicates a planned forecast. When the Forecast Qualifier is 'C', it indicates a firm forecast. This relates to the 830 Forecast Schedule for a Planned Order Receipt Date.
When BSS04 contains code SH, FST02 (in the Detail area) will contain code C, which indicates a Shipment Based schedule. This relates to the 830 Forecast Schedule for a Firm Production Schedule Quantity for a specific date.
When shipping against a FIRM 862, use the date in BSS03 as the PO date in the PRF segment of the 856 Ship Notice.
Code identifying purpose of transaction set
- 00
- Original
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- Use BSS02 to indicate a document number.
Date expressed as CCYYMMDD
- Use BSS03 to indicate the date of this document.
Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast
- PS
- Planned Shipment Based
- SH
- Shipment Based
Date expressed as CCYYMMDD
- Use BSS05 to indicate the schedule horizon start date (the date when the schedule begins).
Date expressed as CCYYMMDD
- Use BSS06 to indicate the schedule horizon end date (the date when the schedule ends).
Name
To identify a party by type of organization, name, and code
When N101 contains code SF, N104 will contain the Sears-assigned vendor number for the ship point. This vendor number must be returned in the 810 - Invoice (REFIA in the header area) and in the 856 - Ship Notice (REFIA in the order level).
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
- SF
- Ship From
- 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.
4 - 7 Buying Party (Bill to)
9 - 9 Ship from vendor number
4 - 7 Ship to unit number
Reference Identification
To specify identifying information
This segment used only when data element N101 in the preceding N1 segment contains code BY.
The code for Rapid Deployment must be returned in the order level of the 856 - Ship Notice (REFMRRD).
Code qualifying the Reference Identification
- MR
- Merchandise Type 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.
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
13 - 13 EAN number
4 - 5 Sears’ item number
3 - 3 Sears’ SKU number
12 - 12 U.P.C. number
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Identifying number for a product or service
See LIN03
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Reference Identification
To specify identifying information
This segment will specify the department number for the item/SKU referenced in the associated LIN segment.
If multiple LIN loops are present, the department number in each REF segment will always be the same within a single 862 transaction.
Code qualifying the Reference Identification
- DP
- Department Number
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.
- 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.
- W
- Weekly Bucket (Monday through Sunday)
- X
- Weekly Bucket (7 day interval)
Code qualifying the Reference Identification
- PH
- Priority Rating
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
- The number of lines items (CTT01) is the accumulation of number of LIN segments. If used, hash total (CTT02) is the sum of the value 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.