DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 1 August 31, 2020

856 Ship Notice/Manifest

Functional Group=SH

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Ship Notice/Manifest Transaction Set

(856) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to list the contents of a

shipment of goods as well as additional information relating to the shipment, such as order information, product description, physical

characteristics, type of packaging, marking, carrier information, and configuration of goods within the transportation equipment. The transaction

set enables the sender to describe the contents and configuration of a shipment in various levels of detail and provides an ordered flexibility to

convey information.The sender of this transaction is the organization responsible for detailing and communicating the contents of a shipment, or

shipments, to one or more receivers of the transaction set. The receiver of this transaction set can be any organization having an interest in the

contents of a shipment or information about the contents of a shipment.

DLMS Note:

1. DoD distinguishes among Foreign Military Sales (FMS) Notices of Availability (NOA) requiring export release authorization, those not

requiring export release authorization and those for which release will be delayed.

2. Identify the overall shipment attributes and detailed line item content of each shipment.

3. Users operating under the Defense Logistics Management Standards (DLMS) must reference DoD/ASC X12 Conversion Guides for Unit

of Materiel Measure, Type of Pack and Transportation Method/Type Code, which can be found on the Enterprise Business Standards Office

(EBSO) Website at www.dla.mil/does/DLMS.

4. This DLMS Implementation Convention contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system. 

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with EBSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or

understood by the recipient's automated processing system. Components must coordinate implementation with EBSO prior to use.

c. Legacy MILSTRIP data which must be retained in the DLMS for a transition period to support transaction conversion in a mixed legacy

MILSTRIP/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components may coordinate

with EBSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded files size above existing legacy MILSTRIP capability which may not be supported by the

recipient's automated processing system. Components must coordinate implementation with EBSO prior to use.

e. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data

(including expanded field sizes) should be adopted during, or subsequent, to modernization when applicable to the Component’s business

process. Prior coordination is not required. Components should ensure that inclusion of this data in a DLMS transaction does not cause

inappropriate rejection of the transaction.

5. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDCs) and Approved DLMS Changes (ADCs) listed. PDCs and

ADCs are available from the EBSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 309, NOA and NOA Reply Transaction Data Content/Mapping including Addition of Type Pack Code for 463L Pallets

- ADC 1043, DLMS Revisions for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1075, Implementation of Geopolitical Entities, Names, and Codes (GENC) Standard by DoD Components for the Identification of

Countries and their Subdivisions

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on June 04, 2014.

- ADC 1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding DLMS 856N NOA and 870N NOA Reply

- ADC 1136, Revise Unique Item Tracking (UIT) Procedures to support DODM 4140.01 UIT Policy and Clarify Requirements (Supply)

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on January 12, 2017

- ADC 1287, DLMS Implementation Convention (IC) Revisions for Data Element Mapping (Form Stock Number and Manufacturer's Part

Number), Removal of Plant Equipment Number, and Administrative Updates 

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

January 22, 2019

- ADC 1353, Transportation Method and Transportation Mode Codes on all DLMS ICs

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions 

- ADC 1370, Administrative Update to Change Data Element N106 Usage from Must Use to Used 

1. DoD distinguishes among Foreign Military Sales (FMS) Notices of Availability (NOA) requiring export release authorization, those not

requiring export release authorization and those for which release will be delayed.

2. Identify the overall shipment attributes and detailed line item content of each shipment.

3. Users operating under the Defense Logistics Management Standards (DLMS) must reference DoD/ASC X12 Conversion Guides for Unit

of Materiel Measure, Type of Pack and Transportation Method/Type Code, which can be found on the Enterprise Business Standards Office

(EBSO) Website at www.dla.mil/does/DLMS.

4. This DLMS Implementation Convention contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system. 

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with EBSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or

understood by the recipient's automated processing system. Components must coordinate implementation with EBSO prior to use.

c. Legacy MILSTRIP data which must be retained in the DLMS for a transition period to support transaction conversion in a mixed legacy

MILSTRIP/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components may coordinate

with EBSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded files size above existing legacy MILSTRIP capability which may not be supported by the

recipient's automated processing system. Components must coordinate implementation with EBSO prior to use.

e. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data

(including expanded field sizes) should be adopted during, or subsequent, to modernization when applicable to the Component’s business

process. Prior coordination is not required. Components should ensure that inclusion of this data in a DLMS transaction does not cause

inappropriate rejection of the transaction.

5. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDCs) and Approved DLMS Changes (ADCs) listed. PDCs and

ADCs are available from the EBSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/

- ADC 309, NOA and NOA Reply Transaction Data Content/Mapping including Addition of Type Pack Code for 463L Pallets

- ADC 1043, DLMS Revisions for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification

- ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

- ADC 1075, Implementation of Geopolitical Entities, Names, and Codes (GENC) Standard by DoD Components for the Identification of

Countries and their Subdivisions

- Organizational Name and Other Non-Substantive (Administrative) Updates Completed on June 04, 2014.

- ADC 1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding DLMS 856N NOA and 870N NOA Reply

- ADC 1136, Revise Unique Item Tracking (UIT) Procedures to support DODM 4140.01 UIT Policy and Clarify Requirements (Supply)

- Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on January 12, 2017

- ADC 1287, DLMS Implementation Convention (IC) Revisions for Data Element Mapping (Form Stock Number and Manufacturer's Part

Number), Removal of Plant Equipment Number, and Administrative Updates 

- Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

January 22, 2019

- ADC 1353, Transportation Method and Transportation Mode Codes on all DLMS ICs

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions 

- ADC 1370, Administrative Update to Change Data Element N106 Usage from Must Use to Used 

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

0100 ST Transaction Set Header M 1 Must use

0200 BSN Beginning Segment for Ship Notice M 1 Must use

* 0400 DTM Date/Time Reference O 10 Not Used
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 2 August 31, 2020

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

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

0100 HL Hierarchical Level M 1 C2/0100 Must use

0200 LIN Item Identification O 1 Used

0300 SN1 Item Detail (Shipment) O 1 Used

* 0400 SLN Subline Item Detail O 1000 Not Used

* 0500 PRF Purchase Order Reference O 1 Not Used

* 0600 PO4 Item Physical Details O 1 Not Used

* 0700 PID Product/Item Description O 200 Not Used

0800 MEA Measurements O 40 Used

* 0900 PWK Paperwork O 25 Not Used

