ADC 54

Attachment

Approved DLMS Change 54 

Revision to DLMS Supplement (DS)

527D Due-In/Advance Receipt/Due Verification 

1. ORIGINATOR: Supply Process Review Committee, Mary Jane Johnson, Defense 

Logistics Management Standards Office (DLMSO), DLA J-673, 703-767-0677 (DSN 

427), Email: maryjane_johnson@hq.dla.mil

2. FUNCTIONAL AREA: Supply

3. REQUESTED CHANGE:

a. Title: Revision to DS 527D, Due-In/Advance Receipt/Due Verification

b. Description of Change: This change modifies the DS to make various changes 

resulting from an in-depth review by the Supply Process Review Committee (SPRC) at 

SPRC Meeting 02-1, January 15-18, 2002. 

c. Procedures: Revise DS 527D as indicated in the enclosure. 

d. Alternatives: None identified.

4. REASON FOR CHANGE: Administrative changes necessary for clarification as 

identified in the enclosure. 

5. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Supports DLMS implementation.

b. Disadvantages: None identified.

6. IMPACT: 

a. Publications. Corresponding Federal IC.
1 of 4

ADC 54 --527D

Enclosure

527D DLMS Supplement

Revisions Discussed at SPRC Meeting 02-1

(Jan 15-18, 2002)

# LOCATION CHANGE RATIONALE

1 DLMS notes at 

transaction set 

level (page 2)

Modify note 4 to add new subparagraph 

4.e:

Data required to accommodate 

Component-unique transaction 

requirements (ex. C-series transactions). 

Data does not apply to DLSS transactions.

To identify new functionality 

incorporated for Service unique 

transactions, which is unrelated 

to current DLSS transactions.

2 DLMS note at 

transaction set 

level (page 2). 

Modify DLMS note 5 to add ADC 45 Administrative correction.

3 1/N1/070 Deleting code Z4 (owning ICP) from 

supplement. 

MILSTRAP Administrator 

could find no intended use not 

already addressed by code KA.

4 1. Revise note for code 'U' to specify it is 

for USAMMA Medical prime vendor 

program

USAMMA is the only known 

current user for this code. Note 

can be modified as needed to 

accommodate additional users 

if requirements are documented 

to DLMSO.

5

2/LIN01/010

Revise "DLMS enhancement" note to 

specify data is "DLMS Componentunique enhancement"

To differentiate from 

enhancements related to DLSS 

transactions

6 2/LIN02/010 Revise DLMS note for code ZZ-Mutually 

defined, as follows (change is in bold 

italics):

"Use to identify non standard material 

when all other authorized codes do not 

apply or cannot be determined (includes 

management control numbers and 

locally assigned control numbers). May 

be used for DLSS-to-DLMS conversion 

when the translator cannot determine a 

more appropriate code."

This change coordinated with 

SPRC representatives by email 

subsequent to the SPRC 02-1 

meeting. Clarifies use of code 

"ZZ".
2 of 4

ADC 54 --527D

Enclosure

# LOCATION CHANGE RATIONALE

7 Add Federal note : "Following is a list of 

preferred codes."

To allow flexibility for adding 

codes for DoD use.

8 Revise DLMS note to specify USAMMA 

DoD medical prime vendor program. 

Make this DLMS note #1.

At the SPRC mtg, it was 

suggested to specify data is 

used in support of USAMMA 

program at this time, since there 

are other medical prime vendor 

programs which do not use this 

information. Note can be 

modified as needed to 

accommodate additional users 

if requirements are documented 

to DLMSO.

9 Add DLMS note #2: For DLMS use, 

only the following codes are authorized.

This note is used in conjunction 

with Federal note added above, 

identifying preferred codes..

10

2/LIN04/010

For codes N4, VC, and VP, modify 

"DLMS enhancement" note to read: 

"DLMS Component-unique 

enhancement"

To differentiate enhancements 

related to Component-unique 

transactions, from 

enhancements related to DLSS 

transactions.

11 2/G62/050 Delete segment level Federal note : "Do 

not use when reversing a transaction."

Data may be needed in reversal

transaction conversion for 

legacy systems during mixed 

DLMS/DLSS environment.

12 2/G62/050 Add a DLMS segment level note #2: 

"Use additional repetitions to define 

unique dates associated with the 

transaction."

For clarification

13 Add Federal note: "Following is a list of 

preferred codes."

To allow flexibility for adding 

codes for DoD use.

14

2/G6201/050

Add DLMS note #2: For DLMS use, 

only the following codes are authorized.

This note is used in conjunction 

with Federal note added above.

15 2/G6201/050 Codes BF and BJ: Add DLMS note #2 to 

each code as follows: "MILSTRAP AMCL 

5 data. See introductory DLMS note 4.b."

For clarification on source of 

data requirement.

16 2/GF/060 Added segment level note that segment is 

a DLMS enhancement.

