X12 862 Shipping Schedule

X12 Release 2040

This standard provides the format and establishes the data contents of a shipping schedule transaction set within the context of an electronic data interchange (EDI) environment. The shipping schedule transaction set provides the ability for 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.

Delimiters

• ~ Segment
• * Element
• > Component

GS Functional Group Header

Required · Max use 1

To indicate the beginning of a functional group and to provide control information

GS-01 · 479 · Functional Identifier Code · Required · Identifier (ID)

Code identifying a group of application related Transaction Sets.

• SS: Shipping Schedule (862)

GS-02 · 142 · Application Sender's Code · Required · String (AN) · Min 2 Max 12

Code identifying party sending transmission. Codes agreed to by trading partners.

GS-03 · 124 · Application Receiver's Code · Required · String (AN) · Min 2 Max 12

Code identifying party receiving transmission. Codes agreed to by trading partners.

GS-04 · 29 · Group Date · Required · Date (DT) · YYMMDD format

Date sender generated a functional group of transaction sets.

GS-05 · 30 · Group Time · Required · Time (TM) · HHMM format

Time (HHMM) when the sender generated a functional group of transaction sets (local time at sender's location).

GS-06 · 28 · Group Control Number · Required · Numeric (N0) · Min 1 Max 9

Assigned number originated and maintained by the sender.

GS-07 · 455 · Responsible Agency Code · Required · Identifier (ID) · Min 1 Max 2

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

GS-08 · 480 · Version / Release / Industry Identifier Code · Required · Identifier (ID)

Code indicating the version, release, subrelease and industry identifier of the EDI standard being used. Positions 1-3, version number; positions 4-6, release and subrelease level of version; positions 7-12, industry or trade association identifier (optionally assigned by user).

002040CHRY

Heading

010 Heading > ST

ST Transaction Set Header

Required · Max use 1

To indicate the start of a transaction set and to assign a control number

ST-01 · 143 · Transaction Set Identifier Code · Required · Identifier (ID)

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

ST-02 · 329 · Transaction Set Control Number · Required · Numeric (N) · Min 4 Max 9

Identifying control number assigned by the originator for a transaction set.

020 Heading > BSS

BSS Beginning Segment for Shipping Schedule

Required · Max use 1

To indicate the beginning of a shipping schedule.

BSS-01 · 353 · Transaction Set Purpose Code · Required · Identifier (ID) · Min 2 Max 2

Code identifying purpose of transaction set.

• Either BSS07 or BSS08 is required.

BSS-02 · 127 · Reference Number · Required · String (AN) · Min 1 Max 30

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.

BSS-03 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

• Use BSS03 to indicate the date of this document.

BSS-04 · 675 · Schedule Type Qualifier · Required · Identifier (ID) · Min 2 Max 2

Code identifying the type of dates used when defining a shipping or delivery time in a schedule or forecast.

BSS-05 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

• Use BSS05 to indicate the schedule horizon start date (the date when the schedule begins.)

BSS-06 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

• Use BSS06 to indicate the schedule horizon end date (the date when the schedule ends.)

BSS-08 · 127 · Reference Number · Optional · String (AN) · Min 1 Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

• BSS08 is the identifying number for a forecast assigned by the orderer/purchaser.

N1 Loop Optional Max >1

050 Heading > N1 Loop > N1

N1 Name

Required · Max use 1

To identify a party by type of organization, name and code

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID) · Min 2 Max 2

Code identifying an organizational entity or a physical location.

• At least one of N102 or N103 must be present.

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 35

Free-form name.

• If either N103 or N104 is present, then the other is required.

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID) · Min 1 Max 2

Code designating the system/method of code structure used for Identification Code (67).

N1-04 · 67 · Identification Code · Optional · Identifier (ID) · Min 2 Max 17

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.

Detail

LIN Loop Required Max >1

010 Detail > LIN Loop > LIN

LIN Item Identification

Required · Max use 1

To specify basic item identification data.

LIN-01 · 350 · Assigned Identification · Optional · String (AN) · Min 1 Max 6

Alphanumeric characters assigned for differentiation within a transaction set.

• LIN01 is the line item identification
• If LIN04 is present, then LIN05 is required.

LIN-02 · 235 · Product/Service ID Qualifier · Required · Identifier (ID) · Min 2 Max 2

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.
• If LIN06 is present, then LIN07 is required.

LIN-03 · 234 · Product/Service ID · Required · String (AN) · Min 1 Max 30

Identifying number for a product or service.

• If LIN08 is present, then LIN09 is required.

LIN-04 · 235 · Product/Service ID Qualifier · Optional · Identifier (ID) · Min 2 Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

• If LIN10 is present, then LIN11 is required.

LIN-05 · 234 · Product/Service ID · Optional · String (AN) · Min 1 Max 30

