1 of 5 

ADC 157 

Attachment 

ATTACHMENT TO ADC 157 

Optional Capability for Sending Information Copy of DLMS Supplements 527D and 527R to 

a Component Unique Item Tracking (UIT) Registry (Supply) 

1. ORIGINATOR: 

a. Service/Agency: Defense Logistics Management Standards Office (DLMSO).

b. Sponsor: Unique Item Tracking Committee (UITC), Chair: Mary Jane Johnson, DLMSO, 

email: Mary.Jane.Johnson@dla.mil. 

2. REFERENCES: All DLMS Supplements (DS) listed in this memorandum are posted to the 

DLMSO web site at http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/x12.asp. Federal 

Implementation Conventions (IC) are available at http://fedebiz.disa.mil/cgi/advsearch.cgi. 

3. FUNCTIONAL AREA: Primary: Supply

4. REQUESTED CHANGE: 

a. Title. Optional Capability for Sending Information Copy of DLMS Supplements 527D 

and 527R to a Component Unique Item Tracking (UIT) Registry (Staffed by PDC 163) (Supply).

b. Description of Change:

(1) This change updates DLMS supplements 527D and 527R transactions to provide 

capability to send an information copy of the transactions to a stand-alone Component UIT 

registry when/if an integrated AIS approach is not used for UIT. Also adds Uniform Resource 

Locator (URL) to the list of code structures available for the registry, such as DUNS number, 

Department of Defense Activity Address Code (DODAAC), Routing Identifier Code, etc. These 

changes represent DLMS enhancements over Defense Logistics Standard System (DLSS, also 

known as MILS) capability. 

(2) This change supports PDC 147, November 4, 2004, DLMS Unique Item Tracking 

(UIT) Procedures – New Chapter 19 (Supply/UIT). [PDC 147 is currently being revised for 

staffing as PDC 147A, based on discussion at the December 9, 2004, Unique Item Tracking 

Committee meeting.] PDC 147 identified additional changes needed to support DLMS UIT 

procedures, to include a PDC for modification of DS to provide capability to send select 

transactions to a stand-alone UIT registry. This change will meet that requirement for DS 527R 

and 527D. An additional PDC will be staffed to incorporate the requirement for other select DS 

with UIT capability. 

(3) This change does not dictate how DoD Component systems accomplish UIT or 

require/recommend use of a stand alone registry. It merely provides capability to send an 

information copy of the transaction to a registry if required by a Component. DLMS UIT 

procedures may be used with an integrated AIS accommodating UIT data as an integral part of 

the standard logistics AIS, or may be used with stand-alone UIT data registries when required. 

Components must address system changes/design necessary to support UIT. 
2 of 5 

ADC 157 

Att 

5. REASON FOR CHANGE: Provides optional capability to send an information copy of DS 

527D/527R transactions to a stand-alone UIT registry when required by a Component. 

6. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Provides capability to send an information copy of DS 527D and DS 527R 

transactions to a Component UIT registry when required by a Component. This capability is 

optional.

b. Disadvantages: None identified. 

7. IMPACT: Publication(s): DoD 4000.25-M, DLMS, Federal IC for 527D and 527R and 

corresponding DLMS Supplements (DS). If needed, revisions to Federal ICs will be submitted to 

the EDISMC/Logistics Functional Work Group for coordination/approval. Modify 527D and 527R 

as identified in the table below. Changes will be carried over to DLMS XML equivalent 

transactions. No comments were received to PDC 163. DLMSO additional administrative changes 

not identified in PDC 163 are highlighted in the table below. 

Item 

# 

Location DS 527D and DS 527R Revision Reason

Federal 

IC 

Impact

1. DLMS 

Introductory Notes 

Revise DLMS note 1 for DS 527D to add 2 new 

sentences at the end of the note:

...This transaction encompasses the functionality of 

MILSTRAP Document Identifier (DI) Codes DD_, DF_, 

DLC, DLD, DLE, DLF, DU_, and DW_. This 

transaction also accommodates the functionality of 

non-DLSS DI Codes C2G, C2H, and C3C in support of 

Medical requirements. 

Revise DLMS note 1 for DS 527R to add 2 new 

sentences at the end of the note:

...This transaction encompasses the functionality of 

MILSTRAP Document Identifier (DI) Codes D4_, D6_, 

DRA, DRF, DXA, DXB, DXC, and DXD. This 

transaction also accommodates the functionality of 

non-DLSS DI Codes C2J, C2K, and C3D in support of 

Medical requirements, and non-DLSS DI Code BAY in 

support of Army Total Package Fielding. 

Administrative update. No impact. 
3 of 5 

ADC 157 

Att 

Item 

# 

Location DS 527D and DS 527R Revision Reason

Federal 

IC 

Impact

2. 1/BR02/20 For 527D, Revise DLMS notes to add corresponding 

MILSTRAP DI code for information purposes as 

follows:

DA Due-In 

DLMS Note: Managers use to establish due-in 

records. (MILSTRAP DI Code DD_/DF_ functionality) 

