1 of 7 

ADC 234 

Attachment 

ATTACHMENT TO ADC 234 

Identification of Intra-Army Data Requirements for DLMS 527R Receipt and 

DLMS 527D Due-In and Advance Receipt Information (ARI) and Administrative 

Update to Batch/Lot and Unique Item Identifier (UII) Length (Staffed by PDC 250) 

1. ORIGINATOR: 

 a. Service/Agency: Army Headquarters, United States Army Material Command 

 b. Originator for Army requirement: Army, Logistics Modernization Program 

(LMP), commercial phone: 856-988-6158 

 c. Originator for DLMSO administrative updates: Ms. Mary Jane Johnson, 

DLMSO, MILSTRAP Administrator, e-mail: Mary.Jane.Johnson@dla.mil 

2. FUNCTIONAL AREA: Supply 

3. REQUESTED CHANGE: 

 a. Title: Identification of Intra-Army Data Requirements for DLMS 527R Receipt 

and DLMS 527D Due-In and Advance Receipt Information (ARI) and Administrative 

Update to Batch/Lot and UII Length 

 b. Description of Change: 

 (1) Army changes: 

(a) This change incorporates data elements in DLMS required to accurately process 

intra-Army data for nonprocurement source receipts, dues-in, and advance receipt information 

(ARI) (formerly prepositioned materiel receipt (PMR) under MILSTRAP). This change 

authorizes Army use of the following data in 527D (for dues-in and ARI) and 527R (for 

receipts): 

Priority Designator (LQ01 qualifier 79) 

Advice Code (LQ01 qualifier 80) 

(b) This data is currently used by Army under the Defense Logistics Standard 

Systems (DLSS) in MILSTRAP transaction fields designated as multiuse for intraComponent data for the following Document Identifier (DI) Codes: 

D6_ materiel receipt other than procurement instrument source 

DF_ due-in other than procurement instrument source, and 

DW_ prepositioned materiel receipt (PMR) other than procurement 

(c) Army currently cites the data in the MILSTRAP DI Code D6_, DF_, and 

DW_, record position (rp) 60-66 multiuse field as follows: 

[1] Priority Designator is identified in Army Regulation (AR) 725-50 for 

intra-Army use in rp 60-61 of MILSTRAP DI Codes D6_, DF_ and DW_. 
2 of 7 

ADC 234 

Attachment 

[2] Advice Code is identified in AR 725-50 for intra-Army use in rp 65-66 

of MILSTRAP DI Codes D6_, DF_ and DW. 

(2) DLMSO Administrative Updates: DLMSO administrative updates include 

documentation of Unique Identification (UID) policy limitations on the maximum field 

size for UII and the batch/lot number; identifies the UII as an authorized DLMS 

migration enhancement; and other administrative updates as needed. UID policy is 

available at: http://www.acq.osd.mil/dpap/UID/. 

 c. Procedures: 

(1) Revise DOD 4000.25-2-M, MILSTRAP, appendices AP3.2 (DI Code D6_), 

AP 3.12 (DI Code DF) and AP 3.43 (DI Code DW_) to document Army use of rp 60-66 

multiuse field as noted in subparagraph 3.b.(1)(c) above. Documentation in MILSTRAP 

will facilitate correct conversion mapping in a mixed DLSS-DLMS environment.

(2) Revise DLMS Supplement 527D as follows: 

Item # Location Revision to 

527D, Due-in/ Advance Receipt /Due 

Verification 

Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Note: 

Add introductory DLMS notes 4.f. and 

4.g:

4.f. Repetition of data (using multiple 

iterations or loops) which is not 

compatible with existing DLSS capability. 

Although supported by the use of the 

ANSI X12 standard, such data is not 

compatible with DLSS/DLMS conversion 

and may not be supported by the 

recipient's automated processing system. 

Components must coordinate 

implementation of enhanced capability 

with DLMSO prior to use. 

4.g. 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.

DLMSO administrative 

update to incorporate 

standard DLMS 

introductory notes in 

527D. 

No update 

needed. 
3 of 7 

ADC 234 

Attachment 

Item # Location Revision to 

527D, Due-in/ Advance Receipt /Due 

Verification 

Reason Federal IC 

Impact 

