ADC 326 

DS 869A, Requisition Inquiry/Supply Assistance Request, Correction and 

Clarification of Data Mapping, Administrative Updates, and 

 Coordination of Procedures for Transaction-Based Supply Assistances Requests 

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: Purpose is clarification of intent for mapping purposes and to assign 

correct beginning segment value for the AFY. 

a. Description of Change: Update DS 869A as shown in the table below; update DAAS 

mapping as shown in the map table below; and coordinate DLMS procedures for the use of the 869A 

for Supply Assistance Request as shown in enclosure 1. Staffing Note: This change requires 

Components review mapping and clarification updates identified to ensure interoperability of the 869A 

for existing MILSTRIP-based functionality. This change also requires a Component response 

regarding DLMS enhancement for future use of the transaction-based supply assistance request. 

Provide concurrence/comments on the desire to implement the enhanced process and a rough 

estimated of target implementation date. Include review of the DLMS enhancement data element 

“Mission Impact Statement Code” established to codify current message text.

 b. Background: 

(1) During review of the DS 869A and mapping for MILSTRIP data content associated in 

support of USAF implementation planning, several problems were noted to include: 

(a) Missing “DLMS enhancement notes” to clearly label non-MILSTRIP 

transactional data elements as DLMS enhancements requiring coordination prior to use. 

(b) Missing DLMS notes to cross-reference MILSTRIP transactions for clear 

identification of the purpose and use of the DLMS data elements. 

(c) A DAAS map error resulting in miss-identification of the correct beginning 

segment code for the MILSTRIP AFY. 

(d) Confusing mapping for the beginning segment codes identifies applicability to 

unshipped or shipped items. 

(e) Incorrect mapping for the MILSTRIP AFC quantity which results in the same 

“urgently needed quantity” field being applied for both supply assistance requests and requests for 

improved estimated shipping date (ESD). 
(2) Procedures for use of the DLMS enhancement for the supply assistance request were 

never fully coordinated and there are no known plans to implement as a DLMS transaction within 

ERP/modernization. This update to the DS provides an opportunity for the Components to establish a 

plan for future use of this DLMS capability and ensure that Component unique/non-DLMS versions of 

the supply assistance request are not promulgated. A DLA unique DoD EMALL web-input automated 

supply assistance request message was implemented without prior coordination under DLMS. 

 c. Procedures: Revise the 869A DLMS supplement as follows:

# Location DS 869A Requisition Inquiry/ 

Supply Assistance Request 

Revision 

Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 326 DLMS Introductory Note 3:

- ADC 326, DLMS Supplement (DS) 869A, Requisition 

Inquiry/Supply Assistance Request, Correction and Clarification 

of Data Mapping, Administrative Updates, and Coordination of 

Procedures for Transaction-Based Supply Assistances Requests 

Identifies DLMS 

Changes included in 

the DLMS Supplement

2. 1/BSI03/20 Revise DLMS notes for the following codes:

PI Selected Orders - Shipped Orders 

DLMS Note: 

1. Use to indicate that the transaction set contains transactions that 

apply to requisitions for which shipment status has been received. 

2. Use for requests for shipment tracing. 

3. Used during DLSS/DLMS transition period when transaction 

contains a request for identification of the initial transportation 

shipping activity.

PO Selected Orders - Unshipped Items 

DLMS Note: 

1. Use to indicate that the transaction set contains transactions that 

apply to open requisitions for which shipment status has not been 

received. 

2. Use for requisition follow-ups including requests for improved 

ESD. 

3. Use for supply assistance requests. DLMS enhancement; see 

introductory DLMS note 2a. 

2. May be used during DLSS/DLMS transition period when 

transaction contains a request for identification of the initial 

transportation shipping activity.

Clarification of 

purpose and use for 

beginning segment 

codes. 

Provides more logical 

mapping to existing 

codes to meet X12 

syntax requirements 

by switching the 

follow-up for shipping 

depot DoDAAC 

(MILSTRIP AFY) to 

the PI-Shipped Orders 

category. 

Staffing note: This 

may require a change 

to Component DLMS 

mapping/planned 

migration for AFY. 

3. 1/BSI08/20 Revise DLMS notes for the following codes:

71 Filing and Search Request 

DLMS Note: Use (in conjunction with BSI03=PI, Shipped Orders) 

