1 of 4 

ADC 347 

Attachment 

ATTACHMENT TO ADC 347 

Revise DLMS Supplement (DS) 527R Receipt, 867I Issue, 945A Materiel Release Advice, 

and 947I Inventory Adjustment to Support Unique Item Tracking (UIT) for Air Force 

Positive Inventory Control (PIC) (Supply) 

1. ORIGINATOR: Defense Logistics Management Standards Office (DLMSO), Mary Jane Johnson, 

703-767-0677, DSN 427-0677, email: Mary.Jane.Johnson@dla.mil; and Ellen Hilert, 703-767-0676; 

DSN 427-0676, email: Ellen.Hilert@dla.mil. 

2. FUNCTIONAL AREA: Supply, UIT 

3. REFERENCES:

a. DLMSO memorandum, September 29, 2009, subject: Proposed DLMS Change (PDC) 370, Revise 

DLMS Supplement (DS) 527R Receipt, 867I Issue, 945A Materiel Release Advice, and 947I Inventory 

Adjustment to Support Unique Item Tracking (UIT) for Air Force Positive Inventory Control (PIC) (Supply) 

b. September 22, and September 30, 2009 telecons among DLMSO, AF PIC Fusion personnel, AF 

Supply Process Review Committee (SPRC) representative, Defense Automated Addressing System 

Center(DAASC), and DLA (HQ J33, J6U DSS, J6N DDC) 

4. PROPOSED CHANGE: 

a. Title/Description of Change/Background: 

(1) Title: Revise DLMS Supplement (DS) 527R Receipt, 867I Issue, 945A Materiel Release 

Advice, and 947I Inventory Adjustment to Support Unique Item Tracking for Air Force Positive 

Inventory Control (PIC) (Supply) 

(2) Description of Change: This change revises DLMS transactions support receipt, issue, 

materiel release advice, and inventory adjustment (DS 527R, 867I, 945A, and 947I) to allow a new 

action code which will clearly identify their use as “image” transactions which do not affect the 

accountable records when the balance-affecting accountable transaction bypassed the normal Defense 

Automated Addressing System Center (DAASC) transaction flow. Once available as an image 

transaction, the DLMS transaction containing information pertaining to the specific business process 

and the applicable serial number(s) may be passed to a designated party for information. 

Note: As noted in PDC 370 (reference 3a) and during September 2009 telecons (reference 3b), USAF 

must identify any additional DLMS standard logistics transaction functions for which serial number is 

required for PIC Fusion. 

(3) Background: 

(a) UIT under DLMS is accomplished with standard logistics transactions. However when 

UIT was first established in the Distribution Standard System (DSS) for use with the Navy Depot Level 

Reparable UIT program in 2002, DSS had not yet fully implemented DLMS. Specifically DSS had not 

yet implemented DLMS for balance affecting transactions to include DLMS 527R Receipt. DLMS 

140B was authorized for use with DSS UIT Phase 1 for a temporary period to provide visibility of 

receipt information serial numbers for UIT assets. Use of 140B for use with receipt information was to 

be phased out under DSS UIT Phase 2. DLMSO understanding was that when DSS implemented UIT 

Phase 2 (implemented balance affecting transactions to include 527R Receipt) several years ago, DSS 

would no longer generate DLMS 140B for receipt UIT information. 
2 of 4 

ADC 347 

Attachment 

(b) Presently, due to a Customer Information Control System (CICS) direct interface between 

DSS and the Air Force (AF) D035K system, which bypasses normal DAASC processing, DSS sends the 

D035K trading partner operating in MILS, MLSTRAP Document Identifier (DI) Code D4_/D6_ receipt 

transactions which cannot accommodate serial numbers under their 80 record position constraints. In 

2009 USAF established a UIT program for PIC Nuclear Weapon Related Materiel (NWRM) and DSS 

started sending a 140B transaction through DAASC for AF PIC NWRM serial numbers associated with 

MILSTRAP D4_/D6_receipt sent direct to D035K. DAASC in turn converts the 140B from DSS for 

transmission via DAASC Integrated E-mail LOGistics (DIELOG), which DAAS then sends to a DIELOG 

email account established on behalf of D035K. The 140B transaction formatted as ASC X12 which DSS 

sent to DAAS is not being sent to any AF application today in the 140B structure. 

(c) In September 2009 AF began discussing expanding use of 140B to additional DLMS 

functions for a new AF PIC Fusion interface. AF identified a requirement for issue transactions, materiel 

