DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

December 20, 2013 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Approved Defense Logistics Management Standards (DLMS) Change (ADC) 1097, 

Administrative Realignment of Contractor Access to Government Sources of 

Supply Procedures in DLM 4000.25, Volume 2 and DLM 4000.25-1 (Supply) 

The attached administrative change to Defense Logistics Manual (DLM) 4000.25, Defense 

Logistics Management System and DLM 4.000.25-1, Military Standard Requisitioning and Issue 

Procedures (MILSTRIP) is approved for publication. This change realigns the Contractor Access 

to Government Sources of Supply procedures in the DLM 4000.25 and DLM 4000.25-1 . This 

change will be published in Formal Change 4 for these two manuals. 

Addressees may direct questions to Ms. Ellen Hilert, DOD MILSTRIP Administrator, 703-

767-0676 or DSN 427-0676, e-mail: ellen.hilert@dla.mil, or Ms. Heidi Daverede, DOD 

MILSTRIP Alternate, 703-767-5111; DSN 427-5111 , e-mail: heidi.daverede@dla.mil. Others 

may contact their Component designated Supply PRC representative available at: 

www.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp. 

Attachment 

As stated 

cc: 

ODASD(SCI) 

PIPP.DQNAL Digit ally signed by 

PIPP.DONALD.C.1035761221 

DC 1 035761 DN:c=US, o =US . Government, 

• • ou= DoD, ou=PKI, ou= DLA, 

cn=PIPP.DONALD.C.1 03576 1221 221 Date:2013.12.20 10:36:11 -05'00' 

DONALD C. PIPP 

Director 

DLA Logistics Management 

Standards Office 
ADC 1097, Attachment

Page 1

ADC 1097

Administrative Realignment of Contractor Access to Government Sources of 

Supply Procedures in DLM 4000.25, Volume 2 and DLM 4000.25-1

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: DLA Logistics 

Management Standards Office, 703-767-5111 

2. FUNCTIONAL AREA: Supply

3. REFERENCES:

a. DLM 4000.25, Defense Logistics Management System (DLMS), Volumes 1 and 2

b. DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP)

c. Approved MILSTRIP Change Letter (AMCL) 1A, Control of Access to DoD Materiel 

Inventories Required by Defense Contractors, dated August 1, 1990.

4. REQUESTED CHANGE(S):

a. Brief Overview of Change: This change establishes a new chapter in DLM 4000.25,

DLMS, Volume 2 that consolidates procedures, both DLMS enhanced and legacy, associated 

with contractor access to government sources of supply into one location. This change 

administratively aligns the new DLMS chapter with its companion chapter in DLM 4000.25-1 

MILSTRIP Chapter 11.

b. Background:

(1) This is the first in a series of DLMS changes to update DLM 4000.25, 

Volume 2 requisitioning and issue procedures to align with the procedures in DLM 4000.25-1. 

Once all the DLM 4000.25-1 chapters are fully aligned into DLMS Volume 2, then DLM 

4000.25-1 will be cancelled. At that time, DLM 4000.25, Volume 2 will serve as the single 

guidance for requisitioning and issue procedures, business rules, data standards, and transaction 

formats.

(2) DLM 4000.25-1, Chapter 11 outlines procedures associated with Contractor 

Access to Government Sources of Supply using legacy MILSTRIP 80 record position formats. 

DLM 4000.25, Volume 2, Chapter 4 outlines DLMS enhanced procedures for Requisitioning and 

Status Reporting, to include Contractor Access to Government Sources of Supply using DLMS 

formats (X12 Electronic Data Interchange and eXtensible Markup Language).

c. Describe Requested Change in Detail: Update DLM 4000.25 and DLM 4000.25-1 

so that requisitioning and issue procedures for Contractor Access to Government Sources of

Supply are aligned between the two manuals.
ADC 1097, Attachment

Page 2

Staffing Note: Request Army review MILSTRIP paragraph C11.7.5 entitled “DAAS Special 

Processing for Army” to validate the continued need for this temporary workaround. AMCL 1A 

(Reference 3.c.) required Component AIS’ to implement procedures to control access to DOD 

materiel inventories by defense contractors. We were advised that this was not yet implemented 

by Army (Retail). If these procedures are now fully implemented in Army systems, request 

advise DLA Logistics Management Standards Office so that a DLMS change can be released to 

discontinue this special process at DLA Transaction Services. 

d. Revisions to DLM 4000.25 Manuals:

(1) Add new Chapter 26 to DLM 4000.25 DLMS, Volume 2 to consolidate 

Contractor Access to Government Sources of Supply-related procedures into a single chapter. 

See Enclosure 1.

(2) Update Chapter 4 of DLM 4000.25 Volume 2 to move Contractor Access to 

Government Sources of Supply procedures to new Chapter 26. See Enclosure 2.

(3) Update Chapter 11 of DLM 4000.25-1 MILSTRIP to align with new Chapter 

26 of DLM 4000.25 Volume 2. See Enclosure 3.

(4) Update Table of Contents of DLM 4000.25, Volume 2 to add Chapter 26

entitled “Contractor Access to Government Sources of Supply”, include major paragraph 

headings, and remove related entries for Chapter 4.

e. Transaction Flow: There are no changes to transaction flows as a result of this 

DLMS change.

f. Alternatives: Continue maintaining two separate manuals requiring the reader to 

review both the DLM 4000.25-1 MILSTRIP manual for the core procedures, as well as DLM 

4000.25 Volume 2 Chapter 4 for the DLMS enhanced procedures. This is not a viable 

alternative, as it is prone to errors in interpretation, cumbersome to extract contractor access to 

government sources of supply procedures from the current DLMS manual, and labor intensive to 

maintain two sets of manuals.

5. REASON FOR CHANGE: Consolidate contractor access to government sources of supply 

related procedures into a single location and align both the DLMS and MILSTRIP manuals so 

that eventually the MILSTRIP manual can be cancelled, with the DLMS manual serving as the 

single source for contractor access to government sources of supply procedures.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Single source for documenting contractor access to government sources 

of supply procedures.

b. Disadvantages: There are no disadvantages.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: This change does not 

require system changes.
ADC 1097, Attachment

Page 3

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: There is no cost/impact to systems.

9. IMPACT:

a. New and Changes to DLMS Data Elements: There are no new or changes to DLMS 

data elements required by this realignment.

b. Automated Information Systems (AIS)/DLA Transaction Services: No impact.

c. Non-DLA Logistics Management Standards Publications: Components should 

update their local procedures to ensure consistency with contractor access to government sources 

of supply procedures documented in DLM 4000.25 and DLM 4000.25-1. 
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 1

Enclosure 1

A. Add new Chapter 26 to DLM 4000.25 Volume 2.

C26. CHAPTER 26

CONTRACTOR ACCESS TO GOVERNMENT SOURCES 

OF SUPPLY

C26.1. GENERAL

C26.1.1. Purpose. This chapter prescribes policies and procedures for 

requisitioning government furnished materiel (GFM) by or for contractors from the DoD 

Supply System. These procedures establish guidelines for requisitioners, authorized 

contractors and Services/Agencies (S/As) to obtain GFM from DoD inventories to fulfill 

contract requirements.1

 These procedures also support the use of MILSTRIP

requisitioning by authorized contractors to obtain materiel from Government supply 

sources to be used as contractor-furnished materiel (CFM) under controls established 

by the authorizing Component and as specified in this chapter. Basic MILSTRIP 

requisitioning procedures are documented in DLM 4000.25, Volume 2, Chapter 4; those 

procedures are augmented by this chapter to identify additional requirements 

associated with GFM and CFM.

C26.1.2. Transactions. This chapter addresses the procedures and applicable 

transactions relevant to requisitioning GFM and CFM. See the DLA Logistics 

Management Standards Office Website for available formats: 

www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp. The corresponding 

MILSTRIP legacy 80 record position transaction functionality is also provided for ease of 

interpretation by DLMS users and to support those working in a legacy environment. In 

addition to the listed MILSTRIP legacy transactions, the DLMS formats may incorporate 

functionality to support Component-unique transactions as noted in the implementation 

convention.

C26.1.2.1. The Requisition Transaction is identified by the DLMS 511R by 

beginning segment (1/BR02/020 Code A0). This transaction provides the functionality 

of MILSTRIP legacy Document Identifier Codes (DIC) A01, A02, A04, A05, A0A, A0B, 

A0D, and A0E.

C26.1.2.2. The Passing Order Transaction is identified by the DLMS 511R by 

beginning segment (1/BR02/020 Code BM). This transaction provides the functionality 

of MILSTRIP legacy DIC A31, A32, A34, A35, A3A, A3B, A3D, and A3E.

 1 Procedures to control access to DoD materiel inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to Approved MILSTRIP Change Letter (AMCL) 1A.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 2

C26.1.2.3. The Referral Order Transaction is identified by the DLMS 511R by 

beginning segment (1/BR02/020 Code BN). This transaction provides the functionality 

of MILSTRIP legacy DIC A41, A42, A44, A45, A4A, A4B, A4D, and A4E.

C26.1.2.4. The Requisition Modification Transaction is identified by the 

DLMS 511M by beginning segment (1/BR02/020 Code AM). This transaction provides 

the functionality of MILSTRIP legacy DIC AM1, AM2, AM4, AM5, AMA, AMB, AMD, and 

AME.

C26.1.2.5. The Requisition Follow-Up Transaction is identified by the DLMS 

869F by beginning segment (1/BSI08/020 Code IN). This transaction provides the 

functionality of MILSTRIP legacy DIC AT1, AT2, AT4, AT5, ATA, ATB, ATD, and ATE.

C26.1.2.6. The Requisition Inquiry Request is identified by the DLMS 869A 

by beginning segment (1/BSI08/020 Code AF). This transaction provides the 

functionality of MILSTRIP legacy DIC AF1, AF2, AF3, AF4, AF5, AFC, AFY).

C26.1.2.7. The Requisition Supply Assistance Request is identified by the 

DLMS 869A by beginning segment (1/BSI08/020 Code AR). There is no equivalent 

MILSTRIP legacy DIC.

C26.1.2.8. The GFM Validation Request is identified by the DLMS 517G by 

beginning segment (1/BR02/20 Code GI). This transaction provides the functionality of 

MILSTRIP legacy DIC AX1.

C26.1.2.9. The GFM Validation Response is identified by the DLMS 517G by 

beginning segment (1/BR02/20 Code GA). This transaction provides the functionality of 

MILSTRIP legacy DIC AX2.

C26.1.2.10. The Supply Status Transaction is identified by the DLMS 870S 

by beginning segment (1/BSR01/020 Code 4). This transaction provides the 

functionality of MILSTRIP legacy DIC AE1, AE2, AE3, AE8, AE9, AEA, AEB, AED, and 

AEE. 

C26.1.2.11. The Requisition Cancellation Transactions is identified by the 

DLMS 869C by beginning segment (1/BSI08/020 Code AC). This transaction provides 

the functionality of MILSTRIP legacy DIC AC1, AC2, AC3, AC4, AC5.

C26.1.2.12. The Follow-Up on Requisition Cancellation Request 

Transactions is identified by the DLMS 869C by beginning segment (1/BSI08/020 Code 

AC). This transaction provides the functionality of MILSTRIP legacy DIC AK1, AK2, 

AK3, AK4, AK5.

C26.1.2.13. The Shipment Status Transaction is identified by the DLMS 

856S by beginning segment (1/BSN06/0200 Code AS). This transaction provides the 

functionality of MILSTRIP legacy DIC AS1, AS2, AS3, AS8, AU1, AU2, AU3, and AU8.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 3

C26.1.2.14. The Materiel Obligation Validation Request Transaction is 

identified by the DLMS 517M by beginning segment (1/BR02/20 Code AN). This 

transaction provides the functionality of MILSTRIP legacy DIC AN1, AN2, AN3, AN4, 

AN5, AN9, and ANZ.

C26.1.2.15. The Materiel Obligation Validation Response Transaction is 

identified by the DLMS 517M by beginning segment (1/BR02/20 Code AP). This 

transaction provides the functionality of MILSTRIP legacy DIC AP1, AP2, AP3, AP4, 

AP5, AP8, AP9, APR, and APX.

C26.1.3. Establishing a Management Control Activity. The S/As must assign a 

unique routing identifier code (RIC) and distribution code to each management control 

activity (MCA) validating GFM requisitions.

C26.1.4. Violations. Any attempt to circumvent GFM/CFM validation requirements 

is sufficient cause to refer the violation to the appropriate criminal investigating activity 

to determine possible fraud, waste, and abuse. The sponsoring Service/Agency must 

refer all violations to criminal investigators and the monitoring MCA based on reports of 

rejected transactions or violations discovered during the post validation process.

C26.2. APPLICABILITY

C26.2.1. These procedures apply to all contractors and all S/A activities 

requisitioning GFM or CFM from DoD sources of supply. 

C26.2.2. Ammunition production is excluded from GFM control.

C26.3. PREPARATION OF REQUISITIONS AND RELATED TRANSACTIONS FOR 

GOVERNMENT MATERIEL FURNISHED TO CONTRACTORS

C26.3.1. Requisition Initiation. Requisitions for GFM may be initiated by the 

responsible S/A or, subject to the terms of the contract, by contractors. Requisitions for 

GFM will be prepared and initially submitted by GFM requisitioners, both contractors 

and S/As, using MILSTRIP transaction formats to the S/A MCA designated for 

monitoring the contract. Transmission through the Defense Automatic Addressing 

System (DAAS) will be utilized to the extent practical.

C26.3.2. Identifying Requisitions for GFM Controls. Requisitions and associated 

transactions containing an S/A code designated for contractors, as specified in 

Appendix AP7.2 (Department of Defense activity address code (DoDAAC) in the 

document number or ship-to DoDAAC), will be processed under GFM controls and 

restrictions except when the signal and fund codes indicate that the issue will be for 

CFM with contractor reimbursement by other than an Army contractor. All Army 

contractor requisitions and associated transactions must be processed under GFM 

controls.

C26.3.3. Required Information. In addition to normal requisition data, GFM 

requisitions, including Referral and Passing Orders will contain the following:
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 4

C26.3.3.1. RlC of the MCA monitoring the contract, (2/N101/70 Code Z5) 

(MILSTRIP legacy rp 4-6).

C26.3.3.2. For contractor generated requisitions, contractor DoDAAC in first 

six positions of document number. Document number DoDAAC perpetuated to the 

ordered by activity (1/N101/70 Code OB) (MILSTRIP legacy rp 30-35).

C26.3.3.3. For S/A generated requisitions for GFM, contractor ship-to 

DoDAAC (2/N101/70 Code ST) which may also be perpetuated to the supplementary 

address (2/LQ01/140 Code A9) based upon signal code usage (MILSTRIP legacy rp 

45-50).

C26.3.3.4. When applicable, a signal code to indicate issue without 

reimbursement, (2/LQ01/140 Code DE) (MILSTRIP legacy rp 51).

C26.3.3.5. When applicable, a fund code to indicate issue without 

reimbursement, (2/FA201/286 Code B5) (MILSTRIP legacy rp 52-53).

C26.3.3.6. Contract Information. All GFM requisitions for or by contractors 

must identify the contract number and other appropriate contract data, as required. 

Components authorizing GFM may direct the inclusion of the manufacturing directive 

number (MDN) as supplemental to the authorizing contract number.2

C26.3.3.6.1. Identification of the contract number (2/GF03/70). In 

MILSTRIP legacy, the last eight positions of the procurement instrument identification 

number (PIIN) are mandatory in rp 73-80.3

C26.3.3.6.2. When applicable, the call/order number, (2/GF07/70) 