to identify requests for shipment tracing - registered, insured, and 

certified U.S. Postal Service. (This corresponds to MILSTRIP 

Clarification of 

purpose and use for 

the beginning segment 

codes. 

Re-instates common 
# Location DS 869A Requisition Inquiry/ 

Supply Assistance Request 

Revision 

Reason 

Document Identifier AFT.)

AF Requisition Follow-Up 

DLMS Note: 

1. Use (in conjunction with BSI03=PO, Unshipped Orders) to 

identify status inquiries requisition follow-ups for status on 

previously submitted requisitions. (This corresponds to MILSTRIP 

Document Identifier AF1-AF5.) 

2. Use (in conjunction with BSI03=PO, Unshipped Orders to 

identify the requisition follow-up requests for improved estimated 

shipping date (ESD). (This corresponds to MILSTRIP Document 

Identifier AFC). When provided for this purpose, must be used in 

combination with PID05, Code 2. 

 

3. Use (in conjunction with BSI03=PI, Shipped Orders) to identify 

requisition follow-up requests for DoDAAC of initial 

transportation shipping activity (This corresponds to MILSTRIP 

Document Identifier AFY). When provided for this purpose, must 

be used in combination with PID05, Code 1. The Request for 

DoDAAC of Initial Transportation Shipping Activity transaction is 

applicable in a mixed DLMS/MILS environment where a separate 

transaction is needed to provide the requested information. Under 

DLMS, the distribution depot identifies the shipping activity in the 

shipment status transaction, eliminating the need for a follow-up. 

AR Supply Assistance 

DLMS Note: 

1. Use (in conjunction with BSI03=PO), Unshipped Orders) to 

identify requests for supply assistance (improved support) for 

requisitions meeting specific criteria for priority (Priority 

Designator 01-08) and receipt of open supply status. (This 

establishes a transaction-based process comparable to the 

MILSTRIP procedures for Supply Assistance Request currently 

prepared as a message, e-mail, or telephonic request. There is no 

comparable MILSTRIP transaction.) 

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

terminology and 

provides more 

complete information. 

Clarifies how to 

distinguish a follow-up 

for improved ESD. 

Clarifies how to 

distinguish a follow-up 

of shipping depot 

DoDAAC. Clarifies 

use of this follow-up 

during transition to 

DLMS. 

Staffing Note: This 

change requires 

correction of the 

DAAS map to use the 

AF beginning segment 

code (vice IN) 

Clarification of 

purpose and use for 

supply assistance 

request. Clarification 

of status as a DLMS 

enhancement based 

upon a MILSTRIP 

process. 

Staffing Note: Use of 

this DLMS transaction 

should be evaluated 

for modernization. 

Component response 

required. 
# Location DS 869A Requisition Inquiry/ 

Supply Assistance Request 

Revision 

Reason 

4. 2/HL03/10 Add DLMS notes for the following codes:

V Address Information 

Federal Note: 

Use in every 2/HL/010 address loop iteration. 

DLMS Note: 

Use to identify the organization originating and the organization 

to receive the transaction set. 

W Transaction Reference Number 

Federal Note: 

Use in every 2/HL/010 transaction loop iteration. 

DLMS Note: 

Use to identify the original requisition and associated data content. 

SB Substitute 

Federal Note: 

1. Use in every 2/HL/010 substitute item loop iteration for supply 

assistance transactions only. 

DLMS Note: 

DLMS enhancement; see introductory DLMS note 2a. 

Clarification of usage. 

Clarifies which 

addresses are provided 

in the V, Address, 

loop. 

Identifies Substitute 

loop as a DLMS 

enhancement. 

5. 2/LIN04/50 Revise DLMS note at the data element level as follows:

Product/Service ID Qualifier 

DLMS Note: 

1. Use codes EM for weapon system application, F8 for next 

higher assembly, and W1 for the end item serial number, as 

needed, on a supply assistance request to indicate amplifying 

information associated with the requisitioned material. DLMS 

enhancement; see introductory DLMS note 2a. 

Clarification 
# Location DS 869A Requisition Inquiry/ 

Supply Assistance Request 

Revision 

Reason 

6. 2/QTY01/80 Revise DLMS notes for the following codes:

01 Discrete Quantity 

Federal Note: 

Use to indicate the quantity requisitioned. Use to indicate the 

