DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 1 March 16, 2022

870 Order Status Report

Functional Group=RS

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Order Status Report Transaction Set

(870) for use within the context of an Electronic Data Interchange (EDI) environment. The transaction set can be used to report on the current

status of a requirement forecast, an entire purchase order, selected line items on a purchase order, selected products/services on a purchase

order, or purchase orders for a specific customer in their entirety or on a selection basis. The transaction set can also be used to report on the

current status of single or multiple requisitions. The report format allows for the inclusion of "reasons" relative to the status. This transaction set

may also be used to update the supplier's scheduled shipment or delivery dates. This transaction set can result from either an inquiry or a

prearranged schedule agreed to by the trading partners.

DLMS Note:

1. Country Representatives/Freight Forwarders (CRs/FFs) use this transaction set to respond to a Foreign Military Sales (FMS) Notice of

Availability (NOA) providing shipment instructions for materiel reported available for shipment.

2. 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 Defense Enterprise Data Standards

Office (DEDSO) Website at www.dla.mil/does/DLMS.

3. This DLMS Implementation Convention (IC) 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 DEDSO 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 DEDSO 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 DEDSO 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 DEDSO 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.

4. Effective April 1, 2014, refer to ADC 1075. Users must reference the GENC Standard for country codes

(https://nsgreg.nga.mil/genc/discovery) for a listing of authorized values. Under DLMS, use the GENC Digraph (two-character).

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 DEDSO 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 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- ADC 448, Implementation of International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries and their

Subdivisions

- ADC 448B, Delayed implementation for International Organization for Standardization (ISO) 3166-1 Codes for the Identification of

Countries and their Subdivisions

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

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

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

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

April 21, 2020

- 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

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on March 16, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

1. Country Representatives/Freight Forwarders (CRs/FFs) use this transaction set to respond to a Foreign Military Sales (FMS) Notice of

Availability (NOA) providing shipment instructions for materiel reported available for shipment.

2. 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 Defense Enterprise Data Standards

Office (DEDSO) Website at www.dla.mil/does/DLMS.

3. This DLMS Implementation Convention (IC) 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 DEDSO 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 DEDSO 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 DEDSO 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 DEDSO 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.

4. Effective April 1, 2014, refer to ADC 1075. Users must reference the GENC Standard for country codes

(https://nsgreg.nga.mil/genc/discovery) for a listing of authorized values. Under DLMS, use the GENC Digraph (two-character).

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 DEDSO 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 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

- ADC 448, Implementation of International Organization for Standardization (ISO) 3166-1 Codes for the Identification of Countries and their

Subdivisions

- ADC 448B, Delayed implementation for International Organization for Standardization (ISO) 3166-1 Codes for the Identification of

Countries and their Subdivisions

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

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

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

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

April 21, 2020

- 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

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards

Office (DEDSO) - Completed on March 16, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

Heading:
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 2 March 16, 2022

Pos Id Segment Name Req Max Use Repeat Notes Usage

10 ST Transaction Set Header M 1 Must use

20 BSR Beginning Segment for Order

Status Report

M 1 Must use

* 42 TD3 Carrier Details (Equipment) O 1 Not Used

* 43 TD4 Carrier Details (Special Handling,

or Hazardous Materials, or Both)

O 1 Not Used

44 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 1 Used

* 45 DTM Date/Time Reference O 10 Not Used

* LOOP ID - REF * LOOP ID - REF >1

* 46 REF Reference Identification O 1 Not Used

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

LOOP ID - N1 LOOP ID - N1 200

50 N1 Name O 1 Must use

* 60 N2 Additional Name Information O 2 Not Used

* 70 N3 Address Information O 2 Not Used

* 80 N4 Geographic Location O 1 Not Used

* 90 REF Reference Identification O 12 Not Used

* 100 PER Administrative Communications

Contact

O 3 Not Used

* 105 PWK Paperwork O 1 Not Used

* LOOP ID - LM * LOOP ID - LM 10

* 120 LM Code Source Information O 1 Not Used

130 LQ Industry Code M 100 Must use

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL LOOP ID - HL 1000

10 HL Hierarchical Level M 1 Must use

* 20 PRF Purchase Order Reference O 1 Not Used

* LOOP ID - ISR * LOOP ID - ISR 104

* 30 ISR Item Status Report O 1 Not Used

* 40 PID Product/Item Description O 6 Not Used

* 50 QTY Quantity O 4 Not Used

* 70 PER Administrative Communications

Contact

O 3 Not Used

80 DTM Date/Time Reference O 10 Used

* 86 CS Contract Summary O 3 N2/86 Not Used

LOOP ID - REF LOOP ID - REF >1

87 REF Reference Identification O 1 Must use

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

LOOP ID - N1 LOOP ID - N1 200

90 N1 Name O 1 Must use

100 N2 Additional Name Information O 2 Used

110 N3 Address Information O 2 Used

120 N4 Geographic Location O 1 Used

* 130 REF Reference Identification O 12 Not Used

140 PER Administrative Communications

Contact

O 3 Used

LOOP ID - LM LOOP ID - LM 10

144 LM Code Source Information O 1 Used

145 LQ Industry Code M 100 Must use
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

Pos Id Segment Name Req Max Use Repeat Notes Usage

004010F870N1NA10 3 March 16, 2022

* LOOP ID - PO1 * LOOP ID - PO1 1000

* 150 PO1 Baseline Item Data O 1 Not Used

* 155 CUR Currency O 1 Not Used

* 160 SLN Subline Item Detail O 100 Not Used

* 170 PO3 Additional Item Detail O 1 Not Used

* 180 PID Product/Item Description O 1000 Not Used

* 190 MEA Measurements O 40 Not Used

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

* LOOP ID - ISR * LOOP ID - ISR 104

* 210 ISR Item Status Report O 1 Not Used

* 220 PID Product/Item Description O 6 Not Used

* 230 QTY Quantity O 4 Not Used

* 240 DTM Date/Time Reference O 10 Not Used

* 250 N1 Name O 1 Not Used

* 251 N2 Additional Name Information O 2 Not Used

* 252 N3 Address Information O 2 Not Used

* 253 N4 Geographic Location O 1 Not Used

* 260 TD1 Carrier Details (Quantity and

Weight)

O 1 Not Used

* 270 TD5 Carrier Details (Routing

Sequence/Transit Time)

O 1 Not Used

* 280 TD3 Carrier Details (Equipment) O 1 Not Used

* 290 TD4 Carrier Details (Special Handling,

or Hazardous Materials, or Both)

O 1 Not Used

* 300 REF Reference Identification O 12 Not Used

* 310 SAC Service, Promotion, Allowance,

or Charge Information

O 25 Not Used

* LOOP ID - LM * LOOP ID - LM 10

* 320 LM Code Source Information O 1 Not Used

330 LQ Industry Code M 100 Must use

* LOOP ID - LX * LOOP ID - LX >1 N2/340L N2/340L

* 340 LX Assigned Number O 1 N2/340 Not Used

* 350 REF Reference Identification O >1 Not Used

* 360 N1 Name O 1 Not Used

* 370 DTM Date/Time Reference O 10 Not Used

* LOOP ID - LM * LOOP ID - LM 10

* 380 LM Code Source Information O 1 Not Used

390 LQ Industry Code M 100 Must use

Summary:

Pos Id Segment Name Req Max Use Repeat Notes Usage

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

20 SE Transaction Set Trailer M 1 Must use

Notes: 

2/86 Use is limited to intra-organizational transactions.

2/340L The LX loop conveys serial number, lot number, and inventory data.

2/340 The LX loop conveys serial number, lot number, and inventory data.

3/10 The 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 quantities ordered (PO102) for each PO1 segment.
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 4 March 16, 2022

ST Transaction Set Header Pos: 10 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

870 Order Status Report

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) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 5 March 16, 2022

BSR Beginning Segment for Order Status

Report

Pos: 20 Max: 1

Heading - Mandatory

Loop: N/A Elements: 6

User Option (Usage): Must use

Purpose: To indicate the beginning of an Order Status Report Transaction Set

Semantics: 

1. BSR03 indicates a status report document number assigned by the sender.

2. BSR04 indicates the date of this report from the sender.

3. BSR07 indicates the time of this report from the sender.

4. BSR08 indicates a status report document number assigned by the inquirer.

5. BSR09 indicates the date this report was requested from the sender by the inquirer.

6. BSR10 indicates the time this report was requested from the sender by the inquirer.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BSR01 850 Status Report Code

Description: Code indicating the reason

for sending the report

M ID 1/2 Must use 1

Code Name

8 Response to Notice of Availability

BSR02 847 Order/Item Code

Description: Code identifying a group of

orders and items

M ID 1/2 Must use 1

Code Name

CO All Orders - Unshipped Items

DLMS Note:

Use to indicate that all orders remain open.

BSR03 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

DLMS Note: Use Code "Z" for this data

element to satisfy mandatory X12 syntax

requirements.

M AN 1/30 Must use 1

BSR04 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: This date is the date of the

transaction set preparation and

corresponds to the Universal Time

Coordinate (UTC).

M DT 8/8 Must use 1

BSR07 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 =

O TM 4/8 Must use 1
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870N1NA10 6 March 16, 2022

hundredths (00-99)

DLMS Note: 1. Express the originating

activity's time of transaction set preparation

in UTC.

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

format.

BSR11 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

O 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.
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 7 March 16, 2022

TD5 Carrier Details (Routing

Sequence/Transit Time)

Pos: 44 Max: 1

Heading - Optional

Loop: N/A Elements: 5

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 to identify the ship mode (air or surface) to the final destination, the port of embarkation and the port of debarkation. Authorized DLMS

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

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

TD502 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

O ID 1/2 Used 1

Code Name

7 Loading Dock

DLMS Note:

Use to identify the Port of Embarkation (DOD Code) associated with the ship mode (air or surface) to

final destination.

TD503 67 Identification Code

Description: Code identifying a party or

other code

O AN 2/80 Used 1

TD504 91 Transportation Method/Type Code

Description: Code specifying the method

or type of transportation for the shipment

DLMS Note: DLMS users see the

Transportation Method/Type Code

Conversion Guide for available codes. 

O ID 1/2 Used 1

TD507 309 Location Qualifier

Description: Code identifying type of

location

O ID 1/2 Used 1
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 8 March 16, 2022

Code Name

PB Port of Discharge

DLMS Note:

Use to identify the Port of Debarkation (DOD Code) associated with the ship mode (air or surface) to

final destination.

TD508 310 Location Identifier

Description: Code which identifies a

specific location

O AN 1/30 Used 1
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 9 March 16, 2022

N1 Name Pos: 50 Max: 1

Heading - Optional

Loop: N1 Elements: 5

User Option (Usage): Must use

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. Must use this N1 loop to identify the organization originating 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 code IF or

CY.

2. For conversion between MILS and DLMS

formats, the transaction originator will

always be identified by Qualifier CY using

the SC Customer Code.

3. Identification of the Freight Forwarder

(FF) or Country Representative (CR) are

identified as an Authorized DLMS

enhancement; see DLMS Introductory Note

3e. Refer to ADC 1098. Use of this

enhancement requires a second iteration of

the N1 loop (refer to ADC 309).

3. Identification of the Freight Forwarder

(FF) or Country Representative (CR) are

identified as an Authorized DLMS

enhancement; see DLMS Introductory Note

3e. Refer to ADC 1098. Use of this

enhancement requires a second iteration of

the N1 loop (refer to ADC 309).

M ID 2/3 Must use 1

Code Name

CY Country

DLMS Note:

1. Use to identify the SC Customer Code associated with the NOA reply.

2. Use to identify the CR originating the transaction set. Authorized DLMS enhancement; see DLMS

Introductory Note 3e. Refer to ADC 1098.

IF International Freight Forwarder

DLMS Note:

Use to identify the designated FF to receive the transaction set. Authorized DLMS enhancement; see

DLMS Introductory Note 3e. Refer to ADC 1098.

N102 93 Name

Description: Free-form name

DLMS Note: This is a DLMS enhancement

for identification of the FF or CR by clear

text where coded address is not available.

X AN 1/60 Used 1
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870N1NA10 10 March 16, 2022

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

38 Country Code

DLMS Note:

Use with N101 Qualifier CY to identify the Security Cooperation Customer Code applicable to the NOA

reply. (Must be consistent with the NOA and original requisition content).

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

This is a DLMS enhancement for use of the constructed MAPAC to identify the FF or CR. Requires

coordination prior to use.

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.

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Must use 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 the appropriate 1/N101/050 code to indicate that the organization cited in N104 is

originating the transaction set.
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 11 March 16, 2022

HL Hierarchical Level Pos: 10 Max: 1

Detail - Mandatory

Loop: HL Elements: 2

User Option (Usage): Must use

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

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

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

3. Use the second 2/HL/010 shipment loop iteration to identify shipment information associated with the transportation control 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

HL03 735 Hierarchical Level Code

Description: Code defining the

characteristic of a level in a hierarchical

structure

M ID 1/2 Must use 1

Code Name

S Shipment

DLMS Note:

Use to identify the individual shipment loops addressed in the FMS NOA reply.

V Address Information

DLMS Note:

Use address loop to identify the consignor (shipping activity initiating the NOA) and the ship-to when the

ship-to instructions are different than those provided originally.
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 12 March 16, 2022

DTM Date/Time Reference Pos: 80 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.

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

DLMS Note: Use to identify the originator's

date of transaction preparation and other

dates associated with the transaction.

M ID 3/3 Must use 1

Code Name

097 Transaction Creation

DLMS Note:

Use to indicate the date of transaction preparation.

108 Postmark

DLMS Note:

Use to identify the date release and shipping instructions were mailed. Use only when mailing separate

release and shipping instructions.

DTM02 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Must use 1
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 13 March 16, 2022

REF Reference Identification Pos: 87 Max: 1

Detail - Optional

Loop: REF Elements: 2

User Option (Usage): Must use

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.

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: For DLMS use, only the

following codes are authorized.

M ID 2/3 Must use 1

Code Name

FN Forwarder's/Agent's Reference Number

DLMS Note:

Use to identify the customer (CR/FF) assigned transportation order number used for internal control of

the shipment.

K1 Foreign Military Sales Notice Number

DLMS Note:

Must use only in 2/HL/010 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. Authorized

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

LO Load Planning Number

DLMS Note:

Use to identify the number of transactions included in the shipment.

TG Transportation Control Number (TCN)

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.

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
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 14 March 16, 2022

N1 Name Pos: 90 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Must use

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:

Must use this 2/N1/090 loop to identify the organization to receive 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: For DLMS use, only the

following codes are authorized.

M ID 2/3 Must use 1

Code Name

CI Consignor

DLMS Note:

Use to indicate the shipping activity (activity initiating the NOA).

ST Ship To

DLMS Note:

Use to identify the ship to clear text address with or without the MAPAC when the ship to address is

different than what is contained in the MAPAD as originally identified by the address codes in the

requisition.

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

10 Department of Defense Activity Address Code (DODAAC)

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

Use to identify Security Assistance structured address data for the Ship To. Interpretation of this data

may require additional codes cited elsewhere in the transaction. Authorized DLMS enhancement; see

DLMS Introductory Note 3e. 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 Must use 1

N106 98 Entity Identifier Code O ID 2/3 Used 1
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870N1NA10 15 March 16, 2022

Description: Code identifying an

organizational entity, a physical location,

property or an individual

Code Name

TO Message To

DLMS Note:

Must use with N101 code CI to indicate that the organization cited in N104 is receiving the transaction

set.
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 16 March 16, 2022

N2 Additional Name Information Pos: 100 Max: 2

Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): Used