* 1000 PKG Marking, Packaging, Loading O 25 Not Used

1100 TD1 Carrier Details (Quantity and

Weight)

O 20 Used

1200 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 12 Used

* LOOP ID - TD3 * LOOP ID - TD3 12

1300 TD3 Carrier Details (Equipment) O 1 Used

1350 AT9 Trailer or Container Dimension and

Weight

O 1 Used

* 1400 TD4 Carrier Details (Special Handling,

or Hazardous Materials, or Both)

O 5 Not Used

* 1450 TSD Trailer Shipment Details O 1 Not Used

1500 REF Reference Identification O >1 Used

* 1510 PER Administrative Communications

Contact

O 3 Not Used

LOOP ID - LH1 LOOP ID - LH1 100

1520 LH1 Hazardous Identification

Information

O 1 Used

1530 LH2 Hazardous Classification

Information

O 4 Used

1540 LH3 Hazardous Material Shipping

Name

O 12 Used

* 1550 LFH Freeform Hazardous Material

Information

O 20 Not Used

* 1560 LEP EPA Required Data O >1 Not Used

* 1570 LH4 Canadian Dangerous

Requirements

O 1 Not Used

* 1580 LHT Transborder Hazardous

Requirements

O 3 Not Used

1590 LHR Hazardous Material Identifying

Reference Numbers

O 10 Used

* 1600 PER Administrative Communications

Contact

O 5 Not Used

* 1610 LHE Empty Equipment Hazardous

Material Information

O 1 Not Used

* LOOP ID - CLD * LOOP ID - CLD 200

* 1700 CLD Load Detail O 1 Not Used

* 1800 REF Reference Identification O 200 Not Used

* 1850 DTP Date or Time or Period O 1 Not Used

* 1900 MAN Marks and Numbers O >1 Not Used

2000 DTM Date/Time Reference O 10 Used

* 2100 FOB F.O.B. Related Instructions O 1 Not Used

* 2150 PAL Pallet Information O 1 Not Used

LOOP ID - N1 LOOP ID - N1 200

2200 N1 Name O 1 Used
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004030F856N0NA05 3 August 31, 2020

* 2300 N2 Additional Name Information O 2 Not Used

* 2400 N3 Address Information O 2 Not Used

* 2500 N4 Geographic Location O 1 Not Used

* 2600 REF Reference Identification O 12 Not Used

2700 PER Administrative Communications

Contact

O 3 Used

* 2800 FOB F.O.B. Related Instructions O 1 Not Used

* 2900 SDQ Destination Quantity O 50 Not Used

* 3000 ETD Excess Transportation Detail O 1 Not Used

* 3100 CUR Currency O 1 Not Used

LOOP ID - SAC LOOP ID - SAC >1

3200 SAC Service, Promotion, Allowance, or

Charge Information

O 1 Used

* 3250 CUR Currency O 1 Not Used

* 3300 GF Furnished Goods and Services O 1 Not Used

3350 YNQ Yes/No Question O 10 Used

LOOP ID - LM LOOP ID - LM 10

3400 LM Code Source Information O 1 Used

3500 LQ Industry Code M 100 Must use

* LOOP ID - V1 * LOOP ID - V1 >1

* 3600 V1 Vessel Identification O 1 Not Used

* 3700 R4 Port or Terminal O >1 Not Used

* 3800 DTM Date/Time Reference O >1 Not Used

Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage

* 0100 CTT Transaction Totals O 1 N3/0100 Not Used

0200 SE Transaction Set Trailer M 1 Must use

Notes: 

3/0100 Number of line items (CTT01) is the accumulation of the number of HL segments. If used, hash total (CTT02) is the sum of the

value of units shipped (SN102) for each SN1 segment.

Comments: 

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

2/0100 The HL segment is the only mandatory segment within the HL loop, and by itself, the HL segment has no meaning.
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 4 August 31, 2020

ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 3

User Option (Usage): Must use

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

Semantics: 

1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction

set definition (e.g., 810 selects the Invoice Transaction Set).

2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate

implementation convention to match the transaction set definition.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use 1

Code Name

856 Ship Notice/Manifest

ST02 329 Transaction Set Control Number

Description: Identifying control number

that must be unique within the transaction

set functional group assigned by the

originator for a transaction set

DLMS Note: A unique number assigned by

the originator of the transaction set, or the

originator's application program.

M AN 4/9 Must use 1

ST03 1705 Implementation Convention Reference

Description: Reference assigned to

identify Implementation Convention

DLMS Note: Use to indicate this

transmission uses the DLMS IC 856N.

Enter the DLMS IC

(e.g.,004030F856N0NA00).

O AN 1/35 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 5 August 31, 2020

BSN Beginning Segment for Ship Notice Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 6

User Option (Usage): Must use

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

Syntax Rules: 

1. C0706 - If BSN07 is present, then BSN06 is required.

Semantics: 

1. BSN03 is the date the shipment transaction set is created.

2. BSN04 is the time the shipment transaction set is created.

3. BSN06 is limited to shipment related codes.

Comments: 

1. BSN06 and BSN07 differentiate the functionality of use for the transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BSN01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

M ID 2/2 Must use 1

Code Name

00 Original

77 Simulation Exercise

DLMS Note:

Use to identify a simulated mobilization exercise transaction set. Activities initiating simulated

mobilization exercises must ensure complete coordination with all activities involved. All transaction set

recipients must use extreme caution to ensure that individual transactions do not process as action

documents which affect accountable records.

BSN02 396 Shipment Identification

Description: A unique control number

assigned by the original shipper to identify

a specific shipment

DLMS Note: Use Code "ZZ" for this data

element to satisfy mandatory X12 syntax

requirements.

M AN 2/30 Must use 1

BSN03 373 Date

Description: Date expressed as

CCYYMMDD where CC represents the first

two digits of the calendar year

DLMS Note: This date corresponds to the

Universal Time Coordinate (UTC).

M DT 8/8 Must use 1

BSN04 337 Time

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)

DLMS Note: 1. Express the originating

activity's time in UTC.

M TM 4/8 Must use 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F856N0NA05 6 August 31, 2020

2. Express time in a four-position (HHMM)

format.

BSN06 640 Transaction Type Code

Description: Code specifying the type of

transaction

X ID 2/2 Must use 1

Code Name

AD Notice of Availability

