1 Attachment 1 

ADC 264 

DLMS Enhancement for Part-Numbered Requisition Format and 

USAF Unique Rules for Descriptive Information including T.O. Number 

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: Part-Numbered Requisitioning 

3. REFERENCE: DLMSO Memorandum dated February 20, 2002, subject Approved DLMS 

Change 52, Termination of DAASC Part Number Conversion Process.

4. BACKGROUND: 

a. Intent of the change. 

 

(1) AF Requirement. This DLMS change supports an AF Jump Start program. Under 

the Air Force Jump Start program, part-numbered requisitions (MILSTRIP A02 and A0B 

transactions), will be produced in DLMS XML using the DLMS 511R format, and will need to 

perpetuate applicable descriptive information including technical order (T.O.) number, end item 

description, commodity name, drawing/specification number, or other miscellaneous 

information. AF business rules for including descriptive data do not conform to the standard 

DLMS/MILS usage. This change will supports unique procedures for the AF requirement 

pending future reengineering. Significant changes from the original staffing are highlighted. 

(2) Associated DLMSO-Sponsored Administrative Changes: 

 (a) This change includes administrative updates to MILSTRIP-identified descriptive 

information data associated with part-numbered requisitions, during the transition to DLMS from 

the MILS-based procedures. This change clarifies DLMS business rules, and specifies future 

DLMS field length for the identified supplemental information in part-numbered requisitions. 

 (b) There is an administrative change to the MILSTRIP format for part-numbered 

requisitions, to remove the requirement for DAAS to insert the Screening Code Z in record 

position 44 of the A02/A0B transaction (refer to MILSTRIP Appendix, AP3.4, Non-National 

Stock Number Requisition). 

b.Scenario applicable to AF unique usage: 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. When this request is made by part number, it normally 
2 Attachment 1 

includes descriptive information. SBSS uses a single data element for descriptive information, 

regardless of the specific type of information. 

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

MILSTRIP and DLMS allow four types of descriptive information which may be passed in a 

part-numbered requisition: T.O., or technical manual number; end item identification; 

commodity name; and, drawing or specification number. In MILSTRIP, an identification code is 

passed in the transaction to distinguish the type of descriptive information. In the DLMS format, 

the identification code is not needed, because each type of descriptive information has available 

a separate data element identified by a unique qualifier code. (The DLMS also identifies 

potential enhancements for further inclusion of descriptive information which will not be 

addressed in this change document.) DAASC used the identification code, or the specific DLMS 

data element qualifier code, to convert back and forth between MILS and DLMS formats. SBSS 

has only a single data field to hold and populate part-number descriptive information; further, 

SBSS has no way to separate or distinguish between the different types of descriptive 

information. AF MILSTRIP A02 and A0B transactions, therefore, do not include the 

identification code. Descriptive information falls into the four types specified by MILSTRIP, or 

may be other miscellaneous information. In addition, the AF field length is 14 positions instead 

of the 10 positions prescribed by MILSTRIP. Specifically, the descriptive information is 

transmitted in record position (rp) 67-80 of the AF A02 and A0B transactions, vice the 

identification code in rp 70, and corresponding descriptive information in 71-80. The DLMS 

Supplement does not expressly define the current or enhanced field length beyond the X12 

standard. Enclosure 1 has actual examples of AF part-numbered requisitions showing different 

types of descriptive information. Enclosure 2 is the DAAS map for conversion between MILS 

and DLMS. 

5. APPROVED CHANGE: 

a. Approved change in detail: The AF will create a DLMS part-numbered requisition 

with all descriptive information, regardless of type, using a single DLMS data field. 

b. Procedures: 

(1) Transaction Preparation: The AF will generate DLMS part-numbered requisition 

with any applicable descriptive information included in the NTE, Note Segment, using NTE01, 

Qualifier ORI, Order Instructions. The data element may include blanks, alpha, numeric, and 

special characters. The value may be of varied length with a current maximum length of 

14 positions which may be expanded further under DLMS. 

(2) DAAS Conversion. If needed, DAAS will convert AF DLMS notes (from NTE01-

02, Qualifier ORI), to the current AF-unique MILS format. That is, the value in the DLMS 

