X12 870 Customer Order Status Report
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.
- ~ 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
- RS
- Order Status Information (869, 870)
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).
- 870
- Order Status Report
Beginning Segment for Order Status Report
To indicate the beginning of an Order Status Report Transaction Set
Example: BSR2CO*870Report-2021-08-01T10:39:32.*20210801~
Code indicating the reason for sending the report
- 2
- Prearranged Schedule or Agreement
Code identifying a group of orders and items
- CO
- All Orders - Unshipped Items
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
- BSR03 indicates a status report document number assigned by the sender.
Detail
Example: HL*172**O~
Hierarchical Level
To identify dependencies among and the content of hierarchically related groups of data segments
A unique number assigned by the sender to identify a particular data segment in a hierarchical structure
- HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL segment and would be incremented by one in each subsequent HL segment within the transaction.
Code defining the characteristic of a level in a hierarchical structure
- HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
- O
- Order
Code indicating if there are hierarchical child data segments subordinate to the level being described
- HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.
- 0
- No Subordinate HL Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
Example: PRFXDR7862**20210801~
Baseline Item Data
To specify basic and most frequently used line item data
Example: PO172EA12.55*VP2316272MGTZE345UP876857682342~
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
This is the line number provided on the Inbound EDI 850 document in the PO101.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- EA
- Each
Price per unit of product, service, commodity, etc.
Code identifying the type of unit price for an item
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- PO106 through PO125 provide for ten different product/service IDs per each item. For example: Case, Color, Drawing No., U.P.C. No., ISBN No., Model No., or SKU.
- VP
- Vendor's (Seller'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)
- MG
- Manufacturer'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)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Product/Item Description
To describe a product or process in coded or free-form format
Example: PIDF02***White on Black 3 4"~
Code indicating the format of a description
- If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then both PID04 and PID05 are used.
- F
- Free-form
Code identifying the general class of a product or process characteristic
Item Status Report
To specify detailed purchase order/item status
ISR02 is the date of the status change.
ISR01 status is applicable to the quantities in QTY02.
Example: ISRBO20210804~
Code indicating the status of an order or shipment or the disposition of any difference between the quantity ordered and the quantity shipped for a line item or transaction
- If ISR01 specifies a date, ISR02 is required.
- BO
- Back Ordered
- BP
- Shipment Partial, Back Order to Ship on (Date)
- DI
- Discontinued
- IC
- Item Canceled
- IN
- In Process
Quantity
To specify quantity information
Example: QTY012*EA~
Code specifying the type of quantity
- 01
- Discrete Quantity
Date/Time Reference
To specify pertinent dates and times
Summary
Transaction Totals
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.
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
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
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample
BSR*2*CO*870Report-2021-08-01T10:39:32.*20210801~
HL*172**O~
PRF*XDR7862***20210801~
PO1*7*2*EA*12.55*CA*VP*2316272*MG*TZE345*UP*757683451232~
PID*F*02***White on Black 3 4"~
ISR*BO*20210804~
QTY*01*2*EA~
DTM*068*20210804~
HL*173**O~
PRF*XDR8358***20210801~
PO1*2*10*EA*20.04*CA*VP*2954213*MG*PURA0001*UP*123432123454~
PID*F*02***Pick Up Roller~
ISR*BP*20210809~
QTY*01*3*EA~
DTM*068*20210809~
PO1*3*10*EA*13.34*CA*VP*2954212*MG*SPA0001*UP*998877654321~
PID*F*02***Separation Pad~
ISR*BP*20210810~
QTY*01*1*EA~
DTM*068*20210810~
CTT*3~
SE*23*1086923~
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.