Page 1 of 3 

PDC 208 

Attachment 

ATTACHMENT TO ADC 224 

REVISED PROCEDURES FOR LOGISTICS 

ACCOUNTABILITY DURING MAINTENANCE 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO)

b. Originator: Ms. Mary Jane Johnson, DLMSO, 703-767-0677, DSN 427-0677, e-mail: 

Mary.Jane.Johnson@dla.mil, and Ms. Ellen Hilert, 703-767-0676, DSN 427-0676, or e-mail: 

Ellen.Hilert@dla.mil

2. FUNCTIONAL AREA: Supply and interface with Maintenance

3. REFERENCES: 

a. DLMS Supply PRC meeting, 03-1, January 29-30, 2003 

b. DLMSO Memorandum, February 2, 2006, subject: Maintaining Accountability 

During Maintenance Actions (published by MILSTRIP Change Number 1 and to be 

published by MILSTRAP Change Number 5 in the 3rd quarter Fiscal Year 2006) 

c. DLMS Supply PRC meeting, 06-1, April 25-27, 2006 

d. Unique Item Tracking (UIT) policy is published by DOD 4140.1-R, DOD Supply 

Chain Materiel Management Regulation, which is available at: 

http://www.dtic.mil/whs/directives/corres/html/41401r.htm. 

e. Unique Identification (UID) policy and associated documentation are available at: 

http://www.acq.osd.mil/dpap/UID

4. REQUESTED CHANGE: 

a. Title: ADC 224, Revised Procedures for Logistics Accountability During 

Maintenance 

b. Description of Change: This change incorporates multiple revisions to 

procedures for maintaining accountability during maintenance. 

(1) The Joint Group Materiel Management (JGMM) subgroup for Supply 

Support to Inter-Service Depot Maintenance reviewed the AMCLs 12 and 43 

(reference 3.b.) procedures for maintaining accountability during maintenance and made 

the following recommendations. The following changes fall within the 

MILSTRIP/DLMS functional area; a separate proposed change is under development for 
Page 2 of 3 

PDC 208 

Attachment 

coordination of revisions and updated procedures in the MILSTRAP/DLMS functional 

area. 

(a) Use existing requisitioning procedures for the induction of reparables 

into maintenance. These procedures include use of the A0_, Requisition transaction and 

describes how the document should be formatted in order to insure material is inducted 

into maintenance at a co-located depot. The format of these transactions further insures 

compliance with JGMM recommendations that the maintenance be accomplished fill or 

kill basis. 

(b) Withdraw directed use of the DI FTA transaction by the shipping activity 

for accountability of items identified and scheduled for repair under a Depot Maintenance 

Inter-Service Support Agreement (DMISA), since that type of workload must be 

negotiated. 

(2) Independent of the JGMM subgroup recommendations, this change also 

proposes additional related revisions recommended during the April 2006 Supply PRC 

meeting as follows: 

 (a) Incorporate procedures associated with storage activity denial of directed 

release of the asset for maintenance action. 

 (b) Establish a requirement for creation of a shipment notification 

transaction when material is shipped from the maintenance depot (organic and 

commercial) to a distribution depot or DRMS. This requirement may be satisfied via a 

DLMS Shipment Status, 856S, or an Advance Shipment Notice, 856, for Property 

Transfer (Government furnished property (GFP) or internal DoD transfer). 

STAFFING NOTE: It is not our intent to publish a MILSTRIP requirement for the 

shipment status, but rather, to establish this requirement under the DLMS. Currently, 

some applications may be capable of transmitting a MILSTRIP AS_ and these should be 

transitioned to DLMS in order to incorporate radio frequency identification (RFID) and 

item unique identification (UID) information. Commercial maintenance depots required 

by DOD UID policy to provide an 856 for property transfer may use this format to satisfy 

both requirements. Distribution depots are capable of receiving both the current format 

for shipment status and advance shipment notification; however, there may be a 

disconnect for shipments to DRMS concerning the 856 and for new enhancements under 

development for the 856 format for property transfer (e.g., recognizing new beginning 

segment codes). Also, the original proposed requirement was for notification to the DD 

or DRMS only, Components may comment for further enhancement if this requirement 

should be expanded to other ship-to locations. 

(3) This change incorporates administrative changes which insert missing 

MILSTRIP text and provide clarifying language for cancellation of customer asset 

reports. 

 

5. REASON FOR CHANGE: During the January 2003 Supply PRC meeting, 

recommended changes to the approved procedures for maintaining accountability during 
Page 3 of 3 

PDC 208 

Attachment 

maintenance, resulting from a series of meetings of the Joint Group Materiel 

Management subgroup for Supply Support to Inter-Service Depot Maintenance, were 

briefed. This change incorporates many of those recommendations. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Incorporates recommendations of the JGMM subgroup for InterService Supply Support to Depot Maintenance, which strengthen the procedures for 

maintaining logistics accountability during maintenance. 

b. Disadvantages: May not be consistent with emerging policy for item unique 

identification (IUID). The UID Program Office may require use of alternative 

transaction formats for shipment and receipt of Government property and items requiring 

IUID while undergoing maintenance (organic and commercial) to update the UID 

Registry. 

7. INTERFACE/IMPACT: 

a. Data Content/Procedures/AIS: The DOD Components may need to revise their 

implementing procedures and automated information systems depending upon the degree 

to which the recommendations of the JGMM subgroup for Supply Support to InterService Depot Maintenance have already been achieved or are under development. 

b. Coordination/Staffing: Requires interface of maintenance, supply, contracting, 

and financial operations and systems to accurately record the status of assets in the 

property accountability records and related financial accounts. 

c. Publications: MILSTRIP and DLMS. May also require changes to Component 

level implementing procedures and contracts for commercial maintenance. 

d. Procedures: 

 (1) Revise MILSTRIP as shown in Enclosure 1. Corresponding changes will 

be adopted in the DLMS manual but are not reflected in this document. 

 (2) Revise DLMS as shown in Enclosure 2. The inclusion of the 

requirement for shipment status is reflected only in the DLMS. This transaction will be 

converted to MILSTRIP for non-DLMS recipients; however, this is considered a 

modernization change and should be adopted under the DLMS.
Page 1 

PDC 208 

MILSTRIP Chap 9 Procedures 

ENCLOSURE 1 TO ADC 224, 

REVISED PROCEDURES FOR LOGISTICS 

ACCOUNTABILITY DURING MAINTENANCE 

MILSTRIP PROCEDURES

[STAFFING NOTE: Procedures reflect MILSTRIP as modified by Joint AMCL 12 and 

43 published as MILSTRIP Change No. 1]

Revise DOD 4000.25-1-M, MILSTRIP Chapters 2, 3 and 9 as follows: 

1. Table of Contents, Chapter 2, Paragraph C2.22. Delete the word "Reserved" and add 

a new entry as follows: 

"C2.22 REQUISITIONING REPARABLES FOR INDUCTION TO 

MAINTENANCE" 

2. Chapter 2, Paragraph C2.22. Delete the word "Reserved" and add the following:

