Attachment, ADC 436 

Page 1 

ATTACHMENT TO ADC 436 

Administrative Revisions to DLMS Supplements to Remove Obsolete RI “Streamline” Notes and 

Update MILSTRIP/DLMS Documentation Associated with RI 

1. ORIGINATOR: 

a. Service/Agency: DLA Logistics Management Standards, J627 

b. Originator: Ms. Ellen Hilert, DLA J-627, Supply Process Review Committee Chair, e-mail 

Ellen.Hilert@dla.mil 

2. FUNCTIONAL AREA: Primary: Supply/MILSTRIP; Secondary: DoD Activity Address 

Directory (DoDAAD)

3. REFERENCES: 

a. DOD 4000.25-1-M, MILSTRIP, Appendix 2.3, Routing Identifier Codes. 

b. DOD 4000.25-M, DLMS Manual: 

(1) Volume 1, Concepts and Procedures, Chapter 1, Introduction. 

(2) DLMS Supplements. Transaction formats are available at http://www.dla.mil/j6/dlmso/elibrary/TransFormats/140_997.asp

4. BACKGROUND: 

a. DOD 4000.25-M Volume 1, Chapter 1 describes the concept for future streamlining of data 

elements carried in the MILS legacy transactions formats that would eventually be phased out under 

DLMS. This concept is documented as follows: “C1.7.1.2 Future Streamlined DLSS Data. The 

DLMS procedures and the supporting DSs identify DLSS data targeted for elimination under a full 

DLMS environment. This data is often referred to as future streamlined data. This data is retained 

within DLMS during a transition period when many trading partners employ legacy systems or 

cannot move to full DLMS capability. DOD Components wishing to eliminate streamlined data 

must coordinate with DLMSO prior to doing so. Components are encouraged to submit a PDC 

reflecting any revised business rules associated with such termination.” 

b. The original DLMS implementation strategy identified the Routing Identifier Code (RIC) (also 

referred to as Routing Identifier (RI)) as a target for future streamlining to be replaced by the DoD 

Activity Address Code (DoDAAC) (or potentially another form of identifier). As a result, many 

DLMS Supplements include notes cautioning users that the RIC may be replaced under DLMS. This 

note is now obsolete. There is no recognized initiative to discontinue use of the RIC in association 

with DLMS implementation.
Attachment, ADC 436 

Page 2 

5. REQUESTED CHANGE: 

a. Description of Change: 

(1) Administrative change to update RIC field note in the DLMS to remove obsolete references 

to future streamlining.

(2) Administrative update to the RIC assignment rules to reflect Washington Headquarter 

Service (WHS) is now responsible for update of “Other DoD DoDAACs (H series)”.

b. Procedures: 

(1) This PDC revises the following DLMS Supplements to remove the obsolete streamline 

notes: 140A, 180M, 511R, 511M, 517G, 517M, 527D, 527R, 536L, 650A, 650C, 810L, 812L, 812R, 

824R, 830D, 830R, 830W, 846A, 846D, 846F, 846I, 846L, 846P, 846R, 846S, 856R, 856S, 867D, 

867I, 869C, 869F, 870L, 870M, 870N, 870S, 888A, 888I, 940R, 945A, and 947I as shown in 

Enclosure 1. 

(2) This PDC revises MILSTRIP Appendix 2.3, Routing Identifier Codes, to reflect the WHS 

designation as shown in Enclosure 2. Additional administrative updates are identified including 

removal of incorrect wording regarding use of numeric routing identifiers (GSA owns and uses 

numeric RICs) and update to the hyperlink/URL for the location of Service/Agency (S/A) RIC 

monitors.

5. REASON FOR CHANGE: The changes included in this document are for administrative 

purposes. The documentation is being updated to reflect the current processes. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Accurate reporting of DLMS processing. 

b. Disadvantages: None known 

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Upon publication.

8. IMPACT: 

a. DLMS Data Elements: There are no new or revised data elements associated with this change. 

b. DLMS Supplement Revisions: There is no impact on programming. All DLMS Supplement 

revisions are administrative. 

 c. Publications: MILSTRIP revisions are shown in Enclosure 2.
ADC 436 

Enclosure 1, Page 1 

Enclosure 1, DLMS Supplement Revisions 

Item # Location Revision Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 436 to DLMS Introductory notes to each updated DS:

- ADC 436, Administrative Revisions to DLMS Supplements 

to Remove Obsolete Routing Identifier Code (RIC) 

