X12 870 Retail 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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
Beginning Segment for Order Status Report
To indicate the beginning of an Order Status Report Transaction Set
BSR3PP1220000312
Code indicating the reason for sending the report
- 3
- Unsolicited Report
Send 3 for all Basic Replenishment purchase order exceptions
Code identifying a group of orders and items
- PP
- Selected Orders - Selected Items
Used when information affects selected items on a purchase order
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.
Number assigned by the sender to identify the request within their application system
Date expressed as CCYYMMDD
- BSR04 indicates the date of this report from the sender.
Transmission Date
Reference Identification
To specify identifying information
REFDP012
Code qualifying the Reference Identification
- DP
- Department Number
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
The 3-digit department number. This will be the same department number that was sent on the PO.
Reference Identification
To specify identifying information
REFIA1234567
Code qualifying the Reference Identification
- IA
- Internal Vendor Number
Identification number assigned to the vendor, by the retailer, for use within the retailer's system
Reference information as defined for a particular Transaction Set or as specified by the Reference Identification Qualifier
Target Corporation's vendor number.
Name
To identify a party by type of organization, name, and code
This N1 is not required by Target Corporation. It has been included for those vendors, whose system requires sending it.
N1BS**920551
Code identifying an organizational entity, a physical location, property or an individual
- BS
- Bill and 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.
This will be the 4 digit location code for the Ship To/Bill To location.
Detail
For Predistro an HL at Order Level must be sent for every Mark for Location.
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.
- 1
- Additional Subordinate HL Data Segment in This Hierarchical Structure.
Purchase Order Reference
To provide reference to a specific purchase order
NOTE: Starting in Dec 2017, Target will start phasing in a new PO format. The new format removes the 4-digit department number prefix and the purchase order number will be moving from 7 digits to 11 digits. No changes are being made to the location number. During this transition, your company needs to be able to receive both PO formats, as both may be received during transition. The same PO format received from Target will need to be returned on all EDI related documents for that PO to ensure no business interruption.
Sample PRF Segment
PRF1234-0456789-123420000312 (Basic and SDQ VCD)
PRF1234-123456720000312 (SDQ non-VCD)
PRF1234-0456789-1234**20000312 (Predistro)
The information needed for this segment can be found in the BEG segment of the original EDI 850 Purchase Order.
Identifying number for Purchase Order assigned by the orderer/purchaser
PO Number Format:
Basic and SDQ VCD: SSSS-PPPPPPP-LLLL
SDQ: SSSS-PPPPPPP
Predistro: SSSS-PPPPPPP-LLLL
(LLLL = the Mark For Location)
New PO Format:
Basic and SDQ VCD: PPPPPPPPPPP-LLLL
Predistro: PPPPPPPPPPP-LLLL
(LLLL = the Mark For Location)
Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction
Date expressed as CCYYMMDD
- PRF04 is the date assigned by the purchaser to purchase order.
Retailer's original purchase order date
Name
To identify a party by type of organization, name, and code
PLEASE NOTE: For Predistro, this N1 MUST contain the Mark for Store Location.
Our system only accepts one (1) N1. If your system is designed to send two (2), we will only map the first one in your transmission. Make certain the first one contains the location to be updated."
Sample N1 Segment
N1ST**920999
For every Mark for Location, an HL at Order Level must be sent.
When N101 equals 'MA,' this will be the Target Corporation location the goods are marked for.
When N101 equals 'ST,' this will be the Target Corporation location the goods will be shipped to.
Please send only one N1 segment. Multiple N1 segments may cause your transaction to fail. If the PO you received is allocated to the stores, the N1 must contain the store location. If the PO you received was not allocated at store level, send the DC location in the N1.
Code identifying an organizational entity, a physical location, property or an individual
- MA
- Party for whom Item is Ultimately Intended
- 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.
When N101 equals 'MA,' this will be the Target Corporation location the goods are marked for.
When N101 equals 'ST,' this will be the Target Corporation location the goods will be shipped to.
A four (4) character field.
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
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.
Baseline Item Data
To specify basic and most frequently used line item data
NOTE: IN will be used as an item identifier for Target in the future. When this item identifier is sent by Target, your system must be capable of sending it back on inbound EDI documents to Target.
May send either the Target Corporation SKU or the UPC code, or the EAN - it is not necessary to send all. However, if sending the UPC code or the EAN, it must be the same as the one sent on the original purchase order.
Sample PO1 Segment
PO1199EACB099090999
PO1199EA*UP999999999999
PO1199EA*CB099090999*UP999999999999
Alphanumeric characters assigned for differentiation within a transaction set
- PO101 is the line item identification.
The sequential number assigned to a PO line on the original purchase order.
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
for future use
- EA
- Each
- LB
- Pound
for future use
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.
- CB
- Buyer's Catalog Number
Target Corporation's SKU (DPCI), consisting of Target Corporation's Department (PIC X3), Class (PIC X2), and Item (PIC X4).
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC - 8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Full 12-digit UPC
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
Target Corporation's SKU (DPCI), consisting of Target Corporation's Department (PIC X3), Class (PIC X2), and Item (PIC X4).
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC - 8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Full 12-digit UPC
Identifying number for a product or service
Code identifying the type/source of the descriptive number used in Product/Service ID (234)
- CB
- Buyer's Catalog Number
Target Corporation's SKU (DPCI), consisting of Target Corporation's Department (PIC X3), Class (PIC X2), and Item (PIC X4).
- EN
- European Article Number (EAN) (2-5-5-1)
- EO
- EAN/UCC - 8
- IN
- Buyer's Item Number
Target Corporation Item Number (TCIN)
- UP
- U.P.C. Consumer Package Code (1-5-5-1)
Full 12-digit UPC
Identifying number for a product or service
Item Status Report
To specify detailed purchase order/item status
ISRCP20000312
ISR*IC
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.
- CP
- Partial Shipment on (Date), Considered No Backorder
- IC
- Item Canceled
Date expressed as CCYYMMDD
If ISR01 contains CP, then ISR02 is required
Quantity
To specify quantity information
This segment is required when ISR is sent at an item level.
The quantity used with ISR code "CP" must be the number of eaches that will be shipped within the original ship/cancel window. This is the quantity you need to send to Target Corporation. The ONLY value acceptable for the QTY02, when an "IC" code is used, is zero (0).
Sample QTY Segment
QTY01120*EA
Code specifying the units in which a value is being expressed, or manner in which a measurement has been taken
- CA
- Case
for future use
- EA
- Each
- LB
- Pound
for future use
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.
CTT*99
Total number of line items in the transaction set
The number of HL segments present in the transaction set.
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
Identifying control number that must be unique within the transaction set functional group assigned by the originator for a transaction set
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
Assigned number originated and maintained by the sender
Interchange Control Trailer
To define the end of an interchange of zero or more functional groups and interchange-related control segments
Sample 870
GS*RS*SENDERGS*RECEIVERGS*20231002*235331*000000001*X*004010
ST*870*0001
BSR*3*PP*12*20000312
REF*IA*1234567
REF*DP*012
N1*BS**92*0551
HL*1**O
PRF*1234-0456789-1234***20000312
N1*ST**92*0999
HL*2*1*I
PO1*1*99*EA***CB*099090999*UP*999999999999
ISR*CP*20000312
QTY*01*120*EA
CTT*99
SE*14*0001
GE*1*000000001
IEA*1*000000001
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.