1 Attachment 1 

ADC 266 

USAF Lateral Requisition Routing Identifiers 

1. ORIGINATING SERVICE/AGENCY: USAF, 754 ELSG/LRS; DSN 596-2012; 

Commercial 334-416-2012

2. FUNCTIONAL AREA: 

a. Primary/Secondary Functional Area: AF Retail Supply 

b. Primary/Secondary Functional Process: Lateral Requisitioning 

3. BACKGROUND: 

a. Intent of the change: This proposed DLMS change is in support of an AF Jump Start 

program. This change supports identification of two additional routing identifiers in lateral 

requisitions to identify the DoD source of supply (as different form the lateral source of supply), and 

the requisitioner. Under the Air Force Jump Start program, AF lateral requisitions, i.e., requisitions 

submitted to another AF base, will be produced in DLMS XML using the DLMS 511R format, and 

need to perpetuate the additional routing identifier as required under AF business rules. 

b. Scenario applicable to this change: Requisitions are submitted by the AF Standard Base 

Supply System (SBSS) by an in-line (user caused) or programmatic input to fill a customer or stock 

requirement. This PDC is applicable to the following A0(x) transactions: A01, A04, A0A, A0D). 

c. Procedures, transactions, data elements, processing details in use today: Today the SBSS 

produces requisitions in MILS formats and transmits them to DAAS for routing to the source of 

supply. Under the Jump Start program, the SBSS will send the requisition transactions in DLMS XML 

format that will include data contained on the Air Force MILS transactions. 

4. APPROVED CHANGE(S): 

a. Change in detail: Under the legacy SBSS system, the Routing Identifier Codes (RIC)-From 

and the Source of Supply (SOS) RIC, are transmitted on lateral requisitions to other Air Force Bases 

(TO RIC = Dxx). The RIC-From, the requisition, is in pos 73-75 of the A0(x) and is taken from the 

Base Constants record on the SBSS database. The Source of Supply (Item Manager) RIC is located in 

positions 78-80. This value is taken from the Item Record detail on the SBSS database. This is unique 

to the Air Force and thus requires this PDC. Note: The original request to include requisition followups (DI AT_) in this revision was withdrawn. 

b. Procedures: 

(1) For AF purposes, the routing identifier of both the requisitioner and the DoD source of 

supply will be carried in the DLMS requisition format. 

(2) Update the DLMS 511R as shown: 
2 Attachment 1 

# Location Revision Reason for 

Change 

1 2/N101/180 Add new DLMS note for existing qualifier Z3: 

Z3 Potential Source of Supply 

DLMS Note: 

1. Use when requisitioning nonstandard material identified in PO106 

only with code FT or MG to identify potential supply sources. 

2. For intra-USAF lateral requisitions, use to identify the DoD 

Source of Supply (applicable when the requisition is submitted to 

another AF base). 

Establishes a new 

business rule for 

USAF lateral 

requisitions. 

Maps to rp 78-80 

of the AF lateral 

requisition. 

2 2/N101/180 Add new DLMS note for existing qualifier Z4: 

Z4 Owning Inventory Control Point 

DLMS Note: 

1. Use to indicate the source of supply owning ICP. 

2. Use to indicate DLA ICP when directing the disposition of previously 

purchased assets. This is a restricted use applicable when a Service has 

entered into an MOA with DLA relative to Service-owned stocks, 

centrally-managed/stored by DLA (1/BR06/020, Code RI). 

3. For intra-USAF lateral requisitions, the supply source will be 

another AF base (rather than the DoD “Owning ICP”). The DoD 

supply source/owning ICP will be identified as the potential source of 

supply (Code Z3). 

Establishes a new 

business rule for 

USAF lateral 

requisitions. 

Maps to rp 4-6 of 

the AF lateral 

requisition. 

3 2/N101/180 Add new DLMS note for existing qualifier OB: 

OB Ordered By 

DLMS Note: 

1. Use to identify the requisitioner when the 1/N1/070 uses code ZL 

(Party Passing The Transaction) or Code Z5 (Management Control 

Activity) to identify the transaction originator. 

2. DLMS enhancement: see introductory DLMS note 3a. Required entry 

for DLSS/DLMS conversion to support BSM. 

3. For intra-USAF lateral requisitions, use to identify the routing 

