856iv4010 DTNA AFTMKT V4 7

856 Ship Notice/Manifest -
Aftermarket
ANSI ASC X12 4010
Version: 4.7 Final
Company: Daimler Trucks North

America, LLC (DTNA)
Publication: 12/7/2016
Trading Partner: All AFTMKT Trading
Partners
12/7/2016 Ship Notice/Manifest - 856
Table of Contents
856 Ship Notice/Manifest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 1
ISA Interchange Control Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . . 9
GS Functional Group Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 12
ST Transaction Set Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 14
BSN Beginning Segment for Ship Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 15
DTM Date/Time Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 16
HL Loop Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 17
HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 18
MEA Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 19
TD1 Carrier Details (Quantity and Weight) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 20
TD5 Carrier Details (Routing Sequence/Transit Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 21
TD3 Carrier Details (Equipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 22
REF Reference Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 23
FOB F.O.B. Related Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 24
N1 Loop Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 25
N1 Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 26
HL Loop Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 27
HL Hierarchical Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 28
LIN Item Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 29
SN1 Item Detail (Shipment) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 30
PRF Purchase Order Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 31
. . 32
CLD Loop Load Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 33
CLD Load Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 34
. . 35
MAN Marks and Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . <PH>
. . 36
CTT Transaction Totals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 37
SE Transaction Set Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 38
GE Functional Group Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 39
IEA Interchange Control Trailer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . <PH>
. . 40
IB856-DTNA-AFTMKT-V4-7.ecs i Daimler Trucks North America, LLC

(DTNA)
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 the shipment to the receiver 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 for materials via fax, email, or an EDI 850 transaction. 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 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. Memphis Distribution Center, Atlanta Distribution Center, etc, or to a Customer location. While the
contents and organization of these 856 transactions will be very similar, there are some differences, see
Manufacturing 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 must be a unique number which references an entire physical shipment from end-to-end for one ship-to
destination, and MUST NOT BE REUSED WITHIN A CALENDAR YEAR PERIOD.
3. If the EDI 810 (Invoice) transaction has been implemented with the supplier, the matching SID must appear in the
REF*SI segment in the invoice (see 810 transaction).
4. The SID AND ANY OTHER IDENTIFICATION 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.
IB856-DTNA-AFTMKT-V4-7.ecs 1 Daimler Trucks North America, LLC

(DTNA)
Each 856 transaction received will be edited for conformance to requirements as described in this implementation
guide. Errors are reported on EDI 824 to the sender, if required segments/elements are missing or are invalid.
If errors are detected in an 856 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. You may contact an EDI
Coordinator if you have any questions about what can cause an error.
It is the supplier's responsibility to monitor 997 and 824 responses from DTNA and take appropriate action to resolve
transaction errors.
EXAMPLE X12 DATA:
ASNs without CLD loop
ST*856*000000025~
BSN*00*SAL28842*20160513*1815~
DTM*011*20160513*1915~
HL*1**S~
MEA*PD*G*82*LB~
TD1*CTN25*12~
TD5*B*2*EXEP*M~
TD3*TL**258272346~
REF*BM*04070~
REF*PK*SAL28842~
REF*CN*258272346~
N1*SU**92*AA42~
N1*ST**92*20A~
HL*2*1*I~
LIN*001*BP*F6HZ 13201 AAA*VN*9FL 938 167-16*CH*US~
SN1**12*EA~
PRF*4502299166***20160513*010~
CTT*2*12~
SE*19*000000025~

(DTNA)
ASN with variants of CLD loop
ST*856*3586~
BSN*00*903568875*20160502*2136~
DTM*011*20160502*2136~
HL*1**S~
MEA*PD*G*5813*LB~
TD1*CTN25*1~
TD5*B*2*PITD*M*NA~
TD3*TL**OEM 7288~
REF*BM*903568875~
REF*CN*903568875~
REF*PK*903568875~
N1*SE**92*CUM2~
N1*SU**92*CUM2~
N1*SO**92*24A~
N1*ST**92*24A~
HL*2*1*I~
LIN*001*BP*FG AF25057***CH*US~
SN1**1*EA~
PRF*4502289570****010~
CLD*1*1*PLT71~
REF*LS*CUM220025~
HL*3*1*I~
LIN*002*BP*FG AH1135M***CH*US~
SN1**1*EA~
PRF*4502289571****010~
CLD*1*1*PLT71~
REF*LS*CUM220032~
HL*4*1*I~
LIN*003*BP*FG FF5137***CH*US~

(DTNA)
SN1**12*EA~
PRF*4502307881****010~
CLD*1*12*PLT71~
REF*LS*CUM220027~
HL*5*1*I~
LIN*004*BP*FG 91085S***CH*US~
SN1**25*EA~
PRF*4502262658****010~
CLD*1*8*PLT71~
REF*LS*CUM220029~
CLD*1*17*PLT71~
REF*LS*CUM220029~
HL*6*1*I~
LIN*005*BP*FG FS19727***CH*US~
SN1**6*EA~
PRF*4502289569****010~
CLD*2*3*PLT71~
REF*LS*CUM220024~
REF*LS*CUM220028~
HL*7*1*I~
LIN*006*BP*FG AF911***CH*US~
SN1**1*EA~
PRF*4502273581****010~
CLD*1*1*PLT71~
REF*LS*CUM220025~
CTT*5*46~
SE*83*3586~

(DTNA)
Third Party ASN
ST*856*0001~
BSN*00*2549608*20160516*0641~
DTM*011*20160516*0641~
HL*1**S~
MEA*PD*G*70*LB~
TD1*PLT90*1~
TD5*B*2*UPSN*L*UNITED PARCEL SERVIC~
TD3*TL**2549608~
REF*BM*5992549608~
REF*PK*2355501~
REF*CN*1Z72V8200360372561~
N1*ST**92*FZSFDA~
N1*SU**92*ETN3~
HL*2*1*I~
LIN*1*BP*FUL 4304128***CH*US~
SN1**10*EA~
PRF*4581255489****001~
CLD*1*10*CTN25~
REF*LS*ETN35417997~
HL*3*1*I~
SN1**5*EA~
PRF*4581255489****002~
CLD*1*5*CTN25~
REF*LS*ETN35417997~
HL*4*1*I~
SN1**4*EA~
PRF*4581255489****003~

(DTNA)
CLD*1*4*CTN25~
REF*LS*ETN35417997~
HL*5*1*I~
SN1**8*EA~
PRF*4581255489****004~
CLD*1*8*CTN25~
REF*LS*ETN35417997~
HL*6*1*I~
LIN*5*BP*FUL K3691***CH*US~
SN1**4*EA~
PRF*4581255489****005~
CLD*1*4*CTN25~
REF*LS*ETN35417997~
CTT*6*31~
SE*45*0001~

(DTNA)
Heading:
Pos Id Segment Name Req Max Use Repeat Notes Usage
0100 ISA Interchange Control Header M 1 Must use
0200 GS Functional Group Header M 1 Must use
0300 ST Transaction Set Header M 1 Must use
0400 BSN Beginning Segment for Ship M 1 Must use
Notice
0500 DTM Date/Time Reference M 1 Must use
Detail:
LOOP ID - HL 200000
0200 HL Hierarchical Level M 1 Must use
0900 MEA Measurements M 1 Must use
1200 TD1 Carrier Details (Quantity O 5 Used
and Weight)
1300 TD5 Carrier Details (Routing O 1 Used
Sequence/Transit Time)
1400 TD3 Carrier Details (Equipment) O 1 Used
1700 REF Reference Identification M 3 Must use
3600 FOB F.O.B. Related Instructions O 1 Used
LOOP ID - N1 5
3900 N1 Name M 1 Must use
LOOP ID - HL 200000
6300 LIN Item Identification M 1 Must use
6400 SN1 Item Detail (Shipment) M 1 Must use
6600 PRF Purchase Order Reference M 1 Must use
6700 REF Reference Identification C 30 N2/6700 Dependent
LOOP ID - CLD 30 N2/6800L
6900 CLD Load Detail O 1 Used
7000 REF Reference Identification O 30 N2/7000 Used
7100 MAN Marks and Numbers O 30 Used
Summary:
0100 CTT Transaction Totals M 1 N3/0100 Must use
0200 SE Transaction Set Trailer M 1 Must use
0300 GE Functional Group Trailer M 1 Must use
0400 IEA Interchange Control Trailer M 1 Must use
Notes:
2/6700 The Packing List number (REF*PK) must be included EITHER at the shipment-level OR the detail-level,
BUT NOT BOTH. If the shipment is divided among different packing lists then use the detail-level
REF*PK. If there is a single packing list for the entire shipment then use the header-level REF*PK.
2/6800L PDC Bar Code Receiving - The CLD loop must be used to provide information to aid in the preparation of
move tags and/or bar coded labels.
2/7000 REF*LS and MAN are mutually exclusive. One or the other should be used but not both.

(DTNA)
3/0100 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.

(DTNA)
Pos: 0100 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

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

(DTNA)
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

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

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

The code "0" in this element indicates that TA1 interchange-level acknowledgements are
not requested or sent by DTNA. Please note that a TA1 interchange acknowledgement is
different than a 997 Functional Acknowledgement. DTNA requires that a 997 Functional
Acknowledgement be returned by trading partners for all EDI transactions that are sent
outbound from DTNA.

Code Name
0 No Acknowledgment Requested
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

Code Name
P Production Data

(DTNA)
Code Name
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.
For the DTNA implementation all valid separators and terminators are allowed, provided
they are unique among each other. However, DTNA's prefered delimiters are listed below:
Preferred Element Separators:
"*" - Asterisk (ASCII Hex "2A")
"~" - Tilde (ASCII Hex "7E")
"`" - Acute (ASCII Hex "60")
Preferred Sub-Element/Component Separators:
">" - Greater Than (ASCII Hex "3E")
"]" - Close Square Bracket (ASCII Hex "5D")
"}" - Close Curly Brace (ASCII Hex "7D")
Preferred Segment Terminators:
"^" - Caret (ASCII Hex "5E")
"~" - Tilde (ASCII Hex "7E")
"|" - Pipe (ASCII Hex "7C")

(DTNA)
Pos: 0200 Max: 1

GS Functional Group Header Heading - Mandatory

Purpose: To indicate the beginning of a functional group and to provide control information
Element Summary:
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.

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

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,

(DTNA)

then other formats are allowed

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

(DTNA)
Pos: 0300 Max: 1

ST Transaction Set Header Heading - Mandatory

Purpose: To indicate the start of a transaction set and to assign a control number
Element Summary:
ST01 143 Transaction Set Identifier Code M ID 3/3 Must use
Description: Code uniquely identifying a Transaction Set

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

(DTNA)
Pos: 0400 Max: 1

BSN Beginning Segment for Ship Heading - Mandatory
Notice Loop: N/A Elements: 4

Purpose: To transmit identifying numbers, dates, and other basic data relating to the transaction set
Element Summary:
BSN01 353 Transaction Set Purpose Code M ID 2/2 Must use
Description: Code identifying purpose of transaction set

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. For the DTNA implementation the BSN02 element MUST CONTAIN a
unique, supplier-assigned Shipment ID number (SID) THAT IS NOT REPEATED WITHIN A
CALENDAR YEAR. There must be only one ship-to address per SID/ASN. The DTNA
application will only process the first 16 characters of this element.
This is expected to be all upper case. The SID in this element should exactly match
(including leading zeroes) the SID provided on an 810(Invoice) and the packing slip.
Dashes and special characters are not allowed in SID.
BSN03 373 Date M DT 8/8 Must use
BSN04 337 Time M TM 4/8 Must use

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

(DTNA)
Pos: 0500 Max: 1

DTM Date/Time Reference Heading - Mandatory

Purpose: To specify pertinent dates and times
Element Summary:
DTM01 374 Date/Time Qualifier M ID 3/3 Must use
Description: Code specifying type of date or time, or both date and time

Code Name
011 Shipped
DTM02 373 Date M DT 8/8 Must use
DTM03 337 Time M TM 4/8 Must use

DTM04 623 Time Code O ID 2/2 Recommended
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
Syntax Rules:
1. R0203 - At least one of DTM02 or DTM03 is required.
2. C0403 - If DTM04 is present, then DTM03 is required.

(DTNA)
Pos: 0100 Repeat:

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

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
0900 MEA Measurements M 1 Must use
1200 TD1 Carrier Details (Quantity and Weight) O 5 Used
1300 TD5 Carrier Details (Routing Sequence/Transit O 1 Used
Time)
1400 TD3 Carrier Details (Equipment) O 1 Used
1700 REF Reference Identification M 3 Must use
3600 FOB F.O.B. Related Instructions O 1 Used
3800 Loop N1 M 5 Must use
Comments:
1. This HL Loop is for the Shipment level detail.

(DTNA)
Pos: 0200 Max: 1

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

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments.
This HL is for the Shipment Level.
Element Summary:
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”.

Code Name
S Shipment

(DTNA)
Pos: 0900 Max: 1

MEA Measurements Detail - Mandatory

Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights
Element Summary:
MEA01 737 Measurement Reference ID Code M ID 2/2 Must use
Description: Code identifying the broad category to which a measurement applies

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

Code Name
G Gross Weight
MEA03 739 Measurement Value M R 1/20 Must use
Description: The value of the measurement
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.

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

(DTNA)
Pos: 1200 Max: 5

TD1 Carrier Details (Quantity and Detail - Optional
Weight) Loop: HL Elements: 2
User Option (Usage): Used

Purpose: To specify the transportation details relative to commodity, weight, and quantity
Element Summary:
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. Use
Packaging Code of the shipping unit (e.g. ten boxes on one pallet is specified as one
pallet).
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. 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
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.

(DTNA)
Pos: 1300 Max: 1

TD5 Carrier Details (Routing Detail - Optional
Sequence/Transit Time) Loop: HL Elements: 5

Purpose: To specify the carrier and sequence of routing and provide transit time information
Element Summary:
TD501 133 Routing Sequence Code M ID 1/2 Must use
Description: Code describing the relationship of a carrier to a specific shipment movement

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)

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 O ID 1/2 Used
Description: Code specifying the method or type of transportation for the shipment

Code Name
A Air
H Customer Pickup
L Contract Carrier
M Motor (Common Carrier)
Q Conventional Ocean
R Rail
TD505 387 Routing O AN 1/35 Used
Description: Free-form description of the routing or requested routing for shipment, or the
originating carrier's identity
Syntax Rules:
1. P0203 - If either TD502 or TD503 is present, then the other is required.

(DTNA)
Pos: 1400 Max: 1

TD3 Carrier Details (Equipment) Detail - Optional

Purpose: To specify transportation details relating to the equipment used by the carrier
Element Summary:
TD301 40 Equipment Description Code M ID 2/2 Must use
Description: Code identifying type of equipment used for shipment

Code Name
TL Trailer (not otherwise specified)
TD303 207 Equipment Number M AN 1/10 Must use
Description: Sequencing or equipment unit's identifying number.
This element is required for Import Security Filings (ISF) with Customs and Border
Protection (CBP).

(DTNA)
Pos: 1700 Max: 3

REF Reference Identification Detail - Mandatory

Purpose: To specify identifying information
Element Summary:
REF01 128 Reference Identification Qualifier M ID 2/3 Must use
Description: Code qualifying the Reference Identification

Code Name
BM Bill of Lading Number
CN Carrier's Reference Number (PRO/Invoice)
PK Packing List Number
REF02 127 Reference Identification M AN 1/30 Must use
Description: Reference information as defined for a particular Transaction Set or as

specified by the Reference Identification Qualifier
Semantics:
1. Bill of Lading max size is 16 characters
2. Carrier’s PRO number max size is 30 characters
3. Packing list max size is 10 characters
Comments:
1. The Packing List (REF*PK) must be EITHER at the shipment OR the detail level BUT NOT BOTH.
2. On REF*CN air carriers may provide air waybill or tracking number; parcel carriers may provide tracking
number; LTL carriers may provide carrier's reference number.

(DTNA)
Pos: 3600 Max: 1

FOB F.O.B. Related Instructions Detail - Optional

Purpose: To specify transportation instructions relating to shipment
Element Summary:
FOB01 146 Shipment Method of Payment M ID 2/2 Must use
Description: Code identifying payment terms for transportation charges

Code Name
CC Collect
PA Advance Prepaid
PB Customer Pick-up/Will Call
PP Prepaid (by Seller)
TP Third Party Pay
Semantics:
1. FOB01 indicates which party will pay the carrier

(DTNA)
Pos: 3800 Repeat: 5

Loop Name Mandatory
Loop: N1 Elements: N/A

Purpose: To identify a party by type of organization, name, and code
Loop Summary:
3900 N1 Name M 1 Must use
Comments:
1. The N1 Loop is at the Shipment Level.

(DTNA)
Pos: 3900 Max: 1

N1 Name Detail - Mandatory
Loop: N1 Elements: 4

Purpose: To identify a party by type of organization, name, and code. For the DTNA implementation the N1 Loops
where N101 = "ST" and N101 = "SU" are required AND the N104 data must match the values sent in the X12 850 or
faxed PO.
Element Summary:
N101 98 Entity Identifier Code M ID 2/3 Must use
Description: Code identifying an organizational entity, a physical location, property or an

individual

Code Name
SE Selling Party
SO Sold To
ST Ship To [Required by DTNA]
SU Supplier/Manufacturer [Required by DTNA]
N102 93 Name O 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)

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. For the DTNA implementation the
N104 element MUST contain the appropriate DTNA-assigned code. For purchase orders
that were communicated via fax the "Customer Code" on the faxed PO is the appropriate
code to populate in the N104 element where N101 = "ST" (i.e. the faxed "customer code" is
the same as the EDI Ship-To code).
Comments:
1. All Purchase Orders listed on this Advance Shipment Notice must have been delivered to the same Ship-To
location.
2. When N101 = "SU" then the data in the corresponding N104 element must exactly match the value
communicated on the Purchase Order in the N104 element where N101 = "SU".