“Streamline” Notes and Update MILSTRIP/DLMS 

Documentation Associated with Routing Identifiers. 

Identifies DLMS 

Changes included in the 

DLMS Supplement 

2. See table 

below for 

specific DS 

locations 

Remove DLMS notes for code M4:

M4 Department of Defense Routing Identifier Code (RIC) 

DLMS Note: 1. The RIC is retained in the DLMS to facilitate 

transaction conversion in a mixed DLSS/DLMS environment. 

Continued support of the RIC in a full DLMS environment will 

be assessed at a future date. Typically under the DLMS, the RIC 

will be replaced with a DoDAAC or a commercial identifier.

2. Future streamlined data; see introductory DLMS note 3c.

Removes obsolete notes. 

DLMS Supplements to remove “future streamlined” DLMS notes from RIC field 

Item # Location Revised DLMS Supplement 

1. 1/N103/40 

2/N103/20 

140A 

Small Arms Reporting 

2. 1/N103/120 

2/N103/60 

180M 

Material Returns Reporting 

3. 1/N103/70 

2/N103/180 

511M 

Requisition (Modification) 

4. 1/N103/70 

2/N103/180 

511R 

Requisition 

5. 1/N103/60 

2/N103/90 

517G 

Government Furnished Material (GFM) Validation 

6. 1/N103/60 517M 

Material Obligation Validation (MOV) 

7. 1/N103/70 

2/N103/210 

527R 

Receipt, Inquiry, Response and MRA 

8. 1/N103/70 

2/N103/210 

2/N103/320 

527D 

Due-in, Advance Receipt, Due Verification

9. 1N103/70 

2/PWK05/150 

2/N103/190 

536L 

Logistics Reassignment Management Data 

10. 1/N103/0500 4030 650A 

Assembly Component Maintenance Structure 
ADC 436 

Enclosure 1, Page 2 

11. 1/N103/0500 4030 650C 

Component Packing Confirmation 

12. 1/N103/70 

2/N103/240 

810L 

Logistics Bill 

13. 1/N103/100 812L 

Logistics Bill Adjustment Request Reply 

14. 1/N103/100 812R 

Logistics Bill Adjustment Request 

15. 1/N103/030 

2/NM108/065 

824R 

Reject Advice 

16. 2/N103/3200 4030 830D 

Demand Data Exchange (DDE) Projected Supply Plan 

17. 1/N103/230 

2/N103/320 

830R 

Special Program Requirements 

18. 1/N103/230 

2/N103/320 

830W 

War Material Requirements 

19. 1/N103/80 

2/N103/450 

846A 

Asset Reclassification 

20. 1/N103/80 

2/N103/450 

846D 

Logistics Reassignment Transfer and Decapitalization 

21. 1/N103/80 

2/N103/450 

846F 

Ammunition Freeze/Unfreeze 

22. 1/N103/80 

2/N103/450 

846I 

Asset Status Inquiry/ Report 

23. 1/N103/80 

2/N103/450 

846L 

Logistics Asset Support Estimate (LASE) 

24. 1/N103/80 

2/N103/450 

846P 

Physical Inventory Request 

25. 1/N103/80 846R 

Location Reconciliation Request 

26. 1/N103/80 

2/N103/450 

846S 

Logistics Reassignment Storage Information Order/Reply 

27. 2/N103/220 856R 

Shipment Status Material Returns 

28. 2/N103/2200 856S 

Shipment Status 

29. 1/N103/80 

2/N103/50 

867D 

 Demand Reporting 

30. 1/N103/80 867I 
ADC 436 

Enclosure 1, Page 3 

2/N103/50 Issue 

31. 2/N103/110 869C 

Requisition Cancellation 

32. 2/N103/110 869F 

Requisition Follow-Up 

33. 1/N103/50 

2/N103/90 

870L 

Special Program Requirement (SPR) / Logistics Asset Support Estimate 

(LASE) Notification 

34. 1/N103/50 

2/N103/90 

870M 

Materiel Returns Supply Status 

35. 2/N103/90 870N 

Notice of Availability Reply 

36. 1/N103/50 

2/N103/90 

870S 

Supply Status 

37. 1/N103/20 

2/N103/156 

888A 

Small Arms & Light Weapons (SA/LW) Data Change 

38. 1/N103/20 

2/N103/156 

888I 

Storage Item Correction 

39. 1/N103/0400 

2/N103/1100 

940R 

Material Release 

40. 1//N103/40 

2/N103/80 

945A 

Material Release Advice 

