EDI 870 Order Status Report

Functional Group RS

X12M Supply Chain Subcommittee

This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Report Transaction Set (870) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report on the current status of a requirement forecast, an entire purchase order, selected line items on a purchase order, selected products/services on a purchase order, or purchase orders for a specific customer in their entirety or on a selection basis. The transaction set can also be used to report on the current status of single or multiple requisitions. The report format allows for the inclusion of "reasons" relative to the status. This transaction set may also be used to update the supplier's scheduled shipment or delivery dates. This transaction set can result from either an inquiry or a prearranged schedule agreed to by the trading partners.

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 an Order Status Report Transaction Set

  3. To specify identifying information

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

  5. To specify transportation special handling requirements, or hazardous materials information, or both

  6. To specify the carrier and sequence of routing and provide transit time information

  7. 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 specify identifying information

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

    7. To identify the type or transmission or both of paperwork or supporting information

  8. To specify pertinent dates and times

  9. LM Loop Optional
    Repeat 10
    1. To transmit standard code list identification information

    2. Code to transmit standard industry codes

Detail

Position
Segment
Name
Max use
  1. HL Loop Mandatory
    Repeat 1000
    1. To identify dependencies among and the content of hierarchically related groups of data segments

    2. To provide reference to a specific purchase order

    3. ISR Loop Optional
      Repeat 104
      1. To specify detailed purchase order/item status

      2. To describe a product or process in coded or free-form format

      3. To specify quantity information

    4. To specify identifying information

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

    6. To specify pertinent dates and times

    7. To provide information about a contract

      Use is limited to intra-organizational transactions.
    8. 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 specify identifying information

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

    9. LM Loop Optional
      Repeat 10
      1. To transmit standard code list identification information

      2. Code to transmit standard industry codes

    10. PO1 Loop Optional
      Repeat 1000
      1. To specify basic and most frequently used line item data

      2. To specify the currency (dollars, pounds, francs, etc.) used in a transaction

      3. To specify product subline detail item data

      4. To specify additional item-related data involving variations in normal price/quantity structure

      5. To describe a product or process in coded or free-form format

      6. To specify physical measurements or counts, including dimensions, tolerances, variances, and weights (See Figures Appendix for example of use of C001)

      7. To describe marking, packaging, loading, and unloading requirements

      8. ISR Loop Optional
        Repeat 104
        1. To specify detailed purchase order/item status

        2. To describe a product or process in coded or free-form format

        3. To specify quantity information

        4. To specify pertinent dates and times

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

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

        7. To specify the location of the named party

        8. To specify the geographic place of the named party

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

        10. To specify the carrier and sequence of routing and provide transit time information

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

        12. To specify transportation special handling requirements, or hazardous materials information, or both

        13. To specify identifying information

        14. To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion, allowance, or charge

        15. LM Loop Optional
          Repeat 10
          1. To transmit standard code list identification information

          2. Code to transmit standard industry codes

      9. LX Loop Optional
        Repeat >1
        1. To reference a line number in a transaction set

          The LX loop conveys serial number, lot number, and inventory data.
        2. To specify identifying information

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

        4. To specify pertinent dates and times

        5. LM Loop Optional
          Repeat 10
          1. To transmit standard code list identification information

          2. Code to transmit standard industry codes

Summary

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

    The number of line items (CTT01) is the accumulation of the number of HL segments. If used, hash total (CTT02) is the sum of the value of quantities ordered (PO102) for each PO1 segment.
  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.