x12/v4010/856 : 856 ship notice/manifest version: 3.0 final · 2019-12-17 · 11/11/2019 ship...

856 Ship Notice/ManifestX12/V4010/856 : 856 Ship Notice/Manifest

Version: 3.0 Final

Author: [email protected] Company: D&H Distributing Publication: 12/17/2019

NotesD&H Usage: This EDI specification is intended for vendors that sell products to D&H for resale. For partners purchasingproducts from D&H, please refer to the Customer Specification guidelines. The most recent versions of allspecifications can be found on the D&H EDI Documentation Site (www.dandh.com/docs).

Acceptable Characters/Format The EDI messages use UTF8/Unicode characters and the field data is limited to the following characters: A through Z (upper or lowercase, non-English characters are not permitted) 0 through 9 ! “ & ’ ( ) / + , - . : ; = (space) % @ [ ] _ { } # $ ?

Data Validation All messages between trading partners need to meet EDI validation.

997 Acknowledgments Upon receiving an EDI message D&H will validate the message and return a 997 Functional Acknowledgment.

Delimiters The default delimiters used by D&H are * (element separator) , ~ (segment terminator), > (component elementseparator)

Segment Usage D&H requires any segment reflected in this guide as ‘mandatory’ (note under the usage section) to be transmittedin your documents. We will accept all valid X12 segments (By ANSI standards) but will only process those requiredfor our business unless otherwise negotiated during your implementation

