1 of 2

Attachment

ADC 61

Approved DLMS Change (ADC) 61 

Optional Use of Purpose Code in Asset Status

Reporting and Lateral Redistribution Orders

(Document Identifier Codes DZF and A4_)

1. ORIGINATOR

a. Service/Agency: DLA

b. Originator: Mr. Robert Vitko, DLA/J3322

2. FUNCTIONAL AREA: Supply

3. REQUESTED CHANGE

a. Title: Optional Use of Purpose Code in Asset Status Reporting and Lateral 

Redistribution Orders (LRO) (Document Identifier (DI) Codes DZF and A4_)

b. Description of Change: This change provides for optional inter-Component use of 

the purpose code in Asset Status Reporting, DI Code DZF, and Lateral 

Redistribution Order, DI Code A4_, transactions. Use of the data on an interComponent basis, would require agreement by the Components involved. This 

change also addresses impact to corresponding DLMS equivalent transactions: 

846I, Asset Status Inquiry/Report and 940R, Material Release.

c. Procedures: 

(1) Revise MILSTRAP DI Code DZF to provide for optional use of the purpose 

code in record positions 54 and 63, as shown in Enclosure 1.

(2) No revision is required to the DLMS Supplement to the 846I Federal 

implementation convention (IC). The purpose code is already available in the 

846I in the LM loop at 2/LQ01/376. The purpose code was previously mapped to 

the 846I in support of the MILSTRAP DI Code DZA, Asset Status transaction, 

requirement for a purpose code. 

(3) Revise MILSTRIP DI Code A4_ for LRO to provide optional use of the 

purpose code derived from the DZF.

(4) No revision is required to the DLMS Supplement to the 940R Federal IC as

changes associated with the requirement were previously addressed under 

Approved DLMS Change 48.

d. Alternatives: None known.

4. REASON FOR CHANGE: During recent meetings between DLA and Army on 

interfacing In-Storage Visibility (ISV) procedures under the Single Stock Fund (SSF) 
2 of 2

Attachment

ADC 61

concept, the Army indicated that the lateral redistribution orders (LROs) DLA sends to 

Army ICPs must contain the purpose code, or the denial rate would be significant. In 

order for DLA to cite the correct purpose code on LROs as Army requires, DLA must 

receive the information from Army on the Document Identifier (DI) Code DZF 

transactions. The Army currently provides purpose code data on an intra-Service basis 

in record position (rp) 54 and rp 63 multiuse fields of DI Code DZF. DLA and Army 

agreed that using these data fields on an inter-service basis was a logical solution to this 

problem. DLA agreed to work with DLMSO and the Supply Process Review Committee 

(PRC) to incorporate the requirement into the DLMS and MILS transactions. Once 

approved, Army agreed to work with their Amy Total Asset Visibility (ATAV) process to 

generate the DZF transactions to DLA with a purpose code. DLA notes that the 

interface with Army SSF is not currently in place and the DZF transactions which DLA

currently receives from Army are blank in rp 54 and 63 as required by current 

MILSTRAP restrictions for inter-Component use. This change proposes modifying that 

restriction to allow for optional entry of the purpose code in inter-Service DZF 

transactions, when agreed to by the Components. 

5. ADVANTAGES AND DISADVANTAGES 

a. Advantages: 

• Under the Army SSF concept, providing the purpose code on the 

DZF/846I optimizes the resulting LRO interface process by identifying the 

assets being directed for issue by the purpose code under which they 

appear on the Army Commodity Command Standard System (CCSS) and 

Standard Army Retail Supply System (SARSS) asset balance files, thereby 

reducing the potential for denials.

• Satisfies a known requirement with no impact except on those 

Components requiring the change. 

b. Disadvantages: None known.

6. IMPACT

a. Data Content/Procedures: Revise the DoD 4000.25-2-M (MILSTRAP) format 

for DI Code DZF, Asset Status Reporting (Base, Post, Camp, and Station Level 

Use) as shown in Enclosure 1. Revise the DoD 4000.25-1-M (MILSTRIP) format 

for DI Code A4_, Referral Order/Lateral Redistribution Order for Retail Assets as 

shown in Enclosure 2. Changes are identified by bold/italicized text. 

b. Publication(s): Revise MILSTRAP/MILSTRIP, and related Service/Agency 

publications if applicable, to reflect the change to the DI Code DZF/A4_ format.
DoD 4000.25-2-M

1 of 3

Enclosure 1

ADC 61

AP3.61 APPENDIX 3.61

ASSET STATUS REPORTING (BASE, POST, CAMP, 

AND STATION LEVEL USE)

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 1-3 Enter DI Code DZF.