2. DLMS 

Introductory 

Note 

Added ADC 234 to DLMS Introductory 

note 6:

- ADC 234, Identification of Intra Army 

Data Requirements for DLMS 527R 

Receipt and DLMS 527D Due-In and 

Advance Receipt Information, and 

Administrative Update to Batch/Lot and 

Unique Item Identifier (UII) Length) 

To identify DLMS 

changes included in the 

DS 

No update 

needed. 

3. 2/LQ01/130 Add qualifier ‘79’ with DLMS note:

79 Priority Designator 

DLMS Note: Army uses to identify 

priority designator in nonprocurement 

source due-in and advance receipt 

information (ARI). Use of this data is 

meaningful to Army only. Army cites 

data in multiuse rp 60-61 of MILSTRAP 

DI Codes DF_ and DW_. Army 

authorized DLMS migration 

enhancement. See DLMS introductory 

note 4.g. 

To document existing 

Army DLSS data 

requirement in DLMS. 

No update 

needed. 

4. 2/LQ01/130 Add qualifier ‘80’ with DLMS note:

80 Advice Code 

DLMS Note: Army uses to identify Army 

return advice code in nonprocurement 

source due-in and ARI. Use of this data 

is meaningful to Army only. Army cites 

data in multiuse rp 65-66 of MILSTRAP 

DI Codes DF_ and DW_. Army 

authorized DLMS migration 

enhancement. See DLMS introductory 

note 4.g. 

To document existing 

Army DLSS data 

requirement in DLMS. 

No update 

needed. 

5. 2/REF01/250 Revise DLMS note 1 for qualifier ‘BT’ 

DLMS as follows:

BT Batch Number 

DLMS Note: 1. Use to identify the batch, 

lot, or 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 update 

needed. 
4 of 7 

ADC 234 

Attachment 

Item # Location Revision to 

527D, Due-in/ Advance Receipt /Due 

Verification 

Reason Federal IC 

Impact 

6. 2/N901/270 Revise DLMS note 1 for qualifier ‘BT’ as 

follows:

BT Batch Number 

DLMS Note: 1. Use to identify the batch, 

lot, or production run when UII or serial 

number is identified in 2/REF/250. 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 update 

needed. 

7. 2/REF01/250 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 “UIIDepartment of Defense Unique Item 

Identifier”. 

2. Authorized DLMS migration 

enhancement. See DLMS introductory 

note 4.g. 

DLMSO Administrative 

updates to: 

1) document maximum 

50 position length for UII 

IAW UID policy; 

2) identify UII as an 

authorized DLMS 

migration enhancement; 

and 

3) identify approved 

ANSI code for UII in 

version 5020. 

No update 

needed. 

(3) Revise DLMS Supplement 527R as follows:

Item # Location Revision to 

527R, Receipt, Inquiry, Response and 

MRA 

Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Note: 

Added ADC 234 to DLMS Introductory 

note 7:

- ADC 234, Identification of Intra Army 

Data Requirements for DLMS 527R 

Receipt and DLMS 527D Due-In and 

Advance Receipt Information, and 

Administrative Update to Batch/Lot and 

Unique Item Identifier (UII) Length) 

To identify DLMS 

changes included in the 

DS. 

No update 

needed. 
5 of 7 

ADC 234 

Attachment 

Item # Location Revision to 

527R, Receipt, Inquiry, Response and 

MRA 

Reason Federal IC 

Impact 

2. 2/LIN02/10 Revise DLMS Note 1 to include qualifier 

A3:

1. Use only one of codes A1, A2, A3, A4, 

FB, FS, FT, MG, YP, or ZZ to identify 

the material. Must use the National Stock 

Number (NSN) (code FS) when known, 

except when appropriate brand name 

subsistence items are identified by the 

Subsistence Identification Number (code 

A4). 

DLMSO administrative 

update to include qualifier 

‘A3’ in list of qualifiers 

that can be used to 

identify materiel. 

No update 

needed. 

3. 2/LQ01/130 Revise existing DLMS notes for qualifier 

‘79’:

79 Priority Designator 

DLMS Note 1. Army uses in 

nonprocurement source receipts to 

identify priority designator. Use of this 

data is meaningful to Army only. Army 

