X12 870 Order Status Report
This standard provides the format and establishes the data contents of an order status report transaction set. The order status report transaction set provides the ability to report on the current status of 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 report format allows for the inclusion of ``reasons'' relative to the status of the purchase order(s). This transaction set may also be used to update the supplier's scheduled shipment or delivery date(s). This transaction set can result from either an inquiry (via the Order Status Inquiry Transaction Set [869]) or a prearranged schedule agreed to by the trading partners.
- ~ Segment
- * Element
- > Component
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.
Date sender generated a functional group of transaction sets.
Time (HHMM) when the sender generated a functional group of transaction sets (local time at sender's location).
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. 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).
- 003010
- Draft Standards Approved By ASC X12 Through June 1990.
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) 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).
- 870
- X12.23 Order Status Report
Beginning Segment for Order Status Report
To indicate the beginning of an Order Status Report.
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.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
- BSR03 indicates a status report document number assigned by the sender.
Note/Special Instruction
To transmit information in a free-form format, if necessary, for comment or special instruction
Code qualifying the Reference Number.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
- Either REF02 or REF03 is required.
Name
To identify a party by type of organization, name and code
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
Free-form name.
- If either N103 or N104 is present, then the other is required.
Code designating the system/method of code structure used for Identification Code (67).
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
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 whether 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
Identifying number for Purchase Order assigned by the orderer/purchaser.
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction.
Reference Numbers
To specify identifying numbers.
Code qualifying the Reference Number.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
- Either REF02 or REF03 is required.
Date/Time Reference
To specify pertinent dates and times
Purchase Order Baseline Item Data
To specify basic and most frequently used purchase order line item data
Alphanumeric characters assigned for differentiation within a transaction set.
- PO101 is the line item identification
- If PO105 is present, then PO104 is required.
Quantity ordered.
- If PO106 is present, then PO107 is required.
Code identifying the basic unit of measurement.
- If PO108 is present, then PO109 is required.
Price per unit of product, service, commodity, etc.
- If PO110 is present, then PO111 is required.
Code identifying the type of unit price for an item.
- If PO112 is present, then PO113 is required.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- PO106 through PO125 provide for ten (10) different product/service ID's per each item. For example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
- If PO114 is present, then PO115 is required.
- BP
- Buyer's Part Number
Identifying number for a product or service.
- If PO116 is present, then PO117 is required.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If PO118 is present, then PO119 is required.
Identifying number for a product or service.
- If PO120 is present, then PO121 is required.
Code identifying the type/source of the descriptive number used in Product/Service ID (234).
- If PO122 is present, then PO123 is required.
- RN
- Release 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.
Quantity
To specify quantity information.
Name
To identify a party by type of organization, name and code
Code identifying an organizational entity or a physical location.
- At least one of N102 or N103 must be present.
Free-form name.
- If either N103 or N104 is present, then the other is required.
Code designating the system/method of code structure used for Identification Code (67).
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.
Carrier Details (Quantity and Weight)
To specify the transportation details relative to commodity, weight and quantity.
Number of units (pieces) of the lading commodity.
- If TD103 is present, then TD104 is required.
Code describing a commodity or group of commodities.
Reference Numbers
To specify identifying numbers.
Code qualifying the Reference Number.
Reference number or identification number as defined for a particular Transaction Set, or as specified by the Reference Number Qualifier.
- Either REF02 or REF03 is required.
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.
Total number of line items in the transaction set.
- If CTT03 is present, then CTT04 is required.
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.
-.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.
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).
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.
sample 1
GS*RS*BTCXA*AF1CC*240311*1623*254855*X*003010~
ST*870*0001~
BSR*2*PO*2403111623*240311~
N1*BY**92*AF1CC~
N1*SE**92*BTCXA~
HL*1**O~
PRF*YG0ZQ0***240312~
REF*IT*09049~
REF*CR*1468204~
PO1*1*1*EA***BP*VFL3Z 84501A42 EA~
ISR*EA*240314~
QTY*01*1*EA~
CTT*1*1~
SE*13*0001~
GE*1*254855~
IEA*1*000254854~
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.