release advice, inventory adjustment, and possibly other transactions to be determined. DLMSO objected 

to this nonstandard approach and expansion of the use of 140B, and strongly recommended an integrated 

approach to include serial number within the standard logistics transaction supporting the functional 

requirement: e.g., 527R receipt, 867I Issue, 945A Materiel Release Advice, 947I Inventory Adjustment, 

rather than through an independent transaction which must then be interpreted and associated with the 

previously transmitted transaction for the designated functional process. 

b. Revise DS 527R, 867I, 945A, and 947I (version 4010 and version 4030) as shown in the 

enclosure. Note: For IUID, DS 947I version 4030 is required.

5. REASON FOR CHANGE: To establish capability to transmit an image transaction for unique 

item tracking, thereby allowing the DSS to pass serial number information to AF PIC Fusion for PIC 

NWRM UIT using the integrated DLMS transaction, even when DSS sends the AF D035K trading 

partner MILSTRIP/MILSTRAP transactions via a CICS interface bypassing DAAS. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages 

(1) Supports AF NWRM PIC Fusion which is a Secretary of the Air Force top priority. 

Provides AF PIC Fusion integrated serial number requirements in the appropriate DLMS transaction 

for a given logistic function, rather than a disjointed approach of PIC fusion receiving 2 separate 

independent transactions (140B and MILSTRIP/MILSTRAP transactions) from 2 disparate systems 

(D035K and DAAS) which PIC Fusion must then marry up to reflect the serial number information. 

(2) Supports OSD Supply Chain Integration Office Item Unique Identification (IUID) 

approach to IUID documented in several SCI IUID workshops conducted with all DOD Components 

(February through June 2009). The IUID workshops addressed the requirement for using standard 

DLMS logistics transactions to convey IUID information. 

(3) Positions AF NWRM PIC Fusion Center application for IUID. The DLMS standard 

logistics transactions for receipt (527R), issue (867I), materiel release advice (945A), and inventory 

adjustment (947I Version 4030 only) all have the capability to pass the IUID unique item identifier (UII). 

This will eliminate rework for transition to IUID use of standard logistics transactions when implemented.

(4) Positions DSS applications for IUID. DLMS standard logistics transactions will be 

required to pass IUID data. 

(5) Halts proliferation of a non-standard, inefficient approach to UIT. 
3 of 4 

ADC 347 

Attachment 

(6) Adopts planned functionality to transmit DLMS transactions to registry/tracking 

programs when required in addition to the designated owner/manager. 

 b. Disadvantages: Requires a DSS and DAAS system change. When serial number information 

is required for PIC NWRM, DSS system requires update to pass the standard DLMS transaction with 

serial numbers and the new beginning segment action code, in addition to the associated MILSTRIP or 

MILSTRAP transaction being sent to the AF D035K system. DAAS will need to recognize the 

indicator for an “image” transaction so that accountable/standard DLMS or the equivalent MILS 

transactions will not be forwarded to the owner/manager or otherwise trigger duplication of information. 

7. RESPONSES TO PDC 370: 

COMPONENT RESPONSE DISPOSITION

DLA Concurs without comment. Noted. 

AIR FORCE Concurs. did not, however, receive verification from PIC Fusion 

personnel on whether a Routing Identifier Code would be required for 

the PIC Fusion Center.

Noted. AF must advise 

DLMSO immediately if 

a routing identifier code 

is not being assigned for 

PIC Fusion. 

NAVY Concurs as written. Noted. 

USTRANSCOM Abstains. Noted. 

DLMSO 

(Heidi 

Daverede) 

For qualifier 945A W0612 Action Code "FI", we need to add an 

additional instruction that says "This is not authorized for use when the 

distribution code = 111 and the message supports the Retail 

Transportation and Supply Receipt and Acknowledgement Interchange 

(See DoD 4000.25-M, Volume 3, Chapter 2)." 

Per ADC 316, the 945A already uses the W0612 Action Code (A6, CN, 

ME) to flag 945A transactions for retail supply/transportation. If 

NWRM PIC decides to need copies of these 945A retail 

supply/transportation transactions, the "FI" qualifier can't be used since 

the Action Code is already in use. DLMSO is preparing an addendum to 

ADC 316C that uses the N1 "KK" and "PK" to flag the ADC 316 for 

image routing to NWRM PIC in addition to normal routing to retail 

supply activity as indicated in the N106 "TO" instance. 