"C2.22 REQUISITIONING REPARABLES FOR INDUCTION TO 

MAINTENANCE 

C2.22.1 When materiel is scheduled for organic maintenance, based on the 

repair schedule the maintenance activity will requisition the materiel from the materiel 

owner using an A0_ using the format specified in AP3.2. All requisitions will cite 

Advice Code 2J (fill or kill) in rp 65-66, and the appropriate supply condition code in 

rp 71. 

 C2.22.2 To preclude billing by the materiel owner, the A0_ requisition will also 

contain the following data elements to denote free issue. For A0_s submitted to: 

 C2.22.2.1 Air Force: For Air Force principals (RIC TO of F**), use Project 

Code "3BB" in rp 57-59. 

 C2.22.2.2 Navy: For Navy principals (RIC To N**), use Signal Code B in rp 

51 and Fund Code 26 in rp 52-53. If RIC TO is N32, use N00383 in rp 45-50; if RIC 

TO is N35 use N00104 in rp 45-50. 

 C2.22.2.3 Army: For Army principals (RIC TO A** or B**), use Project Code 

"3BB" in rp 57-59; Fund Code GM in rp 52-53 and Signal Code D or M in rp 51. 

Staffing Note: Components should verify above format is accurate. Marine Corps?

3. Table of Contents for Chapter 3. 

a. Paragraph 3.12. Delete the word "Reserved" and add a new entry as follows: 

"C3.12. PROCESSING OF REQUISITIONS FOR INDUCTION TO 

MAINTENANCE" 
Page 2 

PDC 208 

MILSTRIP Chap 9 Procedures 

 b. Paragraph 3.18. Delete the word "Reserved" and add a new entry as follows: 

"C3.18. STORAGE ACTIVITY DENIALS OR REJECTION OF MATERIEL 

RELEASES FOR INDUCTION TO MAINTENANCE 

4. Chapter 3, Requisition Processing and Related Actions. Revise as follows. 

a. Paragraph C3.12. Delete the word "Reserved" and add the following: 

"C3.12 PROCESSING OF REQUISITIONS FOR INDUCTION TO 

MAINTENANCE. 

C3.12.1. Upon receipt of a requisition from maintenance for the purpose of 

inducting a reparable, the materiel owner will process the requisition on a 'fill or kill' 

basis, and direct the issue to the co-located storage activity. If there are insufficient 

assets at the co-located storage activity, the requisition will be 'killed' for that portion 

of the requisition that cannot be issued. No billing will be initiated on requisitions 

from maintenance activities for DMISA assets, when the A0_ was submitted consistent 

with C2.22.2 requirements. 

C3.12.2. Preparation of material release orders (MROs) to the co-located 

storage activity will be accomplished using the format reflected in AP3.12. 

C3.12.3. The "Principal" system will interpret the A0_ 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 supply source (Principal) will furnish the requisitioning activity 

(maintenance) an AE_ Status Code of CB for any unfilled quantity. 

b. Paragraph C.18. Delete the word "Reserved" and add text as shown below. 

Existing paragraph C3.17 is repeated here for continuity.

C3.17. STORAGE ACTIVITY DENIALS OR REJECTION OF MATERIEL 

RELEASES

 C3.17.1. MRDs are prepared by storage sites and transmitted to the supply source 

which initiated the MRO as notification of negative action on the MRO. MRDs will be 

prepared in the format reflected in AP3.17 and will show the quantity denied and 

appropriate management code. 

 C3.17.2. If the storage activity cannot meet the delivery timeframe specified by the 

RDP in rp 62-64, DI AE6/CB status will be provided to the supply source. The supply 

source will advise eligible status recipients (applies to conventional ammunition 

requisitions only).1

 

1

 See Footnote 3. 
Page 3 

PDC 208 

MILSTRIP Chap 9 Procedures 

C3.18. STORAGE ACTIVITY DENIALS OF MATERIEL RELEASES FOR 

INDUCTION TO MAINTENANCE

 C3.18.1 MRDs prepared under paragraph C3.17 will be used to provide a 

negative response to supply source (Principal) initiated MROs directing release of a 

repairable asset for maintenance action.

C3.17.2. If the storage activity cannot provide the reparable asset for 

maintenance action in response to directed release, the supply source (Principal) will 

provide supply status, using DI AE_/CB status, to advise the requisitioning activity 

(maintenance) that the asset is not available for induction. 

5. Table of Contents, Chapter 9, paragraph C9.11. Revise wording as shown. 

C9.11. ICP/IMM SUPPLY SOURCE PROCESSING OF AUTOMATIC RETURN 

NOTIFICATION (DI FTA).

6. Chapter 9, Materiel Returns Program (MRP) and Lateral Redistribution of Retail 

Assets. Revise as shown in Enclosure 3. Blue text is used to identify revised text 

published under MILSTRIP Change 1 as approved under AMCL 43, February 2, 2006. 

Bold italics highlight ADC 224 changes. 

 a. Paragraph C9.10.5. Delete first sentence which describes the use of the FTA for 

items scheduled for repair under DMISA because FTA is not appropriate for negotiated 

workload under DMISA. 

 b. Paragraph C9.11. Insert missing paragraph inadvertently dropped during 

publication of MILSTRIP Change 1. 

 c. Paragraph C9.17.4. Insert clarifying text. Without the additional language the 

meaning of the original sentence is difficult to understand. 

7. Appendix 2.16. Revise Status Code CB as indicated. 

CODE EXPLANATION

CB Rejected. Initial requisition requested Rejection of that quantity not available 

for immediate release or not available by the SDD or RDD or within the RDP 

(for conventional ammunition). Quantity field indicates quantity not filled. 

Also May be used by a reporting activity to advise the ICP/IMM that a DI A4_ 

with distribution code 2 cannot be filled from reported materiel. May be used 

by the supply source (Principal), to notify the maintenance activity that a 

requested asset is not available for induction.
Page 1 

PDC 208 

MILSTRIP Chap 9 Procedures 

Enclosure 2 

C9. CHAPTER 9

MATERIEL RETURNS PROGRAM (MRP) AND

LATERAL REDISTRIBUTION OF RETAIL ASSETS

C9.1. GENERAL

 C9.1.1. This chapter provides procedures for the interchange of information, between the 

owning organization and the item manager, on the reporting and disposition of assets. In 

addition, this chapter provides procedures for ICP/IMM directed lateral redistribution of retail 

assets identified by an Inter- or Intra-Service retail asset visibility system. These procedures also 

establish the necessary controls to ensure timely processing of related transactions and provide 

for the automatic return of materiel under specified conditions. 

 C9.1.2. Policy regarding the reporting, transfer, lateral redistribution, and use of assets as 

an alternative to procurement (also known as the procurement offset portion of Total Asset 

Visibility (TAV)) is contained in DoD 4140.1-R, Supply Chain DoD Materiel Management 

Regulation. 

 C9.1.3. Customer Asset Reports (DI FTE) and follow-on documentation transmitted by 

electronic means will always be routed through DAAS. 

 C9.1.4. Credit for materiel returns is granted on the basis of receipt and classification by 

