1 of 4

ADC 423

Attachment

ATTACHMENT TO ADC 423

Revise DLMS 527D to Allow Use of Supply Condition Code with Due-In (Procurement 

Instrument Source) and Specifically Logistics Reassignment Memorandum DueIn (MILSTRAP DDX) (Supply)

1. ORIGINATOR:

a. Service/Agency: Defense Logistic Agency (DLA)

b. Originator: DLA, Supply PRC Representative: HQ DLA/J-335; 703-767-1424; DSN 427

2. FUNCTIONAL AREA: Supply

3. REQUESTED CHANGE:

a. Title: Revise DLMS 527D to Allow Supply Condition Code with Logistics 

Reassignment Memorandum Due-In (Procurement Instrument Source) (MILSTRAP DDX) 

(Supply)

b. Description of Change: DLA’s Enterprise Business System (EBS) requires that a supply 

condition code (SCC) be included in a DDX/DFX Logistics Reassignment (LR) Memorandum 

Due-In transactions. DLA states that if an SCC is not included, the transactions will reject at EBS. 

MILSTRAP currently requires the SCC in record position (rp) 71 of DI Code DF_, due-in from 

nonprocurement instrument source. For DI Code DD_, rp 71 is a multiuse field. However, DLA 

indicates that Service legacy systems provided the SCC in DI Code DDX to SAMMS, and DLA 

believes this proposed change should not require a change to Service legacy systems, but rather 

supports an existing interface requirement; however, DLA also notes that “occasionally” Air Force 

and Navy do not send the SCC. [NOTE FOR THE SERVICES and GSA: As part of the PDC 

staffing Components were asked to determine if their systems include the SCC in rp 71 of DI Code 

DD_ in general , as well as specifically in DI Code DDX transactions sent to DLA, and advise DLA 

Logistics Management Standards of findings in response to the PDC. This information was 

requested to document if this is an existing interface currently in use by the Service legacy systems 

with DLA, and therefore, just a procedural update to MILSTRAP with no system impact; or is this a 

new requirement for Service system modernization efforts. A definitive answer was not provided 

by all Components. Responses to the PDC are at paragraph 7.]

c. Procedures: DLA stated that in DLA’s Standard Automated Materiel Management System 

(SAMMS), the SCC was required and was typically provided by the Services in DI Code DDX;

however, the SCC entry was not required by DoD 4000.25-2-M, MILSTRAP, AP 3.10, which 

identified DI Code DD_ rp 71 as a multiuse field to be left blank for inter-Component use. DLA 

requested that MILSTRAP AP3.10, rp 71, be modified accordingly, to document existing interface

for entry of SCC in DI Code DDX. (See note above.)
2 of 4

ADC 423 Att

(1) Revise DoD 4000.25-2-M, MILSTRAP, AP3.10, DI Code DD_, Due-In Procurement 

Instrument Source, as follows (change is identified by red, bold, italicized text) 

[NOTE: PDC288 stated that the MILSTRAP revision would either be to acknowledge rp 71 is 

used for SCC in either DD_ or DDX across the board, if Service/GSA response to PDC indicates

such; otherwise, it will be a footnote specific to the existing interfaces as shown below. 

Component responses to PDC 288 did not confirm that SCC was used across the board. In 

the absence of additional input from the Services and GSA stating that all use the SCC in 

DI Code DDX, the change is documented in MILSTRAP as used by agreement.]

DI Code DD_

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Multiuse 71-72 For intra-Component use, enter data prescribed 

by the Component. For inter-Component use, 

leave blank.4

4 For DI Code DDX, DLA enters the supply condition code in rp 71 on an inter-Component basis based 

upon trading partner agreement. All DOD Components must implement use of SCC with DLMS 527D 

due-in transaction corresponding to MILSTRAP DI Code DD_ functionality, in their modernized systems. 

MILSTRAP DI Code DD_ corresponds to DLMS 527D with beginning segment Transaction Type Code 

DA and use of CS segment for contract number or purchase request number. DLMS 527D for 

MILSTRAP DI Code DDX functionality includes LIN01 code T. Refer to ADC 423.

(2) Revise DLMS 527D, for memorandum due-in, as follows:

[NOTE: If Service/GSA research/responses to the PDC revealed that SCC was currently used for 

DD_ in legacy systems, no change to 527D would be required, and the table below would not have 

been included in the ADC. If Service responses SCC is not currently used with DD_ in legacy 

systems, the DLMS note would be revised as shown. If research revealed SCC was used with 

DDX, but not other DD_, then the note would be revised accordingly, with the enhancement 

applying to DD_ other than DDX. Responses to the PDC (at paragraph 7) did not provide 

conclusive guidance]

Item 

#

Location Revision to 527D Reason

1. DLMS 

Introductory