(MILSTRIP legacy rp 69-72).

C26.3.3.6.3. Identification of the contract line item number, (2/GF01/70 

Code C7). There is no MILSTRIP legacy equivalent for the contract line item number.

C26.3.3.6.4. At the option of the S/A, a manufacturing directive number 

(MDN), (2/GF01/70 Code W3) (MILSTRIP legacy rp 54-56).

C26.3.3.7. GFM non-national stock number (NSN) requisitions are identified 

by the applicable code qualifier at 2/LIN02/100. In MILSTRIP legacy, they must be 

identified with an E in rp 68; the call/order number, if appropriate, in rp 69-72; and the 

last eight positions of the PIIN in rp 73-80 (the MDN is optional).

 2 Refer to ADC 1014. Staggered implementation is authorized for the transition to the mandatory inclusion of the 

contract number (rather than MDN as an alternative to the contract number). 3 Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS compliant 

contract number (rather than the abbreviated contract number authorized under legacy MILSTRIP procedures).
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 5

C26.4. SUBMISSION OF GOVERNMENT FURNISHED MATERIEL REQUISITIONS 

AND RELATED TRANSACTIONS

C26.4.1. Frequency of submitting GFM requisitions is the prerogative of the 

requisitioner. GFM requisitions will be submitted, when necessary, to meet contract 

requirements.

C26.4.2. Initiating activities must submit all GFM requisitions (DLMS 

511R/MILSTRIP legacy DIC A0_) and associated GFM transactions, regardless of 

origin (such as contractor or S/A initiated) to the appropriate S/A MCA for validation.

C26.4.3. After validating the GFM requisitions, the MCA forwards validated 

requisitions to the inventory control point (ICP). The MCA may pass transactions 

internally when the MCA and ICP are collocated. The MCA will send the transactions 

via DAAS when the MCA and ICP are not collocated. In those instances where a 

Component is performing the procurement/contract writing for another Component that 

includes the authorization for a contractor to order or receive GFM (or Army CFM), the 

Component providing the procurement/contracting service and the Component 

requesting the contract will coordinate efforts to ensure that the requesting 

Component’s MCA has access to the necessary contract and applicable contract 

modification information to perform its management control and accountability functions 

over Government supply system materiel access.

C26.4.4. Modifier transactions are authorized for GFM requisitions only to modify 

the project code, priority designator (PD), advice code, and the required delivery date 

(RDD). Modifiers may not be used to change the ship-to/bill-to information. Modifiers 

are subject to GFM controls and validation procedures.

C26.5. MANAGEMENT CONTROL ACTIVITY PROCESSING OF GOVERNMENTFURNISHED MATERIEL REQUISITIONS AND RELATED TRANSACTIONS

C26.5.1. The MCA must receive and validate GFM, Passing Orders, Referral 

Orders, Requisition Follow-Ups (DIC AT_), and Requisition Modifiers, based on the 

criteria furnished by procurement/contracting offices and as indicated in Table C26.T1. 

The MCA will make changes, reject, or continue the processing action on the GFM 

transactions. The MCA may also receive Supply Status, Shipment Status, Materiel 

Obligation Validation transactions, Requisition Inquiry/Supply Assistance Requests 