the consignee. Policy for granting credit is covered under DoD 4140.1-R. 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 DoD 4000.25-7-M 

(MILSBILLS). MILSBILLS also cover credit procedures for packing, crating, and handling 

(PC&H) and transportation (T). In addition, MILSBILLS provides formats for Follow-up for 

MRP Credit (DI FTP) and Reply to Follow-up for Credit (DI FTB). 

 C9.1.5. U.S. Government activities returning materiel are cautioned that the returning 

activity may be held responsible for costs incurred by the receiving activity when discrepancies 

are reported and validated using SDR procedures (DLAI 4140.55 et al. and DLAI 4140.60 et al.). 

This includes returns made in violation of prescribed materiel returns procedures, returns 

exhibiting packaging discrepancies, and returns of reparable items unaccompanied by required 

technical data. Recoupment action by the ICP against the initiator may include all cost 

reimbursable actions performed by the receiving activity such as repackaging, marking, and 

disposal. 

C9.2. APPLICABILITY AND SCOPE

 C9.2.1. The provisions of this chapter are applicable to all activities offering or returning 

materiel to a Service ICP, DoD IMM, or the GSA. These procedures also apply to activities 

receiving and processing lateral redistribution orders of retail assets. Policy regarding utilization 

and redistribution of MAP materiel is contained in DoD 5105.38-M, chapter 11, section II. These 

procedures also apply to the processing of nonconsumable items. 
Page 2 

PDC 208 

MILSTRIP Chap 9 Procedures 

C9.3. EXCLUSIONS

 C9.3.1. The DLA does not accept part-numbered customer asset reports. (All other partnumbered asset reports will be passed to the RI indicated in the incoming transaction.) Customer 

asset reports identified by part numbers2

 exceeding rp 8-22 of the stock or part number field are 

excluded from the DAAS processing of DI FTG transactions. Other customer asset reports for 

items not identified by an NSN; for example, locally assigned stock numbers, are excluded from 

these procedures on an inter-Component basis. 

 C9.3.2. Perishable subsistence items, with the exception of perishable subsistence returns 

(other than FF&V) from Navy mobile logistics, support fleet ships in the Pacific area. 

 C9.3.3. IPE identified only by plant equipment code/manufacturers part number. Report 

these items to RI S9R using DD Form 1342, DoD Property Record. 

 C9.3.4. Class V (W) ground (surface) ammunition. 

 C9.3.5. Lumber products (with exception of lumber product items stocked by GSA). 

 C9.3.6. Items under DTRA management (such as, FSG 11, DOE special design and quality 

controlled items identified by CAGE 87991 in the FLIS master item file) and all DoD items 

designed specifically for use on or with special weapons (identified by CAGE 57991, 67991, or 

77991 in the FLIS master item file). (These items will be processed under DOE-DTRA TP 100-1 

et al.) 

 C9.3.7. ADPE under DoD 4160.21-M. 

C9.4. RESERVED

C9.5. REPORTING CRITERIA FOR CUSTOMER ASSET REPORTS (DI FTE/FTG)

 C9.5.1. Reporting of assets will be determined by the existing retention and reporting 

policy under DoD 4140.1-R. This includes the reporting policy for the procurement offset 

portion of TAV as described in DoD 4140.1-R. In response to the Asset Status/Transaction 

Reporting Request (DI DZE under MILSTRAP), submit a Customer Asset Report (DI FTE/FTG) 

using the appropriate project codes from paragraph C9.6.7. 

 C9.5.2 The reporting activity will forward customer asset reports to the ICP/IMM. Direct 

all GSA customer asset reports to RI GG0.3

 Customer Asset Reports (DI FTE/FTG) transmitted 

by electronic means will always be routed through DAAS. 

C9.6. PREPARATION OF CUSTOMER ASSET REPORTS (DI FTE/FTG)

 C9.6.1. Customer Asset Reports (DI FTEs) will be prepared using one of the following 

mediums with data elements shown in the AP3 appendices. Part-numbered Customer Asset 

Reports (DI FTGs) will only be prepared using the mechanical format on DD Form 1348m. 

 

2

 Use of part-numbers in the Material Returns Program last reported as not implemented by USMC. Refer 

to AMCL 167. 

3

 Requirement to use a single RI on Customer Asset Reports directed to the GSA last reported as not 

implemented by USA. Refer to AMCL 26. 
Page 3 

PDC 208 

MILSTRIP Chap 9 Procedures 

 C9.6.1.1. DD Form 1348m, DoD Single Line Item Requisition System Document 

(Mechanical). 

 C9.6.1.2. DD Form 1348, DoD Single Line item Requisition Document (Manual). 

 C9.6.1.3. DD Form 173/2, DoD Joint Messageform. 

 C9.6.2. Use the mechanical DD Form 1348m as the normal reporting transaction and 

transmit to the supply source via the DAAS. Prepare the DD Form 1348m using the format 

contained in AP3.33. 

 C9.6.3. The manual DD Form 1348 will be prepared as reflected in AP3.33. The manual 

form will be used only when: 

 C9.6.3.1. Facilities are not available to the reporting activity to permit electronic 

transmission of reports or when machine-processing facilities are not available. 

 C9.6.3.2. The report coding structure does not provide sufficient data to assist the 

ICP/IMM in making decisions on disposition of materiel or the granting of credit to the reporting 

activity. In these instances, the exception data will be entered in remarks portion of the manual 

DD Form 1348. Reporting activities should not attempt to use exception data as a normal method 

for reporting materiel, as this necessitates off-line processing by both the reporting activity and 

the ICP/IMM. 

 C9.6.3.3. The report must be accompanied by technical data including special forms. 

 C9.6.3.4. Manually prepared reports will be submitted by priority mail with 

containers conspicuously marked MILSTRIP ASSET REPORTS. 

 C9.6.4. The joint message form (DD Form 173/2) will be prepared using AP1.22. The 

message form will be used only when message communication facilities are not available and 

rapid transmission is required to expedite processing of the asset report. 

 C9.6.5. Reports of serviceable NIMSC 5 items from SICA reporting activities to the 

appropriate Service SICA will be submitted under Service implementing instructions. Quantities, 

which are not required by the SICA, will be forwarded to the PICA using DI FTE, the PICA’s RI 

in rp 4-6, M&S 9, Signal Code C or L, the SICA’s fund code in rp 52-53, and the SICA’s RI in 

67-69. If appropriate, the SICA will provide DI FTD delay status to the materiel holder for the 

quantity referred to the PICA, under paragraph C9.13.5, below. The date in rp 70-73 of the DI 

FTD, if used, will be 35 days subsequent to the date the report was forwarded to the PICA. The 

PICA will provide disposition instructions to the SICA, designated by rp 52, and the M&S. The 

SICA, in turn, will provide disposition instructions to the reporting activity under Service 

implementing instructions. 

 C9.6.6. When the SICA has NIMSC 5 serviceable stocks on hand which exceed the 

retention limit, the SICA will prepare the DI FTE using the guidelines above but with the SICA’s 

own document number. 

 C9.6.7. The Services/Agencies will use one of the following project codes for the 

