Attachment, ADC 426 

 Page 2 

ATTACHMENT TO ADC 426 

Revise DLMS Supplement (DS) 511R, Requisition to Address Requirements of Navy 

Usage of Warehouse RIC in Multiuse Field of A0_ (Requisition) 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: NAVSUP 

ERP Supply Chain Team, NAVSUP E3, DSN 430-5070, commercial (717) 605-5070

2. FUNCTIONAL AREA: Primary/Secondary Functional Area: Supply 

3. BACKGROUND: 

a. Intent of the transaction: Organizations use this transaction set to requisition 

material. 

b. Scenario for which the transaction is used: Navy organic repair facilities 

requisitioning Navy managed material. This change is associated with intra-Navy 

requisitions originating in the Commercial Asset Visibility - Organic Repairables Module 

(CAV-ORM). 

c. Procedures, transactions, data elements, processing details in use today: Legacy 

Navy organic repair systems send requisitions to the Navy Inventory Control Point (ICP) and 

Fleet Industrial Supply Centers (FISCs) requesting either that they be filled from a certain site or 

that the requisition be killed. The requisitions are sent as DI Code A0_s and the requested site’s 

Routing Identifier Code (RIC) is included in the legacy format multi-use fields.

4. PROPOSED CHANGE(S): 

a. Revise the DLMS to allow for the identification of the desired storage activity from 

which the requisitioned item is to be supplied. This change will be adopted as an intra-Navy 

DLMS enhancement in support of organic maintenance requisitioning procedures associated 

with Project Code Z5X.

 b. Revise transaction conversion mapping to perpetuate the Navy storage activity RIC 

from MILSTRIP legacy format to DLMS (see detail below). 

 c. Alternatives: None identified. 

5. REASON FOR CHANGE: Navy modernized system development is being 

programmed to be DLMS compliant. In order to support ongoing unique legacy 

requirements, the MILSTRIP DI Code A0_ storage activity RIC needs to be mapped to the 

DLMS equivalent. 

6. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages (tangible/intangible): Allows development of a DLMS compliant 

solution for the 511R functionality. 

 b. Disadvantages: None identified. 
Attachment, ADC 426 

 Page 3 

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Expected 

implementation date is June 2011. 

8. IMPACT: 

a. DOD 4000.25-M, DS 511R requires update. 

b. Defense Automatic Addressing System (DAAS) Legacy MILS/DLMS 

Conversion. DLA Transaction Services is required to translate Navy storage activity RIC on 

A0_ transactions to DLMS 511R transactions when sending them to a DLMS compliant 

Navy system. Revise MILS to DLMS mapping to add the following: If DOCID (RP 1-3) = 

A0_ and RIC To (RP4-6) = N** and the Service Code (RP 30) is N, R, or V and the Project 

Code (RP 57-59) is Z5X, then map N101=SB, N103=M4, and N104=RP 74-76. 

c. Automated Information Systems. This change is for intra-Navy use only. No 

change/impact to other Component systems, to include no change/impact to the DLA 

Distribution Standard System. 

 d. DLMS Data Elements. There are no new or revised data elements resulting from 

this proposal. 

e. Publications: MILSTRIP and DLMS format updated as shown in the enclosures.
ADC 426 

Enclosure 1, Page 1 

Enclosure 1, MILSTRIP Revisions - Requisition 

Note: Layout also reflects revisions associated with PDC 453, Revisions to Procedures and 

DLMS 511R Requisition to Support Requisitioning from DLA Disposition Services under 

Reutilization Business Integration (RBI). 

AP3.2. APPENDIX 3.2

REQUISITION

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

Send to Block A1

 Not Applicable Enter the appropriate in-the-clear 

name and address corresponding to 

the RI, if applicable. 

Requisition Is From Block B Not Applicable Enter the appropriate in-the-clear 

name and address of the requisitioner, 

if applicable. 

Document Identifier Block 1 1-3 Enter DI A0_ or AM_. 

Routing Identifier Block 2 4-6 Enter RI indicating the supply source 

to which the document is being 

submitted. 

Media and Status Block 3 7 Enter the M&S code. 

Stock Number2 Blocks 4, 5, 6 8-22 Enter the stock or part number of the 

item being requisitioned. For 

subsistence items, enter the type of 

pack in rp 21. 

Unit of Issue Block 7 23-24 Enter the unit of issue. 

 

1

See the AP2 series of appendices for an explanation of the data fields.

2

Requisitions to DRMS (RI S9D) cannot reflect an entry in rp 21-22 other than a DTID number suffix in rp 21, 

when applicable.
ADC 426 

Enclosure 1, Page 2 

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

Quantity Block 8 25-29 Enter the quantity requisitioned. For 

ammunition requisitions only (items 

in FSG 13), 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 Blocks 9-12 30-43 Enter document number as assigned 

by the preparing activity. 

Demand3

 Block 13 44 Enter the demand; otherwise, leave 

blank. 

Supplementary 

Address 

Blocks 14-15 45-50 When applicable, enter the coded 

SUPADD of the ship-to or bill-to 

activity; otherwise, leave blank. 

When coded data is not significant to 

the supply source (other than an 

AAC), enter an alphabetic “Y” in rp 

45. 

Signal Block 16 51 Enter the signal code. 

Fund Block 17 52-53 Enter the fund code as directed by the 