BSN07 641 Status Reason Code

Description: Code indicating the status

reason

DLMS Note: Use to identify the type of

NOA.

O ID 3/3 Must use 1

Code Name

D50 Delayed

DLMS Note:

Use to indicate that all referenced shipments are delayed.

ENR Export Release Not Required

DLMS Note:

Use to indicate that export release is not required for all referenced shipments.

ERR Export Release Required

DLMS Note:

Use to indicate that export release is required for all referenced shipments.
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 7 August 31, 2020

HL Hierarchical Level Pos: 0100 Max: 1

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

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.

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.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

DLMS Note:

1. The transaction set hierarchical data structure is address information, followed by overall shipment attributes, followed by shipment line

item detail.

2. Use the first 2/HL/0100 loop iteration to provide transaction set address information.

3. Use the second 2/HL/0100 shipment loop iteration to identify shipment information associated with the transportation control number

(TCN) assigned to control the shipment.

4. Use a single or multiple 2/HL/0100 line item loop iterations to identify the line item detail associated with each shipment.

1. The transaction set hierarchical data structure is address information, followed by overall shipment attributes, followed by shipment line

item detail.

2. Use the first 2/HL/0100 loop iteration to provide transaction set address information.

3. Use the second 2/HL/0100 shipment loop iteration to identify shipment information associated with the transportation control number

(TCN) assigned to control the shipment.

4. Use a single or multiple 2/HL/0100 line item loop iterations to identify the line item detail associated with each shipment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

HL01 628 Hierarchical ID Number

Description: A unique number assigned by

the sender to identify a particular data

segment in a hierarchical structure

DLMS Note: In the first 2/HL/0100 loop

iteration, cite numeric 1. In each

subsequent loop iteration, increase

incrementally by 1.

M AN 1/12 Must use 1

HL02 734 Hierarchical Parent ID Number

Description: Identification number of the

next higher hierarchical data segment that

the data segment being described is

subordinate to

DLMS Note: 1. Use for each 2/HL/0100 line

item loop iteration to identify the shipment

loop associated with each line item.

2. Data element content is the sequential

number assigned to the 2/HL/0100

shipment loop iteration and serves as the

cross-reference between the shipment and

all line items contained in the shipment.

O AN 1/12 Used 1

HL03 735 Hierarchical Level Code

Description: Code defining the

characteristic of a level in a hierarchical

structure

M ID 1/2 Must use 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 8 August 31, 2020

Code Name

I Item

DLMS Note:

Use to identify the individual line item loops.

S Shipment

DLMS Note:

Use to identify the individual shipment loops.

V Address Information

DLMS Note:

Use to identify the transaction set address loop.
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 9 August 31, 2020

LIN Item Identification Pos: 0200 Max: 1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To specify basic item identification data

Syntax Rules: 

1. P0405 - If either LIN04 or LIN05 is present, then the other is required.

2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

3. P0809 - If either LIN08 or LIN09 is present, then the other is required.

4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.

6. P1415 - If either LIN14 or LIN15 is present, then the other is required.

7. P1617 - If either LIN16 or LIN17 is present, then the other is required.

8. P1819 - If either LIN18 or LIN19 is present, then the other is required.

9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.

11. P2425 - If either LIN24 or LIN25 is present, then the other is required.

12. P2627 - If either LIN26 or LIN27 is present, then the other is required.

13. P2829 - If either LIN28 or LIN29 is present, then the other is required.

14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

Semantics: 

1. LIN01 is the line item identification

Comments: 

1. See the Data Dictionary for a complete list of IDs.

2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No.,

ISBN No., Model No., or SKU.

DLMS Note:

Must use only in 2/HL/0100 line item loops to identify the materiel included in the shipment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LIN02 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

DLMS Note: 1. Use only one of codes A2,

A4, FB, FS, FT, MG, or YP to identify the

materiel shipped. Must use National Stock

Number (NSN) when known.

2. For DLMS use, only the following codes

are authorized.

M ID 2/2 Must use 1

Code Name

A2 Department of Defense Identification Code (DoDIC)

DLMS Note:

Use to identify ammunition items.

A4 Subsistence Identification Number

DLMS Note:

Use to identify subsistence items.

F4 Series Identifier

DLMS Note:
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

Code Name

004030F856N0NA05 10 August 31, 2020

Use to identify the manufacturer's series number of the end item.

FB Form Number

DLMS Note:

Use to identify the form stock number.

FS National Stock Number

DLMS Note:

Must use NSN when known.

FT Federal Supply Classification

DLMS Note:

Use to identify nonstandard materiel when a part number is not available and materiel requisitioned was

identified by description (e.g., non-NSN lumber products).

MG Manufacturer's Part Number

DLMS Note:

Use to identify nonstandard materiel.

MN Model Number

DLMS Note:

Use to identify the manufacturer's model number of the end item.

SN Serial Number

DLMS Note:

Use to identify the manufacturer's serial number of the end item.

YP Publication Number

DLMS Note:

Use to identify the publication stock number.

LIN03 234 Product/Service ID

Description: Identifying number for a

product or service

M AN 1/48 Must use 1

LIN04 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

X ID 2/2 Used 1

Code Name

CN Commodity Name

DLMS Note:

Use with LIN02 code FT to identify the materiel name or description.

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

Use with LIN02 code MG to uniquely identify a manufacturer's part number.

LIN05 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 11 August 31, 2020

SN1 Item Detail (Shipment) Pos: 0300 Max: 1

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To specify line-item detail relative to shipment

Syntax Rules: 

1. P0506 - If either SN105 or SN106 is present, then the other is required.

Semantics: 

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

Comments: 

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

DLMS Note:

Must use only in 2/HL/0100 line item loops to identify the number of units associated with each transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

SN102 382 Number of Units Shipped

Description: Numeric value of units

shipped in manufacturer's shipping units for

a line item or transaction set

DLMS Note: 1. Use to identify the quantity

associated with the individual transaction.

2. Express as a whole number with no

decimals. 

M R 1/10 Must use 1

SN103 355 Unit or Basis for Measurement Code

Description: Code specifying the units in

which a value is being expressed, or

manner in which a measurement has been

taken

DLMS Note: 1. Use to identify the unit of

issue for the materiel.

2. DLMS users see the Unit of Issue and

Purchase Unit Conversion Table.

M ID 2/2 Must use 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 12 August 31, 2020

