856 Ship Notice/Manifest

ANSI ASC X12 4010

Version: 4.5 Final

Company: Daimler Trucks North

America, LLC
Publication: 5/20/2016
Trading Partner: All MFG Trading Partners
4/6/2017 Ship Notice/Manifest - 856

Table of Contents
856 Ship Notice/Manifest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 1
ISA Interchange Control Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 6
GS Functional Group Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 8
ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 10
BSN Beginning Segment for Ship Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 11
DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 12
HL Loop Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 13
HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 14
MEA Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 15
TD1 Carrier Details (Quantity and Weight) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 16
TD5 Carrier Details (Routing Sequence/Transit Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 17
TD3 Carrier Details (Equipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 18
REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 19
N1 Loop Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 21
N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 22
HL Loop Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 23
HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 24
LIN Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 25
SN1 Item Detail (Shipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 26
PRF Purchase Order Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 27
REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 28
CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 30
SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 31
GE Functional Group Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 32
IEA Interchange Control Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 33

IB856-DTNA-MFG-V4-6.ecs i Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

856 Ship Notice/Manifest

Functional Group= SH
Purpose: This Standard 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. The purpose of the Ship Notice/Manifest transaction, also known as
the "Advanced Ship Notice (ASN)," is to convey the contents of and key reference numbers related to a shipment of
material, e.g. Shipment Identification, Carrier PRO, Bill of Lading, Packing Slip, etc., placed in transit to a Daimler
Trucks North America (DTNA) facility. Shipment quantities in the 856 are a response (ideally from an integrated
system which excludes the need for data entry) to DTNA’s request from either the 830, 862 or 866. The data
transmitted in the 856 is used to facilitate the shipment tracking, material receipt, and payment of supplier invoices.
The Shipment Identification Number (SID) contained in the BSN02 element of the 856 is the primary reference used
in all of these processes.

An EDI 856 transmission (ISA through IEA segment) can consist of one or more transaction sets (ST through SE
segment). Each 856 transaction set will consist of three levels (shipment, item, and summary.) Segments in the
shipment level convey reference numbers, etc. which pertain to the shipment as a whole, while segments at the item
level describe a single part number within the shipment. Summary level segments are used to validate the
transaction (see CTT and SE segments). Generally, the order in which they are presented within each level is not
significant provided that all segments required are included; similarly, DTNA does not desire the inclusion of
segments not required in this implementation guide. The Manufacturing EDI Coordinator must be advised if one or
more segments required cannot be included in the transaction and/or segment(s) not required cannot be excluded;
all discrepancies will be addressed on a case by case basis and must be authorized prior to implementation of the
transaction. The 856 transaction may be requested of a supplier by two separate EDI implementation groups at
DTNA - Manufacturing and Aftermarket. The Manufacturing EDI Coordinator will test and implement the 856
transaction as it pertains to shipments made from the supplier to manufacturing locations, e.g. Portland Truck Plant,
Cleveland Truck Plant, etc. The Aftermarket EDI Coordinator will test and implement the 856 transaction as it
pertains to shipments made from the supplier to parts distribution centers (PDC's), e.g. Chicago Distribution Center,
Atlanta Distribution Center, etc, or to a Dealer location. While the contents and organization of these 856
transactions will be very similar, there are some differences, see Aftermarket 856 Implementation Guide.

Adherence to the following numbered items must be demonstrated:

1. The SID used in an EDI 856 transaction (element BSN02) must appear on the corresponding printed Packing Slip
(or similar) documents which travel with the physical shipment, in the upper right hand corner of the header portion
of the document. The number must be machine printed (handwritten is not acceptable) and appear exactly as it does
in the EDI data. If the shipping document contains multiple pages, the SID must appear on each page. For example.
if multiple packing slips are generated for a shipment, i.e. one packing slip per part per shipment, the same SID must
be machine printed on each one. The SID on the printed shipping document must be preceded by a literal, e.g.
"SID". The literal must also be machine printed. Alternate placement of the literal will be acceptable provided it is
intuitively obvious to which number the literal is referring (subject to DTNA’s approval.) The above requirements
must also be applied to the corresponding printed invoice document for the shipment.

2. The SID number must not include leading zeros. If this is an issue, precede leading zeros with a non-zero
alphanumeric character.

3. The SID must be a unique number which references an entire physical shipment and MUST NOT BE REUSED
WITHIN A ONE YEAR PERIOD.

4. If the EDI 810 (Invoice) transaction has been implemented with the supplier, the matching SID must appear in the
REF*SI segment (see 810 transaction).

IB856-DTNA-MFG-V4-6.ecs 1 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

5. The SID AND ANY OTHER TRACKING NUMBERS MUST BE PASSED TO THE CARRIER.

A supplier should generate and transmit an 856 transaction after the shipment has been sealed but within 30
minutes of the shipment leaving the dock.

Each 856 transaction received will be edited for conformance to requirements as described in this implementation
guide. Errors are reported to the Manufacturing EDI Coordinator if segments/elements required are missing or are
invalid.

If errors are detected in an 856, DTNA will send an 824 Application Advice to the supplier within 30 minutes. The 824
is a mandatory transaction for all suppliers sending 856s. The supplier will be advised of the error condition(s) with
an expectation that they will not be repeated in subsequent transmissions; corrective action may be requested as
well. NOTE: Suppliers must not retransmit 856 transactions which will result (or have resulted) in error(s) without
prior authorization; a retransmit will most likely result in duplicate error(s), further compounding the problem. Do not
resubmit the ASN after adding a character to the SID number. Contact an EDI Coordinator or material planner if you
have any questions about what will cause an error.

It is the supplier's responsibility to monitor 997 responses and 824 application error advices from DTNA and take
appropriate action to resolve transaction errors.

Here are some common errors found in a Manufacturing 856:

1. Invalid Item Number. The Item Number in the LIN segment was not found on DTNA’s database; this is a “hard”
error which prevents an in transit record from being created for the item on DTNA’s Purchasing System.

2. Invalid Purchase Order/Line Number. The Purchase Order (PO) and/or Line Number in the PRF segment was not
found on DTNA’s database or was found but not associated with the supplier, item number in corresponding LIN
segment, and/or ship-to location; this is a “hard” error which prevents an in transit record from being created for the
item.

NOTE: A unique manufacturing blanket PO number is established for each 856 supplier with unique line numbers
(within the blanket PO) assigned to each sourced item. Each PO line can then be opened for one or more
manufacturing ship-to locations.

3. Invalid Ship-to Location Code. The Ship-to Location Code in the N1*ST segment is not valid; this is a hard error
which prevents an in transit record from being created for all item(s) in the transaction.

4. Duplicate Transmission. A duplicate transmission was received (match is on elements ISA06 (Sender ID) + ISA09
(Transmit Date) + ISA10 (Transmit Time) + ISA13 (Control Number) + BSN02 (SID Number from last transaction in
transmission) + CTT01 + CTT02 (CTT01 and CTT02 are hash totals and are summed across all transaction(s) in
transmission for this edit). This is a “hard” error which prevents in transit record(s) from being created for the entire
transmission.

5. Duplicate SID/Item. A duplicate item number was received against SID Number in BSN segment (match is on
elements BSN02 (SID Number) + REF02 (Bill of Lading Number) + REF02 (Packing Slip Number) + SN102 (Ship
Quantity)); this is a “hard” error which prevents an in transit record from being created for the item. This error can
result within a single 856 (duplicate LIN loops) or across multiple transactions (perhaps a duplicate transmission was
sent but new ISA envelope was used causing edit #4 above to pass). MFG NOTE ONLY: A shipped item number
must be specified in one LIN loop only within an 856 unless it is packaged in such a way that dictates multiple
packing slip numbers and/or quantities be specified. For example, if item A is shipped for quantity = 10 and there is
one packing slip number associated with the item (or entire shipment), then specify one LIN loop in the 856 where
element SN102 (Ship Quantity) = 10; if two LIN loops are specified where SN102 = 5 in each, then DTNA’s system
will reject the second occurrence as a duplicate.

6. SID/Item Already Received. A truck plant receipt record was found for an item number specified in the 856 against
SID specified; this is a hard error which prevents an in transit record from being created for the item. This error can
result if the 856 is sent too late (truck plant has already received the material and entered computer receipt
transactions from the shipment paperwork, i.e. packing list).

IB856-DTNA-MFG-V4-6.ecs 2 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Example MFG X12 856 Transaction:

ISA*00* *00* *ZZ*ABCD MFG *ZZ*FTL MFG *120710*1634*U*00401*000001040*0*P*:

GS*SH*ABCD MFG*FTL MFG*20120710*1634*83*X*004010

ST*856*830001

BSN*00*21551*20120710*1634

DTM*011*20120713*1229*PT

HL*1**S

MEA*PD*G*70.560*LB

TD1*BOX25*4

TD5*B*2*CDNK*M

TD3*TL**ABCD123456

REF*CN*123456789123456789123456789312

REF*PK*900021551

REF*BM*900021551

REF*98*XL-3031**ZZ:3

REF*98*XL-2000**ZZ:1

REF*98*EXPENDABLE**ZZ:1:91:12.00

N1*SU*ABCD Company*92*ABCD

N1*ST**92*065

HL*2*1*I

LIN*1*BP*A22-57054-002***CH*US

SN1**1*EA

PRF*A04354****003

REF*VT*AV1951

REF*98*XL-2000**ZZ:1

HL*3*1*I

LIN*2*BP*16-15641-000***CH*US

SN1**100*EA

PRF*A04354****005

REF*VT*AV1952

REF*98*XL-3031**ZZ:3

IB856-DTNA-MFG-V4-6.ecs 3 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

REF*98*EXPENDABLE**ZZ:1:91:12.00

CTT*3*2

SE*31*830001

GE*1*83

IEA*1*000001040

IB856-DTNA-MFG-V4-6.ecs 4 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Heading:
Pos Id Segment Name Req Max Use Repeat Notes Usage
001 ISA Interchange Control Header M 1 N1/001 Must use
002 GS Functional Group Header M 1 Must use
010 ST Transaction Set Header M 1 Must use
020 BSN Beginning Segment for Ship M 1 Must use
Notice
040 DTM Date/Time Reference M 1 Must use

Detail:
Pos Id Segment Name Req Max Use Repeat Notes Usage
LOOP ID - HL 200000 N2/010L
010 HL Hierarchical Level M 1 Must use
080 MEA Measurements M 1 Must use
110 TD1 Carrier Details (Quantity M 2 Must use
and Weight)
120 TD5 Carrier Details (Routing M 1 Must use
Sequence/Transit Time)
130 TD3 Carrier Details (Equipment) M 1 Must use
150 REF Reference Identification M 200 Must use
LOOP ID - N1 3
220 N1 Name M 1 Must use

LOOP ID - HL 200000 N2/020L

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
050 PRF Purchase Order Reference M 1 Must use
150 REF Reference Identification C 3000 Dependent

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
998 GE Functional Group Trailer M 1 Must use
999 IEA Interchange Control Trailer M 1 Must use

Notes:
1/001 DTNA will not send an outbound 824 transaction in response to an inbound 856 that has errors when the
Usage Indicator in the ISA15 of the 856 is "T", indicating test data.
2/010L This HL Loop is for the Shipment Level Detail
2/020L This HL Loop is for the Item Level Detail
3/010 Number of line items (CTT01) is the accumulation of the number of HL segments. Hash total (CTT02) is
the sum of the value of units shipped (SN102) for each SN1 segment.

IB856-DTNA-MFG-V4-6.ecs 5 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 001 Max: 1

ISA Interchange Control Header Heading - Mandatory
Loop: N/A 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 Element Name Req Type Min/Max Usage
ISA01 I01 Authorization Information Qualifier M ID 2/2 Must use

Description: Code to identify the type of information in the Authorization Information

CodeList Summary (Total Codes: 7, Included: 1)

Code Name
00 No Authorization Information Present (No Meaningful Information in I02)

ISA02 I02 Authorization Information M AN 10/10 Must use

Description: 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). Typical DTNA implementations require no
information in this element (i.e. it is entirely populated with space characters).
ISA03 I03 Security Information Qualifier M ID 2/2 Must use

Description: Code to identify the type of information in the Security Information

CodeList Summary (Total Codes: 2, Included: 1)

Code Name
00 No Security Information Present (No Meaningful Information in I04)

ISA04 I04 Security Information M AN 10/10 Must use

Description: 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). Typical DTNA implementations require no information in this
element (i.e. it is entirely populated with space characters).
ISA05 I05 Interchange ID Qualifier M ID 2/2 Must use

Description: Qualifier to designate the system/method of code structure used to designate

the sender or receiver ID element being qualified. For the DTNA implementation this value
is usually "ZZ" (mutually defined).
All valid standard codes are used. (Total Codes: 38)

ISA06 I06 Interchange Sender ID M AN 15/15 Must use

Description: 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. The Sender's ISA ID.
ISA07 I05 Interchange ID Qualifier M ID 2/2 Must use

Description: Qualifier to designate the system/method of code structure used to designate

the sender or receiver ID element being qualified. For the DTNA implementation this value
is usually "ZZ" (mutually defined).
All valid standard codes are used. (Total Codes: 38)

IB856-DTNA-MFG-V4-6.ecs 6 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Ref Id Element Name Req Type Min/Max Usage

ISA08 I07 Interchange Receiver ID M AN 15/15 Must use

Description: 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. The Receiver's ISA ID.
ISA09 I08 Interchange Date M DT 6/6 Must use

Description: Date of the interchange

ISA10 I09 Interchange Time M TM 4/4 Must use

Description: Time of the interchange expressed in 24-hour clock time as follows: HHMM.

ISA11 I10 Interchange Control Standards M ID 1/1 Must use

Identifier

Description: Code to identify the agency responsible for the control standard used by the
message that is enclosed by the interchange header and trailer

CodeList Summary (Total Codes: 2, Included: 1)

Code Name
U U.S. EDI Community of ASC X12, TDCC, and UCS

ISA12 I11 Interchange Control Version Number M ID 5/5 Must use

Description: Code specifying the version number of the interchange control segments

CodeList Summary (Total Codes: 14, Included: 1)

Code Name
00401 Draft Standards for Trial Use Approved for Publication by ASC X12 Procedures
Review Board through October 1997

ISA13 I12 Interchange Control Number M N0 9/9 Must use

Description: A control number assigned by the interchange sender. This must match the
identifying number in the IEA02 element.
ISA14 I13 Acknowledgment Requested M ID 1/1 Must use

Description: Code sent by the sender to request an interchange acknowledgment (TA1).

All valid standard codes are used. (Total Codes: 2)

ISA15 I14 Usage Indicator M ID 1/1 Must use

Description: Code to indicate whether data enclosed by this interchange envelope is test,
production or information

CodeList Summary (Total Codes: 3, Included: 2)

Code Name
P Production Data
T Test Data

ISA16 I15 Component Element Separator M 1/1 Must use

Description: 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

IB856-DTNA-MFG-V4-6.ecs 7 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 002 Max: 1

GS Functional Group Header Heading - Mandatory
Loop: N/A 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 Element Name Req Type Min/Max Usage
GS01 479 Functional Identifier Code M ID 2/2 Must use

Description: Code identifying a group of application related transaction sets. For the 856
transaction the value "SH" is used in this element.

CodeList Summary (Total Codes: 240, Included: 1)

Code Name
SH Ship Notice/Manifest (856)

GS02 142 Application Sender's Code M AN 2/15 Must use

Description: Code identifying party sending transmission; codes agreed to by trading

partners
GS03 124 Application Receiver's Code M AN 2/15 Must use

Description: Code identifying party receiving transmission; codes agreed to by trading

partners
GS04 373 Date M DT 8/8 Must use

Description: Date expressed as CCYYMMDD

GS05 337 Time M TM 4/8 Must use

Description: 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)
GS06 28 Group Control Number M N0 1/9 Must use

Description: Assigned number originated and maintained by the sender

GS07 455 Responsible Agency Code M ID 1/2 Must use

Description: Code identifying the issuer of the standard; this code is used in conjunction
with Data Element 480

CodeList Summary (Total Codes: 2, Included: 1)

Code Name
X Accredited Standards Committee X12

GS08 480 Version / Release / Industry Identifier M AN 1/12 Must use

Code

Description: 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,

IB856-DTNA-MFG-V4-6.ecs 8 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Ref Id Element Name Req Type Min/Max Usage

then other formats are allowed

CodeList Summary (Total Codes: 39, Included: 1)

Code Name
004010 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.

IB856-DTNA-MFG-V4-6.ecs 9 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 010 Max: 1

ST Transaction Set Header Heading - Mandatory
Loop: N/A 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 Usage
ST01 143 Transaction Set Identifier Code M ID 3/3 Must use

Description: Code uniquely identifying a Transaction Set

CodeList Summary (Total Codes: 298, Included: 1)

Code Name
856 Ship Notice/Manifest

ST02 329 Transaction Set Control Number M AN 4/9 Must use

Description: Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set

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., "856" selects the Advanced Ship Notice Transaction Set).
2. The Transaction Set Control Number (ST02) must be identical to the same data element in the associated SE
segment (SE02).

IB856-DTNA-MFG-V4-6.ecs 10 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 020 Max: 1

BSN Beginning Segment for Ship Heading - Mandatory

Notice Loop: N/A Elements: 4

User Option (Usage): Must use

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

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
BSN01 353 Transaction Set Purpose Code M ID 2/2 Must use

Description: Code identifying purpose of transaction set

CodeList Summary (Total Codes: 65, Included: 1)

Code Name
00 Original

BSN02 396 Shipment Identification M AN 2/30 Must use

Description: A unique control number assigned by the original shipper to identify a

specific shipment. NOTE: The Shipment Identification MUST BE a unique,
supplier-assigned Shipment ID number (SID) THAT IS NOT REPEATED WITHIN A ONE
YEAR PERIOD. The SID must not contain leading zeros. The DTNA application will only
process the first 16 characters of the BSN02 element (SID).
BSN03 373 Date M DT 8/8 Must use

Description: Date expressed as CCYYMMDD

BSN04 337 Time M TM 4/8 Must use

Description: 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)

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

IB856-DTNA-MFG-V4-6.ecs 11 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 040 Max: 1

DTM Date/Time Reference Heading - Mandatory
Loop: N/A Elements: 4

User Option (Usage): Must use

Purpose: To specify pertinent dates and times

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
DTM01 374 Date/Time Qualifier M ID 3/3 Must use

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

CodeList Summary (Total Codes: 1112, Included: 1)

Code Name
011 Shipped

DTM02 373 Date M DT 8/8 Must use

Description: Date expressed as CCYYMMDD

DTM03 337 Time O TM 4/8 Recommended

Description: 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)
DTM04 623 Time Code O ID 2/2 Dependent

