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
- 00400
- Standard Issued as ANSI X12.5-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
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.
- ORIGINAL
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
- DL
- Delivery 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
Code identifying an organizational entity, a physical location, property or an individual
- MI
- Planning Schedule/Material Release Issuer
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
Free-form name
Supplier's Name
This Element Is To Be Printed On The AIAG Label
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Detail
Item Identification
To specify basic item identification data
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
Identifying number for a product or service
- This Element Is To Be Printed On The AIAG Label
- The Part Number Does Not Have Any Imbedded Dashes Or Spaces
- “NO SHIP” Is Valid In The LIN03 When There Is A Zero Quantity
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- RC
- Returnable Container Number
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- ZZ
- Mutually Defined
Item Physical Details
To specify the physical qualities, packaging, weights, and dimensions relating to the item
Part Release Status
To indicate the status of the part being ordered or forecast with respect to this material release or planning document
Reference Identification Assembly Line Feed Location
To specify identifying information
Code qualifying the Reference Identification
- LF
- Assembly Line Feed Location
Reference Identification Dock Number
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
- This Element Is To Be Printed On The AIAG label
- The dock code will be used in the IT111 element of the 810 transaction.
Reference Identification Location Number
To specify identifying information
Code qualifying the Reference Identification
- LU
- Location Number
Reference Identification Merchandise Type Code
To specify identifying information
Code qualifying the Reference Identification
- MR
- Merchandise Type Code
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Toyota card code
- The REF02 Element Will Be Used In The IT101 Element Of The 810 Transaction
- The Card Code Will Be A “M390” For All Original Order North American Parts
Reference Identification Product Type
To specify identifying information
Code qualifying the Reference Identification
- PRT
- Product Type
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Product description
- This Element Is To Be Printed On The AIAG Label
- This Segment Is Sent For Ekanban Orders Only
Reference Identification Route Number
To specify identifying information
Code qualifying the Reference Identification
- RU
- Route Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Toyota dock code
- This Element Is To Be Printed On The AIAG Label
- This Segment Is Sent For Ekanban Orders Only
- This Segment Is Optional. It Will Only Appear If There Is A Sub-Route.
Reference Identification Ship From
To specify identifying information
Code qualifying the Reference Identification
- SF
- Ship From
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
This segment is for ekanban orders only
- This Element Is To Be Printed On The AIAG label
- The dock code will be used in the IT111 element of the 810 transaction.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Code identifying the major duty or responsibility of the person or group named
- SC
- Schedule Contact
Code identifying the type of communication number
- TE
- Telephone
Ship/Delivery Pattern
To identify specific ship/delivery requirements
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.
- 38
- Original Quantity
Code specifying type of date or time, or both date and time
- 010
- Requested Ship
Date expressed as CCYYMMDD
- SHP04 is the date shipped, delivered, received, or the cumulative quantity start date (as qualified by SHP03).
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)
Reference Identification Cross Reference Number
To specify identifying information
Code qualifying the Reference Identification
- 6O
- Cross Reference Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Cross dock 2
A free-form description to clarify the related data elements and their content
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Cross dock 2 date
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference Identification Cross-listed Course Number
To specify identifying information
Code qualifying the Reference Identification
- UL
- Cross-listed Course Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Cross Dock 1
A free-form description to clarify the related data elements and their content
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Cross dock 1 date
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference Identification Manifest Key Number
To specify identifying information
Code qualifying the Reference Identification
- MK
- Manifest Key Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Format Is XXXXXXXX-YYYYYYYY Where XXXXXXXX Is The Manifest Number, Then A Dash, Followed By YYYYYYYY, Which is the Receiving Number
A free-form description to clarify the related data elements and their content
Code qualifying the Reference Identification
- DO
- Delivery Order Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Code qualifying the Reference Identification
Format Is XXXXXXXX-YYYYYYYY Where XXXXXXXX Is The Manifest Number, Then A Dash, Followed By YYYYYYYY, Which is the Receiving Number
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Format Is XXXXXXXX-YYYYYYYY Where XXXXXXXX Is The Manifest Number, Then A Dash, Followed By YYYYYYYY, Which is the Receiving Number
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference Identification Mutually Defined
To specify identifying information
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Main route
This Element Is To Be Printed On The AIAG Label
A free-form description to clarify the related data elements and their content
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Routing order sequence $
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Unload date
Code qualifying the Reference Identification
- ZZ
- Mutually Defined
Carrier Details (Routing Sequence/Transit Time)
To specify the carrier and sequence of routing and provide transit time information
Free-form description of the routing or requested routing for shipment, or the originating carrier's identity
Send ROUTING or MAIN ROUTE
Code identifying type of location
- DE
- Destination (Shipping)
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.
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
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.