(DICs AF_, Requisition Cancellations, and Follow-Ups on Requisition Cancellation 

Requests. All other DLMS transactions and legacy DICs received by the MCA must be 

rejected with Status Code CR.

C26.5.2. The MCA will maintain requisition history files to serve as an auditable 

record of GFM transactions. In addition, the MCA will generate reports as required by 

DoD 4140.1-R, “DoD Supply Chain Materiel Management Regulation”, May 23, 2003.

C26.5.3. Under emergency conditions, such as a potential contract work 

stoppage, the MCA may receive telephonic requisitions, with PDs 01-08, for GFM. 

When this occurs, the MCA may telephone the requisitions to the appropriate source of 
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 6

supply (SoS) and validate the requirements afterward. If the post validation process 

reveals that the requisitioner is not authorized GFM, the following actions must be 

taken:

C26.5.3.1. Submit cancellation requests to the appropriate SoS.

C26.5.3.2. Advise the appropriate criminal-investigating agency for

determination of fraud waste, and abuse.

C26.5.4. Upon completion of the validation process, the MCA will identify itself as 

the RIC-From organization in the transaction, make the following changes and forward 

the requisitions, or internal requisition transactions (optional only when the MCA and 

SoS are collocated in the same distribution system), cancellations, follow-ups, 

requisition modifiers, passing orders, or referral orders to the applicable SoS through 

DAAS:

C26.5.4.1. Insert the RIC-To of the SoS.

C26.5.4.2. Insert the distribution code of the MCA validating the transaction. 

C26.5.4.3. Perpetuate all applicable contract data. Under DLMS, the MCA 

must include the DFARS contract number. Where required by the Component, the 

MCA may also perpetuate the MDN consisting of the MCA’s distribution code and two 

other alpha/numeric characters as assigned.4

C26.5.4.4. For MILSTRIP legacy transactions, delete the data in rp 69-80.

C26.5.5. MCAs in receipt of GFM Validation Request transactions will validate the 

data contained therein. This validation process must be completed and a GFM 

Validation Response transaction created and forwarded to the applicable SoS within 15 

days of receipt of the GFM Validation Request transaction. The results of the validation 

will be documented in the GFM Validation Response as follows:

C26.5.5.1. If the requisition has been previously validated, cite Advice Code 

2M.

C26.5.5.2. If the requisition has not been previously validated and the 

call/order number/PIIN (or MDN, if required by the Component in addition to the 

call/order number/PIIN) is not present, cite Advice Code 2U.

C26.5.5.3. If the requisition has not been previously validated and the 

call/order number/PIIN is present, validate the data elements as indicated in Table 

C26.T1, and generate the GFM Validation Response as follows:

 4 Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS compliant 

contract number (rather than the abbreviated contract number authorized under legacy MILSTRIP procedures) 

and for the transition to the mandatory inclusion of the contract number (rather than MDN as an alternative to the 

contract number).
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 7

C26.5.5.3.1. If the validation process reveals that the contract is not 

valid, respond with Advice Code 2U.

C26.5.5.3.2. If the validation process reveals that the requested quantity 

exceeds the contract authorized quantity, respond with Advice Code 2R and indicate 

the quantity approved for issue.

C26.5.5.3.3. If the validation process reveals that the requested quantity 

exceeds the contract authorized quantity, respond with Advice Code 2Q and indicate 

the total quantity is disapproved for issue.

C26.5.5.3.4. If the validation process reveals that the requested item, or 

contractor is not authorized GFM under a valid contract, respond with Advice Code 2V.

C26.5.5.3.5. If the validation process reveals that the requested item is 

authorized, respond with Advice Code 2M.

C26.5.6. MCAs in receipt of Supply Status with Status Code BF from the SoS will 

review for establishment of a valid requisition. If a valid requisition exists, a Requisition 

Follow-Up (MILSTRIP legacy DIC AT_) transaction will be generated. If a valid 

requisition does not exist, a report will be generated for internal review. Subsequent 

receipt of a valid requisition will be processed under the procedures/validation process 

indicated in Table C26.T1.

Table C26.T1. MCA Validation Process for GFM Transactions

CODE OR DATA ELEMENT VALIDATION OF ENTRY

DLMS Transaction 

(MILSTRIP Legacy DIC)

If DLMS 511R Requisition, Referral or Passing Order (MILSTRIP 

Legacy DIC A01, A02, A04, A05, A0A, A0B, A0D, A0E, A3_, A4_), 

DLMS 511M Requisition Modification (MILSTRIP Legacy DIC AM_) 

(for RDD, project code, PD, or advice code), DLMS 869F Requisition 

Follow-Up (MILSTRIP Legacy DIC AT_) continue the GFM validation.

Stock Number Verify item requisitioned against a valid contract to determine 

authority for issue to the contractor. If blank, incorrect, or not 

authorized, reject with Status Code DN.

Unit of Issue Validate the unit of issue in conjunction with the quantity to ensure 

that the requisitioned quantity does not exceed the authorized 

quantity. If quantity is excessive, see validation of quantity field. 

(Note: If a change of unit pack has occurred, appropriate adjustment 

should be made for authorized quantity.)

Quantity If ordered item is authorized by contract, verify the quantity. If blank 

or invalid, reject with Status Code CD. If the requisitioned quantity 

exceeds the remaining authorized quantity, reject the quantity 

exceeding the authorized quantity with Status Code DJ. If authorized 

quantity has been exhausted by previous requisition(s), reject total 

requisitioned quantity with Status Code DQ.

Requisitioner If blank or incorrect, discard. If not authorized, reject with Status 

Code DN.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 8

Table C26.T1. MCA Validation Process for GFM Transactions

CODE OR DATA ELEMENT VALIDATION OF ENTRY

Document Number If blank or incorrect, reject with Status Code CD.

Supplementary Address If contractor DoDAAC, and affected by signal code, and incorrect or 

not authorized, reject with Status Code DN.

Signal and Fund If signal and fund codes indicate issues without contractor 

reimbursement, process as GFM; otherwise, consider as CFM. CFM 

requisitions, except for Army, are not subject to MCA review. All 

Army contractor requisitions and associated transactions will be 

processed under GFM controls. DAAS will respond to requests for 

MCA review for Army CFM under special processing rules authorized 

by the Army.

Manufacturer’s Directive 

Number

If the MDN option is required by the Component and the MDN 

equates to a valid contract number, validate; otherwise, reject with 

Status Code DB.

Contract Call Order Number If specified by S/A contract, and entry is blank or incorrect, reject with 

Status Code DB.

Procurement Instrument 

Identification Number

If blank, or contract is not on MCA file, or contract has expired, reject 

with Status Code DB. (If requisition originated in the MILSTRIP 

legacy format, then only the last eight positions of the PIIN are 

mandatory.)

C26.6. SOURCE OF SUPPLY PROCESSING OF GOVERNMENT-FURNISHED 

MATERIEL REQUISITIONS AND RELATED TRANSACTIONS

C26.6.1. An SoS receiving GFM requisitions, requisition modifiers, passing orders, 

referral orders, requisition follow-ups, and requisition cancellations, regardless of the 

method of transmission, will process such transactions under GFM procedures. A SoS 

in receipt of GFM requisitions for items not managed by their activities will reject the 

requisitions with Status Code CH. The SoS will edit the GFM transactions for the 

prescribed data elements and codes and correct, continue processing actions, or 

provide the appropriate reject status. 

C26.6.2. The SoS will validate all GFM transactions. The SoS in receipt of 

requisitions, passing orders, referral orders, requisition modifiers, or requisition followups being treated as requisitions, containing a contractor’s Service/Agency code under 

Appendix AP7.2, will perform the SoS/MCA validation process except when the signal 

and fund codes indicate that the issue will be with contractor reimbursement by other 

than an Army contractor. All Army contractor requisitions and associated transactions 

will be processed under GFM/CFM controls. (The SoS/MCA validation process is not 

required when an internal requisition transaction is received from a collocated MCA in 

the same distribution system. However, the SoS must have safeguards in place to 

ensure that only internal transactions generated by the collocated MCA are 

accepted/processed.)
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 9

C26.6.3. Under emergency conditions, the SoS may receive telephonic 

requisitions (PD 01-08) from the MCA or requisitioner. The SoS may process these 

requisitions for immediate supply action. Subsequent to taking immediate supply 

action, the GFM validation process will be performed. If the GFM Validation Response 

is not received within 15 days of the GFM Validation Request or the advice code 

indicates that the transaction is not authorized, refer the incident to the appropriate 

criminal investigating agency.

C26.6.4. The SoS/MCA validation process is as follows:

C26.6.4.1. For each GFM requisition or transaction that is treated as a 

requisition, the SoS will employ one of the following options:

C26.6.4.1.1. Create and forward a GFM Validation Request to the MCA 

identified by RIC or distribution code in the requisitioner’s transaction. If the MCA RIC 

and distribution code are not provided or invalid, reject with Status Code CL.

C26.6.4.1.2. Create and forward a GFM Validation Request to DLA 

Transaction Services even if an MCA is contained in the requisitioner’s transaction. 

DLA Transaction Service will perform edits regarding validity of the MCA data.

C26.6.4.1.3. Use a combination of the above options: one for intraComponent transactions and one for inter-Component transactions.

C26.6.4.2. Suspend further supply support action on the requisitioner’s 

transaction pending receipt of the GFM Validation Response or until 15 days have 

elapsed from the date of the GFM Validation Request, whichever occurs first.

C26.6.4.3. If the GFM Validation Response is not received and 15 days have 

elapsed, reject the requisitioner’s transaction with Status Code DR.

C26.6.4.4. Upon receipt of the GFM Validation Response, the SoS will 

process the suspended transaction using instructions provided by the advice or status 

code.

C26.6.4.4.1. If the Advice Code is 2U, reject with Status Code DB.

C26.6.4.4.2. If the Advice Code is 2R, process for the approved quantity 

indicated in the GFM Validation Response. Reject the quantity difference between the 

suspended transaction and the GFM Validation Response with Status Code DJ.

C26.6.4.4.3. If the Advice Code is 2Q, reject with Status Code DQ.

C26.6.4.4.4. If the Status Code is CL, reject with Status Code CL.

C26.6.4.4.5. If the Advice Code is 2V, reject with Status Code DN.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 10

C26.6.4.4.6. If the Advice Code is 2M, process under applicable SoS 

procedures.

C26.6.4.4.7. If neither advice nor status code is provided or is invalid, 

reject with Status Code DR.

C26.6.4.5. If a GFM Validation Response is received, and there is a record of 

the requisition, but a GFM Validation Request has not been submitted, discard the GFM 

Validation Response and generate a GFM Validation Request.

C26.6.4.6. If a GFM Validation Response is received and there is no record 

of the requisition, generate a Supply Status with Status Code BF.

C26.6.5. Follow-ups shall be processed to determine the current status of 

previously submitted requisitions or cancellation requests. Time standards for 

dispatching status in reply to follow-ups are as indicated in Chapter 4, Paragraph 

C4.7.20.1.

C26.7. DEFENSE AUTOMATIC ADDRESSING SYSTEM PROCESSING OF 

GOVERNMENT-FURNISHED MATERIEL TRANSACTIONS

C26.7.1. DAAS will pass all GFM requisitions and related transactions to the 

identified MCA using the MCA RIC or distribution code provided in the transaction. If 

the RIC and the distribution code do not identify an established MCA reject with Status 

Code CL.

C26.7.2. DAAS will pass all GFM Validation Requests to the identified MCA using 

the MCA RIC or distribution code provided in the transaction. If the MCA is invalid, 

generate a GFM Validation Response with Status Code CL to the SoS.

C26.7.3. DAAS will pass all GFM Validation Responses to the SoS.

C26.7.4. DAAS Special Processing for DLA Energy.

5

 DLA Transactions Services 

will perform the GFM Validation Request/Response validation on behalf of DLA Energy 

for selected requisitioning/bill-to activities and stock numbers in accordance with the 

following procedures:

C26.7.4.1. DLA Transaction Services will maintain a DLA Energy GFM Table 

that identifies DLA Energy-established U series contractor DoDAACs authorized to 

requisition specified additive NSNs. The authorized DLA Energy point of contact will 

provide to DLA Transaction Services the U series DoDAAC/NSN combinations for the 

DLA Energy GFM Table.

C26.7.4.2. DLA Energy-sponsored orders for GFM will specify DoDAAC 

SJ0630 (Americas East), SJ0606 (Americas West), SJ0629 (Middle East), SJ0601 

 5 Procedures for exception processing for GFM for packaged fuel additives managed by DLA last reported as a 

delayed implementation by DLA. Refer to Approved DLMS Change (ADC) 211.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 11

(Europe), SJ0600 (Pacific) and SC0600 (DLA Energy for UC locations) as the 

requisitioner/bill-to activity. They will contain a U series DODAAC designated as the 

ship-to activity, and contain the applicable contract number and the DLA Energy 

assigned MDN.

C26.7.4.3. DAAS will route requisitions and requisition related transactions 

(e.g., Requisition, Requisition Modification, Requisition Follow-Up, Referral Orders, and 

Passing Orders) to the SoS for the NSN ordered, and the SoS will generate and 

transmit the GFM Validation Request to DAAS.

C26.7.4.4. DAAS will capture any GFM Validation Requests containing 

DoDAAC SJ0630, SJ0606, SJ0629, SJ0601, SJ0600 or SC0600 (for UC locations) as 

the requisitioner/bill to and a U-series DoDAAC as the ship-to and match it against the 

DLA Energy GFM Table. If a table match is made by U-series DoDAAC and NSN, then 

DAAS will respond to the SoS with a GFM Validation Response, with advice code 2M, 

indicating the order is authorized for processing. If no match, DAAS will respond with a 

GFM Validation Response with Advice Code 2V, indicating the order is not authorized 

for processing.

C26.7.4.5. The SoS will process the GFM Validation Response and either 

honor the order or reject the suspended transaction using Status Code DN, based on 

the advice code provided by DAAS.

C26.7.5. DAAS Special Processing for Army.

6

 Pending implementation of MCA 

procedures in Army systems, DLA Transaction Services will assist the Army by 

performing the GFM Validation Request/Response requirement for the Army wholesale 

MCAs and recording all transactions into a history file for eventual processing to the 

appropriate MCA using the following procedures:

C26.7.5.1. Process all Army contractor identified requisitions (MILSTRIP 

legacy DIC A0_) with the below listed first two positions of the DoDAAC in the document 

number or ship-to DoDAAC to the applicable Army MCA. Contractor requisitions with 

other than the DoDAAC entries indicated are considered Army retail and will be routed 

to the proper SoS with the DAAS RIC SGA or SHA identified as the MCA.

C26.7.5.1.1. If the first two positions of the document number or ship-to 

DoDAAC are CB, pass to RIC A81 (TACOM MCA)

C26.7.5.1.2. If the first two positions of the document number or ship-to 

DoDAAC are CL, pass to RIC A82 (AMCOM MCA).

C26.7.5.1.3. If the first two positions of the document number or ship-to 

DoDAAC are CG, pass to RIC A83 (CECOM MCA).

 6 Procedures to control access to DoD material inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to AMCL 1A.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 12

C26.7.5.1.4. If the first two positions of the document number or ship-to 

DoDAAC are CM, pass to RIC A84 (TACOM MCA)

C26.7.5.1.5. If the first two positions of the document number or ship-to 

DoDAAC area CK, pass to RIC A85 (TACOM MCA).

C26.7.5.1.6. If the first two positions of the document number or ship-to 

DoDAAC are CH, pass to RIC A86 (AMCOM MCA)

C26.7.5.2. For Requisition Modification and Requisition Follow-Up 

transactions containing a valid MCA distribution code as identified below, the DAAS RIC 

SGA or SHA will be entered into the MCA field and routed to the appropriate SoS. If a 

valid MCA is not identified and the transaction contains the entries cited above in the 

first two positions of the document number or ship-to DoDAAC, the transaction will be 

passed to the appropriate MCA. If none of these conditions apply, the transaction will 

be considered retail and be routed to the appropriate SoS with the DAAS RIC SGA or 

SHA entered into the MCA field. The following are valid MCA distribution codes:

C26.7.5.2.1. I (India) - TACOM MCA

C26.7.5.2.2. L (Lima) - AMCOM MCA

C26.7.5.2.3. P (Papa) - CECOM MCA

C26.7.5.2.4. S (Sierra) - TACOM MCA

C26.7.5.2.5. Y (Yankee) - TACOM MCA

C26.7.5.2.6. E (Echo) - AMCOM MCA

C26.7.5.2.7. 8 (Eight) - USACEA MCA 

C26.7.5.3. Upon receipt of a GFM Validation Request transaction, a GFM 

Validation Response transaction will be generated with Status Code 2M and returned to 

the RIC of the SoS submitting the GFM Validation Request transaction.

C26.8. CONTRACTOR REQUISITIONS FOR CONTRACTOR-FURNISHED 

MATERIEL

C26.8.1. Requisitions for materiel from a Government SoS for shipment to 

contractors that identify the contractor as the bill-to activity are not subject to GFM MCA 

controls with the exception of Army contractor requisitions to which MCA controls are 

applicable. DAAS will validate transactions for Army contractor requisitions of CFM for 

those items that contractors are authorized to requisition as CFM as specified in this 

chapter, and for non-wholesale level supply as designated by the contractor-series 

DoDAAC. DoD Components will establish appropriate procedures for oversight of CFM 

requisitions in accordance with the Federal Acquisition Regulation.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 13

C26.8.2. DAAS Processing of CFM Transactions. The process described in this 

paragraph provides mandatory CFM controls for CFM requisitions where the bill-to 

activity, as identified in the requisition, is an Army contractor and the SoS is DLA. This 

process is optional for other Services and may be expanded to include other SoS if 

needed. 

C26.8.2.1. DAAS will maintain a list of Service/Agency authorized contractor 

DoDAACs and the associated NSNs/DoD-managed part numbers for which these 

contractors may submit CFM requisitions on a CFM Authorized Materiel Table for use in 

validating requisitions regardless of method of payment. 

C26.8.2.2. CFM contractor transactions that match the CFM Authorized 

Materiel Table by DoDAAC, but do not match by NSN or part number will be rejected 

with Status Code CL; requisitions that match on DoDAAC and NSN/part number shall 

be processed as valid. 

C26.8.2.3. DAAS will enter the DAAS RIC SGA or SHA as the validating 

MCA. 

C26.8.2.4. DAAS will perform the GFM Validation Request/Response 

validation requirement for authorized CFM requisitions that match the CFM Authorized 

Materiel Table. 

C26.8.2.5. DAAS will furnish CFM reports upon request for use by the 

contracting officer in verifying that quantities ordered are within the contract allowance.

C26.8.2.6. Army contractor requisitions that do not match the CFM 

Authorized Materiel Table will be processed by DAAS under the MCA waiver exception 

process or passed to the applicable MCA as described in C26.7.5.

C26.8.2.7. For DLA CFM, DAAS processing will be as identified in C26.8.3. 

C26.8.2.8. CFM requisitions for other Service contractors will be passed to 

the appropriate SoS. 

C26.8.2.9. NSNs listed in the CFM Authorized Materiel Table may be 

modified over the course of this agreement when the appropriate Army contracting 

officer provides such authority. Updates to the authorized list will be collected, 

consolidated into one Microsoft Excel file by the designated DLA Lead Center point of 

contact with proof of Army Contracting Officer concurrence and provided to 

Headquarters DLA Army Performance Based Logistics (PBL) action officer. DLA will 

coordinate updates to individual contractor lists with DLA DoD EMall and DLA 

Transaction Services on a monthly basis. To optimize program changes, all additions to 

Army partnership lists will be made during an agreed-to monthly timeframe between 

DLA and support entities.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 14

C26.8.3. DLA Transaction Services Processing of DLA CFM Transactions

C26.8.3.1. DLA Transaction Services will maintain a DLA CFM Authorized 

DoDAAC Table listing DLA contractor DoDAACs authorized to requisition CFM. DLA 

Transaction Services will populate or delete DoDAACs to/from the table as directed by 

DLA. Requisitions identifying a DLA-assigned U-series contractor DoDAAC as the billto activity will be edited against this table. 

C26.8.3.2. DLA Transaction Services must edit all incoming Requisitions 

Passing Order, Referral Order, Requisition Modification, and Requisition Follow-Up 

transactions containing a U-series DoDAAC when identified as the bill-to activity against 

the DLA CFM Authorized DoDAAC Table. 

C26.8.3.2.1. If matched to the table, then DAAS will route/pass the

transaction based on established DAAS rules to the appropriate SoS for further 

processing. 

C26.8.3.2.2. If the U-series bill-to DoDAAC does not match the table, 

then DAAS will reject the transaction using Status Code DB. 

C26.8.3.3. DLA Transaction Services will capture any GFM Validation 

Request transactions containing a DLA U-series DoDAAC identified as the bill-to 

DoDAAC and match it against the DLA CFM Authorized DoDAAC Table. 

C26.8.3.3.1. If the U-series bill-to-DoDAAC matches the table, then 

DAAS will respond with a GFM Validation Response transaction with Advice Code 2M 

indicating the requisition is authorized. 

C26.8.3.3.2. If the U-series bill-to-DoDAAC does not match the table, 

then DAAS will respond with a GFM Validation Response transaction with Advice Code 

2U indicating the requisition is not authorized.

C26.9. PREPARATION OF DOD EMALL REQUISITIONS BY CONTRACTORS.

C26.9.1. Account Setup. Authorized contractors may establish DoD EMALL 

accounts to facilitate materiel requisition submissions. To register, go to https://dodemall.dla.mil and click on “New User Registration”. Access to DoD EMALL is fully 

Common Access Card (CAC)/Public Key Infrastructure (PKI) enforced. Details of the

access requirements are listed on the registration pages of the EMALL site. Prior to 

establishing the account, the applicable contracting officer must ensure that the 

contractor is authorized access to Government supply sources and must agree to 

review monthly or quarterly reports prepared by the DoD EMALL monitoring contractor 

activity. The applicable contracting officer must also provide a list of approved NSN/part 

numbers associated with each account/contractor DoDAAC for Army authorized CFM. 

Army contractors will be processed under GFM/CFM controls.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 15

C26.9.2. Contractor GFM/CFM Validations. DoD EMALL will validate that 

contractors are authorized to purchase materiel from DoD supply sources as a 

prerequisite for submission of EMALL orders. 

C26.9.2.1. DoD EMALL requisitions for GFM will be subjected to prescribed 

rules for MCA controls within DoD EMALL or within DAAS. 

C26.9.2.2. DoD EMALL CFM requisitions indicating corporate credit card 

method of payment are subject to special processing controls as described in C26.9.2.

C26.9.2.3. Additionally, CFM requisitions for Army authorized contractors will 

be validated to ensure that requisitioned NSNs or DoD managed part numbers are 

authorized regardless of the method of payment under CFM controls.

C26.9.3. Corporate Credit Card Usage. 

C26.9.3.1. The DoD EMALL program office will identify to DLA Transaction 

Services all contractors authorized access to Government materiel for purchase as 

CFM using a corporate credit card as the method of payment. 

C26.9.3.2. DAAS will maintain these DoDAACs as an authorized contractor 

edit table (referenced hereafter as the DoD EMALL CFM Table) to be employed during 

initial processing and for GFM Validation Request processing.

C26.9.4. Corporate Credit Card CFM Purchases and DAAS Processing. DoD 

EMALL requisitions for shipment to contractors using corporate credit card payment are 

assigned Signal Code B, Fund Code XP, and the ship-to DoDAAC perpetuated to the 

supplementary address of the DoD EMALL DoDAAC (SP5200 or SC4210). This 

configuration identifies a Government DoDAAC as the bill-to activity, thereby triggering 

DAAS and the DoD Component SoS processing systems to misinterpret such 

transactions as GFM requisitions. 

C26.9.4.1. DAAS will validate these transactions against existing GFM edits 

and the DoD EMALL CFM Table to determine appropriate action. 

C26.9.4.2. If the contractor requisition does not contain a valid MCA 

identification code and the DoDAAC is not listed in the DoD EMALL CFM Table, DAAS 

will reject with Status Code CL. 

C26.9.4.3. If an MCA is identified by either a distribution code or a RIC, 

DAAS will forward the requisition to the SoS. 

C26.9.4.3.1. The SoS will submit a GFM Validation Request to DAAS 

for validation following GFM MCA procedures (including Army CFM). 

C26.9.4.3.2. DAAS will recognize the EMALL supplementary address 

and again employ existing GFM edits and the DoD EMALL CFM Table to take 

appropriate action. 
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 16

C26.9.4.3.3. If the validation using the DoD EMALL CFM Table 

identifies the contractor DoDAAC as authorized by the contracting officer for ordering 

CFM using corporate credit cards, then DLA Transaction Services will validate the 

requisition and respond to the SoS with a GFM Validation Response using Advice Code 

2M indicating that the requisition is valid. The SoS will continue processing. 

C26.9.4.3.4. If the contractor DoDAAC is not contained on the DoD 

EMALL CFM Table, but the requisition contains a valid MCA code, then DLA 

Transaction Services will forward the GFM Validation Request to the MCA for validation. 

C26.9.4.3.5. If the contractor DoDAAC is not contained on the DoD 

EMALL CFM Table or does not match the CFM Authorized Materiel Table, when 

applicable, and the requisition does not contain a valid MCA code, then DAAS will 

provide a GFM Validation Response with Status Code CL indicating that the transaction 

is invalid. The SoS shall reject the requisition. 

C26.9.4.4. For DLA contractor credit card purchases (identified by a DLAassigned U-series DoDAAC in the document number), DAAS processing rules will be as 

described in this paragraph, except that the requisition will be validated based upon the 

requisitioner DoDAAC matching to the DLA CFM Authorized DoDAAC Table.

C26.9.5. DoD EMALL Reports. To support DoD requirements for oversight of 

materiel sold to contractors, the DoD EMALL program office will provide reports to 

monitor contractor activity. For contracts having a maximum total dollar ceiling, a DoD 

EMALL report will be provided to the contracting officer when the cumulative value of 

CFM ordered reaches 80 percent of the ceiling.

C26.10. INVENTORY CONTROL POINT/INTEGRATED MATERIEL MANAGERDIRECTED SHIPMENT OF NON-REQUISITIONED GOVERNMENT FURNISHED 

MATERIEL BASED ON A BILL OF MATERIEL. 

C26.10.1. ICP/integrated materiel manager (IMM)-directed shipments of GFM may 

be managed through the use of a bill of materiel (BOM) as identified under the terms of 

the DoD contract. In this context, the BOM identifies the raw materials/component parts 

needed to assemble/manufacture/repair the end item or final product. Based on the unit 

of allowance, the number/amount of GFM component materiel needed to accommodate 

the total number of end items to be manufactured/assembled/repaired on a specific 

contract/purchase order may be calculated and provided. This procedure eliminates the 

need for separate GFM requisitions for the component materiel and subsequent 

MILSTRIP MCA validation. Instead, this process allows the ICP/IMM to push the 

materiel to the contractor as required by schedule and/or usage.

C26.10.2. Upon contract award for production of an end item or final product, the 

BOM becomes the basis for determining the quantity of GFM required by the contractor. 

These deliveries will only include stocked raw material/component parts that the 

Government provides at no separate charge to the contractor for assembly/manufacture 

of the end item/final product. Under this process, the ICP/IMM will use internal control 
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 1

Page 17

procedures to monitor consumption of raw material/component parts against the receipt 

of items awarded by contract.

C26.10.3. The ICP/IMM will prepare materiel release orders for stock shipment 

using document numbers based upon a DLA-established DoDAAC. The ship-to 

location cited in the release order will identify the contractor DoDAAC authorized to 

receive GFM. Under DLMS processing, the Materiel Release Order will include the 

authorizing contract number, and the call/order and CLIN, when applicable; this is not 

applicable to MILSTRIP legacy processing. The storage activity will provide shipment 

confirmation to the ICP/IMM for monitoring GFM shipments and will prepare shipment 

status; under DLMS processing, the shipment status will perpetuate applicable contract 

data. For contractors without capability to accept legacy 80 record position/DLMS 

transactions, status of the GFM component delivery will be provided upon request by 

the contractor. The assembled/manufactured end items may be shipped directly to 

customers or shipped to a storage location for future use.

C26.10.4. Use of the above business process does not relieve the ICP/IMM from 

management reporting requirements required by DoD 4140.1-R, DoD Supply Chain 

Materiel Management Regulation. Materiel Receipt Acknowledgement is required for 

GFM, including pushed shipments, under MILSTRAP procedures.

C26.10.5. This process is discretionary and may not be applicable to all 

commodities and contracts requiring GFM. This process may only be used to support 

GFM requirements satisfied by the DoD Component issuing the contract (that is, by 

design, it does not support inter-Component materiel support).
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 1

Enclosure 2

A. Update Chapter 4 to DLM 4000.25, Volume 2 by removing contractor access to government 

sources of supply related information and moving it to the new Chapter 26. Removed text is 

identified by double strikethroughs. Removed paragraphs have been marked as RESERVED

to avoid renumbering of the remaining paragraphs in the chapter. A reference to the 

realigned procedures was added to the opening paragraph.

C4. CHAPTER 4

REQUISITIONING

C4.1. GENERAL. This chapter prescribes procedures for the preparation and 

submission of requisitions with specific requisitioning requirements involving 

Government Furnished Materiel (GFM), Not Mission Capable Supply (NMCS), 

Anticipated NMCS (ANMCS), Pre-Positioned War Reserve Materiel Stock (PWRMS), 

conventional ammunition, subsistence, and GSA non-mailable items. This chapter also 

provides procedures for requisition cancellations, modifications, and inquiries. In 

addition, this chapter prescribes the source of supply and storage activity processing 

procedures of the aforementioned transactions including the preparation and processing 

of the materiel release, materiel release advice, and DAAS edits associated with 

requisition processing. Specific requisitioning requirements involving Government 

Furnished Materiel and Contractor Furnished Materiel are identified in DLM 

4000.25 Volume 2, Chapter 26.

[Intervening text not shown]

C4.2.10. Government Furnished Materiel Requisitions Reserved

C4.2.10.1. General

C4.2.10.1.1. Purpose. This section prescribes policies and procedures 

for requisitioning GFM by or for contractors from the DoD Supply System. These 

procedures establish guidelines for requisitioners, authorized contractors, and the DoD 

Components to obtain GFM from DoD inventories in support of contract requirements. 

These procedures also support the use of DLMS requisitioning by authorized 

contractors to obtain materiel from Government sources of supply to be used as 

contractor furnished materiel (CFM) under controls established by the authorizing 

Component and as specified in this chapter. In those instances where one Component 

is performing the procurement/contract writing for another Component that includes the 

authorization for a contractor to order or receive GFP (or Army CFM), the Component 

providing the procurement/contracting service and the Component requesting the 

contract will coordinate efforts to ensure that the requesting Component’s management 

control activity (MCA) has access to the necessary contract and applicable contract 
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 2

modification information to perform its management control and accountability functions 

over Government supply system materiel access.

C4.2.10.1.2. Establishing an MCA. The DoD Components will assign a 

unique RIC and distribution code to each MCA. Requisitioners, authorized contractors, 

and the DoD Components will send all requisitions for GFM to the appropriate MCA for 

validation.

C4.2.10.1.3. Violations. Any attempt to circumvent GFM/CFM validation 

requirements is sufficient cause to refer the violation to the appropriate criminal 

investigating activity to determine possible fraud, waste, and abuse. The sponsoring 

Component or monitoring activity must refer all violations to the criminal investigators 

based on reports of rejected transactions or violations discovered during the postvalidation process.

C4.2.10.1.4. Applicability. These procedures apply to all contractors 

and all DoD Components requisitioning GFM or CFM from DoD sources of supply. The 

production of ammunition is excluded from GFM control.

C4.2.10.2. Preparation of Requisitions and Related Transactions For 

Government Furnished Materiel to Contractors

C4.2.10.2.1. Initiation. Requisitions for GFM may be initiated by the 

responsible DoD Component or, subject to the terms of the contract, by contractors. 

Requisitions for GFM will be prepared and initially submitted by GFM requisitioners, 

both contractors and DoD Components, using legacy MILSTRIP or DLMS transaction 

formats to the MCA designated for monitoring the contract. Transmission through 

DAAS will be used to the extent practical.

C4.2.10.2.2. Source of Supply Processing. Sources of supply will 

process requisitions and associated transactions containing the DoD Service/Agency 

codes designated for contractors under GFM controls and restrictions except when the 

issue will be for CFM with contractor reimbursement by other than an Army contractor. 

All Army contractor requisitions and associated transactions will be processed under 

GFM/CFM controls.

C4.2.10.2.3. Required Information. All GFM requisitions, including 

referral and passing orders, must include GFM-related information as follows:

C4.2.10.2.3.1. MCA monitoring the contract will be identified as the 

RIC-To.

C4.2.10.2.3.2. DoDAAC of the contractor requesting and/or 

receiving the materiel.

C4.2.10.2.3.3. Indication when issue is without reimbursement 

(including applicable signal code).
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 3

C4.2.10.2.3.4. Identification of the contract number.

C4.2.10.2.3.5. Identification of the call or order number, when 

applicable.

C4.2.10.2.3.6. Identification of the contract line item number, when 

applicable.7

C4.2.10.2 4. Contract Information. All GFM requisitions for or by 

contractors must identify the contract number and other appropriate contract data, as 

required. Components authorizing GFM may direct the inclusion of the manufacturing 

directive number (MDN) as supplemental to the authorizing contract number.8

C4.2.10.3. Submissions of Government Furnished Materiel Requisitions

C4.2.10.3.1. Requisitioners, control offices, and monitoring activities 

must submit all requisitions and associated transactions for GFM, regardless of origin 

(such as contractor or DoD Component-initiated), to the appropriate DoD Component 

MCA.

C4.2.10.3.2. After validating the GFM requisitions, the DoD Component 

MCA will forward the validated requisitions to the source of supply. The DoD 

Component MCA may pass validated transactions internally where the MCA and source 

of supply are collocated. The DoD Component MCA will send the validated 

transactions via DAAS when the MCA and source of supply are not collocated.

C4.2.10.3.3. Modifier Transactions. Modifier transactions are 

authorized for GFM requisitions to modify information such as the project code, priority 

designator (PD), advice code, and the required delivery date (RDD). Modifiers may not 

be used to change the ship-to/bill-to information. Modifiers are subject to GFM controls 

and validation procedures.

C4.2.10.4. Management Control Activity Processing of Government 

Furnished Materiel Requisitions and Related Transactions

C4.2.10.4.1. Management Control Activity Actions. The MCA will 

receive and validate the data in the GFM requisitions, referral orders, and passing 

orders, as well as subsequent modifiers and follow-ups, based on the criteria furnished 

by the procurement and/or contracting offices and as described in Table C4.T2. The 

MCA will make changes, reject, or continue the processing action.

 7 Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS compliant 

contract number (rather than the abbreviated contract number authorized under legacy MILSTRIP procedures). 8 Refer to ADC 1014. Staggered implementation is authorized for the transition to the mandatory inclusion of the 

contract number (rather than MDN as an alternative to the contract number).
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 4

C4.2.10.4.2. The MCA will maintain a requisition history file to serve as 

an auditable record of each GFM transaction. In addition, the MCA will generate reports 

required by DoD 4140.1-R.

C4.2.10.4.3. Under emergency conditions, such as a potential contract 

work stoppage, the MCA may receive telephonic requisitions, with PDs 01-08, for GFM. 

When this occurs, the MCA may telephone the requisitions to the appropriate source of 

supply and validate the requirements afterward. If the post validation process reveals 

the requisitioner is not authorized GFM, the MCA will:

C4.2.10.4.3.1. Send cancellation requests to the appropriate 

source of supply, and

C4.2.10.4.3.2. advise the appropriate criminal investigating agency 

for determination of fraud, waste, and abuse.

C4.2.10.4.4. Upon completion of the validation process, the MCA will 

identify itself as the FROM organization in the transaction and forward the requisition 

transactions, or internal transactions (optional only when the MCA and source of supply 

are collocated in the same distribution system), cancellations, follow-ups, modifiers, 

passing orders, or referral orders to the applicable source of supply via DAAS.

C4.2.10.4.4.1. Update the outgoing transaction to insert the RICTo of the source of supply.

C4.2.10.4.4.2. Insert the distribution code of the MCA validating 

the transaction. 

C4.2.10.4.4.3. Perpetuate all applicable contract data. Under 

DLMS, the MCA must include the DFARS contract number. Where required by the 

Component, the MCA may also perpetuate the MDN consisting of the MCA’s 

distribution code and two other alpha/numeric characters as assigned.9

C4.2.10.5. Management Control Activity Processing of Government 

Furnished Materiel Validation Requests. MCAs in receipt of a GFM validation request 

(DLMS 517G, GFM Validation Request) will validate the data contained therein. This 

validation process must be completed and a DLMS 517G GFM Validation Response 

transaction created and forwarded to the applicable source of supply within 15 days or 

receipt of the GFM validation request transaction. A GFM validation response (DLMS 

517G) will be transmitted to the applicable source of supply as follows:

C4.2.10.5.1. If the requisition has been previously validated, cite Advice 

Code 2M.

 9 Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS compliant 

contract number (rather than the abbreviated contract number authorized under legacy MILSTRIP procedures) 

and for the transition to the mandatory inclusion of the contract number (rather than MDN as an alternative to the 

contract number).
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 5

C4.2.10.5.2. If the requisition has not been previously validated and the 

call order number/procurement instrument identification number (PIIN) (or MDN, if 

required by the Component in addition to the call order number/PIIN) is not present, cite 

Advice Code 2U.

C4.2.10.5.3. If the requisition has not been previously validated and the 

call order number/PIIN is present, validate the stock number, unit of issue/quantity, and 

contractor, and generate the GFM Validation response as follows:

C4.2.10.5.3.1. If the validation process reveals that the contract is 

not valid, respond with Advice Code 2U.

C4.2.10.5.3.2. If the validation process reveals that the requested 

quantity exceeds the contract authorized quantity, respond with Advice Code 2R and 

indicate the quantity approved for issue.

C4.2.10.5.3.3. If the validation process reveals that the requested 

quantity exceeds the contract authorized quantity, respond with Advice Code 2Q and 

indicate the total quantity is disapproved for issue.

C4.2.10.5.3.4. If the validation process reveals that the requested 

item, or contractor is not authorized GFM under a valid contract, respond with Advice 

Code 2V.

C4.2.10.5.3.5. If the validation process reveals that the requested 

item is authorized, respond with Advice Code 2M.

C4.2.10.5.4. MCAs in receipt of supply status (DLMS 870S 

transactions) with Status Code BF will review for establishment of a valid requisition. If 

a valid requisition exists, a DLMS 869F transaction will be generated. If a valid 

requisition does not exist, a report will generated for internal review. Subsequent 

receipt of a valid requisition will be processed under the procedures/validation process 

indicated in Table C4.T2.

Table C4.T2. MCA Validation Process for GFM Transactions

CODE OR DATA 

ELEMENT

VALIDATION OF ENTRY

Transaction Type If DLMS 511R, Requisition, Referral, or Passing Order (DICs 

A01, A02, A04, A05, A0A, A0B, A0D, A0E, A3_, A4_,)

DLMS 511M, Requisition Modification (DIC AM_) (for 

modification to RDD, project code, PD, or advice code),

DLMS 869F, Requisition Follow-up (DIC AT_),

continue the GFM validation.

Stock Number Verify item requisitioned against a valid contract to determine 

authority for issue to the contractor. If blank, incorrect, or not 

authorized, reject with Status Code DN.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 6

Table C4.T2. MCA Validation Process for GFM Transactions

CODE OR DATA 

ELEMENT

VALIDATION OF ENTRY

Unit of Issue Validate the unit of issue in conjunction with the quantity to 

ensure that the requisitioned quantity does not exceed the 

authorized quantity. If quantity is excessive, see validation of 

quantity field. (Note: If a change of unit pack has occurred, 

appropriate adjustment should be made for authorized 

quantity.)

Quantity If ordered item is authorized by contract, verify the quantity. If 

blank or invalid, reject with Status Code CD. If the 

requisitioned quantity exceeds the remaining authorized 

quantity, reject the quantity exceeding the authorized quantity 

with Status Code DJ. If authorized quantity has been 

exhausted by previous requisition(s), reject total requisitioned 

quantity with Status Code DQ.

Requisitioner If blank or incorrect, discard. If not authorized, reject with 

Status Code DN.

Document Number If blank or incorrect, reject with Status Code CD.

Supplementary Address If contractor DoDAAC, and affected by signal code, and 

incorrect or not authorized, reject with Status Code DN.

Signal and Fund If signal and fund codes indicate issues without contractor 

reimbursement, process as GFM; otherwise, consider as CFM. 

CFM requisitions, except for Army, are not subject to MCA 

review. All Army contractor requisitions and associated 

transactions will be processed under GFM controls. DAAS will 

respond to requests for MCA review for Army CFM under 

special processing rules authorized by the Army.

Manufacturer’s Directive 

Number

If the MDN option is required by the Component and the MDN 

equates to a valid contract number, validate; otherwise, reject 

with Status Code DB.

Contract Call Order 

Number

If specified by S/A contract, and entry is blank or incorrect, 

reject with Status Code DB.

Procurement Instrument 

Identification Number

If blank, or contract is not on MCA file, or contract has expired, 

reject with Status Code DB. (If requisition originated in the 

legacy MILSTRIP format, then only the last eight positions of 

the PIIN are mandatory.)

C4.2.10.6. Source of Supply Processing of Government Furnished Materiel 

Requisitions and Related Transactions

C4.2.10.6.1. Sources of supply receiving GFM requisitions, modifiers, 

follow-ups, and cancellations, regardless of the method of transmission, will process 

such transactions under these procedures. Sources of supply receiving GFM 
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 7

requisitions for items not managed by their activity will reject the requisitions with Status 

Code CH. Sources of supply will edit the GFM transactions for the prescribed data 

elements and codes and correct, continue the processing actions, or provide the 

appropriate reject status.

C4.2.10.6.2. Sources of supply will validate all GFM transactions. 

Sources of supply in receipt of requisitions, passing orders, referral orders, modifiers, or 

follow-ups being treated as requisitions, containing a contractor’s Service/Agency code 

will perform the source of supply/MCA validation process except when the signal and 

fund codes indicate the issue will be with contractor reimbursement by other than an 

Army contractor. All Army contractor requisitions and associated transactions will be 

processed under GFM/CFM controls. The source of supply/MCA validation process is 

not required when an internal requisition transaction is received from a collocated MCA 

in the same distribution system. However, sources of supply must have safeguards in 

place to ensure that only internal transactions generated by the collocated MCA are 

accepted/processed.

C4.2.10.6.3. Under emergency conditions, sources of supply may 

receive telephonic (PD 01-08) requisitions from the MCA or requisitioner. The source of 

supply may process these requisitions for immediate supply action. Subsequent to 

taking immediate supply action, the GFM validation process will be performed. If the 

GFM validation response is not received within 15 days of the request or the advice 

code indicates that the transaction is not authorized GFM, refer the incident to the 

appropriate criminal investigating agency.

C4.2.10.7. Source of Supply Government Furnished Materiel Validation 

Process. For each GFM requisition or transaction that is treated as a requisition, the 

source of supply will employ one of the following options:

C4.2.10.7.1. Create and forward a DLMS 517G GFM Validation 

Request to the MCA or distribution code identified in the requisitioner's transaction. If 

the MCA and distribution code are invalid or missing, reject with Status Code CL.

C4.2.10.7.2. Create and forward a GFM validation request to DLA 

Transaction Services even if an MCA is contained in the requisitioner's transaction. 

DLA Transaction Services will perform edits regarding the validity of the MCA data.

C4.2.10.7.3. Use a combination of the above options: one for intraComponent transactions and one for inter-Component transactions.

C4.2.10.7.4. Suspend further supply support action on the 

requisitioner's transaction pending receipt of the GFM validation response or until 15 

days have elapsed from the date of the GFM validation request, whichever occurs first.

C4.2.10.7.5. If the GFM validation response is not received and 15 days 

have elapsed from the GFM validation request, reject the requisitioner's transaction with 

Status Code DR.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 8

C4.2.10.7.6. Upon receipt of the GFM validation response, the source of 

supply will process the suspended transaction using instructions provided by the 

advice/status code.

C4.2.10.7.6.1. If Advice Code 2U, reject with Status Code DB.

C4.2.10.7.6.2. If Advice Code 2R, process for the approved quantity 

indicated in the GFM validation response. Reject the quantity difference between the 

suspended transaction and the GFM validation response with Status Code DJ.

C4.2.10.7.6.3. If Advice Code 2Q, reject with Status Code DQ.

C4.2.10.7.6.4. If Status Code CL, reject with Status Code CL.

C4.2.10.7.6.5. If Advice Code 2V, reject with Status Code DN.

C4.2.10.7.6.6. If Advice Code 2M, process under applicable source 

of supply procedures.

C4.2.10.7.6.7. If the advice/status code is invalid or an 

advice/status code is not indicated, reject with Status Code DR.

C4.2.10.7.7. If a GFM validation response is received and there is a 

record of the requisition, but a GFM validation request has not been submitted, discard 

the GFM validation response and generate a GFM validation request.

C4.2.10.7.8. If a GFM validation response is received and there is no 

record of the requisition, provide Status Code BF.

C4.2.10.8. DAAS Processing Of GFM Transactions. DAAS will pass the 

following:

C4.2.10.8.1. All GFM transactions to the identified MCA. If the MCA is 

not a valid MCA, reject with Status Code CL.

C4.2.10.8.2. All GFM validation requests to the identified MCA. If the 

MCA is invalid, generate a GFM validation response with Status Code CL to the source 

of supply.

C4.2.10.8.3. All GFM validation responses to the identified source of 

supply.

C4.2.10.9. Exception Processing for Government Furnished Materiel for 

Packaged Fuel Additives Managed by DLA. DLA Transaction Services will perform the 

DLMS 517G validation on behalf of the DLA Energy for selected requisitioning/bill-to 

activities and stock numbers in accordance with the following procedures:
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 9

C4.2.10.9.1. DLA Transaction Services will maintain a DLA Energy 

GFM table that will identify DLA Energy-established U-series contractor DoDAACs 

authorized to requisition specified additive NSNs. The authorized DLA Energy POC will 

provide to DLA Transaction Services the U-series DoDAAC/NSN combinations for the 

DLA Energy GFM table.

C4.2.10.9.2. DLA Energy sponsored orders for GFM will specify 

DoDAAC SJ0630 (Americas East), SJ0606 (Americas West), SJ0629 (Middle East), 

SJ0601 (Europe), SJ0600 (Pacific), and SC0600 (DLA Energy for UC series DoDAAC 

contingency locations) as the requisitioner/bill-to activity. They will contain a U-series 

DoDAAC designated as the ship-to activity, and contain the applicable contract number 

and the DLA Energy assigned MDN.

C4.2.10.9.3. DLA Transaction Services will route requisitions and 

requisition related transactions (DLMS 511R/511M/869F) to the source of supply for the 

NSN ordered, and the source of supply will generate the required DLMS 517G, GFM 

Validation Request to DLA Transaction Services.

C4.2.10.9.4. DLA Transaction Services will capture any DLMS 517G 

transactions containing DoDAAC SJ0630, SJ0606, SJ0629, SJ0601, SJ0600, or 

SC0600 (for UC locations) as the requisitioner/bill-to and a U-series DoDAAC as the 

ship-to and match it against the DLA Energy GFM table. If a table match is made by Useries DoDAAC and the NSN, then DLA Transaction Services will respond to the source 

of supply with a DLMS 517G MCA GFM Validation Response, with Advice Code 2M, 

indicating the order is authorized for processing. If no match, DLA Transaction Services 

will respond with DLMS 517G with Advice Code 2V, indicating the order is not 

authorized for processing.

C4.2.10.9.5. The source of supply will process the DLMS 517G 

Validation Response and either honor the order or reject the suspended transaction 

using Status Code DN, based on the advice code provided by DLA Transaction 

Services.

C4.2.10.10. DAAS Special Processing for Army10. Pending full 

implementation of MCA procedures in Army systems, DLA Transaction Services will 

assist the Army by performing the GFM MCA transaction validation requirement for the 

Army wholesale MCAs and recording all transactions into a history file for eventual 

processing to the appropriate MCA using the following procedures:

C4.2.10.10.1. Process all DLMS 511R (DIC A0_) Army contractor 

identified requisitions with the below listed first two positions of the DoDAAC to the 

applicable Army MCA. Contractor requisitions with other than the DoDAAC entries 

indicated are considered Army retail and will be routed to the proper source of supply 

with the DAAS RIC SGA or SHA identified as the MCA.

 10 Procedures to control access to DoD material inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to AMCL 1A.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 10

C4.2.10.10.1.1. If the first two positions of the document number or 

supplementary address is CB, pass to RIC A81 (TACOM MCA)

C4.2.10.10.1.2. If the first two positions of the document number or 

supplementary address is CL, pass to RIC A82 (AMCOM MCA).

C4.2.10.10.1.3. If the first two positions of the document number or 

supplementary address is CG, pass to RIC A83 (CECOM MCA).

C4.2.10.10.1.4. If the first two positions of the document number or 

supplementary address is CM, pass to RIC A84 (TACOM MCA)

C4.2.10.10.1.5. If the first two positions of the document number or 

supplementary address is CK, pass to RIC A85 (TACOM MCA).

C4.2.10.10.1.6. If the first two positions of the document number or 

supplementary address is CH, pass to RIC A86 (AMCOM MCA)

C4.2.10.10.2. For requisition modifications (DLMS 511M/DIC AM_) and 

requisition follow-ups (DLMS 869F/DIC AT_) transactions, containing a valid MCA 

distribution code as identified below, the DAAS RIC SGA or SHA will be entered into 

MCA field and routed to the appropriate source of supply. If a valid MCA is not 

identified and the transaction contains the entries cited above in the first two positions of 

the document number or supplementary address, the transaction will be passed to the 

appropriate MCA. If none of these conditions apply, the transaction will be considered 

retail and be routed to the appropriate source of supply with the DAAS RIC SGA or SHA 

entered into MCA RIC field. The following are valid MCA distribution codes:

C4.2.10.10.2.1. I (India) - TACOM MCA

C4.2.10.10.2.2. L (Lima) - AMCOM MCA

C4.2.10.10.2.3. P (Papa) - CECOM MCA

C4.2.10.10.2.4. S (Sierra) - TACOM MCA

C4.2.10.10.2.5. Y (Yankee) - TACOM MCA

C4.2.10.10.2.6. E (Echo) - AMCOM MCA

C4.2.10.10.2.7. 8 (Eight) - USACEA MCA 

C4.2.10.10.3. Upon receipt of GFM validation transactions, a GFM validation 

response transaction will be generated with Status Code 2M and returned to the RIC of 

the source of supply submitting the GFM validation request transaction.

C4.2.10.11. Contractor Requisitions for Contractor Furnished Materiel 
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 11

C4.2.10.11.1. Requisitions for materiel from Government sources of 

supply for shipment to contractors that identify the contractor as the bill-to activity are 

not subject to GFM MCA controls with the exception of Army contractor requisitions to 

which MCA controls are applicable. DAAS will validate transactions for Army contractor 

requisitions of CFM for those items that contractors are authorized to requisition as 

CFM as specified in this chapter and for non-wholesale level supply as designed by the 

contractor-series DoDAAC. DoD Components will establish appropriate procedures for 

oversight of CFM requisitions in accordance with the Federal Acquisition Regulation.

C4.2.10.11.2. DAAS Processing of CFM Transactions. The process 

described in this subparagraph provides mandatory CFM controls for CFM requisitions 

where the bill-to-activity, as identified in the requisition, is an Army contractor and the 

source of supply is DLA. This process is optional for other DoD Components and may 

be expanded to include other sources of supply, if needed. DAAS will maintain a list of 

DoD Component-authorized contractor DoDAACs and the associated NSNs/DoDmanaged part numbers for which these contractors may submit CFM requisitions on a 

CFM Authorized Materiel Table for use in validating requisitions regardless of method of 

payment. CFM contractor transactions that match the CFM Authorized Materiel Table 

by DoDAAC, but do not match by NSN or part number, will be rejected with Status Code 

CL; requisitions that match on DoDAAC and NSN/part number will be processed as 

valid. DAAS will enter the DAAS RIC SGA or SHA as the validating MCA. DAAS will 

perform DLMS 517G validation requirement for authorized CFM requisitions that match 

to the CFM Authorized Materiel Table. DAAS will furnish CFM reports upon request for 

use by the contracting officer in verifying that quantities ordered are within the contract 

allowance. Army contractor requisitions that do not match the CFM Authorized Materiel 

Table will be processed by DAAS under the MCA waiver exception process or passed 

to the applicable MCA. For DLA CFM, processing will be as identified in C4.2.8.11.3. 

CFM requisitions for other Service contractors will be passed to the source of supply. 

NSNs listed in the table may be modified over the course of this agreement when 

appropriate Army contracting officer provides such authority. Updates to the authorized 

list will be collected, consolidated into one Excel file by the designated DLA Lead Center 

POC with proof of Army Contracting Officer (CO) concurrence and provided to 

Headquarters DLA Army Performance Based Logistics (PBL) action officer. DLA will 

coordinate updates to individual contractor lists with DLA DoD EMALL and DLA 

Transaction Services on a monthly basis. To optimize program changes, all additions to 

Army partnership lists will be made during an agreed-to monthly timeframe between 

DLA and support entities.

C4.2.10.11.3. DLA Transaction Services Processing of DLA CFM 

Transactions

C4.2.10.11.3.1. DLA Transaction Services will maintain a DLA 

CFM Authorized DoDAAC Table listing DLA contractor DoDAACs authorized to 

requisition CFM. DLA Transaction Services will populate or delete DoDAACs to/from 

the table as directed by DLA. Requisitions identifying a DLA-assigned U-series 

contractor DoDAAC as the bill-to activity will be edited against this table. DLA 

Transaction Services is required to edit all incoming DLMS 511R/511M/869F, (legacy 
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 12

80 record position A0_, A3_, A4_, AM_ and AT_ equivalent), transactions containing a 

U-series DoDAAC when identified as the bill-to activity against the DLA CFM Authorized 

DoDAAC Table. If matched to the table, then DAAS will route/pass the transaction 

based on established DAAS rules to the appropriate source of supply for further 

processing. If the U-series bill-to DoDAAC does not match the table, then DAAS will 

reject the transaction using Status Code DB. 

C4.2.10.11.3.2. DLA Transaction Services will capture any DLMS 

517G (DIC AX1) transactions containing a DLA U-series DoDAAC identified as the billto DoDAAC and match it against the DLA CFM Authorized DoDAAC Table. If the Useries bill-to-DoDAAC matches the table, then DAAS will respond with a DLMS 517G 

(DIC AX2) transaction with Advice Code 2M indicating the requisition is authorized. If 

the U-series bill-to-DoDAAC does not match the table, then DAAS will respond with a 

DLMS 517G (DIC AX2) transaction with Advice Code 2U indicating the requisition is not 

authorized.

C4.2.10.12. Preparation of DoD EMALL Requisitions by Contractors. 

Authorized contractors may establish DoD EMALL accounts to facilitate materiel 

requisition submissions. To register, go to https://dod-emall.dla.mil and click on New 

User Registration. Access to DoD EMALL is now fully Common Access Card 

(CAC)/Public Key Infrastructure (PKI) enforced. Details of the access requirements are 

listed on the registration pages of the EMALL site. Prior to establishing the account, the 

applicable contracting officer must ensure that the contractor is authorized access to 

Government supply sources and must agree to review monthly or quarterly reports 

prepared by the DoD EMALL monitoring contractor activity. The applicable contracting 

officer must also provide a list of approved NSN/part numbers associated with each 

account/contractor DoDAAC for Army authorized CFM. Army contractors will be 

processed under GFM/CFM controls as described.

C4.2.10.12.1. DoD EMALL will validate that contractors are authorized 

to purchase materiel from DoD supply sources as a prerequisite for submission of 

EMALL orders. DoD EMALL requisitions for GFM will be subjected to prescribed rules 

for MCA controls within DoD EMALL or within the DAAS. DoD EMALL CFM requisitions 

indicating corporate credit card method of payment are subject to special processing 

controls as described below. Additionally, CFM requisitions for Army authorized 

contractors will be validated to ensure that requisitioned NSNs or DoD managed part 

numbers are authorized regardless of the method of payment under CFM controls 

described above.

C4.2.10.12.2. The DoD EMALL program office will identify to DLA 

Transaction Services all contractors authorized access to Government materiel for 

purchase as CFM using a corporate credit card as the method of payment. DAAS will 

maintain these DoDAACs as an authorized contractor edit table (referenced hereafter 

as the DoD EMALL CFM Table) to be employed during initial processing and for DLMS 

517G processing.
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 13

C4.2.10.12.3. DoD EMALL requisitions for shipment to contractors using 

corporate purchase/credit card payment are assigned Signal Code B, Fund Code XP, 

and the supplemental address of the DoD EMALL DoDAAC (SP5200 or SC4210). This 

configuration identifies a Government DoDAAC as the bill-to activity, thereby triggering 

DAAS and the DoD Component source of supply processing systems to misinterpret 

such transactions as GFM requisitions. DAAS shall validate these transactions against 

existing GFM edits and the DoD EMALL CFM Table to determine appropriate action. If 

the contractor requisition does not contain a valid MCA identification code and the 

DoDAAC is not listed in the DoD EMALL CFM Table, DAAS shall reject with Status 

Code CL. If an MCA is identified by either a distribution code or a RIC, DAAS shall 

forward the requisition to the source of supply. The source of supply shall submit a 

DLMS 517G to DAAS for validation following GFM MCA procedures (including Army 

CFM). DAAS will recognize the EMALL supplemental address and again employ 

existing GFM edits and the DoD EMALL CFM Table to take appropriate action. If the 

validation using the DoD EMALL CFM Table identifies the contractor DoDAAC as 

authorized by the contracting officer for ordering CFM using corporate purchase/credit 

cards, then DLA Transaction Services shall validate the requisition and respond to the 

source of supply with a DLMS 517G Validation Response using Advice Code 2M 

indicating the requisition is valid. The source of supply shall continue processing. If the 

contractor DoDAAC is not contained on the DoD EMALL CFM Table, but the requisition 

contains a valid MCA code, then DLA Transaction Services shall forward the DLMS 

517G Validation Request to the MCA for validation. If the contractor DoDAAC is not 

contained on the DoD EMALL CFM Table, or does not match the CFM Authorized 

Materiel Table, when applicable, and the requisition does not contain a valid MCA code, 

then DAAS shall provide a DLMS 517G Validation Response with Status Code CL 

indicating the transaction is invalid. The source of supply shall reject the requisition. 

For DLA contractor credit card purchases (identified by a DLA-assigned U-series 

DoDAAC in the document number), DAAS processing rules shall be as described in this 

paragraph, except that the requisition shall be validated based upon the requisitioner 

DoDAAC matching to the DLA CFM Authorized DoDAAC Table.

C4.2.10.12.4. To support DoD requirements for oversight of materiel 

sold to contractors, the DoD EMALL program office will provide reports to monitor 

contractor activity. For contracts having a maximum total dollars ceiling, a DoD EMALL 

report will be provided to the contracting officer when the cumulative value of CFM 

ordered reaches 80 percent of the ceiling.

C4.2.10.13 Inventory Control Point/Integrated Materiel Management-Directed 

Shipment of Non-Requisitioned Government Furnished Materiel Based on a Bill of 

Materiel. ICP/IMM-directed shipments of GFM may be managed through the use of a 

Bill of Materiel (BOM) as identified under the terms of the DoD contract. In this context, 

the BOM identifies the raw materiels/component parts needed to 

assemble/manufacture/repair the end item or final product. Based on the unit of 

allowance, the number/amount of GFM component materiel needed to accommodate 

the total number of end items to be manufactured/assembled/repaired on a specific 

contract/purchase order, may be calculated and provided. This procedure eliminates 

the need for separate GFM requisitions for the component materiel and subsequent 
DLM 4000.25, Volume 2, Month XX, 20XX

Change 4

ADC 1097, Enclosure 2

Page 14

MILSTRIP MCA validation. Instead, this process allows the ICP/IMM to push the 

materiel to the contractor as required by schedule and/or usage.

C4.2.10.13.1. Upon contract award for production of an end item or final 

product, the BOM becomes the basis for determining the quantity of GFM required by 

the contractor. These deliveries will only include stocked raw materiel/component parts 

that the Government provides at no separate charge to the contractor for 

assembly/manufacture of the end item/final product. Under this process, the ICP/IMM 

will use internal control procedures to monitor consumption of raw materiel/component 

parts against the receipt of items awarded by contract.

C4.2.10.13.2. The ICP/IMM will prepare materiel release orders for 

stock shipment using document numbers based upon a DLA established DoDAAC. The 

ship-to location cited in the release order will identify the contractor DoDAAC authorized 

to receive GFM. The MRO will include the authorizing contract number, and the 

call/order and CLIN, when applicable. The storage activity will provide shipment 

confirmation to the ICP/IMM for monitoring GFM shipments and will prepare shipment 

status perpetuating applicable contract data. For contractors without capability to 

accept legacy 80 record position/DLMS transactions, status of the GFM component 

delivery will be provided upon request by the contractor. The assembled/manufactured 

end items may be shipped directly to customers or shipped to a storage location for 

future use.

C4.2.10.13.3. Use of the above business process does not relieve the 

ICP/IMM from a management reporting requirements required by DoD 4140.1-R, DoD 

Supply Chain Materiel Management Regulation. Material Receipt Acknowledgement is 

required for GFM, including pushed shipments, under MILSTRAP procedures.

C4.2.10.13.4. This process is discretionary and may not be applicable to 

all commodities and contracts requiring GFM. This process may only be used to 

support GFM requirements satisfied by the DoD Component issuing the contract (that 

is, by design, it does not support inter-Component materiel support).

[Intervening text not shown]
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 1

Enclosure 3

A. Update Chapter 11 to DLM 4000.25-1 to align with the new Chapter 26 in DLM 4000.25, 

Volume 2. Removed text is identified by double strikethroughs. New text is annotated with 

red, bold, italics.

C11. CHAPTER 11

CONTRACTOR ACCESS TO GOVERNMENT SOURCES 

OF SUPPLY

C11.1. GENERAL

C11.1.1. Purpose. This chapter prescribes policies and procedures for 

requisitioning government furnished materiel (GFM) by or for contractors from the 

DoD Supply System. These procedures establish guidelines to for requisitioners, and

authorized contractors and Services/Agencies (S/As) to obtain government furnished 

materiel (GFM) from DoD inventories to fulfill contract requirements.1 These 

procedures also support the use of MILSTRIP requisitioning by authorized contractors 

to obtain materiel from Government supply sources to be used as contractor-furnished 

materiel (CFM) under controls established by the authorizing Component and as 

specified in this chapter. Basic MILSTRIP requisitioning procedures are 

documented in DLM 4000.25-1, Chapter 2; those procedures are augmented by 

this chapter to identify additional requirements associated with GFM and CFM.

C11.1.2. Transactions. This chapter addresses the procedures to the 

following MILSTRIP legacy 80 record position transactions.

C11.1.2.1. The Requisition Transaction is identified by the DIC A01, A02, 

A04, A05, A0A, A0B, A0D, and A0E.

C11.1.2.2. The Passing Order Transaction is identified by the DIC A31, 

A32, A34, A35, A3A, A3B, A3D, and A3E.

C11.1.2.3. The Referral Order Transaction is identified by the DIC A41, 

A42, A44, A45, A4A, A4B, A4D, and A4E.

C11.1.2.4. The Requisition Modification Transaction is identified by the 

DIC AM1, AM2, AM4, AM5, AMA, AMB, AMD, and AME.

 1 Procedures to control access to DoD materiel inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to Approved MILSTRIP Change Letter (AMCL) 1A.
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 2

C11.1.2.5. The Requisition Follow-Up Transaction is identified by the 

DIC AF1, AF2, AF3, AF4, AF5, AFC, AFY, AT1, AT2, AT4, AT5, ATA, ATB, ATD, and 

ATE. 

C11.1.2.6. Reserved.

C11.1.2.7. Reserved.

C11.1.2.8. The GFM Validation Request is identified by the DIC AX1.

C11.1.2.9. The GFM Validation Response is identified by the DIC AX2.

C11.1.2.10. The Supply Status Transaction is identified by the DIC AE1, 

AE2, AE3, AE8, AE9, AEA, AEB, AED, and AEE. 

C11.1.2.11. The Requisition Cancellation Transaction is identified by the 

DIC AC1, AC2, AC3, AC4, and AC5.

C11.1.2.12. The Follow-Up on Requisition Cancellation Request 

Transaction is identified by the DIC AK1, AK2, AK3, AK4, AK5.

C11.1.2.13. The Shipment Status Transaction is identified by the DIC 

AS1, AS2, AS3, AS8, AU1, AU2, AU3, and AU8.

C11.1.2.14. The Materiel Obligation Validation Request Transaction is 

identified by the DIC AN1, AN2, AN3, AN4, AN5, AN9, and ANZ.

C11.1.2.15 The Materiel Obligation Validation Response Transaction is 

identified by the DIC AP1, AP2, AP3, AP4, AP5, AP8, AP9, APR, and APX.

C11.1.3. Establishing a Management Control Activity. The S/As shall must

assign a unique Routing Identifier Code routing identifier code (RIC) and distribution 

code to each management control activity (MCA) validating GFM requisitions.

C11.1.4. Violations. Any attempt to circumvent GFM/CFM validation 

requirements is sufficient cause to refer the violation to the appropriate criminal 

investigating activity to determine possible fraud, waste, and abuse. The sponsoring 

Service/Agency shall make must refer all violations referrals to criminal investigating

investigators and the activities or monitoring MCA based upon reports of rejected 

transactions or violations discovered during the post validation process.

C11.2. APPLICABILITY

C11.2.1. These procedures apply to all contractors and all S/A activities 

requisitioning GFM or CFM from DoD sources of supply. 

C11.2.2. Ammunition production is excluded from GFM control.
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 3

C11.3. PREPARATION OF REQUISITIONS AND RELATED TRANSACTIONS FOR 

GOVERNMENT MATERIEL FURNISHED TO CONTRACTORS

C11.3.1. Requisition Initiation. Requisitions for GFM may be initiated by the 

responsible S/A or, subject to the terms of the contract, by contractors. Requisitions for 

GFM shall will be prepared and initially submitted by GFM requisitioners, both 

contractors and S/As, using MILSTRIP transaction formats to the S/A MCA designated 

for monitoring the contract. Transmission through the Defense Automatic Addressing 

System (DAAS) shall will be utilized to the extent practical.

C11.3.2. Identifying Requisitions for GFM Controls. Requisitions and 

associated transactions containing an S/A code designated for contractors, as specified 

in Appendix AP2.2 (rp 30-35 Department of Defense activity address code 

(DoDAAC) in the document number or rp 45-50 if ship-to DoDAAC address), shall

will be processed under GFM controls and restrictions except when the signal and fund 

codes indicate that the issue will be for CFM with contractor reimbursement by other 

than an Army contractor. All Army contractor requisitions and associated transactions 

must be processed under GFM controls.

C11.3.3. Required Information. In addition to normal requisition data, GFM 

requisitions, including Referral and Passing Orders will shall contain the following:

C11.3.3.1. Document Identifier Codes (DlCs) A01, A02, A04, A05, A0A, A0B, 

A0D, A0E, A3_, and A4_ shall be in rp 1-3.

C11.3.3.1. RlC in rp 4-6 identifying the appropriate S/A of the MCA 

monitoring the contract, rp 4-6.

C11.3.3.2. For contractor Contractor generated requisitions, shall contain 

the appropriate contractor DoD activity address code (DoDAAC,) in rp 30-35.

C11.3.3.3. For S/A generated requisitions for GFM, shall contain the 

appropriate contractor ship-to DoDAAC, in rp 45-50.

C11.3.3.4. When applicable, a signal code in rp 51 to indicate issue without 

reimbursement, rp 51.

C11.3.3.5. When applicable, a fund code in rp 52-53 to indicate issue without 

reimbursement, rp 52-53.

C11.3.3.6. Contract Information. All GFM requisitions for or by 

contractors must identify appropriate contract data as required. 

C11.3.3.6.1. The last eight positions of the procurement instrument 

identification number (PIIN) is mandatory, rp 73-80.

C11.3.3.6.2. When applicable, the call order call/order number, in rp 

69-72.
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 4

C11.3.3.6.3. Reserved.

C11.3.3.6.4. At the option of the S/A, a three character manufacturing 

directive number (MDN), rp 54-56.

C11.3.3.7. GFM non-national stock number (NSN) requisitions shall be are

identified with an E in rp 68; the call order call/order number, if appropriate, in rp 69-72; 

and the last eight positions of the PIIN in rp 73-80 (the MDN is optional).

C11.4. SUBMISSION OF GOVERNMENT-FURNISHED MATERIEL REQUISITIONS 

AND RELATED TRANSACTIONS

C11.4.1. Frequency of submitting GFM requisitions is the prerogative of the 

requisitioner. GFM requisitions shall will be submitted, when necessary, to meet 

contract requirements.

C11.4.2. Initiating activities must submit all GFM requisitions (DIC A0_) and 

associated GFM transactions, regardless of origin (such as contractor or S/A 

initiated) shall be initially submitted to an the appropriate S/A MCA for validation.

C11.4.3. It is mandatory that GFM requisitions be forwarded regardless of origin, 

such as contractor or S/A initiated, to the appropriate S/A MCA for validation. After 

validating the GFM requisitions validation by the S/A MCA, the MCA shall forwards

validated requisitions to the inventory control point (ICP). The MCA may pass 

transactions internally when Where the MCA and ICP are collocated, internal passing 

of transactions is authorized. The MCA will send the transactions via DAAS when 

When the MCA and ICP are not collocated, the transmission should be via DAAS, 

where practical. In those instances where a Component is performing the 

procurement/contract writing for another Component that includes the authorization for 

a contractor to order or receive GFP GFM (or Army CFM), the Component providing 

the procurement/contracting service and the Component requesting the contract shall

will coordinate efforts to ensure that the requesting Component’s MCA has access to 

the necessary contract and applicable contract modification information to perform its 

management control and accountability functions over Government supply system 

materiel access.

C11.4.4. Modifier transactions are authorized for GFM requisitions only to modify 

the project code, priority designator (PD), advice code, and the required delivery date 

(RDD). Modifiers may not be used to change the ship-to/bill-to information

Supplementary Address (SUPADD) to a contractor’s SUPADD. Modifiers are subject to 

GFM controls and validation procedures.

C11.5. MANAGEMENT CONTROL ACTIVITY PROCESSING OF GOVERNMENTFURNISHED MATERIEL REQUISITIONS AND RELATED TRANSACTIONS

C11.5.1. The MCA shall must receive and validate GFM Requisitions (DICs 

A01, A02, A04, A05, A0A, A0B, A0D, and A0E), Passing Orders (DIC A3_), Referral 

Orders (DIC A4_), Requisition Follow-Ups (DIC AT_), and Requisition Modifiers
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 5

(DIC AM_ only for RDDs, project codes, PDS, and advice codes), based on the 

criteria furnished by procurement/contracting offices and as indicated in Table 

C11.T1. The MCA will make changes, reject, or continue the processing action on 

the GFM transactions. The MCA may also receive Supply Status (DIC AE_), 

Shipment Status (DIC AS_), and MOV Materiel Obligation Validation transactions 

(DICs AN_ and AP_), Requisition Follow-Ups (DICs AF_ and AK_), and Requisition

Cancellations (DIC AC_), and Follow-Ups on Requisition Cancellation Requests. 

All other DICs received by the MCA shall must be rejected with Status Code CR.

C11.5.2. Based upon criteria furnished by procurement/contracting offices, the 

MCA shall validate the data elements and codes in GFM transactions other than DICs 

AE_, AS_, AF_, AK_, AC_, AN_, and AP_, as indicated in Table C11.T1. The MCA 

shall make changes, reject, or continue processing action on the GFM transactions.

C11.5.2. The MCA shall will maintain requisition history files to serve as an 

auditable record of GFM transactions. In addition, the MCA shall will generate reports 

as required by DoD 4140.1-R, “DoD Supply Chain Materiel Management Regulation”, 

May 23, 2003.

C11.5.3. Under emergency conditions, such as a potential contract work 

stoppage, the MCA may receive telephonic requisitions, with PDs 01-08, for GFM. 

When this occurs, the MCA may telephone the requisitions to the appropriate source of 

supply (SoS) and validate the requirements afterward. If the post validation process 

reveals that the requisitioner is not authorized GFM, the following actions shall must be 

taken:

C11.5.3.1. Submit cancellation requests to the appropriate SoS.

C11.5.3.2. Advise the appropriate criminal-investigating agency for 

determination of fraud waste, and abuse.

C11.5.4. Upon completion of the validation process, the MCA shall will identify 

itself as the RIC-From organization in the transaction, make the following changes 

and forward the requisitions, or internal requisition transactions (optional only when the 

MCA and SoS are collocated in the same distribution system), cancellations, follow-ups, 

requisition modifiers, passing orders, or referral orders to the applicable SoS through 

DAAS, if practical:

C11.5.4.1. Insert the RIC-To of the SoS, in rp 4-6.

C11.5.4.2. Insert the distribution code of the MCA validating the transaction, 

in rp 54.

C11.5.4.3. Where required by the Component, the MCA may also 

perpetuate or the MDN consisting of the MCA’s distribution code in rp 54 and two other 

alpha/numeric characters as assigned in rp 55-56.

C11.5.4.4. Delete the data in rp 69-80.
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 6

C11.5.5.4. If required by the S/A, insert the RIC of the validating MCA in rp 

74-76 of the requisition. The MCA RIC shall be in rp 74-76 of the passing order or 

referral order.

C11.5.5. MCAs in receipt of DIC AX1 GFM Validation Request transactions 

(Appendix AP3.52) shall will validate the data contained therein. This validation 

process must be completed and a DIC AX2 GFM Validation Response transaction 

created and forwarded to the applicable SoS within 15 days of receipt of the DIC AX1

GFM Validation Request transaction. The format for the DIC AX2 transaction is 

contained in Appendix AP3.53. The DIC AX1 results of the validation will be 

documented in the GFM Validation Response shall be validated as follows:

C11.5.5.1. If the requisition has been previously validated, the DIC AX2 

transaction shall contain cite Advice Code 2M.

C11.5.5.2. If the requisition has not been previously validated and the call 

order call/order number/PIIN (or MDN, if required by the Component in addition to the 

call order call/order number/PIIN) is not present, the DIC AX2 transaction shall contain

cite Advice Code 2U.

C11.5.5.3. If the requisition has not been previously validated and the call 

order call/order number/PIIN is present, validate the data elements as indicated in 

Table C11.T1, and generate the DIC AX2 transaction GFM Validation Response as 

follows:

C11.5.5.3.1. If the validation process reveals that the contract is not 

valid, the DIC AX2 shall contain respond with Advice Code 2U.

C11.5.5.3.2. If the validation process reveals that the requested quantity 

exceeds the contract authorized quantity, the DIC AX2 shall contain respond with

Advice Code 2R and indicate the quantity approved for issue that can be supplied 

shall be entered in rp 25-29.

C11.5.5.3.3. If the validation process reveals that the requested quantity 

exceeds the contract authorized quantity, DIC AX2 shall contain respond with Advice 

Code 2Q and indicate the total quantity is disapproved for issue.

C11.5.5.3.4. If the validation process reveals that the requested item, or 

requisitioner contractor, or DoDAAC in rp 45-50, is not authorized GFM under a valid 

contract, the DIC AX2 shall contain respond with Advice Code 2V.

C11.5.5.3.5. If the validation process reveals that the requested item is 

authorized, the DIC AX2 shall contain respond with Advice Code 2M.

C11.5.6. MCAs in receipt of DIC AE_ transactions Supply Status with Status 

Code BF from the SoS shall will review for establishment of a valid requisition. If a 

valid requisition exists, a Requisition Follow-Up (DIC AT_) transaction shall will be 

generated. If a valid requisition does not exist, a report shall will be generated for 
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 7

internal review. Subsequent receipt of a valid requisition shall will be processed under 

the procedures/validation process indicated in Table C11.T1.

Table C11.T1. MCA Validation Process for GFM Transactions

CODE OR DATA ELEMENT VALIDATION OF ENTRY

Document Identifier Code If Requisition, Referral or Passing Order (DIC is A01, A02, A04, 

A05, A0A, A0B, A0D, A0E, AT_, A3_, A4_), Requisition 

Modification or (AM_) (for RDD, project code PD, or advice code), 

Requisition Follow-Up (DIC AT_) continue the GFM validation.

Stock Number Verify item requisitioned against a valid contract to determine 

authority for issue to the contractor. If blank, incorrect, or not 

authorized, reject with Status Code DN.

Unit of Issue Validate the unit of issue in conjunction with the quantity to ensure 

that the requisitioned quantity does not exceed the authorized 

quantity. If quantity is excessive, see validation of quantity field. 

(Note: If a change of unit pack has occurred, appropriate adjustment 

should be made for authorized quantity.)

Quantity If ordered item is authorized by contract, verify the quantity. If blank 

or invalid, reject with Status Code CD. If the requisitioned quantity 

exceeds the remaining authorized quantity, reject the quantity 

exceeding the authorized quantity with Status Code DJ. If authorized 

quantity has been exhausted by previous requisition(s), reject total 

requisitioned quantity with Status Code DQ.

Requisitioner If blank or incorrect, discard. If not authorized, reject with Status 

Code DN.

Document Number If blank or incorrect, reject with Status Code CD.

Supplementary Address If contractor DoDAAC, and affected by signal code, and incorrect or 

not authorized, reject with Status Code DN.

Signal and Fund If signal and fund codes indicate issues without contractor 

reimbursement, process as GFM; otherwise, consider as CFM. CFM 

requisitions, except for Army, are not subject to MCA review. All 

Army contractor requisitions and associated transactions shall will be 

processed under GFM controls. DAAS shall will respond to requests 

for MCA review for Army CFM under special processing rules 

authorized by the Army.

Manufacturer’s Directive 

Number

If the MDN option is required by the Component and the MDN 

equates to a valid contract number, validate; otherwise, reject with 

Status Code DB.

Contract Call Order Number If specified by S/A contract, and entry is blank or incorrect, reject with 

Status Code DB.

Last eight positions of the

Procurement Instrument 

Identification Number

If blank, or contract is not on MCA file, or contract has expired, reject 

with Status Code DB. (The last eight positions of the PIIN are 

mandatory.)

C11.6. SOURCE OF SUPPLY PROCESSING OF GOVERNMENT-FURNISHED 

MATERIEL REQUISITIONS AND RELATED TRANSACTIONS
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 8

C11.6.1. An SoS receiving GFM requisitions, requisition modifiers, passing 

orders, referral orders, requisition follow-ups, and requisition cancellations, 

irrespective regardless of the method of transmission, shall will process such 

transactions under GFM procedures. A SoS in receipt of GFM requisitions for items not 

managed by their activities shall will reject the requisitions with Status Code CH. The 

SoS shall will edit the GFM transactions for the prescribed data elements and codes in 

GFM transactions and correct, continue processing actions, or provide the appropriate

reject, as appropriate status. See Appendix AP2.16, this manual, for applicable status 

codes.

C11.6.2. The SoS shall will validate all GFM transactions. Subsequent to 

performing the edits in Chapter 3, A SoS in receipt of requisitions, passing orders, 

referral orders, requisition modifiers, or requisition follow-ups being treated as 

requisitions, containing a contractor’s Service/Agency code under Appendix AP2.2, in 

rp 30-35 or in rp 45-50, if ship-to address, shall will perform the SoS/MCA validation 

process except when the signal and fund codes indicate that the issue will be with 

contractor reimbursement by other than an Army contractor. All Army contractor 

requisitions and associated transactions shall will be processed under GFM/CFM 

controls. (Note: The SoS /MCA validation process is not required when an internal 

requisition transaction is received from a collocated MCA in the same distribution 

system. However, the SoS are required to must have safeguards in place to ensure 

that only internal transactions generated by the collocated MCA are 

accepted/processed.)

C11.6.3. Under emergency conditions, the SoS may receive telephonic 

requisitions (PD 01-08) from the MCA or requisitioner. These requisitions The SoS may 

be processed these requisitions for immediate supply action. Subsequent to taking 

immediate supply action; the GFM validation process shall will be performed. If the DIC 

AX2 transaction GFM Validation Response is not received within 15 days of the DIC 

AX1 transaction GFM Validation Request or the advice code indicates that the 

transaction is not authorized, refer the incident shall be referred to the appropriate 

criminal-investigating agency.

C11.6.4. The SoS /MCA validation process is as follows:

C11.6.4.1. For each GFM requisition or transaction that is treated as a 

requisition, the SoS shall will employ one of the following options:

C11.6.4.1.1. Create and forward a DIC AX1 transaction GFM 

Validation Request to the MCA identified in rp 74-76 or rp 54 of identified by RIC or 

distribution code in the requisitioner’s transaction. The format for the DIC AX1 

transaction is in Appendix AP3.52. If rp 74-76 and rp 54 of the MCA RIC and 

distribution code requisitioner’s transaction are blank or invalid, the transaction shall 

be rejected with Status Code CL.

C11.6.4.1.2. Create and forward a DIC AX1 transaction GFM 

Validation Request to DAAS DLA Transaction Services regardless of the coding 
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 9

contained in rp 74-76 or rp 54 of even if an MCA is contained in the requisitioner’s 

transaction. The format for DIC AX1 transaction is in Appendix AP3.52. DLA 

Transaction Services will perform edits regarding validity of the MCA data in rp 74-76 

or rp 54 shall be performed by DAAS under Paragraph C11.7.2..

C11.6.4.1.3. Utilize Use a combination of the above options: one for 

intra-Component Service transactions and one for inter-Component Service

transactions.

C11.6.4.2. Suspend further supply support action on the requisitioner’s 

transaction shall be suspended pending receipt of the DIC AX2 GFM Validation 

Response or until 15 days have elapsed from the date of the DIC AX1 transaction GFM 

Validation Request, whichever occurs first.

C11.6.4.3. If the DIC AX2 transaction GFM Validation Response is not 

received and 15 days have elapsed, reject the requisitioner’s transaction shall be 

rejected with Status Code DR.

C11.6.4.4. Upon receipt of the DIC AX2 transaction GFM Validation 

Response, the SoS shall will process the suspended transaction using instructions 

provided by the advice/status code in rp 65-66.

C11.6.4.4.1. If the Advice Code is 2U, the suspended transaction shall 

be rejected with Status Code DB.

C11.6.4.4.2. If the Advice Code is 2R, the suspended transaction shall 

be processed for the approved quantity indicated in rp 25-29 of the DIC AX2 

transaction the GFM Validation Response. Reject the quantity difference between the 

suspended transaction and the DIC AX2 transaction shall be rejected GFM Validation 

Response with Status Code DJ.

C11.6.4.4.3. If the Advice Code is 2Q, the suspended transaction shall 

be rejected with Status Code DQ.

C11.6.4.4.4. If the Status Code is CL, the suspended transaction shall 

be rejected with Status Code CL.

C11.6.4.4.5. If the Advice Code is 2V, the suspended transaction shall 

be rejected with Status Code DN.

C11.6.4.4.6. If the Advice Code is 2M, the suspended transaction shall 

be processed under applicable SoS procedures.

C11.6.4.4.7. If the advice/status code is blank or invalid, the suspended 

transaction shall be rejected with Status Code DR.

C11.6.4.5. If a DIC AX2 transaction GFM Validation Response is received,

and there is a record of the requisition, but a DIC AX1 transaction GFM Validation 
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 10

Request has not been submitted, the DIC AX2 transaction shall be discarded the GFM 

Validation Response and generate a DIC AX1 transaction shall be generated GFM 

Validation Request.

C11.6.4.6. If a DIC AX2 transaction GFM Validation Response is received,

and there is no record of the requisition, a DIC AE_ transaction with generate a Supply 

Status with Status Code BF shall be generated.

C11.6.5. Follow-ups shall be processed to determine the current status of 

previously submitted requisitions or cancellation requests. Time standards for 

dispatching status in reply to follow-ups are as indicated in Chapter 3, Paragraph C3.21.

C11.6.6. Sources of Supply in receipt of DIC AT_ transactions containing a 

service code designated for contractors as specified in Appendix AP2.2, in rp 30-35 or 

45-50, if ship-to address, and having no record of the original requisition, shall create 

and forward a DIC AX1 transaction except when the signal and fund codes indicate that 

the issue shall be with contractor reimbursement by other than an Army contractor. All 

Army contractor requisitions and associated transactions shall be processed under 

GFM controls. The processing of the DIC AX1 transaction and the responding DIC AX2 

transactions shall be accomplished under procedures contained in this chapter.

C11.7. DEFENSE AUTOMATIC ADDRESSING SYSTEM PROCESSING OF 

GOVERNMENT-FURNISHED MATERIEL TRANSACTIONS

C11.7.1. DAAS shall will pass all GFM requisitions and related transactions to the 

RIC in rp 4-6 if the RIC identifies an established identified MCA using the MCA RIC or 

the distribution code provided in the transaction. If the RIC is not an established 

MCA, and the distribution code identifies an established MCA or the RIC in rp 74-76 

identifies a valid MCA, DAAS shall route the transaction. If the RIC is not an 

established MCA, and the distribution code does not identify an established MCA or the 

RIC in rp 74-76 does not identify a valid MCA, the transaction shall be rejected with 

Status Code CL.

C11.7.2. DAAS shall will pass all DIC AX1 transactions GFM Validation 

Requests to the activity identified with a valid MCA using the MCA RIC or distribution 

code provided in the transaction RIC in rp 74-76, or MCA distribution code in rp 54. 

If the DIC AX1 transaction has an MCA is invalid, MCA RIC and an invalid MCA 

distribution code, a DIC AX2 generate a GFM Validation Response with Status Code 

CL shall be generated and forwarded to the SoS.

C11.7.3. DAAS shall will pass all DIC AX2 transactions GFM Validation 

Responses to the SoS identified by the RIC in rp 4-6.

C11.7.4. DAAS Special Processing for DLA Energy.

2

 The DLA Transactions 

Services will perform the DIC AX1/AX2 GFM Validation Request/Response validation 

 2 Procedures for exception processing for GFM for packaged fuel additives managed by DLA last reported as a 

delayed implementation by DLA. Refer to Approved DLMS Change (ADC) 211.
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 11

on behalf of DLA Energy for selected requisitioning/bill-to activities and stock numbers 

in accordance with the following procedures:

C11.7.4.1. DLA Transaction Services shall will maintain a DLA Energy GFM 

Table that identifies DLA Energy-established U series contractor DoDAACs authorized 

to requisition specified additive NSNs. The authorized DLA Energy point of contact 

shall will provide to DLA Transaction Services the U series DoDAAC/NSN combinations 

for the DLA Energy GFM Table.

C11.7.4.2. DLA Energy-sponsored orders for GFM shall will specify 

DoDAAC SJ0630 (Americas East), SJ0606 (Americas West), SJ0629 (Middle East), 

SJ0601 (Europe), SJ0600 (Pacific) and SCO600 SC0600 (DLA Energy for UC 

locations) as the requisitioner/bill-to activity. They shall will contain a U series 

DODAAC designated as the ship-to activity, and contain the DLA Energy assigned 

MDN.

C11.7.4.3. DAAS shall will route requisitions and requisition related 

transactions (DIC A0_/AM_/AT_/A3_/A4_e.g., Requisition, Requisition Modification, 

Requisition Follow-Up, Referral Orders, and Passing Orders) to the SoS for the 

NSN ordered, and the SoS shall will generate and transmit the MILSTRIP required 

DIC AX1, ICP GFM Validation Request, to DAAS.

C11.7.4.4. DAAS shall will capture any DIC AX1 GFM Validation Requests

containing DoDAAC SJ0630, SJ0606, SJ0629, SJ0601, SJ0600 or SCO600 SC0600

(for UC locations) as the requisitioner/bill to and a U-series DoDAAC as the ship-to and 

match it against the DESC DLA Energy GFM Table. If a table match is made by Useries DoDAAC and NSN, then DAAS shall will respond to the SoS with a DIC AX2, 

MCA GFM Validation Response, with an advice code 2M, indicating the order is 

authorized for processing. If no match, DAAS shall will respond with DIC AX2, a GFM 

Validation Response with Advice Code 2V, indicating the order is not authorized for 

processing.

C11.7.4.5. The SoS shall will process the DIC AX2 GFM Validation 

Response and either honor the order or reject the suspended transaction using Status 

Code DN, based on the advice code provided by DAAS.

C11.7.5. DAAS Special Processing for Army.

3

 Pending implementation of MCA 

procedures in Army systems, DLA Transaction Services shall will assist the Army by 

performing the DIC AX1/AX2 validation GFM Validation Requests/Response

requirement for the Army wholesale MCAs and recording all transactions into a history 

file for eventual processing to the appropriate MCA using the following procedures:

C11.7.5.1. Process all DIC A0_ Army contractor identified requisitions (DIC 

A0_) with the below listed first two positions of the DoDAAC in the document number 

or ship-to DoDAAC to the applicable Army MCA. Contractor requisitions with other 

 3 Procedures to control access to DoD material inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to AMCL 1A.
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 12

than the DoDAAC entries indicated are considered Army retail and will be routed to the 

proper SoS with the DAAS RIC “SGA” or “SHA” entered into rp 74-76 identified as the 

MCA.

C11.7.5.1.1. If rp 30-31 or rp 45-46 the first two positions of the 

document number or ship-to DoDAAC are CB, pass to RIC A81 (TACOM MCA)

C11.7.5.1.2. If rp 30-31 or rp 45-46 the first two positions of the 

document number or ship-to DoDAAC are CL, pass to RIC A82 (AMCOM MCA).

C11.7.5.1.3. If rp 30-31 or rp 45-46 the first two positions of the 

document number or ship-to DoDAAC are CG, pass to RIC A83 (CECOM MCA).

C11.7.5.1.4. If rp 30-31 or rp 45-46 the first two positions of the 

document number or ship-to DoDAAC are CM, pass to RIC A84 (TACOM MCA)

C11.7.5.1.5. If rp 30-31 or rp 45-46 the first two positions of the 

document number or ship-to DoDAAC are CK, pass to RIC A85 (TACOM MCA).

C11.7.5.1.6. If rp 30-31 or rp 45-46 the first two positions of the 

document number or ship-to DoDAAC are CH, pass to RIC A86 (AMCOM MCA)

C11.7.5.2. For DIC AM_, Requisition Modification and DI AT_ Requisition 

Follow-Up transactions, containing a valid MCA distribution code as identified below, 

the DAAS RIC “SGA” or “SHA” will be entered into rp 74-76 the MCA field and routed 

to the appropriate SoS. If a valid MCA is not in 54 identified and the transaction 

contains the entries cited above in the first two positions of the document number 

or ship-to DoDAAC for rp 30-31/2 or rp 45-46/7, the transaction will be passed to the 

appropriate MCA. If none of these conditions apply, the transaction will be considered 

retail and be routed to the appropriate SoS with the DAAS RIC “SGA” or “SHA” entered 

into the MCA field rp 74-76. The following are valid MCA distribution codes:

C11.7.5.2.1. I (India) - TACOM MCA

C11.7.5.2.2. L (Lima) - AMCOM MCA

C11.7.5.2.3. P (Papa) - CECOM MCA

C11.7.5.2.4. S (Sierra) - TACOM MCA

C11.7.5.2.5. Y (Yankee) - TACOM MCA

C11.7.5.2.6. E (Echo) - AMCOM – MCA

C11.7.5.2.7. 8 (Eight) - USACEA MCA 

C11.7.5.3. Upon receipt of DIC AX1 a GFM Validation Request

transactions, a DIC AX2 GFM Validation Response transaction shall will be generated 
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 13

with Status Code 2M and returned to the RIC in rp 4-6 of the DI AX1 SoS submitting 

the GFM Validation Request transaction.

C11.8. CONTRACTOR REQUISITIONS FOR CONTRACTOR-FURNISHED 

MATERIEL

C11.8.1. Requisitions for materiel from a Government supply SoS for shipment to 

contractors that identify the contractor as the bill-to activity are not subject to MILSTRIP

GFM MCA controls, with the exception of Army contractor requisitions to which MCA 

controls are applicable. DAAS shall perform the validation of will validate transactions 

for Army contractor requisitions of CFM for those items that contractors are authorized 

to requisition as CFM as specified in this chapter, and for nonwholesale level supply as 

designated by the contractor-series DoDAAC under Appendix AP 2.2, Service and 

Agency Codes. DoD Components shall will establish appropriate procedures for 

oversight of CFM requisitions in accordance with the Federal Acquisition Regulation.

C11.8.2. DAAS Processing of CFM Transactions. The process described in this 

paragraph provides mandatory CFM controls for CFM requisitions where the bill-to 

activity, as identified in the requisition, is an Army contractor and the SoS is DLA. This 

process is optional for other Services and may be expanded to include other SoS if 

needed. 

C11.8.2.1. DAAS shall will maintain a list of Service/Agency authorized 

contractor DoDAACs and the associated NSNs/DoD-managed part numbers for which 

these contractors may submit CFM requisitions on a CFM Authorized Materiel Table for 

use in validating requisitions regardless of method of payment. 

C11.8.2.2. CFM contractor transactions that match the CFM Authorized 

Materiel Table by DoDAAC, but do not match by NSN or part number shall will be 

rejected with Status Code CL; requisitions that match on DoDAAC and NSN/part 

number shall be processed as valid. 

C11.8.2.3. DAAS shall will enter the DAAS RIC SGA or SHA into rp 74-76 as 

the validating MCA. 

C11.8.2.4. DAAS shall will perform AX1/AX2 the GFM Validation 

Request/Response validation requirement for authorized CFM requisitions that match 

to the CFM Authorized Materiel Table. 

C11.8.2.5. DAAS shall will furnish CFM reports upon request for use by the 

contracting officer in verifying that quantities ordered are within the contract allowance.

C11.8.2.6. Army contractor requisitions that do not match the CFM 

Authorized Materiel Table shall will be processed by DAAS under the MCA waiver 

exception process or passed to the applicable MCA as described in Paragraph C11.7.5.

C11.8.2.7. For DLA CFM, DAAS processing will be as identified in C11.8.3.
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 14

C11.8.2.8. CFM requisitions for other Service contractors shall will be 

passed to the appropriate SoS. 

C11.8.2.9. NSNs listed in the CFM Authorized Materiel table may be 

modified over the course of this agreement when the appropriate Army contracting 

officer provides such authority. Updates to the authorized list shall will be collected, 

consolidated into one Microsoft Excel file by the designated DLA Lead Center point of 

contact with proof of Army Contracting Officer concurrence and provided to 

headquarters (HQ) DLA Army Performance Based Logistics (PBL) action officer. HQ 

DLA shall will coordinate updates to individual contractor lists with DLA DoD EMall and 

DLA Transaction Services on a monthly basis. To optimize program changes, all 

additions to Army partnership lists shall will be made during an agreed-to monthly timeframe between DLA and support entities.

C11.8.3. DLA Transaction Services Processing of DLA CFM Transactions

C11.8.3.1. DLA Transaction Services shall will maintain a DLA CFM 

Authorized DoDAAC Table listing DLA contractor DoDAACs authorized to requisition 

CFM. DLA Transaction Services shall will populate or delete DoDAACs to/from the 

table as directed by DLA. Requisitions identifying a DLA-assigned U-series contractor 

DoDAAC as the bill-to activity shall will be edited against this table. 

C11.8.3.2. DLA Transaction Services is required to must edit all incoming 

MILSTRIP DIC A0_, A3_, A4_, AM_ and AT_ (DLMS equivalent DLMS 

511R/511M/869F) Requisitions Passing Order, Referral Order, Requisition 

Modification, and Requisition Follow-Up transactions containing a U-series DoDAAC 

when identified as the bill-to activity against the DLA CFM Authorized DoDAAC Table.

C11.8.3.2.1. If matched to the table, then DAAS shall will route/pass the 

transaction based on established DAAS rules to the appropriate SoS for further 

processing. 

C11.8.3.2.2. If the U-series bill-to DoDAAC does not match the table, 

then DAAS shall will reject the transaction using Status Code DB. 

C11.8.3.3. DLA Transaction Services shall will capture any DIC AX1 (DLMS 

517G ) GFM Validation Request transactions containing a DLA U-series DoDAAC 

identified as the bill-to DoDAAC and match it against the DLA CFM Authorized DoDAAC 

Table. 

C11.8.3.3.1. If the U-series bill-to-DoDAAC matches the table, then 

DAAS shall will respond with a DIC AX2 (DLMS 517G) GFM Validation Response

transaction with Advice Code 2M indicating the requisition is authorized. 

C11.8.3.3.2. If the U-series bill-to-DoDAAC does not match the table, 

then DAAS shall will respond with a DIC AX2 (DLMS 517G)) GFM Validation 