to DLMS enhancement notes throughout 

segment.

To clarify that segment is a 

DLMS enhancement.

Replace word "guideline note" with 

"introductory DLMS note". 

Administrative update. These 

documents are no longer 

referred to as guidelines.

17 2/GF01 and 

GF03/060 AND 

THROUGHOUT

Will not identify each instance of this administrative update, but 

changes will be made throughout DS 527D.
3 of 4

ADC 54 --527D

Enclosure

# LOCATION CHANGE RATIONALE

18 2/N901/090 Code 55-sequence #. Specify for 

USAMMA use.

Identify for USAMMA use. 

Can be expanded for other uses 

if requirement identified.

19 Code 55 and Code WO:

Revise "DLMS enhancement" note to 

specify data is "DLMS Componentunique enhancement"

To differentiate enhancements 

related to Component-unique 

transactions, from 

enhancements related to DLSS 

transactions.

20 2/NTE/110 Add DLMS note : "The 2/NTE/110 

segment is a DLMS enhancement. See 

introductory DLMS note 4.a"

To identify that segment is a 

DLMS enhancement.

21 2/LM/120 Delete Federal note #2: Do not use when 

reversing transaction.

Data may be needed in reversal 

transaction conversion for 

legacy systems during mixed 

DLMS/DLSS environment.

22 2/LQ01/130 Revise DLMS note for use of ownership 

code and purpose code, to specify that use 

of both for ammo is a DLMS 

enhancement.

To identify use of both codes 

results in enhanced 

functionality which will not 

convert back to DLSS.

23 2/LQ01/130 CODE 99- Purpose code. Delete DLMS 

enhancement note.

Use of Purpose code is not an 

enhancement.

24 2/LQ01/130 Delete Code AL - Special requirements 

code (derived from RDD). 

MILSTRAP Administrator 

could not find rationale for 

inclusion in 527D.

25 2/LQ01/130 Codes IMC, MCC, and SMI (which were 

added by Navy), delete the following 

sentence from the DLMS note for each 

code: "Indicate NSL for non-stock 

numbered listed items."

Correcting an error. Navy only 

intended to add the "NSL" note 

to the COG code, not the IMC, 

MCC, or SMI.

26 2/CS/140 Add DLMS segment level note: "The 

2/CS/140 loop is a DLMS enhancement. 

See introductory DLMS note 4.a."

To identify loop as a DLMS 

enhancement.

27 2/LM/190 Add segment level DLMS note: "The 

2/LM/190 loop is a DLMS enhancement. 

See introductory DLMS note 4.a."

To identify loop as a DLMS 

enhancement.

28 2/N101/210 Change the Federal notes at N101 to 

DLMS notes #1.

Change DLMS note #1 to DLMS note 

#2.

The current Federal Note 

conveys DLMS specific 

information.
4 of 4

ADC 54 --527D

Enclosure

# LOCATION CHANGE RATIONALE

29 Code WZ. Specify it's for USAMMA 

use.

At the SPRC mtg, it was 

suggested to specify data is 

used in support of USAMMA 

program at this time, since there 

are other medical programs 

which do not use this 

information.

30

2/N102/210

Code WZ: modify "DLMS enhancement" 

note to read: "DLMS Component-unique 

enhancement"

To differentiate enhancements 

related to Component-unique 

transactions, from 

enhancements related to DLSS 

transactions.

31 2/N103/210 Add standard DLMS enhancement note to 

codes 1 (DUNS #); 9 (DUNS +4); 10 

(DODAAC); and 33 CAGE

Administrative update.

32 2/REF/250 Add DLMS note # 3: "The 2/REF/250 

loop is a DLMS enhancement. See 

introductory DLMS note 4.a."

To identify loop as a DLMS 

enhancement.

33 2/REF01/250 Codes BT, LT, SE: Add standard DLMS 

enhancement note to each.

To identify data as 

enhancements consistent with 

remainder of supplement.

34 2/G6201/260 Add standard DLMS enhancement note 

to each code

To identify data as 

enhancement consistent with 

remainder of supplement.

35 2/N910/270 Add standard DLMS enhancement note 

to each code

To identify data as 

enhancement consistent with 

remainder of supplement.

36 2/N101 and 

N103/280

Add standard DLMS enhancement note 

to each code

To identify data as 

enhancement consistent with 

remainder of supplement.

37 2/QTY/310 Add segment level DLMS note:

"Stratification by receiving activity within 

a single due-in transaction is a DLMS 

enhancement. See introductory DLMS 

note 4.a."

To identify enhanced 

capability.

38 2/FA1/345 loop Add segment level DLMS note: "For use 

in nonprocurement source due-in and ARI 

transactions to convey fund code, when 

applicable. All other data conveyed by 

the 2/FA1/345 loop represent DLMS 

enhancements. See introductory DLMS 

note 4.a."

To clarify use and identify 

DLMS enhancements.