procurement offset portion of TAV in rp 57-59 of their Customer Asset Report (DI FTE/FTG): 

 C9.6.7.1. RBB for consumables, 
Page 4 

PDC 208 

MILSTRIP Chap 9 Procedures 

 C9.6.7.2. 3AG for reparables, or 

 C9.6.7.3. 3AU for DRMO assets. 

C9.7. CANCELLATION OF CUSTOMER ASSET REPORTS (DI FTC)

 C9.7.1. Use AP3.38 to prepare cancellation of asset reports, in total or partial quantities, 

and submit to the ICP/IMM under the following conditions; 

 C9.7.1.1. When a determination is made that materiel is not available in the quantity 

reported on the asset report. 

 C9.7.1.2. Upon determination that materiel directed for return will not be returned. 

 C9.7.2. 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. 

C9.8. PROCESSING REPLIES TO CUSTOMER ASSET REPORTS (DI FTR)

 C9.8.1. The Reply to Customer Asset Report (DI FTR), prepared under AP3.34, is used by 

the ICP/IMM to respond to all Customer Asset Reports (DI FTE/FTG). The reporting activity 

will process the DI FTR reply using the asset transaction status code (AP2.16) and take the 

following actions: 

 C9.8.1.1. Use paragraph C9.7., above, to submit a cancellation (DI FTC) when it is 

determined that materiel directed for return will not be returned. 

 C9.8.1.2. Use AP3.39 to prepare a shipment status (DI FTM) and promptly submit to 

the ICP/IMM after materiel directed for return is released to the carrier. Prepare a separate DI 

FTM for each shipment. Exercise care to ensure that appropriate data content, including suffix 

(rp 44) of the individual DI FTR reply, is perpetuated in the DI FTM. 

 C9.8.2. When DI FTR is transmitted to the SICA designated by rp 52, the SICA will 

forward the disposition instructions to the materiel holder under Service implementing 

instructions. The materiel holder will provide advice to the SICA regarding shipment or 

cancellation as appropriate, under Service implementing instructions, and the SICA will provide 

DI FTM or FTC to the PICA. If the SICA receives DI FT6 from the PICA and has no record of 

shipment, the SICA will follow up to the materiel holder and submit an interim DI FTL to the 

PICA containing a future ESD to preserve the PICA’s due-in record pending a firm reply to the 

DI FT6. 

 C9.8.3. All DI FTR replies Customer Asset Reports (DI FTE/FTG) containing Project 

Code RBB 3AG, or 3AU denoting the procurement offset portion of TAV and Status Code TC in 

rp 65-66, require 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. 

C9.9. FOLLOW-UPS ON REPORTED ASSETS (DI FTF/FTT/FTP/FT6)

 C9.9.1. Reporting Activity Follow-ups Consist of Three Types: 
Page 5 

PDC 208 

MILSTRIP Chap 9 Procedures 

 C9.9.1.1. Follow-up for ICP/IMM Reply of Asset Report (DI FTF). This type 

follow-up will be used to obtain intelligence regarding status of the original asset report (DI FTE) 

and will be prepared using AP 3.37. DI FTF will be submitted no earlier than 30 days from date 

of submission of the DI FTE and will contain the same data as reflected in the DI FTE. If a DI 

FTD has been received, the DI FTF will be submitted at the expiration of the expected reply date 

and a DI FTR has not been received. 

 C9.9.1.2. Follow-up for ICP/IMM Materiel Receipt Status (DI FTT). This type 

follow-up will be used when materiel to be returned has been shipped as directed by a Reply to 

Asset Report (DI FTR) but an ICP/IMM Materiel Receipt Status (DI FTZ) has not been received. 

This follow-up will be prepared using AP3.43. DI FTT will be submitted no earlier than 70 days 

(CONUS) or 130 days (OCONUS) after shipment. This data for the DI FTT will be the same as 

reflected in the DI FTM. 

 C9.9.1.3. Follow-up for Credit (DI FTP). This type follow-up will be used when 

materiel to be returned has been shipped and credit allowance was indicated by ICP/IMM 

Materiel Receipt Status (DI FTZ) but no credit billing has been received. This follow-up will be 

prepared under MILSBILLS procedures. 

 C9.9.2. Follow-up will be submitted to the ICP/IMM to whom the original asset report (DI 

FTE) was submitted, except when information has been received in a DI FTQ status that the 

DAAS has rerouted the asset report to the correct ICP/IMM. In this case, the follow-up will be 

submitted to the activity identified in the DI FTQ status received from the DAAS. 

 C9.9.3. ICP/IMM Follow-ups on Directed Returns (DI FT6). Upon receipt of a DI FT6 

follow-up on a DI FTR from the ICP/IMM, the reporting activity will review records to determine 

whether or not a DI FTR had been received. If there is no record of having received a DI FTR, 

the DI FT6 will be converted to a DI FTR and processed. If shipment has not occurred, a DI FTL 

citing the ESD will be submitted. If records indicate that shipment has occurred, the 

transportation activity will be queried to ensure the materiel has actually been shipped. If the 

materiel has been shipped, a new DI FTM will be created. If the materiel has not been shipped, 

ascertain when the shipment will be made and follow the above procedures.4

 When less than the 

total quantity contained in the original DI FTR is to be shipped, the reporting activity will 

respond to the DI FT6 with a DI FTL for the quantity to be shipped and a DI FTC for the quantity 

which will not be shipped. If any of the shipment has already occurred, the reporting activity will 

respond to the DI FT6 with DI FTM for the quantity which has been shipped and with Dls FTL 

and/or FTC for the remaining portions of the originally reported quantity, as appropriate. 

C9.10. AUTOMATIC RETURNS (DI FTA)

 C9.10.1. DI FTA is used for items designed by a supply source for automatic return. 

Supply sources will notify reporting activities of the location to which items so designated are to 

be shipped. DI FTA format is contained in AP3.40. 

 C9.10.2. All NIMSC 5 unserviceable (Supply Condition E or F) items are designated for 

automatic return on an inter-Service basis. PICAs will notify SICAs of the NSN and the storage 

activity to which such items are to be shipped. PICAs will also notify the receiving storage 

activity of such items which are to be returned. The SICAs will perpetuate this information to the 

 

4

 Modification of Materiel Returns Program reporting timeframes last reported as not implemented by 

USN. Refer to AMCL 6.
Page 6 

PDC 208 

MILSTRIP Chap 9 Procedures 

SICA activities using intra-Service procedures. If there is no S/A SICA for the items identified 

for automatic return by a PICA (for example, the Coast Guard), the PICA will provide the 

information to the appropriate S/A designated activity. 

 C9.10.3. Use Project Code 3AL in the DI FTA and in subsequent documentation when an 

unserviceable NIMSC 5 item is automatically returned or when requisitioning a replacement 

item. If a replacement for the unserviceable NIMSC 5 automatic return item will not be 

requisitioned (for example, the returned item exceeds the returning activity’s authorization or 

requirement), the DI FTA and related documentation will not contain Project Code 3AL. Use the 