Description: Code identifying the time. In accordance with International Standards

Organization standard 8601, time can be specified by a + or - and an indication in hours in
relation to Universal Time Coordinate (UTC) time; since + is a restricted character, + and -
are substituted by P and M in the codes that follow
All valid standard codes are used. (Total Codes: 51)

Syntax Rules:
1. R0203 - At least one of DTM02 or DTM03 is required.
2. C0403 - If DTM04 is present, then DTM03 is required.

IB856-DTNA-MFG-V4-6.ecs 12 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 010 Repeat:

Loop Hierarchical Level 200000
Mandatory
Loop: HL Elements: N/A

User Option (Usage): Must use

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

Loop Summary:
Pos Id Segment Name Req Max Use Repeat Usage
010 HL Hierarchical Level M 1 Must use
080 MEA Measurements M 1 Must use
110 TD1 Carrier Details (Quantity and Weight) M 2 Must use
120 TD5 Carrier Details (Routing Sequence/Transit M 1 Must use
Time)
130 TD3 Carrier Details (Equipment) M 1 Must use
150 REF Reference Identification M 200 Must use
220 Loop N1 M 3 Must use

Comments:
1. This HL Loop is for the Shipment level detail.

IB856-DTNA-MFG-V4-6.ecs 13 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 010 Max: 1

