1

Approved DLMS Change 57B 

Revisions to RDD Edit 

1. ORIGINATOR:

a. Service/Agency: DLMS Supply Process Review Committee 

b. Sponsor: Ellen Hilert, DLMSO, SPRC Chair, ellen.hilert@dla.mil, 703-767-0676, 

DSN 427 

2. FUNCTIONAL AREA: Supply 

3. REFERENCES: 

 a. DLMSO memorandum, May 23, 2002, subject: ADC 57, Enhanced Edits for the 

Required Delivery Date (RDD) Data Field in Requisitions (Supply/MILSTRIP) (Staffed as PDC 

65) and Withdrawal of Approved MILSTRIP Change (AMC) 40, Processing Cooperative 

Logistics Supply Support Arrangement Requisitions (CLSSA) 

 b. DLMSO memorandum, September 27, 2002, subject: ADC 57A Addendum, Requisition 

Modifier Processing 

 c. Air Force Manual AFMAN 23-110, USAF SUPPLY MANUAL, VOL 1, PT 1, CHP 11, 

Section B; VOL 2, PT 2, CHP 9; VOL 2, PT 2, CHP 3, AMC Supplement (available at : 

http://www.e-publishing.af.mil/pubfiles/af/23/afman23-110/afman23-110.pdf

4. REQUESTED CHANGE:

a. Title: ADC 57B, Revisions to RDD Edit 

b. Description of Change: 

(1) This change provides a temporary exemption from the ADC 57 RDD edits for 

intra-USAF lateral support requisitions (retail account DoDAACs that begin with FB and RICs 

that start with D) to another retail account (again, DoDAAC that begins with FB and RIC that 

starts with D). The exemption is provided until migration to the DLMS. Under the DLMS the 

USAF will transmit unique codes currently included in the RDD field as discretely identified data 

elements. 

(2) In addition, this change expands the current Navy exemption for the 100-day 

restriction on RDDs to all Components requisitioning conventional ammunitions (FSC 1300). 

(3) This change formally documents the suspension of BK status provided to the Army 

as a result of ADC 57 Priority Designator (PD)/RDD edits. 

c. Procedures: 

 
2

(1) Revise MILSTRIP Chapter 3, Figure C3.1, Requisition Processing and Related 

Actions, as indicated in the enclosure. 

(2) Establish a new DLMS data element Forward Supply Location (FSL) Category 

Code (one-position, numeric). Reference AFMAN 23-110, V2, PT2, CHP 3. The FSL Category 

Code is used with the Urgency Justification Code (UJC) (ADC 76) to provide the FSL stock 

position. 

(3) DAAS will not convert the USAF internal non-date RDD entries identified in this 

change for the DLMS. All possible entries are not clearly defined in terms of the DLMS (see 

below for other examples). If conversion is desired in the future, the USAF will provide 

procedures by which DAAS may programmatically distinguish each entry (e.g., FSL CategoryUJC from F/AD-UJC). 

d. Alternatives: No acceptable alternative. 

5. REASON FOR CHANGE: 

a. During implementation analysis for ADC 57, it was not recognized that there were 

additional Component unique data content carried in the RDD field for lateral support internal to 

the USAF. Modification of the RDD edit will accommodate multiple USAF unique data 

combinations in the MILSTRIP RDD field which must be retained for legacy transactions. Under 

internal USAF guidance the RDD multi-purpose field may contain unique coding. An example 

would be identification of the Air Mobility Command Forward Supply Locations (FSL) to their 

corresponding Primary Supply Points. The PSPs support the FSL's requisitions for stock 

replenishment requirements. The PSPs use these codes to determine which FSLs should have 

their requisitions filled first. Also, the first position of the RDD may equal the Force Activity 

Designator (F/AD) (numeric); the second and third positions equal the Urgency Justification 

Code (UJC) (both positions are alpha/numeric). Other specific entries [NAR or X03] may also 

directed for entry in the RDD field. 

b. An exemption requirement to the 100 day restriction was originally identified only by 

the Navy for requisitions for Naval Ammunitions Logistics Center (NALC). It is now 

recognized that this edit is overly restrictive for current processing for FSC 1300 stock classed 

(conventional ammunition) requisition transactions for other Services as well. Both Army and 

AF depots prioritize their shipments using the RDD rather than priority because they receive so 

many requisitions from each of the other services with the same priority that the RDD is more 

important in determining which requisitions to work first so they can arrive at the requesting 

organization by the RDD. Even if the RDD is within the scope of the priority, there are so many 

that the RDD is the more critical element to prioritizing shipments to meet the customer's 

timeline. Under full DLMS functionality, there will be greater flexibility for identifying the 

required date (including specific entry of ‘delivery not before’ and ‘deliver not after’ 

combinations). 

c. The Army requested termination of the ADC 57 BK status shortly after implementation. 

The BK status triggered confusion and improper processing due to procedures under the Army 

single stock fund requisitioning. Data entries on the BK status no longer matched those on the 
3

original requisition. In addition, the BK status resulted in some unnecessary cancellations of 

requisitions for urgently required material. 

6. ADVANTAGES and DISADVANTAGES:

a. Advantages: Allows legacy system transactions to process and retain applicable 

Component unique data contents. 

b. Disadvantages: Adds complexity to the standard edit. 

7. IMPACT: Publication(s): DOD 4000.25-1-M, MILSTRIP; DOD 4000.25-M, DLMS, 

Component implementing instructions 

Enclosure 
 DoD 4000.25-1-M 

77

Priority Designator1 1. If Expedited Handling Signal 999 is present in the RDD field, 

requisition is for U.S. forces and the PD is not 01-03, enter PD 03 and 

furnish BK supply status. 

2. If an OSD/JCS project code is present in rp 57-59 and the PD is 

not 01-05, enter PD 03 and furnish BK supply status. 

3. If NMCS/ANMCS indicator (N/E) is present in rp 62 and PD is not 

01-15, enter PD 08 and furnish BK supply status.

4. If special mass cancellation coding 555 is present in rp 62-64 and 

PD is not 01-15, enter PD 08 and furnish BK supply status. 

5. If Expedited Transportation Signal 777 is in rp 62-64 and PD is not 

01-15, enter PD 08 and furnish BK supply status. 

6. If required availability period (A in rp 62) is present and PD not 01-

15, enter PD 15. 

7. If extended RDD (S or X in rp 62) is present and PD is other than 

09-15, enter PD 15, furnish BK supply status, and process. 

8. If work stoppage indicator (F or R in rp 62) is present and PD is not 

01-08, enter PD 15, furnish BK supply status, and process. 

9. For all other conditions, if PD is not 01-15, enter PD 15. 

Required Delivery Date23 1. If NMCS/ANMCS indicator (N/E in rp 62) is present and PD is 01-

08, process. If there is an N or E in rp 62 but PD 09-15 in rp 60-61, 

blank the entry in rp 62-64, furnish BK supply status and process 

using the priority. If there is an N or E in rp 62, blank any characters 

in rp 63-64 and furnish BK supply status. Exception: For Air Force 

requisitions, blank only numeric characters (01-99); do not blank 

special coding to fulfill an Air Force internal requirement for 

NMCS/MICAP justification. (Note: This eliminates short RDDs 

associated with NMCS/ANMCS and expressed as number of days 

from requisition date.) 

2. If Expedited handling Signal 999 is present in rp 62-64 and 

requisition is not intended for U.S. forces, blank the expedited 

handling signal, furnish BK supply status, and process using the 

 

1

 See Footnote 37. 

2

 Deferred implementation of PD/RDD compatibility edits and furnishing BK supply status under Approved DLMS 

Change 57 are authorized pending supply source system modernization. BK status resulting from ADC 57 not 

transmitted to US Army customers. 

3

 Non-date entries in the RDD field; such as, Codes E, F, N, R, 444, 555, 777, and 999, are referenced as Special 

Requirements Codes under the DLMS. 
 

DoD 4000.25-1-M 

78

priority.4 If requisition is intended for U.S. forces, process.

3. If special mass cancellation coding 555 is present in rp 62-64 

indicating continued processing during mass cancellation, process. 

4. If Expedited Transportation Signal 777 is in rp 62-64 and PD 01-08 

is in rp 60-61, process. If the PD is 09-15, blank the expedited 

transportation signal, furnish BK supply status, and process using the 

priority. 

5. If Co-Located Customer Handling Service Indicator 444 is present 

in rp 62-64, process. 

6. If RAD or extended RDD (rp 62 is A, S, or X) and rp 63-64 are not 

equal to 01-99, blank entry in 62-64, furnish BK supply status, and 

process. 

7. If work stoppage indicator (F or R in rp 62) is present and rp 63-64 

are not blank, blank entry in 63-64, furnish BK supply status, and 

process. (Note: This eliminates short RDDs associated with work 

stoppage and expressed as number of days from requisition date.) 

8. For subsistence, except for conditions [text deleted] above, all 

requisitions will contain a specific RDD in ordinal day of year format. 

If blank, compute an SDD.5

9. For all other conditions, blank RDD field if entry does not indicate a 

calendar date which falls no more than 100 days subsequent to the 

requisition date6 7, furnish BK supply status, and process.

Required Delivery Period 

(Conventional Ammunition Only)8

If rp 62 is B, C, D, G, H, J, K, L, M, P, T, U, V, or W, and rp 63-64 

contains 01-99, process. 

Figure C3.1. Requisition Processing and Related Actions.

 4

 See Footnote 39.

5

 Use of the RDD to fill subsistence items last reported as not implemented by DLA (Subsistence). Refer to AMCL 7. 

6

 The 100-day edit is not applicable to requisitions directed to Naval Ammunitions Logistics Center (NALC) for FSC 

1300 (conventional ammunition). 

7 Not applicable for Intra-USAF requisitions. 8

 Use of RDP for conventional ammunition last reported as not implemented by USAF. Refer to AMCL 148.