Component. 

Distribution Block 18 54 When applicable, enter the 

distribution code of the activity to 

receive status information in addition 

to the requisitioner or the SUPADD. 

 55-56 Enter the code as directed by the 

Components. 

Project Block 19 57-59 When applicable, enter the 

appropriate code under Component 

instructions. 

Priority Block 20 60-61 Enter priority designator. 

Required Delivery 

Date/Required 

Delivery Period4

Block 21 62-64 Enter data requirements from AP2.14, 

as applicable; otherwise, leave blank. 

 

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 rps 74-75. 
ADC 426 

Enclosure 1, Page 3 

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

Advice Block 22 65-66 Enter advice code to convey 

instructions to the supply source; 

otherwise, leave blank. 

Date of Receipt of 

Requisition5,6,7 Block 

23 

Block 23 67-69 Leave blank. 

Blank Block 23 70-80 Leave blank on inter-Component 

requisitions forwarded to the DLA 

and GSA supply sources. 

a. This field is optional for intraComponent use.8, 9, 10, 11, 12, 13,14

b. This field may be used for internal 

purposes on retained copies of 

requisitions. 

 4

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

5

 Processing Points passing DI AM_ transactions to another supply source for continued processing will enter 

their RI code in rps 67-69. 

6

 The Map Support Office Distribution System (MSODS) will enter the MSODS RI Code SD& in A0_ 

transactions returned to Mapping Agency Automated Distribution Management System (DADMS)(HM8) for 

processing. This will indicate to DADMS that this is not the initial processing of the requisition (requisition was 

previously reviewed and forwarded to MSODS, which was unable to fulfill). 

7

 On Intra-Army basis a RI code 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 rps 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 rps 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 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 and is used on both post-post and image requisitions. 

11 On Intra-Army basis requisitions may contain the date generated in rps 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 supply source identified in rp 4-6 is another Air Force base, the 

Routing Identifier of the requisitioner is identified in rp 73-75, and the Routing Identifier 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. 
ADC 426 

Enclosure 1, Page 4 

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

GOVERNMENT-FURNISHED MATERIEL REQUISITION ENTRIES.

15

Manufacturer’s 

Directive Number 

 54-56 If required by the Component 

contracts, enter the MDN. 

Contract Call Order 

Number 

 69-72 If required by the Component 

contracts, enter the appropriate 

contract call order number.

Contract Identification 73-80 At the option of the Component, enter 

the last eight positions of the PIIN in 

rp 73-80 in lieu of the MDN in rp 54-

56. This entry is mandatory if the 

MDN is not entered in rp 54-56. 

MANAGEMENT CONTROL ACTIVITY ENTRIES: Entries Required for Requisitions for 

Government-Furnished Materiel.16 

Routing Identifier 4-6 Enter the RI code of the supply 

source.

Distribution 54-56 Enter the distribution code of the 

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 74-76 If required by the Component, enter 

the RI code of the validating MCA in 

rp 74-76. 

DEFENSE REUTILIZATION AND MARKETING DLA DISPOSITION SERVICES

ENTRIES: Entries Required When Requisitioning a Specific Item From Disposal.17

 

15 Procedures to control access to DOD material inventories by defense contractors last reported as not 

implemented by USA (Retail). Refer to AMCL 1A.

16 See Footnote 6. 

17 Procedures, formats, and codes for requisitioning material from disposal last reported as not implemented by 

DLA. Refer to AMCL 139A.
ADC 426 

Enclosure 1, Page 5 

Disposal Turn-in 

Document Number or 

Excess Report Number 

67-80 This entry is optional on DI 

A01/A0A/A05/A0E requisitions and 

is mandatory on DI A04/A0D 

requisitions. If applicable, the DTID 

suffix will be entered in rp 21. 

DEFENSE REUTILIZATION AND MARKETING DLA DISPOSTION SERVICES ENTRIES: 

Entries Required on Requisitions to Disposal When a Specific Item is Not Required.18

Blank 70 Leave blank. 

Condition Code 71 Enter lowest acceptable supply 

condition code under Component 

criteria furnished to DRMS DLA 

DISPOSITION SERVICES. See 

Chapter C2, paragraph C2.21., for 

requirement. 

Blank 72-80 Leave blank. 

 

18 See Footnote 8.
ADC 426 

Enclosure 2 Page 1 

Enclosure 2, DLMS Supplement Revisions 

a. Revise DS 511R, Requisition, as shown in Change Table Below: 

# Location DS 511R Revision Reason 

1. DLMS 

Introductory 

Note 5 

Add ADC 426 to DLMS Introductory note 5:

- ADC 426, Intra-Navy DLMS 511R, Requisition, and 

940R, Redistribution Order, Inclusion of Requested 

Storage Activity 

To identify PDC/ADC in the DS. 

2. 2/N101/180 Add new DLMS note 3:

SB Storage Area 

DLMS Note: 

1. Use to identify the distribution depot/storage activity.

2. This is a restricted use applicable when a Service 

has entered into an MOA with DLA relative to Serviceowned stocks, centrally-managed/stored by DLA 

(1/BR06/020, Code RI).

3. For intra-Navy organic maintenance requisitions 

(citing Project Code Z5X), use to identify the storage 

activity from which the requisitioned item is requested. 

Refer to ADC 426. 

Expands usage for the Navy 

requirement.