ADC 363 

Attachment, Page 1 

ATTACHMENT TO ADC 363 

Revise DS 511R, Requisition to Address Requirements of Navy Usage of 

Management Code in Multiuse Field of A4_ (Referral Order/Lateral 

Redistribution Order For Retail Assets) 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

 a. Technical POC: Navy Supply Process Review Committee (SPRC) representative on 

behalf of Navy ERP, NAVSUP E4, DSN 430-7510, commercial (717) 605-7510 

 b. Functional POC: Navy SPRC representative on behalf of Navy ERP, NAVSUP E4, 

DSN 430-7510, commercial (717) 605-7510 

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

3. BACKGROUND: 

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

to another organization. 

b. Scenario for which the transaction is used: Referring a requisition to an 

inventory manager. 

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

Navy systems refer requisitions to the Navy Inventory Control Point (ICP) when the requisition 

cannot be filled by the referring system. The management code is used by the Navy to indicate 

the reason the requisition is being referred to the ICP.

4. PROPOSED CHANGE(S): Revisions which are highlighted in green were identified 

subsequent to staffing.

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

Item # Location DS 511RRevision Reason 

1. DLMS 

Introductory 

Note 5 

Add ADC 363 to DLMS Introductory note 5:

- ADC 363, Revise (DS) 511R, Requisition to 

Address Requirements of Navy Usage of 

Management Code in Multiuse Field of A4_ 

(Referral Order/Lateral Redistribution Order for 

Retail Assets). 

To identify PDC/ADC in 

the DS. 
 ADC 363 

Attachment, Page 2

Item # Location DS 511RRevision Reason 

2. 2/LQ01/140 Add DLMS notes:

84 Management Code 

DLMS Note: 

1. Authorized on an Intra-Army basis with BR02 

transaction type code A0 to provide required 

management code information in order to accurately 

process transactions relative to image and 

post-post requisitions submitted by Army Single Stock 

Fund activities (Refer to ADC 243) 

2. Authorized DLMS enhancement for BRAC IMSP. 

(Refer to ADC 352 and ADC 359) 

3. Authorized on an intra-Navy basis with BR02 

transaction type code BN to provide required 

management code information to accurately process 

transactions relative to referrals to the inventory 

manager. (Refer to ADC 363) 

To add Navy usage of 

qualifier. 

b. MILSTRIP. Revise DoD 4000.25-1-M, Appendix 3.25, Referral Order/Lateral 

Redistribution Order for Retail Assets, as follows. 

Demand Code/ 1

Management Data2

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. 

__________________ 

1 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. 

2 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. 

 c. Alternatives: None identified. 

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

programmed to be DLMS compliant. The legacy systems DI Code A4A Management Code 

needs to be mapped to the 511R/Requisition transaction. 

6. ADVANTAGES AND DISADVANTAGES: 

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

solution for the 511R functionality. 
ADC 363 

Attachment, Page 3 

 b. Disadvantages: None. 

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Expected 

implementation date is April, 2010. 

8. IMPACT: 

a. DAASC mapping. DAASC translate Navy management code on Document 

Identifier A4_ transactions to DLMS 511R transactions when sending them to a DLMS 

compliant Navy system. Revise DAASC MILS to DLMS mapping applicable to Document 

Identifier A4_ record position (RP) 72 as follows1: 

Demand Code 72 If RP1-2=A4 and RP54=2 

RP 72=I, N, O, P, R, or S

DD01=RP 72 

DD02=74 

Management Code 72 If RP1-2=A4 and RP4=N, 

P, Q, R, or V and RP30= N, 

P, Q, R, or V (intra-Navy) 

LQ01=84 

LQ02= RP 72 

Cooperative 

Logistics Program 

Support Code 

(CLPSC) 

72 If RP1-2=A4 and RP30=D 

and RP45=D (intra Air 

Force FMS) 

LQ01=89 

LQ02= RP 72 

b. Automated Information Systems This change is for intra-Navy use only. There is 

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

Distribution Standard System. 

c. DLMS Data. There is no change to DLMS data elements.

 

1

 Includes additional updates to correct mapping for demand code and CLPSC.