(DTNA)
Pos: 6100 Repeat:

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

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments
Loop Summary:
6300 LIN Item Identification M 1 Must use
6400 SN1 Item Detail (Shipment) M 1 Must use
6600 PRF Purchase Order Reference M 1 Must use
6700 REF Reference Identification C 30 Dependent
6800 Loop CLD O 30 Used
Comments:
1. This HL Loop is for the Item level detail.

(DTNA)
Pos: 6200 Max: 1

HL Hierarchical Level Detail - Mandatory

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:
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. For the DTNA implementation only one
shipment per 856 transaction is allowed; therefore, 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. For the
DTNA implementation the value of the HL03 element at the item level will always be "I".

Code Name
I Item

(DTNA)
Pos: 6300 Max: 1

LIN Item Identification Detail - Mandatory

Purpose: To specify basic item identification data
Element Summary:
LIN01 350 Assigned Identification M AN 1/20 Must use
Description: For the DTNA implementation the value of the LIN01 element 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)

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. For the DTNA implementation the
LIN03 element must contain the same Buyer's Part Number as was provided in the
corresponding X12 850 or faxed Purchase Order.
LIN04 235 Product/Service ID Qualifier O ID 2/2 Used


Code Name
VN Vendor's (Seller's) Item Number
VP Vendor's (Seller's) Part Number
LIN05 234 Product/Service ID O AN 1/48 Used
Description: Identifying number for a product or service. For the DTNA implementation the
LIN05 element must contain the Vendor's Part Number of the material.
LIN06 235 Product/Service ID Qualifier M ID 2/2 Must use


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 must contain the appropriate standard, two-letter ISO code for the country of
origin of the material (ISO 3166-1 alpha-2).