Purpose: To specify additional names or those longer than 35 characters in length

DLMS Note:

Use with 2/N101/90 Code ST to identify in-the-clear exception ship-to name information if different than what is contained in the MAPAD as

originally identified by the address codes in the requisition. Authorized DLMS enhancement; see DLMS Introductory Note 3e. Refer to ADC

1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N201 93 Name

Description: Free-form name

M AN 1/60 Must use 1

N202 93 Name

Description: Free-form name

O AN 1/60 Used 1
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 17 March 16, 2022

N3 Address Information Pos: 110 Max: 2

Detail - Optional

Loop: N1 Elements: 2

User Option (Usage): Used

Purpose: To specify the location of the named party

DLMS Note:

Use with 2/N101/90 Code ST to identify in-the-clear exception ship-to address information if different than what is contained in the MAPAD

as originally identified by the address codes in the requisition. Authorized DLMS enhancement; see DLMS Introductory Note 3e. Refer to

ADC 1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N301 166 Address Information

Description: Address information

M AN 1/55 Must use 1

N302 166 Address Information

Description: Address information

O AN 1/55 Used 1
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 18 March 16, 2022

N4 Geographic Location Pos: 120 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

Purpose: To specify the geographic place of the named party

Syntax Rules: 

1. C0605 - If N406 is present, then N405 is required.

