1 of 10 

ADC 165 

Attachment 

ATTACHMENT TO ADC 165 

Optional Capability for Sending Information Copy of DLMS Supplements 856, 856S, 861, 867I, 

870M, 945A, and 947I to a Component Unique Item Tracking (UIT) Registry (Supply) 

1. ORIGINATOR: 

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

b. Sponsors:

(1) Unique Item Tracking Committee, Chair: Mary Jane Johnson, DLMSO/J-6251, 

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

(2) Supply Process Review Committee, Chair: Ellen Hilert, DLMSO/J-6251, email: 

Ellen.Hilert@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. PDC 164, Optional Capability for Sending Information Copy of DLMS 

Supplements 856, 856S, 861, 867I, 870M, 945A, and 947I to a Component Unique Item Tracking 

(UIT) Registry (Supply).

b. Description of Change:

(1) This change updates DLMS supplements (DS) 856, 856S, 861, 867I, 870M, 945A, and 

947I 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), when not already included, 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]. PDC 147 identified additional changes needed to support DLMS UIT 

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

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

856S, 861, 867I, 870M, 945A, and 947I. It is uncertain as systematic UIT evolves, what 

transactions Components may want to send to a stand-alone registry, but this optional capability 

is provided for those identified in this change. 
2 of 10 

ADC 165 

Att 

