ADC 304 

AFY Material Identification and Quantity Mapping to 

DLMS 869A, Requisition Inquiry/Supply Assistance Request 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

b. Originator: Ms. Ellen Hilert, Chair, Supply Process Review Committee, 703-767-0676; DSN: 

427-0676; e-mail: ellen.hilert@dla.mil

2. FUNCTIONAL AREA: Primary: Supply

3. REQUESTED CHANGE: Revise DAAS map document for the material identification and 

quantity within the implemented DLMS transaction 869A, Requisition Inquiry/Supply Assistance 

Request. 

a. Description of Change: 

(1) The DAAS map document incorrectly maps the material identification associated with the 

Requisition Follow-Up Request for Initial Transportation Shipping Activity (MILSTRIP AFY) to the 

REF segment instead of the LIN segment of the 869A, Requisition Inquiry. Although either the REF 

segment or the LIN can be used successfully for material identification, the mapping for the 869A 

equivalent of the MILSTRIP AF[123CT] already correctly maps to the LIN. In the actual DLMS 

Supplement 869A, the NSN carried in the REF (REF04 vice REF01, Qualifier FS)) is associated with 

a DLMS enhancement to identify the NSN of the end items associated with requisitioned non-standard 

substitute item. 

(2) The DAAS map document incorrectly identifies the quantity in the MILSTRIP AFY as the 

“Urgent Delivery Quantity” (Qualifier AB). However, the DLMS Supplement 869A identifies this 

quantity data element for use in supply assistance transactions to identify the quantity urgently 

required. The map should point to the quantity data element labeled “Discrete Quantity” (Qualifier 

01) which is used to indicate the quantity requisitioned or the quantity shipped when requesting 

shipment tracing. 

b. Background: The mapping problems were not previously identified and it is unlikely that the 

mapping error for material identification resulted in any programming disconnects. It is unknown if 

the quantity mapping resulted in misinterpretation by DLMS implementers. Once the problems were 

identified it was agreed that this change would be coordinated to alert others so that implemented 

transactions would be impacted by the correction of the map documents. 

c. Procedures: 

(1) Revise DAAS map document to remove the reference to NSN (Qualifier NS) and other 

material identification (Qualifier ZZ) in the REF01 and insert appropriate material identification 

mapping as already documented for the AF[123CT] in the 869A.
(2) Revise the DAAS map document and programming to use the correct quantity data 

element for the AFY which is identified by Qualifier 01.

(3) Revise the DLMS supplement to clearly identify these elements used for DLMS 

enhancements.

Item 

# 

Location DS 869A Requisition Inquiry/ 

Supply Assistance Request 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Added ADC 304

- ADC 304, AFY Material Identification and Quantity 

Mapping to DLMS 869A, Requisition Inquiry/Supply 

Assistance Request 

Identifies DLMS 

Changes included 

in the DLMS 

Supplement 

2. 2/REF/105 Add DLMS note at the segment level:

Federal Note: 

1. Use in all 2/HL/010 transaction loop iterations to identify the 

transaction number and suffix. 

2. Use in all 2/HL/010 substitute item loop iterations to identify 

and describe acceptable substitute items. 

DLMS Note: Substitute item identification is a DLMS 

enhancement; see introductory DLMS note 2a.

Clarification. 

3. 2/QTY01/80 Add DLMS note:

AB Urgent Delivery Quantity 

DLMS Note: 

1. Use in supply assistance transactions to identify the quantity 

urgently required. 

2. DLMS enhancement; see introductory DLMS note 2a.

Clarification. 

4. REASON FOR CHANGE: USTRANSCOM personnel supporting Global Transportation 

Network Pre-Planned Product Improvement (GTN P31) identified the material identification error in 

the DAAS map for the AFY format requiring correction of the map document. During subsequent 

review, DLMSO identified the quantity issue.

5. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Prevents misunderstanding and facilitates DLMS implementation.

b. Disadvantages: None identified

6. IMPACT: 

a. DAAS maps have been corrected as stated above. 

b. May impact implemented DLMS format for AFY. Components should verify internal 

mapping.