Sears
/
Order Status Report
  • Specification
  • EDI Inspector
Import guide into your account
Stedi maintains this guide based on public documentation from Sears. Contact Sears for official EDI specifications. To report any errors in this guide, please contact us.
Go to Stedi Network
Sears logo

X12 870 Order Status Report

X12 Release 4010

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.

Delimiters
  • ~ Segment
  • * Element
  • > Component
EDI samples
  • None included
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/sears/order-status-report/01H4ND1HPMNPNWCEFGV8M1P89C
Powered by
Build EDI implementation guides at stedi.com
Overview
ISA
-
Interchange Control Header
Max use 1
Required
GS
-
Functional Group Header
Max use 1
Required
heading
ST
010
Transaction Set Header
Max use 1
Required
BSR
020
Beginning Segment for Order Status Report
Max use 1
Required
N1 Loop
detail
HL Loop
GE
-
Functional Group Trailer
Max use 1
Required
IEA
-
Interchange Control Trailer
Max use 1
Required
ISA

Interchange Control Header

RequiredMax use 1

To start and identify an interchange of zero or more functional groups and interchange-related control segments

Example
ISA-01
I01
Authorization Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Authorization Information

00
No Authorization Information Present (No Meaningful Information in I02)
ISA-02
I02
Authorization Information
Required
String (AN)
Min 10Max 10

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)

ISA-03
I03
Security Information Qualifier
Required
Identifier (ID)

Code to identify the type of information in the Security Information

00
No Security Information Present (No Meaningful Information in I04)
ISA-04
I04
Security Information
Required
String (AN)
Min 10Max 10

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)

ISA-05
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-06
I06
Interchange Sender ID
Required
String (AN)
Min 15Max 15

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

ISA-07
I05
Interchange ID Qualifier
Required
Identifier (ID)
Min 2Max 2

Qualifier to designate the system/method of code structure used to designate the sender or receiver ID element being qualified

Codes
ISA-08
I07
Interchange Receiver ID
Required
String (AN)
Min 15Max 15

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

ISA-09
I08
Interchange Date
Required
Date (DT)
YYMMDD format

Date of the interchange

ISA-10
I09
Interchange Time
Required
Time (TM)
HHMM format

Time of the interchange

ISA-11
I10
Interchange Control Standards Identifier
Required
Identifier (ID)

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
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

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
ISA-13
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

ISA-14
I13
Acknowledgment Requested
Required
Identifier (ID)
Min 1Max 1

Code sent by the sender to request an interchange acknowledgment (TA1)

0
No Acknowledgment Requested
1
Interchange Acknowledgment Requested
ISA-15
I14
Usage Indicator
Required
Identifier (ID)
Min 1Max 1

Code to indicate whether data enclosed by this interchange envelope is test, production or information

I
Information
P
Production Data
T
Test Data
ISA-16
I15
Component Element Separator
Required
String (AN)
Min 1Max 1

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

RequiredMax use 1

To indicate the beginning of a functional group and to provide control information

Example
GS-01
479
Functional Identifier Code
Required
Identifier (ID)

Code identifying a group of application related transaction sets

RS
Order Status Information (869, 870)
GS-02
142
Application Sender's Code
Required
String (AN)
Min 2Max 15

Code identifying party sending transmission; codes agreed to by trading partners

GS-03
124
Application Receiver's Code
Required
String (AN)
Min 2Max 15

Code identifying party receiving transmission. Codes agreed to by trading partners

GS-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

GS-05
337
Time
Required
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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)

GS-06
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

GS-07
455
Responsible Agency Code
Required
Identifier (ID)
Min 1Max 2

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
GS-08
480
Version / Release / Industry Identifier Code
Required
String (AN)

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

ST
010
Heading > ST

Transaction Set Header

RequiredMax use 1

To indicate the start of a transaction set and to assign a control number