Additional Reference Documents: For additional processing information, please refer to the following documents: US Terms and Conditions (https://www.dandh.com/docs/vendor/termsandconditions.pdf)\ CA Terms and Conditions (https://www.dandh.ca/docs/vendor/termsandconditions.pdf) US Routing Guide: (https://www.dandh.com/docs/vendor/USDomesticSupplierRoutingGuide.pdf) CA Routing Guide: (https://www.dandh.ca/docs/vendor/CADomesticSupplierRoutingGuide.pdf)

Supported ASN Formats: D&H supports the following ASN formats: SOTPI, SOTI, SOPI. Tare, Carton, or Both levels of detail are required.

Change Log: 10/29/2019, Major version updates to support supply chain visibility (data provisioning to customer/resellers), 3.0 TD5 - TD504 Usage Mandatory; Qualifier T Removed; TD512 Service Level Code List Modified REF (HLS) - Qualifier Usage Updated; Removed IA Qualifier (Moved to Order Level REF) N1 - N103 Qualifier 15 Removed N2 - Added Segment N3 - Updated usage requirements N4 - Updated usage requirements PER - Added Segment REF (HLO) - Added IA Qualifier (Moved from Shipment Level REF) HLT - Tare Hierarchy Level Added MAN (HLT) - Added Segment - Pallet/Tare ID PO4 (HLT) - Added Segment - Pallet/Tare Weight PRF - PRF04 usage optional PO4 (HLP) - Added Segment - Summary Carton Quantity, Weight, and Dimensions REF (HLI) - Added Segment - New standard location for serial (replacing SLN) SN1 - Removed SN104, SN105, SN106 elements SLN - Removed Segment

11/11/2019 Ship Notice/Manifest - 856 D&H Distributing

ImplementationGuide856v3.ecs i V4010

Table of Contents856 Ship Notice/Manifest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

ISA Interchange Control Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>GS Functional Group Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>BSN Beginning Segment for Ship Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD1 Carrier Details (Quantity and Weight) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>TD5 Carrier Details (Routing Sequence/Transit Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>FOB F.O.B. Related Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N2 Additional Name Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N3 Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>N4 Geographic Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PER Administrative Communications Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PRF Purchase Order Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO4 Item Physical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>MAN Marks and Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO4 Item Physical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>MAN Marks and Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>LIN Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SN1 Item Detail (Shipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PO4 Item Physical Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>PID Product/Item Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>GE Functional Group Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>IEA Interchange Control Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>

. . . . . 1. . . . . 3. . . . . 6. . . . . 8. . . . . 9. . . . 11. . . . 12. . . . 14. . . . 16. . . . 17. . . . 18. . . . 19. . . . 20. . . . 21. . . . 22. . . . 23. . . . 25. . . . 26. . . . 27. . . . 28. . . . 29. . . . 30. . . . 31. . . . 32. . . . 34. . . . 35. . . . 36. . . . 38. . . . 39. . . . 40. . . . 41. . . . 42. . . . 43. . . . 44. . . . 45


ImplementationGuide856v3.ecs 1 V4010

856 Ship Notice/ManifestFunctional Group=SH

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the ShipNotice/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 additionalinformation relating to the shipment, such as order information, product description, physical characteristics, type ofpackaging, marking, carrier information, and configuration of goods within the transportation equipment. Thetransaction set enables the sender to describe the contents and configuration of a shipment in various levels of detailand provides an ordered flexibility to convey information.The sender of this transaction is the organizationresponsible for detailing and communicating the contents of a shipment, or shipments, to one or more receivers ofthe transaction set. The receiver of this transaction set can be any organization having an interest in the contents ofa shipment or information about the contents of a shipment.

Heading:Pos Id Segment Name Req Max Use Repeat Notes Usage

ISA Interchange Control Header M 1 Must useGS Functional Group Header M 1 Must use

010 ST Transaction Set Header M 1 Must use020 BSN Beginning Segment for Ship

NoticeM 1 Must use

Detail:Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL 200000 C2/010L LOOP ID - HL 200000 C2/010L

010 HL Hierarchical Level M 1 C2/010 Must use110 TD1 Carrier Details (Quantity

and Weight)O 20 Used

120 TD5 Carrier Details (RoutingSequence/Transit Time)

M 12 Must use

150 REF Reference Identification O >1 Must use200 DTM Date/Time Reference O 10 Must use210 FOB F.O.B. Related Instructions O 1 Must use

LOOP ID - N1 200 LOOP ID - N1 200

220 N1 Name O 1 Must use230 N2 Additional Name

InformationO 2 Used

240 N3 Address Information O 1 Must use250 N4 Geographic Location O 1 Must use270 PER Administrative

Communications ContactO 3 Used

LOOP ID - HL 200000 LOOP ID - HL 200000

010 HL Hierarchical Level M 1 C2/010 Must use050 PRF Purchase Order Reference O 1 Must use150 REF Reference Identification O >1 Must use


010 HL Hierarchical Level M 1 C2/010 Must use060 PO4 Item Physical Details O 1 Used190 MAN Marks and Numbers O >1 Must use


Pos Id Segment Name Req Max Use Repeat Notes Usage



010 HL Hierarchical Level M 1 C2/010 Must use060 PO4 Item Physical Details O 1 Used190 MAN Marks and Numbers O >1 Must use


010 HL Hierarchical Level M 1 C2/010 Must use020 LIN Item Identification O 1 Must use030 SN1 Item Detail (Shipment) O 1 Must use060 PO4 Item Physical Details O 1 Used070 PID Product/Item Description O 200 Used150 REF Reference Identification O >1 Used

Summary:Pos Id Segment Name Req Max Use Repeat Notes Usage010 CTT Transaction Totals O 1 N3/010 Must use020 SE Transaction Set Trailer M 1 Must use

GE Functional Group Trailer M 1 Must useIEA Interchange Control Trailer M 1 Must use

Notes: 3/010 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 units shipped (SN102) for each SN1 segment.

Comments: 2/010L The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no

meaning.2/010 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no





meaning.



ISA Interchange Control Header Pos: Max: 1Heading - Mandatory

Loop: N/A Elements: 16

User Option (Usage): Must usePurpose: To start and identify an interchange of zero or more functional groups and interchange-related controlsegments

Element Summary: Ref Id Element Name Req Type Min/Max UsageISA01 I01 Authorization Information Qualifier

Description: Code to identify the type ofinformation in the AuthorizationInformation

M ID 2/2 Must use

CodeList Summary (Total Codes: 7, Included: 1)Code Name00 No Authorization Information Present (No Meaningful Information in I02)

ISA02 I02 Authorization Information

Description: Information used foradditional identification or authorization ofthe interchange sender or the data in theinterchange; the type of information is setby the Authorization Information Qualifier(I01)

M AN 10/10 Must use

ISA03 I03 Security Information Qualifier

Description: Code to identify the type ofinformation in the Security Information

M ID 2/2 Must use

CodeList Summary (Total Codes: 2, Included: 1)Code Name00 No Security Information Present (No Meaningful Information in I04)

ISA04 I04 Security Information

Description: This is used for identifyingthe security information about theinterchange sender or the data in theinterchange; the type of information is setby the Security Information Qualifier (I03)

M AN 10/10 Must use

ISA05 I05 Interchange ID Qualifier

Description: Qualifier to designate thesystem/method of code structure used todesignate the sender or receiver IDelement being qualifiedD&H Usage Notes: Your QualifierD&H Usage Notes: Your Qualifier

M ID 2/2 Must use

CodeList Summary (Total Codes: 38, Included: 4)Code Name01 Duns (Dun & Bradstreet)


Code Name


08 UCC EDI Communications ID (Comm ID)12 Phone (Telephone Companies)ZZ Mutually Defined

ISA06 I06 Interchange Sender ID

Description: Identification codepublished by the sender for other partiesto use as the receiver ID to route data tothem; the sender always codes this valuein the sender ID elementD&H Usage Notes: Your ISA Sender IDD&H Usage Notes: Your ISA Sender ID

M AN 15/15 Must use

ISA07 I05 Interchange ID Qualifier

Description: Qualifier to designate thesystem/method of code structure used todesignate the sender or receiver IDelement being qualifiedD&H Usage Notes: D&H US -01 D&H Canada-08D&H Usage Notes: D&H US -01 D&H Canada-08

M ID 2/2 Must use

CodeList Summary (Total Codes: 38, Included: 2)Code Name01 Duns (Dun & Bradstreet)08 UCC EDI Communications ID (Comm ID)

ISA08 I07 Interchange Receiver ID

Description: Identification codepublished by the receiver of the data;When sending, it is used by the sender astheir sending ID, thus other partiessending to them will use this as areceiving ID to route data to themD&H Usage Notes: D&H US Production - 007911209 D&H Canada Production - 243337024

D&H US Test/UAT - 007911209T D&H Canada Test/UAT - 243337024T

D&H Usage Notes: D&H US Production - 007911209 D&H Canada Production - 243337024


M AN 15/15 Must use

ISA09 I08 Interchange Date

Description: Date of the interchange

M DT 6/6 Must use

ISA10 I09 Interchange Time

Description: Time of the interchange

M TM 4/4 Must use

ISA11 I10 Interchange Control StandardsIdentifier

Description: Code to identify the agencyresponsible for the control standard usedby the message that is enclosed by the

M ID 1/1 Must use


Ref Id Element Name Req Type Min/Max Usage


interchange header and trailer

CodeList Summary (Total Codes: 1, Included: 1)Code NameU U.S. EDI Community of ASC X12, TDCC, and UCS

ISA12 I11 Interchange Control Version Number

Description: Code specifying the versionnumber of the interchange controlsegments

M ID 5/5 Must use

CodeList Summary (Total Codes: 14, Included: 1)Code Name00401 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures

Review Board through October 1997

ISA13 I12 Interchange Control Number

Description: A control number assignedby the interchange sender

M N0 9/9 Must use

ISA14 I13 Acknowledgment Requested

Description: Code sent by the sender torequest an interchange acknowledgment(TA1)

M ID 1/1 Must use

CodeList Summary (Total Codes: 2, Included: 1)Code Name0 No Acknowledgment Requested

ISA15 I14 Usage Indicator

Description: Code to indicate whetherdata enclosed by this interchangeenvelope is test, production or information

M ID 1/1 Must use

CodeList Summary (Total Codes: 3, Included: 2)Code NameP Production DataT Test Data

ISA16 I15 Component Element Separator

Description: Type is not applicable; thecomponent element separator is adelimiter and not a data element; this fieldprovides the delimiter used to separatecomponent data elements within acomposite data structure; this value mustbe different than the data elementseparator and the segment terminator

M 1/1 Must use

D&H Sample Data:D&H Sample Data:ISA*00* *00* *ZZ*SENDERID *ZZ*RECEIVERID *160202*1135*U*00401*000001661*0*P*>ISA*00* *00* *ZZ*SENDERID *ZZ*RECEIVERID *160202*1135*U*00401*000001661*0*P*>



GS Functional Group Header Pos: Max: 1Heading - Mandatory


User Option (Usage): Must usePurpose: To indicate the beginning of a functional group and to provide control information

Element Summary: Ref Id Element Name Req Type Min/Max UsageGS01 479 Functional Identifier Code

Description: Code identifying a group ofapplication related transaction sets

M ID 2/2 Must use

CodeList Summary (Total Codes: 240, Included: 1)Code NameSH Ship Notice/Manifest (856)

GS02 142 Application Sender's Code

Description: Code identifying partysending transmission; codes agreed to bytrading partnersD&H Usage Notes: Your Sender IDD&H Usage Notes: Your Sender ID

M AN 2/15 Must use

GS03 124 Application Receiver's Code

Description: Code identifying partyreceiving transmission; codes agreed toby trading partnersD&H Usage Notes: D&H US Production - 007911209 D&H Canada Production - 243337024


D&H Usage Notes: D&H US Production - 007911209 D&H Canada Production - 243337024


M AN 2/15 Must use

GS04 373 Date

Description: Date expressed asCCYYMMDDD&H Usage Notes: CCYYMMDDD&H Usage Notes: CCYYMMDD

M DT 8/8 Must use

GS05 337 Time

Description: Time expressed in 24-hourclock time as follows: HHMM, orHHMMSS, or HHMMSSD, orHHMMSSDD, where H = hours (00-23), M= minutes (00-59), S = integer seconds(00-59) and DD = decimal seconds;decimal seconds are expressed asfollows: D = tenths (0-9) and DD =hundredths (00-99)

M TM 4/8 Must use




GS06 28 Group Control Number

Description: Assigned number originatedand maintained by the sender

M N0 1/9 Must use

GS07 455 Responsible Agency Code

Description: Code identifying the issuerof the standard; this code is used inconjunction with Data Element 480

M ID 1/2 Must use

CodeList Summary (Total Codes: 2, Included: 1)Code NameX Accredited Standards Committee X12

GS08 480 Version / Release / Industry IdentifierCode

Description: Code indicating the version,release, subrelease, and industryidentifier of the EDI standard being used,including the GS and GE segments; ifcode in DE455 in GS segment is X, thenin DE 480 positions 1-3 are the versionnumber; positions 4-6 are the release andsubrelease, level of the version; andpositions 7-12 are the industry or tradeassociation identifiers (optionally assignedby user); if code in DE455 in GS segmentis T, then other formats are allowed

M AN 1/12 Must use

CodeList Summary (Total Codes: 39, Included: 1)Code Name004010 Draft Standards Approved for Publication by ASC X12 Procedures Review Board

through October 1997

Semantics: 1. GS04 is the group date.2. GS05 is the group time.3. The data interchange control number GS06 in this header must be identical to the same data element in the

associated functional group trailer, GE02.

Comments: 1. A functional group of related transaction sets, within the scope of X12 standards, consists of a collection of

similar transaction sets enclosed by a functional group header and a functional group trailer.

D&H Sample Data:D&H Sample Data:GS*SH*SENDERID*RECEIVERID*20160202*1135*1661*X*004010GS*SH*SENDERID*RECEIVERID*20160202*1135*1661*X*004010



ST Transaction Set Header Pos: 010 Max: 1Heading - Mandatory


User Option (Usage): Must usePurpose: To indicate the start of a transaction set and to assign a control number

Element Summary: Ref Id Element Name Req Type Min/Max UsageST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying aTransaction Set

M ID 3/3 Must use

CodeList Summary (Total Codes: 298, Included: 1)Code Name856 Ship Notice/Manifest

ST02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction set

M AN 4/9 Must use

Semantics: 1. 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).

D&H Sample Data:D&H Sample Data:ST*856*0061ST*856*0061



BSN Beginning Segment for ShipNotice

Pos: 020 Max: 1Heading - Mandatory


User Option (Usage): Must usePurpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageBSN01 353 Transaction Set Purpose Code

Description: Code identifying purpose oftransaction set

M ID 2/2 Must use

CodeList Summary (Total Codes: 65, Included: 1)Code Name00 Original

BSN02 396 Shipment Identification

Description: A unique control numberassigned by the original shipper to identifya specific shipment

M AN 2/30 Must use

BSN03 373 Date

Description: Date expressed asCCYYMMDD

M DT 8/8 Must use

BSN04 337 Time


M TM 4/8 Must use

BSN05 1005 Hierarchical Structure Code

Description: Code indicating thehierarchical application structure of atransaction set that utilizes the HLsegment to define the structure of thetransaction set

O ID 4/4 Must use

CodeList Summary (Total Codes: 61, Included: 1)Code Name0001 Shipment, Order, Packaging, Item

Semantics: 1. BSN03 is the date the shipment transaction set is created.2. BSN04 is the time the shipment transaction set is created.



D&H Usage Notes:D&H Usage Notes:D&H supports the following ASN formats: SOTPI, SOTI, SOPI. Tare, Carton, or Both levels of detail are required.D&H supports the following ASN formats: SOTPI, SOTI, SOPI. Tare, Carton, or Both levels of detail are required.

D&H Sample Data:D&H Sample Data:BSN*00*1234567890*20141231*1230*0001BSN*00*1234567890*20141231*1230*0001



HL Hierarchical Level Pos: 010 Max: 1Detail - Mandatory

Loop: HL Elements: 3

User Option (Usage): Must usePurpose: To identify dependencies among and the content of hierarchically related groups of data segments

Element Summary: Ref Id Element Name Req Type Min/Max UsageHL01 628 Hierarchical ID Number

Description: A unique number assignedby the sender to identify a particular datasegment in a hierarchical structure

M AN 1/12 Must use

HL02 734 Hierarchical Parent ID Number

Description: Identification number of thenext higher hierarchical data segment thatthe data segment being described issubordinate to

O AN 1/12 Used

HL03 735 Hierarchical Level Code

Description: Code defining thecharacteristic of a level in a hierarchicalstructure

M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameS Shipment

Comments: 1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating

line-item data to shipment data, and packaging data to line-item data.2. The HL segment defines a top-down/left-right ordered structure.3. 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 whichcase the value of HL01 would be "1" for the initial HL segment and would be incremented by one in eachsubsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.5. 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 subsequentsegments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.

D&H Sample Data:D&H Sample Data:HL*1**SHL*1**S



TD1 Carrier Details (Quantity andWeight)

Pos: 110 Max: 20Detail - Optional


User Option (Usage): UsedPurpose: To specify the transportation details relative to commodity, weight, and quantity

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD101 103 Packaging Code

Description: Code identifying the type ofpackaging; Part 1: Packaging Form, Part2: Packaging Material; if the Data Elementis used, then Part 1 is always required

O AN 3/5 Must use

CodeList Summary (Total Codes: 148, Included: 2)Code NameCTN CartonPLT Pallet

TD102 80 Lading Quantity

Description: Number of units (pieces) ofthe lading commodity

X N0 1/7 Must use

TD106 187 Weight Qualifier

Description: Code defining the type ofweight

O ID 1/2 Must use

CodeList Summary (Total Codes: 51, Included: 1)Code NameG Gross Weight

TD107 81 Weight

Description: Numeric value of weight

X R 1/10 Must use

TD108 355 Unit or Basis for Measurement Code

Description: Code specifying the units inwhich a value is being expressed, ormanner in which a measurement hasbeen taken

X ID 2/2 Must use

CodeList Summary (Total Codes: 794, Included: 1)Code NameLB Pound

Syntax Rules: 1. C0102 - If TD101 is present, then TD102 is required.2. C0607 - If TD106 is present, then TD107 is required.3. P0708 - If either TD107 or TD108 is present, then the other is required.

D&H Usage Notes:D&H Usage Notes:



TD102 - reflects the total count of cartons and/or pallets within the entire shipmentTD102 - reflects the total count of cartons and/or pallets within the entire shipment

D&H Sample Data:D&H Sample Data:TD1*CTN*23****G*240.5*LBTD1*PLT*2****G*220.25*LBTD1*CTN*23****G*240.5*LBTD1*PLT*2****G*220.25*LB



TD5 Carrier Details (RoutingSequence/Transit Time)

Pos: 120 Max: 12Detail - Mandatory


User Option (Usage): Must usePurpose: To specify the carrier and sequence of routing and provide transit time information

Element Summary: Ref Id Element Name Req Type Min/Max UsageTD501 133 Routing Sequence Code

Description: Code describing therelationship of a carrier to a specificshipment movement

O ID 1/2 Used

CodeList Summary (Total Codes: 23, Included: 3)Code NameA Origin Carrier, Agent's Routing (Rail)B Origin/Delivery Carrier (Any Mode)O Origin Carrier (Air, Motor, or Ocean)

TD502 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

X ID 1/2 Must use

CodeList Summary (Total Codes: 215, Included: 1)Code Name2 Standard Carrier Alpha Code (SCAC)

TD503 67 Identification Code

Description: Code identifying a party orother code

X AN 2/80 Must use

TD504 91 Transportation Method/Type Code

Description: Code specifying the methodor type of transportation for the shipment

X ID 1/2 Must use

CodeList Summary (Total Codes: 71, Included: 2)Code NameM Motor (Common Carrier)U Private Parcel Service

TD505 387 Routing

Description: Free-form description of therouting or requested routing for shipment,or the originating carrier's identity

X AN 1/35 Must use

TD512 284 Service Level Code

Description: Code indicating the level oftransportation service or the billing serviceoffered by the transportation carrier

X ID 2/2 Must use




CodeList Summary (Total Codes: 66, Included: 6)Code Name3D Three Day ServiceAM A.M.CG GroundND Next Day AirSD SaturdaySE Second Day

Syntax Rules: 1. R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required.2. C0203 - If TD502 is present, then TD503 is required.

Comments: 1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier

within the movement, use TD502 to identify the party responsible for defining the routing sequence, and useTD503 to identify the actual routing sequence, specified by the party identified in TD502.

D&H Usage Notes:D&H Usage Notes:TD504 Qualifier of M (Motor) to be used for Truck/LTL shipmentsTD504 Qualifier of U (Private Parcel Service) to be used for Small Parcel shipments (FedEx, UPS, etc.)TD504 Qualifier of M (Motor) to be used for Truck/LTL shipmentsTD504 Qualifier of U (Private Parcel Service) to be used for Small Parcel shipments (FedEx, UPS, etc.)

D&H Sample Data:D&H Sample Data:TD5**2*WXYZ*M*Name of Carrier*******CGTD5**2*WXYZ*M*Name of Carrier*******CG



REF Reference Identification Pos: 150 Max: >1Detail - Optional


User Option (Usage): Must usePurpose: To specify identifying information

Element Summary: Ref Id Element Name Req Type Min/Max UsageREF01 128 Reference Identification Qualifier

Description: Code qualifying theReference Identification

M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 3)Code Name2I Tracking NumberBM Bill of Lading NumberCN Carrier's Reference Number (PRO/Invoice)

REF02 127 Reference Identification

Description: Reference information asdefined for a particular Transaction Set oras specified by the ReferenceIdentification Qualifier

X AN 1/30 Must use

Syntax Rules: 1. R0203 - At least one of REF02 or REF03 is required.

D&H Usage Notes:D&H Usage Notes:2I - Reserved for Small Parcel ShipmentsCN, BM - Reserved for LTL/Truck Shipments2I - Reserved for Small Parcel ShipmentsCN, BM - Reserved for LTL/Truck Shipments

D&H Sample Data:D&H Sample Data:REF*CN*123456789876543REF*BM*ABC189872REF*2I*78728189287987982721

REF*CN*123456789876543REF*BM*ABC189872REF*2I*78728189287987982721



DTM Date/Time Reference Pos: 200 Max: 10Detail - Optional


User Option (Usage): Must usePurpose: To specify pertinent dates and times

Element Summary: Ref Id Element Name Req Type Min/Max UsageDTM01 374 Date/Time Qualifier

Description: Code specifying type of dateor time, or both date and time

M ID 3/3 Must use

CodeList Summary (Total Codes: 1112, Included: 3)Code Name011 Shipped017 Estimated Delivery067 Current Schedule Delivery

DTM02 373 Date


X DT 8/8 Must use

DTM03 337 Time


X TM 4/8 Used

Syntax Rules: 1. R020305 - At least one of DTM02, DTM03 or DTM05 is required.

D&H Usage Notes:D&H Usage Notes:Required usage of DTM with qualifier 011Required usage of DTM with qualifier 011

D&H Sample Data:D&H Sample Data:DTM*011*20150105*1030DTM*067*20150113DTM*011*20150105*1030DTM*067*20150113



FOB F.O.B. Related Instructions Pos: 210 Max: 1Detail - Optional


User Option (Usage): Must usePurpose: To specify transportation instructions relating to shipment

Element Summary: Ref Id Element Name Req Type Min/Max UsageFOB01 146 Shipment Method of Payment

Description: Code identifying paymentterms for transportation charges

M ID 2/2 Must use

CodeList Summary (Total Codes: 28, Included: 2)Code NameCC CollectPP Prepaid (by Seller)

Semantics: 1. FOB01 indicates which party will pay the carrier.

D&H Sample Data:D&H Sample Data:FOB*PPFOB*PP



N1 Name Pos: 220 Max: 1Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Must usePurpose: To identify a party by type of organization, name, and code

Element Summary: Ref Id Element Name Req Type Min/Max UsageN101 98 Entity Identifier Code

Description: Code identifying anorganizational entity, a physical location,property or an individual

M ID 2/3 Must use

CodeList Summary (Total Codes: 1312, Included: 2)Code NameSF Ship FromST Ship To

N102 93 Name

Description: Free-form name

X AN 1/60 Must use

N103 66 Identification Code Qualifier

Description: Code designating thesystem/method of code structure used forIdentification Code (67)

X ID 1/2 Used

CodeList Summary (Total Codes: 215, Included: 1)Code Name92 Assigned by Buyer or Buyer's Agent

N104 67 Identification Code

Description: Code identifying a party orother code

X AN 2/80 Used

Syntax Rules: 1. R0203 - At least one of N102 or N103 is required.2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 1. 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 transactionprocessing party.

D&H Sample Data:D&H Sample Data:N1*ST*D & H Distributing Co.*92*01N1*SF*Business NameN1*ST*D & H Distributing Co.*92*01N1*SF*Business Name



N2 Additional Name Information Pos: 230 Max: 2Detail - Optional


User Option (Usage): UsedPurpose: To specify additional names or those longer than 35 characters in length

Element Summary: Ref Id Element Name Req Type Min/Max UsageN201 93 Name


M AN 1/60 Must use

N202 93 Name


O AN 1/60 Used

D&H Sample Data:D&H Sample Data:N2*BILL SMITN2*BILL SMIT



N3 Address Information Pos: 240 Max: 1Detail - Optional


User Option (Usage): Must usePurpose: To specify the location of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN301 166 Address Information

Description: Address information

M AN 1/55 Must use

N302 166 Address Information

Description: Address information

O AN 1/55 Used

D&H Usage Notes:D&H Usage Notes:Full address details expected for both Ship From and Ship To address loopsFull address details expected for both Ship From and Ship To address loops

D&H Sample Data:D&H Sample Data:N3*909 KATIE COURT*UNION SQUARE IND PKN3*909 KATIE COURT*UNION SQUARE IND PK



N4 Geographic Location Pos: 250 Max: 1Detail - Optional


User Option (Usage): Must usePurpose: To specify the geographic place of the named party

Element Summary: Ref Id Element Name Req Type Min/Max UsageN401 19 City Name

Description: Free-form text for city name

O AN 2/30 Must use

N402 156 State or Province Code

Description: Code (StandardState/Province) as defined by appropriategovernment agency

O ID 2/2 Must use

N403 116 Postal Code

Description: Code defining internationalpostal zone code excluding punctuationand blanks (zip code for United States)

O ID 3/15 Must use

N404 26 Country Code

Description: Code identifying the country

O ID 2/3 Must use

Comments: 1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.2. N402 is required only if city name (N401) is in the U.S. or Canada.

D&H Usage Notes:D&H Usage Notes:Full address details expected for both Ship From and Ship To address loopsFull address details expected for both Ship From and Ship To address loops

D&H Sample Data:D&H Sample Data:N4*Harrisburg*PA*17109*USN4*Harrisburg*PA*17109*US



PER AdministrativeCommunications Contact

Pos: 270 Max: 3Detail - Optional


User Option (Usage): UsedPurpose: To identify a person or office to whom administrative communications should be directed

Element Summary: Ref Id Element Name Req Type Min/Max UsagePER01 366 Contact Function Code

Description: Code identifying the majorduty or responsibility of the person orgroup named

M ID 2/2 Must use

CodeList Summary (Total Codes: 230, Included: 1)Code NameIC Information Contact

PER02 93 Name


O AN 1/60 Used

PER03 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

X ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 1)Code NameTE Telephone

