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
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Shipping Schedule/Production Sequence
To transmit identifying numbers, dates, and other basic data relating to the transaction set
The segment always indicates a new release of the shipping schedule or trigger data for the material number on the specified order number. The data should always be considered new information for releases to be added to the supplier's previous information.
The BSS dates have little significance to 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 BSS04 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 BSS04 is "SH", the enclosed dates are the expected date of shipment.
Code identifying purpose of transaction set
- 00
- Original
- 05
- Replace
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
- DL
- Delivery 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).
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Identifying number for Purchase Order assigned by the orderer/purchaser
Code identifying the type of quantities used when defining a schedule or forecast
- A
- Actual Discrete Quantities
Name
To identify a party by type of organization, name, and code
Name Loop (N1-N4) can have multiple occurrences.
There will be an associated DUNS number or another 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 862 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
Address Information
To specify the location of the named party
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)
Code identifying type of location
- DE
- Destination (Shipping)
Name
To identify a party by type of organization, name, and code
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 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 862 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
Address Information
To specify the location of the named party
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)
Code identifying type of location
- DE
- Destination (Shipping)
Detail
Item Identification
To specify basic item identification data
This segment contains the John Deere material number being ordered, and possibly other information related to the part (see code definitions). The John 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
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CR
- Contract Number
- EC
- Engineering Change Level
- PD
- Part Number Description
- PL
- Purchaser's Order Line Number
The PO Line Number value needs to be returned on the 856 Advance Ship Notice in the LIN segment's qualified/value pair with qualifier "PL"
- 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
- PD
- Part Number Description
- PL
- Purchaser's Order Line Number
The PO Line Number value needs to be returned on the 856 Advance Ship Notice in the LIN segment's qualified/value pair with qualifier "PL"
- 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
- PD
- Part Number Description
- PL
- Purchaser's Order Line Number
The PO Line Number value needs to be returned on the 856 Advance Ship Notice in the LIN segment's qualified/value pair with qualifier "PL"
- 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
- PD
- Part Number Description
- PL
- Purchaser's Order Line Number
The PO Line Number value needs to be returned on the 856 Advance Ship Notice in the LIN segment's qualified/value pair with qualifier "PL"
- 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.
(Example: PC=pieces)
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
(Example: PC=pieces)
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).
Reference Identification
To specify identifying information
This segment(s) may be included to provide additional delivery location information.
The "DP" qualifier indicates a particular factory Department beyond the receiving gate that the receiving customer would expect to be attached to the shipping information, so that material can be routed efficiently to the correct internal location. Likewise, the "LF" qualifier may be sent to indicate a specific Line Feed location within the customer factory. This information may be expected to be returned on the shipping documents or on the electronic shipping notice (ASN or 856) transaction.
In addition, another REF segment will normally be sent with and indicator of "KB" or "LS" to communicate the trigger release number. This REF segment is also expected to be returned on the ASN 856 transaction when the shipment of this trigger release is completed.
Code qualifying the Reference Identification
- 9H
- Packaging Group Number
- DK
- Dock Number
- DP
- Department Number
- KB
- Beginning Kanban Serial Number
Contains the John Deere trigger number
- LF
- Assembly Line Feed Location
- LS
- Bar-Coded Serial Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Forecast Schedule
To specify the forecasted dates and quantities
This segment contains the date (refer to BSS04 for meaning) and required quantity. The field following the quantity is the indicator of firm, committed ("C") deliveries. 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.
FST06, FST07, FST08, FST09 will be sent by John Deere only under certain conditions.
The following 2 segments (SHP and REF) are normally NOT included in the 862 ship schedule data.
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 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 specifying type of date or time, or both date and time
- FST06 qualifies the time in FST07. The purpose of the FST07 element is to express the specific time of day in a 24-hour clock to satisfy "just-in-time" requirements. As an alternative, the ship/delivery pattern segment (SDP) may be used to define an approximate time, such as a.m. or p.m.
- 002
- Delivery Requested
- 010
- Requested Ship
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)
Code qualifying the Reference Identification
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
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
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
Number of Line Items (CTT01) is the accumulation of 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 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
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*SS*SENDERGS*RECEIVERGS*20231106*125221*000000001*X*004010
ST*862*150600001
BSS*00*0000000289877327*20141017*SH*20141017*20141017*0000460431
N1*ST*JACOBSON WAREHOUSE CO INC*1*603911475
N3*1300 19TH ST
N4*EAST MOLINE*IL*61244-235*US
LIN*0010*BP*PART NO*CR*5500000000*PL*0010
UIT*PC
PKG*F*CB***RS026
PKG*F*CUD***DUNNAGE
REF*DP*M011
REF*LF*M011
REF*KB*004604310010
FST*10*C*D*20141023
LIN*0020*BP*PART NO*CR*5500000000*PL*0010
UIT*PC
PKG*F*CB***RS026
PKG*F*CUD***DUNNAGE
REF*DP*M011
REF*LF*M011
REF*KB*004604310020
FST*10*C*D*20141023
CTT*2*20
SE*23*150600001
GE*1*000000001
IEA*1*000000001
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.