Response transaction with Advice Code 2U indicating the requisition is not authorized.
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 15

C11.9. PREPARATION OF DOD EMALL REQUISITIONS BY CONTRACTORS.

C11.9.1. Account Setup. Authorized contractors may establish DoD EMALL 

accounts to facilitate materiel requisition submissions. To register, go to https://dodemall.dla.mil and click on “New User Registration”. Access to DoD EMALL is fully 

Common Access Card (CAC)/Public Key Infrastructure (PKI) enforced. Details of 

the access requirements are listed on the registration pages of the EMALL site. 

Prior to establishing the account, the applicable contracting officer must ensure that the 

contractor is authorized access to Government supply sources and must agree to 

review monthly or quarterly reports prepared by the DoD EMALL monitoring contractor 

activity. The applicable contracting officer must also provide a list of approved NSN/part 

numbers associated with each account/contractor DoDAAC for Army authorized CFM. 

Army contractors shall will be processed under GFM/CFM controls as described.

C11.9.2. Contractor GFM/CFM Validations. DoD EMALL shall will validate that 

contractors are authorized to purchase materiel from DoD supply sources as a 

prerequisite for submission of EMALL orders. 

C11.9.2.1. DoD EMALL requisitions for GFM shall be subjected to prescribed 

rules for MCA controls within DoD EMALL or within DAAS. 