(DTNA)
Pos: 6400 Max: 1

SN1 Item Detail (Shipment) Detail - Mandatory

Purpose: To specify line-item detail relative to shipment
Element Summary:
SN102 382 Number of Units Shipped M N0 1/10 Must use
Description: Numeric value of units shipped in manufacturer's shipping units for a line
item or transaction set. For the DTNA implementation the SN102 element must contain an
integer (whole number GREATER THAN ZERO, no decimal).
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. For the DTNA implementation the value of the
SN103 element must be the same Unit of Measure code that was provided on the
corresponding X12 850 or faxed Purchase Order.
Comments:
1. SN103 defines the unit of measurement for SN102.
2. SN1 is at the Item Level.

(DTNA)
Pos: 6600 Max: 1

PRF Purchase Order Reference Detail - Mandatory

Purpose: To provide reference to a specific purchase order
Element Summary:
PRF01 324 Purchase Order Number M AN 10/10 Must use
Description: Identifying number for Purchase Order assigned by the orderer/purchaser.

For the DTNA implementation the PRF01 element must contain the PO number provided in
the corresponding X12 850 (in the BEG03 element) or on the faxed Purchase Order. For
aftermarket, the PO number is a 10 digit number starting with "4".
PRF05 350 Assigned Identification M AN 1/7 Must use
Description: Alphanumeric characters assigned for differentiation within a transaction set.