Note:

Added ADC 423 to DLMS Introductory note 6:

- ADC 423, Revise DLMS 527D to Allow Use 

of Supply Condition Code with Due-In 

(Procurement Instrument Source) and 

Specifically with Logistics Reassignment 

Memorandum Due-In (MILSTRAP DDX) 

(Supply) (Staffed as PDC 288)

To identify DLMS changes included in 

the DS.
3of 4

ADC 423 Att

Item 

#

Location Revision to 527D Reason

2. 2/LQ01/130 Revise DLMS note for qualifier 83:

83 Supply Condition Code

Use to identify the material condition of the 

quantity cited in 2/RCD/040. Must use in

nonprocurement source due-in, ARI/PMR, 

delinquent due-in inquiry, and delinquent duein advice transactions. Use of SCC in Due-in 

from procurement instrument source is 

recommended but optional until use of 

SCC is fully implemented by all 

Components. Components should ensure 

that inclusion of the SCC in Due-In from 

procurement transactions does not cause 

inappropriate rejection of the transaction. 

Refer to ADC 423.

To acknowledge that use of SCC with 

Due-In from Procurement Instrument 

source may not be fully implemented 

across all Components.

MILSTRAP DI Code DF_ (Due-In 

from Other Than Procurement 

Instrument Source) provides for entry 

of SCC in rp 71. 

MILSTRAP DI Code DD_ (Due-In

Procurement Instrument Source) does 

not specify entry of SCC, rather rp 71 is 

a multi-use field.

Navy and DLA use SCC in LR 

memorandum Due –in (DI Code DDX

and corresponding 527D). Army, Air

Force, and GSA did not state whether 

SCC was being used. Use of SCC should 

be implemented in due-in transactions 

from procurement source in modernized 

systems, if not already being used.

d. Alternatives: Not applicable. 

4. REASON FOR CHANGE: 

a. DLA indicates this change supports an existing inter-Component interface requirement; however,

MILSTRAP guidance for DI Code DDX indicates rp 71 is a multiuse field for intra-Component use. 

PDC 288 tasked the Services/GSA investigate their use of SCC in DI Code DD_, rp 71, and advise

if the SCC is used in all DD_, only in DDX, or not used. Component responses at paragraph 7 did 

not fully address this. Updates required to MILSTRAP and DLMS 527D notes depended upon 

Service/GSA responses. If the Services and GSA confirmed their use of the SCC in DI Code DD_, or 

DDX, rp 71 for, as a minimum, interface with DLA, the MILSTRAP Administrator would have

documented the use in MILSTRAP DDX, and the corresponding DLMS 527D, as an existing interface 

to ensure proper mapping in a mixed DLSS/DLMS environment. However the PDC responses at 

paragraph 7 did not clearly state this was an existing requirement, and the requirement must be 

optional until such time as all Components have implemented in their modernized systems.

b. The PDC requested Services and GSA review their LR process to determine whether or not the 

SCC is being provided in DI Code DDX, rp 71, and in DI Code DD_ in general. If SCC is provided in 

DDX, request verification include whether it is being provided to DLA only, or is also being provided 

in LRs involving the Services and/or GSA. The Components were to provide this information in 

response to the PDC. SPRC responses at paragraph 7 did not fully address the requirement.

c. If use of SCC is not part of existing Service or GSA LR process for 527D memorandum 

due-in transactions, this change must be implemented as part of modernization.
4 of 4

ADC 423 Att

5. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Including the condition code will enhance LR DDX processing. 

b. Disadvantages: None.

6. IMPACT:

a. Data Content/Procedures: As noted above for DI Code DDX and DLMS 527D.

b. Publication(s): DoD 4000.25-2-M (MILSTRAP), DLMS 527D, and DLA Transaction 

Services Maps.

c. Automated Information Systems (AIS). May impact Service and GSA AIS to ensure 

SCC is included in 527D Due-In transactions modernized systems, if it is determined use is 

not part of legacy systems. DOD Components must also ensure that that inclusion of the 

Supply Condition Code in a DLMS 527D Due-In (Procurement Instrument Source) 

transaction does not cause inappropriate rejection of the transaction

7. RESPONSE AND COMMENT TO PDC 288/Draft ADC 423:

ORGANIZATION RESPONSE

DLA Concur. No impact ICAN.

DDC, DLA MILSTRAP POC, and EBS concur. EBS has no impact.

Army Concurs

Navy Legacy applications expect a condition code in the 71 record position for DD_ 

transactions.

Air Force Response to PDC staffing note regarding current process for DD_/DDX rp 71: 

USAF passes SCC 'A' on all DD_/DDX transactions in rp 71 with the 

exception of PR data which would be blank.

Marine Corps Concur as written (draft ADC 423).

GSA ----------------------