data elements specified under paragraph C9.6.5 in the DI FTA. This does not include the M&S 

which may be assigned using S/A instructions. Enter the SICA RI in rp 67-69 if M&S 9 is 

assigned. Subsequent to the generation of DI FTA, processing will occur as though there has 

been a DI FTE report and a DI FTR reply, along with other provisions of this chapter, except for 

DIs FTF and FTD. 

 C9.10.4. No other inter-S/A use of DI FTA is currently authorized. 

 C9.10.5. The FTA transaction will also be prepared by the shipping activity and forwarded 

to a SICA for items identified and scheduled for repair under a Depot Maintenance Inter-Service 

Support Agreement (DMISA). S/As may use DI FTA internally for intra-S/A programs that do 

not conflict with other provisions of this manual.

C9.11. ICP/IMM SUPPLY SOURCE PROCESSING OF AUTOMATIC RETURN 

NOTIFICATION (DI FTA). Upon receipt of the DI FTA transaction the supply source will 

take action to establish a due-in and generate a PMR transaction to the receiving activity for 

the quantity in the FTA transaction. Action to establish the due-in and create the PMR 

transaction will be accomplished under MILSTRAP. NOTE: For unserviceable NIMSC 5 

items, the SICA will forward the DI FTA transaction, with data elements specified in 

paragraph C9.10.3 of this chapter, to the PICA. The PICA will establish the due-in and 

furnish the PMR to the receiving depot.

C9.12. DEFENSE AUTOMATIC ADDRESSING SYSTEM

 DAAS will accomplish the following: 

 C9.12.1. DIs FTL, FTM, FTP, and FTT will be passed to the activity represented by the RI 

in rp 4-6. 

 C9.12.2. DIs FTB, FTD, FTQ, FTR, FTZ, and FT6 will be routed using the M&S code. 

 C9.12.3. DI FTA will be passed to the RI in 4-6. DIs FTC, FTE, and FTF containing M&S 

9 will be passed to the RI in rp 4-6. 

 C9.12.4. When DIs FTC, FTE, and FTF do not contain M&S 9, DAAS will perform an 

NSN/NIIN validation and supply source edit as follows: 

 C9.12.4.1. If the NSN is correct and managed by the ICP/IMM identified in rp 4-6, 

Advice Code 3T will be entered in rp 65-66 and the DI FTC, FTE, or FTF will be transmitted to 

that ICP/IMM. 

 C9.12.4.2. If the NSN is correct but is not managed by the ICP/IMM identified in rp 

4-6, the correct ICP/IMM RI will be entered in rp 4-6, Advice Code 3T will be entered in rp 65-
Page 7 

PDC 208 

MILSTRIP Chap 9 Procedures 

66, and the DI FTC, FTE, or FTF will be transmitted to the correct ICP/IMM. DAAS will furnish 

the reporting activity a DAAS Customer Asset Report Status (DI FTQ) with Status Code TZ in rp 

65-66. 

 C9.12.4.3. If the FSC/NIIN/NSN validation indicates that the FSC is incorrect, the 

FSC will be changed and the RI of the ICP/IMM in rp 4-6 will be changed where applicable. 

Advice Code 3T will be entered in rp 65-66 and the DI FTC, FTE, or FTF will be transmitted to 

the managing ICP/IMM. DAAS will furnish the reporting activity and DI FTQ with Status Code 

TZ in rp 65-66. 

 C9.12.4.4. If routing to an ICP/IMM cannot be accomplished by DAAS, the DI FTC, 

FTE, or FTF will be passed to the activity identified in rp 4-6. 

 C9.12.5. DAAS will validate DI FTA, FTE, and FTF transactions for valid ship-from and 

credit-to addresses as designated by the signal code. When the signal code is C or L, the code in 

rp 52 must identify a valid credit-to activity as prescribed by MILSBILLS. If DAAS cannot 

identify the ship-from or credit-to address, the transactions will be rejected to the originating 

activity using DI FTQ with SK status.5

 C9.12.6. The DLA will not accept DI FTG part-numbered asset reports. DAAS will reject 

all such reports with Status Code T9. DAAS will pass all other DI FTG part-numbered asset 

reports to the RI present in the incoming transaction. Components may reject (Status Code T9) 

part-numbered assets not acceptable or recognized under internal procedures. Nonmechanical 

part-numbered transactions will not be processed by DAAS but will be rejected for processing 

under intra-Component procedures. 

 C9.12.7. DAAS will edit DI FTR rejects containing Status Codes SC and SD for correct 

ICP/IMM and FSC as follows: 

 C9.12.7.1. If the NSN is correct and belongs to the rejecting ICP/IMM, the DI FTR 

will be converted to DI FTE with Advice Code 3T in rp 65-66 and returned to the rejecting 

ICP/IMM. When DAAS converts DI FTRs to DI FTEs and returns the DI FTEs to the rejecting 

ICP/IMM, DAAS will enter code D in rp 70 of the DI FTE to provide the ICP/IMM with a 

duplicate document override edit. 

 C9.12.7.2. If the FSC is incorrect, the DI FTR will be converted to DI FTE with the 

correct FSC; Advice Code 3T will be entered in rp 65-66 and the document will be returned to the 

rejecting ICP/IMM or transmitted to the correct ICP/IMM. 

 C9.12.7.2.1. When DAAS converts DI FTRs to DI FTEs and routes the DI 

FTEs to an ICP/IMM other than the rejecting ICP/IMM, DAAS will furnish the reporting activity 

with DI FTQ status containing Status Code TZ in rp 65-66. 

 C9.12.7.2.2. When the converted DI FTE is routed back to the rejecting 

ICP/IMM, code D will be inserted into rp 70 to provide the ICP/IMM with a duplicate document 

override edit and DAAS will furnish the reporting activity a DI FTQ containing Status Code TZ 

in rp 65-66. 

 

5

 See Footnote 1. 
Page 8 

PDC 208 

MILSTRIP Chap 9 Procedures 

 C9.12.7.3. If a DLA, GSA, or Navy IMM has coded the item inactivated in DAAS 

records and a DLA, GSA, or Navy activity originated the reject document, DAAS will change the 

status code in rp 65-66 to TC and forward the DI FTR to the reporting activity. 

 C9.12.8. DAAS will edit DI FTR rejects from GSA with Status Code SC as follows: 

 C9.12.8.1. If the NSN is correct and it is managed by GSA, DAAS will change the 

status code in rp 65-66 to TC and forward the DI FTR to the reporting activity. 

 C9.12.8.2. If the NSN is correct but not managed by GSA, DAAS will convert the 

DI FTR to FTE, enter Advice Code 3T in rp 65-66, and transmit the document to the appropriate 

ICP/IMM. In addition, DAAS will furnish the reporting activity a DAAS Customer Asset report 

Status (DI FTQ) with Status Code TZ in rp 65-66. 

 C9.12.8.3 If the NIIN is valid and the FSC is incorrect, DAAS will convert DI FTR 

to DI FTE with the correct FSC; enter Advice Code 3T in rp 65-66 and transmit the FTE 