For the DTNA Aftermarket implementation the PRF05 element must contain the PO LINE
NUMBER that matches the line number on the faxed order or the PO101 element of the
X12 850 PO.
Comments:
1. PRF is at the Item Level

(DTNA)
Pos: 6700 Max: 30

REF Reference Identification Detail - Conditional
User Option (Usage): Dependent

Purpose: To specify identifying information
Element Summary:

Code Name
PK Packing List Number
SE Serial Number

specified by the Reference Identification Qualifier. For the DTNA implementation REF*PK
should ONLY be used at the Item Level if the shipment is divided among different packing
lists. The value for REF*PK is allowed to be 10 characters only.
Syntax Rules:
1. P0102 - If either REF01 or REF02 is present, then the other is required.
Semantics:
1. For the DTNA implementation the REF*PK should only be used at the Item Level if the shipment is divided
among different packing lists

(DTNA)
Pos: 6800 Repeat: 30

Loop Load Detail Optional
Loop: CLD Elements: N/A

Purpose: To specify the number of material loads shipped
Loop Summary:
6900 CLD Load Detail O 1 Used
7000 REF Reference Identification O 30 Used
7100 MAN Marks and Numbers O 30 Used

(DTNA)
Pos: 6900 Max: 1

CLD Load Detail Detail - Optional
Loop: CLD Elements: 3