HL Hierarchical Level Detail - Mandatory
Loop: HL Elements: 2

User Option (Usage): Must use

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

This HL is for the Shipment Detail Level.

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
HL01 628 Hierarchical ID Number M AN 1/12 Must use

Description: A unique number assigned by the sender to identify a particular data

segment in a hierarchical structure.

Note: The HL01 at this level will always be “1”.

HL03 735 Hierarchical Level Code M ID 1/2 Must use

Description: Code defining the characteristic of a level in a hierarchical structure.

Note: The HL03 at this level will always be “S”.

CodeList Summary (Total Codes: 170, Included: 1)

Code Name
S 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 DTNA's purposes the HL01 in this position (Shipment Level Detail) will ALWAYS have a value of "1".
This is because only one unique shipment is allowed to be transmitted for each unique 856 transaction.
4. 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.
For DTNA's purposes the HL03 in this position (Shipment Level Detail) will ALWAYS have a value of "S". This
is because all the data elements that follow this HL will relate to the Shipment.

IB856-DTNA-MFG-V4-6.ecs 14 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 080 Max: 1

MEA Measurements Detail - Mandatory
Loop: HL Elements: 4

User Option (Usage): Must use

Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
MEA01 737 Measurement Reference ID Code M ID 2/2 Must use

Description: Code identifying the broad category to which a measurement applies