transaction will be used to populate rp 67-80 of the MILS format. This will conform to the 

current AF structure which deviates from MILSTRIP rules. AF supply sources will support this 

format; however, descriptive information may not be usable on an inter-Service basis. 
3 Attachment 1 

(3) Transaction Processing. The DLA supply source currently receives notes passed in 

NTE01-02 as technical/descriptive exception information (formerly processed under 

DLA DI Code YRZ). Under DLMS migration, the NTE01-02, Qualifier ORI, is planned to 

support exception requisition data, in addition to designated qualifiers identifying specific types 

of information, such as, T.O. number, commodity name, and end item description, associated 

with part-number requisitions. 

 (4) DLMS 511R, Requisition. Update DLMS Supplements as shown to provide for the 

AF T.O. number, and to show business rules during MILS to DLMS migration, and full MILS 

field length: 

# Location Revision Reason for 

Change 

1 511R 

2/NTE01/120 

 

Revise existing DLMS note as shown: 

ORI Order Instructions 

DLMS Note: 

Use with Requisition Exception Data Transaction (DLA DI Code 

YRZ-Line Counters 01-20) to indicate technical/descriptive exception 

information for procurement purposes. Segment may be repeated up 

to 20 times with same NTE01 qualifier. A maximum of 60 positions 

(including spaces) may be sent for each occurrence of the NTE01. A 

maximum of 1200 positions of text (including spaces) may be sent. 

Pick, pack, and special delivery type instructions (DLA DI Code 

YRZ-Line Counters 01-06) may also be entered as exception data to 

be forwarded to a DSS storage activity, as part of an exception MRO. 

This type of data is limited to 360 positions (including spaces) which 

would be the segment, repeated up to 6 times, with the same NTE01 

qualifier. Also used for USAF descriptive data associated with partnumbered requisitions (A02/A0B rp 67-80). See introductory DLMS 

note 3e. 

Identifies usage for 

USAF. 

Clarifies mapping 

and planned DLMS 

enhancement. 

 (5) Update MILSTRIP Appendix, AP3.4, Non-National Stock Number Requisition 

(Mechanical), as shown in Enclosure 3. 

(6) Administrative/DLMS Migration Update. As a related, administrative change to 

the DLMS Supplement documentation, not associated with the specific Air Force requirement, 

update the DLMS 511R as shown, to provide expanded guidance for additional data elements 

currently available in the DLMS, as equivalent to MILSTRIP data content. Identify the current 

field length for MILSTRIP to permit conversion, and the target expanded field length for DLMS 

enhancements. Apply comparable changes to the 511M, Requisition Modification, and the 869F, 

Requisition Follow-up (both of which may serve as an original requisition when unmatched to 

the Supply Source records). Administrative updates are shown in Enclosure 4. 
4 Attachment 1 

c. Alternatives: None identified. 

6. REASON FOR CHANGE: 

 a. The SBSS-prepared A02 and A0B MILS transactions carry the expanded length 

descriptive data, which could contain various types of information for part-numbered requisitions 

in rp 67-80, and requires mapping to the DLMS transaction. This information is common to the 

YRZ exception data used by DLA, and so can be mapped to the generic note field as specified 

above. 

 b. DLMS Field Length Determination. In determining the field length for the full DLMS 

enhancement, DLMSO reviewed the AF T.O. numbering system published in T.O. 00-5-18. 

There are 60 categories of T.O.s identified in the regulation. Within each category there are 

7 groups. Each group has 1 to 6 parts and subparts. Each chapter of the regulation has specific 

rules by category for identification. The result showed a minimum of 30 characters could be 

used for the complete T.O. number. Taking this and the other data elements associated with part 

number requisitioning into consideration, DLMSO recommended adoption of the available 

X12 EDI maximum length of 48 characters for each of the data elements identified in the current 

MILS format: T.O. Number; End-Item Description; Commodity Name; and, Part Drawing. This 

establishes the authorized DLMS enhancement field length, so that DLMS migration systems 

can establish the larger field length in their applications as soon as practical. 

 c. Reason for removal of Screening Code Z in MILSTRIP Appendix, AP3.4, Non-National 

Stock Number Requisition. This code was developed to indicate that DAAS had screened the 