41. 1/N103/0400 

2/N103/1100 

947I (4010 & 4030) 

Inventory Adjustment 
ADC 436 

Enclosure 2, Page 1 

Enclosure 2, MILSTRIP Manual Update 

Revise DOD 4000.25-1-M Appendix 2.3 as follows: 

Staffing note: URLs for DLMS and DLA Transaction Services web sites are being revised and will 

be updated prior to formal publication. 

AP2.3. APPENDIX 2.3

ROUTING IDENTIFIER CODES

AP2.3.1. RIs (located in rp 4-6, 67-69, and 74-76 of transactions) are assigned by S/As for processing 

inter-S/A, and intra-S/A logistical transactions. The codes serve multiple purposes in that they are 

supply source codes, inter-system routing codes, intra-system routing codes and consignor (shipper) 

codes. DAASC DLA Transaction Services maintains an electronic database of these codes which are

that is accessible from their website1 https://www.transactionservices.dla.mil/DAASINQ/. 

AP2.3.2. To qualify for assignment of an RI, the facility/activity must be an integral and 

predetermined element of an established logistical system and must perform a general logistical 

control, distribution and/or storage mission (to include bases, posts, camps, and stations, when 

applicable). 

AP2.3.3. The use of an RI on any one document does not infer, imply, or intend that follow-on 

documentation resulting there from must contain the same RI or any element thereof. It is a 

fundamental premise of MILSTRIP that any RI serves as only one of the following: 

 AP2.3.3.1. An address to indicate the intended recipient of the document for logistical actions. 

 AP2.3.3.2. Identify the actual consignor (shipper) on supply type release/receipt transactions 

originated within the distribution system(s). 

AP2.3.4. The system does not list or recognize any codes containing “numerics” in the first position. 

Codes of this category are reserved and are not to be used or considered as RIs within the meaning of 

MILSTRIP.

AP2.3.4. All authorized Military Service RIs will contain one of the characters depicting Service 

assignment as listed in MILSTRIP AP2.2., in the first position. 

AP2.3.5. The second2 and third positions may be in any combination of alphanumerics. These 

positions may identify either a facility or activity of the S/A depicted by the first position. 

 

1

DAASC DLA Transaction Services requires a user authorization to obtain information from their website. If you do not 

currently have approved access DAAS (user id and password), please complete a request for access by going to the 

following DAASC website: https://www.transactionservices.dla.mil/sar/sar_menu.asp . 

2

Y in second position identifies United States Coast Guard contractor use only when first position is Z. 
ADC 436 

Enclosure 2, Page 2 

AP2.3.6. Each S/A is responsible for the assignment of RIs to its facilities and activities. An S/A 

which has activities located at another S/A facility will assign its own RI to the activity. An S/A 

which has assets located at another S/A facility will use the RI assigned by the S/A owning/operating 

the facility. (An appropriate RI may be assigned to identify these assets when requested by the S/A 

owning the assets.) The DoD MILSTRIP System Administrator Washington Headquarters Service 

(WHS) will make RI H_ series assignments for “Other DOD Activities.” 

AP2.3.7. Each S/A will designate a coordinator with responsibilities to control, monitor, and 

submit/validate all RI additions, revisions, and deletions relative to its S/A. In most cases the 

DoDAAC and RIC coordinators (or monitors) are the same. The S/A coordinators established for 

assignment of RIs are available at: https://www.dla.mil/j6/dlmso/CertAccess/SvcPointsPOC/ServicePoints/DoDAAC_DOD_Monitors.pdf.

AP2.3.1. Each S/A coordinator will ensure currency in code assignments. Additional assignments, 

revisions, and/or deletions of RI codes, with exception of H_ series will be submitted to the DAASC. 

RI Code H_ assignments will be submitted to DLMSO. The DAASC will monitor RI code assignment 

for compliance with the above assignment rules. 

AP2.3.9. The DAASC DLA Transaction Services maintains the RI database and serves as the focal 

point for receipt of all RI database revisions. The DLA Transactions Services shall monitor RI code 

assignment for compliance with the above assignment rules. The RI database is published 

electronically and updated from requests for additions, changes, and/or deletions as submitted by the 

Component RI coordinators. Interested parties may interrogate the RI database through the DAASC

DLA Transaction Services website3

 at https://www.transactionservices.dla.mil/DAASINQ/ . 

Activities desiring e-mail notification of new RI code assignments, revisions, and/or deletions may 

request this service from DAASC.

 

3

 See Footnote 1.