1

ADC 254 

DLMS Mapping for Army Material Release Order Shipment Status, DI Code B99, 

 and Administrative Updates for DLMS Mapping of the UII 

1. ORIGINATOR: 

 a. Service/Agency: Army Headquarters, United States Army Material Command 

 b. Originator: Army, Logistics Modernization Program (LMP), telephone 856-988-6158 

2. FUNCTIONAL AREA: Supply 

3. REQUESTED CHANGE: 

 a. Title: ADC 254, DLMS Mapping for Army Material Release Order Shipment Status, 

DI Code B99 and Administrative Updates for DLMS Mapping of the UII

 b. Description of Change: 

 (1) This change incorporates the inclusion of the Army-unique Document Identifier Code 

(DIC) B99 (Offline Material Release Order (MRO) Image) to the MILS to DLMS mappings 

maintained by Defense Automatic Addressing System Center (DAASC). All data elements, with 

the exception of the Document Identifier Code, are identical to the already mapped MILS A5 

transactions. The use and data elements of the DIC B99 are found in Table E-43 of 

Army Regulation 725-50 (Requisitioning, Receipt and Issue System). Normally, this transaction 

is systemically generated when the supply source requisition processing record reflects that an 

off-line exception data MRO has been sent to the storage site. The DIC B99 is a mirror image of 

the off-line MRO, less the exception data. 

(2) Document Identifier Code (DIC) B99 represents an image of an Army offline MRO. 

When the Lifecycle Management Command generates an MRO based on an offline exception 

data requisition from the customer, an offline exception data MRO is sent to the storage activity 

to issue the stock. A DIC B99 is generated to the Army Material Command Logistics Support 

Activity (LOGSA) Logistics Information Warehouse (LIW) through DAASC to record an image 

of the MRO. LIW is the Army’s official data repository and authoritative source for all Army 

logistics and distribution management information, to include unique item tracking, asset 

visibility, supply status, and Total Cost of Ownership. 

c. Procedures: Revise DLMS Supplement 940R as follows: 

Item 

# 

Location Revision to 

940R, Warehouse Release Order 

Reason 

1. DLMS 

Introductory 

Note: 

Add ADC 254 to DLMS Introductory note 6.

- ADC 254, DLMS Mapping for Army Material 

Release Order Shipment Status, DI Code B99 and 

Administrative Updates for DLMS Mapping of the UII

To identify DLMS 

changes included in the 

DS 
2

2. 1/W0507/0200 Added qualifier “FI” with the following DLMS Note:

FI File 

DLMS Note: Authorized to be used on an Intra-Army 

basis with W0506 Transaction Type Code NA to 

identify an Offline Material Release Order (MRO) 

Image. DIC B99 will be at LQ02 in association with 

LQ01 qualifier 0, Document Identification Code. 

To support Army DLMS 

migration effort 

Item # Location Administrative updates: 

940R, Warehouse Release Order 

Reason 

Admin 

change 1 

2/N901/1500 Revise DLMS Note for Qualifier BT as shown:

BT Batch Number 

DLMS Note: 

Use to identify the manufacturer's batch/lot number 

or other number identifying the production run. The 

batch/lot number may not exceed 20 characters in 

accordance with IUID policy. 

Administrative change: 

To document maximum 20 

position length for batch/lot 

IAW UID policy. UID PMO 

authorizes 20 position 

maximum batch/lot size.

Admin 

change 2 

2/N901/1500 Revise DLMS Note for Qualifier SE as shown:

SE Serial Number 

DLMS Note: 

Use to identify the serial number. The serial 

number may not exceed 30 characters in 

accordance with IUID policy.

Administrative change: 

To document maximum 30 

position length for Serial 

Number IAW UID policy. 

UID PMO authorizes 30 

position maximum serial 

size.

Admin 

change 3

2/N901/1500 Revise DLMS Note for Qualifier U3 as shown :

U3 Unique Supplier Identification Number (USIN) 