Identifying number for a product or service.

• If LIN12 is present, then LIN13 is required.

LIN-06 · 235 · Product/Service ID Qualifier · Optional · Identifier (ID) · Min 2 Max 2

Code identifying the type/source of the descriptive number used in Product/Service ID (234).

• If LIN14 is present, then LIN15 is required.

LIN-07 · 234 · Product/Service ID · Optional · String (AN) · Min 1 Max 30

Identifying number for a product or service.

• If LIN16 is present, then LIN17 is required.

020 Detail > LIN Loop > UIT

UIT Unit Detail

Required · Max use 1

To specify item unit data

UIT-01 · 355 · Unit of Measurement Code · Required · Identifier (ID) · Min 2 Max 2

Code identifying the basic unit of measurement.

• If UIT03 is present, then UIT02 is required.

030 Detail > LIN Loop > NTE

NTE Note/Special Instruction

Optional · Max use 100

To transmit information in a free-form format, if necessary, for comment or special instruction

NTE-01 · 363 · Note Reference Code · Optional · Identifier (ID)

Code identifying the functional area or purpose for which the note applies.

• LIN: Line Item

NTE-02 · 3 · Free Form Message · Required · String (AN) · Min 1 Max 60

Free-form text.

040 Detail > LIN Loop > PER

PER Administrative Communications Contact

Optional · Max use 6

To identify a person or office to whom administrative communications should be directed

PER-01 · 366 · Contact Function Code · Required · Identifier (ID) · Min 2 Max 2

Code identifying the major duty or responsibility of the person or group named.

PER-02 · 93 · Name · Optional · String (AN) · Min 1 Max 35

Free-form name.

PER-03 · 365 · Communication Number Qualifier · Optional · Identifier (ID) · Min 2 Max 2

Code identifying the type of communication number.

PER-04 · 364 · Communication Number · Optional · String (AN) · Min 7 Max 21

Complete communications number including country or area code when applicable.

050 Detail > LIN Loop > PO4

PO4 Item Physical Details

Optional · Max use >1

To specify the physical qualities, packaging, weights and dimensions relating to the item.

PO4-01 · 356 · Pack · Optional · String (AN) · Min 1 Max 6

Number of inner pack units per outer pack unit.

PO4-03 · 355 · Unit or Basis for Measurement Code · Optional · Identifier (ID) · Min 2 Max 2

Code identifying the basic unit of measurement.

070 Detail > LIN Loop > REF

REF Reference Numbers

Optional · Max use 12

To specify identifying numbers.

REF-01 · 128 · Reference Number Qualifier · Required · Identifier (ID) · Min 2 Max 2

Code qualifying the Reference Number.

REF-02 · 127 · Reference Number · Required · String (AN) · Min 1 Max 30

Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.

081 Detail > LIN Loop > N1

N1 Name

Optional · Max use 1

To identify a party by type of organization, name and code

N1-01 · 98 · Entity Identifier Code · Required · Identifier (ID) · Min 2 Max 2

Code identifying an organizational entity or a physical location.

N1-02 · 93 · Name · Optional · String (AN) · Min 1 Max 35

Free-form name.

N1-03 · 66 · Identification Code Qualifier · Optional · Identifier (ID) · Min 1 Max 2

Code designating the system/method of code structure used for Identification Code (67).

N1-04 · 67 · Identification Code · Optional · Identifier (ID) · Min 2 Max 17

Code identifying a party.

FST Loop Optional Max >1

090 Detail > LIN Loop > FST Loop > FST

FST Forecast Schedule

Required · Max use 1

To specify the forecasted dates and quantities

FST-01 · 380 · Quantity · Required · Decimal number (R) · Min 1 Max 10

Numeric value of quantity.

FST-02 · 680 · Forecast Qualifier · Required · Identifier (ID) · Min 1 Max 1

Code specifying the sender's confidence level of the forecast data.

FST-03 · 681 · Forecast Timing Qualifier · Required · Identifier (ID) · Min 1 Max 1

Code specifying interval grouping of the forecast.

FST-04 · 373 · Date · Required · Date (DT) · YYMMDD format

Date (YYMMDD).

FST-05 · 373 · Date · Optional · Date (DT) · YYMMDD format

Date (YYMMDD).

FST-06 · 374 · Date/Time Qualifier · Optional · Identifier (ID) · Min 3 Max 3

Code specifying type of date or time, or both date and time.

FST-07 · 337 · Time · Optional · Time (TM) · HHMM format

Time expressed in 24-hour clock time (HHMM, time range: 0000 though 2359).

JIT Loop Optional Max >1

120 Detail > LIN Loop > FST Loop > JIT Loop > JIT

JIT Just-In-Time Schedule

Required · Max use 1

To identify the specific shipping/delivery time in terms of a 24-hour clock and the associated quantity.

