X12 862 Shipping Schedule
This standard provides the format and establishes the data content of a Shipping Schedule Transaction within the context of an electronic data interchange (EDI) environment.
The Shipping Schedule Transaction provides the ability for a customer to convey precise shipping schedule requirements to a supplier, and is intended to supplement ANSI X12.14-1986 Planning Schedule transaction set (830). The shipping schedule transaction set will supercede certain shipping and delivery information transmitted in a previous planning schedule transaction, but it does not replace ANSI X12.14-1986. 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 customerlocations when planning schedule transactions are issued by a consolidated scheduling organization.
- ~ Segment
- * Element
- > Component
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.
Code identifying party receiving transmission.
Date sender generated a functional group of transaction sets.
Time (HHMM) expressed in 24-hour clock time when the sender generated a functional group of transaction sets (local time at sender's location).
(Time range: 0000 through 2359.)
Assigned number originated and maintained by the sender.
Code used in conjunction with the version data element to identify the issuer of the standard.
- T
- Transportation Data Coordinating Committee (TDCC)
- X
- Accredited Standards Committee X12
Code indicating the version, release, and industry ID of the EDI standard being used. Positions: 1 - 3, Major Version Number; Positions: 4 - 6, Release Level of Version; Positions: 7 - 12, Industry or Trade Association ID (Optionally assigned by user).
- 002002FORD
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) is intended for use 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
Identifying control number assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)
Beginning Segment for Shipping Schedule
To indicate the beginning of a shipping schedule.
The forecast quantity qualifier element is used to show the quantity usage in the FST01 element of the FST segment. A qualifier of "C" indicates that the quantities are cumulative quantities. A qualifier of "A" indicates that the quantities are discrete (net) quantities. (The FST01 quantities are always discrete (net) when strike protection (S) is indicated in the FST02 element.)
Code identifying purpose of transaction set.
- Either BSS07 or BSS08 is required.
- 00
- Original
- 05
- Replace
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
- Use BSS02 to indicate a document number.
Usually Julian date and sequential number.
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
- Use BSS03 to indicate the date of this document.
Schedule issue date.
Code which qualifies the type of dates used in the forecast.
- BB
- Broadcast based
- DL
- Delivery Based
- SH
- Shipment Based
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
- Use BSS05 to indicate the schedule horizon start date (the date when the schedule begins.)
First day of schedule
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
- Use BSS06 to indicate the schedule horizon end date (the date when the schedule ends.)
Last day of schedule
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.
Ford program number
Code which qualifies the types of quantities.
Identifies quantity usage in FST segments.
"A" - FST01 contains discrete (net) quantities.
"C" - FST01 contains cumulative quantities.
- A
- Actual Discrete Quantities
- C
- Cumulative Quantities
Name
To identify a party by type of organization, name and code
This N1 loop in the heading area can be used to identify the buyer, the seller, the bill to, the ship to and ship from locations.
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
- BY
- Buying Party (Purchaser)
- IC
- Intermediate Consignee
- SE
- Selling Party
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67).
- 92
- Assigned by Buyer
Code identifying a party.
- 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.
Will contain Ford assigned code.
Detail
Item Identification Detail
To specify basic item identification data.
Manufacturing plants will use for Ford part numbers only. Assembly plants will use for both Ford part numbers and returnable container numbers. Ford part numbers may consist of a prefix, base, suffix and control code. Any of these, except the base, may or may not be present. The portions of the part number are delimited by spaces.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If LIN06 is present, then LIN07 is required.
- 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.
- If LIN08 is present, then LIN09 is required.
Ford part number.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If LIN10 is present, then LIN11 is required.
- PO
- Purchase Order Number
Identifying number for a product or service.
- If LIN12 is present, then LIN13 is required.
Ford purchase order number.
Unit Detail
To specify item unit data.
This is a mandatory segment and indicates the unit of measure for all quantities relating to the line item.
Code identifying the basic unit measurement.
- If UNT03 is present, then UNT02 is required.
Will contain same unit of measure as the Ford Material Release (830).
Reference Numbers
To transmit identifying numbers.
Used to convey the dock, line feed location or reserve line feed location where the item is to be delivered.
Code qualifying the Reference Number.
- At least one of REF02 or REF03 must be present.
- DK
- Dock Number
- LF
- Assembly Line Feed Location
- RL
- Reserve Assembly Line Feed Location
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Location code.
Administrative Communications Contact
To identify a person or office to whom administrative communications should be directed
Not used by manufacturing plants. Assembly plants will use this segment for changes only.
FCSD Notes regarding PER*EX:
First 28 characters are the Ford Contact Name. The last 7 characters maybe "PRC O/S".
If "PRC O/S" present in PER02, then the stock should go to PRC2.
Butcher does the following:
- Internally, the GSDB code is changed from AF30A to AF30A-2
- The labels contain AF30A PRC2
- The ASN will contain only AF30A
FCSD Notes regarding PER*WH:
First 8 characters are the warehouse field.
If the Ship To location is USA, then
Position 1-4 = Bin/Bulk Code
Position 5-7 = Zone
Position 8 = Outside storage flag
If the Ship To location is Canada, then
Position 1-8 = Location
If the Ship To location is PRC, then
Position 1-2 = Base Size
Position 3-7 = Spaces
Position 8 = Outside storage flag
Code identifying the major duty or responsibility of the person or group named.
- EX
- Expeditor
- RD
- Receiving Dock
- WH
- Warehouse (FCSD non-production only)
Free-form name
Ford contact name or contact code.
Code identifying the type of communication number
- TE
- Telephone
Complete communications number including country or area code when applicable. Also see: Communications Number Qualifier (365).
Ford contact telephone number.
Forecast Schedule
To specify the forecasted dates and quantities
The FST01 quantity usage is determined by both the BSS11 and FST02 elements. Use these elements to determine if the quantity is discrete (net) or cumulative.
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
- If FST06 is present, then FST07 is required.
f FST02 = "C", FST01 contains discrete (net) or cumulative quantity based on value of BSS11 element of the BSS segment.
If FST02 = "S", FST01 contains discrete (net) quantity. For assembly plants (excluding KTP), this quantity will be rounded up to the next unit pack.
Code specifying the sender's confidence level of the forecast data.
- 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
- S
- Strike Protection
Code specifying interval grouping of the forecast.
- If FST03 - "F" (indicating flexible interval) and 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
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
Code specifying type of date or time, or both date and time.
- FST06 - To qualify 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 "AM" or "PM".
For assembly plant delivery items only - "002" means delivery requested at this time. (FST06 and FST07 - use only for next need time.)
Time expressed in 24-hour clock time (HHMM) (Time range: 0000 through 2359).
Also see: Time Qualifier (176).
Just-In-Time Schedule
To identify the specific shipping/delivery time in terms of a 24-hour clock and the associated quantity.
Shipped/Received Information
To specify shipment and/or receipt information
This is based on ASN information transceived for the last shipment, and the model year cumulative shipped value. The cum quantity is equal to cum receipts plus in-transit thru the last transceived ASN.
If SHP01 = "01" then
SHP02 = Quantity from last ASN
SHP03 = "011"
SHP04 = Shipped date from last ASN
SHP06 = Not Used
If SHP01 = "02" then
SHP02 = Cumulative quantity as of last ASN
SHP03 = "011"
SHP04 = Date the accumulations begin
SHP06 = Shipped date from last ASN
If SHP01 = "21", "22", "23" or "24" then
SHP02 = Quantity - challenged/pending
SHP03 = "011"
SHP04 = Shipped date of cum challenged/pending
SHP06 = Not Used
In addition for Assembly Plants only:
If SHP01 = "01" then
SHP02 = Quantity from last receipt
SHP03 = "050"
SHP04 = Receipt date of last quantity
SHP06 = Not Used
If SHP01 = "02" then
SHP02 = Quantity - cumulative receipts
SHP03 = "050"
SHP04 = Model year start date
SHP06 = Receipt date of last quantity
Code specifying the type of quantity.
- If SHP01 is present, then SHP02 is required.
- If SHP01 = "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
- 21
- Cumulative Quantity Shipped Short- Disposition Pending
- 22
- Cumulative Quantity Shipped Short- Disposition Challenged
- 23
- Cumulative Quantity Shipped Long- Disposition Pending
- 24
- Cumulative Quantity Shipped Long- Disposition Challenged
Numeric value of Quantity. Also see: Unit of Measurement Code (355).
- If SHP03 is present, then SHP04 is required.
If SHP01 = "21", "22", "23" or "24" then SHP02 contains difference between supplier cum and Ford cum.
Code specifying type of date or time, or both date and time.
- 011
- Shipped
- 050
- Received
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
- SHP04 - The date shipped, delivered, received, or the cumulative quantity start date (as qualified by SHP03).
If SHP06 is used SHP04 contains cumulative start date. If SHP06 is not used, SHP04 contains shipped or received date.
Date (YYMMDD). Also see: Date/Time Qualifier (374) and Date Qualifier (432).
- SHP06 - The cumulative quantity end date.
If SHP04 contains cumulative start date, SHP06 contains date last shipment shipped or received. Otherwise, not used.
Reference Numbers
To transmit identifying numbers.
When used, there will be only one "REF" segment per LIN, and it will always follow the "SHP*01" segment.
Code qualifying the Reference Number.
- At least one of REF02 or REF03 must be present.
- SI
- Shipper's Identifying Number for Shipment (SID)
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier. Also see Reference Number Qualifier, (128).
Shipment ID number (for assembly plants, this is the packing slip number).
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight and quantity.
Used by assembly plants only.
Code identifying the type of packaging. Part 1. Packaging form. Part 2.
Packaging Material.
- If TD101 is present, then TD102 is required.
- CNT
- Container
- 90
- Standard
Number of units (pieces) of the lading commodity. Also see: Unit of Measurement Code (355.)
- If TD103 is present, then TD104 is required.
Code defining the type of weight.
- Q
- Weight per 1000 Units
Numeric value of weight. Also see: Weight Qualifier (187), Weight Unit Qualifier (188), Unit of Measurement Code (355.)
Weight per 1000
Code identifying the basic unit measurement.
- LB
- Pound
Carrier Details (Equipment)
To specify transportation details relating to the equipment used by the carrier.
Used by assembly plants only.
Code identifying type of equipment used for shipment.
- If TD302 is present, then TD303 is required.
- CN
- Container
Sequencing or serial part of an equipment unit's identifying number (pure numeric form for equipment number is preferred).
Ford container type code.
Summary
Transaction Totals
To transmit a hash total for a specific element in the transaction set
Total number of line items in the transaction set.
- If CTT03 is present, then CTT04 is required.
Sum of values of the specific 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 leftmost 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.
- If CTT05 is present, then CTT06 is required.
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 assigned by the originator for a Transaction Set.
Also see: Data Interchange Control Number (28.)
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.
sample from Ford
GS~SS~AP10A~BTCXA~231227~0429~000011844~X~002002FORD
ST~862~0001
BSS~05~233610000093~231227~SH~231227~240109~924-13~~~~C
N1~ST~~92~AP10A
N1~SF~~92~BTCXA
N1~IC~~92~GZ7WL
LIN~~BP~AMPC3J 17B820 AC~PO~5700020090
UNT~EA
REF~DK~OW
REF~LF~K-42
REF~RL~CEVA
PER~EX~JP006 GGOWRIS1@FORD.COM~TE~-313-2065633
FST~5496~C~D~231227
FST~5496~C~D~231228
FST~5496~C~D~231229
FST~5496~C~D~231230
FST~5496~C~D~231231
FST~5496~C~D~240101
FST~5496~C~D~240102
FST~5568~C~D~240103
FST~5568~C~D~240104
FST~5616~C~D~240105
FST~5616~C~D~240106
FST~5616~C~D~240107
FST~5688~C~D~240108
FST~5688~C~D~240109
SHP~01~48~011~231220
REF~SI~0007417004
SHP~02~6336~011~230101~~231220
CTT~1~77832
SE~30~0001
GE~1~000011844
IEA~00001~000011844
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.