DLMS Note: 

1. Use to identify the UII. Place UII value in N902. 

If UII is longer than 50 positions, place remainder 

of UII in N903. The UII may not exceed 50 

characters in accordance with IUID policy. A data 

maintenance action was approved in version 5020. 

The approved code/name is "UII - Department of 

Defense Unique Item Identifier”. 

Administrative update:

Provides current IUID 

policy and revises mapping 

of the Unique Item 

Identifier (UII). The UII 

data element was previously 

split across two data fields 

to accommodate the original 

78 character format. 

Current IUID policy limits 

the UII to a 50 character 

format, so the “split” is no 

longer needed. 

Admin 

change 4

2/N902/1500 Delete DLMS Note:

DLMS Note: For use with REF01 codes BT and 

SE. When N901 = U3, enter the UII value. If the 

UII value is greater than 50 positions the value 

must be split between N902 and N903.

Administrative update:

See above. No note is 

needed since all data 

elements now map to N902.
3

Admin 

change 5

2/N903/1500 Delete DLMS Note and mark N903 as “not used.”

Use when N901 = U3 and UII value must be split 

between N902 and N903.

Administrative update:

See above. Because this data 

field is no longer needed, it 

is marked as “not used.”

 d. Alternatives: The NTE segment of the 511R and 940R have the capability to carry 

exception data. The NTE segment conveys exception pick, pack and delivery instructions. 

Exception ship-to/in-the-clear addressing capability is documented in the N1-4 segments. The 

Distribution Standard System is currently capable of receiving and processing the 940R with 

exception data. These DLMS enhancements eliminate the need for off-line exception data 

requisitions and MROs. Army will pursue these capabilities in future releases of their 

modernization effort. Based on their current release timeline, no alternative to the current 

proposal is known. 

4. REASON FOR CHANGE: 

 a. Documents and incorporates Army’s existing MILSTRIP data requirements in DLMS. 

The data provides value-added information for Army. 

b. The administrative revisions are provided to match current Item Unique Identification 

(IUID) policy. The notes contain clarification of future mapping of the UII to the DLMS format 

pending coordination of business rules and implementation of functionality for directed release 

of items with unique identification. 

5. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Supports Army implementation of DLMS migration effort to accurately 

capture and process Army offline requisitions. 

 b. Disadvantages: None identified. 

6. IMPACT: Modify DOD 4000.25-M, DLMS Supplement 940R and DAASC conversion 

maps to include Army DI Code B99. 
4

ENCLOSURE 1 TO PDC 267 

Army Format for DIC B99 

Table E–43 

DIC B99, Duplicate Materiel Release Order(MRO) Shipment Status 

Field legend Record pos. Entry and instructions. 

Document identifier 

code 1–3 Enter DIC B99. 

Routing identifier code 

(to) 4–6 Enter RIC. 

Media and status code 7 Perpetuate from original requisition. 

Stock number 8–22 Stock or part number of item to be released. 

Unit of issue 23–24 Enter. 

Quantity 25–29 Enter. 

Document number 30–43 Perpetuate from original requisition. 

Suffix code 44 Enter the applicable suffix code when the quantities are to be split; 

otherwise, leave blank. 

Supplementary 

address 

45–50 Perpetuate from original requisition. 

Signal code 51 Perpetuate from original requisition. 

Fund code 52–53 Perpetuate from original requisition. 

Distribution code 54–56 Perpetuate from original requisition. 

Project code 57–59 Perpetuate from original requisition. 

Priority 60–61 Perpetuate from original requisition. 

Required delivery date 62–64 Perpetuate from original requisition. 

Advice code 65–66 Perpetuate from original requisition. 

Routing identifier code 

(from) 

67–69 Enter RIC. 

Management data 70–72 Enter the O/P code, condition code, and management code, if applicable. 

Blank 73 Leave blank. 

Unit price 74–80 Enter appropriate unit price when shipment is to be made outside of 

CONUS.