CodeList Summary (Total Codes: 152, Included: 1)

Code Name
PD Physical Dimensions

MEA02 738 Measurement Qualifier M ID 1/3 Must use

Description: Code identifying a specific product or process characteristic to which a

measurement applies

CodeList Summary (Total Codes: 920, Included: 1)

Code Name
G Gross Weight

MEA03 739 Measurement Value M R 1/20 Must use

Description: The value of the measurement. Must be greater than or equal to "1.0".

MEA04 C001 Composite Unit of Measure M Comp Must use

Description: To identify a composite unit of measure. This is a composite element, which

indicates that the element immediately following this element (MEA04, element number
355) is included in the actual data, but this element (C001) does not show up in the EDI
X12 segment data. Example: MEA*PD*G*7.54*LB~ is correct.
MEA04-01 355 Unit or Basis for Measurement Code M ID 2/2 Must use

Description: Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken.

CodeList Summary (Total Codes: 794, Included: 2)

Code Name
KG Kilogram
LB Pound

Semantics:
1. MEA04 defines the unit of measure for MEA03

Comments:
1. This MEA is at the Shipment Level

IB856-DTNA-MFG-V4-6.ecs 15 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 110 Max: 2

TD1 Carrier Details (Quantity and Detail - Mandatory

Weight) Loop: HL Elements: 2