PER04 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

X AN 1/80 Used

PER05 365 Communication Number Qualifier

Description: Code identifying the type ofcommunication number

X ID 2/2 Used

CodeList Summary (Total Codes: 40, Included: 1)Code NameEM Electronic Mail

PER06 364 Communication Number

Description: Complete communicationsnumber including country or area codewhen applicable

X AN 1/80 Used

Syntax Rules: 1. P0304 - If either PER03 or PER04 is present, then the other is required.2. P0506 - If either PER05 or PER06 is present, then the other is required.



D&H Sample Data:D&H Sample Data:PER*IC*JOHN SHIPPER*TE*9781237866*EM*[email protected]*IC*JOHN SHIPPER*TE*9781237866*EM*[email protected]








M AN 1/12 Must use



O AN 1/12 Must use



M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameO Order






D&H Sample Data:D&H Sample Data:HL*2*1*OHL*2*1*O



PRF Purchase Order Reference Pos: 050 Max: 1Detail - Optional


User Option (Usage): Must usePurpose: To provide reference to a specific purchase order

Element Summary: Ref Id Element Name Req Type Min/Max UsagePRF01 324 Purchase Order Number

Description: Identifying number forPurchase Order assigned by theorderer/purchaser

M AN 1/22 Must use

PRF04 373 Date