MEA Measurements Pos: 0800 Max: 40

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights(See Figures Appendix for

example of use of C001)

Syntax Rules: 

1. R03050608 - At least one of MEA03, MEA05, MEA06 or MEA08 is required.

2. C0504 - If MEA05 is present, then MEA04 is required.

3. C0604 - If MEA06 is present, then MEA04 is required.

4. L07030506 - If MEA07 is present, then at least one of MEA03, MEA05 or MEA06 is required.

5. E0803 - Only one of MEA08 or MEA03 may be present.

Semantics: 

1. MEA04 defines the unit of measure for MEA03, MEA05, and MEA06.

Comments: 

1. When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot

be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value.

DLMS Note:

1. Use only in 2/HL/0100 shipment loops. Use two repetitions to identify shipment, weight and cube.

2. If the shipment is over-dimensional, use three additional repetitions to identify the physical dimensions (height, length and width) of the

shipment. 

3. If the shipment is explosive, use an additional repetition to identify the Net Explosive Weight in pounds.

4. Use of the MEA segment to identify dimensions for over-dimensional shipments and Net Explosive Weight are an authorized DLMS

enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098. 

1. Use only in 2/HL/0100 shipment loops. Use two repetitions to identify shipment, weight and cube.

2. If the shipment is over-dimensional, use three additional repetitions to identify the physical dimensions (height, length and width) of the

shipment. 

3. If the shipment is explosive, use an additional repetition to identify the Net Explosive Weight in pounds.

4. Use of the MEA segment to identify dimensions for over-dimensional shipments and Net Explosive Weight are an authorized DLMS

enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

MEA01 737 Measurement Reference ID Code

Description: Code identifying the broad

category to which a measurement applies

O ID 2/2 Used 1

Code Name

NX Net Explosive Weight

DLMS Note:

For explosive shipments, use to identify the Net Explosive Weight in the MEA03 and MEA04-01 Code

LB. 

PD Physical Dimensions

DLMS Note:

For over-dimensional shipments, use to identify the physical dimensions (height, length, and width) of

the shipment in the MEA02, MEA03, and MEA04-01 Code IN.

MEA02 738 Measurement Qualifier

Description: Code identifying a specific

product or process characteristic to which a

measurement applies

O ID 1/3 Used 1

Code Name

A Consolidated Weight

DLMS Note:

Use with code LB in MEA04-01, to identify the shipment weight in pounds.

HT Height
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

Code Name

004030F856N0NA05 13 August 31, 2020

DLMS Note:

Use to identify the height in inches of an over-dimensional shipment.

LN Length

DLMS Note:

Use to identify the length in inches of an over-dimensional shipment.

WD Width

DLMS Note:

Use to identify the width in inches of an over-dimensional shipment.

UCB Cube

DLMS Note:

Use with code CF in MEA04-01 to identify the shipment cubic size (volume) expressed as cubic feet.

MEA03 739 Measurement Value

Description: The value of the

measurement

DLMS Note: Use to identify the actual

number of pounds, inches, or cubic feet,

associated with the shipment based on the

coding in MEA02 and MEA04-01.

X R 1/20 Must use 1

MEA04 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for

examples of use)

Comments: 

1. If C001-02 is not used, its value is to be

interpreted as 1.

2. If C001-03 is not used, its value is to be

interpreted as 1.

3. If C001-05 is not used, its value is to be

interpreted as 1.

4. If C001-06 is not used, its value is to be

interpreted as 1.

5. If C001-08 is not used, its value is to be

interpreted as 1.

6. If C001-09 is not used, its value is to be

interpreted as 1.

7. If C001-11 is not used, its value is to be

interpreted as 1.

8. If C001-12 is not used, its value is to be

interpreted as 1.

9. If C001-14 is not used, its value is to be

interpreted as 1.

10. If C001-15 is not used, its value is to be

interpreted as 1.

X Comp Must use 1

MEA04-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in

which a value is being expressed, or

manner in which a measurement has been

taken

DLMS Note: For DLMS use, only the

following codes are authorized.

M ID 2/2 Must use 1

Code Name

CF Cubic Feet

DLMS Note:

Use with code UCB in MEA02 to indicate that the shipment cube is expressed as cubic feet.

IN Inch
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

Code Name

004030F856N0NA05 14 August 31, 2020

DLMS Note:

Use with MEA01 Code PD and MEA02 Codes HT, LN, and WD.

LB Pound

DLMS Note:

1. Use with code A in MEA02 to indicate that the shipment weight is expressed as pounds.

2. Use with code NX in MEA01 to indicate that the shipment net explosive weight is expressed in

pounds.
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 15 August 31, 2020

TD1 Carrier Details (Quantity and Weight) Pos: 1100 Max: 20

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

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

Syntax Rules: 

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

2. C0304 - If TD103 is present, then TD104 is required.

3. C0607 - If TD106 is present, then TD107 is required.

4. P0708 - If either TD107 or TD108 is present, then the other is required.

5. P0910 - If either TD109 or TD110 is present, then the other is required.

DLMS Note:

Use only in 2/HL/0100 shipment loops.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

TD102 80 Lading Quantity

Description: Number of units (pieces) of

the lading commodity

DLMS Note: Use to identify the number of

physical units (pieces) in the shipment.

X N0 1/7 Must use 1

TD105 79 Lading Description

Description: Description of an item as

required for rating and billing purposes

DLMS Note: Use to identify the freight

nomenclature. Authorized DLMS

enhancement; see DLMS Introductory Note

4e. Refer to ADC 1098.

O AN 1/50 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 16 August 31, 2020

TD5 Carrier Details (Routing

Sequence/Transit Time)

Pos: 1200 Max: 12

Detail - Optional

Loop: HL Elements: 1

User Option (Usage): Used

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

Syntax Rules: 

1. R0204050612 - At least one of TD502, TD504, TD505, TD506 or TD512 is required.

2. C0203 - If TD502 is present, then TD503 is required.

3. C0708 - If TD507 is present, then TD508 is required.

4. C1011 - If TD510 is present, then TD511 is required.

5. C1312 - If TD513 is present, then TD512 is required.

6. C1413 - If TD514 is present, then TD513 is required.

7. C1512 - If TD515 is present, then TD512 is required.

Semantics: 

1. TD515 is the country where the service is to be performed.

Comments: 