Example
ST-01
143
Transaction Set Identifier Code
Required
Identifier (ID)

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
ST-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

BSR
020
Heading > BSR

Beginning Segment for Order Status Report

RequiredMax use 1

To indicate the beginning of an Order Status Report Transaction Set

Example
BSR-01
850
Status Report Code
Required
Identifier (ID)

Code indicating the reason for sending the report

1
Response to an Order Status Inquiry (869)
2
Prearranged Schedule or Agreement
3
Unsolicited Report
BSR-02
847
Order/Item Code
Required
Identifier (ID)

Code identifying a group of orders and items

PA
Selected Orders - All Items
PP
Selected Orders - Selected Items
BSR-03
127
Reference Identification
Required
String (AN)
Min 1Max 30

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.
BSR-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BSR04 indicates the date of this report from the sender.
BSR-07
337
Time
Optional
Time (TM)
HHMM, HHMMSS, HHMMSSD, or HHMMSSDD format

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.
BSR-08
127
Reference Identification
Optional
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

  • BSR08 indicates a status report document number assigned by the inquirer.
N1 Loop
OptionalMax >1
Usage notes

This segment is used only on RPC Order Status Reports to identify the supplier.

N1
050
Heading > N1 Loop > N1

Name

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

SF
Ship From
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

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.
Usage notes

6 - 6 Sears assigned supplier code

N1 Loop end
Heading end

Detail

HL Loop
RequiredMax 1000
HL
010
Detail > HL Loop > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

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
PRF
020
Detail > HL Loop > PRF

Purchase Order Reference

RequiredMax use 1

To provide reference to a specific purchase order

Example
PRF-01
324
Purchase Order Number
Required
String (AN)
Min 1Max 22

Identifying number for Purchase Order assigned by the orderer/purchaser

PRF-04
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • PRF04 is the date assigned by the purchaser to purchase order.
ISR Loop
OptionalMax >1
ISR
030
Detail > HL Loop > ISR Loop > ISR

Item Status Report

RequiredMax use 1

To specify detailed purchase order/item status

Example
ISR-01
368
Shipment/Order Status Code
Required
Identifier (ID)

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
ISR-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

ISR-03
641
Status Reason Code
Optional
Identifier (ID)

Code indicating the status reason

A05
Unable To Locate
C03
Suspended at Customer Request
C06
Waiting Shipping Instructions
P01
Processing Delay
ZZZ
Mutually Defined
ISR Loop end
DTM
080
Detail > HL Loop > DTM

Date/Time Reference

OptionalMax use 1

To specify pertinent dates and times

Example
DTM-01
374
Date/Time Qualifier
Required
Identifier (ID)

Code specifying type of date or time, or both date and time

068
Current Schedule Ship
DTM-02
373
Date
Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

REF Loop
RequiredMax 3
REF
087
Detail > HL Loop > REF Loop > REF

Reference Identification

RequiredMax use 1

To specify identifying information

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

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
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

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)

REF Loop end
N1 Loop
OptionalMax 3
N1
090
Detail > HL Loop > N1 Loop > N1

Name

RequiredMax use 1

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

Example
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

Code identifying an organizational entity, a physical location, property or an individual

BY
Buying Party (Purchaser)
SF
Ship From
ST
Ship To
N1-03
66
Identification Code Qualifier
Required
Identifier (ID)

Code designating the system/method of code structure used for Identification Code (67)

92
Assigned by Buyer or Buyer's Agent
N1-04
67
Identification Code
Required
String (AN)
Min 2Max 80

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.
Usage notes

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)

N1 Loop end
HL Loop
OptionalMax 1000
HL
010
Detail > HL Loop > HL Loop > HL

Hierarchical Level

RequiredMax use 1

To identify dependencies among and the content of hierarchically related groups of data segments