identifier of the requisitioner (this is the same requisitioner identified 

by DoDAAC at 1/N101/070 Code OB). 

Establishes a new 

business rule for 

USAF lateral 

requisitions. 

Maps to the RIFrom, rp 73-75 of 

the AF lateral 

requisition. 

c. Alternatives: 

(1) DLMSO explored alternative mapping, to include assignment of a new code for the routing 

identifier to as a retail location, rather than the DOD source of supply. This approach seemed to create 

unnecessary mapping variations for DAASC. It is illustrated above and may be reconsidered during 

staffing and evaluation. 
3 Attachment 1 

(2) DLMSO also considered requiring a new code in the beginning segment to identify lateral 

requisitions, but could not adequately justify the additional mapping change. It may be reconsidered 

during staffing and evaluation. 

5. REASON FOR CHANGE: The SBSS-generated lateral requisitions contain identification of 

requisitioned RIC and the Dodd Sops, and these require mapping to the DLMS transaction. This 

applies on an intra-USAF basis, and does not apply to other requisition-related transaction types. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages (tangible/intangible): Supports established AF requirements for DLMS 

migration under Jump Start program. 

b. Disadvantages: None identified. 

7. NOTE ANY REGULATIONS OR GUIDANCE: 

a. AFMAN 23-110, Volume II, Part 2, Chapter 9, Attachment 9B-1 (MILSTRIP REQUISITION 

(A0*), Requisition Output Transaction. 

b. DoD 4000.25-1-M MISTRIP 

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: As soon as possible. 

9. IMPACT: Requires DAASC conversion functionality to support the migration of the Air Force 

legacy system to the DLMS. The only unusual impact resulting from this otherwise simple addition of 

Component data uniques, is the resulting variance from the data element names used in DLMS X12 

EDI for the standard requisition as illustrated below. 

Source of Supply 

• Currently, the MILSTRIP requisition rp 4-6 (RI-To) maps to “Owning ICP.” 

• For the AF lateral requisition, rp 4-6 (RI-To) is a retail AF base; however, the standard 

DLMS mapping is retained resulting in a unique association with the X12 qualifier name 

for Owning ICP. The actual “Owning ICP” is in rp 78-80 of the AF lateral requisition, and 

will be carried in the DLMS as the “potential source of supply.” 

Requisitioner: 

• Currently, the requisitioner is mapped as a DoDAAC. 

• For the AF lateral requisition, the requisitioner is identified by RI, thus requiring a double 

mapping using the same qualifier “Ordered By.
1 Enclosure 1 

Enclosure 1 

DoD 4000.25-1-M, October 2007

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. 

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. 

 

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

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

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. 

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 67-69 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.

4

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

5

Processing points passing DI AM_ transactions to another supply source for continued processing will enter their RI code 

in rp 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). 
3 Enclosure 1 

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

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

b. This field may be used for 

internal purposes on retained copies 

of requisitions. 

Remarks Blocks L-W This field will be used to convey any

additional required information not 

provided for in the requisition 

format. 

GOVERNMENT-FURNISHED MATERIEL REQUISITION ENTRIES.

13

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. 

 7

 On an 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 rp 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 rp 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 rp 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 Procedures to control access to DOD material inventories by defense contractors last reported as not implemented by 

USA (Retail). Refer to AMCL 1A.
4 Enclosure 1 

FIELD LEGEND

TYPE REQUISITION BLOCK 

NUMBER(S) (MANUAL) 

RECORD POSITION(S) 

(MECHANICAL) ENTRY AND INSTRUCTIONS

MANAGEMENT CONTROL ACTIVITY ENTRIES: Entries Required for Requisitions for 

Government-Furnished Materiel.14 

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 ENTRIES: Entries Required When 

Requisitioning a Specific Item From Disposal.15

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 ENTRIES: Entries Required on 

Requisitions to Disposal When a Specific Item is Not Required.16

Blank 70 Leave blank. 

Condition Code 71 Enter lowest acceptable supply 

condition code under Component 

criteria furnished to DRMS. See 

Chapter C2, paragraph C2.21., for 

requirement. 

 Blank 72-80 Leave blank. 

 

14 See Footnote 6. 

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

Refer to AMCL 139A.

16 See Footnote 8.