User Option (Usage): Must use

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

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
TD101 103 Packaging Code M AN 3/5 Must use

Description: Code identifying the type of packaging; Part 1: Packaging Form, Part 2:
Packaging Material; if the Data Element is used, then Part 1 is always required.

Note: Use Packaging Code of the shipping unit (e.g. ten boxes on one pallet is specified as
one pallet).

All valid X12 codes are used. Refer to 004010 Data Element Dictionary for acceptable code
values. Some typical codes from ANSI ASC X12 Data Element Dictionary are:

"BAG13" = Bag;

"BBL52" = Barrel;

"BIN51" = Wire Mesh Bin;

"BIN52" = Steel Bin;

"BOX25" = Cardboard Box;

"COL52" = Steel Coil;

"CRT71" = Crate;

"CTN25" = Cardboard Carton;

"LSE71" = Loose;

"MIX90" = Mixed;

"PLT71" = Pallet;

"RCK58" = Rack;

"SKD71" = Skid
All valid standard codes are used. (Total Codes: 203)

TD102 80 Lading Quantity M N0 1/7 Must use

Description: Number of units (pieces) of the lading commodity

Syntax Rules:
1. C0102 - If TD101 is present, then TD102 is required.

IB856-DTNA-MFG-V4-6.ecs 16 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 120 Max: 1

TD5 Carrier Details (Routing Detail - Mandatory

Sequence/Transit Time) Loop: HL Elements: 4

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 Usage
TD501 133 Routing Sequence Code M ID 1/2 Must use

Description: Code describing the relationship of a carrier to a specific shipment movement

CodeList Summary (Total Codes: 23, Included: 1)

Code Name
B Origin/Delivery Carrier (Any Mode)

TD502 66 Identification Code Qualifier M ID 1/2 Must use

Description: Code designating the system/method of code structure used for Identification
Code (67)

CodeList Summary (Total Codes: 215, Included: 1)