Purpose: To specify the number of material loads shipped. The CLD and REF or MAN segments are imperative for
bar code receiving shipments into DTNA Aftermarket PDCs.
Element Summary:
CLD01 622 Number of Loads M N0 1/5 Must use
Description: Number of customer-defined loads shipped by the supplier
CLD02 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
CLD03 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. Below are
some example values:
"BIN51" = Wire Mesh Bin
"BIN52" = Steel Bin
"BOX25" = Cardboard Box
"CNT71" = Container
"CRT71" = Crate
"CTN25" = Cardboard Carton
"PLT71" = Pallet
"RCK58" = Rack
"SKD71" = Skid
Semantics:
1. The sum of CLD01 times CLD02 across all applicable CLD Loops MUST EQUAL the value in the SN102
element.
Comments:
1. The CLD data segment may be used to provide information to aid in the preparation of move tags and/or bar
coded labels.

(DTNA)
Pos: 7000 Max: 30

REF Reference Identification Detail - Optional

Purpose: To specify identifying information. The CLD and REF or MAN segments are imperative for bar code
receiving shipments into DTNA Aftermarket PDCs.
Element Summary:

Code Name
LS Bar-Coded Serial Number

specified by the Reference Identification Qualifier. For the DTNA implementation prefix the
Package Identification Number (PID) with the DTNA-assigned supplier code (from N104
where N101 = "SU") in order to maintain uniqueness across all DTNA suppliers. Only the
first 20 characters of this element will be processed in the DTNA applications.
A pallet ID (PID) used needs to be unique in a calender year.
Semantics:
1. The REF segment may be used to provide information to aid in the preparation of move tags and/or bar coded
labels.
2. REF*LS and MAN are mutually exclusive. One or the other should be used but NOT BOTH.
3. There must be the same number of REF*LS OR MAN segments inside the CLD Loop as indicated in the
CLD01 element. This is because each REF*LS or MAN segment specifies a single bar-coded container ID
and the CLD01 element indicates the number of containers shipped.