cites data in multiuse rp 60-61 of 

MILSTRAP DI Code D6_. Army 

authorized DLMS migration 

enhancement. See DLMS introductory 

note 5.g. 

2. Army also uses to communicate the 

priority designator associated with Army 

Total Package Fielding receipt.

To document expanded 

Army use of priority 

designator code in 

receipts for Army. 

Documents existing Army 

DLSS data requirement in 

DLMS. 

No update 

needed. 
6 of 7 

ADC 234 

Attachment 

Item # Location Revision to 

527R, Receipt, Inquiry, Response and 

MRA 

Reason Federal IC 

Impact 

4. 2/LQ01/130 Number existing DLMS note as 1 and 

revise as noted, and add new DLMS note 

2 for qualifier ‘80’.

80 Advice Code 

DLMS Note: 1. Use when submitting a 

duplicate receipt in reply to a receipt 

inquiry; when submitting a response to a 

receipt inquiry when there is a receipt in 

process; when there is no receipt in 

process and no advance receipt 

information file; when there is no receipt 

in process but there is an advance receipt 

information file; and when submitting a 

delinquent MRA in response to an 

inquiry; otherwise, do not use except as 

noted below. DLMS enhancement, 

see DLMS introductory note 5.a. 

2. Army uses in nonprocurement source 

receipts to identify Army return advice 

codes. Use of Army return advice code 

in receipts is meaningful to Army only. 

Army cites data in multiuse rp 65-66 of 

MILSTRAP DI Code D6_. Army 

authorized DLMS migration 

enhancement. See DLMS introductory 

note 5.g. 

The change to DLMS 

Note 1 documents that 

use of advice code is a 

DLMS enhancement. The 

advice code is not in the 

corresponding 

MILSTRAP formats. 

The change to DLMS 

Note 2 documents 

existing Army DLSS data 

requirement in DLMS. 

No update 

needed. 

5. 2/REF01/250 Revise DLMS note 1 for qualifier ‘BT’ as 

follows:

BT Batch Number 

DLMS Note: 1. Use to identify the batch, 

lot, or 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 update 

needed. 

6. 2/N901/270 Revise DLMS note 1 for qualifier ‘BT’ as 

follows:

BT Batch Number 

DLMS Note: 1. Use to identify the batch, 

lot, or production run when UII or serial 

number is identified in 2/REF/250. 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 update 

needed. 
7 of 7 

ADC 234 

Attachment 

Item # Location Revision to 

527R, Receipt, Inquiry, Response and 

MRA 

Reason Federal IC 

Impact 

7. 2/REF01/250 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 “UIIDepartment of Defense Unique Item 

Identifier”. 

2. Authorized DLMS migration 

enhancement. See DLMS introductory 

note 5.g. 

DLMSO Administrative 

updates to: 

1) document maximum 

50 position length for UII 

IAW UID policy; 

2) identify UII as an 

authorized DLMS 

migration enhancement; 

and 

3) identify approved 

ANSI code for UII in 

version 5020. 

No update 

needed. 

 d. Alternatives: None known. 

4. REASON FOR CHANGE: 

 a. Documents and incorporates Army’s existing DLSS MILSTRAP data requirements 

in DLMS. The data provides value-added information for Army. 

 b. Identifies DLMSO administrative updates to identify UID policy limitations on UII 

and batch/lot field size; and other administrative updates. 

5. ADVANTAGES AND DISADVANTAGES: 

 

 a. Advantages: Supports Army implementation of DLMS migration effort to 

accurately process due-in and receipt transactions within the Army. Incorporates in 

DLMS, Army data currently used in DLSS multiuse intra-Component fields. 

 

 b. Disadvantages: None identified. 

6. IMPACT: 

 a. Modify DLMS Supplements 527D and 527R; and DOD 4000.25-2-M 

(MILSTRAP) to acknowledge Army data currently used in DLSS multiuse fields 

designated for intra-Component use. DLMSO will incorporate revisions in 

corresponding DLMS XML transactions. 

 b. DAASC maps require updating to document Army data mapping between 

MILSTRAP/DLMS for mixed DLSS-DLMS environment. 

 c. Limitation on batch/lot number and UII field size maximum lengths may impact 

DOD Component automated information systems.