O DT 8/8 Used

Semantics: 1. PRF04 is the date assigned by the purchaser to purchase order.

D&H Sample Data:D&H Sample Data:PRF*908704L***20160126PRF*908704L***20160126





User Option (Usage): Must usePurpose: To specify identifying information



M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 3)Code NameIA Internal Vendor NumberIV Seller's Invoice NumberVN Vendor Order Number



X AN 1/30 Must use


D&H Usage Notes:D&H Usage Notes:IA - Required for all shipments. Values should match to the REF*IA vendor number provided on the 850.IA - Required for all shipments. Values should match to the REF*IA vendor number provided on the 850.

D&H Sample Data:D&H Sample Data:REF*IA*12345REF*IV*1234567890REF*VN*987654321

REF*IA*12345REF*IV*1234567890REF*VN*987654321








M AN 1/12 Must use



O AN 1/12 Must use



M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameT Shipping Tare






D&H Sample Data:D&H Sample Data:HL*3*2*THL*3*2*T



PO4 Item Physical Details Pos: 060 Max: 1Detail - Optional


User Option (Usage): UsedPurpose: To specify the physical qualities, packaging, weights, and dimensions relating to the item

Element Summary: Ref Id Element Name Req Type Min/Max UsagePO405 187 Weight Qualifier