Recommend revising the 1/W0612/20 new Action Code 'FI' DLMS note 

as follows (change has bold, italics): 

FI File 

DLMS Note: Authorized for Air Force and DSS use with PIC NWRM 

UIT, except when the distribution code = 111 and the message 

supports the Retail Transportation and Supply Receipt and 

Acknowledgement Interchange (See DoD 4000.25-M, Volume 3, 

Chapter 2). Use with W0611 Code NJ, NK, and Code NM to identify a 

material or disposal release confirmation and materiel release denial 

image transactions where the original transaction has bypassed the 

normal DAAS transaction flow. All transaction set recipients must use 

extreme caution to ensure that individual transactions with this code do 

not process as action documents which affect accountable records. Must 

use with 2/N101/80 code ‘KK’ and 2/N106/80 code ‘PK’. There will be 

no 2/N106/80 code ‘TO’ for this transaction. 

Concur. Change 

incorporated in the 945A 

Change Table at the 

enclosure. 

 
4 of 4 

ADC 347 

Attachment 

8. IMPACT: 

a. Publication(s): DLMS 527R, 867I, 945A, and 947I (versions 4010 and 4030) 

b. Systems/Applications: DAAS, DSS and AF PIC Fusion Center application. 

c. DAASC Mapping: Updates required to DAASC mapping. 

d. DLMS Data Element: This change adds the existing data element for Image Transaction Flag 

(beginning segment code mapped to X12 qualifier FI, File) to additional transactions as specified. 

Enclosure 
1 of 6 

ADC 347 

Enclosure 

ENCLOSURE TO ADC 347 

DLMS Supplement (DS) Change Tables 

Changes from PDC 370 are highlighted in yellow 

Item 

# 

Location DS 527R Receipt 

Recommended Change for PIC 

Reason 

1. DLMS 

Introductory 

Note

Add ADC 347 to Introductory note for 

PDCs/ADCs:

- ADC 347, Revise DLMS Supplement (DS) 527R 

Receipt, 867I Issue, 945A Materiel Release 

Advice, and 947I Inventory Adjustment to Support 

Unique Item Tracking for Air Force Positive 

Inventory Control (PIC) 

To identify DLMS changes included in the 

DS 

2. 1/BR06/20 Add new Action Code ‘FI’ with DLMS note: 

FI File 

DLMS Note: 

Authorized for Air Force and DSS use with PIC 

NWRM UIT. Use with BR02 Code D4 to identify 

a receipt image transaction where the original 

receipt transaction has bypassed the normal 

DAAS transaction flow. All transaction set 

recipients must use extreme caution to ensure 

that individual transactions with this code do 

not process as action documents which affect 

accountable records. Must use with 

2/N101/210 code ‘KK’ and 2/N106/210 code 

‘PK’. There will be no 2/N106/210 code ‘TO’ for 

this transaction. Refer to ADC 347. 

To clearly identify that a 527R receipt 

transaction, going from DSS through DAAS to 

AF PIC Fusion, is an information copy not 

affecting the balance. 

USAF D035K has CICS interface with DSS. 

Through the CICS interface DSS sends 

MILSTRAP DI Code D4_/D6_ receipt 

transactions directly to Do35K without going 

through DAASC. 

If interface was through DAAS, then DSS 

would have sent 527R Receipt to DAASC and 

DAAS could create MILS D4/D6 for USAF 

D035K trading partner still operating in MILS, 

and DAAS could have sent an information copy 

of 527R with the serial numbers to AF PIC 

Fusion for PIC NWRM. 

This revised approach will provide AF PIC 

Fusion with an integrated receipt transaction 

generated by DSS with serial numbers 

incorporated. 

Note: AF was tasked in PDC 370 to verify 

that a Routing Identifier was, or would be, 

assigned for PIC Fusion Center or else there 

was a need to identify an alternative for 

mapping – N102 or N103 required. USAF 

did not confirm RI code assignment---but also 

did not indicate an alternative to RI Code was 

required. Assumption, unless USAF states 

otherwise is that RI Code assignment is being 

made for PIC Fusion.

3. 2/N101/210 Revise note 1and add new DLMS note 2 to 

existing code KK:

KK Registering Party 

DLMS Notes: 

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 the transaction 

must also be sent to a UIT registry for information 

purposes. Must be used with 2/N106/210 code ‘PKParty to Receive Copy’ to identify that this is only an 