1. When specifying a routing sequence to be used for the shipment movement in lieu of specifying each carrier within the movement, use

TD502 to identify the party responsible for defining the routing sequence, and use TD503 to identify the actual routing sequence,

specified by the party identified in TD502.

DLMS Note:

Use only in 2/HL/0100 shipment loops to identify the intended mode of shipment between the shipping activity and designated consignee.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

TD504 91 Transportation Method/Type Code

Description: Code specifying the method

or type of transportation for the shipment

DLMS Note: 1. Use to identify the mode of

shipment code.

2. DLMS users see the Transportation

Method/Type Code Conversion Guide for

available codes.

X ID 1/2 Must use 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 17 August 31, 2020

REF Reference Identification Pos: 1500 Max: >1

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To specify identifying information

Syntax Rules: 

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

Semantics: 

1. REF04 contains data relating to the value cited in REF02.

DLMS Note:

Use in 2/HL/0100 shipment loops to indicate the number of line items included in the shipment and the Transportation Control Number

identification number controlling the shipment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

REF01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: 1. Use only one of codes BT

or LT as needed, to identify batch numbers

or lot numbers assigned to the materiel.

2. For DLMS use, only the following codes

are authorized.

M ID 2/3 Must use 1

Code Name

BT Batch Number

DLMS Note:

Use as needed to identify the manufacturer's batch number or other number identifying the production

run.

K1 Foreign Military Sales Notice Number

DLMS Note:

Must use only in 2/HL/0100 shipment loops to identify the NOA Notice Number, which reflects the

number of times the NOA has been sent to the Freight Forwarder/Country Representative. Second and

subsequent transmissions may be interpreted as follow-ups. Authorized DLMS enhancement; see

DLMS Introductory Note 4e. Refer to ADC 1098.

LO Load Planning Number

DLMS Note:

Use in 2/HL/0100 shipment loops to identify the number of transactions included in the shipment.

LT Lot Number

DLMS Note:

Use to identify the manufacturer's lot number.

TG Transportation Control Number (TCN)

DLMS Note:

Must use only in 2/HL/0100 shipment loops to identify the number assigned to control the shipment

between the shipper and consignee.

TN Transaction Reference Number

DLMS Note:

Must use in every 2/HL/0100 line item loop to identify the customer assigned transaction number for the

requisition associated with the shipment unit.

REF02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

X AN 1/50 Must use 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F856N0NA05 18 August 31, 2020

as specified by the Reference Identification

Qualifier

REF04 C040 Reference Identifier

Description: To identify one or more

reference numbers or identification

numbers as specified by the Reference

Qualifier

Syntax: 

1. P0304 - If either C04003 or C04004 is

present, then the other is required.

2. P0506 - If either C04005 or C04006 is

present, then the other is required.

O Comp Used 1

REF04-01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

M ID 2/3 Must use 1

Code Name

W8 Suffix

DLMS Note:

Use with REF01 code TN to identify the transaction number suffix.

REF04-02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

M AN 1/50 Must use 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 19 August 31, 2020

LH1 Hazardous Identification Information Pos: 1520 Max: 1

Detail - Optional

Loop: LH1 Elements: 4

User Option (Usage): Used

Purpose: To specify the hazardous commodity identification reference number and quantity

Comments: 

1. LH101 and LH102 are used to convey the number and type of packages for bulk and nonbulk movements.

2. LH106 and LH107 are used to convey the quantity or volume and unit of measure for nonbulk shipments only.

3. In LH109, a value of "R" or "P" requires that the receiver generate the words "residue: last contained" prior to the shipping name in

accordance with regulations.

DLMS Note:

Use only in 2/HL/0100 shipment loops for hazardous/explosive shipments. Use the LH1 loop to identify the hazardous characteristics of the

shipment. Repeat the LH1 loop as required identifying the hazardous characteristics associated with the quantity of pieces of the lading

commodity. Authorized DLMS enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LH101 355 Unit or Basis for Measurement Code

Description: Code specifying the units in

which a value is being expressed, or

manner in which a measurement has been

taken

DLMS Note: 1. Use to identify the type of

packaging related to the quantity in the

LH102.

2. DLMS users see the Unit of Issue and

Purchase Unit Conversion Table. 

M ID 2/2 Must use 1

LH102 80 Lading Quantity

Description: Number of units (pieces) of

the lading commodity

DLMS Note: Use to identify the number of

pieces of the lading commodity that is

hazardous in the shipment.

M N0 1/7 Must use 1

LH103 277 UN/NA Identification Code

Description: Code identifying the

hazardous material identification number as

required by Title 49 of the code of Federal

Regulations; UN/NA stands for United

Nations/North America

DLMS Note: Use to identify the United

Nations/North America hazardous material

identification number as required by 49

CFR.

O ID 6/6 Used 1

LH110 254 Packing Group Code

Description: Code indicating degree of

danger in terms of Roman number I, II or III

DLMS Note: Indicate the required packing

group using Roman Numeral I, II, or III to

indicate the degree of danger. Source is 49

CFR Table 172.101.

O ID 1/3 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 20 August 31, 2020

LH2 Hazardous Classification Information Pos: 1530 Max: 4

Detail - Optional

Loop: LH1 Elements: 1

User Option (Usage): Used

Purpose: To specify the hazardous notation and endorsement information

Syntax Rules: 

1. P0607 - If either LH206 or LH207 is present, then the other is required.

2. P0809 - If either LH208 or LH209 is present, then the other is required.

3. P1011 - If either LH210 or LH211 is present, then the other is required.

4. P1213 - If either LH212 or LH213 is present, then the other is required.

Semantics: 

1. LH206 and LH207 indicate the flashpoint temperature.

2. LH208 and LH209 indicate the control temperature.

3. LH210 and LH211 indicate the emergency temperature.

4. LH212 and LH213 indicate the net explosive weight.

DLMS Note:

Authorized DLMS enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LH201 215 Hazardous Classification

Description: The hazardous classification

corresponding to the shipping name of the

hazardous commodity

DLMS Note: Use to identify the primary

hazard class or division for the hazardous

material as shown in column 3 of 49 CFR

Table 172.101. If there is no hazard class

or division, use the code in that column,

such as ORM-D (Other Regulated Material),

reference 49 CFR 173.2.

DLMS Note: Use to identify the primary

hazard class or division for the hazardous

material as shown in column 3 of 49 CFR

