Amazon 856 - Direct Fulfillment Advance Shipment Specifications

Modified on Tue, May 26 at 9:47 AM

**These specifications are a base model. All customers are responsible for ensuring their map or EDI is compliant with their trading partner's most current specifications.

Direct Fulfillment X12 856 ASN

X12/V4010/856: Advance Shipment Notification

Version: 2.2 Final

Company:	Amazon.com
Created:	1/14/2015
Modified:	12/14/2023

856 Ship Notice/Manifest

Functional Group=SH

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set (856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to convey information. The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the contents of a shipment or information about the contents of a shipment.

Not Defined

Pos	Id	Segment Name	Req	Max Use	Repeat	Notes	Usage
	ISA	Interchange Control Header	M	1			Must use
	GS	Functional Group Header	M	1			Must use

Heading

Pos	Id	Segment Name	Req	Max Use	Repeat	Notes	Usage
010	ST	Transaction Set Header	M	1			Must use
020	BSN	Beginning Segment for Ship Notice	M	1			Must use

Detail

Pos	Id	Segment Name	Req	Max Use	Repeat	Notes	Usage
	LOOP ID - HL				200000	C2/010L
010	HL	Hierarchical Level	M	1		C2/010	Must use
050	PRF	Purchase Order Reference	M	1			Must use
	LOOP ID - N1				200
220	N1	Name	M	1			Must use
	LOOP ID - HL				200000	C2/010L
010	HL	Hierarchical Level	M	1		C2/010	Must use
020	LIN	Item Identification	M	1			Must use
030	SN1	Item Detail (Shipment)	M	1			Must use
040	SLN	Subline Item Detail	C	1000			Dependent
190	MAN	Marks and Numbers	M	>1			Must use
	LOOP ID - HL				200000	C2/010L
010	HL	Hierarchical Level	M	1		C2/010	Must use
110	TD1	Carrier Details (Quantity and Weight)	M	1			Must use
120	TD5	Carrier Details (Routing Sequence/Transit Time)	M	1			Must use
120	TD5	Carrier Details (Routing Sequence/Transit Time)	C	12			Dependent
190	MAN	Marks and Numbers	M	1			Must use
200	DTM	Date/Time Reference	M	10			Must use
200	DTM	Date/Time Reference	M	10			Must use

Summary

Pos	Id	Segment Name	Req	Max Use	Repeat	Notes	Usage
010	CTT	Transaction Totals	M	1		N3/010	Must use
020	SE	Transaction Set Trailer	M	1			Must use
	GE	Functional Group Trailer	M	1			Must use
	IEA	Interchange Control Trailer	M	1			Must use

ISA Interchange Control Header
Pos:	Max: 1	Loop: N/A	Not Defined - Mandatory	Elements: 16
User Option (Usage): Must use

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

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
ISA01	I01	Authorization Information Qualifier Notes: Always '00'	M	ID	2/2
ISA02	I02	Authorization Information Notes: Always 10 blank spaces.	M	AN	10/10
ISA03	I03	Security Information Qualifier Notes: Always '00'	M	ID	2/2
ISA04	I04	Security Information Notes: Always 10 blank spaces.	M	AN	10/10
ISA05	I05	Interchange ID Qualifier Notes: This will be the Vendor's ISA Qualifier	M	ID	2/2
ISA06	I06	Interchange Sender ID Notes: This field will contain the vendor's sender ISA ID.	M	AN	15/15
ISA07	I05	Interchange ID Qualifier Notes: Always 'ZZ'	M	ID	2/2
ISA08	I07	Interchange Receiver ID Notes: Always 'AMAZONDS'	M	AN	15/15
ISA09	I08	Interchange Date Notes: Date of interchange. Date formatted YYMMDD.	M	DT	6/6
ISA10	I09	Interchange Time Notes: Time of interchange. Time formatted HHMM.	M	TM	4/4
ISA11	I10	Interchange Control Standards Identifier Notes: Always "U"	M	ID	1/1
ISA12	I11	Interchange Control Version Number Notes: Always "00401"	M	ID	5/5
ISA13	I12	Interchange Control Number Notes: A unique control number assigned by the interchange sender	M	N0	9/9
ISA14	I13	Acknowledgment Requested Notes: Always '1'	M	ID	1/1
ISA15	I14	Usage Indicator Notes: Use "P" for Production, "T" for Test	M	ID	1/1
ISA16	I15	Component Element Separator Notes: Always ">"	M		1/1

Code Values:

Code	Name
00	No Authorization Information Present (No Meaningful Information in I02)
00	No Security Information Present (No Meaningful Information in I04)
ZZ	Mutually Defined
00401	Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures Review Board through October 1997
1	Interchange Acknowledgment Requested
P	Production Data
T	Test Data

Segment Usage: Only one ISA/IEA loop per data file allowed.

Example: ISA*00* *00* *ZZ*SENDERID *ZZ*AMAZONDS *231214*1908*U*00401*100038823*1*P*>

GS Functional Group Header
Pos:	Max: 1	Loop: N/A	Not Defined - Mandatory	Elements: 8
User Option (Usage): Must use

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

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
GS01	479	Functional Identifier Code Notes: Always "SH"	M	ID	2/2
GS02	142	Application Sender's Code Notes: This is the vendor's GS ID.	M	AN	2/15
GS03	124	Application Receiver's Code Notes: Always 'AMAZONDS'	M	AN	2/15
GS04	373	Date Notes: Date. Always CCYYMMDD.	M	DT	8/8
GS05	337	Time Notes: Interchange Time. Either HHMM or HHMMSS are allowed.	M	TM	4/8
GS06	28	Group Control Number Notes: Group Control Number assigned by sender	M	N0	1/9
GS07	455	Responsible Agency Code Notes: Always "X"	M	ID	1/2
GS08	480	Version / Release / Industry Identifier Code Notes: Always "004010"	M	AN	1/12

Code Values:

Code	Name
SH	Ship Notice/Manifest (856)
X	Accredited Standards Committee X12
004010	Draft Standards Approved for Publication by ASC X12 Procedures Review Board through October 1997

Segment Usage: Only one GS/GE loop is allowed per transmission.

Example: GS*SH*SENDERID*AMAZONDS*20231214*1908*39823*X*004010

ST Transaction Set Header
Pos: 010	Max: 1	Loop: N/A	Heading - Mandatory	Elements: 2
User Option (Usage): Must use

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

Element Summary:

Ref Id

Element Name

Req

Type

Min/Max

ST01

143

Transaction Set Identifier Code

Notes: Always "856"

3/3

ST02

329

Transaction Set Control Number

Notes: Transaction Control Number assigned by sender

4/9

Code Values:

Code	Name
856	Ship Notice/Manifest

Segment Usage: One ST/SE loop represents the shipping confirmation for a single order number/ ship ID. Multiple ST/SE loops are only allowed if they are for the same message type.

Example: ST*856*39823

BSN Beginning Segment for Ship Notice
Pos: 020	Max: 1	Loop: N/A	Heading - Mandatory	Elements: 6
User Option (Usage): Must use

Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
BSN01	353	Transaction Set Purpose Code Notes: Always "00"	M	ID	2/2
BSN02	396	Shipment Identification Notes: Vendor's internal shipment identification number.	M	AN	2/30
BSN03	373	Date Notes: Date of the ASN. Date format CCYYMMDD.	M	DT	8/8
BSN04	337	Time Notes: Time of the ASN. Format: HHMMSS.	M	TM	4/8
BSN05	1005	Hierarchical Structure Code Notes: Always 'ZZZZ'	O	ID	4/4
BSN06	640	Transaction Type Code Notes: If the entire shipment has been sent, use "AS". If the entire shipment has been cancelled (full floor denial), use "72". Note that partial fulfillment or shipment is not allowed. If any items from the order cannot be fulfilled, the entire shipment needs to be cancelled.	M	ID	2/2

Code Values:

Code	Name
00	Original
ZZZZ	Mutually Defined
72	Termination — If the entire shipment has been rejected then use '72'
AS	Shipment Advice — If the shipment has been sent then use 'AS'

Segment Usage: This segment provides the ASN ID, date, and appropriate usage code.

Example: BSN*00*S123456*20231214*1908*ZZZZ*AS~

Loop Hierarchical Level - Order

Pos: 010 Repeat: 200000 Loop: HL Mandatory

Loop Summary:

Pos	Id	Segment Name	Req	Max Use	Repeat	Usage
010	HL	Hierarchical Level	M	1		Must use
050	PRF	Purchase Order Reference	M	1		Must use
220	Loop N1		M	200		Must use
010	Loop HL		M	200000		Must use

HL Hierarchical Level (Order)
Pos: 010	Max: 1	Loop: HL	Detail - Mandatory	Elements: 2
User Option (Usage): Must use

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

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
HL01	628	Hierarchical ID Number	M	AN	1/12
HL03	735	Hierarchical Level Code	M	ID	1/2

Code Values:

Code	Name
O	Order — Always 'O'

Segment Usage: The looping structure for the Direct Fulfillment 856 is Order, Item, Pack. Review the sample files included in this package for DF ASN use cases and associated looping structures. For a floor denial ASN, do not include Pack loops or any associated Package ID's (BSN06 = 72).

Example: HL*1**O

PRF Purchase Order Reference
Pos: 050	Max: 1	Loop: HL	Detail - Mandatory	Elements: 2
User Option (Usage): Must use

Purpose: To provide reference to a specific purchase order

Element Summary:

Ref Id

Element Name

Req

Type

Min/Max

PRF01

324

Purchase Order Number

Notes: This needs to be same ship ID/ PO Number as received in the corresponding 850 and sent in the 855. Please note that the PO number is case sensitive.

1/22

PRF06

367

Contract Number

Notes: Vendor Order Reference Number. The vendor's internal order number (e.g., sales order number).

1/30

Segment Usage: This segment provides the related Amazon order number, as well as the vendor's order reference number. Note that the Amazon order number is case sensitive and must match the one provided in the original 850 message (BEG03).

Example: PRF*TSH4CjKCk*****5547416

Loop Name

Pos: 220 Repeat: 200 Loop: N1 Mandatory

Loop Summary:

Pos	Id	Segment Name	Req	Max Use	Repeat	Usage
220	N1	Name	M	1		Must use

N1 Name
Pos: 220	Max: 1	Loop: N1	Detail - Mandatory	Elements: 4
User Option (Usage): Must use

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

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
N101	98	Entity Identifier Code Notes: Always 'SF'	M	ID	2/3
N102	93	Name Notes: This will be the Amazon code representing the warehouse the order is shipping from. This is usually a four character code (e.g., ABCD) and is provided on the corresponding 850.	M	AN	1/60
N103	66	Identification Code Qualifier Notes: Always '92'	M	ID	1/2
N104	67	Identification Code Notes: This will be the Amazon code representing the warehouse the order is shipping from. This is usually a four character code (e.g., ABCD) and is provided on the corresponding 850.	M	AN	2/80

Code Values:

Code	Name
SF	Ship From — Always 'SF'
92	Assigned by Buyer or Buyer's Agent — Always '92'

Segment Usage: This segment provides the Amazon code representing the vendor's ship-from warehouse for this order. This should match the ship-from warehouse indicated on the corresponding 850.

Example: N1*SF*ABCD*92*ABCD

Loop Hierarchical Level - Item

Pos: 010 Repeat: 200000 Loop: HL Mandatory

Loop Summary:

Pos	Id	Segment Name	Req	Max Use	Repeat	Usage
010	HL	Hierarchical Level	M	1		Must use
020	LIN	Item Identification	M	1		Must use
030	SN1	Item Detail (Shipment)	M	1		Must use
040	SLN	Subline Item Detail	C	1000		Dependent
190	MAN	Marks and Numbers	M	>1		Must use
010	Loop HL		M	200000		Must use

HL Hierarchical Level (Item)
Pos: 010	Max: 1	Loop: HL	Detail - Mandatory	Elements: 2
User Option (Usage): Must use

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

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
HL01	628	Hierarchical ID Number	M	AN	1/12
HL03	735	Hierarchical Level Code	M	ID	1/2

Code Values:

Code	Name
I	Item — Always 'I'

Example: HL*2**I

LIN Item Identification
Pos: 020	Max: 1	Loop: HL	Detail - Mandatory	Elements: 3
User Option (Usage): Must use

Purpose: To specify basic item identification data

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
LIN01	350	Assigned Identification Notes: The item line number needs to match the PO101 in the 850 and PO101 in the 855 for the particular line item.	M	AN	1/20
LIN02	235	Product/Service ID Qualifier Notes: Always "SK"	O	ID	2/2
LIN03	234	Product/Service ID Notes: Item or product ID. Needs to match the value in the LIN03 from the corresponding 850 and 855 messages.	M	AN	1/48

Code Values:

Code	Name
SK	Stock Keeping Unit (SKU)

Segment Usage: This segment provides the line item number and product ID.

Example: LIN*1*SK*123456789

SN1 Item Detail (Shipment)
Pos: 030	Max: 1	Loop: HL	Detail - Mandatory	Elements: 6
User Option (Usage): Must use

Purpose: To specify line-item detail relative to shipment

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
SN101	350	Assigned Identification Notes: AlphaNumeric characters assigned for differentiation within a transaction set. The item line number needs to match the 850, 855, and the LIN01 in this 856.	M	AN	1/20
SN102	382	Number of Units Shipped Notes: Quantity shipped for the line item.	M	R	1/10
SN103	355	Unit or Basis for Measurement Code Notes: Always 'EA'	M	ID	2/2
SN105	330	Quantity Ordered Notes: Original order quantity from the corresponding 850.	M	R	1/15
SN106	355	Unit or Basis for Measurement Code Notes: Always 'EA'	M	ID	2/2
SN108	668	Line Item Status Code Notes: Use 'IA' if all the items in order are accepted. Use 'IR' if any item in the order is not available for shipment.	M	ID	2/2

Code Values:

Code	Name
EA	Each — Always 'EA'
IA	Item Accepted — IA if all the units of the item are sent.
IR	Item Rejected — IR if all or any of the items are cancelled or unavailable for shipment (floor denial).

Segment Usage: This segment provides the line item ID, quantity shipped, ordered quantity, and status code for the line item.

Example: SN1*1*3*EA**3*EA**IA

SLN Subline Item Detail
Pos: 040	Max: 1000	Loop: HL	Detail - Conditional	Elements: 1
User Option (Usage): Dependent

Purpose: To specify product subline detail item data

Element Summary:

Ref Id

Element Name

Req

Type

Min/Max

SLN04

380

Quantity

Notes: The cancelled item quantity relating to the line item's SN1 segment (Ordered quantity: SN105).

1/15

Segment Usage: This segment provides the rejected item quantity and is required for a floor denial ASN (BSN06 = 72).

Example: SLN****2

MAN Marks and Numbers (Item Level)
Pos: 190	Max: >1	Loop: HL	Detail - Mandatory	Elements: 2
User Option (Usage): Must use

Purpose: To indicate identifying marks and numbers for shipping containers

Element Summary:

Ref Id

Element Name

Req

Type

Min/Max

MAN01

Marks and Numbers Qualifier

Notes: This field is required. Always 'R'.

1/2

MAN02

Marks and Numbers

Notes: Vendor assigned unique package ID. The package ID from the MAN02 at the Item Level should match the ID used in the MAN02 at the corresponding Package Level.

1/48

Code Values:

Code	Name
R	Originator Assigned — Always 'R'

Segment Usage: This segment is used to provide the vendor assigned package ID for the shipped item. Please note that this is a vendor generated ID and allows for the item to be associated with the corresponding package. Not required for floor denial.

Example: MAN*R*01111178760019599973

Loop Hierarchical Level - Package

Pos: 010 Repeat: 200000 Loop: HL Mandatory

Loop Summary:

Pos	Id	Segment Name	Req	Max Use	Repeat	Usage
010	HL	Hierarchical Level	M	1		Must use
110	TD1	Carrier Details (Quantity and Weight)	M	1		Must use
120	TD5	Carrier Details (Routing Sequence/Transit Time)	M	1		Must use
120	TD5	Carrier Details (Routing Sequence/Transit Time)	C	12		Dependent
190	MAN	Marks and Numbers	M	1		Must use
200	DTM	Date/Time Reference	M	10		Must use
200	DTM	Date/Time Reference	M	10		Must use

HL Hierarchical Level (Package)
Pos: 010	Max: 1	Loop: HL	Detail - Mandatory	Elements: 2
User Option (Usage): Must use

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

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
HL01	628	Hierarchical ID Number	M	AN	1/12
HL03	735	Hierarchical Level Code	M	ID	1/2

Code Values:

Code	Name
P	Pack — Always 'P'

Segment Usage: Package loop. Not required for floor denial.

Example: HL*3**P

TD1 Carrier Details (Quantity and Weight)
Pos: 110	Max: 1	Loop: HL	Detail - Mandatory	Elements: 3
User Option (Usage): Must use

Purpose: To specify the transportation details relative to commodity, weight, and quantity

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
TD106	187	Weight Qualifier Notes: Always 'Z'	M	ID	1/2
TD107	81	Weight Notes: Weight expressed with two decimals. (e.g., 1.88)	M	R	1/10
TD108	355	Unit or Basis for Measurement Code	M	ID	2/2

Code Values:

Code	Name
Z	Mutually Defined — Always 'Z'
KG	Kilogram
LB	Pound

Segment Usage: This segment used to communicate the package weight. Not required for floor denial.

Example: TD1******Z*25.35*LB | TD1******Z*2.5*KG

TD5 Carrier Details (Routing Sequence/Transit Time) - Mandatory
Pos: 120	Max: 1	Loop: HL	Detail - Mandatory	Elements: 2
User Option (Usage): Must use

Purpose: To specify the carrier and sequence of routing and provide transit time information

Element Summary:

Ref Id

Element Name

Req

Type

Min/Max

TD502

Identification Code Qualifier

Notes: Always '92'

1/2

TD503

Identification Code

2/80

Code Values:

Code	Name
92	Assigned by Buyer or Buyer's Agent — Always '92'

Segment Usage: This segment is used to communicate the Amazon ship method code. This should match the provided code from the 850. Not required for floor denial. The Amazon defined code indicates the shipping carrier and shipment service level. The value in this field is case sensitive and format sensitive. The value sent in the 850 should be the value returned in the corresponding 856. To obtain the full list of DF ship methods in use, see the EDI Resources help page in Vendor Central.

Example: TD5**92*UPS_GR_RES

TD5 Carrier Details (Routing Sequence/Transit Time) - Conditional
Pos: 120	Max: 12	Loop: HL	Detail - Conditional	Elements: 2
User Option (Usage): Dependent

Purpose: To specify the carrier and sequence of routing and provide transit time information

Element Summary:

Ref Id

Element Name

Req

Type

Min/Max

TD502

Identification Code Qualifier

1/2

TD503

Identification Code

Notes: Carrier SCAC

2/80

Code Values:

Code	Name
2	Standard Carrier Alpha Code (SCAC)

Segment Usage: This TD5 segment provides the carrier SCAC and is only required for the Vendor Own Carrier (VOC) program. Not required for floor denial.

Example: TD5**2*PGLI

MAN Marks and Numbers (Package Level)
Pos: 190	Max: 1	Loop: HL	Detail - Mandatory	Elements: 5
User Option (Usage): Must use

Purpose: To indicate identifying marks and numbers for shipping containers

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
MAN01	88	Marks and Numbers Qualifier Notes: Always 'R'	M	ID	1/2
MAN02	87	Marks and Numbers Notes: Vendor assigned package ID. The MAN02 at Package Level should match the MAN02 at Line Item Level. This allows for an item to be associated with its corresponding package.	M	AN	1/48
MAN03	87	Marks and Numbers Notes: Manifest Number	M	AN	1/48
MAN04	88	Marks and Numbers Qualifier Notes: CP if Carrier-Assigned (small parcel). CP is for small parcel tracking numbers (e.g. UPS, FedEx). SM if Shipper-Assigned (LTL shipments). SM indicates that the MAN05 contains the shipper's BOL number.	M	ID	1/2
MAN05	87	Marks and Numbers Notes: Carrier assigned package tracking ID for small parcel or the BOL number for LTL pallet.	M	AN	1/48

Code Values:

Code	Name
R	Originator Assigned — Always 'R'
CP	Carrier-Assigned Package ID Number — for small parcel tracking numbers (e.g. UPS, FedEx)
SM	Shipper Assigned — indicates that MAN05 contains the shipper's BOL number (LTL shipments)

Segment Usage: This segment is used to communicate vendor package ID, manifest number, and carrier package tracking number (or BOL number for LTL). Note that the carrier package tracking number has to be unique for every package in a small parcel shipment. For LTL shipments, the BOL can repeat for multiple shipping units/ pallets. Not required for floor denial.

Example: MAN*R*11111878760019599973*11187601112907239*CP*1LA1111M0399059008

DTM Date/Time Reference (Ready to Ship)
Pos: 200	Max: 10	Loop: HL	Detail - Mandatory	Elements: 4
User Option (Usage): Must use

Purpose: To specify pertinent dates and times

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
DTM01	374	Date/Time Qualifier Notes: Always 'ZZZ'	M	ID	3/3
DTM02	373	Date Notes: Date expressed in CCYYMMDD format.	M	DT	8/8
DTM03	337	Time Notes: Time expressed in HHMM format.	M	TM	4/8
DTM04	623	Time Code Notes: Always 'GM'	M	ID	2/2

Code Values:

Code	Name
ZZZ	Mutually Defined — Always 'ZZZ'
GM	Greenwich Mean Time — Always 'GM'

Segment Usage: Date/Time when the order was processed and was 'ready to ship'.

Example: DTM*ZZZ*20231224*1200*GM

DTM Date/Time Reference (Shipped)
Pos: 200	Max: 10	Loop: HL	Detail - Mandatory	Elements: 4
User Option (Usage): Must use

Purpose: To specify pertinent dates and times

Element Summary:

Ref Id	Id	Element Name	Req	Type	Min/Max
DTM01	374	Date/Time Qualifier Notes: Always '011'	M	ID	3/3
DTM02	373	Date Notes: Date expressed in CCYYMMDD format.	M	DT	8/8
DTM03	337	Time Notes: Time expressed in HHMM format.	M	TM	4/8
DTM04	623	Time Code Notes: Always 'GM'	M	ID	2/2

Code Values:

Code	Name
011	Shipped — Always '011'
GM	Greenwich Mean Time — Always 'GM'

Segment Usage: Date/Time when the shipment was manifested and shipped.

Example: DTM*011*20231224*1200*GM

CTT Transaction Totals
Pos: 010	Max: 1	Loop: N/A	Summary - Mandatory	Elements: 2
User Option (Usage): Must use

Purpose: To transmit a hash total for a specific element in the transaction set

Element Summary:

Ref Id

Element Name

Req

Type

Min/Max

CTT01

354

Number of Line Items

Notes: Always the number of line items.

1/6

CTT02

347

Hash Total

Notes: Always Qty shipped.

1/10

Segment Usage: This segment indicates the total number of line items and the total quantity shipped.

Example: CTT*1*3

SE Transaction Set Trailer
Pos: 020	Max: 1	Loop: N/A	Summary - Mandatory	Elements: 2
User Option (Usage): Must use

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

Element Summary:

Ref Id

Element Name

Req

Type

Min/Max

SE01

Number of Included Segments

1/10

SE02

329

Transaction Set Control Number

Notes: Same as ST02

4/9

Segment Usage: One ST/SE loop represents the shipping confirmation for a single order number/ ship ID. Multiple ST/SE loops are only allowed if they are for the same message type.

Example: SE*17*39823

GE Functional Group Trailer
Pos:	Max: 1	Loop: N/A	Summary - Mandatory	Elements: 2
User Option (Usage): Must use

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

Element Summary:

Ref Id

Element Name

Req

Type

Min/Max

GE01

Number of Transaction Sets Included

1/6

GE02

Group Control Number

Notes: Same as GS06

1/9

Segment Usage: Only one GS/GE loop is allowed per transmission.

Example: GE*1*39823

IEA Interchange Control Trailer
Pos:	Max: 1	Loop: N/A	Summary - Mandatory	Elements: 2
User Option (Usage): Must use

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

Element Summary:

Ref Id

Element Name

Req

Type

Min/Max

IEA01

I16

Number of Included Functional Groups

1/5

IEA02

I12

Interchange Control Number

Notes: Same as ISA13

9/9

Segment Usage: Only one ISA/IEA loop per data file allowed.

Example: IEA*1*100038823