information copy of the transaction, for use with the 

Component UIT registry. Cite the applicable 

Routing Identifier in 2/N103. 

2. Authorized DLMS enhancement for Air 

Force and DSS use with PIC NWRM UIT; For 

PIC UIT, must use in conjunction with 2/N106 

code PK and 1/BR06/20 Action Code FI and 

cite the applicable Routing Identifier in 

2/N103.

3. Except as noted above, DLMS enhancement; 

see introductory DLMS note 5a. 
2 of 6 

ADC 347 

Enclosure 

Item 

# 

Location DS 527R Receipt 

Recommended Change for PIC 

Reason 

4. 2/N106/210 Add new DLMS note 2 to existing code PK:

PK Party To Receive Copy 

DLMS Notes: 

1.Use when appropriate to send an information 

copy of the transaction to a Component UIT 

registry. For use with N101 code KK. 

2. Authorized DLMS enhancement for Air Force 

and DSS use with PIC NWRM UIT. For PIC 

UIT, must use in conjunction with 2/N101 

code KK and 1/BR06/20 Action Code FI and 

cite the applicable Routing Identifier in 

2/N103. 

3. Except as noted above, DLMS enhancement; 

see introductory DLMS note 5a.

Item 

# 

Location DS 867I Issue 

Recommended Change for PIC 

Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 347 to Introductory note for 

PDCs/ADCs:

- ADC 347, Revise DLMS Supplement (DS) 527R 

Receipt, 867I Issue, 945A Materiel Release 

Advice, and 947I Inventory Adjustment to Support 

Unique Item Tracking for Air Force Positive 

Inventory Control (PIC) 

To identify DLMS changes included in the DS 

2. 1/BPT07/20 Add new Action Code ‘FI’ with DLMS note: 

FI File 

DLMS Note: 

Authorized for Air Force and DSS use with PIC 

NWRM UIT. Use to identify an issue image 

transaction where the original issue 

transaction has bypassed the normal DAAS 

transaction flow. All transaction set recipients 

must use extreme caution to ensure that 

individual transactions with this code do not 

process as action documents which affect 

accountable records. Must use with 2/N101/50 

code ‘KK’ and 2/N106/50 code ‘PK’. There will 

be no 2/N106/50 code ‘TO’ for this transaction. 

Refer to ADC 347. 

To clearly identify that an 867I Issue transaction, 

going from DSS through DAASC to AF PIC 

Fusion, is an information copy not affecting the 

balance. 

USAF D035K has CICS interface with DSS. 

Through the CICS interface DSS sends 

MILSTRAP DI Code D7_ issue transactions 

directly to D035K without going through 

DAASC. 

If the interface had been through DAAS, then 

DSS would have sent 867I Issue to DAASC and 

DAAS could create MILS D7_ for USAF D035K 

trading partner still operating in MILS, and 

DAAS could have sent an information copy of 
3 of 6 

ADC 347 

Enclosure 

Item 

# 

Location DS 867I Issue 

Recommended Change for PIC 

Reason 

3. 2/N101/50 Revise note 1 and add new DLMS note 2 to 

existing code KK:

KK Registering Party 

DLMS Notes: 

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. 

Cite the applicable Routing Identifier in 

2/N103. 

2. Authorized DLMS enhancement for Air 

Force and DSS use with PIC NWRM UIT; For 

PIC UIT, must use in conjunction with 2/N106 

code PK and 1/BPT07/20 Action Code FI and 

cite the applicable Routing Identifier in 

2/N103. 

3. Except as noted above, DLMS enhancement; 

see introductory DLMS note 5a. 

the 867I to AF PIC Fusion for PIC NWRM. 

This revised approach will provide AF PIC 

Fusion with an integrated Issue transaction 

generated by DSS with serial numbers 

incorporated. 

Note: AF was tasked in PDC 370 to verify 

that a Routing Identifier was, or would be, 

assigned for PIC Fusion Center or else there 

was a need to identify an alternative for 

mapping – N102 or N103 required. USAF did 

not confirm RI code assignment---but also did 

not indicate an alternative to RI Code was 

required. Assumption, unless USAF states 

otherwise, is that RI Code assignment is being 

made for PIC Fusion.

4. 2/N101/50 Add new DLMS note 2 to existing code PK:

PK Party To Receive Copy 

DLMS Notes: 

1. Use when appropriate to send an 

information copy of the transaction to a 

Component UIT registry. For use with N101 code 

KK. 

