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

X12 870 Drop Ship Order Status Report

X12 Release 5010

This X12 Transaction Set 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
  • ^ Repetition
EDI sample
  • Sample
View the latest version of this implementation guide as an interactive webpage
https://www.stedi.com/app/guides/view/dsco/drop-ship-order-status-report/01HBGR6KQS9PD444PJJB96DMJN
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
detail
HL Loop
HL
0100
Hierarchical Level
Max use 1
Required
PRF
0200
Purchase Order Reference
Max use 1
Required
Internal Vendor Number
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 identifying 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 identifying 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

Code indicating 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

Code indicating 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
I65
Repetition Separator
Required
String (AN)
Min 1Max 1

Type is not applicable; the repetition separator is a delimiter and not a data element; this field provides the delimiter used to separate repeated occurrences of a simple data element or a composite data structure; this value must be different than the data element separator, component element separator, and the segment terminator

^
Repetition Separator
ISA-12
I11
Interchange Control Version Number
Required
Identifier (ID)

Code specifying the version number of the interchange control segments

00501
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003
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 indicating sender's request for an interchange acknowledgment

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

Code indicating 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 where CC represents the first two digits of the calendar year

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 identifying the issuer of the standard; this code is used in conjunction with Data Element 480

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

005010
Standards Approved for Publication by ASC X12 Procedures Review Board through October 2003

Heading

ST
0100
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) is 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
0200
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

2
Prearranged Schedule or Agreement
BSR-02
847
Order/Item Code
Required
Identifier (ID)

Code identifying a group of orders and items

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

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

Vendor's Reference Number

Required
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

  • BSR04 indicates the date of this report from the sender.
Heading end

Detail

HL Loop
RequiredMax >1
HL
0100
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
0200
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

REF Internal Vendor Number
OptionalMax >1
Variants (all may be used)
Reason for ChangeVendor Order Number
REF
0870
Detail > HL Loop > Internal Vendor Number > REF

Reference Information

RequiredMax use 1

To specify identifying information

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

Code qualifying the Reference Identification

IA
Internal Vendor Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 50

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

Usage notes

Trading Partner ID is used as the first priority, otherwise the Dsco supplier ID will be utilized.

REF Internal Vendor Number end
REF Reason for Change
OptionalMax >1
Usage notes

See trading partner specific guides

REF
0870
Detail > HL Loop > Reason for Change > REF

Reference Information

RequiredMax use 1

To specify identifying information

Example
At least one of Reference Identification (REF-02) or Description (REF-03) is required
REF-01
128
Reference Identification Qualifier
Required
Identifier (ID)

Code qualifying the Reference Identification

TD
Reason for Change
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 50

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

Usage notes

The cancellation reason for the order assigned by the Supplier. For example: 'Out of stock'.

REF-03
352
Description
Optional
String (AN)

A free-form description to clarify the related data elements and their content

order_cancel_reason
Order Cancel Reason

Conditional

REF Reason for Change end
REF Vendor Order Number
OptionalMax >1
Variants (all may be used)
Internal Vendor NumberReason for Change
REF
0870
Detail > HL Loop > Vendor Order Number > REF

Reference Information

RequiredMax use 1

To specify identifying information

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

Code qualifying the Reference Identification

VN
Vendor Order Number
REF-02
127
Reference Identification
Optional
String (AN)
Min 1Max 50

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

Usage notes

Vendor's internal order number assigned to this Ship-To.

REF Vendor Order Number end
HL Loop
RequiredMax >1
HL
0100
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
1500
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
If either Product/Service ID Qualifier (PO1-12) or Product/Service ID (PO1-13) is present, then the other is required
If either Product/Service ID Qualifier (PO1-14) or Product/Service ID (PO1-15) is present, then the other is required
If either Product/Service ID Qualifier (PO1-16) or Product/Service ID (PO1-17) is present, then the other is required
If either Product/Service ID Qualifier (PO1-18) or Product/Service ID (PO1-19) 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

Line item number on the PO.

PO1-02
380
Quantity
Required
Decimal number (R)
Min 1Max 15

Numeric value of quantity

  • PO102 is quantity ordered.
Usage notes

Quantity being cancelled.

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

EA
Each
PO1-04
212
Unit Price
Required
Decimal number (R)
Min 1Max 15

Price per unit of product, service, commodity, etc.

Usage notes

The expected cost of the item being ordered.

Max with format: 9999.99 (The decimal place must be included)

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.
SK
Stock Keeping Unit (SKU)
PO1-07
234
Product/Service ID
Required
String (AN)
Min 1Max 70

Identifying number for a product or service

Usage notes

The SKU of the item. A limit of 70 characters is enforced. A SKU is required. If a SKU is not available you may duplicate the UPC or EAN to this field.

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)

BP
Buyer's Part Number
CB
Buyer's Catalog Number
E6
Contract Transfer Reason Code
EM
Equipment Identification Number
EN
EAN/UCC - 13
IB
International Standard Book Number (ISBN)
MG
Manufacturer's Part Number
UK
GTIN 14-digit Data Structure
UP
UCC - 12
PO1-09
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'E6': Cancel Reason in Text Form

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)