document back to GSA or to the managing ICP/IMM. When the converted FTE is routed back to 

GSA, code D will be inserted in rp 70 to provide a duplicate document override edit. DAAS will 

furnish the reporting activity a DI FTQ with Status Code TZ in rp 65-66. 

 C9.12.8.4. If the NSN cannot be identified, DAAS will change the status code to SD 

and transmit the DI FTR to the reporting activity. 

C9.12.9. DAAS will automatically route all DI FTE transactions for GSA-managed items to RI 

GG0.6

C9.13. INVENTORY CONTROL POINT/INTEGRATED MATERIEL MANAGER 

PROCESSING OF CUSTOMER ASSET REPORTS (DI FTE)

 C9.13.1. The ICP/IMM will process asset reports to determine disposition. Asset reports 

containing project codes assigned for specific returns program purposes (such as rollbacks and 

automatic returns) will be processed under the assigned controls. (See paragraph C9.6.7., above). 

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. 

 C9.13.1.1. The Reply to Customer Asset Report (DI FTR) will be prepared using 

AP3.34 to respond to asset reports no later than 30 days from date of receipt of the DI FTE.7

 C9.13.1.2. If a DI FTR cannot be provided within 30 days, send a DI FTD (AP3.36) 

with Status Code TR and enter a date in rp 70-73 when final disposition instructions are expected 

to be provided.8

 C9.13.1.3. Suffixes, as indicated in AP2.8, will be used to identify partial actions.9

 C9.13.2. If it is determined that the materiel is required, the IMM will forward a DI FTR 

citing Status Code TA, TB, TH, or TJ to the reporting activity. The ICP/IMM will establish a 

 

6

 See Footnote 2. 

7

 See Footnote 3. 

8

 See Footnote 3. 

9

 See Footnote 3. 
Page 9 

PDC 208 

MILSTRIP Chap 9 Procedures 

due-in for the quantity of materiel to be returned and generate a MILSTRAP PMR transaction to 

the receiving depot.10

 C9.13.2.1. The time allowed for shipment and return of materiel is 120 (CONUS) 

and 180 (OCONUS) days, and the counting starts with the day of posting the receipt of the DI 

FTM or the estimated shipping date cited in the DI FTL. The Due-in EDD will be updated upon 

receipt of a DI FTM or FTL to equal the time allowed for shipment and return of material.

 C9.13.2.2. If the materiel is not received by the due-in EDD, or 30 days have elapsed 

since the transmission of a DI FT6 without receiving a response, the ICP/IMM will initiate 

cancellation action under paragraph C9.17.

 C9.13.2.3. Action taken to cancel the due-in and delete the PMR transaction does not 

preclude requirements prescribed in other DoD manuals and joint regulations to initiate tracer 

action and file discrepancy reports, such as a TDR or SDR, on shipments not received but for 

which shipment status has been received.11

 C9.13.3. Enter PDs in DI FTR replies as follows: 

 C9.13.3.1. PD 03 will be used in the return of critical items and approved intensive 

management items (including serviceable local stocks). 

 C9.13.3.2. PD 06 will be used in the return of materiel identified by the ICP/IMM as 

qualified for automatic return to the DoD distribution system. 

 C9.13.3.3. PD 13 will be used in the routine return of materiel not covered above 

(except surplus and scrap) such as the return of local stocks to supply sources. 

 C9.13.4. Customer Asset Reports (DI FTEs) received by the ICP/IMM which cannot be 

processed will be rejected to the reporting activity using DI FTR status with the appropriate S_ 

series reject status code from AP2.16. 

 C9.13.5. Customer Asset Reports (DI FTEs) received for items requiring extended 

screening/review will be suspended. The reporting activity will be furnished a DI FTD with 

Status Code TR containing an estimated date of reply in rp 70-73. 

 C9.13.6. All manually prepared asset reports (DI FTEs) received by an ICP/IMM for 

which it is not the prime manager will be forwarded to the responsible ICP/IMM for processing. 

The correct ICP/IMM RI will be entered in rp 4-6 of the DI FTE. The ICP/IMM will furnish the 

reporting activity DI FTR containing Status Code T6 in rp 65-66. The RI of the forwarding 

ICP/IMM will be entered in rp 4-6 and the RI of the ICP/IMM representing the last known source 

will be entered in rp 67-69. 

 C9.13.7. If the determination has been made that a FSC change is required on a manually 

prepared Customer Asset Report (DI FTE), the correct FSC will be entered, the RI of the 

ICP/IMM in rp 4-6 will be changed, where applicable, and the DI FTE will be forwarded to the 

responsible ICP/IMM for processing. The reporting activity will be furnished a DI FTR 

containing Status Code T7 in rp 65-66. The RI of the forwarding ICP/IMM will be entered in rp 

4-6 and the RI of the ICP/IMM representing the last known holder will be entered in rp 67-69. 

 

10 See Footnote 3.

11 See Footnote 3. 
Page 10 

PDC 208 

MILSTRIP Chap 9 Procedures 

C9.14. INVENTORY CONTROL POINT/INTEGRATED MATERIEL MANAGER 

MATERIEL RECEIPT STATUS (DI FTZ)

 C9.14.1. The ICP/IMM will prepare DI FTZ documents using AP3.42 to provide reporting 

activities with notification of materiel receipt or nonreceipt on returns. The DI FTZ will be 

provided upon processing of the receipt for other than suspended condition materiel, or upon 

processing of inventory adjustment action moving assets from suspended condition to correct 

condition, or not less than 30 days after DI FT6 when no receipt or DI FTM has been processed. 

Multiple DI FTZ documents will be provided when a single shipment is received in more than 

one materiel condition. Use status codes in the DI FTZ documents as follows: 

 C9.14.1.1. Enter Status Code TN when credit is granted for the condition and 

quantity of materiel received. 

 C9.14.1.2. Enter Status Code TM when reduced or no credit is allowed because the 

condition of materiel received is less than that authorized for return. 

 C9.14.1.3. Enter Status Code TL when the materiel received is other than that 

authorized for return and no credit is allowed. 

 C9.14.1.4. 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. 

 C9.14.1.5. Enter Status Code TQ when the materiel has been received for an 

authorized noncreditable return. 

 C9.14.2. DI FTZ will always reflect the document number, including the suffix code, 

contained in the DI FTA or FTR. When multiple DI FTZ documents are required for materiel 

received in different conditions, each DI FTZ produced will retain the document number and 

suffix of the DI FTA/FTR. 

C9.15. PROCESSING OF SHIPMENT STATUS (DI FTM)

 C9.15.1. Shipment status provides information and normally requires no subsequent 

generation of documentation. ICPs/IMMs will receive the DI FTM shipment status and update 

appropriate ICP/IMM records. The shipment date indicated in the DI FTM is available to 

ICPs/IMMs to verify intransit status and provide information on expected receipts. DI FTMs 

received for items not under the cognizance of the ICP/IMM will be rejected to the reporting 

activity using DI FTR with reject Status Code SC. DI FTMs which do not pass data field validity 

checks will be rejected to the reporting activity using DI FTR with the appropriate S_ series status 