(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 integrated AIS accommodating UIT data as an integral part of a 

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

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

(4) The basic structure for this capability was approved by ADC 157, Optional Capability 

for Sending Information Copy of DLMS Supplements 527D and 527R to a Component Unique 

Item Tracking (UIT) Registry, March 31, 2005. 

(5) This change revises the following DLMS Supplements/versions: 

DS # Name ANSI Version

856 Advance Ship Notice 4010 

856S Shipment Status 4030 

861 Acceptance Report 4010 

867I Issue 4010 

870M Materiel Returns Supply Status 4010 

945A Materiel Release Advice 4010 

947I Inventory Adjustment 4030 

5. REASON FOR CHANGE: Some Component UIT systems may require use of a UIT 

registry. This change provides optional capability to send an information copy of DS 856, 856S, 

861, 867I, 870M, 945A, and/or 947I transactions to a UIT registry when required by a Component. 

6. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: Provides optional capability to send an information copy of 856, 856S, 

861, 867I, 870M, 945A, and 947I transactions to a Component UIT registry when required by a 

Component. 

b. Disadvantages: None identified. 
3 of 10 

ADC 165 

Att 

7. IMPACT: Publication(s): DOD 4000.25-M, DLMS, Federal IC for 856, 856S, 861, 867I, 

870M, 945A, and 947I 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 856, 856S, 861, 867I, 870M, 945A, and 947I as identified in the 

table below. Changes will be carried over to DLMS XML equivalent transactions. 

Item 

# 

Location Advance Ship Notice (ASN) 

DS 856 (Version 4010) Revision 

Reason

Federal 

IC 

Impact

1. DLMS 

Introductory Notes 

Add note 7 reading: 

7. This revision to the DLMS Supplement incorporates 

Approved DLMS Change (ADC) listed. ADCs are 

available from the DLMSO website: 

http://www.dla.mil/j-6/dlmso/Changes 

- ADC 165, Optional Capability for Sending 

Information Copy of DLMS Supplements 856, 

856S, 861, 867I, 870M, 945A, and 947I to a 

Component Unique Item Tracking (UIT) Registry 

(Supply).

Identifies DLMS 

Changes included in the 

DLMS Supplement 

No impact. 

2. 2/N1/220 Add N1 Segment level note:

DLMS note: 

Must use at least one iteration of this N1segment to 

identify the organization to receive the transaction 

(N106 code TO with appropriate N101 code). May use 

additional iterations to identify other organizations 

associated with the transaction.

To clarify use of the N1 

segment. 

No impact 

3. 2/N101/220 Add code ‘KK-Registering Party’ with DLMS note

KK Registering Party 

DLMS note: 

Use to identify the Component UIT registry. May be 

used by a Component when their UIT process requires 

that a copy of the transaction also be sent to a UIT 

registry for information purposes. Must be used with 

2/N106/220 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. 

To provide optional 

capability to send an 

information copy of a 

transaction to a 

Component UIT 

Registry. 

Revision 

required. 

4. 2/N103/220 Add code ‘UR-Uniform Resource Locator’ with

DLMS notes: 

UR Uniform Resource Locator (URL) 

DLMS Note: 

Use when appropriate to identify the Component UIT 

registry. 

Adds optional capability 

to use a URL for a UIT 

registry. 

Revision 

required. 
4 of 10 

ADC 165 

Att 

Item 

# 

Location Advance Ship Notice (ASN) 

DS 856 (Version 4010) Revision 

Reason

Federal 

IC 

Impact

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

note.

PK Party to Receive Copy 

DLMS Note: 

Use when appropriate to send an information copy of 

the transaction to a Component UIT registry. For use 

with N101 code KK. 

To provide capability to 

send an information 

copy of a transaction to a 

UIT registry, when 

required by a 

Component.

Revision 

required. 

Item 

# 

Location Shipment Status 

DS 856S (Version 4030) Revision 

Reason

Federal 

IC 

Impact

1 DLMS 

Introductory 

Notes 

Add to DLMS note 3 

- ADC 165, Optional Capability for Sending Information 

Copy of DLMS Supplements 856, 856S, 861, 867I, 

870M, 945A, and 947I to a Component Unique Item 

Tracking (UIT) Registry (Supply). 

Identifies DLMS 

Changes included in the 

DLMS Supplement 

No impact. 

2.. 2/N101/2200 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 the transaction also be sent to a UIT 

registry for information purposes. Must be used with 

2/N106/2200 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 2.a. 

To provide optional 

capability to send an 

information copy of a 

transaction to a 

Component UIT 

Registry. 

No Impact 
5 of 10 

ADC 165 

Att 

Item 

# 

Location Shipment Status 

DS 856S (Version 4030) Revision 

Reason

Federal 

IC 

Impact

3. 2/N103/2200 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 2.a. 

 

Adds optional capability 

to use a URL for a UIT 

registry. 

No Impact 

4 2/N106/2200 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 2.a. 

To provide capability to 

send an information 

copy of a transaction to a 

UIT registry, when 

required by a 

Component.

Revision 

required. 

Item 

# 

Location Acceptance Report 

DS 861 (version 4010) 

Reason

Federal 

IC 

Impact

1. DLMS 

Introductory Notes 

Add to DLMS note:

- ADC 165, Optional Capability for Sending 

Information Copy of DLMS Supplements 856, 856S, 

861, 867I, 870M, 945A, and 947I to a Component 

Unique Item Tracking (UIT) Registry (Supply) 

Identifies DLMS 

Changes included in the 

DLMS Supplement 

No impact. 

2. 1/N1/130 Add N1 Segment level note:

DLMS note: 

Must use at least one iteration of this N1 segment to 

identify the organization to receive the transaction 

(N106 code TO with appropriate N101 code). May use 

additional iterations to identify other organizations 

associated with the transaction.

To clarify use of the N1 

segment. 

No impact 
6 of 10 

ADC 165 

Att 

Item 

# 

Location Acceptance Report 

DS 861 (version 4010) 

Reason

Federal 

IC 

Impact

3. 1/N101/130 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 the transaction also be sent to a UIT 

registry for information purposes. Must be used with 

2/N106/130 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. 

To provide optional 

capability to send an 

information copy of a 

transaction to a 

Component UIT 

Registry. 

Revision 

required 

4. 1/N103/130 Add code ‘UR-Uniform Resource Locator’ with DLMS 

notes: 

UR Uniform Resource Locator (URL) 

DLMS Note: 

Use when appropriate to identify the Component UIT 

registry. 

Adds optional capability 

to use a URL for a UIT 

registry. 

Revision 

required. 

5. 1/N106/130 Add code ‘PK - Party to Receive Copy’ with DLMS 

note.

PK Party to Receive Copy 

DLMS Note: 

 Use when appropriate to send an information copy of 

the transaction to a Component UIT registry. For use 

with N101 code KK. 

To provide capability to 

send an information 

copy of a transaction to 

a UIT registry, when 

required by a 

Component.

Revision 

required 
7 of 10 

ADC 165 

Att 

Item 

# 

Location Issue 

DS 867I (Version 4010) Revision 

Reason

Federal 

IC 

Impact

1. DLMS 

Introductory 

Notes 

Add to DLMS note 7:

- ADC 165, Optional Capability for Sending Information 

Copy of DLMS Supplements 856, 856S, 861, 867I, 870M, 

945A, to a Component Unique Item Tracking (UIT) 

Registry (Supply). 

Identifies DLMS 

Changes included in the 

DLMS Supplement 

No impact. 

2. 2/N1/050 Add N1 Segment level note:

DLMS note: 

Must use at least one iteration of this N1 segment to 

identify the organization to receive the transaction (N106 

code TO with appropriate N101 code). May use additional 

iterations to identify other organizations associated with 

the transaction.

To clarify use of the N1 

segment. 

No impact 

3. 2/N101/50 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 the transaction also be sent to a UIT 

registry for information purposes. Must be used with 

2/N106/50 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. 

No impact 

4. 2/N106/50 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.

Revision 

required. 
8 of 10 

ADC 165 

Att 

Item 

# 

Location Materiel Returns Supply Status 

DS 870M (Version 4010) Revision 

Reason

Federal 

IC 

Impact

1. DLMS 

Introductory 

Notes 

Add to DLMS note 6:

- ADC 165, Optional Capability for Sending Information 

Copy of DLMS Supplements 856, 856S, 861, 867I, 870M, 

945A, and 947I to a Component Unique Item Tracking 

(UIT) Registry (Supply). 

Identifies DLMS 

Changes included in the 

DLMS Supplement 

No impact. 

2. 2/N1/90 Add N1 Segment level note:

DLMS note: 

Must use at least one iteration of this N1 segment to 

identify the organization to receive the transaction (N106 

code TO with appropriate N101 code). May use additional 

iterations to identify other organizations associated with 

the transaction.

To clarify use of the N1 

segment. 

No impact 

3. 2/N101/90 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 the transaction also be sent to a UIT registry for 

information purposes. Must be used with 2/N106/90 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 4.a 

To provide optional 

capability to send an 

information copy of a 

transaction to a 

Component UIT 

Registry. 

No impact. 

4. 2/N103/90 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 4.a. 

Adds optional capability 

to use a URL for a UIT 

registry. 

Revision 

required. 

5. 2/N106/90 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 4.a. 

To provide capability to 

send an information 

copy of a transaction to 

a UIT registry, when 

required by a 

Component.

Revision 

required. 
9 of 10 

ADC 165 

Att 

Item 

# 

Location Materiel Release Advice 

DS 945A (Version 4010) Revision 

Reason

Federal 

IC 

Impact

1. DLMS 

Introductory 

Notes 

Add to DLMS note 5:

- ADC 165, Optional Capability for Sending Information 

Copy of DLMS Supplement 856, 856S, 861, 867I, 870M, 

945A, and 947I to a Component Unique Item Tracking 

(UIT) Registry (Supply). 

Identifies DLMS 

Changes included in the 

DLMS Supplement 

No impact. 

2. 2/N1/80 Add N1 Segment level note:

DLMS note: 

Must use at least one iteration of this N1 segment to 

identify the organization to receive the transaction (N106 

code TO with appropriate N101 code). May use additional 

iterations to identify other organizations associated with 

the transaction.

To clarify use of the N1 

segment. 

No impact 

3. 2/N101/80 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 the transaction also be sent to a UIT registry for 

information purposes. Must be used with 2/N106/80 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 3.a. 

To provide optional 

capability to send an 

information copy of a 

transaction to a 

Component UIT 

Registry. 

No impact. 

4. 2/N103/80 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 3.a. 

Adds optional capability 

to use a URL for a UIT 

registry. 

Revision 

required. 

5. 2/N106/80 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 3.a. 

To provide capability to 

send an information 

copy of a transaction to 

a UIT registry, when 

required by a 

Component.

Revision 

required 
10 of 10 

ADC 165 

Att 

Item 

# 

Location Inventory Adjustment 

DS 947I (Version 4030) Revision 

Reason

Federal 

IC 

Impact

1. DLMS 

Introductory 

Notes 

Add to DLMS note 6:

- ADC 165, Optional Capability for Sending Information 

Copy of DLMS Supplements 856, 856S, 861, 867I, 870M, 

945A, and 947I to a Component Unique Item Tracking 

(UIT) Registry (Supply). 

Identifies DLMS 

Changes included in the 

DLMS Supplement 

No impact. 

2. 2/N1/1100 Add N1 Segment level note:

DLMS note: 

Must use at least one iteration of this N1 segment to 

identify the organization to receive the transaction (N106 

code TO with appropriate N101 code). May use additional 

iterations to identify other organizations associated with 

the transaction.

To clarify use of the N1 

segment. 

No impact 

3. 2/N101/1100 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 the transaction also be sent to a UIT registry for 

information purposes. Must be used with 2/N106/1100 

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

To provide optional 

capability to send an 

information copy of a 

transaction to a 

Component UIT 

Registry. 

No impact. 

4. 2/N106/1100 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 4.a. 

To provide capability to 

send an information 

copy of a transaction to 

a UIT registry, when 

required by a 

Component.

No impact.