Table 172.101. If there is no hazard class

or division, use the code in that column,

such as ORM-D (Other Regulated Material),

reference 49 CFR 173.2.

O ID 1/30 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 21 August 31, 2020

LH3 Hazardous Material Shipping Name Pos: 1540 Max: 12

Detail - Optional

Loop: LH1 Elements: 2

User Option (Usage): Used

Purpose: To specify the hazardous material shipping name and additional descriptive requirements

Syntax Rules: 

1. P0102 - If either LH301 or LH302 is present, then the other is required.

Semantics: 

1. If LH304 is "Y", then this is an Association of American Railroads Operations and Transportation Bulletin 55 commodity. If "N", it is not

an Association of American Railroads Operations and Transportation Bulletin 55 commodity.

DLMS Note:

1. Mandatory for all hazardous material shipments, including ammunition and explosives.

2. Create additional LH3 segment(s) for the remainder of the Proper Shipping Name exceeding 25 characters in the LH301.

3. Authorized DLMS enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LH301 224 Hazardous Material Shipping Name

Description: The proper shipping name of

the hazardous commodity as specified by

Title 49 Code of Federal Regulations, or the

shipping name of the dangerous good as

defined in the Canadian Transportation of

Dangerous Goods Act and Regulations, or

the international regulations as

promulgated by the United Nations

DLMS Note: Use to identify the Proper

Shipping Name.

X AN 1/25 Used 1

LH302 984 Hazardous Material Shipping Name

Qualifier

Description: Qualifier indicating the source

(regulatory) of the proper shipping name

DLMS Note: Use one of the following

codes to describe the Proper Shipping

Name.

X ID 1/1 Used 1

Code Name

C Canadian Shipping Name

D Domestic (United States) Shipping Name

I International Shipping Name
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 22 August 31, 2020

LHR Hazardous Material Identifying

Reference Numbers

Pos: 1590 Max: 10

Detail - Optional

Loop: LH1 Elements: 2

User Option (Usage): Used

Purpose: To transmit specific hazardous material reference numbers

DLMS Note:

1. Use this segment to identify applicable transportation approval authorities for hazardous/explosives shipments.

2. Use this segment to identify the DODIC for ammunition/explosive shipments.

3. Authorized DLMS enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LHR01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

M ID 2/3 Must use 1

Code Name

1I Department of Defense Identification Code (DoDIC)

DLMS Note:

Use to identify the DODIC of the ammunition or explosive.

HA Competent Authority

DLMS Note:

1. Use to identify the Competent Authority Approval Number (CAA) issued by the Department of

Transportation.

2. The approval number format is CA-YYNNNNA, where YY=last two positions of year, N=approval

number within that year, and A=optional alphanumeric designator.

3. This is only applicable when DoD requires an exception to the international performance oriented

packaging rules.

1. Use to identify the Competent Authority Approval Number (CAA) issued by the Department of

Transportation.

2. The approval number format is CA-YYNNNNA, where YY=last two positions of year, N=approval

number within that year, and A=optional alphanumeric designator.

3. This is only applicable when DoD requires an exception to the international performance oriented

packaging rules.

HE Hazardous Exemption Number

DLMS Note:

1. Use to identify the Department of Transportation Exemption (DOT-E) Number.

2. This identifies the DOT-E exemption to any of the 49 CFR regulations for hazardous materials.

3. Normally used for domestic shipments. Can be used for international shipments, but is not

guaranteed to be accepted by international customs.

HN Hazardous Certification Number

DLMS Note:

1. Use to identify the Certification of Equivalency (COE). 

2. This identifies the DoD approval when packaging design differs from the prescribed regulations in 49

CFR. It certifies that the proposed packaging design equals or exceeds the comparable requirements

of 49 CFR for the commodity being shipped.

LHR02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

M AN 1/50 Must use 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 23 August 31, 2020

DTM Date/Time Reference Pos: 2000 Max: 10

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

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

2. C0403 - If DTM04 is present, then DTM03 is required.

3. P0506 - If either DTM05 or DTM06 is present, then the other is required.

DLMS Note:

Use in 2/HL/0100 shipment and line item loops to identify dates associated with the NOA.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DTM01 374 Date/Time Qualifier

Description: Code specifying type of date

or time, or both date and time

M ID 3/3 Must use 1

Code Name

169 Product Availability Date

DLMS Note:

Use in every 2/HL/0100 shipment loop to identify the NOA preparation date.

601 First Submission

DLMS Note:

Use in the shipment loop to identify the original NOA preparation date when the original NOA contained

items which the customer rejected.

996 Required Delivery

DLMS Note:

Use to accommodate legacy system requirements to identify the required availability date.

DTM02 373 Date

Description: Date expressed as

CCYYMMDD where CC represents the first

two digits of the calendar year

X DT 8/8 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 24 August 31, 2020

N1 Name Pos: 2200 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

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

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

1. Use the 2/N1/2200 loop in the 2/HL/010 address loop to identify the organization originating the transaction set and the organization to

receive the transaction set.

2. Use additional repetitions of the 2/N1/2200 loop to identify the consignor, ship-to, and mark-for activities. Authorized DLMS

enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: 1. Use only one of codes IF or

CY.

2. For DLMS use, only the following codes

are authorized.

M ID 2/3 Must use 1

Code Name

CI Consignor

DLMS Note:

1. Use as needed to identify the shipping activity.

2. In the PER segment, provide the consignor contact information.

CY Country

DLMS Note:

Use to identify the designated CR to receive the transaction set.

IF International Freight Forwarder

DLMS Note:

Use to identify the designated FF to receive the transaction set.

ST Ship To

DLMS Note:

Use to identify the Ship-To MAPAC. Authorized DLMS enhancement; see DLMS Introductory Note 4e. 

Refer to ADC 1098.

X6 International Organization

DLMS Note:

Use to identify the International Logistics Control Office (ILCO) serving as the SC Implementing Agency

for the shipment. The ILCO is identified by the SC Implementing Agency Code in the first position of

the document number; authorized values are restricted to those identified in DLM 4000.25, Volume 2

Appendix 7.2. Authorized DLMS enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098.

Z7 Mark-for Party
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

Code Name

004030F856N0NA05 25 August 31, 2020

DLMS Note:

Use to identify the Mark for MAPAC. Authorized DLMS enhancement; see DLMS Introductory Note 4e. 

