Volume 2
Volume 2
Volume 2
25, Volume 2
VOLUME 2
SUPPLY STANDARDS
AND PROCEDURES
TABLE OF CONTENTS
VOLUME 2: SUPPLY STANDARDS AND PROCEDURES
PAGE
TABLE OF CONTENTS…………………………………………………………………..TOC-1
CHAPTER 1 INTRODUCTION
C1.1 GENERAL ............................................................................................ C1-1
C1.2 POLICY ................................................................................................ C1-1
C1.3 APPLICABILITY ................................................................................... C1-1
C1.4 SUPPLY PROCESS REVIEW COMMITTEE ....................................... C1-1
C1.5 SUPPLY DISCREPANCY REPORTING PRC ..................................... C1-2
C1.6 JOINT PHYSICAL INVENTORY WORKING GROUP .......................... C1-2
C1.7 NONCOMPLIANCE.............................................................................. C1-2
C1.8 TRANSACTION REVERSAL ............................................................... C1-2
C1.9 TRANSACTION REJECTION .............................................................. C1-3
C1.10 MILITARY STANDARD REQUISITIONING AND ISSUE
PROCEDURES .................................................................................... C1-3
C1.11 MILITARY STANDARD TRANSACTION REPORTING AND
ACCOUNTABILITY PROCEDURES .................................................... C1-4
CHAPTER 28 RESERVED
APPENDICES
APPENDIX 1 - FORMS
AP1 FORMS INDEX .................................................................................. AP1-I
AP1.1 INVENTORY CONTROL EFFECTIVENESS REPORT
AMMUNITION) DD FORM 2338-1……………………………… ....... AP1.1-1
AP1.2 INVENTORY CONTROL EFFECTIVENESS REPORT
(GENERAL SUPPLIES) DD FORM 2338-2 .................................... AP1.2-1
APPENDIX 2 - CODES
AP2 CODES INDEX .................................................................................. AP2- I
AP2.1 DOCUMENT IDENTIFIER CODES ................................................ AP2.1-1
AP2.2 TYPE OF PHYSICAL INVENTORY/TRANSACTION
HISTORY CODES .......................................................................... AP2.2-1
AP2.3 OWNERSHIP CODES ................................................................... AP2.3-1
TABLES
Table Title
C2.T1 DLMS 830R MILSTRAP EQUIVALENT DOCUMENTS/CODES ......... C2-2
C4.T1 DERIVATION OF PRIORITY DESIGNATORS
(RELATING F/AD TO UND) ................................................................. C4-6
FIGURES
Figure Title
C29.F1. INSTRUCTIONS FOR COMPLETION OF DD FORM 1348-1A (OR DD
FORM 1348-2), USED FOR RETURNS TO STOCK TRANSFERS
(EXCLUDING TRANSFERS TO DLA DISPOSITION SERVICES FIELD
OFFICES) .......................................................................................... C29-7
C1. CHAPTER 1
INTRODUCTION
C1.1. GENERAL
C1.2. POLICY. The DoD policy governing the procedures in this volume are:
C1.3. APPLICABILITY. This volume applies to the Office of the Secretary of Defense,
the Military Departments, the Joint Staff, the Combatant Commands, and Defense
Agencies. The manual applies, by agreement, to external organizations conducting
logistics business operations with DoD including (a) non-Government organizations,
both commercial and nonprofit; (b) Federal agencies of the U.S. Government other than
DoD; (c) foreign national governments; and (d) international government organizations.
C1-1 CHAPTER 1
DLM 4000.25, Volume 2, April 09, 2022
Change 14
improvement, maintenance, and administration of supply requirements for the DLMS.
The Supply PRC chairperson, in coordination with the DoD Component Supply PRC
representatives, is responsible for the contents of this volume of the DLMS.
Representatives to the Supply PRC are identified on the Defense Enterprise Data
Standards Office (DEDSO) Website. See DLMS Volume 1, Chapter 1 for a discussion
of DLMS PRC functions and responsibilities.
• Chapter 6 for quality control requirements and for additional controls required
when reversing physical inventory adjustments,
C1-2 CHAPTER 1
DLM 4000.25, Volume 2, April 09, 2022
Change 14
• Chapter 13 for additional controls required when reversing receipt transactions,
and
C1-3 CHAPTER 1
DLM 4000.25, Volume 2, April 09, 2022
Change 14
processing, and contractor shipments) are prescribed in the applicable regulatory
documents of the standard system.
C1-4 CHAPTER 1
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C1.11.1. MILSTRAP Purpose
C1.11.1.1. The forms, formats, and codes prescribed herein were developed
on the basis of the DoD Components' requirement for standard transaction reporting
and accountability procedures for item accountability and financial inventory of DoD
materiel. The prescribed codes are mandatory for inter- and intra-DoD Component use
when data are interchanged among distribution system elements.
C1.11.2.1. Excluded are supply transactions below the inventory control point
(ICP) and storage activity level in the distribution system (i.e., transactions at post,
camp, station, base (or equivalent) level or between post, camp, station, base (or
equivalent) and using organizations), unless a DoD Component establishes an internal
requirement for use at this level.
C1.11.3.1. MILSTRAP holds to the principle that the structure of the system
provides essential information to inventory control points (ICPs) for the exercise of
supply and financial management without encumbering the system with details peculiar
to differing types of materiel. A standard system of this design imparts uniformity
without limiting the ICP’s internal management options for the items of supply it controls.
C1-5 CHAPTER 1
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C1.11.3.2.2. Uniformity in the interchange of inventory accountability
information within and between the DoD Components.
C1-6 CHAPTER 1
DLM 4000.25, Volume 2, April 09, 2022
Change 14
system (designed to account for items of supply controlled, managed, or stocked in the
distribution system) is based on the concept of inventory segmentation by
ownership/purpose, supply condition, and location. The coding information indicates
who owns the assets (ownership), for what purpose the materiel is held within an
ownership (purpose), the condition of the materiel in terms of serviceability and
readiness for issue (supply condition), and where the materiel is physically stored
(location). These basic data elements are required for inventory management,
requisition processing, and distribution management. This information is also required
for preparing financial and supply status reports required for management and decision
making.
C1-7 CHAPTER 1
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C1.11.4.2.3.2. The three-digit routing identifier code (RIC) structure
established by MILSTRIP provides a standard system for identifying activities within
established supply distribution systems, including those that store materiel. To make
use of this existing structure, location codes used to identify activities storing materiel
correspond to the RICs established by MILSTRIP.
C1-8 CHAPTER 1
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C2. CHAPTER 2
SPECIAL PROGRAM REQUIREMENTS AND DEMAND
DATA EXCHANGE PROJECTED SUPPLY PLAN
C2.1. GENERAL
C2.1.2.1. The DDE Projected Supply Plan function uses DLMS 830D
(version 4030) identified by Accredited Standards Committee (ASC) X12 beginning
segment (1/BFR12/0200) Planning Schedule Type Code AA–Customized Ordering
Forecast. The DDE function is further broken down in 1/LN01/0100 to identify a DDE
Projected Supply Plan submission (LN01 Code H) and a DDE Projected Supply Plan
cancellation (LN01 Code C) for a given national item identification number (NIIN). This
transaction is a DLMS enhancement and has no corresponding DLSS MILSTRAP
legacy transaction.
C2.1.2.2. The SPR function uses DLMS 830R (version 4010) identified by
ASC X12 beginning segment (1/BFR12/020) Planning Schedule Type Code XA–
Requirement Forecast. SPR functions are further broken down in 2/LIN01/10 to identify
SPR Request, SPR Security Assistance Request, SPR Cancellation, SPR Modification,
SPR Acceptance or Rejection of Substitute Item, and SPR Inquiry. The corresponding
MILSTRAP legacy 80 record position transaction functionality is identified for
information purposes in a mixed DLSS/DLMS environment. DLMS 830R provides
functionality of MILSTRAP legacy Document Identifier Codes (DIC) DYA, DYB, DYC,
DYD, DYG, DYH, DYJ, DYL, and DYM. Table C2.T1. provides the specific 2/LIN01/10
correlation to the legacy DICs.
C2-1 CHAPTER 2
DLM 4000.25, Volume 2, April 09, 2022
Change 14
Table C2.T1. DLMS 830R MILSTRAP Equivalent Documents/Codes
Legacy MILSTRAP Title 830R DLMS Title Required BFR
DIC LIN01 Action Code
Code
DYA SPR Request A SPR Request
DYB SPR Request A SPR Request OT, indicates
(Exception Data) exception data is
provided
DYC SPR Cancellation C SPR Cancellation
DYD SPR Modifier D SPR Modification
DYG SPR Substitute Item F SPR Substitute Item
Acceptance Acceptance
DYH SPR Substitute Item G SPR Substitute Item
Rejection Rejection
DYJ SPR Follow-up E SPR Follow-up
DYL SPR Request B SPR Security Assistance
(Cooperative Logistics Request
Supply Support
Arrangement
(CLSSA))
DYM SPR Request B SPR Security Assistance OT, indicates
(Exception Data for Request exception data is
CLSSA) provided
C2.2.1. Forecasting activities may submit SPR requests for requirements meeting
one or more of the following criteria:
C2-2 CHAPTER 2
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C2.2.1.3. New constructions (e.g., ships, buildings).
C2-3 CHAPTER 2
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C2.2.4. DAAS Processing. DAAS will pass or route SPR inquiries as follows:
Upon receipt of the DLMS 830R SPR transactions, DAAS will edit the national stock
number (NSN) of the incoming transaction to determine whether 1) the NIIN can be
identified, 2) the Federal supply class (FSC) is compatible with the NIIN, and 3) the
transaction is directed to the correct source of supply. DAAS will pass the transaction,
reject the transaction, or effect necessary changes to process the transaction and provide
appropriate status notification or reject transactions to the submitter as follows:
C2.2.4.1. If the NIIN is valid (including NIINs coded obsolete/inactive) but the
FSC and NIIN are not compatible, DAAS will correct the FSC and provide a DLMS 870L
Status Notification Transaction to the submitter. DAAS will prepare the notification
whenever the FSC is corrected in the incoming transaction. Show the correct FSC and
Status Code BG in the Status Notification Transaction.
C2.2.4.3. If the NIIN cannot be identified, DAAS will reject the transaction to
the submitter citing Reject Advice Code AD.
1
Source of supply for obsolete/inactive items will be taken from the source of supply file when possible;
otherwise, the source of supply will be the activity identified as the “To” activity in the incoming
transaction.
C2-4 CHAPTER 2
DLM 4000.25, Volume 2, April 09, 2022
Change 14
and ensure that all future SPR transactions show the change identified by the status
code in the notification.
C2.2.7.1. Source of Supply Risk. The IMM measures the size of the
requirement being forecasted to determine its acceptability in terms of the risk of long
supply being generated. This measurement requires consideration of the size of the
forecasted quantity in relation to the normal demand estimated for the item being
forecasted, the value (cost) of this quantity, the supply status of the item being forecasted,
funding capability of the IMM, accuracy of past forecasts, and the degree of assurance
that requisitions will follow.
C2.2.8. Inquiry on SPR Requests. When the forecasting activity has not received
an SPR Status Transaction or a DLMS 824R within 21 calendar days from the SPR
request submission date, the forecasting activity may submit an SPR Inquiry Transaction
to the ICP.
C2-5 CHAPTER 2
DLM 4000.25, Volume 2, April 09, 2022
Change 14
initiator of the SPR requirement. If the originator of the SPR modifier differs from the
originator of the original SPR, maintain a record of the revised originator.
C2.2.11. Response to SPR Modification. The ICP must prepare replies to SPR
modifiers, as specified in paragraph C2.2.7.
C2.2.13. Response to SPR Cancellations. The ICP must reply to SPR Cancellation
Transactions with an SPR Status Transaction citing SPR Status Code PD indicating that
the cancellation was accepted.
C2.2.15. Response to Substitute Item Rejection. The IMM must initiate action on
the item originally requested. The IMM must prepare status responses as specified in
paragraph C2.2.7.
C2.2.16. Retention of SPR Requests. The ICP will retain SPR requests until:
C2.2.16.1. The support date of those requirements for which SPR Status Code
PA was furnished or until a requisition is received that can be identified to all or a portion
of a particular SPR quantity.
C2.2.16.2. One procurement lead time/assembly time away from the support
date when procurement/assembly is required in support of those requirements for which
SPR Status Code PB was furnished.
C2.2.16.3. Assembly time prior to support date when extra time is required for
assembly in support of those requirements for which SPR Status Code PC was furnished.
C2.2.17. Follow-on Status. The IMM must provide revised SPR Status
Transactions when the situation changes (e.g., change in procurement lead time,
procurement is required for materiel originally anticipated to be available from stock).
Generally, these situation changes are unusual in nature, are not programmed, and
require off-line processing. IMMs must provide the status as specified in paragraph
C2.2.7.
C2-6 CHAPTER 2
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C2.2.18. Preparation of SPR Requisitions
C2.2.19.2. Logistics Loss within Same DoD Component. When the logistics
loss is to an IMM within the same DoD Component, the LIM must forward the record of
the SPR Request Transaction to the GIM. No status need be furnished the forecasting
Activity.
C2.3.1. DDE supply planning activities may submit to DLA their projected supply
plan/collaboration data for future requirements expected to be obtained from DLA using
the DLMS 830D, DDE Projected Supply Plan Transaction. Separate projected supply
C2-7 CHAPTER 2
DLM 4000.25, Volume 2, April 09, 2022
Change 14
plans into monthly periods based on the projected requirement date materiel is expected
for a planned maintenance schedule. Use of the formal collaboration process is restricted
to Class IX materiel. Condition guidelinesfor collaborative forecasting include, but not
limited to:
C2-8 CHAPTER 2
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C2.3.2.3. Intra-Component optional fields. Components may use optional fields
available in DLMS 830D and 870L to carry intra-Service information as necessary.
Optional information received in a DLMS 830D must be perpetuated in the response back
to the originator using DLMS 870L.
C2.3.3. Processing of DDE Data. DLA will compare the collaboration customer’s
projected supply plan to the projected customer supply plan calculated by the Planning
and Collaboration Subsystem or the previous collaborative projected supply plan if the
NIIN is a recurring Demand Forecast Unit.
C2.3.3.1. Collaborative items (which may or may not exceed system tolerance
parameters) will be available for collaboration interaction with the customer and DLA via
the Planning and Collaboration Subsystem.
C2-9 CHAPTER 2
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C2.3.3.2. Items previously identified for inclusion in DDE that are not in the
current DDE submission will remain flagged as Collaborate with the most recent DDE
projected supply plan quantities received from the customer. If the customer would like to
remove an item from the DDE effort, the customer will submitt a DLMS 830D, DDE
Cancellation Transaction for the NIIN and the item will be removed from the
DDE/Collaboration effort.
C2.3.4. Collaboration Interaction. All Collaborative items (which may or may not
exceed system tolerance parameters) will be available for monthly collaboration
interaction with the customer and DLA. The point of contact for the customer will be
alerted, via e-mail by the Collaboration lead at the DLA Field Activity (DLA Aviation,
Richmond, VA, DLA Land and Maritime, Columbus, OH, DLA Troop Support,
Philadelphia, PA, by the seventh business day of every month, to notify the customer of
the open and close dates of the monthly collaboration window. The customer will have
until the fourth Thursday of the month to complete the review (specific open and close
dates will be cited in the e-mail). The DLA demand planner will then have until the fourth
Friday of the month (also know as “Demand Month End”) to complete the review and
publish the demand plan for inclusion in the projected supply plan.
C2-10 CHAPTER 2
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C3. CHAPTER 3
WAR MATERIEL REQUIREMENTS AND SIMULATED
MOBILIZATION EXERCISES
C3.1. GENERAL
C3.1.2.1. DIC DMS, Recurring U.S. Other WMR Data = LQ01 qualifier
‘LZ’ WMR Code 7–Recurring U.S. Balance War Reserves.
C3.1.2.4. DIC DMD, WMR Forecasted Return Data = LQ01 qualifier ‘LZ’
WMR Code 4–WMR Forecasted Reparable Return.
C3.1.2.5. DIC DME, WMR Visibility Data = LQ01 qualifier ‘LZ’ WMR
Code 10–Pre-Positioned War Reserve. Wholesale, Protected and Nonprotected.
1
Refer to legacy DLM 4000.25, DLMS Volume 2, Appendix 3.28 DM_ War Materiel Requirements Data
format.
C3-1 CHAPTER 3
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C3.2. WAR MATERIEL REQUIREMENTS
C3.2.1. DoD Policy. DoD Instruction 3110.06, “War Reserve Materiel Policy,”
June 23, 2008, contains DoD policy for management and development of WMR.
C3.2.3. This chapter also provides guidelines which affect simulated mobilization
exercises.
C3.2.4. DoD Component Input. The DoD Components shall send WMR data to
reach IMMs by 15 February of each year and shall submit corrections and/or changes
as required. Do not submit zero quantity requirements.
C3.2.5. IMM Responsibility. The IMM shall control each DoD Component's input
WMR Transactions by national stock number (NSN), edit the WMR Transactions, and
validate the edited transactions for data adequacy and accuracy. The IMM shall
consider validated requirements in the annual computation of the Balance War Reserve,
and in any recomputation of these requirements upon receipt of corrected or revised
input. When a WMR Transaction contains an invalid NSN, unit of issue, quantity, or
date, process a DLMS 824R, Reject Advice. However, when the transaction is invalid
for any other reason, manually reject the entire submission to the submitting DoD
Component. Include all rejects on a listing showing an image of the input transaction
and a code identifying the reason for the reject. Mail the listing together with a letter
explaining the reject code and action(s) required of the submitter.
C3.2.6. Logistically Reassigned Items. When items are logistically reassigned, the
LIM shall send the GIM a listing of WMR data with a supporting WMR Transaction, as
prescribed in the Chapter 9 of this manual.
C3-2 CHAPTER 3
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C3.3.2. C15.3.2. Military Standard Requisitioning and Issue Procedures
(MILSTRIP), prescribe Project Codes in the 3E series that are reserved for use in
simulated mobilization exercises.
C3-3 CHAPTER 3
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4. CHAPTER 4
REQUISITIONING
C4.1. GENERAL.
C4.1.1. This chapter prescribes procedures for the preparation and submission of
requisitions with specific requisitioning requirements involving 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.
C4.1.2. 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.
C4.1.4. There are additional processing procedures over and above those
contained in this chapter that must be applied for serially managed materiel requiring
owner visibility at DLA Distribution Centers. The identity of the materiel and the additive
procedures are in Chapter 30. 1
1
Refer to ADC 1244.
C4-1 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.1.5.3. Requisition Inquiry Transaction is DLMS 869A with Transaction
Type Code AF – Requisition Follow-Up. This transaction provides the functionality of
MILSTRIP legacy DIC AF_.
2
Refer to ADC 1043/1043A.
C4-2 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
elements in the transaction do not match data elements from the SFIS Fund Code to
Fund Account Conversion Table for the Fund Code in the transaction, reject with the
DLMS 870S Supply Status citing Status Code CF. If invalid/missing fund code for
Signal Code A, B, C, J, K, or L, reject with the DLMS 870S/DIC AE9 Supply Status
citing Status Code CF. Requisitions must be edited by the ordering application prior to
acceptance of the order for further processing. Image and post-post transactions will
not be rejected by the source of supply or DAAS. 3
C4.2.1.1. Identification Code. This consists of the first six positions of the
document number and is a six-position constructed code for identification purposes.
Use the applicable DoD activity address code (DoDAAC) (AAC for Federal Civil
Agencies).
C4.2.1.3. Serial Number. This is the assigned four-position line item code for
each requisition within the transaction set. It is located in the eleventh through
fourteenth positions of the document number. Use the Utilization Code in the LQ
segment to identify the purpose of the requisition.
C4-3 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.2.2.1. Commander Requirements Review. Commanders (or
acting commanders during absences) must personally review all requirements based on
UND A to certify an inability to perform the mission.
4
Refer to ADC 1009A. Automatic downgrade for PD 01 requisitions will not be authorized pending
implementation of the mark-for party as an alternate location for the authorized activity DoDAAC.
5
Materiel requirements of this nature affect the readiness of mission-essential materiel and actually result in a
report of casualty in accordance with equipment readiness information systems authorized by the Office of the
Secretary of Defense (OSD), the Chairman of the Joints Chief of Staff, or the DoD Component headquarters.
6
Ibid.
C4-4 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.2.4.1.5. Required for immediate end-use to effect the
replacement or repair of the essential physical facilities of an industrial or production
activity and without which that activity is unable to perform its assigned missions.
7
Materiel requirements of this nature directly affect the capability of the force or activity to perform its mission; it
can temporarily accomplish assigned missions and tasks but with effectiveness and efficiency below the DoD
Component Headquarters-determined level of acceptable readiness.
C4-5 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.2.4.2.8. Required for the immediate replacement of the safety
level quantity of mission-essential items on allowance and load lists (such as,
prescribed load lists, spares kits, station sets, or coordinated shipboard allowance lists)
when the last item has already been issued.
C4.2.2.5. Deriving PDs. Refer to Table C4.T1 to derive the PD from the F/AD
and UND.
C4-6 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
documentation will be forwarded to Transaction Services and GSA to support inclusion
of all F/AD I authorized activities. In order to maintain unclassified communication, the
JCS contact points are advised to identify authorized activities by DoDAAC only (no
clear-text activity names) and make no reference to the associated F/AD. F/AD I
requisitions (DLMS 511R or DLMS 511M, Modification, Transaction Type Codes A0,
BM, BN, AM) that do not identify an authorized activity in the document number, ship-to,
bill-to, or mark-for fields will be identified for investigation without interruption of normal
requisition processing. In addition, Transaction Services will assess the validity of
transactions that bypass the F/AD I validation process as a result of alternative
requisition submission, (e.g., Defense Supply Expert System (DESEX)) input, using the
requisition image transaction. Suspected abuse will be output to the Unauthorized
Priority Designator Assignment Report.
C4.2.2.6.2. RESERVED.
C4-7 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
to PD 13. 8 PD 01 requisitions may be downgraded with the exception of Air Force
(Service Code F) requisitions. 9 GSA will notify the requisitioner of the downgrade by
generating a Supply Status Transaction with BK Status, and route to DAAS for
distribution to the correct recipient(s) depending on the Media/Status and Distribution
Codes in the transaction. The modified requisition will be forwarded within GSA for
processing based on the new PD. GSA will report downgrading action to DAAS via the
DLMS 511R (future enhancement) Transaction. Action will allow Transaction Services
to merge GSA priority abuse data into the Unauthorized Priority Designator Assignment
Report on a monthly basis.
C4-8 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.2.7.1.2. Avoiding or reducing the impact of epidemics or
similar potential mass illnesses or diseases when in the opinion of medical
professionals the probability of epidemics or similar potential mass illnesses is
imminent.
C4.2.2.10. Issue Priority Groups. PDs are grouped into Issue Priority Groups
(IPGs) as follows:
C4.2.2.10.3. PDs 09, 10, 11, 12, 13, 14, and 15 form IPG III.
10
Non-date entries in the RDD field, (i.e., Codes E, F, N, R, 444, 555, 777, and 999), are referenced as
Special Requirement Codes under the DLMS.
C4-9 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.2.11.2. Nonstandard Delivery Times. When an RDD shorter than
the UMMIPS time standards is assigned, the appropriate PD, consistent with the
activity's F/AD and UND, must be cited in the requisition.
C4.2.6. Exception Data. Requisitioners must limit repetitive exception data to aid
timely source of supply processing of requisitions to meet IPG processing times,
standard delivery dates (SDDs), or RDDs, particularly those that satisfy high priority
requirements. Use available requisitioning capabilities to ensure maximum utilization of
C4-10 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
automated processes. Processing exception data requisitions is resource intensive,
prone to errors, and generally delays required support. The sources of supply will
disregard all unnecessary exception data (such as ship by commercial air, do not use
postal system, ship by fastest traceable means, or ship overnight delivery) and continue
processing. Sources of supply will process all requisitions under UMMIPS (see DoDM
4140.01). Within the UMMIPS time segment for transporting the materiel, it is the
shipper's prerogative to select the mode of shipment based on time, distance, item
characteristics, and economic factors. The repetitive use of the same exception ship-to
address is an uneconomical way of doing business for all concerned. A separate
DoDAAC assignment for this type of ship-to address should be made or the
Transportation Account Code (TAC) 2 address of the involved activity should be
changed and the resulting DoDAAC(s) used on applicable requisitions. Activities having
multiple locations should assign a separate DoDAAC to each receiving location. It is
incumbent upon the requisitioner to work with the applicable DoD Component focal
point to develop procedures to automatically process requisitions.
11
Refer to ADC 1075.
C4-11 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.7.2.7. Requisitions from deployed naval units with an R or V in the
first position of the document number; Utilization Code E, G, or W; PD 01, 02, or 03;
and Special Requirements Code 999.
C4.2.7.3.5. NSN items for chemicals for boiler water and feed water
analysis.
C4-12 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
transactionally. When the owner-generated MRO identifies a clear-text ship-to address
there is no requirement to perpetuate this address in the confirmation beyond the first
address line containing the organization name.
C4.2.9. Nonstandard Materiel. The requisitioner may cite an estimated unit price
to advise the source of supply of a reasonable expectation of the cost of the item. The
source of supply may contact the requisitioner, if in its estimation, the price incongruity
between estimated price and quoted price warrant further clarification relative to the
item being ordered. Requisitioners should use the last price paid as their estimate if
they have previously ordered the item or use the price of a similar item ordered if they
have not previously ordered the item.
C4-13 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.10.2. Supply sources authorizing the use of ordering processes external
to the customer’s Component-sponsored supply system shall:
12
Refer to ADC 328
C4-14 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.11.3. Requisitioning organizations should provide a job title if a name is
not authorized in accordance with applicable security or privacy reasons.
C4.2.12.1. General
C4-15 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.12.2.2.3. The items or equipment required have been
identified during maintenance or testing as necessary to prevent mission-essential
systems or equipment from being unable to perform assigned operational missions or
tasks within five calendar days of the date of the requisition.
C4.2.13.1. Initial Fill. Use Demand Code O and Project Code 3AA to identify
requisitions for the initial fill of PWRMS consumable item requirements. Use Project
Code 3PR in PWRMS replenishment requisitions. DoD organizations cannot submit
non-reimbursable requisitions to GSA.
C4-16 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.14. Conventional Ammunition Requisitions
C4.2.14.2. Use Advice Code 3Q, 3V, 3W, 3X, 3Y, or 3Z, as applicable, when
usable SCC E materiel is acceptable.
C4.2.15.2. Low Item Value. GSA will cancel requisitions (with Status Code
CW) when received without Advice Code 2A for an item valued at $25 or less if, at the
time of shipment, transportation costs incurred for shipping that order is in excess of 50
percent of the item value. GSA will notify the ordering activity when this condition exists
and the requisitioner should attempt to procure the item locally. If local procurement
cannot be effected, submit a new requisition with Advice Code 2A. In response, GSA
will supply the item regardless of the transportation costs.
C4-17 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Management Code 3 or 9 to request the DLA source of supply satisfy the specified
requirement from an alternative storage location or new procurement, if no stock is
available. This is applicable only when re-requisitioning subsequent to purchase of
materiel that was sourced from a collocated depot without visual inspection of the
materiel. Use of the Management Code 3 will indicate that purchased materiel did not
satisfy shelf-life requirements. Management Code 9 will indicate that the materiel was
not available in one continuous length. The prior (original) requisition document number
and shipment suffix code (if applicable due to split shipment), must be included on the
new requisition. The originally purchased materiel will be returned to DLA via BRAC
returns procedures.
C4.2.19. Special Army Single Stock Fund (SSF) Procedures for Image, Working,
and Post-Post Requisitions and Authorization of Edit Action Codes (EACs) for Both SSF
and non-SSF Army Activities. The following procedures are restricted to use by the
Army on an intra-Service basis.
C4-18 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.19.1. These procedures include Army-unique data elements required to
accurately process transactions in the Army wholesale system that originate from the
Army retail system for SSF activities. For both Army retail replenishment orders for
authorized stock listed items and for dedicated customer orders for non-stock listed
items, an image of the order containing a special EAC, management code, and date
generated is created and passed to the wholesale system. For these replenishment
and dedicated customer orders, the EAC indicates that the order is to be held until
either post-post issue requisitions are received equaling the image requisition quantity
or a live/working requisition is received for the total or residual quantity of the image
requisition. Additionally, customer/consumer orders for authorized stock listed items
that cannot be filled by the retail system are backordered at the retail level and an
image of the consumer requisition containing an EAC, management code, and date
generated is created and passed to the wholesale system. For these backordered
consumer requisitions, the EAC indicates that the order is to be held until either post-
post issue requisitions are received equaling the image requisition quantity, or a
cancellation is received. Based on business rule parameters, these EAC codes
facilitate the Army process, that searches for assets at multiple retail levels, prior to
requiring a wholesale asset search to fill the retail and consumer level requisitions. The
post-post issue requisition also contains an EAC, management code, and date
generated. Additionally, the post-post requisition contains the SSF routing identifier
code (RIC) of the activity issuing the assets and codes indicating the ownership,
purpose and condition of these assets, as well as a suffix code, if it is only a partial
issue of the image requisition quantity. The following are the types of requisitions
included in this process:
C4-19 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.19.1.4. Image Dedicated Requisition. An image of a dedicated
requisition containing an EAC, management code, and the date generated is submitted
by the SSF site to the Army wholesale source of supply. Upon receipt, the source of
supply establishes a document control file with a requisition quantity control, creates a
demand record, and takes no further action until receipt of a post-post or working
requisition.
C4.2.19.3. Working Requisition Processing. If the SSF site can fill the total
requisition through post-post issues, the wholesale source of supply will not receive a
working requisition. However, if the SSF site is unable to satisfy the total demand
quantity of the requisition, the wholesale site will receive either a working requisition for
the residual quantity or a cancellation on the same document number as the image
requisition. Upon receipt of the working requisition the wholesale source of supply will
initiate normal support actions. Any actions taken by the wholesale source of supply on
the working requisition will always begin with Suffix Code L. The total quantity of all
post-post requisitions and all working requisitions received on a single document
number should not exceed the quantity on the original image requisition.
C4.2.19.4. EAC Authorization. In addition to the use of the EAC in the above
SSF procedures, for both Army SSF and non-SSF activities, the EAC is authorized to
be used for requisition reinstatement and other varied purposes.
C4-20 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.20. Requisitioning in Support of an Inter-service Maintenance Agreement 13
C4.2.20.3. To preclude billing by the materiel owner, the requisition will also
contain the following data elements to denote free issue. For requisitions submitted to:
C4.2.20.3.1. Air Force: For Air Force principals (RIC TO of F**), use
Project Code 3BB.
C4.2.20.3.3. Army: For Army principals (RIC-TO A** or B**), use Project
Code 3BB, Fund Code GM, and Signal Code D or M.
13
Refer to ADC 1176. Staggered implementation of SCC for requisitions authorized.
C4-21 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.2.20.4.2. Passing the requisition to the Principal reduces financial
losses that would be incurred to purchase new materiel while previously purchased
materiel is sitting in the Principal’s inventory. This will reduce inventory balances as
intended at the designated Principal, and does not unnecessarily draw down inventory
at the supply source.
C4.20.6. DAAS will pass requisitions (DIC A0_), modifications (DIC AM_),
and follow-ups (DIC AT_) containing Project Codes 3AB, 3AD, and 3BB to the
designated recipient (rather than routing to the source of supply).
C4.2.21. DoDAAC Authority Code Edits. Requisitions will be prepared using valid
DoDAACs for the purpose(s) intended. DoDAACs designated as the requisitioner, bill-
to, or ship-to activity will be validated based upon the authority code assigned to each
DoDAAC in the DoD Activity Address File. Refer to DAAS edit of incoming requisitions
below for edit rules.
C4.4.1. General
C4-22 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
deobligate funds or update individual due-in records until you receive status from the
source of supply confirming cancellation.
C4.4.2. Reserved
C4-23 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.5.1.1. Non-GFM Requisitions
C4.5.1.1.7. PD
C4.5.1.2.2. PD
C4.5.1.2.4. RDD
C4-24 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.5.2. Identifying Applicable Supply Actions. Identify requisitions for which
supply action must be continued during mass cancellation situations and submit
modifications with Special Requirements Code 555 to the source of supply at the
earliest possible date to ensure the continued processing of the requisitions.
C4.5.3. Pertinent Modification Data. Only data on the modification transaction will
be changed. All other data will remain as stated on the original requisition.
C4.6.2. Follow-Ups. Submit follow-ups to obtain the latest status for a previously
submitted requisition.
C4-25 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
the materiel within normal transit time based on the date of the shipment as cited in the
shipment status transaction.
C4.6.3.2. Submission
C4-26 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.6.3.2.3.2. Code 2: Inability to perform assigned mission.
C4.7.1. General
C4.7.1.1. Verification. Sources of supply will validate the data elements and
codes in these transactions and accomplish changes, continue processing action, or
reject with the appropriate status code using DLMS 870S, Supply Status. Rejection of
transactions will be done only after an attempt has been made to correct the
questionable data element or code. If rejection action is a result of more than one data
element or code, and no other reject status code applies, reject using Status Code CA.
C4-27 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.1.3. Backorders. Backordered requirements will be merged (in the
above sequence) with all new transactions in any requisition processing cycle in which
additional assets become available; for example, receipts of materiel and debit on hand
adjustments.
C4-28 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
will blank the special requirements code and process using the priority. Type of
assistance is identified as the sixth position of the SA identification data portion of the
document number or separately in the LQ segment.
C4.7.2.1.10. For all other conditions, if the PD is not 01 - 15, the source
of supply will enter PD 15.
C4-29 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
provide for a release of demands containing the specifically designated OSD/Joint
Chiefs of Staff project codes and Special Requirements Code 999 as the respective
most urgent. PD 01-08 requisitions, including FMS requisitions, containing Special
Requirements Code 555 in the RDD field and other requisitions/materiel obligations, will
be processed for release as prescribed in paragraph C4.7.1.2.
C4.7.3. Source of Supply Processing of Requisitions with Advice Code 2D, 27, or
29. Sources of supply will edit all requisitions containing Advice Codes 2D, 27, and 29
to determine if an increase in the requisition quantity to the quantity unit pack is less or
more than $5. If less than $5, the source of supply will disregard the advice code in the
requisition. If $5 or more, the source of supply will honor the advice code and process
the requisition for the exact quantity requested. When a quantity adjustment is made
using the above criteria, the source of supply will use Status Code BJ to notify the
customer of the quantity adjustment.
C4.7.5.1. General. Sources of supply, except GSA, will process funded and
unfunded requisitions for the initial fill of PWRMS consumable item requirements using
the criteria established below. GSA will process only funded requisitions for PWRMS
requirements and does not differentiate between those requisitions and others.
C4-30 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.5.2.2. Excess Assets. If the assets available in excess of the
AFAO are not sufficient to satisfy the total requisition quantity, then the portion of the
requisition quantity equal to the quantity of assets available in excess of the AFAO will
be processed as free issue and the balance of the requisition quantity will be processed
as follows:
C4-31 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.6.3. Rejecting Late Requisitions. Requisitions that cannot be delivered
within the RDP will be rejected with Status Code CB.
C4.7.7.1. PD 01-08. If the PD is 01-08, process the requisition for issue and
provide Status Code DS to the requisitioner.
C4.7.7.2. PD 09-15. If the PD is 09-15 and assets are available above the
ROP, process the requisition for issue and provide Status Code DS to the requisitioner.
C4.7.7.3. Assets Not Available. If the PD is 09-15 and assets are not
available above the ROP, reject the requisition with Status Code CC or CN, as
appropriate.
14
Expanded use for all DoD Components requisitioning from DLA is planned for future implementation
(approximately 2014.)
C4-32 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
in receipt of Management Code 3 or 9 will disregard and continue processing. DLA will
verify that the requisitioning activity is a BRAC Inventory Management and Stock
Positioning (IMSP) industrial/maintenance site authorized to use these codes. If not,
DLA will disregard the management code. Where authorized, Management Codes 3
and 9 will be recognized as a request for materiel sourced from an alternative storage
location or new procurement, if stock is not available, due to previous receipt of materiel
that did not support shelf life or continuous length requirements. The prior requisition
document number and the shipment suffix (if applicable due to a split shipment) will be
used for cross reference to the original requirement and storage location. This process
is only applicable to materiel originally sourced from a co-located depot without physical
inspection of the materiel. The suitability for shelf life and length could not be
determined until directed release by the Service owner at which time the storage activity
would provide a denial citing Management Code 3 or 9, as applicable. The DLA would
apply unique logic applicable to the management code. If the item is available in an
alternative storage site, then a materiel release order would be sourced to that
alternative storage site. When no stock is available in the network, a new procurement
action will be initiated. The DLA ICP will also update an internal denial table to preclude
other comparable requests from being sourced to the original storage activity until
inventory balances have been reconciled. 15
C4.7.10.2. The "Principal" system will interpret the DLMS 511R Requisition
with Advice Code 2J (fill or kill) as “no substitution allowed” but will allow for a partial fill,
(i.e., do not backorder unfilled quantity, or pass an MRO to other than the co-located
storage activity). The source of supply (Principal) will furnish the requisitioning activity
(maintenance) DLMS 870S Supply Status using CB status for any unfilled quantity.
15
Refer to ADC 359, implementation date December 2010.
C4-33 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.12. Rejection of Requisitions. Sources of supply will provide supply status to
requisitioning and status organizations identified in the requisition or follow on
transactions, as notices of requisition rejection with the reason for such action indicated
by an appropriate status code.
16
Use the legacy PIIN pending transition to the PIID. When GFM is authorized under a PIIN, include the
legacy four-position call/order number associated with the PIIN when available and directed by the
authorizing Component. Refer to ADC 1161A.
C4-34 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.14.1.5. MROs directing the return of PQDR exhibits may include
both the DCN provided by the storage activity and the PQDR report control number
(RCN), if available. 17
C4.7.14.1.8. MROs directing the return of SDR exhibits will include the SDR
distribution center number (DCN), if available.
C4.7.14.2. Advice Code 2T. Requisitions or MROs that contain Advice Code
2T and do not contain an RDD will be processed under the assigned PD without regard
to the advice code.
ADC 1169, DLA Distribution Center Denial Scenarios Associated with Product Quality Deficiency
17
C4-35 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.14.5. Expedited/Replacement Shipment Subsequent to Validated
Supply Discrepancy Report. MROs directing release of materiel in response to
customer requests for expedited or replacement shipment due to shortage, non-receipt,
wrong item, or comparable discrepancy/deficiency will be processed using the original
document number and the next available suffix code to ensure separate billing and
unique TCN assignment. When requested by the customer via Supply Discrepancy
Report, an Expedited Transportation Signal 777 may be assigned for the reshipment
when the original special requirements code (legacy required delivery date (RDD) field
is blank or all numeric (other than 444, 555, 777) or the RDD from the original
requisition is less than 8 days from the current date. Inclusion of the Expedited
Transportation Signal 777 will normally cause the shipment to move by premium (air)
transportation. Shipments identifying Expedited Transportation Signal 777 are subject
to air clearance processing whereby the air clearance authority may consult with the
requisitioner to determine if the additional expense associated with air transportation is
justified and potentially direct shipment movement by a surface mode. 18
C4.7.15. Reserved
C4.7.16.1. Purpose. The MRC serves as advice from a storage site to the
source of supply that initiated the MRO of supply action taken. The MRC will be
provided using DLMS 945A. The MRC will include enhanced data content under DLMS
to include:
C4-36 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
tracking at the DoD level. Submitters must prepare materiel release confirmation citing
the applicable serial number(s) and include the UII when available. 19
19
Refer to ADC 1198
C4-37 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.16.3.1.6. The ICP will adjust its Materiel Release
Acknowledgment (MRA) follow-up timeframes based on the updated MRC in
accordance with standard MILSTRAP business rules.
C4.7.17.2. Delivery Status. If the storage activity cannot meet the delivery
timeframe specified by the RDP, the storage activity will use the materiel release advice
to provide Status Code CB to the source of supply. The source of supply will provide
this status advice to the eligible status recipients (applies to conventional ammunition
requisitions only).
ADC 1169, DLA Distribution Center Denial Scenarios Associated with Product Quality Deficiency
20
C4-38 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
the MRO containing the SDR DCN or PQDR RCN does NOT match any of the DCNs
or RCNs on the storage activity accountable record.
C4.7.17.4.2. When the DLMS 940R MRO contains the SDR DCN or
PQDR RCN and the DCN or RCN DOES match a DCN or RCN on the storage activity
accountable record, but the DCN or RCN in the bin location is not the expected DCN
or RCN for the MRO, the storage activity will prepare a DLMS 945A MRD.
C4.7.18.2. To establish assets controlled by the DLA ICP under the MOA,
the DoD Component may initiate an “in-place” sale. To accomplish this, the DoD
Component requisitions materiel to be centrally managed by DLA, establishing the
Component-owned assets on the DLA records. Ownership changes from DLA to the
DoD Component, but DLA maintains item management control and continues to store
the item in a DLA Distribution Depot. The DLMS 511R, Requisition, must contain the
preferred depot DoDAAC for stock to be commingled and Advice Code 8D. The DLA
ICP internally produces and posts the DLMS 940R, Materiel Release, (which is not
actually sent to and from depot) and uses a DLMS 867I, Issue (DoD Activities), to drop
and a DLMS 527R, Materiel Receipt – Other Than Procurement Instrument Source
(DoD Activity) to post assets to the DLA ICP inventory record under Component-
ownership. An image of the DLMS 527R, Materiel Receipt – Other Than Procurement
Instrument Source (DoD Activity) will also be sent to the Component ICP for recording
the financial receipt. Normal procedures will be followed for billing the reimbursable in-
place sale.
C4-39 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
DLA ICP using DLMS 511R, Referral Order. Mandatory entries prescribed in paragraph
C4.7.18.3 for requisitions also apply to referral orders.
C4.7.18.5. DLA will process a requisition or referral order and create a DLMS
940R, Materiel Release. Additionally, DLA will produce and forward a DLMS 867I,
Issue (DoD Activities), to the Component ICP for the issue quantity dropped from the
DLA inventory records. Quantities not available will be rejected to the Component ICP
using Status Code CB.
C4.7.18.6. In the event a warehouse denial occurs, the distribution depot will
report the denial in the normal manner. DLA will send a DLMS 867I, Issue (DoD
Activities), reversal and a DLMS 947I, Inventory Adjustment – Decrease (Physical
Inventory), to the applicable Component ICP. Requisition documents will not be
reinstated for continued supply action.
C4.7.18.7. Under the MOA, the DoD Component assets may be issued
directly to DLA assembly points. The DLMS 511R, Requisition, must include Advice
Code 8L; the depot to ship from, the DLA assembly point DoDAAC, Signal Code M,
ownership code, and condition code. DLA will process a requisition in this format and
create the MRO. Additionally, DLA will produce a DLMS 867I, Issue
(Assembly/Disassembly/Conversion/Modification), and post to the DLA ICP records. An
image of the DLMS 867I will be sent to the Component ICP.
C4.7.18.9. To terminate the asset posture under the MOA, the Component
ICP may direct shipment of the materiel using the directed shipment format above, or
one of the following methods.
C4-40 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
sends the Component ICP an image of the DLMS 947I and a DLMS 527R, Materiel
Receipt – Other Than Procurement Instrument Source (Other).
C4-41 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.20. Processing Follow-Ups
C4-42 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.20.7. Request for Supply Assistance
C4-43 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.20.7.4.2. If the current status is BA and the ESD or the
UMMIPS timeframes has passed, provide Status Code B5 to the requisitioner and send
a DLMS 940R, Materiel Release, with Transaction Type Code NB to the reporting
activity. Sources of supply in receipt of responses to follow-ups will send appropriate
status to eligible recipients using section C4.7. procedures.
C4.7.22.2. For intra-Service use, an RDO may be used to direct release and
shipment of materiel from a post, camp, station, or base to another similar activity within
the Service’s distribution system to satisfy a specific Service demand.
C4.7.22.3. For intra-DLA use, an RDO may be used to redistribute DLA stock
from a DLA Distribution Center to the contractor location in support of the DLA’s
Industrial Product-Support Vendor (IPV) program.
C4-44 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.23. Processing Requisition and MRO Modifiers
C4-45 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.23.1.6. Sources of supply will process requested modifications
only when all data fields can be modified, as requested. If this cannot be done, reject
the modifier using DLMS 870S with Status Code B2.
C4-46 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.24.2. General Rules. General rules for the disposition and diversion of
materiel that has been shipped are as follows:
C4-47 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.25. Reserved
C4.7.26. Reserved
21
Staggered implementation authorized. Refer to ADC 93A.
C4-48 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
contract termination, as appropriate. The foregoing also applies to nonstocked and
non-NSN materiel at S/A option, when there is a foreseeable demand for the item.
C4.7.28.6. Status. In the event the above actions are taken, use a DLMS
870S with Status Code B4 to indicate that the organization identified in the canceled
requisition may be billed as follows:
C4.7.28.8.1. DLMS 870S with Status Code B4, B6, BQ, BR, or BS to
indicate cancellations/diversions accomplished.
C4-49 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.28.8.6. DLMS 870S with an appropriate B_, C_, or D_ series
status code for those transactions showing a record of a previous cancellation or
rejection.
C4.7.29.2.7. All contract data, if known; otherwise, the PRN and date of
the purchase request.
C4-50 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.29.3.2. For items and/or quantities on awarded contracts and/or
purchase agreements and the dollar value of the cancellation/diversion action exceeds
$200.
C4.7.29.6.1. DLMS 870S with Status Code B4, B6, BQ, or BS applies to
cancellations/diversions accomplished.
22
As an exception for intra-Component use only, cancellation/diversion may be submitted to procurement
regardless of dollar value when critical/short supply items are affected.
C4-51 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.29.6.2. DLMS 870S with Status Code B9 indicates
cancellation/diversion action being attempted.
C4-52 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
cancellation requests are received on the same day, consideration will be given to the
priority of the requests, OCONUS destination, the dollar value of the materiel, and the
status of the contract involved.
C4.7.32.2. Diversions. DLMS 940R will identify the DoDAAC of the activity to
which shipments will be diverted when shipment has already been released. When the
source of supply does not desire or cannot provide diversion to a specific activity, do not
indicate a diversion address. In the latter case, the source of supply will obtain and
provide alternate destinations, if requested, by storage activities.
C4-53 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.32.2.2.1. In receipt of the MRC at the time of receipt of a
cancellation request and the item requested for cancellation has a line-item value of
less than $200 and is for an OCONUS shipment.
C4-54 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Table C4. T2. Depot Work Area Identification
SHIPMENT
COMPUTER STORAGE PREPARATION SHIPPING
C4.7.33.6.1. The dollar value is less than $25 for a single line-item
shipment unit.
C4.7.33.7. Source Notification. The storage activity will advise the source of
supply and, if applicable, all authorized status organizations of actions taken in
response to cancellation requests. Send this notice as follows:
C4-55 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.33.7.2. When the items have not left the depot and cancellation
action is accomplished, respond only to the source of supply with a DLMS 945A with
Status Code BQ.
C4.7.33.7.6. The storage activity will not initiate action to stop or divert
OCONUS shipments within DTS when:
C4-56 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Code B8 (Transaction Type Code NJ in the WO6 segment) and pertinent shipping
information in the applicable segments.
C4.7.34.2. No LRO Record. When the reporting activity has no record of the
LRO receipt, send the source of supply a DLMS 945A with Status Code BF.
C4-57 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.7.35.2. Purchase Requests. Purchase requests must contain specific in-
the-clear and coded data, as specified below, that must be perpetuated on procurement
instruments and related transactions:
C4.8.2. Once an item of supply is identified for a national repair program and the
NIIN has an established Exchange Price, all requisitions for the items will be priced at
the Exchange Price if the customer is an authorized EP customer.
C4-58 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
systems will continue processing the legacy 80 record position transactions; LMP will
process DLMS transactions that are converted by Transaction Services.
C4.8.4. All related supply transactions prepared by Army will carry and perpetuate
the EP Indicator. As a result of the EP implementation the following transactions are
impacted: Requisition; Requisition Modifier; Requisition Follow-up; MRO; and Supply
Status. The returns process will also process EP related transactions. The Materiel
Receipt Transaction will be generated by SARSS for all returns of EP NIINs, and will
include an EP Type of Credit indicator for unserviceable credit when applicable, as well
as an EP conversion indicator to identify the need to provide credit according to the pre-
EP credit policy, that lasts for 60 calendar days following the implementation of EP.
C4.9.1. Navy uses a two-tier pricing system for selling Depot Level Reparable
materiel to Navy customers. The Navy sells DLRs to other Services at full (standard)
price and then provides carcass value credit when the carcass is returned. This is the
same method the Air Force and Army use when selling reparable items to the Navy.
The Standard Price is the price representing the full value of the DLR item, and is the
price charged when a Not Ready for Issue (NRFI) unit (also referred to as a ‘Carcass’)
is not turned in. The Net Price (also referred to as Exchange Price) is the price that
represents the cost of repairing a DLR item, and is the price charged to customers when
a NRFI unit has been or will be turned in. Navy customers indicate on their requisitions
whether or not a NRFI unit is available for turn-in via the Advice Code, and they are
then charged Net or Standard Price accordingly.
C4.9.2. Requisitions received indicating that a carcass will be returned are tracked
in the Navy’s Carcass Tracking System. This system monitors these requisitions and
matches them with carcass returns as they occur. This system also generates follow-
ups to customers who have not returned their carcasses as promised. Ultimately, the
system triggers an additional charge to the customer, if the carcass is not returned.
Navy uses the term Carcass Charge for this additional billing; it represents the
difference between Standard Price and Net (Exchange) Price. This additional billing is
also referred to as a Delta Bill. If the customer returns the carcass after receiving the
Carcass (Delta) Bill, then the additional billing is reversed, resulting in a Carcass
Charge Reversal (Credit Delta Bill). Navy customers may also return excess DLRs for
credit. The credit can be Standard, Net, or Carcass value.
C4-59 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.9.3. Under MILSBILLS legacy 80 record position billing, the Navy ICPs use the
Sales Price Condition Code to indicate to customers that a particular bill is either Net
(Exchange) Price or Carcass (Delta) Price. Once operational, Navy’s Enterprise
Resource Planning will replace the Navy ICP’s legacy MILSBILLS billing system with a
DLMS based system. Since DLMS does not utilize a Sales Price Condition Code, Navy
will use a combination of Stock Exchange Code and Type of Bill Code to indicate on the
bill that the price charged is Standard, Net, or Carcass price. The DAAS will convert
Navy DLMS bills back to MILSBILLS legacy 80 record position format for any Navy
customers unable to accept DLMS formats.
C4.10.1. DAAS will edit all incoming requisitions and other DLMS transactions for
data errors and validity under procedures in DLM 4000.25-4, “Defense Automatic
Addressing System.”
C4.10.2. As a result of these edits, DAAS will correct data entries or reject
transactions. In case of source of supply errors, the correct source of supply will be
entered and the transaction rerouted, as appropriate.
C4.10.3. DAAS will reject all requisitions/ FedMall orders containing GY/GZ series
AACs. DAAS will send DLMS 870S transactions with Status Code CX to advise all
concerned of rejection of the requisition.
C4.10.4. DAAS will recognize the enhanced DLMS capability to discretely identify
different DoDAACs as the requisitioner, ship-to, and bill-to activities as a DLMS
enhancement. 23
C4-60 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.10.5. DAAS will pass DLMS 511R part-numbered (DIC A02 and A0B)
requisitions to the RIC present in the incoming transaction.
C4.10.7. DAAS will validate F/AD I usage through the requisitioning process.
Requisitions with an unauthorized priority designator will be downgraded. DAAS will
send DLMS 870S with Status Code BK to the customer.
C4.10.8. DAAS will perform validation of requisitions (DLMS 511R, DLMS 511M,
517M, and DLMS 869F) for accuracy and reasonableness of the entry in the RDD field
and its compatibility with the PD. DAAS will send a DLMS 870S with Status Code BK to
advise the requisitioner of the resulting modification. For SA requisitions forwarded to
the applicable ILCO, DAAS will not blank out customer input. DAAS will perform PD
and RDD edits according to Table C4. T1.
C4.10.11. Requisition Date Edit. DAAS will edit requisitions to reject any
requisitions that are greater than one calendar year old, or are more than one day in the
future. 24 For all requisitions (DIC A01, A0B, A02, A0E, A05, A07, A04, A0D), where the
requisition is not applicable to FMS/Grant Aid or Navy initial outfitting (document
number Service Code N, R, or V, and Fund Codes equals: VO (Victor Oscar), V7 (Victor
Seven), or LQ (Lima Quebec), QU (Quebec Uniform) or QZ (Quebec Zulu)), then:
C4.10.11.1. Reject requisitions that are more than one day in the future. If
the document number ordinal date YDDD (rp 36-39) converted to CCYYDDD is greater
than the current date plus 1 (CCYYDDD + 1), reject with Supply Status CD, and if less
than or equal to the current date plus 1, allow to process.
24
Refer to ADC 427A.
C4-61 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4.10.11.2. Reject requisitions that are greater than one-year-old. If the
document number ordinal date YDDD (rp 36-39) converted to CCYYDDD is equal to or
less than the current date minus 1 year (CCYYDDD - l000), reject with Supply Status
CD, and if greater than the current date minus 1 year (CCYYDDD - 1000), allow to
process.
C4.10.12. DAAS and the source of supply will perform validation of requisitions,
modifiers, and follow-ups that can be treated as requisitions for authorized ordering, bill-
to, or ship-to DoDAACs according to the DoDAAC Authority Codes below (Table C4.
T3.), and will reject requisitions that do not meet the DoDAAC authority code edits.
DAAS or the source of supply will furnish Status Code CX to advise all concerned of the
rejection of the requisition. If the transaction failing the edit is a modifier, then DAAS or
the source of supply will reject with Status Code D7 (see Table C4.T5.).
C4-62 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4-63 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4-64 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
28
This data element is referred to as Supplemental Data under the DLMS.
29
Elimination of requirement to change the priority on CJCS project code requisitions last reported as not
implemented by USAF, USMC, and DLA (Subsistence). Refer to AMCL 9.
30 Edit is mandatory during DAAS processing and optional for DoD sources of supply.
C4-65 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C4-66 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
31
Deferred implementation of PD/RDD compatibility edits and furnishing BK supply status under Approved DLMS
Change 57 are authorized pending supply source system modernization. BK status resulting from ADC 57 not
transmitted to US Army customers.
32 Non-date entries in the RDD field; such as, Codes E, F, N, R, 444, 555, 777, and 999, are referenced as Special
C4-67 CHAPTER 4
DLM 4000.25, Volume 2, January 22, 2024
Change 17
33 Use of the RDD to fill subsistence items last reported as not implemented by DLA (Subsistence). Refer to AMCL 7.
34 Not applicable for intra-USAF requisitions
35 Refer to ADC 1065.
36 Use of RDP for conventional ammunition last reported as not implemented by USAF. Refer to AMCL 148.
C4-68 CHAPTER 4
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5. CHAPTER 5
STATUS REPORTING
C5.1. SUPPLY AND SHIPMENT STATUS - GENERAL
C5.1.1. Status Data. Status data is either supply status or shipment status.
Sources of supply to include inventory control point (ICP)/integrated materiel manager
(IMM) and shipping activities prepare status transactions using the applicable
transaction described under paragraphs C5.1.2. and C5.1.4. Status documents from
sources of supply will be forwarded to the Defense Automatic Addressing System
(DAAS) for transmission to status recipients. Status data may be informational or
require additional action by organizations based on the assigned status code. Status
recipients include, but are not limited to, requisitioners, storage activities, control offices,
and/or monitoring activities.
C5.1.1.4. There are additional processing procedures over and above those
contained in this chapter that must be applied for serially managed materiel requiring
owner visibility at DLA Distribution Centers. The identity of the materiel and the additive
procedures are in Chapter 30.
1
Refer to ADC 1198
C5-1 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.2. Transactions. This chapter address procedures applicable to supply and
shipment status. The DEDSO Website provides DLMS electronic data interchange
(EDI) transaction formats on the DLMS Implementation Convention (IC) page. The IC
page also includes the corresponding MILSTRIP transaction formats by document
identifier code (DIC). The corresponding MILSTRIP legacy 80 record position
transaction functionality is identified for information purposes in a mixed DLSS/DLMS
environment.
C5.1.2.1. Supply Status. Use the DLMS 870S Supply Status transaction to
provide supply status. 2
2
Organizations furnishing Materiel Returns Program (MRP) supply status will use the DLMS 870M
transaction. DLMS Volume 2, Chapter 11 addresses MRP procedures.
3
Organizations furnishing Materiel Returns Program (MRP) shipment status transactions will use the
DLMS 856R transaction. DLMS Volume 2, Chapter 11 addresses MRP procedures.
C5-2 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
Up and Product/Item Description (PID) 05, Code 2 to identify requisition follow-up
requests for an improved estimated shipping date. This transaction provides the
functionality of MILSTRIP legacy DIC AFC.
4
The Request for DoDAAC of Initial Transportation Shipping Activity transaction is applicable in a mixed
DLMS/MILS environment where a separate transaction is needed to provide the requested information.
Under DLMS, the distribution depot identifies the shipping activity in the shipment status transaction,
eliminating the need for a follow-up. Refer to ADC 223.
C5-3 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
requests for supply assistance). Organizations will identify additional status addressees
in the original requisition and/or requisition-related transactions, as applicable. DAAS
generates supply status in selected situations resulting from item identification edits but
will indicate their RIC as the MESSAGE FROM address in the supply status.
C5.1.3.1.1.2.1. Backorder.
C5-4 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.3.1.5. Air Force Integrated Logistics Solution-Supply (ILS-S)
(Retail Supply). Supply Status DLMS 870S will be used on an intra-Air Force basis to
provide the latest status to the intended receiving activity. Additionally, supply status
will be used to support the unique item tracking (UIT) program for positive inventory
control (PIC) nuclear weapons related materiel (NWRM) by providing UII and/or serial
numbers. For legacy items where the unique item identifiers (UIIs) have not been
marked in accordance with item unique identification (IUID) policy, the serial number
alone will be passed.
5
Refer to ADC 257, DLMS Shipment Status Generated by Consolidation and Containerization Point
C5-5 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
support item unique identification (IUID) and intransit visibility requirements as directed
under DoD policy/procedures (DoDM 4140.01), when available and pending full DLMS
implementation/modernization. In support of FIAR, accountability and management of
capital equipment assigned under an established UIT program requires serialization
data visibility. 6 Submitters must prepare shipment status citing the applicable serial
number(s) and include the UII when available. 7 Shipment status will be provided by the
DoD shipping activity, the CCP, or by the source of supply 8 using the DLMS 856S.
Maintenance activities (organic and commercial) will provide shipment notification to the
receiving activity and other interested parties when materiel is shipped to the distribution
depot, DLA Disposition Services Field Office, or other designated receiving activity per
source of supply/inventory control point guidance. This may be accomplished using
either the DLMS 856S Shipment Status, or the DLMS 856 Advance Shipment Notice
(ASN), provided via Wide Area Work Flow (WAWF). 9 The DLMS Shipment Status will
include asset visibility content, such as IUID, and intransit visibility requirements, such
as passive RFID and the TCN as directed under DoD policy/procedures (DoDM
4140.01). DLMS enhancements include, but are not limited to the following:
C5.1.4.1.2. For UIT purposes, the UII (when available) and serial
number will be added to the shipment status transaction. Serial number without the
applicable UII may only be used during MILSTRIP/DLMS transition and pending
implementation of IUID capability. Refer to Chapter 30 for UIT guidance.
C5.1.4.1.3. Under the DoD IUID Supply Policy, the UII and/or serial
number (when available) must be added to the shipment status transaction. Serial
number without the applicable UII may be used only during MILSTRIP/DLMS transition
and pending implementation of IUID capability. Paragraph C5.1.4.5 contains specific
procedures to identify the UII in shipment status transactions when the NSN(s) contains
the IUID Indicator Y denoting that serialized item management is required. Capital
equipment assigned under an established UIT program requires serialization data
visibility and therefore must cite the serial number and include the UII when available.
6
Refer to ADC 1198B
7
Refer to ADC 1198
8
Direct vendor delivery shipment status using the 856S includes shipment status prepared by the DLA-
sponsored Defense Planning and Management System (DPMS) application.
9
Business rules for use of the 856 for GFM or Property Transfer, including internal DoD transfers, are
evolving. Refer to the Defense Pricing and Contracting policy for UID. Specific applicability and
interoperability issues to be resolved by the UID Program Office and ODASD(Logistics).
10
Refer to ADC 223, DLMS Shipment Status Enhancements: Secondary Transportation Number, Initial
Shipping Activity, Carrier Identification, and POE, approved for phased and staggered implementation.
C5-6 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.4.1.5. Identification of the carrier when other than United States
Postal Service (USPS) by name and Standard Carrier Alpha Code (SCAC). 11
C5.1.4.1.10. The shipment status may include the unit price (required
for Distribution Standard System (DSS)-generated shipment status; otherwise
optional). 16
11
Ibid.
12
Ibid.
13
Ibid.
14
Refer to ADC 242, Shipment Status DS 856S: Priority Designator (PD), Transportation Priority, Project
Code, Special Requirements Code, approved for phased and staggered implementation.
15
Ibid
16
Refer to ADC 242A, Inclusion of Unit Price on DLMS Shipment Status (DS 856S).
C5-7 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.4.1.11.2. DAAS will recognize the inclusion of the PDREP-
AIS DoDAAC in the shipment status and forward a copy of the shipment status for use
in exhibit tracking.
C5-8 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.4.2.1.2. Shipment status information content may be
repeated from the original shipment status when this information is available, (e.g.,
when the original shipper was a co-located distribution depot). Where access to the
original shipment status information is not available, the original data content will not be
perpetuated and applicable data fields will not be populated.
C5-9 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
just need to be read and an XML Visibility transaction sent to DAAS recording the tag
read event. If there is no document number either on the inbound data or on the pack
list/shipping documentation, then do not generate the DLMS 856S for conveying the
pRFID tag. This is to preclude a mismatch of data with the original DLMS 856S
transmitted by the ICP, that will have a document number.
C5-10 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5-11 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5-12 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
materiel requirements, and non-MILSTRIP Shipments (e.g., DD Form 1149) to Off-Base
Customers. The value of this transaction to the receiving activity is to support passive
RFID-enabled receipt processing. DLMS applications not supporting passive RFID may
disregard this status or choose to append the mode of shipment and the shipment date.
New content on the shipment status should not be viewed as replacement values for a
previously received shipment status matching on document number/suffix.
C5.1.4.4.2. For UIT purposes, the IUID and/or serial number. Serial
number without applicable IUID may be used during MILSTRIP/DLMS transition and
pending implementation of IUID capability. Refer to Chapter 19 “Procedures For
Serially Managed Materiel Requiring Owner Visibility”, for UIT guidance.
C5-13 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
long-term end state goal is to rely on the UII only. Table C5.T2 shows the decision
matrix that applies to scenarios where the UII and/or serial number may not be available
when the item is being shipped. The overriding vision is that, pending full transition to
DoD IUID Supply Policy using the UII, processing of outgoing shipments does not stop
due to lack of a viable UII and/or serial number when the NSN contains an IUID
Indicator Y. Capital equipment assigned under an established UIT program requires
serialization data visibility and therefore must cite the serial number and include the UII
when available.
Machine
Release
UII Serial Number Approved UIT Readable Serial
Shipment?
Number
Y Y N Y Y
Y N N N Y
N Y N Y Y
N N N N Y
Y Y Y Y Y
Y N Y N N
N Y Y Y Y
N Y Y N N
N N Y N N
Note: N (No) in the Release Shipment column indicates additional
research is required by the shipping activity to identify a valid UII and/or
serial number or to hand type the serial number data when required for
UIT items.
C5.1.4.5.4. Due In Record. Receiving activities will use the UIIs and/or
serial numbers in the shipment status to create or update the due-in record. This
C5-14 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
information will be used to verify the UIIs actually received. Receiving activities will
follow the supply discrepancy reporting procedures to report mismatches as
appropriate.
C5-15 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
to perpetuate the IUID content to the ship-to activity. DAAS, at a minimum, will indicate
the following:
• DIC AS1 if the ship-to activity is the requisitioner. If the ship-to activity is
not the requisitioner, then indicate DIC AS2. The ship-to will be
perpetuated from the DLMS 856S (DIC AS6).
• The RIC-To from the DLMS 856S (DIC AS6) becomes the RIC-From in
the DLMS 856S (DIC AS1) (indicating that the shipment status is provided
on behalf of the manager).
• Distribution Code 2 or 3
C5-16 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.4.5.5.8. Shipment Status on Multiple Freight Pieces. For a
shipment containing IUID content and shipped in multiple freight pieces, shippers are
NOT authorized to execute the movement of the shipment using multiple freight piece
procedures (e.g., citing the same TCN for all boxes). Those shipments must be
“partialled” by using the 16th position of the TCN to uniquely identify each freight piece.
A separate DLMS 856S Shipment Status will be transmitted for each document number
– partial TCN pair, identifying the contents of each freight piece, to include pRFID tag(s)
and UII(s) and/or serial numbers.
C5-17 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.4.6.1.3. It will repeat the shipment status information from the
original shipment status message, in addition to any changes to the original information.
DAAS will not distribute the shipment status change/update to MILSTRIP legacy
recipients.
C5-18 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.6. Status Recording. Organizations will promptly record all status
information received (automatically and/or in response to requisition inquiries) to
applicable due-in records and/or requisition history (status) files, and, in the case of the
DLA Disposition Services, the disposal suspense file. Status recipients will use supply
status data to establish or update the due-in record to monitor for materiel receipts
under Chapter 13. In addition, status recipients will:
C5.1.6.2. Review the DLMS 870S received for any additional action required
by the status code if any.
C5.1.6.3. Treat shipment status received as notice shipment has been made
and that additional follow up will only result in receipt of another shipment status
document.
C5-19 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
modifications, and requisition inquiries (follow-ups and requests for supply assistance).
MCAs will send reject status for requisitions they process. Sources of supply will
maintain and send current supply status as provided below. For these purposes, MCAs
and sources of supply will maintain accessible requisition history records for a minimum
of 6 months after completing a shipment of materiel or canceling a requisition, to
provide for timely status responses. MCAs will maintain requisition history records until
contract termination.
17
Refer to ADC 465, Contract Data for 870S_BV Status
C5-20 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
designated as STATUS TO organizations, as information addressees on requests for
additional information. When an inquiry for additional information is made, the source of
supply will send a DLMS 870S with Status Code BD, to all designated STATUS TO
organizations. Sources of supply will suspend further action on requisitions awaiting
additional information until a response is received or until 30 calendar days from date of
inquiry, whichever occurs first. Upon receipt of requested information, the source of
supply will continue normal processing. If the organization does not provide needed
information within 30 calendar days, the source of supply will reject the requisition using
a DLMS 870S with Status Code D3.
18
Refer to ADC 242B.
19
Refer to ADC 1075.
C5-21 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
Table C5.T3. DLA Distribution Center and Co-Located Material Processing Centers
DISTRIBUTION CENTER WITH DISTRIBUTION MPC ROUTING
CO-LOCATED MPC CENTER DODAAC IDENTIFIER CODE
Norfolk SW3117 PSJ
Jacksonville SW3122 PSU
San Diego SW3218 PSK
Puget SW3216 PSN
Yokosuka SW3142 PSL
Sasebo SW3143 PSM
Guam SW3147 SCN
Pearl Harbor SW3144 PSY
Sigonella SW3170 SNH
Bahrain SW3183 SNN
Everett, Washington State SW3237 SNY
Little Creek, Norfolk, VA SW3187 SEF
Groton, Ct SW3188 SEX
Djibouti SW331M S5W
Rota, Spain SW310J SC1
Salalah, Oman SW3156 S1C
C5-22 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
the supply condition, and other mandatory data elements for the shipment status
are identified in Chapter 16.
20
Authorized for use on an intra-Army basis (ADC 191) and later expanded to inter-Service/Agency use
(ADC 312). Not implemented by DLA and other Components.
C5-23 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
applicable to materiel obligations including procurement for DVD. Conversely, the
source of supply will reject requisitions that contain Advice Code 2C, 2J, 2T, or 2W with
Status Code CB when items are not available for immediate release or cannot be
supplied by the SDD/RDD/RDP, with a DLMS 870S.
C5-24 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.7.12.9. Materiel Returns Status. Use Chapter 11 procedures for
providing materiel returns supply status transactions resulting from processing OMRs
and OMR-related transactions.
C5.1.7.12.10. Free Issue. Requisitions that fail free issue validation will
be rejected with Status Code CM; a new funded requisition may be submitted if the
materiel is still required. Requisitions that fail free issue validation after materiel release
(post-post requisitions/issue) may be handled as funded requirements. In this case, the
source of supply will furnish Status Code DT alerting eligible status recipients that the
post-post requirement is not authorized for free issue and to adjust fund obligation
records as materiel will be billed to the requisitioner.
21
Refer to ADC 1091, SDRs Requesting Expedited or Replacement Shipment.
C5-25 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.7.13.1.1. Two calendar days from receipt of PD 01-08
transactions.
C5-26 CHAPTER 5
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C5.1.8.2.2. When there is a record of the requisition cancellation,
address the status transaction to the organization(s) identified in the cancellation
request, including any additional status organizations.
C5-27 CHAPTER 5
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6. CHAPTER 6
PHYSICAL INVENTORY CONTROL
C6.1. GENERAL
C6.1.1. Purpose.
C6.1.1.2. There are additional processing procedures over and above those
contained in this chapter that must be applied for items identified as serially managed
materiel requiring owner visibility at DLA Distribution Centers. The identity of the
materiel and the additive procedures are in Chapter 30.
C6-1 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
physical inventory in workload bank or in process; or response to follow-up when
inventory already complete (Management Codes R, S, and Y respectively).
C6-2 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
change elements of data pertaining to an item of supply. This transaction provides
MILSTRAP legacy DIC DZB functionality.
C6.1.3.2.4. ammunition,
C6.1.3.2.6. subsistence.
C6.1.4. Exclusions
C6-3 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.2. POLICY. DoD policy is contained in DoDM 4140.01, “DoD Supply Chain Materiel
Management Procedures”.
C6.2.1. Purpose. The purpose of the DoD physical inventory control process is to:
C6.2.2.2. The dynamic nature of the physical inventory control function and
the cost of counting and reconciling records require that the approach be more selective
than the "100 percent wall-to-wall total item count" concept. Available inventory
resources will be directed toward potential and actual discrepancies, controlled
inventory items, and weapon system critical items for which maximum returns are
derived from applied resources.
C6.2.2.4. Storage activities will make use of any one or a combination of the
following three inventory counting approaches, as appropriate to the physical inventory
item policy requirements, storage facility physical constraints, physical inventory support
system capabilities, types of items, and inventory accuracy conditions.
C6-4 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.2.2.4.2. Statistical sample counts that are statistically significant and
representative of the total inventory item population are an efficient approach to quickly
determine the accuracy of the inventory with minimal operational disruption. When
statistical sample counts are allowed and the resultant count is within required
tolerances, the inventory is considered complete. If the statistical count is outside the
allowed accuracy tolerance, then the entire results of the statistical sampling must be
voided. This requires scheduling another physical inventory via another sample count,
cycle count, or wall-to-wall count as appropriate to the accuracy conditions determined
by the first sample count. If another sample count is used, it will not be the same
sample or a sub-set of the same sample selected earlier.
C6.2.2.5. All physical counts will be blind counts; that is, personnel
conducting physical counts will have no prior knowledge or access to the on-hand
quantity balance in the inventory records. In those rare instances where segregation of
duty controls cannot guarantee blind counts, other local effective risk mitigation
techniques will be applied such as increased supervision and two member count teams.
C.6.2.2.7. The implementing procedures for the DoD Components are to:
C6-5 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C.6.2.2.7.3. Ensure that sufficient emphasis is placed on materiel
accountability and inventory accuracy to promote improved performance of individuals
directly responsible for the care, security, and management of DoD supply system
materiel, as well as those responsible for making reports on the status of that inventory.
C6.2.3. Security of Materiel. Security is the first line of defense for physical
inventory control; therefore, DoD Components will pay special attention to safeguarding
of inventory items. This will include analysis of loss rates through inventories, financial
liability investigation of property loss reports (DD Form 200,), and criminal incident
reports, to establish whether repetitive losses indicate criminal or negligent activity.
C6-6 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
Physical security procedures for supply system materiel are contained in
DoD 5200.08-R, “Physical Security Program.”
C6.2.4. Asset Management. Inventory Control Points (ICPs) and storage activities
will collaborate to ensure that inventory data in their respective systems is the same,
thus becoming, in effect, a single item inventory record. At minimum, the total item
property record will include materiel that is due-in, in transit, in organic maintenance
facilities, in a contractor's custody, on loan, on-hand in distribution centers, reported on-
hand at retail activities, and for reported assets in the custody of users. The record or
record set will identify the quantity, condition, and value of the item assets for each
organizational entity having physical custody of these assets.
C6-7 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.2.5.4. US Air Force (USAF) Contractor Inventory Control Point (CICP)
Responsibilities
C6-8 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
through/customer pickup) in the MRC identifies the exclusions to the “Intransit Balance.
The materiel receipt acknowledgement (MRA)/turn-in receipt acknowledge (TRA)
received from the customer constitute the receipt acknowledgment. The intransit
balance is a cumulative calculation and is not restricted to activity occurring during the
day/month being reconciled.
C6.2.6. End of the Day Processing. Use the following end of the day processing
procedures as follows:
C6-9 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.2.6.3.2. Include the Materiel Release Advice Count to the EOD
Transaction Count transaction (DLMS 846P with BIA02 B1) provided to the USAF GFP-
A APSR for reconciliation with the USAF CICP inventory balance records. The Materiel
Release Advice Count represents the number of MRC and DRC transactions (DLMS
945A) received by the USAF CICP during the day or month being reconciled. The USAF
CICP will transmit the sum total of MRC and DRC transactions combined into a single
value.
C6-10 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
adjusted with Inventory Adjustment Increase/Decrease (Accounting Error) (DLMS 947I
with Quantity or Status Adjustment Reason Code AB; MILSTRAP legacy DIC D8B/D9B).
6.2.6.5.4. Update the affected record on-hand balance with the storage
activity's closing on-hand balance for unresolved mismatched quantities. The
mismatched quantity (gains and losses) will be adjusted with Inventory Adjustment
Increase/Decrease (Accounting Error) (DLMS 947I with Quantity or Status Adjustment
Reason Code AB; MILSTRAP legacy DIC D8B/D9B). Owner/managers will refer to
section C6.6 for guidance on research of potential or actual Inventory Adjustments.
C6-11 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.2.6.6.1. Receipts (DLMS 527R with 1/BR02 Transaction Type Code
D4; MILSTRAP legacy DIC D4_/D6_).
C6.2.6.6.6. For intra-Navy use only; Navy also provides an end of day
transaction count for Asset Status Reports (DLMS 846I).
C6.2.6.6.7. For U.S. Air Force CICP only. Materiel Release Advice
(DLMS 945A with 1/W0611 Transaction Type Code NJ and NM; MILSTRIP legacy DIC
AR_). The Air Force CICP must combine the total sum of MRC and the total sum of
DRC into a single value.
C6.2.7. Reconciling Total Item Property Records with Financial Records. Owning
DoD Components will reconcile total item property records and financial records as
prescribed by DoD 7000.14-R, “Department of Defense Financial Management
Regulations (FMR)” to ensure compatibility of the total inventory value reflected by
these records and associated reports.
C6-12 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.2.10. Inventory Prioritization. DoD Components will select and prioritize items
for inventory for which they are accountable as follows:
C6-13 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
stratifications used for sample will be included in the CFO Inventory Value Sample Plan
for that year.
C6-14 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.2.10.2.1.7. Inert nuclear ordnance materiel.
C6-15 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.2.12. Accuracy and Performance Goals. The acceptable DoD accuracy and
performance goals are as follows:
C6-16 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
Table C6.T1. General Supplies Record Accuracy Goals Stratification Sub-Populations And
Associated Goals And Tolerance Levels
GOAL TOLERANCE
CATEGORY SUB-POPULATION
(PERCENT) (PERCENT)
1
Applicable Units of Issue: AT, AY, BF, BK, CD, CF, CZ, DZ, FY, FT, FV, GP, GR, HD, KT, LB, MR, OZ,
OT, PG, PR, SE, SF, SO, SP, SY, TD, TE, TF, TN, TO, TS, MC, MX, YD
C6-17 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.3.3.1. Item Characteristics. Storage activities will initiate all scheduled
inventories based on item characteristics, specifically the controlled inventory item code
and any other category codes designated by the DoD Components that require physical
inventory not less than once each fiscal year, with a Physical Inventory Request
Transaction using Type of Physical Inventory/Transaction History Code G.
C6.3.3.2. Selection and Prioritization Model. Storage activities will initiate all
scheduled inventories based on selection and prioritization model criteria with a
Physical Inventory Request Transaction using Type of Physical Inventory/Transaction
History Code I.
C6-18 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.3.4.2. Spot Inventory
2
Refer to ADC 415 available at the DLMS ADC 400-499 page.
3
Ibid
C6-19 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
Inventory/Transaction History Code E) is canceled, it must be rescheduled within 15
calendar days.
C6.3.6.3. In-Float Document Control. The storage activity may reduce the
volume of in-float accountable documents during the period required for an item count
by suspending the issue of low priority materiel release transactions from items
undergoing inventory. However, materiel will be released for items undergoing
inventory when such release is necessary to meet the order/ship timeframes prescribed
by DoDM 4140.01, to include the recognition of the required delivery date. The storage
activity may also reduce the volume of in-float accountable documents by deferring
routine SCC changes, providing that it complies with Chapter 7 control requirements.
C6-20 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
with Quantity or Status Adjustment Reason Code AA; MILSTRAP legacy DIC D8A) with
zero quantity for each line item to the owner/manager to indicate completion of the
inventory. The owner/manager will update the date of last inventory using the
adjustment transaction date.
C6.3.7. Reconciling Manual Records for Controlled Items. When manual records
are maintained for control of assets in secured storage, the storage activity, will at
minimum reconcile these records at the time of inventory with the corresponding
storage activity records and physical materiel counts.
C6-21 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.3.8.3. No Record of Physical Inventory Request. If the storage activity
does not have a record of the owner/manager original Physical Inventory Request
Transaction, the storage activity will process the Physical Inventory Request
Transaction with Management Code X as an original Physical Inventory Request
Transaction.
C6.4.1. Policy. DoD Components will ensure that potential or actual Inventory
Adjustments (Physical Inventory), (DLMS 947I with Quantity or Status Adjustment
Reason Code AA; D8A/D9A), are researched in accordance with the value of the
adjustment and type of item. The DoD criteria for this research are set forth in Table
C6.T3, and will be used as the basis for selective research for supply system materiel.
A reduction of the volume of erroneous adjustments can only be achieved by
conducting specified degrees of research before posting the adjustment transaction.
More stringent research requirements may be imposed by DoD Components based
upon the limits of available resources and upon specific asset control problems.
However, in no case will adjustments be processed against items without required pre-
adjustment research having been performed (see Table C6.T3.).
C6-22 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.4.3.2. Mandatory Causative Research. The storage activity must
complete mandatory causative research within 45 calendar days from the date the
adjustment transaction was posted. If sample causative research is used as allowed by
Table C6.T3., Minimum Research Requirements, the sample causative research must
be completed within 45 calendar days from the date the sample causative research
listing is created.
C6.4.4.2. Transaction History Data. The storage activity will send transaction
history data by submitting the affected transactions identified as a historical submission
with beginning segment Action Code W1. DLMS transactions subject to historical
submission are: receipt, issue, materiel release order, materiel release advice, and
inventory adjustment (DLMS 527R, DLMS 867I, DLMS 940R, DLMS 945A, and DLMS
947I, respectively). When no history is available for the selected timeframe, submit a
Response to Transaction History Request (No History Available) Transaction with Type
of Physical Inventory/Transaction History Code 8 or 9. (Storage activities still operating
under MILSTRAP will send legacy DIC DZK Transaction History Transmittal for all
transactions affecting the balance for the requested timeframe).
4
The owner/manager may use Error Classification Codes in Inventory Adjustment (Accounting Error)
Transactions (DLMS 947I with Quantity or Status Adjustment Reason Code AB; MILSTRAP legacy DIC
D8B/D9B) pending establishment of single shared asset balances (see paragraphs C6.2.2. and C6.2.4.).
C6-23 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.4.6. Error Classification Feedback and Correction
C6.4.8.1.1. Reverse the issue, adjust the storage activity record on-
hand quantitative balance to zero, and send an inventory adjustment decrease
transaction (DLMS 947I with Quantity or Status Adjustment Reason Code AA;
MILSTRAP legacy DIC D9A) for the adjusted quantity to the owner/manager attempting
to issue the materiel, citing denial Management Code 1, 2, 3, or 4, and send an
C6-24 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
inventory adjustment decrease to any other owners affected by the denial loss, citing
denial Management Code Q.
C6.5.4.1. Absolute adjustment rates will include all gain and loss reversals
from reporting and prior quarters’ adjustment transactions.
C6.5.4.2. Initial adjustment rates will not include gain and loss reversals from
reporting or prior quarters’ adjustments:
5
Refer to ADC 415 available at the DLMS ADC 400-499 page.
C6-25 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.6. RESEARCH OF POTENTIAL OR ACTUAL INVENTORY ADJUSTMENTS
(ACCOUNTING ERRORS) – (DLMS 947I with Quantity or Status Adjustment Reason
Code AB) - Document Identifier Code D8B/D9B 6)
C6.6.1. Policy. DoD Components will ensure that potential or actual Inventory
Adjustments (Accounting Errors), DLMS 947I with Quantity or Status Adjustment
Reason Code AB; D8B/D9B, are researched in accordance with the value of the
adjustment and type of item. The DoD criteria for this research are set forth in Table
C6.T3. and will be used as the basis for selective research for supply system materiel.
More stringent research requirements may be imposed by DoD Components based
upon the limits of available resources and upon specific asset control problems.
Though physical inventory adjustments are based on physical counts, accounting
adjustments are based on the reconciliation of inventory records as part of End-of-Day
or Location Reconciliation business processes. When differences exist between the
‘systems’, an accounting adjustment (gain/loss) (DLMS 947I with Quantity or Status
Adjustment Reason Code AB; DIC D8B/D9B) will be created to adjust the
owner/manager’s total item property record inventory balance to agree with the storage
activity’s closing end of day balance. As such, the causes of accounting adjustments
are driven by the handling of ‘transaction data’ versus the physical handling of materiel.
Therefore, research requirements will focus on events/processes that cause the
databases (between the storage activity and total item property record) to be out of
sync. DoD Components will research transaction histories and violation files to locate
‘missing’ supply transactions, clear exceptions, process the appropriate ‘supply’
transaction, and reverse the accounting adjustment to resolve the original mismatch
condition.
6
Refer to ADC 414 available at the DLMS ADC 400-499 page.
C6-26 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.6.2.4. Evaluate indicators of trends or system problems for corrective
action.
7
The owner/manager may use Error Classification Codes in Inventory Adjustment (Accounting Error)
Transactions (DLMS 947I with Quantity or Status Adjustment Reason Code AB; MILSTRAP legacy DIC
D8B/D9B) pending establishment of single shared asset balances (see paragraphs C6.2.2. and C6.2.4.).
C6-27 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
DoD 7000.14-R, will be referred to security officials of the storage activity at which the
adjustment occurred to determine whether there is culpability or when fraud, waste, or
abuse is suspected (see Table C6.T3.).
8
The location reconciliation process will not be required with the establishment of single shared-asset
balances (see paragraphs C6.2.2. and C6.2.4.).
C6-28 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.2.12.3. The DoD Components may impose more stringent standards internally. The
record reconciliation program is subject to the quality control checks delineated in
section C6.10. Errors will be subject to validation and research before they are counted
as errors. The DoD Components will collect and analyze all Type III errors (see
subparagraphs C6.8.1.2.3. and C6.8.2.2.3.) by element.
C6-29 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.8.1.5. Comparison of Storage Locations with Locator Records. The
proper sequence for operating a location survey requires comparing assets in storage
locations with locator records. This sequence of operation is important to detect assets
in unrecorded locations.
C6.8.1.9.3.2. SCC.
C6-30 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.8.1.9.3.3. Controlled inventory item code (see DoD 4100.39-M,
Volume 10, Table 61). Verification of the code will consist of ensuring that assets are
stored in areas providing the degree of security commensurate with the assigned code.
9
The location reconciliation process will not be required with the establishment of single shared-asset
balances (see paragraphs C6.2.2 and C6.2.4).
C6-31 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.8.2.2.3.2. Ownership/manager identifier.
C6-32 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6-33 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
requests to the owner/manager records. When a mismatch is programmatically
unresolved, Inventory Adjustment (Accounting Error) Transaction (DLMS 947I with
Quantity or Status Adjustment Reason Code AB; MILSTRAP legacy DIC D8B/D9B) will
be processed to adjust the owner/manager records. All Type I, II, III, and IV
mismatches meeting the criteria for causative research (see Table C6.T3.) will be
resolved as follows:
C6-34 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.9. RETENTION OF ACCOUNTABLE DOCUMENTATION. DoD requires that all
Components meet audit requirements following the processing of documents and data
and completion of the research efforts. Owners and storage activities will maintain
records and supporting documentation in accordance with DoDI 5015.02 and DoD
7000.14-R, Financial Management Regulation, Volume 1 Chapter 9. The following
business rules apply to storage activities and owners when retaining records for audit
purposes:
C6.9.2. Transaction History. Retain registers, records, files, tapes, and data in a
format useful for audit trail purposes. Automated inventory control systems facilitate the
output of transaction histories that indicate the date the last physical inventory was
conducted for each item.
C6.10.1. Goals and Objectives. DoD Components will establish a quality control
program at each owner/manager and storage activity. Portions of the program can be
accomplished during ongoing practices within inventory processes. Quality control
results will assist management in identifying those human, procedural, or system errors
that adversely affect record accuracy and in achieving better control over physical
materiel and warehousing practices. Within the scope of this quality control program,
work processes directly related to the control of physical materiel will be monitored for
attained quality levels and performance evaluated on improvements, not numerical
goals. Accordingly, all quality control programs will include reviews to assess the
accuracy/quality of the following work processes:
C6-35 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.10.1.3. Issuing Practices. This includes checks of legibility of issue
documents; accuracy of stock selection as to identity, quantity, unit of issue, shelf life,
SCC, and type of pack (subsistence only); marking of outgoing shipments; and release
to carriers.
C6-36 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
The quality control program will include provisions for initiation of corrective action when
acceptable quality levels are not met.
10
Refer to ADC 415 available at the DLMS ADC 400-499 page.
11
Book-to-Book Adjustments are not included in section 1.
C6-37 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.11.1.1.1.5. (Line 1.E.) Causative Research Variance Rate.
The percentage of the total number of line items inventoried (scheduled and
unscheduled) that had an inventory variance that met the Causative Research
threshold. Compute this figure by dividing the lines that meet Causative Research
Criteria by the total line items inventoried and multiplying by 100. ((1D/1A) x 100).
12
Book-to-Book Adjustments are included in section 2.
13
Book-to-Book Adjustments are included in section 3.
C6-38 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.11.1.1.3.1. (Line 3.A.) Value of Adjustment Gains (D8A).
Monetary value of gain adjustments excluding the monetary value of gain reversals
processed during the report period.
14
Book-to-Book Adjustments are included in section 4.
C6-39 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.11.1.1.5. Denial Rates
C6-40 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.11.2. Ammunition Performance Standards and Data. (The information in this
section corresponds to information shown on DD Form 2338-1.)
15
The location reconciliation process will not be required with the establishment of a single shared asset
balances (see paragraphs C6.2.2. and C6.2.4.).
C6-41 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.11.2.1.3.2. (Line 3.B.) Survey Errors. The total number of
location discrepancies as defined in subparagraph C6.8.1.8. Report only one error per
stock number per location.
16
Performance data maintained by owner/Inventory Manager regardless where material is stored.
17
The end of day process and location reconciliation process will not be required with the establishment
of single shared asset balances (see paragraphs C6.2.2 and C6.2.4).
C6-42 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.11.2.2.2.1. (Line 2.A.) Number of Location Reconciliation
Adjustments. The number of location reconciliation adjustments (DLMS 947I with
Quantity or Status Adjustment Reason Code AB; MILSTRAP legacy DIC D8B/D9B).
C6-43 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.11.2.2.5.3.1.3. (Line 5.C.(1)(C)) Gross Adjustments.
Computed as lines (5C(1)(A) + 5C(1)(B)).
C6-44 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.11.2.2.6.1. (Line 6.A.) Average Value of Inventory. Divide the
total value of gross adjustments by the average value of inventory and multiply by 100.
((5C)(1)(C) / 5A) x 100).
C6-45 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.12.1.1. Reported transactions indicate that the ICP and storage activity
records are inconsistent.
C6.12.2. Inventory Control Point Action. ICPs use the Storage Item Data
Correction/Change Transaction to provide storage activities with data record changes on
supply items. The ICP enters the “correction/change code for storage item records” in the
18
Sample causative research in lieu of complete causative research for pilferable and CIIC 7 item
discrepancies with a value from $.01 to $2,500 may be accomplished to serve as a deterrent to fraud,
waste, or abuse and to identify systemic inventory and security problems. Causative research will be
conducted on all adjustments (gains and losses) of classified and sensitive items regardless of dollar
value of item or extended dollar value of adjustment. Causative research will be conducted on all
adjustments (gains and losses) of pilferable items, and CIIC 7 items, with an extended value greater than
$2,500, and all adjustments with an extended value of greater than $16,000 or greater than 25 percent
unit variance and greater than $5,000.
C6-46 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
transaction to provide information on the nature of the change, actions to be taken, and
data affected by the change.
C6.12.3. Storage Activity Action. Storage activities will use the Storage Item Data
Correction/Change Transaction to update stock records, item locator records, and bin
tags.
C6.13.1.2. Capital equipment items are items must; (1) have a FLIS IUID
Indicator (Y); (2) are within Classes of Supply II, VII, and VIII; and (3) have a current
Unit Price recorded in the FLIS of at least $100,000. Not all capital equipment items will
require serial number tracking. Materiel Owners will enable serial number tracking by
assigning an active UIT designator code to each selected capital equipment NSN.
19
Refer to ADCs 1198, 1198A, and ASC 1198B.
C6-47 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.13.2. Conduct of Physical Inventories. The transaction history request,
response to transaction history request when no history is available, physical inventory
request, response to physical inventory request and end of day transaction count will
not contain serial numbers or UIIs However, when the owner initiates a physical
inventory request for a capital equipment item (assigned under an established UIT
program) to assist in resolving discrepancies where the only difference between the
owner records and the storage activity records is the serial number (or UII if available),
the physical inventory request will contain Type of Physical Inventory Code B. Owners
will initiate a physical inventory when a mismatched condition on serial number (and UII
when available) is identified between its records and transactions received. The owner
will first request a physical inventory of all owners be conducted by the storage activity
that sent the transaction generating the mismatched condition. If the initial physical
inventory is unable to resolve the mismatched condition the owner may need to
coordinate requests for physical inventories with DLA Distribution to conduct inventories
of all owners at all other storage activities storing that NSN.
C6-48 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C6.13.3. Location Survey
C6.13.4.3. The combination of UII and serial number increases the accuracy
of inventory records across the DOD. When a serially managed item lacks a UII, there
is a potential for duplicate serial numbers. A duplicate serial number may surface as a
result of the record reconciliation. For mismatches due to a duplicate serial number, the
owner is responsible for taking the necessary steps to resolve the discrepancy.
C6-49 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
adjustments due to serial number/UII discrepancies resulting in a mismatch (Quantity or
Status Adjustment Reason Code AQ). Two inventory adjustment transactions are
required to correct the mandatory serial number/UII and to update the SCC.
C6-50 CHAPTER 6
DLM 4000.25, Volume 2, August 03, 2023
Change 16
owner records and the transactions received from the storage activity. The history
transactions will perpetuate the serial numbers/UIIs included in the original transactions.
C6-51 CHAPTER 6
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C7. CHAPTER 7
INVENTORY ADJUSTMENTS
C7.1. GENERAL
C7.1.1. Purpose
C7.1.1.3. There are additional processing procedures over and above those
contained in this chapter that must be applied for items identified as serially managed
materiel requiring owner visibility at DLA Distribution Centers. The identity of the materiel
and the additive procedures are in Chapter 30.
1
Refer to ADC 1198.
C7-1 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
markup language (XML) are also available. See the Defense Enterprise Data Standards
Office Website for available formats on the DLMS IC page.
Table C7.T1. DLSS DIC/DLMS Quantity Or Status Adjustment Reason Code Correlation
W1901 Quantity
Corresponding
or Status
Explanation MILSTRAP
Adjustment
legacy DIC
Reason Code
AA Inventory Adjustment (Physical Inventory). Gain or D8A or D9A
loss disclosed as a result of physical count of
stock, single adjustment.
AB Inventory Adjustment (Accounting Error). Gain or D8B or D9B
loss resulting from clerical or automated
information system errors which are not subject to
correction by reversal of original transaction,
single adjustment.
AC Inventory Adjustment (Condition). Gain, loss or D8C or D9C or
dual adjustment resulting from condition transfer. DAC
AD Inventory Adjustment (Purpose). Gain, loss or D8D or D9D or
dual adjustment resulting from purpose transfer. DAD
AK Inventory Adjustment (Logistics Transfer). Gain D8E or D9E
or loss of item management responsibility as a
result of logistics transfer.
AL Inventory Adjustment (Capitalization). Gain to, or D8F or D9F
loss from, a stock fund or stock fund division at
time of activation or subsequent extension/
expansion, as result of capitalization,
AJ Inventory Adjustment Decrease (Survey Process). D9G only
Loss from shrinkage, theft contamination,
deterioration, and/or expired shelf life, single
adjustment.
C7-2 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
Table C7.T1. DLSS DIC/DLMS Quantity Or Status Adjustment Reason Code Correlation
W1901 Quantity
Corresponding
or Status
Explanation MILSTRAP
Adjustment
legacy DIC
Reason Code
AI Inventory Adjustment Decrease (Disaster). Loss D9H only
from major disasters, fire loss, enemy action, act
of God, etc., single adjustment.
AE Inventory Adjustment (Reidentification). Gain D8J or D9J
resulting from inspection of an item in stock which
has been misidentified, single adjustment.
AF Inventory Adjustment (Stock Number Changes). D8K or D9K
Gain or loss resulting from stock number change. Inventory
Excludes change of unit price only. Adjustment
AN Inventory Adjustment (Unit of Issue Changes). (Catalog
Gain or loss resulting from unit of issue changes. Changes). Gain
Excludes change of unit price only. or loss resulting
from stock
number and/or
unit of issue
changes, single
adjustment.
Excludes change
of unit price only.
AG Inventory Adjustment (Ownership). Gain, loss, or D8S or D9S or
dual adjustment resulting from ownership transfer DAS
by the single manager conventional ammunition
(SMCA). Use is restricted to users of the
conventional ammunition system.
AH Inventory Adjustment (Other). Gain or loss for D8Z or D9Z
which a specific code is not otherwise provided.
(Assignor of code will maintain detailed
intelligence pertaining to its use and, as required,
will furnish these data.)
AM Inventory Adjustment (UII and/or serial number Not applicable to
missing). Gain, loss or dual adjustment resulting legacy
solely from UII and/or serial number missing. 2 MILSTRAP
2
Refer to ADC 1198A.
C7-3 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
Table C7.T1. DLSS DIC/DLMS Quantity Or Status Adjustment Reason Code Correlation
W1901 Quantity
Corresponding
or Status
Explanation MILSTRAP
Adjustment
legacy DIC
Reason Code
AQ Inventory Adjustment (UII and/or serial number Not applicable to
mismatch). Gain, loss, or dual adjustment legacy
resulting solely from UII and/or serial number MILSTRAP
mismatch. 3
3
Refer to ADC 1198.
C7-4 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C7.1.3.1. Single Adjustment. The single adjustment method accommodates
processing techniques that use individual increase or decrease adjustment actions
against the accountable and owner records.
C7-5 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
not otherwise provided. (The DoD Components will maintain detailed backup information
as to use and requirement for the transaction.)
C7-6 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C7.2.2.2. When inspection or technical/engineering analysis of materiel
confirms a product quality deficiency, possibilities for other use of the materiel within the
Department of Defense, as well as public health/safety and national security interests,
must be considered. Owners will determine if further use of the item can be made within
the Department of Defense.
C7.2.2.4. If the deficiency does not prohibit further DoD use (i.e., the defect is
minor or the item meets specifications for another national stock number (NSN)), owners
will direct storage activities to re-identify and/or transfer the suspended SCC Q materiel to
the appropriate condition. Storage activities will, within 3 calendar days from receipt of
the ICP direction, reclassify the SCC Q materiel to the appropriate condition. Report
completion of this action with an Inventory Adjustment transaction, using the same
document number originally used to report the materiel in SCC Q (i.e., the document
number of the original receipt or inventory adjustment transaction). For re-identifications,
storage activities will follow the procedure in C7.7.
C7.2.2.5. If the deficiency prohibits further DoD use, the materiel will remain in
SCC Q and owners will direct transfer of the materiel to the DLA Disposition Services
Field Offices following Chapter 16 procedures. Improperly documented, unauthorized
source, defective, non-repairable, and time-expired Aviation CSI/FSCAP materiel that is
not mutilated by the holding activity will be directed to the DLA Disposition Services Field
Office in SCC Q with Management Code S. All such materiel will be mutilated. When
turning such Aviation CSI/FSCAP materiel in to a DLA Disposition Services Field Office,
the turn-in document must clearly note that the part is defective, non-repairable, time-
expired, or otherwise deficient and that mutilation is required.
C7-7 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C7.2.3.3. Reclassification Procedures. When directed by the owner, storage
activities will, within 3 calendar days from receipt of an asset reclassification request,
reclassify the suspended materiel to its correct SCC. Report completion of action with an
Inventory Adjustment – Dual (SCC Change) using the same document number originally
used to record the materiel in SCC L (i.e., the document number of the original receipt or
inventory adjustment transaction). See C7.2.8. for storage activity asset reclassification
denial procedures when requested reclassification action cannot be done.
C7-8 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C7.2.5. Reclassification of SCC X 4
4
Refer to ADC 1159, New Supply condition Code X, Suspended (Repair Decision Delayed)
C7-9 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
owner of such simultaneous reclassification and automatic disposal action by entering
Management Code M (materiel condemned–excludes expired shelf-life materiel) or
Management Code T (materiel condemned–expired shelf-life materiel) in the inventory
adjustment transaction. Refer to C13.2.8.2.10.1. for exclusions from automatic disposal.
C7.2.8.1. SCC J, K, and R. Owners will review records for all materiel
suspended in SCC J, K, and R at least monthly and ensure that storage activities
accomplish reclassification actions within prescribed timeframes.
C7-10 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C7.2.8.4. SCC X. Although there is no prescribed timeframe for transferring
suspended materiel from SCC X, owners will review all records for materiel suspended in
SCC X at least semi-annually to ensure expeditious development of a repair process.
C7-11 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
corresponding Inventory Adjustment or Asset Reclassification Denial Transaction. In
response to a follow-up, when the corresponding inventory adjustment was previously
provided, the storage activity will resubmit the inventory adjustment transaction with
Advice Code 3P indicating it is a duplicate of a previously submitted transaction sent in
response to the follow-up. Caution must be used by recipient to assure the transaction is
not processed twice.
C7.3.1. Change of Ownership. Based on unique requirements of the SMCA and the
DoD Components authorized by DoD Directive 5160.65, “Single Manager for
Conventional Ammunition”, August 1, 2008, separate Inventory Adjustment (Ownership
Transfer) transactions have been developed to permit:
C7-12 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C7.3.4. Ownership Transfer via Ship-in-Place (Other than Ammunition/
Ammunition Related Materiel). 5 The term ship-in-place (also known as ship-to-self)
is a procedure that causes a custodial activity of a given materiel to transfer the
ownership without a physical shipment. These procedures do not apply to
ammunition and ammunition related materiel. Storage activities can recognize an
MRO for ship-in-place when the Ship-To DoDAAC matches the custodial activity
performing the transfer. In addition, a PMR is mandatory for every release request
to ensure the storage activity has the necessary information to perform the
transfer. The MRO and the PMR will serve as evidential matter to justify the
transfer.
5
Refer to ADC 1395.
C7-13 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C7.3.4.4. Inventory Adjustments Due to Ship-in-Place. Once the re-
warehousing action is complete, the storage activity will notify both owners with
the respective inventory adjustment as follow:
C7.6. INVENTORY GAINS AND LOSSES DUE TO UNIQUE ITEM IDENTIFIER AND/OR
SERIAL NUMBER MISMATCH. Procedures concerned with inventory adjustments due
to UII and/or serial number mismatch losses or gains are contained in Chapter 6. 6
C7.7.1.2. When one new stock number is picked up due to reidentification, the
inventory adjustment will contain the same document number as the original transaction,
identified stock number, quantity of the identified stock number using (Quantity or Status
Adjustment Reason Code AE (Reidentification)), and Suffix Code B.
C7.7.1.3. When more than one new stock number is picked up due to
reidentification, an additional inventory adjustment for each newly identified stock number
will be prepared and sent. The additional inventory adjustment transaction(s) will be
prepared in the same manner as the second transaction except that the suffix codes will
progress to C, D, etc., as each transaction is prepared. The suffix codes in the second
6
Refer to ADC 1198
C7-14 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
and ensuing transactions will serve to correlate the transactions to the misidentified stock
number.
C7.7.2.1. When only a stock number change occurs, the owner/IMM prepares
and processes an inventory adjustment containing the old and new stock numbers
(Quantity or Status Adjustment Reason Code AF (Stock Number Change)) and the
associated inventory adjustment increase and decrease.
C7.7.2.2. When only a unit of issue change occurs, the owner/IMM prepares
and processes an inventory adjustment containing the old and new units of issue
(Quantity or Status Adjustment Reason Code AN (Unit of Issue Change)) and the
associated inventory adjustment increase and decrease.
C7.7.2.3. When a simultaneous stock number and unit of issue change occurs,
the owner/IMM prepares and processes an inventory adjustment containing the old and
new stock numbers and units of issue (Quantity or Status Adjustment Reason Code AF
and AN), and the associated inventory adjustment increase and decrease.
C7.8.1. When materiel is not identified by an NSN and is actually scrap, the DoD
Components may prescribe that it be classified in SCC S for turn in to a DLA Disposition
Services Field Office. Otherwise, only materiel recorded on property accountability
records in SCC A through H and SCC Q will be reported or turned in to the DLA
Disposition Services Field Office.
C7-15 CHAPTER 7
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C7.8.4. DLA Disposition Services Field Offices will use the supply condition
codes to accurately describe the physical condition of the materiel based on its
inspection at time of receipt. DLA Disposition Services Field Offices will record the
supply condition codes as management data for DLA Disposition Services program
screening and review. Within the DLA Disposition Services Field Office process, Supply
Condition Code S is assigned for "property with no value except for its basic materiel
content." Consequently, Supply Condition Code S may be assigned by DLA Disposition
Services Field Offices to materiel with or without NSN identification.
C7-16 CHAPTER 7
DLM 4000.25, Volume 2, April 2, 2019
Change 12
C8. CHAPTER 8
MATERIEL OBLIGATION VALIDATION
C8.1. SUPPORT OF UNITED STATES FORCES
C8.1.1. General
C8.1.1.1. Purpose. This chapter prescribes policies and procedures for the
validation by organizations of the continuing need for over age requisitioned
requirements and for the reconciliation of source of supply materiel/obligation records
with the due-in records of requisitioning activities. The materiel obligation validation
(MOV) process is twofold: (1) validation of need; and (2) reconciliation of records.
C8.1.1.4. Use of the DLMS 517M. Sources of supply use the DLMS 517M,
Materiel Obligation Validation, to generate MOV requests to organizations for a
comparison and validation of the continued requirement of outstanding requisitions held
as materiel obligations by the source of supply with those carried as due-in by the
organization.
1
Status Code BP may be deferred for inclusion under logistics system modernization.
C8-1 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
C8.1.1.4.2. Materiel Obligation Validation Request Control is DLMS
517M with Transaction Type Code AN – Material Obligation Inquiry with BR07=X7
– Batch Sequence Number (legacy batch control number), and BR10=XM – Issuer
Number (number of individual detail transactions). This transaction provides the
functionality of MILSTRIP legacy DIC AN9. Note: Modernized systems may not
require exchange of batch control numbers.
C8-2 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
Inquiry and Action Code RU – Return (backordered materiel in pre-award (BZ)
status.
C8.1.3. Exclusions
C8.1.4.1. Timeframe. Materiel obligations are over age and subject to these
procedures when PD 01-08 requisitions have aged 30 calendar days past the
2
Refer to ADC 1043/ADC1043A.
3
Refer to ADC 1043E.
C8-3 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
requisition date or PD 09-l5 requisitions have aged 75 calendar days past the requisition
date.
C8.1.4.3. Long Production Lead Time. These procedures also apply to long
production lead time items since requirements for such items may also change as a
result of unit/force movements, deactivation, and other population changes; however,
only item managers may elect to establish longer intervals for the validation of long
production lead time items.
C8-4 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
difference resulted from a shipment, a cancellation, or if the requisitioner actually
requested cancellation of the obligation. Only cancellations actually requested by the
requisitioner using the MOV response are included in the MOV report. Do not report a
difference in quantity resulting from any other cause and/or process.
C8.1.5.4. Special IMM Requests. The IMM may initiate a special validation
request. For example, the IMM may need to validate requirements for high dollar value,
critical items, or for those NSNs that have the largest number of materiel obligations on
record or account for certain percentages of the total materiel obligations. These
special validations should be selective in approach and may be made regardless of
whether the materiel obligations were previously validated. The IMM may determine
and define critical items as those essential items that are in short supply or expected to
be in short supply for an extended period.
C8.1.6.1. Purpose. Use the DLMS 517M, to request a special MOV at times
other than the normal MOV cycles indicated in Table C8.T1. Organizations will validate
the special MOV and use a DLMS 517M in response to the special MOV request.
C8.1.6.2. Document Number. The MOV request must identify the document
number of the demand that is held as a materiel obligation, the unfilled quantity, and a
response due date that is always 15 calendar days from the date of the MOV request.
C8.1.6.3. Urgent Requests. Due to the urgency of demands for critical items,
IMMs may determine that supply of current demands should be accomplished from due-
4
Refer to ADC 369. Deferred implementation is authorized.
C8-5 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
in stocks, against which there are materiel obligations of lesser or equal priorities. In
these instances, the IMMs will initiate a special MOV request.
C8-6 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
C8.1.8.4. DAAS Initiated Responses
C8.1.8.4.3. MOV History File. DAAS uses the MOV history file to
generate appropriate MOV responses for the activity(ies) identified in the MOV
exemption.
5
Refer to ADC 1043E
C8-7 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
of embarkation, or vendor (in the instance of purchase actions). Based on action taken,
sources of supply will provide requisitioning organizations with appropriate supply or
shipment status.
C8.1.10.2. Source of Supply Codes. Sources of supply will use Status Code
DK, DL, and DM to reject MOV reinstatement requests received over 60 calendar days
after the BS status transaction date, or when there is no record of the BS status, or
when the MOV reinstatement request is for a quantity greater than the canceled
quantity.
C8.2.1. General. This section prescribes policies and procedures for the
validation of ICP materiel obligation records with the records of the DoD Component
ILCO maintaining Security Assistance Organization (SAO) program control and for the
validation of the continuing need at the GA country level for over age demands. The
purpose is twofold: (1) the reconciliation of records and (2) the validation of need.
C8-8 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
C8.2.2. Annual Validation Schedule. The annual schedule of cyclic validation in
support of GA materiel obligations is shown in Table C8.T2.
C8.2.3. Aged Materiel Obligation Requests. Sources of supply will provide the
ILCO with MOV requests applicable to aged materiel obligations for GA requirements.
MOV requests will be sent to the ILCO by the sources of supply using schedules for
validating aged GA materiel obligations established by the Assistant Secretary of
Defense (Logistics & Materiel Readiness)(ASD(L&MR)].
C8-9 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
C8.2.6.2. Program Originator Codes. The DoD Components may elect to
have their ILCOs identify the program originator code in MOV requests transmitted to
SAOs for validation. The identification of this code enables the SAO to determine the
specific section to which to direct the MOV requests. In these instances, the codes
shown in Table C8.T3 apply. (Do not include these codes in MOV responses that are
sent to the source of supply.)
C8.2.7.1. Item/Record Matching. The Navy ILCO (NAVILCO) will match the
items indicated as being on record at the source of supply with its records of unfilled
demands and effect a file reconciliation. NAVILCO will send MOV responses for each
MOV request received to the source of supply that submitted the validation request.
The source of supply will use the MOV response to determine whether the items should
be canceled or requirements still exist and the items should be continued as materiel
obligations.
C8-10 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
reconciliation request was received from the source of supply. See Chapter 4 for the
requisition inquiry procedures.
C8.2.9.2. Item Status Request. SAO will request status of any items that are
outstanding, have met the age criteria, and are not included in the MOV requests.
When such status is required, SAO will submit a requisition inquiry, DLMS 869A, to the
appropriate ILCO. See Chapter 4 for the requisition inquiry procedures.
C8.2.10. Response to MOV Requests by the Army and Air Force ILCOs
C8-11 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
obligations. Provide MOV responses to the source of supply by the response due date
indicated in the MOV requests. Response due date is established as the 125th calendar
day following the cutoff date for validation. MOV requests must indicate the cutoff date.
C8.2.10.2. Quantity Remaining Required. ILCO will indicate the quantity still
required in the MOV response. If total cancellation is desired, do not include the
quantity segment in the MOV response.
C8-12 CHAPTER 8
DLM 4000.25, Volume 2, April 2, 2019
Change 12
to GA for an individual item being canceled, the supplying DoD Component will take
action under DoD 5105.38-M, Part II, Chapter H.
C8-13 CHAPTER 8
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C9. CHAPTER 9
LOGISTICS REASSIGNMENT
C9.1. GENERAL
C9-1 CHAPTER 9
DLM 4000.25, Volume 2, October 09, 2018
Change 11
terminates at ETD. ETD is the date of the LR. Although ETD is a specific point in time,
for the purpose of these procedures, any actions involving data requirements that show
conditions as of the ETD will be discussed as if such actions took place on the ETD,
even though they may have been taken immediately before or after the actual ETD.
The post-ETD period begins immediately following the ETD and includes all actions that
do not specifically involve data requirements that show conditions as of the ETD.
Specific events required to take place during the LR are set forth under the appropriate
period.
C9.3. REQUIREMENTS
C9.3.1. General. The LIM, GIM, and storage activities will accomplish the actions
required by this manual to reassign asset accountability to the GIM in a timely manner
to ensure uninterrupted supply support. Resolution of problems affecting supply
operation requires direct communication, coordination, and assistance.
C9.3.2. GIM. The GIM will accept, as of the ETD, those items and book balances
submitted by the LIM. (The following policy covering transfer of assets for LR is
implemented from DoD 4140.26 and AMC-R 700-99 et al., respectively.) The LIM will
transfer all on-hand wholesale balances, in place, except:
C9-2 CHAPTER 9
DLM 4000.25, Volume 2, October 09, 2018
Change 11
shipments, packaged shipments). On hand wholesale assets in support of the ILP will
not be transferred to the GIM nor will any ongoing procurement action in support of the
ILP be terminated.
C9.3.3. LIM. On an expedited basis the LIM will decapitalize to the GIM wholesale
assets, other than the SCCs shown above, generated during the first year following
ETD. The LIM will report assets generated after 1 year of ETD under Chapter 11,
(Materiel Returns Program Procedures). Except for decapitalization of procurement
receipts, the GIM will reject assets decapitalized more than 1 year after the ETD using
Reject Advice Code AW.
C9.4.1. General
C9.4.1.1. The LIM procurement office will provide the GIM with contractual
status on contracts either retained by the LIM or assigned to the Defense Contract
Management Agency (DCMA) for contract administration. Contract status includes, but
is not limited to, delivery status, acceleration of delivery, follow-up status requests,
contract warranty provisions, and executing appropriate modifications to basic
contracts.
C9.4.1.2. For nonconsumable items, the LIM will give the GIM listings of all
purchase requests (procurement actions that have not reached the award stage)
throughout the pre-ETD period. The GIM will, within 15 calendar days following receipt
of the purchase request listing from the LIM, annotate required changes, and return one
copy to the LIM. For consumable items, the LIM will send listings of all purchase
requests to the GIM 45 calendar days prior to the ETD in the format established by DoD
4140.26.
C9.4.1.4. For assets in SCC H, the LIM will either forward the assets to DLA
Disposition Services or reclassify the item to their true condition as authorized by
Chapter 7.
C9.4.1.5. For assets in SCC X, the LIM will reclassify the assets as
appropriate for LR or for transfer to DLA Disposition Services.
C9-3 CHAPTER 9
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C9.4.2. One hundred and fifty calendar days prior to ETD, or upon notification if
less than 150 calendar days, the LIM will take the following actions:
C9.4.3. One hundred and twenty calendar days prior to ETD, or upon notification if
less than 120 calendar days, for consumable items being transferred, the LIM will send
the GIM an LR Management Data Transaction containing backorder and demand data,
on-hand data, due-in data, and contract history data. Do not provide PQDR history data
at this time.
C9.4.4. Sixty calendar days prior to ETD the LIM will process excess reports
received for LR items for which disposition action is appropriate, in accordance with
Chapter 11 procedures.
C9.4.5.1. By mutual agreement between the GIM and the LIM, the LIM will
initiate action to amend existing LR item contracts/purchase orders not reassigned to
the GIM to provide for diversion of stock by quantities into storage activities of the GIM.
The GIM will send addresses of the shipping destinations to the LIM, as appropriate.
The LIM will retain the due-in.
C9.4.5.2. For consumable items, the LIM will send listings of all purchase
requests in accordance with DoD 4140.26. The GIM will, within 15 calendar days
following receipt of the purchase request listing from the LIM, annotate required
changes and return one copy to the LIM.
C9.4.6. Thirty Calendar Days Prior to ETD. The LIM will take the following
actions:
C9.4.6.1. Furnish the GIM a war materiel requirement (WMR) data listing
sorted by NSN and the DoD Component (and routing identifier code (RIC)) within the
DoD Component when the requirements have been allocated), major to minor, showing
the current computed data.
C9-4 CHAPTER 9
DLM 4000.25, Volume 2, October 09, 2018
Change 11
OWRMR, Protectable (OWRMRP); Pre-Positioned War Reserve Materiel Requirement
(PWRMR); PWRMR, Protectable (PWRMRP)); dollar value subtotals for FSC, RIC if
allocated, and the DoD Component; and grand total dollar value.
C9.5. EFFECTIVE TRANSFER DATE PERIOD ACTIONS. The LIM will do the
following at ETD:
C9.5.5. Send the GIM storage activity a DLMS 527D ARI (PMR) for each due-in
from procurement on which the destination has changed to the GIM. In addition, send
the LIM storage activity a reversal DLMS 527D ARI (PMR) to delete the PMR.
C9-5 CHAPTER 9
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C9.5.6. Transfer funded backorders to the GIM in accordance with DoD 4140.26.
Transfer the funded backorders using referral/passing orders in accordance with
MILSTRIP procedures.
C9.5.8. For items with SPR, prepare and send a DLMS 870L, Order Status Report
(SPR Status), to the forecasting activity as outlined in Chapter 2.
C9.5.9. Advise the GIM of the latest data available on assets being held for
litigation action.
C9.6.1. Storage Activity Action. The storage activity will prepare an LR Storage
Information Reply Transaction within 5 working days of receipt of an LR Storage
Information Order Transaction advising the LIM of the quantity transferred to GIM
ownership. If the storage activity does not receive an LR Storage Information Order
Transaction, the storage activity will prepare and send the LIM an LR Storage
Information Reply Transaction showing each balance by SCC.
C9-6 CHAPTER 9
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C9.6.2.5. LR Transfer/Decapitalization Reversals. Accept and process
reversals of LR Transfer/Decapitalization Transactions, adjust their management and
financial records, and discontinue processing any other transactions against the LR
assets until the GIM processes new LR Transfer/Decapitalization Transactions from the
LIM.
C9.6.3.1. Updating Due-Ins. The LIM will update the memorandum due-in
and PMR in accordance with Chapter 13, as necessary, to include the following actions:
C9-7 CHAPTER 9
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C9.6.3.5.3. Determine whether the quantity reported by the storage
activity is correct (based on the best data available after research/inventory). If
research shows the quantity reported was not correct the LIM will process a reversal, or
LR Transfer/Decapitalization Transaction and a LR Storage Information Order
Transaction containing new document numbers with the revised quantity.
C9.6.3.6. Ninety Calendar Days after ETD. For consumable items, the LIM
will send the GIM an updated LR Management Data Transaction containing contract
history and PQDR history data. Give data for PQDRs completed between the ETD and
the ETD plus 90 calendar days only. Do not give backorder and demand, on hand, or
due-in data at this time.
C9.6.3.7. One Hundred and Eighty Calendar Days after ETD. For
consumable items, the LIM will send the GIM an updated LR Management Data
Transaction with PQDR history data. Give data for PQDRs completed between the
ETD plus 90 calendar days and the ETD plus 180 calendar days only. Do not give
backorder and demand, on hand, due-in, or contract history data at this time.
C9.7.1.1. Upon receipt of assets from procurement by either the GIM or LIM
storage activity, send a DLMS 527R Receipt Transaction to the LIM.
C9-8 CHAPTER 9
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C9.7.1.2. Procurement receipts received after 1 year past the ETD will be
processed by the LIM and GIM in the same manner that procurement receipts would be
processed when received during the ETD to 1 year period.
C9.7.1.3. When the LIM receives a receipt transaction from the storage
activity for an item that was logistically reassigned, the LIM will:
C9.7.1.3.1. Process the receipt to reduce the due-in record, record the
assets on the LIM owner record.
C9.7.1.4. If no DLMS 527D ARI (PMR) is recorded, the storage activity will
report materiel received from procurement sources in accordance with Chapter 13.
C9.7.1.5.3. If assets from procurement are received for which there are
no PMRs at the receiving storage activity, the receiving activity will report the receipt to
the cognizant IMM. If the GIM does not have a recorded due-in and the item was
recently involved in an LR, the GIM should research/contact the LIM to determine
proper reporting of the receipt to maintain accountability accuracy. If the procurement
C9-9 CHAPTER 9
DLM 4000.25, Volume 2, October 09, 2018
Change 11
receipt is incorrectly reported to the LIM (and the LIM did not initiate the procurement
action), the LIM should reject the receipt back to the originator with a DLMS 824R citing
Reject Advice Code AB.
C9.7.2.1. The LIM’s storage activity, upon receipt of assets from other than
procurement, will send DLMS 527R receipt to the LIM.
C9.8.2. LIM Response. The LIM will send the necessary LR Transfer/
Decapitalization Transaction or a duplicate thereof.
C9-10 CHAPTER 9
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C10. CHAPTER 10
MATERIEL RECEIPT ACKNOWLEDGEMENT
C10.1. PURPOSE
C10.1.1. This chapter provides the procedures for a DoD automated, closed-loop
system to provide accountability and monitor receipt of shipments of DoD and General
Services Administration (GSA) wholesale stocks and DLA Disposition Services stocks
issued from on-hand assets or procured for direct vendor delivery (DVD). These
procedures interface with logistics response time (LRT) for measuring receipt take-up
time by requisitioners and with Chapter 5, for providing 100 percent shipment status on
stock issues, including DVDs.
C10.1.2. These procedures provide for the control of due-in records below the
wholesale level and the interface among the transportation, quality, supply, and financial
operations/systems below the wholesale level and between the supply and purchasing
operations/systems at the wholesale level to provide proper control over in transit
assets and document receipt in the payment files.
C10.1.3. MRA Business Rules. Appendix 12 identifies the detailed business rules
for generating the MRA Report. Appendix 12 also includes an MRA Decision Tree
diagram to provide graphic representation of the MRA business rules to capture
shipments out of wholesale assets that qualify for MRA Reporting.
C10-1 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C10.2. APPLICABILITY.
C10.2.2.1. All DoD wholesale inventory control points (ICP) and the
DLA Disposition Services (for the purposes of MRA, DLA Disposition Services is the
DoD ICP for shipments from Disposition Services).
C10.3.2. Shipments to foreign military sales and grant aid customers except
when the shipment concerns an unconfirmed materiel release order (MRO) as
described in Chapter 4 (Processing Follow-Ups). FMS documents beginning with B, D,
I, P, K and T .
1
Known MRA gaps include shipments associated with DLA Industrial Prime Vendor (IPV), and DLA
Tailored Vendor Relationships (TVR) such as Medical Prime Vendor; Subsistence Prime Vendor;
Maintenance Repair and Operations program; and Kentucky Logistics Operation Center (KyLOC). The
MRA process requires a MILSTRIP Shipment Status transaction; there is no shipment status in these
processes. These processes are not excluded from MRA (except Fresh fruits and vegetables (FF&V)),
and are identified as known process gaps that DLA is working to close. Another possible MRA gap exists
for immediate issue scenarios (e.g., bearer walk-through or “over the counter” issues) where shipment
status/materiel release confirmation is provided and an MRA would typically be expected. DLA will
submit a proposed DLMS change to document this as a valid MRA exclusion. (ADC 1088)
C10-2 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C10.3.4. Shipments to state, civil, or federal agency activities. Special
Program DoDAACs are identified by numeric character in the first position followed by
an alpha character in the second position. These identify entities that are neither DoD
or other Federal entities and that are associated with a special program. Among other
purposes, special programs include programs authorized by Congress for state and
local entities to purchase materiel from Federal sources. The existing Defense
Automatic Addressing System (DAAS) logic for extracting the LMARS database
includes the exclusion of Special Program DoDAACs (ADC 1088).
C10.3.5. Receipts into DoD wholesale stock controlled under Chapter 13,
including relocations/shipments to contractors, commercial or industrial activities which
are receipt reported to the owning ICP, when the owing ICP also issued the materiel.
However, when ICPs requisition materiel from another ICP or the DLA Disposition
Services, and the receipt is reported under Chapter 13, the requisitioning ICP will
acknowledge the receipt (ADC 1087).
2
This is not a true “exclusion” from MRA because the MRA is only required for release of wholesale
assets. When DAAS gets the passing order that has a RIC-TO of a non-wholesale ICP, they will flag the
document number as not eligible for LMARS/MRA, but still be available for WEBVLIPS as history. Any
subsequent transactions that come in under that document number (regardless of data content and
indication of a wholesale ICP) automatically gets that flag. This is similar to what DAAS does for the
requisition alert process. The one underlying assumption to this solution is that the passing order (DIC
A3_) will be present so that the flag can be set at the document number level. This is a safe assumption,
since ADC 1062 states that GCSS-A will not release the requisition image until they receive the passing
order routed by DAAS. Note the DAAS check on the shipment status is just the presence of a shipment
status for the document number that clears the first part of the MRA decision Tree. DAAS feels this will
eliminate a concern with LMARS picking up the transaction as a byproduct when the bill comes out of the
wholesale ICP system (LMP) after the post-post issue is passed to that system (For Army GCSS-A to
LMP). (ADC 1088)
C10-3 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
and the issuing ICP would not generate a Follow-up for Delinquent MRA transaction.
For the purpose of this exclusion logic, DAAS will use the MRA Follow-up timeframe
plus one day. Under existing MRA Report logic, lookup will be done at the end of the
month (ADC 1087).
C10.4. COMMUNICATIONS
C10.4.1. Reporting activities will direct MRAs to the managing ICP using guidance
in C10.4.2. If operating under MILSTRAP legacy transactions, refer to the instructions
in DLMS Volume 2, Appendix 3.29 for the legacy DRA/DRB transactions. DAAS will
pass the MRA to the designated ICP and provide images to other designated activities
based upon DoD Component rules.
C10.4.2 Reporting activities will direct the MRA to the managing ICP using one of
the following (listed in order of preference):
C10.4.3. ICPs will send all MRA follow-ups to the DAAS for
transmission. The DAAS will route MRA follow-ups for U.S. forces to the “ship-to”
activity identified in the 856S Shipment Status. The DAAS will route MRA follow-ups for
security assistance requisitions to the applicable Service International Logistics Control
Office (ILCO) based upon the Service Code in the Document Number and distribution
code
C10.5. RESPONSIBILITIES
C10.5.1. Reporting activities and ICPs will meet the time limits stated throughout
this chapter and summarized in Table C10.T1, MRA Submission Timeframe, and Table
C10.T2, MRA Follow-up Timeframe for ICPs and Disposition Services.
C10-4 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
and shipment status received. Establish due-in record estimated delivery dates which
equal the MRA prescribed timeframes in Table C10.T1.
C10.5.3. ILCO reporting activities will screen history records for valid shipment
status or coordinate with freight forwarders/customers to determine shipment
status/receipt data, for unconfirmed MROs and send an MRA Advice Transaction within
the prescribed timeframes in Table C10.T1.
C10-5 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C10.5.4.5. Consider MRA data in the supply discrepancy report (SDR)
validation process.
C10.5.5.1. Will establish the internal interface among the logistics, financial,
and contracting operations/systems necessary to accomplish the requirements of this
chapter. When operations are geographically removed from each other, DoD
Components may prescribe use of intra-DoD Component transactions to accomplish the
required interface.
C10.5.5. May record MRA data in requisition history and use to close
unconfirmed MROs.
C10.5.6. GSA will not use the MRA to monitor materiel receipt but will use
the data to interface with the discrepancy reporting process. Therefore, GSA will not
follow-up to reporting activities to request an MRA.
C10.6.1. Reporting activities will meet the time limits identified in this chapter.
These requirements and timeframes are independent from prescribed shipment tracing
and discrepancy reporting requirements and timeframes to which the receiving facility
must also adhere. MRA reporting timeframes are summarized below:
C10-6 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
Table C10.T1. Materiel Receipt Acknowledgement Submission Time Limits
ACTION TIME LIMIT 3
U.S. Forces send MRA * 5 Business days from date materiel received and:
12 calendar days from the DLMS 856S date shipped
(date released to carrier) field entry (CONUS
destination) for nonreceipt;
29 calendar days from the DLMS 856S date shipped
(date released to carrier) field entry (OCONUS
destination) for nonreceipt for Transportation Category
1 and 2;
or
76 calendar days from the DLMS 856S date shipped
(date released to carrier) field entry (OCONUS
destination) for nonreceipt for Transportation Category
3.
ILCOs Send MRA *120 calendar days from the DS 856S (Pseudo Shipment
Status for Unconfirmed Materiel Release Orders) date
shipped (date released to carrier) field entry for security
assistance shipments.
Send MRA in Reply to *10 calendar days from transaction preparation date in
Follow-up the MRA Follow-up.
* Means take the action before the time limit is reached.
Means take the action when the time limit is reached.
3
Refer to ADC 1114.
C10-7 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C10.6.2.4. For nonreceipt of materiel (Transportation Category 3) with
an OCONUS destination, within 76 calendar days from the date shipped (date released
to carrier) cited in DLMS 856S.
C10.6.3. ILCOs in receipt of DLMS 856S pseudo shipment status will screen
history records for valid shipment status. If valid shipment status is not available, ILCOs
may coordinate with freight forwarders/customers to determine shipment status/receipt
data. Submit an MRA to reflect the shipment status, receipt data, or nonreceipt within
120 calendar days from the pseudo shipment status release date.
C10.6.5. MRA for Tailored Vendor Relationship. DLA, in conjunction with the DoD
Components and vendors, has implemented tailored vendor relationship (TVR). TVR is
a business process where there is a direct relationship between the customer and the
vendor. Under TVR, customers place orders directly with the Prime Vendor, outside the
routine supply requisitioning process/systems, using various communication channels
such as EDI, phone, fax, email, or via the prime vendor's ordering system. DLA EBS
receives copies of transactions in order to maintain line item accountability. MRA of
TVR shipments require use of the contract number, call, and line item numbers to
uniquely identify lines. This data is necessary because TVR orders can have multiple
lines for the same document number and suffix code. DLA receives MRAs for TVR
from, Defense Medical Logistics Standard Support (DMLSS), Theater Enterprise-Wide
Logistics System (TEWLS), EMALL, or customer systems.
C10.6.6. When a shipped line item (requisition document number and suffix code)
is consigned as a split or partial shipment, send an MRA, for the shipment segments as
they are received. The split or partial shipment codes are part of the transportation
control number (TCN) structure in accordance with DTR 4500.9-R, DoD Transportation
Regulation”. Accordingly, reporting activities will include the TCN in the MRA
transaction when it is available. If the total quantity for the shipped line item is not
received by the due-in date, report the missing quantity, citing Discrepancy Indicator
Code F, in accordance with the guidance in the MRA transaction.
C10-8 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
exception of the receipt of multiple stock numbers, use a single MRA transaction to
acknowledge the receipt showing both non-discrepant and discrepant quantities. 4 Note
that MRA requirements and timeframes are independent from prescribed shipment
tracing and discrepancy/deficiency reporting requirements and timeframes to which the
receiving facility must also adhere.
C10.6.7.5. When the discrepancy causes the receipt to be posted using more
than one transaction (e.g., multiple supply condition codes or multiple stock numbers
are received), send an MRA for each transaction posted. If needed, also send an MRA
for any quantity not received.
C10.6.7.7. The MRA report is created at the end of each month to reflect the
MRA transactions as received/not received in the preceding month. Receipt of an MRA
citing Discrepancy Code B or F updates the Logistics Metrics Analysis Reporting
System (LMARS) reports to reflect the current status of MRA transactions received.
The MRA Reports are created monthly and reflect the MRA data at the end of each
month and will not be adjusted retroactively when an MRA is submitted following receipt
of materiel after an MRA citing Discrepancy Indicator Code B or F is received. 6
4
This this is an enhancement that the Components never implemented as part of the looping structure
capability.
5
Refer to ADC 1114.
6
Ibid.
C10-9 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C10.7. FOLLOW-UPS FOR DELINQUENT MATERIEL RECEIPT
ACKNOWLEDGEMENT
C10.7.1.1. The organization that the materiel was shipped to, for U.S.
Forces.
C10.7.1.3. The MRA Follow-up timeframes are based upon the Time Definite
Delivery (TDD) Standards and take into account the wide variation in TDD timeframes
based on the Combatant Commands/Regions and the allowed receipt take-up
timeframe. 7
C10.7.1.4. The follow-up time limits for a delinquent MRA are 17 calendar
days from the date shipped (date released to carrier) field entry in the MRC or DLMS
856S Pseudo Shipment Status for CONUS, 34 calendar days for OCONUS destinations
with Transportation Category 1 and 2, and 81 calendar days for OCONUS destinations
with Transportation Category 3. (See Table C10.T2).
7
With the knowledge that TDD Standards have changed since ADC 1114 (2015), an analysis was
performed in 2019 to determine if MRA Timeframes needed to be adjusted. The analysis showed that
TDD Standards have not changed sufficiently to merit adjustment of these timeframe standards. Future
analyses may be performed to ensure this remains the case.
C10-10 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
Table C10.T2. Materiel Receipt Acknowledgement Follow-Up Time Limits for ICPs and DLA
Disposition Services
The Time Limits below for an MRA Follow-up reflect the TDD timeframes, which include the
transaction processing time, and also allow time for processing a Non-Receipt Materiel Receipt
Acknowledgement.
C10.7.2. To answer the follow-up, the reporting activity will prepare a MRA
following paragraph C10.6. Send the MRA to the ICP within 10 calendar days from the
transaction preparation date cited in the follow-up.
C10.7.3. In the event that materiel has not been received because a Navy ship
has not yet had the opportunity to physically pick it up (it is awaiting pick up at a Navy
Local Logistics Support Center or the Material Processing Center), the Navy ship
reporting activity will respond with a MRA Follow-up Transaction containing Discrepancy
Indicator Code G. This will signal the ICP to keep the record open and continue to
monitor for receipt of MRA(s), and send another MRA Inquiry Transaction after another
45 calendar days have elapsed (which may be responded to with an additional MRA
Response to Inquiry Transaction with Discrepancy Indicator Code G if the ship is unable
to pick up their materiel from the Navy Local Logistics Support Center or the Material
Processing Center). The Navy ship reporting activity may send up to six MRA
transactions in response to follow-up, using MRA Response to Inquiry Transaction with
Discrepancy Indicator Code G. The Navy ship reporting activity will send an MRA,
using DLMS 527R MRA Response to Inquiry Transaction, without the Discrepancy
Indicator Code G, once the materiel is received (e.g., picked-up or otherwise delivered
directly to the ship), which may include the use of other discrepancy codes as
appropriate. If a reply is not received within 45 calendar days from the sixth MRA
8
Refer to ADC 1114.
C10-11 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
Response to Inquiry Transaction with Discrepancy Indicator Code G, the ICP will
include the delinquency information in the management evaluation report (C10.10).
Also, if the requisition involves an unconfirmed MRO (see Chapter 4, (Processing
Follow-Ups)), then the ICP will resolve the record as described in Chapter 4 for Force
Closed Materiel Release Confirmation).
C10.7.6.2. When ICP data reveals an MRA was not received within the
timeframes identified in Table C10.T2 plus the 10 day reply response timeframe
(paragraph C10.7.2), the wholesale ICP (source of supply) may initiate action to close
the record. The ICP will initiate internal system procedures and notify the ordering
activity of the administrative closeout action using a Supply Status transaction (DLMS
IC 870S or equivalent) with Requisition Transaction Status Code D9: Closed. Open
order was administratively closed due to non-receipt of a materiel receipt
acknowledgement (MRA). This transaction must also include one of two Management
Codes: X for shipments from DoD Stock, or Y for shipments made via DVD.
9
Refer to ADC 1114.
10
Ibid.
11
Refer to ADC 1343.
C10-12 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C10.7.6.3. Controlled inventory items (CII) designated with a controlled
inventory item code (CIIC) in the Federal Logistics Information System (FLIS) record for
the national stock number (NSN) will be excluded from this process. Orders for NSNs
coded as CII within FLIS must be systemically excluded from these procedures. In
addition to CII, Component wholesale ICPs may develop local policy and thresholds to
manage the inherent material and/or financial risk involved in assuming receipt and
define their own additional criteria for issuing an MRA closeout Supply Status
transaction based upon those risk thresholds.
C10-13 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C10.8.1.2.2.1. DAAS will reject legacy MRA transactions (DICs
DRA/DRB) received with a blank unit of issue (record position 23-24) to the reporting
activity with a narrative message reject stating: Unit of Issue contains blanks or special
characters.
C10-14 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
for in-transit wholesale stock. Supply Process Review Committee representatives are
responsible for initiating corrective action with delinquent and non-reporting activities.
12
ADC 1086.
13
Refer to ADC 1330 Revise MRA Download Reports to Include a Component Summary Option.
C10-15 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
• Supplementary Address 14
• Ship-To DoDAAC
• Signal Code 15
• Bill-To DoDAAC
• Priority
• NSN
• Shipped Quantity
• Unit of Issue
• Unit Price (U/P)
• Total Cost
• Initial Transaction DLMS/MILS, (e.g., requisition or initial supply transaction if no
requisition is available per MRA Business Rules/Decision Tree) 16
• Communication Routing Identifier (COMMRI) of the system from which the
requisition or initial supply transaction originated
• COMMRI associated with the Document Number DoDAAC, (e.g., could be a
requisitioner/requiring/other activity)
• COMMRI where the Follow-up for Delinquent MRA transaction was transmitted.
14
This enhancement perpetuates legacy “MILS” data requirements due to the DAAS Micro Automated
Routing System (DMARS) which performs transaction level services, such as, validation, editing, routing,
imaging, and exception processing, using the 80 record position legacy format.
15
Ibid.
16
This is the transaction that results in the inclusion in the MRA Report per the MRA Business
Rules/Decision Tree (ADC 1088 , Reference 3.d.).
17
Refer to ADC 1343.
C10-16 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
• Shipment Date
• Document Number
• Suffix
• Supplementary Address
• Ship-To DoDAAC
• Signal Code
• Priority
• NSN
• Shipped Quantity
• Unit of Issue
• Unit Price
C10-17 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
DoD Components/Participating Agencies and all categories by Ship-to DoDAAC. Detail
report is available.
C10-18 CHAPTER 10
DLM 4000.25, Volume 2, December 27, 2022
Change 15
process in their respective AIS. The use of system generated MRAs is an
alternative for Components unable to generate MRAs on their own systemically.
C10-19 CHAPTER 10
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11. CHAPTER 11
MATERIEL RETURNS, REDISTRIBUTION OF ASSETS,
DIRECTED DISCREPANT/DEFICIENT MATERIEL
RETURNS, AND RETROGRADE RETURNS
C11.1. GENERAL
C11.1.1.4. There are additional processing procedures over and above those
contained in this chapter that must be applied for items identified as serially managed
materiel requiring owner visibility at DLA Distribution Centers. The identity of the
materiel and the additive procedures are in Chapter 30.
C11-1 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.1.2.1.2. Cancellation of Customer Asset Report is DLMS 180M with
Action Code C – Cancelled. This transaction provides the functionality of MILSTRIP
legacy DIC FTC.
C11.1.2.2. Shipment Status Materiel Returns. Use a DLMS 856R with the
applicable Transaction Type Code. The Action Code further specifies the type of
materiel returns shipment status.
C11.1.2.3. Materiel Returns Supply Status. Use a DLMS 870M with the
applicable Status Report Code to provide status on customer asset reports.
C11-2 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.1.2.3.3. ICP/IMM Delay in Disposition Instructions is DLMS 870M
with Status Report Code 7 – Response to Materiel Returns and 2/ISR01/210 Code HQ
to indicate the delayed date. This transaction provides the functionality of MILSTRIP
legacy DIC FTD.
C11-3 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.1.2.4.6. Billing for Transportation (Credit) is DLMS 810L with
Transaction Type Code PP – Prepaid Invoice (DoD interfund bill) and 3/SAC02/040
Code I260. This transaction provides the functionality of MILSBILLS legacy DIC FQ2.
C11-4 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.1.2.5.4. Supply Status to ICP/IMM from Storage or Reporting
Activity is DLMS 945A with Transaction Type Code NL – Material Release Denial. This
transaction provides the functionality of MILSTRIP legacy DIC AE6.
C11.1.2.7. Returns to DLA from Industrial Sites under Base Realignment and
Closure, Supply, Storage and Distribution and National Inventory Management Strategy
Site Customers
C11.1.2.7.3. Billing for Issue from Stock (Credit) is DLMS 810L with
Transaction Type Code PP – Prepaid Invoice and 2/LQ01/310 Code 0 – FA2. This
transaction provides the functionality of MILSBILLS legacy DIC FA2.
C11.1.3. Reporting Policy. Policy regarding the reporting of assets, the transfer of
assets, the lateral redistribution of assets, and the use of assets as an alternative to
procurement (also known as the procurement offset portion of total asset visibility
C11-5 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
(TAV)), is contained in DoDM 4140.01, "DoD Supply Chain Materiel Management
Procedures," February 10, 2014.
C11.1.5. Financial Credit Policies and Procedures. Credit for materiel returns is
granted on the basis of need, direction to return, and subsequent receipt and
classification by the consignee. These credits may or may not include materiel credit;
however, credit for all directed returns will include credit for packing, crating, handling,
and transportation. Policy for granting credit is covered under DoDM 4140.01 1.
Procedures for the timeframes and transactions for providing credit for materiel returns,
lateral redistributions, and materiel provided for the procurement offset portion of TAV
are contained in the MILSBILLS procedures identified in DLM 4000.25, Volume 4,
Finance. MILSBILLS also covers credit procedures for packing, crating, handling and
transportation (PCH&T). In addition, MILSBILLS provides and transaction formats for
DLMS 812R, Adjustment Request (Follow-Up for Materiel Returns Program Credit)
(MILSBILLS legacy DIC FTP), and Reply to Follow-up for Materiel Returns Program
credit (MILSBILLS legacy DIC FTB).
C11.2. APPLICABILITY AND SCOPE. The provisions of this chapter are applicable as
follows:
C11.2.1. To all activities offering or returning materiel to the DoD Component ICP/
IMM.
1
DLA is required to request approval of new procedures supporting BRAC/NIMS allowing full materiel
credit for returns regardless of asset position with no credit for packing, crating, handling and
transportation (PCH&T).
C11-6 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.2.3. To the processing of Grant Aid. Policy regarding utilization and
redistribution of Grant Aid materiel is contained in DSCA 5105.38-M, “Security
Assistance Management Manual, (SAMM)” Chapter 11.
C11.3. EXCLUSIONS. The following categories are excluded from these procedures:
C11-7 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.3.2. Perishable subsistence items, with the exception of perishable
subsistence returns (other than fresh fruit and vegetables (FF&V)) from Navy mobile
logistics support fleet ships in the Pacific area.
C11.4.2. Reporting Activity Actions. The reporting activity will forward customer
asset reports to the ICP/IMM. Forward all part-numbered Customer Asset Reports
(DLMS 180M) directly to DAAS for possible conversion to an NSN using information in
the FLIS files. Customer Asset Reports (DLMS 180M) transmitted by electronic means
must always be routed through DAAS.
C11.5.1. Customer Asset Reports. Use DLMS 180M to offer or report materiel
that is no longer needed.
C11-8 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.5.2. Reports of Serviceable Items. Reports of serviceable non-consumable
item materiel support code (NIMSC) 5 items from secondary inventory control activity
(SICA) reporting activities to the appropriate DoD Component SICA will be submitted
under the DoD Component implementing instructions. Quantities that are not required
by the SICA will be forwarded to the primary inventory control activity (PICA) using
DLMS 180M. If appropriate, the SICA will provide DS 870M, Materiel Returns Supply
Status (ICP/IMM Status to Customer) delay status to the materiel holder for the quantity
referred to the PICA under section C11.11.5. The expected reply date of the DLMS
870M, if used, will be 35 calendar days after the date the report was forwarded to the
PICA. The PICA will provide disposition instructions to the SICA. The SICA, in turn, will
provide disposition instructions to the reporting activity under the DoD Component
implementing instructions.
C11.5.3. NIMSC 5 Stocks Exceeding Retention Limit. When the SICA has NIMSC
5 serviceable stocks that exceed the retention limit, the SICA will prepare DLMS 180M,
Materiel Returns Reporting, to report available assets to ICP/IMM using the guidelines
above, but with the SICA’s own document number.
C11.5.4. Use of Project Codes. The DoD Components will use one of the
following project codes for the procurement offset portion of TAV of their Customer
Asset Report (DLMS 180M):
C11.6.1. Use of DLMS 180M. Use DLMS 180M to prepare cancellation of asset
reports, in total or partial quantities, and submit to the ICP/IMM under the following
conditions:
C11.6.1.2. Upon determination that materiel directed for return will not be
returned.
C11.6.2. Timely and Accurate Cancellations. The need for timely and accurate
cancellation actions under the above conditions is emphasized to avoid unnecessary
follow-up actions and to ensure that ICP/IMM records or expected returns reflect proper
quantities.
C11-9 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.7. PROCESSING REPLIES TO CUSTOMER ASSET REPORTS
C11.7.1.2. Reporting activities returning materiel under MRP will prepare and
submit a DLMS 856R, Shipment Status Materiel Returns, with Unique Item Identifier
(UII) and/or corresponding serial number(s) for NSNs containing an item unique
identifier (IUID) Indicator Yes (Y), indicating that DoD IUID Supply Policy compliance is
required, after materiel directed for return is released to the carrier. The exception to
the forgoing in support of Financial Improvement and Audit Readiness (FIAR),
accountability and management of capital equipment requires serialization data
visibility. Serial number tracking does not automatically apply to capital equipment. The
materiel owner will evaluate capital equipment items and assign the appropriate UIT
designator code only when the item requires serial number tracking at the DoD level.
Submitters must prepare shipment status materiel returns citing the applicable serial
number(s) and include the UII when available. Prepare a separate DLMS 856R for
each shipment. Exercise care to ensure that appropriate data content, including suffix
of the individual DLMS 870M, Reply to Customer Asset Report (MILSTRIP Legacy DIC
FTR), is perpetuated in the DLMS 856R. The DLMS 856R will be sent to the ICP/IMM
and the designated return-to activity. The ICP/IMM is not required to store UIIs 2 except
for capital equipment that require serialization data visibility when assigned under an
established unique Item tracking (UIT) program. 3
C11.7.3. Replies to DLMS 180M Customer Asset Reports. DLMS 870M replies to
Customer Asset Reports (DLMS 180M) containing Project Code RBB, 3AG, or 3AU
denoting the procurement offset portion of TAV and Status Code TC require
2
ADC 1071, Implementation of DoD Item Unique Identification (IUID) Supply Policy in Version 4030
DLMS 856R Shipment Status Materiel Returns
3
Refer to ADC 1198 and ASC 1198B
C11-10 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
reevaluation prior to disposal since these assets may not be above an activity’s
retention limit. Assets required and offered using either Project Code RBB or 3AG will
always be directed for return with credit; however, assets required and offered using
Project Code 3AU will only be directed for return without credit.
C11-11 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
customer excess report, the 870M ICP/IMM Follow-Up transaction will be converted to
DLMS 870M, Reply to Customer Excess Report, and processed. If shipment has not
occurred, DLMS 870M, Materiel Returns Program Supply Status, citing the ESD will be
submitted. If records indicate that shipment has occurred, the transportation activity will
be queried to ensure that the materiel has been shipped. If the materiel has been
shipped, a new DLMS 856R, will be prepared and submitted identifying the quantity
shipped to include UIIs and/or corresponding serial numbers for NSNs containing an
IUID Indicator Y, indicating that DoD IUID Supply Policy compliance is required. The
DLMS 856R will be sent to the ICP/IMM and the designated receiving activity. Capital
equipment assigned under an established UIT program requires serialization data
visibility and therefore must cite the serial number and include the UII when available. If
materiel has not been shipped, determine when the shipment will be made and follow
the above procedures. When less than the total quantity contained in the original DLMS
870M is to be shipped, the reporting activity will respond to the DLMS 870M, ICP/IMM
Follow-Up, with DLMS 870M, Materiel Returns Supply Status, for the quantity to be
shipped and DLMS 180M for the quantity that will not be shipped. If any of the
shipment has already occurred, the reporting activity will respond to DLMS 870M
(ICP/IMM Follow-up), with DLMS 856R for the quantity that has been shipped, to
include UIIs and/or corresponding serial numbers for NSNs containing an IUID Indicator
Y, indicating that DoD IUID Supply Policy compliance is required. The DLMS 856R
indicating partial shipment will be sent to the ICP/IMM and the designated receiving
activity. Capital equipment assigned under an established UIT program requires
serialization data visibility and therefore must cite the serial number and include the UII
when available. A DLMS 870M supply status and/or DLMS 180M cancellation will be
sent to the ICP/IMM for the remaining portions of the originally reported quantity, as
appropriate.
4
Refer to ADC 1043/ ADC 1043A.
C11-12 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
elements from the SFIS Fund Code to Fund Account Conversion Table for the Fund
Code in the transaction, reject with the DLMS 870M Materiel Returns Supply Status
citing Status Code CF. If invalid/missing fund code for Signal Code A, B, C, J, K, or L,
reject with the DLMS 870M/DIC FTQ Materiel Returns Supply Status citing Status Code
CF. 5
C11.9.2.2. PICAs will notify SICAs of the NSN and the storage organization
to which such items are to be shipped. PICAs will also notify the receiving storage
activity of the NSN of such items to be returned. The SICAs will perpetuate this
information and the PICA RIC to the materiel holder/SICA activities using intra-DoD
Component procedures. The materiel holder will prepare and submit the DLMS 856R
with UII(s) and/or corresponding serial numbers for NSNs containing an IUID Indicator
Y, indicating that DoD IUID Supply Policy compliance is required. Capital equipment
assigned under an established UIT program requires serialization data visibility and
therefore must cite the serial number and include the UII when available. The materiel
holder will send the DLMS 856R to the SICA and the designated return-to activity, with
a copy to the PICA when directed by the SICA. The PICA will be identified as the Party
to Receive Status in the DLMS 856R. The PICA and SICA are not required to store the
UIIs and/or serial numbers.
C11.9.2.3. If there is no DoD Component SICA for the items identified for
automatic return by a PICA (e.g., Coast Guard), the PICA will provide the information to
the appropriate DoD Component designated activity. The materiel holder will prepare
and submit the DLMS 856R with UII(s) and/or corresponding serial numbers for NSNs
containing an IUID Indicator Y, indicating that DoD IUID Supply Policy compliance is
required. Capital equipment assigned under an established UIT program requires
serialization data visibility and therefore must cite the serial number and include the UII
when available. The materiel holder will send the DLMS 856R to the PICA and the
designated return-to activity.
5
Refer to ADC 1043E.
C11-13 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
to store the UIIs and/or serial numbers 6,with the exception of capital equipment
assigned under an established UIT program requires serialization data visibility. 7
C11.9.6. Internal DoD Component Use. The DoD Components may use DLMS
180M Automatic Return Notification internally for intra-DoD Component programs that
do not conflict with other provisions of this manual.
6
ADC 1071, Implementation of DoD Item Unique Identification (IUID) Supply Policy in Version 4030
DLMS 856R Shipment Status Materiel Returns.
7
Refer to ADC 1198
8
Refer to ADC 1256. Staggered implementation authorized by December 2019.
C11-14 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.9.7. Source of Supply Processing of Automatic Return Notification. Upon
receipt of DLMS 180M Automatic Return Notification, the SICA will establish a due-in
and generate a PMR transaction to the receiving activity for the quantity in the DLMS
180M Automatic Return Notification transaction. The SICA will prepare the due-in and
the PMR transaction under Chapter 12 procedures. Note: For unserviceable NIMSC 5
items, the SICA will send a DLMS 180M Automatic Return Notification, with data
elements specified in C11.9.3, to the PICA. The PICA will establish the due-in and send
the PMR transaction to the receiving depot.
C11.10.1. Route Using the RIC To. DLMS 870M, Materiel Returns Supply Status;
DLMS 856R, Materiel Returns Shipment Status; DLMS 812R, Adjustment Request
(Follow-Up for Materiel Returns Program Credit); DLMS 180M, (Follow-Up for ICP/IMM
Materiel Receipt Status); and DLMS 180M, Automatic Return Notification, will be
passed to the activity represented by the RIC To.
C11.10.2. Route Using the M&S Code. DLMS 812L, Reply to Follow-Up for Credit
Status; DLMS 870M, ICP/IMM Status Advising of Delay; DLMS 870M DAAS Customer
Asset Report Status; DLMS 870M ICP/IMM Reply to Customer Asset Report; DLMS
870M, ICP/IMM Advice of Receipt or Non-Receipt of Materiel; and DLMS 870M,
ICP/IMM Follow-Up, will be passed using the M&S code.
C11.10.3. Route Using the RIC To when M&S Code is 9. DLMS 180M,
Cancellation; DLMS 180M, Customer Asset Report; and DLMS 180M, Customer
Follow-Up to ICP/IMM, will be passed to the RIC To if the M&S code is 9.
C11.10.4. Perform NSN/NIIN Validation when M&S Code is not 9. For DLMS
180M, Cancellation; DLMS 180M, Customer Asset Report; and DLMS 180M, Customer
Follow-Up to ICP/IMM, DAAS will perform NSN/national item identification number
(NIIN) validation and source of supply edit as follows:
C11-15 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
transmitted to the correct ICP/IMM. DAAS will send the reporting activity a DLMS
870M, Materiel Returns Supply Status with Status Code TZ.
C11.10.7. Edit Rejects Containing Status Code SC. DAAS will edit DLMS 870M,
Materiel Returns Supply Status (From ICP/IMM), rejects containing Status Code SC or
SD for correct ICP/IMM and FSC as follows:
C11.10.7.1. Correct NSN and ICP/IMM. If the NSN is correct and belongs to
the rejecting ICP/IMM, the DLMS 870M, Materiel Returns Supply Status (From
ICP/IMM), will be converted to DLMS 180M, Materiel Returns Reporting (Report of
Available Assets to ICP/IMM), with Advice Code 3T and sent to the ICP/IMM.
C11.10.7.2. Correct NSN But Wrong ICP/IMM. If the NSN is correct but not
managed by the ICP/IMM, the DLMS 870M, Materiel Returns Supply Status (From
ICP/IMM), will be converted to DLMS 180M, Materiel Returns Reporting (Report of
Available Assets to ICP/IMM), with Advice Code 3T and sent to the correct ICP/IMM.
DAAS will send the reporting activity a DLMS 870M, DAAS Customer Excess Report
Information Status, with Status Code TZ.
C11-16 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
DLMS 180M, Materiel Returns Reporting (Report of Available Assets to ICP/IMM), with
the correct FSC, with Advice Code 3T, and the document returned to the rejecting
ICP/IMM or transmitted to the correct ICP/IMM. DAAS will send the reporting activity a
DLMS 870M, DAAS Customer Excess Report Information Status, with Status Code TZ.
C11.10.8. Country Code Edit. DAAS will validate the DLMS 856R to ensure the
country code is a valid value of the Geopolitical Entities, Names, and Codes (GENC)
Standard. If not valid, the transaction will be rejected by DAAS using the DLMS 824R
Reject Advice citing Reject Advice Code AU. 9
C11.11.2.1. Shipment Time Allowed. Time allowed for shipment and return
of materiel is 120 (CONUS) and 180 (OCONUS) days, and the counting starts with the
day of posting of DLMS 856R, or the estimated shipping date cited in DLMS 870M. The
9
Refer to ADC 1075.
C11-17 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
due-in estimated delivery date (EDD) will be updated upon receipt of a DLMS 856R or
DLMS 870M Status to equal the time allowed for shipment and return of materiel.
C11.11.2.2. Materiel Not Received Within 120 or 180 Calendar Days. If the
materiel is not received by the due-in EDD, or 30 days have elapsed since the
transmission of DLMS 870M, ICP/IMM Follow-Up, without receiving a response, the
ICP/IMM will take action to cancel the due-in and delete DLMS 527D transaction.
DLMS 527D will also be canceled when DLMS 180M, Materiel Returns Reporting, is
received from the customer activity. The EDD required for the due-in will be 120
calendar days (CONUS) and 180 calendar days (OCONUS) from the processing date of
DLMS 870M Materiel Returns Supply Status (From ICP/IMM). The due-in estimated
delivery date will be updated upon receipt of DLMS 870M, Materiel Returns Supply
Status, or DLMS 856R, Shipment Status Materiel Returns (Customer Status to
ICP/IMM).
C11-18 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.11.6. FSC Change Required. If the determination has been made that an
FSC change is required on a customer asset report (DLMS 180M, Materiel Returns
Reporting), the correct FSC will be entered, the RIC To of the ICP/IMM will be changed,
where applicable, and the DLMS 180M, Customer Asset Report, will be forwarded to
the responsible ICP/IMM for processing. The reporting activity will be sent a DLMS
870M, Materiel Returns Supply Status (From ICP/IMM), containing Status Code T7.
The RIC of the forwarding ICP/IMM will be entered in the RIC field of the ICP/IMM
representing the last known holder and will be entered as the RIC of the activity
preparing the document.
C11.12.1.1. Status Code TN. Enter Status Code TN when credit is granted
for the condition and quantity of materiel received.
C11.12.1.3. Status Code TL. Enter Status Code TL when the materiel
received is other than authorized for return and no credit is allowed.
C11.12.1.4. Status Code TP. Enter Status Code TP when the materiel is not
received within prescribed timeframes, follow-up action has been unsuccessful, and the
credit authorization is canceled.
C11.12.1.5. Status Code TQ. Enter Status Code TQ when the materiel has
been received for an authorized non-creditable return.
C11.12.2. Multiple DLMS 870Ms Required. DLMS 870M, Materiel Returns Supply
Status, will always show the document number, including suffix code, contained in the
DLMS 180M, Materiel Returns Reporting, or DLMS 870M, Materiel Returns Supply
Status (From ICP/IMM). When multiple DLMS 870M, Materiel Returns Supply Status,
transactions are required for materiel received in different conditions, each DLMS 870M
C11-19 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
produced will retain the document number and suffix of the DLMS 180M, Materiel
Returns Reporting/DLMS 870M, Materiel Returns Supply Status (From ICP/IMM).
C11.13.1.1. If the controlling document number for the return is the same as
the customer’s original requisition for the item, a unique transportation control number
(TCN), not derived from the original document number, must be created.
C11.13.1.2. Shipments containing IUID data content (e.g., UIIs and/or serial
numbers) and requiring more than one freight piece to execute the movement must
have a unique TCN assigned to each freight piece by using a partial indicator in the 16th
position of the TCN. Multiple freight piece shipments using the same TCN for all related
freight pieces are not authorized when IUID content is required 10 or when capital
equipment that requires serialization data visibility where the serial number is
mandatory and UII is provided when available. 11
C11.13.3. Shipment Advice. In the event that the ICP/IMM requires an advice of
shipment to support related supply decisions and a DLMS 856R, Shipment Status
Materiel Returns, has not been received, an ICP/IMM follow-up (DLMS 870M, Materiel
Returns Supply Status) will be prepared and forwarded to the reporting activity. DLMS
870M will not be generated until at least five calendar days have elapsed from the
10
ADC 1071, Implementation of DoD Item Unique Identification (IUID) Supply Policy in Version 4030
DLMS 856R Shipment Status Materiel Returns.
11
Refer to ADC 1198
C11-20 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
transmission of DLMS 870M (from ICP/IMM) for PD 03 or 50 calendar days for PD 13
and no DLMS 856R, Shipment Status Materiel Returns, or receipt has been posted.
DLMS 870M with Status Code T3 may be generated upon expiration of the due-in
timeframe when DLMS 856R has been received, but receipt has not been posted. The
ICP/IMM is authorized to follow up without regard to the established timeframe when the
need arises to satisfy PD 01-08 requirements.
C11-21 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.14.3. Receipt of DS 180M, Follow-Up for ICP/IMM Materiel Receipt Status.
On receipt of a DLMS 180M, Materiel Returns Reporting, ICP/IMM will review records
and take action as follows:
C11.14.3.1. Received Materiel. If the records indicate that the materiel has
been received and classified, transmit a DLMS 870M, Materiel Returns Supply Status,
to the customer.
C11.14.3.3. Materiel Not Located. If records indicate that the materiel has
not been received, and if the materiel is not located after investigation, the reporting
activity will be sent DLMS 870M, Materiel Returns Supply Status (From ICP/IMM), with
Status Code TU.
C11.14.5. Items Not Under Cognizance of the ICP/IMM. DLMS 180M, Materiel
Returns Reporting (For Reply to Asset Report), received for items not under awareness
of the ICP/IMM will be rejected to the reporting activity using DLMS 870M, Materiel
Returns Supply Status (From ICP/IMM), with Status Code SC. DLMS 180M, Follow-up
for ICP/IMM Reply to Customer Asset Report, that does not pass data field validity edits
will be rejected to the reporting activity using DLMS 870M Status with the appropriate
reject status code.
C11.15.2. Materiel Not Received by Due-In Estimate. The ICP/IMM will initiate
cancellation (DLMS 870M, Materiel Returns Supply Status) action when materiel is not
received by the due-in EDD or when materiel is not received and no response has been
received within 30 calendar days after its DLMS 870M, ICP/IMM Follow-Up. ICP/IMM
will also initiate cancellation when DLMS 856R, Shipment Status Materiel Returns, is
not received within 120 calendar days (CONUS) or 180 calendar days (OCONUS) after
receipt of DLMS 870M, Materiel Returns Supply Status.
C11-22 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.15.3.1. Creditable Returns. For creditable returns, notification of
cancellation to the reporting activity will be made using DLMS 870M, Materiel Returns
Supply Status, with Status Code TP.
C11.15.4. Receipt of Shipment Status. When DLMS 856R has been received, but
material has not been received within the timeframe allotted under C11.11.2.1., action
to cancel the due-in and PMR will be accomplished under Chapter 12 procedures.
C11.16.1. Advice Code 3T. Upon receipt of DLMS 180M, Materiel Returns
Reporting, Cancellation of Customer Asset Report, or Customer Follow-Up to ICP/IMM
(For Reply to Asset Report), transaction from DAAS with Advice Code 3T when the
SOS has been changed, the losing ICP/IMM will arrange to change the FLIS and DAAS
SOS files.
C11.16.2. Losing Supply Source. The losing ICP/IMM will prepare and transmit
through DAAS DLMS 180M, Materiel Returns Reporting (Report of Available Assets to
ICP/IMM), Cancellation of Customer Asset Report, and/or Customer Follow-Up to
ICP/IMM (For Reply to Asset Report)), transactions containing Advice Code 3U to the
gaining SOS.
C11.16.3. DAAS Action. DAAS will pass DLMS 180M transactions, above, to the
gaining SOS.
C11.17.1. Purpose. This paragraph outlines procedures for filling back orders by
generating lateral redistribution orders for retail materiel that has been identified through
an inter- or intra-DoD Component retail asset visibility system. Additionally, ICPs/IMMs
may use these procedures to direct lateral redistribution when the total cost of such
action is lower or when the wholesale level does not have stock available to meet a
requisition’s required response time.
C11-23 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
ICP/IMM DoDAAC and fund code, materiel average acquisition cost, and the RIC of
the receiving ICP/IMM. Conformance with SLOA/accounting classification requires
any initiation of a financial business event to include SLOA mandated standard
financial information system (SFIS) elements. The DLMS shipment status for
ICP/IMM directed lateral redistribution supports inclusion of SLOA required
elements. Pending full implementation of SLOA, DAAS will facilitate
interoperability by updating selected SLOA data fields based upon the reporting
activity’s Service/Agency and Fund Code. If discrete values for the SLOA data
elements in the transaction do not match data elements from the SFIS Fund Code
to Fund Account Conversion Table for the Fund Code in the transaction, reject
with the DLMS 824R Reject Advice citing Reject Advice Code BU. The LRO will be
forwarded through DAAS to the reporting activity. DLMS 945A, Materiel Release
Advice (to ICP/IMM From Storage Activity) with Status Code BA will be provided to
eligible status recipients.
C11-24 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.17.4.2. Update Estimated Ship Dates. Use DLMS 945A, Materiel
Release Advice (To ICP From Storage Activity), with Status Code BA and Distribution
Code 2 or 3 to update ESDs.
12
Refer to ADC 1062. Initial implementation applicable to Global Combat Supply System-Army (GCSS-
Army) and authorized trading partners. Phased implementation for shipment status is authorized.
C11-25 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
01-03 and Special Requirements Code N) may be submitted using a passing order
requisition (DLMS 511R/DIC A3_ with Transaction Type code BM) identifying the retail
source supply as the RIC-To. These transactions will bypass DAAS routing logic to the
wholesale SoS. By alternative, the requiring Service may choose to skip the initiating
requisition passing order transaction and request materiel in person as bearer walk-thru.
C11.18.4 The Service supply source has responsibility for preparation of Interfund
billing and any required internal transactions associated with this method of lateral
supply support.
C11.19.1.2. Upon notification of receipt, the DLA ICP will determine whether
a corresponding sale to Service maintenance (identified by DoDAAC series/internal
customer group) has occurred for the same materiel and condition code within a 60 day
time frame. If there is a matching sale, the customer will receive credit equal to the
C11-26 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
original sale. The Service’s financial system will be notified of a credit via a DLMS
810L, Logistics Bill (MILSBILLS Billing for Issue from Stock (Credit) (DIC FA2)).
C11.19.1.3. If no sale has occurred or the condition code differs from that on
the original sale, DLA will provide credit based upon stock position. If the return
quantity exceeds that of previous sales, credit will be provided equal to the original sale
quantity and credit on the remaining quantity will be based upon stock position. DLA
ICP business rules for determining whether to provide credit/credit amount are
equivalent to the MRP program and policy contained in DoDM 4140.01. The Service’s
financial system will be notified of a credit via a DLMS 810L (MILSBILLS DIC FA2).
C11.20.1. General Requirements. The DoD supply chain may require the return
of supply items for a variety of reasons beyond the usual excesses turned in for credit
under the materiel returns program (MRP) described earlier in this chapter. These can
include the exchange of depot level repairable (DLR) Class IX repair parts as required
by Military Services’ Exchange Pricing programs, the retrograde of forward-positioned
retail stock back to a home location, and discrepant/deficient materiel returns directed
by SDRs, Product Quality Deficiency Reports (PQDRs), or TDRs. In some cases,
logistics business rules require that the return use the same document number as the
related order/sale. While this reuse may be appropriate for some materiel held at the
customer’s location, it is not feasible for all situations. When the materiel is already
located in a DLA Distribution Center and no physical shipment is required to return the
materiel to the original owner/manager, the current owner must not reuse (or suffix) the
original document number for the Prepositioned Materiel Receipt (PMR) and Materiel
Release Order (MRO) directing the return. The responsible action activity must assign
an alternative document number when materiel is located in a DLA Distribution Center
and the current owner must use a ship-in-place MRO to direct the return or when the
submitters system prohibits reuse of document numbers. Returning activities may ask
for an alternative document number if the action activity does not provide one. When
using a new document number for the directed return of discrepant/deficient materiel,
the responsible activity and the returning activity must retain an audit trail linking the old
and new document number/suffix. The PMR, Materiel Returns Shipment Status, and
C11-27 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Receipt provide transactional visibility of the original and new document numbers. The
directed return must identify the return-to location by DoDAAC or CAGE (used for
contractors when no DoDAAC is assigned). Clear text addresses may be included in
addition to the DoDAAC and must be included for returns directed to a contractor
identified by a CAGE only. The use of a combination of enhanced return transactions
and the addition of specific indicators to other transactions allows for the specific
reporting of the transactions without confusion about the nature of the return and enable
enhanced in-transit visibility (ITV) of these returns. The procedures also support recent
process improvement initiatives related to requirements for directed returns.
C11.20.2. Associated Transactions. There are three DLMS transactions that contain
specific content that support the procedures for retrograde and directed
discrepant/deficient returns. They are the DLMS 527D, Pre-Positioned Materiel Receipt,
DLMS 856R, Materiel Returns Shipment Status, and DLMS 842A/R Standard Supply
Discrepancy Report Reply. A fourth transaction, the DLMS 842P, Product Quality
Deficiency Report (PQDR), is pending implementation. 13
C11.20.2.3. The materiel returns shipment status will include passive radio
frequency identification (pRFID) when applicable. Under DoD IUID Supply Policy, the
DLMS materiel returns shipment status identifying capital equipment or NSNs
containing an IUID Indicator Y in FLIS, must include serial numbers and the
corresponding UIIs (when UII is available).
13
Refer to ADC 1007 series.
14
Refer to ADC 1198.
C11-28 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
by an SDR, PQDR, or TDR response. This section also addresses retrograde of
forward-positioned retail stock back to a home location.
C11.20.3.1.2. The organization responsible for the SDR reply will take
action to establish a due-in and generate a PMR transaction to the receiving activity.
The PMR will include the return quantity and the appropriate supply condition code.
Action to establish the due-in and create the PMR transaction will be accomplished
under MILSTRAP/DLMS. The PMR will perpetuate the document number associated
with the SDR, normally the document number of the original shipment, or the alternative
document number assigned by the activity directing the return as described in
paragraph C11.20.1. The DLMS PMR will include a Return Type Code indicating the
reason for return for which the PMR is established and will perpetuate the DoD
WebSDR control number associated with the SDR.
C11.20.3.1.3. The PMR Due-in EDD indicating the time allowed for
shipment and return of discrepant materiel will be based upon the date of the SDR reply
directing the return. The EDD will be calculated based upon the date of the initial SDR
reply directing return. (This may be a reply from the storage activity when action activity
responsibility has been delegated by the ICP/IM.) The EDD is a “not to exceed” time
standard established for system processing and does not necessarily equal the number
of days identified in the SDR reply. The return-by date may be dictated by policy or by
need. PMR time standards are shown in Table C11.T1., PMR Due-In Estimated
Delivery Date for SDRs.
C11-29 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Table C11.T1. Pre-Positioned Materiel Receipt Due-In Estimated Delivery Date for
Supply Discrepancy Reports
EDD USAGE
C11-30 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
automated research tools to determine status where applicable: query for materiel
returns shipment status in WEB Visual Logistics Information Processing System
(WEBVLIPS), transportation shipment status in Integrated Data Environment (IDE)-
Global Transportation Network (GTN) Convergence (IGC), and Report of Shipment
(REPSHIP) in Intelligent Road/Rail Information Server (IRRIS). Offline communication
with the shipper may be necessary to determine the status of the materiel. The ICP will
verify that proper discrepancy procedures are followed for materiel reported as in-transit
and not received. If shipment was delayed an updated EDD will be identified and
disseminated.
C11-31 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
reason for the PMR as return of quality deficient materiel and will perpetuate the PQDR
report control number (RCN).
C11.20.3.2.3. The PMR due-in EDD indicating the time allowed for
shipment and return of deficient materiel will be based upon the date of the PQDR reply
directing the return. The EDD is a “not to exceed” time standard established for system
processing and does not necessarily correlate to the PQDR reply return-by date which
may be dictated by other criteria. See Table C11.T2., PMR Estimated Delivery Date
Days for Product Quality Deficiency Reports, to establish the EDD.
Table C11.T2. Pre-Positioned Materiel Receipt Estimated Delivery Date Days for
Product Quality Deficiency Reports
EDD USAGE
C11-32 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C11.20.3.2.5. Upon receipt of materiel returns shipment status, the
ICP/IMM will recalculate the EDD to equal the original time allowed for shipment and
return of materiel (i.e., reset the EDD using the date of the shipment status as the
starting date, comparable to MILSTRIP MRP EDD procedures) and provide a
replacement PMR to the receiving location. This action ensures that both records have
the same EDD.
C11.20.3.2.6. The ICP/IMM and the ILCO will monitor for directed
returns. Follow-up with customers is required where materiel/PQDR exhibit has not
been returned by the EDD. The ICP/IMM will use automated research tools to
determine status where applicable: query for materiel returns shipment status in
WEBVLIPS, transportation shipment status in IGC, and REPSHIP in IRRIS. The ICP
will verify that proper discrepancy procedures are followed for materiel reported as in-
transit and not received. The originator of the PMR will cancel the PMR if
circumstances have changed and materiel will not be returned as directed. The PMR
will be cancelled and a new PMR established if the originally planned receiving location
is changed.
C11.20.3.3.3. The PMR due-in EDD indicating the time allowed for
shipment and return of deficient materiel will be based upon the date of the TDR
response directing the return. The EDD is a “not to exceed” time standard established
for system processing and does not necessarily correlate to the TDR reply return-by
date, which may be dictated by other criteria. See Table C11.T3., Due-In Estimated
Delivery Date for Transportation Discrepancy Report, to establish the EDD.
C11-33 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
EDD USAGE
45 calendar days Returns within Combatant Command/geographic area
90 calendar days Returns between Combatant Commands/geographic areas
(e.g., between CONUS and OCONUS locations)
195 calendar days Security Assistance returns
C11.20.3.3.6. The ICP/IMM and ILCO will monitor for receipt. Follow-up
with customers is required where materiel has not been returned by the EDD. The
ICP/IMM will use automated research tools to determine status where applicable: query
for materiel returns shipment status in WEBVLIPS, transportation shipment status in
IGC, and REPSHIP in IRRIS. The ICP will verify that proper discrepancy procedures
are followed for materiel reported as in-transit and not received. The originator of the
PMR will cancel the PMR if circumstances have changed and materiel will not be
C11-34 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
returned as directed. The PMR will be cancelled and a new PMR established if the
originally planned receiving location is changed.
C11.20.3.4.3. The PMR EDD indicating the time allowed for shipment
and return of deficient materiel will be based upon the date of the directed return or
generation of PMR where the return is initiated by the returning activity. The EDD is a
“not to exceed” time standard established for system processing and does not
necessarily correlate to the reply return-by date when applicable since that date may be
dictated by other criteria. See Table C11.T4., PMR EDD Time Standard for Retrograde
Returns, to establish the EDD.
EDD USAGE
45 calendar days Returns within Combatant Command/geographic area
90 calendar days Returns between Combatant Commands/geographic areas
(e.g., between CONUS and OCONUS locations)
195 calendar days Security Assistance returns
C11-35 CHAPTER 11
DLM 4000.25, Volume 2, January 22, 2024
Change 17
number may be included when applicable to identify the original requisition document
number. The materiel returns shipment status will include pRFID, and for NSNs
containing an IUID Indicator Y, UII(s) and/or corresponding serial numbers must be
included in the DLMS 856R, indicating that DoD IUID Supply Policy compliance is
required. Shipment returns containing IUID data content (e.g., UIIs and/or serial
numbers or capital equipment requiring serial numbers and UIIs if available) and
requiring more than one freight piece to execute the movement must have a unique
TCN assigned to each freight piece by using a partial indicator in the 16th position of the
TCN. Multiple freight piece shipments using the same TCN for all related freight pieces
are not authorized when IUID content is required. The shipment status will be directed
to the ICP/IMM (or other organization that directed the return). With the exception of
capital equipment assigned under an established UIT program and requires serialization
data visibility, the ICP/IMM (or other organization directing the return) is not required to
store the UIIs and/or serial numbers. The shipment status will also be directed to the
return-to activity when identified by DoDAAC. DAAS will transmit to DLMS capable
activities as identified.
C11.20.3.4.6. The ICP/IMM will monitor for receipt. Follow-up with the
returning activity is required where materiel has not been returned by the EDD. The
ICP/IMM will use automated research tools to determine status where applicable: query
for materiel returns shipment status in WEBVLIPS, transportation shipment status in
IGC, and REPSHIP in IRRIS. The ICP will verify that proper discrepancy procedures
are followed for materiel reported as in-transit and not received. The originator of the
PMR will cancel the PMR if circumstances have changed and materiel will not be
returned as directed. The PMR will be cancelled and a new PMR established if the
originally planned receiving location is changed.
C11-36 CHAPTER 11
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C12. CHAPTER 12
DUE-IN AND PRE-POSITIONED MATERIEL RECEIPT
C12.1. GENERAL
C12-1 CHAPTER 12
DLM 4000.25, Volume 2, April 09, 2022
Change 14
Delinquent Due-in Inquiry. This transaction provides MILSTRAP legacy DIC DLC
functionality.
C12.1.5. Use of DLMS 527D. Use the DLMS 527D functionality as follows:
C12.1.5.2. GIMs use for due-in reconciliation and to inquire about delinquent
due-in transactions
C12.2.1. Establishing Due-In Records. IMMs will establish due-in records for all
anticipated receipts of materiel to maintain property accountability or visibility of materiel
due-in to inventory, as required under Chapter 6.
C12.2.2. Keep Current Status. IMMs shall keep due-in records in a current status.
Use revised delivery schedules, notification of shipment or delayed shipment, repair
schedules and repair schedule changes, contracts and contract changes, customer and
manager cancellations, materiel receipts, and completion of shipment
tracer/discrepancy reporting actions to establish, revise, and delete due-in records and
maintain appropriate delivery dates. Refer to Chapter 11, C11.20. for specific content
and estimated delivery date requirements for PMR associated with directed
discrepant/deficient materiel returns and retrograde returns.
C12.2.3. Audit Trail. IMMs will establish an audit trail when deleting or reversing
due-in quantities. All due-in deletions and reversals will interface with the financial
C12-2 CHAPTER 12
DLM 4000.25, Volume 2, April 09, 2022
Change 14
system. Due-in deletions and reversals are prohibited without advance coordination
between the supply and financial functions, and with the procurement function for dues-
in from procurement instrument sources, unless the supply, financial, and procurement
systems are fully integrated. When deleting or reversing due-in quantities, managers
will initiate action to correct the receiving storage activity's PMR file under C12.3.3.
C12.2.4. Supply and Financial Interface. The DoD Components will establish the
necessary interface between supply and financial operations/functions to account for
materiel in-transit as required under DoD 7000.14-R, “Department of Defense Financial
Management Regulation”.
C12.2.5. In-Transit Due-In Procedures. IMMs will monitor due-in records and
inquire to storage activities for information on in-transit dues-in under the procedures in
Chapter 13.
C12.2.6. Product Quality Deficiency Materiel. When IMMs direct materiel for
return based on a reported product quality deficiency, they will prescribe use of Supply
Condition Code (SCC) Q in the disposition instructions to the returning activity. IMMs
will establish and monitor due-ins for all returns of potential/confirmed product quality
deficiency related materiel, citing the document number included in the report. Provide
PMRs for the returns to receiving storage activities, under C12.3, citing the due-in
document number and SCC.
1
DLA DSS will implement these new procedures IAW Approved DLMS Change (ADC) 172 in January
2007, enabling DSS to use the indicator when the IMM provides it in the 527D PMR transaction.
C12-3 CHAPTER 12
DLM 4000.25, Volume 2, April 09, 2022
Change 14
the PMR from the IMM. Storage activities may use the PMR contract information and
packaging data to facilitate the receiving process.
C12.3.3. PMR. IMMs will send PMR transactions and PMR transaction reversals
as due-in records are revised so that receiving storage activities can maintain the
records to show status equivalent to IMM due-in records. IMMs will send PMR
reversals to the storage activities when deleting due-in records. IMMs will also send
PMR reversals when revising due-in records (e.g., dates, quantities, destinations) and
simultaneously send replacement PMR transactions showing revised due-in record
data.
2
Refer to ADC 297, DAAS Passive Radio Frequency Identification (pRIFD)-Required Exclusion Table for
DLMS 527D PMR/Prepositioned Materiel Receipt (PMR). At the time of implementation, DLA is the only
participating Component.
C12-4 CHAPTER 12
DLM 4000.25, Volume 2, April 09, 2022
Change 14
site that materiel to support their replenishment requirement is delayed. In this
instance, PMR will contain the quantity not available for push replenishment, the Delay
Notification Code BD and an estimated shipping date. If at the time push replenishment
is required, only a partial quantity is available, then two PMR transactions will be
generated; one for the quantity pushed and one for quantity delayed. These
transactions will have different document numbers and the delayed one will have the
BD Delay Notification Code. Later, if only a partial amount of the quantity previously
delayed becomes available to push, two PMR transactions will be generated. The one
for the quantity pushed will maintain the document number of the original delayed
notification with the “BD” indicator eliminated. The PMR for the quantity still delayed
must be assigned a new document number and a BD Delay Notification Code. If the
total quantity is initially delayed and later the total quantity is shipped, PMR must have
the same document number throughout the process. The IMM will update/replace the
PMR delayed notification anytime either the replenishment quantity or the estimated
shipping date changes. New delayed notification must maintain the same document
number unless a partial push occurs. Replacement delayed notification under the same
or new document number will not require the reversal of the previous PMR transaction.
Reversal logic for PMR transactions indicating that a push shipment has been initiated
will follow the requirement in C12.3.3.
C12.3.5. PMR for Materiel Returns under NIMS and Base Realignment and
Closure (BRAC) Retail Supply, Storage and Distribution (SS&D)/Inventory Management
and Stock Positioning (IMSP). The PMR is used in a variation of the materiel returns
program for processing DLA-managed materiel returns to DLA from selected sites in
support of the BRAC SS&D/IMSP and NIMS. The returning activity will be responsible
for submission of an PMR to the storage site identifying the Military Service activity to
which the receipt will be reported for these returns of DLA-managed items. Because
the Military Service sites will no longer retain retail stock balances under these
programs, DLA will assume ownership of all materials regardless of asset position.
Upon notification of receipt of returned materiel by the storage activity via a Receipt
Transaction (DLMS 527R Receipt with 2/LIN01/10 Code I; MILSTRAP DIC D6A), the
Military Service activity will determine if there is a need for the material by another
maintenance user (backorder). If so, an issue document will be forwarded to the
storage activity for action. If not, a materiel release order will be initiated, directing
shipment-in-place (citing the ship-to/supplemental address of the storage activity),
authorizing a change of ownership to DLA. The receipt of the returned materiel from the
Military Service ownership to DLA will be accomplished with a receipt (DLMS 527R
Receipt with 2/LIN01/10 Code J; MILSTRAP DIC D6B).
3
Refer to ASC 1395.
C12-5 CHAPTER 12
DLM 4000.25, Volume 2, April 09, 2022
Change 14
owner. In addition, the MRO and the PMR will serve as evidential matter to justify
the transfer.
C12-6 CHAPTER 12
DLM 4000.25, Volume 2, April 09, 2022
Change 14
due-in to the GIM. Additionally, when an award is made for an unawarded purchase
request, the LIM will prepare and send a memorandum due-in reversal and a new
memorandum due-in transaction to the GIM and a PMR transaction to the applicable
storage activity.
C12. 6.1.1. Inquiry for Due-In with Expired EDD. The GIM will initiate a
DLMS 527D due-in inquiry when the EDD for delivery of materiel is delinquent by more
than 30 calendar days. Compute the delinquent date from the memorandum due-in that
the LIM provided on the ETD. The GIM will also initiate DLMS 527D when a revised
due-in date later becomes delinquent by 30 calendar days.
C12.6.1.2. Inquiry for Due-In with Invalid EDD. The GIM will initiate DLMS
527D due-in inquiry 30 calendar days after the ETD when the memorandum due-in, the
LIM provided on the ETD, contains an invalid EDD (e.g., for materiel pending
procurement/contract action by the LIM). The GIM will initiate a second inquiry 60
calendar days after the ETD for all dues-in with invalid EDDs. If the LIM does not reply
to the second inquiry, the GIM must intervene off-line. The GIM will include all due-ins
with invalid EDDs 90 calendar days after the ETD in the reconciliation. Based on the
response, the GIM will determine if additional inquiry/reconciliation action is required.
C12.6.2.1. The LIM will provide the GIM with due-in information in response
to an inquiry using a delinquent due-in advice transaction citing the appropriate asset
transfer status code.
C12.6.3.1. Due-In Verification. The DoD Components will use the due-in
reconciliation process to verify that the GIM is in receipt of all procurement/contract
award data for assets due-in and the most current EDDs available. This process will
also ensure that all items still pending procurement/contract award on the ETD are still
valid.
C12-7 CHAPTER 12
DLM 4000.25, Volume 2, April 09, 2022
Change 14
C12.6.3.3. Due-In Reconciliation Response. The LIM will respond to due-in
reconciliation requests using a due-in reconciliation advice containing the appropriate
asset transfer status code. The LIM will ensure that due-in information for all items still
pending procurement/contract action, pending delivery, or in litigation is readily available
to respond to the reconciliation request.
C12-8 CHAPTER 12
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13. CHAPTER 13
MATERIEL RECEIPT
C13.1. GENERAL
C13.1.1. Purpose.
C13.1.2. There are additional processing procedures over and above those
contained in this chapter that must be applied for items identified as serially managed
materiel requiring owner visibility at DLA Distribution Centers. The identity of the
materiel and the additive procedures are in Chapter 30.
C13-1 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.1.3.2. Receipt Inquiry Transaction is identified by the DLMS 527R ASC
X12 beginning segment (1/BR02/020) Transaction Type Code IN – Inquiry. This
transaction provides MILSTRAP legacy DIC DXA/DXB functionality.
C13.1.5. Use of DLMS 527R for Receipt. DLMS 527R will be used by receiving
activities to report both receipts and historical receipt information to owners and other
management control activities.
C13-2 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.1. Receiving Activity Actions. Receiving activities will report receipts of
materiel using a Materiel Receipt transaction and:
1
Refer to ADC 1273.
2
Ibid.
C13-3 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.5.1.2. Package markings must be in accordance with MIL-STD-
129.
C13.2.6.1. Purchase card receipts from AMMA sites must contain a purchase
card account number and purchase card call number in order to uniquely identify
transactions. A vendor reference number should also be included which is the
C13-4 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Customer Automation and Reporting Environment invoice number. This value will help
with issue resolution and reconciliation.
C13.2.7.1.1. The first segment is the time period between the date
materiel is turned over by the carrier to the designated receiving activity and the date of
posting the receipt to the total item property records (both accountable and owner
records).
C13.2.7.1.2. The second segment is the time period between the date
materiel is turned over by the carrier to the designated receiving activity and the date
stored. Materiel is considered to be stored when it reaches the first location (either
temporary or permanent) where actual storage control exists through locator data and
the materiel can be issued without delay in response to materiel release documentation.
C13.2.7.3. Making asset records visible from the point of inspection and
acceptance must be accomplished within 24 hours of recording receipts (holidays and
weekends excepted). (This applies to receipts from a procurement source when
required inspection and acceptance are not performed at origin.) The accounting and
finance office will be notified of the item receipt within the 24-hour period.
C13-5 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
performance against the time standard, include Receipt Transactions frustrated for a
long period of time prior to posting, storing, or reporting
C13.2.8.2. Actions after Materiel Receipt. Do the following actions after the
materiel has been physically received but prior to or concurrent with movement to
storage:
C13-6 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.9.1. Discrepant/Deficient Reports. In addition to processing and
reporting materiel receipts, receiving storage activities will submit reports for all
discrepant/deficient receipts in accordance with the procedures and forms prescribed by
the following:
C13.2.9.2. Exceptions. Neither the dollar value nor the timeframes for
submitting discrepancy/deficiency reports apply for reporting the materiel receipt to the
owner. The receipt reporting timeframes are prescribed by C13.2.7.The procedures for
reporting receipt of discrepant/deficient shipments to the owner are prescribed by
C13.2.9.3.
3
Refer to ADC 1198 and ADC 1198A.
C13-7 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
documentation corresponds with the identification label in accordance with MIL-STD-
129 marking requirements. 4
4
Refer to ADC 1269.
C13-8 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.9.3.4.2. Authorized procurement delivery documents and
vendor packing lists.
C13-9 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
packed and expiration date. The U.S. Government's right to litigate a discrepant receipt
is not affected by the point of acceptance. Consequently, receiving activities will report
discrepancies detected during the destination examination in accordance with the
regulations cited in C13.2.9.1.
C13-10 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
When overages are valued above the contract variance clause, or above the excess
delivery clause (after considering any allowable variance), report the overage above the
allowable variance as discrepant with a Receipt Transaction citing SCC L and
Management Code U. Owners will initiate immediate action to resolve the discrepancy
upon receipt of the Receipt Transaction. Overages within the allowable variance or
within the excess delivery clause (after considering any allowable variance) are not
discrepant. Report the total quantity in the applicable condition, and do not cite a
management code for that quantity.
C13-11 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.9.3.8.11. Receipts Not Due-In (no PMR file exists). When a
PMR is not available, the receiving activity will report the receipt using documentation,
packaging, and other information, as available. DLA Distribution Centers will prepare
an SDR to report the lack of a PMR to the manager (as the only discrepancy or in
combination with other identified discrepancies). The distribution center will identify the
SDR as informational or otherwise indicate requested action.
C13-12 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.9.3.9.1. Identifying the NSN. When a receipt cannot be
identified to an NSN, the receiving activity will attempt to identify the NSN or usage by
following the procedures in C13.2.8.2.1., and report the receipt to the owner.
C13-13 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
than $500 per item except as specified in these procedures, or take other automatic
disposal action based on criteria issued by the DoD Components. This includes expired
shelf-life materiel identified as Type I, or whose expiration cannot be identified at time of
receipt regardless of ownership, supply condition code, or dollar value, except as listed
in C13.2.5.3.2. When taking automatic disposal action, cite SCC H and Management
Code M or T in the Receipt Transaction, in addition to the discrepant receipt
management code, for the discrepant quantity. To establish an audit trail when materiel
is condemned upon receipt and shipped directly to DLA Disposition Services, cite the
disposal turn-in document number in the Receipt Transaction in addition to the original
document number.
• DEMIL Codes: B, C, D, E, F, G, or P
• CIIC: A-H, K, L, O, Q, R, S, T, 5, 6, 8, 9
C13-14 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.9.3.10.1.1.3.4. FMS materiel will not be
subject to automatic disposal. Follow procedures in paragraph C13.2.9.3.10.1.
C13-15 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.9.3.10.8. Wrong Item. Report receipt of the total quantity of
the incorrect item in the applicable condition citing the NSN of the incorrect item
received and the discrepant receipt management code for the quantity. If both correct
and incorrect items are received in the same shipment, submit a separate Receipt
Transaction for the correct item.
C13-16 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
ensures the assets are recorded on a DoD record. The Navy, Marine Corps, and Air
Force have directed implementation of this procedure as follows:
5
Refer to ADC 1102/1102A.
C13-17 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
the packaging label, including AIT readable content; the item marking, including AIT
readable marks; supply documentation; the due-in record; and/or a mismatch between
the item and any of these. Discrepancies identified during receipt of new procurement
materiel must be reported prior to acceptance (if not accepted at origin). Discrepant
materiel may be placed in a suspended condition pending resolution. Discrepancies
that resulted in incorrect information within the IUID registry must be reported and
corrective action taken.
C13-18 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.10. Maintaining Accountability During Maintenance Actions
C13.2.10.1. Applicability.
C13.2.10.4. Accountability
C13.2.10.5. Requirements
C13-19 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.10.5.2.1. Receiving Storage Activity Reporting. Receiving
storage activities will report receipt of reparable materiel based on the information
contained in the PMR file. If an PMR file is not available, report the receipt in
accordance with C13.2.9.3.10.11.2. for processing receipts not-due-in for reparable
items.
C13.2.10.7. Item Owner Actions. Owners will establish due-in records for
expected returns from commercial and Government maintenance activities and provide
C13-20 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
PMR to the storage activities to receive the materiel under Chapter 12. Storage
activities will report receipts under this section.
C13-21 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.12.1. Procurement Instrument Processing. The storage activity will
process procurement instrument source receipts for LR materiel received after 1 year
past the effective transfer date (ETD), in the same manner that they process
procurement instrument source receipts received during the ETD to 1-year period.
C13.2.12.2. Storage Activity Actions. For receipt of materiel that has been
logistically reassigned, after the ETD, the receiving storage activity will perform the
following:
C13-22 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.2.12.4. Reject Receipt as Appropriate. If a procurement instrument
source receipt for an LR item is incorrectly reported to the LIM or the GIM, and the LIM
or GIM does not have a recorded due-in, did not initiate the procurement action, and/or
has a record of a due-in or memorandum due-in and is able to determine the
appropriate reporting for the receipt, the LIM or GIM should reject the receipt back to the
initiator using DLMS 824R, Reject Advice, and citing Reject Advice Code AB (Navigate
to LOGDRMS and enter advice code AB in the “Enter a Specific Data Code to Search
for” text box, click “Search”).
C13.3.2. Tracer Action. When the storage activity response shows that the
materiel has not been received, initiate any shipment tracer and/or discrepancy reports
required under the procedures cited in C13.2.9. Coordinate with the CAO/PO for in-
transit contract receipts. Storage activities will submit shipment tracers and discrepancy
reports for materiel not received as shown in the DoD Component implementing
procedures or when directed to do so by the owner.
C13.4.2. Receipt in Process. When the storage activity has the receipt in process,
storage activities will reply using the Response to Inquiry Transaction citing Advice
Code 3K
C13.4.3. No Receipt but Record of Due-In. When the storage activity has no
receipt in process but there is a PMR file, the storage activity will reply using the
Response to Inquiry Transaction citing Advice Code 3M.
C13.4.4. No Receipt and No Record of Due-in. When the storage activity has no
receipt in process and no record of a PMR file, the storage activity will reply using the
Response to Inquiry Transaction citing Advice Code 3N.
6
Refer to ADC 313. DoD components must provide Defense Enterprise Data Standards Office with their
Component implementation date for ADC 313.
C13-23 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.5. ARMY EXCHANGE PRICING PROCESS
C13.5.1. The Army approach to the Exchange Pricing (EP) interim approach is a
multi-system functionality implementation. EP employs a dual pricing system for
repairable NSN items based upon Standard Price (latest acquisition cost plus cost
recovery rate) and Exchange Price (latest repair cost plus cost recovery rate) and a
“buy one – return one” relationship with the customer. That is, a qualified exchange
pricing customer buys at the Exchange Price and pays a penalty if a reparable is not
turned-in within a specified period of time from the issue date. This process is
applicable to the Army customers and Army-managed materiel only; other Services will
continue to pay Standard Price and receive 65 percent credit exchange upon receipt of
carcass by the Army primary inventory control activity (PICA).
C13.5.2. Once an item of supply is identified for a national repair program and the
national item identification number (NIIN) has an established Exchange Price, all
requisitions for the item will be priced at the Exchange Price if the customer is an
authorized EP customer.
C.13.5.4. All related supply transactions prepared by the Army will carry and
perpetuate the EP Indicator. As a result of the EP implementation the following
transactions will be impacted, Requisition, Requisition Modifier, Requisition Follow-Up,
Materiel Release Order and Supply Status. The returns process will also process EP
related transactions. The Materiel Receipt transaction will be generated by SARSS for
all returns of EP NIINs, and will include an EP Type of Credit indicator for Unserviceable
credit when applicable, as well as an EP Conversion Indicator to identify the need to
provide credit according the pre-EP credit policy, which will last for 60 calendar days
following the implementation of Exchange Pricing.
C13-24 CHAPTER 13
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C13.6. OPTIONAL INTRA-SERVICE USE OF RECEIPT FOR MATERIEL
PROVIDED TO CONTRACTORS AS GOVERNMENT FURNISHED MATERIEL. Under
the Government Furnished Materiel (GFM) business process contractors are authorized
to receive specific items and quantities of GFM from Government supply sources.
Materiel may be issued to the contractor based upon a contract schedule/bill of material
(BOM) or issued in response to a requisition made by the contractor or a responsible
Government representative. It is normally required that the contractor (or authorized
Government representative) submit a materiel receipt acknowledgment (MRA)
Transaction to the ICP under MRA procedures (refer to Chapter 10, C10.2.5.6).
However, on an intra-Service basis, if the Service requires the contractor to send a
Receipt Transaction to their issuing ICP rather than an MRA, the contractor must cite
the DoD contract number which authorized the provision of GFM. This establishes
GFM accountability to the contract. The GFM contract number, and call/order number,
when applicable, is required in addition to the controlling document number for the
Receipt Transaction. Under the MRA exclusions, MRA is not required for shipments to
contractors, commercial, or industrial activities which are receipt reported to the owning
ICP.
C13-25 CHAPTER 13
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C14. CHAPTER 14
ISSUE, LOAN, DEMAND, AND SINGLE MANAGER FOR
CONVENTIONAL AMMUNITION FREEZE/UNFREEZE
ACTION
C14.1. GENERAL
C14-1 CHAPTER 14
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C14.2. ISSUE
C14.2.1. General
C14-2 CHAPTER 14
DLM 4000.25, Volume 2, October 09, 2018
Change 11
information system (SFIS) elements. 1 The DLMS issue transaction supports inclusion
of SLOA required elements. Pending full implementation of SLOA, DAAS will facilitate
interoperability by updating selected SLOA data fields based upon the initiating activity’s
Service/Agency and Fund Code. If discrete values for the SLOA data elements in the
transaction do not match data elements from the SFIS Fund Code to Fund Account
Conversion Table for the Fund Code in the transaction, reject with the DLMS 824R
Reject Advice citing Reject Advice Code BU.
C14.2.1.4. Issue transactions are used to convey issue data to the ICP.
Issue Transactions resulting from a backorder release are identified by Issue
Transaction related Management Code M.
C14.2.2.1. Applicability
C14.2.2.2. Accountability
1
Refer to ADC 1043/ADC 1043A
C14-3 CHAPTER 14
DLM 4000.25, Volume 2, October 09, 2018
Change 11
facilities will assume accountability of materiel upon receipt at the maintenance facility
and while in its custody during maintenance actions.
C14.2.2.3. Requirements
C14-4 CHAPTER 14
DLM 4000.25, Volume 2, October 09, 2018
Change 11
Management Regulation” accounting and reconciliation requirements. (Responsibility of
the owner (Principal for maintenance by DMISA).)
C14.2.4.1. Issue reversals are used to correct owner and storage activity
inventory records due to erroneous input by the storage activity.
C14-5 CHAPTER 14
DLM 4000.25, Volume 2, October 09, 2018
Change 11
reversals used to adjust inventory records will systemically trigger a financial adjustment
by the owner system, when applicable, for discrepant shipments including, but not
limited to, shortage, wrong item, or incorrect condition. The issue for wrong item
shipments will not be reversed until after the incorrect materiel has been returned to the
storage activity (with exception by direction of the ICP to correct records where a wrong
item received is not returned). 2
C14.2.4.3. Navy use only. Storage activities will cite Reason for Reversal
Code S in the issue reversal transaction when a cancellation request is issued for a
materiel/disposal release order (MRO/DRO) and the item was not shipped. The
reversal requirement stems from a timing issue. The MRO/DRO is in process, the
storage activity property accountability record was decremented and the issue
transaction was sent to the ICP to decrement to the owner balance. Subsequent to this
action, but prior to the materiel being physically shipped and a materiel release
confirmation being generated, the MRO/DRO issue action is cancelled and the materiel
is returned to stock, if necessary. An issue reversal transaction is then required to
increment the storage activity’s property accountability record and the ICP's record to
the original quantity.
2
Refer to ADC 1160. Implementation delayed.
3
Backorder transactions were eliminated from DLMS by intent after coordination with the DoD Supply
Process Review Committee (SPRC).
C14-6 CHAPTER 14
DLM 4000.25, Volume 2, October 09, 2018
Change 11
do not use Issue Transactions for the issue of loan materiel; however, the applied
method should show the issue for audit and accountability purposes. For a
decentralized system, the Issue Transaction, if created by other than the ICP, may be
used.
C14.6.2. When freeze or unfreeze actions are taken based on C14.6.1, the SMCA
will provide the SMCA Freeze/Unfreeze Action Transaction to the owning DoD
Component ICP for update of the ICP wholesale financial accountable records.
C14-7 CHAPTER 14
DLM 4000.25, Volume 2, October 23, 2015
Change 6
C15. CHAPTER 15
INSTALLATION CLOSURE PROCEDURES
C15.1. GENERAL
1
Mass cancellation and follow-on transactions are DLMS enhancements. Refer to ADC 1132.
Delayed implementation authorized.
2
Universal cancellation and follow-on transactions are DLMS enhancements. Refer to ADC 1132.
Delayed implementation authorized.
C15-1 CHAPTER 15
DLM 4000.25, Volume 2, October 23, 2015
Change 6
Code FT) and baseline item data (1/BLI01/10 Code FS). This transaction provides
the functionality of MILSTRIP legacy DIC FTE.
C15.2. APPLICABILITY AND SCOPE. These procedures and timeframes apply to all
DoD installations, both Continental U.S. (CONUS) and Outside the Continental U.S.
(OCONUS); DoD tenant and satellite activities; DoD inventory control points (ICP); and
DoD integrated materiel managers (IMM) processing reports for materiel no longer
required as a result of an installation closure.
C15-2 CHAPTER 15
DLM 4000.25, Volume 2, October 23, 2015
Change 6
C15.3.8. real property.
C15-3 CHAPTER 15
DLM 4000.25, Volume 2, October 23, 2015
Change 6
requisitions not required. When time is insufficient to effect single-line cancellations,
use the mass or universal cancellation procedures under Chapter 27. Universal
cancellation procedures do not provide for continuation of requisitions for
shipment to a new location site.
C15-4 CHAPTER 15
DLM 4000.25, Volume 2, October 23, 2015
Change 6
C15.4.3.6. Reporting Personal Property Items. Report items identified as
related personal property (See C15.3.6.) to the ICP/IMM using the Customer Asset
Report (DLMS 180M) and cite Project Code 3QQ. Project Code 3QQ informs the
ICP/IMM that the item has been placed on the preliminary inventory of related personal
property designated to be transferred to the local community at the time of installation
closure. If there is a DoD requirement, delete the item(s) from the inventory of related
personal property. Do not report related personal property to GSA under materiel
returns program (MRP) procedures.
C15-5 CHAPTER 15
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16. CHAPTER 16
DISPOSITION SERVICES
C16.1. General
C16-1 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.1.2.3.3. Action Code DE – Deny. DLA Disposition Services Field
Office uses to deny the Disposition Category Code DS – Disposal assigned to the DTID
by the DLA Disposition Services ICP.
C16.2.1. General
C16-2 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
four different continental United States (CONUS) screening periods within the
reutilization/transfer/donation (RTD) formal screening cycle: DoD Formal and Special
Programs (Screening Cycle Code = DOD), General Services Administration (Screening
Cycle Code = GSA), Donation (Screening Cycle Code = DON), and a second RTD
screening cycle for items eligible to RTD customers (Screening Cycle Code = RTD2).
Outside continental United States (OCONUS) Screening Cycle Codes are FEPP (for
Department of Defense, DoD Special Programs and federal Civil Agencies); FEPD (for
Donation); and RTD2 for all others. DoD customers can requisition an item at any time
during the cycle; however, non DoD agencies and groups only have access to the item
once it reaches a certain day within that cycle.
C16-3 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
system (SFIS) elements. 1 The DLMS MRO transaction supports inclusion of SLOA
required elements.
C16.2.2.3. RTD Web Generated Requisitions. Items that are within the
reutilization cycles are reported daily by DLA Disposition Services via a property
characteristic flat file to RTD Web when the Screening Cycle Code is either DOD or
RTD2. This daily file to the RTD Web notifies the Web application of the available
items. RTD Web maintains rules that determine eligibility to requisition specific items.
For all requisitions prepared/generated within RTD Web, the document numbers will be
constructed using the customer’s DoDAAC, the current ordinal date, and a serial
number. The serial number may begin with a specific letter value based upon the
applicable business process as directed below.
1
Refer to ADC 1043.
C16-4 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Web only) or specific items from within the container. A separate requisition identifying
the disposition services container identification (ID) is sent for each item ordered by the
customer. If the customer selects the entire container, a separate requisition is still
generated for each item within the container. Where multiple document numbers are
needed to support customers ordering containerized property, the RTD Web-generated
document number will assign serial numbers beginning with utilization code R. The
generation of a distinct document number for each item ordered allows the customer to
have visibility and status relative to the processing of each requisition, maintains
container synchronization, and facilitates inventory control. In addition to the disposition
services container ID mentioned above, when the customer selects the entire container,
each individual DLMS 511R Requisition (Transaction Type Code A0) will include an
indicator (i.e., Container Issued in Full) to communicate that the whole container is
being requisitioned and total of the DTID numbers within the container.
C16-5 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
However, there are situations in support of customers or disaster relief efforts when
Disposition Services will require immediate support for special programs; one example
is customer support for FEMA. In order to support the Special Programs customers,
the DLMS 511R Requisition will provide a Special Programs Hold Override Indicator,
allowing these customers the ability to bypass the required hold period for these
special circumstances.
C16.2.2.5.2.5. Civil Air Patrol - 2YX. Allows the Civil Air Patrol
(CAP), as the official auxiliary of the United States Air Force, to receive excess and
Federal excess personal property (FEPP) without reimbursement.
C16-6 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
requested materiel does not become available during the 60 calendar day period, DLA
Disposition Services will cancel the remaining unfilled quantity and send a DLMS 870S
with Status Code D1 to the requisitioner.
C16.2.4.1. Materiel Release. The MRO (Transaction Type Code NA) will be
used to direct the release of property from a DLA Disposition Services Field Office. The
MRO will be sent from DLA Disposition Services to the field office when materiel is
being issued as a result of sales, reutilization, transfer, or donation. The materiel
release process will be accomplished at the DTID number or DTID number and suffix,
level of detail. The rules in DLMS Volume 2, Chapter 4 apply to the MRO process;
however, the transaction may contain the following additional data to support disposal
processing as described below: DTID number, or DTID number and suffix, disposition
services container ID, container issued in full indicator, minimum/maximum ship
quantity, sales order reference number, complete container count, transportation
method, cancellation mandatory/optional flag, customer type, DEMIL code, DEMIL
integrity code, and/or funds appropriation number. Upon shipment of the materiel for
each MRO, the DLA Disposition Services Field Office will send the DLMS 856S
Shipment Status (Type Transaction Code AS_) transaction to the customer. The
transaction will contain the DTID number or DTID number and suffix of the original
document number, and associated disposition services container ID.
C16-7 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
indicator, the information will be used to insure all requisitions for that container are
received and processed appropriately. MROs generated by DLA Disposition Services
for requisitioned items associated with a container will identify the disposition services
container ID. In addition to the disposition services container ID, MRO transactions
generated based on the customer ordering the entire container will contain a container
issued in full indicator and the count of total of DTID numbers or DTID numbers and
suffix within the container. This allows DLA Disposition Services Field Offices to insure
that an MRO for each item/DTID number or DTID number and suffix associated with a
container is received and processed. Upon shipment of the materiel for each MRO, the
DLA Disposition Services Field Offices will send the DLMS 856S Shipment Status (Type
Transaction Code AS) transaction to the customer, containing the DTID number or
DTID number and suffix, the customer’s original requisition number, and the associated
disposition services container ID.
C16.2.4.1.7. Local Stock Number/Unit of Use. The MRO will carry the
unit of use LSN and the cross-reference NSN. The unit of use indicator will define the
quantity and unit of measure as applicable to unit of use. See C16.6.9. for assignment
and use of LSNs, including unit of use LSNs.
C16-8 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
will enable the field office to identify all associated MROs into a single pick order. The
supplementary address will contain the valid DLA Disposition Services public sales
DoDAAC, along with Signal Code K indicating ship to and bill to supplementary
address. Public sales MROs will contain a DoD Transportation Method Code of X to
indicate customer pick up. Additionally, these MROs will contain the public customer’s
first and last name as exception data, which will be used by field office personnel
responsible for supervising customer removals to verify the correct customer is
removing the property. Once property is removed, the field office will send a DLMS
945A Materiel Release Confirmation transaction, containing the associated ODN and
DTID number or DTID number and suffix, to DLA Disposition Services.
C16.2.4.4. Follow-up for Materiel Release Order Status. The DLMS 940R,
MRO Follow-Up (Transaction Type Code NB) will be used to communicate the follow-up
request for status on open MROs. The DLA Disposition Services Field Office will
provide MRO status using the DLMS 945A, Materiel Release Order Status (Transaction
Type Code NL), as prescribed in DLMS Volume 2, Chapter 4.
C16-9 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
number or DTID number and suffix for the item that is being cancelled. When the
cancellation involves a unit of use LSN, the DLMS 869C will carry the unit of use LSN
and the cross-reference NSN. The unit of use indicator will define the quantity and unit
of measure as applicable to unit of use. See C16.6.9 for assignment and use of LSNs,
including unit of use LSNs. DLA Disposition Services will use the DTID number or DTID
number and suffix as well as the requisition document number and suffix when
applicable, to identify and attempt to cancel the order. If no MRO has been generated,
the DLA Disposition Services can cancel immediately and adjust available inventory
accordingly. If an MRO has been generated to the DLA Disposition Services Field
Office and is open, then DLA Disposition Services will attempt to cancel the MRO.
C16-10 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.2.4.5.3. Customer Requisition Cancellation without Submission of a
DLMS 869C, Customer Cancellation Request (Transaction Type Code AC) or the
Subsequent DLMS 940R, Materiel Release Order Cancellation Request (Transaction
Type Code ND). DLA Disposition Services allows cancellation of submitted requisitions
based upon the customer declining the ordered materiel available for pick up at the DLA
Disposition Services Field Office. In these instances, the DLA Disposition Services
Field Office will notify DLA Disposition Services of the cancellation by providing the
DLMS 945A, Materiel Release Order Cancellation Confirmation (Transaction Type
Code NR), that will contain DLMS Cancellation Reason Code YD (DLA Disposition
Services Customer No-Show), YE (DLA Disposition Services Sales Customer Refused
– Penalty May Apply), YF (DLA Disposition Services Sales Customer Refused – No
Penalty), YG (DLA Disposition Services Sales Reutilization/Transfer/Donation (RTD)
Customer Declined with Prior Notice), YH (DLA Disposition Services RTD Customer
Refused Without Prior Notice), or YI (DLA Disposition Services Commercial Venture
(CV) Rejected by CV Customer), as appropriate. Subsequently, DLA Disposition
Services will communicate requisition status to their RTD Web in order to make the
cancellation visible to the customer.
C16-11 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.2.4.6.1.1 Exception Shipping Addresses
C16-12 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.2.4.7.3. Processing Status. RTD Web will provide processing
status via the DLMS 870S Supply Status transactions for the original customer
document number including any suffix codes assigned by RTD Web.
• U.S. DoD Military Customers, Priority Designator (PD) 1-15 (based upon
Force/Activity Designator (F/AD) and Urgency of Need Designator (UND)).
• Law Enforcement Support Office (LESO), PD 15
• Senior Reserve Officers Training Corps (SROTC), PD 12-15
• National Guard Units, PD 12-15
• Deploying National Guard Units, PD varies based upon DoDAAC and/or F/AD
assignment.
• All Special Programs and walk-ins, PD 15
• Humanitarian Assistance Program (HAP), PD 15
• DoD or Service Museums, PD 15
• Computers for Learning (CFL), PD 15
• Morale, Welfare, Recreation Activities (MWRA), PD 15
• Military Affiliated Radio System (MARS), PD 15
• Civil Air Patrol (CAP), PD 15
• DoD Contractors, PD 15
• Foreign Military Sales (FMS), PD 15
C16-13 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.2.4.8.3. Exceptions to 24-Hour Processing Cycle. The two
exceptions that can alter the 24-hour processing cycle are customer walk-in requisitions
and FMS requisitions.
C16-14 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.2.4.8.3.2.2. It may be necessary to relocate frozen
materiel from one field office to another. When this occurs, DLA Disposition Services
will provide a DLMS 527D PMR to the new location including the freeze indicator and
the FMS Case Number data elements. These will be perpetuated to the DLMS 527R
Receipt.
C16-15 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.2.4.10.1. Materiel Receipt Acknowledgement Required. This
indicator will be applied to requisitions for DLA Disposition Services’ property falling
outside standard MRA requirements under MILSTRAP/DLMS. DoD activities
requisitioning from DLA Disposition Services are required to provide the DLMS 527R
MRA (MILSTRAP legacy DRA functionality) under current procedures. 2
2
DLA Disposition Services must define the expanded requirements for materiel receipt acknowledgment
by DLA Disposition Services’ non-DoD customers, via a future DLMS Change Proposal.
C16-16 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
directed to the DLA Disposition Services, DAAS will reject the requisition back to the
message originator with a clear-text message stating, INVALID FORMAT FOR DLA
DISPOSITION SERVICES REQUISITION.
C16.3.1 Applicability. Refer to this manual’s Definitions and Terms for the
definition of applicable small arms/light weapons (SA/LW).
C16-17 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
(RDO)/Disposal Release Order (DRO) Confirmation will include the serialization data in
the response from DLA Disposition Services Field Offices back to DLA Disposition
Services for verification that the correct weapon was issued.
C16.4.1. General. Sources of supply use the DLMS 940R Disposal Release
Order (DRO) to direct and control issue of supply system stocks on their records to
disposal. Sources of supply will send DROs to the storage site having custody of the
stock and result in the preparation of DD Form 1348-1A (or DD Form 1348-2). If the
item is classified in SCC Q and is being sent to a DLA Disposition Services Field
Offices, the DRO will contain Management Code O (alpha) or S, as appropriate, to
indicate if materiel is hazardous to public health and/or safety and whether mutilation 3 is
required. The retention quantity in the DRO will determine the quantity of materiel to be
turned in to disposal by the storage site. The retention quantity cited in the DRO will be
kept and all remaining stocks transferred to disposal, or, if the quantity on hand is less
than the quantity indicated, the storage site will answer with DLMS 945A Disposal
Release Denial with Status Code BY.
C16.4.1.2. RESERVED
3
Material requiring mutilation may not be consigned to DLA Disposition Services Field Offices unless the
DoD Component of the activity directing the shipment has made prior official arrangements with the DLA
Disposition Services. If mutilation is required, provide specific instructions to the DLA Disposition
Services Field Offices by separate correspondence, citing the DTID number.
4
ADC 1169, DLA Distribution Center Denial Scenarios Associated with Product Quality Deficiency Report
(PQDR) Exhibits
5
DLMS enhancement for future implementation.
C16-18 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Shipment Status provided by the storage activity to the DLA Disposition Services Field
Office will perpetuate the Intransit Control Indicator.
C16.4.3. Release Follow-Up. The source of supply will use a DLMS 940R
Disposal Release Inquiry to follow-up on storage facilities for unconfirmed DROs 10
calendar days after the date the DRO was created. If the DRO has been complied with,
the storage facility will respond with a DRC (see C16.4.2). If the DRO has not been
complied with and shipment is anticipated, the storage facility will send supply status, a
DLMS 945A, with an estimated shipping date. If there is no record of the DRO, the
storage facility will send a status message DLMS 945A with Status Code BF. If the
DRO has been denied, the storage activity will send a DLMS 945A Disposal Release
Denial with Status Code BY.
C16.4.4.1. The storage site will send a DLMS 945A Disposal Release Denial
to the source of supply that prepared the DRO as a notification of no action taken.
Sources of supply will use the DLMS 945A to adjust inventory records.
C16.4.4.2.2. When the DLMS 940R DRO contains the SDR DCN or
PQDR RCN and the SDR DCN or RCN DOES match an RCN on the storage activity
accountable record, but the DCN or RCN in the bin location is not the expected DCN
or RCN for the DRO, the storage activity will prepare a DLMS 945A Disposal Release
Denial.
6
ADC 1169, DLA Distribution Center Denial Scenarios Associated with Product Quality Deficiency Report
(PQDR) Exhibits
C16-19 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
processed by the storage site as a cancellation request if the original request was not
received. If the original request was received and all required actions have been
completed, the storage site will respond to the disposal release cancellation follow-up
by duplicating previously submitted documentation, a DLMS 945A.
C16.4.7. Reporting Excess Quantity. The source of supply will send replies to
excess reports, a DLMS 870M, to notify the reporting activity that the quantity reported
is in excess to source of supply requirements and further action is authorized under
appropriate DoD Component procedures. Refer to Chapter 11 Materiel Returns.
C16-20 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
identified in Appendix 2.8 Reject Advice Codes. Missing the SCC alone should not
result in non-receipt of the materiel but could contribute to increase in-transit tracking
time due to research required by DLA Disposition Services.
C16-21 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Form 1348-2 for receipt, so long as all required information for turn-in is included in the
automated file.
C16.5.2.1. Shipment Status. The DLA Disposition Services Field Offices will
use the DLMS 856S to electronically capture and validate information about inbound
HM/HW property from a customer that is shipping property to a DLA Disposition
Services field office prior to physical receipt. The information contained within the
transaction is used by DLA Disposition Services Field Offices to schedule inbound
shipments and to match the inbound shipment to a Hazardous Waste Profile Sheet
(HWPS). In addition to data requirements for shipment status of non-hazardous
materials, shipment status for HW/HM will add the following: DTID number or DTID
number and suffix number, HWPS number, disposal authority code, disposition services
indicator code, item nomenclature, SCC, special materiel identification code, materiel
management aggregation code, and DEMIL code. This additional information will assist
the DLA Disposition Services Field Offices with the receipt, inspection, and materiel
identification of the HM/HW turn-ins.
7
Refer to ADC 1043/ADC 1043A.
8
Refer to ADC 1043E.
C16-22 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
the DTID contains one or more erroneous data elements, DSS will transmit a DLMS
824R containing the rejected DTID number and reject advice code to the generating
activity. Generating activities will resubmit corrected DTID content in a new DLMS
856S citing the original DTID number. Reject Advice Codes are located in the DLM
4000.25, Volume 2, Appendix 2.8.
C16-23 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Neither the waste streams nor the identification of the waste streams has changed in a
manner that would warrant a change in the data previously provided on these waste
profiles.
Unit of Issue Name Description DoT UoI X12 UoM X12 UoM
(MEA04) (MEA09)
Fiber or Plastic Box, Carton, Case CF BX SD
Metal Box, Carton, Case CM BX SE
Wood Box, Carton, Case CW BX SF
Fiberboard or Plastic Drum, Barrel, Keg DF BR SD
Metal Drum, Barrel, Keg DM BR SE
Wooden Drum, Barrel, Keg DW BR SF
Car HG NC ---
Tank Car TC 1P ---
Cylinder CY CL ---
Tank TP TK ---
Tank Truck TT 19 ---
C16-24 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.5.2.3.1. Safety Data Sheet Hard Copy Requirement. Turn-in
activities will provide a hard copy SDS for hazardous material in the absence of a
Hazardous Material Information Repository System (HMIRS) Number. If there is a valid
SDS in HMIRS, then indicate the SDS five-digit alpha code from the HMIRS on the
DTID (DD Form 1348-1A). This requirement applies to turn-ins of both used and
unused HM, as well as opened or unopened HM. The SDS requirement does not apply
to exclusions listed in 29 CFR 1910.1200(b)(6).
C16-25 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
856S is successfully received by DLA Disposition Services warehousing system,
the system will use the DTID number or DTID number and suffix, and the HWPS
reference number from the 856S to pull the matching HWPS for the shipment to be
receipted. If no electronic records are on file for the DTID number or DTID number with
suffix, and/or the HWPS, the DLA Disposition Services Field Office personnel will be
manually prompted to enter the information into their warehousing system based on the
hard copy documentation accompanying the shipment turn-in. Reject Advice Codes
can be located in the DLM 4000.25, Volume 2, Appendix 2.8.
C16.5.4. DAAS Processing of the DLMS 824R Reject Advice Transaction. If the
turn-in activity is not fully DLMS-compatible and cannot process the DLMS 824R, DAAS
will transmit a DLMS 824R with Reject Advice Code DZ for 824R DTID rejection and HZ
for 824R HWPS rejection to the DLA Disposition Services Field Office. In response to
Reject Advice Codes DZ or HZ, the DLA Disposition Services Field Office will use
alternative methods of communicating with the turn-in activity. 9
C16.6.1. General
9
Refer to ADC 1214
C16-26 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
the ETID application will provide notification to the generating activity responsible for the
property via email.
C16.6.2. Intransit Control System Suspense File. The ETID interface described
above, shipment status transactions, or any receipts processed prior to shipment status
meeting ICS criteria (see C16.6.1.1.), will initiate the ICS suspense file maintained as
part of the DLA Disposition Services Field Office global record. This global record will
be visible and available to all DLA Disposition Services Field Offices as required. At a
minimum, the suspense file will contain the following data shown in Table C16.T4:
C16.6.3. Intransit to DLA Disposition Services Field Office Report. ICS provides a
capability for DLA Disposition Services to furnish management information to
Service/Agency headquarters concerning the transfer of property to DLA Disposition
Services Field Offices. DLA Disposition Services will provide a quarterly Intransit to
DLA Disposition Services Field Office Report upon request. DLA Disposition Services
will provide tailored special extract reports as requested (Appendix 6.33).
10
References to shipment status in this table include both DLMS 856S/MILSTRIP Legacy AS3 and DLMS
856W. Refer to ADC 1131.
C16-27 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.6.4. Intransit Control System Tracking and Associated Actions
C16-28 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
receipt to the ICS there is no matching shipment status transaction and the extended
value is $800 or more, or the item is recorded as pilferable or sensitive, the field office
will forward the 940R Disposal Shipment Confirmation Follow-up transaction with
Advice Code 36 (MILSTRIP DIC AFX functionality. No response is required and this
notification closes the ICS suspense.
C16-29 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.6.4.1.7.4. DLMS 870S Supply Status with Status Code DH.
Receipt of a DLMS 870S Supply Status with Status Code DH indicates shipment is
confirmed and a signed copy of the DTID or a digitally signed email from ETID
confirming disposition services receipt acknowledgement is on file, however the quantity
on the DTID is different than the quantity on the shipment status. Further research on
the quantity discrepancy is being conducted within Service/Agency channels. This will
close the record in ICS for the document number in question. DLA Disposition Services
will keep an accessible history file record for two years. Additionally, the DLA
Disposition Services Field Office will provide a TRA transaction to the DoDAAC
identified by the DTID (inclusive of ETID) when the field office reports the receipt to DLA
Disposition Services.
C16.6.4.1.9.2. Reserved.
C16-30 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
DLMS 870S Supply Status with Status Code DE will be sent in response to the DLMS
940R Disposal Shipment Confirmation Follow-up.
C16-31 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
the turn-in was initiated via ETID, then send the TRA transaction to ETID, which in turn
will generate a digitally signed email to the customer notifying them of the disposition
services receipt acknowledgement in addition to the TRA transaction sent to the
document number DoDAAC. This action provides confirmation to the generator that
DLA Disposition Services processed a Receipt transaction to record DLA Disposition
Services materiel accountability and ownership for the materiel turned in, and provides
a linkage to audit trails retained by the field office. If the DTID (DD Form 1348-1A or DD
Form 1348-2), did not reflect a valid NSN or LSN (excluding scrap [SCC S], waste, non-
appropriated fund activity, and lost, abandoned, or unclaimed privately owned personal
property), the TRA transaction materiel identification (NSN/LSN/MCN) data field will
contain the invalid materiel identification provided on the DTID as the primary materiel
identification (LIN02), and will include the materiel identification (valid NSN or
Disposition Services LSN) that the field office assigned at receipt, as a secondary
reference (LIN16) for an audit trail. The TRA will also include the original DTID number
and suffix, date and time of the receipt, quantity received by the field office, and the
DoDAAC and RIC of the from and to activity. The quantity received may be converted to
unit of use when less than the full quantity associated with the DoD unit of issue.
C16.7.2.1. Maintaining Owner Compliance Table. The field office system will
maintain an owner compliance table to ensure daily (end of day) and annual (total
C16-32 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
reconciliation) requirements are executed based on pre-established business rules in
compliance with DLM 4000.25, DLMS Manual, Chapter 6. (Physical Inventory Control)
C16-33 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.7.2.4 Mismatches. For any mismatches found, the DLA Disposition
Services personnel will ensure that potential or actual inventory accounting adjustments
are researched and corrected in accordance with the value of the adjustment and type
of item involved. Emails will be sent to the appropriate Disposition Services Field Office
personnel requesting assistance to isolate errors in data transmission.
C16-34 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.7.4 Reclassification of Scrap
C16-35 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
via a DLMS 846C, Disposition Status Update (Report Type Code PC), to change the
disposition status of the DTID number or DTID number and suffix to DS (Disposal).
When the field office receives a disposal recommendation, the disposition of the
property at the field office is determined by pre-defined ultimate disposal process
business rules.
C16.7.4.2. Upgrade from Scrap. The upgrade from scrap process is used by
the DLA Disposition Services and its field offices when a business need exists to re-
classify materiel previously receipted as scrap or downgraded to scrap after receipt to a
useable NSN or useable LSN item. An upgrade from scrap can occur at any time
subsequent to the initial receipt of scrap or downgraded materiel. Policy and authority
for upgrading materiel from scrap can be found in DoD 4160.21-M.
C16-36 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
internal type turn-in for the item to be upgraded to in the DLA Disposition Services Field
Office system (US – Useable, HM – Hazardous Material, or HW – Hazardous Waste).
C16.7.5.1. Use of DLMS 940R, DLMS 856S and DLMS 945A When
Relocating Materiel Between Field Offices. In all instances when relocation of materiel
between DLA Disposition Services Field Offices is necessary, the DLA Disposition
Services will direct this action by using the DLMS 940R, Redistribution Order (RDO)
(Transaction Type Code NI), and sending it to the shipping field office, except when the
Disposal Category Code for the DTID number or DTID number and suffix is DS
Disposal. In addition, an RDO may be created by the DLA Disposition Services Field
Office for materiel meeting specific conditions with the intent of transferring the Disposal
Turn-In Document (DTID) from the current Field Office where it was receipted to
C16-37 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
another Field Office (e.g., a Certified DEMIL Center (CDC) for demilitarization. The
RDO transaction prepared by the Field Office is provided to DLA Disposition Services.
The Field Office processing the RDO will always provide a DLMS 856S, Shipment
Status (Transaction Type Code AS) and the DLMS 945A, Redistribution Order
Shipment Confirmation (Transaction Type Code NJ) to DLA Disposition Services upon
shipment.
11
Deferred implementation authorized. Pending implementation, field offices may use RDO cancellation
procedures per paragraph C16.6.5.1.2. in place of an RDO denial. Refer to ADC 1034B.
C16-38 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
suffix or UCN and, when applicable, the disposition services container ID provided in
the PMR to DLA Disposition Services using a DLMS 527R, Receipt, (Transaction Type
Code D4) identified by 2/LIN01/10 Code N, and sequentially assign the Disposition
Services Current Container Count number for each DTID number or DTID number and
Suffix that is in the container. DLA Disposition Services Field Offices must comply with
the Chapter 13 time standards for processing receipts.
C16-39 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
code to EBS upon actual shipment of the redistributed materiel, in addition to sending a
DLMS 856S to the receiving office via DAAS. EBS will update the order status and
DTID quantity to reflect the materiel as shipped, and update the inventory records as
indicated by the DLMS 945A.
C16.7.5.3.3. RESERVED.
C16-40 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
numbers to be associated with the shipment/receipt transaction: (1) the original RDO
document number serving as the primary document number for the new receipt, (2) the
original DTID number or DTID number and suffix from the issuing/losing field office
(secondary reference number), which is perpetuated from the RDO, and (3) the UCN
generated to prevent DTID number or DTID number and suffix re-use. These document
numbers are all linked and all three will be reported on the DLMS 527R Receipt
transaction submitted to DLA Disposition Services.
C16.7.6.1. Public Sales Contracts. Contracts for public sales are maintained
at DLA Disposition Services. The DLMS 832N, Catalog Data Support transaction
(Catalog Purpose Code SC) will be used to communicate sales contract catalog data to
the field offices. This pre-positioned information will be used by the field office to
facilitate the receipt process for turned-in property/DTIDs or DTIDs and suffixes initially
assigned Disposition Category Code SL–Sales. A separate transaction will be used for
each field office, since specific site data and materiel contract information is maintained
at the line item level. A detail line is required for each combination of property, sales
contract, and sales contract line item. Each transaction may contain one or more detail
lines. The following detail level data is included, but not limited to: sales contract
number, sales contract line item number, generic name/description, DLA Disposition
Services Field Office, unit of measure, and the catalog transaction purpose code used
to indicate whether the line item record will be added, changed, or deleted.
C16-41 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Services web auctions, which are required to be accessible to the general public without
any form of user registration. While published web auctions will be viewable by the
general public, users will be restricted from submitting bids until a self-registration
process is completed. The completion of the self-registration process will result in the
creation of a DLA Disposition Services business partner record, enabling the registered
user to submit bids against published web auctions.
C16.7.6.4.2. Materiel Release Order for Public Sale Property. Once the
Defense Finance Accounting Service (DFAS) posts customer payment against the sales
order, then DLMS 940R Materiel Release Orders will be generated by DLA Disposition
Services to the DLA Disposition Services Field Office authorizing release of the
materiel. The MRO transaction will serve as the indicator to DLA Disposition Services
Field Office personnel responsible for managing property removals, that customer
payment was received and removal is permitted. See C16.2.4.1.9. - Materiel Release
Orders in Support of Public Sales.
C16-42 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.7.7.1. Assignment of Disposition Category Code. When property
identified to a DTID number or DTID number and suffix is turned in, it is assigned an
initial disposition category at pre-receipt (i.e., physical examination of property), which is
provided in the DLMS 527R Receipt to DLA Disposition Services (see C16.7.9.). This
disposition category is used to determine how the property is to be processed
subsequent to receipt; (e.g. reutilization, disposal, etc). When the receipt transaction is
received, DLA Disposition Services will confirm that the correct disposition category has
been assigned using property characteristics provided in the DLMS 527R; (e.g. DEMIL
Code, HM/HW indicator, etc.).
C16.7.7.2. DLMS 527R Required Data Elements. The DLMS 527R Receipt
transaction includes the following data elements as applicable to support the disposition
category code assignment process and to subsequently track other disposal processes:
Bill to DoDAAC, DEMIL code, demilitarization integrity code, demilitarization performed
code, disposition services accumulation number, disposition category code, disposition
services container ID, disposition services complete container count, disposition
services current container count, disposition services term sales code, disposition
services indicator (e.g., Abandoned Property (AP) Indicator, Certificate Availability (CA)
Indicator, Controlled Property Branch Verified as Not controlled (CPBV), DEMIL
Instructions (DI) Indicator, HM Indicator, HW Indicator, or HWPS Indicator, Receipt-In-
Place (RIP) Indicator, SA/LW Indicator, Wash Post (WP) Indicator), disposition services
reimbursement code, disposition services UCN, DTID number or DTID number and
suffix, DTID materiel description, hazardous material indicator code, Industrial Plant
Equipment (IPE) report number, SDS Number, model number (used only in conjunction
with IPE Report Number), Sales Contract Number, Sales Contract Line Item Number,
Service LSN, year of manufacturer (used only in conjunction with IPE Report Number).
C16-43 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
by the originating generating customer. .The receipt reversal transaction will be the
last step to the process. See C16.8.1 and C16.8.1.2 for additional information.
12
Refer to ADC 1175.
C16-44 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
parts or equivalent certification are discrepant. DLA Disposition Services will generate
an SDR in accordance with Chapter 17 SDR guidance.
C16-45 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.7.7.7.9. SA/LW – Small Arms and Light Weapons
C16.7.7.8. Delivery Order Term Sales. The field office will identify property
designated for resale under CV delivery order term sales contracts by including the
disposition services term sales code in the receipt transaction. The disposition services
term sales code is based on specific item characteristics. An example is rolling stock
(wheeled items). The delivery order term sales code is a code set maintained by DLA
Disposition Services. An internal DLA Disposition Services table is used to associate
the delivery order term sales code with the applicable CV contract for sourcing materiel
for release to the purchaser.
C16-46 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
RU Reutilization status need to be tracked by an accumulation number. The field office
will use the RU value to trigger the correct processing of the transaction.
C16-47 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
maintained by, DLA Disposition Services. There will not be a property area code
assigned for RIP property. DLA Disposition Services will update the RTD Web with the
warehouse storage location data to facilitate the screening process when the RTD
specialist or customers request visual inspection (prior to requisitioning).
C16-48 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Controlled Property Center) (see C16.7.5.3.2.) or the DLMS 511R (post-post Directed
MRO (DIC C0_)) if the property is issued to a disposal customer (see C16.7.8.5.).
C16-49 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
(MILSTRIP legacy DIC A6A/A6B/A61/A62) citing Denial Management Code W needs to
be sent to DLA Disposition Services to remove the item from the delivery order and
generate a systemic credit for that delivery order. Sales personnel at the DLA
Disposition Services Field Offices will then have the ability to properly close-out a pick
requirement for property that appears on the CV delivery order that does not qualify for
issuing to CV and expedite the denial with a systematic credit to the CV firm.
C16.7.8.3.2.2. RESERVED
C16.7.8.4.1. Use of Internal DLMS 940R MRO. For these issues, the
field office will create an internal DLMS 940R MRO using a unique document number
constructed by using the field office DoDAAC and current ordinal date, followed by a
unique 4-digit serial number, (e.g., SY205411390001, SY205411390002, etc). The field
office will then decrement the owner balance, create and exit the DLMS 511R directed
MRO, position the MRO for release, and once released, generate the DLMS 945A
materiel release confirmation to the owner and DLMS 856S Shipment Status to the
customer. Materiel release confirmations for both scrap and commercial venture
property will use the transportation method code for “Bearer, Walk-Thru (Customer
Pickup of Materiel)” to indicate no physical shipment is involved.
C16.7.8.4.2. DIC for Internal MRO. The DIC cited in the internal DLMS
940R will be A5_, MRO since the property is being shipped or picked up by a customer.
C16-50 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
determine the type of post-post order that should be generated based upon the
disposition category code/disposition sub-category code. Disposition Category Code
DS will indicate a DLA Disposition Services post-post disposal order.
C16.7.8.9. Billing for Materiel. The DLMS 511R transactions for scrap sales
and commercial venture will indicate non-Interfund billing to the contractor (Fund Code
XP) and the customer will be billed prior to removal of the materiel. The DoDAAC of the
commercial or scrap venture firm will be identified as both the ordered-by and ship-to
activity. For DLMS 511R transactions, the Signal Code M indicates there will be no
billing. In addition, the DoDAAC of the disposal customer will be identified as both the
ordered-by and ship-to activity. When a unit of use LSN is being issued, the DLMS
511R will carry both the unit of use LSN and the cross-reference NSN. The unit of use
Indicator defines the quantity and unit of measure applicable to the Unit of Use.
C16-51 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.7.9. Local Stock Numbers (LSN) and Unit of Use.
C16.7.9.1. Local Stock Numbers (LSN) and Unit of Use. There are several
instances that an LSN will be used by the DLA Disposition Services Field Office and
supported activities:
C16.7.9.3. Creation/Update of Unit of Use LSNs. The DLMS 832N will not
be used between DLA Disposition Services and their field offices for creation or update
of unit of use LSNs, rather both will maintain tables which contain agreed upon
conversion factors for what will be the lowest possible assigned unit of measure for
each valid Federal Logistics Information System (FLIS) unit of use. When receipts for
C16-52 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Unit of Use LSN materiel are processed by DLA Disposition Services, internal logic will
link the materiel back to the NSN.
C16.8.1. Outgoing SDR. During the receiving process, if the DLA Disposition
Services Field Office identifies a supply discrepancy, an SDR will be generated via the
field office system using using DLMS 842A/W transaction to the generating customer
using Discrepancy Report Document Type Code D in conjunction with the appropriate
SDR Disposition Services sub type code to distinguish the source of discrepant
shipment (generating activity turn-In = T, DLA Distribution Center = B, and
Redistribution between field offices = E, SDR Requested Action Type 3C.). Once the
originating generator picks the non-accepted property, DLA Disposition Services will
update the original SDR (Disposition Services SDR Sub Type Code T) with SDR
Requested Action Code 3B. DLA Disposition Services Field Site will also annotate in
the remarks section of the SDR the date the materiel was picked up by the generator.
Using the SDR Requested Action Code 3B will close out the original SDR created with
SDR Requested Action Code 3C. Failure of DLA Disposition Services to send the SDR
Action Codes in this order will result in SDRs that remain open, adversely impacting
metrics and possibly resulting in an audit.
C16.8.1.2. Action Codes. The DLA Disposition Services Field Office will
indicate the applicable action taken or requested on the SDR. When an activity turns in
property that cannot be accepted by the field office, the field office will prepare an SDR
using SDR Requested Action Code 3C, indicating receiving activity not authorized to
accept property (pick-up by original owner required) (Disposition Services use only).
Once the originator picks the non-accepted property, DLA Disposition Services will
update the original SDR with SDR Requested Action Code 3B (Discrepancy reported for
C16-53 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
corrective action and trend analysis. No reply required). DLA Disposition Services
Field Office will also annotate in the remarks section of the SDR the date the materiel
was picked up by the originator. Using the SDR Requested Action Code of 3B will close
out the original SDR created with Action Code 3C.
C16.8.2. SDRs Prepared via DoD Web SDR. DLA Disposition Services personnel
will receive and process discrepancies for property shipped by the DLA Distribution
Centers to various customers. DLA Disposition Services personnel will log in to
WebSDR to create and submit SDRs on behalf of the customer using Document Type
Code 7 and the related DLA Disposition Services SDR type code to distinguish
customer type, as follows:
C16-54 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C16.8.3. Incoming Customer SDRs. SDRs addressed to DLA Disposition
Services (RIC S9D) will be supported by conversion to email via DoD WebSDR. SDRs
will be processed in accordance with paragraph C16.8.2. The generic email address for
S9D will be associated with all the DLA Disposition Services Field Offices for Document
Type 7 SDR only, allowing customer generated SDRs to be forwarded to DLA
Disposition Services. Replies will be created in DoD WebSDR. Incoming Customer
SDRs will not be sent to the DLA Disposition Services ICP system.
C16.8.4.2. SDRs with Type Code T. SDRs citing DLA Disposition Services
SDR Type Code T will be sent directly to the activity responsible for the turn-in of
property whenever possible. In order to ensure electronic notification to the generating
activity, DLA Disposition Services will provide the generator’s email address to DoD
WebSDR. This email address will be used by WebSDR for dissemination of the SDR.
C16.8.4.3. SDRs Citing the DLA Disposition Services SDR Type Code B or
E. SDRs with Type Code = B or E will be directed to the shipping activity and no
information copies required.
C16-55 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
laws, and regulations. As appropriate based upon the security and classification
requirements of specific property, DLA Disposition Services may contact the generator
in advance of the 55 day SDR time standard (which is consistent with all host nation,
Federal, State, and local laws and regulations including DoD disposal policies).
C16-56 CHAPTER 16
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17. CHAPTER 17
SUPPLY DISCREPANCY REPORTING1
C17.1 GENERAL
C17.1.1. Purpose.
C17.1.2. Component SDR Systems. The intent of the SDR program is to support
reporting of discrepancies identified during receipt processing without requiring separate
action by receiving or support personnel to manually re-enter receipt information for the
creation of the SDR in a separate, stand-alone SDR system. To facilitate the
preparation of complete and accurate SDRs, Components must design supply systems
to report supply discrepancies as an integral and seamless part of the receiving
process.
C17.1.3. Standard SDR Transactions. Under DLMS, the SDR will be considered
a common logistics information exchange to be integrated with transaction processing
through DAAS. The DoD approved standard for electronic transmission of SDR
transactions is prescribed by the DLMS Implementation Convention (IC) using an ASC
X12-compliant variable-length transaction format. Multiple DLMS ICs are provided to
support different SDR related functions. The DLMS 842A/W, Standard SDR, will be
employed for transactional exchange of initial reports and associated follow-on actions.
The DLMS 842A/R, DoD SDR Reply, will be employed for transactional exchange of the
SDR reply by the action point. The DLMS ICs for SDRs are available via the
Implementation Convention/DLMS IC page of the Defense Enterprise Data Standards
Office (DEDSO) Management Standards Website.
1
Chapter 17 supersedes and replaces Joint Publication DLAI 4140.55/AR 735-11-2/SECNAVINST
4355.18A/AFJMAN 23-215, Reporting of Supply Discrepancies, August 6, 2001.
C17-1 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.1.4. DoD WebSDR. The DoD WebSDR supports DLMS implementation via a
DAAS-maintained application, that enables SDR transaction exchange; provides a web-
based entry method to assist users who are not supported by a Component DLMS-
compliant SDR application; and provides visibility of SDRs for research and trend
analysis via management report/query capability. The term “DoD WebSDR” (or
“WebSDR”) refers to both the overall business process and supporting automation,
including both direct web input and transaction exchange.
C17.1.4.1. The DoD WebSDR application automates the Standard Form (SF)
364 SDR paper form facilitating the DoD standard transactional exchange described
above. It brings the SDR into an integrated transactional environment, supporting both
direct input (under Component business rules) and transaction exchange originating
within Component applications. The WebSDR system facilitates communication and
interoperability between U.S. Military and Federal Agencies and the International
Logistics Control Office (ILCO) on behalf of the Security Assistance customer. It
controls routing of web submissions and logistics transactions according to business
rules. It supports information exchange between the customer, the Inventory Control
Point (ICP)/Integrated Material Manager (IMM), the shipper, and other interested
parties. It encompasses new report submission, correction/modification, cancellation,
follow-up, requests for reconsideration, and SDR replies (including interim responses,
additional information requests, and resolution responses), in addition to the capture of
report and response management statistics.
C17.1.4.3. The DoD WebSDR process reduces manual SDR form creation
and eliminates dual entry where multiple Component systems are used. The DoD
requirement is that paper submission of SDRs and non-DLMS compliant SDR
applications will be phased out with migration to DLMS. By exception, until electronic
reporting under DLMS is universally available, SDRs and associated responses may be
reported via hard-copy SF 364, e-mail, through customer service help lines (e.g. the
DLA Customer Interaction Center, [email protected]) 1-877-352-2255
(1- 877- DLA-CALL)), or any other manner acceptable to the submitter and recipient.
All manner of reporting must meet the criteria described in this publication.
C17.1.4.4. Access for DoD WebSDR input and management reports requires
submission of a System Access Request (SAR) available from the DAAS home page.
DoD WebSDR training is available on the Defense Enterprise Data Standards Office
Website.
C17-2 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.1.4.5. DoD Components with an established interface with DoD
WebSDR will designate primary and alternate representatives for the Component SDR
application to DAAS. These representatives will be notified via e-mail when
transactions fail during WebSDR processing due to failure to meet minimum
format/content requirements for processing. Components will provide name, telephone,
and e-mail address to the DoD SDR System Administrator and DAAS WebSDR
Program Manager.
C17.1.7. Exclusions. The following types of discrepancies are excluded from the
provisions of this publication:
C17-3 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.1.7.5. Product quality deficiencies to the extent covered by Joint DLAR
4155.24 /AR 702-7/SECNAVINST 4855.5B/ AFR 74-6l, except as specifically permitted
under Security Assistance procedures in this chapter.
C17-4 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
manufacturing, and workmanship. These are reportable on an SDR only by a Security
Assistance customer. All others follow PQDR policy found in DLAR 4155.24/AR 702-
7/SECNAVINST 4855.5B, AFR 74-6 Product Quality Deficiency Report Program.
Quality deficiencies reported via SDR will be investigated within the ICP/IMM under
procedures associated with Product Quality Deficiency Reports. PQDR resolution
provided via SDR reply to the submitting ILCO will identify the associated PQDR record
control number (RCN) as a cross-reference to the PQDR identification used by the
ICP/IMM.
C17.2. POLICY
C17.2.1. Use of SDR. The DoD Components will use the SDR to report shipping
or packaging discrepancies attributable to the responsibility of the shipper (including
contractors/manufacturers or vendors) and to provide appropriate responses. The
purposes of this exchange are to determine the cause of such discrepancies, effect
corrective action, and prevent recurrence.
C17-5 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
further directed encryption of all SDR e-mail transmissions. This requirement has been
levied on the DoD WebSDR and impacts all participating DoD Components.
C17.2.2.2. All action activities using e-mail SDRs must register their
certificate, so that all information is available for SDR resolution. For low volume
customers relying on e-mail SDRs, especially those supported by third party direct
WebSDR input, registration is encouraged, but not required. These users will receive
an abridged SDR reply that will provide disposition instructions and financial action,
without the accompanying shipment detail.
C17.2.2.4. SDR management reports will be distributed only via e-mail if the
corresponding certificate has been signed.
C17-6 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.2.5. Responsible action activities as identified in this chapter will use SDRs
to:
C17.2.5.1. Notify the report initiator of interim status or resolution of the SDR.
C17.2.7.1. IMMs will use the SDR response to establish a due-in record for
return of discrepant materiel under Chapter 12 of this volume. ICPs/IMMs will use the
prepositioned materiel receipt (PMR) to advise storage activities to which a return is
directed using MILSTRAP procedures for the DLMS 527D, Due-In/Advance
Receipt/Due Verification. Refer to paragraph C11.19. of this volume, for additional
guidance.
C17-7 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
restricted by the appropriate advice code in the customer requisition. Such adjustments
resulting in quantity variance are not reportable as discrepant.
C17.3. PROCEDURES
C17-8 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
activity, including mandatory clarifying remarks to supplement discrepancy codes, so
that they can take timely action to correct the problem and provide a timely response
and disposition to the customer.
C17.3.1.3.1. The SDR originator must indicate what action has been
taken concerning the discrepant materiel and/or the desired response from the
responsible action activity. Identify the action code using the SDR Requested Action
3
Use the legacy PIIN pending transition to the PIID. When using the PIIN, include the four-position
call/order number. Refer to ADC 1161A.
C17-9 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Code (Appendix 7.28). Within the context of SDR processing, this data element is
known as the Action Code. If no code exists to adequately describe the action taken or
requested disposition, select Code 1Z and use a clear-text description.
C17-10 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.2.3. Condition of Materiel
C17.3.2.3.3. Missing Part. Report materiel received for repair that has
been cannibalized of nonexpendable parts or components (including cannibalization of
nonexpendable basic issue item (BII) or nonexpendable supply system responsibility
item (SSRI) without the authorization of the inventory manager when the total value of
the missing item(s) is in excess of $100). Expendable BII and SSRI are not subject to
these procedures.
C17.3.2.3.4. Expired Shelf Life. Report receipt of materiel for which the
shelf life either has expired (Type I non-extendible item) or the inspect/test date has
lapsed (Type II extendible item), regardless of dollar value. Use the hazardous materiel
discrepancy code when applicable.
4
Refer to ADC 1198.
C17-11 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
process only applies to demilitarization (DEMIL) Code A materiel. The storage activity
will generate an information only SDR (Action Code 3B) to the owner.
C17-12 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
when controlled inventory items are received on previously canceled requisitions
regardless of dollar value.
C17-13 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
A constructed document number must be provided when the original number is not
known. Use the reporting activity’s DoDAAC as the basis for constructing the document
number, citing Code U in the first position of the constructed document number serial
number (DLMS Utilization Code U).
C17-14 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.2.6.6.2. Security Assistance customers reporting non-receipt
are required to provide documentation from the freight forwarder indicating that no
materiel has been received on the requisition and transportation control numbers that
apply. The ILCO will deny and return as incomplete any SDRs that do not have the
documentation attached.
C17-15 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.2.8. Packaging Discrepancies
C17-16 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
cost to correct the discrepant packaging is less than $300, the DLA Distribution Center
may perform the corrective action without authorization based upon prior agreement
regardless of whether a PMR was provided. The SDR will be provided to the owner for
information only.
C17-17 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
repackaging or disposal on the initial SDR submission, in the remarks section and
complete the appropriate data element entries for electronic submission.
C17-18 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
specification, preservation, or packaging method. Reports relative to packaging
discrepancies found in storage will be annotated "not incident to shipment.”
C17-19 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.2.11.2. Incorrect item discrepancies discovered while opening a
sealed vendor pack will be reported regardless of dollar value or shipper. These reports
must contain the PIID from the packaging and, if available, the lot number and the
original document number. A constructed document number will be provided when the
original number is not known. Use the reporting activity’s DoDAAC as the basis for
constructing the document number, citing Code U in the first position of the constructed
document number serial number (DLMS Utilization Code U). Include identity of the
incorrect item received in the discrepancy report.
C17-20 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
from a DLA Distribution Center will be submitted as type 8 SDRs. Only the current
action activity can update the owner, manager, or source of supply field. Submitters
must cancel and resubmit their SDR if they need to update this field. When a storage
activity receives a shipment based upon a redistribution order and the materiel is short,
over, wrong, quality deficient, or otherwise discrepant the receiving activity will:
C17-21 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
regardless of condition when the dollar value is equal to or greater than $100 per line-
item. Discrepancies pertaining to controlled inventory items will be reported by SDR
regardless of dollar value or condition.
C17.3.4.3. Exception for Returns Between U.S. Activities. When the materiel
return shipments are classified as unserviceable and uneconomically reparable upon
receipt, the receiving activity will report to the shipping activity. The report will include
materiel return document number, quantity, and an explanation of condition
classification.
7
Refer to ADC 110/1102A.
8
Refer to ADC 1268.
C17-22 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.4.4. Reimbursable Costs for Discrepant/Unauthorized Returns. Under
MILSBILLS and MILSTRIP procedures DoD activities returning materiel in violation of
prescribed procedures may be held accountable for recoupment of all reimbursable
costs including disposal. Recoupment action may be initiated by the DLA Distribution
or, upon subsequent identification of the applicable manager, by the manager.
C17.3.5.1. All SDRs submitted for DLA directed LROs where the item is
managed by DLA, owned by Army’s Non-Army Managed Items (NAMI) Group, Supply
Directorate (Routing Identifier Code (RIC) AJ2), and shipped from an Army CONUS
site, must be sent to NAMI for investigation, with an information copy to DLA (RIC
SMS). This is normally accomplished via exception routing rules within DoD WebSDR.
SDRs meeting these criteria will be assigned Document Type V. Any SDRs received
directly by DLA will be forwarded to NAMI (RIC AJ2) via SDR forwarding reply citing
Reply Code 504. NAMI will research the discrepancy and forward recommended
disposition to DLA for final action. The NAMI action activity will provide recommended
disposition to DLA within 25 calendar days using an SDR forwarding reply citing Reply
Code 307. After 25 calendar days have elapsed and NAMI recommended resolution
has not been received, DLA will follow-up for recommended disposition.
C17-23 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
with other identified discrepancies. The distribution center will identify the SDR as
informational or otherwise indicate requested action. If the distribution center
erroneously reported the receipt to the wrong owner due to missing/unmatched PMR,
the wrong owner will use the SDR reply process to reject the SDR (using Reply Codes
901). If the wrong owner is unable to reject the receipt transaction systemically, the
wrong owner will also request that the distribution center reverse the receipt (using
Reply Codes 612). If known, the wrong owner should identify the correct owner in the
receipt rejection or SDR reply to facilitate reprocessing of the receipt. These procedures
do not authorize rejection/reversal of receipts reported to the owner designated by PMR
or the pre-designated Service owner for unauthorized return of consumable items. 9
C17.3.6.2. If other than new procurement, the SDR should show receipt in
SCC K when the actual condition cannot be determined. Materiel returned with other
identified discrepancies, (e.g., without associated technical data), will also be reported
as indicated under the appropriate discrepancy category. Returns of excess materiel
that are not ICP/IMM directed are subject to recoupment of costs associated with
disposal or repackaging costs incurred by the distribution Center. If the receiving
activity identifies no other discrepancies requiring disposition instructions and is able to
process the receipt to the owner the SDR will cite Action Code 3B for corrective action
and trend analysis. The distribution center will direct the action copy of the SDR to the
owner or manager and a distribution copy to the returning activity (based on the
DoDAAC in the document number or shipping documentation.)
C17.3.7.1. Dollar Value Greater Than $100. Receiving activities will submit
an SDR for discrepancies specified above in shipments to and from DLA Disposition
Services Field Offices when the dollar value is greater than $100 per line item.
C17.3.7.3. DLA Disposition Services and DLA Disposition Field Office SDR
Procedures. During the receiving process, if the DLA Disposition Services Field Office
9
Refer to ADC 1273.
C17-24 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
identifies a supply discrepancy, an outgoing SDR will be generated consistent with
Chapter 16.
C17.3.8.1. Serial numbers are mandatory for all serially managed items to
include capital equipment and UIT Programs. Report supply-related discrepancies
involving IUID under DoD IUID Supply policy. Pending full transition to DoD IUID
Supply policy using the UII, SDRs identifying discrepancies in unique identification will
be prepared citing both UII and/or corresponding serial number, when both are
available. Until UII is implemented as the primary identifier under full IUID
implementation across the Department of Defense, the human readable serial number
is mandatory in the SDR for discrepancy scenarios identified in this chapter, as is the
UII when available. The intent is to capture both serial number and UII, however not all
items are marked and the UII cannot be considered a mandatory element at this time.
That is the context in which the term “serial number/UII” is used in this chapter. 11
Applicability under DoD IUID Supply Policy is identified by NSNs with IUID Indicator Yes
(Y). For missing or mismatched unique item identification of items that are DoD serially-
managed/tracked, use the applicable U-series discrepancy code (see Table C17.T1.).
Report missing or mismatched materiel identification unrelated to IUID (e.g. missing or
mismatched part number or NSN) using the applicable packaging (labeling/marking),
documentation, technical data, or wrong item discrepancy code(s). Report quality-
related deficiencies involving IUID, (e.g., improperly constructed unique item identifier
within the 2D data matrix), using Product Quality Deficiency Report (PQDR) procedures
under DLA Regulation 4155.24, et al.
10
Refer to ADC 1030.
11
Refer to ADC 1244.
12
Discrete data entries (rather than attachment files) for serial number/UII identification are required
under ADC 1244 beginning December 2018.
C17-25 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
procurement materiel requiring IUID or serial number tracking in a suspended condition
pending resolution.
C17-26 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.8.7. Discrepancies involving missing/illegible serial number
markings must be reported at time of receipt via SDR. A data plate is required for all
serially managed items destined to remain in the supply chain. Temporary tags are
authorized for items intended for disposal or maintenance. The materiel owner is
responsible for permanently embedding data plates when required due to the type of
item (e.g., small arms/light weapons).
C17.3.8.7.1.6.1. Reserved
C17-27 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.8.7.1.6.2. Reserved
C17.3.8.11. SDRs prepared for receipt of an incorrect item where the item
received is identified by an NSN with a IUID Indicator Y will include the serial
number/UII for the wrong item. Cite the applicable discrepancy code for the incorrect
item receipt and the IUID discrepancy code
C17-28 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Table C17.T1. SDR Decision Matrix: Discrepant IUID Data
(For SDRs, serially managed capital equipment and UIT items follow the same guidance)
Procurement Approved Wrong Missing Mismatch Mismatch Create SDR
Source UIT Item IUID (item IUID with IUID no SDR Action
(IUID Received or shortage/ shortage/ Code 13
contractually w/IUID packaging) overage overage
required) Indicator
Y
Y Y/N N N Y N Y 1A or 2A
Y Y/N N N N Y Y 1A
Y Y/N N Y N N Y 1A
Y Y/N N N N Y Y 1A
Y Y/N N Y N N Y 1A
Y/N Y/N Y Y/N Y/N Y/N Y 1A or 2A
N N N N N Y Y 3B
N N N N Y N Y 1A or 2A
N N N Y N N N No SDR
N Y N N N Y Y 1A
N Y N N Y N Y 1A or 2A
N Y N Y N N Y 1A
N N N N N Y Y 1A
N N N N Y N Y 1A
N N N Y N N Y 1A
13
SDR Action Codes are selected by the submitter based upon the desired response to the SDR. Codes
identified in Table C17.T1 are:
1A Disposition instructions for discrepant materiel requested; financial action not applicable.
2A Disposition of materiel and financial adjustment (credit) requested.
3B Discrepancy reported for corrective action and trend analysis; no reply required.
14
Refer to ADC 1244
C17-29 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.9. Transshipper Prepared SDRs. CCPs will prepare an SDR to report packaging
discrepancies as described below.
C17.3.9.2. CCP SDRs for Non-Compliant WPM. CCPs will notify ICPs that
their OCONUS WPM shipment is not in compliance with DoD 4140.65-M, “Compliance
For Defense Packaging: Phytosanitary Requirements for Wood Packaging Material
15
Refer to ADC 317A. Note: Discrepancy Code H6, Shipper’s Declaration for Dangerous Goods is re-
assigned to the D series code list in DLMS Volume 2, Appendix 7.28.
C17-30 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
(WPM),” and ISPM 15 requirements. The expiration of the DoD Pest Free mark and the
requirement to use the International Plant Protection Convention (IPPC) stamp to
indicate WPM compliance brings the requirement to remediate all noncompliant WPM
destined for OCONUS. WPM shipments can be remediated by repackaging or by use
of a heat chamber. SDRs will be prepared for noncompliant shipments received by the
CCPs. Noncompliant shipments will not be held for disposition. Shipments on
noncompliant pallets will immediately be re-palletized onto compliant wood pallets.
Boxes, crates, etc. will be sent to a remediation area through use of DSS packing,
packaging, preservation & marking (PPP&M) process, and placed in a Hold Status W
until remediation is completed. SDRs will be generated for both pallet replacements
and box/crate rebuilds. The SDR will normally cite SDR Action Code 3B, Discrepancy
Reported for Corrective Action and Trend Analysis. No reply is required. This type of
SDR does not require a response from the source of supply or other designated activity;
but is provided so that the source of supply may take appropriate action with the
Component shipper or vendor and track trends and associated repackaging costs. The
SDR will be auto-closed in the DSS, based on the P215 discrepancy code (indicating
noncompliant WPM), and will not be reopened. The point of contact (POC) may be
contacted if SDR was sent to the wrong supply source. Labor and material to remediate
will be charged to a CCP Cost Code. If a frustrated shipment requires an expedited
SDR reply to the CCP, use of Action Code 3A, Transshipper (Aerial/Water port or CCP)
Requests Expedited Response; Shipment Frustrated, is authorized.
C17.3.9.4. Expected Data Content for Transshipper SDRs. These SDRs will
be identified by Discrepancy Document Type Code W and will include the number and
type of discrepant pieces. The transportation control number (TCN) will be the primary
reference number for operational processes. If the shipment is received at the CCP
without a TCN, one will be assigned in accordance with the DTR. SDRs prepared at the
shipment level may include multiple items, or there may not be due-in or documentation
available. Because a document number is mandatory within DoD WebSDR, the CCP or
other transshipment activity may need to generate a document number based upon the
submitter’s DoDAAC if multiple documents are included or the original document
number is unavailable. Action activities will not reject Transshipper SDRs for
unmatched document numbers without researching by TCN and other identifying
shipment information. Multiple document numbers, when available, will be recorded in
the SDR remarks. Materiel identification may be identified as “UNKNOWN” or “MIXED”
(multi-pack or other consolidation of different items). When this occurs, quantity and U/I
C17-31 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
will be left blank. Identification of hazardous materiel shipments is mandatory using the
hazardous materiel indictor (Yes/No). When possible, the shipper will be perpetuated
from the due-in notification (e.g. DLMS (US TRANSCOM-maintained) 856A) or shipping
documentation. The owner/manager (source of supply) will be identified as the
ICP/IMM that directed the shipment when applicable.
C17.3.10. SDR Distribution. This section addresses those organizations that must
be identified on the SDR as initial action recipient or as receiver of information copies.
Such determination is based upon the type or origin of the shipment involved, the DoD
Component that directed shipment, and the type of discrepancy. Applicable action
activities include ICP, ILCOs, DLA CCPs, and DLA Distribution Centers. For items
requiring special handling and/or reporting, such as controlled inventory items, the
responsible action activity must ensure additional distribution of the report as required.
The submitter will provide a copy of the Serious Incident Report, or other Component-
required report, regarding controlled inventory items believed to be stolen, lost, or
unaccounted for. Do not mail hard copy documents when access to an electronic SDR
application and associated supply information is available. Where electronic attachment
capability is not available, users should supplement their original SDR submission via
WebSDR correction process attachment functionality to upload information not readily
available to the action activity and photographic/pictorial evidence of the discrepancy.
16
Refer to ADC 1102, implementation delayed.
C17-32 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
correction of inventory records where applicable; DLA Distribution Centers are not
authorized to respond to the submitter via SDR reply. Army users are advised not to
submit SDRs to single stock fund (SSF) site RICs or to Army shipping depot RICs via
DoD WebSDR. There are currently no WebSDR interfaces to support SSF sites or
Army shipping depots. The Army action activity can be determined from the shipping
documentation (e.g., the RIC in record position 67-69 of the DD 1348-1A), or as part of
a NIIN/NSN or Part Number search in WebFLIS. Note that the FLIS source of supply
will not apply if the requisition was filled by AJ2, Non-Army Manager Item (NAMI) source
of supply. Services ammunition users may send SDRs to B14 for ammunition
commodity discrepancies or directly to those Army ammunition storage depots listed
below.
17
Refer to ADC 1241.
C17-33 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.10.2.1.2.2.2. The CCP will reply to the
customer with status of the shipment if no further action is needed. WebSDR will
provide a copy of the SDR to the source of supply. If the CCP cannot provide status or
if POD is not available, the CCP will annotate the SDR reply to the submitter with this
information and forward to the source of supply for further research using the
appropriate 300-series forwarding reply code.
• repetitive discrepancies,
• cases of dispute that cannot be resolved between the ordering office and the
supplier, or
C17-34 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
• product quality deficient materiel in Security Assistance shipments where
GSA has provided inspection at source.
18
Refer to ADC 1052.
C17-35 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.10.4.3. Partial Weapon Turn-in. 19 When SA/LW materiel is
received, DLA Disposition Services DEMIL Center, Anniston, Alabama must identify the
SA/LW by a valid NSN or DoD SA/LW Registry assigned management control number
(MCN), in addition to a separate serial number for each individual weapon.
19
Refer to ADC 1175.
C17-36 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.10.6. Local Purchase. Follow DoD Component guidance. A copy will
be furnished the Government inspector when inspection is at origin. DoD WebSDR
does not support SDRs applicable to local purchase discrepancies.
C17.3.10.7. Industrial Plant Equipment Shipments. DLA, will review all SDRs
from the initiator, make further distribution as necessary, request appropriate action
from the consignor, and provide the initiator with replies from the consignor and other
closeout action.
20
Refer to ADC 1268.
21
Refer to ADC 1052.
C17-37 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.10.8.2.2. Information copy to be provided systemically by
DoD WebSDR per Component guidance. SDRs for Air Force ICP directed shipments
will be provided to the designated Air Force ICP packaging monitor.
C17.3.10.10. The Exchange (formerly Army and Air Force Exchange Service
(AAFES)). SDRs may be routed to the Exchange via DoD WebSDR to the source of
supply RIC.
6, 8, 9, R, A, N, P, 56 30 31 3
V
7 31 30 31 3
C17-38 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
time standards specified in this chapter, the submitting activity must provide an SDR
follow-up. Follow-ups must be directed to the last identified action activity when the
original SDR was forwarded by the original recipient. Cite the SDR report number of the
original report. For transactional exchange, include the WebSDR-assigned control
number when known. Follow-up transactions should include all data that was in the
previous SDR submission. POC information for the follow-up and the follow-up date are
required. A narrative entry is required to provide clarification for the follow-up. The
submitter or DoD WebSDR must forward the follow-up to the current action activity
when SDR history indicates a or updated action activity has been identified (such as
based upon prior Reply Code 504 or a 300-series reply code).
C17-39 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
turn-in activity. DLA Disposition Services will contact the Army Logistics Data Analysis
Center (LDAC) for resolution/disposition instructions or referral to the owning Service as
necessary in order to identify the turn-in activity or alternate recipient. Subsequently,
LDAC may contact others to include item managers as deemed necessary to provide
resolution. Upon resolution of the SDR or when the SDR resulted in the return of the
shipment, DLA Disposition Services will update the Action Code from 3C, to 3B and
update the remarks appropriately to ensure the SDR is closed out.
C17.3.12.1. Procedures
22
Refer to ADC 1066.
C17-40 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.12.1.2.1. Action activities may provide multiple
dispositions when appropriate and provide disposition instructions for each reply
code in the remarks field citing the reply code with the associated disposition.
The responder will have to reference the reply code and specify the quantity to
the corresponding disposition instructions in the remarks field in long text.
23
Refer to ADC 1181A.
24
Refer to Approved DLMS Change 317B, Action Activity Replies to Transshipper-Prepared SDRs
C17-41 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.12.1.2.6. New Procurement SDRs. The action activity must
complete shipment information applicable to DVD, new procurement, etc., where
incomplete or inaccurate on the original report. This includes identification of the vendor
(by CAGE), PIID, and identifying shipment numbers. When procurement information is
populated by EDA interface, it will not be overridden by subsequent entries. The
submitting activity must ensure that DVD shipments are identified by Document Type
Code 6. When the customer incorrectly routes a Document Type 6 (DVD) SDR to a
DLA Distribution Center, they will reject it using Reply Code 901 Transaction rejected:
Discrepancy report submitted to wrong activity. Resubmit to the correct action activity
(identified in remarks when known).
C17-42 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
to provide the final response. The final response may differ from that provided on the
interim response.
25
Refer to ADC 1044A Clarification of Business Rules associated with SDR Replies for Status Update
and Completion Notification.
C17-43 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
update may also be used to send research findings/ recommendations to the ICP/IMM
(Army directed shipments only).
C17-44 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
with the action activity that final action has been taken on an SDR requiring a materiel
disposition action. The SDR system receiving the Completion Notification may close
the SDR as well or keep it open for additional actions. Submission of a Completion
Notification is required for all SDRs prepared by the submitter, with the exception of
those clearly identified as being provided for information only and requiring no action
activity reply (SDR Action Codes 1H or 3B only). Action Code 1H or 3B SDRs will
automatically be placed into a closed status in WebSDR metrics. The completion notice
may not be used to modify originally reported SDR data elements. The following sub-
paragraphs provide more detailed information regarding Completion Notification
processing.
C17-45 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.12.1.2.11.6. The storage activity will use a completion
notification to inform the action activity that materiel disposition could not be completed
due to zero balance at storage location using Reply Code 412 and clarifying remarks.
The ICP may close the SDR due to the materiel no longer being available. If the SDR is
a Document Type 9, the ICP must take further action to locate the new procurement
materiel.
C17-46 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.12.1.3.4. Fulfill customer requests for expedited or
replacement shipment (e.g., due to shortage, non-receipt, wrong item, or comparable
discrepancy) when feasible and assets are available. 28
28
Refer to ADC 1091, SDRs Requesting Expedited or Replacement Shipment.
C17-47 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
customer’s location, it is not feasible for all situations. When the materiel is already
located in a DLA Distribution Center and no physical shipment is required to return the
materiel to the original owner/manager, the current owner must not reuse (or suffix) the
original document number for the Prepositioned Materiel Receipt (PMR) and Materiel
Release Order (MRO) directing the return. The responsible action activity must assign
an alternative document number when materiel is located in a DLA Distribution Center
and the current owner must use a ship-in-place materiel release order to direct the
return. Additionally, submitters must use the reconsideration request to ask for an
alternative document number due to system constraints prohibiting reuse of the original
shipment document number. When using a new document number for the directed
return of discrepant/deficient materiel, the owner/manager and the returning activity
must retain an audit trail linking the old and new document number/suffix (both
document numbers will be included in the PMR, Materiel Returns Shipment Status, and
Receipt transactions). The SDR reply will include the date by which the customer is
requested to return the materiel to the designated location. The ICP will require
expedited return where appropriate, such as FMS classified/sensitive item returns, and
overage returns for back-ordered materiel not available within another customer’s
required delivery date. Identify the return-to location by DoDAAC or CAGE (use for
contractors when no DoDAAC is assigned). Clear text addresses may be included in
addition to the DoDAAC and must be included in the SDR Reply remarks text for returns
directed to the contractor identified by a CAGE only. 29 The source of supply will
provide reimbursement for packing, crating, handling, and transportation for directed
returns under MILSBILLS procedures in DLM 4000.25, Volume 4, Finance, procedures.
Use of the Defense Transportation System (DTS) for the return movement is
encouraged except where use of a designated commercial carrier is more cost
effective/efficient or transportation cost will be borne by another party (e.g., a vendor for
return of nonconforming materiel). As an alternative to providing transportation
reimbursement, the responsible action activity may provide the transportation account
code (TAC) chargeable for the transportation services or direct use of a commercial
carrier by providing the paying activity’s carriers account number or a pre-paid return
shipping label. In those cases where an exhibit of the discrepant materiel is directed for
return, the activity requesting this action will pay for exhibit shipment costs. Action
activities will either furnish DD Form 1348-1A for materiel to be returned or provide
comparable information to accomplish the return. A copy of the SDR and the shipment
document will be included with returned materiel and annotated as an “SDR RETURN.”
When discrepant materiel is directed for return to a contractor, a hard-copy SDR
including disposition instructions will be included with the shipment. No statement
adversely affecting the Government's claim will be shown on any documentation
returned to the contractor. For non-Security Assistance customers, materiel not
returned as directed within 90 calendar days (if CONUS) or 120 days (if OCONUS) of
the SDR reply will be billed.
29
Include return-to location, suspense date, return document number/suffix, and (when applicable) carrier
tracking number in the SDR Reply remarks text pending full implementation of discrete transaction data
fields. Refer to ADC 1249.
C17-48 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.12.1.4.2. DLA Distribution Center Returns and Transfers to
DLA Disposition Services. SDR disposition instructions to DLA disposition centers may
direct disposal or shipment of discrepant/deficient materiel to another location (e.g.,
return to a vendor) using the appropriate SDR reply code. This type of SDR disposition
must be provided concurrent to transmission of the DLMS 940R Materiel Release
Order, which includes the option to add the corresponding distribution center
number (DCN), in accordance with MILSTRIP procedures in DLM 4000.25 Volume 2
for clear audit history for inventory reporting. The DLMS MRO supports discrete
identification of the carrier and the carrier account number to allow systemic recognition
of this information and ensure the appropriate party is charged for the transportation of
the nonconforming materiel. 30
30
Refer to ADC 1164
C17-49 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
This supports mandatory tracking and trend analysis using automated SDR
applications. In the event the shipment becomes frustrated, the action activity will
provide instructions for corrective action in order to bring the shipment into conformance
or otherwise direct remedial action. Corrective actions and options will be based upon
the circumstances of the quarantined/frustrated shipment, value and priority of the
shipment, access to the shipment by DoD personnel, and location of the consignee.
Alternatives include:
C17-50 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
identified as classified or sensitive. In addition, pilferable codes associated with arms
and ammunition are also included (codes N and P) in this category.
C17.3.13.1.1.4. Exceptions:
31
Refer to ADC 1359.
C17-51 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17-52 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.13.3.1. Logistics Reassignment
C17-53 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
activity with information to all concerned parties within 45 calendar days. When the
shipping depot is unable to respond to the reconsidered SDR, the depot will forward the
SDR to the source of supply for resolution. The resulting decision will be final.
C17-54 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
X12 EDI or EDI-based XML. Guidance for transaction content is provided in DLMS ICs
available on the DLMS IC page. DoD WebSDR will perform the following actions:
32
Refer to ADC 1026.
33
Refer to ADC 317, Revised Business Rules for Transshipper-Prepared Supply Discrepancy Reports.
Implementation delayed.
C17-55 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
identified action activity (current action activity after Reply Code 504 forwarding) and
SDR distribution rules.
34
Refer to ADC 425, Revised SDR Codes and Procedures, including Incorrect Part Number Discrepancy
Codes and DoD WebSDR Data Edits and Forwarding Enhancement.
35
Refer to ADC 1168.
36
Refer to ADC 1043E.
C17-56 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
program items is met. Reject SDRs identifying a discrepant condition, shortage,
overage, or IUID data mismatch with no identified serial number using Reply Code 946.
Refer to Table C17.T2 for applicable discrepancy codes.
C17-57 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.18.1.2.17. WebSDR will suppress informational copies
of Completion Notices (CN) to the activity identified in the Owner/Manager/Source
of Supply (OMS) field on the original (00) SDR for all SDR Document Type Codes.
C17-58 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
• Discrepancy Code(s)
• Action Code
• Submitter (Activity From)
• SDR Point of Contact
o Name
o Commercial Phone or DSN
o E-mail
• Attachment/Off-line Flag
C17-59 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
where no SDR application or e-mail address has been identified for an SDR recipient, or
an attempted e-mail distribution has failed due to an invalid address.
C17-60 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.18.1.7. Maintain the DoD WebSDR as a value-added service to
support submission, reply, and other functions related to SDR processing.
C17.3.18.2.1. WebSDR (DAAS) will edit SDR transactions for core data
elements required for the SDR transaction to be processed. If the core data elements
are missing or contain invalid entries, WebSDR will perform a DAAS Reject for the SDR
transaction and send an e-mail to the component SDR primary/alternate, and system
POCs for the scenarios identified below.
C17.3.18.2.3. DAAS will reject SDRs when document suffix length is not
equal to 0 or 1, alphanumeric only (no special characters). The following characters are
not allowed: I, N, O, P, R, S, Z, 1, and 0. WebSDR will generate an e-mail to the
Component SDR primary/alternate, and system POCs stating, “The document number
suffix code you provided has a length not equal to 0 or 1, contains a non-alphanumeric
or one of the following disallowed characters: I, N, O, P, R, S, Z, 1 or 0. Please submit
a new SDR with a valid document number suffix.”
C17.3.18.2.4. DAAS will reject SDRs, when document type code is not
valid in the set specified for use within WebSDR – 6, 7, 8, 9, A, D, N, P, R, V, and W.
WebSDR will generate an e-mail to the component SDR primary/alternate, and system
POCs stating, “The document type code you provided is not equal to 6, 7, 8, 9, A, D, N,
P, R, V, and W. Please submit a new SDR with a valid document type code.”
37
Refer to ADC 452, Implementation of DOD WebSDR Automated SDR Rejection Capability.
C17-61 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
when the only e-mail address is the DoD SDR Administrator e-mail address for systemic
routing. WebSDR will reject both of the specified scenarios with Reply Code 941.
C17-62 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
number). 38 Where wrong item discrepancies are reported, materiel identification of the
wrong item must be included. Wrong item received may be identified as previously
indicated or by description alone (citing “UNKNOWN” as the wrong item part number).
Reject with Disposition/Status (Reply) Code 931.
Refer to ADCs 282, CCP-Originated SDRs including Noncompliant WPM Procedures and Shipment
38
Hold Code; 317, Revised Business Rules for Transshipper-Prepared SDRs; and 322, Addition of Local
Catalog ID qualifier to Support Requirements for Theater Enterprise-Wide Logistics System (TEWLS)
Requisitions. Local Catalog ID implementation delayed.
C17-63 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
specified additional address or information as transaction data fields and must include
narrative remarks to reflect the address (due to limited implementation of the separate
address fields). Reject with Discrepancy Status/Disposition Code (Reply) 924.
C17-64 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
the 9th position in the call/order number data field will be rejected using Reply Code 940
and clarifying remarks stating that the thirteen-position PIID Call/Order Number must be
provided in the PIID (contract number) data field.
Refer to ADC 1044 Enhanced Interim SDR Reply Capability, Status Update, and Completion
39
Notification.
C17-65 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
unique SDRs to preclude rejection as a duplicate. 40 Reject with Discrepancy
Disposition/Status (Reply) Code 719.
40
Refer to ADC 1250.
41
Refer to ADC 1217.
42
Refer to ADC 1005.
C17-66 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
initial transmission plus the unique data fields applicable to the forwarding action per the
DLMS 842A/W. The submitter will receive the reply transaction as notification of interim
status. If an information copy of the initial SDR was provided to the source of supply
based upon Component rules, WebSDR will prepare an information copy of the
forwarded transaction using the correction format (Transaction Set Purpose Code CO).
When the source of supply identified in the SDR correction is the same activity identified
to receive the source of supply copy of the SDR reply (Transaction Set Purpose Code
11), this reply transaction will be suppressed as redundant to the correction. WebSDR
will update the SDR database to reflect the current action activity after this type of
forwarding action and ensure that subsequent transactions are properly transmitted to
the new action activity (rather than the original action activity). 43
43
Refer to ADC 1066/1066A. Delayed implementation authorized for rerouting of follow-on transactions.
C17-67 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.18.2.12.5.1. All parties receiving an information
copy of the original SDR as designated by the initiator or by a Component business rule
will receive a copy of all changes, cancellation, and replies associated with the SDR.
44
Ibid.
45
See ADC 1127, Enclosure 1
46
See ADC 1174, Enclosure 1
C17-68 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
47
Refer to ADC 1181B
48
Refer to ADC 1181A.
C17-69 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.3.18.2.15.3. Attachment file names must follow a specific
naming convention to allow space for WebSDR or the submitting system to append a
date/time stamp and other information to ensure uniqueness and to associate the
attachment with the appropriate transaction. The user-assigned portion of the file name
may be up to ten characters and should include key words to facilitate user recognition.
When submitted to WebSDR, the submitting system must ensure that the file name
contains no special characters other than the underscore ( _ ). The period may only be
used once prior to the file extension. WebSDR supports the following file types: BMP,
DOC, DOCX, GIF, JPEG, JPG, PDF, TXT, XLS, and XLSX.
C17-70 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.4.1.7. Promote timely QAR performance to prevent delays in
processing of procurement source receipts.
C17-71 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
authorized electronic/automated formats. Incorrect item SDRs must provide supporting
documentation to include photographs of the wrong item received.
C17.5.1.3. Responding action activities will provide the SDR reply for
Security Assistance SDRs using a DLMS-compliant SDR application via DoD WebSDR
or, pending full implementation, via direct DoD WebSDR input or authorized
electronic/automated equivalent format. SDR replies must include, at a minimum, the
applicable document number, the Security Assistance report number (item 2 of the SF
364), point of contact information, and pertinent information from the data blocks on the
reverse side of the SF 364 or the expanded SDR data element code lists (Appendix
7.28).
C17.5.1.4. The DoD shipping activity will retain paper copies of the Security
Assistance shipping documentation (signed carrier's receipt and shipping document) at
the shipping site for a period of 2 years following the shipping date. After this point, the
DoD shipping activity will retain a copy of the Security Assistance shipping
documentation in accordance with its NARA-approved Component record schedule as
required by DoDI 5015.02, DoD Records Management Program. Billing documentation
will be retained by the Military Departments and DoD agencies as specified in
MILSBILLS procedures and DoD 7000.14-R, Vol. 15, Department of Defense Financial
Management Regulation (Security Assistance Policy and Procedures).
C17-72 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.5.3. Directed Returns
C17.5.4. Incorrect Items. Incorrect item SDRs are not permitted for authorized
substitution, unless the substitute item does not meet fit, form, or function standards.
DoD Components and GSA follow the policy of automatic shipment of an
interchangeable item unless the requisition contains an appropriate advice code, in
accordance with MILSTRIP, limiting the request to a specific item. Similarly, quantities
may be adjusted to the unit pack quantity, when appropriate, unless restricted by the
C17-73 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
appropriate advice code in the customer requisition. Such adjustments resulting in
quantity variance are not reportable as discrepant.
49
Refer to ADC 1203.
C17-74 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
include the applicable 300-series forwarding reply code and a copy will be provided to
the submitter.
C17-75 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
15) to the ILCO within 45 calendar days from the date of the ILCO final reply to the
submitter concerning disposition, except when materiel/exhibit return to the customer is
required subsequent to US Government-directed evaluation/testing/repair. This
exception is applicable only when the materiel/exhibit must be re-inspected by the
customer to confirm that the reported discrepancy/deficiency has been resolved and,
therefore, additional transportation time is necessary for the return shipment. Under this
scenario only, the SA purchaser is authorized up to 90 days from the date of the final
ILCO reply to submit the Request for Reconsideration to the ILCO. The ILCO will be
responsible for monitoring that requests for reconsideration are submitted within the
allowable time standards.
50
ADC 430, Timeframe Change for Security Assistance SDR Requests for Reconsideration
C17-76 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.5.9. Follow-up on Credit Adjustments on SDRs
C17.5.9.1. When an action activity has indicated that a credit adjustment has
been authorized, reimbursement is normally provided to the fund code/line of
accounting and bill-to address cited on the original requisition. When concerned about
an apparent non-receipt of credit, the ILCO should consult with the appropriate finance
office for verification. Allow a minimum of 60 calendar days from the date of the SDR
response before initiating a follow-up action. To facilitate research of supply and
financial records, it is suggested that follow-up action for non-receipt of credit
associated with the return of discrepant materiel occur within a reasonable period (e.g.,
not longer than 45 calendar days after the ILCO provides the action activity the initial
notice with evidence of discrepant materiel return).
C17.5.10.3. Justification that initial receipt inspection and testing could not
have detected the deficiency.
C17-77 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C17.5.10.4. Documentation of storage and handling of the item since receipt
including type of storage.
C17.5.14. Responsibilities
C17-78 CHAPTER 17
DLM 4000.25, Volume 2, January 22, 2024
Change 17
that lack sufficient justification or were not received within the established time
standards.
C17-79 CHAPTER 17
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C18. CHAPTER 18
RESERVED
C18-1 CHAPTER 18
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C19. CHAPTER 19
RESERVED
C19-1 CHAPTER 19
DLM 4000.25, Volume 2, October 03, 2017
Change 9
C20. CHAPTER 20
MEDICAL UNIT ASSEMBLY PROGRAM
C20.1. GENERAL. This chapter provides procedures supporting the DoD Medical Unit
Assembly Program. This program is an integral part of the DoD Deployable Medical
Systems (DEPMEDS). These procedures cover from issuance of the advance
assembly build/release order through the actual building and packing of the assembled
component. Included are receipts at the assembly activity (e.g., Distribution Standard
System (DSS) assembly depot), from procurement and non-procurement sources and
the reporting of those receipts to the assembly manager (e.g., United States Army
Medical Materiel Agency (USAMMA), DLA Troop Support, Philadelphia, PA. Receipts
under the USAMMA Prime Vendor Program are included.
C20.2. APPLICABILITY AND SCOPE. These procedures apply primarily to DLA and
USAMMA, who issue/process transactions in support of the DoD Medical Unit Assembly
Program. Other DoD Components who participate in this program or other similar
programs will comply with these procedures.
C20.3. BUILD REQUIREMENT. The assembly manager will use DLMS 650A
Assembly Component Maintenance Structure to identify to the assembly activity, the
specific medical assembly to be built. DLMS 650A may also be used by the assembly
manager and assembly activity to enter corrections, provide missing data, or to send
history data. This is the initial transaction establishing the requirement, and it identifies
the end-item to be assembled, as initiated by a new requisition, or by changes to a
previous one. The transaction provides the build directive number, unit assembly
number, end-item nomenclature, cost estimate, total number of assemblies to be built,
number of components in each, and DoD activity address code (DoDAAC) of the ship-to
activity by providing the assembly activity sufficient information to start planning the
end-item assembly.
C20.4. DUE-IN ESTABLISHMENT. The assembly manager will use the Defense
Logistics Management Standards (DLMS) 527D, Due-in/Advance Receipt/Due
Verification transaction to establish pre-positioned materiel receipt (PMR) information at
the assembly activity. DLMS 527D PMR provides the procurement instrument
identifier (PIID) 1, contract line item number, national stock number (NSN), part number,
build directive number, and other information necessary to ensure that the assembly
activity receipts the item in the correct build directive number. When a PIID call/order
number (F in 9th position) is used, provide the value in the PIID field. The PMR
also provides data to prepare the DLMS 527R Receipt transaction upon receipt of the
materiel. Assembly managers and assembly activities will follow procedures in Chapter
1
Use the legacy PIIN pending transition to the PIID. When using the PIIN, include the four-
position call/order number. Refer to ADC 1161A.
C20-1 CHAPTER 20
DLM 4000.25, Volume 2, October 03, 2017
Change 9
12, Due-in PMR, to establish advance receipt information PMR and to maintain control
of due-in materiel.
C20.5. RECEIPT PROCESSING. The assembly activity will report procurement and
nonprocurement receipts to the assembly manager using DLMS 527R Receipt. This
notifies the assembly manager that assembly components have been received for a
specific build/assembly of the medical end item. Assembly activities must comply with
Chapter 13 for maintaining control of receipts, to include the time standards for
processing receipts, and for reporting discrepant/deficient receipts.
C20-2 CHAPTER 20
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C21. CHAPTER 21
STOCK READINESS PROGRAM
C21.1. GENERAL. This chapter provides general information supporting the DoD
Stock Readiness (SR) Program. The authoritative source for detailed procedures
pertaining to this program is
DLAR (JSR) 4145.04/AR 740-3/AFMAN 23-125/NAVSUPINST 4400.100B/MCO
4450.15B, Stock Readiness. Under the SR Program, the Department of Defense
requires uniform care of supplies, including the inspection and reporting of condition and
serviceability of materiel, and the scheduling, controlling, and reporting of packaging
and other cost reimbursable actions in support of the stock readiness program. This
chapter provides an overview of the DLMS transactions that support the stock readiness
program. Initial implementation is internal to DLA and its storage activities using
Distribution Standard System (DSS). The DoD Components will phase in usage during
modernization. All transactions must be processed through the Defense Automatic
Addressing System (DAAS). Capability to support communication with non-DLMS
owner/managers and non-DSS storage sites using email and web-based processing is
authorized. 1
1
Refer to ADC 1045. Target implementation is 1Q FY 2017.
2
Ibid.
C21-1 CHAPTER 21
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C21.2. APPLICABILITY AND SCOPE. This guidance is applicable to DoD
Components owner/managers and storage activities. It applies to classes of supply that
are managed by the DoD Components and stored at the storage activities, except Class
V, Class VI, and Bulk Class III. Use is required for materiel stored operating under the
DLA Distribution Standard System (DSS) and is supported by Component direction for
other storage activities.
C21.3.1. Under DLMS, the stock screening request is prepared using the DLMS
842C/I, Stock Screening Request. The owner/manager will create and transmit a
separate transaction for each action and information copy recipient (i.e., 28 transactions
prepared for 28 storage activities). The owner/manager will identify as the action
recipient those storage activities known by the owner/manager to have the materiel in
question in storage. An information copy will also be provided to all other storage
activities that might possibly have the identified stock in storage. When directing a
stock screening request to a DLA Distribution Center, all DLA Distribution Centers must
be identified as either action or information copy recipients. This process will ensure
that all applicable materiel is screened, to include, for example, DLA-managed materiel
that is now owned by the DoD Components. The only exception to this is for Type
Inspection Code P, which is used to request a special inspection at a single storage
activity. For Type Inspection Code P, information copies will not be provided to other
storage activities.
C21.3.2. The stock screening request will remain open in the owner/manager
application until a reply is received from all the action storage activities/locations
indicating that the stock screening has been: completed with no defects found;
completed with SQCR created; or completed with a “no stock” reply. An interim reply
may be provided under exceptional circumstances with explanatory comments. When
all action activity replies have been received, the request will be closed.
C21.3.3. Under DLMS, the stock screening reply is prepared using the DLMS
842C/R, Stock Screening Reply, to close the automated coordination of stock screening
actions. Storage activities will send a stock screening reply transaction to the
C21-2 CHAPTER 21
DLM 4000.25, Volume 2, January 22, 2024
Change 17
owner/manager for storage activities identified for action. If no stock is stored at a
particular storage activity, the storage activity will send a “no stock” reply where
designated for action.
C21.3.4. If the storage activity finds stock within its location, the storage activity
will automatically create an inspection workload using the data from the stock screening
transaction. If the inspection type is critical safety item (CSI), the storage activity will
automatically freeze the stock. When the inspection is complete, action storage
activities will send a reply to the owner/manager with the results of the stock screening
and close the screening request. When materiel is found matching the screening
criteria, the reply will specify the quantity and condition of the materiel. Depending upon
the results of the screening, the reply may indicate that an SQCR will follow.
3
Use the legacy PIIN pending transition to the PIID. When using the PIIN, may include the four-position
call/order number. Refer to ADC 1161A.
4
Refer to ADC 1045. Target implementation is 1Q FY 2017.
C21-3 CHAPTER 21
DLM 4000.25, Volume 2, January 22, 2024
Change 17
the receipt restriction will be reported to the owner via SDR receipt notification under
Chapter 17 pending enhanced procedures to notify both the owner and the manager. 5
5
Ibid.
6
Ibid. Pending implementation, Code A (ASAM) will remain available for use.
C21-4 CHAPTER 21
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C21.3.6.3.2. Informational Stock Screening. This is sent to storage
locations where materiel matching screening criteria is not known to be held, but which
may hold such materiel owned by other organizations.
C21-5 CHAPTER 21
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C21.4.1.3. Changes in condition of dated, limited shelf-life materiel, medical,
or subsistence items.
C21.4.2. Under DLMS, the SQCR is prepared by using the DLMS 842S/Q, SQCR.
Where DLMS is not supported, the SQCR will be entered via WebSQCR 7 to the
materiel owner pending implementation of the DLMS or DAAS capability to convert
transactions to email.
C21.4.3. Under DLMS, the SQCR response is prepared using the DLMS 842S/R,
SQCR Reply. Where DLMS is not supported, the materiel owner will reply via
WebSQCR. 8
C21.4.5. Detailed Requirements. The storage activity must prepare an SQCR for
each item, reporting quantity by condition code. The storage location may also be
provided (up to 20 locations may be identified per SQCR). Notification of SQCRs are
forwarded to the appropriate materiel owner stock readiness (SR) coordinator for
response by WebSQCR-generated email. The SQCR will use up to two discrepancy
codes in conjunction with narrative remarks to identify the problem being reported. The
SQCR will remain open in at the storage activity until disposition is received from the
materiel owner. The SR coordinator reviews the item for excess stock position, cost of
action in relation to the value of materiel, etc., and approves or disapproves the stock
readiness action request. When disapproving the stock readiness request, the SR
coordinator will concurrently provide disposition instructions for the materiel. When
approving the SR request, the SR coordinator will reply to the storage activity for action.
A disposition/status reply code is available in the DLMS format to communicate the
reply to reduce reliance on narrative text and to facilitate automated tracking/trend
analysis.
7
Ibid. Pending implementation, SQCRs will be forwarded manually.
8
Refer to ADC 1045; target implementation is 1Q FY 2017. Pending implementation, the owner will
return the SQCR form annotated with the applicable response information.
9
Refer to ADC 1045; target implementation is 1Q FY 2017. Pending implementation, the following codes
will remain available for use:
A ASAM
O Outbound Shipment
T Stock Readiness
C21-6 CHAPTER 21
DLM 4000.25, Volume 2, January 22, 2024
Change 17
Table C21.T2, Type Inspection Code and Suspense Table
C21-7 CHAPTER 21
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C21.4.7. The storage activity will provide materiel identification by NSN
manufacturer’s CAGE/part number, or other form of materiel identification authorized by
the DLMS format. It will also support identification by description if needed. Data
content is comparable to the DD Form 1225. When applicable, the report will include
the stock screening request reference number as a cross-reference between the
screening request and the resulting SQCR. The SQCR will use up to two discrepancy
codes to identify the non-conformance situation. It provides the estimated/actual cost
for repair or repackaging. Item unique identification (IUID) data requirements will be
populated on the SQCR in accordance with DoD Supply Policy when NSNs have an
IUID Indicator Y. 10
10
Refer to ADC 1045; target implementation is 1Q FY 2017.
C21-8 CHAPTER 21
DLM 4000.25, Volume 2, January 22, 2024
Change 17
an interim reply requesting additional information or clarification. Using the Status
Update allows for two-way communication between the submitting activity and the
owner.
11
Refer to ADC 1198A.
12
Refer to ADC 1084.
C21-9 CHAPTER 21
DLM 4000.25, Volume 2, January 22, 2024
Change 17
number must be used. Failing to provide the original document number for
material issued by the source of supply (SOS) will result in no credit to the
Component performing the return when using a constructed document number.
C21.4.9.4. The manager will provide disposition for all suspended materiel
via SQCR reply. Additionally, the manager will provide a DLMS 940R Materiel Release
to the storage activity to trigger shipment or disposal action as required. Upon
completion of the actions identified by the manager’s disposition instructions, the DLA
Distribution Center(s) will provide a completion notice to the item manager with an
information copy to the original owner.
C21.4.10.3. WebSS and WebSQCR will block Web input and reject
transactions associated with owner/manager or storage activity RICs that are not
C21-10 CHAPTER 21
DLM 4000.25, Volume 2, January 22, 2024
Change 17
capable of receiving DLMS transactions or not registered for automated email
notification.
C21.4.10.4. WebSS and WebSQCR will validate Web input and transactions
for correct format and valid data content. Invalid Web input will be blocked and
transactions rejected citing the applicable reply code.
13
Query capability not currently available pending full implementation of ADC 240 and ADC 1045
supporting Web-enhanced Stock Screening Requests and SQCRs.
C21-11 CHAPTER 21
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C22. CHAPTER 22
ASSET STATUS REPORTING
C22.1. GENERAL
C22.1.1. Purpose. This chapter prescribes asset status reporting procedures for
the interchange of asset status information between the DoD Component wholesale and
below wholesale distribution systems and owners/managers.
C22.1.2.1. DLMS 846I, Asset Status Inquiry/Report is used for the following
transaction functions identified by the beginning segment Report Type Code:
C22.2.1.1. For assets within the wholesale distribution system, Asset Status
Report Transactions may be used between DoD Components by mutual agreement.
Send Asset Status Report Transactions (legacy DIC DZA) between DoD Components
based on mutually agreed schedules.
C22-1 CHAPTER 22
DLM 4000.25, Volume 2, October 09, 2018
Change 11
distribution systems, each Component is authorized to procure a printed format suited
to its needs. DoD Components must identify to Defense Logistics Management
Standards any Component-prescribed data in DIC DZA that will be required in the
Component’s modernized system using DLMS. This is necessary so that Defense
Logistics Management Standards can incorporate the Component data in the DLMS
846I Asset Status Report Transaction.
C22.2.2. Assets Below the Wholesale Distribution System. Assets below the
wholesale distribution system will be reported to the owner/manager when requested by
the owner/ manager.
C22.2.2.1. Use the Request for Asset Status Report Transaction with the
appropriate asset status code to request, change, or discontinue asset status reporting
from the below wholesale distribution system.
C22.2.2.2. For the total asset visibility program, use the Request for Asset
Status Report Transaction to request the report of assets above the requisitioning
objective using DLMS 180M, Materiel Returns Reporting (Legacy Military Standard
Requisitioning and Issue Procedures (MILSTRIP) DIC FTE). Use with the asset
visibility program is based on agreement of the involved DoD Components.
C22-2 CHAPTER 22
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C22.2.2.4. Always show dates for commencement of reporting (Asset Status
Reporting Codes C and D) and change of reporting (Reporting Codes H and J) in the
Request for Asset Status Report Transaction as the first day of a month. In these
instances, send the request transaction not later than 60 calendar days before the
commencement date.
C22.2.2.7. When a one-time asset status report is required for the asset
visibility/redistribution program, the Request for Asset Status Report Transaction will
contain Reporting Code N and the date the report is required. Use with the asset
visibility program is based on agreement of the involved DoD Components.
C22.2.2.8. Use the Request for Asset Status Report Transaction to request
termination of reporting by citing Asset Reporting Code E. Show dates for termination
of reporting in the transaction as the last day of the month. Send the Request for Asset
Status Report Transaction termination request not later than 60 calendar days prior to
the termination date entered in the transaction.
C22.2.2.10. The asset status reporting code cited in the Asset Status Report
Transaction will indicate the type of reporting being accomplished.
C22.3.1 Intra-Army Use. Army also uses the DLMS Asset Status Report
Transaction on an intra-Army basis for Army Single Stock Fund Asset Balance
Reporting. This use serves a dual purpose:
C22-3 CHAPTER 22
DLM 4000.25, Volume 2, October 09, 2018
Change 11
C22.3.1.1 When used to report on the single stock fund to the national level
systems, the Asset Status Report Transaction represents a report to update the
requisitioning objective, reorder point, and retention limit.
C22.3.2. Intra-Navy Use. Navy also uses the DLMS 846I Asset Status Report
Transaction on an intra-Navy basis for reporting allowance-based assets that are below
the whole distribution system to the ICP. This allows the ICP to determine when the
activity requires more materiel due to being below its allowance.
C22-4 CHAPTER 22
DLM 4000.25, Volume 2, October 03, 2017
Change 9
C23. CHAPTER 23
CATALOG DATA SUPPORT
C23.1. GENERAL
C23.1.2.1. DLMS 832N, Catalog Data Support, is used for the following
transaction functions identified by the beginning segment Catalog Purpose Code
(1/BCT01/0200):
C23-1 CHAPTER 23
DLM 4000.25, Volume 2, October 03, 2017
Change 9
C23.2. INDUSTRIAL ACTIVITY CATALOG DATA SUPPORT
C23.2.3. The catalog data exchange supports the following functions. Specific
implementation varies by Service:
C23-2 CHAPTER 23
DLM 4000.25, Volume 2, October 03, 2017
Change 9
C23.2.3.5. Identification of MCMC LSNs to a unit of use LSN.
C23.3.1. Upon data conversion, all the current LSNs and non-DLA managed
materiel masters from the FRC and NSY systems will migrate to EBS. DLA managed
items will be identified and materiel master record will extended to each site as
applicable. This will provide a base line for the materiel currently used at the BRAC
sites.
C23.3.2. The catalog data will be applicable to new item inductions, FLIS change
notices for DLA items and non-DLA managed items, as well as Navy-assigned LSNs.
Manual updates for user unique data elements will be included in the process. Since
DLA will purchase, store, and sell these items to industrial activities, DLA will have this
data resident in EBS and will provide visibility and updates to the Navy systems via the
DLMS 832N IA Catalog Data Support transaction.
C23.3.3. EBS will also maintain site specific materiel master records for Depot
Level Repairable, Nuclear Support Consumables, or Program Owned Material (even
cognizance (COG)) items to provide updates pertaining to FLIS data or user unique
data elements to the FRC or NSY sites. DLMS 832N IA Catalog Data Support change
transactions will be provided to applicable sites based on FLIS updates or end user
changes to user defined data elements for these items.
C23.3.4. Web-based Query. When new items are needed by any of these sites,
the capability is required to create new materiel masters or update user defined data
elements to existing materiel masters directly into EBS through a user unique screen.
This application within EBS will prompt users for mandatory fields and user defined
fields for new entries, that may be optional depending upon the site (FRC/NSY). The
screen will allow the user to query the current EBS data base and determine if an NSN
or LSN already exists within EBS.
C23.3.5. If an existing record is found, and EBS does not currently reflect the
materiel master is extended to the user site, based on user response, the materiel will
be extended to the user site and an DLMS 832N IA Catalog Data Support transaction
will be sent to user site and identified as an ‘ADD’ record.
C23.3.6. When no record is found within EBS, the system will query the FLIS
reference master data environment (RMDE) to identify any associated NSN. Once the
C23-3 CHAPTER 23
DLM 4000.25, Volume 2, October 03, 2017
Change 9
materiel master is created in EBS, an DLMS 832N IA Catalog Data Support transaction
will be sent to the applicable FRC or NSY site. If found, the user will have the option to
build a materiel master record created with FLIS data and any mandatory user unique
data elements in EBS based on user response/input. EBS will then format a DLMS
832N IA Catalog Data Support transaction. This DLMS 832N IA Catalog Data Support
transaction will be identified as an ‘ADD’ and will be sent to the appropriate NSY/FRC
site via DAAS.
C23.3.7. If no NSN is found in FLIS, the user will have the option to add a materiel
master identified by an EBS assigned LSN. EBS has logic that defaults specific
mandatory FLIS data elements, and prompts the user for those for which a default
cannot be determined. EBS will then format an DLMS 832N IA Catalog Data Support
transaction identified as an “ADD” and send it to the site identified by the user and also
furnish a copy to the instance of DSS at the same site.
C23.3.8.1. Items identified by NSN. For these, DLA will relay FLIS catalog
information in the absence of a Navy-FLIS interface. DLA will also incorporate
additional DLA/Navy unique content.
C23-4 CHAPTER 23
DLM 4000.25, Volume 2, October 03, 2017
Change 9
C23.3.8.2.4. Hazardous Materiel under Hazardous Material
Management System (HMMS)Control System (RHICS). For items for which a materiel
master is needed to identify hazardous materiel under HMMS, an LSN identifying the
HMMS cataloged or created “LLN” numbers will be used if no NSN is assigned. LSNs
in this category will use the following construct: 6810-LL-N00-0001.
1
Refer to ADC 1176. Staggered implementation applies.
C23-5 CHAPTER 23
DLM 4000.25, Volume 2, October 03, 2017
Change 9
C23.3.8.5. Transaction Query. NSY sites will have the additional capability
to inquire EBS materiel master records using an DLMS 832N IA Catalog Data Support
transaction citing Catalog Purpose Code QU, Site Query for Catalog Record, to
determine if NSN or LSN or CAGE Code and Part Number combination exists in the
EBS data base when there is no existing record on the internal table within the NSY
Navy system.
C23.3.8.5.3. If the response from FLIS for the inquired NSN is negative
EBS will return an DLMS 832N IA Catalog Data Support transaction citing Catalog
Purpose Code NN, No record exists for NSN query. MAT will output for manual review.
C23.3.8.5.5. If the response for the inquired LSN is negative EBS will
return an DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose
Code NL, No record exits for LSN query. MAT will output for manual review. The user
may at this point enter data into the EBS user unique entry screen indicating the need to
create a record.
C23-6 CHAPTER 23
DLM 4000.25, Volume 2, October 03, 2017
Change 9
Catalog Record Added, containing all mandatory data elements to build a record in the
MAT system.
C23.3.10.1. EBS will create an LSN record for all NSN items identified with a
unit of use upon data conversion as a base line. After initial conversion, these records
will be based on either a requisition alert or funded requisition from any NSY or FRC
site identifying a unit of use requirement. An DLMS 832N IA Catalog Data Support
transaction record will NOT be generated to the NSY/FRC sites, but will be forwarded to
the applicable DSS site.
C23.3.10.2. The DLMS 832N IA Catalog Data Support record will reflect the
assigned LSN and Unit of Use as well as the associated NSN and FLIS unit of issue.
DSS will build an internal table cross-referencing the NSN and the associated Unit of
Use LSN, FLIS Unit of Issue and the Unit of Use.
C23.3.11. Substitute Cross Reference. EBS will provide catalog data reflecting
substitute reference during the status process. This will occur for both DLA managed
substitutions and for other Service managed substitutions.
C23-7 CHAPTER 23
DLM 4000.25, Volume 2, October 03, 2017
Change 9
C23.3.11.1. When EBS processes a request from an NSY or FRC and
determines the primary materiel identification number (e.g., NSN) is not available but
an approved substitute is available, EBS will provide ‘BH’ status and format an DLMS
832N IA Catalog Data Support identified as a substitute record reflecting the primary
NSN and reference the substitute NSN.
C23.3.11.2. When EBS receives a ‘BH’ indicating DLA will be sent an item
previously identified as a Navy suitable substitute for a DLA funded requisition, the
status will prompt EBS to format a DLMS 832N IA Catalog Data Support transaction
citing Catalog Purpose Code SN, NSN Substituted, reflecting the primary NSN and
referencing the substitute NSN when a materiel master already exists in EBS.
C23.3.11.3. When a materiel master for the substitute NSN does not exist in
EBS, a materiel master record will be created. Any user unique data elements will be
copied from the primary NSN specific to that site. A DLMS 832N IA Catalog Data
Support transaction citing Catalog Purpose Code SN, NSN Substituted, reflecting the
primary NSN and referencing the substitute NSN will be forwarded to the applicable site
for updating of Navy systems.
C23.3.12. FLIS Change Notices. EBS will be responsible for providing all change
notices to the Navy BRAC 2005 SS&D sites. These change notices will be generated
as a result of FLIS data changes. Anytime a FLIS recorded data element in EBS is
modified, a DLMS 832N IA Catalog Data Support transaction citing Catalog Purpose
Code CC, Catalog Record Changed, will be sent to all FRC/NSY sites that the material
has been extended to within EBS. The changed data element will not be specifically
identified. Each FRC/NSY system will update internal records accordingly.
C23-8 CHAPTER 23
DLM 4000.25, Volume 2, October 03, 2017
Change 9
C23.3.13. Unanticipated Situations Impacting Catalog Transaction Exchange
C23.3.13.1. If the connection between DLA EBS and FLIS, via FLIS Portfolio
Data Warehouse (FPDW) is down, EBS will initially respond with a ‘Response Delayed’
status and recycle the query until the FPDW connection resumes and then provide the
appropriate status at that time. This process is identified by a DLMS 832N IA Catalog
Data Support transaction citing Catalog Transaction Purpose Code RD.
C23.4.1. Upon data conversion, all the current local stock numbers and non-DLA
managed materiel masters from the MCMC systems will be migrated to DSS. This will
provide a base line for the materiels currently used at all MCMC sites.
C23.4.3. Web-based Query. When new items are needed by any of these sites,
the capability to create new material masters or update user defined data elements to
existing material masters directly into MCMC systems through a user unique screen.
This application within the MCMC systems will prompt users for mandatory fields and
user defined fields for new entries, which may be optional depending upon the site
application. The screen will allow the user to query the current MCMC data base and
determine if an NSN or LSN already exists.
C23.4.4. If no NSN or LSN exists in the MCMC systems, the user will have the
option to add a materiel master identified by a MCMC assigned LSN. MCMC systems
have logic that will default specific mandatory data elements, and prompt user for those
for which a default cannot be determined. MCMC systems will then format a DLMS
832N IA Catalog Data Support transaction and send to the site identified by the user.
C23-9 CHAPTER 23
DLM 4000.25, Volume 2, October 03, 2017
Change 9
C23.4.5.2. For items identified by contractor and Government entity (CAGE)
and part number combination (with no LSN or NSN assigned) within MCMC systems,
MCMC systems will allow end users to create a materiel master for these items via the
user unique screen application and systemically assign an LSN. Updates will be sent to
applicable sites based on the initial creation and any subsequent updates based on end
user input. These LSNs will be established based on the FSC with a sequentially
assigned number in the LSN NIIN.
C23.4.7. Modified Records. When the user entry modifies an existing record via
the user unique screen application, the system will prompt the user to save changes.
This will trigger the MCMC system to generate a DLMS 832N IA Catalog Data Support
transaction citing Catalog Purpose Code CC, Catalog Record Changed. This record will
contain all applicable data elements to build a record within the DSS system (allowing
overlay, vice transmission) of only the modified content. The system receiving a
transaction identified by Catalog Purpose Code CC that is unmatched to an
existing record in the database will accept the transaction and process it as a
new record. 2
C23.4.8. Deleted Records. When the user entry deletes an existing record via the
user unique screen application, the user will be prompted to save changes. This will
trigger the MCMC system to generate a DLMS 832N IA Catalog Data Support
transaction citing Catalog Purpose Code DD, Catalog Record Delete. This record will
contain all applicable data elements to delete a record within the DSS system
C23.4.9. FLIS Change Notices. DSS will be responsible for providing change
notice information via catalog data support transactions to MCMC sites for changes
related to the NSN itself. MCMC systems will be updated as applicable for these
records.
C23-10 CHAPTER 23
DLM 4000.25, Volume 2, October 03, 2017
Change 9
NSN Discontinued; no Replacement, will be provided. If a subsequent NSN is identified
from the FLIS update, the DLMS 832N IA Catalog Data Support transaction citing
Catalog Purpose Code NS, NSN Superseded, will be provided containing both the
former and new NSN.
C23.5.1. Air Force Background: The Air Force chartered the Government
Furnished Property-Accountability (GFP-A) Capability Initiative to provide
property accountability/control of Air Force-owned, contractor-managed and
possessed property by implementing standard and integrated processes. This
capability establishes and maintains accountable inventory records for GFP
assets managed by the Air Force contractor inventory control points (CICPs), and
makes them visible in the Air Force accountable property system of record
(APSR).
C23.5.1.1. Air Force CICPs will use their own inventory management
systems to send catalog data for local stock number (LSN) items to the Air Force
APSR. The contractor is the source of this information, which is similar to
standard catalog data. The Air Force APSR maintains the data fields used to track
the contractor-provided catalog data. As the item manager, the Air Force CICP is
responsible for identifying the appropriate values to be provided to the Air Force
APSR. The Air Force APSR’s asset master record must mirror the asset
information in the CICP’s IMS at all times.
C23.5.1.1.1. The Air Force CICPs will send catalog data when a new LSN
is added to its contractual requirements, or when information for a previously
assigned LSN changes. The Air Force CICP will transmit a DLMS 832N to the Air
Force APSR after processing the update to reconcile the information between the
two systems. The Air Force APSR will process the DLMS 832N and update its
master record for the affected asset(s).
C23-11 CHAPTER 23
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C24. CHAPTER 24
PRODUCT QUALITY DEFICIENCY REPORT PROGRAM
C24.1. GENERAL. This chapter replaces DLAR 4155.24/AR 702-7/SECNAVINST
4855.5 series/AFI 21-115/DCMA INST 1102, as the DoD Product Quality Deficiency
Report (PQDR) Program authoritative source for procedures pertaining to this program.
DoD Components must first consult this chapter for PQDR program guidance before
referring to DLAR 4155.24/AR 702-7/SECNAVINST 4855.5 series/AFI 21-115/DCMA
INST 1102, pending full migration of guidance and the eventual cancellation of the Joint
Service Regulation. The DoD PQDR program requires DoD Component capture and
exchange product quality deficiency information to facilitate root cause determinations,
corrective actions, reliability analysis, and recoupment actions (contractor caused
deficiencies). This chapter provides an overview of the DLMS transaction exchange
supporting the PQDR program. Initial implementation will include the DLA Enterprise
Business Systems (EBS), SECNAV Product Data Reporting and Evaluation Program
(PDREP), and NAVAIRSYSCOM Joint Deficiency Reporting System (JDRS). Initially,
all transactions will pass through the PQDR Inter-service Interface (PQDR II).
Components developing new PQDR processing systems will comply with this DLMS
standard to exchange data with other DoD PQDR systems.
C24-1 CHAPTER 24
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C24.1.4. PQDR Transaction Sets. The PQDR transaction set is used to move
all PQDR data as listed in DLMS 842P between the various PQDR processing
points (Originator/Originating Point, Screening Point, Action Point, and Support Point).
It is also used to facilitate PQDR exhibit movement, and exchange pertinent
correspondence and/or data regarding a PQDRs status (i.e., interim responses,
general correspondence, etc.). The DLMS 842P IC, PQDR Data Exchange, replaces
system unique transactions currently used to exchange PQDR by providing the DOD
Components with a standard electronic transmission method for PQDR data exchange
between AIS's.
C24.1.5. Product Data Reporting and Evaluation Program (PDREP). The term
PDREP refers to both the overall business process and supporting automation,
including both direct web input and transaction exchange. PDREP promotes
continuous process improvement of supply chain processes within the DoD for
increased material readiness by providing a means to hold external DoD
suppliers and internal supply chain stakeholders accountable. PDREP-AIS
formerly known as the Product Quality Deficiency Report Inter-service Interface
(PQDRII), is the DoD's PQDR system of record. PDREP-AIS supports DLMS
implementation that enables PQDR transaction exchange; provides a web-based
entry method to assist users who are not supported by another DLMS-compliant
PQDR application; and provides visibility of PQDRs for research and trend
analysis via management report/query capability. PDREP-AIS will allow users to
query the transaction history by Report Control Number (RCN), view a composite
of the PQDR, and provide central points of contact in the event of a transaction
failure.
C24-3 CHAPTER 24
DLM 4000.25, Volume 2, January 22, 2024
Change 17
another DOD Component or AIS to process a PQDR. When more than one DOD
Component or AIS is involved in processing a PQDR, it is referred to as an inter-
Service PQDR and must comply with inter-Service processing instructions
contained in this document. It applies to all supply classes not specifically excluded
from PQDR reporting.
C24.2. PROCEDURES
C24-4 CHAPTER 24
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C24.3. Exhibit Tracking. Systemic update of the PDREP-AIS for exhibit tracking is
provided as a by-product of standard logistics transactions. When received at a
distribution center, the receipt transaction will identify the PQDR RCN, and an
information copy of the receipt will be provided. Similarly, when a DLMS shipment
status transaction is prepared for the shipment of an exhibit, the shipment status will
perpetuate the PQDR RCN from the release order.
C24.4.2. DLA will not reopen a PQDR investigation after 180 days of
sending a Completion Notification (T- CN) Final Reply with no response (action)
by the Screening Point. On day 181 or later, a new PQDR (RCN) would need to be
issued referencing the old RCN, if further action by the Action Point or Support
Point is required.
C24-5 CHAPTER 24
DLM 4000.25, Volume 2, January 22, 2024
Change 17
C24.5.1. Input by either the PQDR Action Point or Support Point, the
information to be entered in each data element is dependent upon the type and
cause of the deficiency, and the information requested may not be appropriate in
all cases. The information requested is typical when the cause of the deficiency is
due to non-conformance with contract requirements. The investigative closing
codes provide specific details about the findings of the investigation. Together
these codes make up seven segments of investigation related data forming a
nine-character code referred to as the Summary Code. All segments of the
investigative closing codes must be completed prior to the Action Point
submitting a Final Reply. Failure to complete each of these data elements by the
Action Point will result in the transaction being rejected.
C24.6. PQDR Inter-Service Interface Query Capability. The PQDR II will allow users to
query the transaction history by RCN, the system inbox to view pending incoming
transactions, and the system outbox to view pending outgoing transaction.
C24-6 CHAPTER 24
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25. CHAPTER 25
SECURITY ASSISTANCE PROGRAM
C25.1 GENERAL
C25-1 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.1.2.6.1. Transaction Type Code 4 – Response to Requisition. This
transaction provides the functionality of MILSTRIP legacy DIC AE1, AE2, AE3, AE8,
AE9, AEA, AEB, AED, and AEE.
C25.2.1. Requisitions for FMS and Grant Aid materiel vary from the construction
of requisitions in support of U.S. Forces. Codes peculiar to FMS and Grant Aid
requisitions are listed in the designated appendices and in the military assistance
program address directory (MAPAD) found in DLM 4000.25 Volume 6, Chapter 3,
together with their meanings and applications. Specific FMS and Grant Aid requisition
entries are as follows:
C25.2.1.1.1.1. The first position will contain the FMS and Grant Aid
service assignment code (Appendix 7.2) of the SC implementing agency responsible for
administering the Grant Aid Program line.
C25-2 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.2.1.1.1.2. The second and third positions will contain the SC
customer code (Appendix 7.18) 1.
1
Refer to Approved Defense Logistics Management Standards (DLMS) Change (ADC) 448B
C25-3 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
Management Manual (SAMM); and DoD 7000.14-R, DoD Financial Management
Regulation, in combination, provide the interpretation of these codes.
C25.2.1.2.1.1. The first position will contain the FMS and Grant Aid
Service assignment code (Appendix 7.2) of the SC implementing agency responsible for
administering the FMS case.
C25.2.1.2.1.4. The fifth position will contain the FMS delivery term
code (see DTR 4500.9-R, “Defense Transportation Regulation” (DTR) or DLMS
Dictionary Logistics Data Resources Management System (LOGDRMS) for code
definition and applicable values) to convey the point of delivery condition negotiated
under the case agreement, and must correspond to delivery terms specified in the
applicable letter of offer and acceptance.
2
Ibid.
C25-4 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
This entry or the use of code X or W will be applied and recognized in conjunction with
the mark-for code entry as explained in Paragraph C25.2.1.2.3.
C25-5 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
exception data. See paragraph C25.2.1.2.3.2. The mark-for field, if required, will
designate the mark-for address.
C25.3.1. Requisitions for FMS and Grant Aid requirements for major weapons
systems, end items, and concurrent spares will be prepared to reflect the amount of
time remaining from dates of requisitions until required availability dates (RADs)
become effective. In FMS cases, compute the RAD by adding the lead time stated on
the letter of offer and acceptance (LOA) to the date of acceptance by the purchaser.
For Grant Aid, compute the RAD by adding the ICP determined lead time to the date of
the order.
C25.3.2. The requisition RAD is a three position value consisting of the character
A in the first position followed by the number of months remaining from the date of the
requisition to the computed RAD in the second and third positions. The RAD is
identified in the DLMS 511R Requisition by the Date/Time segment (2/G6201/80 Code
C25-6 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
BD; in MILSTRIP legacy DIC A0_ transactions, it is identified in rp 62-64. The
concatenated RAD value enables the source of supply, ILCO, and customer control of
requisitions, provides for recognition of firm commitments to foreign governments, and
helps ensure that materiel requirements are ready for delivery by the approved RAD.
The actual date for calculation of the RAD will be the last day of the month depicted by
the RAD entries in the requisition. Shipment of materiel will be made at the time of
initial requisition processing to the extent that releasable assets are available,
regardless of the number of lead time months shown in the RAD entry. Materiel not
immediately available should be acquired and shipped by the last day of the month
depicted by the RAD entries. However, depending on availability, materiel may be
acquired and shipped after the RAD expires and cancellations are submitted.
Appropriate status will be provided to the address(es) designated in the requisition.
C25.3.3. For Grant Aid, as soon as practicable, but not later than 120 days after
receipt of an approved funded order, the Service/Agency (S/A) Departments will place a
RAD on the requisitions for major items, and the associated support equipment and
initial issue parts, as determined by the S/A.
C25.3.4. RAD time begins with the date of the requisition (i.e., the date contained
in the requisition document number (See Appendix 7.14)) and does not have the effect
of holding release of the materiel.
C25.3.5. Requisition originators will modify the RADs when contract forecast
delivery dates indicate availability of items at a time other than designated by the
previously established RADs. In inter-S/A actions, when requisitions or other
documents bear a RAD with a shorter lead time than when the materiel will be available,
the supplying S/A will promptly provide the requesting S/A with status reflecting the true
availability date. This will be accomplished by use of DLMS 870S Supply Status
(MILSTRIP legacy DIC AE_) with Supply Status Code BB, BV, or B3, as appropriate.
The requesting S/A will adjust all records to reflect the new availability date information.
When the supplying S/A is aware that the established RAD will not be met, that S/A’s
source of supply will advise the appropriate ILCO that the RAD will not be met due to
slippage and internal processing. The advice of RAD slippage will be furnished to the
ILCO by letter, message, or DLMS 870S Supply Status (MILSTRIP legacy DIC AE_)
with Supply Status Code B3.
C25.3.6.1. The release date is defined as five days prior to the last day of the
month indicated in the last two positions of the extended RDD. Releasable assets will
be held until 50 days prior to the last day of the indicated month.
C25-7 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.3.6.2. In the case of DLA support, the extended RDDs will cause
intentional holding of support. For those orders, the support date is calculated
externally by DAAS upon receipt of the transaction and fed to DLA (RIC SMS). DAAS
sends RIC SMS the actual Standard Delivery Date, which in the case of extended
RDDs will cause the order to go into BP status and be held until 50 days prior to the
release date.
C25.4.2. Requisitions prepared by the U.S. Service for FMS and Grant Aid
requirements will be transmitted to the appropriate source of supply in the prescribed
MILSTRIP format.
C25.4.3. ILCOs will enter a cooperative logistics program support category code
(CLPSC) (Appendix 7.22) to applicable requisitions and passing orders, in order to
convey programmed/non-programmed status of a requisition to an ICP/integrated
materiel manager (IMM). The CLPSC is identified in the DLMS 511R Requisition by the
cooperative logistics program support code (2/LQ01/140 Code 89) ; in MILSTRIP legacy
DIC A0_ transactions it is identified in rp 72. Supply support provided under
cooperative logistics supply support arrangement (CLSSA) agreements is intended to
provide support to the requiring nation on the same basis that support is provided to
U.S. Forces, within assigned priority (based upon force or activity designator (F/AD))
and with all other coding being equal. However, such support cannot be provided if it
will impair the combat effectiveness of U.S. Forces. Consequently, CLSSA support is
not to be provided on the same basis as for U.S. Forces until after the expiration of a
lead time period necessary to augment U.S. Stocks to support the agreement. CLSSA
requisitions received before the expiration of required lead time may be filled from
existing supply source stocks only if stock levels do not drop below the established
reorder point. If sufficient stock balances are not available to fill such requisitions
without dropping below the reorder point, sources of supply will initiate procurement
action to fill the CLSSA requirement. CLSSA requisitions received prior to expiration of
the established lead times are considered to be “un-programmed” requirements. Un-
programmed CLSSA requisitions and passing orders will contain CLPSC 2 (Appendix
7.22). CLSSA requisitions and passing orders received after expiration of the lead time
required to augment stock levels will be processed in the same manner as U.S.
demands. Such requisitions and passing orders are considered to be “programmed”
requirements and will contain CLPSC 1. If the requisition does not identify a CLPSC
code, the ICP/IMM will process it as an un-programmed requirement.
C25.4.4. Certain FMS and Grant Aid requisitions will be subject to a restriction in
quantity when it is determined that the total requirement for an item will result in more
C25-8 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
than 25 shipment units. This constraint is employed to preclude the assignment of non-
MILSTRIP transportation control numbers (TCN) that occur when the number of
shipment units exceeds 25 and that cause a loss of identity to the shipment. The DoD
Components must specify the items of equipment to which the quantity restriction
applies. Generally, these items are equipment such as wheeled/tracked vehicles or
other items when a unit of issue of one each constitutes a single shipment unit.
C25.5.1. Sources of supply will provide status only to the ILCO or other monitoring
activities identified by the distribution code. The DLMS 870S (MILSTRIP legacy DIC
AE3) will be used to provide supply status, and the DLMS 856S (MILSTRIP legacy DIC
AS3) will be used to provide shipment status in response to follow-ups. However, the
DLMS 870S (MILSTRIP legacy DIC AE8)/DLMS 856S (MILSTRIP legacy DIC AS8) will
be used for status initiated by the source of supply or as otherwise delegated. It is the
responsibility of the ILCO or monitoring activity to furnish status to the appropriate
country status recipient.
C25.5.2. Status from the ILCO/monitoring activity to the MAPAD country status
recipient will be transmitted through DAAS.
3
Refer to Approved DLMS Change (ADC) 1177.
4
Ibid
C25-9 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.5.3. Status to FMS customers is sent to the MAPAD type address code
(TAC) 4 country status recipient.
C25.5.4. Status to Grant Aid customers is sent to the MAPAD TAC 3 purchaser/in-
country SAO status recipient.
C25.5.5. The media and status (M&S) entry should be zero to preclude
unnecessary status output. The transmission medium is determined by DAAS.
C25.6.1. General. Status is provided by the ILCO to the customer when the
requisition enters the supply system.
C25.6.2. Service Initiated Requisitions. When FMS requisitions are prepared and
introduced by a U.S. Military Service, a supply status document representing the U.S.
prepared requisition will be transmitted by the introducing U.S. Military Service to the
appropriate MAPAD status recipient. The supply status document may also be
prepared for Continental United States (CONUS)-generated Grant Aid transactions and,
when prepared, will be transmitted to the appropriate in-country SAO.
C25.6.2.1. For MILSTRIP legacy DIC AE_, the supply status will contain
code A, B, D, or E in the third position of the DIC to reflect the type of stock number
being requisitioned.
C25.6.2.2. The latest available unit price should be entered in the DLMS
870S in the Baseline Item Data segment (2/PO104/150); in MILSTRIP legacy DIC AE_
transactions, it is identified in rp 74-80; however, this is an optional entry depending on
the capability of the involved Military Service.
C25.6.2.3. Status Code BU will be entered in the DLMS 870S in the status
code 2/LQ01/330 Code 81); in MILSTRIP legacy DIC AE_ transactions, it is identified in
rp 65-66.
C25.6.2.4. The estimated shipping date (ESD) may be left blank. If provided,
it is entered in the DLMS 870S in the Date/Time Reference segment (2/DTM01/240
Code 369; in MILSTRIP legacy DIC AE_ transactions, it is identified in rp 70-73.
C25.6.3.2. When Grant Aid requisitions prepared by the in-country SAO are
forwarded to sources of supply by the ILCO, a DLMS 870S (MILSTRIP legacy DIC AE1)
citing Status Code BW will be provided to the customer/SAO.
C25-10 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.6.3.3. The latest available unit price may be entered in the DLMS 870S
in the Baseline Item Data segment (2/PO104/150); in MILSTRIP legacy DIC AE_
transactions, it is identified in rp 74-80.
C25.6.3.4. The ESD may be left blank. If provided, it is entered in the DLMS
870S in the Date/Time Reference segment (2/DTM01/240 Code 369; in MILSTRIP
legacy DIC AE_ transactions, it is identified in rp 70-73.
C25.7.2. When follow-ups are submitted to the ILCO/monitoring activity, the latest
status information will be furnished to the CR by the ILCO/monitoring activity.
C25.7.3. FMS requisition status will be provided in the DLMS 870S Supply Status
(MILSTRIP Legacy DIC AE2) or the DLMS 856S Shipment Status (MILSTRIP legacy
DIC AS2).
C25.7.4. Grant Aid requisition status will be provided in the DLMS 870S
(MILSTRIP Legacy DIC AE1) or DLMS 856S (MILSTRIP legacy DIC AS1).
C25.7.5. When current status information is not available on requisitions that were
submitted to the supply system, the ILCO/monitoring activity may transmit the follow-up
to the appropriate source of supply or provide interim status to the customer pending
completion of ILCO/monitoring activity follow-up action. In either case, a supply status
document containing Supply Status Code BW or BM (as indicated by the U.S. Military
Service) and a blank ESD field may be provided to the customer. When requisitions
have not been introduced into the supply system, the ILCO/monitoring activity will
provide a written reply to the customer originated follow-ups.
5
Ibid
C25-11 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.8.1. Cancellation and rejection status from the source of supply will be
provided to the ILCO/monitoring activity using the DLMS 870S (MILSTRIP legacy DIC
AE3) and the appropriate status code.
C25.9.1. When FMS requisitions are processed and a NOA is forwarded to the
FF/CR, a DLMS 870S (MILSTRIP legacy DIC AE2) supply status transaction containing
Status Code BL will be furnished to authorized status recipients at the same time the
NOA is forwarded.
C25.9.2. The BL status advises that the item is available for shipment and was
offered to the FF/CR on the date entered in the DLMS 870S in the Date/Time Reference
segment (2/DTM01/240) Date/Time Qualifier 169 – Product Availability Date; in
MILSTRIP legacy DIC AE2 transactions, it is identified in rp 70-73.
C25.10.1. Unusual circumstances may require a change in the country FMS offer
release option code or FF/CR code for an FMS case or for individual requisitions within
an FMS case. When this condition exists, either FMS customers or ILCO/monitoring
activity may initiate a DLMS 511M (MILSTRIP legacy DIC AM_) Requisition Modification
to change the coded data in FMS requisitions that have been released to the supply
system.
6
Revised requisition modifier procedures last reported as not implemented by the United States Marine
Corps (USMC). Refer to AMCL 123C.
C25-12 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.10.2.4. Signal code, Industry Code segment (2/LQ01/140 Code DE)
(MILSTRIP legacy rp 51)
C25.10.3. Modifiers that change the country FMS offer release option or FF/CR
must be submitted to procurement for manual amendment of contracts. Customers are
responsible for additional charges that may accrue. To limit manual processing and
avoid additional contract charges, modifiers that change the country FMS offer release
options or FF/CRs should be submitted only when the change is mandatory. When
LOAs have not been amended to reflect the changes, FMS customers must coordinate
with the Service ILCO/monitoring activity before requesting requisition modification.
C25.11.1. General. U.S. shipping activities use the NOA to notify the designated
FF/CR addressee and the International Logistics Control Office (ILCO) (identified by the
SC Implementing Agency) that materiel is ready for shipment.
7
Refer to ADC1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding DLMS
856N NOA and 870N NOA Reply. DLMS implementation for SCES may be delayed until fully fielded to
all the ILCOs (estimated for January 2019)
C25-13 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
size, weight, or value. Classified shipments always require use of an NOA, as indicated
below.
C25.11.1.3. U.S. shipping activities use the NOA to notify both the
designated FF/CR addressee and the ILCO that materiel is ready for shipment. A
manual NOA will be prepared for all FMS purchases except those customers
specifically requesting mechanized NOAs such as the Federal Republic of Germany.
Countries desiring to receive the mechanized NOA will submit a request to the Director,
Defense Enterprise Data Standards Office. All purchasers requesting the mechanized
NOA will be identified in this paragraph. Procedures for NOA preparation are contained
in Paragraphs C25.11.2. and C25.11.3.
C25.11.1.4. The NOA will identify the TCN assigned to the shipment, which
will be created in accordance with guidance in DTR 4500.9-R, Appendix L. The manual
or mechanized NOA document will be assigned an NOA notice number to reflect the
number of times the NOA has been sent to the FF/CR.
C25-14 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.11.1.5. ILCO Notifications.
C25-15 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.11.2.2. Replies to manual NOAs will be performed by two different
methods, contingent on the need for an export release. When an export release is
required, the FF/CR will furnish specifying consignment instructions, if any, and
coordinate these or other shipment or delivery instructions with the SDDC releasing
authority. When an export release is not required, the reply will be accomplished by
insertion of shipment release instructions on the third copy, which will be returned to the
shipping activity. Shipment release instructions will provide for shipment or delivery of
materiel to a single destination by shipment unit. Shipping activities will not split
shipment units identified by shipment unit numbers to accommodate shipments or
deliveries to multiple points. Instructions to FF/CRs regarding replies to NOAs will
specify the need for coordinated instructions when an export release is required and
include provisions for the following minimum data in the replies to other NOAs:
C25-16 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
follow-up, the appropriate ILCO will be contacted (offline) for assistance and follow-up
action to obtain the NOA response. Upon receipt of the offline contact from the shipping
activity, the ILCO must intervene, on behalf of the shipping activity, to obtain a response
to the NOA so the open shipment action can be closed. NOTE: This follow-up
procedure does not apply to Delivery Term Code (DTC) 8 releases. DTC 8 releases
involve materiel, usually Sensitive Arms, Ammunition and Explosives, which follow
special export procedures that require more time to process than can be encompassed
by the above follow-up procedure.
C25.11.3.1. The initial DLMS 856N (MILSTRIP legacy DIC AD1 and ADR)
contains both shipment unit information and line item information as contained in the DD
Form 1348-1A. When an export release is not required, indicate in the DLMS 856N
beginning segment (1/BSN07/020 Code ENR); for MILSTRIP legacy transactions, use
DIC AD1. When an export release is required, indicate in the DLMS 856N beginning
segment (1/BSN07/020 Code ERR); for MILSTRIP legacy transactions, use DIC ADR.
When export release instructions have not been received within 15 days of the NOA
date, a follow-up will be made to the SDDC releasing authority. If the FMS offer release
option Y applies, do not prepare or transmit to the FF/CR a DLMS 856N Delay NOA
(MILSTRIP legacy DIC AD3). When FMS offer release option Z applies and release
instructions have not been received within 15 calendar days of the initial NOA date,
prepare and transmit a DLMS 856N Delay NOA citing beginning segment (1/BSN07/020
Code D50); for MILSTRIP Legacy transactions, a DIC AD3 will accompany the delay
NOA detail documents.
C25.11.3.2. The DLMS 856N FMS NOA contains line item information as
contained in the issue/release document (e.g., the MRO or DD Form 1348-1A). For
MILSTRIP legacy transactions, the initial detail document contains a DIC AD2. When
FMS offer release option Z applies and release instructions have not been received
within 15 calendar days of the NOA date, a DLMS 856N Delay NOA will document all
the line items using the hierarchical level loop (2/HL03/010 Code I); for MILSTRIP
legacy transactions, a DIC AD4 will be prepared for each initial detail document that
accompanied the initial key document.
C25-17 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.11.3.3.1. When shipment release is to be made to the addresses
identified by coded entries in the MAPAD, the NOA Reply will contain a Shipment
Release Code R in the industry code segment (2/LQ01/145 Code 96). For MILSTRIP
legacy DIC AD5, the Shipment Release Code R is conveyed in rp 60.
C25-18 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
code), FMS offer release option code, FMS FF/CR code, FMS case and case line
number, project code (if applicable), priority designator (PD), and distribution code.
C25-19 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.13. DOCUMENT DISTRIBUTION
C25-20 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.14.2. When issues of DoD Defense Working Capital Fund (DWCF) stocks are
made in support of reimbursable Grant Aid requisitions, type of assistance/financing
code C is currently being used. DWCF activities are billing for those after the fact.
C25.15.2. When individual line items with a Grant Aid program RCN are to be
canceled, or FMS cases/programs are to be canceled, the canceling Agency/activity will
submit single-line cancellation requests under the appropriate Service policy.
C25-21 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
incident to actual diversion/cancellation of FMS requisitions will be charged under DoD
7000.14-R, “DoD Financial Management Regulation.”
C25.15.6. Grant Aid shipments that meet the criteria for shipment diversion under
mass cancellation conditions will be diverted to the pre-designated storage sites of the
canceling Service by the Defense Transportation Service (DTS). Storage sites in
receipt of Grant Aid cancellation shipment(s) will report the receipt(s) to the applicable
Service ICP/ILCO and the materiel will be accounted for as suspended materiel pending
receipt of disposition instructions. Service ILCOs will provide disposition instructions
under the provisions of DoD 5105.38-M, “Security Assistance Management Manual”
(Part II).
C25.16.1. General. Purchasing countries can establish FMS cases to get items
repaired, most commonly at the depot level. Purchasing country repair requirements
are integrated with the repair programs of the military services and are accomplished by
organic military repair facilities (i.e., Army maintenance depots, Air Force logistics
centers, Naval aviation depots, Naval shipyards) or by civilian contractors. There are
two concepts used in obtaining repairs under the FMS repairable program:
C25.16.1.1 Repair and Return. The FMS customer must request approval
for repair through the ILCO from the item/repair manager before shipping materiel to the
U.S. for repair. After receiving approval and shipping instructions from the item
manager, the purchaser ships the materiel to the designated repair facility where it is
entered into the repair queue. After repairs are completed, the item is shipped back to
the FMS customer. In the repair and return program, the cost to the country is the
actual cost of the repair in accordance with DoD 7000.14-R, Financial Management
Regulation (FMR), Volume 15, Chapter 7.
C25.16.1.2 Repair and Replace. Under the repair and replace program, the
unserviceable item is returned to the repair activity and, if it can be economically
repaired or overhauled, a replacement item is issued from the U.S. Military Service’s
stocks. The country’s unserviceable item is repaired or overhauled and returned to the
U.S. military service’s stocks. Under this program, countries are charged the estimated
average cost of repairs (also referred to as net cost or exchange price).
C25.16.2. Repair Service Value. The repair service value is the cost to repair or
replace an FMS-origin item returned by an FMS customer. The estimated or actual
repair unit cost, as appropriate for the type of repair program, will be identified for use in
specific business processes including status, shipment, and preparation of the
C25-22 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
subsequent billing statement by Defense Finance and Accounting Services (DFAS). If
actual cost varies among multiple items in a shipment, off-line manual processing may
be used to communicate the applicable values.
C25.16.2.3. Shipment Document. The repair facility and/or the storage activity will
include the estimated or actual repair service unit cost on the shipping document. This
is required for U.S. Customs export purposes. For DoD storage activities, the repair
service value will be perpetuated from the MRO and will be properly identified on the
DD 1348-1A/2 (see Appendices 6.1, 6.35, and 8.48).
C25.17.3. The DTS will be used to return discrepant FMS materiel when
appropriate. This can be accomplished in two ways:
C25.17.3.1. If a transshipment point has not been specified and the SAO has
the capability/capacity to perform this function, the SAO will arrange for movement
through the DTS.
C25-23 CHAPTER 25
DLM 4000.25, Volume 2, April 29, 2016
Change 7
C25.17.3.3. The transshipment point should be a U.S. Activity located in the
FMS country that submitted the SDR and/or be reasonably accessible to the FMS
country.
C25.17.3.5. Coordination between the U.S. source of supply and the ILCO is
required prior to initial designation as a transshipment point of an S/A other than that of
the source of supply.
C25.17.3.6. When the DTS is not used for return of discrepant FMS materiel,
the holding FMS country will arrange for movement through the FF/CR to the activity
designated in Block 3 of DD Form 1348-1A. CONUS inland shipments will be effected
by the use of a collect commercial bill of lading (CCBL). Reimbursement of
transportation charges between the holding FMS country and the FF/CR will be
requested by the CR to the U.S. supply source identified in the DD Form 1348-1A.
C25.18.1. FMS detention and demurrage charges are located in the Security
SAMM, Chapter 7.
C25.18.2. FMS document retention requirements are defined in the DTR 4500.9-
R, Appendix E, Paragraph Q.
C25-24 CHAPTER 25
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C26. CHAPTER 26
CONTRACTOR ACCESS TO GOVERNMENT SOURCES
OF SUPPLY
C26.1. GENERAL
C26-1 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
the functionality of MILSTRIP legacy DIC AM1, AM2, AM4, AM5, AMA, AMB, AMD, and
AME.
C26-2 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
transaction provides the functionality of MILSTRIP legacy DIC AP1, AP2, AP3, AP4,
AP5, AP8, AP9, APR, and APX.
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-3 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C26.3.3. Required Information. In addition to normal requisition data, GFM
requisitions, including Referral and Passing Orders will contain the following:
C26.3.3.1. RlC of the MCA monitoring the contract, (2/N101/180 Code Z5)
(MILSTRIP legacy rp 4-6).
2
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
3
Refer to ADC 1014. Staggered implementation is authorized for the transition to the mandatory
inclusion of the PIID (rather than MDN as an alternative to the PIID).
4
Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS
compliant PIID (rather than the abbreviated contract number authorized under legacy MILSTRIP
procedures).
C26-4 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
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 legacy call/order number, if appropriate, in rp 69-72;
and the last eight positions of the PIID in rp 73-80 (the MDN is optional).
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 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.1. The MCA must receive and validate GFM Requisitions, 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
C26-5 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
DoDM 4140.01, “DoD Supply Chain Materiel Management Procedures”, February 10,
2014.
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 system), cancellations, follow-ups, requisition modifiers,
passing orders, or referral orders to the applicable SoS through DAAS:
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 PIID. 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. 5
C26.5.5. MCAs in receipt of MCA Validation Request transactions will validate the
data contained therein. This validation process must be completed and an MCA
Validation Response transaction created and forwarded to the applicable SoS within 15
days of receipt of the MCA Validation Request transaction. The results of the validation
will be documented in the MCA Validation Response as follows:
C26.5.5.1. If the requisition has been previously validated, cite Advice Code
2M.
5
Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS
compliant PIID (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 PIID
C26-6 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C26.5.5.2. If the requisition has not been previously validated and the legacy
call/order number/PIID (or MDN and/or CLIN, if required by the Component in addition
to the legacy call/order number) is not present, cite Advice Code 2U.
C26.5.5.3. If the requisition has not been previously validated and the
call/order number/PIID is present, validate the data elements as indicated in Table
C26.T1, and generate the MCA Validation Response as follows:
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.
C26-7 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
Table C26.T1. MCA Validation Process
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 are subject to MCA review. 6
Manufacturer’s Directive If the MDN option is required by the Component, the Component will
Number validate; otherwise, reject with Status Code DB.
Call or Order Number (four- If specified by S/A contract, and entry is blank or incorrect, reject with
position legacy value) Status Code DB.
Contract Line Item Number If specified by S/A contract, and entry is blank or incorrect, reject with
(CLIN) Status Code DB.
Procurement Instrument If blank, or contract is not on MCA file, or contract has expired, reject
Identifier (PIID) with Status Code DB. (If requisition originated in the MILSTRIP
legacy format, then only the last eight positions of the PIID are
mandatory.). When the procurement instrument is issued under the
PIID call/order number (F in 9th position), this value must be provided
in the PIID field.
6
Staggered implementation authorized; refer to ADC 1123. Pending implementation by all Services and
Agencies, Army contractor requisitions for CFM will be forwarded for MCA validation except as noted
in paragraphs C26.7.4. (for Army retail) and C26.8.2. (for use of the DAAS CFM Authorized Materiel
Table).
C26-8 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
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 follow-
ups being treated as requisitions, containing a contractor’s Service/Agency code under
Appendix AP7.2, will perform the SoS/MCA validation process. (The SoS/MCA
validation process is not required when an internal requisition transaction is received
from a collocated MCA in the same system. However, the SoS must have safeguards
in place to ensure that only internal transactions generated by the collocated MCA are
accepted/processed.)
C26-9 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C26.6.4.3. If the MCA Validation Response is not received and 15 days have
elapsed, reject the requisitioners transaction with Status Code DR.
C26.6.4.4. Upon receipt of the MCA 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 MCA Validation Response. Reject the quantity difference between the
suspended transaction and the MCA 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.
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-10 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C26.7.2. DAAS will pass all MCA Validation Requests to the identified MCA using
the MCA RIC or distribution code provided in the transaction. If the MCA is invalid,
generate an MCA Validation Response with Status Code CL to the SoS. If the MCA
Validation Request does not include the MCA RIC, DAAS will populate the MCA RIC (or
DoDAAC) based upon the distribution code and forward the transaction accordingly.
C26.7.3. DAAS will pass all MCA Validation Responses to the SoS.
7
Procedures to control access to DoD material inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
8
DAAS special processing for Army to be terminated upon full implementation of MCA validation. Refer to
ADC 1123.
C26-11 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
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:
9
Staggered implementation authorized; refer to ADC 1123.
10
CFM requisitions are required to have data content comparable to GFM requisitions by January 1,
2017. Refer to ADC 1123.
C26-12 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
full implementation of MCA validation for CFM, the following special DAAS processing
procedures will be terminated; CFM will be validated in the same manner as GFM. 11
C26.8.2.3. DAAS will enter the DAAS RIC SGA or SHA as the validating
MCA.
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.
11
Refer to ADC 1123.
12
Staggered implementation is authorized for Service generation of outgoing requests for MCA validation
for CFM. In order to support staggered implementation, Services must be able to respond to incoming
requests for MCA validation beginning January 1, 2017. Refer to ADC 1123.
C26-13 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C26.8.3. DAAS Processing of DLA CFM Transactions
C26.8.3.2. If the transaction contains a valid DLA MCA, DAAS will route/pass
the transaction based upon established DAAS rules to the appropriate SoS for further
processing.
13
Special processing unique to validation of contractor requisitions submitted via DoD EMALL will be
terminated upon full implementation of MCA validation. Staggered implementation authorized. Refer
to ADC 1123.
C26-14 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C26.9.3.1. The DoD EMALL program office will identify to DAAS all
contractors authorized access to Government materiel for purchase as CFM using a
corporate credit card as the method of payment.
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 (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-15 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
C26.9.4.4. For DLA contractor credit card purchases (identified by a DLA-
assigned U-series DoDAAC in the document number), DAAS processing rules will be as
described in this paragraph, except that the requisition will be validated against the DLA
ICP MCA Table.
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
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 PIID 14, and CLIN, when applicable; this is not applicable to MILSTRIP
legacy processing. When a PIID call/order number (F in 9th position) is used, provide
the value in the PIID field. 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,
14
Use the legacy PIIN pending transition to the PIID. When using the PIIN, may include the four-position
call/order number. Refer to ADC 1161A.
C26-16 CHAPTER 26
DLM 4000.25, Volume 2, August 03, 2023
Change 16
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 DoDM 4140.01, DoD Supply Chain
Materiel Management Procedures. Materiel Receipt Acknowledgement is required for
GFM, including pushed shipments, under MILSTRAP procedures.
C26-17 CHAPTER 26
DLM 4000.25, October 23, 2015
Change 6
C27. CHAPTER 27
MASS OR UNIVERSAL CANCELLATION OF
REQUISITIONS
C27.1. GENERAL
C27.1.1. Purpose. This chapter provides procedures for the request, generation,
submission, and processing of mass and universal cancellations of requisitions. It also
provides procedures for the disposition of frustrated shipments and materiel resulting
from mass and universal cancellation actions.
C27.1.2. Transactions
1
Mass cancellation and follow-on transactions are DLMS enhancements. Refer to ADC 1132. Delayed
implementation authorized.
2
Universal cancellation and follow-on transactions are DLMS enhancements. Refer to ADC 1132.
Delayed implementation authorized.
C27-1 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
Code 2). This transaction provides the functionality of passing the MILSTRIP legacy
DIC AMJ.
C27-2 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
C27.1.2.14. The Reply to Cancellation Request – Materiel Release
Confirmation is identified by the DLMS 945A by beginning segment (1/W0611/0200
Code NJ). This transaction provides the functionality of MILSTRIP Legacy DIC AU0,
AUA, and AUB.
C27.2. APPLICABILITY
C27.2.1. Events such as base closures, termination of special projects, ship and
unit inactivation, termination of agreements, and termination of vessel outfitting or
construction can necessitate the requirement for mass or universal cancellation.
C27.2.3. When a total project (or total requirement for a single base) is no longer
required and should be canceled and it is known that insufficient time remains to permit
continued cancellation on a single line basis, a mass cancellation or universal
cancellation request may be initiated.
C27-3 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
activity at the earliest date through submission of a Requisition Modification (DLMS
511M) citing Special Requirements Code 555 3.
3
Code 555 identified in the required delivery date field for MILSTRIP legacy transactions.
4
Revised requisition modifier procedures last reported as not implemented by U.S. Marine Corps
(USMC). Refer to Approved MILSTRIP Change Letter (AMCL) 123C.
C27-4 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
designated Component contact points must ensure that the appropriate overseas
theater, force, logistics, or type commanders are cognizant of mass or universal
cancellation actions affecting their areas of responsibility.
C27.4.1. A need may exist to continue the processing of certain requisitions and
shipments during mass cancellations such as high priority demands to satisfy not
mission capable supply (NMCS) conditions (identified by Special Requirements Code
999 or N in the requisition). In addition, a need may exist to allow continued processing
of requisitions for materiel required to effect base closure. In these instances, submit a
requisition modification citing Special Requirements Code 555 to the SoS prior to the
submission of the mass cancellation request. For Security Assistance, use of Special
Requirements Code 555 is restricted to approved cooperative logistics supply support
arrangement (CLSSA) requisitions with Type of Assistance Code U or V (the buying
government has made cash payment to buy equity in DoD stocks). Sources of supply
will not cancel requisitions that have been modified to contain Special Requirements
Code 555 during a mass cancellation process. If submitting the mass cancellation
C27-5 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
request via offline message, then cite one of the following selective criteria in the special
instructions segment of the message:
C27.4.1.1. Project code(s) when associated with the ship-to DoDAAC being
canceled
C27.4.1.3. FSC, NSN, or CAGE/part number when associated with the ship-
to DoDAAC being canceled
C27.4.1.5. Specific priority designator (PD) when associated with the ship-to
address DoDAAC being canceled
C27.4.1.6. Required delivery period (RDP) when associated with the ship-to
address DoDAAC being canceled - conventional ammunition only. 5
C27.4.3. Upon receipt of either the Request for Mass Cancellation transaction or
the offline Mass Cancellation message citing selective criteria for continued processing
action in the special instructions segment, the SoS must review all prospective
cancellations to identify those for which continued processing has been requested. For
continued processing of requisitions at storage activities, the SoS will provide a Materiel
Release Order Modification (for MILSTRIP legacy processing, pass the Requisition
Modification) to the Storage Activity. In the case of items scheduled for direct vendor
delivery, the SoS must forward ICP Requisition Modifications (DIC AMP) to
procurement sources.
5
Use of RDP for conventional ammunition last reported as not implemented by U.S. Air Force (USAF).
Refer to AMCL 148.
C27-6 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
C27.5.1. Sources of supply are responsible for ensuring that requisition
processing, procurement, and storage activities exercise the fullest practical
resourcefulness in preventing the issue and shipment of unwanted materiel. The
practical considerations involved in the processing of cancellation requests include such
factors as time, packing and handling, related costs, and location of materiel for which
cancellation is requested.
C27.5.2. The SoS must cancel all requisitions dated on or prior to the effective
date announced in mass or universal cancellation requests for which materiel release
orders (MROs), and/or purchase requests have not been submitted to storage or
procurement activities. Provide a Supply Status transaction citing Status Code BQ or
B4, as appropriate, as notice of accomplished cancellations to all eligible status
recipients under Chapter 5 within the timeframe for furnishing status.
C27.5.3. The SoS will furnish Supply Status transactions citing Status Code B9 to
all eligible recipients under Chapter 5 within the timeframes for furnishing status for:
C27.5.4. Provide subsequent Supply Status transactions citing Status Codes BQ,
B4, or B6 as notification for each line-item canceled or diverted. Cite Status Code B8
for each line-item that was not canceled or diverted.
C27.5.5. The SoS will provide storage activities with mass requisition cancellation
transactions (DLMS 940R/DIC AC6) and universal requisition cancellation transactions
(DLMS 940R/DIC AC7) for all unconfirmed MROs and MRCs that indicate shipment to
OCONUS activities within 45 days of the effective date of the mass or universal
cancellation.
C27.5.6. The SoS will provide procurement activities with mass requisition
cancellation transactions (DLMS 869C/DIC ACP) and universal requisition cancellation
transactions (DLMS 869C/DIC ACM) for all open procurement actions. These
transactions are mandatory when purchase requests have been issued to another
Component. If processed within an integrated Component system, equivalent internal
transactions may be used.
C27.5.7. The SoS will not provide storage and procurement activities with
cancellation requests when:
C27-7 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
C27.5.7.3. In receipt of MRCs that show shipment to OCONUS customers
was accomplished more than 45 days prior to the receipt of the mass or universal
cancellation request.
C27.5.8. The SoS will follow-up with the procurement or storage activity, as
applicable, when no response to the original universal or mass requisition cancellation
request has been received within three days. The SoS will follow-up to procurement
activities via internal system communications or offline means (e.g., email, phone). For
follow-ups to a storage activity, the SoS will use the DLMS 940R Follow-Up to Storage
Activity for Mass/Universal Requisition Cancellation (there is no MILSTRIP legacy
equivalent).
C27.6.1.1. For mass cancellation, the storage activity will not suspend
processing of MROs identified for continued processing under paragraph C27.4.
C27.6.1.2. For universal cancellation, the storage activity will suspend further
processing of all MROs, including any citing Special Requirements Code 555.
C27.6.2. For CONUS shipments, storage activities will accomplish cancellation for
all items for which mass or universal requisition cancellation transactions are received
from SoS and the items have not been released to a carrier for delivery to the
consignee.
C27.6.3. Storage activities will advise the SoS of actions taken in response to
cancellation requests. When a shipment has not been released to the carrier for
delivery to consignee and cancellation is accomplished, the storage activity will send the
SoS a Reply to Cancellation Request transaction (DIC AG6) citing Status Code BQ.
C27.6.4. For shipments already released to a carrier for delivery to the consignee
not meeting the criteria stipulated in paragraph C27.5.7., the storage activity will
generate a Reply to Cancellation Request – Shipment Status (DLMS 856S/DIC AU_) for
routing by DAAS under standard MILSTRIP procedures for shipment status. It will also
generate the Storage Activity Supply Status (DLMS 945A/DIC AE6) to the SoS.
C27.6.4.1. For CONUS shipments and those OCONUS shipments that meet
the mass or universal cancellation criteria and have entered the DTS within 45 calendar
days of the date of the mass or universal requisition cancellation request, the storage
activity will cite Action Code W10 in the Reply to Cancellation Request – Shipment
Status to indicate actions are being taken to divert the shipment.
C27-8 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
C27.6.4.2. The Storage Activity Supply Status transaction to the SoS will cite
Status Code B9 indicating that action is being taken to cancel/divert the shipment.
C27.7.2. The SoS will initiate universal requisition cancellation transactions (DIC
ACM) and mass requisition cancellation transactions (DIC ACP) for all items scheduled
for direct delivery, and for which purchase requests have been submitted, regardless of
materiel costs, unless continued processing has been requested under Paragraph
C27.4.
C27.7.3. Procurement activities will advise the SoS of actions taken in response to
cancellation requests. When a shipment has not been released to the carrier for
delivery to consignee and cancellation is accomplished, the procurement activity will
C27-9 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
send the SoS a Reply to Cancellation Request transaction (DIC AG6) citing Status
Code BQ or B4. Procurement activities will not initiate actions with the DTS to cause
diversion of shipments at terminals.
C27.7.4. For shipments already released to a carrier for delivery to the consignee
not meeting the criteria stipulated in paragraph C27.5.7., the procurement activity will
generate the Storage Activity Supply Status (DLMS 945A/DIC AE6) to the SoS. The
SoS will generate, on behalf of the procurement activity, a Reply to Cancellation
Request – Shipment Status (DLMS 856S/DIC AU_) for routing by DAAS under standard
MILSTRIP procedures for shipment status.
C27.7.4.1. For CONUS shipments and those OCONUS shipments that meet
the mass or universal cancellation criteria and have entered the DTS within 45 calendar
days of the date of the mass or universal requisition cancellation request, the SoS will
cite Action Code W10 in the Reply to Cancellation Request – Shipment Status to
indicate actions are being taken to attempt to divert the shipment.
C27.7.4.2. The Storage Activity Supply Status transaction to the SoS will cite
Status Code B9 indicating that action is being taken to cancel/divert the shipment. This
status will be perpetuated by the SoS in a Supply Status transaction to the requesting
activity.
C27.8.1. Diverting Outside the Continental U.S. Shipments. When outside the
continental U.S. (OCONUS) shipments have already departed from continental U.S.
(CONUS) ports, the responsibility for diversion or disposition is that of the consignee or
the appropriate theater, force, logistics, or type commander. Notice to the latter will be
C27-10 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
the transportation lift data provided by the DTS clearance authority. (See paragraph
C27.9.4.)
C27.8.3. Designated Storage Points. All shipping DoD Components will designate
storage points within their distribution system to receive shipments redirected as a result
of mass or universal cancellation. Fund citations for bill of lading (BL) preparation must
also be provided. These designated points and fund citations will be provided to Air
Mobility Command (AMC), Military Surface Deployment and Distribution Command
(SDDC), or theater commanders and will serve as predesignated consignees for any
announced mass or universal cancellation. If more than one storage point is
designated, instructions will be furnished to specify on a geographical basis the storage
point designation in relation to each range of water and aerial ports (e.g., west, gulf, and
east coasts). In addition, canceling DoD Components will designate a contact point(s)
to provide disposition instructions on materiel that does not meet the automatic
diversion conditions specified in paragraph C27.9. Designated points of contact will
provide requested disposition instructions to DTS within 24 hours on materiel located at
air terminals and within 48 hours on materiel located at water terminals.
6
Refer to ADC 1142, Update to Remove General Services Administration (GSA) from MILSTRIP Materiel
Returns Program (MRP)
C27-11 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
controlling factors. In most situations, however, the strategic, tactical, or political
environment is such that complete disregard of these economic considerations is not
warranted.
C27.9.5. The DTS will generate specified documentation for the following
shipment categories:
C27.9.5.1. For all shipments that are diverted as a result of mass or universal
cancellation, the DTS will contact the shipper to confirm shipment diversion. The
confirmation of shipment diversion will contain complete Transportation Control and
Movement Document (TCMD) data for each shipment unit and, if available, the contract
number. In addition:
C27.9.5.1.2. For shipment units that are frustrated and were not
diverted to a specific site, the DTS will send a request for disposition instructions to the
appropriate Component contact points. In situations where the designated DoD
Component contact point is a collocated liaison office, the request for disposition
instruction transactions will be listed and provided to the contact point directly. After
receipt of disposition instructions for such frustrated shipments, the DTS will prepare
appropriate DTR transactions for the new consignee.
C27-12 CHAPTER 27
DLM 4000.25, October 23, 2015
Change 6
C27.9.5.1.3. For shipments in transit to, at, or between the POD and the
OCONUS consignee, OCONUS DTS activities will request disposition instructions from
the appropriate theater, force, logistics, or type commander’s designated contact point.
C27.9.6. Storage sites in receipt of diverted shipments will report the receipt to the
appropriate SoS under Chapter 13. Reconsignment/disposition will be as directed.
C27-13 CHAPTER 27
DLM 4000.25, October 09, 2018
Change 11
C28. CHAPTER 28
RESERVED
C27-1 CHAPTER 27
DLMS 4000.25 Volume 2, April 09, 2022
Change 14
C29. CHAPTER 29
RELEASE AND RECEIPT OF MATERIEL
DD FORM 1348-1A
C29.1. GENERAL
C29.1.3. Use of carbonless paper for a preprinted DD Form 1348-1A (or DD Form
1348-2) is authorized at the option of the Service/Agency.
C29.1.5. For transfers to DLA Disposition Services Field Offices, at least one copy
of DD Form 1348-1A (or DD Form 1348-2) must accompany the property and be in a
legible, easy-to-read format.
C29.1.6. For the DD Form 1348-1A, see Appendices 6.25 through 6.29, Appendix
6.31 and Appendix 6.35. There are two methods for generating the form:
C29.1.6.2. Non-preprinted form. When this method is used, the form and
data are printed simultaneously and will contain the prescribed data elements.
C29.1.7. The preprinted DD Form 1348-1A is 8-1/2 inches long (side to side) and
51/2 inches high (top to bottom). When printed on plain stock paper using laser,
thermal transfer, ion disposition, cold fusion, or other nonimpact printers, the size may
vary within a range of 7-3/4 to 9 inches long and 4 to 5 inches high (with one-sixth inch
C29 - 1 Chapter 29
DLMS 4000.25 Volume 2, April 09, 2022
Change 14
tolerance). When such print technology is used, the in-the-clear/human-readable data
must be easily read and the AIT entries must be machine readable. Margins of one-
fourth inch and outside lines are preferred, but may be eliminated provided the DD form
number remains readable. When printing three forms per 8-1/2- by 14-inch sheet of
paper, the originator must shall ensure that the form, spacing, size, and data entered
thereon are legible and capable of being interpreted by a Logistics Applications of
Automated Marking and Reading Symbols (LOGMARS) scanning device.
C29.1.7.1. Block numbers are provided for data entry. Data to be entered in
the data blocks are shown in Appendices 3.48 and 3.49. Block 27 will contain
information facilitating item unique identification (IUID) in support of unique item tracking
(UIT) and DoD supply policy in conjunction with the expanded content of the Portable
Data File 417 (PDF417) two-dimensional (2D) bar code as illustrated in Appendices
6.35 and 6.36. For a single item shipment, include the clear-text, concatenated/single
value unique item identifier (UII). Phased/staggered implementation is authorized
pending DoD-wide implementation of DoD policy for the application of IUID in supply
processes. As an interim approach, identification of the item on the Issue
Release/Receipt Document (IRRD) by serial number alone is authorized. Additional
optional information may include the item manufacturer’s contractor and Government
entity (CAGE) code, current part number, and batch/lot number. Block 27 will contain
all additional data and in-the-clear text that may be required and is not shown elsewhere
on the form. The in-the-clear text may be used with the AIT encoded information for
those activities possessing bar coding capability.
C29.1.7.2. The paper may be any color that provides a minimum bar code
contrast as specified in International Organization for Standardization (ISO) and
International Electrotechnical Commission (IEC) (ISO/IEC) 15415, Information
Technology - Automatic Identification and Data Capture Techniques - Bar Code Print
Quality Test Specification – Two-dimensional Symbols and in ISO/IEC 15416,
Information Technology – Automated Identification and Data Capture Techniques – Bar
Code Symbology Specification – Linear Symbols.
C29.1.8. The Code 39 (three-of-nine) linear bar code, and PDF417 2D bar code,
and Macro PDF417 2D bar code, as defined in ISO/IEC 16388 Information Technology
– Automated Identification and Data Capture Techniques – Bar code symbology
specifications – Code 39 and ISO/IEC 15438 Information Technology – Automated
Identification and Data Capture Techniques – PDF417 2D bar code symbology
specification, are established as the standard symbologies for the automated marking
and reading of items of supply, equipment, materiel packs, and containers in logistics
operations throughout the DoD. This symbology will be applied using MIL-STD-129
(latest revision), unless otherwise authorized. When Code 39 linear bar code symbols
are printed on DD Form 1348-1A (or DD Form 1348-2), all record positions of data
elements that will be encoded, will contain a bar code character even if the position was
blank on the source document. The specific technical information provided in
MILSTRIP is not intended to be compressive and should be used in conjunction with the
MIL-STD-129.
C29 - 2 Chapter 29
DLMS 4000.25 Volume 2, April 09, 2022
Change 14
C29.1.9. IRRD (DD 1348-1A or DD Form 1348-2) Continuation Page. For
shipment quantities of two or more serialized items, the responsible activity will prepare
a continuation page to facilitate automatic data capture.
C29.1.9.3. The continuation page will also contain Code 39 linear bar
coding with the respective human-readable interpretation (i.e., clear text) for the
included serial numbers to satisfy legacy system requirements.
C29.1.10.4. Printing Code 39 linear bar code symbols for A&E is optional on
the continuation page(s). All A&E hand held terminals (bar code imagers) in use
support Code 39 linear, PDF417 and Data Matrix 2D barcode symbols. Serial, Lot, or
any other required clear text data from either the DD Form 1348-1A or the continuation
page will be included in the PDF417 or PDF417 Macro 2D barcodes.
C29 - 3 Chapter 29
DLMS 4000.25 Volume 2, April 09, 2022
Change 14
C29.2. DOCUMENT DISTRIBUTION
C29.2.1. Actual copies utilized, other than the original and first carbon copy, will
be at the option of the individual S/A. See Tables C29.T1 and C29.T2 for the
distribution of the transactions.
C29.2.2. For transfers to DLA Disposition Services Field Offices, if all DD 1348-1A
data is provided in automated transactions and/or available via digital image, one copy
of the printed document must accompany the shipment; in accordance with the
Paperwork Reduction Act, additional paper copies are not required including verification
of receipt copies.
C29 - 4 Chapter 29
DLMS 4000.25 Volume 2, April 09, 2022
Change 14
C29 - 5 Chapter 29
DLMS 4000.25 Volume 2, April 09, 2022
Change 14
C29.3.2. To accommodate the various distribution systems and equipment, DD
Form 1348-1A (or DD Form 1348-2) provides blocks for data entry. With the exception
of Blocks 9, and 15, use of these blocks is optional, but when used, will contain
information shown in Appendix 8.48.
C29.3.3. The continuation page will accompany the DD Form 1348-1A (or DD
Form 1348-2) and must be attached to the material and shipment IAW MIL-STD-129
shipping document requirements for all shipments of two or more items which are
tracked under a UIT program or in support of DoD policy of the application of IUID in
supply business process. Minimum data entries are outlined in Appendix 6.36.
C29.4.3. For intra-S/A use, the data prescribed in Figure C29.F1. must be
entered. Other entries may be prescribed by concerned S/As; however, any such
entries must relate to the columnar and/or block headings indicated in the form.
C29 - 6 Chapter 29
DLMS 4000.25 Volume 2, April 09, 2022
Change 14
Figure C29.F1. Instructions for Completion of DD Form 1348-1A (or DD Form 1348-2), Used for
Returns to Stock Transfers (Excluding Transfers to DLA Disposition Services Field Offices)
RECORD POSITION(S) ENTRY AND INSTRUCTIONS
1-3 Perpetuate from source document or blank.
4-7 Leave blank.
8-22 Enter the stock or part number.
23-24 Enter the U/I.
25-29 Enter the quantity.
30-43 Enter the document number of the consignor (shipper.)
44-73 Leave blank.
74-80 Enter the unit price 2.
Blocks 3 and 27 Enter DoDAAC of the activity to which the materiel is directed.
The in-the-clear name, number, and address may be in Block
27.
Block 27 Enter the supply condition code reflecting the condition of the
materiel. (See Appendix 2.5, Supply Condition Codes)
Block 27 Enter activity account number of the activity to be credited (if
applicable) and the appropriate fund code (if applicable). (See
DLM 4000.25, Volume 4 Finance).
For single quantity item, enter applicable serial number and/or
UII content in conjunction with application of a PDF417 2D bar
as illustrated in Volume 2, Appendix 6.35. For multiple uniquely
identified items, use the continuation page per Volume, 2,
Appendix 6.36 3
2
Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will
reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for
display on the printed form, the generating application may leave blank. Refer to ADC 221
3
For Security Assistance shipments, see Figure C25-F1.
C29 - 7 Chapter 29
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30. CHAPTER 30
PROCEDURES FOR SERIALLY MANAGED MATERIEL
REQUIRING OWNER VISIBILITY
C30.1. GENERAL.
C30.1.1. Purpose. This chapter covers the additional procedures required for
serially managed materiel requiring owner visibility. See section C30.5. for the
categories of serially managed materiel covered by this chapter.
C30.1.1.4. These procedures require record keeping by both the owner and
storage activity and the constant transaction exchange at the item instance level (serial
number/UII) to ensure that the records of both reflect the correct serial numbers/UIIs, by
storage location, owner, and supply condition code (SCC).
1
The UII is an identifier used to uniquely identity an individual item used within the Department of
Defense. The UII may be a DoD Recognized IUID equivalent [e.g., Vehicle identification number (VIN)]
or a composite structure defined by the Department of Defense [refer to UII Construct 1 and UII construct
2]. Refer to DoD policy and supporting documentation for specific IUID guidance at
www.acq.osd.mil/dpap/pdi/uid/index.html. Refer to the most current version of MIL-STD-130 for specific
guidance marking of U.S. Military property.
C30-1 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.1.2. Transactions. This chapter addresses the following DLMS transactions
with their functions identified by their beginning segment and transaction type code.
Transactions identified support the business process, but may not actually be used to
exchange serial number/UII. The procedures in this chapter require that a system
transact business interchanges using DLMS transactions, The DLMS Implementation
Conventions (IC) are available on the Defense Enterprise Data Standards Office
(DEDSO) Website on the DLMS IC Page.
C30-2 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.1.2.11. Location Reconciliation History Notification is DLMS 846R with
beginning segment (1BIA02/020) Report Type Code ZZ – Mutually Defined.
C30.2.1. The provisions of this chapter apply to the Military Departments including
Coast Guard and Defense Agencies (hereafter referred to as the DoD Components).
C30.3. EXCLUSIONS.
C30.3.1. Classified activities that determine the visibility of specific items may
compromise operational security must request guidance from their DoD Components.
C30.3.2. The DoD excludes all items that are not cataloged in the Federal
Logistics Information System (FLIS) from the procedures in this chapter, with the
exception of management control numbers (MCN) under the SA/LW Program.
C30-3 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.3.3.The procedures in this chapter do not directly address update of the IUID
registry. The procedures for updating the IUID registry are contained in the DoD
Procurement Toolbox found on the “Unique Identification” link at
https://dodprocurementtoolbox.com. Procurement Integrated Enterprise
Environment (PIEE) eBusiness Suite web based training video tutorials of different
aspects of the IUID registry and baseline functionality are available at
https://piee.eb.mil/.
C30.4. POLICY.
C30.4.1. DoD Instruction 8320.04, Item Unique Identification (IUID) Standards for
Tangible Personal Property, dated September 3, 2015 states, “The unique item
identifier (UII) will be used globally as the common data key in financial, property,
acquisition, and logistics (including supply and maintenance) automated information
systems to enable asset accountability, valuation, life-cycle management, and
counterfeit materiel risk reduction.”
C30.4.2. DoD Components will follow the IUID procedures identified in DODM
4140.01, Volume 9, “Materiel Programs”, and Volume 11, “Inventory Accountability and
Special Management and Handing.
C30.4.3. The DoD Integrated Requirements Set (IRS) for IUID in Supply Business
Processes documents the ODASD(Logistics) vision for the integration of IUID at the
transactional level.
C30.4.4. DOD established overarching guidance for the serial number convention
and only alpha numeric (A-Z, 0-9), dashes, and forward slashes are allowed with a
maximum field length of 30 characters. Spaces are not allowed. DOD Components
must ensure future procurement actions require vendors to follow serial number
convention guidance as applicable. ODASD (Logistics) will update appropriate DOD
policies to reflect these changes followed by the implementation of this change.
Consequently, DEDSO will develop a change to incorporate these changes in all
applicable DLMS transactions and manuals.
C30.5.1. DoD Unique Item Tracking Programs. The procedures in this chapter
apply to items within a DoD level (inter-DoD Component) unique item tracking (UIT)
program 2.
2
This chapter does not apply to the DoD Small Arms and Light Weapons Serialization Program
(DoDSALWSP) pending implementation of weapon transaction reporting using standard supply logistic
transactions. The Defense Enterprise Data Standards Office will address DoDSALWSP use of standard
logistics transactions by a proposed DLMS change.
C30-4 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.5.1.1.1. The UIT designator code indicates that an item is part of
an established UIT program. In accordance with DODM 4140.01 policy, the DoD
Components will not establish any new UIT programs. The FLIS is the authoritative
source for UIT designator codes.
3
Refer to ADC 1198, 1198A, ASC 1198B, and ASC 1317.
C30-5 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.5.1.2.1. To maintain full accountability of all SA/LW within the
DoD, Components will ensure all SA/LW are properly recorded and managed in their
respective accountable system of record in accordance with DoDM 4140.01. All
SA/LW must be reconciled by line item as stated in the DLM 4000.25, Chapter 6
Physical Inventory Control. Components will follow the procedures in this chapter as
well as those listed in paragraph C30.2.2. for intra and inter Component shipments
pertaining SA/LW.
4
Radiation Testing and Tracking System (RATTS) was replaced by Radiation Source Tracking System
(RASTS). NRC licenses 12-00722-13 and 12-00722-14 covering Chemical Detection Equipment (CDE)
and Tritium are obsolete terminated licenses and are replaced by NRC license 21-32838-01.
C30-6 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.5.1.5.1. The NDLR UIT program is the recognized inter-DoD
Component program for select Navy-managed Depot Level Reparables (DLR).
C30.5.1.5.2. Interim Process for NDLR UIT Program. Navy and DLA
Distribution previously activated the NDLR UIT program with a limited set of DLMS
transactions. Navy and DLA Distribution will continue that process as an interim
process, until they implement Chapter 30 procedures. DLMS will eliminate this interim
procedure at that time. Navy’s target implementation date to transition to the Chapter
30 procedures for the NDLR UIT program is unknown.
Table C30.T2. Interim Navy Depot Level Reparable Program UIT transactions
Transaction Title
527R Receipt
856S Shipment Status
945A Materiel Release Confirmation/Disposal Release Confirmation
C30-7 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.5.1.8. Controlled Cryptographic Items (CCI)
C30-8 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.5.1.9.4. Interim Process for PIC NWRM UIT Program. Air Force
and DLA Distribution previously activated the PIC NWRM UIT program with the limited
set of DLMS transactions shown in Table C30.T4. Air Force and DLA Distribution will
continue that process as an interim process, until they implement Chapter 30. DLMS
will delete this interim procedure at that time. The Air Force target implementation date
to transition to the Chapter 30 procedures for the PIC NWRM UIT program is unknown.
5
Refer to ADC 407, Requirements for Unique Item Tracking (UIT) in the DLMS Supply Status (870S)
Supporting the Cargo Movement Operations System (CMOS) Interface (MILSTRIP/Supply/Transportation
Interchange)
6
Refer to ADC 316C, Revise DLMS 940R Material Release and DLMS 945A Material Release Advice, to
Support UIT for Air Force Positive Inventory Control (PIC) under the Retail Transportation and Supply
Receipt and Acknowledgement Interchange
7
Ibid
8
Refer to ADC 347, Revise DLMS 527R Receipt, 867I Issue, 945A Materiel Release Advice, and 947I
Inventory Adjustment to Support Unique Item Tracking (UIT) for Air Force Positive Inventory Control.
DLA Distribution Standard System (DSS) has implemented ADC 347.
9
Ibid.
10
Ibid.
11
Ibid.
12
Refer to ASC 1317.
C30-9 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
serially managed items that they store, beyond those items that require special handling
under existing UIT designator codes. The intent of this new program code is to account
for serialized items stored at DLA Distribution Centers, however, UIT Designator Code
AAK is available to all DoD storage activities.
C30.5.2.2. Following the initial implementation by DLA, the Services will be able to
classify items as serialized under the UIT Designator Code AAK by submitting the
change to FLIS.
C30.6. OBJECTIVES.
C30.6.1. Establish visibility by serial number/UII, from point of entry into the DoD
logistics systems through disposal, demilitarization, or shipment outside the control of
the Department of Defense.
C30.7.1. Establishing serial number/UII visibility may begin at any point in the
supply chain. Customarily, “cradle to grave” serial number/UII tracking begins at the
time of Government acceptance from the supplier/manufacturer.
C30.7.2. Alternatively, serial number/UII visibility may begin after items are
already in the DoD logistics system. Examples are items that meet the criteria and are
already in the inventory, or returns to inventory at any time after the item was originally
accepted by the Government.
C30-10 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.8.1.3. Apply the appropriate FLIS IUID indicator to NSNs for which they
have PICA responsibility. The IUID indicator provides the DoD Components a systemic
means to identify whether an NSN requires tracking by serial number and the UII when
available. The FLIS IUID indicator currently has two values (Y) indicating that IUID
marking is required and (N) indicating IUID marking is not required. For system to
system updates of this data, activities should subscribe to the IUID data through the
FLIS Portfolio Data Warehouse which is DLA Logistics Information Services Master
Data Capability. To negotiate this XML Data Exchange/Subscription, send an e-mail
request to [email protected]
C30.8.1.5. Owner visibility tracking by serial number/UII will cease when DLA
Disposition Services acknowledges receipt of serially managed materiel. DLA
Disposition Services will validate serial number/UII for serially managed materiel during
receipt processing and provide an SDR to the turn-in activity for any discrepancies.
C30-11 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.8.2.3. Shipping Activity Processes
13
See www.acq.osd.mil/dpap/pdi/uid for specific UID DFARS clause information to include in the contract.
C30-12 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
ensure the necessary information is available at time of receipt. Failing to
provide serialization data will result in the materiel to be suspended.
C30.8.2.3.3.2. The AIS supporting the owner will use the materiel
release confirmation to record which serial numbers/UIIs have been shipped and
decrement those serial numbers/UIIs from its record as no longer available and in
storage at that location.
C30-13 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
in the IUID registry. Additional information and guidance on the IUID registry can be
found on the UID Website http://www.acq.osd.mil/dpap/pdi/uid.
C30-14 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.8.2.4.3.2. Shipping activities will use the MRA follow-up
process for outstanding shipments awaiting receipt acknowledgement as stated
in DLMS Volume 2, Chapter 10. The shipping activities may use the WEB Visual
Logistics Information Processing System (WEBVLIPS) to research for missing
MRAs before submitting a follow-up.
C30-15 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
SDR is required for UIT program items, based on missing or mismatched IUID data
during receipt processing.
C30-16 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.8.2.6.5.2. When a discrepancy exists solely on mismatched
serial number and/or UII, the storage activity will transmit a DLMS 947I Inventory
Adjustment, Inventory Transaction Type Code DU (Inventory Adjustment Dual),
Quantity or Status Adjustment Reason Code AQ (Inventory Adjustment (UII and/or
serial number mismatch)) to correct the serial number/UII in question. The storage
activity will collaborate with the materiel owner(s) to research inventory adjustments due
to serial number/UII discrepancies resulting in a mismatch (Quantity or Status
Adjustment Reason Code AQ) in accordance chapter 6. When the item was previously
suspended, two inventory adjustment transactions are required to correct the serial
number/UII, and to update the SCC.
C30-17 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.8.2.6.5.6.1. The shipping activity will initiate the
investigation and perform an inventory adjustment using Quantity or Status
Reason Code WS, Suspected Lost or Stolen, to record the loss of the missing
asset pending an investigation.
C30-18 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.10.2. Activities shipping returns of any kind or responding to redistribution
orders will include the serial number/UII in the shipment status materiel return
transaction.
C30.10.3. Storage activities receiving returns or redistributed items will include the
serial numbers/UIIs in the receipt transaction. Missing serial number(s) and
mismatches on serial number/UII will be considered discrepancies. Refer to the SDR
processing section in this chapter.
C30.12.2. Missing serial number. Serially managed items requiring owner visibility
that are located in storage without a serial number will stop the equipment in the supply
chain until a serial number is identified and the materiel is marked. If the
remarking/relabeling exceeds the dollar threshold for pre-authorized corrective action or
the storage activity cannot identify the serial number using inventory records and other
available information, the storage activity will suspend the item in SCC J and prepare an
SQCR. Cite the applicable discrepancy code and provide clarifying remarks with
descriptive information for the item. The materiel owner is responsible for determining
the appropriate serial number and providing disposition for marking the item
C30-19 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.12.3.1. When a potential duplicate human readable serial number
exists, the materiel owner is responsible for resolving any discrepancies
pertaining the human readable serial number and/or missing data plates as well
as providing the corresponding information to the storage activity for proper
marking. The DoD Component will suspend any movement of the materiel
pending resolution. Upon confirmation of the duplicate human serial number, the
materiel owner may issue a modified human serial number using selected alpha
suffix to maintain a historical cross-reference. The Component will permanently
inscribe the modified human serial number into the item as required. Temporary
tags are authorized for Items destined for disposal or maintenance.
C30-20 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
numbers must follow DoD guidance as stated in section C30.4.4. Upon
assignment, the DoD Component will permanently inscribe the newly assigned
serial number on the weapon, except for those with historical artifact value or
weapons turn-in to DLA Disposition Services for disposal. When permanent
inscription is not possible, the DoD Component will securely tag the SA/LW. DoD
Components will maintain records of the original serial number for a historical
cross-reference of the weapon.
C30.13.3.2. DoD Components will request a new MCN from the Army when
a cataloged NSN is not available. The Army is the authoritative source for MCNs.
To ensure no duplicate MCNs, the Components must provide a detail description
of the weapon to include, but not limited to, make, model, caliber, manufacturer,
manufacturer commercial and government entity (CAGE) code, and/or
nomenclature, unit price, and supporting documentation. Examples of
acceptable supporting documentation includes procurement documents, bills of
sale, photograph of the weapon’s data plate, and technical drawings. Army
publication DA 708-1 provides additional guidance pertaining to the assignment
of MCNs.
C30-21 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
combination with other data elements, helps uniquely identify a serially managed
item. However, a human serial number alone is only unique to the manufacturer
and not to the DoD. A duplicate serial number refers to two or more items where
the NSN, serial number, UII (when available), and manufacturer CAGE code are
the same. Two identical items with the same serial number may not necessarily
be a duplicate. DoD Components will report discrepancies at time of receipt
using the SDR; storage quality control report (SQCR) for materiel in storage.
C30-22 CHAPTER 30
DLM 4000.25, Volume 2, December 27, 2022
Change 15
C30.13.8.1. DoD Components shipping weapons to entities outside of the
DoD will retain all evidential matter pertaining to the shipment and have it readily
accessible to respond to inquiries from law enforcement when requested. The
shipping activity will need to obtain acknowledgement of receipt (electronic or
offline) prior to closing in-transit status.
C30.13.8.2. When shipping SA/LWs to FMS and Grant Aid customers, DoD
Components will release property accountability at time of shipment. The last
DoD Component is responsible for retaining all evidential matter of the shipment
and must be available to respond to inquiries pertaining the shipment. If the
weapon is returned to the DoD supply chain, the Component will re-establish
property accountability via the receipt process and update their respective APSR.
C30.13.9. Loan of SA/LW(s). Loan of SA/LW may occur within the DoD or
under the Law Enforcement Support Program. For the purpose of loans, the
loaner is the entity or organization that owns the SA/LW while the loanee is the
organization receiving the loan. The accountability of the SA/LW(s) remains with
the DoD owning Component (Loaner) while the custodial accountability transfers
to the authorized DoD organization or Law Enforcement Agency (loanee) until the
SA/LW(s) returns to the loaner.
C30-23 CHAPTER 30
DLM 4000.25-2, June 13, 2012
AP1-i APPENDIX 1
DLM 4000.25, Volume 2, November 26, 2019
Change 13
AP2. APPENDIX 2
CODES INDEX
APPENDIX TITLE
AP2 Index
AP2.1 Document Identifier Codes
AP2.2 Type of Physical Inventory/Transaction History Codes
AP2.3 Ownership Codes
AP2.4 Purpose Codes
AP2.5 Federal Condition Codes
AP2.6 Management Codes
AP2.7 Correction/Change Codes for Storage Item Records
AP2.8 Reject Advice Codes
AP2.9 Asset Status Reporting Codes
AP2.10 Asset Transfer Status Codes
AP2.11 Special Program Requirement Status Codes
AP2.12 Small Arms and Light Weapons Transaction Codes
AP2.13 Small Arms and Light Weapons Error Transaction Reject Codes
AP2.14 Type of Media Codes
AP2.15 Inventory Adjustment - Physical Inventory Error Classification Codes
AP2.16 Inventory Adjustment - Accounting Error Classification Codes
AP2.17 Discrepancy Indicator Codes
AP2.18 Type Inspection Codes
AP2.19 Review Period Indicator Codes
AP2.20 Competitive Characteristics Codes
AP2.21 Type of Contractor Codes
AP2.22 Type Due-In Indicator
AP2.23 Type Location Reconciliation Request
AP2.24 Other Codes
AP2-i APPENDIX 2
DLM 4000.25, Volume 2, November 26, 2019
Change 13
EXPLANATION: Identifies:
A table showing the correlation of MILSTRAP legacy document Identifier Code (DIC)
functionality to the Defense Logistics Management Standards (DLMS) is available from
the Defense Logistics Management Standards Website. This table provides visibility of
how MILSTRAP DIC functionality is incorporated in DLMS American National Standards
Institute (ANSI) Accredited Standards Committee (ASC) X12 transactions.
AP2.1.1. Under MILSTRAP legacy 80 record position transacttions, the DIC provides a
means of identifying a given product (e.g., receipt, issue, demand, inventory adjustment,
etc.) to the logistics system and processing operation(s) to which it pertains and further
identifies such data as to the intended purpose, usage, and operation dictated. The DIC
enables automatic data processing equipment to select the appropriate program(s) and
to mechanically perform operations dictated by the code, and provides a corresponding
function for manual processing.
AP2.1.2. The DIC is a mandatory entry on all legacy 80 record position documents
entering and leaving the supply distribution systems under MILSTRAP. Each
transaction, therefore, will be identified by an appropriate code. The assignment of the
first character of the code is a responsibility of DoD.
MILSTRAP – E Series
MILSBILLS – H Series
MILSTRIP – U Series
AP2.1.3.2. The second record position may be either alpha or numeric. A numeric
entry denotes a transaction which affects an on hand balance and shows the general
nature of the transaction. An even number denotes a receipt or debit; an odd number
denotes an issue or credit. An alpha entry, excluding DIC DAC, DAD, or DAS, denotes
a transaction which does not affect the overall or total on hand balance.
AP2.1.4. D series DICs are listed on the following pages. Unassigned codes in the D
series are reserved for future assignment by DoD.
RECORD POSITIONS: 7
CODE DEFINITION
A through B Reserved for future DoD assignment.
C Special Inventory, all supply condition codes (SCC). Initiated by the
storage activity in support of inventory accuracy improvements initiative.
D Special Inventory, all supply condition codes. Initiated by owner as a
result of end of day processing imbalances.
E Spot Inventory due to denial (all SCCs). Initiated by the storage activity
or owner as a result of denials.
F Reserved for future DoD assignment.
G Scheduled Inventory. Inventory to be conducted within a specified
period of time according to an established plan on controlled items and
all other items or categories designated by the DoD Component.
H Special Inventory, all SCCs. Initiated by owner when an Inventory is
necessary and the date of last Inventory is less than 90 days.
I Scheduled Inventory. Initiated by owner based on owner’s inventory
prioritization methodology.
J Special Inventory, all SCCs. Initiated by owner as a result of location
reconciliation errors.
CODE DEFINITION
K Special Inventory, all SCCs. Initiated by storage activity as a result of
location survey errors.
L Scheduled Inventory, specified SCCs. Initiated by owner for a random
statistical sample Inventory.
M Special Inventory, SCCs. Initiated by storage activity as a result of
onhand balance mismatches between the locator and property
accountability records.
N Scheduled Inventory, specified SCCs. Initiated by storage activity for
the annual statistical sample Inventory.
O Reserved for future DoD assignment.
P Scheduled Inventory, specified SCCs. Initiated by storage activity for a
random statistical sample Inventory.
Q Reserved for future DoD assignment.
R Special inventory, specified SCC. Initiated by storage activity in an effort
to resolve a customer report of discrepancy.
S Special inventory, specified SCC. Initiated by storage activity as part of
receipt follow-up (intransit) resolution process.
T Special inventory, specified SCC. Initiated by storage activity as a result
of a disposal release order directing ownership transfer to the Recycling
Control Point.
U Special inventory, specified SCC. A location-level inventory initiated by
storage activity for low asset visibility counts.
V Special inventory, specified SCC. Initiated by storage activity as a result
of a location-level inventory adjustment or exceeding predetermined
thresholds.
W Automatic submission of transaction history from storage activity to
owner/ manager.
X Storage activity transaction history requested by owner/manager or
transaction history response from storage activity to owner.
Y Annual (Total) Transaction History (optional for use to distinguish history
associated with annual reconciliation from other transaction history)
Z Special Inventory (specified SCC) systemically initiated by the storage
activity for quantity mismatches within the storage activity’s
management system between the quantity-by-location and the owner
balances (i.e. Book-to-Book adjustments).
0 through 7 Reserved for future DoD assignment.
CODE DEFINITION
81 Distribution depot/storage activity has no transaction for the stock or part
number requested for the dates specified, but transactions are available
since the date of last location reconciliation. For use with DLMS
Supplement 846P when beginning segment Report Type Code
(1/BIA02/20) is 'AD'. Used only with DLMS.
92 Distribution depot/storage activity has no transactions available for the
dates specified or since the date of last reconciliation. For use with
DLMS Supplement 846P when beginning segment Report Type Code
(1/BIA02/20) is 'AD'. Used only with DLMS.
1
As an interim exception, DLA vendor storage activities do not use codes 8 or 9 under DLMS. DLA
vendor storage activities 8-fill or 9-fill the document number field, until such time as they fully implement
ADC 198.
2
Ibid .
RECORD POSITIONS: 70
RECORD POSITIONS: 70
1
In accordance with the approved change for Ownership Code 0 (Zero) to identify DoD Special
Operations Forces ownership, DoD Component publications and procedures are to restrict alpha Purpose
Code O from being assigned/used. This restriction is made to avoid confusion between use of alpha
Purpose Code O and numeric Ownership Code 0, since ownership code and purpose code share a field
under the constraints of the legacy 80-record position Defense Logistics Standard System (DLSS)
transaction formats. (See AMCL 15.)
1
Refer to the DoD 4140.27, “Shelf-Life Item Management Programl”, 31 August 2018 for serviceability
timeframes associated with shelf-life items. SCCs J through P, R, and V, will not be used for materiel
turn-ins to the DLA Disposition Services.
2
Ordnance Information System implementation date for SCC T is October 1, 2012. Ordinance Information
System is used by Navy, Marine Corps, and Coast Guard. For Army, further analysis is required to determine
supportability and implementation timeline for incorporation of SCC T in Army’s Logistics Modernization
Program. Air Force has no plans to implement SCC T at this time. Refer to ADC 446.
3
Refer to ADC 1159.
RECORD POSITION: 72
1
Refer to ADC 375. New Management Code for Navy Funded Non-Production Support Materiel Ordered
under BRAC SS&D/IMSP.
2
Also applicable to DICs assigned by the DoD Components for use on the Disposal Turn-In Document
(DTID) below the wholesale level.
3
Refer to ADC 391, implementation date January 2011.
4
Expanded for use for all DoD Components requisitioning from DLA is planned for future implementation
(approximately 2014.)
5
ADC 391, New Denial Management Code to Support the New Protection Process at the Navy Shipyards
(NSYs) when Protection Document Number/Job Order does not Match DSS Records under BRAC
SS&D/IMSP.
6
Refer to ADC 449, Intra-DLA Revisions to the DLMS 945A, Materiel Release Advice, Cancellation
Reason Code, Management Code, and Associated Procedures under Reutilization Business Integration
(RBI)
7
ADC 1169, DLA Distribution Center Denial Scenarios Associated with Product Quality Deficiency Report
(PQDR) Exhibits.
8
Authorized for use in intra-Army supply status (ADC 191), and subsequently expanded for inter-
Service/Agency use (ADC 312). Implementation outside Army applications is pending.
9
Also applicable to DICs assigned by the DoD Components for use on DTID below the wholesale level.
10
Authorized for use in Army interface with DLA in response to a DLA directed LRO.
11
Refer to ADC 396, Revised Procedures and Data Content for DLMS Materiel Release Order (940R)
and Material Release Advice (945A) and New Denial Management Code for Marine Corps BRAC SDI.
12
See ADC 1054.
13
Authorized for use only in intra-Navy referral orders.
14
Excludes intra-DLA Disposition Services A6A, A6B, A61, and A62 denial transactions in support of
Commercial Venture actions.
15
Authorized for use only in intra-Navy D7_ Issue transaction reversals and in D7_ Issue transaction
reversals between Navy Specialized Support Points and DLA.
16
Authorized for use in intra-Army supply status (ADC 191), and subsequently expanded for inter-
Service/Agency use (ADC 312). Implementation outside Army applications is pending.
17
Authorized for use in Army interface with DLA in response to a DLA directed LRO.
18
Refer to ADC 370, Requisitioning for Off-Station Forward Site Support and New Non-Inventory
Affecting Denial Management Code indicating Off-Station Materiel under Navy BRAC SS&D IMSP
19
Authorized for use only in intra-Navy D7_ Issue transaction reversals and in D7_ Issue transaction
reversals between Navy Specialized Support Points and DSCs.
20
Authorized for use only in intra-Navy referral orders.
21
Authorized for use only in intra-Navy D7_ Issue transaction reversals and in D7_ Issue transaction
reversals between Navy Specialized Support Points and DSCs.
22
Authorized for use only in intra-Navy referral orders.
23
Authorized for use in intra-Army supply status (ADC 191), and subsequently expanded for inter-
Service/Agency use (ADC 312). Implementation outside Army applications is pending.
24 Authorized for use in Army interface with DLA in response to a DLA directed LRO.
25
Authorized for use only in intra-Navy D7_ Issue transaction reversals and in D7_ Issue transaction
reversals between Navy Specialized Support Points and DSCs.
26
Authorized for use only in intra-Navy referral orders.
27
Authorized for use only in intra-Navy D7_ Issue transaction reversals and in D7_ Issue transaction
reversals between Navy Specialized Support Points and DSCs.
28
Authorized for use only in intra-Navy referral orders.
29
Authorized for use only in intra-Navy D7_ Issue transaction reversals and in D7_ Issue transaction
reversals between Navy Specialized Support Points and DSCs.
30
Authorized for use only in intra-Navy referral orders.
31
Authorized for use in intra-Army supply status (ADC 191), and subsequently expanded for inter-
Service/Agency use (ADC 312). Implementation outside Army applications is pending.
32
Authorized for use in Army interface with DLA in response to a DLA directed LRO.
33
Authorized for use only in intra-Navy D7_ Issue transaction reversals and in D7_ Issue transaction
reversals between Navy Specialized Support Points and DSCs.
34
Authorized for use only in intra-Navy referral orders.
35
Refer to ADC 243, Identification of Army Single Stock Fund (SSF) Requisitioning Actions and Edit
Action Code (EAC) Authorization.
36
ADC 1390 Air Force Management Codes in 511R, 511M and 869F
37
Refer to ADC 375, New Management Code for Navy Funded Non-Production Support Materiel Ordered
under BRAC SS&D/IMSP.
38
Refer to ADC 352, Identification of Army Single Stock Fund (SSF) Requisitioning Actions and Edit
Action Code (EAC) Authorization. Management Code for Product Quality Deficiency Report (PQDR)
Replacement Requisitions. Note: The requisition alert transaction allows Navy BRAC IMSP sites to
notify DLA of their requirements in advance of the funded requisition, thereby allowing DLA to procure
and position materiel appropriately to support prompt order fulfillment. Refer to ADC 381 for the
procedures and content of the DLMS Requisition Alert.
39
Expanded use for all DoD Components requisitioning from DLA is planned for future implementation
(approximately 2014).
40
Refer to ADC 338A, Requirements of Mission Support Material (MSM) under Navy BRAC SS&D IMSP.
Implementation date January 2011. Note: The requisition alert transaction allows Navy industrial sites to
notify DLA of their requirements in advance of the funded requisition, thereby allowing DLA to procure
and position materiel appropriately to support prompt order fulfillment. Refer to ADC 352 for DLMS
Requisition Alert procedures.
41
Refer to ADC 359, Perpetuation of the Denial Management Code to the DLMS Requisition, and
Modification of Air Force BRAC IMSP SDR Procedures.
42
Ibid.
1
This code is obsolete when using a DLMS transaction. To express multiple changes, use multiple loops
of 2/LQ/190. For legacy MILSTRAP transactions this code may still be used.
2
Ibid
AP2.8.1. All A B, D and H series reject advice codes not listed in this appendix are
reserved for future use and are not to be used unless authorized and disseminated by
the DoD MILSTRAP Administrator. All other series are reserved for intra-Component
use.
CODE EXPLANATION
AA Rejected. DIC iinvalid.
AB Rejected. Submitted to incorrect manager. If known, the correct manager’s routing
identifier code (RIC) is supplied in the DLMS 824R 2/NM1/065 segment.
AC Rejected. Type of physical inventory code invalid or blank.
AD Rejected. Stock or part number unidentifiable.
AE Rejected. Quantity field invalid.
AF Rejected. Document number invalid.
AG Rejected. Ship-to address unidentifiable.
AH Rejected. Required signal code invalid or blank.
AI Rejected. Procurement instrument identifier (PIID) (contract number) call/order
number, contract line-item number (CLIN), and/or sub-CLIN is invalid or blank.
AJ Rejected. Required fund code invalid or blank.
CODE EXPLANATION
AK Rejected. Ownership/purpose code invalid or blank.
AL Rejected. Unauthorized owning DoDAAC or RIC (use for Air Force Government
Furnished Property - Accountability (GFP-A) only).
AM Rejected. Supply condition code invalid or blank.
AN Rejected. Physical location of property not provided.
AO Rejected. Insufficient inventory in the accountable property system of record
(APSR) due to potential mismatch.
AP Rejected. Required management code invalid or blank.
AQ Rejected. Processing/count date invalid or blank. Location Reconciliation Request
cutoff date invalid.
AR Rejected. Unit of issue incorrect.
AS Rejected. Support date invalid. Location Reconciliation Request and/or
Transaction History Transmittal received past scheduled deadline.
AT Reserved for DoD assignment.
AU Rejected. Invalid Country Code. The code is not valid in the Geopolitical Entities,
Names, and Codes (GENC) Standard. Originator must update the transaction with a
valid country code and resend.
AV Rejected. Location Reconciliation Request RIC (From) activity not valid.
AW Rejected. Logistic Reassignment Logistics Transfer/Decapitalization transaction
(DLMS 846D, DIC DEE/DEF) or memorandum Due-in transaction (DLMS 527D with
LIN01 Code T, DIC DDX)) received more than 1 year after the ETD. (The gaining
item manager (GIM) will reject the memorandum Receipt transaction (DLMS 527R
with LIN01 Code T, DIC D4X) if no memorandum due-in is on record at the GIM to
indicate it is a valid procurement receipt.)
AX Rejected. General Services Administration (GSA) is the source of supply for the
requested SPR. GSA does not participate in SPR procedures. If required, submit a
funded requisition citing the applicable required delivery date.
AY Rejected. Location Reconciliation Request and/or Transaction History Transmittal
does not equal the number of transactions recorded in the Location Reconciliation
Notification and/or Location Reconciliation History Notification.
AZ Rejected. Number of Location Reconciliation Requests received from storage
activity exceed reasonable variance from owner/manager.
BA Rejected. Serial Number or UII (when available) invalid or missing (use for Air
Force Government Furnished Property - Accountability (GFP-A) only).
BB Rejected. Others, see remarks.
CODE EXPLANATION
BC Rejected. Estimated Delivery Date Missing/Invalid.
(Approved for Army and DPAS. Requires coordination with other Services prior to implementation
and use)
BD Rejected. Submitter in the PMR not found/Unknown/Inactive in the system rejecting
the transaction.
BE Rejected. Distribution Code Missing/Invalid
(Approved for Army and DPAS. Requires coordination with other Services prior to implementation
and use)
BN Rejected. Invalid logistics bill number.
BU Rejected. Failed validation with Standard Financial Information Structure (SFIS)
Fund Code to Fund Account Conversion Table.
(1) Discrete values for the SLOA data elements in the transaction do not match data
elements from the SFIS Fund Code to Fund Account Conversion Table for the Fund
Code cited in the transaction.
(2) Invalid/missing fund code. Resubmit with a valid fund code.
Note: Issues with content of the SFIS Fund Code to Fund Account Conversion
Table are to be communicated to the Fund Code Monitor of the cognizant
Component.
BV Rejected. DoDAAC in the transaction does not have the appropriate authority code
for its intended use
BW Rejected. Suspense account is not authorized for Interfund use
BX Rejected. Total dollar value detail of bills is not equal to total dollar value of the
summary bill
BY Rejected. Count of detail bills is not equal to the count in the summary bill. The
count of DLMS 810L IT1 Loops (2/IT1/010) must equal DLMS 810L 3/CTT01/070.
BZ Rejected. DoDAAC or MAPAC is not valid in DAAS
DA Rejected. FSC Missing/Invalid.
DB Rejected. NIIN or LSN Missing/Invalid.
DC Rejected. Unit of Issue Missing/Invalid.
DD Rejected. Quantity Missing/Invalid.
DE Rejected. Hazardous Waste/Material Code Missing/Invalid.
DF Rejected. Unit Price Missing/Invalid.
DG Rejected. Supply Condition Code Missing/Invalid.
DH Rejected. Demil Code Missing/Invalid.
DI Rejected. Contact Name Missing/Invalid.
CODE EXPLANATION
DJ Rejected. Contact Phone Missing/Invalid.
DK Rejected. Chemical Abstract Service Number is Missing/Invalid.
DL Rejected. Fund Code Missing/Invalid.
DM Rejected. Suffix Code Invalid
DN Rejected. Advice Code Invalid
DZ Rejected. Turn-in activity cannot process DLMS-formatted transactions. DTID
rejection must be communicated through alternative methods.
HA Rejected. Waste Profile Sheet Invalid or Missing/Invalid.
HB Rejected. Generator Name Missing/Invalid.
HC Rejected. Facility Address Missing/Invalid.
HD Rejected. Facility City and State Missing/Invalid.
HE Rejected. Facility Zip Code Missing/Invalid.
HF Rejected. Technical Contact Missing/Invalid.
HG Rejected. Technical Phone is Missing/Invalid.
HH Rejected. Chemical Name Missing/Invalid.
HI Rejected. Chemical Concentration is Missing/Invalid.
HJ Rejected. Chemical Range is Missing/Invalid.
HK Rejected. Chemical Abstract Service Number is Missing/Invalid.
HL Rejected. EPA HW Number Missing/Invalid.
HM Rejected. Range of Concentration Missing/Invalid.
HN Rejected. Unit of Issue Incorrect.
HO Rejected. Container Number Missing/Invalid.
HP Rejected. Hazardous Waste Profile Sheet Data required to support Disposal
TurnIn Document (DTID)
HZ Rejected. Turn-in activity cannot process DLMS-formatted transactions. HWPS
acknowledgment must be communicated through alternative methods.
1 Throughout this document, the “date indicated” refers to segment 2/DTM/100 of the DLMS 846I.
CODE EXPLANATION
F and G Reserved for future assignment by DoD.
H Change type of reporting to daily asset status reporting (Code C
above) on the date indicated in the asset status reporting request.
J Change type of reporting to monthly asset status reporting (Code D,
above) on the date indicated in the asset status reporting request.
K and L Reserved for future assignment by DoD.
M Commence daily asset status reporting as soon as possible.
N2 Submit a one-time asset status report (DIC DZF) for the asset
visibility/redistribution program. Submit the report by the date
indicated in the asset status reporting request.
O Reserved for future assignment by DoD.
P3 Report assets above the activity’s requisitioning objective using the
customer asset report materiel returns program transaction (DLMS
180M 3).
Q thru Y Reserved for future assignment by DoD.
Z One-time asset status report is requested/furnished on an expedited
basis. The date Submit the report by the date is required is entered
indicated in the asset status reporting request.
0 thru 9 Reserved for intra-Component use.
2 Restricted for use based upon agreement of the DoD Components involved.
3 Legacy DIC FTE
CODE EXPLANATION
AA No assets are available for transfer. (Applies to Document Identifier Code
(DIC) DLB.) No record of due-in; cancel memorandum due-in record.
(Applies to DICs DLD and DLF.)
AB DIC DEE/DEF Logistic Transfer/ Decapitalization transactions and DIC
DD_/DF_ due-in transactions (provided due-in existed) submitted
previously. Losing inventory manager (LIM) will submit duplicate
transactions. (Applies to DIC DLB.) Due-in (full or partial quantity) has
been received. LIM will provide duplicate DIC DEE/DEF logistics
transfer/decapitalization transactions and DIC D4X/D6X memorandum
receipt transactions. (Applies to DICs DLD and DLF.)
AC DIC DEE/DEF Logistics Transfer/Decapitalization transaction will be
submitted. (Applies to DIC DLB.)
AD No assets are available for transfer but due-ins exist. Due-in transactions
will be submitted. (Applies to DIC DLB.) Delinquent due-in exists. Routine
follow-up action being taken by the LIM. (Applies to DICs DLD and DLF.)
AE Additional due-in available for transfer. LIM will provide memorandum due-
in. (Applies to DIC DLF when additional due-in is available for transfer or
when no DIC DLE was received.)
AF Change to estimated delivery date. Revised delivery date is provided.
(Applies to DICs DLD and DLF.)
AG Original due-in transaction has been reversed (i.e., cancelled). Cancel
delinquent due-in. (Applies to DICs DLD and DLF.)
CODE EXPLANATION
AH Original pre-award procurement due-in has been awarded on a contract.
LIM will submit DIC DDX reversal for the pre-award due-in and a new DIC
DDX with contract number, quantity, EDD, etc. (Applies to DICs DLD and
DLF.)
A1 Contract delivery action is complete. LIM will submit DIC DDX reversal for
the portion of the due-in quantity not received. (Applies to DICs DLD and
DLF.)
AJ Materiel pending litigation or returned to contractor. GIM will retain due-in
pending resolution by ACO. (Applies to DICs DLD and DLF.)
AK Invalid due-in. Original due-in transaction will be reversed (i.e., cancelled).
(Applies to DICs DLD and DLF.)
CODE EXPLANATION
PA Request or modifier accepted. Submit requisition in time to all for delivery within
the appropriate Uniform Materiel Movement and Issue Priority System
(UMMIPS) time standard.
PB SPR is not within inventory control point (ICP) acceptance criteria. The ICP will
maintain the SPR quantity only until the procurement lead time and/or assembly
time away from the support date to advise the forecasting activity of any
technical or management changes and to assure return/retention should
unexpected assets materialize. Continuation of this requirement into the
procurement lead time and/or assembly time period depends solely on receipt of
a requisition sufficiently in advance of the support date. The number of days for
procurement lead-time and/or assembly time included in the support date is
indicated in 2/QTY/230.
PC Request or modifier accepted. Requires extra time to assemble after receipt of
requisition. The required assembly time in number of days is indicated in
2/QTY/230..
PD Cancellation accepted.
CODE EXPLANATION
PE Rejected. The request is a duplicate of a previously submitted request.
PF Rejected. Remarks listed herein or separate correspondence referring to this
document number explain reason(s) for this action.
PI USAF Request Rejected by DLA. SPR is from an Air Force activity. Per Air Force
guidance, all future forecasts to DLA should be submitted via Demand Data
Exchange. Contact the AF Global Logistics Support Center Planning for DLA
Managed Consumables Flight Office for more information. 1
PJ Rejected. Item coded (or being coded) obsolete in latest stock lists/catalogs. See
superseding item in stock number field (2/PO1/150). Resubmit under stock number
of superseding item.
PM Rejected. Request received less than 90 calendar days in advance of the support
date. Submit requisition.
PN Rejected. Source of supply is local manufacture or fabrication.
PP Rejected. Source of supply is local procurement.
PQ Rejected. Stocks not available to meet your support date. Procurement/assembly
required. Request received less than procurement lead time/assembly time in
advance of support date. Procurement lead time/ assembly time in number of days
is indicated in 2/QTY/230. Submit funded requisition.
PR SPR for which a PB Status Code was previously furnished is now within one
procurement lead time and/or assembly time of the support date. Submit
immediate requisition to continue this requirement and to allow for delivery in time
to meet support date. (See DLMS, Volume 2, Chapter 2 for SPR requisition
preparation.)
PS Rejected. The item is coded (or is being coded) as a terminal item in latest stock
lists/catalogs and has no known replacement.
PT Substitute item available. If substitute stock number shown in stock number field
(2/PO1/150) is acceptable, resubmit using SPR Substitute Item Acceptance
transaction and submit requisition in time to allow for delivery within the appropriate
UMMIPS time standard. In the event substitute item is not acceptable, resubmit
SPR Substitute Item Acceptance transaction.
PV Cancelled. Item has been logistically reassigned to the activity indicated in
2/N101/90. Submit new SPR to gaining activity.
PW This is an interim reply to your request. Manual review being made and additional
response will be furnished.
1
Refer to ADC 366, New Special Program Requirement (SPR) Status Code to Reject Air Force SPRs
Submitted for Planning for DLA Managed Consumables (PDMC) Flight
CODE EXPLANATION
PX Rejected. The item is an Acquisition Advice Code J item (centrally procured for
shipment directly to user or another service, not stocked by procuring activity).
Submit funded requisition in time to permit procurement. Procurement lead time in
days is indicated in 2/QTY/230.
PY Cancelled. Item has been changed from stocked to non-stocked by the Integrated
Materiel Manager (IMM). If still required, submit requisition for quantity required, so
that procurement action can be initiated for direct shipment.
RECORD POSITION: 60
CODE EXPLANATION
A Transaction images to be transmitted using DLA Transaction Services
methodologies for exchanging computer-readable transactions. 1
1
See DLM 4000.25-4, Defense Automatic Addressing System, for an explanation of DLA Transaction
Services methodologies for transaction exchange.
DLMS SEGMENT/QUALIFIER: DLMS 947I LQ segment, LQ01 qualifier ‘EL’ used with
W19 segment, W1901 Quantity or Status Adjustment
Reason Code ‘AA-Physical Count’
AP2.15.1. PURPOSE
AP2.15.2.1. First Position. The first character is the operation code which shall be
numeric or alphabetic and shall identify the operation during which the error occurred
and not the operation in which the error was detected. Code assignment for the first
character is controlled by DoD and may not be assigned by the Components. The
following operation codes are assigned as the first character in the error classification
code:
2 Issue 8 Other
5 Logistics Reassignments
AP2.15.2.2. Second Position. The second character is the type of error code
which is alphabetic or numeric and identifies the type of error which occurred. Code
assignment for the second character is controlled by DoD and may not be assigned by
the Services/ Agencies. The following type of error codes are assigned as the second
character in the error classification code:
D Data Entry Error Input transaction did not match source document NSN,
quantity, unit of issue, condition, type of pack, lot
number, ownership/purpose, and/or location (routing
identifier) and caused erroneous update of the property
accountability record
E Rejected Document Transaction was rejected during processing and was not
Not Posted reinput to update the property accountability record
I Not Assigned
M Materiel Selected Storage location from which materiel was selected did
From Wrong Location not match storage location cited in the transaction
N Physical Processing Not Transaction updated the property accountability record but
Complete physical processing of materiel was not completed
O Not Assigned
APPENDIX 2.16
INVENTORY ADJUSTMENT - ACCOUNTING ERROR
CLASSIFICATION CODES
AP2.16.1 PURPOSE
AP2.16.2.1 First Position. The first character shall be numeric or alphabetic and
shall identify the type of transaction during which the error occurred. Code assignment
for the first character is controlled by DoD and may not be assigned by the DoD
Components. The following operation codes are assigned as the first character in the
error classification code:
1
The owner/manager may use the Inventory Adjustment –Accounting Error Classification Codes in rp 63-
65 in DIC D8B/D9B Inventory Adjustment Transactions (Accounting Errors) pending the establishment of
single shared asset balances (see chapter 7).
CODES USED WITH MRA and select codes (A, D, E, and F) used with TRA:
CODE DEFINITION
A SDR being submitted. (Excludes shortage and partial or total nonreceipt.)
B No record of requisition. Use in MRA reply to follow-up if there is no record
of the requisition and the materiel has not been received.
C Reserved for future DoD assignment.
D Transportation discrepancy report being submitted. (Excludes shortage and
partial or total nonreceipt.)
E Product quality deficiency report being submitted.
F Shortage or partial or total nonreceipt.
When used with MRA transaction, the quantity not received is entered.
When used with TRA transaction, the quantity received is entered.
G Nonreceipt due to extended transit time. Use in MRA reply to follow-up, if
more time is needed to pick up the materiel. Only for use by Navy ships and
only when materiel is being held at a Navy Local Logistics Support Center
or Materiel Processing Center. 1
H Materiel still in transit 2
I-L Reserved for future DoD assignment.
M-T See below
U Reserved for future DoD assignment.
V MRA is based on a systemic virtual receipt. MRA is generated from virtual
receipt transaction which the Navy industrial site (Navy Shipyard/Fleet
Readiness Center) created from a Supply Status transaction (DLMS 870S)
with Status Code ‘PD’. Authorized for Navy and DLA use in MRA under
Supply, Storage and Distribution/Inventory Management and Stock
Positioning (SS&D/IMSP). Refer to ADC 372.
W Reserved for future DoD assignment.
X Discrepant receipt, other than shortage and partial or total nonreceipt, which
does not meet qualifying criteria for discrepancy report submission.
Y-Z Reserved for future DoD assignment.
1 Refer to ADC 474. As required by DODM 4140.01, the DoD Components must provide implementation
status for this approved change. Navy expected implementation by 2020/21. DLA EBS implemented
indicator G in October 2017.
2
Refer to ADC 1114.
CODE DEFINITION
M Damaged Receipt (for intra-Army use only)
N Receipt Storage (for intra-Army use only)
O Reserved for future DoD assignment
P Receipt Overage (for intra-Army use only)
Q Wrong Material (for intra-Army use only)
R Duplicate Receipt (for intra-Army use only)
S Receipt previously processed as a Materiel Receipt Discrepancy (for intra-
Army use only)
T Condemned Upon Receipt or Shelf-Life Expired (for intra-Army use only)
RECORD POSITION: 48
Type inspection codes used with MILSTRAP DIC DLX and corresponding DLMS
536L:
CODE EXPLANATION
1 Contractor.
2 Standard source inspection.
3 Inspection in accordance with ANSI/ASQC Q9000-1-1994, “Quality
Management and Quality Assurance Standards-Guidelines and Selections for
Use” (formerly MIL-I-45208A, “Military Specification Inspection System
Requirements”).
4 Inspection in accordance with ANSI/ASQC Q9000-1-1994, “Quality
Management and Quality Assurance Standards-Guidelines and Selections for
Use” (formerly MIL-Q-9858A, “Military Specification Quality Program
Requirements”).
AP 2.18.2. Type inspection codes used with DLMS 842S/Q SQCR and 842C/I Stock
Screening Request: 1
CODE DEFINITION USAGE
C Visual Inspection Monthly care of supplies in storage (COSIS) inspections.
Applicable to SQCRs only; not used on Stock Screening
Requests.
F Safety of Flight (SOF) Special inspection of SOF materiel or Aviation Safety
Inspection Action Message (ASAM).
P Special Inspection at Specific to one storage location (e.g., take picture of
Single Location materiel at specific location).
1
Refer to ADC 240 and ADC 1045. Pending implementation of ADC 1045, targeted for first quarter FY
2017, the following codes will remain available:
A Aviation Safety Action Message (ASAM)
O Outbound Shipment
T Stock Readiness
RECORD POSITION: 7
CODE EXPLANATION
1 ETD minus 120 days review period.
2 ETD minus 30 days review period.
3 ETD plus 90 days review period.
4 ETD plus 270 days review period.
Code Detail
G04 ETCHING
CODE EXPLANATION
1 Purchase request.
2 Contract.
3 Other.
RECORD POSITION: 7
CODE EXPLANATION
1 End-of-day processing
2 Annual location reconciliation request
1
The end-of-day processing and location reconciliation process will not be required with the establishment
of single shared asset balances (see Volume 2, Chapter 6).
References in this Appendix are linked to the authoritative sources from the Defense
Enterprise Data Standards Office Website pages, unless otherwise specified, for the
following publication categories.
1
Defense Federal Acquisition Regulations (DFAR) applies for structure of contract data entries
assigned/prescribed by DoD inventory control points (ICP)/integrated materiel managers (IMM). Federal
Acquisition Regulation (FAR) applies for structure of contract data entries assigned/prescribed by non-
DoD IMMs.
2
Ibid.
3
Ibid
AP3. APPENDIX 3
FORMATS INDEX
APPENDIX Document TITLE
Identifier
Code(s)
AP3 Index
AP3 Introduction
AP3.1 D4_ Materiel Receipt - Procurement Instrument Source
AP3.2 D6_ Materiel Receipt - Other Than Procurement Instrument Source
AP3.3 D7_ Issue
AP3.4 D8_, D9_ Inventory Adjustment - Increase or Decrease
AP3.5 D8E, D8F, Inventory Adjustment - Increase or Decrease (Logistics Transfer/
D9E, D9F Capitalization/Decapitalization)
AP3.6 D8S, D9S Inventory Adjustment - Increase or Decrease (Ownership Transfer)
AP3.7 DA1, DA2 Single Managed Conventional Ammunition Freeze/ Unfreeze Action
AP3.8 DAC, DAD Inventory Adjustment - Dual (Condition/Purpose Transfer)
AP3.9 DAS Inventory Adjustment - Dual (Ownership Transfer)
AP3.10 DD_ Due-In - Procurement Instrument Source
AP3.11 DEE, DEF Logistics Transfer/Decapitalization
AP3.12 DF_ Due-In - Other Than Procurement Instrument Source
AP3.13 DG_ Backorder
AP3.14 DHA Demand
AP3.15 DJA Physical Inventory Request
AP3.16 DLA Logistics Transfer/Decapitalization Follow-up
AP3.17 DLB Reply To Logistics Transfer/Decapitalization Follow-up
AP3.18 DLC Logistics Reassignment Delinquent Due-In Follow-Up
AP3.19 DLD Logistics Reassignment Delinquent Due-In Response
AP3.20 DLE Logistics Reassignment Due-In Reconciliation Request
AP3.21 DLF Logistics Reassignment Due-In Reconciliation Response
AP3.22 DLS Logistics Reassignment General Management Data
AP3.23 DLT Logistics Reassignment Backorder and Demand Data
AP3.24 DLU Logistics Reassignment On-Hand Asset Data
AP3.25 DLV Logistics Reassignment Due-In Asset Data
AP3-i APPENDIX 3
DLM 4000.25, Volume 2, November 26, 2019
Change 13
APPENDIX Document TITLE
Identifier
Code(s)
AP3.26 DLW Logistics Reassignment Contract History Data
AP3.27 DLX Logistics Reassignment Technical and Quality Data
AP3.28 DM_ War Materiel Requirements Data
AP3.29 DRA, DRB Materiel Receipt Acknowledgment
AP3.30 DRF Follow-Up For Delinquent Materiel Receipt Acknowledgment
AP3.31 DSA Small Arms Multi-Field Corrections
AP3.32 DSB Small Arms Mass Stock Number Change
AP3.33 DSC Small Arms Correction
AP3.34 DSD Small Arms Receipt/Shipment Follow-Up
AP3.35 DSF Small Arms Reconciliation/Reject Follow-Up
AP3.36 DSM Weapon Serial Number Control
AP3.37 DSR Small Arms Reconciliation/Reject
AP3.38 DU_ Pre-Positioned Materiel Receipt - Procurement Instrument Source
AP3.39 DW_ Pre-Positioned Materiel Receipt - Other Than Procurement
Instrument Source
AP3.40 DXA Materiel Receipt Follow-Up - Procurement Instrument Source
AP3.41 DXB Materiel Receipt Follow-Up - Other Than Procurement Instrument
Source
AP3.42 DXC Reply To Materiel Receipt Follow-Up - Procurement Instrument
Source
AP3.43 DXD Reply To Materiel Receipt Follow-Up - Other Than Procurement
Instrument Source
AP3-ii APPENDIX 3
DLM 4000.25, Volume 2, November 26, 2019
Change 13
APPENDIX Document TITLE
Identifier
Code(s)
AP3.54 DZC Logistics Reassignment Storage Information
AP3.55 DZD Logistics Reassignment Storage Information Reply
AP3.56 DZE Asset Status Reporting Request
AP3.57 DZF Asset Status Reporting (Base, Post, Camp, and Station Level Use)
AP3.58 DZG Transaction Reject
AP3.59 DZH Location Reconciliation Request
AP3.60 DZJ Transaction History Request
AP3.61 DZK Transaction History Transmittal
AP3.62 DZM End of Day Transaction Count
AP3.63 DZN Location Reconciliation Notification
AP3.64 DZP Location Reconciliation History Notification
AP3-iii APPENDIX 3
DLM 4000.25, Volume 2, November 26, 2019
Change 13
AP3. APPENDIX 3
FORMATS INTRODUCTION
AP3.1. General. The AP3 series appendices prescribe the alignment and data
entries for the MILSTRAP formats.
AP3-1 APPENDIX 3
DLM 4000.25, Volume 2, November 26, 2019
Change 13
AP3.3.3. When all data elements, other than quantity, are identical and the
quantity due-in or being adjusted exceeds 99,999 or 9999M (M-Modifier thousands -
and residual quantities are for ammunition); or when all data elements are the same,
except the condition of materiel, for materiel being received or being adjusted;
assign consecutive suffix codes in record position 44 beginning with alpha code A in
the initial transaction; otherwise, leave blank.
AP3.3.4. Date Indicator is a three-position field used to identify the year and
month (e.g., 305 is year 2003, month of May). Date indicators refer to the last day of
the month unless otherwise noted in the transaction. The Date Indicators in special
program requirement (SPR) transactions refer to the first day of the month as noted
in the formats.
AP3-2 APPENDIX 3
DLM 4000.25, Volume 2, November 26, 2019
Change 13
AP3.4.2. Day. The term Julian day is not recognized for data element
terminology. Accordingly, all instructions covering the entry of a 3-digit day refer to
the ordinal day of the calendar year. For instance, 25 February shall be entered as
056 and 14 July would be entered as 195 or 196 in a leap year.
AP3-3 APPENDIX 3
DLM 4000.25, Volume 2, November 26, 2019
Change 13
or
Due-In Document (30-43) For intra-Component use only, enter (or
Number perpetuate due-in document number.
1
See Appendix AP3 - Formats Introduction, AP3.3.1.
2
See Appendix AP3 - Formats Introduction, AP3.3.2.
3
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
4
Ibid.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
5
See Appendix AP3 - Formats Introduction, AP3.3.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter appropriate DIC from the D6 series.
Code
Routing Identifier 4-6 Enter (or perpetuate) the RIC of the
Code (TO) Inventory Control Point to which this
transaction is being forwarded.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number of item received.
Unit of Issue 23-24 Enter UI of item.
Quantity (Received) 25-29 Enter quantity received, preceding
significant digits with zeros. 1, 2
Document Number 30-43 Enter controlling document number.
Suffix 44 Enter consecutive alpha codes A through Z
when assignments of suffix codes are
necessary. 3
Supplementary 45-50 Enter (or perpetuate) SUPADD; otherwise,
Address leave blank.
Signal 51 Enter (or perpetuate) the signal code;
otherwise, leave blank.
Fund 52-53 Enter (or perpetuate) fund code; otherwise,
leave blank.
Distribution 54-56 Enter (or perpetuate) distribution code;
otherwise, leave blank.
Project 57-59 Enter (or perpetuate) project code;
otherwise, leave blank.
1
See Appendix AP3 - Formats Introduction, AP3.3.1.
2
See Appendix AP3 - Formats Introduction, AP3.3.2.
3
See Appendix AP3 - Formats Introduction, AP3.3.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Dual-Use 60-66
4
For intra-Army use, rp 60-61 identifies the priority designator. (Refer to ADC 234.)
5
For intra-Army use, rp 65-66 identifies the advice code. (Refer to ADC 234.)
6
For intra-Air Force use, rp 60-65 identifies the Ship-From DoDAAC for use in Air Force retail receipts of
shipments from Air Force retail activities. (Refer to ADC 1185.)
7
Refer to ADC 218.
8
On an intra-Army basis, Army sometimes uses D6X for their Direct Support/Reparable Exchange
process by citing X in rp 73 with rp 74-75 blank. This is a temporary deviation from standard processing
in place until implementation of Army Exchange Pricing (estimated to be April 2009). (Refer to ADC 267.)
9
For Navy CAV-ORM DIC D6K, rp 76-78 identifies the Shipper RIC.
10
For intra-Army use only, rp 80 identifies the discrepancy indicator code (see appendix 2.17). (Refer to
ADC 272.)
2
See Appendix AP3 - Formats Introduction, AP3.3.2.
3
For Navy, rp 77 identifies the “issue on request” code. Navy uses when a customer receives material
without a material release order and DSS sends a D7_ (with an “I” in position 77) to Navy systems (e.g.,
Uniform Inventory Control Program (UICP)) to indicate that material has been issued. (See ADC 235)
4
For Navy, rp 80 identifies the Issue Reversal Code B or S per legacy requirements. (See ADC 259.)
5
Implementation staggered. Refer to ADC 1160.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Distribution 54-56 Enter appropriate distribution code if stocks
are segregated and maintained by codes
reflected in the distribution field; otherwise,
leave blank.
Project 57-59 Enter appropriate project code if stocks are
segregated and maintained by code
reflected in the project field; otherwise, leave
blank.
Multiuse 60-62 For intra-Component use, enter data
prescribed by Component. For inter-
Component use, leave blank.
Dual Use 63-65
Error Classification (63-64) For DIC D8A and D9A, enter appropriate
DoD assigned physical inventory error
classification code from Appendix 2.15,
otherwise, leave blank.
For DIC D8B and D9B enter appropriate
DoD assigned accounting error classification
code from Appendix 2.16, otherwise, leave
blank.
(65) For DIC D8A/D9A and D8B/D9B, enter
Component assigned code amplifying the
DoD error classification code; otherwise,
leave blank.
or
Multiuse (63-65) For intra-Component use with DIC other
than D8A/D9A or D8B/D9B, enter data
prescribed by Component. For inter-
Component use except for DIC D8A/D9A or
D8B/D9B, leave blank.
Multiuse 66 For intra-Component use, enter data
prescribed by Component.
For inter-Component use, leave blank.
Routing Identifier 67-69 Enter RIC of the storage activity at which
Code (Storage item is stored.
Activity)
Ownership/Purpose 70 Enter appropriate ownership/purpose code,
if applicable.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Supply Condition 71 Enter supply condition code of inventory
balance being affected.
Management 72 Enter appropriate management code;
otherwise, leave blank.
Day of Year 73-75 Enter the ordinal day of the calendar year on
which the adjustment is processed by the
initiating activity.
Multiuse 76-80 For intra-Component use, enter data
prescribed by Component. For inter-
Component use, leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2.
3
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2.
3
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.3.
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2.
3
For intra-DLA use only, if DAC is applicable to Supply Condition Code (SCC) L, enter the Procurement
Instrument Identifier (PIID) in rp 30-42.
4
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.3.
5
For intra-DLA use only, if DAC is applicable to SCC L, enter the intra-DLA Contract Line Item Number in
rp 45-50.
6
Ibid
7
Cannot change ownership code with DIC DAC or DAD. Must use appropriate issue and receipt
transactions to change ownership.
8
Ibid.
9
Air Force enters the existing numeric ownership code in rp 70 for the DAC transaction. Refer to ADC
1149.
10
Refer to ADC 461
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2.
3
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.3.
2
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2.
3
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
4
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.3.
5
For DIC DDX, DLA enters the supply condition code in rp 71 on an inter-Component basis based upon
trading partner agreement. All DOD Components must implement use of SCC with DLMS 527D due-in
transaction corresponding to MILSTRAP DIC DD_ functionality, in their modernized systems. MILSTRAP
DIC DD_ corresponds to DLMS 527D with beginning segment Transaction Type Code DA and use of CS
segment for contract number or purchase request number. DLMS 527D for MILSTRAP DIC DDX
functionality includes LIN01 code T. Refer to ADC 423.
6 See Appendix AP3 - Formats introduction, Paragraph AP3.3.4.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DEE or DEF, as appropriate.
Code
Routing Identifier 4-6 Enter RIC of the Inventory Control Point
Code (TO) (ICP) to which this transaction is being
forwarded.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number of item being
transferred.
Unit of Issue 23-24 Enter UI of item.
Quantity 25-29 Enter quantity being transferred/
(Transfer/ decapitalized, preceding significant digits
Decapitalization) with zeros. 1 / 2
Document Number 30-43 Enter current document number of the losing
ICP using consecutive numbers for each
different inventory record control balance.
Suffix 44 Enter consecutive suffix code (beginning
with the letter A in the initial transaction)
when quantity for inventory control record
balance exceeds 99,999.
Routing Identifier 45-47 Enter RIC of the losing ICP.
Code (Losing)
Blank 48-53 Leave blank.
Distribution 54-56 Enter distribution code if stocks are
segregated and maintained by codes
reflected in the distribution field; otherwise,
leave blank.
Multiuse 57-61 For intra-Component use, enter data
prescribed by Component. For inter-
Component use, leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Day of Year 62-64 Enter the effective day (ordinal day of the
(Effective) calendar year) of the logistic transfer or
decapitalization.
Ownership/Purpose 65 To be used by gaining Inventory Control
Point (ICP).
Supply Condition 66 To be used by gaining ICP.
Routing Identifier 67-69 Enter RIC of the storage activity at which
Code (Storage item is stored.
Activity)
Ownership/Purpose 70 Enter appropriate ownership/purpose code
of the balance being transferred/
decapitalized.
Supply Condition 71 Enter supply condition code of the balance
being transferred/decapitalized.
Multiuse 72 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
Blank 73 Leave blank. 3
Unit Price 74-80 Enter unit price in effect for valuing the
inventory. (For transfers within a
Component, this field may be left blank.)
3
For intra-DLA use only, enter the intra-DLA logistics reassignment price type indicator when applicable;
otherwise leave blank. (See ADC 125.)
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2.
3
For intra-Army use, rp 60-61 identifies the priority designator. (See ADC 234.)
4
For intra-Army use, rp 65-66 identifies the advice code. (See ADC 234.)
5
Priority Designator is identified in Army Regulation (AR) for intra-Army use in rp 60-61.
6
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.4.
1
See Appendix AP3 – formats introductions, paragraph AP3.3.1.
2
See Appendix AP3 – formats introductions, paragraph AP3.3.2.
RECORD
FIELD LEGEND POSITION ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DHA.
Code
Routing Identifier Code 4-6 Enter RIC of the Inventory Control Point
(TO) (ICP) to which this transaction is being
forwarded.
Media and Status 7 Enter M&S code from source document.
Stock or Part Number 8-22 Enter stock or part number from source
document.
Unit of Issue 23-24 Enter UI of item.
Quantity 25-29 Enter quantity of the demand, preceding
significant digits with zero. 1 / 2
Document Number 30-43 Enter document number from source
document.
Suffix 44 Enter assigned suffix code; otherwise, leave
blank.
Supplementary 45-50 Perpetuate from source document.
Address
Signal 51 Perpetuate from source document.
Fund 52-53 Perpetuate from source document.
Distribution 54-56 Perpetuate from source document.
Project 57-59 Perpetuate from source document.
Priority 60-61 Perpetuate from source document.
Day of Year (Delivery) 62-64 Perpetuate from source document.
Advice 65-66 Perpetuate from source document.
Routing Identifier Code 67-69 Enter RIC of the storage activity from which
(Storage Activity) the item should have been shipped. (Leave
blank on submission to ICP.)
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2.
AP3.14-1 AP3.14
DLM 4000.25, Volume 2, November 26, 2019
Change 13
RECORD
FIELD LEGEND POSITION ENTRY AND INSTRUCTIONS
Blank 70-71 Leave blank.
Management 72 Enter management code; otherwise, leave
blank.
Day of Year 73-75 Enter ordinal day of the calendar year on
(Transaction) which the transaction is processed.
Blank 76-80 Leave blank.
AP3.14-2 AP3.14
DLM 4000.25, Volume 2, November 26, 2019
Change 13
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DJA.
Code
Routing Identifier 4-6 Enter RIC of the activity to which this
Code (TO) transaction is being forwarded.
Type of Physical 7 Enter appropriate type of inventory/transaction
Inventory/Transaction history code.
History
Stock or Part Number 8-22 Enter stock or part number of item to be
counted.
Unit of Issue 23-24 Enter UI of item.
Blank 25-34 Leave blank.
Date (Physical 35-38 Enter the ordinal date established for initiating
Inventory Infloat controls on all in-process transactions and
Control) materiels which could affect the outcome of
the inventory.
Blank 39-43 Leave blank.
Multiuse 44-46 For inter-Component use, when agreed by the
Components involved, enter the lot/segment
number for controlling the inventory;
otherwise, leave blank. For intra-Component
use, enter the data prescribed by the
Component.
Blank 47-53 Leave blank.
Distribution 54-56 Enter distribution code if stocks are
segregated and maintained by codes reflected
in the distribution field; otherwise, leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Multiuse 65-66 For intra-Component transactions, enter the
data prescribed by the Component. For inter-
Component use, leave blank.
Routing Identifier 67-69 Enter RIC of the activity from which this
Code (FROM) transaction is being forwarded.
Ownership/Purpose 70 Enter the ownership/purpose code if stocks
are segregated and maintained by codes
reflected in the ownership/purpose field;
otherwise, leave blank.
Supply Condition 71 Enter the applicable supply condition code of
the item to be counted when Type of Physical
Inventory/Transaction History Code L, N, and
P is entered in record position 7; otherwise,
leave blank.
Management 72 Enter management code; otherwise, leave
blank.
Blank 73-75 Leave blank.
Multiuse 76-78 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
Dual Use 79-80
Multiuse (79-80) For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
or
Subsistence Type (79) For Subsistence Items Only: Enter the
of Pack applicable subsistence type of pack code (see
MILSTRIP).
Blank (80) For Subsistence Items Only: Leave blank.
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
1
See Appendix AP3 – formats introductions, paragraph AP3.3.1.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLS.
Code
Routing Identifier Code 4-6 Enter RIC identifying the gaining item
(TO) manager to which the transaction is being
forwarded.
Review Period Indicator 7 Enter review period indicator 1 or 2 in
accordance with appendix AP2.19.
National Stock Number 8-20 Enter NSN of item being transferred.
Blank 21-23 Leave blank.
Routing Identifier Code 24-26 Enter RIC identifying the losing item
(FROM) manager preparing the transaction.
Date (Extracted) 27-31 Enter date data was extracted from files.
(Enter two-digit year in record positions
27-28 and three-digit ordinal day in record
positions 29-31).
Unit Cube 32-38 Enter the actual maximum cube of unit
pack in feet (rounded to three decimals);
otherwise, leave blank.
Unit Weight 39-43 Enter maximum gross weight of unit pack
in pounds (rounded to two decimals);
otherwise, leave blank.
Date (Last Buy) 44-48 Enter date of last purchase request
initiation (enter two-digit year in record
positions 44-45 and three- digit ordinal day
in record positions 46-48); otherwise,
leave blank.
Date (Last Demand) 49-53 Enter date last demand was recorded
(enter two-digit year in record positions
49-50 and three-digit ordinal day in record
positions 51-53); otherwise, leave blank.
RECORD 1
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Quantity (Total 55-63 Enter sum of recurring and nonrecurring
Demand) demand quantities (previous four quarters);
otherwise, leave blank.
Total Demand 64-72 Enter total frequency of recurring and
Frequency Count nonrecurring demands (previous four
quarters); otherwise leave blank.
Quantity (Reorder 73-80 Enter the computed reorder point quantity;
Point Level) otherwise, leave blank.
RECORD 2
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLT.
Code
Routing Identifier 4-6 Enter RIC identifying the GIM to which the
Code (TO) transaction is being forwarded.
Blank 7 Leave blank.
National Stock 8-20 Enter NSN of item being transferred.
Number
Package Sequence 21-23 Enter A02 on this record and increment by
Number one (i.e., A03, A04, etc.) for each additional
record. On the last record, enter Z and the
appropriate two position sequence number.
If only this record is required, enter Z02.
Quantity (1st Quarter 24-32 Enter total recurring demand quantity;
Recurring Demand) otherwise leave blank.
1st Quarter Recurring 33-37 Enter total recurring demand frequency;
Demand Count otherwise leave blank.
Quantity (1st Quarter 38-46 Enter total nonrecurring demand quantity;
Nonrecurring otherwise leave blank.
Demand)
1st Quarter 47-51 Enter total nonrecurring demand frequency;
Nonrecurring Demand otherwise leave blank.
Count
Blank 52 Leave blank.
Quantity (2d Quarter 53-61 Enter total recurring demand quantity;
Recurring Demand) otherwise leave blank.
2d Quarter Recurring 62-66 Enter total recurring demand frequency;
Demand Count otherwise leave blank.
Quantity (2d Quarter 67-75 Enter total nonrecurring demand quantity;
Nonrecurring otherwise leave blank.
Demand)
2d Quarter 76-80 Enter total nonrecurring demand frequency;
Nonrecurring Demand otherwise leave blank.
Count
RECORD 3
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLT.
Code
Routing Identifier 4-6 Enter RIC identifying the GIM to which the
Code (TO) transaction is being forwarded.
Blank 7 Leave blank.
National Stock 8-20 Enter NSN of item being transferred.
Number
Package Sequence 21-23 Enter the next sequence number for this DIC
Number and NSN. On the last record, enter Z and
the appropriated two-positoin sequence
number
Quantity (3d Quarter 24-32 Enter total recurring demand quantity;
Recurring Demand) otherwise leave blank.
3d Quarter Recurring 33-37 Enter total recurring demand frequency;
Demand Count otherwise leave blank.
Quantity (3d Quarter 38-46 Enter total nonrecurring demand quantity;
Nonrecurring otherwise leave blank.
Demand)
3d Quarter 47-51 Enter total nonrecurring demand frequency;
Nonrecurring Demand otherwise leave blank.
Count
Blank 52 Leave blank.
Quantity (4th Quarter 53-61 Enter total recurring demand quantity;
Recurring Demand) otherwise leave blank.
4th Quarter Recurring 62-66 Enter total recurring demand frequency;
Demand Count otherwise leave blank.
Quantity (4th Quarter 67-75 Enter total nonrecurring demand quantity;
Nonrecurring otherwise leave blank.
Demand)
4th Quarter 76-80 Enter total nonrecurring demand frequency;
Nonrecurring Demand otherwise leave blank.
Count
RECORD 41
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLT.
Code
Routing Identifier 4-6 Enter RIC identifying the GIM to which the
Code (TO) transaction is being forwarded.
Blank 7 Leave blank.
National Stock 8-20 Enter NSN of item being transferred.
Number
Package Sequence 21-23 Enter the next sequence number for this DIC
Number and NSN. On the last record, enter Z and
the appropriate two position sequence
number.
Provisioning Item 24 Enter y or N; otherwise, leave blank.
Date (Provisioning 25-29 Enter date provisioning item is required;
Item Requirement) otherwise leave blank. Enter two-digit year
in record positions 25-26 and three-digit
ordinal day in record position 27-29.
Life of Type Buy 30 Enter Y or N; otherwise, leave blank.
Diminishing 31 Enter Y or N; otherwise leave blank.
Manufacturing Source
Item
Quantity 32-40 Enter procurement cycle quantity if
(Procurement Cycle) available; otherwise, leave blank.
Quantity (Economic 41-49 Enter economic order quantity if available;
Order) otherwise leave blank.
Quantity (Price Break; 50-58 Enter total quantity of all buys for price buy;
Life of Type Buy, and life of type buy; and minimum buy quantities;
Minimum Buy otherwise, leave blank.
1
DLT Record 4 is optional and intended for use only by DoD Components which implemented Record 4
in their legacy systems in the 1990s. DLA, Air Force, and Navy are known to have implemented Record
4 in the 1990s. Any DoD Component that has not previously implemented DIC DLT record 4 should NOT
revise their legacy systems to do so.
RECORD 41
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Quantity (Numeric 59-67 Enter total quantity of all buys from numeric
Stockage Objective stockage objective quantity and insurance
and Insurance) quantity, only is not included in reorder point
quantity computation; otherwise, leave
blank.
Quantity (Funded 68-76 Enter funded planned requirement quantity
Planned Requirement) not included in reorder point quantity
computation; otherwise, leave blank.
Blank 78-80 Leave Blank.
RECORD 1
RECORD
FIELD LEGEND POSITION ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLU.
Code
Routing Identifier 4-6 Enter RIC identifying the gaining item
Code (TO) manager to which the transaction is being
forwarded.
Review Period 7 Enter review period indicator 1 or 2 in
Indicator accordance with appendix AP2.19.
National Stock 8-20 Enter NSN of item being transferred.
Number
Package Sequence 21-23 To sequence the records, enter A01 if more
Number than one record is required for this DIC and
NSN. Enter Z01 if only one record is
required.
Routing Identifier 24-26 Enter RIC identifying the losing item
Code (FROM) manager preparing the transaction.
Date (Extracted) 27-31 Enter date data was extracted from files.
(Enter two-digit year in record positions
27-28 and three-digit ordinal day in record
positions 29-31).
Quantity (Total 32-41 Enter the total quantity of onhand wholesale
Onhand Wholesale assets (all locations); otherwise, leave blank.
Assets)
Blank 42-46 Leave blank.
Quantity (Onhand 47-56 Enter onhand wholesale quantity;
Wholesale) Wholesale) otherwise, leave blank. 2
1
The DIC DLU records convey the total onhand wholesale assets. The records provide the individual
quantities, by ownership/purpose and supply condition, at each storage activity. The sum of all assets
reported for individual locations are to equal the total quantity in record positions 32-41. When an
individual quantity is entered, the routing identifier code, ownership/purpose code, and supply condition
code for that quantity must be entered; otherwise all four fields are left blank.
2
The DIC DLU records convey the total onhand wholesale assets. The records provide the individual
quantities, by ownership/purpose and supply condition, at each storage activity. The sum of all assets
reported for individual locations are to equal the total quantity in record positions 32-41. When an
RECORD 1
RECORD
FIELD LEGEND POSITION ENTRY AND INSTRUCTIONS
Routing Identifier 57-59 Enter RIC of the storage location; otherwise,
Code (Storage leave blank.2
Location)
Ownership/Purpose 60 Enter ownership/purpose code; otherwise,
leave blank.2
Supply Condition 61 Enter supply condition code; otherwise,
leave blank. 2
Quantity (Onhand 62-71 Enter onhand wholesale quantity; otherwise,
Wholesale) leave blank. 2
Routing Identifier 72-74 Enter RIC of the storage location; otherwise,
Code (Storage leave blank. 2
Location)
Ownership/Purpose 75 Enter ownership/purpose code; otherwise,
leave blank. 2
Supply Condition 76 Enter supply condition code; otherwise,
leave blank.2
Blank 77-80 Leave blank.
individual quantity is entered, the routing identifier code, ownership/purpose code, and supply condition
code for that quantity must be entered; otherwise all four fields are left blank.
RECORD 2
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLU.
Code
Routing Identifier 4-6 Enter RIC identifying the GIM to which the
Code (TO) transaction is being forwarded.
Blank 7 Leave blank.
National Stock 8-20 Enter NSN of item being transferred.
Number
Package Sequence 21-23 Enter A02 on this record and increment by
Number one (i.e. A03, A04, etc.) for each additional
record. On the last record, enter Z and the
appropriate two position sequence number.
If only this record is required, enter Z02.
3
The DIC DLU records convey the total onhand wholesale assets. The records provide the individual
quantities, by ownership/purpose and supply condition, at each storage activity. The sum of all assets
reported for individual locations are to equal the total quantity in record positions 32-41. When an
individual quantity is entered, the routing identifier code, ownership/purpose code, and supply condition
code for that quantity must be entered; otherwise all four fields are left blank.
4
The DIC DLU records convey the total onhand wholesale assets. The records provide the individual
quantities, by ownership/purpose and supply condition, at each storage activity. The sum of all assets
reported for individual locations are to equal the total quantity in record positions 32-41. When an
individual quantity is entered, the routing identifier code, ownership/purpose code, and supply condition
code for that quantity must be entered; otherwise all four fields are left blank.
RECORD 1
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLV.
Code
Routing Identifier 4-6 Enter RIC identifying the gaining item
Code (TO) manager (GIM) to which this transaction is
being forwarded.
Review Period 7 Enter review period indicator 1 or 2 in
Indicator accordance with appendix AP2.19.
National Stock 8-20 Enter NSN of item being transferred.
Number
Package Sequence 21-23 To sequence the records, enter A01 if more
Number than one record is required for this DIC and
NSN. Enter Z01 if only one record is
required.
Routing Identifier 24-26 Enter RIC identifying the losing item
Code (FROM) mamanger preparing the transaction.
Date (Extracted) 27-31 Enter date data was extracted from files.
Enter two-digit year in record positions
27-28 and three digit ordinal date in record
positions 29-31.
Quantity (Total Due-In 32-41 Enter the total due-in wholesale quantity;
Wholesale) otherwise, leave blank.1
Blank 42-49 Leave blank.
Quantity (Due-In 50-58 Enter due-in wholesale quantity; otherwise,
Wholesale) leave blank.1
1
The DIC DLV records convey the total due-in wholesale assets. The records provide the individual
quantities due-in at each storage activity by due-in date and due-in indicator. The sum of all the due-in
quantities for the individual locations are to equal the total quantity in record 1, record positions 32-41.
When an individual quantity is entered, the RI code, due-in date and due-in indicator for that quantity
must be entered; otherwise all four fields are left blank.
RECORD 1
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Routing Identifier 59-61 Enter RIC of the storage location; otherwise,
Code (Storage leave blank. 2
Location)
Date (Due-In) 62-66 Enter due-in date; otherwise, leave blank.2
67 Enter type due-in indicator in accordance
Type Due-In Indicator
with appendix AP2.22; otherwise, leave
blank.2
Blank 68-80 Leave blank.
2
The DIC DLV records convey the total due-in wholesale assets. The records provide the individual
quantities due-in at each storage activity by due-in date and due-in indicator. The sum of all the due-in
quantities for the individual locations are to equal the total quantity in record 1, record positions 32-41.
When an individual quantity is entered, the RI code, due-in date and due-in indicator for that quantity
must be entered; otherwise all four fields are left blank.
RECORD 2
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLV.
Code
Routing Identifier 4-6 Enter RIC identifying the GIM to which the
Code (TO) transaction is being forwarded.
Blank 7 Leave blank.
National Stock 8-20 Enter NSN of item being transferred.
Number
Package Sequence 21-23 Enter A02 on this record and increment by
Number one (i.e. A03, A04, etc.) for each additional
record. On the last record, enter Z and
appropriate two position sequence number.
If only this record is required, enter Z02.
Blank 24-31 Leave blank.
Quantity (Due-In 32-40 Enter due-in wholesale quantity; otherwise,
Wholesale) leave blank.2
Routing Identifier 41-43 Enter RIC of the storage location; otherwise,
(Storage Location) leave blank.2
Date (Due-In) 44-48 Enter due-in date; otherwise, leave blank. 3
3
The DIC DLV records convey the total due-in wholesale assets. The records provide the individual
quantities due-in at each storage activity by due-in date and due-in indicator. The sum of all the due-in
quantities for the individual locations are to equal the total quantity in record 1, record positions 32-41.
When an individual quantity is entered, the RI code, due-in date and due-in indicator for that quantity
must be entered; otherwise all four fields are left blank.
RECORD 2
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
blank.3
Blank 68-80 Leave blank.
RECORD 1
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLW.
Code
Routing Identifier 4-6 Enter RIC identifying the gaining item
Code (TO) manager (GIM) to which the transaction is
being forwarded.
Review Period 7 Enter appropriate review period indicator in
Indicator accordance with appendix B26.
National Stock 8-20 Enter NSN of item being transferred.
Number
Package Sequence 21-23 Enter A01 indicating first record for this
Number procurement instrument. If record position
24 = N, enter Z01.
1
Review periods subsequent to the ETD-120 days are to include updated information. If updated
transactions have blank spaces, the blank spaces will not overlay any data in the file.
2
If record position 24 is N, record positions 25-80 will be blank.
RECORD 1
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Contract Unit Price 52-61 Enter CLIN unit price from award to four
decimals; zero fill left and right. For
example, enter 0000127500 for $12.75. 3 / 4
Price Status 62 Air Force, Navy and Marine Corps enter E
for estimated or A for actual.
Army enter price status code in accordance
with appendix E of DoD MILSCAP as
follows:
E = has price listed;
U = unavailable;
N = not applicable;
C = not separately priced;
9 = MILS exceeds two positions;
blank = firm fixed price (equal to A for
actual).3
Date (Transmitted) 63-67 Enter date data was transmitted. Enter two-
digit year in record positions 63-64 and
three-digit ordinal day in record positions 65-
67.3
Blank 68-70 Leave blank.
Date (Award) 71-75 Enter contract award date or effective date.
Enter two-digit year in record positions 71-
72 and three-digit ordinal day in record
positions 73-75.3
Routing Identifier 76-78 Enter RIC identifying the losing item
Code (FROM) manager preparing the transaction.3
Blank 79-80 Leave blank.
3
If record position 24 is N, record positions 25-80 will be blank.
4
If record position 62 is U, N, C, or 9, zero fill record positions 52-61. If record position 62 is E or blank,
enter contract unit price in record positions 52-61.
RECORD 2
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLW.
Code
Routing Identifier 4-6 Enter RIC identifying the GIM to which the
Code (TO) transaction is being forwarded.
Review Period 7 Enter appropriate review period indicator in
Indicator accordance with appendix AP2.19.
National Stock 8-20 Enter NSN of item being transferred.
Number
Package Sequence 21-23 Enter A02 indicating second record for this
Number procurement instrument.
Blank 24 Leave blank.
Procurement 25-37 Enter the PIID or the applicable 13-position
Instrument Identifier call/order number (identified by F in the 9th
(PIID) position).
Supplementary 38-43 Enter the six-position supplementary PIID;
Procurement otherwise, leave blank.
Instrument Identifier
(PIID)
Contract Line Item 44-49 Enter CLIN or contract subline item number.
Number or Contract Not mandatory for GSA.
Subline Item Number
Contractor/Supplier 50-58 Enter CAGE code of awardee, right justify
Commercial and and fill left with zeros. For GSA enter Data
Government Entity Universal Numbering System number.
Quantity (Delivered) 59-69 Enter total quantity delivered on CLIN or
contract subline item number.
Blank 70-78 Leave blank.
Type of Business 79 Enter type of business code; otherwise,
leave blank.
RECORD 2
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Type of Contractor 80 Enter code indicating type of contractor;
otherwise leave blank. This may be the only
descriptive data available if Type of
Business code is not available. (The type of
contractor code is obsolete and is no longer
published in MILSCAP. It was replaced by
the type of business code. This code is
temporarily published in MILSTRAP,
appendix AP2.21 only for convenience in
interpreting this field when data is entered in
this transaction.)
RECORD 3
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLW
Code
Routing Identifier 4-6 Enter RIC identifying the GIM to which the
Code (TO) transaction is being forwarded.
Review Period 7 Enter appropriate review period indicator in
Indicator accordance with appendix AP2.19.
National Stock 8-20 Enter NSN of item being transferred.
Number
Package Sequence 21-23 Enter A03 indicating third record for this
Number procurement instrument.
Blank 24 Leave blank.
Procurement 25-37 Enter the PIID or the applicable 13-position
Instrument Identifier call/order number (identified by F in the 9th
position).
Supplementary 38-43 Enter the six-position supplementary PIID;
Procurement otherwise, leave blank.
Instrument Identifier
(PIID)
Contract Line Item 44-49 Enter CLIN or contract subline item number.
Number or Contract Not mandatory for GSA.
Subline Item Number
Manufacturer's 50-76 Enter manufacturer's part number being
Reference or Part supplied; otherwise, leave blank. Do not
Number include Original Equipment Manufacturer
(OEM) CAGE code.
Blank 77-80 Leave blank.
RECORD 4
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLW.
Code
Routing Identifier 4-6 Enter RIC identifying the GIM to which the
Code (TO) transaction is being forwarded.
Review Period 7 Enter appropriate review period indicator in
Indicator accordance with appendix AP2.19.
National Stock 8-20 Enter NSN of item being transferred
Number
Package Sequence 21-23 Enter Z04 indicating last record for this
Number Procurement Instrument. 5
Blank 24 Leave blank.
Procurement 25-37 Enter the PIID or the applicable 13-position
Instrument Identifier call/order number (identified by F in the 9th
position).
Supplementary 38-43 Enter the six-position supplementary PIID;
Procurement otherwise, leave blank.
Instrument Identifier
(PIID)
Contract Line Item 44-49 Enter CLIN or contract subline item number.
Number (CLIN) or Not mandatory for GSA.
Contract Subline
Item Number
Design Contractor 50-54 Enter CAGE code of OEM or design control
and Government activity; otherwise, leave blank.
Entity
Quantity Variance 55-56 Enter percentage of positive variance
Positive allowed; otherwise, leave blank.
Quantity Variance 57-58 Enter percentage of negative variance
Negative allowed; otherwise, leave blank.
5
Package Sequence Number Z04 indicates that all contract history data for the PIIN/supplementary
PIIN/CLIN, entered in record positions 25-49 of the Package Sequence Number A01 record, has been
identified. If there are additional contract history records for this NSN, continue preparation of DIC DLW
for up to a maximum of 25 submissions per NSN.
RECORD 4
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Contract 59-64 Enter contract administration services code
Administration component's DoD activity address (see DoD
Services Component 4140.59H); otherwise, leave blank. For
Identifier GSA one position, right justify, zero fill.
Enter L if locally administered.
Competitive 65 Enter competitive characteristics code;
Characteristics otherwise leave blank. (This code is
obsolete and is no longer published in
DFARS. This code is temporarily published
in MILSTRAP, appendix AP2.20, only for
convenience in interpreting this field when
data is entered in this transaction.)
Criticality Designator 66 Enter criticality designator code; otherwise,
leave blank.
Acquisition Method 67 Enter acquisition method code at time of
award; otherwise, leave blank.
Acquisition Method 68 Enter acquisition method suffix code at
Suffix Suffix time of award; otherwise, leave blank.
Date (Shipped) 69-73 If active record and date is available, enter
date of last shipment for this CLIN or zero fill
if no shipment has been made. If purged
record, enter contract physically completed
date. For GSA enter last receipt date.
(Enter two-digit year in record positions
69-70 and three-digit ordinal day in record
positions 71-73.)
Date (Original 74-78 Enter original contract delivery date
Contract Delivery) Contract if available. Air Force will enter
last delivery date when multiple deliveries
per CLIN or contract subline item number. If
original contract delivery date is not
available, Army will enter contract physically
completed date; Navy will enter date of last
shipment or zeros if no date is available.
(Enter two-digit year in record positions
74-75 and three-digit ordinal day in record
positions 76-78.)
RECORD 4
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Type of Contract 79 Enter type of contract code; otherwise,
leave blank.
Blank 80 Leave blank.
RECORD 1
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLX.
Code
Routing Identifier Code 4-6 Enter RIC identifying the gaining item
(TO) manager (GIM) to which the transaction is
being forwarded.
Review Period 7 Enter appropriate review period indicator in
Indicator accordance with appendix AP2.19.
National Stock Number 8-20 Enter NSN of item being transferred.
Package Sequence 21-23 To sequence the records, enter A01 if more
Number than one record is required for this DIC and
NSN. Enter Z01 if only one record is
required.
Routing Identifier Code 24-26 Enter RIC identifying losing item manager
(FROM) preparing the transaction.
Date (Extracted) 27-31 Enter date data was extracted from files.
(Enter two-digit year in record positions
27-28 and three-digit ordinal date in record
positions 29-31).
Blank 32 Leave blank.
End Item National 33-45 Enter the NSN, name, type, or model
Stock Number, Name, number for the end item application;
Type, or Model otherwise leave blank. For items with
Number multiple applications, enter data for most
critical application, or enter the word various.
RECORD 1
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Type of Inspection 48 Enter the appropriate type of inspection
Code code in accordance with appendix AP2.18.
Leave blank if type of inspection has not
been indicated or established.
First Article Test 49 Enter Y (yes) if first article testing is
required. Enter N (no) if not required.
Leave blank if first article testing
requirements have not been indicated or
determined.
Source, Maintenance, 50-54 Enter applicable source, maintenance, and
and Recoverability recoverability code; otherwise leave blank.
Packaging Data 55 Enter Y (yes) if specific preservation,
Availability Indicator packaging, packing, and marking data is
available for the item. Enter N (no) if
specific requirements have not been
developed/specified.
Product Quality 56 Enter Y (yes) if reports on contractor
Deficiency Report performance are on file at the LIM. Enter N
History Indicator (no) if no reports are on file.
Purchase Description 57 Enter Y (yes) if a purchase description is
Indicator being included on the following DLX
record(s) for the NSN. Enter N (no) if a
purchase description is not available.
Blank 58-80 Leave blank.
RECORD 2
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DLX.
Code
Routing Identifier Code 4-6 Enter RIC of gaining item manager to which
(TO) the transaction is being forwarded.
Blank 7 Leave blank.
National Stock Number 8-20 Enter NSN of the item being transferred
Package Sequence 21-23 Enter A02, and increment by one (i.e., A03,
Number A04, etc.) for each additional record. On
last record, enter Z and the appropriate two
position sequence number. If only this
record is required, enter Z02.
Blank 24-31 Leave blank.
Purchase Description 32-79 Enter clear text purchase description;
otherwise, leave blank. Continue
description on additional DIC DLX records
using package sequence number to
maintain correct sequence number to
maintain correct sequence. Max of 30
records can be used.
Blank 80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter appropriate DIC in the DM series.
Code
Routing Identifier 4-6 Enter RIC of the item manager to which this
Code (TO) transaction is being forwarded.
Transaction Serial 7 Enter consecutive numeric serial number for
Number each transaction within a DIC for this stock
or part number (e.g., 1 for first DMA, 2 for
second DMA, 1 for first DMB, etc.). 1
Stock or Part Number 8-20 Enter stock or part number of item required.
Unit of Issue 21-22 Enter UI of item.
Quantities 23-70 a. For DICs DMA, DMB, and DMC,
respectively, enter the monthly OWRMR
First Month (23-30) quantity for recurring U.S. requirements,
Second Month (31-38) nonrecurring U.S. requirements, and
nonrecurring Allies requirements.
Third Month (39-46)
b. For DIC DMD, enter the forecasted
Fourth Month (47-54) monthly reparable return quantity.
Fifth Month (55-62) c. For DIC DME, enter the PWRMR in
record positions 23-30 and the PWRMRP in
Sixth Month (63-70) record positions 31-38; leave record
positions 39-70 blank.1
Blank 71 Leave blank.
Total Number of 72-73 Enter the total number of WMR transactions
Transactions submitted for all DICs for this stock or part
number.
Routing Identifier 74-76 Enter RIC of the activity from which this
Code (FROM) transaction is being submitted.
1
Use additional transactions as required, entering the consecutive transaction serial number within each
DIC, to accommodate submission of the number of months data specified by the Defense Guidance
issued each year.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Date 77-80 Enter the date (last digit of the calendar year
(Transaction and ordinal day of the calendar year) on
Preparation) which this transaction is prepared.
1
In reply to follow-up, when no record of the basic requisition document number exists, duplicate record
positions 8-24 and record positions 30-51 from the DIC DRF Follow-up.
2
Duplicate from the following in listed order of preference: record positions 4-6 of the DIC DRF, MRA
follow-up or DIC AS_ Shipment Status; record positions 67-69 of the DD Form 1348-1 or DIC AE_ Supply
Status; record positions 4-6 of the original requisition. For intra-DoD Component follow-up requirements,
enter code prescribed as the DoD Component.
3
If the stock number/part number of the item received cannot be fully entered in record positions 8-22,
leave blank. If item received exceeds stock number field and is wrong item or cannot be identified leave
record positions 8-22 blank and enter Discrepancy Indicator Code A in record position 63.
4
See Appendix AP3 - Formats Introduction, paragraph AP3.3.1.
5
Defense Automatic Addressing System will edit and provide an MRA to the activity identified by a valid
RIC in record position 54-56.
1
For Intra-Component followup requirements, enter code prescribed by the Component.
2
See DLMS Volume 2, Appendix 8 for transaction format.
3
See Appendix AP3 - Formats Introduction, paragraph AP3.3.1
4
See footnote 2 on page AP3.30-1.
5
Based on November 1993 implementation of MILSTRIP AMCL 138; otherwise priority is entered in
record positions 60-61.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter appropriate DIC from the DU series.
Code
Routing Identifier 4-6 Enter RIC of the Inventory Control Point
Code (FROM) (ICP) to which the receipt will be reported.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number of item to be
received.
Unit of Issue 23-24 Enter UI of the item.
Quantity 25-29 Enter quantity to be received, preceding
significant digits with zeros. 1 2
Procurement 30-43
Instrument or Due-In
Document Number
Procurement (30-42) Enter (or perpetuate) the PIID or the
Instrument Identifier applicable 13-position call/order number
(PIID) (identified by F in the 9th position) 3.
Blank (43) Leave blank.
or
Due-In Document (30-43) For intra-Component use only, enter (or
Number perpetuate) due-in document number.
Suffix 44 Enter consecutive alpha codes A through Z
when assignment of suffix codes is
necessary. 4
Item Number 45-50 Enter the contract/exhibit line item number
or subline item number as indicated below,
if applicable; otherwise, leave blank.
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2.
3
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
4
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Contract/Exhibit Line (45-48) Contract Line Item Number:
Item Number
Enter the CLIN, preceding significant
digits with zeros.
5
For intra-Navy use rp 60-66 identifies the ‘standard unit price’ (see ADC 63).
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Date Indicator 73-75 If prescribed by the Component managing
(Estimated Delivery) the item, enter last digit of calendar year
and two-digit month signifying estimated
delivery date, e.g., 207 means 2002, month
of July. 6
Multiuse 76 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
Call/Order Number 77-80 Enter applicable legacy four-position
call/order number associated with the PIIN;
otherwise, leave blank.
RECORD
FIELD LEGEND POSITIONS ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter appropriate DIC from the DW series.
Code
Routing Identifier 4-6 Enter RIC of the Inventory Control Point to
Code (FROM) which the receipt will be reported.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number of item to be
received.
Unit of Issue 23-24 Enter UI of the item.
Quantity 25-29 Enter quantity to be received, preceding
significant digits with zeros. 1/2
Document Number 30-43 Enter controlling document number.
Suffix 44 Enter controlling suffix code; otherwise,
leave blank.
Supplementary 45-50 Enter SUPADD; otherwise, leave blank.
Address
Signal 51 Enter signal code; otherwise, leave blank.
Fund 52-53 Enter fund code; otherwise, leave blank.
Distribution 54-56 Enter distribution code; otherwise, leave
blank.
Project 57-59 Enter project code; otherwise, leave blank.
Multiuse 60-66 For intra-DoD Component use, enter data
prescribed by the DoD Component.3, 4, 5
Dual Use 65-66
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.2.
3
For intra-Navy use, rp 60-66 identifies the standard unit price. (See ADC 63.)
4
For intra-Army use, rp 60-61 identifies the priority designator. (See ADC 234).
5
For intra-Air Force use, rp 60-61 identifies the priority designator. (See ADC 1080).
RECORD
FIELD LEGEND POSITIONS ENTRY AND INSTRUCTIONS
Multiuse (65-66) For intra-DoD Component use, enter data
prescribed by the DoD Component. 6
or
Optional inter- (65-66) For Inter-DoD Component use, either
DoD Component use shipment delay notification code “BD” in rp
for delay notification 65-66, if required based on Service/Agency
NIMS agreement, and assets are not
available to replenish the NIMS retail site
requirement; otherwise, leave blank. 7
Routing Identifier 67-69 Enter RIC of the storage activity which is to
Code (TO) receive item.
Ownership/Purpose 70 Enter ownership/purpose code of item to be
received.
Supply Condition 71 Enter SCC of item to be received.
Management 72 Enter management code; otherwise, leave
blank.
Date Indicator 73-75 If prescribed by the DoD Component
(Estimated Delivery) managing the item, enter last digit of the
calendar year and two-digit month signifying
estimated delivery date, e.g., 211, means
2002, month of November. 8 (When delayed
shipment notification “BD” is used in rps 65-
66, then the date entry represents the
Estimated Shipping Date vice the Estimated
Delivery Date).
Blank 76-78 Leave blank. 9
Multiuse 79-80 For intra-DoD Component use, enter data
prescribed by Component. For inter-
Component use, leave blank.
6
For intra-Army use, rp 65-66 identifies the advice code. (See ADC 234).
7
The DWK, Pre-Positioned Materiel Receipt-Other Than Procurement, may carry “BD” delayed
notification on an optional basis, IAW Service/Agency agreement when materiel to support a National
Inventory Management Strategy (NIMS) site requirement is delayed. Under this circumstance, the
transaction will also carry an Estimated Ship Date. See Chapter 4, Paragraph C4.3.4.
8
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.4.
9
For Navy Commercial Asset Visibility-Organic Repair Module DIC DWK, rp 76-78 identifies the Shipper
RIC. (See ADC 124.)
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DXA.
Code (DIC)
Routing Identifier 4-6 Enter RIC identifying the Inventory Control
Code (FROM) Point to which the receipt will be reported.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number to be received.
Unit of Issue 23-24 Enter UI of item to be received.
Quantity 25-29 Enter quantity to be received, preceding
significant digits with zeros. 1
Procurement 30-42 Enter applicable PIID or the applicable 13-
Instrument Identifier position call/order number (identified by F in
(PIID) the 9th position). 2
Blank 43 Leave blank.
Suffix 44 Enter consecutive alpha codes A through Z
when assignment of suffix codes is
necessary. 3
Item Number 45-50 Enter the contract/exhibit line item number
or subline item number, as follows:
Contract/Exhibit (45-48) Contract Line Item Number:
Line Item Number Enter the CLIN, preceding significant digits
with zeros.
Exhibit Line Item Number:
Enter the alphabetic exhibit identifier in
record position 45. Enter the exhibit line
number in record positions 46-48, preceding
significant digits with zeros.
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
2
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
3
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Contract/Exhibit (49-50) Enter the contract or exhibit subline item
Subline Item Number number, if applicable; otherwise, zero fill.
Blank 51-53 Leave blank.
Distribution 54-56 Enter (or perpetuate) distribution code;
otherwise, leave blank.
Project 57-59 Enter project code; otherwise, leave blank.
Shipment Number 60-66 Enter vendor shipment number if known;
otherwise, leave blank.
Routing Identifier 67-69 Enter RIC identifying storage activity which
Code (TO) is to receive the item.
Ownership/ Purpose 70 Enter ownership/purpose code of item to be
received.
Supply Condition 71 Enter SCC of item to be received.
Management 72 Enter appropriate management code;
otherwise, leave blank.
Date Indicator 73-75 Enter the last digit of calendar year and two-
(Estimated Delivery) digit month signifying estimated delivery
date, e.g., 205 means 2002, month of May. 4
Blank 76 Leave blank.
Call/Order Number 77-80 Enter applicable legacy four-position
call/order number associated with the PIIN;
otherwise, leave blank.
4
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.4.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DXB.
Code
Routing Identifier 4-6 Enter RIC identifying the Inventory Control
Code (FROM) Point to which the receipt shall be reported.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number to be received.
Unit of Issue 23-24 Enter UI of item to be received.
Quantity 25-29 Enter quantity to be received, preceding
significant digits with zeros. 1
Document Number 30-43 Enter controlling document number.
Suffix 44 Enter consecutive alpha codes A through Z
when assignment of suffix codes is
necessary. 2
Supplementary 45-50 Enter SUPADD; otherwise, leave blank.
Address
Signal 51 Enter signal code; otherwise, leave blank.
Fund 52-53 Enter fund code; otherwise, leave blank.
Distribution 54-56 Enter distribution code; otherwise, leave
blank.
Project 57-59 Enter project code; otherwise leave lank.
Unit Price 60-66 Enter unit price if prescribed by the
Component managing the item; otherwise,
leave blank.
Routing Identifier 67-69 Enter RIC identifying the storage activity
Code (TO) which is to receive the item.
1
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Ownership/Purpose 70 Enter ownership/purpose code of the item to
be received.
Supply Condition 71 Enter SCC of the item to be received.
Management 72 Enter appropriate management code;
otherwise, leave blank.
Date Indicator 73-75 Enter the last digit of calendar year and two-
(Estimated Delivery) digit month signifying estimated delivery
date, e.g., 207 is 2002, month of July. 3
Blank 76-80 Leave blank.
3
See Appendix AP3 - Formats Introduction, Paragraph AP3.3.4.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DXC.
Code
Routing Identifier 4-6 Enter RIC of the Inventory Control Point to
Code (TO) which the receipt shall be reported.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number received.
Unit of Issue 23-24 Enter UI of the item to be received.
Quantity 25-29 Enter quantity to be received, preceding
significant digits with zeros. 1
Procurement 30-42 Enter applicable PIID or the applicable 13-
Instrument Identifier position call/order number (identified by F in
(PIID) the 9th position). 2
Blank 43 Leave blank.
Suffix 44 Enter consecutive alpha codes A through Z
when assignment of suffix codes is
necessary. 3
Item Number 45-50 Enter the contract/exhibit line item number
or subline item number as follows:
Contract/Exhibit (45-48) Contract Line Item Number:
Line Item Number Enter the CLIN, preceding significant digits
with zeros.
Exhibit Line Item Number:
Enter the alphabetic exhibit identifier in
record position 45. Enter the exhibit line
number in record positions 46 through 48,
preceding significant digits with zeros.
1
See Appendix AP3 - Formats Introduction, paragraph AP3.3.1.
2
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
3
See Appendix AP3 - Formats Introduction, paragraph AP3.3.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Contract/Exhibit (49-50) Enter the contract or exhibit subline item
Subline Item Number number, if applicable; otherwise, zero fill.
Blank 51-53 Leave blank.
Distribution 54-56 Enter (or perpetuate) distribution code;
otherwise, leave blank.
Project 57-59 Enter project code; otherwise, leave blank.
Shipment Number 60-66 Enter vendor shipment number, if known;
otherwise, leave blank.
Routing Identifier 67-69 Enter RIC of the storage activity which is to
Code (FROM) receive the item.
Ownership/Purpose 70 Enter ownership/purpose code of the item to
be received.
Supply Condition 71 Enter SCC of item to be received.
Management 72 Enter management code; otherwise, leave
blank.
Date Indicator 73-75 Enter last digit of calendar year and two-digit
(Estimated Delivery) month signifying estimated delivery date,
(e.g., 307 means 2003, month of July). 4
Blank 76 Leave blank.
Call/Order Number 77-80 Enter applicable legacy four-position
call/order number associated with the PIIN;
otherwise, leave blank.
4
See Appendix AP3 - Formats Introduction, paragraph AP3.3.4.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Supply Condition 71 Enter SCC of the item to be received.
Management 72 Enter management code; otherwise, leave
blank.
Date Indicator 73-75 Enter the last digit of calendar year and two-
(Estimated Delivery) digit month signifying estimated delivery
date, e.g., 307 means 2003, month of July. 2
Blank 76-80 Leave blank.
2
See Appendix AP3 - Formats Introduction, paragraph AP3.3.4.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DYA, DYB, DYL, or DYM, as
Code appropriate.
Routing Identifier 4-6 Enter RIC of the Inventory Control Point
Code (TO) (ICP) to which this transaction is being
forwarded.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number.
Unit of Issue 23-24 Enter UI of item.
Quantity 25-29 Enter quantity required, preceding
significant digits with zeros. If the quantity
exceeds 99,999, additional transactions will
be prepared and submitted for the remaining
balance. 1
Document Number 30-43 Enter document number controlling this
transaction.
Suffix 44 Enter consecutive alpha codes A through Z
when assignment of suffix codes is
necessary. 2
Supplementary 45-50 Enter DoDAAC of the expected ship-to
Address address; otherwise, leave blank.
Multiuse 51-56 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
Project 57-79 Enter project code; otherwise, leave blank.
Coast Designation 60 Enter E if consignee location is east of the
Mississippi River, Atlantic, Europe, Near
east, Africa, Central, or South America.
Enter W if consignee location is other than
above.
Blank 61 Leave blank.
1
See Appendix AP3 - Formats Introduction, paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, paragraph AP3.3.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Date Indicator 62-64 The first day of the month by which it is
(Support) anticipated materiel will be requisitioned for
the program. Enter last digit of the calendar
year and 2-digit month signifying the support
date; e.g., 503 is 2005, month of March. 3
Advice 65-66 Enter MILSTRIP Advice Code 2B
(requested item only will suffice; do not
substitute/interchange); otherwise, leave
blank.
Routing Identifier 67-69 Enter RIC of the activity submitting this
Code (FROM) request.
Purpose 70 Enter purpose code of item; otherwise,
leave blank.
Supply Condition 71 Enter supply condition code of item
required.
Blank 72 Leave blank.
Routing Identifier 73-75 If the activity submitting the SPR is not the
Code originator of the requirement, enter the RIC
of the originator; otherwise, leave blank.
Generic Submission 76 For clothing and footwear, enter the alpha G
to indicate that this is a generic submission
and that the stock number indicated is the
first size in the series. When used, it will
indicate that the quantity entered in record
positions 25-29 represents the total
requirements for the generic item. This
quantity will be converted by the ICP to
individual sizes using the applicable tariff.
Blank 77-80 Leave blank.
3
See Appendix AP3 - Formats Introduction, paragraph AP3.3.4.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DYC.
Code
Routing Identifier 4-6 Enter RIC identifying the Inventory Control
Code (TO) Point to which this transaction is being
forwarded.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number of item required.
Unit of Issue 23-24 Enter UI of item.
Quantity 25-29 Enter quantity required, preceding significant
digits with zeros. If the quantity exceeds
99,999, additional transactions will be
prepared and submitted for the remaining
balance. 1
Document Number 30-43 Perpetuate from source document.
Suffix 44 Perpetuate from source document.
Supplementary 45-50 Perpetuate from source document.
Address
Multiuse 51-56 Perpetuate from source document.
Project 57-59 Perpetuate from source document.
Coast Designation 60 Perpetuate from source document.
Blank 61 Leave blank.
Date Indicator 62-64 Perpetuate from source document.
(Support)
1
See Appendix AP3 - Formats Introduction, paragraph AP3.3.1.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Blank 72 Leave blank.
Day of Year 73-75 Enter ordinal day of the calendar year on
(Transaction) which the transaction is prepared.
Generic Submission 76 Perpetuate from source document.
Blank 77-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DYD.
Code
Routing Identifier 4-6 Enter RIC of the Inventory Control Point to
Code (TO) which the transaction is being forwarded.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number of item required.
Unit of Issue 23-24 Enter UI of item required.
Quantity 25-29 Enter new quantity when quantity required is
changed; otherwise, enter quantity from the
source document. 1
Document Number 30-43 Perpetuate from source document.
Suffix 44 Perpetuate from source document.
Supplementary 45-50 Enter new address, when applicable;
Address otherwise, perpetuate from source
document.
Multiuse 51-56 Perpetuate from source document.
Project 57-59 Enter new project code, when applicable;
otherwise, perpetuate from source
document.
1
See Appendix AP3 - Formats Introduction, paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, paragraph AP3.3.4.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Advice Code 65-66 Perpetuate from source document.
Routing Identifier 67-69 Enter new RIC of the activity submitting the
(FROM) transaction, if applicable; otherwise,
perpetuate from source document.
Purpose 70 Perpetuate from source document.
Supply Condition 71 Perpetuate from source document.
Blank 72 Leave blank.
Day of Year 73-75 Enter ordinal day of the calendar year on
(Transaction) which the transaction is prepared.
Generic Submission 76 Perpetuate from source document.
Blank 77-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DYG.
Code
Routing Identifier 4-6 Enter RIC of the Inventory Control Point to
Code (TO) which this transaction is being forwarded.
Blank 7 Leave blank.
Stock or Part Number 8-22 Perpetuate from Special Program
Requirement (SPR) status.
Unit of Issue 23-24 Perpetuate from SPR status.
Quantity 25-29 Perpetuate from SPR status.
Document Number 30-43 Perpetuate from SPR status.
Suffix 44 Perpetuate from SPR status.
Supplementary 45-50 Perpetuate from SPR status.
Address
Multiuse 51-56 Perpetuate from SPR status.
Project 57-59 Perpetuate from SPR status.
Coast Designation 60 Perpetuate from SPR status.
Blank 61 Leave blank.
Date Indicator 62-64 Perpetuate from SPR request/modifier.
(Support)
Advice 65-66 Perpetuate from SPR request.
Routing Identifier 67-69 Enter RIC identifying the activity submitting
Code (FROM) the acceptance transaction.
Purpose 70 Perpetuate from SPR status.
Supply Condition 71 Perpetuate from SPR status.
Blank 72 Leave blank.
Day of Year 73-75 Enter the ordinal day of the calendar year on
(Transaction) which the transaction is prepared.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Generic Submission 76 Perpetuate from SPR status.
Blank 77-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DYH.
Code
Routing Identifier 4-6 Enter RIC of the Inventory Control Point to
Code (TO) which this transaction is being forwarded.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number of item required.
Unit of Issue 23-24 Enter UI of item.
Quantity 25-29 Perpetuate from Special Program
Requirement (SPR) Status.
Document Number 30-43 Perpetuate from SPR Status.
Suffix 44 Perpetuate from SPR Status.
Supplementary 45-50 Perpetuate from SPR Status.
Address
Multiuse 51-56 Perpetuate from SPR Status.
Project 57-79 Perpetuate from SPR Status.
Coast Designation 60 Perpetuate from SPR Status.
Blank 61 Leave blank.
Date Indicator 62-64 Perpetuate from SPR Request/Modifier.
(Support)
Advice 65-66 Perpetuate from SPR Request.
Routing Identifier 67-69 Enter RIC of the activity submitting the
Code (FROM) rejection transaction.
Purpose 70 Perpetuate from SPR Status.
Supply Condition 71 Perpetuate from SPR Status.
Blank 72 Leave blank.
Day of Year 73-75 Enter ordinal day of the calendar year on
(Transaction) which transaction is prepared.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Generic Submission 76 Perpetuate from SPR Status.
Blank 77-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DYJ.
Code
Routing Identifier Code 4-6 Enter RIC of the Inventory Control Point to
(TO) which this transaction is being forwarded.
Blank 7 Leave blank.
Stock or Part Number 8-22 Perpetuate from source document.
Unit of Issue 23-24 Perpetuate from source document.
Quantity 25-29 Perpetuate from source document.
Document Number 30-43 Perpetuate from source document.
Suffix 44 Perpetuate from source document.
Supplementary 45-50 Perpetuate from source document.
Address
Multiuse 51-56 Perpetuate from source document.
Project 57-59 Perpetuate from source document.
Coast Designation 60 Perpetuate from source document.
Blank 61 Leave blank.
Support Date Indicator 62-64 Perpetuate from source document.
Advice 65-66 Perpetuate from source document.
Routing Identifier Code 67-69 Enter RIC of the activity submitting the
(FROM) request.
Purpose 70 Perpetuate from source document.
Supply Condition 71 Perpetuate from source document.
Blank 72 Leave blank.
Routing Identifier Code 73-75 Perpetuate from source document.
Generic Submission 76 Perpetuate from source document.
Blank 77-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DYK.
Code
Routing Identifier 4-6 Enter RIC of forecasting activity from record
Code (TO) positions 67-69 of the incoming request.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number of substitute, if
offered, or superseding item when
requested item is obsolete; otherwise,
perpetuate stock number from the
document being replied to.
Unit of Issue 23-24 Enter UI of item in record positions 8-22.
Quantity 25-29 Perpetuate from document being replied to.
Document Number 30-43 Perpetuate from document being replied to.
Suffix 44 Perpetuate from document being replied to.
Supplementary 45-50 Perpetuate from document being replied to.
Address
Multiuse 51-56 Perpetuate from document being replied to.
Project Code 57-59 Perpetuate from document being replied to.
Coast Designation 60 Perpetuate from document being replied to.
Blank 61 Leave blank.
Lead Time 62-64 When specified by the status code in record
positions 65-66, enter the number of days
representing procurement lead time and/or
time required for assembly; otherwise leave
blank.
Special Program 65-66 Enter applicable SPR status code from
Requirement Status appendix AP2.11.
Routing Identifier 67-69 Enter RIC of the ICP preparing this
Code (FROM) response.
Purpose Code 70 Perpetuate from document being replied to.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Supply Condition 71 Perpetuate from document being replied to.
Code
Blank 72 Leave blank.
Day of Year 73-75 Enter ordinal day of the calendar year on
(Transaction) which transaction is prepared.
Generic Submission 76 Perpetuate from document being replied to.
Gaining Inventory 77-79 Enter GIM on logistic reassignments;
Manager otherwise leave blank.
Blank 80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZ9.
Code
Routing Identifier 4-6 Enter RIC of the activity which submitted the
Code (TO) incoming transaction being rerouted or
revised by the Defense Automated
Addressing System (DAAS).
Request 7 Perpetuate from incoming request.
Federal Supply Class 8-11 When MILSTRIP Status Code BG is
entered in record positions 79-80, enter the
correct FSC for the National Item
Identification Number; otherwise, perpetuate
from original transaction.
Other fields 12-56 Perpetuate from original transaction.
Routed Document 57-59 Enter DIC identification from record
Identification positions 1-3 of the incoming transaction
being rerouted or revised by the DAAS.
Other Fields 60-66 Perpetuate data from original transaction.
Routing Identifier 67-69 When MILSTRIP Status Code BM is
Code entered in record positions 79-80, enter RIC
of the source of supply to whom DAAS is
rerouting the transaction; otherwise, leave
blank.
Other Fields 70-76 Perpetuate from original transaction.
Blank 77-78 Leave blank.
Status 79-80 Enter MILSTRIP Status Code BG when the
FSC in the original transaction was revised.
Enter MILSTRIP Status Code BM when the
original transaction was rerouted to the
correct source of supply.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZA.
Code
Routing Identifier Code 4-6 Enter RIC of the Inventory Control Point (ICP) to
(TO) where this transaction is being forwarded.
Card Overflow 7 Enter codes A through Z (Except I and O) when
any quantity exceeds the number of digits
allotted.
For ammunition and ammunition related items
in Federal Supply Group (FSG) 13, and
Federal Supply Class (FSC) 1410, 1420,
1427, 1440, 5330, 5865, 6810, or 8140 by
trading partner agreement, enter code ‘9’ and
enter the 7th, 8th and 9th position of the "on-
hand" quantity in record position (rp) 52-54,
prefixing significant digits with zeros. 1
Stock or Part Number 8-22 Enter stock or part number of item reported.
Unit of Issue 23-24 Enter UI of item.
Quantity (On hand) 25-30 Enter quantity of the item on hand, preceding
significant digits with zeros.
For FSG 13 and FSC 1410, 1420, 1427, 1440,
5330, 5865, 6810, or 8140 ammunition and
ammunition related items, when ‘9’ is entered
in rp 7, follow guidance at rp 7.
Quantity (Due-In) 31-36 Enter quantity of the item due-in, preceding
significant digits with zeros.
Quantity 37-41 Enter quantity of the item on backorder,
(Backordered) preceding significant digits with zeros.
Multi-use 42-66 When used between Components, leave blank.
When used within a Component, enter data
prescribed by that Component. See rows below
for specific Component use.
1
Refer to ADC 444,
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
For Army, the following data is entered in rp 43-64 of the multi-use field 2.
For ammunition and ammunition related FSG 13 and FSC 1410, 1420, 1427, 1440, 5330,
5865, 6810, or 8140, the following data is entered in rp 52-54 of the multi-use field.
Quantity Overflow 52-54 For ammunition and ammunition related
items in Federal Supply Group 13 and
Federal Supply Classes 1410, 1420, 1427,
1440, 5330, 5865, 6810, and 8140, when
‘9’ is entered in rp 7, enter the first through
sixth positions of the on hand quantity in rp
25 – 30, and the seventh through ninth
positions in rp 52 – 54, preceding
significant digits with zeroes. For example
for a quantity of 98,765,432, enter 765432
in rp 25 – 30 and enter 098 in rp 52-54. 3
Routing Identifier 67-69 Enter RI code of the ICP preparing the
(FROM) transaction. 4
2
Refer to ADC 250, Revise DLMS Supplement (DS) 846I and MILSTRAP DZA Asset Status
Transactions to Support Army Distribution Operations, and Revise DS 846I for Use of Universal Time
Coordinate (UTC) and for Administrative Updates.
3
Refer to ADC 444, Revise Asset Status Report Transactions, DLMS 846I and MILSTRAP DZA, to
Document Ammunition Systems Use by Agreement of Nine Digit Quantity On-Hand.
4
For Army/DLA interface, based upon mutual agreement, a DLA storage activity may prepare the DZA on
behalf of the DLA ICP. The DLA ICP RI Code SMS appears in rp 67-69. (Refer to ADC 250, Revise
DLMS Supplement (DS) 846I and MILSTRAP DZA Asset Status Transactions to Support Army
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
For ammunition and ammunition related items
in FSG 13 and FSC 1410, 1420, 1427, 1440,
5330, 5865, 6810, and 8140, enter the RI code
of the Storage Activity preparing the
transaction.5
Ownership/Purpose 70 When used between Components, enter
ownership code of the item. When used within a
Component, enter purpose code of the item.
Supply Condition 71 Enter supply condition code of the item.
Multiuse 72-80 For intra-Component use, enter data prescribed
by the Component. For inter-Component use,
leave blank. See rows below for specific
Component use.
The following DoD Component data is identified for rp 72-77 multiuse field:
Time 72-77 Army enters time of transaction preparation in
HHMMSS Format expressed in universal time
coordinate. Refer to ADC 250.
Date (Transaction 73-75 Navy, and ammunition systems, enters
Preparation) transaction preparation date. Navy, and
ammunition ICPs, uses this date to determine
the most current asset posture when more than
one asset report is received within the same
cycle. 6 7
Stockage List Code 78 Army enters the Stockage List Code. This is an
intra-Army code and use of this data is
meaningful to Army only. 8
Distribution Operations, and Revise DS 846I for Use of Universal Time Coordinate (UTC) and for
Administrative Updates.)
5
Refer to ADC 444 Revise Asset Status Report Transactions, DLMS 846I and MILSTRAP DZA, to
Document Ammunition Systems Use by Agreement of Nine Digit Quantity On-Hand.
6
Refer to ADC 355, Revise DLMS Supplement (DS) 846I, Asset Status Inquiry/Report to Address Intra-
Navy Use of Transaction Preparation Date in Multiuse Field of MILSTRAP DZA Transaction
7
Refer to ADC 444, Revise Asset Status Report Transactions, DLMS 846I and MILSTRAP DZA, to
Document Ammunition Systems Use by Agreement of Nine Digit Quantity On-Hand.
8Refer to ADC 458, Documentation of Intra-Army Use of Army Data Elements for MILSTRAP DZA and DLMS 846I
Asset Status Transactions
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZC.
Code
Routing Identifier 4-6 Enter RIC of the activity to where this
Code (TO) transaction is being forwarded.
Blank 7 Leave blank.
Stock or Part Number 8-22 Enter stock or part number of item being
transferred.
Unit of Issue 23-24 Enter UI of item being transferred.
Quantity (Transfer) 25-29 Enter quantity being transferred to gaining
item manager (GIM); otherwise, enter
zeros. 1,2
Document Number 30-43 Perpetuate from the DEE/DEF transaction.
Suffix 44 Enter consecutive alpha code A through Z
when assignment of suffix codes is
necessary. 3
Routing Identifier 45-47 Enter RIC of the GIM.
Code (Gaining)
Multiuse 48-56 Enter data prescribed by the Component.
Project 57-59 Enter appropriate code if stocks are
segregated and maintained by codes
reflected in project code field: otherwise,
leave blank.
Blank 60 Leave blank.
Date 61-64 Enter ordinal date on which the logistics
(Effective Transfer) reassignment is effective.
Blank 65-66 Leave blank.
1
See Appendix AP3 - Formats Introduction, paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, paragraph AP3.3.2.
3
See Appendix AP3 - Formats Introduction, paragraph AP3.3.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Routing Identifier 67-69 Enter RIC of activity preparing document.
(FROM)
Ownership/Purpose 70 Enter ownership/purpose code if prescribed
by Component; otherwise, leave blank.
Supply Condition 71 Enter supply condition code of balance
affected.
Management 72 Enter management code as prescribed by
Component; otherwise, leave blank.
Multiuse 73-75 Enter data prescribed by the Component.
Quantity (Retention) 76-80 Enter quantity being retained by the losing
item manager.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZD.
Code
Routing Identifier Code 4-6 Enter RIC from record positions 67-69 of
(TO) DIC DZC to which reply is being made or
losing item manager (LIM) RIC.
Follow-up Indicator 7 LIM storage activity not in receipt of a DIC
DZC, enter A (denoting follow-up) to
provide available asset information to the
LIM. Otherwise, leave blank.
Stock or Part Number 8-22 Perpetuate from DIC DZC.
Unit of Issue 23-24 Perpetuate from DIC DZC.
Quantity (Transfer) 25-29 Enter quantity which was available for
transfer subject to the retention quantity
contained in record positions 76-80 of DIC
DZC. 1,2
Document Number 30-43 Perpetuate from DIC DZC.
Suffix Code 44 Enter consecutive alpha codes A through
Z when assignment of suffix codes are
necessary. 3
Routing Identifier Code 45-47 Perpetuate from DIC DZC.
(Gaining)
Multiuse 48-56 Enter data prescribed by the Component.
Project Code 57-59 Perpetuate from DIC DZC.
Blank 60 Leave blank.
Date 61-64 Perpetuate from DIC DZC.
(Effective Transfer)
Blank 65-66 Leave blank.
1
See Appendix AP3 - Formats Introduction, paragraph AP3.3.1.
2
See Appendix AP3 - Formats Introduction, paragraph AP3.3.2.
3
See Appendix AP3 - Formats Introduction, paragraph AP3.3.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Routing Identifier Code 67-69 Enter RIC of storage activity from which
reply is being made.
Ownership/Purpose 70 Perpetuate from DIC DZC.
Supply Condition Code 71 Perpetuate from DIC DZC.
Management 72 Perpetuate from DIC DZC.
Multiuse 73-75 Enter data prescribed by the Component.
Quantity (Retention) 76-80 Enter the quantity being retained by the
LIM.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZE.
Code
Routing Identifier Code 4-6 Enter RIC of the activity to which the request
(TO) is submitted (see chapter 8).
Reporting 7 Enter the appropriate code from appendix
AP2.9.
Stock or Part Number 8-22 Enter the stock or part number of item to be
reported.
Date 23-26 Enter the ordinal date when required by the
reporting code in record position 7. Always
reflect dates for commencing, or change of
reporting, under codes C, D, H, and J, as the
first day of a month. Always reflect the date
for termination of reporting (code E) as the
last day of a month. When the code entered
in record position 7 is M or P, this field will be
left blank. When the code entered in record
position 7 is N or Z, enter the date by which
the one-time asset status report is required.
Blank 27-66 Leave blank.
Routing Identifier Code 67-69 Enter the appropriate RIC of the activity to
which the asset status reports are to be
submitted.
Multiuse 70-80 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZF.
Code
Routing Identifier 4-6 Enter the RIC of the activity to which this
Code (TO) transaction is being forwarded.
Reporting 7 Enter code from appendix AP2.9 which
indicates type of reporting being
accomplished.
Stock or Part Number 8-22 Enter the stock or part number of item
reported.
Unit of Issue 23-24 Enter the UI of item.
Multiuse 25-30 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
Routing Identifier 31-33 When rp 7 = N, enter RIC of the owning
Code activity to which any resulting MILSTRIP
DIC A4_ Lateral Redistribution Orders are
to be sent; otherwise enter RIC of the
activity preparing this transaction (FROM
RIC).
Routing Identifier 34-36 Enter the RIC of storage activity at which
Code (Storage item is stored, if different from record
Activity) positions 31-33; otherwise, leave blank.
Date 37-40 Enter last digit of the calendar year and
ordinal day of the calendar year which
reflects assets as of close of business.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Quantity 41-46 When rp 7 = N, enter total system RO for
(Requisitioning RIC in rp 31-33; if multiple transactions
Objective) with the same rp 31-33 RIC are generated
for the same NSN, each shall reflect the
same requisitioning objective. 1 If rp 7 does
not equal N, enter requisitioning objective
quantity established for item being
reported, preceding significant digits with
zeros; if quantity exceeds 999,999, enter
overflow quantity in next transaction.
Leave field blank in ensuing transactions
when overflow quantity is not involved.
Quantity (Due-In) 47-52 Enter quantity of the item due-in, preceding
significant digits with zeros. If quantity
exceeds 999,999, enter overflow quantity
in next transaction. Leave field blank in
ensuing transactions when overflow
quantity not involved. When rp 7 = N, this
field may be left blank.
Multiuse 53 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
Multiuse 54 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, enter the purpose code
of quantity on hand reported in rps 56-61, if
required based on Service/Agency
agreement; otherwise leave blank.
Supply Condition 55 Enter SCC of quantity on hand reported in
Code record positions 56-61.
1For Air Force Secondary Inventory Control Activities (SICAs) which own their Services= wholesale and
retail assets, only DIC DZFs with the same RIC in rps 31-33 for the same NSN, and 01 entry in rps 79-80
will contain the same SICA total system requisitioning objective. DIC DZFs with the SICA RIC in rp
31-33 without a 01 entry in rps 79-80 will contain the requisitioning objective for the RIC in rps 34-36.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Quantity (On Hand) 56-61 When rp 7 = N, enter the quantity on-hand
for the activity at which the materiel is
stored, i.e., the quantity on-hand for the
RIC in rps 31-33 (if no RIC is present in rps
34-36) or the quantity on-hand for the RIC
in rps 34-36 if both RICs are present. 2 If rp
7 does not equal N, enter quantity on hand
preceding significant digits with zeros.
(Does not include reserved quantity
entered in record positions 71-76.) If
quantity exceeds 999,999, enter overflow
quantity in next transaction. Leave field
blank in ensuing transactions when
overflow quantity not involved.
Multiuse 62 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
Multiuse 63 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, enter the purpose code of
quantity on hand reported in rps 65-70, if
required by Service/Agency agreement;
otherwise leave blank.
Supply Condition 64 Enter SCC of quantity on hand reported in
Code record positions 65-70.
2
For all Service Secondary Inventory Control Activities (less Air Force): If both rps 31-33 and rps 34-36
contain RICs, then the recipient must add the on-hand quantity on all the DIC DZF transactions, for the
reported NSN, that have the same RIC in rps 31-33. This aggregate on-hand quantity is then compared
to the system requisitioning objective in rps 41-46 when making MILSTRIP Lateral Redistribution Order
decisions using DoD Total Asset Visibility business rules.
For Air Force Secondary Inventory Control Activities: Both rps 31-33 and rps 34-36 will contain RICs.
The recipient must add the quantity on-hand on all DZF transactions containing a "01" in rps 79-80, for
the reported NSN, that have the same RIC in rps 31-33. This aggregate on-hand quantity is then
compared to the system requisitioning objective contained in rp 41-46 when making Lateral
Redistribution Order decisions using DoD Total Asset Visibility business rules.
For DZFs with only one RIC (rps 31-33) and for Air Force Secondary Inventory Control Activity DZFs
with two RICs and "blanks" in rps 79-80, the on-hand quantity and requisitioning objective in the
individual DZF are compared when making Lateral Redistribution Order decisions using DoD Total Asset
Visibility business rules.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Quantity (On Hand) 65-70 Enter quantity on hand, preceding
significant digits with zeros. (Does not
include reserved quantity entered in record
positions 71-76.) If quantity exceeds
999,999, enter overflow quantity in next
transaction. Leave field blank in ensuing
transactions when overflow quantity not
involved.
Quantity (Reserved) 71-76 Enter quantity reserved for special
projects/programs, preceding significant
digits with zeros. If quantity exceeds
999,999, enter overflow quantity in next
transaction. Leave field blank in ensuing
transactions when overflow quantity not
involved.
Blank 77-78 Leave blank.
Number of 79-80 Enter total number of transactions being
Transactions submitted for item identified in record
positions 8-22 (precede significant digit
with zero, when applicable).
EXCEPTION: when rp 7 = N, leave blank
for all Service SICAs except Air Force; for
Air Force SICAs, enter a SICA
wholesale/retail indicator as follows:
01 for SICA wholesale
Blank for SICA retail
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZG.
Code
Routing Identifier Code 4-6 Enter RIC of the activity to which the
(TO) transaction is being forwarded.
Other Fields 7-53 Perpetuate data from the incoming
transaction being rejected.
Correct Manager's 54-56 Enter RIC of correct manager, if known,
Routing Identifier Code when code AB is indicated in record
positions 79-80; otherwise, leave blank.
Rejected Document 57-59 Enter DIC from record positions 1-3 of the
Identification Code incoming transaction being rejected.
Other Fields 60-66 Perpetuate data from the incoming
transaction being rejected.
Routing Identifier Code 67-69 Enter RIC of the activity rejecting the
(FROM) document.
Other Fields 70-78 Perpetuate data from the incoming
transaction being rejected.
Dual Use 79-80
Reject Advice (79-80) Enter applicable advice code (see
appendix AP2.8 of this manual).
or
MILSTRIP Status (79-80) Enter applicable MILSTRIP status code
(see MILSTRIP).
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZH.
Code
Routing Identifier 4-6 Enter RIC of the Inventory Control Point to
Code (TO) which this transaction is being forwarded.
Type of Location 7 Enter type of location reconciliation request
Reconciliation code which indicates the type of reporting
Request being accomplished.
Stock or Part Number 8-22 Enter stock or part number of item being
requested for reconciliation.
Unit of Issue 23-24 Enter UI of item.
Quantity 25-34 Enter quantity, preceding significant digits
with zeros.
Multiuse 35 For intra-Component use, enter the data
prescribed by the Component. For inter-
Component use, leave blank.
Date Cutoff 36-39 Enter mutually agreed upon cutoff date (last
digit of the calendar year and ordinal day of
the calendar year; e.g., 6253 is 10 Sep 86)
for location reconciliation.
Shelf-Life 40 Enter shelf-life code of the item.
Controlled Inventory 41 Enter controlled inventory item code
Item applicable to the item.
Manager/Owner 42 Enter numeric 1 if activity in record Identifier
positions 4-6 is the Integrated Materiel
Manager (IMM) or numeric 2 if the activity is
an owner but not the IMM. 1
Blank 43 Leave blank.
Transaction 44-46 Enter the lot/segment number of the
Lot/Number Segment transactions being reconciled;
otherwise, leave blank.
1
May be used intra-Component or inter-Component when agreed to by the Components involved.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Blank 47-59 Leave blank.
Consecutive 60-66 Enter consecutive number beginning with
Transaction Number 0000001 in the first transaction to identify
each transaction in the reconciliation.
Routing Identifier 67-69 Enter RIC of the storage activity preparing
Code (FROM) the transaction.
Ownership/Purpose 70 Enter ownership or purpose code if assets
are segregated physically or on the storage
activity record; otherwise leave blank. 2
Supply Condition 71 Enter SCC of item being reconciled.
Inventory Category 72 Enter inventory category code, if prescribed
by Component managing the item;
otherwise, leave blank.
Blank 73-75 Leave blank.
Multiuse 76-78 For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
Dual Use 79-80
Multiuse (79-80) For intra-Component use, enter data
prescribed by the Component. For inter-
Component use, leave blank.
or
Subsistence Type (79) For Subsistence Items Only: Enter
of Pack subsistence type of pack code (see
MILSTRIP) for the item.
Blank (80) For Subsistence Items Only: Leave blank.
2
May be used intra-Component or inter-Component when agreed to by the Components involved.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZJ.
Code
Routing Identifier 4-6 Enter RIC of the storage activity to which
Code (TO) the request is being forwarded.
Type of Physical 7 Enter the applicable type of physical
Inventory/Transaction inventory/transaction history code.
History
Stock or Part Number 8-22 Enter stock or part number of the item for
the history/balance being requested.
Unit of Issue 23-24 Enter UI of item.
Transaction History 25-31 Enter data specifying the period timeframe
Timeframe for which transaction history is being
requested.
(25-28) Enter transaction history start date.
(29-31) Enter the total number of prior days
transaction history required.
Blank 32-53 Leave blank.
Distribution 54-56 Enter distribution code if stocks are
segregated and maintained by codes
reflected in distribution field; otherwise,
leave blank.
Lot/Segment Number 57-59 Enter the lot/segment number for controlling
the inventory/reconciliation; otherwise, leave
blank.
Type of Media 60 Enter the code which identifies the
transaction history transmission media (see
appendix AP2.15); otherwise, leave blank.
Blank 61-66 Leave blank.
1
May be used intra-Component or inter-Component when agreed to by the Components involved.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Routing Identifier 67-69 Enter RIC of the activity from which the
Code (FROM) request is being forwarded.
Ownership/Purpose 70 Enter applicable ownership/purpose code
for the history/balance requested;
otherwise, leave blank.
Supply Condition 71 Enter applicable SCC for the history/
balance requested; otherwise, leave blank.
Blank 72 Leave blank.
Day of Year 73-76 Enter the ordinal date of the calendar year
(Transaction) on which the transaction is prepared.
Blank 77-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZK.
Code
Routing Identifier 4-6 Enter RIC of the activity to which the
Code (TO) transaction is being forwarded.
Type of Physical 7 Perpetuate from the DIC DZJ Transaction
Inventory/Transaction History Request; otherwise, enter code W
History for automatic submission of transaction
history.
Other Fields 8-29 Perpetuate from source document. 2
Document Number 30-43 When record position 7 of the DIC DZJ
request is W and the storage activity has no
transactions for the stock or part number
requested for the dates specified in record
positions 25-31, but transactions are available
since the date of last location reconciliation, 8-
fill this field; when no transactions are
available for the dates specified or since the
date of last reconciliation, 9-fill this field.
When record position 7 is X and the storage
activity has no transactions for the dates
specified, 9-fill this field; otherwise, perpetuate
from the source document.
Other Fields 44-50 Perpetuate from source document.
Blank 51 Leave blank.
Fund 52-53 Perpetuate from source document.
Source Document 54-56 Enter DIC from record positions 1-3 of the
Identifier Code source document.
Lot/Segment Number 57-59 Enter the lot/segment number for controlling
the inventory/reconciliation; otherwise, leave
blank.
1
May be used intra-Component or inter-Component when agreed to by the Components involved.
2
All references to the source document relate to the document on the storage activity transaction
history file; e.g., D4_, D6_, D7_, D8_, D9_.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Contract Shipment 60-66 Perpetuate from source document.
Number
Routing Identifier 67-69 Enter RIC of the activity from which the
Code (FROM) transaction is being forwarded.
Other Fields 70 Perpetuate from source document.
Supply Condition 71 When record positions 30-43 of the DIC
DZK are 8- or 9-filled, enter the applicable
SCC; otherwise perpetuate from the source
document.
Other fields 72 Perpetuate from the source document.
Ordinal Date 73-76 Enter the date on which the source
document was entered on the storage
activity record.
Blank 77-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZM.
Code
Routing Identifier 4-6 Enter RIC identifying the owner/manager to
Code (TO) which the transaction is being forwarded.
Type of Accountable 7 Enter 1 to identify the number of transactions
Transaction Count included in this transmission.
or
Enter 2 to identify the individual balance
affecting transaction.
Blank 8-27 Leave blank.
Accountable 28-29 Enter the first two positions of the balance
Transaction affecting transactions (D4, D6, D7, D8, D9,
Document Identifier DA, DZ). Leave blank if record position 7 is
Code equal to 1.
Accountable 30 Enter the number of transactions included in
Transaction Count this transmission. Leave blank if record
position 7 is equal to 2.
Blank 31-37 Leave blank.
Number of Balance 38-43 Enter the daily volume of balance affecting
Affecting Transactions transactions applicable to the reported DIC in
record position 28-29. Leave blank if record
position 7 is equal to 1.
Blank 44-66 Leave blank.
Routing Identifier 67-69 Enter the RIC identifying the storage activity
Code (FROM) preparing the transaction.
Date (Transaction) 70-73 Enter the ordinal day on which the transaction
took place.
Blank 74-80 Leave blank.
RECORD
POSITION(S)
FIELD LEGEND ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZN.
Code
Routing Identifier Code 4-6 Enter RIC identifying the owner/manager to
(TO) which the transaction is being forwarded.
Type of Location 7 Enter code from Appendix AP2.23 identifying
Reconciliation Request Type of Location Reconciliation Request.
Number of DIC DZH 8-14 Actual number of DIC DZH requests to be
Transactions to be transmitted, e.g., 0000151.
Transmitted
Date (Cutoff) 15-18 Enter the date for location reconciliation. The
last digit of the calendar is entered in record
position 15 and the day of the year is entered
in record positions 16-18; e.g., 2027 is Jan
27, 2002.
Routing Identifier Code 19-21 Enter RIC identifying the storage activity
(FROM) preparing the transaction.
Type of Media 22 Enter type of media code from Appendix
AP2.15 identifying medium used to transmit
the transactions.
Blank 23-80 Leave blank.
RECORD
POSITION(S)
FIELD LEGEND ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC DZP.
Code
Routing Identifier Code 4-6 Enter the RIC identifying the
(TO) owner/manager to which the transaction is
being forwarded.
Type of Location 7 Enter code from Appendix AP2.23
Reconciliation Request identifying Type of Location Reconciliation
Request.
Number of DIC DZK 8-14 Actual number of DIC DZK requests to be
Transactions to be transmitted, e.g., 0000151.
Transmitted
Date (Cutoff) 15-18 Enter the date for location reconciliation.
The last digit of the calendar is entered in
record position 15 and the day of the year
is entered in record positions 16-18; e.g.,
2029 is Jan 29, 2002.
Routing Identifier Code 19-21 Enter the RIC identifying the storage
(FROM) activity preparing the transaction.
Type of Media 22 Enter type of media code from Appendix
AP2.15 identifying medium used to
transmit the transactions.
Blank 23-80 Leave blank.
AP6. APPENDIX 6
FORMS/MESSAGE FORMATS INDEX
Number Title
AP6.3. RESERVED
AP6.7. RESERVED
AP6.14. RESERVED
AP6-1 APPENDIX 6
DLM 4000.25, Volume 2, April 09, 2022
Change 14
Number Title
AP6.22. ABBREVIATED MESSAGE ASSET REPORT, ETC. (MATERIEL RETURNS PROGRAM)
AP6.26. RESERVED
ISSUE RELEASE/RECEIPT DOCUMENT PREPRINTED FORM WITHOUT LOGMARS
AP6.27. BAR CODING DATA
AP6.28. RESERVED
AP6.30. RESERVED
AP6.37 RESERVED
AP6.38 RESERVED
AP6-2 APPENDIX 6
DLM 4000.25, Volume 2, November 26, 2019
Change 13
AP6.1.2.1. The first line in the body of the message will contain the words
“MILSTRIP REQUISITION.” Thereafter, each requisition will be numbered,
commencing with number 1, and the first 66 positions of data (except for dividing
slashes (/)) will be inserted. The basic requisition will consist of 18 separated field-
lengths of data.
2
Narrative messages shall only be used on an exception basis. When used, each transmission shall be
limited to a maximum of seven transactions or the contents of a single page, whichever is greater.
When an element of data is not available, the field shall be recognized and entered as “BLNK.”
3
Ibid.
4
AP6.1.4. Request for Supply Assistance. Requests for Supply Assistance are
described under Volume 2, Chapter 4 and illustrated in AP6.10. Paragraphs AP6.3.2
and AP6.3.3., above, also apply, except DIC AFC will always be used. This will ensure
manual review and reply using Volume 2, Chapters 4 and 5.
AP6.1.5.2. The first line is the body of the message will contain the words
“MILSTRIP CANCELLATION.” Exception data, remarks, and additional verbiage will be
omitted.
Ibid.
5
Ibid.
6
7
Narrative messages shall only be used on an exception basis. When used, each transmission shall be
limited to a maximum of seven transactions or the contents of a single page, whichever is greater.
8
When an element of data is not available, the field shall be recognized and entered as “BLNK.”.
9
Ibid.
AP6.1.6.3. When abbreviated messages are used, each message will be limited to
a maximum of seven items or the contents of a single page, whichever is greater.
AP6.1.6.4. The first line in the body of the message will contain the words
ABBREVIATED MILSTRIP FOLLOW-UP, CANCELLATIONS, SUPPLY STATUS, OR
SHIPMENT STATUS, as applicable. Thereafter, number each line item, commencing
with number 1. Insert slashes (/) or other appropriate marks between each code and/or
data element as depicted in AP6.11 and AP6.12. The authorized data elements 11 and
code entries for abbreviated messages are as follows:
AP6.1.6.4.1.5. Quantity
10
CJCS Directives Home Page – https://www.jcs.mil/library.
11
When an element of data is not available, the field shall be recognized and entered as “BLNK.”.
AP6.1.6.4.2.5. Quantity
AP6.1.6.4.2.8. Status
AP6.1.6.4.3.4. Quantity
AP6.1.6.4.3.8. Status
AP6.1.6.4.4.2. Quantity
AP6.1.6.4.4.8. Mode-of-Shipment
AP6.1.6.5. Materiel Obligation Validation Form Letters and Messages. Form letter
requests, followup requests, message requests, and replies are provided in AP6.15
through AP6.20 and AP6.32 for use in connection with Materiel Obligation Validation
(MOV) procedures under Chapter C8.
Distribution 3 54-56
Project 3 57-59
Priority 2 60-61
Required Delivery Date 3 62-64
Advice 2 65-66
Routing Identifier 3 67-69
Ownership/Purpose 1 70
Condition 1 71
Management 1 72
Multi Use 1 73
Unit Price 12 7 74-80
12
Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size shall
reflect the unit price as 9 digits for dollars and 2 digits for cents. Refer to ADC 221.
13
Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size shall
reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for
display on the printed form, the generating application may leave blank. Refer to ADC 221.
14
Maximum length is 24 positions: Mark-for clear text (with no DoDAAC or RIC) displays on DoD
shipment documents as two lines of 12 characters each. If text is combined with a DoDAAC, up to 17
clear text characters are allowed. If text is combined with a RIC, up to 20 clear text characters is allowed.
Insert a slash (/)during printing of shipment documentation to separate the DoDAAC or RIC from clear
text; do not perpetuate the slash (/) in the DLMS transaction. Refer to ADC 1009A.
15
Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will
reflect the unit price as 9 digits for dollars and 2 digits for cents. Refer to ADC 221.
16
Ibid
17
Refer to ADC 473A
18
Refer to ADC 1031
19
Capability to support IUID data content within the PDF 417 2D bar code has been approved for
staggered and phased implementation under ADC 44B and ADC 399/ADC 399A. Components have not
reported implementation at this time.
AP6.1.7.1. The Service/Agencies have the option to stock or print the DD Form
1348-2. The DD Form 1348-2 configuration is a DD Form 1348-1A with a perforated
address label attached to the outer right edge. The length of the DD Form 1348-2 is 13
inches. The DD Form 1348-2 may be configured for printing as continuous forms. For
continuous forms configuration, pin-fed strips of one-half inch on each side may be
added. The length of the DD Form 1348-2 with pin-fed strip will not exceed 14 inches.
The address label dimensions of the DD Form 1348-2 are 4-1/4 inches long and 5-1/2
inches high. Use of the address label with preprinted postage data is only authorized
for shipments by the U.S. Postal Service. The address label will contain the following
elements.
AP6.1.7.2.4. Type Service. Enter the appropriate type of delivery service; for
example, first-class-priority, express mail, and Military Official Mail (MOM).
AP6.1.8. IRRD (DD Form 1348-1A or DD Form 1348-2) Continuation Page. This is a
mandatory document for serialized Item shipments containing machine readable bar
codes for the encoded content information to include the serial numbers, unique item
identifiers (UIIs), and batch/lot numbers as required for tracking under a UIT program or
in support of DoD policy for the application of IUID in supply processes. The
continuation page is intended to expedite supply and distribution processes by providing
a means to automate the capture of data using automatic identification technology (AIT)
devices. The continuation page is free form. The data elements and preferred format
are shown in AP6.36.
SAMPLE
SAMPLE
SAMPLE
SAMPLE
1.
A0A/FMI/2/8305001234567/EA00040/FB2300/1150/0111/R/BLNK/A/12/089/BLNK/02/
154/2B
2.
A0A/FMI/B/8305002345678/EA/00001/FB2300/1150/0112/N/BLNK/A/19/089/BLNK/03/
154/BLNK
3.
A0E/FMI/B/1234005123456/EA/00015/FB2300/1150/0113/R/BLNK/A/19/089/BLNK/03/
154/BLNK
4.
A0A/FMI/B/8310002345678/EA/00011/FB2300/1150/0114/R/BLNK/A/14/089/BLNK/02/
155/BLNK
SAMPLE
1. AF1/FMI/2/8305001234567/EA/00040/FB2300/1250/0111/R/BLNK/A/12/089/BLNK/
02/154/2B
2. ATE/FMI/B/8310002345678/EA/00010/FB2300/1250/0114/R/BLNK/A/14/089/BLNK/
02/155/BLNK
3. AFC/FMI/0/8310002345679/EA/00010/FB2300/1250/0115/R/BLNK/A/15/089/BLNK/
02/156/BLNK
AT5 OR ATE FOLLOWUPS WILL REPEAT THE EXCEPTION DATA FROM THE
ORIGINAL A05 OR A0E REQUISITION.
SAMPLE
FB2300/1152/0111/0 8305-01-123-4567
5. KNOWN SOURCE. LIST ANY KNOWN SOURCES FOR THE ITEM TO INCLUDE
NAME, MAILING ADDRESS, AND TELEPHONE NUMBER (IF KNOWN). IF NONE,
SO STATE.
SAMPLE
1. AE1/8305001234567/EA/00040/FB2300/1215/0001/BLNK/02/BB/3015
2. AE1/8310002345678/EA/00012/FB2300/1259/0014/B/02/BV/2283
SAMPLE
1. AS1/00040/FB5249/1165/0001/BLNK/036/02/FB524911650001XXX/B
2. AS1/00012/FB5294/1165/0003/A/C44/02/FB529411650003XXX/B
SAMPLE
1. A0E/FHZ/2/350451234567899/EA/00040/FB2300/0150/0111/R/BLNK/A/12/089/BLNK/02/
154/29
A. CAGE CODE AND PART NUMBER <USE TOTAL CAGE CODE AND PART NUMBER
WHEN TOO LARGE FOR RP 8-22\ WHEN PLACED HERE LEAVE RP 8-22 BLANK>.
B. MFG. NAME
C. MFG. CAT. AND DATE
D. TECH. ORD. NO.
E. TECH.MAN.NO.
F. END ITEM APPL.
G. NAME/DESCRIPTION
H. MAKE
I. MODEL NO.
J. SERIES
K. SERIAL NO.
L. COLOR
M. SIZE
SAMPLE
SAMPLE
SAMPLE
NOTE: Paragraph 2 above shall be omitted if none of the items have been received.
FROM: (Insert the official clear-text name and address of the initiating activity
and its assigned activity address code (AAC).)
TO: (Insert the official clear-text name and address, including the AAC of the
ILCO to receive the Validation Request Documents.)
SUBJECT: Request for Validation of Materiel Obligations
AP6.17.1. Enclosed are (enter quantity) MOV Request documents (enter a listing of the
documents or strike out if not applicable). Each of the enclosed validation requests,
pertaining to FMS and Grant Aid transactions, reflects quantities of the items indicated
held as materiel obligations at this installation as of (enter cutoff date) and for which the
requisitions are aged 180 days or more past the requisitions document number date.
The validation requests are submitted to your activity using the code contained in record
position 54 of the original requisition document.
AP6.17.2. It is required that the item indicated by each validation request be reconciled
with your records. It is also required that each enclosed MOV request be reviewed by
the appropriate country Security Assistance office (SAO) to determine the continuing
need for the item and quantity shown. An AP_ response document is required for each
item contained with the validation request, enclosed/listed, to indicate the desirability for
continuation or cancellation of the requirement.
AP6.17.3. Acknowledge the receipt of the enclosed validation request by inserting the
date and signature below and return the correspondence to this installation.
Enclosures
MOV Request documents
Listing of Request documents (if applicable)
(ACKNOWLEDGMENT OF RECEIPT)
_____________________________________________________________________
________________________
(Signature)
DO NOT DETACH
FROM: (Insert the official clear-text name and address of the initiating activity
and its assigned Activity Address Code (AAC).)
TO: (Insert the official clear-text name and address, including the AAC of the
International Logistics Control Office (ILCO) to receive the MOV
Request documents.)
SUBJECT: Request for Validation of Materiel Obligations
AP6.18.1. The referenced letter forwarded (enter quantity) MOV Request documents,
pertaining to FMS and Grant Aid transactions, and requested that receipt be
acknowledged. This activity has no record of receipt of the requested acknowledgment
nor any response to the validation requests. Enclosed are duplicates/triplicates (strike
out one) of the (enter quantity) MOV Request documents and a listing of these
documents (strike out if not applicable).
AP6.18.2. It is required that the item indicated by each validation request be reconciled
with your records. It is also required that each enclosed validation request be reviewed
by the appropriate country Security Assistance office (SAO) to determine the continuing
need for the item and quantity shown. A response is required for each validation
request to indicate the desirability for continuation or cancellation of the requirement.
Enclosures
MOV Request documents
Listing of Request documents (as applicable)
(ACKNOWLEDGMENT OF RECEIPT)
_____________________________________________________________________
________________________
(Signature)
DO NOT DETACH
(Insert date)
FROM: (Insert the official clear-text name and address of the initiating
International Logistics Control Office (ILCO) and its assigned activity
address code (AAC).)
TO: (Insert the official clear-text name and address, of the security
assistance office (SAO) to receive the validation request documents.)
SUBJECT: Request for Validation of Materiel Obligations.
AP6.19.1. Enclosed are listings (in duplicate) of MOV Request documents and a
complete set of the documents (strike out if not applicable). Each of the enclosed
validation requests, reflect quantities of the indicated item recorded as materiel
obligations as of (enter cutoff date) and for which the requisition are aged 180 days or
more past the requisitions document number date. The requests are submitted to your
activity for validation of the continuing need for the item in the original requisition
document.
AP6.19.2. It is required that the item indicated by each validation request be reconciled
with your records. It is also required that each validation request be reviewed to
determine the continuing need for the item and quantity shown.
AP6.19.3. Request that a copy of the enclosed listing/data Block 8 and Block 21 of the
remarks block, respectively (strike out one) of documents be annotated to indicate: (1)
the quantity of each item still required and (2) the quantity of each item received prior to
receipt of the validation requests. A copy of the annotated listing/the annotated
documents should transmitted by priority mail to this activity to arrive no later than (enter
date), which is 35 calendar days prior to the supply source response due date.
Enclosures
Listings of Validation Requests (in duplicate)
MOV Request documents (as applicable)
(ACKNOWLEDGMENT OF RECEIPT)
_____________________________________________________________________
_________________________________
(Date)
________________________
(Signature)
DO NOT DETACH
(Insert date)
FROM: (Insert the official clear-text name and address of the initiating ILCO
and its assigned AAC.)
TO: (Insert the official clear-text name and address of the security
assistance organization (SAO) to receive the validation request
documents.)
SUBJECT: Follow-up on Request for Validation of Materiel Obligations.
REFERENCES: (Insert reference to original letter.)
AP6.20.1. The referenced letter forwarded a listing (in duplicate) of MOV Request
documents and a complete set of the documents (strike out one if not applicable) and
requested that receipt be acknowledged. This activity has no record of receiving the
requested acknowledgment, nor any response to the validation requests. Enclosed are
duplicates/triplicates (strike out one) of listings for MOV Request documents and a
complete set of the documents (strike out if not applicable). The requests are submitted
to your activity for validation of the continuing need for the item in the original requisition
document.
AP6.20.2. It is required that the item indicated by each validation request be reconciled
with your records. It is also required that each validation request be reviewed to
determine the continuing need for the item and quantity shown.
AP6.20.3. Annotate a copy of the enclosed listing/Data Block 8 and Block U of the
remarks block, respectively, for each document to indicate:
(2) The quantity of each item received prior to receipt of the validation requests.
A copy of the annotated listing/the annotated documents (strike out one) should be
transmitted by priority mail to this activity to arrive no later than enter date, which is 35
calendar days prior to the supply source response due date.
(ACKNOWLEDGMENT OF RECEIPT)
_____________________________________________________________________
______________________________________
(Date)
________________________
(Signature)
4. Percentage of accomplishment
Percent Percent
(Line 3 divided by Line 2).
8 Ibid
9 Ibid.
10 Ibid.
11Reinstatement requests received are measured from the ending of the prior MOV cycle to the ending date of the
current MOV cycle. This report reflects cycle reinstatements.
12 Established procedures to reinstate canceled requisitions last reported as not implemented by USN. Refer to
AMCL 150C.
13 All dollar values will be expressed in thousands.
14 Ibid.
15 Ibid.
16 Ibid.
17 Ibid.
18 Reinstatementrequests received are measured from the ending of the prior MOV cycle to the ending date of the
current MOV cycle. This report reflects cycle reinstatements.
19 Established procedures to reinstate canceled requisitions last reported as not implemented by USN. Refer to
AMCL 150C.
20 All dollar values will be expressed in thousands.
21 Ibid
22 Ibid
23 Ibid
24 Ibid
FTE/SMS/2/5910001882725/EA/53188/FB2300/1221/001/Blank/FM2300/J/6C/Blank/
3AA/ Blank/Blank/DPK/Blank/A/Blank
NOTE: The above example applies equally to other MRP formats by indicating
applicable document identifier code (DIC) and data content displayed in this Appendix.
SAMPLE
5. FSC, FSG, NSN, P/N: {ENTER “N/A” OR FSC, FSG, NSN, P/N TO BE
CANCELLED}.
NOTE: All paragraph headings are mandatory entries. The Department of Defense
activity address code (DoDAAC) is a mandatory entry in Paragraph 2 above, when data
is entered in Paragraph 4 or 5.
SAMPLE
SAMPLE
1 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will
reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for
display on the printed form, the generating application may leave blank. Refer to ADC 221.
1 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will reflect the unit
price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for display on the printed form,
the generating application may leave blank. Refer to ADC 221, DLMS enhancement for communication of unit price and
total price.
AP6.27-1 APPENDIX 6.27
DLM 4000.25, Volume 2, November 26, 2019
Change 13
1 Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will
reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for
display on the printed form, the generating application may leave blank. Refer to ADC 221.
SAMPLE
THE ACTION OFFICER FOR THIS MESSAGE IS (ENTER THE NAME AND DSN
TELEPHONE NUMBER OF RESPONSIBLE INDIVIDUAL HAVING KNOWLEDGE OF
THIS REQUEST).
1
Use of revised MOV temporary suspension procedures for selected activities last reported as not
implemented by USMC. Refer to AMCL 37.
AP6.33.2. The report shall be distributed upon request. All copies of the reports are
provided to the designated DoD Component MILSTRIP Focal Points. Further
dissemination of the reports is the responsibility of each individual DoD Component.
AP6.33.3. The format of the report and the explanation of the derivation of the counts
are as follows:
Total DoD, Service, or DoDAAC (Clear-text name and address of the DoDAAC will be printed)
AFX AFZ No Response to AFZ Unresolved
Generated Generated Discrepancies
Moved to
Discrepancies Advice 30-60 60-90 >90
Advice Code History
Cleared Code Days Days Days
Total ASZ/AE3 – 36 37 36 37 36 37 36 37 36 37 36 37
Matches BF, DE, DF,
DG, DH
Note: 1. All columns show transaction totals and dollar totals. Dollars shall be shown in
multiples of $100.00
2. Report prepared in hardcopy shall page break after each distinct record, i.e., after each
DoDAAC or Service.
1 Establishing intransit control procedures for shipments to DLA Disposition Services Field Offices last
reported as not implemented by USAF and USMC. Refer AMCL 158B.
AP6.34.2. The report is available for review or downloading through Internet access to
the DLA Transaction Services website 1 after the 5th of the month.
1
Defense Automatic Addressing System (DAAS) requires a user ID and logon to gain access to their
various reports and services; such as, the Unauthorized Priority Designator Assignment Report, DoDAAC
queries, fund codes, Routing Identifier Codes (RIC), Military Assistance Program Address Codes
(MAPAC), Military Standard Billing System (MILSBILLS) reports, and other information. If you do not
currently have an approved access (user id and password) please complete a request for access by
going to the following DAAS Website: https://www.transactionservices.dla.mil/sar/warning.asp
NAVY 0 0 0 0 0 0
AIR FORCE 0 0 0 4 19 19
MARINES 0 0 0 0 0 0
DLA 0 0 0 3 30 30
SUB-TOTAL 0 0 0 7 49 49
W90M7W 0 76 0 76 0 0 0 0
W81EWF 0 66 0 51 0 77 0 77
XU ASF EUSTIS
BLDG 2407
FELKER AAF
FORT EUSTIS VA 23604-5594
PD 01 NOT DOWNGRADED 2
AP6.34.4.3. Part VII identifies requisitions that have been subjected to automatic
downgrading of the PD based upon DLA Transaction Services validation and S/A
agreement. Transactions are grouped by PD and indicate in the header the original and
modified PD assignment.
PARTIAL
UII UN077991289S123TS001100223
CAGE 12345 P/N 9988771212SP
LOT MGU12345 S/N 123TS001100223
Notes:
1. Above sample is for illustration only. Implemented version may differ in
placement and size of PDF417 2D bar code. The Code 39 linear bar code and
PDF417 2D bar code requirements are described in this appendix.
2. For shipment quantities of two or more serialized items, in lieu of printing the
PDF417 2D bar code in Block 27 of the DD Form 1348-1A, the continuation page
will contain a single PDF417 2D bar code or multiple Macro PDF417 2D bar
codes (as required by data volume) for the included data (see AP6.36).
3. Unit prices obtained via electronic interfaces that are not constrained by the
MILSTRIP field size will reflect the unit price as 9 digits for dollars and 2 digits for
cents. If total price exceeds available space for display on the printed form, the
generating application may leave blank. Refer to ADC 221.
AP6.35.1.1. Code 39 linear bar coded data with human-readable interpretation for
issue to Services/Agencies.
AP6.35.1.2.1. Block 24. The document number and suffix assigned to the
requisition up to a maximum fifteen characters should be bar coded.
AP6.35.1.2.2. Block 25. The thirteen digit national stock number (NSN) and
two additional code values, as applicable, per Appendix 7.5.2, should be bar coded. In
the absence of the NSN, the manufacturer’s CAGE and part number will be used up to
a maximum of 15 characters.
AP6.35.1.2.3. Block 26. The two character unit of issue (UI) code, five digit
zero filled quantity (QTY), one character condition code (COND), a seven digit or eleven
digit zero filled unit price (UP) showing dollars and cents with no decimal, and the first
position and last 3 positions of supplementary address (SUPADD) should be bar coded.
The bar code will have a fixed length of 19 or 23 characters to include leading zeros and
spaces depending on the implemented version of the unit price annotation noted in
Appendix 8.48.
AP6.35.1.3. The application of Code 39 linear bar codes on the DD Form 1348-1A
should be in accordance with MHIA MH10.8.1, Annex A and MIL-STD-129 (as revised).
The specific technical information provided in is not intended to be compressive and
should be used in conjunction with the MIL-STD 129. A data check character is not
used. The following requirements and exceptions apply:
AP6.35.1.3.2. Blocks 24 and 25. The length of the bar code must not be
greater than 4.0 inches (101.6 mm). Each bar code must have 15 characters. When
there is an absence of any character(s) (less than 15) within these two bar codes,
encoded spaces will be used as fillers (based upon specific encoded data element).
AP6.35.1.3.3. Block 26. The length of the bar code must not be greater than
4.5 inches (114.3 mm). Encoded spaces will be used as fillers for any unknown, or
unencoded, data characters.
AP6.35.1.3.4. Block 27. The length of the bar codes must not be greater
than 4.00 inches (101.6 mm) for serial numbers that may have up to 30 characters. The
narrow element X-dimension should be at least 0.01 inches (.25mm) but will not be less
than 0.007 inches (0.1778 mm) for these high-density bar codes. The wide to narrow
ratio should be 3 to 1 but must not be less than 2 to 1.
AP6.35.2.2. The PDF417 2D bar code used for shipping and receiving should be
printed with no more than 12 data columns in width. The use of 13 to 18 data columns is
allowed for inventory or supporting documentation applications (identification marking,
ammunition/explosive marking, packing list, etc.) if smaller PDF417 2D bar codes
cannot accommodate the increased data requirements. A PDF417 2D bar code
Start Stop
P attern P attern
AP6.35.2.3. The PDF417 2D bar code must not exceed 2.4 inches (61 mm) in
height to include the surrounding minimum quiet zone.
AP6.35.2.4. The PDF417 2D bar code must have a minimum quiet zone of 0.04
inches (1 mm) above, below, to the left, and to the right.
AP6.35.2.6. The PDF417 2D bar code must have a minimum row height of three
times the width of the narrow element (X-dimension).
AP6.35.2.7. The PDF417 2D bar code will use error correction level 5.
AP6.35.2.8. The label should be designed so that two bar codes are not next to
each other in the same horizontal plane unless the label is wide enough to reduce the
possibility of interference with successful bar code scanning.
AP6.35.2.10. The quality of the printed PDF417 2D bar code must meet a grade
requirement of 2.5 (B) at the point of production when measured in accordance with
ISO/IEC 15438 with a measurement aperture of 0.25 mm and an inspection wavelength
of 660 ± 10 nm.
AP6.35.3. Data Format. The following table provides examples and explanations of the
data stream for a PDF417 2D bar code.
AP6.35.3.7. Sample Data (Column 7) contains sample data for the field indicated.
Category/Description
Separator / Trailer
Total Characters
Characters
Format Header
ANSI MH10.8.2 Sample Data
Compliance
Indicator
Format 06 (Compliance,
Data Field Data Format
Data Identifier (DI) Header, Identifier
(DoD Usage) (Type/Length)
or and
Format 07 Data)
Data Element Identifier (DEI)
12S
G Category 19, Traceability Number for an Document Number 12SW90GF88296
S an14..15 19
Entity: Document Number (internally Includes Suffix Code when applicable 20258
assigned or mutually defined)
National Stock Number (NSN) or Stock
Identification Elements
May reflect NSN, CAGE Code/part number,
FSC, etc., as applicable. May also include
associated coding, e.g., Type of Pack, USN
Special Material Identification Code (SMIC) or
N USAF Materiel Management Aggregation Code
G
(MMAC). This data content is analogous to the
S Category 14, Industry Assigned Codes: legacy MILSTRIP stock number field. When an..15 N5340013145957 17
National/NATO Stock Number (NSN) using this data field to identify an item byCAGE
Code/part number, also use separate identifiers
below for CAGE Code and part number. For
unique item tracking or in support of DoD policy
for the application of IUID in supply processes,
use this identifier for the NSN and use separate
identifiers listed below to uniquely identify a
specific individual item.
7Q
Quantity and Unit of Issue
Category 17, Measurement:
G Quantity, Amount, or Number of Pieces in Do not include leading zeros an..5+an2 7Q1EA 10
S
the format: Quantity followed by the two Staffing Note: Original footnote deleted;
character ANSI X12.3 Data Element restricted quantity to 1.
Number 355 Unit of Measurement Code
V Routing Identifier Code – Shipping Activity
G an3 SRR 5
S Category 22, Party to the Transaction: Identifies the RIC of the shipping activity
Supplier Code assigned by Customer (MILSTRIP legacy transaction rp 4-6).
7V
Routing Identifier Code – ICP/IMM
Category 22, Party to the Transaction:
G
S Code assigned to a party which has Identifies the RIC of the activity originating the an3 7VN32 6
financial liability for an entity or group of MRO/LRO/DRO (MILSTRIP transaction rp 67-
entities (e.g., owner of inventory) (mutually 69).
defined)
8V
Distribution Cognizance Code
G
S Category 22, Party to the Transaction: an2 8V7V 5
Last two positions of DoD Distribution Code
Customer Code assigned by Customer
used for DD Form 1348-1A linear bar code data.
2R
G Condition Code an1 2RA 4
S Category 18, Miscellaneous: Return code
assigned by the Customer
12Q Unit Price
GS Category 17, Measurement: Value Configured as 9 digits (whole dollars), decimal, n..9.n2+an3 12Q50.20USD 19
followed by an ISO 4217 data element and 2 digits (cents) followed by “USD” indicating
code for representing unit of value of U.S. dollars. Do not include leading zeros.
Category/Description
Separator / Trailer
Total Characters
Characters
Format Header
ANSI MH10.8.2 Sample Data
Compliance
Indicator
Format 06 (Compliance,
Data Field Data Format
Data Identifier (DI) Header, Identifier
(DoD Usage) (Type/Length)
or and
Format 07 Data)
Data Element Identifier (DEI)
Repair Value
Category/Description
Separator / Trailer
Total Characters
Characters
Format Header
ANSI MH10.8.2 Sample Data
Compliance
Indicator
Format 06 (Compliance,
Data Field Data Format
Data Identifier (DI) Header, Identifier
(DoD Usage) (Type/Length)
or and
Format 07 Data)
Data Element Identifier (DEI)
4R
U.S. Department of Defense Identification
G Category 18, Miscellaneous: U.S.
S Code (DoDIC) an4 4RA576 7
Department of Defense Identification Code
The DoDIC currently used to identify this item.
(DoDIC)
11V
Ownership Code
G The ownership code of the military Service or an1 11V5 5
S Category 22, Party to the transaction:
Ownership Code other activity having title to the assets
Serviceable Condition Expiration Date for
7D
G Ammunition and Explosive (A&E)
S n4 7D0217 7
Category 4, Date Also known as Maintenance/Expiration/Next
Inspection Due (M/E/N) Date. (MMYY).
G Consignee DoDAAC
S 27 an6 27WK4FV9 9
Reflects ship-to DoDAAC (Block 3)
Supplementary Address
G 81 an6 81WK4FV9 9
S
Derived from rp 45-50 of the requisition
H Mark-for Party DoDAAC an6+UC
Category 8, Name of Party: DI (H) is
G HW90GF8+UC 10
S followed by the (Mark-for DoDAAC) Reflects DoDAAC in MARK FOR (Block 4)
followed by a (+) character followed by the The (+UC) is
EDIFACT Code List 3035 code value (UC) encoded data
1
This row added as an administrative update; although this row is shown in ADC 1252 it was
inadvertently not added in formal change 10
Category/Description
Separator / Trailer
Total Characters
Characters
Format Header
ANSI MH10.8.2 Sample Data
Compliance
Indicator
Format 06 (Compliance,
Data Field Data Format
Data Identifier (DI) Header, Identifier
(DoD Usage) (Type/Length)
or and
Format 07 Data)
Data Element Identifier (DEI)
AP6.35.4 Encoding the Separator/Trailer Characters. The following table shows the
encoded values that can be used for the non-printing ASCII control characters used as
Element Separators.
RS 1E 30
GS 1D 29
EOT 04 04
AP6.35.5.2. For an IRRD quantity of one item, the Format 06 envelope may also
be used to associate the format applicable item-specific data (e.g. serial number, UII,
batch/lot, etc.) for the uniquely identified item. A single data qualifier or paired data
qualifiers (e.g., UII (DI 25S), serial number (DI S), batch/lot (DI 1T)) may be used with
the Format 06 envelope to identify and associate the serialized data for an item. The
UII and serial number (used for tracking under a UIT program or in support of DoD
supply policy for the application of IUID) will be encoded to based upon IUID Indicator Y
when they are when machine readable and readily available, or when retrievable from
the system generating the form. However, at a minimum, the serial number is required
for a NSNs falling under a UIT program.
AP6.35.5.3. For IRDD quantities of two or more items, use the DD Form 1348-1A
Continuation Page (see AP6.36).
WAREHOUSE/SHIPPING INSTRUCTIONS:
OTHER INSTRUCTIONS:
Note: Example 1 is for illustration only and is not actual size. The sample shows only
the first page of a multi-page set; the follow-on pages would show the listed serial
number linear bar code information for the remaining items in the shipment.
34.WAREHOUSE BY 35.DATE
(SERIAL NUMBER)
TFS1 7.58
39 TCN
40.REMARKS
(SERIAL NUMBER)
41.FIRST DEST ADDRESS 42.SHIP TO ADDRESS
W6TC 596TH USA TRANS SURF BDE 0001 CS HHC HHC X1 THTR SPT
TRANS SDAT OPT BLDG 101 6280 SUNNY
POINT ROAD SE
25461T
AMMO SUPPLY POINT KUWAIT CLASS V AL
JALAIL ASP
SOUTHPORT NC 28461-7800
Note: Example 2 is an illustration only and is not actual size. The sample reflects A&E
Continuation Page for the DD Form 1348-1A prepared as a separate document.
W53XMD
CRANE ARMY AMMUNITION
ACTIVITY 300 HWY 361 M132200
CRANE, IN 47522-5009
2 1 12.5 1.82
UN#001
UN 0181 PSN: ROCKETS 1.1E PG II
HA29
ROCKET, HIGH EXPLOSIVE
PL 1 25LBS 2.364 FT
Shipment is a United States Munitions List (USML) Item. Shipment is property of the U.S.
Government. Title remains with U.S. Government. Ultimate end user is agency of U.S.
Government (Dept. of Defense). Not intended for introduction to commercial economy.
Shipment is for the exclusive end use of U.S. Military Forces.
34.WAREHOUSE BY 35.DATE
40.REMARKS
(SERIAL NUMBER)
41.FIRST DEST ADDRESS 42.SHIP TO ADDRESS
2ND BN 3RD MARINES UDP EAST
SUPPLY OFFICER
MF 2ND BN 3RD MAR SUPO UDP EAST
25461T BLDG 1094 TEL 808 257 5284
MCBH KANEOHE BAY HI 96863-3006
Note: Example 3 is an illustration only and is not actual size. It is acceptable for AIT
systems to print both the 1348-1A and the continuation page on a single page when
AP6.36.1. IRRD (DD 1348-1A or DD Form 1348-2) Continuation Page. There are two
unique continuation pages addressed in AP6.36, the standard continuation page used
with all commodities other than A&E, and a continuation page specific to A&E. The
A&E continuation page may be produced by AIT systems either on the same page as
the 1348-1A if space permits, or separately. When the continuation page is used as an
extension of the IRRD Block 27, it will contain the following minimum data:
AP6.36.1.5. PDF417 2D bar code or Macro PDF417 2D bar codes. See Appendix
6.35 for included data elements, their respective data identifiers, and print quality
requirements.
1
Refer to ADC 1175.
AP6.36.3. Code 39 Linear Bar Code Business Rules. Format requirements for the DD
Form 1348-1A Continuation Page applications are:
AP6.36.3.1. The minimum bar height should be at least 0.50 inches (12.7 mm),
but must not be less than 0.25 inches (6.3 mm.).
AP6.36.3.2. The space provided on the continuation page must be able to encode
up to 30 characters for the serial number and the bar code should not exceed 4 inches
in length.
AP6.36.3.5. The ASCII characters encoded will consist of the standard uppercase
characters, numbers, and symbols identified ISO/IEC 16388, Table 1. The full ASCII
128 character set will not be used.
AP6.36.4. Common data for all of the IRDD items will be encoded in the PDF417 (or
Macro PDF417) 2D bar code’s first ISO/IEC 15434 Format 06 and Format 07
envelopes, as applicable.
AP6.36.5. UIIs and serial numbers (including batch/lot number when required for
tracking) will be encoded and linked together to support DoD supply policy based upon
IUID Indicator Y when they are machine readable and readily available, or when
retrievable from the AIS generating the form. However, at a minimum, the serial
number is required for NSNs falling under a UIT program.
AP6.36.5.1. One item. If the continuation page is used for an IRDD quantity of
one serialized item, the first Format 06 envelope may also be used to associate item-
specific data for the uniquely identified item. A single data qualifier or a single set of
data qualifiers (e.g., UII (DI 25S), serial number (DI S), batch/lot (DI 1T)) may be used
with the Format 06 envelope to identify and associate the serialized data for an item.
AP6.36.5.2. Two or more items. For an IRDD quantity of two or more serialized
items, an additional Format 06 envelope (one per item) will be used for each item to
encode item-specific data (e.g., UII (DI 25S), serial number (DI S), batch/lot (1T)) for the
uniquely identified item.
AP6.36.6. PDF417 2D Bar Code Business Rules. If only one PDF417 2D bar code is
required to encode the information, it will be a standard PDF417 2D bar code and not a
Macro PDF417 2D bar code. If two or more PDF417 2D bar codes are required, they
must be Macro PDF417 2D bar codes. The PDF417 2D bar codes will be on the first
page(s) of the continuation page to be followed by each item’s serial number encoded
with Code 39 linear bar codes.
AP6.36.6.1. Macro PDF417 2D bar codes will be used when the encoded data
message file exceeds the capacity of a single PDF417 2D bar code. When space is
exhausted in a PDF417 2D bar code’s data capacity, the application program must
begin using Macro PDF417 2D bar codes to encode the data content in multiple bar
codes. There is no requirement to repeat shipment-related data in the next Macro
PDF417 2D bar code; the Macro PDF417 2D bar codes are linked with codewords to
derive a single transaction file. A full size 18 data column 2D bar code (PDF417 or
Macro PDF417) can encode approximately 1100 characters at Error Level 5. The
character capacity of the PDF417 2D bar code is based on a PDF417 2D bar code limit
of 925 codewords, the compaction algorithm used to encode data in a codeword, and
the PDF417 2D bar code’s error correction level.
AP6.36.6.3. Each Macro PDF417 2D bar code represents a segment of the whole
file. To reconstruct the whole file, the segments need to be placed in the correct order.
Each Macro PDF417 2D bar code is encoded with a control block of codewords that
facilitates this reassembly process after all the PDF417 2D bar codes have been
scanned at least once in any sequence order.
AP6.36.6.4. Each receiving system used to scan Macro PDF417 2D bar codes will
need to determine if the system scanner will operate in a buffered or unbuffered mode.
As the Macro PDF417 2D bar codes are scanned, the de-packetizing function
reconstructs the original message. If operating in buffered mode, the PDF417 2D bar
code codeword de-packetizing function is in the scanner’s decoder; if operating in
unbuffered mode, it is in the receiving system decoder.
AP6.36.7. Example Macro PDF417 2D Bar Codes. The following two Macro PDF417
2D bar codes from the continuation sample page are printed full size for system
developer review. The two Macro PDF417 2D bar codes contain all of the linear bar
coded information from the parent DD Form 1348-1A (or DD Form 1348-2), additional
item identification detail, and the included UIIs and/or serial numbers. The annotations
of ^(nnn) in the encoded strings below denote Macro PDF417 code words.
Macro PDF417 2D Bar Code Samples (actual size) from Continuation Page
[)>RS06GS12SW90GF8829620258GSN5340013145957GS7Q60EAGSVS9IGS7VN32GS2RAGS12Q050.20USDGS5P9999
12GS1TMGU12345GS17V1AAA9GS1P9988771212SPRS07GS03ZCNGSB6 7VGS27WK4FV9GS38LOOP,
STRAPGS32999GSB702GSB8PGS81WK4FV9RS06GSS30-CHARACTER SERIAL NO
EXAMPLERS06GSSA1B2C3112345678RS06GSSA1B2C3234567890RS06GS25SD1AAA9A1B2C33GSSA1B2C33RS06
GS
25SD1AAA9A1B2C34GSSA1B2C34RS06GS25SD1AAA9A1B2C35GSSA1B2C35RS06GS25SD1AAA9A1B2C36GS
SA1B2C36RS06GS25SD1AAA9A1B2C37GSSA1B2C37RS06GS25SD1AAA9A1B2C38GSSA1B2C38RS06GS25SD1AA
A9A1B2C39GSSA1B2C39RS06GS25SD1AAA9A1B2C310GSSA1B2C310RS06GS25SD1AAA9A1B2C311GSSA1B2C
311RS06GS25SD1AAA9A1B2C312GSSA1B2C312RS06GS25SD1AAA9A1B2C313GSSA1B2C313RS06GS25SD1AAA9
A1B2C314GSSA1B2C314RS06GS25SD1AAA9A1B2C315GSSA1B2C315RS06GS25SD1AAA9A1B2C316GSSA1B2C3
16RS06GS25SD1AAA9A1B2C317GSSA1B2C317RS06GS25SD1AAA9A1B2C318GSSA1B2C318RS06GS25SD1AAA9
A1B2C319GSSA1B2C319RS06GS25SD1AAA9A1B2C320GSSA1B2C320RS06GS25SD1AAA9A1B2C321GSSA1B2C3
21RS06GS25SD1AAA9A1B2C322GSSA1B2C322RS06GS25SD1AAA9A1B2C323GSSA1B2C323RS^(928)^(111)^(100
)^(129)^(923)^(001)^(111)^(002)
06GS25SD1AAA9A1B2C324GSSA1B2C324RS06GS25SD1AAA9A1B2C325GSSA1B2C325RS06GS25SD1AAA9A1B
2C326GSSA1B2C326RS06GS25SD1AAA9A1B2C327GSSA1B2C327RS06GS25SD1AAA9A1B2C328GSSA1B2C328RS
06GS25SD1AAA9A1B2C329GSSA1B2C329RS06GS25SD1AAA9A1B2C330GSSA1B2C330RS06GS25SD1AAA9A1B
2C331GSSA1B2C331RS06GS25SD1AAA9A1B2C332GSSA1B2C332RS06GS25SD1AAA9A1B2C333GSSA1B2C333RS
06GS25SD1AAA9A1B2C334GSSA1B2C334RS06GS25SD1AAA9A1B2C335GSSA1B2C335RS06GS25SD1AAA9A1B
2C336RS06GS25SD1AAA9A1B2C337RS06GS25SD1AAA9A1B2C338RS06GS25SD1AAA9A1B2C339RS06GS25SD1A
AA9A1B2C340RS06GS25SD1AAA9A1B2C341RS06GS25SD1AAA9A1B2C342RS06GS25SD1AAA9A1B2C343RS06G
S
25SD1AAA9A1B2C344RS06GS25SD1AAA9A1B2C345RS06GS25SD1AAA9A1B2C346RS06GS25SD1AAA9A1B2C
347RS06GS25SD1AAA9A1B2C348RS06GS25SD1AAA9A1B2C349RS06GS25SD1AAA9A1B2C350RS06GS25SD1AA
A9A1B2C351RS06GS25SD1AAA9A1B2C352RS06GS25SD1AAA9A1B2C353RS06GS25SD1AAA9A1B2C354RS06GS2
5SD1AAA9A1B2C355RS06GS25SD1AAA9A1B2C356RS06GS25SD1AAA9A1B2C357RS06GS25SD1AAA9A1B2C3
58RS06GS25SD1AAA9A1B2C359RSEOT^(928)^(111)^(101)^(129)^(923)^(001)^(111)^(002)^(922)
Item 1 Date of Preparation. Use month, day, and four-position year format for
the date the reporting activity prepares the SDR (e.g., January 10,
2012).
Item 2 Report Number. Provide the locally assigned report number. For
Security Assistance shipments, this consists of one alpha character to
identify the initiating office in-country, four numeric characters for
number control, two alpha characters for the foreign customer country
and three to six alphanumeric characters for the master and line item
case designator, i.e., A0010-JA-KBD/001. For any unnumbered reports
received, the International Logistics Control Office (ILCO) shall assign
number x9000 to x9999 and so advise the foreign country customer on
the receipted copy. Suffix code R added to the report number indicates
the purchaser has asked for reconsideration of the report disposition.
Suffix code C added to the report number indicates that the purchaser
has contested the U.S. Government's decision on a request for
reconsideration.
Item 3 To. In-the-clear name, address, ZIP code and DoD Activity Address
Code (DoDAAC) and/or Routing Identifier Code (RIC) (if assigned), and
attention symbol/code of action activity. The action activity is based
upon the origin of the shipment. If forwarding to the ICP, the RIC of the
ICP is located in positions 67-69 of the DD Form 1348-1A. If forwarding
to the Defense Distribution Depot, the RIC of the shipping depot is
located in positions 4-6 of the DD Form 1348-1A.
Item 4 From. DoDAAC, name, address and ZIP code of the reporting activity
or Security Assistance customer (consignee). The in-the-clear address
shall be entered.
Item 7a Shipper's Number. Enter shipment number (when more than one
shipment is made under a contract or requisition) and contract/contract
line item number/document number (e.g., contract, purchase order).
For Security Assistance, also include the shipment date to distinguish
multiple shipments from a contractor source.
Item 7b Office Administering Contract. Name, address, and ZIP code of the
Contract Administration Office (CAO) activity that directed/arranged
shipment.
Item 10b Discrepancy Unit Price. Enter the unit price as billed or shown on
shipping document.
Item 10c Discrepancy Total Cost. For shipping discrepancies, enter the total
value of materiel (10a x 10b). For U.S. SDR packaging deficiencies,
enter total cost for corrective packaging of all discrepant items. For
SDRs reporting both a packaging and a shipping discrepancy on the
same item, enter on separate lines both the total value of the materiel
and the total cost for corrective packaging.
Item 10d Discrepancy Code. Nature of the discrepancy using the applicable
discrepancy code. See Appendix 7.28 for discrepancy codes that
supplements those listed on the face of the form. If a condition exists
that is not listed, use code Z1 and describe discrepancy in Item 12,
Remarks. Use up to three discrepancy codes. When Discrepancy
Code Q1, Product Quality Deficiency, or C2, Expired Shelf Life, is
applicable, enter the following information under Item 12, Remarks:
1. Manufacturer's name and commercial and government entity (CAGE) code (if
available).
3. Date manufactured, date cured, date assembled, date packed (apply one as
appropriate), and expiration date for Type I (nonextendible) shelf-life
items and inspection or test date for Type II (extendible) shelf-life items.
Include the date overhauled/rebuilt if pertinent.
4. Lot/batch number.
Item 11 Action Code. Nature of the action requested identified by action code.
See Appendix 7.28 for action codes that supplements those listed on
the face of the form.
Item 12 Remarks.
General Conditions. Use for any supplemental information when the combination of
discrepancy codes and action codes needs clarification; when
discrepancies need explanation; and when a breakdown of cost to
report, in terms of labor man-hours and materials, is required. Specific
data such as appearance, lot/batch number, manufacture/packaging
date, inspector number and inspection date, probable cause of
improper packaging, and suggested corrective action should be entered
here. Provide photos where it would assist in determining the
cause/validity of the discrepancy/deficiency.
Information Contact. Include name and communication numbers, (e.g., DSN and
commercial telephone numbers, facsimile number, and e-mail address)
of the person to be contacted for additional information if different from
that entered in Item 14a.
Special conditions. For shortages or nonreceipt of GSA items shipped via U.S.
Postal Service--cite whether all packages shown as shipped in Item 5 of
GSA or DD Form 1348-1A were received. For medical materiel
requiring refrigeration or frozen storage--cite the information requested
on the special instruction sheet, which is included with shipments of
such materiel. For classified materiel--cite whether indications of
container tampering were or were not evident; indicate whether a
security deviation inquiry may be necessary at the origin.
Item 14a Typed or Printed Name, Title, and Phone Number of Preparing Official.
Self-explanatory. Include both full commercial, DSN, and facsimile
communication numbers and e-mail address, if available.
Item 16 From. The name, DoDAAC and/or RIC, and address of the activity
preparing the reply.
Item 18 To. Enter address (including DoDAAC and/or RIC (if assigned)) of the
activity indicated in Item 4 on face of the form. For Security Assistance,
use the address for the appropriate ILCO.
Item 21 Enter an "X" to indicate to the reporting activity that a new requisition is
required if the materiel is still needed. Also, see instructions for Item 23.
Item 22 Enter an "X" to indicate a replacement shipment will be made and the
approximate shipment date. Also, see instructions for Item 23.
Item 23 Remarks
Item 24a Typed or Printed Name and Phone Number of Preparing Official. This is
the individual authorized to provide an SDR response. Include both DSN
and full commercial telephone numbers.
Item 24c Date. Use month, day, and four-position year (e.g., January 10, 2012).
AP6.39.3.1. At the top of the original report annotate the appropriate word
("FOLLOW-UP," "CORRECTION," or "CANCELLATION") and the date the follow-up,
correction, or cancellation was prepared and forward to the same distribution addresses
as the initial report.
AP6.39.3.3. For corrected or cancelled SDRs, the initiator shall explain the
clarifying data in detail in the "Remarks" block. Include the signature, date, DSN
number, complete commercial telephone number, and e-mail address, if available, of
the person preparing the revised report.
AP7. APPENDIX 7
DATA ELEMENTS AND CODES INDEX
Number Title
AP7.1 DOCUMENT IDENTIFIER CODES
AP7AP7-1 APPENDIX 7
DLM 4000.25, Volume 2, November 26, 2019
Change 13
Number Title
AP7.24 AUTOMATED DATA PROCESSING IDENTIFICATION CODES
AP7AP7-2 APPENDIX 7
DLM 4000.25, Volume 2, November 26, 2019
Change 13
AP7.1.2. DIC is a mandatory entry on all documents entering and leaving the supply
distribution systems under MILSTRIP; therefore, each transaction shall be identified by
an appropriate code.
AP7.1.4.1.3. RESERVED:
AP7.1.4.3. The third position (rp 3) may be either alphabetic or numeric. When
used with alphabetic A in the first position of requisitions, passing orders, referral
orders, redistribution orders, and MROs, any numeric in rp 3 shall signify that shipment
of materiel is intended for an Outside Continental United States (OCONUS) consignee.
Conversely, when rp 3 is any alphabetic character, it shall mean shipment to a domestic
recipient. The actual character (regardless of whether numeric or alphabetic) will
indicate the content of the stock or part number field.
AP7.1.5. The alphabetic FT_ series DICs are applicable to reporting and return of
materiel to a distribution system.
AP7.1.5.1. First two positions (rp 1 and 2): Alphabetic FT shall identify
transactions relating to the reporting and return of materiel to distribution systems
irrespective of Component or systems within a Component.
1
See DTR 4500.9-R. “Defense Transportation Regulation.”
2
Processing activity shall, by screening of documents, determine whether the incoming requisition type
document contains NSN/NATO Stock Number, part number, or other. If item identifying data can be
acted upon without need for further exception data, the code in rp 3 shall be changed, as appropriate, to
correspond to the NSN/NATO Stock Number, part number, or other in rp 8-22.
3
Ibid.
4
Ibid.
A2E Redistribution Order For domestic shipment/with exception data 5. Also for
use in support of the Retail Transportation and
Supply Receipt and Acknowledgment Interchange
(transactions identified by a Distribution Code = 111)
from retail supply to transportation (DLM 4000.25,
Volume 3, Chapter 2).
A31 Passing Order For overseas shipment/with NSN/NATO stock
number
5
Ibid.
6
Ibid.
7
Ibid.
8
Ibid.
9
Ibid.
A55 Materiel Release For overseas shipment/with exception data 10. Also
Order for use in support of the Retail Transportation and
Supply Receipt and Acknowledgment Interchange
(transactions identified by a Distribution Code = 111)
from retail supply to transportation ( DLM 4000.25,
Volume 3, Chapter 2).
10
Ibid.
A5J Disposal Release From ICP to storage activity (may also be used by
Order local generating activity).
Also for use in support of the Retail Transportation
and Supply Receipt and Acknowledgment
Interchange (transactions identified by a Distribution
Code = 111) from retail supply to transportation (DLM
4000.25, Volume 3, Chapter 2).
11
Ibid.
12
Ibid.
13
Ibid.
AC3 Cancellation By rp 54
14
Use of DIC AB_ changed from intra- to inter-Service for direct delivery from procurement last reported
as not implemented by Government Services Administration (GSA). Refer to AMCL 155.
15
Ibid.
16
Ibid.
17
Ibid.
ADR FMS Notice of To designate CR/FF. Will accompany the FMS NOA
Availability (export Initial Detail document
release Required)
18
Used by internet ordering applications on requisitions, modifications, and follow-ups for subsequent
rejection by DAAS. Refer to ADC 328.
AF3 Follow-up By rp 54
AFT Request for Shipment From consignee (based on signal code) to source of
Tracing-Registered, supply and ILCO to source of supply unless business
Insured, and Certified firm or civilian contractor not required to process
Parcel Post follow-ups received from Military sources. In this
case, from consignee to ICP and ILCO to ICP
AFY 20 Follow-up (Request for A request to source of supply to obtain the DoDAAC
DoDAAC of Initial of the initial (origin) transportation shipping activity for
Transportation tracing shipments.
Shipping Activity)
19
Establishing intransit control procedures for shipments to DLA Disposition Services Field Offices last
reported as not implemented by USAF and USMC. Refer AMCL 158B.
20
Procedures requesting and/or providing the DoDAAC of the initial shipping activity last reported as not
implemented by GSA. Refer to AMCL 5.
AK3 Follow-up on By rp 54
Cancellation Request
(process as
cancellation if original
cancellation not
received)
21
Processing activity shall, by screening of documents, determine whether the incoming requisition type
document contains NSN/NATO Stock Number, part number, or other. If item identifying data can be
acted upon without need for further exception data, the code in rp 3 shall be changed, as appropriate, to
correspond to the NSN/NATO Stock Number, part number, or other in rp 8-22.
22
Ibid.
AMJ Disposal Release To storage activity from ICP (Not applicable for
Order Modification MILSTRIP legacy formatted transactions; used for
DLMS transaction exchange only).
23
Revised requisition modifier procedures last reported as not implemented by USMC. Refer to AMCL
123C.
APX Notice of Non-receipt Notification to DAAS or the source of supply that the
of Total Batch of MOV total number of documents indicated in the control
Documents document was not received
ARA Materiel Release For release of quantity greater than requested (due to
Confirmation unit pack).
Also for use in support of the Retail Transportation
and Supply Receipt and Acknowledgment
Interchange (transactions identified by a Distribution
Code = 111) from retail supply to transportation (DLM
4000.25, Volume 3, Chapter 2).
24
Use of revised MOV temporary suspension procedures for selected activities last reported as not
implemented by USMC. Refer to AMCL 37.
25
Established procedures to reinstate canceled requisitions last reported as not implemented by USN.
Refer to AMCL 150C.
ARB Materiel Release For release of quantity less than requested (due to
Confirmation unit pack).
Also for use in support of the Retail Transportation
and Supply Receipt and Acknowledgment
Interchange (transactions identified by a Distribution
Code = 111) from retail supply to transportation (DLM
4000.25, Volume 3, Chapter 2).
ARH Force Closed Materiel For use by ICPs and storage activities to force close
Release Confirmation open MRO records.
Also for use in support of the Retail Transportation
and Supply Receipt and Acknowledgment
Interchange (transactions identified by a Distribution
Code = 111) from retail supply to transportation (DLM
4000.25, Volume 3, Chapter 2).
ARK Disposal Release From storage activity to ICP for release of quantity
Confirmation greater than requested.
Also for use in support of the Retail Transportation
and Supply Receipt and Acknowledgment
Interchange (transactions identified by a Distribution
Code = 111) from retail supply to transportation (DLM
4000.25, Volume 3, Chapter 2).
ARL Disposal Release From storage activity to ICP for release of quantity
Confirmation less than requested.
Also for use in support of the Retail Transportation
and Supply Receipt and Acknowledgment
Interchange (transactions identified by a Distribution
Code = 111) from retail supply to transportation (DLM
4000.25, Volume 3, Chapter 2).
AS8 Shipment Status To DAAS from S/A for distribution by DAAS of AS_
shipment status under MILSTRIP distribution rules
ASH Pseudo Shipment From ICP to DAAS for distribution under MILSTRIP
Status for rules. This transaction shall be used by the ICP as
Unconfirmed Materiel shipment status for unconfirmed MROs
Release Orders
ASY 26 Shipment Status The source of supply response to the request for
(DoDAAC of Initial DoDAAC of the initial (origin) transportation shipping
Transportation activity
Shipping Activity)
26
Procedures requesting and/or providing the DoDAAC of the initial shipping activity last reported as not
implemented by GSA. Refer to AMCL 5.
27
Processing activity shall, by screening of documents, determine whether the incoming requisition type
document contains NSN/NATO Stock Number, part number, or other. If item identifying data can be
acted upon without need for further exception data, the code in rp 3 shall be changed, as appropriate, to
correspond to the NSN/NATO Stock Number, part number, or other in rp 8-22.
28
Ibid.
AU8 Reply to Cancellation To DAAS from S/A for distribution by DAAS of status
Request-Shipment (AU_) under MILSTRIP distribution rules
Status
AX1 29 Inventory Control point From ICP to MCA to validate GFM transactions to a
Government- valid contract. May be intercepted by DAAS when
Furnished Materiel applied to contractor requisitions submitted via DoD
Validation Request EMALL indicating payment by corporate credit card.
AX2 30 Management Control From MCA to ICP. Response to ICP validation
Activity Government- request of GFM transactions. Also used by DAAS
Furnished Materiel when applied to contractor requisitions submitted via
Validation Response DoD EMALL indicating payment by corporate credit
card.
29
Procedures to control access to DoD materiel inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
30
Processing activity shall, by screening of documents, determine whether the incoming requisition type
document contains NSN/NATO Stock Number, part number, or other. If item identifying data can be
acted upon without need for further exception data, the code in rp 3 shall be changed, as appropriate, to
correspond to the NSN/NATO Stock Number, part number, or other in rp 8-22..
FTB Reply to Follow-up for Reserved for DLM 4000.25, Volume 4 (MILSBILLS
Materiel Return Procedures)
Program Credit
FTP Follow-up for Materiel Reserved for DLM 4000.25, Volume 4 (MILSBILLS
Return Program Credit Procedures)
Use of part-numbers in the Materiel Returns Program last reported as not implemented by USMC.
31
1
Refer to the Treasury Financial Manual Supplement--FAST Book (Part II link to Independent Agencies)
for listing of Federal Civil Agency codes
https://www.fiscal.treasury.gov/fsreports/ref/fastBook/fastbook_home.htm used as the first two positions
of the activity address code (AAC).
2
Combination codes authorized for USCG and DLA. Refer to ADC 319.
3
Mandatory usage rules for Service and Agency Codes are established for the assignment of DoD
Activity Address Codes (DoDAACs) and Routing Identifier Codes (RICs). Further stratification for
DoDAAC assignment usage rules may be found in the Logistics Data Resources Management System
(LOGDRMS) under DLMS Qualifier/DLMS Code List ID 71, Service and Agency Code.
4
Refer to the Treasury Financial Manual Supplement--FAST Book (Part II link to Independent Agencies)
for listing of Federal Civil Agency codes
https://www.fiscal.treasury.gov/fsreports/ref/fastBook/fastbook_home.htm used as the first two positions
of the activity address code (AAC).
SERVICE CODES
CODE 4 5 30 31 45 46 67 68 74 75 S/A REMARKS
A A A A A A Army
B B B B Army
B B B Army Security Assistance Use
Only 5
C C C C Army
C C C Army Contractor Use Only
D D D D Air Force
D D D Air Force Security Assistance Use
Only 6
E E E E Air Force
E E E Air Force Contractor Use Only
F F F F F F Air Force
G G G G G G GSA
H H H H Other DoD Note: To designate
Activities other 7 DoD Activity
contractors, you must
H H G H G Other DoD Activity
use Service Code H with
Contractors
G. When code HG is
H H H Not Assigned used, rp 30-31 or 45-46
shall contain the HG
code, as appropriate 8.
I I Missile Defense Security Assistance Use
Agency Only
J J J J J J Air Force
K K K K Not Assigned
K K K Marine Corps Security Assistance Use
Only 9
L L L Not Assigned
L L L L Marine Corps Contractor Use Only
5
On Grant Aid requisitions, rp 45 shall contain S/A Code Y.
6
Ibid.
7
Procedures to control access to DoD material inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
8
Mandatory usage rules for Service and Agency Codes are established for the assignment of DoD
Activity Address Codes (DoDAACs) and Routing Identifier Codes (RICs). Further stratification for
DoDAAC assignment usage rules may be found in the Logistics Data Resources Management System
(LOGDRMS) under DLMS Qualifier/DLMS Code List ID 71, Service and Agency Code.
9
On Grant Aid requisitions, rp 45 shall contain S/A Code Y.
SERVICE CODES
CODE 4 5 30 31 45 46 67 68 74 75 S/A REMARKS
M M M M M M Marine Corps
N N N N N N Navy
O Not Assigned
P P P P Navy
P P P Navy Security Assistance Use
Only 10
Q Q Q Q Navy
Q Q Q Navy Contractor Use Only
R R R R R R Navy
S S S S S S DCMA See footnote 11
S S S S S S DLA See footnote 12
S S D S D DLA Contractor Use Only
T T T T DLA
T T DLA Security Assistance Use
Only 13
T T (See Footnote 14 )
U U U U Not Assigned
U U U DLA Contractor Use Only
V V V Navy
10
Ibid.
11
DCMA: DoDAACs begin with S and end with A; any character is allowed in between. RICs are in
the format S-numeric-alpha, where the numeric value is 6, 7, or 8 only.
12
DLA: S-series excluding those values that fall within the DCMA format rules identified in the previous
footnote for DCMA.
13
On Grant Aid requisitions, rp 45 shall contain S/A Code Y.
14
S/A Code T entered in rp 45 may be used for any Foreign Military Service (FMS) country Defense
organization which is not designated as an element of that country’s Army, Navy, Air Force, or Marine
Corps.
15
Identifies Security Assistance Grant Aid when used in a Security Assistance requisition (as designated
by rp 30). Otherwise, considered nonsignificant except by coordinated prior agreement or authorized
procedures for inter-Service ownership transfer of ammunition/ammunition-related materiel. See
Appendix 7.9 for details.
SERVICE CODES
CODE 4 5 30 31 45 46 67 68 74 75 S/A REMARKS
16
Refer to the Treasury Financial Manual Supplement – FAST Book (Part II link to Independent
Agencies) for linsitn of Federal civil Agency codes
https://www.fiscal.treasury.gov/fsreports/ref/fastBook/fastbook_home.htm used as the first two positions
of the AAC.
17
Request for Implementation Date for Approved DLMS Change (ADC) 384, Special Programs for
NonDoD/No-Federal Agency Requisitioners and Administrative Change for Contractor DoDAACs,
January 18, 2011
AP7.3.2. To qualify for assignment of a RIC, the facility/activity must be an integral and
predetermined element of an established logistical system and must perform a general
logistical control, distribution and/or storage mission (to include bases, posts, camps,
and stations, when applicable).
AP7.3.3. The use of a RIC on any one document does not infer, imply, or intend that
follow-on documentation resulting from there must contain the same RIC or any element
thereof. It is a fundamental premise of Military Standard Requisitioning and Issue
Procedures (MILSTRIP) that any RIC serves as only one of the following:
AP7.3.4. All authorized RICs shall contain one of the characters depicting Service
assignment as listed in Appendix 7.2, Service and Agency Codes, in the first position.
AP7.3.5. The second and third positions may be in any combination of alphanumerics,
except as noted in Appendix 7.2. These positions may identify either a facility or activity
of the S/A depicted by the first position.
AP7.3.6. Each S/A is responsible for the assignment of RICs to its facilities and
activities. A S/A that has activities located at another S/A facility shall assign its own
RIC to the activity. A S/A which has assets located at another S/A facility shall use the
RIC assigned by the S/A owning/operating the facility. (An appropriate RIC may be
assigned to identify these assets when requested by the S/A owning the assets.)
1
DAAS requires a user authorization to obtain information from their website. Users without approved
access to DAAS (user id and password), must complete a request for access available on the DAAS
Website https://www.transactionservices.dla.mil/sar/sar_menu.asp
AP7.3.7. Each S/A shall designate a coordinator with the responsibility to control,
monitor, and submit/validate all RIC additions, revisions, and deletions relative to its
S/A. In most cases the DoDAAC and RIC coordinators (or monitors) are the same. S/A
coordinators established for assignment of RICs are available at
http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/
AP7.3.8. DAAS maintains the RIC database and serves as the focal point for receipt of
all RIC database revisions. DAAS will monitor RIC code assignment for compliance
with the above assignment rules. RIC database is published electronically and updated
from requests for additions, changes, and/or deletions as submitted by the Component
RIC coordinators. Interested parties may interrogate the RIC database through the
DAAS Website 2 at https://www.transactionservices.dla.mil/DAASINQ.
2
DAAS requires a user authorization to obtain information from their website. Users without approved
access to DAAS (user id and password), must complete a request for access available on the DAAS
https://www.transactionservices.dla.mil/sar/sar_menu.asp.
AP7.4.1.1. Based upon the status recipient profile, DLA Transaction Service’s
Defense Automatic Addressing System (DAAS) will determine the appropriate
communication process/format, e.g., Defense Information System Network (DISN) using
DLMS (X12/XML) or the legacy 80 record position (rp) format, or DLA Transaction
Services Automatic Message Exchange System (DAMES). The original M&S code set
defined the media for communication of status, as well as the type of status and
required recipients. However, with the substitution of web portals for viewing status
where transactional exchange is not available, document mailing has been terminated,
thus eliminating the option for the user to specify a communication media by M&S code.
Requisitioners without communication services supported by DAAS may use various
web portals for supply and shipment status. Web portals include:
AP7.4.1.4. Status recipients may be identified by using the M&S code as a pointer
to various organizations identified by coded data within the transaction:
AP7.4.1.5. The M&S code is not used for all status distribution processing:
AP7.4.1.5.2. Under the DLMS, not all status recipients are identified by the
M&S Code. An enhancement to DLMS transactions allows for discrete identification of
status recipients by DoDAAC when not specified by the M&S Code (see N1
Segment/Code Z1 – Party to Receive Status). DAAS will provide distribution to these
activities when status distribution is required.
AP7.4.1.6. M&S codes are used in different ways on requisition-related and MRP
transactions.
AP7.4.1.6.2. With the exception of M&S 8, M&S codes do not apply to:
AP7.4. 1.7.2. M&S codes may indicate that such replies must be routed to
the credit-to activity associated with the Fund Code (M&S 9).
AP7.4. 1.7.3. When the SICA is identified as the credit-to activity associated
with the fund code, M&S 9 will be entered (optional for automatic return notification).
1
Refer to PDC 1067.
AP7.1.10. M&S is a mandatory entry by the originator of the document and will not
be altered during subsequent processing except under the procedures for SICA
processing (See DLMS Volume 2, Chapter 4 and 11) or Service-level guidance for
internet-based ordering applications.
LEGACY RECORD 7
POSITION:
M&S Codes Used with MRP Transactions
CODE EXPLANATION
1 Reserved.
2 Reply to the reporting activity.
3 Reserved.
4 Reply to shipped from and/or credit-to as perpetuated to the SUPADD.
5, 6, 7, 8 Reserved.
9 Reply to credit-to activity as associated with the fund code.
CODE EXPLANATION
1 Reserved.
3 Reserved.
5, 6, 7 Reserved.
8 One hundred percent supply status and shipment status to activity indicated in
the distribution code (first position). Do not provide status to any other status
eligible recipient under any other circumstances. (For use only by SICAs on
transactions for nonconsumable items).
9, A Reserved.
C Reserved.
E Reserved.
F One hundred percent supply status and shipment status to requisitioner and
ship-to and/or credit-to as perpetuated to the SUPADD.
G, H Reserved.
I Not used.
J Reserved.
L Reserved.
CODE EXPLANATION
N Reserved.
O Not used.
P, Q, R Reserved.
T Reserved.
U One hundred percent supply status and shipment status to ship-to and/or
credit-to as perpetuated to the SUPADD.
V, W, X Reserved.
Z Exception supply status and shipment status to requisitioner and ship-to and/or
credit-to as perpetuated to the SUPADD.
AP7.5.1.2. The national or NATO item identification number (NIIN) will be entered
in record position (rp) 12-20.
AP7.5.1.3. Example:
rp 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
NSN 8 3 2 0 0 0 3 1 2 3 4 1 2 BLANK
AP7.5.2. When codes are required in addition to the NSN to properly identify the item
being requisitioned and these codes are recognizable to the initial processing source,
the codes will be entered in rp 21 and 22. If one digit only, entry will be in rp 21. See
examples below:
rp 8 9 10 11 12 13 14 25 16 17 18 19 20 21 22
NSN 8 3 2 0 0 0 3 1 2 3 4 1 2 3 BLANK
plus one
code
OR
rp 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
NSN 1 5 6 0 0 0 3 1 2 3 4 1 2 B C
plus two
codes
AP7.5.3.1. The North Atlantic Treaty Organization (NATO) FSC will be entered in
rp 8-11.
AP7.5.3.2. A two-position NCB code which identifies the NATO country assigning
the NIIN will be entered in rp 12-13. Examples of NCB codes are: (1) 00 and 01 -
United States, (2) 99 - United Kingdom, (3) 21 - Canada, and (4) 12 - Germany. See
Cataloging Data and Transaction Standards, Volume 10, Table 9 for a complete listing
of NCB codes.
AP7.5.3.4. Example:
rp 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
NATO
5 3 4 0 0 0 1 2 3 1 2 3 4 BLANK
NSN
AP7.5.4.1. The contractor and Government entity (CAGE) code will be entered in
rp 8-12 (see example in paragraph AP7.5.4.5., below). If the CAGE code is not
available, enter the in-the-clear description in the remarks section.
AP7.5.4.3. When a manufacturer’s part number exceeds 10 digits, the materiel will
be requisitioned on DD Form 1348-6.
rp 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Part
1 2 3 4 5 1 2 3 4 5 6 7 8 9 0
Number
AP7.5.6. When other than an NSN or part number is applicable (i.e., a plant equipment
code, DoD ammunition code, locally assigned number, etc.) and:
rp 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Number 1 2 3 4 5 6 7 8 9 1 2 3 Blank
AP7.5.6.2. If 15 digits, it will commence in rp8 and progress to the right. Example
of Fifteen digits:
rp 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Number 1 2 3 4 5 6 7 8 9 1 2 3 4 5 6
AP7.5.6.3. If 16 digits or more, the DD Form 1348-6 will be used and the entire
number will be entered in block 1 thereof.
AP7.5.7. Brand name resale subsistence items are identified by special item
identification numbers assigned by DLA Troop Support and configured to conform with
the NSN, as explained below:
rp 8 9 10 11 12 13 14 15 16 17 18 19 20
DLA
Troop
Support
8 9 1 5 0 0 A 1 6 1 0 9 9
Number
FSC NCB Alp Supply Item
(a) (b) ha Bulletin Number
(c) Number (e)
(d)
AP7.5.7.1. Rp 8-11 will contain the FSC. Example: FSC 8915 is canned fruit and
vegetables.
AP7.5.7.4. Rp 15-17 will contain the supply bulletin number, which identifies the
brand name supplier. Example: SB 10-500-161, the numeric 161 identifies the specific
supplier by name for brand name resale items listed in that bulletin.
AP7.5.7.5. Rp 18-20 will contain the numerical sequence of items listed in the
specific bulletin (0 thru 999), i.e., line item number in the bulletin.
AP7.5.9. Requisitions for perishable and nonperishable subsistence will contain the
applicable subsistence type of pack code in rp 21.
AP7.6.3. Exception rule for ammunition and ammunition related items (federal supply
group (FSG) 13 and federal supply classification (FSC) 1410, 1420, 1427, 1440, 5330,
5865, 6818 or 8140). By trading partner agreement and by coordination with DLA
Transaction Services, an exception rule is available for communicating larger quantities.
This rule is only applicable when the initiating system is Defense Logisitcs Management
System compliant (and supports larger quantities) and the receiving system is using
legacy MILSTRIP. Under this rule, when the quantity exceeds 99,999, the DLA
Transaction Services transaction conversion from DLMS to legacy format shall transmit
the initial quantity using the standard configuration of using the qualifier “M” in rp 29 to
represent thousands. The residual quantity from the DLMS transaction shall be
transmitted separately using the original document number and original/blank suffix
code. The legacy trading partner system shall be responsible for accumulating the
quantities transmitted separately (rather than superseding or rejecting as duplicate
transactions). 2
1
For ammunition transactions only (FSG 13), enter an “M” in rp 29 to express in thousands any
quantity exceeding 99,999. Example: A quantity of 1,950.00 shall be expressed as 1950M
(1950 in rp 25-28 and an “M” in rp 29). The “M” modifier is an optional feature that can be
applied intraS/A and, by agreement, inter-S/A.
2
Refer to ADC 441, Exception Rules to Accommodate Communication of Ammunition/Ammunition
Related Quantities in Excess of Five Digits
Service
Agency Code
Activity Address Code Ordinal Date Serial Number
30 31 32 33 34 35 36 37 38 39 40 41 42 43
AP7.7.2. The entries in rp 30 and 31 will always be the appropriate character(s) from
appendix AP7.2 that indicates the Service/Agency (S/A).
AP7.7.3. DoDAAC or FEDSTRIP AAC for each activity will be established and
disseminated by each of the Services, DLA and the GSA. (See DLM 4000.25, Volume
6, Chapter 2, DoDAAD.) Each code so established will contain or serve as an address
to permit shipping and billing for materiel and for mailing of documentation.
AP7.7.4. Entries in rp 36-39 (date) will always be numeric and will indicate the actual
date of transmittal from the requisitioner to the initial supply source. If requisitions are
predated to facilitate local processing, the requisition date will be amended (if
necessary) to reflect the true date of transmittal.
AP7.7.4.1. Rp 36 will indicate the last numeric digit of the calendar year in which
the document was originated. Example: 0 for 1990, 1 for 1991, etc.
AP7.7.4.2. Rp 37-39 will indicate the numerical or consecutive day of the calendar
year; for example, 035 is equal to February 4TH.
AP7.7.5.3. The following alphabetic codes have been reserved for use in rp 40:
CODE EXPLANATION
B1 Document number assigned by the Marine Corps Maintenance Center Bridge in
conjunction with the changes required under DLA Marine Corps industrial activity
support agreement. Applies where release of materiel is initiated within the
Marine Corps systems and submission of the corresponding material release
order is transmitted to the DLA managed warehouse. (This meaning is
applicable only when an MCMC-associated DoDAAC is used to construct the
document number.)
C Use in the document number (unique control number) assigned for receipt of an
item upgraded from scrap under DLA Disposition Services procedures. (This
meaning is applicable only to DLA Disposition Services Field Office-prepared
receipt transactions.)
1
Available under DLMS. Refer to ADC 396, Revised Procedures and Data Content for DLMS Materiel
Release Order (940R) and Material Release Advice ((945A) and New Denial Management Code for
Marine Corps BRAC Storage and Distribution Interface (SDI).
CODE EXPLANATION
D2 Document number assigned by the depot on behalf of the Marine Corps
Maintenance Center under DLA Marine Corps industrial activity support
agreement. Applies where release of materiel is initiated without submission of a
corresponding material release order. (This meaning is applicable only when an
MCMC-associated DoDAAC is used to construct the document number.)
E Navy exception "ship to" for deployed naval units.
G Navy exception "ship to" for deployed naval units.
J Inventory control point (ICP) interrogations or offers of excess, and requisitions
resulting from the interrogations or offers (denotes inter-service supply support
transactions between ICPs).
K Reserved.
L Use to identify requisitions submitted to DLA Disposition Services that result
from physical screening of property at the DLA Disposition Services Field Office.
This type of requisition is referred to as a “Walk-In Requisition.”
M3 Use to identify Inventory Control Point/Integrated Materiel Manager directed
disposal release orders resulting from Base Realignment and Closure (BRAC).
This value is not currently approved for use on other transaction types.
N Reserved.
P Reserved for DoD assignment.
Q Use to identify requisitions and related transactions/documents for items
reclaimed from aircraft and equipment from the Aerospace Maintenance and
Regeneration Center (AMARC).
R4 Use to identify document numbers generated within the DLA Disposition
Services’ Reutilization/Transfer/Donation (RTD) Web to accommodate
processing of the individual lines associated with requisitioning a Disposition
Services container.
S5 Use to identify requisitions submitted to DLA Disposition Services.
T Use to identify Electronic Turn-In Document (ETID) prepared shipments/
transfers to DLA Disposition Services. 6
2
Ibid.
3
Use of modified definitions for codes M, R, and S in record position 40 last reported as not implemented
by United States Navy (USN), United States Air Force (USAF), and United States Marine Corps (USMC).
Refer to AMCL 145
4
Ibid.
5
Ibid.
6
ADC 464 (PDC 484), Intransit Control System (ICS), Shipment Status (DLMS 856S/Document Identifier
Code (DIC) AS3), and Disposal Shipment Confirmation Follow-up (DLMS 940/ DIC AFX/AFZ) under RBI.
CODE EXPLANATION
U Product quality deficiency report (PQDR), storage quality control report (SQCR),
and supply discrepancy report (SDR) related transactions when the original
requisition number is not known. (See MILSBILLS procedures in DLM 4000.25,
Volume 4, Finance.)
V7 Nuclear Related Materiel Code 2305 material requires manual routine contact of
Nuclear Engineering Department for delivery instructions.
W Navy exception "ship to" for deployed naval units.
Z8 Nuclear related materiel code 2305 material requires manual immediate contact
of Nuclear Engineering Department for delivery instructions.
7
Available under DLMS. Refer to ADC381, Procedures and Additional Data Content supporting
Requisitions, Requisition Alerts, and Unit of Use Requirements under Navy BRAC SS&D/IMSP
8
Ibid.
CODE EXPLANATION
I INACTIVATED ITEM DEMAND. This code will be entered only in
requisitions (document identifier code (DIC) A0_) applicable to inactivated
items by DAAS.
N NONRECURRING DEMAND. A request made for a requirement known to
be a one-time occurrence; for example, a modification work order (MWO) kit
for application or an initial request for storage. Requisitions shall be coded
nonrecurring when the demand is anticipated to be nonrepetitive.
O NO DEMAND. To be assigned by requisitioning activities in submitting
requisitions for substitute items which are acceptable in lieu of previously
(Alpha)
requisitioned but delayed items and for initial fill of prepositioned war reserve
materiel stock (PWRMS) consumable item requirements. Also applicable to
resubmission of previously requisitioned requirements under a new
document number when associated with shortage or nonreceipt for which
shipment status was received. May be prescribed by the program manager
on the basis of a nonrepetitive program requirement for which use of
Demand Code N or P is determined to be inappropriate.
P NONRECURRING DEMAND FOR SPECIAL PROGRAM REQUIREMENTS.
Entered in requisitions by a requisition initiator to identify a requisition for
special program/requirements for which stocks were known to have been
acquired by the ICP in anticipation of such demands.
1
When no demand code is entered in the requisition, the ICP shall consider such demand as R.
(See DLMS Volume 2, Chapter 4.)
AP7.8.2.3. Suffix codes shall be alphabetic or numeric with the exception that the
following alpha and numeric characters shall never be used:
ALPHA NUMERIC
I, N, O, P, R, S, and Z 1 and 0
AP7.8.2.4. Suffix Y is reserved for used by Navy and DLA only in their intra-
Service action involving duplicate shipments.
AUTHORIZED SUFFIXES
Central Processing Source A through Z and 2 through 9,
exclusive of I, N, O, P, R, S, Y,
and Z
AP7.8.2.7. Storage and other activities responsible for processing transactions
containing suffixes shall always perpetuate the suffix code onto related transactions that
they generate.
AP7.8.3.1. Processing elements of the distribution system shall enter a suffix code
in rp 44 2 of transactions involving partial quantities such as:
2
MILSTRIP supports the valid use of Suffix Code X, which may be perpetuated into the 15th character of
the Transportation Control Number (TCN) (which is normally derived from the MILSTRIP suffix code).
However, the Defense Transportation Regulation (DTR) also allows X as a default value when no suffix
code is assigned. This redundancy in the significance of the X in the TCN is recognized and accepted.
AP7.8.4.1. Processing elements of the distribution system shall enter a suffix code
in rp 44 of MRP transactions involving partial quantities, such as:
Service/Agency
45 46 47 48 49 50
AP7.9.2.4.3 Under DLMS, the originating system will also provide the
discrete data elements where applicable, mirroring those contained in the supplemental
data. This redundancy will be retained until all parties are using DLMS and the
supplemental data field may be repurposed for unrelated information.
AP7.9.2.5. When the first position of the document number contains a valid S/A
alpha designator and the first position of the SUPADD/data field contains a zero (0),
DAAS shall change the zero (0) to Y.
AP7.9.3.1.1. For Foreign Military Sales (FMS), the first position (legacy
format rp 45) shall contain the in-country Service designating the military service within
the Security Assistance customer country. For Grant Aid, the first position shall contain
Service/Agency Code Y. Note that the Y is subsequently converted to an X for
establishment of the applicable Military Assistance Program Address Code (MAPAC).
AP7.9.3.1.2. The contents of the remaining positions vary for both FMS and
Grant Aid, according to the Security Assistance country and the originator’s intent. (See
Chapter 25 and Appendix 8.3 or DLM 4000.25, Volume 6, Chapter 3, Military
Assistance Program Address Directory (MAPAD), for detailed guidance.)
AP7.10.2. Legacy MILSTRIP Business Rules. The signal code (record position 51) in
A series documents has two purposes; it designates the fields containing the intended
consignee (ship-to), and the activity to receive and effect payment of bills, when
applicable. In the case of the Material Returns Program (MRP), Document Identifier
Code (DIC) FT_ series, the signal code designates the fields containing the intended
consignor (ship-from) and the activity to receive and process credits, when applicable.
All requisitions/asset reports will contain the appropriate signal code.
AP7.10.2.1. The coding structure and its meaning for DIC A_ series documents
are shown in Table AP7.10.T1.
AP7.10.2.2. The coding structure and its meaning for applicable Materiel Returns
Program (MRP) (DIC FT_ series documents) are shown in Table AP7.10.T2.
1
When used to identify ownership transfer of ammunition and ammunition-related materiel with no
physical movement of materiel or billing, Signal Code M is used in conjunction with Project Code CYK
and the supplementary address/supplemental data field beginning with Service/Agency Code Y and will
not require inclusion of a valid ship-to DoDAAC. Refer to ADC 1020.
AP7.10.2.3. When the Signal Code is C or L, an additional use for the fund code is
to indicate the bill-to office. The fund code to bill-to office conversion under MILSBILLS
procedures is prescribed in the fund code appendix of DLM 4000.25, Volume 4,
Finance.
AP7.10.3 DLMS MILSTRIP Business Rules. 2 Pending future termination of the signal
code under DLMS, the signal code remains as a required data element. Redundant
mapping of the discretely identified activities is required during an extended transition
period to ensure interoperability in a mixed DLMS/legacy environment.
AP7.10.3.2 The coding structure and its meaning for requisition documents
are shown in Table AP7.10.T3.
2
Refer to ADC 1009A.
3
Refer to DLM 4000.25, Volume 4, Finance.
4
Ibid.
5
When used to identify ownership transfer of ammunition and ammunition-related materiel with no
physical movement of materiel or billing, Signal Code M is used in conjunction with Project Code CYK
and the supplementary address/supplemental data field beginning with Service/Agency Code Y and will
not require inclusion of a valid ship-to DoDAAC. Refer to ADC 1020.
AP7.10.3.3. The coding structure and its meaning for MRP asset reports
documents are shown in Table AP7.10.T4.
6
Ibid.
7
A single party to receive credit is used pending implementation of a DLMS enhancement to distinguish
and discretely identify the party to receive credit for materiel; party to receive credit for packing, crating,
and handling; and party to receive credit for transportation.
8
Refer to DLM 4000.25, Volume 4, Finance.
Bill to activity in block 27 of the DTID. If Signal Code B is present and no bill-to activity
B is provided in DTID block 27, the bill-to office will default to the turn-in activity identified
in the document number (MILSTRIP legacy rp 30- 35).
Addressee designated by the fund code (MILSTRIP legacy rp 52-53). If Signal Code
C is present and no bill-to activity is identified on the Fund Code to Billed DoDAAC
C Conversion Table, the bill-to office will default to the turn-in activity in the document
number (MILSTRIP legacy rp 30-35).
For Signal Code C, bill to activity must also be identified in block 27 of the DTID.
Addressee designated by the fund code (legacy rp 52-53). If Signal Code L is present
and no bill-to activity is identified on the Fund Code to Billed DoDAAC Conversion
L Table, the bill-to office will default to the turn-in activity in the document number
(MILSTRIP legacy rp 30-35).
For Signal Code L, bill to activity must also be identified in block 27 of the DTID.
AP7.10.4.2. Only the signal codes in AP7.10.3.1 are applicable on the DTID for
hazardous materiel or waste turn-in. Processing under Signal Codes C and L are
redundant to allow perpetuation of legacy system procedures.
AP7.10.5. Designation of the DoD EMALL DoDAAC SC4210 as the bill-to indicates
payment via Government purchase card or corporate credit card applies.
AP7.11.2. An additional use for the fund code is to indicate the DoDAAC of the “bill-to”
office when the Signal Code is C or L. The conversion of fund code to billed office DoD
activity address code (DoDAAC) conversion is prescribed in the fund code appendix of
DLM 4000.25, Volume 4, Finance.
AP7.12.2.4. The DAAS maintains the database of distribution codes 2 and will
serve as the focal point for all database revisions. Use
https://www2.transactionservices.dla.mil/edaasinq/ to interrogate the distribution code
file. Assigned distribution codes are listed at
https://www2.transactionservices.dla.mil/eDoDAAD_asearch/download_dodaaf.asp 3.
Select ‘MILSTRIP Distribution Codes’ from the drop-down menu box. The report
displays the ‘as of’ date for the codes listed.
AP7.12.3. Numeric Distribution Codes. Current use of numeric distribution codes are
as follows:
CODE USE
1 Reserved for assignment by the DoD MILSTRIP System Administrator.
2 For use by IMMs to identify transactions associated with lateral redistribution
of DoD consumable assets
3 For use by IMMs to identify transactions associated with lateral redistribution
of DoD reparable assets
4 Use for DoD EMALL requisitions
1
DAAS requires a user authorization to obtain information from their website. If you do not currently have
approved access to DAAS (user id and password), please complete a request for access by going to the
following DAAS website: https://www.transactionservices.dla.mil/sar/warning.asp
2
Ibid.
3
Ibid.
CODE USE
5 Inter-Component use with Service/Agency Code N to identify a DLA
DoDAAC to receive supply and shipment status and materiel obligation
validation (MOV) for DLA-funded Navy requisitions to other Services under
industrial activity support agreement.
6 Inter-Component use with the Navy Service Codes N, V, and R
7 and 8 Inter-Component use with the transmission of MOV requests
9 DLA Disposition Services
Federal Center
Battle Creek MI 49016-3412
111 Inter-Component use for Retail Transportation and Supply Receipt and
Acknowledgement Interchange (See DLM 4000.25, Volume 3, Chapter 2)
AP7.13.1. Project codes are used to distinguish requisitions and related documentation
and shipments, and to accumulate Service/Agency (S/A) performance and cost data
related to exercises, maneuvers, and other distinct programs, projects, and operations.
If no project code is applicable, leave blank in the applicable transaction.
AP7.13.2. Project codes, other than Office of the Secretary of Defense (OSD)/
Chairman of the Joint Chiefs of Staff (CJCS) assigned codes, do not provide nor imply
any priority or precedence for requisition processing or supply decisions. Project codes
are not related to priority in any respect and, when used, do not alter nor override the
priority assigned to a requisition or shipment. Requisitions containing project codes and
shipments related thereto will be processed strictly under the assigned priority
designator and implied/requested preferential treatment to the contrary will be
disregarded.
AP7.13.3. Project codes will be perpetuated in all related documentation and will
appear as a part of shipping container markings. Recognition of project codes by
suppliers in another S/A and the resultant special handling afforded requisitions and
shipments will be limited to:
1
ADC 1043 added the Standard Line of Accounting (SLOA) requirement for a project code element in the
FA2 segment, but also noted that the SLOA project code may or may not be the same as the supply
project code.
AP7.13.4. Project codes are categorized into four groups and the authority to assign
project codes varies by category. The following paragraphs provide the definitions of
each category of project codes and identify the S/A which is authorized to assign each
category of project code. The authoritative source for each category of project codes is
either maintained with the Services or the Project Code Management System (PCMS)
as part of DAAS logistics transaction processing infrastructure.
AP7.13.4.3.2. Project Codes CYK, JZC, JZM, JZO, and RBB are designated
as Category C and are authorized exceptions to the normal Category C
3/alphanumeric/alphanumeric structure.
AP7.13.4.5.2.4. OSD.
AP7.13.5. Dissemination. When Category C & D project codes are initially assigned,
extended, or cancelled prior to the current expiration date, the change will be reflected
on PCMS generated reports.
AP7.13.5.1.2. The approved project code is finalized and made active and
will be available from the Defense Automatic Addressing System (DAAS)
Logistics Data Gateway (LDG).
AP7.13.5.2. When an active project code is extended, the extension will not
exceed two years.
AP7.13.5.3. When an active project code is cancelled early (i.e., before the
currently published termination date) or reaches its termination date, the prior
termination date is to be crossed out on the PCMS reports and the actual expiration
date distinctly displayed.
AP7.13.5.4. For those without LDG accounts, reports containing all Category C
and D codes will be published electronically on the Defense Enterprise Data
Standards Office (DEDSO) Website. The report includes active project codes and
those that have expired in the six months prior of the report generation date.
AP7.13.6.2. Validation. Using project code data in PCMS, DAAS will edit all
requisitions and related transactions (DLMS 511R / MILSTRIP Document Identification
Code (DIC) A0_, AM_, DLMS 869F / MILSTRIP DIC AT_, and DLMS 517M / MILSTRIP
DIC APR) for invalid/expired Category C & D project codes.
AP7.13.6.2.2. If the edit check determines the project code exists but has
expired, PCMS compares the ordinal date from the requisition document number in the
transaction to the beginning date and actual expiration date of the project code in PCMS
to determine if the project code was active at the time of the original requisition.
AP7.13.6.3. PCMS will track which project codes are reserved, pending active,
and expired.
AP7.13.6.3.1. PCMS users may reserve a project code within their authority
to assign for up to one year. If the project code is not made active or given a pending
date to become active within the year it was reserved, then PCMS will no longer
reserve the project code. During the time that a project code is reserved, it is only
discoverable within PCMS by other users who could have been assigned the same
code.
AP7.14.3.1.1. Required for immediate end use and without which the force or
activity is unable to perform its assigned operational mission or without which the force
or activity will be unable to perform its assigned operational mission within 15 days (20
days if the force or activity is located OCONUS). 1
1
Materiel requirements of this nature affect the readiness of mission-essential materiel and
actually result in a report of casualty in accordance with equipment readiness information
AP7.14.3.1.3. Required for immediate end use for installation on, or repair of,
direct support equipment (ground support, firefighting, etc.) necessary for the operation
of mission-essential materiel. 2
AP7.14.3.2.1. Required for immediate end use and without which the
capability of the force or activity to perform its assigned operational mission is impaired.
AP7.14.3.2.3. Required for immediate end use for installation on, or repair of,
auxiliary equipment which supplements mission-essential materiel or takes the place of
such materiel should it become inoperative.
systems authorized by the OSD, the Chairman of the Joint Chiefs of Staff, or DoD Component
headquarters.
2
Ibid.
3
Materiel requirements of this nature directly affect the capability of the force or activity to
perform its mission; it can temporarily accomplish assigned missions and tasks but with
effectiveness and efficiency below the DoD Component Headquarters-determined level of
acceptable readiness.
AP7.14.5. Purpose. This section describes the assignment process for determining the
appropriate PD based on the assigned F/AD and the validation process for those
activities using the F/AD I assignment inappropriately.
AP7.14.5.2. Validation of F/AD I Activities. By direction of the OSD, the DAAS will
validate F/AD I usage through the requisitioning process. The DAAS will maintain an
edit table consisting of activities authorized to use F/AD I. To preserve accuracy and
timely update, the JCS will forward to DAAS and Government Services Administration
(GSA) all OSD-approved assignments of F/AD I immediately upon approval.
Telephonic or electronic communication, to include on-line update, with the DAAS and
GSA is authorized for time sensitive updates; however, formal documentation will be
forwarded to DAAS and GSA to support inclusion of all F/AD I authorized activities. In
order to maintain unclassified communication, JCS contact points are advised to identify
authorized activities by DoDAAC only (no clear-text activity names) and make no
reference to the associated F/AD. DAAS will edit PD 01, 04, and 11 requisitions (DLMS
511R, 511M, 869F, and 517M or MILSTRIP legacy DICs A0_, AM_, AT_, A3_, A4_, and
APR) to ensure that F/AD I requisitions identify an authorized activity in the document
number (MILSTRIP legacy rp 30-43), supplementary address field (MILSTRIP legacy rp
45-50), or DLMS ship-to, bill-to, or mark-for party 4 DoDAAC. DAAS will identify PD 01
requisitions failing this edit for suspected abuse and subsequent investigation without
interruption of normal requisition processing. DAAS will use Table AP7-14.T2, to
downgrade PD 04 and 11 requisitions failing this edit. DAAS will report downgrading
action back to the requisitioner in DLMS 870S/DIC AE9 transaction with BK status and
will forward the modified requisition for processing. By agreement, all suspected F/AD I
abuses found in US Coast Guard requisitions (document number beginning with
Service/Agency Code Z) identified under above validation process will be automatically
downgraded. In addition, DAAS will assess the validity of transactions which bypass
4
Refer to ADC 1009A. Automatic downgrade for PD 01 requisitions will not be authorized pending
implementation of the mark-for party as an alternate location for the authorized activity DoDAAC.
5
Effective November 3, 2003, DAAS implemented logic change to allow requisitions with DoDAAC
N00421 in rp 30-35, Document Number Serial Numbers FQ and GQ (in rp 40-41) and PDs 04 and 11 to
pass through DAAS processing without being downgraded. Requisitions with DoDAAC N00421,
document number serial numbers beginning with FQ and GQ for PDs 01, 04, and 11 will not be included
in the monthly Priority Designator Reports.
6
Refer to ADC 279, Automated Downgrade for Priority Abuse and Reporting Procedures. The exception
for the AF is an interim waiver pending better methodology for identification of the F/AD I authorized
activity in AF requisitions.
AP7.14.6. In the following special circumstances, the stated PD may be used by all
requisitioners, irrespective of F/AD, but they are not to be used for the routine
replenishment of stocks to meet authorized stockage objectives:
AP7.14.9. ISSUE PRIORITY GROUPS (IPGs). PDs are grouped into IPGs as follows:
AP7.14.9.3. PDs 09, 10, 11, 12, 13, 14, and 15 form IPG III.
AP7.14.10. The key to achieving and maintaining a well balanced stock position is
timeliness is submitting stock replenishment requisitions. Services, in promulgating this
system, will ensure establishment of directives to provide positive assurance that
replenishment requisitioning is effected when the reorder point has been reached and/or
when planned program requirements or issue experience reveals the necessity for the
establishment of stock levels. Continued emphasis on stock replenishment
requisitioning will minimize the necessity for priority requisitioning. Competing
demands; such as, different demands having the same PD or RDD for assets in short
supply, will be manually reviewed when release of assets may result in failure to satisfy
a firm commitment for delivery of materiel to a Security Assistance recipient or failure to
satisfy a requisition reflecting a CJCS assigned project code. Decision on the selection
of demands to be satisfied will be based on scheduled dues-in, significance of the CJCS
assigned project codes, and acceptability of substitute items. The CJCS project codes
are the 9__ series. Control levels may be established to reserve assets for requisitions
with designated ranges of PDs, CJCS approved projects, or firm commitments for
delivery of materiel to a Security Assistance recipient.
AP7.14.11. RDD Data Field. Requisitioning activities, after determining the appropriate
PD applicable to requisitions, will determine the appropriate entry for the RDD data
field. 7 The combination of the PD and the designation or non-designation of an RDD or
other allowable entry for rp 62-64, as stated in this appendix, will determine the supply
and transportation system response time requirements. Response times are referenced
in DoDM 4140.01, Volume 8, DoD Supply Chain Materiel Management Procedures:
Materiel Data Management and Exchange.
7
Non-date entries in the RDD field, i.e., Codes E, F, N, R, 444, 555, 777, and 999, are referenced as
Special Requirement Codes Under the DLMS.
AP7.14.11.3. Collocated Stock. If the customer is collocated with the supply depot
issuing the materiel or has through local negotiations obtained collocated customer
status and does not require the fastest possible service of the supply and transportation
system, the customer should enter an RDD of 444. The customer entering a “444" RDD
should expect the total time from order placement to delivery to be within the UMMIPS
time standards for the assigned PD.
8
The 100-day edit is not applicable to requisitions directed to Naval Ammunitions Logistics Center
(NALC).
9
Ibid
AP7.14.11.5.4. Expedited Handling Signal 999 and other not mission capable
supply (NMCS) conditions covered in the succeeding paragraphs take precedence over
the specific RDD requirements.
AP7.14.11.6.2. The requisitioning unit must possess F/AD I, II, or III, and
AP7.14.11.6.6. Requisitions for NMCS conditions other than 999, and all
ANMCS conditions, must contain PD 01-08 with an N (NMCS) or E (ANMCS) in rp 62.
[text deleted] Rp 63-64 are considered nonsignificant. Use UMMIPS time standards to
ship materiel.
B C D G H J K L M P T U V W
1 2 3 4 5 6 7 8 9 10 11 12 13 14
10
Use of RDP for conventional ammunition last reported as not implemented by USAF. Refer to AMCL
148.
11
The 100-day edit is not applicable to requisitions directed to Naval Ammunitions Logistics Center
(NALC).
1
The codes assigned for DLA, inter-Service and Government Services Administration (GSA) transaction
use will also be recognized and used for intra-Service transactions and will not be duplicated within the
Service assignment latitude.
2
Ibid.
3
Ibid.
4
Ibid.
5
Ibid.
6
Ibid.
7
Procedures for quantity adjustment related to requisitions with Advice Codes 2D, 27, or 29 last reported
as not implemented by GSA. Refer to AMCL 161.
8
Procedures to control access to DoD material inventories by defense contractors last reported as not
implemented by United States Army (USA) (Retail). Refer to AMCL 1A.
9
Ibid.
10
Ibid.
11
Ibid.
12
Ibid.
DLMS enhancement. Not for use in corresponding MILSTRAP legacy 80 record position transactions.
13
Refer to ADC 313. DOD Components must provide Defense Enterprise Data Standards Office with their
Component implementation date for ADC 313.
1
Codes assigned for DLA, inter-Service, and GSA use will also be recognized and used for intraService
transactions and will not be duplicated within the Service assignment latitude.
2
Ibid
NUMBER OF Two
CHARACTERS:
TYPE OF CODE: Alpha/Alpha or Alpha/Numeric.
EXPLANATION: Used to inform appropriate recipient(s) of the status of a
requisition’s or asset report’s processing, or of the
processing of related transactions.
Legacy Record Position 65-66
DLMS/Segment/Qualifier: LQ Segment, LQ01 Data Element ID 1270 Qualifier 81 –
Status Code
3
Submit a new requisition using a new document number with a current ordinal date.
4
Ibid.
5
If requisitioning via submission of a new document number, submit a cancellation request prior to fund
deobligation to ensure against a potential duplicate shipment.
6
Submit a new requisition using a new document number with a current ordinal date.
7
Ibid.
8
Ibid.
9
Ibid.
10
Ibid.
11
Ibid.
12
Ibid.
13
Ibid.
14
Ibid.
15
Ibid.
16
Ibid.
17
Ibid.
18
Ibid.
19
Ibid.
20
Ibid.
21
Per AMCL 22, approved for implementation under Defense Security Assistance Management System
(DSAMS) December 31, 2003. No implementation date available for Navy due to legacy system freeze.
22
Submit a new requisition using a new document number with a current ordinal date.
23
Ibid.
24
Ibid.
25
Ibid.
26
Ibid.
27
Ibid.
28
Ibid.
29
Ibid.
30
Ibid.
31
Per AMCL 22, approved for implementation under Defense Security Assistance Management System
(DSAMS) December 31, 2003. No implementation date available for Navy due to legacy system freeze.
32
Ibid.
33
Submit a new requisition using a new document number with a current ordinal date
34
Ibid.
35
Ibid.
CODE EXPLANATION
CF Rejected. Failed validation with SFIS Fund Code to Fund Account
Conversion Table.
(1) Discrete values for the Standard Line of Accounting data elements in
the transaction do not match data elements from the SFIS Fund Code to
Fund Account Conversion Table for the Fund Code in the transaction. If
still required, submit a new requisition 36 with valid data entries.
(2) Invalid/missing fund code 37
Note: Issues with content of the SFIS Fund Code to Fund Account
Conversion Table are to be communicated to the Fund Code Monitor of
the cognizant Component.
EP Customer DoDAAC and reparable item being returned or item being
issued are Army Exchange Pricing relevant and no unserviceable return
has been received associated with an issue. The specific monetary
amount shows any billing differences that result from the status of the
turn-in, i.e., delta amount (Standard Price minus Exchange Price). The
status code is authorized for intra-Army use only in the legacy format 80
rp MILSTRIPtransaction DIC FTZ/DLMS Transaction 870M.
SA Rejected. If appropriate, resubmit with exception information as required
by instructions disseminated separately by applicable ICP/IMM. (Assign
a new document number if a new asset report is submitted.) (Use on
DIC FTR.)
SB Rejected. Report garbled and incomplete. Corrective action cannot be
determined. Review entire contents, correct, and resubmit if appropriate.
(Assign a new document number if a new asset report is submitted.)
(Use on DIC FTR.)
SC Rejected. ICP/IMM of the reported item cannot be determined.
Research records and, if applicable, resubmit citing correct stock
number. (Assign a new document number if a new asset report is
submitted.) If NSN is GSA managed, item is non- stocked; disposition is
authorized under local directives. (Use on DIC FTR.)
36
Ibid.
37
Ibid.
CODE EXPLANATION
SD Rejected. NSN not identifiable. Corrective action cannot be determined.
Review, correct, and resubmit, if appropriate. (Assign a new document
number if a new asset report is submitted.) (Use on DIC FTR.)
SF Rejected. Item not in authorized condition to be reported or condition
code cannot be identified. Materiel should be screened for correct
condition code and new DIC FTE submitted; or, if not reportable,
dispose of under current procedures. (Assign a new document number if
a new asset report is submitted.) (Use on DIC FTR.)
SG Rejected. This transaction is a duplicate of a previously received report.
Recipient must research records to determine if this transaction was
previously rejected with an S series status/reject code. If so, resubmit a
new asset report with a new document number. Otherwise, no action is
required.
SH Rejected. Unit of issue is incorrect and cannot be converted or
corrected. (Assign a new document number if a new asset report is
submitted.) (Use on DIC FTR.)
SJ Rejected. Signal code is blank or incorrect. (Assign a new document
number if a new asset report is submitted.) (Use on DIC FTQ or FTR.)
SK Rejected. Unable to identify the ship-from or credit-to address as
designated by the signal code. (Assign a new document number if a
new asset report is submitted.) (Use on DIC FTQ and FTR.)
SM Rejected. Stock balance indicates materiel is not required; however,
item is in process of migrating and further action is deferred until date
contained in rp 70-73. If asset position exceeds retention limits after that
date, resubmit to appropriate IMM. (Assign a new document number if a
new asset report is submitted.) (Use on DIC FTR.)
SN Rejected. Materiel reported not authorized for return. Asset reports
directed to GSA are not authorized. (Use on DIC FTR and FTQ.)
SP Rejected. Item was reported and requisitioned by the reporting activity
(rp 30-35) or requisitioned by another activity for shipment to the
reporting activity (rp 45-50). (For use with DIC FTR.)
SQ Rejected. Reported NSN is master item number (i.e., all makes and
models) used for reference purpose only. Review records and resubmit
with new document number(s), citing appropriate NSN(s) for the specific
item(s) being reported. (Use on DIC FTR.)
TA Creditable return. Credit will be granted for quantity indicated in rp 25-
29. Ship materiel to activity in rp 54-56. (Use on DIC FTR or FT6.)
TB Noncreditable return. Return quantity indicated in rp 25-29 to activity
indicated in rp 54-56. (Use on DIC FTR or FT6.)
CODE EXPLANATION
TC Not returnable. Quantity reported has been determined by the IMM to be
not economically feasible to return. Use Component regulations for
further processing. (Use on DIC FTR.)
TD Not returnable.
(l) Special instructions for disposition are stated in the remarks field. In
this case, the status document will be mailed. This code will not be used
when other status codes have been established to convey applicable
status.
(2) When due to security reasons, or space limitations, instructions will
be furnished by separate media referring to pertinent document
numbers. In this case, the remarks block will be left blank and TD status
documents may be transmitted electrically. (Use on DIC FTR.)
TE Materiel required for lateral redistribution. DIC A4_ referral(s) will follow.
(Use on DIC FTR.)
TF Materiel received. Status being investigated. (Use on DIC FTR.)
TG Materiel required for lateral redistribution. DIC A4_ referral(s) will follow,
containing stock number and/or unit of issue as changed and as
indicated in rp 8-22 and/or rp 23-24. Examine unit of issue and quantity
fields for possible changes. (Use on DIC FTR.)
TH Credit will be granted for quantity indicated in rp 25-29. Stock number
and/or unit of issue changed as designated in rp 8-22 and/or rp 23-24.
The quantity field (rp 25-29) is adjusted as required. Examine unit of
issue and quantity fields for possible changes. Ship materiel to activity in
rp 54-56. (Use on DIC FTR or DIC FT6.)
TJ Noncreditable return. Stock number and/or unit of issue changed as
designated in rp 8-22 and/or rp 23-24. Examine unit of issue and
quantity fields for possible changes. Return quantity indicated in rp 25-
29 to activity indicated in rp 54-56. (Use on DIC FTR or DIC FT6.)
TK Not returnable. Stock number and/or unit of issue changed as
designated in rp 8-22 and/or rp 23-24. Quantity indicated in rp 25-29
exceeds authorized retention levels. Examine unit of issue and quantity
fields for possible changes. (Use on DIC FTR.)
TL Materiel received. No credit allowed as item received was other than
that authorized for return. (Use on DIC FTZ.)
TM Materiel received. No credit or reduced credit allowed as condition
received was less than reported. Condition of materiel received is
indicated in rp 71. (Use on DIC FTZ.)
TN Materiel received. Credit authorized for quantity in rp 25-29. (Use on
DIC FTZ.)
TP Materiel not received within prescribed timeframe. Credit authorization is
canceled. (Use on DIC FTZ.)
CODE EXPLANATION
TQ Materiel received. Noncreditable return as indicated in reply to customer
asset report. (Use on DIC FTZ.)
TR DIC FTE received and in process. Reply will be provided by date
indicated in rp 70-73. (Use on DIC FTD.)
TT Materiel received and in process of inspection and classification. DIC
FTZ will be provided upon completion. (Reply to DIC FTT.) (Use on DIC
FTR.)
TU Materiel not received. (Reply to DICs FTT and FTP.) (Use on DICs FTR
and FTB.)
TV Materiel not received within prescribed timeframe. Noncreditable return
authorization is cancelled. (Use on DIC FTZ.)
TW Credit action in process. Financial transaction is forthcoming. (Reply to
FTP.) (Use on DIC FTB.)
TX Financial transaction accomplished. Bill number of credit transaction
appears in rp 76-80. (Reply to DIC FTP.) (Use on DIC FTB.)
TY DIC FTZ generated on document number cited indicated no credit
authorized for return. (Reply to DIC FTP.) (Use on DIC FTB.)
TZ Customer Asset Report changed by DAAS (rp 4-6). Examine rp 8-22 for
possible change in FSC/NSN/part number being converted to an NSN if
the original Customer Asset Report was DIC FTG. Also, examine rp 67-
69 to determine if the transaction has been routed to another activity.
(Use on DIC FTQ.)
T1 Materiel received. No credit allowed because the stock number was
changed from a stock fund to an appropriation financed item. For intra-
Service use only. (Use on DIC FTZ.)
T3 DIC FTM has been received. Materiel has not been received. Materiel
should be shipped, tracer action initiated, or DIC FTC submitted, as
appropriate. (Use on DIC FT6.)
T4 Materiel not returnable. Quantity indicated in rp 25-29 is no longer
required IPE and must be reported to Defense Industrial Plant
Equipment Center (DIPEC) (SE 4300) under
DLAM 4215.1/AR 700.43/NAVSUP PUB 5009/AFR 78-9.
T5 Deleted. (Use TZ.)
T6 DIC FTE has been routed to the activity indicated in rp 67-69. Forward
all future FT_ documents to that activity. (Use on DIC FTR.)
T7 FSC has been changed by the ICP in rp 4-6. (Use on DIC FTR.)
T9 Part-numbered materiel reported is not authorized for return. DIC FTG
not authorized for asset reports directed to DLA. Use current
Component instructions for disposition of materiel. (Use on DIC FTQ.)
CODE EXPLANATION
A Shipment unit held for consolidation.
B Awaiting carrier equipment
C Awaiting export/domestic traffic release.
D Delay due to diversion to surface resulting from challenge by air clearance
activity.
E Delay resulting from challenge by air clearance activity for which no diversion to
surface occurs and materiel was shipped by air.
F Embargo.
G Strikes, riots, civil commotion.
H Acts of God.
J Shipment delayed to process customer cancellation request(s).
K Diversion to surface movement due to characteristics of materiel that preclude
air shipment; for example, size, weight, or hazard clarification.
L Delay requested and/or concurred in by consignee.
M Delay to comply with delivery dates at Continental United States (CONUS)
destinations/out loading terminal.
N Delay due diversion to air (requisition priority upgraded).
O Reserved
R DLA Disposition Services receipt-in-place property held pending disposition and
shipping instructions.
CODE EXPLANATION
CODE EXPLANATION
1 Grant Aid rendered under the authority of the Federal Aviation
Administration (FAA) of 1961 for which the United States receives no
reimbursement.
A Grant transfers of Excess Defense Articles provided under the authority of
the FAA of 1961 for which the United States receives no reimbursement
for the value of the materiel.
C Presidential determination to order defense articles from stock and
performance of defense services to satisfy Grant Aid requirements with
reimbursement from subsequent military assistance appropriations.
(Section 506 of the FAA of 1961.) All requests for Working Capital Fund
activities (to include transportation), shall include a funding source to
allow Defense Working Capital Fund (DWCF) activities to be reimbursed
by the military departments; orders will not be accepted without a funding
source. (DoD FMR 7000.14R, Vol 12, paragraph 230502 and Vol 11B,
paragraph 110106.A.
D Military Assistance Service Funded (MASF). Grant Aid programs
transferred to the DoD budget, which were not controlled and
implemented through the Grant Aid documentation and automatic data
processing (ADP) system.
H Grant Aid share of cost sharing agreements.
K Grant Aid-owned assets obtained through barter arrangements with
Federal Republic of Germany (used in conjunction with Supply Source
Code B only).
CODE EXPLANATION
L Grant Aid provided through the NATO Hawk Production and Logistics
Office (NHPLO) for maintenance support of Hawk Missile system (use in
conjunction with Supply Source Code N only).
P Grant Aid programs transferred to the DoD budget which were controlled
and implemented through the Grant Aid documentation and ADP system.
R Grant Aid of U.S. recovered materiel resulting from liquidation of NATO
Maintenance and Supply Agency (NAMSA) excess stockage.
S Assigned to all records in the Repbulic of Korea (ROK) Equipment
Transfer program authorized by Public Law 95-384 at no charge to Grant
Aid. This code is also assigned to all PY 71 update and 72 equipment
transferred to the ROK under Public law 91-652 at no cost to Grant Aid.
This code is also assigned to ammunition transferred to the Royal Thai
Government from Army foreign military sales (FMS) Case UEB. Transfer
at no cost to Grant aid was authorized by Section 24, Public Law 96-92.
AP7.19.1.1. Type of assistance Codes used in other than Grant Aid transactions:
CODE EXPLANATION
3 Cash sale from Stock with Payment in Advance. This code applies to cash
payments in advance of delivery and/or performance for a foreign military
sale which the Implementing Agency determines at the time of the offer will
be from DoD stocks.
CODE EXPLANATION
4 Source of Supply Not Predetermined with Payment in Advance. This code
applies to cash payment for a foreign military sale for which the Implementing
Agency has not yet determined, at the time of the offer, the extent to which
the supply source will be DoD stocks or procurement.
5 Cash Sale from Procurement with Payment in Advance. This code applies to
cash payment in advance of delivery and/or performance for a foreign military
sale which the Implementing Agency determines at the time of the offer will
be from DoD procurement.
6 Cash Sale from Stock with Payment on Delivery. This code applies to cash
payment upon delivery of defense articles or initiation of performance of
defense services which the implementing Agency determines at the time of
offer will be from DoD stocks.
7 Cash sale from Procurement with 120-Day Payment. This code applies to
cash payment 120 days after delivery of articles or commencement of
performance of services for a foreign military sale, which the implementing
Agency determines at the time of the offer, will be from DoD procurement.
8 Cash sale from Stock with 120-Day payment. This code applies to cash
Payment 120 days after delivery of articles or commencement of
performance of services for a foreign military sale which the Implementing
Agency determines at the time of the offer will be from DoD stocks.
M Grant Aid Merger. The Grant Aid, established under the mutual Defense
Assistance Act of 1949, originally provided for the loan or grant if military
equipment, materials, and services (including training) to eligible nations.
Since FY 82, the authority of Section 503(a)(3) of the FAA of 1961 has been
used to merge Grant Aid funds with recipient countries funds and/or with
FMS financing credit in the FMS Trust Fund, to make adequate funds
available to finance the country’s FMS cases. In addition, since FY06, other
authorized granting of US appropriations for use for FMS.
N Section 23 or 24 Arms Export Control Act (AECA) FMS, Credit (Non-
Repayable).
U FMSO No. 1. This code applies to cash payment for a Foreign Military Sales
Order (FMSO) No.1 Supply Support Arrangement (SSA). The purchasing
government buys equity in a specified dollar amount of DoD stocks. DoD
maintains that portion of its stocks for eventual delivery to the purchasing
government under a FMSO No.2 requisition agreement.
CODE EXPLANATION
V FMSO No. 2. This code applies to cash payment for a FMSO No.2 SSA
which permits the purchaser to submit requisitions for common repair parts
and secondary items in the DoD stocks of which the purchaser has bought
an equity under a FMSO No.1 agreement. The use of this code requires the
input of Cooperative Logistics Program Support Code (CLPSC) 1 or 2
(Appendix 7.22) in rp 72 of Cooperative Logistics Supply Support
Arrangement (CLSSA) requisitions and passing orders by the applicable
International Logistics Control Office (ILCO).
Z Section 23 or 24, AECA, FMS Credit.
AP7.20.2.3. Fresh Eggs, Milk, Fruits, and Vegetables; Frozen Meats, Fish, and Poultry:
CODE EXPLANATION
7 Wax impregnated fiberboard containers. The conditions that justify customer
requirement for this type of pack are defined as follows:
a. Items are desired for specific operations involving shipment to remote
areas, transfer at sea, ice or hydro cooling, prolonged storage, deploying
ships, lengthy environmental exposure or multiple handling transshipment, or;
b. At the option of the requisitioner when local demand and experience
indicates upgrading of shipping container requirements as being essential to
ensure adequate production protection, and;
c. The items (for example, Fresh Fruits and Vegetables (FF&V)) have been
approved by the cognizant Services/Agencies (S/A) for application and
requisitioning of this type of pack.
CODE EXPLANATION
M Items on this transaction are ICP/IMM stocks and are being transferred to
DLA Disposition Services by authority of the responsible ICP/IMM.
N Items on this transaction are not reportable by virtue of exclusion to the
MRP or other specific criteria; such as, extended dollar value or condition
limitations on asset reporting, and are duly authorized to be transferred to
DLA Disposition Services.
R Items on this transaction have been reported to the ICP/IMM under
MILSTRIP MRP procedures and are considered over the ICP/IMMs
authorized retention levels. Use Service/Agency (S/A) retention levels and
instructions to manage this materiel.
CODE EXPLANITION
OTS Navy One Touch
1
Applicable only to DLA-supported Document Identifier Code YRZ-formatted requisition trailers that
provide exception ship-to information as identified by Type Transaction Code ST.
NUMBER OF One
CHARACTERS:
TYPE OF CODE: Alpha
EXPLANATION: The delivery priority/special processing code communicates
special processing and/or priority requirements to the
Distribution Standard System for DLA Distribution Center
shipments under agreements with DOD Components.
Delivery priority/special processing codes carry no
precedence in ICP asset allocation decisions. Asset
allocation decisions are controlled by UMMIPS as defined in
DoD 4140.01-M, DoD Supply Chain Materiel Management
Procedures (February 10, 2014) and by DLM 4000.25,
Defense Logistics Management Standards. This data
element is found in MILSTRIP legacy DIC A5_ and DLMS
Implementation Conventions (ICs) 511M, 511R, 869A, 869F,
870S, 856S, 940R, 940S, and 945A. 1,2,3
• Only Code X is valid in the 511M, 511R, 869A, 869F,
870S, 856S, 940S, and 945A DLMS ICs.
• All codes are valid in the DLMS IC 940R.
RECORD POSITION: 73
DLMS LQ Segment, LQ01 Qualifiers R3 and KJ 4
SEGMENT/QUALIFIER
CODE EXPLANATION
A Immediate release (all users)
B Bearer Walk-Through (Navy)
C Subscriptions (Mapping)
F Allowance (Mapping)
1
Refer to ADC 141, Revise DLMS Supplement (DLMS IC) 940R, Material Release, to Accommodate
Delivery Priority Codes and National Geospatial-Intelligence Agency (NGA) Product Codes
2
Refer to ADC 381, Procedures and Additional Data Content supporting Requisitions, Requisition Alerts,
and Unit of Use Requirements under Navy BRAC SS&D/IMSP
3
Refer to ADC 401, Procedures and Data Content for DLMS Warehouse Service Request (940S) and
Warehouse Service Advice (943A) under Navy and Marine Corps BRAC
4
A data maintenance action was approved in version 5030. The approved code/name is "DPC – Delivery
Priority Code.
CODE EXPLANATION
G Flight Information Publications and Products (FLIPS) (Mapping)
H Hot (Navy)
J Disposal Release Order (Mapping) (Process order as free flow bypassing work
bench for cycle releases)
M Ammunition Transship via Customer Interface Control System (CICS) (Air
Force)
O Overnight (Navy)
P Digital Point Positioning Data Base (DPPB) (Mapping)
Q Quick (Navy)
R Sectional (Mapping)
S Standard Base Supply System (SBSS) Prepositioned Transship (Air Force)
T Next Day Delivery (Air Force) (SBSS stock - Relates to Air Force Delivery
Priority 7)
U Twelve (12) Hour Delivery (Air Force) (Mission Impaired Capability (MIC) Stock
Replenishment/Bench Stock - Relates to Air Force Delivery Priority 6)
V Eight (8) Hour Delivery (Air Force) (Production Issues - Relates to Air Force
Delivery Priority 5)
W Four (4) Hour Delivery (Air Force) (Maintenance Line - Relates to Air Force
Delivery Priority 4)
X One (1) Hour Delivery
(Air Force) (Awaiting Parts (AWP)/Work Stoppage - Relates to Air Force
Delivery Priority 3), or (Navy) (Navy Request to free flow BRAC Issues)
Y Thirty (30) Minute Delivery (Air Force) (Anticipated Mission Impaired Capability
Awaiting Parts (MICAP) - Relates to Air Force Delivery Priority 2)
Z Thirty (30) Minute Delivery (Air Force) (MICAP - Relates to Air Force Delivery
Priority 1)
Code Literal
<Blank> Draft Record
A1 Child PQDR
Code Literal
A2 Screening Pt Request For Information
A3 Action Point Request For Information
A4 Request for Support Point Investigation
A8 Awaiting Verification Of Corrective Action
A9 Stock Screened PQDR
AA Request for Additional Information
AB Under Engineering Review
AC Investigation Requested Of Action Pt
AD Action Point Accepted PQDR for Investigation
AE Exhibit Requested
AF Exhibit Shipped
AG Case/PQDR Reopened
AH PQDR Rebutted Back To Support Pt
AI Information Only/Trending Purposes
AJ Awaiting Credit Recommendation Or Credit Reversal
AK Awaiting Other Closing Delay
AM Awaiting Final Materiel Disposition Instructions
AN Awaiting Funds
AO Record Returned To Originator
AP Action Pt Inv Report Submitted
AQ Investigation Requested Of Support Pt
AR Request for Additional Information
AU Other
CA Invalid PQDR
CC Nonresponsive Investigation
CD Defect Previously Investigated
CE Enhancement
CF Exhibit Unavailable
CG Investigation Completed Without Exhibit (Not Requested)
Code Literal
CH No Investigation - Exhibit Damaged
CI Information Only/Reliability Data
CJ Investigation With Damaged Exhibit
CK Contractor Unwilling To Investigate
CN Manufacturing Sources Or Technical Data No Longer Available
CO Child PQDR
CP Investigation Completed With Exhibit
CR Stock Screened PQDR
CS No Closing Data Received From External System
CT Missing Necessary Information
CU Investigation Could Not Validate Defect
CV Corrected And Verified
CW Isolated Incident/Acceptable Risk
CX Cancelled Record
CY Closed Under Warranty Provisions
CZ Administrative Closing
Code Literal
C Root Cause Not Addressed
D Responsible Party Not Addressed
E Corrective Action Not Addressed
F Disposition Not Addressed
G Credit Not Addressed
H Preventive Action Not Addressed
I Incomplete Or Incorrect PQDR Information On Closing Letter
M Multiple Reasons For Rebuttal
N Disagree With Closing Response/Findings
O Other - Not Covered By A Defined Code
R Repeat Rebuttal
S Response Truncated Or Not Submitted In Proper Format
T Case Reopened Due To Delayed Receipt Of Exhibit Or Data
U Update Or Change Requested
V Response Needs Clarification
W Response Is For Wrong PQDR
Code Literal
F Repaired by User
P Vendor Replacement
R Vendor Repair
S Source of Supply Replacement
T Source of Supply Repair
W Credit Authorized
X No Credit Authorized
Code Literal
H Holding Exhibit
D Disposed or Destroyed
R Repaired
O Other
Code Literal
H Hold Exhibit
N Exhibit Not Required
Q Exhibit Required (but not Requested)
R Exhibit Requested
03 Seconds
1
Codes 7A and 7C are established Local Codes. A data maintenance action has been submitted for
establishment of “7A – Landings” and “7C – Flight Hours” in a future X12 Version. Refer to ADC 1007C.
Code Literal
Code Literal
Code Literal
Code Literal
A1 Incorrect Screening Point Assigned
A2 Incorrect Action Point Assigned
A3 Incorrect Support Point Assigned
B1 Major Data Element Correction Required
Code Literal
GN Gain or increase in quantity reported
LS Loss or decrease in quantity reported
CC Change in point of contact information
IP Requested information provided
MI Minor Data Element Change Required
MJ Major Data Element Change Required
MR Follow Up Requested Due to Late/Missed Interim Reply
OT Other
AP7.27.11.2. Usage. Informs the recipient of the status and reason that
the investigation is pending final completion.
Code Literal
AE Pending for Engineering Response
AR Pending Approving Official Review Prior to Completion
Notification
CR Pending Credit/Replacement Determination
ED Pending Exhibit Disposition Confirmation
ER Exhibit Requested, Awaiting Exhibit
IR Awaiting IM Response
MD Pending Material Disposition
OR Awaiting Originator Response
PA Pending Post Award Review
PM Awaiting PM Review
PR Pending Pre-positioned Materiel Request
RR Pending Requisition Number request
SC Awaiting Screening Pt Response
SP Awaiting Support Pt Response
SR Pending Shipment Received (Exhibit)
SS Pending Stock Screening Results
TD Awaiting Design Information
TR Awaiting Test Results
VL Pending Vendor Litigation
VR Awaiting Vendor Response
VR Pending Vendor Receipt of Exhibits
Code Description
19 Exhibit Compromised
Code Literal
1AA Material, Incorrect
1AB Blank Intentionally
1AC Welding
1AD Coating, Protective
1AE Marking Improper
1AF Installation Improper
1AG Blank Intentionally
1AH Manufacturing /Fabrication
1AI Soldering Inadequate
1AJ Lubrication Improper
1AK Documentation Missing
1AL Blank Intentionally
1AM Damaged (Visual)
1AN Component Failure
1AO Blank Intentionally
1AP Brazing
1AQ Bonding
1AR Potting
1AS Heat Treat
1AT Plating
1AU Chemical Film
1AV Impregnation
1AW Kitting
1AX Machining (Cutting, Grinding, Etc.)
1AY Cleaning
1AZ Clean Room
2AA Technical Data Package, Incorrect/Incomplete
2AB Blank Intentionally
2AC Blank Intentionally
2AD Test Procedures, Inadequate
2AE Blank Intentionally
2AF Blank Intentionally
2AG Configuration Control, Inadequate
2AH Instructions, Work
Table AP7.27.T17. SEGMENT 4 - Detailed Cause - 4th, 5th, and 6th Position
Code Literal
1AA Material, Incorrect
1AB Blank Intentionally
1AC Welding
1AD Coating, Protective
1AE Marking Improper
1AF Installation Improper
1AG Blank Intentionally
1AH Manufacturing /Fabrication
1AI Soldering Inadequate
1AJ Lubrication Improper
1AK Documentation Missing
1AL Blank Intentionally
Code Literal
A Process Changed (Includes Changes to Process Instructions)
B Initiated Engineering Change Proposal
C Revised Test Procedures
D Revise/Reviewed Specification/Drawing/Technical Order,
Publication/Manual
E Blank Intentionally
F Issued Technical/Safety Bulletins
G Improved Packaging
H Change Contractual Requirements for Future Buys
I Policy Changed
J Quality Assurance Requirements Changed
K Training Provided/Modified
L Blank Intentionally
M Further Investigation to Determine Root Cause And Corrective Action
N Corrective Action Request Submitted
O Contract Terminated
P Source Qualification Revoked / Removed as Approved Source From
Total Item Record.
Q Blank Intentionally
R No Preventative Action - Operational Risk Accepted – Use Of This Code
Is Restricted To The PQDR Owner Or Service Only.
X No Preventative Action - Use of This Code Requires The Reason(S) For
No Preventative Actions To Be Stated As Part Of The Investigation
Report
Z Invalid Report
Code Literal
A To Be Repaired/Replaced by Contractor At No Cost To Government
B Repaired By Using Activity - Not Contractor Representative
C To Be Repaired/Replaced by Govt - Depot/Overhaul Facility
D Exhibit(S) Scrapped Without Replacement
E Use-As-Is
F To Be Repaired/Replaced by Contractor At Government Expense
G Exhibit Not Required, Turn in Through Normal Supply
H Consideration Requested
DISCREPANCY CODES
Condition of Materiel
A1 Condition of stored materiel changed because of damage
Supply Documentation
D1 Supply documentation not received with materiel
D2 Supply documentation illegible or mutilated
D3 Supply documentation incomplete, improper, or without authority (use
only when receipt cannot be properly processed)
D301 Defense Turn-In Document (DTID) for partial weapon lacks missing parts
list or certification statement
D4 Missing Quality Assurance Representative (QAR) Signature in Wide
Area Workflow (WAWF)
D401 Receiving Report/Material Inspection and Receiving Report/Receiving
Report (DD 250 or equivalent) incomplete, incorrect, or hard copy
missing
D5 Transportation related documentation discrepancy 1
D501 Special Handling Data/Certification, DD Form 1387-2, omitted
D502 Special Handling Data/Certification, DD Form 1387-2, incomplete or
incorrect
1
Two-position transportation-related documentation discrepancy code is not applicable for new
submissions. Refer to ADC 1153.
DISCREPANCY CODES
D503 Transportation Control and Movement Document (TCMD), DD Form
1384, omitted
D504 TCMD, DD Form 1384, incomplete or incorrect
D505 Shipper's Declaration for Dangerous Goods omitted
D506 Shipper's Declaration for Dangerous Goods incomplete (including
incomplete item description)
D507 Shipper's Declaration for Dangerous Goods not appropriate for
transportation mode
D508 Department of Transportation Special Permit (DOT-SP) omitted
D509 Competent Authority Approvals (CAA) omitted
D510 Certificate of Equivalency (COE) omitted
D511 Inert certification omitted
D512 Drained and Purge Certificate/AFTO Form 20 omitted
D513 Explosives Classification Approval (CA) (EX-Letter) omitted
D599 Transportation-related documentation discrepancy (not identified by
other code). See remarks.
D601 Hazardous Waste Profile Sheet omitted
D602 Hazardous Waste Profile Sheet incomplete or incorrect
D701 Hazardous Waste Manifest omitted
D702 Hazardous Waste Manifest incomplete or incorrect
Hazardous Material 2
H1 Hazardous item in a condition other than shown on supply document or on
the supporting inspection/test certificate
H2 Hazardous item in storage damaged or requires repair
H3 Lack of a Safety Data Sheet (SDS) in Hazardous Material Information
Resource System (HMIRS)
2
Discrepancy Code H6, Shipper’s Declaration for Dangerous Goods, has been re-assigned to the
D-series. See D505 and D506.
DISCREPANCY CODES
H4 Non-radioactive item classified as radioactive, or non-hazardous item
classified as hazardous
H5 Expired hazardous shelf life item
Lumber
L1 Moisture exceeds allowable percentage
L2 Not treated in accordance with specification
L3 Product off grade
L4 Improper size
L5 Improper tally
L6 Improper or no grade mark on product
L7 Rotten product
L8 Splits, excessive wane, scant, or not end trimmed (one or all)
Misdirected
M1 Materiel improperly addressed and shipped to wrong activity
3
Two-position packaging discrepancy codes are not applicable for new submissions after September 1,
2013. Refer to ADC 1059.
DISCREPANCY CODES
P106 Desiccant incorrect, improperly located, or omitted
P107 Tape/closure of unit container incorrect or inadequate
P108 Hazardous materiels not removed as required
P109 Improper preservation of hazardous materiels (includes ammunitions/
explosives)
P110 Level of protection excessive or inadequate
P111 Minimum protection not applied (materiel returns)
P112 Non-conformance to specified requirements for preservation (explanation
required)
P113 Electrostatic/electromagnetic device preservation inadequate or omitted
P114 Concealed preservation defect found in storage (retail only)
P116 Preservation inadequate or incorrect resulting in item corrosion
P199 Improper preservation (not identified by other code). See remarks.
Packaging Discrepancy Codes
P2 Improper packing 4
P201 Container inadequate, incorrect, or oversized
P202 Intermediate container inadequate, incorrect, oversized, or omitted
P203 Exterior container inadequate, incorrect, oversized, or omitted
P204 Blocking and bracing inadequate, incorrect, or omitted
P205 Cushioning inadequate, incorrect, or omitted
P206 Level of protection excessive or inadequate
P207 Container deteriorated
P208 Skids incorrect or omitted
P209 Improper packing of hazardous materiels (includes
ammunitions/explosives)
P210 Non-conformance to specified requirements for packing (explanation
required)
P211 Improper foam-in-place
P212 Reusable container not used or improperly prepared
P213 Closure incorrect or inadequate
P214 Concealed packing defect found in storage (retail only)
P215 Non-conformance to specified requirements for wood packaging materiel
(WPM)
4
Ibid.
DISCREPANCY CODES
P216 Packaging inadequate or incorrect resulting in item corrosion
P299 Improper packing (not identified by other code). See remarks.
Packaging Discrepancy Codes
P3 Improper markings 5
P301 Identification markings omitted, incomplete, incorrectly located, or not
legible
P302 Improper marking of hazardous materiels (includes
ammunitions/explosives)
P303 Labels omitted or improperly affixed
P304 Contract data omitted, incomplete, incorrectly located, or not legible
P305 Precautionary or handling markings omitted, incomplete, or not legible
P306 Shelf-life markings omitted, incorrect, or not legible
P307 Bar code markings omitted, or not legible
P308 Incorrect lot number
P309 Set or assembly markings omitted
P310 Address incorrect or not legible
P311 Non-conformance to specified requirements for marking (explanation
required).
P312 Electrostatic/electromagnetic device markings inadequate or omitted
P313 Packing list omitted or incorrectly located
P314 Passive RFID tag is missing
P315 Passive RFID tag is visibility damaged and unreadable
P316 Passive RFID tag is present but unreadable (not visibility damaged)
P317 Passive RFID tag read has no corresponding advance shipment
notification
P318 Passive RFID tag read duplicates previously used tag identification
P319 Military Shipment Label (MSL), DD Form 1387, omitted; no Transportation
Control Number (TCN)
P320 MSL, DD Form 1387, improperly affixed, incorrect, or incomplete
P399 Improper markings (not identified by other code). See remarks.
5
Ibid.
DISCREPANCY CODES
Packaging Discrepancy Codes
P4 Improper unitization (includes palletization and containerization) 6
P401 Cargo not unitized
P402 Shrink/stretch wrap inadequate or omitted
P403 Strapping inadequate or omitted
P404 Multiple consignees in single consignee consolidation container
P405 Protective covering/wrapping inadequate, improper, or omitted
P406 Contents of multipack container inadequately packaged, stuffed or missing
unit packs
P407 Improper unitization/palletization/containerization of hazardous materiels
(includes ammunitions/explosives)
P499 Improper unitization (not identified by other code). See remarks.
6
Ibid.
7
ADC 1126, not yet implemented.
DISCREPANCY CODES
Q99 New receipt item received for First Article Testing
Shortage or Nonreceipt
S1 Quantity received less than quantity indicated on supply documentation
S2 Quantity received is less than quantity requested minus variance, (other
than unit of issue or unit of pack)
S3 Total nonreceipt of U.S. Postal Service shipment.
S4 Total nonreceipt; not transportation related. (U.S. only)
S5 Total nonreceipt (Security Assistance only)
S6 Shortage due to unit of issue/ unit of pack incompatibility
8
Discrepancy Code T8 discontinued. See W7 and W8.
DISCREPANCY CODES
U02 Unique identification (UII/serial number) on item missing, damaged, or
unreadable
U03 Unique identification (UII/serial number) on supply documentation missing,
damaged, or unreadable
U04 Unique identification (UII/serial number) not provided on shipping notice/
returns notice
U05 Non-conformance to unique identification requirements under terms of
contract
U06 Multiple containers without separate unique identification (UII/serial
number) listings
U07 Mismatch between unique identification (UII/serial number) on item and
label
U08 Mismatch between unique identification (UII/serial number) on item or
packaging marks/labels and the associated shipping documentation
U09 Mismatch between unique identification (UII/serial number) on item or
packaging marks/labels and the associated due-in/shipping notice
U10 Mismatched or missing unique identification (UII/serial number) discovered
upon opening a sealed pack
U12 Duplicate UII or serial number (applicable to UII/serial number)
U13 Serial number unknown/missing for serially-tracked item.
U14 Serial number convention invalid.
U15 Missing shipping/return notice
Incorrect Item
W1 Incorrect item received.
W2 Unacceptable substitute received.
W3 Incorrect item received, but not identifiable to an NSN or part number.
W4 Misidentified item received.
W5 Mixed stock received.
W6 Incorrect item discovered upon opening a sealed vendor's pack (Not
applicable to Security Assistance)
W7 Part number unmatched to FEDLOG/FLIS
W8 Incorrect part number for NSN received
Other Discrepancies
Z1 Other discrepancy - see remarks
DISCREPANCY CODES
Z2 Repetitive discrepancy (must use in combination with other codes or
describe in remarks)
Z3 Distribution Center receipt not due-in; no prepositioned materiel receipt
(PMR)
Z4 No record exists for document number cited on supply document (not used
by distribution center; not applicable to Security Assistance)
Z5 Immediate resolution/replacement of discrepant item under inter-Service
support agreement (restricted use per Service guidance) 9
Z7 Property not authorized or not acceptable for turn-in to DLA Disposition
Services
Z8 Materiel unidentifiable; stock number missing or damaged.
9
Refer to ADC 1062 and 1174. Not authorized for use by DLA Distribution Centers.
Reply Codes
The 100-series codes provide status of financial resolution, materiel disposition
instructions, or other appropriate information: 12
101 Credit authorized by source of supply/item manager. 13
102 Credit not authorized; see remarks.
105 Forward materiel received to location identified. Must use traceable and most
economical means available.
106 Forward materiel received to contractor location identified (must use traceable
and most economical means available).
109 Credit authorized by source of supply/item manager for repackaging costs. 14
110 Disposal authorized in accordance with local procedures.
111 Disposal authorized, monetary reimbursement from contractor.
112 Disposal authorized, contractor will provide replacement.
113 Provide disposal documentation as requested.
114 Provide disposal documentation by date indicated as requested. Credit will be
authorized upon receipt.
115 Turn in materiel received to DLA Disposition Services Field Office.
116 Turn in hazardous materiel received to DLA Disposition Services Field Office
(MIPR or bill-to DoDAAC provided to cover disposal costs).
117 Materiel will be billed if not returned by date indicated.
10
Refer to ADC 1126 and 1084. Not authorized for use pending implementation; target implementation is
1Q FY 2017.
11
Ibid.
12
Exception: Reply Codes 103, 104, 107, and 108 have been moved to interim reply grouping.
13
No longer authorized for use by storage activities upon implementation of ADC 1160.
14
Refer to ADC 1203.
Reply Codes
118 Debit authorized for material retained.
119 Retain materiel received at no charge.
120 Retain materiel with consideration from contractor.
121 Retain materiel without consideration from contractor.
122 Retain materiel for future supply decision.
123 Materiel will be shipped/reshipped (estimated date of shipment provided, when
known).
124 Materiel is no longer procurable.
125 Incomplete part/missing component being forwarded.
126 Stock not available or will not be reshipped in response to SDR.
127 Contractor to reship.
128 Balance of contract materiel will not be shipped.
129 Reimbursement for repackaging discrepancy cannot be authorized until
submitter provides cost for repackaging.
130 Place materiel in stock as is.
131 Remark/repackage materiel.
132 Inspect and place in depot stock.
133 Upgrade materiel to Condition Code A, correction made by government with
reimbursement from contractor.
134 Upgrade materiel to Condition Code A, correction made by government without
reimbursement from contractor.
135 Documentation/technical data is being forwarded.
136 Confirmed canceled requisition shipped.
137 Additional comments provided; see remarks.
138 Shipment shortage based on pieces, weight, and cube.
139 Warehouse denial total shipment.
140 Warehouse denial partial shipment.
141 Duplicate shipment from stock or procurement.
142 Proof of Delivery/Evidence of Shipment not available.
143 SDR canceled by submitter.
144 Recorded for information, trend analysis, and/or process correction where
applicable.
145 No contractor liability found.
146 Material return acknowledged.
147 Corrected shipment document (DD Form 250) provided.
148 Representative will contact you for discussion concerning disposition.
Reply Codes
149 Material will be picked up in number of days indicated.
150 Your requisition will be reinstated and placed on backorder.
151 Replacement/revised disposition/status; prior response is superseded.
152 Discrepancy validated by storage activity; credit processing associated with
issue reversal 15
The 300-series codes indicate storage activity or initial action activity status on SDRs
forwarded to the owner/manager for action:
301 Interim reply; SDR forwarded to USA for disposition instructions or final
resolution.
302 Interim reply; SDR forwarded to USAF for disposition instructions or final
resolution.
303 Interim reply; SDR forwarded to USMC for disposition instructions or final
resolution.
304 Interim reply; SDR forwarded to USCG for disposition instructions or final
resolution.
305 Interim reply; SDR forwarded to USN for disposition instructions or final
resolution.
306 Interim reply; SDR forwarded to GSA for disposition instructions or final
resolution.
307 Interim reply; SDR forwarded to DLA for disposition instructions or final
resolution.
15
Refer to ADC 1160.
Reply Codes
308 Interim reply; SDR forwarded to the identified Item Manager for disposition
instructions or final resolution.
309 Interim reply; SDR forwarded to owner for disposition instructions or final
resolution.
320 Reclassification of materiel complete. (Use only with Status Update.)
321 Documentation/technical data/other information are being forwarded. (Use
only with Status Update.)
The 400-series codes indicate the SDR has been closed for the reason provided:
400 SDR closed. Non-compliance with disposition instructions.
401 SDR closed. Non-response to additional information request.
402 SDR closed. Wrong material returned.
410 SDR closed. Disposition action complete.
411 SDR closed SDR closed due to zero balance on record.
412 SDR closed. Materiel disposition could not be completed due to zero balance
at storage location.
450 Administrative closure notification. SDR information copy sent to wrong source
of supply
16
Refer to ADC 1160.
Reply Codes
The 600-series codes indicate an ICP reply to the storage activity:
601 Change supply condition code and submit as new complaint (original
complaint cannot be modified to show new supply condition code).
602 Item(s) unsuitable; destroy.
603 Remark and return to stock.
604 Repackage and return to stock.
605 Reidentify and return to stock.
606 Safety hazard; destroy.
607 Safety hazard; dispose.
608 Reclassify materiel as instructed; final disposition instructions will be provided
upon confirmation of reclassification. (Do not use in combination with other
reply codes.)
609 Reclassify materiel; disposition instructions provided (see remarks/ additional
reply code(s)).
610 Materiel previously dispositioned; close SDR with no further action. (Provide
remarks to explain circumstances for use of this code.) 17
611 Reidentify unique identification (UII/serial number) and return to stock.
612 Reverse associated receipt and reprocess to correct owner as identified.
17
Refer to ADC 1174.
Reply Codes
713 SDR rejected. Discrepancy does not meet required minimum dollar value.
714 SDR rejected. Billing adjustments may not be requested on a SDR (except
Security Assistance). Contact local finance office.
715 SDR rejected. Discrepancy report/follow-up not submitted within authorized
timeframe.
716 SDR recorded for information and possible corrective action.
717 SDR identifies a carrier discrepancy. Resubmit as a Transportation
Discrepancy Report (TDR). 18
718 SDR identifies a quality deficiency. Resubmit as a PQDR. 19
719 Discrepancy report rejected. Duplicate of previously submitted SDR.
18
Use of this code is discouraged. Every effort should be made to process the discrepancy report and
resolve the situation without requiring the initiator to resubmit. See preferred codes 518 and 519.
19
See footnote 1.
Reply Codes
901 Transaction rejected. Discrepancy report submitted to wrong activity.
Resubmit to the correct action activity (identified in remarks when known).
When applicable, use with Reply Code 612 or receipt rejection transaction
(DLMS 824R/MILSTRAP DZG) to reverse/reject the original receipt for
reprocessing.
902 Transaction rejected. Invalid action code for type of discrepancy submitted.
904 Transaction rejected. Open suffix must be closed before SDR can be
reopened.
906 Transaction rejected. Record already closed.
907 Transaction rejected. Discrepancy report canceled.
908 Transaction rejected. Record is currently open and cannot be reopened for
reconsideration until closed.
909 Transaction rejected. SDR must be reopened for reconsideration before it can
be contested.
910 Transaction rejected. Missing or invalid document number (or document
number/suffix).
911 Transaction rejected. Missing or invalid case designator.
912 Transaction rejected. Missing or invalid discrepancy report number.
915 Transaction rejected. Missing or invalid type of discrepancy code.
916 Transaction rejected. Missing or invalid action desired code.
917 Transaction rejected. Missing or invalid discrepant quantity.
918 Transaction rejected. Missing or invalid quantity received.
919 Transaction rejected. Invalid Security Assistance materiel location code. 20
920 Transaction rejected. Missing or invalid point of contact name.
921 Transaction rejected. Missing or invalid point of contact phone number/email.
923 Transaction rejected. Missing or invalid transaction date.
924 Transaction rejected. Narrative missing.
926 Transaction rejected. No record found.
927 Transaction rejected. Missing or invalid disposition/reply code
928 Transaction rejected. Missing or invalid condition code.
929 Transaction rejected. Missing, invalid, or unauthorized use of DoDAAC,
MAPAC, or RIC.
930 Transaction rejected. Missing information associated with disposition/reply
931 Transaction rejected. Missing or invalid materiel identification.
932 Transaction rejected. Missing or invalid wrong item information.
20
Refer to ADC 1203.
Reply Codes
933 Transaction rejected. Discrepancy report follow-up submitted before action
activity response time has elapsed.
934 Transaction rejected. Forwarding action not authorized. Submit new SDR.
935 Transaction rejected. Forwarding action cannot be processed due to
incomplete SDR history. Contact originator to resubmit with updated action
activity.
936 SDR processing suspended. Request DoD WebSDR provide an information
copy of the original report.
937 Transaction rejected. DoD WebSDR/WebSQCR unable to provide requested
SDR information copy.
938 Transaction rejected. Missing or invalid transaction set purpose code.
939 Transaction rejected. Missing, invalid, or inappropriate discrepancy report
document type code.
940 Transaction rejected. Improper or Missing either contract number or
contractor-assigned shipment number on SDR associated with vendor
shipment.
941 Transaction failed during processing. SDR cannot be transmitted electronically
to the designated action activity because no systemic e-mail routing is in place.
942 Transaction rejected. Unauthorized use of reply code. The 200-series reply
codes may only be used for Security Assistance SDRs.
943 Transaction rejected. Fund Code or Standard Line of Accounting (SLOA) data
elements do not match SFIS Fund Code to Fund Account Conversion Table. 21
944 Transaction rejected. Forwarding transaction not properly formatted.
945 SDR rejected. Invalid 500-series SDR Reply Code used; see remarks.
946 Transaction rejected. Missing serial number for serially-tracked item.
947 Transaction rejected. Invalid serial number length or convention.
948 Transaction rejected. Unauthorized change in the Owner, Manager, or Source
of Supply field.
949 Transaction rejected. Reply Code 504 can only be used for SDR Document
Type Code 7 or R, and cannot be used with any other reply code.
950 Transaction rejected. Unauthorized generation of completion notice (CN).
Only the submitter of the SDR is authorized to generate a CN.
951 Transaction rejected. Unauthorized change of data value using a Correction.
Submit a new SDR.
952 Transaction rejected. A completion notice (CN) has processed against this
SDR, no further transactions will process.
Refer to ADC 1043A/1043E. Note: Issues with content of the SFIS Fund Code to Fund Account
21
Conversion Table are to be communicated to the Fund Code Monitor of the cognizant Component.
AP7.28.5.1. The following codes are used to identify report categories for
appropriate automated processing. Discrepancy Report Document Type Codes and
DLA Disposition Services SDR Type Codes are one position alphanumeric codes.
AP7.28.5.3. The DLA Disposition Services SDR Type Code (DLMS Qualifier ST)
is used as a sub-type code in conjunction with the SDR Document Type to further clarify
the shipment scenario. This data element may be referred to as an SDR Sub-Type
Code. This data element is conditional; it is used when applicable.
22
SDR Document Type Code D must be used in conjunction with the applicable DLA Disposition
Services Document Type Code.
Available for DoD WebSDR only. Restricted Use. Must use in conjunction with SDR
Document Type Code 7:
D Disposition Services donated materiel
F Disposition Services transferred materiel
O Other Disposition Services shipment
R Disposition Services reutilization
S Disposition Services sale
Restricted. No longer available for new submissions after March 30, 2012:
L Disposition Services DEMIL
P Disposition Services Field Office SDR, depot shipment
DISCREPANCY CODES
Condition of Materiel
A1 Condition of stored materiel changed because of damage
A2 Condition of materiel changed because of deterioration
A3 Stored materiel is misidentified
A4 Stored materiel is incomplete
A5 Stored materiel requires repair
A6 Improper storage conditions resulting in item corrosion
C1 In a condition other than shown on supply document or on the supporting
inspection/test certificate (if hazardous materiel use code H1)
C2 Expired shelf life item (if hazardous materiel use code H5)
C6 Damage caused by pilferage, vandalism, or theft
Hazardous Material
D601 Hazardous waste profile sheet omitted
D602 Hazardous waste profile sheet incomplete or incorrect
DISCREPANCY CODES
D701 Hazardous waste manifest omitted
D702 Hazardous waste manifest incomplete or incorrect
H1 Hazardous item in a condition other than shown on supply document or
on the supporting inspection/test certificate
H2 Hazardous item in storage damaged or requires repair
H3 Lack of a Safety Data Sheet (SDS) in Hazardous Material Information
Resource System (HMIRS)
H4 Non-radioactive item classified as radioactive, or non-hazardous item
classified as hazardous
H5 Expired hazardous shelf life item
Lumber
L1 Moisture exceeds allowable percentage
L2 Not treated in accordance with specification
L3 Product off grade
L4 Improper size
L5 Improper tally
L6 Improper or no grade mark on product
L7 Rotten product
L8 Splits, excessive wane, scant, or not end trimmed (one or all)
Overage
O5 Concealed overage discovered in a sealed shipping container
O6 Overage due to unit of issue/unit of pack incompatibility
1
Two-position packaging discrepancy codes are not applicable for new submissions after September 1,
2013. Refer to ADC 1059.
DISCREPANCY CODES
P109 Improper preservation of hazardous materiels (includes ammunitions/
explosives)
P110 Level of protection excessive or inadequate
P112 Non-conformance to specified requirements for preservation (explanation
required)
P113 Electrostatic/electromagnetic device preservation inadequate or omitted
P114 Concealed preservation defect found in storage (explanation required)
P116 Preservation inadequate or incorrect resulting in item corrosion
P199 Improper preservation not identified by other code; see remarks
P2 Improper Packing
P201 Container inadequate, incorrect, or oversized
P202 Intermediate container inadequate, incorrect, oversized, or omitted
P203 Exterior container inadequate, incorrect, oversized, or omitted
P204 Blocking and bracing inadequate, incorrect, or omitted
P205 Cushioning inadequate, incorrect, or omitted
P206 Level of protection excessive or inadequate
P207 Container deteriorated
P208 Skids incorrect or omitted
P209 Improper packing of hazardous materiels (includes
ammunitions/explosives)
P210 Non-conformance to specified requirements for packing (explanation
required)
P211 Improper foam-in-place
P212 Reusable container not used or improperly prepared
P213 Closure incorrect or inadequate
P214 Concealed packing defect found in storage (explanation required)
P215 Non-conformance to specified requirements for wood packaging materiel
(WPM)
P216 Packaging inadequate or incorrect resulting in item corrosion
P299 Improper packing (not identified by other code); see remarks
P3 Improper markings
P301 Identification markings omitted, incomplete, incorrectly located, or not
legible
DISCREPANCY CODES
P302 Improper marking of hazardous materiels (includes
ammunitions/explosives)
P303 Labels omitted or improperly affixed
P304 Contract data omitted, incomplete, incorrectly located, or not legible
P305 Precautionary or handling markings omitted, incomplete, or not legible
P306 Shelf-life markings omitted, incorrect, or not legible
P307 Bar code markings omitted, or not legible
P308 Incorrect lot number
P309 Set or assembly markings omitted
P311 Non-conformance to specified requirements for marking (explanation
required).
P312 Electrostatic/electromagnetic device markings inadequate or omitted
P313 Packing list omitted or incorrectly located
P399 Improper markings not identified by other code; see remarks
DISCREPANCY CODES
Shortage or Nonreceipt
S6 Unit of issue/unit of pack incompatible
S9 Incomplete component, assembly, set, kit, outfit (CASKO) (do not use to
report cannibalization of Supply System Responsibility Item (SSRI),
Components Of End Item (COEI), or Basic Issue Item (BII); see
Discrepancy Code C4)
Other Discrepancies
Z1 Other discrepancy - see remarks
Z5 Immediate resolution/replacement of discrepant item under DLA
industrial activity support agreement
Z6 Discrepancy report resubmitted following cancellation must use with
other codes
ACTION CODES
1A Disposition instructions for discrepant materiel requested; financial action not
applicable.
1Z Other action requested (see remarks).
2C Technical documentation/data requested.
3B Discrepancy reported for corrective action and trend analysis; no reply
required.
4A Manager disposition requested for non-manager owned suspended stock per
receipt/stock screening; no action by owner pending manager response. 2
4B Action transferred to manager subsequent to return of non-manager owned
suspended materiel to the manager. 3
Reply Codes
The 100-series codes provide status of financial resolution, materiel disposition
instructions, or other appropriate information: 4
105 Forward materiel received to location identified. Must use traceable and
most economical means available.
106 Forward materiel received to contractor location identified (must use
traceable and most economical means available).
110 Disposal authorized in accordance with local procedures.
111 Disposal authorized, monetary reimbursement from contractor.
112 Disposal authorized, contractor will provide replacement.
119 Retain materiel received at no charge.
2
Refer to ADC 1084. Not authorized for use pending implementation; target implementation is 1Q FY
2017.
3
Ibid.
4
Reply Codes 103, 104, 107, and 108 have been moved to interim reply grouping.
Reply Codes
120 Retain materiel with consideration from contractor.
121 Retain materiel without consideration from contractor.
122 Retain materiel for future supply decision.
129 Reimbursement for repackaging discrepancy cannot be authorized until
submitter provides cost for repackaging.
130 Place materiel in stock as is.
131 Remark/repackage materiel and place in stock.
133 Upgrade materiel to Condition Code A, correction made by government
with reimbursement from contractor.
134 Upgrade materiel to Condition Code A, correction made by government
without reimbursement from contractor.
135 Documentation/technical data is being forwarded.
137 Additional comments provided; see remarks.
144 Recorded for information only; no action taken.
145 No contractor liability found.
148 Representative will contact you for discussion concerning disposition.
151 Replacement/revised disposition/status; prior response is superseded.
152 Discrepancy report recorded for information and possible corrective action.
The 400-series codes indicate the SDR/SQCR has been closed for the reason
provided:
410 Discrepancy report closed. Disposition action complete.
411 Discrepancy report closed due to zero balance on record.
412 Discrepancy report closed. Materiel disposition could not be completed due
to zero balance at storage location.
Reply Codes
107 Forward materiel to address shown for inspection/exhibit analysis (must
use traceable and most economical means available).
108 Forward materiel to contractor address shown for inspection/exhibit
analysis (must use traceable and most economical means available).
503 Discrepancy report currently under investigation.
514 Discrepancy report forwarded to the packaging specialist for research.
520 Discrepancy report materiel undergoing test/evaluation.
521 Discrepancy report resolution pending PQDR review.
522 Discrepancy report resolution pending investigation/response from item
manager. 5
523 Manager notification to owner: return materiel to manager at current
location. 6
524 Owner notification to manager: materiel returned at current location for
credit. 7
5
Refer to ADC 1084. Not authorized for use pending implementation; target implementation is 1Q FY
2017.
6
Ibid.
7
Ibid.
Reply Codes
The 900-series codes are intended for system/application use in processing
transactions. When SDRs/SQCRs are processed manually, these codes may be
user assigned as appropriate:
901 Transaction rejected. Discrepancy report submitted to wrong
owner/manager. Resubmit to the correct action activity.
902 Transaction rejected. Invalid action code for type of discrepancy submitted.
904 Transaction rejected. Open suffix must be closed before discrepancy
report can be reopened.
906 Transaction rejected. Record already closed.
907 Transaction rejected. Discrepancy report canceled.
908 Transaction rejected. Record is currently open and cannot be reopened for
reconsideration until closed.
910 Transaction rejected. Missing or invalid document number (or document
number/suffix).
912 Transaction rejected. Missing or invalid discrepancy report system-
assigned control number.
915 Transaction rejected. Missing or invalid type of discrepancy code.
916 Transaction rejected. Missing or invalid action desired code.
917 Transaction rejected. Missing or invalid discrepant quantity.
920 Transaction rejected. Missing or invalid point of contact name.
921 Transaction rejected. Missing or invalid point of contact phone
number/email.
923 Transaction rejected. Missing or invalid transaction date.
924 Transaction rejected. Narrative missing.
926 Transaction rejected. No record found.
927 Transaction rejected. Missing or invalid disposition/reply code
928 Transaction rejected. Missing or invalid condition code.
929 Transaction rejected. Missing, invalid, or unauthorized use of DoDAAC,
MAPAC, or RIC.
930 Transaction rejected. Missing information associated with disposition/reply
931 Transaction rejected. Missing or invalid materiel identification.
933 Transaction rejected. Discrepancy report follow-up submitted before action
activity response time has elapsed.
937 Transaction rejected. DoD WebSDR/WebSQCR unable to provide
requested Discrepancy report information copy.
938 Transaction rejected. Missing or invalid transaction set purpose code.
Reply Codes
939 Transaction rejected. Missing, invalid, or inappropriate discrepancy report
document type code.
941 Transaction failed during processing; it cannot be transmitted electronically
to the designated action activity.
943 Transaction rejected. Fund Code or Standard Line of Accounting (SLOA)
data elements do not match Standard Financial Information Structure
(SFIS) Fund Code to Fund Account Conversion Table.
CODE EXPLANATION
HM Hazardous Material. GenComm legacy equivalent code is M.
HW Hazardous and Non-Regulated Waste. GenComm legacy equivalent code
is W.
SC Scrap Property. GenComm legacy equivalent code is S.
SS Special Services Request. GenComm legacy equivalent code is P.
US Useable Property. GenComm legacy equivalent code is N.
CODE EXPLANATION
1 Lithographs
2 Digital Data Products/ Plastics
3 Publications
4 Catalogs
5 Download Only
6 Download/Lithographic
7 Video Laser Disc Products
8 Flip - Flight Information Program
9 Navigational Filmstrips
P Gridded Air Photos
CODE EXPLANATION
0 Redistribution Action
1 New Item
2 Revision of existing item
3 Reprint of existing item
4 Reprint of new item
5 Corrected reprint
6 Procured Item with Same Edition
APPLICABLE
CODE NAME/DEFINITION EXPLANATION
TRANSACTION
1
Refer to Request for Implementation Date for ADC 12. Not authorized for use; implementation pending.
2
Refer to ADC 1160.
APPLICABLE
CODE NAME/DEFINITION EXPLANATION
TRANSACTION
3
Refer to ADC 1323.
4
Refer to ADC 1273.
APPLICABLE
CODE NAME/DEFINITION EXPLANATION
TRANSACTION
5
Refer to ADC 259, Revise DLMS Supplement 867I and MILSTRAP Issue Transactions to Support Navy
Requirement for Reason for Reversal Code.
6
Refer to ADC 1160 and ADC 1273.
APPLICABLE
CODE NAME/DEFINITION EXPLANATION
TRANSACTION
7
Ibid.
CODE EXPLANATION
00 Forecast received; awaiting evaluation.
01 Forecast accepted, processed, and planned.
02 Rejected. Unit of Measure/Unit of Use does not match.
03 Rejected. Item does not exist in Source of Supply Item Master.
04 Rejected. Nuclear or reparable item. For DLA use only.
05 Rejected. Non-stocked item by Source of Supply Item.
06 Rejected. Invalid submitter DoDAAC/Sold-To DoDAAC combination.
DLA managed for Fleet Readiness Center (FRC) requirements use only
07 Reserve for future use.
08 Reserve for future use.
09 Rejected. Item has future requirements with no requisition history within
the past 12 months. FRC use only.
10 Rejected. Hazardous item. FRC use only.
11 Rejected. Item planned via other business processes as agreed upon
with Formal Collaborative partners. DLA managed items only.
12 Rejected. Item excluded by Supply Chain or Profit Center from the
Formal Collaborative Process. DLA managed items only.
13 Rejected. Item not managed by Source of Supply.
AP7.34.3. Warehouse project codes are not related to requisition project codes (Refer
to DLM 4000.25, Volume 2, AP7.13, Appendix 7.13.).
AP8. APPENDIX 8
FORMATS INDEX
APPENDIX DIC TITLE PAGE
1
Use of Document Identifier Code (DIC) AB_ changed from intra- to inter-Service for direct delivery from
procurement last reported as not implemented by GSA. Refer to AMCL 155.
AP8-1 APPENDIX 8
DLM 4000.25, Volume 2, November 26, 2019
Change 13
APPENDIX DIC TITLE PAGE
AP8-2 APPENDIX 8
DLM 4000.25, Volume 2, November 26, 2019
Change 13
APPENDIX DIC TITLE PAGE
2
Established procedures to reinstate canceled requisitions last reported as not implemented by USN.
Refer to AMCL 150C.
AP8-3 APPENDIX 8
DLM 4000.25, Volume 2, November 26, 2019
Change 13
APPENDIX DIC TITLE PAGE
3
Procedures to control access to DOD material inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
4
Ibid.
5
Use of revised MOV temporary suspension procedures for selected activities last reported as not
implemented by USMC. Refer to AMCL 37.
AP8-4 APPENDIX 8
DLM 4000.25, Volume 2, November 26, 2019
Change 13
AP8.1.2. Formats. Legacy MILSTRIP formats are described in AP8.2 through AP8.55.
1
Refer to ADC 441 and ADC 441A, Exception Rules to Accommodate Communication of Ammunition/
Ammunition Related Quantities in Excess of Five Digits
1
See the AP2 series of appendices for an explanation of the data fields.
2
Requisitions to DLA Disposition Services (RIC S9D) cannot reflect an entry in rp 21-22
3
On an Intra-Army basis, a suffix code entry is authorized for identification of post-post partial issues of
materiel by Army Single Stock Fund Activities. These requisitions will contain Army Edit Action Code IV in
rp 74-75.
4
Use of RDP for conventional ammunition last reported as not implemented by USAF. Refer to AMCL
148.
5
Processing Points passing DIC AM_ transactions to another source of supply for continued processing
will enter their RIC in rp 67-69.
6
The DLA Distribution Mapping System (DDMS) will enter the DDMS RIC SD7 in A0_ transactions
returned to Mapping Enterprise Business System (MEBS)(HM8) for processing. This will indicate to
MEBS that this is not the initial processing of the requisition (requisition was previously reviewed and
forwarded to DDMS, which was unable to fulfill).
7
On Intra-Army basis a RIC entry is authorized for identification of the storage site related to post-post
issues of materiel by Army Single Stock Fund Activities. These post-post requisitions will contain Army
Edit Action Code IV in rp 74-75.
8
On Intra-Army requisitions rp 70 will contain the ownership/purpose code and rp 71 will contain the
supply condition code of the material post-post issued by Army Single Stock Fund Activities. These post-
post requisitions will contain Army Edit Action Code IV in rp 74-75.
9
On Intra-Army basis both post-post and image Single Stock Fund Activity requisitions may contain a
management code in rp 72 to facilitate processing.
10
On Intra-Army basis requisitions may contain an Army Edit Action Code in rp 74-75 to indicate the
actions required by the receiving system in order to process transactions and direct authorized follow-on
actions. This code is meaningful to the Army only and is used on both post-post and image requisitions.
11
On Intra-Army basis requisitions may contain the date generated in rp 77-80. This date is required to
accurately process transactions relative to image, post-post and working requisitions submitted by Army
Single Stock Fund activities.
12
For intra-Air Force lateral requisitions, the source of supply identified in rp 4-6 is another Air Force
base, the RIC of the requisitioner is identified in rp 73-75, and the RIC of the DoD source of supply is
identified in rp 78-80. Refer to ADC 266.
13
For intra-Air Force requisition modification, the unit price may be identified in rp 71-80. Refer to ADC
263.
14
For intra-Navy organic maintenance requisitions (citing Project Code Z5X), used to identify the storage
activity from which the requisitioned item is requested in rp 74-76.
15
Refer to ADC 1176.
16
Procedures to control access to DoD materiel inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
17
Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 1014.
18
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
19
Procedures to control access to DoD materiel inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A
20
Procedures, formats, and codes for requisitioning material from disposal last reported as not
implemented by DLA. Refer to AMCL 139A.
21
Ibid.
1
See the “AP6” series of appendices for the explanation of data fields.
2
Processing points passing DIC AM_ modifiers to another supply source for continued processing will
enter their RIC in rp 67-69.
3
Requirement to expand the CLPSC to differentiate a Foreign Military Sales Order (FMSO) I requisition
from a FMSO II requisition was not implemented. Refer to AMCLs 7 and 22.
1
If the CAGE and part number cannot be entered in rp 8-22, use DD Form 1348-6 (AP1.6) to requisition
the part number or non-NSN items.
2
Air Force part-numbered requisitions use rp 67-80 (without the identification code in rp 70. to provide
descriptive information. This may not be recognizable on an inter-Service basis. Refer to ADC 264.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Reference Identification 71-80 Enter the identification of the reference
specified in rp 70.
GOVERNMENT-FURNISHED MATERIEL REQUISITION ENTRIES: 3
(rp 23-67 entries are the same as AP8.2)
Part Number Designation 68 Enter an E in the GFM requisition when a
part number is requisitioned.
Call/Order Number 69-72 If required by an Service/Agency (S/A)
contract, enter the appropriate contract
legacy four-position call/order number
associated with the PIIN; otherwise leave
blank.
Procurement Instrument 73-80 At the option of the S/A, enter last eight
Identifier (PIID) positions of the PIID in lieu of the
Manufacturing Directive Number (MDN)
in rp 54-56. This entry is mandatory. 4, 5
When materiel is authorized under a PIID
call/order number (F in 9th position),
provide the last eight positions.
MANAGEMENT CONTROL ACTIVITY ENTRIES: Entries Required for Requisitions for
Government-Furnished Materiel.
Routing Identifier Code 4-6 Enter the RIC of the source of supply.
Distribution 54-56 Enter the distribution code of the
Management Control Activity (MCA)
validating the transaction or the MDN
consisting of the MCA’s distribution code
in rp 54 and two other alpha/numeric
characters in rp 55-56.
Routing Identifier Code 74-76 If required by the S/A, enter the RIC of
the validating MCA in rp 74-76.
3
Procedures to control access to DoD materiel inventories by defense contractors last reported as not
implemented by Army vice USA (Retail). Refer to AMCL 1A.
4
Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 1014.
5
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
AP8.5.1. The following entries will apply when no positive supply status has been
received from the supply source:
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC AT_.
Code
All Other Fields 1, 2 4-80 Duplicate entries from the original
requisition.
AP8.5.2. The following entries will apply when positive supply status has been received
from a supply source:
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
AP8.5.3. The following entries apply when a shipment status transaction is received but
it does not contain adequate information for shipment tracing under DTR 4500.9-R,
“Defense Transportation Regulation 4:
1
On Intra-Army basis AT_ transactions may contain an Army Edit Action Code in rps 74-75 to indicate
the actions required by the receiving system in order to process transactions and direct authorized follow-
on actions. This code is meaningful to the Army only.
2
On Intra-Army basis AT_ transactions may contain the date generated in rp 77-80. This date is required
to accurately process transactions submitted by Army Single Stock Fund activities.
3
Processing points passing DIC AF_ or DIC AT_ transactions to another source of supply for continued
processing will enter their RIC in rp 67-69.
4
Procedures requesting and/or providing the Department of Defense Activity Address Code (DoDAAC) of
the initial shipping activity last reported as not implemented by Government Services Administration
(GSA). Refer to AMCL 5.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AFY.
Routing Identifier Code 4-6 Enter the RIC identifying the last known
supply source (rp 4-6 of the shipment
status transaction).
All Other Fields 7-80 Duplicate the entries from the last
shipment status received.
AP8.6.1. The following entries shall apply when shipment status has been received
from a shipping activity by DLA Disposition Services on shipments to DLA Disposition
Services Field Offices:
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AFX for initial followup.
Enter DIC AFZ when response to
initial followup has not been received.
Routing Identifier Code 4-6 See Paragraph AP8.6.3. instructions.
All Other Fields 7-61 Duplicate entries from the DIC AS3
shipment status.
Blank 62-64 Leave blank.
Advice 65-66 Enter the advice code from AP2.15
indicating the reason for followup.
Research Guidance 67-74 Identify as “CRITICAL” or leave blank,
as appropriate.
All Other Fields 75-80 Leave blank.
AP8.6.2. The following entries shall apply when shipment status has not been received
from a shipping activity by DLA Disposition Services on shipments to DLA Disposition
Services Field Offices:
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AFX for initial followup.
Enter DIC AFZ when response to
initial followup has not been received.
Routing Identifier Code 4-6 See Paragraph AP8.6.3. instructions.
Media and Status 7 Leave blank.
Stock Number 8-22 Enter stock number/data as shown in
the DLA Disposition Services Field
Office receipt of usable property
document.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Unit of Issue 23-24 Enter unit of issue as shown in the
DLA Disposition Services Field Office
receipt of usable property document.
Quantity 25-29 Enter quantity as shown in the DLA
Disposition Services Field Office
receipt of usable property document.
Document Number 30-43 Enter document number as shown in
the DLA Disposition Services Field
Office receipt of usable property
document.
Suffix 44 Enter suffix code as shown in the DLA
Disposition Services Field Office
receipt of usable property document
or leave blank when none is entered
by DLA Disposition Services Field
Office.
Supplementary Address 45-50 Enter DoDAAC of receiving DLA
Disposition Services Field Office.
Signal 51 Leave blank.
Fund 52-53 Leave blank.
Distribution 54 Enter 9.
All Other Fields 55-64 Leave blank.
Advice 65-66 Enter advice code from AP7.15
indicating the reason for the followup.
Research Guidance 67-74 Identify as “CRITICAL” or leave blank,
as appropriate.
All Other Fields 75-80 Leave blank.
AP8.6.3.1. DLA Disposition Services shall generate DIC AFX/AFZs with rp 4-6
always blank.
AP8.6.3.3.1. Enter the shipping activity RIC in rp 4-6 of the DIC AFX/AFZ
and route them to the shipping activity via DAAS for the shipping activity to answer
directly to DLA Disposition Services using DIC ASZ; or
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AC_ or AK_.
Routing Identifier Code 4-6 Enter RIC for the last known source
of supply 1.
Media and Status 7 Enter the M&S code as shown in the
original requisition.
Stock or Part Number 8-22 Enter the NSN or part number as
shown in the requisition or in supply
status, when such status has been
received.
Unit of Issue 23-24 Enter the U/I as shown in the
requisition or status.
Quantity 25-29 Enter the quantity for which
cancellation is requested. For
ammunition and ammunition related
item cancellations only (items in
Federal supply group (FSG) 13 and
for Federal supply classification
(FSC) 1410, 1420, 1427, 1440,
5330, 5865, 6810 or 8140), enter an
M in rp 29 to express in thousands
any quantity exceeding 99,999.
Example: A quantity of 1,950,000
shall be expressed as 1950M (1950
in rp 25-28 and an M in rp 29).
Document Number 30-43 Enter document number of the
requisition for which cancellation is
requested.
Suffix 44 Enter the suffixcode as shown on
the supply status, when applicable.
Otherwise, enter demand code from
the requisition.
1
Processing points passing DIC AC_ or DIC AK_ transactions to another supply source for continued
processing will enter their RIC in rp 67-69.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
All Other Fields 2 45-61 Enter data from the requisition or
supply status.
Date of Preparation 62-64 Enter the ordinal day of preparation.
All Other Fields 65-80 Enter data from the requisition or
supply status. 3
2
On Intra-Army basis cancellations may contain an Army Edit Action Code in rp 74-75 to indicate the
actions required by the receiving system in order to process transactions and direct authorized follow-on
actions. This code is meaningful to the Army only.
3
For intra-Air Force requisition cancellation/follow-up, the reason for cancellation
(Excess Cause Code) maybe identified in rp 71. Refer to ADC 265.
RECORDS
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AC6/AC7. Also used by storage
activity in reply to cancellation request from
the ICP (DIC AG6).
Routing Identifier Code 4-6 Enter RIC applicable to the activity to which
the DIC AC6/7 is directed. When the DIC
is AG6, enter the RIC of the source of
supply that created the DIC AC6/7.
Media and Status 7 Enter the M&S code as shown in the
materiel relese order (MRO) or lateral
redistribution order (LRO).
Stock or Part Number 8-22 Enter NSN or part number from original
requisition.
Unit of Issue 23-24 Enter U/I from original requisition.
Quantity 25-29 Enter quantity for which cancellation is
requested. For ammunition and
ammunition related cancellations only
(items in Federal supply group (FSG) 13
and for Federal supply classification (FSC)
1410, 1420, 1427, 1440, 5330, 5865, 6810
or 8140), enter an M in rp 29 to express in
thousands any quantity exceeding 99,999.
Example: A quantity of 1,950,000 shall be
expressed as 1950M (1950 in rp 25-28 and
an M in rp 29).
Document Number 30-43 Enter document number of the MRO or
LRO for which cancellation action is
requested.
RECORDS
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Suffix 44 Enter suffix code shown in the MRO or
LRO; otherwise, leave blank. (For DIC
AG6, enter the suffix code from the DIC
AC6/AC7.)
New Consignee DoDAAC 45-50 Enter Department of Defense activity
address code (DoDAAC) to reflect the new
consignee to which shipments are to be
diverted; otherwise, leave blank.
Signal 51 Enter signal code as shown in the MRO or
LRO.
Fund 52-53 Enter fund code as shown in the MRO or
LRO.
Distribution 54-56 When used to cancel an LRO, enter 2 for
consumables or 3 for reparables in rp 54.
Otherwise, enter data as shown in the
MRO.
Project 57-59 Enter the project code as shown on the
MRO or LRO or from the 1348-1A (or
1348-2).
Priority 60-61 Enter the priority designator as shown on
the MRO or LRO or from the DD Form
1348-1A (or DD Form 1348-2).
Required Delivery 62-64 Enter data as shown on the MRO or LRO
or from the DD Form 1348-1A (or DD Form
1348-2).
Advice 65-66 Enter the advice code as shown on the
MRO or LRO or from the DD Form 1348-
1A (or DD Form 1348-2).
Routing Identifier Code 67-69 Enter the RIC to identify the activity
preparing the document.
Blank 70-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC ACP or ACM.
Routing Identifier Code 4-6 Enter RIC of the activity to which the
transaction is to be transmitted.
Media and Status 7 Enter the M&S code as shown in the
original requisition.
Stock or Part Number 8-22 Enter the NSN or part number from original
requisition, as applicable.
Unit of Issue 23-24 Enter U/I from original requisition, as
applicable.
Quantity 25-29 a. Enter the quantity for which cancellation
is requested.
b. For ammunition and ammunition related
cancellations only (items in Federal supply
group (FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427,
1440, 5330, 5865, 6810 or 8140), enter an
M in rp 29 to express in thousands any
quantity exceeding 99,999. Example:
Express a quantity of 1,950,000 as 1950M
(1950 in rp 25-28 and an M in rp 29).
Document Number 30-43 Enter the requisition document number as in
the procurement request.
Suffix 44 Enter the suffix code as shown in the
procurement request; otherwise, leave
blank.
New Consignee DoDAAC 45-50 Enter the DoDAAC to reflect the new
consignee to which shipments are to be
diverted; otherwise, leave blank.
Multiple Use 51-69
Procurement Request (51-64) Enter PRN, when applicable.
Number
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Blank (65-69) When procurement request number (PRN)
is applicable, leave blank.
OR
Procurement Instrument (51-63) Enter PIID. 1 Enter the PIID call/order
Identifier (PIID) number (F in 9th position) if applicable.
Contract Line Item Number (64-67) Enter CLIN.
Contract Subline Item (68-69) Enter contract subline item number, if
Number applicable.
Project 70-72 Enter the project code from original
requisition.
Priority 73-74 Enter priority from original requisition.
Blank 75-77 Leave blank.
Routing Identifier Code 78-80 Enter the RIC to identify the activity
preparing transaction.
1
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
RECORD
FIELD LEGEND POSITION(S ENTRY AND INSTRUCTIONS
Document Identifier Code 1 1-3 Enter DIC AE_.
Routing Identifier Code 4-6 Enter RIC of the source of supply furnishing
the supply status (RIC From). If used as a
DIC AE6 transaction, enter the RIC of the
source of supply to which the transaction will
be sent (RIC To). 2
Media and Status 7 Enter the M&S code as shown in the original
requisition.
Stock or Part Number 8-22 Enter NSN or part number.
Unit of Issue 23-24 Enter U/I.
Quantity 3 25-29 a. Enter quantity for which status is provided.
b. For ammunition and ammunition related
items only (items in Federal supply group
(FSG) 13 and for Federal supply slassification
(FSC) 1410, 1420, 1427, 1440, 5330, 5865,
6810 or 8140), enter an M in rp 29 to express
in thousands any quantity exceeding 99,999.
Example: A quantity of 1,950,000 will be
expressed as 1950M (1950 in rp 25-28 and an
M in rp 29).
Document Number 30-43 Enter document number as shown in the
requisition.
1
Intra-Service ammunition and ammunition related orders following the ammunition storage site selection
utilize the storage depot being transacted against instead of the Inventory Control Point when providing
supply and shipment status in order to maintain traceability of ammunition and ammunition related items
shipped. Refer to ADC 441/441A, Clarification of Exception Rules to Accommodate Communication of
Ammunition/Ammunition Related Quantities in Excess of Five Digits.
2
When used by the material processing center (MPC) to notify the Navy customer that materiel has arrived
(NL Status), been delivered (NW or Navy-unique BA Status), or transshipped (NY Status), rp 4-6 will identify
the MPC that originated the transaction.
3
See Appendix AP8.1 - Formats Introduction, Paragraph AP8.1.3.
RECORD
FIELD LEGEND POSITION(S ENTRY AND INSTRUCTIONS
Suffix 44 a. Enter the suffix code applicable to quantity
in rp 25-29 when the requisitioned quantity is
divided into separate supply actions.
b. When the requisition quantity is not
divided, leave this field blank.
Supplementary Address 45-50 Enter data from original requisition.
Signal/Shipment Hold Code 51 Enter data from original requisition. 4
Fund 52-53 Enter fund code from original requisition.
Distribution 54-56 When used as an AE6 to provide status on the
processing on an lateral redistribution order
(LRO), enter 2 for consumables or 3 for
reparables in rp 54. Otherwise, enter data as
shown in the requisition. 5
Project 57-59 Enter project code from original requisition.
Priority 60-61 Enter data from the original requisition.
Transaction Date 62-64 Enter the day that corresponds with the date
of this reply.
Status 65-66 Enter the status code to convey the
information regarding the status of this
transaction.
Routing Identifier Code 67-69 Enter the “last known source” to which
authorized follow-up action will be directed. If
used as a DIC AE6 transaction, the RIC will
be the activity preparing the document. 6
Estimated Shipping Date 70-73 When designated by the status code, enter
the four-position ordinal day by which it is
estimated the materiel will be shipped. 7,8
4
If the Distribution Code in rp 5556 = 111 and the Status Code (rp 65-66) is blank, rp 51 contains the hold
code; if a status code is present, then rp 51 is the signal code.
5
When used by transportation and supply receipt and acknowledgement interchange, insert Distribution Code
= 111.
6
When used by the MPC to notify the Navy customer that materiel has arrived (NL Status) or been delivered
(NW or Navy-unique BA Status), rp 67-69 will repeat the identification of the MPC that originated the
transaction in rp 4-6. When used for transshipment notification (NY Status), rp 67-69 will identify the MCP to
which materiel is transshipped.
7
When used by the MPC, this will be the date associated with the materiel arrival (NL Status) or delivery (NW
or Navy-unique BA Status), or transshipment (NY Status).
8
When used with PW Status, this will be Engineering Support Activity Response Due Date indicating the date
established by the IMM/ICP waiting for a response from the Engineering Support Activity. A revised date may
RECORD
FIELD LEGEND POSITION(S ENTRY AND INSTRUCTIONS
Multiple Use 9,10
74-80
Unit Price 74-80 Enter unit price of the stock or part number
shown in rp 8-22. When the status code in rp
65-66 relates to an erroneously routed
requisition, this field will be left blank.
OR
Blank (74-75) Leave blank.
Minimum Order Quantity (76-80) For C8 Status, enter the minimum order
quantity.
OR
Blank (74-75) Leave blank.
Federal Supply (76-80) For DA Status, enter Federal supply schedule
Schedule Number 11 number constructed as follows:
rp 76-77 Group (numeric) rp 78-79 Part
(numeric) rp 80 Section (alphabetic).
Unit Price 12 74-80 Enter unit price of the stock or part number
shown in rp 8-22.
be provided in a second transmission of Supply Status PW if additional time is required to coordinate with the
ESA. Refer to ADC 1049.
9
When used by the storage activity in response to a query by the ICP (DIC AE6), this data may be omitted at
Component option.
10
DIC AE9 transactions generated by Defense Automatic Addressing System (DAAS) shall always be blank
in rp 74-80.
11
Requirement to use DA requisition rejection status to indicate the supply source is direct ordering from the
Federal Supply Schedule last reported as not implemented by United States Air Force (USAF). Refer to
AMCL 132B.
12
When used by storage in response to a query by the ICP (DIC AE6), this data may be omitted at
Component option.
RECORD
FIELD LEGEND POSITION(S ENTRY AND INSTRUCTIONS
For DIC AE_ Transactions with Status Code CE
79-80 For transactions containing rejection Status
Code CE in rp 65-66, source of supply will
enter the correct unit of issue in rp 79-80 13.
For DIC AE6 Transactions with Distribution Code 2 and Status Code CB (Army/DLA Interface
Only)
13
Requirement to provide correct unit of issue when original unit of issue on the requisition could not be
converted last reported as not implemented by United States Navy (USN). Refer to AMCL 162.
14
Authorized for use on an intra-Army basis (ADC 191), and subsequently expanded for inter-Service/Agency
use (ADC 312). Implementation outside Army applications is pending.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AB_.
Routing Identifier Code 4-6 Enter the RIC of the source of supply
furnishing the status.
Media and Status 7 Enter the M&S code as shown in the
original requisition.
Stock or Part Number 8-22 Enter stock or part number to which the
status applies.
Unit of Issue 23-24 Enter U/I.
Quantity 25-29 a. Enter quantity for which the status is
provided
b. For status on ammunition and
ammunition related items only (items in
Federal supply group (FSG) 13 and for
Federal supply classification (FSC) 1410,
1420, 1427, 1440, 5330, 5865, 6810 or
8140), enter an M in rp 29 to express in
thousands and quantity exceeding 99,999.
Example: A quantity of 1,950,000 shall be
expressed as 1950M (1950 in rp 25-28 and
an M in rp 29).
Document Number 30-43 Enter the document number as shown in
the requisition.
Suffix 44 Enter the suffix code applicable to the
quantity in rp 25-29 when the requisitioned
quantity is divided into separate supply
actions; otherwise, leave blank.
Supplementary Address 45-50 Enter SUPADD from the original requisition
or modified transaction.
Signal 51 Enter signal code from the original
requisition or modified transaction.
1
Use of DIC Code AB_ changed from intra- to inter-Service for direct delivery from procurement last
reported as not implemented by Government Services Administration (GSA). Refer to AMCL 155.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Fund 52-53 Enter fund code from the original
requisition or modified transaction.
Distribution 54-56 Enter distribution code from the original
requisition or modified transaction.
Project 57-59 Enter project code from the original
requisition or modified transaction.
Procurement Instrument 60-72 Enter the PIID. 2 Enter the PIID call/order
Identifier (PIID) number (F in 9th position) if applicable.
Call/Order Number 73-76 Enter the legacy four-position call/order
number associated with the PIIN, if
applicable; otherwise; leave blank.
Estimated Shipping Date 77-80 Enter the four-position ordinal date.
2
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC A5_/AF6.
Routing Identifier Code 4-6 Enter the RIC indicating the source to which
the material release order (MRO)/followup
is directed.
Media and Status 7 Enter the M&S code as shown in the
original requisition.
Stock or Part Number 8-22 Enter NSN or part number of the item
ordered for release. For subsistence items,
enter type of pack in rp 21.
Unit of Issue 23-24 Enter U/I.
Quantity 1 25-29 a. Enter quantity for which MRO/followup is
provided.
b. For ammunition and ammunition related
items only (items in Federal supply group
(FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427,
1440, 5330, 5865, 6810 or 8140), enter an
M in rp 29 to express in thousands any
quantity exceeding 99,999. Example:
Express a quantity of 1,950,000 as 1950M
(1950 in rp 25-28 and an M in rp 29).
Document Number 30-43 Enter document number as shown in the
requisition.
Suffix 44 a. Enter the suffix code applicable to
quantity in rp 25-29 when the requisitioned
quantity is divided into separate actions.
b. When the requisitioned quantity is not
divided, this field shall be left blank.
1
See Appendix AP3.1 - Formats Introduction, Paragraph AP3.1.3.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Supplementary Address 45-50 Enter data from original requisition.
Signal 51 Enter data from original requisition.
Fund 52-53 Enter data from original requisition.
Distribution 54-56 When used as a followup to an laterial
redistribution order (LRO) of retail assets,
enter “2" for consumables or “3" for
reparables in rp 54; otherwise, enter data
as shown in the material release order
(MRO).
Project 57-59 Enter data from original requisition.
Priority 60-61 Enter data from original requisition.
Required Delivery 62-64 Enter data from original requisition.
Date/Required Delivery
Period 2
Advice 65-66 Enter data from original requisition.
Routing Identifier Code 67-69 Enter RIC applicable to the activity
originating the MRO/followup. When the
MRO format is used as a followup, enter
the inventory control point ( ICP) RIC if
shipment status in reply is to be furnished
to the supply source.
Ownership 70 Enter ownership code, as applicable.
Supply Condition 71 Enter appropriate condition code.
Management 72 Enter management code applicable to the
transaction.
Intra-Service/Agency 73 For use under intra-Service/Agency (S/A)
procedures. Leave blank for inter-S/A
transactions.
Unit Price 74-80 Enter unit price applicable to the NSN or
part number shown in rp 8-22.
2
Use of RDP for conventional ammunition last reported as not implemented by united States Air Force
(USAF). Refer to AMCL 148.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC A5J for disposal release order
(DRO), DIC AFJ for ICP follow-up on a
DRO, DIC ACJ for inventory control
point (ICP) cancellation of a DRO, DIC
AKJ for ICP follow-up on DRO
cancellation, or DIC AGJ for reply to
DRO cancellation.
Routing Identifier Code 4-6 Enter the appropriate code applicable to
the facility to which the DRO is directed.
(If used as a DIC AGJ transaction, will
contain RIC of the source of supply to
which the document shall be
transmitted).
Media and Status 7 Enter 0 or leave blank.
Stock or Part Number 8-22 1 Enter the NSN or part number of the
item ordered for disposal. For
subsistence items, enter the type of pack
in rp 21.
Unit of Issue 23-24 Enter the unit of issue applicable to the
stock or part number.
Quantity 25-29 Enter the quantity to be transferred,
based on the inventory control record
balance. Quantity actually transferred
shall be dependent on the entry in rp 55-
61 if applicable. (For DIC ACJ/AKJ,
enter DIC A5J quantity to be canceled.
For DIC Code AGJ, enter quantity
canceled.)
Document Number 30-43 Enter document number as assigned by
the preparing activity.
Suffix 44 Leave blank.
1
For subsistence transactions, rp 22 and 52-53 shall contain the date packed indicator code.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Supplementary Address 45-50 Leave blank in DRO. The shipping
activity shall enter the Department of
Defense activity address code
(DoDAAC) of predesignated DLA
Disposition Services Field Office.
Signal 51 Enter applicable signal code if required;
otherwise, leave blank. For hazardous
materiel or waste, use Signal Code A, B,
C, or L. For Signal Code B, identify the
bill-to activity to be included on the
disposal turn-in document (DTID), Block
27, using an off-line communication with
the activity to which the DRO is directed.
Fund 52-53 Enter the fund code to be credited with
proceeds from the sale by DLA
Disposition Services Field Office. If no
credit is desired, leave blank. For
hazardous materiel or waste, this shall
be the bill-to fund code for reimbursable
actions associated with disposal.
Distribution 54 Enter Distribution Code 9.
Retention Quantity 55-61 Enter quantity to be retained in stock by
activity in rp 4-6. When the quantity to
be retained exceeds the retention
quantity field, the transaction shall be
processed offline.
Precious Metals Indicator 62 Enter applicable code from AP7.23.
Automated Data Processing 63 Enter applicable ADPE code from
Equipment Identification AP7.24.
Disposal Authority 64 Enter applicable code from AP7.21.
Demilitarization 65 Enter the demilitarization code assigned
by the ICP/IMM as required by DoD
Manual 4160.21, “Defense Materiel
Disposition”
Reclamation 66 Enter Y if reclamation is required prior to
release to DLA Disposition Services
Field Office. Enter N if reclamation is
not required.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Routing Identifier Code 67-69 Enter RIC of ICP/IMM originating the
DRO. (For DIC AGJ transaction, enter
RIC of the activity preparing the
transaction.)
Ownership 70 Enter ownership code, if applicable,
otherwise, leave blank.
Supply Condition 71 Enter the condition code of the materiel
to be transferred.
Management 72 Enter management code, if applicable;
otherwise, leave blank.
Flight Safety Critical Aircraft 73 Enter Criticality Code E to indicate
Parts 2 Nuclear Hardened Flight Safety Critical
Aircraft Parts (FSCAP) or Criticality
Code F to indicate a standard FSCAP.
Unit Price 74-80 Enter the unit price for the NSN or part
number shown in rp 8-22.
2
Identification of FSCAP codes on the DTID and disposal release transactions last reported as not
implemented by USA and USN. Refer to Approved DLSS/DLMS Change 6.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC ARA, ARB, AR0, AUA, AUB or AU0.
Code
Routing Identifier Code 4-6 Enter RIC of thesource of supply from which the
materiel release order (MRO)/cancellation
request was received.
Media and Status 7 Enter the M&S code as shown in the
MRO/cancellation request.
Stock or Part Number 8-22 Enter NSN or part number of the item supplied.
Unit of Issue 23-24 Enter the unit issue.
Quantity 1 25-29 a. Enter the quantity.
b. For ammunition and ammunition related
items only (items in Federal supply group (FSG)
13 (and Federal supply classification (FSC)
1410, 1420, 1427, 1440, 5330, 5865, 6810 or
8140), enter an M in rp 29 to express in
thousands any quantity exceeding 99,999.
Example: Express a quantity of 1,950,000 as
1950M (1950 in rp 25-28 and an M in rp 29).
Document Number 30-43 Enter document number as shown in the
MRO/cancellation request.
Suffix 44 Enter the suffix code contained in rp 44 of the
MRO. If no code is in rp 44 of the
MRO/cancellation request, leave blank.
Supplementary Address 45-50 Enter SUPADD as shown in the
MRO/cancellation request.
Hold 51 Enter shipment hold code, when applicable.
Leave blank in response to follow-up when item
has not been selected for shipment.
Fund 52-53 Enter the fund code as shown in the MRO.
1
See Appendix AP8.1 - Formats Introduction, Paragraph AP8.1.3
2
Refer to the USTRANSCOM Reference Data Management (TRDM) for available code list at
https://trdmws.maf.ustranscom.mil/trdm/index.html (DTR Data)
3
Procedures, formats, and codes for requisitioning material from disposal last reported as not
implemented by DLA. Refer to AMCL 139A.
4
Refer to the USTRANSCOM Reference Data Management (TRDM) for available code list at
https://trdmws.maf.ustranscom.mil/trdm/index.html (DTR Data)
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC ARH.
Routing Identifier Code 4-6 Enter the RIC of the source of supply
generating this transaction.
Media and Status 7 Enter the M&S code from the materiel
release order (MRO).
Stock or Part Number 8-22 Enter the NSN or part number from the
MRO.
Unit of Issue 23-24 Enter the U/I from the MRO.
Quantity 25-29 Enter the quantity from the MRO.
Document Number 30-43 Enter the document number as shown in
the MRO.
Suffix 44 Enter the suffix code contained in rp 44 of
the MRO. If rp 44 in the MRO is blank,
leave blank.
Supplementary Address 45-50 Enter the SUPADD as shown in the MRO.
Blank 51-56 Leave blank.
Date Shipped 1 57-59 Enter date released/tendered to carrier;
otherwise, leave blank.
Blank 60-76 Leave blank.
Mode of Shipment 2 77 Enter the code identifying the mode of
shipment 3; otherwise, leave blank.
Blank 78-80 Leave blank.
1
For U.S. forces, leave blank. For Security Assistance, may contain the release date from the materiel
receipt acknowledgement (MRA).
2
For U.S. forces, leave blank. For Security Assistance, may contain the mode of shipment from the
MRA.
3
Refer to the TRDM for available code list at URL: https://trdmws.maf.ustranscom.mil/trdm/index.html
(DTR Data)
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC ARJ, ARK, ARL, or AEJ, as
applicable.
Routing Identifier Code 4-6 Enter RIC of the source of supply from
which the DRO or follow-up was received.
Media and Status 7 Leave blank.
Stock or Part Number 8-22 1 Enter NSN or part number of the item
released.
Unit of Issue 23-24 Enter the U/I from the DRO.
Quantity 25-29 a. Enter the quantity for which release is
confirmed (DIC AR_) or the quantity
appropriate to the status being provided
(DIC AEJ).
b. For ammunition and ammunition related
items only (items in FSG 13 and for FSC
1410, 1420, 1427, 1440, 5330, 5865, 6810
or 8140), enter an M in rp 29 to express in
thousands any quantity exceeding 99,999.
Example: Express a quantity of 1,950,000
as 1950M (1950 in rp 25-28 and an M in rp
29).
Document Number 30-43 Enter document number as shown in the
DRO.
Suffix 44 Leave blank.
Retention Quantity 45-51 Enter quantity actually retained.
52-54 2 Perpetuate from DRO.
Blank 55-56 Leave blank.
1
For subsistence transactions, rp 22 and 52-53 will contain the date packed/expiration date indicator
code.
2
Ibid.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Estimated Shipping Date 57-59 Enter date delivered/shipped to DLA
or Date Shipped Disposition Services Field Office. When
used in response to follow-up and
shipment has not occurred, enter ESD.
Blank 60-61 Leave blank.
Precious Metals 62 Enter applicable code from AP2.23.
ADPE Identification 63 Enter applicable code from AP2.24.
Disposal Authority 64 Enter applicable code from AP2.21.
Supply Status 65-66 Enter supply status from AP2.16, if
applicable; otherwise, leave blank.
Routing Identifier Code 67-69 Enter the RIC (From).
Ownership 70 Enter the ownership code, as applicable.
Supply Condition 71 Enter the supply condition code, as
applicable.
Management 72 Enter the management code, as
applicable.
All Other Fields 73-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC A6_.
Routing Identifier Code 4-6 Enter RIC as indicated in rp 67-69 of the
MRO. This is the code of the accountable
point that originated the MRO.
Media and Status 7 Enter the M&S code as shown in the MRO.
Stock or Part Number 8-22 1 Enter NSN or part number as shown in the
MRO.
Unit of Issue 23-24 Enter U/I as shown in the MRO.
Quantity 25-99 a. Enter quantity denied.
b. For ammunition and ammunition related
items only (items in Federal supply group
(FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427,
1440, 5330, 5865, 6810 or 8140), enter an
M in rp 29 to express in thousands any
quantity exceeding 99,999. Example:
Express a quantity of 1,950,000 as 1950M
(1950 in rp 25-28 and an M in rp 29).
Document Number 30-43 Enter document number as shown in the
MRO.
Suffix 44 Enter the suffix code as shown in the MRO.
Supplementary 45-50 Enter SUPADD as shown in the MRO.
Signal 51 Enter the signal code as shown in the MRO.
Fund 52-53 2 Enter the fund code as shown in the MRO.
Distribution 54-56 Enter the distribution code as shown in the
MRO.
1
For subsistence transactions, rp 22 and 52-53 shall contain the date packed/expiration date indicator
code.
2
Ibid
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Project 57-59 Enter the project code as shown in the
MRO.
Priority 60-61 Enter the priority as shown in the MRO.
Required Delivery 62-64 Enter data as shown in the MRO.
Advice 65-66 Enter the advice code as shown in the
MRO.
Routing Identifier Code 67-69 Enter the RIC identifying the activity
preparing the denial.
Ownership 70 Enter the ownership code, as applicable.
Supply Condition 71 Enter the supply condition, as applicable.
Management 72 Enter the management code indicating
reason for denial.
Intra-Service/Agency 73-80 For use with intra-S/A procedures;
otherwise, leave blank for inter-S/A
transactions.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC A6J.
Routing Identifier Code 4-6 RIC or the source of supply from which
the disposal release order (DRO) was
received.
Media and Status 7 Leave blank.
Stock or Part Number 8-22 Enter the stock or part number of the item
denied.
Unit of Issue 23-24 Enter U/I.
Quantity 25-29 a. Enter quantity denied; for example, the
difference between the quantity
transferred and the quantity shown in the
DRO.
b. For ammunition and ammunition
related items only Federal supply group
((FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427,
1440, 5330, 5865, 6810 or 8140), enter an
M in rp 29 to express in thousands any
quantity exceeding 99,999. Example:
Express a quantity of 1,950,000 as 1950M
(1950 in rp 25-28 and an M in rp 29).
Document Number 30-43 Enter document number as shown in the
DRO.
Suffix Code 44 Leave blank.
Retention Quantity 45-51 Enter quantity actually retained.
Fund 52-53 Perpetuate from the DRO.
Distribution 54 Perpetuate from the DRO.
Blank 55-56 Leave blank.
Denial Date 57-59 Enter date DRO is denied.
Blank 60-66 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Routing Identifier Code 67-69 Enter RIC identifying the activity preparing
(From) the denial.
Ownership 70 Enter ownership code, as applicable.
Supply Condition 71 Enter appropriate supply condition code.
Management 72 Enter management code indicating the
reason for denial.
Blank 73-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter the DIC applicable to the shipment
status (DIC AS1-6, AS8, or ASY) or reply to
cancellation request-shipment status (AU1-
5 or AU8). 1
Routing Identifier Code 2, 3 4-6 Enter the RIC of the source of supply that
generated the lateral redistribution order
(LRO)/materiel release order
(MRO)/cancellation request/disposal
release order (DRO)/DIC FTR or the
shipping activity if the shipment was not
initiated by a supply source LRO/MRO
cancellation request/DRO/DIC FTR. If a
disposal shipment was not initiated by a
source of supply DRO/DIC FTR and the
shipping activity has no RIC, leave blank. If
used as a DIC AS6, indicate the RIC of the
inventory control point (ICP)/integrated
materiel manager (IMM) to which the
transaction will be sent.
Media and Status 7 Use the M&S code from the
MRO/LRO/DRO or cancellation request.
Stock or Part Number 8-22 Enter the NSN or part number of the item
supplied.
Unit of Issue 23-24 Enter the U/I.
1
Procedures requesting and/or providing the DoDAAC of the initial shipping activity last reported as not
implemented by GSA. Refer to AMCL 5.
2
See Appendix AP8.1 - Formats Introduction, Paragraph AP8.1.3
3
Intra-Service ammunition and ammunition related orders following the ammunition storage site selection
utilize the storage depot being transacted against instead of the Inventory Control Point when providing
supply and shipment status in order to maintain traceability of ammunition and ammunition related items
shipped. Refer to ADC 441/441A, Clarification of Exception Rules to Accommodate Communication of
Ammunition/Ammunition Related Quantities in Excess of Five Digits.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Quantity 25-29 a. Enter the quantity shipped.
b. For ammunition federal supply group
(FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427,
1440, 5330, 5865, 6810 or 8140 items only,
enter an M in rp 29 to express in thousands
any quantity exceeding 99,999. Example:
Express a quantity of 1,950,000 as 1950M
(1950 in rp 25-28 and an M in rp 29).
Document Number 30-43 Use the document number from the
MRO/LRO/DRO or cancellation request.
Suffix 44 Use the suffix code from the
MRO/LRO/DRO or cancellation request. If
no suffix code, leave blank.
Supplementary Address 45-50 Use SUPADD from the MRO/DRO or
cancellation request. The shipping activity
will all enter the DoDAAC of the
predesignated DLA Disposition Services
Field Office for shipments to DLA
Disposition Services Field Offices. If used
as a DIC AS6, enter the DoDAAC of the
activity to which the credit for the materiel
and reimbursement for the packing, crating,
handling and transportation (PCH&T) costs
is to be provided.
Hold 51 If used as a DIC AS6, enter Signal Code B.
Otherwise, enter the shipment hold code,
when applicable.
Fund 52-53 Enter the fund code as shown in the
MRO/DRO or cancellation request. If used
as a DIC AS6, enter the fund code to which
the credit for the materiel and
reimbursement for the PCH&T costs is to be
provided.
Distribution 54-56 Enter the distribution code as shown in the
MRO/LRO/DRO or cancellation request.
Release Date 57-59 Enter the date the materiel is released to
the carrier.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Transportation Control 60-76 Enter the shipment unit TCN as prescribed
Number in DTR 4500.9-R, “Defense Transportation
Regulation”.
Mode of Shipment 77 Enter the code identifying the mode of
shipment. 4 (Leave blank when transmitting
DIC AS3 through DAAS to DLA Disposition
Services.)
Port of Embarkation 78-80 a. CONUS. Leave blank.
b. OCONUS:
(1) For shipments moving to OCONUS
designations through the DTS, GBL/CBL,
parcel post (except APO/FPO); and small
package carrier shipments entering the DTS
at the POE, enter the POE or SEAVAN
CCP. (See DTR 4500.9-R, Part II,
Appendices CC, MM, and PP.)
(2) Leave blank for parcel post movement
through an APO or FPO.
(3) Enter the POE for Security Assistance
Program transactions moving through the
DTS; otherwise, leave blank.
4
Refer to the TRDM for available code list at https://trdmws.maf.ustranscom.mil/trdm/index.html
(DTR Data)
5
Procedures requesting and/or providing the DoDAAC of the initial shipping activity last reported as not
implemented by GSA. Refer to AMCL 5.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC ASH.
Routing Identifier Code 4-6 Enter the RIC of the source of supply
generating this transaction. 1
Media and Status 7 Enter the M&S code from the material
release order (MRO).
Stock or Part Number 8-22 Enter the stock or part number from the
MRO.
Unit of Issue 23-24 Enter the U/I from the MRO.
Quantity 25-29 Enter the quantity from the MRO.
Document Number 30-43 Enter the document number as shown in
the MRO.
Suffix 44 Enter the suffix code contained in rp 44 of
the MRO. If the MRO rp 44 is blank, leave
blank.
Supplementary Address 45-50 Enter the SUPADD as shown in the
Address MRO.
Signal 51 Enter the signal code from the MRO.
Fund 52-53 Enter the fund code as shown in the MRO.
Distribution 54-56 Enter the data as shown in the MRO.
Date Shipped 57-59 Enter the date this transaction was
generated.
Blank 60-66 Leave blank.
Routing Identifier Code 67-69 Enter the RIC of the source of supply
(From) generating this transaction.
Blank 70-80 Leave blank.
1
The Defense Automatic Addressing System (DAAS) will overlay transactions containing the DAAS RIC
(SGA) to show the RIC (From) in rp 67-69. (NOTE: This allows DAAS to overlay original entries of the
DAAS RIC so that Component systems may be modified over time.)
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AMF (to change the SUPADD
field) or DIC AMP (to change the required
delivery date (RDD) field to 555).
Routing Identifier Code 4-6 Enter the code of the activity to which the
document is to be transmitted.
Media and Status 7 Enter the M&S code as shown in the
original requisition.
Stock or Part Number 8-22 Enter data as shown in the procurement
instrument or procurement request.
Unit of Issue 23-24 Enter the unit of issue.
Quantity 25-29 a. Enter the quantity.
b. For ammunition and ammunition related
items only (items in Federal supply group
(FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427,
1440, 5330, 5865, 6810 or 8140), enter an
M in rp 29 to express in thousands any
quantity exceeding 99,999. Example:
Express a quantity of 1,950,000 as 1950M
(1950 in rp 25-28 and an M in rp 29).
Document Number 30-43 Enter the requisition document number as
shown in the procurement request.
Suffix 44 Enter the suffix code as shown in the
procurement request; otherwise, leave
blank.
Supplementary Address 45-50 Enter the SUPADD in the DIC AMF;
otherwise, leave blank in the DIC AMP.
Procurement Instrument 51-69 Enter the PIID when available, otherwise
Identifier (PIID) or enter the PRN. Enter the PIID call/order
Procurement Request number (F in 9th position) if applicable.
Number
Procurement Instrument (51-63) Enter the PIID. 1 Enter the PIID call/order
Identifier (PIID) number (F in 9th position) if applicable.
Contract Line Item Number (64-67) Enter the CLIN.
Contract Subline Number (68-69) Enter the contract subline item number, if
applicable.
Procurement Request (51-64) Enter the PRN.
Blank (65-69) Leave blank when a PRN is entered.
Project (70-72) Enter the project code as shown in the
original requisition.
Priority (73-74) Enter the priority designator as shown in the
original requisition.
Procurement Document 75-76 Enter PR in rp 75-76 when the entry in rp
Indicator 51-64 is a PRN; otherwise, leave blank.
Signal 2 77 Enter the signal code in the DIC AMF;
otherwise, leave blank in DIC AMP.
Routing Identifier Code 78-80 Enter RIC to identify the activity preparing
the transaction.
1
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
2
Revised requisition modifier procedures last reported as not implemented by USMC. Refer to AMCL
123C.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC A3_.
Routing Identifier Code 4-6 Enter the RIC of the activity to which the
document is being passed.
All Fields 7-66 Enter data as shown in the requisition.
Date of Receipt of Demand 67-69 Leave blank on submission. Processing
points shall enter date of receipt when
received from another distribution system.
Blank 70-71 Leave blank.
Cooperative Logistics Program 72 Enter data as shown in the requisition, if
Support Code applicable.
Blank 73 Leave blank.
Routing Identifier Code 74-76 Enter the RIC of the activity from which
the document is being passed.
Blank 77-80 Leave blank.
GOVERNMENT-FURNISHED MATERIEL PASSING ORDER ENTRIES. 2
Manufacturer’s Directive 54-56 If required by the Component contracts,
Number enter the MDN.
Call/Order Number 69-72 If required by the Component, enter the
appropriate legacy four-position call/order
number associated with the PIIN;
otherwise leave blank.
Procurement Instrument 73-80 Enter the last eight positions of the PIID.
Identifier (PIID) This entry is mandatory. 3, 4 When
materiel is authorized under a PIID
call/order number (F in 9th position)
provide the last eight positions
1
Entries from the remarks field shall be made only when it is necessary to report that data when
it is entered on the requisition. In all such instances, rp 3 of the DIC shall identify the document
as containing exception data and the passing order shall not be transmitted.
2
Procedures to control access to DoD materiel inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
3
Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 1014.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
MANAGEMENT CONTROL ACTIVITY ENTRIES. Entries Required for passing orders for
Government-Furnished Materiel. 5
Routing Identifier Code 4-6 Enter the RIC of the source of supply.
Distribution 54-56 Enter the distribution code of the
management control activity (MCA)
validating the transaction or the MDN
consisting of the MCA’s distribution code
in rp 54 and two other alpha/numeric
characters in rp 55-56.
Routing Identifier Code 74-76 If required by the Component, enter the
RIC of the validating MCA in rp 74-76.
4
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
5
Procedures to control access to DoD materiel inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC A4_.
Routing Identifier Code 4-6 Enter the RIC of the activity to which the
transaction is being sent.
Media and Status 7 Enter the M&S code as shown in the original
requisition.
Stock or Part Number 8-22 a. When no change or substitution is made,
enter the stock or part number shown in the
requisition.
b. When a change or substitution is made,
enter the corrected stock or substituted stock
or part number.
Unit of Issue 23-24 Enter U/I.
Quantity 25-29 a. Enter the quantity.
b. For ammunition and ammunition related
items only (items in Federal supply group
(FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427, 1440,
5330, 5865, 6810 or 8140), enter an M in rp
29 to express in thousands any quantity
exceeding 99,999. Example: Express a
quantity of 1,950,000 as 1950M (1950 in rp
25-28 and an M in rp 29).
Document Number 30-43 Enter document number as shown in the
requisition.
Suffix 44 a. Enter the suffix code applicable to
quantity in rp 25-29 when the requisitioned
quantity is divided into separate actions.
b. When the requisitioned quantity is not
divided, leave this field blank.
AP8.24-1 APPENDIX.24
DLM 4000.25, Volume 2, November 26, 2019
Change 13
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Supplementary Address 45-50 Enter data from the original requisition. 1
Signal 51 Enter data from the original requisition.
Fund 52-53 Enter data from the original requisition.
Distribution 54-56 When used to effect lateral redistribution of
retail assets, enter 2 for consumables and 3
for reparables in rp 54; otherwise, enter data
from the original requisition.
Project 57-59 Enter data from the original requisition.
Priority 60-61 Enter data from the original requisition.
Required Delivery 62-64 Enter data from the original requisition.
Date/Required Delivery
Period 2
Advice 65-66 Enter data from the original requisition.
Date of Receipt of Demand 67-69 Enter the date of receipt of the demand
document as recorded in that document by
the initial recipient in the supply distribution
system. Note: Referral orders generated as
a result of backorder releases and submitted
to the (Single Manager for Conventional
Ammunition) SMCA shall contain code 888
in rp 67-69.
Management Data 70-71 Enter management data, as authorized.
Demand Code/ 3 72 Enter demand code from rp 44 of original
Management Data 4 requisition or management data, as
authorized. Note: Intra-Air Force Foreign
Military Service (FMS) DIC A4_ transactions
may use a Cooperative Logistics Program
Support Code (CLPSC) (program/non-
program) code in rp 72.
1
When used on a referral order to initiate an inter-Service ammunition-related ownership transfer with no
physical movement of materiel and no billing, cite Signal Code M and Project Code CYK in conjunction
with the supplementary address constructed as follows: Service/Agency Code Y followed by the old
(from) ownership code, the RIC to which ownership is transferred, and the new/gaining (to) ownership
code. Refer to ADC 1020.
2
Use of RDP for conventional ammunition last reported as not implemented by USAF. Refer to AMCL
148.
3
Deferred implementation authorized. The revised format of the referral order to include the demand
code of the original requisition may be deferred for DLMS/logistics systems modernization.
AP8.24-2 APPENDIX.24
DLM 4000.25, Volume 2, November 26, 2019
Change 13
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Management Data 73 Enter Management data, as authorized.
Routing Identifier Code 74-76 Enter RIC applicable to the activity
generating the transaction.
Management Data 77-80 Enter management data, as authorized.
4
On an Intra-Navy basis, a management code may be used to identify the reason a requisition is referred
to the Navy Inventory Control Point (ICP) when the requisition cannot be filled by the referring system.
Refer to ADC 363.
AP8.24-3 APPENDIX.24
DLM 4000.25, Volume 2, November 26, 2019
Change 13
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
GOVERNMENT-FURNISHED MATERIEL REFERRAL ORDER ENTRIES. 5
Manufacturer’s Directive 54-56 If required by the Component contracts,
Number enter the MDN.
Call/Order Number 69-72 If required by the Component, enter the
appropriate legacy four-position call/order
number associated with the PIIN; otherwise
leave blank.
Procurement Instrument 73-80 Enter the last eight positions of the PIID.
Identifier (PIID) This entry is mandatory. 6, 7 When materiel is
authorized under a PIID call/order number (F
in 9th position) provide the last eight positions
MANAGEMENT CONTROL ACTIVITY ENTRIES. Entries Required for referral orders for
Government-Furnished Materiel. 8
Routing Identifier Code 4-6 Enter the RIC of the source of supply.
Distribution 54-56 Enter the distribution code of the
management control activity (MCA)
validating the transaction or the MDN
consisting of the MCA’s distribution code in
rp 54 and two other alpha/numeric
characters in rp 55-56.
Routing Identifier Code 74-76 If required by the Component, enter the RIC
of the validating MCA in rp 74-76.
5
Procedures to control access to DoD materiel inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
6
Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 1014.
7
Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
8
Procedures to control access to DoD materiel inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
AP8.24-4 APPENDIX.24
DLM 4000.25, Volume 2, November 26, 2019
Change 13
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC A2_.
Routing Identifier Code To 4-6 Enter RIC of the source to which the
document is directed.
Media and Status 7 Enter the M&S code.
Stock or Part Number 8-22 Enter the NSN or part number.
Unit of Issue 23-24 Enter the U/I.
Quantity 25-29 a. Enter the quantity.
b. For ammunition and ammunition related
items only (items in Federal supply group
(FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427,
1440, 5330, 5865, 6810 or 8140), enter an
M in rp 29 to express in thousands any
quantity exceeding 99,999.
Example: Express a quantity of 1,950,000
as 1950M (1950 in rp 25-28 and an M in rp
29).
Document Number 30-43 Enter document number assigned by the
preparing activity.
Demand/Suffix 1 44 For intra-DLA, enter suffix code, if
appropriate; all others leave blank.
Supplementary Address 45-50 Enter the SUPADD of the consignee.
Signal 51 Enter the signal code, as appropriate.
Fund 52-53 Enter the fund code, if appropriate.
Distribution 54-56 This field will be blank unless entries are
prescribed by the preparing activity.
Distribution 54-56 This field will be blank unless entries are
prescribed by the preparing activity.
1
Suffix Code authorized for intra-DLA use in support of Industrial Product-Support Vendor (IPV) program.
Refer to ADC 1152.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Project 57-59 Enter the project code, when applicable.
Priority 60-61 Enter the priority designator.
Required Delivery 62-64 Normally left blank. Enter three-position
Date/Required Delivery ordinal day when conditions meet
Period 2 prescribed requirements.
Advice 65-66 Use an advice code to convey instructions
to the supply source. When code is not
required leave blank.
Date of Receipt of Order 67-69 Leave blank on submission. Processing
points will enter date of receipt.
Ownership 70 Enter ownership code, as appropriate.
Supply Condition 71 Enter supply condition code, as
appropriate.
System Management 72-73 Enter system management codes
applicable to this transaction.
Routing Identifier Code 74-76 Enter the RIC of initiating activity.
From
Inventory Control Data 77-80 Enter inventory control codes as
prescribed.
2
Use of Required Delivery Period (RDP) for conventional ammunition last reported as not implemented by
USAF. Refer to AMCL 148.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AN_.
Routing Identifier Code 4-6 Enter RIC (From) of the source of supply
From initiating the request.
Media and Status 7 Grant Aid transaction submitted to security
assistance organization (SAO) by Service;
international logistics control office (ILCO)
may, at Service option, contain a program
originator code. Otherwise, this field shall be
left blank. The program originator code shall
not be perpetuated in DIC AP_ responses
transmitted to inventory control points (ICP).
Stock or Part Number 8-22 Enter stock or part number of the item on
which validation is required. This number
should be in agreement with the number
included in latest status furnished recipient
activities prior to validation requests.
Unit of Issue 23-24 Enter U/I from original requisition.
Quantity 25-29 a. Enter quantity of MOV request, unfilled
quantity of items being validated that is on the
source of supply record.
b. For ammunition and ammunition related
items only (items in Federal supply group
(FSG) 13 and for Federal supply classification
(FSC) 1410, 1420, 1427, 1440, 5330, 5865,
6810 or 8140), enter an M in rp 29 to express
in thousands any quantity exceeding 99,999.
Example: Express a quantity of 1,950,000 as
1950M (1950 in rp 25-28 and an M in rp 29).
Document Number 30-43 Enter document number of original requisition
for item being validated.
Suffix 44 Enter the suffix code assigned to the
document number at time backorder was
established or leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Supplementary Address 45-50 Enter SUPADD from original requisition for
item being validated.
Signal 51 Enter the signal code from original requisition
for item being validated.
Fund 52-53 Enter the fund code from original requisition
for item being validated.
Distribution 54-56 Enter the distribution code from original
requisition for item being validated.
Project 57-59 Enter the project code from original requisition
for item being validated.
Priority 60-61 Enter the priority designator from original
requisition for item being validated.
Estimated Shipping Date 62-64 When ascertainable, enter the numerical day
corresponding to the date that the source of
supply estimates materiel shall be released for
shipment.
Status 65-66 Enter status code to convey the information
regarding the status of the materiel obligation.
Blank 67-70 Leave blank.
Cutoff Day 71-73 Enter ordinal day of the year of the cutoff date
for validation; for example, use 121 for the
April 30th cycle.
Blank 74 Leave blank.
Reply Due Day 75-77 Enter the ordinal day corresponding to the day
on which the supply source must receive a
response.
Blank 78-79 Leave blank.
Multi-Use 80 Reserved for ILCO entry of internal control
data on Grant Aid transactions. Otherwise,
this rp shall be left blank. ILCO code data
shall not be perpetuated in DIC AP_
responses transmitted to ICPs.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AN9 when transmitting request.
Enter DIC ANZ when following up on DIC AN9
request.
Routing Identifier Code 4-6 Enter address of source of supply making the
request. Use as address-to when making
response.
Batch Control No. 7-10 Enter a control number assigned each batch of
DIC AN_ transactions forwarded to a single
activity for validation. Rp 7-8 shall contain the
batch number and rp 9-10 shall contain the
total number of batches being forwarded. For
example, if two batches are sent, the first DIC
AN9 would contain “01" in rp 7-8 and “02" in rp
9-10 (for example, “1" of “2"). The second
DIC AN9 would contain “02" in rp 7-8 and “02"
in rp 9-10.
Number of AN_ 11-13 Enter actual number of DIC AN_ detail
Documents in Batch requests in this batch (under control number in
rp 7-10) from 001 to 493 maximum.
Blank 14-29 Leave blank.
Address (To) 30-35 Enter the Department of Defense activity
address code (DoDAAC) of recipient of
requests. Identifies acknowledging activity in
responses. Enter DoDAAC of rp 54 activity
when recipient of DIC AN_ transactions.
Cutoff Date 36-39 Enter prescribed cutoff date of the validation
cycle. (One position for last digit of calendar
year and three positions for numerical day of
year.)
Blank 40 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Receipt Acknowledgment 41-44 When computer-readable documents are used
Date in responding, enter date documents were
received at responding activity.
Blank 45 Leave blank.
Response Due Date 46-49 Enter prescribed date the DIC AP_ document
is due at the source of supplye. (Year and
ordinal day configured as in rp 36-39 above).
Blank 50-53 Leave blank.
Distribution 54-56 Enter the distribution code when applicable;
otherwise, leave blank.
Blank 57-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AP9 or APX.
Other Fields 4-40 Duplicate from AN9/ANZ received.
Receipt Acknowledgment 41-44 Enter ordinal day DIC AN9/ANZ were received
by validating activity. (Enter one position for
last digit of calendar year and three positions
for numerical day of year.)
Other Fields 45-80 Duplicate from DIC AN9/ANZ received.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AP_.
Routing Identifier Code 4-6 Enter the RIC indicating the source of supply
to which the response is submitted.
Other Fields 7-24 Enter data from the request for which the
response is prepared.
Quantity 25-29 a. Enter quantity still required. If total
cancellation is desired, zero fill this field.
b. For ammunition and ammunition related
items only (items in Federal supply group
(FSG) 13 and for Federal supply classification
(FSC) 1410, 1420, 1427, 1440, 5330, 5865,
6810 or 8140), enter an M in rp 29 to express
in thousands any quantity exceeding 99,999.
Example: Express a quantity of 1,950,000 as
1950M (1950 in rp 25-28 and an M in rp 29).
Other Fields 30-59 Enter data from the request for which the
response is prepared.
Priority 60-61 Enter validated priority designator.
Blank 62-70 Leave blank.
Transaction Day 71-73 Enter ordinal day of year on which the
response is prepared.
Blank 74-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 a. Enter DIC AD1 for the initial key NOA
Code document when an export release is not required.
b. Enter DIC ADR for the initial key NOA
document when an export release is required.
c. Enter DIC AD3 for the delay key NOA
document.
Routing Identifier 4-6 Enter the RIC of the activity transmitting the NOA.
Code
Number of Line Items 7-10 Enter the number of line items included in the
shipment unit as represented by NOA detail
documents transmitted with the NOA key
document.
Commodity/Cargo 11-17 a. Rp 11-15 will always contain the appropriate
Exception/Special water commodity and cargo exception code to be
Handling used to describe the predominant commodity
within the shipment unit for ocean manifesting.
(See DTR 4500.9-R, “Defense Transportation
Regulation”)
b. Rp 16-17 will always contain the appropriate
air commodity and special handling code to be
used for all shipments via air. Identifies materiel
for manifesting and customs requirements and
denotes cargo requiring special handling or
reporting (see DTR 4500.9-R).
Air Dimension 18 Identifies dimensional characteristics of air
shipments by relating the dimensions of the
largest piece to the minimum size cargo door
opening of an aircraft (see DTR 4500.9-R).
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Security Cooperation 19-20 Enter SC Customer Code.
Customer Code
Blank 21-22 Leave blank.
Mode of Shipment 23 Identifies the intended mode to be used from
shipping activity to designated consignee. 1
Type of Pack 24-25 Identifies the type of pack code used for the
shipment unit 2.
Pieces 26-29 Enter total pieces in shipment unit.
Weight 30-35 Enter total weight of shipment unit. This entry will
be rounded to the next whole number.
Cube 36-39 Enter total cubic feet of shipment unit. This entry
will be rounded to the next whole number.
Blank 40-44 Leave blank.
Supplementary 45-50 Enter data same as the issue release/receipt
Address document (MRO, DD Form 1348-1A, DD Form
1348-2, etc).
Blank 51-52 Leave blank.
Transportation Priority 53 See DTR 4500.9-R.
Blank 54-56 Enter data same as the issue release/receipt
document (materiel release order (MRO), DD
Form 1348-1A, DD Form 1348-2, etc).
Project Code 57-59 Enter the same project code as the issue
release/receipt document (MRO, DD Form 1348-
1A, DD Form 1348-2, etc).
Blank 60 Leave blank.
Transportation 61-77 Identifies the number assigned to the shipment
Control Number 3 that controls the shipment from shipper to
consignee. See DLM 4000.25, Chapter 25,
Paragraph C25.11.
1
Refer to the TRDM for available code list at https://trdmws.maf.ustranscom.mil/trdm/index.html (DTR
Data).
2
Ibid.
3
Refer to (ADC) 1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding
DLMS 856N NOA and 870N NOA Reply.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Date of Offer 78-80 a. For DICs AD1, ADR, and AD3 documents,
enter the ordinal day the initial NOA is
transmitted.
b. When new NOAs are prepared, because the
original NOA contained items that were rejected,
the date of offer will be the transmission date of
the NOA.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 a. Enter DIC AD2 for the initial detail NOA
Code document.
b. Enter DIC AD4 for the delay detail NOA
document.
Routing Identifier Code 4-6 Enter the RIC of the activity transmitting the
NOA.
Media and Status 7 Enter the same M&S code as the issue
release/receipt document (MRO, DD Form 1348-
1A, DD Form 1348-2).
Stock or Part Number 8-22 Enter the stock or part number of the item
supplied.
Unit of Issue 23-24 Enter data same as the issue release/receipt
document (MRO, DD Form 1348-1A, DD Form
1348-2).
Quantity 25-29 a. Enter data same as the issue release/receipt
documents (MRO, DD Form 1348-1A, DD Form
1348-2).
b. For ammunition and ammunition related items
only (items in Federal Supply Group (FSG) 13
and for Federal Supply classification (FSC) 1410,
1420, 1427, 1440, 5330, 5865, 6810 or 8140),
enter an “M” in rp 29 to express in thousands any
quantity exceeding 99,999. Example: Express a
quantity of 1,950,000 as 1950M (1950 in rp 25-
28 and an “M” in rp 29).
Document Number 30-43 Enter data same as the issue release/receipt
document (MRO, DD Form 1348-1A, DD Form
1348-2).
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Suffix 44 Enter data same as the issue release/receipt
document (MRO, DD Form 1348-1A, DD Form
1348-2).
Supplementary 45-50 Enter data same as the issue release/receipt
Address document (MRO, DD Form 1348-1A, DD Form
1348-2).
Blank 51-53 Leave blank.
Required Delivery 54-56 Enter data same as the issue release/receipt
Date/Required document (MRO, DD Form 1348-1A, DD Form
Availability Date 1348-2).
Project 57-59 Enter data same as the issue release/receipt
document (MRO, DD Form 1348-1A, DD Form
1348-2).
Blank 60 Leave blank.
Transportation Control 61-77 Enter data same as rp 61-77 of the initial FMS
Number 1 NOA key document.
Date of Offer 78-80 a. For DIC AD2 and DIC AD4 documents, enter
the ordinal day the initial NOA is transmitted.
b. When new NOAs are prepared because the
original NOA contained items that were rejected,
the date of offer shall be the transmission date of
the new NOA.
1
Refer to (ADC) 1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding
DLMS 856N NOA and 870N NOA Reply.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AD5.
Routing Identifier Code through 4-39 Enter data same as rp 4-39 of initial or
Cube delay FMS NOA key document.
Customer Transportation Order 40-44 When customer (CR/FF) assigns a
Number number for internal control of shipments,
the number shall be entered in these
columns.
Other Fields 45-59 Enter data same as rp 45-59 of initial or
delay FMS NOA key document.
Shipment Release 60 Enter codes as follows:
a. Enter R when shipment to be released
to appropriate ship-to address contained
in the MAPAD as identified by address
codes in the FMS requisition.
b. Enter E when release instructions are
being mailed under separate cover on the
date of this reply.
Transportation Control 61-77 Enter data same as rp 61-77 of initial or
Number 1 delay FMS NOA key document.
Date of Reply 78-80 Enter ordinal day reply to NOA is
transmitted.
1
Refer to (ADC) 1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding
DLMS 856N NOA and 870N NOA Reply.
1
Use of part-numbers in the material returns program last reported as not implemented by USMC. Refer
to AMCL 167.
2
Requirement to use a single RIC on customer asset reports directed to the GSA last reported as not
implemented by USA. Refer to AMCL 26.
(MECHANICAL)
(MANUAL) RECORD
FIELD LEGEND BLOCK NO. POSITION(S) ENTRY AND INSTRUCTIONS
Stock or Part Number 8-22 Enter NSN (DIC FTE) or part
number (DIC FTG) 3. (Part-
numbered materiel not
authorized for asset reports
directed to DLA). For
subsistence items only, rp 21
shall be type of pack and rp 22
shall be the last digit of the
calendar year the item, was
packed.
Unit of Issue 23-24 Enter the U/I.
Quantity 25-29 a. Enter the quantity.
b. For ammunition and
ammunition related items only
(items in Federal supply group
(FSG) 13 and for Federal supply
classification (FSC) 1410, 1420,
1427, 1440, 5330, 5865, 6810 or
8140), items only, enter an M in
rp 29 to express in thousands
any quantity exceeding 99,999.
Example: Express a quantity of
1,950,000 as 1950M (1950 in rp
25-28 and an M in rp 29).
Document Number 30-43 Enter the document number.
Blank 44 Leave blank.
Supplementary 45-50 When applicable, enter the
Address activity address code (AAC) of
the credit to and/or ship from
activity. Field may be left blank
when code entry is not
applicable. When code entry is
not significant to the ICP, enter a
Y in rp 45.
Signal 51 Enter the signal code.
3
Use of part-numbers in the material returns program last reported as not implemented by USMC. Refer
to AMCL 167.
(MECHANICAL)
(MANUAL) RECORD
FIELD LEGEND BLOCK NO. POSITION(S) ENTRY AND INSTRUCTIONS
Fund 52-53 Enter the fund code.
Blank 54-56 Leave blank.
Project 57-59 When applicable, enter project
code using Service instructions;
otherwise, leave blank.
Blank 60-64 Leave blank.
Advice 65-66 Enter 3T to indicate to the
ICP/IMM that the document has
been edited by DAAS. When
code is not required, leave blank.
Routing Identifier 67-69 Enter the RIC of the activity
Code preparing the document, if
assigned; otherwise, leave blank.
Blank or Intra-Air 70 Leave blank or use for intra-Air
Force Use Force to display asset position
code.
Supply Condition 71 Enter supply condition code.
Blank 72-80 Leave blank.
Remarks Field L-V Not Applicable This field shall be used to convey
any additionally required
information not provided for in
the report format.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC FTR.
Routing Identifier Code 4-6 Enter the RIC of the inventory control
point (ICP)/integrated material manager
(IMM) furnishing the reply.
Media and Status 7 Enter data as contained in the customer
asset report unless modified by the ICP.
Stock Number 8-22 Enter data as contained in the customer
asset report unless modified by the ICP.
Unit of Issue 23-24 Enter data as contained in the customer
asset report unless modified by the ICP.
Quantity 25-29 a. Enter the quantity.
b. For ammunition and ammunition
related items only (items in Federal
supply group (FSG) 13 and for Federal
supply classification (FSC) 1410, 1420,
1427, 1440, 5330, 5865, 6810 or 8140),
enter an M in rp 29 to express in
thousands any quantity exceeding
99,999. Example: Express a quantity of
1,950,000 as 1950M (1950 in rp 25-28
and an M in rp 29).
Document Number 30-34 Enter data as contained in the customer
asset report (DIC FTE).
Suffix 44 Enter the suffix, when applicable.
Supplementary Address 45-50 Enter data as contained in the customer
asset report (DIC FTE).
Signal 51 Enter data as contained in the customer
asset report (DIC FTE).
Fund 52-53 Enter data as contained in the customer
asset report (DIC FTE).
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Receiving Depot 54-56 Enter the RIC of the receiving activity to
which materiel is directed for return, or
leave blank when no return is directed.
Project 57-59 Enter data as contained in the customer
asset report (DIC FTE).
Priority Designator 60-61 Enter priority designator of the materiel
return as directed by the ICP.
Action Date 62-64 Enter the ordinal day of document
preparation.
Status 65-66 When Status Code SM is entered, rp 70-
73 will contain the date when further
action should be taken.
Routing Identifier Code 67-69 Enter the last known source to which all
future DIC FT_ transactions will be
directed.
Multi-Use 70-73
On SM Status 70-73 On SM status, enter date when further
Date action should be taken by the reporting
activity.
On Other Status
Blank 70 Leave blank.
Supply Condition 71 Enter code from the customer asset
report (DIC FTE).
Demilitarization 72-73 Rp 72 will contain code assigned by the
ICP/IMM as required by DODM 4160.21,
“Defense Materiel Disposition”, when
available. Entry not required on rejected
transactions. Rp 73 is reserved for
reclamation code, special reports, etc.
Unit Price 74-80 Enter the unit price applicable to the
stock number shown in rp 8-22, when
available. Entry not required on rejected
transactions.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC FTQ.
Routing Identifier Code 4-6 Enter the RIC for the DAAS facility.
Media and Status 7 Enter data as contained in DIC FTC, DIC
FTE, or DIC FTF.
Stock Number 8-22 Enter data as contained in DIC FTC, DIC
FTE, or DI FTF.
Unit of Issue 23-24 Enter data as contained in DI FTC, or DI
FTF.
Quantity 25-29 a. Enter the quantity.
b. For ammunition and ammunition
related items only (items in Federal supply
froup (FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427,
1440, 5330, 5865, 6810 or 8140), enter an
“M” in rp 29 to express in thousands any
quantity exceeding 99,999. Example:
Express a quantity of 1,950,000 as
1950M (1950 in rp 25-28 and an “M” in rp
29).
Document Number 30-43 Enter data as contained in DIC FTC, DIC
FTE, or DIC FTF.
Suffix 44 Enter data as contained in DIC FTC, DIC
FTE, or DIC FTF.
Supplementary Address 45-50 Enter data as contained in DIC FTC, DIC
FTE, or DIC FTF.
Signal 51 Enter data as contained in DIC FTC, DIC
FTE, or DIC FTF.
Project 57-59 Enter data as contained in DIC FTC, DIC
FTE, or DIC FTF.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Blank 60-64 Leave blank.
Status 65-66 Enter status code.
Routing Identifier Code 67-69 Enter the RIC of ICP to which all future
DIC FT_ transactions shall be directed.
Blank 70-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC FTD.
Routing Identifier Code 4-6 Enter the RIC of the inventory control
point (ICP)/integrated material manager
(IMM) or Defense Automatic Addressing
System (DAAS) facility furnishing the
status.
Media and Status 7 Enter data as contained in DIC FTE or
DIC FTF.
Stock Number 8-22 Enter data as contained in DIC FTE or
DIC FTF.
Unit of Issue 23-24 Enter data as contained in DIC FTE or
DIC FTF.
Quantity 25-29 a. Enter the quantity.
b. For ammunition and ammunition
related items only (items in Federal supply
group (FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427,
1440, 5330, 5865, 6810 or 8140), enter an
M in rp 29 to express in thousands any
quantity exceeding 99,999. Example:
Express a quantity of 1,950,000 as
1950M (1950 in rp 25-28 and an M in rp
29).
Document Number 30-43 Enter data as contained in DIC FTE or
DIC FTF.
Suffix 44 Enter data as contained in DIC FTE or
DIC FTF.
Supplementary Address 45-50 Enter data as contained in DIC FTE or
DIC FTF.
Signal 51 Enter data as contained in DIC FTE or
DIC FTF.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Fund 52-53 Enter data as contained in DIC FTE or
DIC FTF.
Blank 54-56 Enter data as contained in DIC FTE or
DIC FTF.
Project 57-59 Enter data as contained in DIC FTE or
DIC FTF.
Blank 60-61 Leave blank.
Action Date 62-64 Enter the ordinal day of document
preparation.
Status 65-66 Enter the status code.
Routing Identifier 67-69 Enter data as contained in DIC FTE or
DIC FTF.
Expected Reply Date 70-73 Enter the ordinal day disposition
instructions from the ICP may be
expected.
Blank 74-80 Leave blank.
(MECHANICAL)
(MANUAL) RECORD
FIELD LEGEND BLOCK NO. POSITION(S) ENTRY AND INSTRUCTIONS
Send To A Not Applicable Enter the appropriate in-the-clear
name and address corresponding to
the RIC.
Follow-up is B Not Applicable Enter the appropriate in-the-clear
From name and address of the reporting
activity.
Document 1 1-3 Enter DIC FTF.
Identifier Code
Other Fields 2-23 4-80 Enter data as contained in the
customer asset report (DIC FTE).
Remarks Field L-V Not Applicable This field will be used to convey any
additional required information not
provided for in the follow-up format.
TYPE CANCELLATION
(MECHANICAL)
(MANUAL) RECORD
FIELD LEGEND BLOCK NO. POSITION(S) ENTRY AND INSTRUCTIONS
Send To A Not Applicable Enter the appropriate in-the-clear
name and address
corresponding to the RIC.
Cancellation is From B Not Applicable Enter the appropriate in-the-clear
name and address of the
reporting activity.
Document Identifier 1-3 Enter DIC FTC.
Code
Routing Identifier Code 4-6 Enter data as contained in the
customer asset report (DIC
FTE).
Media and Status 7 Enter data as contained in the
customer asset report (DIC
FTE).
Stock Number 8-22 Enter data as contained in the
customer asset report (DIC
FTE).
Unit of Issue 23-24 Enter data as contained in the
customer asset report (DIC
FTE).
TYPE CANCELLATION
(MECHANICAL)
(MANUAL) RECORD
FIELD LEGEND BLOCK NO. POSITION(S) ENTRY AND INSTRUCTIONS
Quantity 25-29 a. Enter quantity being
canceled.
b. For ammunition and
ammunition related items only
(items in Federal supply group
(FSG) 13 and for Federal supply
classification (FSC) 1410, 1420,
1427, 1440, 5330, 5865, 6810 or
8140), enter an M in rp 29 to
express in thousands any
quantity exceeding 99,999.
Example: Express a quantity of
1,950,000 as 1950M (1950 in rp
25-28 and an M in rp 29).
Other Fields 20-80 1 Enter data as contained in the
customer asset report (DIC
FTE).
Remarks L-V Not Applicable This field shall be used to convey
any additional required
information not provided for in
the cancellation format.
1
Indicate suffix code (rp 44), when applicable, for split actions indicated in DIC FTR.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC FTM.
Routing Identifier Code 4-6 Enter data as contained in the DIC FTR/FTA.
Media and Status 7 Enter data as contained in the DIC FTR/FTA.
Stock Number 8-22 Enter data as contained in the DIC FTR/FTA.
Unit of Issue 23-24 Enter data as contained in the DIC FTR/FTA.
Quantity 25-29 a. Enter quantity released to the carrier for
shipment.
b. For ammunition and ammunition related
items only (items in Federal supply group
(FSG) 13 and for Federal supply classification
(FSC) 1410, 1420, 1427, 1440, 5330, 5865,
6810 or 8140), enter an M in rp 29 to express
in thousands any quantity exceeding 99,999.
Example: Express a quantity of 1,950,000 as
1950M (1950 in rp 25-28 and an M in rp 29).
Document Number 30-43 Enter data as contained in the DIC FTR/FTA.
Suffix 44 Enter data as contained in the DIC FTR/FTA.
Supplementary Address 45-50 Enter data as contained in the DIC FTR/FTA.
Signal 51 Enter data as contained in the DIC FTR/FTA.
Fund 52-53 Enter data as contained in the DIC FTR/FTA.
Routing Identifier 54-56 Enter data as contained in the DIC FTR/FTA.
Release Date 57-59 Enter the date materiel was released to the
carrier.
Transportation Control 60-76 Enter the shipment unit TCN as prescribed in
Number DTR 4500.9-R, “Defense Transportation
Regulation”.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Mode of Shipment 77 Enter the code identifying the mode of
transportation used to move the materiel. 1
Blank 78-80 Leave blank.
1
Refer to the USTRANSCOM Reference Data Management (TRDM) for available code list at
https://trdm.c2.amc.af.mil/trdm/index.jsp (DTR Data).
TYPE STATUS
(MANUAL) (MECHANICAL)
BLOCK RECORD
FIELD LEGEND NO. POSITION(S) ENTRY AND INSTRUCTIONS
Send To A Not Applicable Enter the appropriate in-the-
clear name and address
corresponding to the RIC.
Status is From B Not Applicable Enter the appropriate in-the-
clear name and address of the
reporting activity.
Document Identifier 1-3 Enter DIC FTA.
Code
Routing Identifier Code 4-6 Enter the RIC of the inventory
control point (ICP)/integrated
materiel manager (IMM) to
which the document is directed.
Media and Status 7 Enter the M&S code.
Stock Number 8-22 Enter the stock number.
Unit of Issue 23-24 Enter the U/I.
Quantity 25-29 a. Enter quantity released to
the carrier for shipment.
b. For ammunition and
ammunition related items only
(items in Federal supply group
(FSG) 13 and for Federal
supply classification (FSC)
1410, 1420, 1427, 1440, 5330,
5865, 6810 or 8140), enter an
M in rp 29 to express in
thousands any quantity
exceeding 99,999. Example:
Express a quantity of 1,950,000
as 1950M (1950 in rp 25-28 and
an M in rp 29).
TYPE STATUS
(MANUAL) (MECHANICAL)
BLOCK RECORD
FIELD LEGEND NO. POSITION(S) ENTRY AND INSTRUCTIONS
Document Number 30-43 Enter the document number.
Blank 44 Leave blank.
Supplementary 45-50 When applicable, enter the
Address activity address code (AAC) of
the credit-to and/or ship-from
activity. Field may be left blank
when a code entry is not
applicable. When a code entry
is not significant to the ICP, a Y
shall be entered in rp 45.
Signal 51 Enter the signal code.
Fund 52-53 Enter the fund code.
Routing Identifier Code 54-56 Enter the RIC of receiving
activity to which automatic
shipment is made.
Project 57-59 When applicable, enter
appropriate project code.
Priority Designator 60-61 Enter the priority designator 03
or 06.
Blank 62-66 Leave blank.
Routing Identifier Code 67-69 Enter the RIC of the submitter, if
(From) applicable.
Blank 70 Leave blank.
Supply Condition 71 Enter supply condition code.
Blank 72-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC FT6.
Routing Identifier Code 4-6 Enter data as contained in DIC FTA or
FTR.
Media and Status 7 Enter data as contained in DIC FTA or
DIC FTR.
Stock Number 8-22 Enter data as contained in DIC FTA or
DIC FTR.
Unit of Issue 23-24 Enter data as contained in DIC FTA or
DIC FTR.
Quantity 25-29 Enter quantity from DIC FTA or DIC FTR
or lesser quantity due to cancellation.
Document Number 30-43 Enter data as contained in DICFTA or DIC
FTR.
Suffix 44 Enter data as contained in DIC FTA or
DIC FTR.
Supplementary Address 45-50 Enter data as contained in DIC FTA or
DIC FTR.
Signal 51 Enter data as contained in DIC FTA or
DIC FTR.
Fund 52-53 Enter data as contained in DIC FTA or
DIC FTR.
Routing Identifier Code 54-56 Enter data as contained in DIC FTA or
DIC FTR.
Project 57-59 Enter data as contained in DIC FTA or
DIC FTR.
Priority 60-61 Enter data as contained in DIC FTA or
DIC FTR.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Action Date 62-64 Enter data as contained in DIC FTA or
DIC FTR.
Status 65-66 Enter appropriate status code from
Appendix AP2.16.
Other Fields 67-80 Enter data as contained in DIC FTA or
DIC FTR.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC FTZ.
Routing Identifier Code 4-6 Enter IMM RIC.
Media and Status 7 Enter data as contained in the shipment
status (DIC FTM) or receipt document.
Stock Number 8-22 Enter stock number of materiel received.
Unit of Issue 23-24 Enter UI of materiel received.
Quantity 25-29 a. Quantity of materiel received in a single
materiel condition. Multiple DIC FTZ
documents are provided when a single
shipment is received in more than one
materiel condition.
b. For ammunition and ammunition related
items only (items in Federal supply group
(FSG) 13 and for Federal supply
classification (FSC) 1410, 1420, 1427,
1440, 5330, 5865, 6810 or 8140), enter an
M in rp 29 to express in thousands any
quantity exceeding 99,999. Example:
Express a quantity of 1,950,000 as 1950M
(1950 in rp 25-28 and an M in rp 29).
Document Number 30-43 Perpetuate from DIC FTM.
Suffix 44 Perpetuate from DIC FTM.
Supplementary Address 45-50 Perpetuate from DIC FTM.
Signal 51 Perpetuate from DIC FTM.
Fund 52-53 Enter data as contained in the shipment
status (DIC FTM).
Receiving Depot 54-56 Enter data as contained in the shipment
status (DIC FTM).
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Release Date 57-59 Enter data as contained in the shipment
status (DIC FTM).
Priority Designator 60-61 Enter Data as contained in DIC FTA or DIC
FTR
Materiel Receipt Date 62-64 Enter date materiel received or date credit
authorization canceled.
Status 65-66 Enter status code from Appendix AP2.16 .
Routing Identifier Code 67-69 Enter the RIC of the reporting activity.
Blank 70 Leave blank.
Supply Condition 71 Enter supply condition code indicating
condition of materiel received.
Expected Credit 72-80 Enter credit to be granted in dollars and
cents. When no credit is granted, zero fill.
Expected Credit 80 1 For intra-Army return of reparables only:
To designate To designate
amount of credit amount of credit
granted, enter: reversal, enter:
Code Value Code Value
{ 0 { 0
A 1 J 1
B 2 K 2
C 3 L 3
D 4 M 4
E 5 N 5
F 6 O 6
G 7 P 7
H 8 Q 8
I 9 R 9
1
Refer to ADC 215, Material Receipt Status (material returns program (MRP)) Credit Reversal Amount.
TYPE FOLLOW-UP
(MANUAL) (MECHANICAL)
BLOCK RECORD
NO.
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC AFT.
Code
Routing Identifier Code 4-6 Enter RIC (To), Consignor.
Other Entries 7-80 Duplicate of DIC AS_ or DIC AU_ document
received.
TYPE STATUS
(MANUAL) (MECHANICAL)
BLOCK NO. RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Send To A Not Applicable Enter the appropriate in-the-clear
name and address corresponding
to the routing identifier code (RIC).
Status is From B Not Applicable Enter the appropriate in-the-clear
name and address of the reporting
activity.
Document Identifier 1-3 Enter DIC FTL.
Code
Routing Identifier 4-6 Enter data as contained in DIC
Code FTR.
Media and Status 7 Enter data as contained in DIC
FTR.
Stock Number 8-22 Enter data as contained in DIC
FTR.
Unit of Issue 23-24 Enter data as contained in DIC
FTR.
Quantity 25-29 a. Enter quantity to be shipped.
b. For ammunition and
ammunition related items only
(items in Federal supply group
(FSG) 13 and for Federal supply
cassification (FSC) 1410, 1420,
1427, 1440, 5330, 5865, 6810 or
8140), enter an M in rp 29 to
express in thousands any quantity
exceeding 99,999. Example:
Express a quantity of 1,950,000 as
1950M (1950 in rp 25-28 and an M
in rp 29).
TYPE STATUS
(MANUAL) (MECHANICAL)
BLOCK NO. RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Number 30-43 Enter data as contained in DIC
FTR.
Suffix 44 Enter data as contained in DIC
FTR.
Supplementary 45-50 Enter data as contained in DIC
Address FTR.
Signal 51 Enter data as contained in DIC
FTR.
Fund 52-53 Enter data as contained in DIC
FTR.
Routing Identifier 54-56 Enter data as contained in DIC
Code FTR.
Estimated Shipping 57-59 Enter estimated date of shipment.
Date
Priority 60-61 Enter data as contained in DIC
FTR.
Action Date 62-64 Enter ordinal day of document
preparation.
Blank 65-80 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 1 Perpetuate from requisition or source
document unless otherwise indicated.
Routing Identifier Code 4-6 2 Enter the RIC of the shipping activity.
(From)
Media and Status 7 Enter the M&S code assigned to the
requisition or source document.
Stock or Part Number 8-22 Indicate the NSN or part number being
released. See Block 25.
Unit of Issue 23-24 Indicate the U/I of the NSN or part
number being released.
Quantity 25-29 Indicate the quantity being released.
See Block 26.
Document Number 30-43 Enter the document number of
requisition. See Block 24.
Suffix Code 44 Leave blank if the document represents
release of the total quantity
requisitioned. Indicate the appropriate
suffix code assigned to indicate a partial
quantity release. See Block 24.
Supplementary Address 45-50 3 Perpetuate from the original requisition
or source document. See Block 26.
Signal 51 4 Perpetuate from the original requisition
or source document.
Fund 52-53 5 Perpetuate from the original requisition
or source document.
1
Procedures, formats, and codes for requisitioning material from disposal last reported as not
implemented by DLA. Refer to AMCL 139A.
2
Ibid.
3
Ibid.
4
Ibid.
5
Ibid.
AP8.48-1 APPENDIX8.48
DLM 4000.25, Volume 2, November 26, 2019
Change 13
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Distribution 54-56 6 Perpetuate from the original requisition
or source document.
Project 57-59 7 Perpetuate from the original requisition
or source document.
Priority 60-61 8 Perpetuate from the original requisition
or source document.
Required 62-64 9 Perpetuate from the original requisition
or source document.
Advice 65-66 10 Perpetuate from the original requisition
or source document.
Routing Identifier Code 67-69 11 Perpetuate from the original requisition
or source document.
Management 70-73 Perpetuate from the original requisition
or source document.
Unit Price 12 74-80 Indicate the unit price of item being
released. See Block 26.
6
Ibid.
7
Ibid.
8
Ibid.
9
Ibid.
10
Ibid.
11
Ibid.
12
Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will
reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for
display on the printed form, the generating application may leave blank. Refer to ADC 221.
AP8.48-2 APPENDIX8.48
DLM 4000.25, Volume 2, November 26, 2019
Change 13
BLOCK(S) ENTRIES
1 Total price (10 digits dollars and 2 digits cents). 13
2 Department of Defense Activity Address Code (DoDAAC) of shipping
activity/DLA Disposition Services Field Office. If reduced print in used, in-the-
clear address may be entered in addition to the DoDAAC.
3 DoDAAC of the activity to receive the shipment, if applicable. If reduced print
is used, in-the-clear address may be entered in addition to the DoDAAC.
4 Mark-for Party, if applicable. The mark-for party may be identified by
DoDAAC, RIC, clear text, or a combination of these. Up to 24 characters may
be displayed as two lines of 12 each. The DoDAAC or RIC (when provided)
will appear in the first line and must be separated from clear text with a slash
(/). Reduced print may be used.
5 Document preparation date (enter numerical day of year).
6 National motor freight classification commodity code.
7 Freight rate for the shipment.
8 Type of cargo code (See DTR 4500.9-R “Defense Transportation Regulation)
9 Enter applicable controlled inventory item code (CIIC) that describes the
classified and/or sensitive or pilferage classification of the shipment from DoD
Cataloging Data and Transaction Standards (CDTS), Volume 10, Chapter 3,
Table 61. (Mandatory Entry) 14
10 Actual quantity received.
11 Unit pack of item shipped.
12 Unit weight of item shipped.
13 Unit cube of item shipped.
14 Uniform freight classification (UFC) commodity code.
15 Shelf life of item shipped. Enter SL (for shelf life) followed by applicable shelf-
life code from DoD Cataloging Data and Transaction Standards (CDTS)
Volume 10, Chapter 3, Table 50. (Mandatory Entry) 15
16 Freight classification nomenclature.
17 Item nomenclature.
18 Type of container used for the shipment.
19 Number of containers that make up the shipment.
13
Ibid.
14
Mandatory requirement to enter the controlled inventory item code (CIIC) and shelf-life code on the DD
Form 1348-1A for issues from stock last reported as not implemented by USN. Refer to AMCL 32.
15
Ibid.
AP8.48-3 APPENDIX8.48
DLM 4000.25, Volume 2, November 26, 2019
Change 13
BLOCK(S) ENTRIES
20 Total weight of all containers that make up the shipment.
21 Total cube of all containers that make up the shipment.
22 Received by, signature of receiver, or call sign/code of individual authorized
access to the automated file.
23 Date received, date shipment was received.
24 Document Number - The document number assigned to the requisition. 16
Suffix Code - Blank if the document represents release of the total quantity
requisitioned. If partial shipment, the appropriate suffix code assigned to
indicate partial quantity released.
25 National Stock Number - Enter the stock or part number being released.
Add - For subsistence items, enter the type of pack code in position 21.
FOR OTHER THAN FMS SHIPMENTS
26 Routing Identifier Code - The RIC code of the shipping activity.
Unit of Issue - The unit of issue of the stock or part number being released.
Quantity - The quantity being released.
Condition Code - The supply condition code of materiel being released.
Distribution - Perpetuate from record positions 55 and 56.
Unit Price 17 - The unit price for the NSN/part number being released.
27 This block may contain additional data including bar coding for internal use.
This block may contain a PDF417 2D bar code that contains information for
serially tracked items and repeats bar coded data content. Data entered in
this block is as required by shipping activity by commodity. When data is
entered in this block, it will be clearly identified.
See Appendix 6.35 for Code 39 linear bar code and PDF417 2D bar code
format information. See Appendix 6.36 for the Block 27 continuation page
requirements.
For shipments of GFP, include the GFP contract number (and call order
number when provided). This includes shipments from DOD to contractors
and contractor shipment of GFP to DOD activities. The contract number will
be prefaced by “GFP” to clarify the usage.
16
Prepare data from blocks 24-26 in two configurations: (1) three-of-nine bar code and (2) in-the-clear.
When prepared manually, do not include bar code.
17
Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will
reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for
display on the printed form, the generating application may leave blank. Refer to ADC 221.
AP8.48-4 APPENDIX8.48
DLM 4000.25, Volume 2, November 26, 2019
Change 13
BLOCK(S) ENTRIES
DTID - On issues from DLA Disposition Services Field Office, enter Disposal
Turn-In Document (DTID). 18
18
Procedures, formats, and codes for requisitioning material from disposal last reported as not
implemented by DLA. Refer to AMCL 139A.
19
Refer to ADC 473A
AP8.48-5 APPENDIX8.48
DLM 4000.25, Volume 2, November 26, 2019
Change 13
BLOCK(S) ENTRIES
For IUID to support UIT/serialized item management: 20
Unique Item Identifier (UII) and/or Serial Number
The following additional data elements may be included in support of
IUID:
Manufacturer’s commercial and Government entity (CAGE)
Current Part Number (PN)
Batch/Lot (BT/LT)
Clear text labeling of IUID information must be provided using
the following acronyms: CAGE, P/N, BT/LT, S/N, and UII.
FOR OTHER THAN FMS SHIPMENTS
26 Unit of Issue - two positions - the unit of issue of the stock or part number
being released.
Quantity - five positions - the quantity being released.
Condition - one position - the supply condition code of materiel being
released.
Unit Price 21 - the unit price for the NSN/part number being released.
Supplementary Address - the first position and last three positions of the
supplementary address.
27 This block may contain additional data including bar coding for internal use.
This block may contain a PDF417 2D barcode which contains information for
serially tracked items and repeats bar coded data content. Data entered in
this block is as required by shipping activity by commodity. When data is
entered in this block, it will be clearly identified. See Appendix 6.35 for Code
39 linear bar code and PDF417 2D barcode format information. See
Appendix 6.36 for the Block 27 continuation page requirements.
USML Items – This block will contain clear-text information to identify
shipments of United States Munitions List (USML) items which may require
filing of export licenses and Shipper Export Declarations (SED) per
22CFR126.4 and 22CFR123.22 as follows: “USML item—may need SED.
20
Capability to support IUID data content within the PDF417 2D bar code has been approved for
staggered and phased implementation under ADC 44B and ADC 399/399A. Components have not
reported implementation at this time.
21
Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will
reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for
display on the printed form, the generating application may leave blank. Refer to ADC 221.
AP8.48-6 APPENDIX8.48
DLM 4000.25, Volume 2, November 26, 2019
Change 13
BLOCK(S) ENTRIES
For FMS Repair/Return and Repair/Replace Items – Include the estimated or
actual unit cost for the repair service; perpetuate from the release order when
provided. This block will contain the following statement: “Unit repair value of
$XXXXXXXXX.XX is provided for United States Customs export purposes. 22
For IUID to support UIT/serialized item management: 23
Unique Item Identifier (UII) and/or Serial Number (S/N)
The following additional data elements may be included in support of IUID:
Manufacturer’s CAGE
Current Part Number
Batch/Lot
Clear text labeling of IUID information must be provided using the following
acronyms: CAGE, P/N, BT/LT, S/N, and UII.
22
Refer to ADC 1031.
23
Ibid.
AP8.48-7 APPENDIX8.48
DLM 4000.25, Volume 2, November 26, 2019
Change 13
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Perpetuate from the source document. For
locally determined excesses generated at a
base, post, camp, or station, assign a DIC as
determined by Service/Agency (S/A)
procedures.
Routing Identifier Code 4-6 Enter the RIC of the shipping activity or leave
blank when the shipping activity is not
assigned an RIC.
Media and Status 7 Leave blank.
Stock or Part Number 8-22 Enter the stock or part number being turned
in. For subsistence items, enter the type of
pack in rp 21. See Block 25.
Unit of Issue 23-24 Enter the unit of issue of the stock or part
number being turned in.
Quantity 25-29 Enter the quantity being turned in to DLA
Disposition Services Field Office.
Document Number 30-43 Perpetuate from source document. This
cannot be the same document number that
was used to receive the materiel. For locally
determined excess generated at base, post,
camp, or station, assign as determined by S/A
procedures. See Block 24.
Suffix 44 Leave blank.
Supplementary Address 45-50 Enter DoDAAC of predesignated consignee
DLA Disposition Services Field Office .
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Signal 51 For hazardous materiel and waste turn-ins,
enter the applicable signal code; otherwise,
leave blank. Signal Codes A, B, C, and L are
authorized; if using Signal Code B, bill-to
office must be identified in block 27. Refer to
Appendix AP7.10, Signal Codes, for bill-to
identification rules associated with disposal
turn-in document (DTID).
Fund 52-53 For Hazardous materiel and waste turn-ins,
enter the bill to fund code for reimbursable
actions associated with disposal.
Distribution 54 Perpetuate from source document or leave
blank.
Retention Quantity 55-61 Enter the quantity to be retained in inventory
or leave blank.
Precious Metals 62 Enter applicable precious metals code from
appendix AP7.23.
Automated Data 63 Enter applicable ADPE code from appendix
Processing Equipment AP7.24.
Identification
Disposal Authority 64 Enter applicable disposal authority code from
Appendix AP7.21.
Demilitarization 65 Enter code assigned as required by DoD
4160.21-. Note: When demilitarization has
been accomplished prior to transfer to DLA
Dispostion Services Field Office, the
appropriate demilitarization certification, as
required by DoD 4160.21 , must be reflected
in Block 27.
Reclamation 66 Enter Y if reclamation was performed prior to
release to a DLA Disposition Services Field
Office. Enter R if reclamation is to be
performed after turn-in to DLA Disposition
Services Field Office. Enter N if reclamation
is not required.
Routing Identifier Code 67-69 Perpetuate from disposal release order
(DRO).
Ownership 70 Enter applicable ownership code or leave
blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Supply Condition 71 Enter the applicable MILSTRAP supply
condition code.
Management 72 Perpetuate from source document or leave
blank.
Flight Safety Critical 73 1 Enter Criticality Code E to indicate Nuclear
Aircraft Parts Hardened Flight Safety Critical Aircraft Parts
(FSCAP) or Criticality Code F to indicate a
standard FSCAP.
Unit Price 74-80 Enter the unit price for the NSN or part
number in rp 8-22 2.
BLOCK(S) ENTRIES
1 Enter the extended value of the transaction 3.
2 Enter the shipping point by Department of Defense activity address code
(DoDAAC); if reduced printing is used, in-the-clear address may be
entered in addition to the DoDAAC.
3 Enter the consignee DLA Disposition Services Field Office by DoDAAC.
This will be the predesignated DLA Disposition Field Office and will be
entered by the shipping activity; if reduced printing is used, the in-the-clear
address may be entered in addition to the DoDAAC.
4 Insert HM, if the turn-in is hazardous materiel or HW, if the turn-in is
hazardous waste.
5 Enter the date of document preparation, if required by the shipper.
6 Enter the national motor freight classification (NMFC), if required by the
shipper.
7 Enter the freight rate, if required by the shipper.
8 Enter coded cargo data, if required by the shipper.
9 Enter applicable controlled inventory item code which describes the
security/pilferage classification of the shipment from DoDM Cataloging
Data and Transaction Standards (CDTS), Volume 10, Chapter 3, Table
61.
1
Identification of of FSCAP codes on the DTID and disposal release transactions last reported as not
implemented by USA and USN. Refer to Approved DLSS/DLMS Change 6.
2
Unit prices obtained via electronic interfaces which are not constrained by the MILSTRIP field size will
reflect the unit price as 9 digits for dollars and 2 digits for cents. If total price exceeds available space for
display on the printed form, the generating application may leave blank. Refer to ADC 221A.
3
If total price exceeds available space for display on the printed form, the generating application may
leave blank. Refer to ADC 221.
BLOCK(S) ENTRIES
10 Enter the quantity actually received by the DLA Disposition Field Office, if
different from positions 25-29.
11 Enter the number of units of issue in a package, if required by the shipper.
12 Enter the unit weight applicable to the unit of issue, if required by the
shipper.
13 Enter the unit cube applicable to the unit of issue, if required by the
shipper.
14 Enter the uniform freight classification, if required by the shipper.
15 Enter the shelf life, if appropriate; otherwise, leave blank.
16 Enter in-the-clear freight classification nomenclature, if required by the
shipper.
17 Enter the item nomenclature. For non-NSN items; enter as much
descriptive information as possible. Specified additive data or certification
from the generating source for specific types of property should be
entered.
18 Enter type of container, if required by the shipper.
19 Enter number of containers that makes up the shipment, if required by the
shipper.
20 Enter total weight of shipment, if required by the shipper.
21 Enter total cube of shipment, if required by the shipper.
22 Received By - Enter the signature of person receiving the materiel.
23 Date Received - Enter date materiel was received and signed for.
24 Document Number - Perpetuate from source document. This cannot be
the same document number that was used to receive the materiel. For
locally determined excesses generated at base, post, camp, or station,
assign a document number as determined by Service/Agency procedures.
Suffix Code - Leave blank. 4
25 National Stock Number - Enter the stock number or part number being
turned in.
Additional - For subsistence items, enter the type of pack code rp 21.
26 For turn-in to DLA Disposition Services Field Office - This block will not
contain bar code data, it is reserved for internal DLA Disposition Services
Field Office use.
4
Data from blocks 24-25 will be displayed in two configurations; (1) three-of-nine bar code and (2) in-
the-clear. When prepared manually, bar code will not be included.
BLOCK(S) ENTRIES
27 This block may contain additional data including bar coding for internal
use. This block may contain a PDF417 2D bar code that contains
information for serially tracked items and repeats bar coded data content.
Enter data in this block as required by the shipping activity or the DLA
Disposition Services receiving the materiel. When data is entered in the
block, it will be clearly identified. See Appendix 6.35 for Code 39 linear
bar code and PDF417 2D bar code format information. See Appendix 6
.36 for the Block 27 continuation page requirements.
HM/HW Turn-Ins – For hazardous materiel and waste turn-ins, enter the
DoDAAC of the bill-to office (required for Signal Code B), the contract line
item number (CLIN) for the item on the disposal contract, the total cost of
the disposal, Hazardous Waste Profile Sheet Reference Number, the
Material Safety Data Sheet 5-digit alpha code from the Hazardous Material
Information Repository System, the Chemical Name of Hazardous
Contaminant(s), and the Noun Name of Non-Hazardous Contaminant(s).
FSCAP Items –This block will contain both coding and clear-text
information to identify Flight Safety Critical Aircraft Parts (FSCAP)
shipments to DLA Disposition Services Field Offices using Criticality Code
E or F as follows: FSCAP E - Flight Safety Critical Aircraft Part-Nuclear
Hardened or FSCAP F – Standard Flight Safety Critical Aircraft Part. 5
Scrap Reimbursement – This block will contain the fund citation for
reimbursement of scrap proceeds minus Disposition processing costs.
For IUID to support UIT/serialized item management 6
Unique Item Identifier (UII) and/or Serial Number
The following additional data elements may be included in support of IUID:
Manufacturer’s CAGE
Current Part Number
Batch/Lot
Clear text labeling of IUID information must be provided using the
following acronyms: CAGE, P/N, BT/LT, S/N, and UII.
Small Arms/Light Weapons (SA/LW) Turn-In 7 – Ship serialized weapons
and serialized weapon parts to the Anniston, Alabama, DEMIL Center. Do
not mix partial and complete weapons on a single IRRD. For
partial/incomplete weapon turn-in, identify missing parts in this block. If
there is insufficient space, use an attached continuation page (refer to
5
Identification of of FSCAP codes on the DTID and disposal release transactions last reported as not
implemented by USA and USN. Refer to Approved DLSS/DLMS Change 6,
6
Capability to support IUID data content within the PDF417 2D bar code has been approved for
staggered and phased implementation under ADC44B and ADC 399/399A. Components have not
reported implementation at this time.
7
Refer to ADC 1175 and https://www.dla.mil/DispositionServices/.
BLOCK(S) ENTRIES
Appendix 1.36). If the shipment includes multiple weapons, associate
each list of missing parts with the serial number of the whole weapon. In
lieu of listing the missing parts, the owning Component may authorize
including aa signed statement certifying that the weapons have missing
parts. Provide the name and contact information of the authorizing official.
If prepared electronically, provide a digital signature.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Leave blank.
Routing Identifier Code 4-6 Leave blank.
From
Media and Status 7 Leave blank.
Stock Number 8-22 Enter the stock or part number of the item
authorized to be returned.
Unit of Issue 23-34 Enter the UI.
Quantity 25-29 Enter the quantity authorized to be
returned.
Document Number 30-43 Enter the requisitioner’s document number
from block 8, SF 364.
Suffix 44 Leave blank.
Supplementary Address 45-50 Leave blank.
Signal 51 Leave blank.
Fund 52-53 Leave blank.
Distribution 54-56 Leave blank.
Project 57-59 Leave blank.
Priority 60-61 Leave blank.
Required Delivery Date 62-64 Leave blank.
Advice 65-66 Leave blank.
Routing Identifier Code 67-69 Enter the RIC of U.S. source of supply
preparing the DD Form 1348-1A or DD
Form 1348-2.
Blank 70-73 Leave blank.
Unit price 74-80 Enter the unit price for the NSN or part
number shown in rp 8-22. (This should be
the same price as used on the issue
document.)
BLOCK(S) ENTRIES
A Leave blank.
B The consignee by account number, name, and address.
C-D Enter words “Transshipment point” and account number, name,
and address of activity designated to receive the transshipped
materiel. If not designated, leave blank.
E The extended value of the transaction.
F-N Leave blank.
O Date of document preparation.
P Supply condition of the materiel authorized for return.
Q-Y Leave blank.
1-10 Leave blank.
AA-BB Enter the “SDR number” from Block 2, SF 364.
CC-GG Leave blank.
11-12 Leave blank.
13 Transportation fund cite applicable to the shipment.
14-15 Leave blank.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC APR.
Code
Routing Identifier Code 4-6 Enter the RIC of the source of supply that
canceled the requisition.
Other Fields 7-24 Enter the data from the supply status
transaction (DIC AE_) with Status Code BS.
Quantity 25-29 Enter the quantity required; this quantity
cannot be greater than the original quantity
canceled
Other Fields 30-61 Enter the data from supply status
transaction (DIC AE_) with Status Code BS.
Blank 62-64 Leave blank.
Advice Code 65-66 Enter the advice code from the original
requisition; otherwise, leave blank.
Blank 67-70 Leave blank.
Transaction Day 71-73 Enter the ordinal day of year of the
reinstatement request.
Blank 74-80 Leave blank.
1
Established procedures to reinstate canceled requisitions last reported as not implemented by United
States Navy (USN). Refer to AMCL 150C.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier Code 1-3 Enter DIC AX1.
Routing Identifier Code 4-6 Enter the RIC identifying the
(From) inventory control point (ICP)
creating the DIC AX1
transaction.
Media and Status 7 Perpetuate from the requisition.
Stock Number 8-22 Perpetuate from the requisition.
Unit of Issue 23-24 Perpetuate from the requisition.
Quantity 25-29 Perpetuate from the requisition.
Document Number 30-43 Perpetuate from the requisition.
If perpetuating from a referral
order, use suffix code.
Demand/Suffix Code 44 Perpetuate from the requisition.
Supplementary Address 45-50 Perpetuate from the requisition.
Signal 51 Perpetuate from the requisition.
Fund Code 52-53 Perpetuate from the requisition.
Distribution 54 Perpetuate from the requisition.
Project Code 57-59 Perpetuate from the requisition.
Priority Designator 60-61 Perpetuate from the requisition.
Supply Source Origination 62-64 Enter the date the DIC AX1 was
Date created.
Advice 65-66 Perpetuate from the requisition.
Blank 67-68 Leave blank.
1
Procedures to control access to DoD material inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Call Number 69-72 Perpetuate from the requisition.
Contract Identification 73-80 Perpetuate from the requisition.
OR
Management Control 74-76 Perpetuate from the requisition.
Activity Routing Identifier
Code
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC AX2.
Code
Routing Identifier Code 4-6 Perpetuate from the DIC AX1 transaction.
(To)
Media and Status 7 Perpetuate from the DIC AX1 transaction.
Stock Number 8-22 Perpetuate from the DIC AX1 transaction.
Unit of Issue 23-24 Perpetuate from the DIC AX1 transaction.
Quantity 25-29 If Advice Code 2R is entered in rp 65-66,
enter quantity to be supplied. If Advice
Code 2Q is entered in rp 65-66, enter
total quantity to be rejected.
Document Number 30-43 Perpetuate from the DIC AX1 transaction.
Demand 44 Perpetuate from the DIC AX1 transaction.
Supplementary Address 45-50 Perpetuate from the DIC AX1 transaction.
Signal 51 Perpetuate from the DIC AX1 transaction.
Fund Code 52-53 Perpetuate from the DIC AX1 transaction.
Distribution 54-56 Perpetuate from the DIC AX1 transaction.
Project Code 57-59 Perpetuate from the DIC AX1 transaction.
Priority 60-61 Perpetuate from the DIC AX1 transaction.
Validation Date 62-64 Enter date validated or rejected by the
MCA.
Advice or Status 65-66 Enter the applicable advice code from
Appendix AP7.15 or status code from
Appendix AP7.16 .
Blank 67-68 Perpetuate from the DIC AX1 transaction.
1
Procedures to control access to DoD materiel inventories by defense contractors last reported as not
implemented by USA (Retail). Refer to AMCL 1A.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Call Number 69-72 Perpetuate from the DIC AX1 transaction.
Contract Identification 73-80 Perpetuate from the DIC AX1 transaction.
OR
Management Control 74-76 Perpetuate from the DIC AX1 transaction.
Activity Routing
Identifier Code
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC AP8.
Code
Routing Identifier Code 4-6 Enter RIC SGA.
Submitting Activity 7-12 Enter Department of Defense
activity address code (DoDAAC)
of applicable activity.
Blank 13-80 Leave blank.
1
Use of revised Materiel Obligation Validation (MOV) temporary suspension procedures for selected
activities last reported as not implemented by USMC. Refer to AMCL 37.
RECORD
FIELD LEGEND POSITION(S) ENTRY AND INSTRUCTIONS
Document Identifier 1-3 Enter DIC AV_.
Code
Routing Identifier Code 4-6 Enter RIC of supply source
initiating the request.
Media and Status 7 Enter the program originator
code; otherwise, leave blank.
This code may be entered by the
international logistics control
office (ILCO), at Service option,
on Service initiated foreign
military service (FMS) and grant
aid transactions to security
assistance organizations (SAO).
Stock or Part Number 8-22 Enter the stock or part number of
item on which validation is
required. This number should be
in agreement with the number
included in the latest status
transaction furnished to the
recipient activities prior to the
notification request.
Unit of Issue 23-24 Enter data from original
requisition.
1
Refer to ADC 1181A.
2
Refer to ADC 1181B.
3
Refer to ADC 1161A, Update Uniform Procurement Instrument Identifier (PIID) Numbering System.
Note: If only the PIID call/order number is available, it will be provided in this data field.
4
Populated by the shipper field in WebSDR.
5
Refer to ADC 1181B.
6
Refer to ADC 1161A, Update Uniform PIID Numbering System. The call/order number will only be
provided as a discrete data field when populated with the legacy four-position data element. Otherwise,
the PIID call/order number will be reflected in the PIID data field.
AP9. APPENDIX 9
GENERATOR COMMUNICATIONS INTERFACE
STANDARD 5.0.0
AP9.1 General.
AP9.1.2. GenComm allows for the electronic transfer of the Waste Profile Sheet
(WPS, DRMS 1930 and the Disposal Turn-In Document (DTID, DD1348-1A) data.
AP9.2. Procedure.
AP9.2.1. The generator uses their system to create either an ASCII or an XML file.
AP9.2.2. The generator transfers their file to the GenComm server by using one of
the following methods:
AP9.2.3. Generator checks the GenComm Log file to check for problems or
errors. The log file lists the WPS numbers and DTID numbers, which processed. Items
rejected show the WPS/DTID number and a reason for the reject. Items rejected need
to be resubmitted in a new file, with a different name. Note: the individual records
reject – not the entire file.
AP9.2.4. To receive the GenComm Log file submit the following via e-mail:
AP9.2.4.1. DoDAAC
AP9-1 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
AP9.2.4.3. To: mailto:[email protected]
AP9.3. File Format for Generator Communications (Version 5.0.0 – 04/17/08). The
basic structure for communicating this data is to use sections and subsections in a text
file. The record format for each text line is determined by a combination of its sequence
in the outline and its first field.
AP9.3.1. Structure.
• File Header
• WPS Section, if any
• DTID Section, if any
• WPS Record
• Chemical Composition Subsection, if any
• EPA Waste Number Subsection, if any.
AP9-2 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
• DTID Record
• DTID Container Subsection, if any
• DTID EPA Waste Code Subsection, if any
• DTID State Waste Code Subsection, if any
AP9.3.2. Fields are restricted to a maximum of the length indicated, unless noted
as variable (V).
AP9.3.3. Fields will be delimited by the pipe symbol (“|”) in the bar delimited files.
However, there will not be a trailing pipe (“|”).
AP9.3.4. Records will be delimited by the carriage return <CR>, technically stored
as the carriage return line feed (LF) combination. This will be represented as End of
Record Indicator in the record formats.
AP9.3.5.2. Terminate the section or subsection with its trailer and start a new
section or subsection.
AP9.3.5.3. Terminate the section or subsection with its trailer and quit (End
of file).
• Mandatory (M)
• Optional (O)
AP9-3 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
• Alpha (A)
• Numeric (N)
• Alpha/Numeric (A/N)
AP9.4.1. File Header Format. The header record will be followed by one or two
sections: Waste Profile Sheet (WPS) Section or Disposal Turn In Document (DTID)
Section. Each section can contain one or more records. A section must have a section
header and a section trailer. Permissible combinations are: File Header (FH) and WPS
and DTID Sections (in that order), FH and WPS Section only, or FH and DTID section
only. Note: The Routing Identifier Code (RIC) SFX must be coordinated with your
environmental contact to ensure proper routing.
Min
A, N or Field Field
M/ O Field Name A/N Length Length Example, Format or Style
Generator’s File
M A/N 6 6 The Generator DoDAAC i.e. FB2020
Transfer DoDAAC
Transaction Julian date the file was created i.e.
M N 7 7
Date 1994332
Transaction
M N 4 4 In the format HHMM
Time
DLA Disposition
M Services Site ID A/N 4 3 DLA Disposition Services Site ID
(RCCC)
Generator’s
Generator Software Release Version
O Software Release A/N 50 1
Number
Version Number
End of Record
M
Indicator
Min
A, N or Field Field
M/ O Field Name A/N Length Length Example, Format or Style
M WPS Section Header A/N 12 12 A constant of “beg_wps_sect”
End of Record
M
Indicator
AP9-4 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
A, N Min DRMS 1930
or Field Field Example, Format or Block # Correlating Data
M/O Field Name A/N Length Length Style Elements
M Waste Profile Number A/N 20 5 Part 1 – A
M Generator Name A/N 30 2 Part 1 – A-1
M Facility Address Line 1 A/N 30 3 Part 1 – A-2
O Facility Address Line 2 A/N 30 0 Part 1 – A-2
M Facility Address Line 3 A/N 30 2 City & State Part 1 – A-2
M Facility ZIP Code A/N 10 5 NNNNN-NNNN Part 1 – A-3
O Generator USEPA ID A/N 13 0 Part 1 – A-4
O Generator State ID A/N 13 0 Part 1 – A-5
M Technical Contact Name A/N 30 2 Part 1 – A-6
O Technical Contact Title A/N 30 0 Part 1 – A-7
XXX(NNN)NNN-
M Technical Contact Phone A/N 21 4 Part 1 – A-8
NNNNxNNNN
Waste Profile Established
O N 7 0 Julian YYYYDDD
Date
O Name of Waste A/N 60 0 Part 1 – B-1
O Process Generating Waste A/N 60 0 Part 1 – B-3
NNNNNNNNNN.NNN
O Projected Annual Volumes N 10.4 0 Part 1– B-3
N
O Projected Annual Units A 10 0 Part 1 – B-4
O Mode of Collection A 15 0 Part 1 – B-5
O Dioxin Waste A 1 0 Y/N Part 1 – B-6
Land Disposal Restrictions
O A 1 0 Y/N Part 1 – B-7-A
Indicator
Exemption Granted
O A 1 0 Y/N Part 1 – B-7-B
Indicator
Meets Treatment
O A 1 0 Y/N Part 1 – B-7-C
Standards Indicator
Treatment Standard
O A/N 30 0 Part 1 – B-7-C
Reference
O Color A 30 0 Part 2 – 1-1
O Density A/N 15 0 Part 2 – 1-2
O BTU/LB A/N 15 0 Part 2 – 1-3
O Total Solids A/N 15 0 Part 2 – 1-5
O Ash Content A/N 15 0 Part 2 – 1-4
AP9-5 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
A, N Min DRMS 1930
or Field Field Example, Format or Block # Correlating Data
M/O Field Name A/N Length Length Style Elements
MULTILAYERED,
O Layering A 12 0 BILAYERED, Part 2 – 1-6
SINGLE PHASE
S = SOLID,
L = LIQUID,
O Physical State A 10 0 SS = SEMISOLID, Part 2 – 2
G = GAS,
O = OTHER
W=Wastewater,
O Treatment Group A 1 0
N = Nonwastewater
O Ignitable Indicator A 1 0 Y/N Part 2 – 2
Flash Point (Degrees
O A/N 9 0 Part 2 – 2
Fahrenheit)
High TOC (> 10 %)
O A 1 0 Y/N Part 2 – 2
Indicator
Low TOC (< 10 %)
O A 1 0 Y/N Part 2 – 2
Indicator
O Reactive Indicator A 1 0 Y/N Part 2 – 2
O Water Reactive Indicator A 1 0 Y/N Part 2 – 2
Cyanide Reactive
O A 1 0 Y/N Part 2 – 2
Indicator
O Sulfide Reactive Indicator A 1 0 Y/N Part 2 – 2
O Corrosive Indicator A 1 0 Y/N Part 2 – 2
O Ph A/N 8 0 Example: >= 12.5
Toxicity Characteristic
O A 1 0 Y/N Part 2 – 2
Indicator
O Corrodes Steel Indicator A 1 0 Y/N
O Copper Quantity N 20 0
O Copper Units A/N 5 0
O Phenolics Quantity N 20 0
O Phenolics Units A/N 5 0
O Nickel Quantity N 20 0
O Nickel Units A/N 5 0
O Total Halogens Quantity N 20 0
O Halogens Units A/N 5 0
O Zinc Quantity N 20 0
O Zinc Units A/N 5 0
AP9-6 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
A, N Min DRMS 1930
or Field Field Example, Format or Block # Correlating Data
M/O Field Name A/N Length Length Style Elements
O Volatile Organics Qty N 20 0
O Volatile Organics Units A/N 5 0
O Chromium Hex Quantity N 20 0
O Chromium Units A/N 5 0
O PCB Quantity N 20 0
O PCB Units A/N 5 0
Other Chemical
O A/N 30 0
Component Description
Other Chemical
O N 20 0
Component Quantity
Other Chemical
O A/N 5 0
Component Units
O Dot Hazardous Material A 1 0 Y/N Part 2-4
O Proper Shipping Name A/N 200 0 Part 2-4
O Hazard Class A/N 18 0 Part 2-4
O UN or NA Number A/N 6 0 Part 2-4
O Additional Description A/N 60 0 Part 2-4
BULK, DRUM or
O Packing Type A/N 30 0 Part 2-4
OTHER (Describe)
O DoT Reportable Quantity N 5 0 Part 2-4
O DoT Unit of Issue A/N 5 0
O Packing Group A 3 0 Part 2-4
Emergency Response
O N 4 0 Part 2-4
Guide Page Number
O Edition (YR) N 4 0
Special Handling
O A/N 90 0 Part 2-5
Information
USER for user
knowledge
O Basis For Information A 4 0 Part 2-6
LAB for chemical
analysis
O RCRA Requirements A/N 255 0
Additional RCRA
O A/N 255 0 Part 2-6
Requirements
O Certifier Name A 45 0 Part 2-6
M End of Record Indicator
AP9-7 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
AP9.4.4. Chemical Composition Header Format.
Min
A, N Field
M/O Field Name Field Example, Format or Style
or A/N Length
Length
Composition
M A/N 13 13 A constant of “end_comp_sect”
Subsection Trailer
M End of Record Indicator
Min
A, N Field Field
M/O Field Name or A/N Length Length Example, Format or Style
EPA Waste No
M A/N 12 12 A constant of “beg_ewn_sect”
Subsect Header
AP9-8 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
End of Record
M
Indicator
A, N Min
or Field Field
M/O Field Name A/N Length Length Example, Format or Style
M EPA HW Number A/N 4 4 EPA HW Number i.e. D001
M EPA Units A/N 5 2
M End of Record Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
EPA Waste No
M A/N 12 12 A constant of “end_ewn_sect”
Subsection Trailer
End of Record
M
Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
M WPS Section Trailer A/N 12 12 A constant of "end_wps_sect"
End of Record
M
Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
M DTID Section Header A/N 12 12 A constant of "beg_dtid_sect"
End of Record
M
Indicator
AP9-9 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
AP9.4.12. DTID Record Format.
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
M Federal Supply Class N 4 4
NIIN/Local Stock
M A/N 9 9
Number
O Additional Data A/N 2 0
M Document Number A/N 15 14 Disposal Turn In Document Number
M Unit of Issue A 2 2
M Issued Quantity N 7 1
Disposal Authority M=Approved, N=Not Reqd.,
O A 1 0
Code R=Auth. Received
“W” for hazardous and non-regulated
waste, “M” for hazardous material, and
Hazardous “N” for usable property, “P” for
M A 1 1
Waste/Material Code Special Services request, and “S” for
scrap property turn-ins to DLA
Disposition Services Field Office
M Issue Unit Price N 5.2 1 NNNNN.NN (Acquisition Unit Price)
M Item Nomenclature A/N 60 2
Supply Condition
M A 1 1
Code
Demilitarization
M A 1 1
Code
Accumulation Start
O N 7 0 Julian Date i.e. 1994320
Date
Waste Profile Sheet
O A/N 20 5
Number
O MSDS Number A/N 15 0
Only used for property received at the
Receipt Manifest DLA Disposition Services Field Office
O A/N 17 0
Number from an off-site facility. Put in the 12
digit EPA Manifest Number.
O Type of Container A/N 60 0
Disposal Total
O N 6 0
Weight/Volume
P= Pounds, T= Short Tons (2000 LB),
Disposal Total G= Gallons, Y= Cubic Yards,
O A 1 0
Weight/Volume Unit K= Kilograms, M= Tonnes (1000KG),
L= Litres, C= Cubic Meters
O Organization Code A/N 6 0
AP9-10 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
O Building A/N 6 0
i.e. Motor Pool, Spill Residue,
O Type Operation A/N 60 0
Degreasing etc.
M Contact Name A 18 4
M Contact Phone A/N 21 4
Waste Description
O A/N 60 0
Line 1
Waste Description
O A/N 60 0
Line 2
Waste Description
O A/N 60 0
Line 3
Waste Description
O A/N 60 0
Line 4
O Contract Number A/N 13 0
O HIN A/N 6 6
M Total Disposal Cost N2 5.2 4 NNNNN.NN
M Fund Code A/N 2 2
O Bill to DoDAAC A/N 6 0
O Pickup DoDAAC A/N 6 0
Number of
O N 4 0 Count of containers in DTID
Containers
End of Record
M
Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
Container Subsection
M A/N 13 13 A constant of "beg_cont_sect"
Header
End of Record
M
Indicator
AP9-11 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
M Document Number A/N 15 1 Disposal Turn In Document Number
M Container Number A/N 15 1 Alias "Drum Number"
Storage Location
O A/N 16 0 Location within the building
Code
Container
O N 6 0
Weight/Volume
Accumulation Start
O N 7 0 Julian Date i.e. 1994320
Date
End of Record
M
Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
Container Subsection
M A/N 13 13 A constant of "end_cont_sect"
Trailer
End of Record
M
Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
EPA Waste Code
M A/N 16 16 A constant of "beg_dtidepa_sect"
Subsection Header
End of Record
M
Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
M Document Number A/N 15 14 Disposal Turn In Document Number
DTID EPA Waste
M A/N 4 4 EPA waste code for DTID
Codes
AP9-12 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
End of Record
M
Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
EPA Waste Code
M A/N 16 16 A constant of "end_dtidepa_sect"
Subsection Trailer
End of Record
M
Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
State Waste Code
M A/N 16 16 A constant of "beg_dtidsta_sect"
Subsection Header
M End of Record
Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
M Document Number A/N 15 14 Disposal Turn In Document Number
DTID State Waste
M A/N 10 4 State waste code for DTID
Codes
End of Record
M
Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
State Waste Code
M Subsection Trailer A/N 16 16 A constant of "end_dtidsta_sect"
AP9-13 APPENDIX 9
DLM 4000.25, Volume 2, April 29, 2016
Change 7
End of Record
M Indicator
Min
A, N or Field Field
M/O Field Name A/N Length Length Example, Format or Style
M DTID Section Trailer A/N 13 13 A constant of "end_dtid_sect"
End of Record
M
Indicator
AP9-14 APPENDIX 9
DLM 4000.25, Volume 2, October 23, 2015
Change 6
AP10. APPENDIX 10
RESERVED
AP10-1 APPENDIX 10
DLM 4000.25, Volume 2, June 16, 2015
Change 5
http://www.dla.mil/Portals/104/Documents/DLMS/eApplications/LogDataAdmin/MILSTR
AP_DI_Code_Function_DI_Code_sequence.doc
http://www.dla.mil/Portals/104/Documents/DLMS/eApplications/LogDataAdmin/MILSTR
AP_DI_Code_Function_InDLMSsequence.doc
AP11-1 APPENDIX 11
DLM 4000.25, December 14, 2016
Change 8
AP12. APPENDIX 12
MATERIEL RECEIPT ACKNOWLEDGMENT REPORT
BUSINESS RULES
AP12.1. Materiel Receipt Acknowledgement Report – Business Rules
AP12.2. Background.
AP12.2.1. MRA reports show shipments and the percentage of shipments for
which the DAAS receives and does not receive the associated MRA transactions.
Qualifying Shipments included in the report are determined by the date released to
carrier (recorded at DLA Transaction Services) plus 25 calendar days to
accommodate the 17 calendar days MRA reporting period and the 10 calendar days
MRA follow-up response timeframes (if CONUS); or plus 43 calendar days to
accommodate the 34 calendar days MRA reporting period and the 10 calendar
days MRA follow-up response timeframe (if OCONUS – Transportation
Category 1 or 2); or plus 90 calendar days to accommodate the 81 Calendar days
MRA reporting period and the 10 calendar days MRA follow-up response timeframe
(if OCONUS – Transportation Category 3). 1 Security assistance program
requisitions are not captured for inclusion in LMARS or MRA Reports based on the
Security Cooperation Implementing Agency code in the first position of the document
number.
AP5.12.2.2. The MRA report is created at the end of each month to reflect
the MRA transactions as received/not received in the preceding month.
Receipt of an MRA citing Discrepancy Code B or F updates the Logistics
Metrics Analysis Reporting System (LMARS) reports to reflect the current
status of MRA transactions received. The MRA Reports are created monthly
and reflect the MRA data at the end of the month and will not be adjusted
retroactively when an MRA is submitted following receipt of materiel after an
MRA citing Discrepancy Indicator Code B or F is received.
AP12.3. TRANSACTIONS
1
Per DLM 4000.25, Chapter 10, the reporting period is defined as 17 calendar days for CONUS; 34
calendar days for OCONUS Transportation Category 1 and 2 shipments; and 81 calendar days
for OCONUS Transportation Category 3 shipments. The follow-up response timeframe for both is
10 days. Refer to ADC 1114.
AP12-1 APPENDIX 12
DLM 4000.25, December 14, 2016
Change 8
functionality of MILSTRIP legacy Document Identifier Codes (DIC) A01, A02, A04,
A05, A07, A0A, A0B, A0D, and A0E.
AP12.3.2.2. The DLA post-post issue from forward stock at recruit training
centers is identified by the DLMS 867I by beginning segment (1/BPT04/20 Code 01).
This transaction provides the functionality of MILSTRAP legacy DIC D7_.
AP12-2 APPENDIX 12
DLM 4000.25, December 14, 2016
Change 8
used by the requisitioner to establish a due-in record for receipt processing of
materiel issued by the NICP/SICC from processing of a pre-positioned requisition. 2
AP12.3.3.5. The Army Offline MRO Image is identified by the DLMS 940R
by the beginning segment (1/W0506/0200 Code NA, and 1/W0507/0200 Code FI).
This transaction provides the functionality of the Army unique transaction B99.
2
The Army advised that with the transition to Army LMP, this functionality is not currently in use, but the
DAAS processing rules should be retained for potential future use.
3 Standard A4_ transaction with a Distribution Code = 2 or 3 is treated as a lateral redistribution order.
Navy A4_ is treating this A4_ as an MRO and not a requisition, thus a special rule is required so LOTS
can flag appropriately. The internal rule in LOTS for categorizing these D7s is: If there is no other
requisition DIC equivalent as defined in decision blocks 2 and 3, then flag the D7 as a requisition
equivalent; if there is a requisition equivalent, but no traditional MRO, then treat the D7 as an MRO; if
there is a requisition equivalent and MRO equivalent, but no shipment status, then treat the D7 as
shipment. Summary: Navy – No Shipment; D7_ is a shipment; No MRO, D7_ is an MRO; No Reqn, D7_
is a Requisition.
AP12-3 APPENDIX 12
DLM 4000.25, December 14, 2016
Change 8
functionality of the Intra Navy use of MILSTRIP legacy DIC D7_. These two
transactions are primarily from Navy Enterprise Resources Planning (ERP) to
Commercial Asset Visibility (CAV) sites to issue A condition materiel from a CAV
site.
AP12.4. MRA Business Rules derived from the MRA Decision Tree. The following
list identifies the decision blocks and key transactions and business rules used to
identify the presence of a requisition or MRO type transactions to determine MRA
Report eligibility. The decision blocks identify transactions unique to Component
specific processes. Figure AP12. F1 is a graphical version of the MRA Decision
Tree.
4 Some of the Air Force A2_, BF7 process was identified in ADC 405 to support ECSS development.
5 DLA Transaction Services records the ICP (To RIC) for requisition type transaction, passing, referral and
redistribution order transactions. When an MRO type transaction is received, the ICP is re-recorded and
the From RIC is used. If and MRO is received by DLA Transaction Services, unless they receive a denial,
the recorded ICP is never changed. A denial and new MRO will change the ICP.
AP12-4 APPENDIX 12
DLM 4000.25, December 14, 2016
Change 8
b. If No, proceed to Decision Block 3
Decision Block 3. Is the original source transaction a passing order or referral order,
where the Distribution Code does not equal 2 or 3 in the first position? 6 This business
rule applies to all Services/Agencies.
c. DLA: Post-Post issues (D7_) from forward stock at recruit training centers?
6
Distribution Code:
2 – For use by IMMs to identify transactions associated with lateral redistribution of DoD consumable
assets.
3 – For use by IMMs to identify transactions associated with lateral redistribution of DoD reparable
assets.
7
DLA will not generate an A5_ unless it is for a customer requisition.
AP12-5 APPENDIX 12
DLM 4000.25, December 14, 2016
Change 8
e. Air Force: RDO and RDO Follow-Up 8
Decision Block 8. Did the ICP generate a follow-up for delinquent MRA transaction
(DRF) within the required time limit? 10
8
Air Force BF7 was only used between D035A and SBSS (ILS-S and base retail). It is an RDO follow-up
to the shipping activity. Air Force plans to continue using A2_ and has no plan to convert to A5_.
9
See ADC 1062 – Non-Inventory Control Point/Integrated Materiel Manager (ICP/IMM)-Directed Inter-
Service Lateral Support via Retail Level Passing Order.
10
See ADC 1087 – Revise Materiel Receipt Acknowledgement (MRA) Report Selection Criteria to Reflect
the MRA Process Exclusion for Receipt Transaction Reporting.
AP12-6 APPENDIX 12
DLM 4000.25, December 14, 2016
Change 8
b. If No, No MRA Tracking required
AP12.5.1.1. The initial rule for reports that must be met is the document
numbers that yielded the requirement for MRA Tracking are based on the business
rules identified in the MRA Decision tree (Enclosure 3).
AP12-7 APPENDIX 12
DLM 4000.25, December 14, 2016
Change 8
AP12.5.1.8.2. Revised Business Rule. DLM 4000.25, Volume 2,
C10.2.6. Acknowledgement of Split or Partial Shipments. When a shipped line item
(requisition document number and suffix code) is consigned as a split or partial
shipment, submit an MRA for the shipment segments as they are received. The split
or partial shipment codes are part of the transportation control number (TCN)
structure in accordance with DTR 4500.9-R, Defense Transportation Regulation.
Accordingly, reporting activities must include the TCN in the MRA transaction when
it is available (ADC 247). If the total quantity for the shipped line item is not received
by the due-in date, report the missing quantity, citing Discrepancy Indicator Code F,
in accordance with the guidance in the MRA transaction.
11
Existing requisition edits are addressed in Chapter 4, Table C4.T4, Requisition Processing and Related
Actions, and the DoDAAC authority code edits identified in Chapter 4, paragraph C4.10.2. Table
C4.T3. DoDAAC Authority Codes.
AP12-8 APPENDIX 12
DLM 4000.25, December 14, 2016
Change 8
Figure AP12.F1. MRA Report Business Rules
Capture Shipments out of Wholesale Assets that Qualify for MRA Reporting
Update MRA Business Rules/Report Logic to require the presence of a requisition or MRO type document to determine MRA report eligibility1
4
2 3
Service Specific:
1 All: All:
Is the initial supply
SoS = Is the initial supply Is the initial supply
transaction one of the following?
Wholesale ICP? Yes transaction a No transaction an A3_ or No
Army: BE9, (RP30 = A, C, W)
(Refer to master requisition? A4_? 2
DLA: CH1, CHA, D7_
list) A0_, AT_ or (and not 2 or 3
Air Force: CH1, CHA
AM_ in RP54)
GSA: CH1, CHA
LMARS processes first to
look for a valid SoS in either
the Requisition or MRO.
No
Yes Yes
Yes
7
5
Do any of the Following
3 Is the
Exclusions Apply?
Initial supply transaction
Reqn or Ship-To DoDAAC = GSA or 6
an equivalent A5_MRO?
FEDSTRIP Is there Shipment
All: A5_ (except A5J) and
FMS docs start w/B, D, I, K, P or T Yes Status (from a Yes
A4_ with 2 or 3 in RP54
Shipment to state, civil or Federal Agencies Wholesale ICP)?
DLA ICPs: C0_, CQ_
Shipments of FF&V (DIC AS_)
4 Intra Navy: A4_, D7_
DoDAAC begins with HX 4
Yes Air Force: A2_, BF7
Distribution Code = 9_
Army: B99
No MRA
tracking No
No
8
Did the ICP
Generate a Follow-Up
For Delinquent MRA transaction No MRA
No No
(DRF) within the require time limit? tracking
(Intra-Component
shipments)
PDC1087
1
This will eliminate redistribution orders from being included in MRA Reports
2
DLA post-post issues (D7_) from forward stock at recruit training centers
Yes 3
Exclusions noted in DLA Transaction Services Business rules from 2/2003
and clarified in PDC 1088
4
Track for AF uses A2_ as an equivalent MRO, no plans to change to A5_.
Receipt of MRA Key: Blue text = Proposed new selection criteria.
Transaction
Gaps
Offline DLA processes for Subsistence, Medical; and
Maintenance Repair and Operations. These are known
MRA gaps because no shipment status is created.
A2 – Redistribution Order (RDO), A3 – Passing Order, A4 – Referral Order, Lateral Redistribution Order (LRO),
A5 – Materiel Release Order (MRO), A5J – Materiel Release Order, Image Transactions – (CH_), Post Post (CO_, CQ_ ).
Revised: October 31, 2014 (Corrected text in Step 7 to add “Reqn or Ship-To DoDAAC and remove associated footnote).
AP12-9 APPENDIX 12