Example
HL-01
628
Hierarchical ID Number
Required
String (AN)
Min 1Max 12

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.
HL-02
734
Hierarchical Parent ID Number
Required
String (AN)
Min 1Max 12

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.
HL-03
735
Hierarchical Level Code
Required
Identifier (ID)

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
REF Loop
OptionalMax 2
REF
087
Detail > HL Loop > HL Loop > REF Loop > REF

Reference Identification

RequiredMax use 1

To specify identifying information

Usage notes

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.

Example
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

CR
Customer Reference Number
PL
Price List Number
REF-02
127
Reference Identification
Required
String (AN)
Min 1Max 30

Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier

Usage notes

5 - 5 Customer reference or bin location number
3 - 3 Price list number

REF Loop end
PO1 Loop
OptionalMax >1
PO1
150
Detail > HL Loop > HL Loop > PO1 Loop > PO1

Baseline Item Data

RequiredMax use 1

To specify basic and most frequently used line item data

Example
If either Product/Service ID Qualifier (PO1-08) or Product/Service ID (PO1-09) is present, then the other is required
If either Product/Service ID Qualifier (PO1-10) or Product/Service ID (PO1-11) is present, then the other is required
PO1-01
350
Assigned Identification
Optional
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • PO101 is the line item identification.
PO1-02
330
Quantity Ordered
Required
Decimal number (R)
Min 1Max 15

Quantity ordered

PO1-03
355
Unit or Basis for Measurement Code
Required
Identifier (ID)
Min 2Max 2

Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken

PO1-06
235
Product/Service ID Qualifier
Required
Identifier (ID)

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
PO1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

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)

PO1-08
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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
PO1-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

See PO107

PO1-10
235
Product/Service ID Qualifier
Optional
Identifier (ID)

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
PO1-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

See PO107

ISR Loop
OptionalMax >1
ISR
210
Detail > HL Loop > HL Loop > PO1 Loop > ISR Loop > ISR

Item Status Report

RequiredMax use 1

To specify detailed purchase order/item status

Example
ISR-01
368
Shipment/Order Status Code
Required
Identifier (ID)

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
ISR-02
373
Date
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

Required when ISR01 contains code AS, ED, PS or RD

ISR-03
641
Status Reason Code
Required
Identifier (ID)

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
QTY
230
Detail > HL Loop > HL Loop > PO1 Loop > ISR Loop > QTY

Quantity

OptionalMax use 1

To specify quantity information

Usage notes

This segment is used only by RSOS and ISOS to specify a quantity associated with the previous ISR segment.

Example
QTY-01
673
Quantity Qualifier
Required
Identifier (ID)

Code specifying the type of quantity

01
Discrete Quantity
QTY-02
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

ISR Loop end
PO1 Loop end
HL Loop end
HL Loop end
Detail end

Summary

SE
020
Summary > SE

Transaction Set Trailer

RequiredMax use 1

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

Example
SE-01
96
Number of Included Segments
Required
Numeric (N0)
Min 1Max 10

Total number of segments included in a transaction set including ST and SE segments

SE-02
329
Transaction Set Control Number
Required
Numeric (N)
Min 4Max 9

Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set

Summary end

Functional Group Trailer

RequiredMax use 1

To indicate the end of a functional group and to provide control information

Example
GE-01
97
Number of Transaction Sets Included
Required
Numeric (N0)
Min 1Max 6

Total number of transaction sets included in the functional group or interchange (transmission) group terminated by the trailer containing this data element

GE-02
28
Group Control Number
Required
Numeric (N0)
Min 1Max 9

Assigned number originated and maintained by the sender

Interchange Control Trailer

RequiredMax use 1

To define the end of an interchange of zero or more functional groups and interchange-related control segments

Example
IEA-01
I16
Number of Included Functional Groups
Required
Numeric (N0)
Min 1Max 5

A count of the number of functional groups included in an interchange

IEA-02
I12
Interchange Control Number
Required
Numeric (N0)
Min 9Max 9

A control number assigned by the interchange sender

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.