1 of 4 

ADC 235 

Attachment 

ATTACHMENT TO ADC 235 

Revise DLMS Supplement (DS) 867I and MILSTRAP Issue Transactions to Support Navy Issue 

On Request Code and Administrative DS 867I Updates (Supply) (Staffed by PDC 242) 

1. ORIGINATOR: 

a. Service/Agency: Naval Supply Systems Command (NAVSUP)

b. Originator: NAVSUP Enterprise Resource Planning Organization, Program Control SUP E1, 

Uniform Automated Data Processing Inventory Control Point program manager, DSN 430-7510, 

commercial: 717-606-7510

2. FUNCTIONAL AREA: Supply

3. REQUESTED CHANGE: 

a. Title: Revise DLMS Supplement (DS) 867I and MILSTRAP Issue Transactions to Support Navy 

Issue On Request Code and DS 867I Administrative Updates (Supply).

b. Description of Change: 

(1) Revise DLMS 867I Issue transaction to add the Navy issue on request code in support of an 

existing Navy requirement. Navy uses the issue on request code when interfacing with Defense Logistics 

Agency Distribution Standard System (DSS). 

(2) Revise MILSTRAP to document existing Navy use of the issue on request code in 

Document Identifier (DI) Code D7_ issue transaction. 

(3) Administrative updates to DLMS 867I to include an update to add a new DLMS introductory 

note for ‘authorized DLMS migration enhancements’ such as the Navy’s Issue on request code. The 

new note states: “Data associated with a DLMS enhancement authorized for implementation by 

modernized systems under DLMS migration. This data (including expanded field sizes) should be 

adopted during, or subsequent to, modernization when applicable to the Component’s business process. 

Prior coordination is not required. Components should ensure that inclusion of this data in a DLMS 

transaction does not cause inappropriate rejection of the transaction.” 

c. Procedures: 

(1) Revise DOD 4000.25-2-M, MILSTRAP, Appendix AP3.3, DI Code D7_ Issue, as follows 

(change identified by bold, red, italicized text):

FIELD LEGEND RP ENTRY AND INSTRUCTIONS

Multiuse 76-80 For intra-Component use, enter data prescribed by 

Component. For inter-Component use, leave blank.4

4 For Navy, rp 77 identifies the ‘issue on request’ code. Navy uses when a customer receives material without a 

Material Release Order and DSS sends a D7_ (with an “I” in position 77) to Navy systems (e.g., Uniform 

Automated Data Processing System (UADPS) II (U2) and Uniform Inventory Control Program (UICP) ) to indicate 

that material has been issued. (See ADC 235.) 
2 of 4 

ADC 235 

Att 

 