C11.9.2.2. DoD EMALL CFM requisitions indicating corporate credit card 

method of payment are subject to special processing controls as described in C11.9.2.

below. 

C11.9.2.3. Additionally, CFM requisitions for Army authorized contractors 

shall will be validated to ensure that requisitioned NSNs or DoD managed part numbers 

are authorized regardless of the method of payment under CFM controls described 

above.

C11.9.3. Corporate Credit Card Usage. 

C11.9.3.1. The DoD EMALL program office shall will identify to DLA 

Transaction Services all contractors authorized access to Government materiel for 

purchase as CFM using a corporate credit card as the method of payment. 

C11.9.3.2. DAAS shall will maintain these DoDAACs as an authorized 

contractor edit table (referenced hereafter as the DoD EMALL CFM Table) to be 

employed during initial processing and for DIC AX1 GFM Validation Request

processing.

C11.9.4. Corporate Credit Card CFM Purchases and DAAS Processing. DoD 

EMALL requisitions for shipment to contractors using corporate credit card payment are 

assigned Signal Code B, Fund Code XP, and the SUPADD ship-to DoDAAC 

perpetuated to the supplementary address of the DoD EMALL DoDAAC (SP5200 or 

SC4210). This configuration identifies a Government DoDAAC as the bill-to activity, 