quantity shipped when requesting shipment tracing. 

DLMS Note: 

1. Use in requisition inquiry follow-ups, including requests for 

improved estimated delivery date, to indicate the quantity 

requisitioned. 

2. Use in request for shipment tracing to indicate the quantity 

released to carrier. 

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

AB Urgent Delivery Quantity 

DLMS Note: 

1. Use only in supply assistance request transactions to identify the 

quantity urgently required. 

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

Clarification of use in 

AFC and supply 

assistance request. 

Staffing note: This 

clarification is 

provided for correction 

of DAAS maps and 

consistent 

implementation by 

Components. 

7. 2/N1/110 Add DLMS note at segment level:

DLMS Note: 

The substitute item loop is a DLMS enhancement for the supply 

assistance request transaction; see introductory DLMS note 2a. 

Clarification; 

identifies DLMS 

enhancement. 

8. 2/N106/110 Revise DLMS Note:

FR Message From 

Federal Note: 

Must use with the appropriate 2/N101/110 code to indicate the 

organization cited in N104 is originating the transaction set. 

DLMS Note: 

1. For DLMS requests for shipment tracing resulting from 

conversion of the original DLSS DI Code AFT, the originating 

activity will be identified as DAASC. 

2. For DLMS follow-up requests for the DoDAAC of the initial 

transportation shipping activity resulting from conversion of the 

original DLSS DI Code AFY, the originating activity will be 

identified as the requisitioner due to lack of a from address in the 

MILS format. 

Clarification; 

correction of typo in 

Supplement. 

9. 2/PER/160 Add DLMS note at segment level:

DLMS Note: DLMS enhancement; see introductory DLMS note 

2a.

Identifies DLMS 

enhancement. 
# Location DS 869A Requisition Inquiry/ 

Supply Assistance Request 

Revision 

Reason 

10. 2/LQ01/180 Revise DLMS notes at the data element level as follows:

LQ01 1270 Code List Qualifier Code 

Federal Note: Use any code. 

DLMS Note: 1. Use code JN only in

2/HL/010 address loops. Use all other only in 2/HL/010 transaction 

loops. 

2. For DLMS use, only the following codes are authorized. 

JN Mission Impact Statement Code 

DLMS Note: 

Use in 2/HL/010 address loops to identify the code value which best 

defines mission degradation created by the absence of the required 

material. 

Corrects error in 

DLMS Supplement 

and changes mapping. 

Because JN represents 

is associated with an 

unimplemented DLMS 

enhancement this 

change has no map 

impact. 

4. REASON FOR CHANGE: Provided clarification and will prevent future problems with 

interpretation of the intended mapping of specific data fields. Corrects a mapping error for the 

urgently needed quantity in requests for improved ESD. Only the supply assistance request is defined 

functionally as urgently needed quantity. Urgently needed quantity may be a portion of the originally 

requisitioned quantity; the request for improved ESD must contain the quantity as requisitioned.

5. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Prevents misunderstanding and facilitates DLMS implementation. Corrects 

DAAS mapping for MILSTRIP AFC quantity to be consistent with original DLMS intent and 

functional requirements. 

b. Disadvantages: May require design/program updates.

6. IMPACT: 

a. DAAS maps to be corrected as illustrated: 

869A INQUIRY 

(AF[123CT]) 

Field Name 

Record Position 

(DLSS) Conditions DLMS Data Element Table Updated 

Transaction Set 

Identifier Code 

None None ST01=869 1 

Transaction Set 

Control Number 

None None ST02= Serial Number 1 
Beginning 

Segment 

None 

Translator Date 

If RP1-3≠AFT 

IfRP1-3=AFT 

Translator Time 

If RP1=A 

If RP1=U 

If RP1-2=AF and 

RP3≠T or AK or AT

If RP1-3=AFT 

BSI01=Z 

BSI02=()CCYYMMDD 

BSI03=PO 

BSI03=PI 

BSI06=()HHMM 

BSI07=00 

BSI07=77 

BSI08=AF 

BSI08=71 

1 4/5/05 

 

Urgent Quantity None If RP1-3=AFC QTY01=AB 2 9/11/01 

Quantity None If RP1-3AFC QTY01=01 2 11/9/04 

Quantity 25-29 If RP1-2=AF and If 

RP29=M Convert to 