(2) Revise DS 867I to add the issue on request code ( row #6 below), and make DLMSO 

administrative updates:

# Location DS 867I Revision Reason Federal 

IC Impact 

1 DLMS 

Introductory 

Note 1 

Revise note to spell out DI as Document Identifier (DI): DLMSO Administrative 

update to spell out 

document identifier the 

first time it is used in DS 

No revision 

required 

2 DLMS 

Introductory 

Note 5 

Add new DLMS introductory note 5.e: 

e. Data associated with a DLMS enhancement 

authorized for implementation by modernized systems 

under DLMS migration. This data (including expanded 

field sizes) should be adopted during, or subsequent to, 

modernization when applicable to the Component’s 

business process. Prior coordination is not required. 

Components should ensure that inclusion of this data in 

a DLMS transaction does not cause inappropriate 

rejection of the transaction.

To provide a DLMS note 

to acknowledge enhanced 

data authorized for 

implementation in DLMS 

No revision 

required

3 DLMS 

Introductory 

note 7 

Add ADC 235 to DLMS introductory note 7: 

- ADC 235, Revise DS 867I and MILSTRAP Issue 

Transactions to Support Navy Issue On Request Code 

and Administrative DS 867I Updates. 

To identify changes in the 

DS 

No revision 

required 

4 1/BPT04/20 Revise DLMS note as follows: 

DLMS Note. Use to identify Issue transactions

(MILSTRAP DI Code D7_ functionality.)

DLMSO Administrative 

update to correlate 

beginning segment code 

with corresponding 

MILSTRAP DI Code 

No revision 

required 

5 2/PTD01/10 Add a new DLMS note 1 to Ref ID 521-Product 

Transfer Type Code, and renumber existing note as 2: 

New DLMS Note: 1. The information conveyed by this 

code corresponds to the information conveyed by the 

third position of MILSTRAP DI Code D7_. 

DLMSO administrative 

update to acknowledge 

that the information 

provided by BPT01 

correlates to the 

information provided by 

the third position of the 

MILSTRAP DI Code D7_. 

No revision 

required 

6 2/LQ01/270 Add qualifier RT-Request Type with DLMS note: 

RT Request Type 

DLMS note: Use for the Navy Issue on Request Code. 

DLMS enhancement authorized for use by Navy and 

DLA Distribution Standard System (DSS). 

To document existing 

Navy DLSS data 

requirement in DLMS. 

Navy uses this code when 

interfacing with DLA 

Distribution Standard 

System (DSS). Code 

entered in DLSS multiuse 

field designated for intraComponent use. 

No revision 

required 
3 of 4 

ADC 235 

Att 

# Location DS 867I Revision Reason Federal 

IC Impact 

7 2/REF01/290 Revise DLMS note 1 for qualifier ‘BT’ DLMS: 

BT Batch Number 

DLMS Note: 1. Use to identify the batch, lot, or other 

number identifying the production run. The batch/lot 

number may not exceed 20 characters in accordance 

with UID policy. 

DLMSO Administrative 

update to document 

maximum 20 position 

length for batch/lot IAW 

UID policy. UID PMO 

authorizes 20 position 

maximum batch/lot size in 

the DOD IUID registry. 

No revision 

required 

8 2/REF01/290 Revise DLMS Notes 1 and 2 for qualifier ‘U3’: 

U3 Unique Supplier Identification Number (USIN) 

DLMS Note: 1. Use to identify the UII. Place UII value 

in REF03. The UII may not exceed 50 characters in 

accordance with UID Policy. An ANSI data 

maintenance was approved in version 5020. The 

approved code/name is “UII - Department of Defense 

Unique Item Identifier”. 

2. Authorized DLMS migration enhancement. See 

DLMS introductory note 5.e. 

DLMSO Administrative 

updates to: 

1) document maximum 50 

position length for UII 

IAW UID policy; 

2) identify UII as an 

authorized DLMS 

migration enhancement; 

3) identify approved ANSI 

code for UII in version 

5020. 

No revision 

required 

 

 d. Alternatives: None 

4. REASON FOR CHANGE: 

 a. Navy currently uses the issue on request code when a customer receives material without a 

Material Release Order and DSS sends a D7_ (with an “I” in position 77) to Navy systems to indicate that 

material has been issued. The "I" in rp 77 means a Materiel Release Order (MRO) was keyed in to DSS. 

DSS refers to this process as the SMOK or Super MRO process. The issue on request code ("I" in rp 77) 

is referred to as an "IOR" by the Navy and it means that they have no requisition history because they did 

not systemically generate the A5_ MRO, hence they build their requisition history upon receipt of the IOR 

D7_. The MRO was introduced into DSS via a phone call, fax, or user standing there in person. 

b. Navy currently allows for entry of the issue on request code in MILSTRAP DI Code D7_ Issue 

transactions, in a multi-use field. MILSTRAP multi-use fields allow for Component entry of data 

unique to their system. The code is required by the Navy logistics system. Navy uses the code when 

interfacing with DLA DSS. This change adds the code to DS 867I, and provides visibility in 

MILSTRAP for mapping in a mixed DLSS/DLMS environment. 

5. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Enables DS 867I to accommodate Navy requirement for an issue on request 

code. Supports DSS interface with Navy using DLMS 867I to provide Navy’s required logistics data. 

DSS migration to an DS 867I has been delayed until the Navy issue on request code and “issue reversal 

code” are added to the 867I. Navy issue reversal code and will be staffed by a separate PDC. 

b. Disadvantages: None 
4 of 4 

ADC 235 

Att 

6. IMPACT: 

a. Data Content/Procedures: 

(1) Revise MILSTRAP as shown in paragraph 3.c(1).

(2) Revise DLMS 867I as shown in paragraph 3.c(2).

(3) Update DAASC mapping as needed to accommodate this change.

b. Publication(s): DLMS 867I, MILSTRAP, and DAASC maps.