O ID 1/2 Used


PO406 384 Gross Weight per Pack

Description: Numeric value of grossweight per pack

X R 1/9 Used

PO407 355 Unit or Basis for Measurement Code


X ID 2/2 Used


Syntax Rules: 1. C0506 - If PO405 is present, then PO406 is required.2. P0607 - If either PO406 or PO407 is present, then the other is required.

D&H Sample Data:D&H Sample Data:PO4*****G*1560*LBPO4*****G*1560*LB



MAN Marks and Numbers Pos: 190 Max: >1Detail - Optional


User Option (Usage): Must usePurpose: To indicate identifying marks and numbers for shipping containers

Element Summary: Ref Id Element Name Req Type Min/Max UsageMAN01 88 Marks and Numbers Qualifier

Description: Code specifying theapplication or source of Marks andNumbers (87)

M ID 1/2 Must use

CodeList Summary (Total Codes: 20, Included: 1)Code NameGM SSCC-18 and Application Identifier

MAN02 87 Marks and Numbers

Description: Marks and numbers used toidentify a shipment or parts of a shipment

M AN 1/48 Must use

Semantics: 1. MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the

same physical container.

D&H Usage Notes:D&H Usage Notes:D&H supports the following ASN formats: SOTPI, SOTI, SOPI. Tare, Carton, or Both levels of detail are requiredD&H supports the following ASN formats: SOTPI, SOTI, SOPI. Tare, Carton, or Both levels of detail are required

D&H Sample Data:D&H Sample Data:MAN*GM*00109111040123459991MAN*GM*00109111040123459991








M AN 1/12 Must use



O AN 1/12 Must use



M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameP Pack






D&H Sample Data:D&H Sample Data:HL*4*3*PHL*4*3*P






Element Summary: Ref Id Element Name Req Type Min/Max UsagePO401 356 Pack

Description: The number of innercontainers, or number of eaches if thereare no inner containers, per outercontainer

O N0 1/6 Used

PO405 187 Weight Qualifier


O ID 1/2 Used




X R 1/9 Used



X ID 2/2 Used


PO410 82 Length

Description: Largest horizontaldimension of an object measured whenthe object is in the upright position

X R 1/8 Used

PO411 189 Width

Description: Shorter measurement of thetwo horizontal dimensions measured withthe object in the upright position