DE Advance Receipt 

DLMS Note: Owners use to provide storage activities 

with advance receipt information. (MILSTRAP DI 

Code DU_/DW_ functionality) 

LC Due-in Reconciliation Inquiry 

DLMS Note: GIMs use to initiate a reconciliation of 

all procurement source dues-in for logistically 

reassigned material which was not received. 

(MILSTRAP DI Code DLE functionality)

TI Delinquent Due-in Advice 

DLMS Note: LIMs use to provide GIMs with due-in 

information in response to an inquiry and to provide 

revised Estimated Delivery Dates (EDDs) as changes 

occur. (MILSTRAP DI Code DLD functionality)

TJ Delinquent Due-in Inquiry 

DLMS Note: GIMs use to inquire to LIMs for 

information on delinquent procurement source dues-in. 

(MILSTRAP DI Code DLC functionality)

TK Due-in Reconciliation Advice 

DLMS Note: LIMs use to respond to GIMs due-in 

reconciliation inquiries. (MILSTRAP DI Code DLF 

functionality)

Administrative update to 

provide corresponding 

MILSTRAP DI code for 

information purposes. 

No impact. 
4 of 5 

ADC 157 

Att 

Item 

# 

Location DS 527D and DS 527R Revision Reason

Federal 

IC 

Impact

3. 1/BR02/20 For 527R, Revise DLMS notes to add corresponding 

MILSTRAP DI code for information purposes as 

follows:

D4 Receipt 

DLMS Note: Use when reporting a receipt of material 

into DoD inventory. (MILSTRAP DI Code D4_/D6_ 

functionality) 

DG Response 

DLMS Note: Use when responding to an inquiry 

regarding an over-due receipt. (MILSTRAP DI Code 

DXC/DXD functionality) 

IN Inquiry 

DLMS Note: Use when initiating an inquiry for 

receipt information. (MILSTRAP DI Code DXA/DXB 

functionality) 

TG Receipt Acknowledgement Inquiry 

DLMS Note: Use when initiating an inquiry for 

delinquent MRA. (MILSTRAP DI Code DRF 

functionality)

TH Receipt Acknowledgement Advice 

DLMS Note: Use for MRA to acknowledge the receipt 

or nonreceipt of material. (MILSTRAP DI Code DRA 

functionality)

Administrative update to 

provide corresponding 

MILSTRAP DI code for 

information purposes. 

No impact. 

4. 2/LIN01/10 Change to DS 527D ONLY—Revise LIN01 #20 code T 

note as follows:

20. T - Memorandum notification from the LIM to the 

GIM of anticipated receipt, or return to inventory, 

which is scheduled to be logistically reassigned to the 

GIM when received. For use only with due–in 

transactions (1/BR02/20 code DA). 

Administrative 

clarification for Code T 

applicability. 

No impact. 

5. DLMS 

Introductory Notes 

Add ADC to DLMS note 7:

- ADC 157, Optional Capability for Sending 

Information Copy of DLMS Supplements 527D and 

527R to a Component Unique Item Tracking (UIT) 

Registry (Supply). 

Identifies DLMS 

Changes included in the 

DLMS Supplement 

No impact. 
5 of 5 

ADC 157 

Att 

Item 

# 

Location DS 527D and DS 527R Revision Reason

Federal 

IC 

Impact

6. 2/N101/210 Add code ‘KK-Registering Party’ with DLMS note

KK Registering Party 

DLMS note: 

 

1. Use to identify the Component UIT registry. 

May be used by a Component when their UIT 

process requires that a copy of this 527R 

transaction must also be sent to a UIT registry for 

information purposes. Must be used with 

2/N106/210 code ‘PK-Party to Receive Copy’ to 

identify that this is only an information copy of the 

transaction, for use with the Component UIT 

registry. 

2. DLMS enhancement. See introductory DLMS 

note 5.a. 

To provide optional 

capability to send an 

information copy of a 

transaction to a 

Component UIT 

Registry. 

The note shown at left is 

for the 527R transaction. 

The same note applies to 

527D except that it 

would specify “527D” 

rather than “527R”. 

No impact. 

7. 2/N103/210 Add code ‘UR-Uniform Resource Locator’ with DLMS 

notes: 

UR Uniform Resource Locator (URL) 

DLMS Note: 

1. Use when appropriate to identify the Component 

UIT registry. 

2. DLMS enhancement; see introductory DLMS note 

5.a. 

Adds capability to use a 

URL consistent with 

DLMS UIT capability 

added to DS 140B. 

Revision 

required. 

8. 2/N106/210 Add code ‘PK - Party to Receive Copy’ with DLMS 

note.

PK Party to Receive Copy 

DLMS Note: 

1. Use when appropriate to send an information copy 

of the transaction to a Component UIT registry. For use 

with N101 code KK.

2. DLMS enhancement. See introductory DLMS note 

5.a. 

To provide capability to 

send an information 

copy of a transaction to 

a UIT registry, when 

required by a 

Component.

No impact.