EDI 862 Shipping Schedule

Functional Group SS

X12M Supply Chain Subcommittee

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.

Heading

Position
Segment
Name
Max use
  1. To indicate the start of a transaction set and to assign a control number

  2. To indicate the beginning of a shipping schedule.

  3. To specify pertinent dates and times

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

  5. N1 Loop Optional
    Repeat 200
    1. To identify a party by type of organization, name and code

    2. To specify additional names or those longer than 35 characters in length

    3. To specify the location of the named party

    4. To specify the geographic place of the named party

    5. To transmit identifying numbers.

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

    7. To specify transportation instructions relating to shipment

Detail

Position
Segment
Name
Max use
  1. LIN Loop Mandatory
    Repeat 10000
    1. To specify basic item identification data.

    2. To specify item unit data.

    3. To transmit identifying numbers.

    4. To identify specific ship/delivery requirements

    5. FST Loop Optional
      Repeat 100
      1. To specify the forecasted dates and quantities

      2. To specify destination and quantity detail.

      3. JIT Loop Optional
        Repeat 24
        1. To identify the specific shipping/delivery time in terms of a 24-hour clock and the associated quantity.

        2. To transmit identifying numbers.

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

    7. SHP Loop Optional
      Repeat 10
      1. To specify shipment and/or receipt information

      2. To transmit identifying numbers.

    8. To specify the transportation details relative to commodity, weight and quantity.

    9. To specify transportation details relating to the equipment used by the carrier.

Summary

Position
Segment
Name
Max use
  1. To transmit a hash total for a specific element in the transaction set

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

Stedi is a registered trademark of Stedi, Inc. Stedi's EDI Reference is provided for marketing purposes and is free of charge. All names, logos, and brands of third parties listed on our site 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. Our use of these names, logos, and brands is for identification purposes only, and does not imply any such endorsement, sponsorship, or affiliation.