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

X12 870 Retail 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 sample
  • Sample 870
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/target/retail-order-status-report/01HBRP7H89PZSEQG73G4WYJHVF
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
Department Number
N1 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

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

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

Usage notes

BSR3PP1220000312

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

Code indicating the reason for sending the report

3
Unsolicited Report

Send 3 for all Basic Replenishment purchase order exceptions

BSR-02
847
Order/Item Code
Required
Identifier (ID)

Code identifying a group of orders and items

PP
Selected Orders - Selected Items

Used when information affects selected items on a purchase order

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

Number assigned by the sender to identify the request within their application system

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • BSR04 indicates the date of this report from the sender.
Usage notes

Transmission Date

REF Department Number
RequiredMax >1
Variants (all may be used)
Internal Vendor Number
REF
046
Heading > Department Number > REF

Reference Identification

RequiredMax use 1

To specify identifying information

Usage notes

REFDP012

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

Code qualifying the Reference Identification

DP
Department Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 3

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

Usage notes

The 3-digit department number. This will be the same department number that was sent on the PO.

REF Department Number end
REF Internal Vendor Number
RequiredMax >1
Variants (all may be used)
Department Number
REF
046
Heading > Internal Vendor Number > REF

Reference Identification

RequiredMax use 1

To specify identifying information

Usage notes

REFIA1234567

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

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

REF-02
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

Usage notes

Target Corporation's vendor number.

REF Internal Vendor Number end
N1 Loop
OptionalMax >1
N1
050
Heading > N1 Loop > N1

Name

RequiredMax use 1

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

Usage notes

This N1 is not required by Target Corporation. It has been included for those vendors, whose system requires sending it.

N1BS**920551

Example
If either Identification Code Qualifier (N1-03) or Identification Code (N1-04) is present, then the other is required
N1-01
98
Entity Identifier Code
Required
Identifier (ID)

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

BS
Bill and Ship To
N1-03
66
Identification Code Qualifier
Optional
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
Optional
String (AN)
Min 2Max 4

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

This will be the 4 digit location code for the Ship To/Bill To location.

N1 Loop end
Heading end

Detail

HL Loop
RequiredMax >1
Usage notes

For Predistro an HL at Order Level must be sent for every Mark for Location.

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
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

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

Purchase Order Reference

RequiredMax use 1

To provide reference to a specific purchase order

Usage notes

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-1234567
20000312 (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.

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

Identifying number for Purchase Order assigned by the orderer/purchaser

Usage notes

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)

PRF-02
328
Release Number
Optional
String (AN)
Min 1Max 30

Number identifying a release against a Purchase Order previously placed by the parties involved in the transaction

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

  • PRF04 is the date assigned by the purchaser to purchase order.
Usage notes

Retailer's original purchase order date

N1 Loop
RequiredMax >1
N1
090
Detail > HL Loop > N1 Loop > N1

Name

RequiredMax use 1

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

Usage notes

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.

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

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

MA
Party for whom Item is Ultimately Intended
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 4

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

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.

N1 Loop end
HL Loop
RequiredMax >1
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
HL-04
736
Hierarchical Child Code
Optional
Identifier (ID)

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.
PO1 Loop
RequiredMax >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

Usage notes

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
PO1
199EA*
UP999999999999
PO1
199EA*CB099090999*UP999999999999

Example
If either Product/Service ID Qualifier (PO1-06) or Product/Service ID (PO1-07) is present, then the other is required
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.
Usage notes

The sequential number assigned to a PO line on the original purchase order.

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)

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

PO1-06
235
Product/Service ID Qualifier
Optional
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.
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

PO1-07
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

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)

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

PO1-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

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)

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

PO1-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

ISR Loop
RequiredMax >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

Usage notes

ISRCP20000312
ISR*IC

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.
CP
Partial Shipment on (Date), Considered No Backorder
IC
Item Canceled
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD

Usage notes

If ISR01 contains CP, then ISR02 is required

QTY
230
Detail > HL Loop > HL Loop > PO1 Loop > ISR Loop > QTY

Quantity

OptionalMax use 4

To specify quantity information

Usage notes

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

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

QTY-03
C001
Composite Unit of Measure
RequiredMax use 1
To identify a composite unit of measure (See Figures Appendix for examples of use)
C001-01
355
Unit or Basis for Measurement Code
Required
Identifier (ID)

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

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

Summary

CTT
010
Summary > CTT

Transaction Totals

RequiredMax use 1

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

CTT*99

Example
CTT-01
354
Number of Line Items
Required
Numeric (N0)
Min 1Max 6

Total number of line items in the transaction set

Usage notes

The number of HL segments present in the transaction set.

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

EDI Samples

Sample 870

ISA*00* *00* *ZZ*SENDER *ZZ*RECEIVER *231002*2353*U*00401*000000001*0*T*>
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.