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 one 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 sender or the data in the interchange. The type of information is set by the Authorization Information Qualifier.
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 sender or the data in the interchange. The type of information is set by the Security Information Qualifier.
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 number 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.
- 00304
- Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1993
This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.
Code sent by the sender to request an interchange acknowledgment.
- 0
- No Acknowledgment Requested
- 1
- Interchange Acknowledgment Requested
Code to indicate whether data enclosed by this interchange envelope is test or production.
- P
- Production Data
- T
- Test Data
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.
- 003040
- Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1993
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
- X12.37 Shipping Schedule
Beginning Segment For Shipping Schedule/Production Sequence.
To transmit identifying numbers, dates and other basic data relating to the transaction set.
Code identifying purpose of transaction set.
- 00
- Original
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
- Use BSS02 to indicate a document number.
TMS purchase order number.
Date (YYMMDD).
- 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.
- SH
- Shipment Based
Date (YYMMDD).
- Use BSS05 to indicate the schedule horizon start date (the date when the schedule begins.)
Date (YYMMDD).
- Use BSS06 to indicate the schedule horizon end date (the date when the schedule ends.)
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.
TMS Purchase order number.
The first 3 iterations of this segment are mandatory. The fourth iteration is optional and can occur only in case of direct-ship orders.
Name
To identify a party by type of organization, name and code
Code identifying an organizational entity, a physical location, or an individual
- BY
- Buying Party (Purchaser)
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.
If N101 = BY:
TMS assigned supplier code.
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
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 USA or Canada.
Reference Numbers
To specify identifying numbers.
Code qualifying the Reference Number.
- CR
- Customer Reference Number
The first 3 iterations of this segment are mandatory. The fourth iteration is optional and can occur only in case of direct-ship orders.
Name
To identify a party by type of organization, name and code
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
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 USA or Canada.
Reference Numbers
To specify identifying numbers.
Code qualifying the Reference Number.
- CR
- Customer Reference Number
The first 3 iterations of this segment are mandatory. The fourth iteration is optional and can occur only in case of direct-ship orders.
Name
To identify a party by type of organization, name and code
The field will contain “DIRECT SHIP” in case of a direct-ship/VOR order.
Code identifying an organizational entity, a physical location, or an individual
The field will contain “DIRECT SHIP” in case of a direct-ship/VOR order.
- 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.
If N101 = ST:
In case of a direct ship/VOR order, this field will contain the dealer code.
- 51
- Ontario
- KY
- Kentucky
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
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 USA or Canada.
Reference Numbers
To specify identifying numbers.
Code qualifying the Reference Number.
- CR
- Customer Reference Number
The first 3 iterations of this segment are mandatory. The fourth iteration is optional and can occur only in case of direct-ship orders.
Name
To identify a party by type of organization, name and code
Code identifying an organizational entity, a physical location, 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.
If N101 = SU:
TMS assigned vendor code.
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
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 USA or Canada.
Reference Numbers
To specify identifying numbers.
Code qualifying the Reference Number.
- CR
- Customer Reference Number
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 (15) different product/service ID's for each item. For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- BP
- Buyer's Part Number
Identifying number for a product or service.
TMS part number.
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.
Part description
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- PL
- Purchaser's Order Line Number
Identifying number for a product or service.
Line item number
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- PO
- Purchase Order Number
Reference Numbers
To specify identifying numbers.
Code qualifying the Reference Number.
- WS
- Warehouse storage location number
Forecast Schedule
To specify the forecasted dates and quantities
Numeric value of quantity.
Scheduled quantity for this shipment date.
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
Code specifying interval grouping of the forecast.
- If FST03 - "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
- Specified in contract
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier, sequence of routing and to provide transit time information
Code describing the relationship of a carrier to a specific shipment movement.
- B
- Origin/Delivery Carrier (Any Mode)
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 one or more functional groups and interchange-related control segments
A count of the number of functional groups included in a transmission.
This number uniquely identifies the interchange data to the sender. It is assigned by the sender. Together with the sender ID it uniquely identifies the interchange data to the receiver. It is suggested that the sender, receiver, and all third parties be able to maintain an audit trail of interchanges using this number.
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.