ADC 20A 

Revision of Status Code CX; 

Application of Status Code D7 for Modifier Rejects 

1. ORIGINATOR: 

 a. Service/Agency: DLA and Army 

b. Sponsor: Supply PRC Chair, Ellen Hilert, DLA DLMSO/J-673, 

DLMSO, 703-767-0676 (DSN 427), ellen_hilert@hq.dla.mil 

c. Functional Point of Contact: ASA(FM)

2. FUNCTIONAL AREA: Supply 

3. REFERENCE: DLMSO memorandum subject: ADC 20, Revision of 

Status Code CX and SK (MILSTRIP/Supply) (Staffed as PDC 11), dated 

February 28, 2000. 

4. REQUESTED CHANGE:

a. Description of Change: The original ADC 20 required a valid 

bill-to/credit-to address on requisition and related transactions, 

and rejected invalid entries with Status Code CX. Applicable DI 

Codes were listed as A0_, AM_, AT_, A3_, A4_, APR. This revision 

removes the applicability of the Status Code CX for the AM_, 

Requisition Modifier. The generic Status Code D7 for invalid data 

on an AM_ will be applied. (The actual edit is not revised; only 

the resulting status code.) 

b. Procedures: Revise MILSTRIP Figure C3.1. Requisition 

Processing and Related Actions, (page C3-39)as follows:

CODE OR DATA ELEMENT ENTRY IS BLANK OR INCORRECT 

Supplementary Address Reject (CX status) if blank or invalid and 

the signal code is B, J, K, L, or M. 

Fund No edit is required unless signal code is C 

or L. Reject (CX status) if signal code is 

C or L and fund code does not identify a 

valid bill-to activity as prescribed by 

MILSBILLS. 
No change is required to current MILSTRIP AP2.16, Status Codes which 

read as follows: 

CODE EXPLANATION 

 

CX Rejected. Unable to identify the bill-to and or shipto address as designated by the signal code or the 

signal code is invalid. If still required, submit a 

new requisition with valid data entries.

D7 Requisition modifier rejected because of errors in one 

or more data elements. 

5. REASON FOR CHANGE: 

 a. The general rule for MILSTRIP processing is to use the 

Status Code D7 to reject a modifier for invalid data content as 

follows: “C3.25.1.4.1. When the modifier transaction contains 

invalid entries for data elements listed in chapter C2, which would 

require rejection under requisition edits prescribed in paragraph 

C3.1.1., the modifier request will be rejected by means of D7 supply 

status (DI AE_). Note: This supply status transaction will contain 

the same data fields as on the unmodified requisition, except for 

the status code (rp 65-66) and transaction date (rp 62-64). This 

will allow the initiator of the DI AM_ to rebuild the requisition as 

it appears on the supply source records.” (Status Code B2 is used 

by the supply source to reject modifiers which cannot be honored for 

other reasons.) 

 b. When CX status is used to reject a DI Code AM_, Requisition 

Modifier, the recipient’s automated processing system may be 

triggered to cancel the original requisition and initiate 

resubmission under a new document number (as is required for DI Code 

A0_, Requisition, rejects). Due to timing and other factors, the 

requisitioner may be unable to establish a new obligation within the 

same fiscal year. The U.S. Army has reported significant losses of 

deobligated funds resulting from this unnecessary cancellation of 

modifiers. The appropriate process would be to correct the modifier 

and resubmit. Use of the D7 status would not trigger a cancellation 

action by the originator. 

6. ADVANTAGES/DISADVANTAGES: 

a. Advantages: Switching to the Status Code D7 will not impact 

other Components and will assist the Army in reducing lost funds. 

b. Disadvantages: The Status Code D7 is less informative 

concerning the cause of the error. 

7. Alternatives: 
 a. The Status Code CX could be retained for modifier rejection 

with a revised definition explaining that rejected modifiers may be 

corrected and resubmitted. This would be a deviation from standard 

procedures and, it is believed that this would have a programming 

impact on the Components to recognize two different processing paths 

for the same reject status code. 

 b. Under DLMS process re-engineering, multiple status codes 

could be used. The D7 would be retained to indicate that it was a 

modifier that was rejected, and one or more additional status codes 

would be used to indicate the specific error(s). 

8. IMPACT: 

 a. This change impacts the existing Army-unique DAAS fund code 

edit as applied to requisition modification transactions. As 

implemented, this additional edit may also result in a CX reject 

status. The edit will remain in place, but will be revised to use 

the D7 reject status code. Code D7 is considered to be the 

“standard” for invalid requisition modification transactions. This 

change does not impact any other requisition-related transaction 

types; CX status will be in effect for other DI Codes in both the 

DoD and Army context. 

b. Minor program changes at DAAS are required, no other known 

impact. The source of supply programming for ADC 20 Status Code CX 

reject is believed to be unimplemented at this time. However, if 

implemented as originally approved, this revision may be 

incorporated during modernization or as soon as feasible. 

c. The DoD DLMS Finance PRC will assess the requirement for a 

DOD a standard DoD edit on Fund Code and make a recommendation for 

appropriate action.