Code Name
2 Standard Carrier Alpha Code (SCAC)

TD503 67 Identification Code M AN 2/80 Must use

Description: Code identifying a party or other code

TD504 91 Transportation Method/Type Code M ID 1/2 Must use

Description: Code specifying the method or type of transportation for the shipment

CodeList Summary (Total Codes: 71, Included: 4)

Code Name
A Air
M Motor (Common Carrier)
Q Conventional Ocean
R Rail
Syntax Rules:
1. P0203 - If either TD502 or TD503 is present, then the other is required.

IB856-DTNA-MFG-V4-6.ecs 17 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 130 Max: 1

TD3 Carrier Details (Equipment) Detail - Mandatory
Loop: HL Elements: 2

User Option (Usage): Must use

Purpose: To specify transportation details relating to the equipment used by the carrier

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
TD301 40 Equipment Description Code M ID 2/2 Must use

Description: Code identifying type of equipment used for shipment

CodeList Summary (Total Codes: 134, Included: 1)

Code Name
TL Trailer (not otherwise specified)

TD303 207 Equipment Number M AN 1/10 Must use

Description: Sequencing or serial part of an equipment unit's identifying number (pure

numeric form for equipment number is preferred). This element is required for Import
Security Filings (ISF) with Customs and Border Protection (CBP).

IB856-DTNA-MFG-V4-6.ecs 18 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 150 Max: 200

REF Reference Identification Detail - Mandatory
Loop: HL Elements: 4

User Option (Usage): Must use

Purpose: To specify identifying information

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
REF01 128 Reference Identification Qualifier M ID 2/3 Must use

Description: Code qualifying the Reference Identification

CodeList Summary (Total Codes: 1503, Included: 4)

Code Name
98 Container/Packaging Specification Number
BM Bill of Lading Number
CN Carrier's Reference Number (PRO/Invoice)
PK Packing List Number

REF02 127 Reference Identification X AN 1/30 Used

Description: Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier.

Bill of Lading Number max size: 16

Carrier’s PRO Number max size: 30

Packing List Number max size: 10

REF03 352 Description X AN 1/80 Used

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

REF04 C040 Reference Identifier O Comp Used

Description: To identify one or more reference numbers or identification numbers as

specified by the Reference Qualifier
REF04-01 128 Reference Identification Qualifier M ID 2/3 Must use

Description: Code qualifying the Reference Identification

CodeList Summary (Total Codes: 1503, Included: 1)

Code Name
ZZ Mutually Defined

REF04-02 127 Reference Identification M AN 1/30 Must use

Description: Number of returnable containers. This is required with REF01 = 98

REF04-03 128 Reference Identification Qualifier X ID 2/3 Used

Description: Code qualifying the Reference Identification

CodeList Summary (Total Codes: 1503, Included: 1)

Code Name
91 Cost Element

IB856-DTNA-MFG-V4-6.ecs 19 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

REF04-04 127 Reference Identification X AN 1/30 Used

Description: Optional cost associated with the expendable container.

Comments:
1. This instance of the REF Segment is at the Shipment Level only.
2. If an air carrier is used, the air waybill or tracking number must be present in the REF*CN segment. If a parcel
carrier is used, the tracking number must be present in the REF*CN segment. If a LTL carrier is used, the
carrier's reference number must be present in the REF*CN segment.
3. REF01 = 98 is used to provide details about returnable containers.

IB856-DTNA-MFG-V4-6.ecs 20 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 220 Repeat: 3

Loop Name Mandatory
Loop: N1 Elements: N/A

User Option (Usage): Must use

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

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

Comments:
1. The N1 Loop is at the Shipment Level.

IB856-DTNA-MFG-V4-6.ecs 21 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 220 Max: 1

N1 Name Detail - Mandatory
Loop: N1 Elements: 4

User Option (Usage): Must use

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

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
N101 98 Entity Identifier Code M ID 2/3 Must use

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

individual

CodeList Summary (Total Codes: 1312, Included: 2)

Code Name
ST Ship To
SU Supplier/Manufacturer

N102 93 Name X AN 1/60 Used

Description: Free-form name

N103 66 Identification Code Qualifier M ID 1/2 Must use

Description: Code designating the system/method of code structure used for Identification
Code (67)

CodeList Summary (Total Codes: 215, Included: 1)

Code Name
92 Assigned by Buyer or Buyer's Agent

N104 67 Identification Code M AN 2/80 Must use

Description: Code identifying a party or other code. When N101 = 'SU' then N104 must
contain the DTNA assigned vendor code for the supplier. When N101 = 'ST' then N104
must contain the DTNA assigned Ship To Code.

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 transaction
processing party.

IB856-DTNA-MFG-V4-6.ecs 22 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 020 Repeat:

Loop Hierarchical Level 200000
Mandatory
Loop: HL Elements: N/A

User Option (Usage): Must use

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

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
050 PRF Purchase Order Reference M 1 Must use
150 REF Reference Identification C 3000 Dependent

Comments:
1. This HL Loop is for the Item level detail.