thereby triggering DAAS and the DoD Component SoS processing systems to 

misinterpret such transactions as GFM requisitions. 
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 16

C11.9.4.1. DAAS shall will validate these transactions against existing GFM 

edits and the DoD EMALL CFM Table to determine appropriate action. 

C11.9.4.2. If the contractor requisition does not contain a valid MCA 

identification code and the DoDAAC is not listed in the DoD EMALL CFM Table, DAAS 

shall will reject with Status Code CL. 

C11.9.4.3. If an MCA is identified by either a distribution code in rp 54 or a 

RIC in rp 74-76, DAAS shall will forward the requisition to the SoS. 

C11.9.4.3.1. The SoS shall will submit a DIC AX1 GFM Validation 

Request to DAAS for validation following GFM MCA procedures (including Army CFM).

C11.9.4.3.2. DAAS shall will recognize the EMALL SUPADD

supplementary address and again employ existing GFM edits and the DoD EMALL 

CFM Table to take appropriate action. 

C11.9.4.3.3. If the validation using the DoD EMALL CFM Table 

identifies the contractor DoDAAC as authorized by the contracting officer for ordering 

CFM using corporate credit cards, then DLA Transaction Services shall will validate the 

requisition and respond to the SoS with a DIC AX2 GFM Validation Response using 