Comments: 

1. A combination of either N401 through N404, or N405 and N406 may be adequate to specify a location.

2. N402 is required only if city name (N401) is in the U.S. or Canada.

DLMS Note:

Use with 2/N101/90 Code ST to identify in-the-clear exception ship-to geographical location information if different than what is contained in

the MAPAD as originally identified by the address codes in the requisition. Authorized DLMS enhancement; see DLMS Introductory Note 3e.

 Refer to ADC 1098.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N401 19 City Name

Description: Free-form text for city name

O AN 2/30 Used 1

N402 156 State or Province Code

Description: Code (Standard

State/Province) as defined by appropriate

government agency

O ID 2/2 Used 1

N403 116 Postal Code

Description: Code defining international

postal zone code excluding punctuation

and blanks (zip code for United States)

O ID 3/15 Used 1

N404 26 Country Code

Description: Code identifying the country

DLMS Note: Use to identify the GENC

country code. See DLMS introductory note

4 (Refer to ADC 1075 for implementation).

O ID 2/3 Used 1
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 19 March 16, 2022

PER Administrative Communications

Contact

Pos: 140 Max: 3

Detail - Optional

Loop: N1 Elements: 6

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 ship to. Authorized DLMS enhancement; see DLMS

Introductory Note 3e. 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