2. Authorized DLMS enhancement for Air 

Force and DSS use with PIC NWRM UIT. For 

PIC UIT, must use in conjunction with 2/N101 

code KK and 1/BPT07/20 Action Code FI and 

cite the applicable Routing Identifier in 

2/N103. 

3. Except as noted above, DLMS enhancement; 

see introductory DLMS note 5a.
4 of 6 

ADC 347 

Enclosure 

Item 

# 

Location DS 945A Materiel Release Advice 

Recommended Change for PIC

Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 347 to Intro note for PDCs/ADCs:

- ADC 347, Revise DLMS Supplement (DS) 527R 

Receipt, 867I Issue, 945A Materiel Release Advice, 

and 947I Inventory Adjustment to Support Unique 

Item Tracking for Air Force Positive Inventory 

Control (PIC) 

To identify DLMS changes included in the 

DS 

2. 1/W0612/20 Add new Action Code ‘FI’ with DLMS notes: 

FI File 

DLMS Note: Authorized for Air Force and DSS 

use with PIC NWRM UIT, except when the 

distribution code = 111 and the message 

supports the Retail Transportation and Supply 

Receipt and Acknowledgement Interchange 

(See DoD 4000.25-M, Volume 3, Chapter 2). 

Use with W0611 Code NJ, NK, and Code NM to 

identify a material or disposal release 

confirmation and materiel release denial image

transactions where the original transaction has 

bypassed the normal DAAS transaction flow. 

All transaction set recipients must use extreme 

caution to ensure that individual transactions 

with this code do not process as action 

documents which affect accountable records. 

Must use with 2/N101/80 code ‘KK’ and 

2/N106/80 code ‘PK’. There will be no 

2/N106/80 code ‘TO’ for this transaction. Refer 

to ADC 347. 

To clearly identify when a 945A transaction, 

going from DSS through DAASC to AF PIC 

Fusion, is an information copy not affecting the 

balance. 

See the DLMSO comment at paragraph 7, 

RESPONSES TO PDC 370, for an 

explanation of new change at left. 

USAF D035K has CICS interface with DSS. 

Through the CICS interface DSS sends 

MILSTRIP DI Code AR__ and A6_ 

transactions directly to D035K without going 

through DAASC. 

If the interface had been through DAAS, then 

DSS would have sent 945A to DAASC and 

DAAS could create MILSTRIP DI Code 

AR_/A6_ for USAF D035K trading partner still 

operating in MILS, and DAAS could have sent 

an information copy of the 945A to AF PIC 

Fusion for PIC NWRM. 

This revised approach will provide AF PIC 

Fusion with an integrated Materiel Release 

Advice transaction generated by DSS with serial 

numbers incorporated. 

Note: AF was tasked in PDC 370 to verify 

that a Routing Identifier was, or would be, 

assigned for PIC Fusion Center or else there 

was a need to identify an alternative for 

mapping – N102 or N103 required. USAF 

did not confirm RI code assignment---but also 

did not indicate an alternative to RI Code was 

required. Assumption, unless USAF states 

otherwise is that RI Code assignment is being 

made for PIC Fusion.

3. 2/N101/80 Revise note 1 and add new DLMS note 2 to 

existing code KK:

KK Registering Party 

DLMS Notes: 

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. 

Cite the applicable Routing Identifier in 

2/N103. 

2. Authorized DLMS enhancement for Air 

Force and DSS use with PIC NWRM UIT; For 

PIC UIT, must use in conjunction with 2/N106 

code PK and 1/W0612/20 Action Code FI and 

cite the applicable Routing Identifier in 

2/N103. 

3. Except as noted above, DLMS enhancement; 

see introductory DLMS note 3a. 
5 of 6 

ADC 347 

Enclosure 

Item 

# 

Location DS 945A Materiel Release Advice 

Recommended Change for PIC

Reason 

4. 2/N101/80 Add new DLMS note 2 to existing code PK:

PK Party To Receive Copy 

DLMS Notes: 

1. Use when appropriate to send an information 

copy of the transaction to a Component UIT 

registry. For use with N101 code KK. 

2. Authorized DLMS enhancement for Air 

Force and DSS use with PIC NWRM UIT. For 

PIC UIT, must use in conjunction with 2/N101 

code KK and 1/W0612/20 Action Code FI and 

cite the applicable Routing Identifier in 

2/N103. 

3. Except as noted above, DLMS 