Millions 

QTY01=01 

QTY02=RP 25-29 

2 11/9/04 

Staffing Note: All AF_, 

including AFC, are now 

mapped to “01” – AB will 

be exclusively used for the 

planned enhancement for 

supply assistance requests 

Required Delivery 62-64 If RP62=0, 1, 2, or 3 

DDD2CCDAT 

RP62-64

DTM01=996

DTM02=()CCYYMMD

D

2 8/10/06

Staffing Note: Required 

Delivery Date is not 

carried in the 869A. 

Ordered By 30-35 If RP1-3=AFT N101=OB 

N103=10 

N104=RP 30-35 

N106=FR 

2 OR DAASC?? 

869A FOLLOW UP 

(AFY) 

Field Name 

Record Position 

(DLSS) Conditions DLMS Data Element Table Updated 

Transaction Set 

Identifier Code 

None None ST01=869 1 

Transaction Set 

Control Number 

None None ST02= Serial Number 1 

Beginning 

Segment 

None 

Computer Assigned 

Computer Assigned 

If RP1=A 

If RP1=U 

BSI01=Z 

BSI02=()CCYYMMD

D 

BSI03=PO PI

BSI06=()HHMM 

BSI07=00 

BSI07=77 

BSI08=IN AF

1 3/18/03 

b. May impact implemented DLMS 869A procedures. DLA has confirmed that their DLMS 
portal will need to be updated per above mapping. 

c. May impact Global Transportation Network Pre-Planned Product Improvement (GTN P31) 

mapping. 
1

Enclosure 1, DLMS Manual, DoD 4000.25-M Volume 2 

Update the DLMS manual as identified (bold italics): 

C4.6.3 Request for Supply Assistance 

 C4.6.3.1. Initiation. Requisitioners may initiate requests for supply assistance only for PD 

01-08 requisitions after receipt of supply status indicating an unacceptable delivery date. Requests for 

supply assistance includes status of requisitions, timely supply of requirements, I&S items, release of 

cancellation or backordered requisitions, and diversion of material shipments. Do not generate 

requests for supply assistance prior to the receipt of supply status indicating open status. 

 C4.6.3.2. Submission. 

 C4.6.3.2.1 Forward requests for supply assistance on previously submitted PD 01-

08 requisitions to the supply source processing the requirement. In addition to the DS cited in 

paragraph C4.6.1, above, Requests for assistance may be done by electronic mail (computer-DISN), 

message, letter, or telephone to the appropriate supply source. Telephone requests should not exceed 

seven lines; however, the limitation of items shall be determined by the supply source ability to record 

the items and initiate timely responses. Include the urgently needed quantity (supply assistance may 

be requested for entire quantity requisitioned or a lesser quantity required for mission 

performance).

 C4.6.3.2.2 DLA accepts supply assistance requests via the DoD EMALL 

requisition query function for open requisitions PD 01-08 with MILSTRIP Supply Status BB, BV, 

BZ, or BD. 

 C4.6.3.2.3 In addition to the above, the DLMS 869A, Supply Assistance Request 

(BSI08=AR) is designed to transmit requests electronically. This is a DLMS enhancement which 

cannot be used without prior coordination to ensure that the receiving supply source has 

implemented this business process using transaction exchange.1

 The DLMS format supports 

identification of point of contact information; identification of acceptable substitute items; 

alternative sources for the requested item; and a codified mission impact resulting from delay or 

lack of support for the required item: 

 C4.6.3.2.3.1 Code 1: Inability to perform assigned mission for a classified 

project 

 C4.6.3.2.3.2 Code 2: Inability to perform assigned mission. 

 C4.6.3.2.3.3 Code 3: Performance of assigned mission anticipated to be 

curtailed or stopped if materiel is not received within 15 days continental United States (CONUS) or 

20 days other than continental United States (OCONUS). 

 C4.6.3.2.3.4 Code 4: Mission performance below prescribed level of 

 

1

 Coordinated under PDC 349. DoD Components must identify implementation/planned implementation dates to DLMSO 

for publication. 
effectiveness and efficiency. 

 C4.6.3.2.3.5 Code 5: A classified NMCS condition exists due to lack of 

required assets. 

 C4.6.3.3. Replies. Replies to supply assistance requests will include an information copy to 

each addressee included in the incoming request.