O AN 1/60 Used 1

PER03 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

O 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

O AN 1/80 Used 1

PER05 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

O ID 2/2 Used 1

Code Name

EM Electronic Mail

DLMS Note:

Use to identify the e-mail address.

PER06 364 Communication Number

Description: Complete communications

number including country or area code

O AN 1/80 Used 1
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F870N1NA10 20 March 16, 2022

when applicable
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 21 March 16, 2022

LM Code Source Information Pos: 144 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:

Use this 2/LM/144 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) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 22 March 16, 2022

LQ Industry Code Pos: 145 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: For DLMS use, only the

following codes are authorized.

O ID 1/3 Must use 1

Code Name

0 Document Identification Code

79 Priority Designator Code

DLMS Note:

Recommend using in all requisitions

96 Shipment Release Code

DLMS Note:

Use to provide FMS NOA shipment release instructions.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data. 

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

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 3e. 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 3e. 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. This is a

Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without

action.
DLMS Implementation Convention (IC) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

Code Name

004010F870N1NA10 23 March 16, 2022

MCC Material Control Code

DLMS Note:

Use to identify the Material Control Code (MCC) for special inventory reporting. 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. 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) 870N Notice of Availability

Reply

ADC 309, 436, 448, 448B, 1043C, 1098, 1353, 1367, 1370 and 1412 DLM

4000.25

004010F870N1NA10 24 March 16, 2022

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