IB856-DTNA-MFG-V4-6.ecs 23 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 010 Max: 1

HL Hierarchical Level Detail - Mandatory
Loop: HL Elements: 3

User Option (Usage): Must use

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

This HL is for the Item Detail Level.

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
HL01 628 Hierarchical ID Number M AN 1/12 Must use

Description: A unique number assigned by the sender to identify a particular data

segment in a hierarchical structure.

For the DTNA implementation the value of the first HL01 at the item level must be "2" and
increase by 1 for each subsequent HL loop at the item level.
HL02 734 Hierarchical Parent ID Number M AN 1/12 Must use

Description: Identification number of the next higher hierarchical data segment that the
data segment being described is subordinate to.

Because DTNA only allows one shipment per 856 transaction the value of the HL02 at the
item level will always be "1"
HL03 735 Hierarchical Level Code M ID 1/2 Must use

Description: Code defining the characteristic of a level in a hierarchical structure. The

value of the HL03 element at the item level will always be "I".

CodeList Summary (Total Codes: 170, Included: 1)

Code Name
I Item

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 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.
4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.
Since only one shipment per 856 transaction is allowed the value of the HL02 at the item level will always be
"1".
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 subsequent
segments in the HL loop form a logical grouping of data referring to shipment, order, or item-level information.
The value of the HL03 at the item level will always be "I".

IB856-DTNA-MFG-V4-6.ecs 24 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 020 Max: 1

LIN Item Identification Detail - Mandatory
Loop: HL Elements: 7

User Option (Usage): Must use

Purpose: To specify basic item identification data

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
LIN01 350 Assigned Identification M AN 1/20 Must use

Description: Alphanumeric characters assigned for differentiation within a transaction set.

Values must start with 1 and increase by 1 for each subsequent LIN loop.
LIN02 235 Product/Service ID Qualifier M ID 2/2 Must use

Description: Code identifying the type/source of the descriptive number used in

Product/Service ID (234)

CodeList Summary (Total Codes: 477, Included: 1)

Code Name
BP Buyer's Part Number

LIN03 234 Product/Service ID M AN 1/48 Must use

Description: Identifying number for a product or service. In this implementation this is the
buyer's part number of the material.
LIN06 235 Product/Service ID Qualifier M ID 2/2 Must use

Description: Code identifying the type/source of the descriptive number used in

Product/Service ID (234)

CodeList Summary (Total Codes: 477, Included: 1)

Code Name
CH Country of Origin Code

LIN07 234 Product/Service ID M AN 2/2 Must use

Description: Identifying number for a product or service. For the DTNA implementation
this element contains the appropriate two digit standard code for the country of origin of the
material.
LIN08 235 Product/Service ID Qualifier X ID 2/2 Used

Description: Code identifying the type/source of the descriptive number used in

Product/Service ID (234)

CodeList Summary (Total Codes: 477, Included: 1)

Code Name
ZZ Engine Family Code

LIN09 234 Product/Service ID X AN 1/48 Used

Description: Engine Family Code

IB856-DTNA-MFG-V4-6.ecs 25 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 030 Max: 1

SN1 Item Detail (Shipment) Detail - Mandatory
Loop: HL Elements: 2

User Option (Usage): Must use

Purpose: To specify line-item detail relative to shipment

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
SN102 382 Number of Units Shipped M R 1/10 Must use

Description: Numeric value of units shipped in manufacturer's shipping units for a line
item or transaction set.

Note: Use whole numbers

SN103 355 Unit or Basis for Measurement Code M ID 2/2 Must use

Description: Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken. Note: This shall be the same Unit of Measure
provided on the corresponding releasing document (830, 862, 866).

Comments:
1. SN103 defines the unit of measurement for SN102.
2. SN1 is at the Item Level.

IB856-DTNA-MFG-V4-6.ecs 26 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 050 Max: 1

PRF Purchase Order Reference Detail - Mandatory
Loop: HL 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 Usage
PRF01 324 Purchase Order Number M AN 6/10 Must use

Description: Identifying number for Purchase Order assigned by the orderer/purchaser.

Note: Use PO number provided on releasing documents (830, 862, 866).

PRF05 350 Assigned Identification O AN 1/5 Used

Description: Alphanumeric characters assigned for differentiation within a transaction set.

For the DTNA/TBB MFG implementation the PRF05 element is expected to contain the PO
LINE NUMBER. This element is limited to 3 characters for DTNA, 5 characters for TBB,
AND must include any leading zeros from the PO Line Number that was sent in the
830/862/866.

Comments:
1. PRF is at the Item Level

IB856-DTNA-MFG-V4-6.ecs 27 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 150 Max: 3000

REF Reference Identification Detail - Conditional
Loop: HL Elements: 4

User Option (Usage): Dependent

Purpose: To specify identifying information.

1. This segment is only used if the trading partner receives an 866 or an 830 for a major component.

2. One REF*SE segment must be included for each major component part shipped, e.g. engine, transmission, etc.;
for example, if SN102 (Shipment Quantity) = 10, then there should be 10 REF*SE segments included within the
same LIN loop, each specifying a unique serial number.