part number for association with an existing National Stock Number (NSN). However, the 

DAASC screening/conversion was terminated under ADC 52 (reference 3). There was a 

remaining requirement whereby DAASC automatically inserted the Code Z, to prevent the 

previously time-consuming screening process for an NSN on part-numbered requisitions for 

repair parts in support of commercial construction equipment (CCE), and materials handling 

equipment (MHE) using project codes "JZC” and “JZM." Under ADC 52, screening is either 

eliminated or performed internally, and all other references to this function were removed from 

MILSTRIP/DLMS. In confirmation, DLA reported that there is no longer a need for the Z code, 

and that that internal screening under the DLA modernization system (EBS) replaces this 

requirement. 

7. ADVANTAGES AND DISADVANTAGES: 

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

migration under Jump Start program with minimal impact on others. Provides guidance for 

DLMS migration. 

 b. Disadvantages: Perpetuates AF deviation from MILSTRIP procedures. There is no 

improvement in communication of descriptive information under MILS; however, the end result 

is consistent with current practice. 
5 Attachment 1 

8. 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 and DLMS manual. 

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

10. IMPACT: 

a. Requires DAASC conversion functionality for the T.O. Number to support the migration 

of the Air Force legacy system to the DLMS. 

 

b. DLMS migration systems will take action when practical, to adopt the expanded field 

length for the specified data elements. 

c. The AF will develop improved techniques for identifying descriptive information within 

their ERP design, for future separation of descriptive information between authorized data 

elements.
1 Enclosure 1 

Enclosure 1 

AF Example Transactions (document number hidden) 

 Yellow 

highlights on rp 

67-80

A02SMSK325260017835897EA00002FB------------ZYAF368A6C 01JZC023642DT.O.COMMER 

MAN 

A02SMSK230400021155897EA00001FB------------ZYAF368A6C 01JZC023642DT.O.36A10-

3-42 

A02SMSK1186215082619 EA00002FB------------ZYBF368A6C 01JZC050102DTO.GM LIGHT 

TR 

A0BF16S1111123065345 RO00005FB------------NY185JMD 01 03777 NO TO 

A02SMSK3462312339353-1EA00002FB------------ZYAF384A6C 01JZC023652A1998/M1116 

LLA 

A0BFZZS0L1E5LA-RG317-4EA00001FB------------RYBGGPKD 01 05 TUBE 

A0BF83S0YJB5UPA92145-1EA00009FB------------RYAZAQLD 01 02 1Q-1(R)B12-3W 

A02FGZS81755P5053-16 EA00001FB------------NYAW275D64 01 02 NYLON 

MATERIAL 

A0BF06S98897374997-30 EA00001FB------------RYBQ328D 01 05365 C130 

MAINTENAN 

A0BF06S98897443XS003NFEA00002FB------------NYAE505D 01 03 1C-130J-2-

00WD 

A0BF83S0YJB5UXP95760-1EA00001FB------------R D 0188008777 *ODOM 

A0BF77S8827702-211 EA00001FB------------NYAW690D 01 03 4-4 F190 I6 

A02F83S0YJB5A3236SS012EA00100FB------------RYAZ264D6 019GJ02777 SHOPUSE 

A0BFHZS97942583R583H62EA00001FB------------RYBQ194D64 01 06 TINKER AFB 

OK 

A0BF74S8120569-17280-2EA00001FB------------RYBQ687D 0170005777 JSTARS E8 

A0BFZZS52793LA-31058-6EA00001FB------------RYBGGL4D 01 05 HOSE 

ASSEMBLY 

A02SMSK230400016705897EA00001FB------------ZYAF368A6C 01JZC023642D36A10-3-42-

4-2 
1 Enclosure 2 

Enclosure 2 

Current DAAS Map 

Technical Order Number 71-80 If RP3=2 or B and if RP70=A LIN02=F2 LIN03=RP 71-80 

End-Item Description 71-80 If RP3=2 or B and if RP70=B LIN02=F7 LIN03=RP 71-80 

Commodity Name 71-80 If RP3=2 or B and if RP70=C LIN02=CN LIN03=RP 71-80 