JIT-01 · 380 · Quantity · Required · Decimal number (R) · Min 1 Max 10

Numeric value of quantity.

JIT-02 · 337 · Time · Required · Time (TM) · HHMM format

Time expressed in 24-hour clock time (HHMM, time range: 0000 though 2359).

135 Detail > LIN Loop > FST Loop > DTM

DTM Date/Time Reference

Optional · Max use >1

To specify pertinent dates and times

DTM-01 · 374 · Date/Time Qualifier · Required · Identifier (ID) · Min 3 Max 3

Code specifying type of date or time, or both date and time.

DTM-02 · 373 · Date · Optional · Date (DT) · YYMMDD format

Date (YYMMDD).

DTM-03 · 337 · Time · Optional · Time (TM) · HHMM format

Time expressed in 24-hour clock time (HHMM, time range: 0000 though 2359).

DTM-04 · 623 · Time Code · Optional · Identifier (ID) · Min 2 Max 2

Code identifying the time.

140 Detail > LIN Loop > ATH

ATH Resource Authorization

Optional · Max use 1

To specify resource authorizations (i.e., finished labor, material, etc.) in the planning schedule.

ATH-01 · 672 · Resource Authorization Code · Required · Identifier (ID) · Min 2 Max 2

Code identifying the resource which the buyer is authorizing the seller to commit to.

ATH-02 · 373 · Date · Optional · Date (DT) · YYMMDD format

Date (YYMMDD).

ATH-03 · 380 · Quantity · Optional · Decimal number (R) · Min 1 Max 10

Numeric value of quantity.

ATH-04 · 380 · Quantity · Optional · Decimal number (R) · Min 1 Max 10

Numeric value of quantity.

ATH-05 · 373 · Date · Optional · Date (DT) · YYMMDD format

Date (YYMMDD).

SHP Loop Optional Max >1

150 Detail > LIN Loop > SHP Loop > SHP

SHP Shipped/Received Information

Required · Max use 1

To specify shipment and/or receipt information

SHP-01 · 673 · Quantity Qualifier · Optional · Identifier (ID) · Min 2 Max 2

Code specifying the type of quantity.

SHP-02 · 380 · Quantity · Optional · Decimal number (R) · Min 1 Max 10

Numeric value of quantity.

SHP-03 · 374 · Date/Time Qualifier · Optional · Identifier (ID) · Min 3 Max 3

Code specifying type of date or time, or both date and time.

SHP-04 · 373 · Date · Optional · Date (DT) · YYMMDD format

Date (YYMMDD).

SHP-05 · 337 · Time · Optional · Time (TM) · HHMM format

Time expressed in 24-hour clock time (HHMM, time range: 0000 though 2359).

SHP-06 · 373 · Date · Optional · Date (DT) · YYMMDD format

Date (YYMMDD).

SHP-07 · 337 · Time · Optional · Time (TM) · HHMM format

Time expressed in 24-hour clock time (HHMM, time range: 0000 though 2359).

175 Detail > LIN Loop > TD5

TD5 Carrier Details (Routing Sequence/Transit Time)

Optional · Max use 1

To specify the carrier, sequence of routing and to provide transit time information

TD5-04 · 91 · Transportation Method/Type Code · Optional · Identifier (ID) · Min 1 Max 2

Code specifying the method of transportation for the shipment.

TD5-10 · 732 · Transit Time Direction Qualifier · Optional · Identifier (ID) · Min 2 Max 2

Code specifying the value of time used to measure the transit time.

TD5-11 · 733 · Transit Time · Optional · String (AN) · Min 1 Max 30

The numeric amount of transit time.

Summary

010 Summary > CTT

CTT Transaction Totals

Required · Max use 1

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.

CTT-01 · 354 · Number of Line Items · Required · Numeric (N0) · Min 1 Max 6

Total number of line items in the transaction set.

• If CTT03 is present, then CTT04 is required.

CTT-02 · 347 · Hash Total · Required · Decimal number (R) · Min 1 Max 10

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.

## Example:
-.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.

020 Summary > SE

SE Transaction Set Trailer

Required · Max use 1

To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments).

SE-01 · 96 · Number of Included Segments · Required · Numeric (N0) · Min 1 Max 6

Total number of segments included in a transaction set including ST and SE segments.

SE-02 · 329 · Transaction Set Control Number · Required · Numeric (N) · Min 4 Max 9

Identifying control number assigned by the originator for a transaction set.

GE Functional Group Trailer

Required · Max use 1

To indicate the end of a functional group and to provide control information

GE-01 · 97 · Number of Transaction Sets Included · Required · Numeric (N0) · Min 1 Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element.

GE-02 · 28 · Group Control Number · Required · Numeric (N0) · Min 1 Max 9

Assigned number originated and maintained by the sender.