3. One or more REF*VT segments must be included which indicate all vehicle serial truck number(s) for which the
part specified in the previous LIN segment is to be assembled onto/within (typically one REF*VT per occurrence of
the part). The serial truck numbers to use should come directly from the 866 transaction data which initiated the
shipment. The REF*VT segment is used to flag the part as shipped in DTNA’s Line Sequence System for the vehicle
serial truck number identified, therefore causing 866 data to not be sent again to the supplier for the vehicle/part
number, even in the event of a scheduling change (vehicle's build date is moved out into the future after shipment of
material pegged to the vehicle has been made).

Element Summary:
Ref Id Element Name Req Type Min/Max Usage
REF01 128 Reference Identification Qualifier M ID 2/3 Must use

Description: Code qualifying the Reference Identification

CodeList Summary (Total Codes: 1503, Included: 4)

Code Name
98 Container/Packaging Specification Number
LS Bar-Coded Serial Number of part number
SE Serial Number of part number
VT DTNA Truck number from 866

REF02 127 Reference Identification X AN 1/30 Used

Description: Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier. Serial number of part number max size:
15. Packing List Number max size: 10. DTNA Truck number max size: 6.
REF03 352 Description X AN 1/80 Used

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

REF04 C040 Reference Identifier O Comp Used

Description: To identify one or more reference numbers or identification numbers as

specified by the Reference Qualifier
REF04-01 128 Reference Identification Qualifier M ID 2/3 Must use

Description: Code qualifying the Reference Identification

CodeList Summary (Total Codes: 1503, Included: 1)

Code Name
ZZ Mutually Defined

REF04-02 127 Reference Identification M AN 1/30 Must use

IB856-DTNA-MFG-V4-6.ecs 28 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Ref Id Element Name Req Type Min/Max Usage

Description: Number of returnable containers. This is required with REF01 = 98

REF04-03 128 Reference Identification Qualifier X ID 2/3 Used

Description: Code qualifying the Reference Identification

CodeList Summary (Total Codes: 1503, Included: 1)

Code Name
91 Cost Element

REF04-04 127 Reference Identification X AN 1/30 Used

Description: Optional cost associated with the expendable container.

Comments:
1. This REF Segment is at the Item Level.
2. REF01 = 98 is used to provide details about returnable containers.

IB856-DTNA-MFG-V4-6.ecs 29 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 010 Max: 1

CTT Transaction Totals Summary - Mandatory
Loop: N/A 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 Usage
CTT01 354 Number of Line Items M N0 1/6 Must use

Description: Total number of HL segments in the transaction set

CTT02 347 Hash Total M R 1/10 Must use

Description: Hash total of quantity shipped (SN102).

This element will contain the sum of values of the specified data element. All values in the
data element will be summed without regard to decimal points (explicit or implicit) or signs.
Truncation will occur on the left most digits if the sum is greater than the maximum size of
the hash total of the data element. Example: -.0018 First occurrence of value being
hashed. .18 Second occurrence of value being hashed. 1.8 Third occurrence of value
being hashed. 18.01 Fourth occurrence of value being hashed. --------- 1855 Hash total
prior to truncation. 855 Hash total after truncation to three-digit field.

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

IB856-DTNA-MFG-V4-6.ecs 30 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 020 Max: 1

SE Transaction Set Trailer Summary - Mandatory
Loop: N/A 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 Usage
SE01 96 Number of Included Segments M N0 1/10 Must use

Description: Total number of segments included in a transaction set including ST and SE

segments
SE02 329 Transaction Set Control Number M AN 4/9 Must use

Description: Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set. Must equal ST02.

Semantics:
1. The Transaction Set Control Number (SE02) must be identical to the same data element in the associated ST
segment (ST02).

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

IB856-DTNA-MFG-V4-6.ecs 31 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 998 Max: 1

GE Functional Group Trailer Summary - Mandatory
Loop: N/A 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 Usage
GE01 97 Number of Transaction Sets Included M N0 1/6 Must use

Description: Total number of transaction sets included in the functional group or

interchange (transmission) group terminated by the trailer containing this data element
GE02 28 Group Control Number M N0 1/9 Must use

Description: Assigned number originated and maintained by the sender. This must match
the identifying number in the GS06 element.

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 the
corresponding header.

IB856-DTNA-MFG-V4-6.ecs 32 Daimler Trucks North America, LLC

4/6/2017 Ship Notice/Manifest - 856

Pos: 999 Max: 1

IEA Interchange Control Trailer Summary - Mandatory
Loop: N/A 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 Usage
IEA01 I16 Number of Included Functional Groups M N0 1/5 Must use

Description: A count of the number of functional groups included in an interchange

IEA02 I12 Interchange Control Number M N0 9/9 Must use

Description: A control number assigned by the interchange sender. This must match the
identifying number in the ISA13 element.

IB856-DTNA-MFG-V4-6.ecs 33 Daimler Trucks North America, LLC