code. 

 C9.15.2. In the event that the ICP/IMM requires advice of shipment to support related 

supply decisions and the DI FTM has not been received, an ICP/IMM follow-up (DI FT6) will be 

prepared using AP3.41 and forwarded to the reporting activity. The DI FT6 will not be generated 

until at least five days have elapsed from the transmission of the DI FTR (PD 03) or 50 days (PD 

13) and no DI FTM nor receipt has been posted. A DI FT6 with Status Code T3 may be 

generated upon expiration of the due-in timeframe when a DI FTM has been received, but receipt 
Page 11 

PDC 208 

MILSTRIP Chap 9 Procedures 

has not been posted.12 The ICP/IMM is authorized to follow up without regard to the established 

timeframe when the need arises to satisfy PD 01-08 requirements. 

C9.16. PROCESSING FOLLOW-UPS FROM REPORTING ACTIVITIES (DI FTF/FTT/FTP)

 C9.16.1. Follow-ups submitted by reporting activities consist of three types: 

 C9.16.1.1. Follow-up for ICP/IMM Reply Customer Asset Report (DI FTF). 

 C9.16.1.2. Follow-up for ICP/IMM Materiel Receipt Status (DI FTT). 

 C9.16.1.3. Follow-up for Credit (DI FTP). 

 C9.16.2. On receipt of a DI FTF, the ICP/IMM will determine if there is a record 

indicating that the original DI FTE was received. 

 C9.16.2.1. If a record is established and a DI FTD indicating delayed response was 

furnished to the customer, a duplicate DI FTD or FTR will be provided. If a record is established 

and a DI code FTD or FTR was not provided, one of the following actions will be initiated 

 C9.16.2.1.1. If the DI FTE transaction is in process, a DI FTD will be 

provided to the customer with Status Code TR in rp 65-66 indicating the DI FTE is in process and 

a DI FTR will be provided at a later date. 

 C9.16.2.1.2. If the DI FTE was rejected by the ICP/IMM as invalid, the DI 

FTF will produce a DI FTR to the reporting activity with the same status code utilized in the 

original DI FTR. 

 C9.16.2.2. If no record of receipt of the DI FTE exists, the ICP will process the DI 

FTF as a new DI FTE and provide a DI FTR, as appropriate, to the reporting activity. 

 C9.16.3. On receipt of a DI FTT, the ICP/IMM will review records and take action as 

follows: 

 C9.16.3.1. If the record indicates materiel has been received and classified, a DI FTZ 

will be transmitted to the customer. 

 C9.16.3.2. If the records indicate that materiel has been received but not classified, 

the ICP/IMM will provide a DI FTR with Status Code TT to the customer. 

 C9.16.3.3. If the records indicate that materiel has not been received, and if materiel 

is not located after investigation, the reporting activity will be furnished a DI FTR with Status 

Code TU. 

 C9.16.4. On receipt of a DI FTP, the ICP/IMM will take action under MILSBILLS. 

 C9.16.5. DI FTF received for items not under the cognizance of the ICP/IMM will be 

rejected to the reporting activity using DI FTR with reject Status Code SC. A DI FTF which does 

not pass data field validity edits will be rejected to the reporting activity using the DI FTR with an 

appropriate reject status code. 

 

12 See Footnote 3. 
Page 12 

PDC 208 

MILSTRIP Chap 9 Procedures 

C9.17. CANCELLATION OF CUSTOMER ASSET REPORTS (DI FTC/FTZ)

 C9.17.1. Upon receipt of customer cancellation (DI FTC), the ICP/IMM will take 

necessary action to cancel or reduce the quantity in all applicable transactions affected by the DI 

FTC including decision to return, due-in record, PMR, and credit suspense, if applicable. 

 C9.17.2. The ICP/IMM will initiate cancellation action (DI FTZ) when materiel is not 

received by the due-in EDD or when material is not received and no response has been received 

within 30 days after the DI FT6 follow-up. The ICP/IMM will also initiate cancellation action 

when a DI FTM is not received within 120 (CONUS) or 180 (OCONUS) days after the receipt of 

the DI FTL.

 C9.17.3. Cancellations initiated by the ICP/IMM or in response to a DI FTC will be 

accomplished as follows: 

 C9.17.3.1. For creditable returns, notification of cancellation to the reporting activity 

will be made using DI FTZ with Status Code TP. 

 C9.17.3.2. For noncreditable returns, notification of cancellation to the reporting 

activity will be made using DI FTZ with Status Code TV. 

 C9.17.4. When a DI FTM or FTL has been received, but material has not been received 

within timeframe allotted under C9.13.2.1, action to cancel the due-in and PMR will be 

accomplished under MILSTRAP.

C9.18. INVENTORY CONTROL POINT/INTREGRATED MATERIEL MANAGER 

PROCESSING OF DI FTE/FTC/FTF TRANSACTIONS WHEN SUPPLY SOURCE HAS 

CHANGED

 C9.18.1. Upon receipt of a DI FTE, FTC, or FTF transaction from DAAS with Advice 

Code 3T when the supply source has been changed, the losing ICP/IMM will arrange to change 

the FLIS and DAAS supply source files. 

 C9.18.2. The losing ICP/IMM will then prepare and transmit through DAAS DIs FTE, 

FTC, and/or FTF transactions containing Advice Code 3U to the gaining supply source in rp 4-6. 

 C9.18.3. DAAS will pass the DI FTE, FTC, or FTF transactions to the gaining supply 

source. 

C9.19. INVENTORY CONTROL POINT/INTEGRATED MATERIEL MANAGER LATERAL 

REDISTRIBUTION OF RETAIL ASSETS (DI A4_/AE6/AF6/AS6)

 C9.19.1. This paragraph outlines procedures for filling backorders by generating lateral 

redistribution orders for retail materiel that has been identified through Inter- or Intra-Service 

retail asset visibility systems. Service/Agencies may elect to exclude GFM, SA, and CFM 

backorders from these procedures under the DoD 4140.1-R procedures. 

 C9.19.2. If a backorder is to be supplied by lateral redistribution of materiel identified by 

an Inter- or Intra-Service retail asset visibility system, the LRO will contain appropriate data from 

the requisition, DI A4_ in rp 1-3, the RI of the reporting activity in rp 4-6, Distribution Code 2 for 

consumable materiel or Distribution Code 3 for reparable materiel in rp 54, and the ICP/IMM’s 
Page 13 

PDC 208 

MILSTRIP Chap 9 Procedures 

RI in rp 74-76. The LRO will be forwarded through DAAS to the reporting activity. A DI AE6 

with BA status will be provided to eligible status recipients. LROs for lateral redistribution of 

retail assets will be prepared in the AP3.24 format. 

 C9.19.3. The reporting activity will: 

 C9.19.3.1. Process the LRO on a fill and kill basis. Provide DI AE6/BA status for 

the quantity being filled and/or CB status for the quantity not being filled (killed) to the activity 

identified in rp 74-76 of the LRO and include Distribution Code 2 or 3 in rp 54. 

 C9.19.3.2. Substitutions (I&S) are allowed if the requiring/requisitioning activity 

