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

004010F856N1NA10 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:

1a. Organizations use this transaction set to provide shipment availability, specification and content information to designated Country

Representatives/ Freight Forwarders (CR/FF). Use a single occurrence of this transaction set to transmit single or multiple NOAs to one

designated CR/FF.

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

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 05, 2014.

- 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

1a. Organizations use this transaction set to provide shipment availability, specification and content information to designated Country

Representatives/ Freight Forwarders (CR/FF). Use a single occurrence of this transaction set to transmit single or multiple NOAs to one

designated CR/FF.

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

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 05, 2014.

- 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

010 ST Transaction Set Header M 1 Must use

020 BSN Beginning Segment for Ship Notice M 1 Must use

* 040 DTM Date/Time Reference O 10 Not Used

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

004010F856N1NA10 2 August 31, 2020

Pos Id Segment Name Req Max Use Repeat Notes Usage

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

010 HL Hierarchical Level M 1 C2/010 Must use

020 LIN Item Identification O 1 Used

030 SN1 Item Detail (Shipment) O 1 Used

* 040 SLN Subline Item Detail O 1000 Not Used

* 050 PRF Purchase Order Reference O 1 Not Used

* 060 PO4 Item Physical Details O 1 Not Used

* 070 PID Product/Item Description O 200 Not Used

080 MEA Measurements O 40 Used

* 090 PWK Paperwork O 25 Not Used

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

110 TD1 Carrier Details (Quantity and

Weight)

O 20 Used

120 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 12 Used

* 130 TD3 Carrier Details (Equipment) O 12 Not Used

* 140 TD4 Carrier Details (Special Handling,

or Hazardous Materials, or Both)

O 5 Not Used

* 145 TSD Trailer Shipment Details O 1 Not Used

150 REF Reference Identification O >1 Used

* 151 PER Administrative Communications

Contact

O 3 Not Used

* LOOP ID - LH1 * LOOP ID - LH1 100

* 152 LH1 Hazardous Identification

Information

O 1 Not Used

* 153 LH2 Hazardous Classification

Information

O 4 Not Used

* 154 LH3 Hazardous Material Shipping

Name

O 12 Not Used

* 155 LFH Freeform Hazardous Material

Information

O 20 Not Used

* 156 LEP EPA Required Data O >1 Not Used

* 157 LH4 Canadian Dangerous

Requirements

O 1 Not Used

* 158 LHT Transborder Hazardous

Requirements

O 3 Not Used

* 159 LHR Hazardous Material Identifying

Reference Numbers

O 10 Not Used

* 160 PER Administrative Communications

Contact

O 5 Not Used

* 161 LHE Empty Equipment Hazardous

Material Information

O 1 Not Used

* LOOP ID - CLD * LOOP ID - CLD 200

* 170 CLD Load Detail O 1 Not Used

* 180 REF Reference Identification O 200 Not Used

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

* 190 MAN Marks and Numbers O >1 Not Used

200 DTM Date/Time Reference O 10 Used

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

* 215 PAL Pallet Information O 1 Not Used

LOOP ID - N1 LOOP ID - N1 200

220 N1 Name O 1 Used

* 230 N2 Additional Name Information O 2 Not Used

* 240 N3 Address Information O 2 Not Used

* 250 N4 Geographic Location O 1 Not Used

* 260 REF Reference Identification O 12 Not Used
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F856N1NA10 3 August 31, 2020

* 270 PER Administrative Communications

Contact

O 3 Not Used

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

* 290 SDQ Destination Quantity O 50 Not Used

* 300 ETD Excess Transportation Detail O 1 Not Used

* 310 CUR Currency O 1 Not Used

* LOOP ID - SAC * LOOP ID - SAC >1

* 320 SAC Service, Promotion, Allowance, or

Charge Information

O 1 Not Used

* 325 CUR Currency O 1 Not Used

* 330 GF Furnished Goods and Services O 1 Not Used

* 335 YNQ Yes/No Question O 10 Not Used

LOOP ID - LM LOOP ID - LM 10

340 LM Code Source Information O 1 Must use

350 LQ Industry Code M 100 Must use

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

* 360 V1 Vessel Identification O 1 Not Used

* 370 R4 Port or Terminal O >1 Not Used

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

Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage

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

020 SE Transaction Set Trailer M 1 Must use

Notes: 

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

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

Comments: 

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

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

004010F856N1NA10 4 August 31, 2020

ST Transaction Set Header Pos: 010 Max: 1

Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

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

Semantics: 

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

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

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
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 5 August 31, 2020

BSN Beginning Segment for Ship Notice Pos: 020 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

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.

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

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