Routing Identifier (TO) 4-6 Enter the RI code of the activity to which this 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 RI code of the owning activity to 

which any resulting MILSTRIP DI Code A4_ Lateral 

Redistribution Orders are to be sent; otherwise enter RI 

code of the activity preparing this transaction (FROM RI 

Code).

Routing Identifier 

(Storage Activity) 

34-36 Enter the code of storage activity at which item is stored, 

if different from record 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.

Quantity (Requisitioning 

Objective)

41-46 When rp 7 = N, enter total system RO for RI code in rp 

31-33; if multiple transactions with the same rp 31-33 RI 

code are generated for the same NSN, each will reflect 

the same RO.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.

 

1

For Air Force Secondary Inventory Control Activities (SICAs) which own their Services= wholesale and retail 

assets, only DI Code DZFs with the same RI code in rps 31-33 for the same NSN, and 01 entry in rps 79-80 will 

contain the same SICA total system RO. DI Code DZFs with the SICA RI code in rp 31-33 without a 01 entry in 

rps 79-80 will contain the RO for the RI code in rps 34-36.
DoD 4000.25-2-M

2 of 3

Enclosure 1

ADC 61

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

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, leave blank

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 supply condition code of quantity on hand reported 

in record positions 56-61.

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 RI code in rps 31-33 (if no RI code is present in 

rps 34-36) or the quantity on-hand for the RI code in rps 

34-36 if both RI codes 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.

 

2

 For all Service Secondary Inventory Control Activities (less Air Force): If both rps 31-33 and rps 34-36 contain 

RI codes, then the recipient must add the on-hand quantity on all the DI Code DZF transactions, for the reported 

NSN, that have the same RI code in rps 31-33. This aggregate on-hand quantity is then compared to the system 

RO 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 RI codes. 

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 RI code in rps 31-33. This aggregate on-hand quantity is then compared to the 

system RO contained in rp 41-46 when making Lateral Redistribution Order decisions using DoD Total Asset 

Visibility business rules.

For DZFs with only one RI code (rps 31-33) and for Air Force Secondary Inventory Control Activity DZFs with 

two RI Codes and "blanks" in rps 79-80, the on-hand quantity and RO in the individual DZF are compared when 

making Lateral Redistribution Order decisions using DoD Total Asset Visibility business rules.
DoD 4000.25-2-M

3 of 3

Enclosure 1

ADC 61

Multiuse 63 For intra-Component use, enter data prescribed by the 

Component. For inter-Component use, leave blank

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 supply condition code of quantity on hand reported 

in record positions 65-70.

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 Transactions 79-80 Enter total number of transactions being 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

 
DoD 4000.25-1-M

Enclosure 2

ADC 61

AP3.24 APPENDIX 3.24

REFERRAL ORDER/LATERAL REDISTRIBUTION

ORDER FOR RETAIL ASSETS

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 1-3 Enter DI A4_.

Routing Identifier 4-6 Enter RI of the supply source to which the 

transaction is being sent.

Media and Status 7 Enter M&S 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 FSG 13 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 document number as shown in the 

requisition.

Suffix 44 a. Enter suffix 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.

Supplementary Address 45-50 Enter data from the original requisition.

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.
DoD 4000.25-1-M

2 of 2

Enclosure 2

ADC 61

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Required Delivery Date/Required 

Delivery Period1

62-64 Enter data from the original requisition.

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 SMCA will contain code 888 in rp 67-69.

Management Data 70-71 Enter management data, as authorized. (for 

lateral redistribution orders, rp 54 equals 2 or 

3, leave rp 70 blank, enter the condition code 

in rp 71, and leave rp 72-73 blank.)

Demand Code/ 2

Management Data

72 Enter demand code from rp 44 of original 

requisition or management data as authorized. 

Note: Intra-Air Force FMS DI A4_ transactions 

may use a CLPSC (program/nonprogram) 

code in rp 72.

Management Data 73 Enter Management data, as authorized.

Routing Identifier 74-76 Enter RI applicable to the activity generating 

the transaction.

Management Data 77-80 Enter management data, as authorized.

LATERAL REDISTRIBUTION ORDER ENTRIES: Entries applicable when rp 54 equals 2 or 3:

Purpose Code 70 Enter the purpose code of the materiel 

being issued if required based on 

Service/Agency agreement (derived from DI 

Code DZF, Asset Status Reporting 

transaction); otherwise leave blank.

Condition Code 71 Enter the applicable condition code.

Blank 72-73 Leave blank.

 

1 Use of RDP for conventional ammunition last reported as not implemented by USAF. Refer to 

AMCL 148.

2 Components are authorized to defer inclusion of the demand code of the original requisition pending 

DLMS/logistics systems modernization.