(DTNA)
Pos: 7100 Max: 30

MAN Marks and Numbers Detail - Optional

Purpose: To indicate identifying marks and numbers for shipping containers. The CLD and REF or MAN segments
are imperative for bar code
receiving shipments into DTNA Aftermarket PDCs.
Element Summary:
MAN01 88 Marks and Numbers Qualifier M ID 1/2 Must use
Description: Code specifying the application or source of Marks and Numbers (87)

Code Name
CA Shipper-Assigned Case Number [Bar-Coded Package Identification (PID)]
MAN02 87 Marks and Numbers M AN 1/20 Must use
Description: Marks and numbers used to identify a shipment or parts of a shipment. For
the DTNA implementation prefix the Package Identification Number (PID) with the
DTNA-assigned supplier code (from N104 where N101 = "SU") in order to maintain
uniqueness across all DTNA suppliers. Only the first 20 characters of this element will be
processed in the DTNA applications. A pallet ID (PID) used needs to be unique in a
calender year.
Semantics:
1. REF*LS and MAN are mutually exclusive. One or the other should be used but not both.
2. The MAN data segment may be used to provide information to aid in the preparation of move tags and/or bar
coded labels.
3. There must be the same number of REF*LS OR MAN segments inside the CLD Loop as indicated in the
CLD01 element. This is because each REF*LS or MAN segment specifies a single bar-coded container ID
and the CLD01 element indicates the number of containers shipped.