Advice Code 2M indicating that the requisition is valid. The SoS shall will continue 

processing. 

C11.9.4.3.4. If the contractor DoDAAC is not contained on the DoD 

EMALL CFM Table, but the requisition contains a valid MCA code, then DLA 

Transaction Services shall will forward the DIC AX1 GFM Validation Request to the 

MCA for validation. 

C11.9.4.3.5. If the contractor DoDAAC is not contained on the DoD 

EMALL CFM Table or does not match the CFM Authorized Materiel Table, when 

applicable, and the requisition does not contain a valid MCA code, then DAAS shall will

provide a DIC AX2 GFM Validation Response with Status Code CL indicating that the 

transaction is invalid. The SoS shall reject the requisition. 

C11.9.4.4. For DLA contractor credit card purchases (identified by a DLAassigned U-series DoDAAC in the document number), DAAS processing rules shall will

be as described in this paragraph, except that the requisition shall will be validated 

based upon the requisitioner DoDAAC matching to the DLA CFM Authorized DoDAAC 

Table.

C11.9.5. DoD EMALL Reports. To support DoD requirements for oversight of 

materiel sold to contractors, the DoD EMALL program office shall will provide reports to 

monitor contractor activity. For contracts having a maximum total dollar ceiling, a DoD 

EMALL report shall will be provided to the contracting officer when the cumulative value 