Refer to ADC 1098.

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Must use 1

Code Name

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

Use to indicate the Security Assistance structured address data that identifies the CR/FF to receive the

NOA, the Ship To, and the Mark For. Interpretation of this data may require additional codes cited

elsewhere in the transaction.

LC Agency Location Code (U.S. Government)

DLMS Note:

Use to identify the International Logistics Control Office (ILCO) SC Implementing Agency Code. 

Authorized values are restricted to those identified in DLM 4000.25, Volume 2 Appendix 7.2. 

Authorized DLMS enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Used 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

Code Name

FR Message From

DLMS Note:

Must use with 2/N101/2200 code CI to indicate that the organization cited in N104 is originating the

transaction set.

PK Party to Receive Copy

DLMS Note:

Use with 2/N101/2200 Code X6 when the organization cited in N104 is receiving an information copy of

the transaction set.

TO Message To

DLMS Note:

Use with 2/N101/2200 codes CY, IF, and X6 as applicable when the organization cited in N104 is

receiving the transaction set.
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 26 August 31, 2020

PER Administrative Communications

Contact

Pos: 2700 Max: 3

Detail - Optional

Loop: N1 Elements: 8

User Option (Usage): Used

Purpose: To identify a person or office to whom administrative communications should be directed

Syntax Rules: 

1. P0304 - If either PER03 or PER04 is present, then the other is required.

2. P0506 - If either PER05 or PER06 is present, then the other is required.

3. P0708 - If either PER07 or PER08 is present, then the other is required.

DLMS Note:

Use to provide point of contact information. Use only in the N1 loop identifying the consignor. Authorized DLMS enhancement; see DLMS

Introductory Note 4e. Refer to ADC 1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PER01 366 Contact Function Code

Description: Code identifying the major

duty or responsibility of the person or group

named

M ID 2/2 Must use 1

Code Name

IC Information Contact

DLMS Note:

Use to identify the point of contact.

PER02 93 Name

Description: Free-form name

DLMS Note: Use to provide the full name

of the point of contact.

O AN 1/60 Used 1

PER03 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

X ID 2/2 Used 1

Code Name

TE Telephone

DLMS Note:

Use to identify the commercial phone number.

PER04 364 Communication Number

Description: Complete communications

number including country or area code

when applicable

X AN 1/256 Used 1

PER05 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

X ID 2/2 Used 1

Code Name

EM Electronic Mail

PER06 364 Communication Number

Description: Complete communications

number including country or area code

when applicable

X AN 1/256 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F856N0NA05 27 August 31, 2020

PER07 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

X ID 2/2 Used 1

Code Name

FX Facsimile

DLMS Note:

Use to identify the commercial fax number.

PER08 364 Communication Number

Description: Complete communications

number including country or area code

when applicable

X AN 1/256 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 28 August 31, 2020

SAC Service, Promotion, Allowance, or

Charge Information

Pos: 3200 Max: 1

Detail - Optional

Loop: SAC Elements: 3

User Option (Usage): Used

Purpose: To request or identify a service, promotion, allowance, or charge; to specify the amount or percentage for the service, promotion,

allowance, or charge

Syntax Rules: 

1. R0203 - At least one of SAC02 or SAC03 is required.

2. P0304 - If either SAC03 or SAC04 is present, then the other is required.

3. P0607 - If either SAC06 or SAC07 is present, then the other is required.

4. P0910 - If either SAC09 or SAC10 is present, then the other is required.

5. C1110 - If SAC11 is present, then SAC10 is required.

6. L130204 - If SAC13 is present, then at least one of SAC02 or SAC04 is required.

7. C1413 - If SAC14 is present, then SAC13 is required.

8. C1615 - If SAC16 is present, then SAC15 is required.

Semantics: 

1. If SAC01 is "A" or "C", then at least one of SAC05, SAC07, or SAC08 is required.

2. SAC05 is the total amount for the service, promotion, allowance, or charge.

3. If SAC05 is present with SAC07 or SAC08, then SAC05 takes precedence.

4. SAC08 is the allowance or charge rate per unit. 

5. SAC10 and SAC11 is the quantity basis when the allowance or charge quantity is different from the purchase order or invoice quantity.

6. SAC10 and SAC11 used together indicate a quantity range, which could be a dollar amount, that is applicable to service, promotion,

allowance, or charge.

7. SAC13 is used in conjunction with SAC02 or SAC04 to provide a specific reference number as identified by the code used.

8. SAC14 is used in conjunction with SAC13 to identify an option when there is more than one option of the promotion.

9. SAC16 is used to identify the language being used in SAC15.

Comments: 

1. SAC04 may be used to uniquely identify the service, promotion, allowance, or charge. In addition, it may be used in conjunction with

SAC03 to further define SAC02.

2. In some business applications, it is necessary to advise the trading partner of the actual dollar amount that a particular allowance,

charge, or promotion was based on to reduce ambiguity. This amount is commonly referred to as "Dollar Basis Amount". It is

represented in the SAC segment in SAC10 using the qualifier "DO" - Dollars in SAC09.

DLMS Note:

Use the SAC loop in the 2/HL/0100 shipment loop. Authorized DLMS enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

SAC01 248 Allowance or Charge Indicator

Description: Code which indicates an

allowance or charge for the service

specified

M ID 1/1 Must use 1

Code Name

C Charge

DLMS Note:

Use for X12 syntax compliance.

SAC02 1300 Service, Promotion, Allowance, or

Charge Code

Description: Code identifying the service,

promotion, allowance, or charge

X ID 4/4 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 29 August 31, 2020

Code Name

C675 Entered Value

DLMS Note:

Use to identify the total shipment value.

SAC05 610 Amount

Description: Monetary amount

DLMS Note: Enter total shipment value in

US Dollars and Cents.

O N2 1/15 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 30 August 31, 2020

YNQ Yes/No Question Pos: 3350 Max: 10

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To identify and answer yes and no questions, including the date, time, and comments further qualifying the condition

Syntax Rules: 

1. E010910 - Only one of YNQ01, YNQ09 or YNQ10 may be present.

2. P0304 - If either YNQ03 or YNQ04 is present, then the other is required.

3. C0908 - If YNQ09 is present, then YNQ08 is required.

Semantics: 

1. YNQ02 confirms or denies the statement made in YNQ01, YNQ09 or YNQ10. A "Y" indicates the statement is confirmed; an "N"