BP
Buyer's Part Number
CB
Buyer's Catalog Number
E6
Contract Transfer Reason Code
EM
Equipment Identification Number
EN
EAN/UCC - 13
IB
International Standard Book Number (ISBN)
MG
Manufacturer's Part Number
UK
GTIN 14-digit Data Structure
UP
UCC - 12
PO1-11
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'E6': Cancel Reason in Text Form

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

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

BP
Buyer's Part Number
CB
Buyer's Catalog Number
E6
Contract Transfer Reason Code
EM
Equipment Identification Number
EN
EAN/UCC - 13
IB
International Standard Book Number (ISBN)
MG
Manufacturer's Part Number
UK
GTIN 14-digit Data Structure
UP
UCC - 12
PO1-13
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'E6': Cancel Reason in Text Form

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

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

BP
Buyer's Part Number
CB
Buyer's Catalog Number
E6
Contract Transfer Reason Code
EM
Equipment Identification Number
EN
EAN/UCC - 13
IB
International Standard Book Number (ISBN)
MG
Manufacturer's Part Number
UK
GTIN 14-digit Data Structure
UP
UCC - 12
PO1-15
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'E6': Cancel Reason in Text Form

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

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

BP
Buyer's Part Number
CB
Buyer's Catalog Number
E6
Contract Transfer Reason Code
EM
Equipment Identification Number
EN
EAN/UCC - 13
IB
International Standard Book Number (ISBN)
MG
Manufacturer's Part Number
UK
GTIN 14-digit Data Structure
UP
UCC - 12
PO1-17
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'E6': Cancel Reason in Text Form

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

Code identifying the type/source of the descriptive number used in Product/Service ID (234)

BP
Buyer's Part Number
CB
Buyer's Catalog Number
E6
Contract Transfer Reason Code
EM
Equipment Identification Number
EN
EAN/UCC - 13
IB
International Standard Book Number (ISBN)
MG
Manufacturer's Part Number
UK
GTIN 14-digit Data Structure
UP
UCC - 12
PO1-19
234
Product/Service ID
Optional
String (AN)
Min 1Max 48

Identifying number for a product or service

Usage notes

When the Qualifier is 'UP': Universal Product Code (UPC)
When the Qualifier is 'EN': European Article Number (EAN)
When the Qualifier is 'IB': International Standard Book Number (ISBN)
When the Qualifier is 'UK': Global Trade Number (GTIN)
When the Qualifier is 'BP': Partner SKU
When the Qualifier is 'CB': Retailer Item Identifier
When the Qualifier is 'EM': Dsco Item ID
When the Qualifier is 'E6': Cancel Reason in Text Form

SLN
1600
Detail > HL Loop > HL Loop > PO1 Loop > SLN

Subline Item Detail

OptionalMax use 100

To specify product subline detail item data

Example
SLN-01
350
Assigned Identification
Required
String (AN)
Min 1Max 20

Alphanumeric characters assigned for differentiation within a transaction set

  • SLN01 is the identifying number for the subline item.
  • SLN01 is related to (but not necessarily equivalent to) the baseline item number. Example: 1.1 or 1A might be used as a subline number to relate to baseline number 1.
SLN-03
662
Relationship Code
Required
Identifier (ID)

Code indicating the relationship between entities

  • SLN03 is the configuration code indicating the relationship of the subline item to the baseline item.
O
Information Only
SLN-04
380
Quantity
Optional
Decimal number (R)
Min 1Max 15

Numeric value of quantity

Usage notes

line_item_original_order_quantity

ISR Loop
RequiredMax >1
ISR
2100
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.
IC
Item Canceled
Optional
Date (DT)
CCYYMMDD format

Date expressed as CCYYMMDD where CC represents the first two digits of the calendar year

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

Code indicating the status reason

Usage notes

See trading partner specific guides

030
Fraud
051
Vendor-Supplied Carrier Delay
A03
Incorrect Address
A05
Unable To Locate
A06
Address Corrected - Delivery Attempt
A07
Refused by Consignee
A13
Other
A58
Unable to Contact Recipient For Broker Information
A80
Item or Service Not Available
A82
Address Specified Does Not Match Account
A83
Unauthorized or Invalid Action
ABN
Abnormal
B14
Missing Documents
D01
Carrier Dispatch Error
D30
Declined Services
D50
Delayed
IV1
Failed Material Returned for Repair
MIN
Mental Incompetency
POA
Power of Attorney
RUN
Reason Unknown
SOW
Shipment Overweight
UCD
Unknown Cause of Delay
W01
Out of Stock
W05
Order Discrepancy
W13
Product Allocation Exceeded
ISR Loop end
PO1 Loop end
HL Loop end
HL Loop end
Detail end

Summary

CTT
0100
Summary > CTT

Transaction Totals

OptionalMax 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.
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

Total number of line items in the transaction set.

SE
0200
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

ST*870*000020001~
BSR*2*PP*789123456*20200313~
HL*1*0*O~
PRF*11150439~
REF*IA*3286495~
REF*VN*ST01173~
REF*TD*Out of Stock*order_cancel_reason~
HL*2*1*I~
PO1**3*EA*5.5**SK*98989898~
ISR*IC**W01~
HL*3*1*I~
PO1**1*EA*5.5**SK*999999~
ISR*IC**W01~
SE*14*000020001~

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.