X R 1/8 Used

PO412 65 Height

Description: Vertical dimension of anobject measured when the object is in theupright position

X R 1/8 Used

PO413 355 Unit or Basis for Measurement Code X ID 2/2 Used





CodeList Summary (Total Codes: 794, Included: 1)Code NameIN Inch

Syntax Rules: 1. C0506 - If PO405 is present, then PO406 is required.2. P0607 - If either PO406 or PO407 is present, then the other is required.3. C1013 - If PO410 is present, then PO413 is required.4. C1113 - If PO411 is present, then PO413 is required.5. C1213 - If PO412 is present, then PO413 is required.6. L13101112 - If PO413 is present, then at least one of PO410, PO411 or PO412 is required.

Comments: 1. PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack

(PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the cartoncontains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element357 = "12"; Data element 355 = "OZ".

2. PO413 defines the unit of measure for PO410, PO411, and PO412.

D&H Usage Notes:D&H Usage Notes:This segment data reflects summary carton quantity, weight, and dimensionsThis segment data reflects summary carton quantity, weight, and dimensions

D&H Sample Data:D&H Sample Data:PO4*6****G*24.5*LB***22.5*18.75*12*IN~PO4*6****G*24.5*LB***22.5*18.75*12*IN~



MAN Marks and Numbers Pos: 190 Max: >1Detail - Optional


User Option (Usage): Must usePurpose: To indicate identifying marks and numbers for shipping containers

Element Summary: Ref Id Element Name Req Type Min/Max UsageMAN01 88 Marks and Numbers Qualifier


M ID 1/2 Must use

CodeList Summary (Total Codes: 20, Included: 1)Code NameGM SSCC-18 and Application Identifier



M AN 1/48 Must use

MAN04 88 Marks and Numbers Qualifier


X ID 1/2 Used

CodeList Summary (Total Codes: 20, Included: 1)Code NameCP Carrier-Assigned Package ID Number



X AN 1/48 Used

Syntax Rules: 1. P0405 - If either MAN04 or MAN05 is present, then the other is required.

Semantics: 1. MAN01/MAN02 and MAN04/MAN05 may be used to identify two different marks and numbers assigned to the

same physical container.2. When both MAN02 and MAN03 are used, MAN02 is the starting number of a sequential range and MAN03 is

the ending number of that range.

D&H Usage Notes:D&H Usage Notes:D&H supports the following ASN formats: SOTPI, SOTI, SOPI. Tare, Carton, or Both levels of detail are requiredD&H supports the following ASN formats: SOTPI, SOTI, SOPI. Tare, Carton, or Both levels of detail are required

D&H Sample Data:D&H Sample Data:MAN*GM*00109111040123456785**CP*987654321098765MAN*GM*00109111040123456785**CP*987654321098765








M AN 1/12 Must use



O AN 1/12 Must use



M ID 1/2 Must use

CodeList Summary (Total Codes: 170, Included: 1)Code NameI Item






D&H Sample Data:D&H Sample Data:HL*5*4*IHL*5*4*I



LIN Item Identification Pos: 020 Max: 1Detail - Optional


User Option (Usage): Must usePurpose: To specify basic item identification data

Element Summary: Ref Id Element Name Req Type Min/Max UsageLIN01 350 Assigned Identification

Description: Alphanumeric charactersassigned for differentiation within atransaction set

O AN 1/20 Must use

LIN02 235 Product/Service ID Qualifier

Description: Code identifying thetype/source of the descriptive numberused in Product/Service ID (234)

M ID 2/2 Must use

CodeList Summary (Total Codes: 477, Included: 1)Code NameVP Vendor's (Seller's) Part Number

LIN03 234 Product/Service ID

Description: Identifying number for aproduct or service

M AN 1/48 Must use



X ID 2/2 Must use

CodeList Summary (Total Codes: 477, Included: 1)Code NameBP Buyer's Part Number



X AN 1/48 Must use



X ID 2/2 Must use

CodeList Summary (Total Codes: 477, Included: 1)Code NameUP U.P.C. Consumer Package Code (1-5-5-1)



X AN 1/48 Must use




Syntax Rules: 1. P0405 - If either LIN04 or LIN05 is present, then the other is required.2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

Semantics: 1. LIN01 is the line item identification

Comments: 1. See the Data Dictionary for a complete list of IDs.2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color,

Drawing No., U.P.C. No., ISBN No., Model No., or SKU.

D&H Usage Notes:D&H Usage Notes:D&H expects vendor to return the same data values to D&H that were received on the 850 Purchase Order for theVP, BP, and UPLIN qualifiers should be coded in the same order documented

D&H expects vendor to return the same data values to D&H that were received on the 850 Purchase Order for theVP, BP, and UPLIN qualifiers should be coded in the same order documented

D&H Sample Data:D&H Sample Data:LIN*1*VP*1234567890*BP*12345678901*UP*1234567890LIN*1*VP*1234567890*BP*12345678901*UP*1234567890



SN1 Item Detail (Shipment) Pos: 030 Max: 1Detail - Optional


User Option (Usage): Must usePurpose: To specify line-item detail relative to shipment

Element Summary: Ref Id Element Name Req Type Min/Max UsageSN101 350 Assigned Identification

Description: Alphanumeric charactersassigned for differentiation within atransaction set

O AN 1/20 Recommended

SN102 382 Number of Units Shipped

Description: Numeric value of unitsshipped in manufacturer's shipping unitsfor a line item or transaction set

M R 1/10 Must use

SN103 355 Unit or Basis for Measurement Code


M ID 2/2 Must use

CodeList Summary (Total Codes: 794, Included: 1)Code NameEA Each

Semantics: 1. SN101 is the ship notice line-item identification.

Comments: 1. SN103 defines the unit of measurement for both SN102 and SN104.

D&H Sample Data:D&H Sample Data:SN1**50*EASN1**50*EA






Element Summary: Ref Id Element Name Req Type Min/Max UsagePO401 356 Pack

Description: The number of innercontainers, or number of eaches if thereare no inner containers, per outercontainer

O N0 1/6 Used

PO405 187 Weight Qualifier


O ID 1/2 Used




X R 1/9 Used



X ID 2/2 Used


Syntax Rules: 1. C0506 - If PO405 is present, then PO406 is required.2. P0607 - If either PO406 or PO407 is present, then the other is required.

Comments: 1. PO403 - The "Unit or Basis for Measure Code" in this segment position is for purposes of defining the pack

(PO401) /size (PO402) measure which indicates the quantity in the inner pack unit. For example: If the cartoncontains 24 12-Ounce packages, it would be described as follows: Data element 356 = "24"; Data element357 = "12"; Data element 355 = "OZ".

D&H Sample Data:D&H Sample Data:Standard (packed in eaches) Example PO4*1****G*5.12*LBMulti-pack (inner pack) Example PO4*3****G*12.23*LB

