X12 870 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
- None included
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
Code indicating the reason for sending the report
- 1
- Response to an Order Status Inquiry (869)
- 2
- Prearranged Schedule or Agreement
- 3
- Unsolicited Report
Code identifying a group of orders and items
- PA
- Selected Orders - All Items
- PP
- Selected Orders - Selected 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.
Date expressed as CCYYMMDD
- BSR04 indicates the date of this report from the sender.
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)
- BSR07 indicates the time of this report from the sender.
This segment is used only on RPC Order Status Reports to identify the supplier.
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- SF
- Ship From
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- 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.
6 - 6 Sears assigned supplier code
Detail
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
Purchase Order Reference
To provide reference to a specific purchase order
Item Status Report
To specify detailed purchase order/item status
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.
- DE
- Deleted Order
- ED
- Expect to Ship By (Date)
- NN
- Not in Process - No Shipping Schedule
Date/Time Reference
To specify pertinent dates and times
Reference Identification
To specify identifying information
Code qualifying the Reference Identification
- 19
- Division Identifier
- CO
- Customer Order Number
- DP
- Department Number
- IA
- Internal Vendor Number
- MI
- Mill Order Number
- MR
- Merchandise Type Code
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
3 - 3 Division identifier (REF01=19)
12 - 12 Customer order number (REF01=CO)
3 - 3 Department number (REF01=DP)
9 - 9 Internal vendor number (REF01=IA)
8 - 30 Mill order number (REF01=MI)
3 - 6 Merchandise type code (REF01=MR)
Name
To identify a party by type of organization, name, and code
Code identifying an organizational entity, a physical location, property or an individual
- BY
- Buying Party (Purchaser)
- SF
- Ship From
- ST
- Ship To
Code designating the system/method of code structure used for Identification Code (67)
- 92
- Assigned by Buyer or Buyer's Agent
Code identifying a party or other code
- 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.
4 - 7 Buying party (Bill to) (N101=BY)
9 - 9 Ship point location code (vendor number) (N101=SF)
4 - 7 Ship to unit number (N101=ST)
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.
Identification number of the next higher hierarchical data segment that the data segment being described is subordinate to
- HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
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.
- I
- Item
Reference Identification
To specify identifying information
This segment is used at the item level only on RPC Order Status Reports. 2 iterations are required to return the price list number and customer reference or bin location number from the order.
Code qualifying the Reference Identification
- CR
- Customer Reference Number
- PL
- Price List Number
Baseline Item Data
To specify basic and most frequently used line item data
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
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.
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- PN
- Company Part Number
- SR
- Substitute Product Number
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
13 – 13 European Article Number (PO1 Qualifier=EN)
4 – 5 Sears’ Item Number (PO1 Qualifier=IN)
3 – 3 Sears’ SKU number (PO1 Qualifier=IZ)
1 – 24 Company Part Number (PO1 Qualifier=PN)
1 - 24 Substitute product number (PO1 Qualifier=SR)
12 – 12 U.P.C. Number (PO1 Qualifier=UP)
1 – 30 Vendor’s Style Number (PO1 Qualifier=VA)
1 – 15 Vendor’s Item Number (PO1 Qualifier= VN)
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- PN
- Company Part Number
- SR
- Substitute Product Number
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Identifying number for a product or service
See PO107
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- EN
- European Article Number (EAN) (2-5-5-1)
- IN
- Buyer's Item Number
- IZ
- Buyer's Size Code
- PN
- Company Part Number
- SR
- Substitute Product Number
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
- VA
- Vendor's Style Number
- VN
- Vendor's (Seller's) Item Number
Item Status Report
To specify detailed purchase order/item status
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.
- AS
- Available Now - Scheduled to Ship (date)
- ED
- Expect to Ship By (Date)
- IC
- Item Canceled
- ID
- Insufficient Information
- IN
- In Process
- NN
- Not in Process - No Shipping Schedule
- NY
- No Shipping Schedule
- PS
- In Process, Scheduled to Ship On (Date)
- QP
- Quantity Past Due
Date expressed as CCYYMMDD
Required when ISR01 contains code AS, ED, PS or RD
Code indicating the status reason
- A05
- Unable To Locate
- A13
- Other
- A15
- Business On Strike
- A17
- Customer Requested Future Delivery
- A18
- Missort
- A30
- Mechanical Breakdown
- A33
- Other Carrier-Related
- A37
- Damaged Rewrapped In Hub
- A42
- Holiday - Closed
- A43
- Weather or Natural Disaster Related
- A45
- Delivery Not Completed
- A80
- Item or Service Not Available
- A81
- Item or Service Not Available on Requested Date
- B12
- Connecting Line or Cartage Pick-Up
- C03
- Suspended at Customer Request
- C06
- Waiting Shipping Instructions
- C07
- Waiting for Customer Specified Carrier
- P01
- Processing Delay
- P03
- Production Falldown
- P04
- Held for Full Carrier Load
- T07
- Insufficient Delivery Time
- W04
- On Hold
- ZZZ
- Mutually Defined
Quantity
To specify quantity information
This segment is used only by RSOS and ISOS to specify a quantity associated with the previous ISR segment.
Summary
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
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.