Print or Drawing 71-80 If RP3=2 or B and if RP70=D LIN02=PT LIN03=RP 71-80 

Exception Data 21-80 If RP1-2=A0 and If RP1-3=YRZ 

and RP4-5=01 

NTE01=ORI 

NTE02=RP 21-80 

Additional Map Instruction 

Exception Data 67-80 If RP1-3=A02/B and rp 30=E or F 

and rp 70 not=A, B, C, or D 

NTE01=ORI 

NTE02=RP 67-80 
1 Enclosure 3 

Enclosure 3 

AP3.4. APPENDIX 3.4.

NON-NATIONAL STOCK NUMBER REQUISITION

(MECHANICAL)

FIELD LEGEND

RECORD 

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 1-3 Enter DI A02 or A0B. 

(rp 4-7 entries are the same as AP3.2) 

Manufacturer’s Code and 

Part No.1

8-22 Enter the CAGE from the DoD and Part No. 

Cataloging Handbook H4-1 and the part 

number assigned to the item by the manager. 

(rp 23-43 entries are the same as AP3.2) 

Demand/Screening 44 Enter appropriate code from AP2.8. Code Z 

may be entered by the DAAS to indicate an 

Air Force A02/A0B transaction or one with 

Project Code JZ_ has been screened for a 

match to a definitive NSN.

(rp 45-69 entries are the same as AP3.2) 

Identification 702 Enter the applicable code to designate the 

entry in rp 71-80 (if not applicable, leave 

blank): 

A - TO or TM

B - End Item Identification 

C - Noun Description of Item 

D - Drawing or Specification No. 

Reference Identification 71-80 Enter the identification of the reference 

specified in rp 70. 

 

1

If the CAGE and part number cannot be entered in rp 8-22, use DD Form 1348-6 (AP1.6) to requisition the part 

number or non-NSN items. 

2

 Air Force part-numbered requisitions use rp 67-80 (without the identification code in rp 70) to provide 

descriptive information. This may not be recognizable on an inter-Service basis. Refer to ADC 264. 
2 Enclosure 3 

FIELD LEGEND

RECORD 

POSITION(S) ENTRY AND INSTRUCTIONS

GOVERNMENT-FURNISHED MATERIEL REQUISITION ENTRIES:

3

(rp 23-67 entries are the same as AP3.2) 

Part Number Designation 68 Enter an E in the GFM requisition when a 

part number is requisitioned. 

Contract Call Order Number 69-72 If required by an S/A contract, enter the 

appropriate contract call order number. 

Procurement Instrument 

Identification Number 

73-80 At the option of the S/A, enter last eight 

positions of the PIIN 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: 

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 S/A, enter the RI code of 

the validating MCA in rp 74-76. 

 

3 Procedures to control access to DoD material inventories by defense contractors last reported as not implemented 

by USA (Retail). Refer to AMCL 1A. 
1 Enclosure 3 

Enclosure 4 

Administrative Updates 

# Location Revision Reason for Change 

1 511R 

2/LIN/100 

Revise the DLMS segment level note: 

DLMS Note: 

1. Must Use as needed when requisitioning nonstandard nonNSN material. 

2. Data elements are DLMS enhancements except where 

specifically identified. The following nonstandard non-NSN 

material identification includes data derived from the DD 

Form 1348-6. 

Clarification. This 

segment is used to 

identify 

characteristics for 

non-NSN material. 

Some of these data 

elements are mapped 

to MILSTRIP partnumbered 

requisitions which 

were not previously 

identified. 

3 511R/511M 

2/LIN02/100 

And 

869F 

2/LIN02/50 

Add the DLMS note for existing qualifier F2: 

F2 Technical Order Number 

DLMS Note: 

1. During the DLSS/DLMS transition, this field will be used to 

perpetuate/populate the Technical Order Number/Technical 

Manual Number identified on MILSTRIP part-numbered 