indicates the statement is denied.

2. YNQ10 contains a free-form question when codified questions are not available.

DLMS Note:

Use in 2/HL/0100 shipment loop to indicate if the shipment contains hazardous materials or explosives. Authorized DLMS enhancement;

see DLMS Introductory Note 4e. Refer to ADC 1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

YNQ01 1321 Condition Indicator

Description: Code indicating a condition

X ID 2/2 Used 1

Code Name

C8 Special Servicing Required

DLMS Note:

Use to indicate if the shipment contains explosives.

QQ Item is a Hazardous Item

DLMS Note:

Use to indicate if the shipment contains hazardous materials.

YNQ02 1073 Yes/No Condition or Response Code

Description: Code indicating a Yes or No

condition or response

DLMS Note: Use one of the following

codes in response to the YNQ01.

M ID 1/1 Must use 1

Code Name

N No

Y Yes
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 31 August 31, 2020

LM Code Source Information Pos: 3400 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

Must use this 2/LM/3400 loop to identify coded information maintained in department or agency documentation.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 32 August 31, 2020

LQ Industry Code Pos: 3500 Max: 100

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

DLMS Note:

Use to identify codes consistent with management information requirements.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific

industry code list

DLMS Note: 1. Use codes 33, 34, 35, 40,

A3, and NT only in 2/HL/0100 shipment

loops.

2. Use codes 0, 71, 78, 85, 95, A4, A5, A6,

A9, AJ, BD, DF, EQ, COG, IMC, MCC, and

SMI only in 2/HL/0100 line item loops.

3. For DLMS use, only the following codes

are authorized.

O ID 1/3 Must use 1

Code Name

0 Document Identification Code

33 Air Commodity and Special Handling Code

DLMS Note:

Use for air shipments to identify materiel manifesting, customs, and special handling or reporting

requirements.

34 Water Commodity and Special Handling Code

DLMS Note:

Use for water shipments to identify the predominant commodity within the shipment unit for ocean

manifesting.

35 Air Dimension Code

DLMS Note:

Use for air shipments.

40 Type Pack Code

DLMS Note:

Use the DOD code to describe the type of pack for the shipment unit. Refer to the Table Management

Distribution System (TDMS) available at URL: 

https://www-tmds.c2.amc.af.mil/TMDS/USTRNSCOM_index.xsql for applicable code list. (ADC 309

includes an abbreviated listing to facilitate implementation within DoD supply systems.)

71 Service and Agency Code

DLMS Note:

Must use in FMS transactions to identify the customer country's requisitioning Service code: B, D, K, P,

or T.

78 Project Code

DLMS Note:

Use to identify the special programs, exercises, project, operation, and other purposes.

85 Country and Activity Code

DLMS Note:

Use to identify the Security Cooperation Customer Code. Refer to ADC 1075.
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

Code Name

004030F856N0NA05 33 August 31, 2020

95 Offer and Release Option Code

DLMS Note:

Use to identify the offer and release option code.

A3 Delivery Term Code

DLMS Note:

Use to identify the Delivery Term Code for the shipment. Authorized DLMS enhancement; see DLMS

Introductory Note 4e. Refer to ADC 1098.

A4 Case Designator Number

DLMS Note:

Must use in FMS transactions to identify the FMS case number.

A5 Subcase Number

DLMS Note:

Use in FMS transactions based on Service requirements.

A6 Freight Forwarder Number

DLMS Note:

Use to identify the CR/FF to receive shipments and documentation.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

2. Future streamlined data; see introductory DLMS note 4c.

AJ Utilization Code

DLMS Note:

1. Under Legacy MILSTRIP, this is the first position of the document serial number.

2. Authorized DLMS enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098.

AL Special Requirements Code

DLMS Note:

1. Use to identify the precedence, special handling, and processing requirements.

2. Under legacy MILSTRIP, this is carried in the required delivery date field.

3. Authorized DLMS enhancement; see DLMS Introductory Note 4e. Refer to ADC 1098.

BD Transportation Priority Code

DLMS Note:

Use to identify the transportation priority.

DF Media and Status Code

EQ Controlled Inventory Item Code

DLMS Note:

Use to identify the Controlled Inventory Item Code for the item. Authorized DLMS enhancement; see

DLMS Introductory Note 4e. Refer to ADC 1098.

NT Type of Cargo Code

DLMS Note:

Use for water shipments to identify the predominate type of cargo code within the shipment unit for

ocean manifesting. Used in conjunction with the water commodity and special handling code identified

in the 2/LQ01/3500 Code 34. Authorized DLMS enhancement; see DLMS Introductory Note 4e. Refer

to ADC 1098.

COG Cognizance Symbol

DLMS Note:

Use to identify the materiel cognizance symbol (COG) of the end item. Indicate NSL for non-stock

numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy

Components are to perpetuate without action.

IMC Item Management Code

DLMS Note:

Use to identify the Item Management Code (IMC) for integrated materiel management. Indicate NSL for

non-stock numbered listed items. This is a Navy-unique data element meaningful to Navy only; 
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

Code Name

004030F856N0NA05 34 August 31, 2020

Non-Navy Components are to perpetuate without action.

MCC Material Control Code

DLMS Note:

Use to identify the Material Control Code (MCC) for special inventory reporting. Indicate NSL for

non-stock numbered listed items. This is a Navy-unique data element meaningful to Navy only;

Non-Navy Components are to perpetuate without action.

SMI Special Material Identification Code

DLMS Note:

Use to identify the Special Material Identification Code (SMIC) for an end item. Indicate NSL for

non-stock numbered listed items. This is a Navy-unique data element meaningful to Navy only;

Non-Navy Components are to perpetuate without action.

LQ02 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

X AN 1/30 Must use 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1098, 1136, 1287, 1353, 1367 and 1370 DLM 4000.25

004030F856N0NA05 35 August 31, 2020

SE Transaction Set Trailer Pos: 0200 Max: 1

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)

Comments: 

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

SE01 96 Number of Included Segments

Description: Total number of segments

included in a transaction set including ST

and SE segments

M N0 1/10 Must use 1

SE02 329 Transaction Set Control Number

Description: Identifying control number

that must be unique within the transaction

set functional group assigned by the

originator for a transaction set

DLMS Note: Cite the same number as the

one cited in ST02. 

M AN 4/9 Must use 1