of CFM ordered reaches 80 percent of the ceiling.
DLM 4000.25-1, Month XX, 20XX

Change 4

ADC 1097, Enclosure 3

Page 17

C11.10. INVENTORY CONTROL POINT/INTEGRATED MATERIEL MANAGERDIRECTED SHIPMENT OF NONREQUISITIONED GOVERNMENT-FURNISHED 

MATERIEL BASED ON A BILL OF MATERIEL. 

C11.10.1. ICP/integrated materiel manager (IMM)-directed shipments of GFM may 

be managed through the use of a bill of materiel (BOM) as identified under the terms of 

the DoD contract. In this context, the BOM identifies the raw materials/component 

parts needed to assemble/manufacture/repair the end item or final product. Based on 

the unit of allowance, the number/amount of GFM component materiel needed to 

accommodate the total number of end items to be manufactured/assembled/repaired on 

a specific contract/purchase order may be calculated and provided. This procedure 

eliminates the need for separate GFM requisitions for the component materiel and 

subsequent MILSTRIP MCA validation. Instead, this process allows the ICP/IMM to 

push the materiel to the contractor as required by schedule and/or usage.

C11.10.2. Upon contract award for production of an end item or final product, the 

BOM becomes the basis for determining the quantity of GFM required by the contractor. 

These deliveries shall will only include stocked raw material/component parts that the 

Government provides at no separate charge to the contractor for assembly/manufacture 

of the end item/final product. Under this process, the ICP/IMM shall will use internal 

control procedures to monitor consumption of raw material/component parts against the 

receipt of items awarded by contract.

C11.10.3. The ICP/IMM shall will prepare materiel release orders for stock 

shipment using document numbers based upon a DLA-established DoDAAC. The shipto location cited in the release order shall identify the contractor DoDAAC authorized to 

receive GFM. The storage activity shall will provide shipment confirmation to the 

ICP/IMM for monitoring GFM shipments and shall will prepare shipment status. For 

contractors without capability to accept legacy 80 record position/DLMS transactions, 

status of the GFM component delivery shall will be provided upon request by the 

contractor. The assembled/manufactured end items may be shipped directly to 

customers or shipped to a storage location for future use.

C11.10.4. Use of the above business process does not relieve the ICP/IMM from 

management reporting requirements required by DoD 4140.1-R, DoD Supply Chain 

Materiel Management Regulation. Materiel Receipt Acknowledgement is required for 

GFM, including pushed shipments, under MILSTRAP procedures.

C11.10.5. This process is discretionary and may not be applicable to all 

commodities and contracts requiring GFM. This process may only be used to support 

GFM requirements satisfied by the DoD Component issuing the contract (that is, by 

design, it does not support inter-Component materiel support).