Standard (packed in eaches) Example PO4*1****G*5.12*LBMulti-pack (inner pack) Example PO4*3****G*12.23*LB



PID Product/Item Description Pos: 070 Max: 200Detail - Optional


User Option (Usage): UsedPurpose: To describe a product or process in coded or free-form format

Element Summary: Ref Id Element Name Req Type Min/Max UsagePID01 349 Item Description Type

Description: Code indicating the formatof a description

M ID 1/1 Must use

PID05 352 Description

Description: A free-form description toclarify the related data elements and theircontent

X AN 1/80 Must use

Comments: 1. If PID01 equals "F", then PID05 is used. If PID01 equals "S", then PID04 is used. If PID01 equals "X", then

both PID04 and PID05 are used.

D&H Sample Data:D&H Sample Data:PID*F****Product DescriptionPID*F****Product Description





User Option (Usage): UsedPurpose: To specify identifying information



M ID 2/3 Must use

CodeList Summary (Total Codes: 1503, Included: 1)Code NameSE Serial Number



X AN 1/30 Must use


D&H Sample Data:D&H Sample Data:REF*SE*SN12988382768798REF*SE*SN12988382768798



CTT Transaction Totals Pos: 010 Max: 1Summary - Optional


User Option (Usage): Must usePurpose: To transmit a hash total for a specific element in the transaction set

Element Summary: Ref Id Element Name Req Type Min/Max UsageCTT01 354 Number of Line Items

Description: Total number of line items inthe transaction set

M N0 1/6 Must use

Comments: 1. This segment is intended to provide hash totals to validate transaction completeness and correctness.

D&H Sample Data:D&H Sample Data:CTT*6CTT*6



SE Transaction Set Trailer Pos: 020 Max: 1Summary - Mandatory


User Option (Usage): Must usePurpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including thebeginning (ST) and ending (SE) segments)

Element Summary: Ref Id Element Name Req Type Min/Max UsageSE01 96 Number of Included Segments

Description: Total number of segmentsincluded in a transaction set including STand SE segments

M N0 1/10 Must use

SE02 329 Transaction Set Control Number

Description: Identifying control numberthat must be unique within the transactionset functional group assigned by theoriginator for a transaction set

M AN 4/9 Must use

Comments: 1. SE is the last segment of each transaction set.

D&H Sample Data:D&H Sample Data:SE*40*0061SE*40*0061



GE Functional Group Trailer Pos: Max: 1Summary - Mandatory


User Option (Usage): Must usePurpose: To indicate the end of a functional group and to provide control information

Element Summary: Ref Id Element Name Req Type Min/Max UsageGE01 97 Number of Transaction Sets Included

Description: Total number of transactionsets included in the functional group orinterchange (transmission) groupterminated by the trailer containing thisdata element

M N0 1/6 Must use

GE02 28 Group Control Number

Description: Assigned number originatedand maintained by the sender

M N0 1/9 Must use

Semantics: 1. The data interchange control number GE02 in this trailer must be identical to the same data element in the

associated functional group header, GS06.

Comments: 1. The use of identical data interchange control numbers in the associated functional group header and trailer is

designed to maximize functional group integrity. The control number is the same as that used in thecorresponding header.

D&H Sample Data:D&H Sample Data:GE*3*1661GE*3*1661



IEA Interchange Control Trailer Pos: Max: 1Summary - Mandatory


User Option (Usage): Must usePurpose: To define the end of an interchange of zero or more functional groups and interchange-related controlsegments

Element Summary: Ref Id Element Name Req Type Min/Max UsageIEA01 I16 Number of Included Functional Groups

Description: A count of the number offunctional groups included in aninterchange

M N0 1/5 Must use

IEA02 I12 Interchange Control Number

Description: A control number assignedby the interchange sender

M N0 9/9 Must use

D&H Sample Data:D&H Sample Data:IEA*1*000001661~IEA*1*000001661~

D&H Transaction Set Sample Data:D&H Transaction Set Sample Data:SMALL PARCEL ASN EXAMPLE:ISA*00* *00* *ZZ*SENDERID *ZZ*RECEIVERID *191115*1135*U*00401*000001662*0*T*>~GS*SH*SENDERID*RECEIVERID*20191115*1135*1662*X*004010~ST*856*0062~BSN*00*1234567890*20191115*1135*0001~HL*1**S~TD1*CTN*1****G*23.8*LB~TD5*O*2*FDEN*U*FEDEX AIR*******ND~REF*2I*112570433591~DTM*011*20191115~DTM*017*20191116~FOB*PP~N1*SF*VENDOR WAREHOUSE~N2*SHIPPING DEPT~N3*143 ELM STREET*ZONE C~N4*ANYTOWN*PA*17057*US~N1*ST*JOHN SMITH~N3*89 MAIN STREET*APT C4~N4*MECHANICSBURG*PA*17050*US~HL*2*1*O~PRF*958704L***20191114~REF*IA*12345~REF*IV*1234567891~REF*VN*987654322~HL*3*2*P~PO4*6****G*23.8*LB***12*8*8*IN~MAN*GM*00109111040123457058**CP*112570433591~

SMALL PARCEL ASN EXAMPLE:ISA*00* *00* *ZZ*SENDERID *ZZ*RECEIVERID *191115*1135*U*00401*000001662*0*T*>~GS*SH*SENDERID*RECEIVERID*20191115*1135*1662*X*004010~ST*856*0062~BSN*00*1234567890*20191115*1135*0001~HL*1**S~TD1*CTN*1****G*23.8*LB~TD5*O*2*FDEN*U*FEDEX AIR*******ND~REF*2I*112570433591~DTM*011*20191115~DTM*017*20191116~FOB*PP~N1*SF*VENDOR WAREHOUSE~N2*SHIPPING DEPT~N3*143 ELM STREET*ZONE C~N4*ANYTOWN*PA*17057*US~N1*ST*JOHN SMITH~N3*89 MAIN STREET*APT C4~N4*MECHANICSBURG*PA*17050*US~HL*2*1*O~PRF*958704L***20191114~REF*IA*12345~REF*IV*1234567891~REF*VN*987654322~HL*3*2*P~PO4*6****G*23.8*LB***12*8*8*IN~MAN*GM*00109111040123457058**CP*112570433591~