(DTNA)
Pos: 0100 Max: 1

CTT Transaction Totals Summary - Mandatory

Purpose: To transmit a hash total for a specific element in the transaction set
Element Summary:
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 element values).

(DTNA)
Pos: 0200 Max: 1

SE Transaction Set Trailer Summary - Mandatory

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

(DTNA)
Pos: 0300 Max: 1

GE Functional Group Trailer Summary - Mandatory

Purpose: To indicate the end of a functional group and to provide control information
Element Summary:
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.

(DTNA)
Pos: 0400 Max: 1

IEA Interchange Control Trailer Summary - Mandatory

Purpose: To define the end of an interchange of zero or more functional groups and interchange-related control
segments
Element Summary:
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.

(DTNA)

856iv4010 DTNA AFTMKT V4 7

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

856iv4010 DTNA AFTMKT V4 7

Загружено:

Авторское право:

Доступные форматы

856 Ship Notice/Manifest -

Version: 4.7 Final

Company: Daimler Trucks North

IB856-DTNA-AFTMKT-V4-7.ecs i Daimler Trucks North America, LLC

856 Ship Notice/Manifest

Adherence to the following numbered items must be demonstrated:

IB856-DTNA-AFTMKT-V4-7.ecs 1 Daimler Trucks North America, LLC

EXAMPLE X12 DATA:

ASNs without CLD loop

LIN*001*BP*F6HZ 13201 AAA*VN*9FL 938 167-16*CH*US~

IB856-DTNA-AFTMKT-V4-7.ecs 2 Daimler Trucks North America, LLC

ASN with variants of CLD loop

IB856-DTNA-AFTMKT-V4-7.ecs 3 Daimler Trucks North America, LLC

IB856-DTNA-AFTMKT-V4-7.ecs 4 Daimler Trucks North America, LLC

Third Party ASN

TD5*B*2*UPSN*L*UNITED PARCEL SERVIC~

IB856-DTNA-AFTMKT-V4-7.ecs 5 Daimler Trucks North America, LLC

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

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

IB856-DTNA-AFTMKT-V4-7.ecs 8 Daimler Trucks North America, LLC

Pos: 0100 Max: 1

User Option (Usage): Must use

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

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

ISA02 I02 Authorization Information M AN 10/10 Must use

Description: Information used for additional identification or authorization of the

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

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

ISA04 I04 Security Information M AN 10/10 Must use

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

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

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

IB856-DTNA-AFTMKT-V4-7.ecs 9 Daimler Trucks North America, LLC

Ref Id Element Name Req Type Min/Max Usage

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

Description: Date of the interchange

ISA10 I09 Interchange Time M TM 4/4 Must use

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

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

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

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

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

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

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

ISA15 I14 Usage Indicator M ID 1/1 Must use

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

IB856-DTNA-AFTMKT-V4-7.ecs 10 Daimler Trucks North America, LLC

ISA16 I15 Component Element Separator M 1/1 Must use

Preferred Element Separators:

"*" - Asterisk (ASCII Hex "2A")

"~" - Tilde (ASCII Hex "7E")

"`" - Acute (ASCII Hex "60")

Preferred Sub-Element/Component Separators:

">" - Greater Than (ASCII Hex "3E")

"]" - Close Square Bracket (ASCII Hex "5D")

"}" - Close Curly Brace (ASCII Hex "7D")

Preferred Segment Terminators:

"^" - Caret (ASCII Hex "5E")

"~" - Tilde (ASCII Hex "7E")

"|" - Pipe (ASCII Hex "7C")

IB856-DTNA-AFTMKT-V4-7.ecs 11 Daimler Trucks North America, LLC

Pos: 0200 Max: 1

User Option (Usage): Must use

LIN001BPF6HZ 13201 AAAVN9FL 938 167-16CH*US~

TD5B2*UPSNLUNITED PARCEL SERVIC~