requisition (corresponds to AM2/AMB with Identification Code 

A (rp 70). During this time, a field length greater than 10 

positions may be truncated or dropped by the receiving 

application. 

2. Under full DLMS, the field length shall be expanded to 

conform to this standard which allows 48 positions. DLMScapable applications should plan to support this expanded field 

length as a DLMS enhancement. See introductory DLMS 3f. 

****************************************** 

Note variation for MILSTRIP Document Identifier: 

For DLMS Note on Follow-up, substitute AT2/ATB. 

Clarifies standard 

usage/mapping and 

planned DLMS 

enhancement. 

Identifies DLMS 

enhancement for field 

length. This is the 

target field length for 

modernization. 

4 511R/511M 

2/LIN02/100 

And 

869F 

2/LIN02/50 

Modify the Federal Note and expand the DLMS note for existing 

qualifier F7: 

F7 End-Item Description 

Federal Note: 

Use to identify the applicable end item which applies to the 

nonstandard non-NSN material. Description may include the NSN 

of the end item and/or nomenclature. 

DLMS Note: 

Clarifies standard 

usage/mapping and 

planned DLMS 

enhancement. 

Identifies DLMS 

enhancement for field 
2 Enclosure 3 

1. During the DLSS/DLMS transition, this field will be used to 

perpetuate/populate the End Item Identification on MILSTRIP 

part-numbered requisition (corresponds to A02/A0B with 

Identification Code B (rp 70)). During this time, a field length 

greater than 10 positions may be truncated or dropped by the 

receiving application. 

2. Under full DLMS, the field length shall be expanded to 

conform to this standard which allows 48 positions. DLMScapable applications should plan to support this expanded field 

length as a DLMS enhancement. See introductory DLMS 3f.

****************************************** 

Note variation for MILSTRIP Document Identifier: 

1. For DLMS Note on Modification, substitute AM2/AMB. 

2. For DLMS Note on Follow-up, substitute AT2/ATB. 

length. This is the 

target field length for 

modernization.

5 511R/511M 

2/LIN02/100 

And 

869F 

2/LIN02/50 

Expand the DLMS notes for existing qualifier CN: 

CN Commodity Name 

Federal Note: 

Use to identify the nomenclature of the nonstandard non-NSN

material. 

DLMS Note: 

1. During the DLSS/DLMS transition, this field will be used to 

perpetuate/populate the Noun Description of Item on MILSTRIP 

part-numbered requisition (corresponds to A02/A0B with 

Identification Code C (rp 70)). During this time, a field length 

greater than 10 positions may be truncated or dropped by the 

receiving application. 

2. Under full DLMS, the field length shall be expanded to 

conform to this standard which allows 48 positions. Multiple 

repetitions of the commodity name may be used in successive 

Product/Service ID pairs where additional text space is needed. 

DLMS-capable applications should plan to support this 

expanded field length as a DLMS enhancement. See 

introductory DLMS 3f.

****************************************** 

Note variation for MILSTRIP Document Identifier: 

1. For DLMS Note on Modification, substitute AM2/AMB. 

2. For DLMS Note on Follow-up, substitute AT2/ATB. 

Clarifies standard 

usage/mapping and 

planned DLMS 

enhancement. 

Identifies DLMS 

enhancement for field 

length. This is the 

target field length for 

modernization.

6 511R/511M 

2/LIN02/100 

Expand the DLMS notes for existing qualifier PT: 

PT Print or Drawing 

Clarifies standard 

usage/mapping and 

planned DLMS 
3 Enclosure 3 

And 

869F 

2/LIN02/50 

Federal Note: 

Use to identify the applicable drawing numbers for the 

nonstandard material. 

 DLMS Note: 

1. During the DLSS/DLMS transition, this field will be used to 

perpetuate/populate the Drawing or Specification Number on 

MILSTRIP part-numbered requisition (corresponds to A02/A0B 

with Identification Code D (rp 70)). During this time, a field 

length greater than 10 positions may be truncated or dropped by 

the receiving application. 

2. Under full DLMS, the field length shall be expanded to 

conform to this standard which allows 48 positions. DLMScapable applications should plan to support this expanded field 

length as a DLMS enhancement. See introductory DLMS 3f.

****************************************** 

Note variation for MILSTRIP Document Identifier: 

1. For DLMS Note on Modification, substitute AM2/AMB. 

2. For DLMS Note on Follow-up, substitute AT2/ATB. 

enhancement. 

Identifies DLMS 

enhancement for field 

length. This is the 

target field length for 

modernization.