HL*4*3*I~LIN*1*VP*VENDSKU1-A3*BP*VENDSKU1A3*UP*123456789012~SN1**4*EA~PO4*1****G*4*LB~PID*F****Product Description~REF*SE*SN12988382764442~REF*SE*SN12988382764443~REF*SE*SN12988382764444~REF*SE*SN12988382764445~HL*5*3*I~LIN*2*VP*VENDSKU2-A6*BP*VENDSKU2A6*UP*123456789029~SN1**2*EA~PO4*1****G*3.2*LB~PID*F****Product Description~REF*SE*SN12988382768712~REF*SE*SN12988382768713~CTT*5~SE*42*0062~GE*1*1662~IEA*1*000001662~ LTL/TRUCK ASN EXAMPLE:ISA*00* *00* *ZZ*SENDERID *ZZ*RECEIVERID *191115*1135*U*00401*000001661*0*T*>~GS*SH*SENDERID*RECEIVERID*20191115*1135*1661*X*004010~ST*856*0061~BSN*00*1234567890*20191115*1135*0001~HL*1**S~TD1*PLT*2****G*254.3*LB~TD5*O*2*ABCD*M*ABCD Freight Co.*******CG~REF*CN*123456789876543~REF*BM*987654321098765~DTM*011*20191115*1030~DTM*017*20191121~FOB*PP~N1*SF*VENDOR WAREHOUSE~N2*SHIPPING DEPT~N3*243 NORTH INDUSTRIAL PKWY*SUITE 3B~N4*ANYTOWN*WA*98001*US~PER*IC*JOHN SHIPPER*TE*9781237866*EM*[email protected]~N1*ST*D & H DISTRIBUTING CO.*92*01~N3*909 KATIE COURT*UNION SQUARE IND PK~N4*HARRISBURG*PA*17109*US~HL*2*1*O~PRF*908704L***20191110~REF*IA*12345~REF*IV*1234567890~REF*VN*987654321~HL*3*2*T~PO4*****G*201.1*LB~MAN*GM*00109111040123459991~

HL*4*3*I~LIN*1*VP*VENDSKU1-A3*BP*VENDSKU1A3*UP*123456789012~SN1**4*EA~PO4*1****G*4*LB~PID*F****Product Description~REF*SE*SN12988382764442~REF*SE*SN12988382764443~REF*SE*SN12988382764444~REF*SE*SN12988382764445~HL*5*3*I~LIN*2*VP*VENDSKU2-A6*BP*VENDSKU2A6*UP*123456789029~SN1**2*EA~PO4*1****G*3.2*LB~PID*F****Product Description~REF*SE*SN12988382768712~REF*SE*SN12988382768713~CTT*5~SE*42*0062~GE*1*1662~IEA*1*000001662~ LTL/TRUCK ASN EXAMPLE:ISA*00* *00* *ZZ*SENDERID *ZZ*RECEIVERID *191115*1135*U*00401*000001661*0*T*>~GS*SH*SENDERID*RECEIVERID*20191115*1135*1661*X*004010~ST*856*0061~BSN*00*1234567890*20191115*1135*0001~HL*1**S~TD1*PLT*2****G*254.3*LB~TD5*O*2*ABCD*M*ABCD Freight Co.*******CG~REF*CN*123456789876543~REF*BM*987654321098765~DTM*011*20191115*1030~DTM*017*20191121~FOB*PP~N1*SF*VENDOR WAREHOUSE~N2*SHIPPING DEPT~N3*243 NORTH INDUSTRIAL PKWY*SUITE 3B~N4*ANYTOWN*WA*98001*US~PER*IC*JOHN SHIPPER*TE*9781237866*EM*[email protected]~N1*ST*D & H DISTRIBUTING CO.*92*01~N3*909 KATIE COURT*UNION SQUARE IND PK~N4*HARRISBURG*PA*17109*US~HL*2*1*O~PRF*908704L***20191110~REF*IA*12345~REF*IV*1234567890~REF*VN*987654321~HL*3*2*T~PO4*****G*201.1*LB~MAN*GM*00109111040123459991~



HL*4*3*P~PO4*6****G*100.6*LB***48*40*24*IN~MAN*GM*00109111040123456785~HL*5*4*I~LIN*1*VP*VENDSKU1-A3*BP*VENDSKU1A3*UP*123456789012~SN1**4*EA~PO4*1****G*20*LB~PID*F****Product Description~REF*SE*SN12988382768798~REF*SE*SN12988382768799~REF*SE*SN12988382768800~REF*SE*SN12988382768801~HL*6*4*I~LIN*2*VP*VENDSKU2-A6*BP*VENDSKU2A6*UP*123456789029~SN1**2*EA~PO4*1****G*10.3*LB~PID*F****Product Description~REF*SE*SN12988382768802~REF*SE*SN12988382768803~HL*7*3*P~PO4*5****G*100.5*LB***48*40*24*IN~MAN*GM*00109111040123456792~HL*8*7*I~LIN*1*VP*VENDSKU1-A3*BP*VENDSKU1A3*UP*123456789012~SN1**5*EA~PO4*1****G*20*LB~REF*SE*SN12988382768804~REF*SE*SN12988382768805~REF*SE*SN12988382768806~REF*SE*SN12988382768807~REF*SE*SN12988382768808~HL*9*2*T~PO4*****G*53.2*LB~MAN*GM*00109111040123456808~HL*10*9*I~LIN*2*VP*VENDSKU2-A6*BP*VENDSKU2A6*UP*123456789029~SN1**5*EA~PO4*1****G*10.3*LB~PID*F****Product Description~REF*SE*SN12988382768809~REF*SE*SN12988382768810~REF*SE*SN12988382768811~REF*SE*SN12988382768812~REF*SE*SN12988382768813~CTT*10~SE*72*0061~GE*1*1661~IEA*1*000001661~

HL*4*3*P~PO4*6****G*100.6*LB***48*40*24*IN~MAN*GM*00109111040123456785~HL*5*4*I~LIN*1*VP*VENDSKU1-A3*BP*VENDSKU1A3*UP*123456789012~SN1**4*EA~PO4*1****G*20*LB~PID*F****Product Description~REF*SE*SN12988382768798~REF*SE*SN12988382768799~REF*SE*SN12988382768800~REF*SE*SN12988382768801~HL*6*4*I~LIN*2*VP*VENDSKU2-A6*BP*VENDSKU2A6*UP*123456789029~SN1**2*EA~PO4*1****G*10.3*LB~PID*F****Product Description~REF*SE*SN12988382768802~REF*SE*SN12988382768803~HL*7*3*P~PO4*5****G*100.5*LB***48*40*24*IN~MAN*GM*00109111040123456792~HL*8*7*I~LIN*1*VP*VENDSKU1-A3*BP*VENDSKU1A3*UP*123456789012~SN1**5*EA~PO4*1****G*20*LB~REF*SE*SN12988382768804~REF*SE*SN12988382768805~REF*SE*SN12988382768806~REF*SE*SN12988382768807~REF*SE*SN12988382768808~HL*9*2*T~PO4*****G*53.2*LB~MAN*GM*00109111040123456808~HL*10*9*I~LIN*2*VP*VENDSKU2-A6*BP*VENDSKU2A6*UP*123456789029~SN1**5*EA~PO4*1****G*10.3*LB~PID*F****Product Description~REF*SE*SN12988382768809~REF*SE*SN12988382768810~REF*SE*SN12988382768811~REF*SE*SN12988382768812~REF*SE*SN12988382768813~CTT*10~SE*72*0061~GE*1*1661~IEA*1*000001661~