Ref Id Element Name Req Type Min/Max Usage Rep

004010F856N1NA10 6 August 31, 2020

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, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 7 August 31, 2020

HL Hierarchical Level Pos: 010 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/010 loop iteration to provide transaction set address information.

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

4. Use a single or multiple 2/HL/010 shipment loop iterations to identify the attributes associated with a single FMS notice number assigned

to control the 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/010 loop iteration to provide transaction set address information.

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

4. Use a single or multiple 2/HL/010 shipment loop iterations to identify the attributes associated with a single FMS notice number assigned

to control the 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/010 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/010 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/010 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, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 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, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 9 August 31, 2020

LIN Item Identification Pos: 020 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/010 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. 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:

Use to identify the manufacturer's series number of the end item.
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

Code Name

004010F856N1NA10 10 August 31, 2020

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 materi\el 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, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 11 August 31, 2020

SN1 Item Detail (Shipment) Pos: 030 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/010 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 DLMS Unit of Issue

and Purchase Unit Conversion Table for

available codes. 

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

004010F856N1NA10 12 August 31, 2020

MEA Measurements Pos: 080 Max: 40

Detail - Optional

Loop: HL Elements: 3

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:

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

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.

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, pieces, 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)

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

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

Ref Id Element Name Req Type Min/Max Usage Rep

004010F856N1NA10 13 August 31, 2020

Code Name

CF Cubic Feet

DLMS Note:

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

LB Pound

DLMS Note:

Use with code A in MEA02 to indicate that the shipment weight is expressed as pounds.
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 14 August 31, 2020

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

Detail - Optional

Loop: HL Elements: 1

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/010 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
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 15 August 31, 2020

TD5 Carrier Details (Routing

Sequence/Transit Time)

Pos: 120 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/010 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, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 16 August 31, 2020

REF Reference Identification Pos: 150 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/010 shipment loops to indicate the number of line items included in the shipment and the FMS Notice 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. 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/010 shipment loops to identify the number assigned to control the shipment

between the shipper and consignee.

LO Load Planning Number

DLMS Note:

Use in 2/HL/010 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.

TN Transaction Reference Number

DLMS Note:

Must use in every 2/HL/010 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

as specified by the Reference Identification

Qualifier

X AN 1/30 Must use 1

REF04 C040 Reference Identifier

Description: To identify one or more

reference numbers or identification

numbers as specified by the Reference

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

Ref Id Element Name Req Type Min/Max Usage Rep

004010F856N1NA10 17 August 31, 2020

Qualifier

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/30 Must use 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 18 August 31, 2020

DTM Date/Time Reference Pos: 200 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/010 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/010 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

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

004010F856N1NA10 19 August 31, 2020

N1 Name Pos: 220 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/220 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 iterations to identify other organizations associated with the transaction.

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 98

or CY.

2. The following codes are authorized.

M ID 2/3 Must use 1

Code Name

98 Freight Management Facilitator

DLMS Note:

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

CI Consignor

DLMS Note:

Use as needed to identify the shipping activity.

CY Country

DLMS Note:

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

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 SA structured address data which identifies the CR//FF to receive the NOA. 

Interpretation of this data may require additional codes

cited elsewhere in the transaction.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code X AN 2/80 Used 1
DLMS Implementation Convention (IC) 856N Notice of Availability ADC 309, 1043, 1043C, 1075, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F856N1NA10 20 August 31, 2020

Description: Code identifying a party or

other code

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/220 code CI to indicate that the organization cited in N104 is originating the

transaction set.

TO Message To

DLMS Note:

Must use with 2/N101/220 codes CY and 98 to indicate that the organization cited in N104 is receiving

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

004010F856N1NA10 21 August 31, 2020

LM Code Source Information Pos: 340 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Must use

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/340 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, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 22 August 31, 2020

LQ Industry Code Pos: 350 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, and

69 only in 2/HL/010 shipment loops.

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

BD, and DF only in 2/HL/010 line item

loops.

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

95 Offer and Release Option Code

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

Code Name

004010F856N1NA10 23 August 31, 2020

Use to identify the offer and release option code.

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. DLMS enhancement; see introductory DLMS note 4a.

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. DLMS enhancement; see introductory DLMS note 4a.

BD Transportation Priority Code

DLMS Note:

Use to identify the transportation priority.

DF Media and Status Code

COG Cognizance Symbol

DLMS Note:

Use to identify the material 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 material management. 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.

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, 1136, 1254, 1287, 1353, 1367 and 1370 DLM 4000.25

004010F856N1NA10 24 August 31, 2020

SE Transaction Set Trailer Pos: 020 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