**DoD 4000.25-M, Vol 2**

*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.  Transactions.  This chapter addresses the procedures applicable to the asset status reporting function using  the DLMS 846I.  The asset status reporting function is identified by the DLMS 846I Accredited Standards Committee***(***ASC) X12 beginning segment (1/BIA02/020) report type codes.  Its DLSS (MILSTRAP) legacy counterpart identified by document identifier codes (DIC), is included for information purposes to allow for processing in a mixed DLMS/DLSS environment.  Other formats such as Extensible Markup Langauage (XML) are also available See the Defense Enterprise Data Standards Website for available formats on the DLMS IC page.

		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.1.2.1.1.  Request for Asset Status Report is identified by Report Type Code TI–Asset Status Inquiry.  This transaction provides MILSTRAP legacy DIC DZE functionality, which was sent from an inventory control point (ICP) to Military Service designated central points to request reporting from bases, posts, camps and stations.

			C22.1.2.1.2.  Asset Status Report is identified by Report Type Code TJ–Asset Status Advice.  This transaction provides MILSTRAP legacy DIC DZA and DZF functionality.

C22.2.  IN STORAGE ASSETS

	C22.2.1.  Assets Within the Wholesale Distribution System

		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.2.1.2.  Asset status transactions may be used between a Component ICP and a DLA storage activity by mutual agreement.

		C22.2.1.3.  Under MILSTRAP, due to the number of record positions in DIC DZA devoted to entries prescribed by the DoD Components for use within Component 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.2.3.  Transmit Request for Asset Status Report Transactions to central points designated by DoD Components.  Each DoD Component designated activity will be responsible for notifying its reporting activities of the reporting requirements shown in the Request for Asset Status Report Transactions received from the other Components.  The Component activities designated to receive the requests are:

		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.5.  Provision is made for requesting earlier commencement of reporting by use of Asset Status Reporting Code M.  In this instance, the DoD Components’ central points will ensure that reporting commences as soon as possible after receipt of the request.

		C22.2.2.6.  When a one-time asset status report is required on an expedited basis, the Request for Asset Status Report Transaction will contain Asset Status Reporting Code Z and the date the report is required.  The DoD Component central point or the reporting activity in receipt of the request will take no further action if the date the report is required is already past.

		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.9.  Activities below the distribution system (base, post, camp, or station) will use Asset Status Report Transactions to report assets to the requesting ICP.  Report on hand balances by each separate supply condition of held materiel.  Under the constraints of the MILSTRAP fixed length format, the DIC DZF Asset Status Report Transaction is designed to provide for use of multiple transactions when either or both of the following apply:

			C22.2.2.9.1.  More than two supply conditions of materiel are held.

			C22.2.2.9.2.  Requisitioning objective, due-in, or reserved quantities exceed 999,999.

		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.  INTRA-COMPONENT USE

	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.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.1.2.  When used during a logistics reassignment outside the Army by the losing item manager, the Asset Status Report Transaction informs the Army manager for Non-Army Managed Items (NAMI) of the requisitioning objective and safety level to be set in their systems to be able to monitor and maintain the single stock fund stocking levels.

	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.

2

**C**

C22-4	CHAPTER 22