and the supplying/holding activity are the same Service. Do not substitute if the 

requiring/requisitioning activity and the supplying/holding activity are different Services. 

C9.19.3.3. Ensure materiel is shipped, using DD Form 1348-1A or DD Form 1348-2, to the 

activity identified in the LRO as the “ship-to” addressee. When the materiel is shipped, transmit 

a DI AS6 to the activity identified in rp 74-76 of the LRO. The DI AS6 will include the 

DoDAAC (rp 45-50) and fund code (rp 52-53) of the activity to which the credit for the materiel 

and reimbursement for the PCH&T costs are to be provided, Signal Code B (rp 51), and 

Distribution Code 2 or 3 (rp 54). Retail activities will use UMMIPS time standards for 

processing LROs directed by the ICP/IMM. Refer to DoD 4140.1-R Appendix AP8, UMMIPS 

time Standards (published electronically at http://198.3.128.177/supreg/).

 C9.19.3.4. Establish internal records to receive credit for the materiel and 

reimbursement for the PCH&T costs and not generate billing transactions. 

 C9.19.4. The ICP/IMM will: 

 C9.19.4.1. Utilize the DI AE6 with BA status and Distribution Code 2 or 3 in rp 54 

to update estimated ship dates. 

 C9.19.4.2. Generate DI AF6 follow-up with Distribution Code 2 or 3 in rp 54 to the 

reporting activity as follows: 

 C9.19.4.2.1. When the initial supply status (BA or CB status) is not received 

on LROs within 10 days. 

 C9.19.4.2.2. Upon receipt of BA supply status without an ESD and 10 days 

have elapsed since the transaction date of the DI AE6/BA status. 

 C9.19.4.2.3. Upon receipt of BA supply status with an ESD and the ESD has 

expired. 

 C9.19.4.2.4. When no response is received to the previous follow-up and 10 

days have elapsed. Continue to follow-up until status is received, backorder is re-established, or 

final disposition is determined. 

 C9.19.5. Reinstate the requisition and provide appropriate status to eligible status 

recipients upon receipt of DI AE6/CB status with Distribution Code 2 or 3 in rp 54. 

 C9.19.6. Upon receipt of the DI AS6 with Distribution Code 2 or 3 in rp 54, generate 

billing transactions to the requisitioner and provide crediting transactions for the materiel and 
Page 14 

PDC 208 

MILSTRIP Chap 9 Procedures 

PCH&T, under the procedures of MILSBILLS, to the activity identified in rp 45-50 of the DI 

AS6. In addition, the ICP/IMM will generate a DI AS8 shipment status transaction to DAAS. 

 C9.19.7. When creating customer supply status transactions as a result of processing DI 

AE6/AS6 transactions with Distribution Code 2 or 3 in rp 54, always use the distribution code 

which was in the original requisition. 
Page 1 of 2 

PDC 208 

Enclosure 4 

DLMS, Volume 2 Procedures 

ENCLOSURE 4 TO ADC 224, 

REVISED PROCEDURES FOR LOGISTICS 

ACCOUNTABILITY DURING MAINTENANCE 

DLMS PROCEDURES

Revise DLMS, Volume 2, Chapter 5, as shown in the extracts below: ADC 224 changes 

are shown in bold italics. Red text identifies changes under PDC 224, DLMS Shipment 

Status Enhancements: Secondary Transportation Number, Initial Shipping Activity, 

Carrier Identification, and Port of Embarkation (POE), dated June 28, 2006 . 

C5.2 SUPPLY AND SHIPMENT STATUS - GENERAL

 C5.2.1. Status Data. Status data is either supply status or shipment status. Supply 

sources to include ICP/IMM and shipping activities prepare status transactions using the 

applicable transaction described under paragraphs C5.2.2. and C5.2.3., below. Status 

documents from supply sources are forwarded to 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, distribution depots, control offices, and/or monitoring activities. For SA 

shipment status, the control office or monitoring activity receives the status from the 

supply source and provides it to the appropriate country status recipient. For FMS 

customers, the status goes to the Military Assistance Program Address Directory 

(MAPAD) Type of Assistance Code (TAC) 4 country status recipient. For MAP/GA 

customers, the status goes to the MAPAD TAC 3 country/in-country security assistance 

organization (SAO) status recipient. 

(additional text not shown) 

C5.2.3. Types of Shipment Status

 C5.2.3.1 Shipment Status. Shipment status informs organizations of the 

actual shipping dates (such as the date released to the carrier), the release criteria for 

shipments, or shipment delay notifications. It also provides for an interface with 

transportation and for shipment tracing by organizations under DoD 4500.9-M. The 

shipment status may be provided by the shipping activity or by the supply source using 

the DLMS Supplement 856S. Maintenance activities (organic and commercial) will 

provide shipment notification to the receiving activity and other interested parties when 

material is shipped to the distribution depot or DRMO. This may be accomplished 

using either the Shipment Status 856S or the Advance Shipment Notice 856.13 

 

13 Business rules for use of the 856 for Government Furnished Property or Property Transfer, including 

internal DoD transfers, are still evolving. Refer to the Defense Procurement and Acquisition policy for 

UID available at url: http://www.acq.osd.mil/dpap/UID/. Specific applicability and interoperability issues 

to be resolved by the UID Program Office and DUSD(L&MR)SCI. 
Page 2 of 2 

PDC 208 

Enclosure 4 

DLMS, Volume 2 Procedures 

Shipment status provided by shipping activities will reflect enhanced data content under 

DLMS and support DoD initiatives for unique identification and asset visibility as listed 

below. Shipment status provided by the supply source will include enhanced data content 

when available. 

 

 C5.2.1.2.1 Passive Radio Frequency Identification (RFID) for the shipment 

unit/case/pallet associated at the requisition document number level. 

 C5.2.1.2.2 For Unique Item Tracking (UIT) purposes, the Item Unique 

Identification (IUID) and/or serial number. Serial number without applicable IUID may 

only be used during MILS/DLMS transition and pending implementation of IUID 

capability. Additional UID information as identified in the DS 856S is optional. Refer to 

chapter 19 for UIT guidance. 

 C5.2.1.2.3 Both the TCN and a secondary transportation number, such as the 

small package carrier number, when this is applicable. 

 C5.2.1.2.4 Identification of the carrier when other than United States Postal 

Service (USPS) by Standard Carrier Alpha Code (SCAC). 

 C5.2.1.2.3 Identification of the initial DoD shipping activity (origin) by 

DODAAC. 

 C5.2.1.2.4 For Outside Continental United States (OCONUS) shipments made via 

Defense Transportation System (DTS), GBL/CBL, parcel post, and small package carrier 

shipments, specific identification of the Port of Embarkation (POE) or Consolidation and 

Containerization Point (CCP). The shipment status will specify air terminal, water 

terminal, or CCP by applicable qualifier code in the DS. (During MILS/DLMS 

transition, DAAS may substitute a generic terminal qualifier for shipment status 

transactions converted from MILS where the type of facility is unknown.)