enhancement; see introductory DLMS note 3a. 

Item 

# 

Location 

Version 

4030 

DS 947I Inventory Adjustment 

(Table Locations address 947I version 4030, 

corresponding changes are being made to 

947I version 4010) 

Reason 

1. DLMS 

Introductory

Notes 

Add ADC 347 to Intro note for PDCs/ADCs:

- ADC 347, Revise DLMS Supplement (DS) 527R 

Receipt, 867I Issue, 945A Materiel Release Advice, 

and 947I Inventory Adjustment to Support Unique 

Item Tracking for Air Force Positive Inventory 

Control (PIC) 

To identify DLMS changes included in the 

DS 

2. 1/W1506/ 

0200 

Add new Action Code ‘FI’ with DLMS note: 

FI File 

DLMS Note: 

Authorized for Air Force and DSS use with PIC 

NWRM UIT. Use with W1505 Code NU to 

identify a material or disposal release 

confirmation and materiel release denial image

transactions where the original transaction has 

bypassed the normal DAAS transaction flow. 

All transaction set recipients must use extreme 

caution to ensure that individual transactions 

with this code do not process as action 

documents which affect accountable records. 

Must use with 2/N101/1100 code ‘KK’ and 

2/N106/1100 code ‘PK’. There will be no 

2/N106/1100 code ‘TO’ for this transaction. 

Refer to ADC 347. 

To clearly identify when a 947I Inventory 

Adjustment transaction, going from DSS 

through DAASC to AF PIC Fusion, is an 

information copy not affecting the balance. 

USAF D035K has CICS interface with DSS. 

Through the CICS interface DSS sends 

MILSTRAP DI Code D8_, D9_, and DAC 

transactions directly to D035K without going 

through DAAS. 

If the interface had been through DAAS, then 

DSS would have sent a 947I to DAAS and 

DAAS could create MILSTRAP DI Code 

D8_/D9_/DAC for the USAF D035K trading 

partner still operating in MILS, and DAAS 

could have sent an information copy of the 947I 

to AF PIC Fusion for PIC NWRM. 
6 of 6 

ADC 347 

Enclosure 

Item 

# 

Location 

Version 

4030 

DS 947I Inventory Adjustment 

(Table Locations address 947I version 4030, 

corresponding changes are being made to 

947I version 4010) 

Reason 

3. 2/N101/1100 

Also adds 

KK to 947I 

version 4010 

Revise note 1 and add new DLMS note 2 to 

existing code KK:

KK Registering Party 

DLMS Notes: 

1. Use to identify the Component UIT registry. May 

be used by a Component when their UIT process 

requires that a copy of the inventory adjustment

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. 

Cite the applicable Routing Identifier in 

2/N103. 

2. Authorized DLMS enhancement for Air 

Force and DSS use with PIC NWRM UIT; For 

PIC UIT, must use in conjunction with 2/N106 

code PK and 1/W1506/0200 Action Code FI 

and cite the applicable Routing Identifier in 

2/N103. 

3. Except as noted above, DLMS enhancement; 

see introductory DLMS note 4a. 

This revised approach will provide AF PIC 

Fusion with an integrated DLMS Inventory 

Adjustment transaction generated by DSS with 

serial numbers incorporated. 

Note: AF was tasked in PDC 370 to verify 

that a Routing Identifier was, or would be, 

assigned for PIC Fusion Center or else there 

was a need to identify an alternative for 

mapping – N102 or N103 required. USAF 

did not confirm RI code assignment---but also 

did not indicate an alternative to RI Code was 

required. Assumption, unless USAF states 

otherwise, is that RI Code assignment is being 

made for PIC Fusion.

Note: 2/N101 codes KK and PK are currently 

available in 947I version 4030, but are not 

currently in version 4010. They are being 

added to version 4010 by this change.

4. 2/N101/1100 

Also adds 

PK to 947I 

version 4010 

Add new DLMS note 2 to existing code PK:

PK Party To Receive Copy 

DLMS Notes: 

1. Use when appropriate to send an information 

copy of the transaction to a Component UIT 

registry. For use with N101 code KK. 

2. Authorized DLMS enhancement for Air 

Force and DSS use with PIC NWRM UIT. For 

PIC UIT, must use in conjunction with N101 

code KK and 1/W1506/0200 Action Code FI 

and cite the applicable Routing Identifier in 

2/N103. 

3. Except as noted above, DLMS 

enhancement; see introductory DLMS note 4a.