Attachment, ADC 1244

Page 1

Attachment to ADC 1244

Establishing Visibility of Unique Item Tracking (UIT) Program Items 

for Service-Owned Assets Stored at DLA Distribution Centers and 

Corresponding Revisions to Inventory Procedures Related to Capital 

Equipment

1. ORIGINATING SERVICE/AGENCY AND POINT OF CONTACT (POC) INFORMATION:

a. Sponsored by: Enterprise Business Standards Office, supporting the Office of the Deputy 

Assistant Secretary of Defense (Supply Chain Integration) (ODASD(SCI)) and the DOD IUID 

Working Group 

b. Technical and Functional POC: Enterprise Business Standards Office: Rafael 

Gonzalez and Eric Flanagan, Co-Chairs DLMS Supply Process Review Committee (PRC); and Ben 

Breen, Chair Supply Discrepancy Reporting PRC, email: DLMS.IUID@dla.mil

2. FUNCTIONAL AREA:

a. Primary Functional Area: Supply, IUID

b. Secondary Functional Process: Physical Inventory Control, UIT

3. REFERENCES:

a. DOD Integrated Requirements Set (IRS) for Item Unique Identification (IUID) in Supply 

Business Processes 

b. Defense Logistics Manual (DLM) 4000.25, Volume 2, Supply Standards and Procedures

c. DOD IUID Working Group Meeting, September 15, 2016

d. Approved DLMS Change (ADC) 1198, Establishing and Maintaining Accountability for 

Service Owned Capital Equipment Stored at DLA Distribution Centers, October 6, 2016

e. Approved Addendum to ADC 1198A, Establishing and Maintaining Accountability for 

Service Owned Capital Equipment Stored at DLA Distribution Centers – (Missing Serial Numbers, 

and Remove 867I Issue Transaction), September 6, 2017

f. DODI 8320.04, Item Unique Identification (IUID) Standards for Tangible Personal 

Property, September 3, 2015

g. DODM 4140.01, Volume 9, DOD Supply Chain Materiel Management Procedures:

Materiel Programs, February 10, 2014; revised by Change 1, October 17, 2016

h. DODM 4140.01, Volume 11, DOD Supply Chain Materiel Management Procedures: 

Inventory Accountability And Special Management And Handling, March 8, 2017

i. ADC 1071, Implementation of DOD Item Unique Identification (IUID) Supply Policy in 

Version 4030 DLMS 856R Shipment Status Materiel Returns, March 26, 2014
Attachment, ADC 1244

Page 2

j. ADC 1030, Implementation of Item Unique Identification (IUID) in the DLMS Shipment 

Status Supporting DOD IUID Supply Procedures and Associated Supply Discrepancy Report (SDR) 

Procedures (Supply/SDR), February 21, 2013

k. ADC 1253, Administrative Update Supporting Army Elimination of the Army Maintenance 

Management System (TAMMS) Equipment Data Base (TEDB) Unique Item Tracking (UIT) Program 

and Elimination of Associated UIT Designator Code AAE, February 3, 2017, to be published in Formal 

Change 9 to DLMS Volume 2, 4th quarter fiscal year 2017

l. ADC 81, Establish New DLMS Supplement (DS) and Federal Implementation Convention

(IC) for 140B, Unique Item Tracking (UIT) Reporting, and 888B, UIT Data Change, October 22, 2002

4. APPROVED CHANGE(S): Green highlighting identifies substantive changes subsequent to 

staffing.

a. Scope of Change:

(1) This change provides standard procedures for all Services UIT programs except the 

DOD Small Arms and Light Weapons (SA/LW) Serialization Program (DODSA/LWSP). The 

DODSA/LWSP is however, included in the new DLMS chapter developed for this change as a 

placeholder to acknowledge that this change represents the planned way ahead for SA/LW. Following 

is the complete list of UIT programs with the associated Federal Logistics Information System (FLIS) 

UIT Designator Code:

UIT 

Designator 

Code

UIT Program

AAA DOD Small Arms and Light Weapons Serialization Program (DODSA/LWSP)

AAB Security Risk Category I Non-Nuclear missiles and Rockets 

AAC Radiation Source Tracking System (RASTS) Program

AAD Navy Depot Level Reparables (NDLR) Program

AAF Aviation Component Tracking Program

AAG Tritium Unique Item Tracking Program

AAH Controlled Cryptographic Items (CCI) 

AAJ Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM)

AAI

Proposed

DLA Serially Managed Items (on behalf of the Components)

Staffing Note: This is a new UIT Designator Code being proposed by a separate DLMS 

Change to enable DLA to address serially managed items that it stores for the Services, 

beyond those item that require special handling. For example, items that can be managed 

under the Capital Equipment procedures (ADCs 1198 and 1198A) and the existing UIT 

Designator Codes. ODASD(SCI) requested and received a one-time waiver to the policy 

in Reference 3.g. to establish an additional UIT program.

(2) At this time, the procedures in this change do not apply to the DODSA/LWSP

UIT program (UIT Designator Code AAA). The Enterprise Business Standards Office, in 

conjunction with the DOD SA/LW Coordinating Group and the ODASD(SCI), will develop a 
Attachment, ADC 1244

Page 3

separate follow-on PDC to align and transition the current unique DODSA/LWSP transactions and 

procedures with the use of standard logistics transactions and procedures described in this change;

(3) These procedures apply to national stock number (NSN) items with FLIS IUID 

Indicator = Y;

(4) This change applies to the NSN in the supply transaction when identified with the 

appropriate UIT designator code. This change does not cover embedded items;

(5) This change applies to UIT program items stored at DLA Distribution Centers,

however the Services may pattern their intra-Service procedures after these procedures to the 

maximum extent practicable;

(6) For the purpose of this change, the term “serial number” refers to the human 

readable serial number either marked on or associated with an item, and not the serial number used to 

create the UII, as they do not always match.

b. Brief Overview of Change: This document is one of a series of DLMS changes to define 

procedures and establish a coordinated implementation for the exchange of IUID and serialization

data in accordance with DODM 4140.01, IUID supply policy in Volumes 9 and 11 (References 3.g. 

and 3.h., respectively). This ADC:

(1) Develops the necessary DLM 4000.25, DLMS, Volume 2, (Reference 3.b.) 

procedures to include serialization data in all DLMS balance affecting transactions and selected 

additional transactions for UIT programs.

(2) Adds a new chapter titled “Procedures for Serially Managed Materiel Requiring 

Owner Visibility”, and it allows for expansion to other areas as ODASD(SCI) and the DOD IUID 

Working group identify additional IUID requirements for serially managed materiel requiring owner 

visibility while physically located at DLA Distribution Centers. The new Chapter 30 is modeled after 

requirements previously approved under ADCs 1198 and 1198A for capital equipment candidates, 

and is augmented by additional requirements noted below.

(3) Uses the serial number to satisfy the immediate need for visibility pending full 

implementation of IUID policy across the Department of Defense based upon UII. The intent is to 

capture both human readable serial number and UII, however not all items are IUID marked, and the 

UII cannot be considered a mandatory element at this time.

(4) Authorize the use of a unique document number to relate a physical inventory 

request and its response.

(5) Modify End of Day (EOD)/reconciliation procedures to clarify that storage 

activities and owner must reconcile records by UII/serial number for materiel under capital equipment 

and/or UIT items.

(6) Modify SDR procedures for new discrepancy code and reply code. Modify DOD 

WebSDR to apply serial number edits to new submission SDR (transactions and direct input) to 

ensure that the requirement for mandatory inclusion of serial number for UIT program items is met. 
Attachment, ADC 1244

Page 4

(7) Clarify DLMS Implementation Convention (IC) 947I Inventory Adjustment and

further explain the use of Quantity or Status Adjustment Reason Code AA (Physical Count) with 

quantity of 0 (zero).

c. Background:

(1) This change originated from the DOD IUID Working Group approving inclusion of 

the UIT programs in the DOD Integrated Requirements Set (IRS) for IUID in Supply Business 

Processes (Reference 3.a.) (hereafter referred to as the IRS). The IRS establishes overarching 

requirements for the application of IUID unique item identifiers (UII) and related serial numbers in 

supply business processes across the DOD enterprise. ODASD(SCI) develops and updates the IRS in 

conjunction with the DOD IUID Working Group.

(2) In accordance with DODM 4140.01, Volume 9, the DOD Components will 

transition from uniquely identifying items by serial number to the use of UIIs. DoD Components will 

continue to use the human readable serial numbers as a supporting mark and data element. To 

facilitate transition and tracking in the current environment for UIT program serialization data 

procedures, the serial number is mandatory in the DLMS transaction, as is the unique item identifier 

(UII), when available. The intent is to capture both serial number and UII, however not all items are 

marked and the UII cannot be considered a mandatory element at this time.

(3) With the exception of active UIT programs for Navy DLR, PIC NWRM, and 

DODSA/LWSP, DLA Distribution does not currently have a requirement to provide serial number/UII 

visibility of Service-owned UIT program assets stored at DLA Distribution Centers. Army established 

several other DOD UIT programs, but the programs were never activated as inter-DOD Component 

UIT programs using DLMS transaction exchange of UII and/or serial number. To activate these 

programs at the DOD-level, a PDC is required to document the procedures and associated DLMS 

transaction exchange requirements for inter-DOD Component use.

(4) ODASD(SCI), in conjunction with the IUID Working Group, developed and 

approved the overarching requirements for which the detailed DLMS procedures and transaction 

updates are set forth in this ADC. At the September 15, 2016, DOD IUID Working Group meeting 

(Reference 3.c.), ODASD(SCI) addressed Army’s proposed inclusion of UIT programs in the IUID 

IRS with the group. The intent was to revise the IRS to include the requirement that all balance 

affecting transactions and other selected transactions, for UIT programs maintain serialization data 

visibility between DLA storage activities and owner/manager supply systems. When ODASD(SCI) 

authorizes new requirements in the IRS which impact the DLMS, PDCs are written to reach consensus 

on the DLMS procedures necessary to implement the approved requirements. This change addresses 

serialized data visibility for UIT programs under IUID supply policy, and leverages the transactions 

which ADC 1198 (Reference 3.d.), as modified by the Addendum to ADC 1198A (Reference 3.e.),

approved for providing serialized data for capital equipment.

(5) The iRAPT 5.10 requirements and design review meetings identified several gaps 

for serial number field length and characteristics. The ODASD(SCI) led IUID Working Group is 

working to harmonize these gaps and will issue a policy with specific guidance on serial number 

format and length. The following gaps were discussed during recent meetings:

(a) The current serial number format in iRAPT is 30 characters, 

representing the serial number used in the pedigree data to establish the UII, allowing no special 

characters (except hyphen and forward slash) and no spaces. iRAPT proposed adding a field for the 
Attachment, ADC 1244

Page 5

serial numbered items without a UII with a length of 50 characters. However, due to the lack of 

existing policy for the human readable serial number format and existing restrictions on the serial 

number in DLMS logistics transactions, iRAPT will restrict the field length to 30 characters, pending 

ODASD (SCI) policy.

(b) The IUID Registry requires a maximum 30-character serial number for 

creation of UII, allowing hyphen and slash. An optional human readable serial number may be 

entered in the marks section of the Registry allowing 50 characters with special characters including 

spaces.

(c) Per MIL-STD 130, the serial number used to construct UII is 30 

characters with hyphen, forward slash and no spaces. There is no specific guidance on humanreadable field length and special characters.

(d) The serial number in DLMS transactions supporting IUID and Unique 

Item Tracking (UIT) (exclusive of small arms/light weapons (SA/LW)) was designed to be consistent 

with the IUID Registry, allowing 30 positions with no special characters other than hyphen and 

forward slash. The intent of the DLMS requirement is to capture the human readable serial number

used for tracking (especially if different from the value used for creation of the UII). Unfortunately, 

DLMS transactions originating from iRAPT are perpetuating the pedigree UII serial number to the 

receiving activity. Although normally this will be consistent with the serial number used for tracking, 

it can differ and, therefore, will not satisfy DLMS requirements and will provide no meaningful 

information to the receiving activity. Expanding the serial number field length to 50 characters (as 

originally proposed for iRAPT tracking of non-UII serially-managed GFP and for consistency with

the human readable mark in the IUID registry) would require DLMS transactions to either remap the 

existing X12 data elements for serial number or upgrade the DLMS transactions to a higher X12 

version.

(e) The SA/LW Registry rules differ on special character use and the serial 

number in the SA/LW legacy transactions is restricted to 11 characters due to legacy MILSTRAP 

transaction limitations. The JSA/LWCG provided input to ODASD(SCI) for policy development to 

standardize serial number field length and special characters.

(f) Subsequent to the initial staffing of this change, ODASD(SCI) established 

overarching guidance for the convention of human readable serial numbers. Based on recent 

guidance, only alpha numeric (A-Z, 0-9), dash and forward slash are allowed with a maximum field 

length of 30 characters. Spaces are not allowed. DOD Components must ensure future procurement 

actions require vendors to follow serial number convention guidance as applicable. ODASD(SCI) 

will update appropriate DOD policies to reflect these changes followed by the implementation of this 

change. Consequently, EBSO will develop a change to incorporate these changes in all applicable 

DLMS transactions and manuals.

Staffing Note: Serially managed items with non-compliant human readable serial number will be 

considered and reported through the SDR process as missing serial number.

(4) Refer to Enclosure 1 for the relevant IUID policy contained in:

(a) DODI 8320.04, IUID Standards for Tangible Personal Property, 

September 3, 2015, (Reference 3.f.);
Attachment, ADC 1244

Page 6

(b) DODM 4140.01, Volume 9, DOD Supply Chain Materiel Management 

Procedures: Materiel Programs, December 5, 2017 (Reference 3.g.); and

(c) DODM 4140.01, Volume 11, DOD Supply Chain Materiel Management 

Procedures: Inventory Accountability and Special Management and Handling, November 27, 2017

(Reference 3.h.).

d. Approved Change in Detail: This change addresses the additional procedures 

automated information systems must implement to provide serial number/UII visibility for UIT 

program items. DODM 4140.01 Volume 9 directs that DOD Components will transition from 

uniquely identifying items by serial number to the use of UIIs, and will continue to use the human 

readable serial numbers as a supporting mark and data element. To facilitate transition and tracking 

in the current environment for UIT program serialization data procedures, the serial number is 

mandatory in the DLMS transaction, as is the unique item identifier (UII), when available. The 

intent is to capture both serial number and UII, however not all items are marked and the UII cannot 

be considered a mandatory element at this time. That is the context in which the term “serial 

number/UII” is used in this ADC. There is an exception for receipt processing which requires

processing of receipt transaction when serial number is missing, as noted under discrepant receipt 

processing. 

(1) The following transactions, require the inclusion of the serial number/UII for UIT 

program items:

 527R Receipt (Receipt =527R with 1/BR02/020 Transaction Type Code D4)

 842A/W SDR Submission

 842S/Q Storage Quality Control Report

 842P Product Quality Deficiency Report (PQDR) Data Exchange

 846R Location Reconciliation

 856R (version 4030) Shipment Status Materiel Returns

 856S Shipment Status 

 945A (version 4030) Materiel Release Confirmation

 947I (version 4030) Inventory Adjustment

(2) The proposal identifies changes for standard processing of serialized data for UIT 

programs, which are additive to the existing procedures for the specific functional areas documented in 

DLMS, Volume 2, Chapters 4, 5, 6, 7, 11, 13, 14, and 17. The new Chapter 30 (Enclosure 3) to DLM 

4000.25, Volume 2, provides the additive detailed DLMS procedures to establish and maintain item 

visibility by serial number/UII for Service-owned UIT assets stored at DLA Distribution Centers. The 

new Chapter 30 is modeled after requirements previously approved under ADCs 1198 and 1198A for 

capital equipment candidates, and is augmented by additional requirements noted in paragraphs (2), 

(3), (4) and (7) below. Additionally, Chapter 17, SDR, includes updates applicable to UIT assets,

which are not limited to those assets stored at DLA Distribution Centers. Updates to related chapters 

pointing to the new Chapter 30 are at Enclosure 4.

(3) Clarify DLMS Implementation Convention (IC) 947I Inventory Adjustment and 

further explain the use of Quantity or Status Adjustment Reason Code AA (Physical Count) with 

quantity of 0 (zero). The use of reason code AA for an inventory adjustment gain combined with a 

quantity of 0 (zero) indicates that a requested physical inventory has taken place, and no record 

adjustment was necessary.

Staffing Note: This clarifies current procedures and no program changes are required. 
Attachment, ADC 1244

Page 7

(4) For the purpose of Capital Equipment and UIT items, the combination of Reason 

Code AA (Physical Count) with a quantity of 0 (zero) will indicate to the owner the completion of the 

inventory and will include all serial numbers/UII associated with the NSN, condition code and owner 

identified in the initial request. The storage activity will transmit the final inventory adjustment 

transaction (Reason Code AA with a quantity of 0 (zero)) indicating completion of the inventory at 

end of day.

(5) Authorize the use of a unique document number to relate a physical inventory 

request and its response. The owner will include a document number in the request and send the 

Physical Inventory Request DLMS 846P transaction to the storage activity. Consequently, the 

storage activity will perpetuate the same document number in the response to the physical inventory 

request (usually a 947I Inventory Adjustment). 

Staffing Note: Authorized DLMS enhancement for all commodities. Required for capital equipment 

and UIT Programs.

(6) Modify End of Day (EOD)/reconciliation procedures under chapter 6 Physical 

Inventory Control (and the new Chapter 30) and clarify that storage activities and owner must 

reconcile records by UII/serial number.

Staffing Note: Required for capital equipment and UIT Programs.

(7) Establish new SDR Discrepancy Code U13 (Serial number unknown for seriallytracked item). This code is distinguished from other similar U-series discrepancy codes in that this 

code specifically informs the owner that the receiving activity is unable to support tracking 

requirements due to the missing serial number. This code applies when the serial number cannot be 

obtained readily from the item, packaging, documentation, or shipment notice. This code may be 

used alone or in combination with other discrepancy codes. 

(8) Establish new SDR Discrepancy Code U14 (Serial number convention invalid). 

This code is distinguished from other similar U-series discrepancy codes in that this code specifically 

informs the owner that a serially managed item was received with an invalid serial number 

convention. The receiving activity must annotate the non-compliant serial number in the SDR 

comments field since the DLMS 842A/W SDR transaction will not allow for an invalid serial number 

convention to be transmitted in the transaction. 

(9) Modify DOD WebSDR to apply serial number edits to new submission SDR 

(transactions and direct input) to ensure that the requirement for mandatory inclusion of serial number 

for UIT program items is met. Reject SDRs identifying a discrepant condition, shortage, overage, or 

IUID data mismatch for missing serial number using new Reply Code 946 (Transaction Rejected. 

Missing serial number for serially-tracked item.). Rejection criteria is applicable to specific 

discrepancy codes as follows for UIT program items (see paragraph 4.d.(8)(b)) and is applicable 

regardless of originator or action activity.

Staffing Note: Required for all UIT Program items without restriction to DLA Distribution 

shipments or receipts.

(a) Discrepant condition applies to Discrepancy Code C1 – C5, H1, or H5.

C1 In a condition other than shown on supply document or on the supporting inspection/test 

certificate (if hazardous materiel use code H1)

C2 Expired shelf life item (if hazardous materiel use code H5)
Attachment, ADC 1244

Page 8

C3 Damaged U.S. Postal Service shipment

C4 Materiel received stripped of parts or components (cannibalized) (applicable to materiel

returns or repairs only)

C5 Incomplete item received. Do not use for incomplete sets/kits/outfits 

H1 Hazardous item in a condition other than shown on supply document or on the supporting 

inspection/test certificate

H5 Expired hazardous shelf life item

(b) Shortage applies to Discrepancy Codes S1, S2, or S8.

S1 Quantity received less than quantity indicated on supply documentation

S2 Quantity received is less than quantity requested minus variance (other than unit of issue or 

unit of pack)

S8 Concealed shortage discovered upon opening a sealed vendor's pack 

(c) Overage applies to Discrepancy Codes O1, O2, or O5.

O1 Quantity received is more than quantity shown on the supply document

O2 Quantity received is more than quantity requested plus variance, if applicable (other than 

unit of issue or unit of pack)

O5 Concealed overage discovered in a sealed shipping container

(d) IUID mismatch applies to Discrepancy Code U07 – U09 or U12.

U07 Mismatch between unique identification (UII/serial number) on item and label

U08 Mismatch between unique identification (UII/serial number) on item or packaging 

marks/labels and the associated shipping documentation

U09 Mismatch between unique identification (UII/serial number) on item or packaging 

marks/labels and the associated due-in/shipping notice

(10) Modify DOD WebSDR to apply serial number edits to new submission SDR 

(transactions and direct input) to enforce serial number convention. Serial number convention must 

contain alpha numeric (A-Z, 0-9) and only dashes and forward slashes are allowed with a maximum 

field length of 30 characters and no spaces are allowed. Reject SDRs with serial numbers not meeting 

this convention using new Reply Code 947 (Transaction Rejected. Invalid serial number length or 

convention.)

(11) Identification of UIT program items. To allow for uniform tracking and processing 

for UIT program items, these procedures are based upon identification of the items as follows: 
Attachment, ADC 1244

Page 9

(a) FLIS IUID Indicator Y, plus

(b) FLIS UIT Designator code. UIT designator codes for the UIT programs as

shown in table below: 

UIT 

Designator

Code

UIT Program 

AAB Security Risk Category I Non-Nuclear missiles and Rockets 

AAC Radiation Source Tracking System (RASTS) Program

AAD Navy Depot Level Reparables (NDLR) Program

AAF Aviation Component Tracking Program

AAG Tritium Unique Item Tracking Program

AAH Controlled Cryptographic Items (CCI) 

AAJ Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM)

Staffing Note: Active UIT programs for Navy Depot Level Reparables (NDLR) Program and 

Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM) programs do not use 

the full suite of transactions and procedures addressed in this change for UIT. ODASD(SCI) has 

authorized staggered implementation for those programs if needed. Navy and Air Force must 

respond with a transition plan and target implementation date for the NDLR and PIC NWRM 

programs respectively. 

(12) Delete and reserve DLMS, Volume 2, Chapter 19 Unique Item Tracking (as 

revised by ADC 1253). UIT procedures are included in the new Chapter 30, and in the case of 

SA/LW, in the existing Chapter 18.

(13) This change withdraws ADC 81 (Reference 3.l.). In 2002, ADC 81 authorized 

DLMS 140B Unique Item Tracking Reporting and 888B Unique Item Data for DLA Phase I UIT. 

There is currently no DLMS, Volume 2, documented procedure for use of 140B or 888B. If a DOD 

Component determines there is a need for 140B or 888B, they must submit a PDC documenting the 

requirement and procedures. As background, the transactions were originally developed for DLA 

DSS and Navy use with the NDLR UIT program. The 140B was authorized for interim use under 

DLA Phase I UIT, for use with receipts until such time as DLA implemented DLMS 527R Receipt 

transaction under DLA UIT Phase II. Use of 140B was necessary as an interim step because during 

DLA Phase 1 UIT, DSS had not yet implemented 527R, so DSS processed MILSTRAP legacy 80-

record position receipt transactions (DIC D4_/D6_) for NDLR UIT program items, by NSN, quantity 

and supply condition code, while providing the corresponding serial number information for NDLR 

items using 140B. Use of 140B was no longer authorized with receipts when DSS implemented the 

DLMS 527R Receipt, which could accommodate the serial number.

e. Revisions to DLM 4000.25 Manuals:

(1) Revise the following DLMS implementation conventions (IC) as shown in 

Enclosure 2: 527D Prepositioned Materiel Receipt (PMR), 527R Receipt, 842A/W SDR, 842P 

Product Quality Deficiency Report (PQDR) Data Exchange, 842S/Q Storage Quality Control 

Report, 846P Physical Inventory Request, 846R Location Reconciliation Request, 856R Shipment 
Attachment, ADC 1244

Page 10

Status Materiel Returns (version 4030), 856S Shipment Status, 945A Materiel Release Advice

(version 4030), and 947I Inventory Adjustment (version 4030).

(a) The DLMS 527D PMR and 527R Receipt ICs include administrative 

changes to remove unused placeholders for IUID related data elements including the component 

pieces of a constructed UII. This is consistent with administrative updates to IUID related data 

elements made to DLMS 856S Shipment status by ADC 1030 (Reference 3.j.), and with the IUID 

approach for DLMS transactions which is to convey the constructed IUID UII, not the individual 

pieces of the UII.

(b) The DLMS 842A/W SDR IC includes administrative updates for clarity.

(2) Revise DLM 4000.25, DLMS, Volume 2, Supply Standards and Procedures, to 

add new Chapter 30 as shown in Enclosure 3.

(3) Revise DLM 4000.25, DLMS, Volume 2, Chapters 4, 5, 6, 7, 11, 13, 14, and 17 

as shown in Enclosure 4 to add text providing a link to the new Chapter 30. Update Chapter 6 

capital equipment section for the new inventory procedures. Additionally, update Chapter 17 for 

WebSDR edits as shown in Enclosure 4.

(4) Revise DLM 4000.25, DLMS, Volume 2, to delete and reserve Chapter 19, 

Unique Item Tracking, as shown in Enclosure 5.

(5) Revise DLM 4000.25, DLMS, Volume 2 Supply Standards and Procedures as 

shown in Enclosure 6. 

(6) Revise DLM 4000.25, DLMS, Volume 2, Appendix 7.28, Supply Discrepancy 

Report Relevant Data Elements as follows:

(a) Add discrepancy code:

“U13 Serial number unknown for serially-tracked item.”

“U14 Serial number convention invalid.”

(b) Add SDR reply codes:

“946 Transaction Rejected. Missing serial number for serially-tracked item.”

“947 Transaction Rejected. Invalid serial number length or convention.”

f. Approved Transaction Flow: This change addresses procedures for inclusion of serial 

number/UII into the existing logistics transactions and processes noted herein for serially managed 

material requiring owner visibility at DLA Distribution Centers (currently applicable to UIT 

program items as identified). Two Quantity or Status Adjustment Reason codes associated with 

UIT programs are being shown for this process. See Enclosure 5 for transaction scenarios.

g. Alternatives: None identified.

5. REASON FOR CHANGE: To establish procedures for serial number/UII visibility of UIT 

program items at DLA Distribution Centers under DOD IUID Supply Policy in DODM 4140.01, 

Volumes 9 and 11 (References 3.g. and 3.h.).
Attachment, ADC 1244

Page 11

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Provides Services with unique item visibility for UIT program items

stored at DLA Distribution Centers, with serial number/UII.

b. Disadvantages: None identified.

7. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT:

a. Users of this change have fully implemented the DLMS transaction capability in their 

business application.

b. These procedures only apply to assets with a NSN as the assets are cataloged in FLIS. 

FLIS IUID indicator Y, in conjunction with the FLIS UIT Designator Code, identifies the items 

subject to these procedures. Exception is UIT Designator Code AAA for the DODSALWSP UIT 

program; EBSO will develop a separate PDC to address DODSALWSP.

8. ADDITIONAL COMMENTS TO CONSIDER:

a. The use of AIT will greatly reduce or eliminate errors associated with the manual capture 

of serial numbers (to include human read errors) that could lead mismatches between transactions, 

documentation, and Component property records resulting in SDRs. 

b. This process does not apply to the Materiel Receipt Acknowledgement (MRA) or the DLA 

Disposition Services Turn In Receipt Acknowledgement (TRA) transaction.

c. ODASD (SCI) has not formally identified requirements for serial number/UII tracking for 

DLA Disposition Services. EBSO recommends inclusion of the serial number/UII for serially 

managed materiel in the shipment status in order to meet visibility objectives and facilitate receipt 

processing.

Staffing Note: Request ODASD (SCI) confirm this requirement. See impact below (paragraph 12).

d. Air Force PIC NWRM and DLMS 870S Supply Status. The current DLMS, Volume 2, 

Chapter 19, UIT procedures identify PIC NWRM use of DLMS 870S Supply Status with Air 

Force Integrated Logistics Solution-Supply (ILS-S) (Retail Supply) as implemented under ADC

4071. 

Staffing Note: Request Air Force confirm whether they use DLMS 870S Supply Status transaction 

for PIC NWRM with Air Force ILS-S (Retail Supply).

9. ADDITIONAL FUNCTIONAL REQUIREMENT:

a. DLA reviewed requirements/constraints for conveying to the materiel owner the cost of 

managing UIT program inventory by serial number/UII . DLA provided their methodology for 

conveying the cost to the owner at the DLA Cost Summit in November 2017; all Services were 

present. 

 

1 ADC 407, Requirements for Unique Item Tracking (UIT) in the DLMS Supply Status (870S) Supporting the Cargo 

Movement Operations System (CMOS) Interface (MILSTRIP/Supply/Transportation Interchange)
Attachment, ADC 1244

Page 12

b. Per ODASD(SCI) guidance, DLA and the Services will develop memorandums of 

understanding (MOU) for conducting the initial inventory (i.e., recording, creation and application of 

any required serial numbers and UIIs to bare item or packaging) of UIT program items at DLA 

Distribution Centers. This MOU requirement is outside the scope of the DLMS procedures addressed 

in the new DLMS chapter.

c. The Enterprise Business Standards Office will develop a separate PDC to revise the 

Inventory Control Effectiveness (ICE) Report – General Supplies DD Form 2338-2 (Report Control 

Symbol (RCS): DD-AT&L 935) to address use of Type of Physical Inventory/Transaction History 

Code B. Code B can separately identify inventory adjustments resulting solely from the need to 

correct mismatches on UII and/or serial number.

2

 This is necessary due to the inherent value of 

adjustments necessary to correct UII and/or serial number mismatched conditions that could 

adversely affect what is currently reported in the ICE Report. 

d. The Enterprise Business Standards Office will develop a separate PDC to provide 

procedures to correct or reverse DLMS 945A Materiel Release Confirmation (MRC), and DLMS 

856S Shipment Status, to notify the owner/customer when materiel is not shipped as originally 

reported. For example, if a package does not make it onto the truck, the distribution center will 

need to make a correction to the MRC and shipment status (or part of it). This may require adding 

the reversal reason code to the transactions (new or existing value). It will require reversal of the 

associated DLMS 867I issue transaction (UII will not be on the 867I). Reversal or correction of the 

MRC/shipment status would be a significant change for ICP systems since reversal of MRCs and 

Shipment Status is not current MILSTRIP/DLMS functionality.

e. Components must determine if there is a need to produce DOD WebSDR reports or 

support management queries for UIT program-related supply discrepancies. WebSDR has inherent 

functionality to allow ad hoc management report selection criteria by UIT Designator Code and 

could include Codes AAB, AAC, AAD, AAF, AAG, AAH, and AAJ in the existing drop down 

menu. However, due to the sensitivity of the type of materiel included in most of these programs, 

this action has not been implemented. User restrictions for management report view are System 

Access Request (SAR) controlled, usually at the DoDAAC or Service/Agency level, and cannot 

currently be restricted by specific selection criteria used to generate the report. If desired canned 

queries may be requested and these would be encrypted for distribution to limited pre-identified 

personnel.

10. ESTIMATED TIME LINE/IMPLEMENTATION TARGET:

a. Services and DLA DSS will provide target implementation dates in response to this 

PDC. The active UIT Programs for Navy DLR and PIC NWRM, which will require changes to the 

existing programs, can have later staggered implementation for Navy, Air Force, and DLA 

Distribution, if needed.

Staffing Note: This change involves many transaction and procedural changes that will impact 

DOD Component systems.

b. DOD WebSDR edits for mandatory inclusion of serial number/UII based upon the 

discrepancy scenario is targeted for implementation December 2018. Until that time, Components 

may use SDR attachment functionality for serial number/UII identification.

 

2 MILSTRAP, Appendix 2.2, Type of Physical Inventory/Transaction History Codes.) 

B – Special inventory due solely to UII and/or serial number mismatches between owner and storage activity records.
Attachment, ADC 1244

Page 13

11. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH IMPLEMENTATION 

OF THIS CHANGE: This change will enable the DLMS compliant Services to meet requirements

ODASD(SCI) addressed at the September 15, 2016, DOD IUID Working Group meeting, for visibility of 

UIT program items. The implementation of this change is not intended as an attempt to save or avoid 

costs. 

12. IMPACT:

a. The cost to the Services for the DLA Distribution Centers to provide serialized data 

visibility for Service-owned UIT program items (i.e., by serial number as mandatory, and when 

available, the UII) stored at DLA Distribution Centers is unknown at this time. Subsequent to the 

staffing of this PDC, DLA provided their methodology at the DLA Cost Summit in November 

2017, all Services were present. 

b. Care of Supplies in Storage. For UIT program items requiring serialized data visibility,

the distribution center may report storage quality issues requiring care of supplies in storage 

(COSIS) work to the materiel owner via the Storage Quality Control Report. Include the serial 

numbers as mandatory and when available, include UIIs, for approval in accordance with DOD

Component "Stock Readiness" Policy using DLMS 842SQ Storage Quality Control Report (refer to 

Enclosure 3, DLMS Manual, Volume 2, new Chapter 30, paragraph C30.12).

Staffing Note: Request DoD Stock Readiness Program Manager identify mandatory serial number 

scenarios for SQCRs. 

c. DLA Disposition Services. ODASD(SCI) in conjunction with DLA Disposition Services 

and the DOD IUID Working Group, will update the IUID IRS to address DLA Disposition Services 

IUID requirements. DLA will then submit a PDC to address any additional DLA Disposition 

Services IUID procedures, to include UIT program items.

d. New DLMS Data Elements: None identified.

e. Changes to DLMS Data Elements: Changes to Data Elements as shown in the IC 

changes enclosure.

f. Automated Information Systems (AIS): DLA Distribution and Service AISs receiving 

the DLMS transactions cited in this change with serialization data to include the serial number and 

when available, UII, for Service owned UIT program items stored at DLA Distribution Centers

must recognize and use the data.

g. Defense Automatic Addressing System (DAAS): Update the DAAS maps as need for 

the 846P.

h. Defense Automatic Addressing System (DAAS) WebSDR: Update WebSDR online 

direct input screens to adhere to the serial number convention cited in this change. Also, update 

WebSDR with the new discrepancy and reply codes cited in this change. 

i. Non-DLM 4000.25 Series Publications:

(1) DASD SCI to update the DOD Integrated Requirements Set (IRS) for IUID in 

Supply Business Processes to address UIT programs.
Attachment, ADC 1244

Page 14

(2) DOD Components should review their Component level publications and update 

as necessary.

13. PROPOSED DLMS CHANGE (PDC) 1244 STAFFING RESPONSE/COMMENT 

RESOLUTION

Originator Response/Comment Disposition

1. Army  Replace Radiation Testing and Tracking 

System (RATTS)" with "Radiation Source 

Tracking System." (RASTS)

 In paragraph C6.13.5.3. Requested 

clarification. "The storage activity may add 

multiple missing serial number/UII for an 

item using a single transaction

 Requested clarification of applicability to 

embedded items. 

 In paragraph 4.b(3), delete first sentence " 

Includes an interim mandatory requirement 

for serial number to satisfy the immediate 

need for visibility pending full 

implementation of IUID policy across the 

Department of Defense based upon UII.

 PDC 1244 must state that DLA will continue 

to support serial number tracking manually, 

through WebUIT until the Army and DLA are 

capable of electronic transfer of information 

between respective systems and Army is able 

to update Army Serial Number Tracker 

(ARSNT) with these transactions

 PDC 1244 included a staffing note for DLA: 

Staffing note for DLA: Request DLA provide 

their proposed methodology for conveying the 

cost to the owner in response to this change.”

When will this transpire? Is there a suspense 

for this information? Is cost important to the 

AMC G8

 Limitation of special character support to just 

a dash is not acceptable.

Updated.

Added “an item” to the existing 

sentence for clarification

Changed to:4.a(4) to clarify. “This 

change applies to the NSN in the supply 

transaction when identified with the 

appropriate UIT designator code. This 

change does not cover embedded items”

Revised sentence: Uses the serial 

number to satisfy the immediate need 

for visibility pending full 

implementation of IUID policy across 

the Department of Defense based upon 

UII. The intent is to capture both 

human readable serial number and UII, 

however not all items are IUID marked, 

and the UII cannot be considered a 

mandatory element at this time.

This is a separate agreement between 

Army and DLA as an internal 

workaround until system changes can 

be made. This is not essential to the 

PDC procedures and no change was 

made to ADC 1244

The methodology was conveyed at the 

DLA Cost Summit in November 2017, 

all Services were present.

Updated per a meeting between 

ODASD(SCI), Army and EBSO on 

5/21/2018 to reflect the serial number 

convention to be: alpha numeric (A-Z, 

0-9), dash and forward slash are 

allowed with a maximum field 
Attachment, ADC 1244

Page 15

Originator Response/Comment Disposition

length of 30 characters. Spaces are 

not allowed.

2. Army  C30.8.1.3. Change definitions of FLIS IUID 

indicator Y/N to identifying material for 

tracking by serial number and/or UII when 

available

Changed C30.8.1.3 to reflect "The 

IUID indicator provides the DoD 

Components a systemic means to 

identify whether an NSN requires 

tracking by serial number and the UII 

when available. 

"Serial number and the UII when 

available" is the wording consistent 

with the beginning of the chapter, rather 

than "serial number and/or UII when 

available.

3. Navy

4. Air Force

5. Marine Corps Concurs with Comment.

This PDC does not address the 5270 PMR 

establishment at the serialized/IUID level. 

Currently the Marine Corps is producing the 5270 

Preposition Material Receipt (PMR) at a quantity 

level augmented by the 856S transactions 

providing serialized data to our DPAS 

warehousing system. This is being done to help 

identify frustrated cargo where the documentation 

has be removed or lost. By searching for the NSN 

and serial numbers, the warehouse can determine 

the document(s) the equipment was shipped under 

to their facilities. This process should be 

incorporated into DLAs processes to help reduce 

SOR submissions relating to the NSN associated 

to this PDC

Pending EBSO response

6. DLA

7. USTRANSCOM
Enclosure 1, PDC 1244

Related IUID Policy Excerpts

Page 1

ENCLOSURE 1 TO ADC 1244

IUID Related Policy for ADC 1244

A. DODI 8320.04, IUID Standards for Tangible Personal Property, September 3, 2015 (Reference 3.f.).

DODI 8320.04 was reissued to “establish policy and assign responsibilities for the process of uniquely 

identifying tangible personal property and their associated selected attributes. The unique item identifier (UII) 

will be used globally as the common data key in financial, property accountability, acquisition, and logistics 

(including supply and maintenance) automated information systems to enable asset accountability, valuation, 

life-cycle management, and counterfeit materiel risk reduction.” 

B. DODM 4140.01, Volume 9, DOD Supply Chain Materiel Management Procedures: Materiel 

Programs, February 10, 2014; as revised by Change 2, December 5, 2017 (Reference 3.e.), Enclosure 3, 

Paragraph 2, IUID, Subparagraph a. directs the following: 

“2. IUID

a. The DoD Components will:

(1) Use unique item identifiers (UIIs) to improve property accountability and to enhance 

product life-cycle management. Follow instructions for constructing the UII found in Military 

Standard 130 (Reference (q)).

(2) Use a UII in accordance with DoDI 8320.04 (Reference (r)), for the population of 

items that have a unique item level traceability requirement identified.

(3) Transition from uniquely identifying items by serial number to the use of UIIs. DoD 

Components will continue to use the human readable serial numbers as a supporting mark and data

element.

(4) For items with a national stock number (NSN) assigned, include an IUID value (Yes or 

No) in the Federal Logistics Information System (FLIS) field “IUID Indicator.”

(5) Use UII for all items in approved serialized item management (SIM) programs.

(6) Review existing unique item tracking (UIT) and serial number tracking (SNT) programs 

for possible transition to IUID Registry functionality. The DoD Components will not establish 

additional UIT or SNT programs.

(7) Include UII in functional databases to enable information sharing and information 

access to achieve collaboration between and among already existing, or emerging, item 

management systems.

(8) Capture, retain, and provide current and historical data regarding uniquely identified 

tangible items by UII.

(9) Develop the capability to exchange IUID data using Defense Logistics Management 

Standards (DLMS) and wide area workflow transactions.

(10) Include provisions for all IUID implementations to allow for AIT devices to capture the 

UII for an item based on the data elements used to determine the UII in accordance with DoDI 

4151.19 (Reference (s)) and MIL-STD-130 (Reference (q)). For business processes that include 
Enclosure 1, PDC 1244

Related IUID Policy Excerpts

Page 2

IUID capabilities, use AIT devices that are capable of reading an error correction code 200-

compliant data matrix symbol and portable document format (PDF) 417 symbol from product 

markings, PDF417 barcode from unit or exterior packaging markings, or accompanying 

documentation. Use information recorded in AIT devices to update automated information systems 

per SIM programs required by DoDI 4151.19 (Reference (s)).

(11) For unmarked existing items in inventory, installed, in use, or undergoing 

maintenance repair or overhaul, mark IUID-required items based on the marking strategy 

identified in the DoD Components’ IUID implementation plans.

(12) Place machine-readable UII marks on the item itself in accordance with Reference (q), 

as required. Place machine-readable marks on the packaging, as described in Reference (m) and on 

DoD shipment documentation, as described in Defense Logistics Manual (DLM) 4000.25-1 

(Reference (t)).

(13) Provide training to personnel who perform functions affecting IUID; update training 

courses with current DoD policies and procedures.

b. The Director of the DLA Logistics Management Standards Office will:

(1) Provide capability for use of the UII in applicable DLMS transactions, as required by 

DoD-level IUID supply policy.

(2) Coordinate recommended changes to the DLMS to support IUID through the appropriate 

process review committee.”

C. DODM 4140.01, Volume 11, DOD Supply Chain Materiel Management Procedures: Inventory 

Accountability and Special Management and Handling (Reference 3.h.). 

1. “3.2. ACCOUNTABLE RECORD FOR INVENTORY. The accountable record for inventory 

consists of the total item property record. 

a. At a minimum, the total item property record consists of: 

(1) Materiel manager name or designation. 

(2) NSN. 

(3) Unit of issue code. 

(4) Item description or name. 

(5) Unit cost. The materiel manager will assign a value in accordance with Chapter 4 of Volume 4 

of DoD 7000.14-R. 

(6) Unique item identifier and serial number for controlled items only per Section 4 of this 

volume.”

[Remaining subparagraphs not shown]
Enclosure 1, PDC 1244

Related IUID Policy Excerpts

Page 3

2. “3.3. IN-STORAGE ACCOUNTABILITY.

a. The DoD Component that has physical custody of materiel in storage is responsible for 

maintaining balances of in-storage inventory in its system of record, regardless of which DoD 

Component owns the materiel. The in-storage balance in the custodian’s system of record is the official 

auditable quantity for an item of inventory.

(1) DoD Components will establish accountability of government-owned contract property 

where contractors are responsible for the physical custody, in accordance with Part 52.245-1 of the FAR.

(2) If applicable, DoD Components will transfer accountability between contracts, in 

accordance with Part 45.106 of the FAR and Part 245.103-71 of the Defense Federal Acquisition 

Regulation Supplement.

b. ICPs and storage activities will collaborate to ensure that the in-storage inventory balances 

in their respective systems are the same, thus becoming, in effect, a single set of in storage balances in 

the total item property record. ICPs and storage activities should maintain and retain records and 

supporting documentation in accordance with Chapter 9 of Volume 1 of DoD 7000.14-R.

c. The storage activity is responsible for the content, changes, and accuracy of the inventory 

held under its control, as well as for the caring and safeguarding of that inventory.

(1) Each storage activity having physical custody of item assets will maintain a record or 

record set that identifies the quantity and condition of the item assets. Where required, item records will 

satisfy applicable unique item identification requirements.

(2) Storage activities will leverage the application of automatic identification technology 

(AIT) to improve the timeliness, accuracy, and efficiency of their inventory accounting by enabling use 

of machine-readable materiel identification and supporting serialized item tracking. AIT is described in 

Volume 7 of this manual.

(3) In accordance with Chapter 7 of Defense Logistics Manual (DLM) 4000.25-2, the 

storage activity maintaining physical custody of item assets will handle inquiries and audits of physical 

inventory discrepancies related to those assets and will:

(a) Conduct physical inventories, initiate and conduct causative research, prepare 

supply discrepancy reports (SDRs) or storage quality control reports, resolve inventory discrepancies, 

investigate and assess liability for loss, damage, and destruction of government property, and take 

applicable actions necessary to ensure accurate physical on-hand balances.

(b) Inform the owning materiel manager of any changes in the on-hand balances in the 

total item property record and provide quarterly summaries of item causative research results.

(c) While investigating a potential loss, ensure that the total item property record lists 

the quantity being investigated as a potential loss.

(4) Storage activities will use the Defense Logistics Management Standards (DLMS) in 

DoDD 8190.01E and DLM 4000.25 for SDRs, storage quality control reports, and the associated 

responses.”
Enclosure 1, PDC 1244

Related IUID Policy Excerpts

Page 4

3. “4.3. ADDED ACCOUNTABILITY REQUIREMENTS FOR SERIALLY-MANAGED 

ITEMS.”

Staffing Note: DODM 4140.01, Volume 11 defines ‘trusted systems network critical component (TSN 

CC)’, used in section 4.3., as: “A component which is or contains information and communications 

technology including hardware, software, and firmware, weather custom, commercial, or otherwise 

developed, and which delivers or protects mission critical functionality of a system or which, because of 

the system’s design, may introduce vulnerability to the mission critical functions of an applicable system.”

“4.3. ADDED ACCOUNTABILITY REQUIREMENTS FOR SERIALLY-MANAGED ITEMS. 

While most items are accounted for by NSN, DoD Components will account for DoD serially-managed 

items by UII within NSN in accordance with DoDI 8320.04, subject to information security and operation 

security requirements. DoD Components will maintain human-readable identification and supporting 

serialized item tracking for those items. In the event the UII is lost, missing, or unreadable, the DoD 

Components will use item serial number for tracking purposes. The Military Departments and DLA will: 

a. Maintain UII records at DoD storage activities. 

b. Provide shipment notification or shipment accompanying documentation from the issuing activity to 

the recipient identifying the NSN and UII.”

4. “5.10. RECEIPT VALIDATION FOR CII, INCLUDING NWRM AND TSN CC THAT ARE 

CLASSIFIED AS SECRET OR ABOVE.

a. DoD Components will validate receipt at the individual item level of UII or by serial number for 

kind, count, and condition unless the recipient has verification that the appropriate packing procedure 

was followed and there is no evidence of tampering. Until system changes implementing the IUID 

concept are completed, interim UII procedures are acceptable. 

b. If there is evidence of tampering, the recipient will open and inspect the contents of the package to 

validate the receipt. If product integrity could be compromised by opening the package, the receiving 

Military Department or Defense Agency will work with the shipper to establish what could be done to 

validate the receipt. 

c. If the markings on the packaging, documentation, or automated shipment notification do not 

match the actual item in the package (e.g., quantity discrepancies (over or under shipment), incorrect 

item received, unique identification (UII or serial number) mismatch, or receipt of a misdirected 

shipment), the recipient will submit an SDR within 24 hours of discovery to the responsible shipping 

activity or SOS, in accordance with Chapter 17 in Volume 2 of DLM 4000.25. 

d. The action activity must respond to the discrepancy report within 24 hours and take appropriate 

corrective actions to preclude a recurrence of mismatches. When the discrepancy requires further research 

for resolution, the action activity must provide an interim response within 24 hours, followed by a 

comprehensive response within 15 business days.”

[Intervening text not shown]

“5.15. TSN CC STEWARDSHIP AND CONTROL. In addition to the requirements specified in 

Volume 5 of this manual, all DoD Components having custody of TSN CC, including CCIs, must: 

a. Perform a complete physical inventory by UII or by serial number at periodic intervals not to 

exceed 12 months between successive inventories, pursuant to National Security Telecommunications 

and Information Systems Security Instruction No. 4001. 

b. Include all TSN CC and CCI equipment and uninstalled TSN CC and CCI components in the 

physical inventory.”
Enclosure 2, PDC 1244

IC Change Tables

Page 5

ENCLOSURE 2 TO ADC 1244

DLMS Implementation Convention (IC) Change Tables

Changes are identified by bold italics; deletions are identified by double strike-through.

A. 527D Prepositioned Materiel Receipt (PMR)

# Location DLMS 527D Prepositioned Materiel Receipt (PMR)

Administrative Revisions

Reason

1. IC Cover pages 

DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Note 6:

- ADC 1244, Establishing Visibility of Unique Item Tracking 

(UIT) Program Items for Service-Owned Assets Stored at DLA 

Distribution Centers and Corresponding Revisions to Inventory 

Procedures Related to Capital Equipment.

Identifies DLMS 

Changes

included in the 

IC.

2. 2/REF/250 Revise segment level DLMS Notes as follows:

1. At this time, the 2/REF/250 loop is not authorized for use to 

provide item unique identification (IUID) information. for the 

purpose of Unique Item Tracking (UIT). A PDC must be submitted 

documenting requirement and procedures before using this 

transaction for IUID.

2. This transaction will support item identification based upon the 

serial number/UII or theserial number. Data elements associated with 

the UII may be identified separately. Use the appropriate data 

elements to satisfy the desired functionality.

32. When both UII or serial number and batch/lot number are 

required for the item, enter the UII or serial number in 2/REF/250 and 

enter the batch/lot number in 2/N9/270. When the batch/lot number is 

required, but the serial number/UII/serial number does not apply, 

enter the batch/lot number in 2/REF/250.

43. The entire 2/REF/250 loop is a DLMS enhancement. See 

introductory DLMS note 4a.

Administrative 

update. There is no 

established 

requirement for 

using IUID data 

with 527D PMR at 

this time.

Removes 

individual parts of 

the UII consistent 

with IUID 

approach for 

DLMS 

transactions. 

DLMS only passes 

the constructed UII, 

not the individual 

pieces of the UII 

convention.

3. 2/REF01/250 Delete Federal Note: 

Federal Note: Use any code.

Revise existing qualifiers SE and U3 DLMS notes as follows:

SE Serial Number

DLMS Note: 

1. Use to identify the serial number (when the UII (code U3) is not 

used). When UII and serial number are both being identified, 

provide the serial number in2/N9/270. The serial number may not 

exceed 30 characters and may only include alpha numeric 

characters, dashes and forward slashes. Spaces are not allowed.

Use this qualifier for unique item tracking based upon the serial 

number.

2 DLMS enhancement. See introductory DLMS note 4a.

U3 Unique Supplier Identification Number (USIN) 

DLMS Note:

Administrative 

update to cite serial 

number length 

consistent with 

other ICs, and to 

identify code U3 

(UII) as a DLMS 

enhancement. 
Enclosure 2, PDC 1244

IC Change Tables

Page 6

# Location DLMS 527D Prepositioned Materiel Receipt (PMR)

Administrative Revisions

Reason

1. Use to identify the UII. Place UII value in REF03. The UII may 

not exceed 50 characters in accordance with IUID Policy. A data 

maintenance action was approved in version 5020. The approved 

code/name is "UII - Department of Defense Unique Item Identifier.

2. DLMS enhancement. See DLMS introductory note 4a. 

Authorized DLMS migration enhancement. See DLMS introductory 

note 4g.

4. 2/G62/260 Delete segment level Federal Note and combine with DLMS note.

Federal Note:

Use to identify dates related to data represented in 2/REF/250.

DLMS Note:

Use to identify dates related to data represented in 2/REF/250. 

DLMS enhancement; see introductory DLMS note 4a.

Administrative 

update.

5. 2/G6201/260 Delete Federal note:

Federal Note: Use any code

Administrative 

update.

6. 2/N9/270 Delete Federal Note and combine with DLMS note:

Federal Note: Use multiple repetitions to identify the characteristic(s) 

not defined in the 2/REF/250 segment.

DLMS Note: Use multiple repetitions to identify the 

characteristic(s) not defined in the 2/REF/250 segment. DLMS 

enhancement. See introductory DLMS note 5a.

Administrative 

update.

7. 2/N901/270 Remove codes PM, QW, and T0 and associated DLMS notes:

Delete Federal Note:

Federal Note: Use any code.

PM Part Number

DLMS Note:

Use to identify the part number of the item identified by UII or serial 

number. Use to identify the original

part number when associated with a UII. When this differs from the 

current part number use N901 to identify the new part number. A data 

maintenance action was approved in version 5020. The approved 

code/name is “OPN –

Original Part Number”.

QW New Part Number

DLMS Note:

Use to indicate the current part number when different from the 

original part number.

T0 Dealer Type Identification 

DLMS Note: 

Use to identify the UII type per IUID guidance e.g., VIN, UID1, 

UID2, etc.

Administrative 

update to remove 

individual parts of 

the UII consistent 

with IUID 

approach for 

DLMS 

transactions. 

DLMS transactions 

provide the 

constructed UII, 

not the individual 

pieces of the UII.
Enclosure 2, PDC 1244

IC Change Tables

Page 7

# Location DLMS 527D Prepositioned Materiel Receipt (PMR)

Administrative Revisions

Reason

8. 2/N1/280 Close 2/N1/280:

Federal Note:

Use to identify UIT information as needed.

DLMS Note:

DLMS enhancement. See introductory DLMS note 5a.

Removes 

requirement to 

provide individual 

parts of the UII 

consistent with 

IUID approach for 

DLMS 

transactions.

9. 2/N101/280 2/N1/280 closed; 2/N101/280 content is removed:

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following codes are authorized

MF Manufacturer of goods

DLMS Note:

Use to identify the manufacturer of the identified item.

IAT Party Executing and Verifying

DLMS Note: Use to indicate the Enterprise Identifier (EID) 

responsible for the UII.

A data maintenance action was approved in version 5020. The 

approved code/name is "EID - Department of Defense Enterprise 

Identifier".

Removes 

requirement to 

provide individual 

parts of the UII 

consistent with 

IUID approach for 

DLMS 

transactions.

Remove 

manufacturer of 

good from UIT 

loop, a DLMS 

enhancement for 

which no 

requirement was 

documented in a 

PDC.

10. 2/N103/280 2/N1/280 closed; 2/N103/280 content is removed:

Federal Note: Use any code.

DLMS Note: 1. For DLMS use, the following codes are authorized. 

2. The value of the IUID Issuing Agency Code (IAC) may be derived 

from the qualifier used for the Enterprise Identifier. 

1 D-U-N-S Number, Dun & Bradstreet 

DLMS Note: Corresponds to IAC 'UN'.

8 UCC/EAN Global Product Identification Prefix

DLMS Note: Corresponds to IAC '0-9'.

9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note: Corresponds to IAC 'LD'.

33 Commercial and Government Entity (CAGE)

DLMS Note: Corresponds to IAC 'D'.

41 Telecommunications Carrier Identification Code 

DLMS Note: Corresponds to IAC 'LB' (ANSI T1.220, Commercial 

Telecommunications Standards).

Removes 

requirement to 

provide individual 

parts of the UII 

consistent with 

IUID approach for 

DLMS 

transactions. The 

deleted DLMS 

notes at the codes 

were associated 

with the IUID 

issuing agency 

code (IAC).

11. 2/N104/280 2/N1/280 closed; 2/N104/280 content is removed:

67 Identification Code

Removes 

requirement to 

provide individual 

parts of the UII.
Enclosure 2, PDC 1244

IC Change Tables

Page 8

B. 527R Receipt

# Location DLMS 527R Receipt

Revision

Reason

1 IC Cover pages 

DLMS 

Introductory 

Notes

Revise DLMS Introductory Note 6:

6. This transaction may be used on a limited scope to provide item 

unique identification (IUID) information in accordance with DLMS 

procedures and OSD Supply Policy. Loop ID REF (2/REF/250) 

documents the authorized uses of unique item identifier (UII) and 

serial number. is limited to use with receipt transactions for unique 

item tracking (UIT) programs for Positive Inventory Control (PIC) 

Nuclear Weapon Related Materiel (NWRM), and Navy Depot Level 

Reparables. Also authorized for limited DLA Disposition Services 

use with receipt and TRA transactions for the UIT program for Small 

Arms and Light Weapons Serialization Program (DoDSALWSP). 

Additionally, under OSD Supply Policy for item unique identification 

(IUID) implementation is limited to receipt for the return of items to 

inventory which had previously been issued to a commercial activity 

for repair (2/LIN01/010 Code E (D4M functionality)). For all other 

purposes procedures, the serial number and UII are placeholders for 

DLMS enhancements pending development of DLMS procedures and 

overarching OSD Supply Policy. Refer to the IUID web at URL: 

http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy.

Updates 

introductory note 

on use of 

UII/serial 

number.

2. IC Cover pages

DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Note 7:

- ADC 1244, Establishing Visibility of Unique Item Tracking 

(UIT) Program Items for Service-Owned Assets Stored at DLA 

Distribution Centers and Corresponding Revisions to Inventory 

Procedures Related to Capital Equipment.

Identifies DLMS 

Changes

included in the

IC.

3. 2/REF/250 Revise Segment Level DLMS Notes as follows:

1. At this time,The entire 2/REF/250 loop is not an authorized 

DLMS enhancement for use to provide item unique identification 

(IUID) serialized data or Unique Item Tracking (UIT) information

except as noted below for specific implementations; see introductory 

DLMS note 4e. For all other applications, see introductory DLMS 

note 5a.

2. This transaction will support item identification based upon the 

UII or the serial number/UII. Must use 2/REF/250 loop when 

authorized for including UII, serial number, and/or batch/lot 

number in the transaction. When item requires both UII and serial 

number, enter the UII in 2/REF/250 and enter the serial number in 

2/N9/270. Repeat the 2/REF/250 loop for each item to be identified 

by UII, serial number, or batch/lot number. Data elements 

associated with the UII may be identified separately. Use the 

appropriate data elements to satisfy the desired functionality. The 

entire 2/REF/250 loop is a DLMS enhancement. See introductory 

DLMS note 5a. 

3. Authorized for DLA Distribution Center receipt processing to 

identify the UII for reparable items returned to DoD inventory by 

repair contractors (2/LIN01/010 Code E).

Documents UIT 

program items

requirement.

DLMS Note 2 

updates include 

deleting the

individual data 

elements associated 

with the UII 

consistent with the 

IUID approach for

DLMS 

transactions.

Administrative 

updates to 

reorganize the 

segment level 

notes; not all such 

administrative 

updates are bold 

italicized. Includes 
Enclosure 2, PDC 1244

IC Change Tables

Page 9

# Location DLMS 527R Receipt

Revision

Reason

Refer to ADC 1042. 

4. Authorized for DLA Disposition Services use in receipt, and TRA

to identify the serial number for Small Arms/Light Weapons 

(SA/LW) or industrial plant equipment. For the receipt, the serial 

number/UII is used by both the DLA Disposition Services Field 

Offices and the DLA Disposition Services ICP. For the TRA, DLA 

Disposition Services Field Office provides the serial number/UII to 

the TRA recipient. Refer to ADC 442 and ADC 1111.

5. In support of Financial Improvement and Audit Readiness 

(FIAR) compliance, capital equipment candidates require 

serialization data visibility. Authorized for use with receipts under 

DoD IUID policy for accountability and management of capital 

equipment. Prepare the receipt with the serial number and when 

available, include the UII. Refer to ADC 1198.

6. Under DOD IUID policy, UIT programs require serialization 

data visibility. Authorized for use with receipts for all UIT 

programs with the exception of SA/LW. Prepare the receipt with 

the serial number and when available, include the UII. For 

SA/LW, refer to the separate program procedures pending 

transition to DLMS logistics transactions. Refer to ADC 1244.

7. Authorized for use with receipts for the reporting of Air Force GFP 

accountability of serially tracked assets between the Air Force CICP 

and Air Force APSR systems. Authorized for use with serial 

number, UII, and batch/lot number. Refer to ADC 1230.

8. Commercial Asset Visibility (CAV) uses in receipts to identify the 

serial number of the repair item.

moving the Air 

Force GFP 

accountability note 

to note #7.

Administrative 

update to move 

detailed 

requirements notes

from UII and serial 

number data 

element level to 

segment level, for 

consistency with 

the identification of 

other requirements 

at segment level.

4. 2/REF01/250 Delete Federal Note: 

Federal Note: Use any code.

Revise qualifiers BT, SE and U3 DLMS notes as follows:

BT Batch 

DLMS Note:

1. Use to identify the batch, lot, or production run. The batch/lot 

number may not exceed 20 characters in accordance with IUID 

policy.

2. Use ‘BT’ in 2/REF/250 when UII or serial number does not apply 

for the item. When UII or serial number is required in addition to 

batch/lot number, enter the UII or serial number in 2/REF/250 and 

enter the batch/lot number in 2/N9/270.

3. Authorized for Air Force GFP-A. Refer to ADC 1230.

SE Serial Number

DLMS Note: 

1. Use to identify the serial number (when the UII (code U3) is not 

used). When UII and serial number are both being identified, 

provide the serial number in2/N9/270. The serial number may not 

exceed 30 and may only include alpha numeric characters, dashes

and forward slashes. Spaces are not allowed. Use this qualifier for 

unique item tracking based upon the serial number.

Administrative 

updates to:

--Cite serial 

number length.

--Remove DLMS 

enhancement notes

at data element 

level. The 

2/REF/250 segment 

level note identifies 

that the 2/REF/250 

loop is an 

authorized DLMS 

enhancement for 

specific 

implementations; 

otherwise see 

introductory DLMS 

note 5a. No need to 

repeat at data 

element level 

within the loop.
Enclosure 2, PDC 1244

IC Change Tables

Page 10

# Location DLMS 527R Receipt

Revision

Reason

2. Commercial Asset Visibility (CAV) uses in receipts to identify the 

serial number of the repair item.

3. Authorized DLMS enhancement for DLA Disposition Services use 

in receipt, historical receipt, and TRA to identify the serial number 

for Small Arms/Light Weapons (SA/LW) or industrial plant 

equipment. For the Receipt, the serial number is used by both the 

DLA Disposition Services Field Offices and the DLA Disposition 

Services ICP. For the TRA, DLA Disposition Services Field Office 

provides the serial number to the TRA recipient. Refer to ADC 442 

and ADC 1111.

4. Authorized for capital equipment candidates.

5. Authorized for Air Force GFP-A. Refer to ADC 1230. 

6. Except as noted DLMS enhancement. See introductory DLMS note 

5a.

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 IUID Policy. A data 

maintenance action was approved in version 5020. The approved 

code/name is "UII - Department of Defense Unique Item Identifier.

2. Authorized DLMS enhancement for DLA Disposition Services use 

in receipt, historical receipt, and TRA to identify the UII for SA/LW 

or industrial plant equipment. For the Receipt, the UII is for use by 

both the DLA Disposition Services Field Offices and the DLA 

Disposition Services ICP. For the TRA, DLA Disposition Services 

Field Office provides the UII to the TRA recipient. Refer to ADC 

442 and ADC 1111.

3. Authorized DLMS enhancement for DLA Distribution Center 

receipt processing to identify the UII for reparable items returned to 

DoD inventory by repair contractors. Refer to ADC 1042.

4. Authorized for capital equipment candidates. Refer to ADC 1198.

5. Authorized to support Air Force GFP-A. Refer to ADC 1230. 

5Except as noted DLMS enhancement. See DLMS introductory 

note 5a.

--Move CAV, 

Disposition 

Services, capital 

equipment and AF 

GFP accountability

DLMS Notes from 

serial number or 

UII or Batch data

element level to 

segment level, for 

consistency with 

other ICs 

identifying 

requirements at 

segment level.

5. 2/REF04-01/250 Delete Federal note:

Federal Note: Use any code

Administrative 

update.

6. 2/G62/260 Delete segment level Federal note and combine with DLMS note.

Federal Note:

Use to identify dates related to data represented in 2/REF/250.

DLMS Note:

Use to identify dates related to data represented in 2/REF/250. 

DLMS enhancement; see introductory DLMS note 4a.

Administrative 

update.

7. 2/G6201/260 Delete Federal note:

Federal Note: Use any code
Enclosure 2, PDC 1244

IC Change Tables

Page 11

# Location DLMS 527R Receipt

Revision

Reason

8. 2/N9/270 Combine segment level Federal note with DLMS note:

Federal Note: Use multiple repetitions to identify the characteristic(s) 

not defined in the 2/REF/250 segment.

DLMS Note: Use multiple repetitions to identify the 

characteristic(s) not defined in the 2/REF/250 segment. DLMS 

enhancement. See introductory DLMS note 5a.

Administrative 

update.

9. 2/N901/270 Administrative update: 

SE Serial Number

DLMS Note:

Use to identify the serial number (when UII (code U3) is used in 

2/REF01/250). The serial number may not exceed 30 characters

and may only include alpha numeric characters, dashes and 

forward slashes. Spaces are not allowed.

Administrative 

update to document 

maximum serial 

number length. 

10. 2/N901/270 Remove codes PM, QW, and T0 and associated DLMS notes:

Delete Federal Note:

Federal Note: Use any code.

PM Part Number

DLMS Note:

Use to identify the part number of the item identified by UII or serial 

number. Use to identify the original

part number when associated with a UII. When this differs from the 

current part number use N901 to

identify the new part number. A data maintenance action was 

approved in version 5020. The approved code/name is “OPN –

Original Part Number”.

QW New Part Number

DLMS Note:

Use to indicate the current part number when different from the 

original part number.

T0 Dealer Type Identification 

DLMS Note: 

Use to identify the UII type per IUID guidance e.g., VIN, UID1, 

UID2, etc.

Removes 

requirement to 

provide individual 

parts of the UII 

consistent with 

IUID approach for 

DLMS 

transactions.

11. 2/N1/280 Close 2/N1/280:

Federal Note:

Use to identify UIT information as needed.

DLMS Note:

DLMS enhancement. See introductory DLMS note 5a.

Removes 

requirement to 

provide individual 

parts of the UII 

consistent with 

IUID approach for 

DLMS 

transactions.
Enclosure 2, PDC 1244

IC Change Tables

Page 12

# Location DLMS 527R Receipt

Revision

Reason

12. 2/N101/280 2/N1/280 closed; 2/N103/280 content is removed:

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following codes are authorized

MF Manufacturer of goods

DLMS Note:

Use to identify the manufacturer of the identified item.

IAT Party Executing and Verifying

DLMS Note: Use to indicate the Enterprise Identifier (EID) 

responsible for the UII.

A data maintenance action was approved in version 5020. The 

approved code/name is "EID - Department of Defense Enterprise 

Identifier".

Removes 

requirement to 

provide individual 

parts of the UII 

consistent with 

IUID approach for 

DLMS 

transactions.

Remove 

manufacturer of 

good from UIT 

loop, a DLMS 

enhancement for 

which no 

requirement was 

ever identified and 

documented in a 

PDC.

13. 2/N103/280 2/N1/280 closed; 2/N103/280 content is removed:

Federal Note: Use any code.

DLMS Note: 1. For DLMS use, the following codes are authorized. 

2. The value of the IUID Issuing Agency Code (IAC) may be derived 

from the qualifier used for the Enterprise Identifier. 

1 D-U-N-S Number, Dun & Bradstreet 

DLMS Note: Corresponds to IAC 'UN'.

8 UCC/EAN Global Product Identification Prefix

DLMS Note: Corresponds to IAC '0-9'.

9 D-U-N-S+4, D-U-N-S Number with Four Character Suffix

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note: Corresponds to IAC 'LD'.

33 Commercial and Government Entity (CAGE)

DLMS Note: Corresponds to IAC 'D'.

41 Telecommunications Carrier Identification Code 

DLMS Note: Corresponds to IAC 'LB' (ANSI T1.220, Commercial 

Telecommunications Standards).

Removes 

requirement to 

provide individual 

parts of the UII 

consistent with 

IUID approach for 

DLMS 

transactions. The 

deleted DLMS 

notes at the codes 

were associated 

with the IUID 

issuing agency 

code (IAC).

14. 2/N104/280 2/N1/280 closed; 2/N104/280 content is removed:

67 Identification Code

Removes 

requirement to 

provide individual 

parts of the UII.
Enclosure 2, PDC 1244

IC Change Tables

Page 13

C. 842A/W Standard SDR, Follow-Up, Correction, Cancellation & Reconciliation 

Request

# Location DLMS 842A/W Standard SDR, Follow-up, Correction, 

Cancellation & Reconciliation Revision

Reason

1. IC cover page 

DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Notes:

- ADC 1244, Establishing Visibility of Unique Item 

Tracking (UIT) Program Items for Service-Owned Assets 

Stored at DLA Distribution Centers and Corresponding 

Revisions to Inventory Procedures Related to Capital 

Equipment.

Identifies DLMS Changes

included in the IC.

2. 2/HL03/0100 Revise DLMS note for existing Code I:

I Item

DLMS Note:

Use to identify IUID data consistent with IUID data 

requirements. The IUID data is carried in the REF segment (UII 

and Serial Number). The NCD segment is required by ANSI 

syntax and is used to indicate if an item is received or not 

received; and no other segments are used in the IUID loop. Must

use a separate IUID loop for each item. Skip this level when not 

applicable. The UII value and some of the associated data 

elements are IUID data is a DLMS enhancements; these data 

elements may or may not be received or understood by the 

recipient’s automated processing system.

Administrative update for 

clarification.

3. 2/NCD03/2300 Revise DLMS note for existing data element:

Assigned Identification

DLMS Note:

1. Use as a counter to satisfy ANSI syntax. Must cite numeric 1 

EXCEPT where pending future enhancement to support

additional NCD loops for are used to report multiple missing 

component parts or multiple incorrect items received when 

providing unique identification of discrepant items. In these 

instances, increase incrementally by 1 for each missing 

component or uniquely identified item.

2. When providing item unique identification due to a mismatch 

(including shortage/overage) resulting from comparison between 

shipping notice, due-in, or documentation, and the packaging or 

item, follow the numeric counter by an indicator to distinguish 

the item(s) received from the anticipated item(s) not received. 

Suffix the counter by the letter R for items received and N for 

items not received. See ADC 1030.

3. Use of this looping structure to describe multiple incorrect 

items received in association with Discrepancy Code W5, Mixed 

Stock, is reserved for future implementation. 

4. Use of this looping structure to describe multiple missing 

component parts is reserved for future implementation.

Administrative update for 

clarification.

Administrative update for 

clarification
Enclosure 2, PDC 1244

IC Change Tables

Page 14

# Location DLMS 842A/W Standard SDR, Follow-up, Correction, 

Cancellation & Reconciliation Revision

Reason

4. 2/REF/2600 Add new Segment Level note 4:

1. Use in 2/HL/0100 IUID loop to provide IUID information. 

Repeat the REF segment within each IUID loop to identify 

relevant IUID information. 

2. This transaction will support item identification based upon the 

UII or the serial number. Data elements associated with the UII 

may be identified separately. Use the appropriate data elements 

to satisfy the desired functionality.

32. In support of Financial Improvement and Audit Readiness 

(FIAR) compliance, capital equipment candidates require 

serialization data visibility. Submitters must prepare SDRs citing 

the applicable serial number(s) as mandatory, and when 

available, include UIIs, when IUID is appropriate for the type of 

discrepancy (e.g., wrong item, shortage/overage, receipt in a 

condition other than expected, or a serial number/UII mismatch 

between the item and documentation). Refer to ADC 1198.

3. Under DOD IUID policy, UIT programs require 

serialization data visibility. Submitters must prepare SDRs 

citing the applicable serial number(s) as mandatory, and when 

available, include UIIs, when appropriate for the type of 

discrepancy (e.g., wrong item, shortage/overage, receipt in a 

condition other than expected, or a serial number/UII 

mismatch between the item and documentation). Refer to ADC

1244.

Documents UIT program 

requirement.

5. 2/REF01/2600 No change to the following:

SE Serial Number

DLMS Note: 

1. Use in IUID loop to identify the serial number.

2. The serial number may not exceed 30 characters and may only 

include alpha numeric characters, dashes and forward slashes. 

Spaces are not allowed. in accordance with IUID Policy .

U3 Unique Supplier Identification Number (USIN) 

DLMS Note:

1. Use in IUID loop to identify the UII value. Cite the UII in 

REF03. A data maintenance action was approved in version 

5020. The approved code/name is "UII - Department of Defense 

Unique Item Identifier.

2. The UII may not exceed 50 characters in accordance with 

IUID Policy.

Provided for context.
Enclosure 2, PDC 1244

IC Change Tables

Page 15

D. 842P Product Quality Deficiency Report (PQDR) Data Exchange

# Location DLMS 842P Product Quality Deficiency Report (PQDR) 

Data Exchange

Reason

1. IC cover page 

DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Notes:

- ADC 1244, Establishing Visibility of Unique Item 

Tracking (UIT) Program Items for Service-Owned Assets 

Stored at DLA Distribution Centers and Corresponding 

Revisions to Inventory Procedures Related to Capital 

Equipment.

Identifies DLMS Changes

included in the IC.

2. 2/REF01/2600 Revise DLMS note 2 as shown:

DLMS Note: 

1. For DLMS use the following codes are authorized.

2. Use codes separately or in combination, to identify 

appropriate information for serialized items for unique item 

tracking (UIT) or reporting. 

3. In support of Financial Improvement and Audit Readiness 

(FIAR) compliance, capital equipment candidates require 

serialization data visibility. Submitters must prepare PQDRs 

citing the applicable serial number(s) as mandatory, and when 

available, include UIIs.

4. Under IUID policy, unique item tracking (UIT) program 

items require serialization data visibility. Submitters must 

prepare PQDRs citing the applicable serial number(s) as 

mandatory, and when available, include UIIs.

SE Serial Number

DLMS Note:

1. Use in IUID loop to identify the serial number. Equates to SF 

368 Block 11 Deficient Item Serial Number.

2. For Next Higher Assembly Serial Number (SF368, Block 

17d) refer to 2/LIN20/0200 Code EM in the report loop. For 

Engine Serial Number, refer to 2/LIN26/0200 Code SN in the 

report loop. For serial number of the End Item (SF 368, Block 

18d), refer to 2/REF01/0700 Code SE in the report loop.

3. The serial number may not exceed 30 characters and may

only include alpha numeric characters, dashes and forward 

slashes. Spaces are not allowed.

U3 Unique Supplier Identification Number (USIN)

DLMS Note:

1. Use in IUID loop to identify the UII value.

2. A data maintenance action was approved in version 5020. The 

approved code/name is "UII - Department of Defense Unique 

Item Identifier.

3. The UII may not exceed 50 characters in accordance with 

IUID policy.

Documents UIT program 

requirement.

Provided for context.
Enclosure 2, PDC 1244

IC Change Tables

Page 16

E. 842S/Q Storage Quality Control Report

# Location DLMS 842S/Q Storage Quality Control Report

Revision

Reason

1. IC cover page 

DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Notes:

- ADC 1244, Establishing Visibility of Unique Item Tracking 

(UIT) Program Items for Service-Owned Assets Stored at DLA 

Distribution Centers and Corresponding Revisions to Inventory 

Procedures Related to Capital Equipment.

Identifies DLMS 

Changes included

in the IC. 

2. 2/REF/2600 Add new Segment Level note 4 as follows:

1.Use in 2/HL0100 IUID loop to provide IUID information. Use a 

separate IUID loop for each item. Repeat the REF segment within

each IUID loop to identify relevant IUID information.

2. This transaction will support item identification based upon the 

UII or the serial number. Data elements associated with the UII may 

be identified separately. Use the appropriate data elements to satisfy 

the desired functionality.

32. In support of Financial Improvement and Audit Readiness 

(FIAR) compliance, capital equipment candidates require 

serialization data visibility. Submitters must prepare SQCRs citing 

the applicable serial number(s). Include the UII when available.

Refer to ADC 1198.

3. Under DOD IUID policy, UIT program items require 

serialization data visibility. Submitters may prepare SQCRs citing 

the applicable serial number(s), and when available, include the 

UII, in accordance with stock readiness procedures. Refer to ADC

1244.

Documents UIT 

program 

requirement.

3. 2/REF01/2600 No change to the following:

SE Serial Number

DLMS Note: Use in IUID loop to indicate Serial Number.

The serial number may not exceed 30 characters and may only 

include alpha numeric characters, dashes and forward slashes. 

Spaces are not allowed.

U3 Unique Supplier Identification Number (USIN) 

DLMS Note: 1. Use in IUID loop to identify the UII value.

2. A data maintenance action was approved in version 5020. The 

approved code/name is "UII - Department of Defense Unique Item 

Identifier".

Provided for context
Enclosure 2, PDC 1244

IC Change Tables

Page 17

F. 846P Physical Inventory Request 

# Location DLMS 846P Physical Inventory Request

Revision

Reason

1. IC cover page 

DLMS 

Introductory 

Notes

Add change to DLMS Introductory Notes:

- ADC 1244, Establishing Visibility of Unique Item Tracking 

(UIT) Program Items for Service-Owned Assets Stored at DLA 

Distribution Centers and Corresponding Revisions to Inventory 

Procedures Related to Capital Equipment.

Identifies DLMS 

Changes included

in the IC. 

2/REF01/140 Add new DLMS Note 1 to existing qualifier TN, and renumber 

existing notes:

TN Transaction Reference Number

DLMS Note:

1. Use to identify the document number assigned by the materiel 

owner/manager as part of an physical inventory request. The 

storage activity must perpetuate the document number in the 

response when provided.. Required for capital equipment

candidates and UIT programs. Authorized DLMS enhancement 

for all other commodities. Refer to ADC 1244.

2. For Air Force GFP accountability, use to identify the document 

number assigned by the Air Force program manager in the 

accountable property system of record (APSR). The CICP must 

perpetuate the document number to the response. Refer to ADC 

1224.

Relates a Physical 

Inventory Request 

and associated 

response.

G. 846R Location Reconciliation Request

# Location DLMS 846R Location Reconciliation 

Request Revision

Reason

1 IC cover page 

DLMS 

Introductory 

Notes

Revise DLMS Introductory Note 5:

5. This transaction may be used on a limited scope to provide 

item unique identification (IUID) information in accordance 

with DLMS procedures and OSD Supply Policy. Loop ID REF 

(2/REF/390) documents the authorized uses of unique item 

identifier (UII) and serial number. For all other purposes, This 

transaction includes the IUID information is a placeholders for 

DLMS enhancements to provide item unique identification (IUID) 

information pending development of DLMS procedures and 

overarching OSD Supply Policy. Refer to the IUID web at URL:

http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy. There is 

limited authorization to use IUID information to support Service 

ammunition systems as documented in IC.

Updates note for 

authorization of use of 

IUID UII and serial 

number data. Refers

user to the 2/REF/390 

Loop for detailed 

information.
Enclosure 2, PDC 1244

IC Change Tables

Page 18

# Location DLMS 846R Location Reconciliation 

Request Revision

Reason

2. IC cover page 

DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Note 6:

- ADC 1244, Establishing Visibility of Unique Item Tracking 

(UIT) Program Items for Service-Owned Assets Stored at 

DLA Distribution Centers and Corresponding Revisions to 

Inventory Procedures Related to Capital Equipment.

Identifies DLMS 

Changes included in

the IC.

3. 2/REF/390 Revise Segment Level notes as follows:

1. At this time, The entire 2/REF/390 loop is not an authorized 

DLMS enhancement for use to provide item unique identification 

(IUID) or Unique Item Tracking (UIT) serialized data information

as noted below for specific implementations; see introductory 

DLMS note 4f. For all other applications, see introductory 

DLMS note 4a. except for Service Ammunition systems; and in 

support of Financial Improvement and Audit Readiness (FIAR) 

compliance for capital equipment.

2. This transaction will support item identification based upon the

serial number/unique item identifier (UII) or the serial number; 

also provides for use of a batch/lot number when applicable. Must 

use 2/REF/390 loop in location reconciliation request transactions 

when authorized for including UII, serial number, and/or batch/lot 

number.

3. Repeat the 2/REF/390 loop for each item to be identified by 

UII, serial number or batch/lot number. If UII and serial number, 

and/or batch/lot number are required for the item, enter the UII in 

REF01, and enter the serial number and/or batch/lot number in 

REF04. If UII is not used, enter the serial number in REF01 and 

enter the batch/lot number in REF04. If only batch/lot number is 

required, enter the batch/lot number in REF01.The entire 

2/REF/390 loop is a DLMS enhancement see introductory DLMS 

note 4a.

4. Authorized for use with location reconciliation request 

transactions to support Service Ammunition systems (i.e., Naval 

Operational Logistics Support Center (NOLSC) Ordnance 

Information System – Wholesale (OIS-W) requirement; Program 

Manager for Ammunition, Marine Corps Systems Command 

(MARCORSYSCOM) Ordnance Information System-Marine 

Corps (OIS-M); and Warner Robins Air Logistics Center Combat 

Ammunition System (CAS). See introductory DLMS notes 4a and 

4e. Refer to ADC 283 and ADC 445.

5. Authorized in support of Financial Improvement and Audit 

Readiness (FIAR) compliance for capital equipment. Capital

candidates require serialization data visibility. Prepare location 

reconciliation request transactions with the serial number as 

mandatory and when available, include the UIIusing the serial 

number and include the UII when available. Refer to ADC 1198.

6. Authorized under DOD IUID policy for UIT programs. UIT 

programs require serialization data visibility. For all UIT 

programs with the exception of SA/LW, prepare the location 

Documents UIT program 

requirement.

Administrative update 

rearranges notes for 

consistency and 

clarification. This 

administrative update is 

not identified by bold 

italics.
Enclosure 2, PDC 1244

IC Change Tables

Page 19

# Location DLMS 846R Location Reconciliation 

Request Revision

Reason

reconciliation request with the serial number and when 

available, include the UII. For SA/LW, refer to the separate 

program procedures pending transition to DLMS logistics 

transactions. Refer to ADC 1244.

7. Authorized for the reporting of Air Force GFP accountability of 

serially tracked assets between the Air Force CICP and Air Force 

APSR systems. Authorized for use with serial number, UII, and 

batch/lot number. Refer to ADC 1230. 

8. Supports Inter-Service Ammunition BG1/BG2 data 

requirement. See introductory DLMS note 4.e. When the serial 

number is used in REF01 with Ammunition BG1/BG2 

transactions, this qualifier implies that the transaction is a BG1 

(Serial Number or Lot and Serial Number Controlled Item 

Transaction). When the batch number is used in REF01 with 

Ammunition BG1/BG2 transactions, this qualifier implies that the 

transaction is a BG2 (Lot Number Controlled Item Transaction). 

In a mixed DLSS/DLMS environment, UII is not used in 

Ammunition BG1/BG2 transactions. Only authorized values for 

Ammunition BG1/BG2 are BT and SE, used at REF01 and 

REF04-01. Refer to ADC 283 and ADC 445.

4. 2/REF01/390 Update as follows:

BT Batch 

DLMS Note:

1. Use to identify the manufacturer's batch/lot number or other 

number identifying the production run when UII and/or serial 

number are not required. If UII and/or serial number are required 

in addition to the batch/lot number, enter the batch/lot number in 

REF04. The batch/lot number may not exceed 20 characters in 

accordance with IUID policy.

2. DLMS enhancement; see introductory DLMS note 4a. 

3. Supports Inter-Service Ammunition BG1/BG2 data 

requirement. See introductory DLMS note 4.e. When used with 

Ammunition BG1/BG2 transactions, this qualifier implies that 

the transaction is a BG2 (Lot Number Controlled Item 

Transaction). Refer to ADC 283 and ADC 445.

4. Authorized for Air Force GFP-A. Refer to ADC 1230. 

SE Serial Number

DLMS Note: 

1. Use to identify the serial number when UII is not required. If 

UII is required in addition to the serial number, enter serial 

number in REF04. The serial number may not exceed 30

characters and may only include alpha numeric characters, 

dashes and forward slashes. Spaces are not allowed.

2. DLMS enhancement; see introductory DLMS note 4a.

3. Supports Inter-Service Ammunition BG1/BG2 data 

requirement. See introductory DLMS note 4.e. When used with 

Administrative update to 

identify serial number 

maximum field length.

Administrative update to 

move detailed data 

element level DLMS 

Notes for AF GFP 

accountability and interService ammunition 

BG1/BG2, to segment 

level notes, consistent 

with other ICs.

Administrative update to 

delete data element level 

enhancement note. The 

entire 2/REF/390 loop is 

an enhancement as noted 

at 2/REF/390 segment 

level note. No need to 

repeat enhancement notes 

at data elements within 

the loop.
Enclosure 2, PDC 1244

IC Change Tables

Page 20

# Location DLMS 846R Location Reconciliation 

Request Revision

Reason

Ammunition BG1/BG2 transactions, this qualifier implies that the 

transaction is a BG1 (Serial Number or Lot and Serial Number 

Controlled Item Transaction). Refer to ADC 283 and ADC 445.

4. Authorized for Air Force GFP-A. Refer to ADC 1230.

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 IUID Policy. An 

ANSI data maintenance was approved in version 5020. The 

approved code/name is “UII-Department of Defense Unique Item 

Identifier”.

2. Authorized DLMS migration enhancement see DLMS 

introductory DLMS note 4f.

3. In a mixed DLSS/DLMS environment, UII is not used in 

Ammunition BG1/BG2 transactions. Only authorized values for 

Ammunition BG1/BG2 are BT and SE.

4. Authorized for Air Force GFP-A. Refer to ADC 1230.

5. 2/REF04-

01/390

Revise as follows:

Delete Federal Note : Use any code.

BT Batch Number

DLMS Note:

1. Use to identify the manufacturer's batch/lot number or other 

number identifying the production run, when UII or serial number 

is entered in REF01, and batch/lot is the only other identifying 

number in 2/REF/390. The batch/lot number may not exceed 20 

characters in accordance with IUID policy.

2. Supports Inter-Service Ammunition DIC BG1/BG2 data 

requirement. See introductory DLMS note 4.e. When used with 

Ammunition BG1/BG2 transactions, this qualifier implies that the 

transaction is a BG1 (Serial Number or Lot and Serial Number 

Controlled Item Transaction). Refer to ADC 283 and ADC 445.

SE Serial Number

DLMS Note:

1. Use to identify the serial number when UII is entered in REF01 

and serial number is also used. The serial number may not 

exceed 30 characters and may only include alpha numeric 

characters, dashes and forward slashes. Spaces are not allowed.

2. Not used in Ammunition BG1/BG2 transactions. For BG1/BG2 

requirement, SE qualifier is only used in the REF01 segment.

Administrative updates to 

remove specific 

requirements at data 

element level in favor of 

using segment level 

notes.

Administrative update to 

identify serial number 

maximum field length.

6. 2/REF04-

03/390

Revise as follows:

Delete Federal Note : Use any code.

BT Batch Number

DLMS Note:

1. Use to identify the manufacturer's batch/lot number or other 

number identifying the production run when UII is entered in 

Administrative updates to 

remove specific 

requirements at data 

element level in favor of 

using segment level 

notes.
Enclosure 2, PDC 1244

IC Change Tables

Page 21

# Location DLMS 846R Location Reconciliation 

Request Revision

Reason

REF01 and serial number is entered in REF04-01. The batch/lot 

number may not exceed 20 characters in accordance with IUID 

policy. 

2. Not used with Ammunition DIC BG1/BG2 transactions. For 

BG1/BG2 requirement, BT qualifier is only used in the REF01 

and REF04/C00401 segments.

H. 856R Shipment Status Materiel Returns (must use 856R Version 4030 for IUID)

# Location DLMS 4030 856R Shipment Status Materiel 

Returns Revision

Reason

1. DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Notes:

- ADC 1244, Establishing Visibility of Unique Item 

Tracking (UIT) Program Items for Service-Owned Assets 

Stored at DLA Distribution Centers and Corresponding 

Revisions to Inventory Procedures Related to Capital 

Equipment.

Identifies DLMS 

Changes included in

the IC.

2. 2/REF/1500 Revise Segment Level notes as follows:

1. Must use in 2/HL/0100 transaction reference number loops to 

identify the document number, fund code and the transportation 

control number with the shipment status transaction.

2. Financial accounting data is provided as a DLMS enhancement. 

When implemented, refer to the Accounting Classification 

Appendix for specific entries for the basic appropriation number 

and supplemental accounting classification data.

3. This transaction supports unique item identification based upon 

the UII. Shipment status for materiel returns will be prepared 

using both the serial number and UII (when available) and 

required by DoD IUID Supply Policy. (see ADC 1071).

4. This transaction will support association of the IUID 

information with the RFID tag at the IUID packaging level and/or 

at each higher level of packing which has been tagged. 

5. In support of Financial Improvement and Audit Readiness 

(FIAR) compliance, capital equipment candidates require 

serialization data visibility. Prepare shipment status materiel 

return using the serial number. Include the UII when available. 

Refer to ADC 1198.

6. Under DOD IUID policy, UIT programs require serialization 

data visibility. Prepare shipment status materiel return with the 

serial number as mandatory and when available, include the 

UII. Refer to ADC 1244.

Documents UIT 

program requirement
Enclosure 2, PDC 1244

IC Change Tables

Page 22

# Location DLMS 4030 856R Shipment Status Materiel 

Returns Revision

Reason

3. 2/REF01/1500 No change to the following:

SE Serial Number

DLMS Note: 

1. Use in IUID loop to identify the serial number. See ADC 1071.

2. DLMS enhancement; see introductory DLMS Note 3f.

3. The serial number may not exceed 30 characters and may

only include alpha numeric characters, dashes and forward 

slashes. Spaces are not allowed. 

U3 Unique Supplier Identification Number (USIN) 

DLMS Note:

1. Use in IUID loop to identify the UII value in REF03. See ADC 

1071. The UII may not exceed 50 characters in accordance with 

IUID Policy. An ANSI data maintenance action was approved in 

version 5020. The approved code/name is "UII - Department of

Defense Unique Item Identifier”.

2. DLMS enhancement; see introductory DLMS Note 3f.

Provided for context.

I. 856S Shipment Status

# Location DLMS 4030 856S Shipment Status 

Revision

Reason

1. IC cover page 

DLMS 

Introductory 

Notes

Add ADC to DLMS Introductory Notes:

- ADC 1244, Establishing Visibility of Unique Item 

Tracking (UIT) Program Items for Service-Owned Assets 

Stored at DLA Distribution Centers and Corresponding 

Revisions to Inventory Procedures Related to Capital 

Equipment.

Identifies DLMS 

Changes included

in the IC.

2. 2/REF/1500 Revise Segment Level notes as follows:

1. This transaction supports unique item identification based 

upon the UII. Pending full transition to DoD IUID Supply 

Policy using the UII, shipment status will be prepared using

both the UII and corresponding serial number when available 

and required by DoD IUID Supply Policy. See ADC 1030.

2. This transaction will support association of the IUID 

information with the RFID tag at the IUID packaging level 

and/or at each higher level of packing which has been tagged.

3. Use this segment to comply with the DoD SLOA/Accounting 

Classification. Cost object elements Project Identifier, Funding 

Center Identifier, Functional Area, Cost Element Code, Cost 

Center Identifier, Activity Identifier, and Work Order Number 

are used as appropriate for the system. Refer to ADC 1043.

4. In support of Financial Improvement and Audit Readiness 

(FIAR) compliance, capital equipment candidates require 

serialization data visibility. Prepare shipment status using the 

serial number. Include the UII when available. Refer to ADC 

1198.

Documents UIT 

program requirement.
Enclosure 2, PDC 1244

IC Change Tables

Page 23

# Location DLMS 4030 856S Shipment Status 

Revision

Reason

5. Under DOD IUID policy, UIT programs require 

serialization data visibility. Prepare shipment status with the 

serial number as mandatory and when available, include the 

UII. Refer to ADC 1244.

3. 2/REF01/1500 Revise existing qualifiers SE and U3:

SE Serial Number

DLMS Note: 

1. Use in IUID loop to identify the serial number. See ADC 

1030.

2. DLA Distribution must use in shipment of items designated 

as capital equipment candidates. All others use in accordance 

with Component guidance for capital equipment. See ADC 

1198.

3. Must use in shipment of UIT program items. Refer to ADC

1244.

4. The serial number may not exceed 30 characters and may

only include alpha numeric characters, dashes and forward 

slashes. Spaces are not allowed.

5. DLMS enhancement; see introductory DLMS Note 2f.

U3 Unique Supplier Identification Number (USIN) 

DLMS Note:

1. Use in IUID loop to identify the UII value in REF03. See 

ADC 1030. A data maintenance action was approved in version 

5020. The approved code/name is "UII - Department of 

Defense Unique Item Identifier”.

2. DLA Distribution must use in shipment of items designated 

as capital equipment candidates when the item has been marked 

under IUID policy. All others use in accordance with 

Component guidance for capital equipment. See ADC 1198.

3. Must use in shipment of UIT program items when the item 

has been marked under IUID policy. Refer to ADC 1244.

4. DLMS enhancement; see introductory DLMS Note 2f.

Documents UIT 

program requirement.

J. 945A Materiel Release Advice (Must use 945A Version 4030 for IUID)

# Location DLMS 4030 945A Materiel Release Advice 

Revision

Reason

1. IC cover page 

DLMS 

Introductory

Notes

Add ADC to DLMS Introductory Notes:

- ADC 1244, Establishing Visibility Unique Item Tracking 

(UIT) Program Items for Service-Owned Assets Stored at 

DLA Distribution Centers and Corresponding Revisions to 

Inventory Procedures Related to Capital Equipment.

Identifies DLMS 

Changes

included in the

IC.

2. 2/LX/1100 Revise Segment Level notes as follows: 

3. Use for UII, serial number, and batch/lot number, when this 

message supports the Retail Supply-Transportation Interface (See 

Documents UIT 

program 

requirement.
Enclosure 2, PDC 1244

IC Change Tables

Page 24

# Location DLMS 4030 945A Materiel Release Advice 

Revision

Reason

DLM 4000.25 Volume 3, Chapter 2) and when required by DoD 

IUID Supply Policy. Authorized DLMS enhancement. See ADC 

1073. 

4. Authorized when required by DoD IUID Supply Policy for 

capital equipment candidates and UIT program items. Refer to 

ADC 1098/1098A and ADC 1244.

5. Authorized for the reporting of Air Force GFP accountability 

of serially tracked assets between the Air Force CICP and Air 

Force APSR systems. See ADC 1230.

6. Use a separate 2/LX/1100 loop for each identified item.

3. 2/N9/1200 Revise Segment Level notes as follows:

1. This segment supports item identification based upon the serial 

number/UII or the serial number. 

2. When this message supports the Retail Supply-Transportation 

Interface (See DLM 4000.25 Volume 3, Chapter 2), this 

transaction supports unique item identification (UII). Pending full 

transition to DoD IUID Supply Policy using the UII, the Materiel 

Release Confirmation will be prepared using the UII and the 

corresponding serial number and the batch/lot number when 

available when required by DoD IUID Supply Policy. Authorized 

DLMS enhancement. See ADC 1073. Also authorized for Air 

Force GFP accountability of serially tracked assets. See ADC 

1230. 

3. In support of Financial Improvement and Audit Readiness 

(FIAR) compliance, capital equipment candidates require 

serialization data visibility. Prepare Materiel Release 

Confirmation using the serial number. Include the UII when 

available. See ADC 1198.

4. Under DOD IUID policy, UIT programs require serialization 

data visibility. For all UIT programs with the exception of

SA/LW, prepare materiel release confirmation with the serial 

number as mandatory and when available, include the UII. For 

SA/LW refer to the separate program procedures pending 

transition to DLMS logistics transactions. See ADC 1244.

5. Authorized for Air Force GFP accountability of serially tracked 

assets. See ADC 1230.

6. This segment also provides for use of a batch/lot number, when 

applicable.

7. Repeat the N9 segment as needed to identify desired 

characteristics for the specific item.

8. With the exception of the limited implementation authorized by 

ADC 1073 in support of the Retail Supply-Transportation 

Interface, and use with capital equipment as noted, the entire 

2/N9/1200 segment is a DLMS enhancement. The 2/N9/1200 

segment is an authorized enhancement as noted above for 

specific implementations; see introductory note 4e. For all other 

applications, see introductory DLMS note 4a. 

Documents UIT 

program 

requirement.
Enclosure 2, PDC 1244

IC Change Tables

Page 25

# Location DLMS 4030 945A Materiel Release Advice 

Revision

Reason

4. 2/N901/1200 No change to the following:

SE Serial Number

DLMS Note: 

1. Use to identify the serial number. The serial number may not 

exceed 30 characters and may only include alpha numeric 

characters, dashes and forward slashes. Spaces are not allowed.

2. Authorized for intra-DLA use between DLA Disposition 

Services and DLA Disposition Field Offices to identify the serial 

number for Small Arms/Light Weapons (SA/LW). DLMS 

enhancement; Refer to ADC 449.

3. Use when this transaction supports the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange SBSS 

interface with CMOS to provide the serial number. Serial number 

may be used alone for legacy items when UII is not assigned, 

otherwise use two occurrences of this segment to identify both the 

serial number and the UII. A maximum of 60 items may be 

identified for this interface. See ADC 1073.

U3 Unique Supplier Identification Number (USIN) 

DLMS Note:

1. Use to identify the UII. The UII may not exceed 50 characters 

in accordance with DoD IUID Supply Policy.

2. Use when this transaction supports the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange SBSS 

interface with CMOS to provide the UII. A maximum of 60 items 

may be identified for this interface. See ADC 1073.

3. A data maintenance action was approved in version 5020. The 

approved code/name is UII -Department of Defense Unique Item 

Identifier.

Provided for 

context.

K. 947I Inventory Adjustment (Must use 947I Version 4030 for IUID)

# Location DLMS 947I Inventory Adjustment 

Revision

Reason

1. DLMS 

Introductory 

Notes on IC 

cover page

Revise DLMS Introductory Note 5:

5. This transaction may only be used on a limited scope to 

provide item unique identification (IUID) information in 

accordance with DLMS procedures and OSD Supply Policy

for the Unique Item Tracking (UIT) program for Positive 

Inventory Control (PIC) Nuclear Weapon Related Materiel 

(NWRM). Loop ID 0330 (2/LX/1500) documents the 

authorized uses of unique item identifier (UII) and serial 

number. For all other purposes, the IUID information is a 

placeholder for DLMS enhancements pending development 

of DLMS procedures and overarching OSD Supply Policy. 

Refer to the item unique identification (IUID) web at URL: 

http://www.acq.osd.mil/dpap/pdi/uid/ for DoD policy.

Updates introductory 

note to defer to Loop 

ID 0330 for details on 

authorized use of 

serial number and 

UII.
Enclosure 2, PDC 1244

IC Change Tables

Page 26

# Location DLMS 947I Inventory Adjustment 

Revision

Reason

2. DLMS 

Introductory 

Notes on IC 

cover page.

Add ADC 1244 to DLMS Introductory Note 4: 

ADC 1244, Establishing Visibility of Unique Item Tracking 

(UIT) Program Items for Service-Owned Assets Stored at 

DLA Distribution Centers and Corresponding Revisions to 

Inventory Procedures Related to Capital Equipment.

Adds change to IC.

3. All segments 

below

Remove Federal Notes from all segments below and change to 

DLMS Notes where appropriate.

Administrative 

update.

4. 2/W1901/0200 Revise DLMS Note for existing qualifier AA:

AA Physical Count

DLMS Note:

1. Inventory Adjustment (Physical Inventory). Gain or loss 

disclosed as a result of physical count of stock,

single adjustment (DIC D8A or D9A functionality). The use 

of reason code AA for an inventory adjustment gain 

combined with a quantity of 0 (zero) indicates that a physical 

inventory has taken place, and no record adjustment was 

necessary. 

2. For Capital Equipment and UIT Programs, identify all 

serial numbers corresponding to the NSN, Condition Code, 

and Owner from the initial physical inventory request when 

using in combination with quantity of 0 (zero). The use of 

reason code AA in combination with zero quantity indicates 

to the owner the completion of the inventory. See ADC 1244.

Clarifies why an 

inventory 

adjustment gain, for 

Status or 

Adjustment Reason 

Code AA (Physical 

Count), would have 

a quantity of 0 

(zero).

Clarifies the 

requirement to 

provide a complete 

list of serial 

number/UII to the 

owner

5. 2/LX/1500 Add new LX Segment Level Note for UIT as shown, and 

renumber subsequent notes:

DLMS Note:

1. Use the LX segment as a counter to identify the number of 

2/LX/1500 loop iterations in the transaction set.

2. The entire 2/LX/1500 loop (Loop ID 0330) is an authorized 

DLMS enhancement for use to provide item unique identification 

(IUID) data as noted in these segment level notes. below for 

specific implementations; see introductory DLMS note 4e. For 

all other applications, see introductory DLMS note 4a.

3. With the exception of dual inventory adjustments for UII and/or 

serial number mismatch (2/W1901/0200 Code AQ), the 

2/LX/1500 loop is repeated for each item to be uniquely identified 

and provides flexibility to accommodate tracking by UII and serial 

number. 

4. For dual inventory adjustments with a UII and/or serial number 

mismatch (2/W1901/0200 Code AQ), the 2/LX/1500 loop is 

repeated for “from” (original) and “to” (corrected) IUID 

information for a single item. 

5. May use the 2/LX/1500 loop to provide batch/lot number 

information.

Documents UIT 

program 

requirement.
Enclosure 2, PDC 1244

IC Change Tables

Page 27

# Location DLMS 947I Inventory Adjustment 

Revision

Reason

6. Authorized for use under DoD IUID policy for accountability 

and management of capital equipment. Refer to ADC 1198.

7. Under DOD IUID policy, UIT programs require serialization 

data visibility. Authorized for all UIT programs with the 

exception of SA/LW, prepare materiel release confirmation with 

the serial number as mandatory and when available, include the 

UII. For SA/LW refer to the separate program procedures 

pending transition to DLMS logistics transactions. Refer to ADC

1244.

8. The 2/LX/1500 loop is Authorized for Air Force GFP-A. Refer 

to ADC 1230.

9. Except as noted, the entire 2/LX/1500 loop is DLMS 

enhancement see introductory DLMS note 4a.
Enclosure 2, PDC 1244

IC Change Tables

Page 28

6. 2/N9/1600 Revise segment level DLMS Notes:

DLMS Notes: 

1. The 2/N9/1600 segment is an authorized DLMS enhancement

for use in Inventory Adjustment transactions to provide Item 

Unique Identification (IUID) data as noted here below for specific 

implementations; see introductory DLMS note 4e. For all other 

applications, see introductory DLMS note 4a.

2. This segment supports item identification based upon the serial 

number/UII and the serial number. This segment also provides for 

use of a batch/lot number, when applicable. If UII and serial 

number, and/or batch/lot number, are required for the item, enter 

the UII in N901, and enter the serial number and/or batch/lot 

number in N907. If UII is not used, enter the serial number in 

N901and enter the batch/lot number in N907. If only batch/lot 

number is required, enter the batch/lot number in N901.

3. Use multiple iterations of 2/N9/1600 segment within the 

2/LX/1500 loop, to provide identifying information for an item as 

needed. 

 -- When used for a dual adjustment resulting from UII, serial 

number or batch/lot number mismatch, the first iteration of the 

2/LX/1500 loop will contain the "from" (original) IUID or 

Batch/Lot and the second iteration will contain the "to" (corrected) 

IUID or Batch/Lot for the same item.

 -- When used for a dual adjustment resulting from missing UII, 

serial number, or batch/lot number, use multiple iterations of the 

2/LX/1500 loop to identify the missing IUID or Batch/Lot for 

each item. 

4. Capital equipment candidates require serialization data 

visibility. Prepare inventory adjustment transactions for capital 

equipment using the serial number and when available, include the 

UII. Refer to ADC 1198.

5. Under DoD IUID policy, UIT programs require serialization 

data visibility. For all UIT programs with the exception of 

SA/LW, prepare the inventory adjustment transactions with the 

serial number and when available, include the UII. For SA/LW 

refer to the separate program procedures pending transition to 

DLMS logistics transactions. Refer to ADC 1244.

6. Serial number, UII, and batch/lot number are authorized for 

the reporting of Air Force GFP accountability of serially 

tracked assets between the Air Force CICP and Air Force 

APSR systems. Refer to ADC 1230.

7. Use in CAV inventory adjustment (Condition Code) 

transactions to identify part numbers required to complete the 

repair/overhaul action and to provide an estimated receipt date for 

each item.

8. Except as noted, this is a DLMS enhancement. see introductory 

DLMS note 4a. 

Documents UIT 

program 

requirement.
Enclosure 2, PDC 1244

IC Change Tables

Page 29

# Location DLMS 947I Inventory Adjustment 

Revision

Reason

7. 2/N901/1600 Update data element level note as follow:

43 Supporting Document Number

DLMS Note:

1. Must use to perpetuate the document number assigned by the 

materiel owner in the Physical Inventory Request transaction 

when available. Required for capital equipment candidates and 

UIT programs.

2. For Air Force GFP accountability, the CICP must use to 

perpetuate the document number assigned by the Air Force 

program manager in the Physical Inventory Request.

3. Authorized DLMS enhancement for all commodities. See 

ADC 1244.

TN Transaction Reference Number

DLMS Note:

Must use to identify the document number for each transaction., 

except (for DLA only) when the contract

number is provided in 2/CS/0500.

Administrative 

update to clarify 

existing 

requirements. 

EBSO confirmed 

with DLA 

Distribution that the 

contract number is 

not used in the 947I

8. 2/N901/1600 Remove data element level notes for Air Force GFP from BT, SE, 

and U3. The requirement is identified in segment level note:

BT Batch Number

DLMS Note:

1. Use to identify the manufacturer’s batch/lot, or other number 

identifying the production run when UII and or serial number are 

not required. If UII and/or serial number are required in addition 

to the batch/lot number, enter the batch/lot number, enter the 

batch/lot number in N907. The batch/lot number may not exceed 

20 characters in accordance with IUID policy.

2. DLMS enhancement. See introductory DLMS note 4a.

3. Authorized to support Air Force GFP-A. Refer to ADC 

1230. 

SE Serial Number

DLMS Note:

1. Use to identify the serial number when UII is not required. If 

UII is required in addition to the serial number, enter the serial 

number in N907. The serial number may not exceed 30 characters 

and may only include alpha numeric characters, dashes and 

forward slashes. Spaces are not allowed.

2. Except as noted, this is a DLMS enhancement. See introductory 

DLMS note 4a.

3. Authorized to support Air Force GFP-A. Refer to ADC 

1230. 

Administrative 

update removing 

separate data 

element level Air 

Force GFP 

accountability notes 

at each data 

element. This is 

consistent with 

documenting the 

various 

requirements as 

segment level notes, 

rather than repeat at 

each data element in 

the segment.
Enclosure 2, PDC 1244

IC Change Tables

Page 30

# Location DLMS 947I Inventory Adjustment 

Revision

Reason

U3 Unique Supplier Identification Number (USIN)

DLMS Note:

1. Use to identify the UII. The UII may not exceed 50 characters 

in accordance with IUID Policy. An ANSI data maintenance was 

approved in version 5020. The approved code/name is “UIIDepartment of Defense Unique Item Identifier”.

2. Except as noted, this is a DLMS enhancement. See DLMS 

introductory note 4a.

3. Authorized to support Air Force GFP-A. Refer to ADC 

1230. 

9. 2/N907-

01/1600

No change. Provided for context.

BT Batch Number

DLMS Note

Use to identify the manufacturer’s batch/lot, or other number 

identifying the production run when UII or serial number is 

entered in N901 and batch/lot is the only other identifying number 

in 2/N901/1600. The batch/lot number may not exceed 20 

characters in accordance with IUID policy.

SE Serial Number

DLMS Note

Use to identify the serial number when UII is entered in N901. 

The serial number may not exceed 30 characters and may only 

include alpha numeric characters, dashes and forward slashes. 

Spaces are not allowed.

Provided for 

context.
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 1

ENCLOSURE 3 TO ADC 1244

This is a new Chapter added to DLM 4000.25, DLMS, Volume 2. Red, bold italics are not used 

to identify change since the chapter is new in its entirety. 

C30. CHAPTER 30

Procedures for Serially Managed Materiel Requiring 

Owner Visibility

C30.1. GENERAL.

C30.1.1. Purpose. This chapter covers the additional procedures required for 

serially managed materiel requiring owner visibility while physically located at DLA 

Distribution Centers, hereafter referred to as storage activities. See section C30.5. for 

the categories of serially managed materiel covered by this chapter. 

C30.1.1.1. For these procedures, the serial number is mandatory in the 

DLMS transaction, as is the unique item identifier (UII), when available--the intent is to 

capture both serial number and UII. Many legacy items have not been marked with an 

assigned UII; therefore, the UII cannot be considered a mandatory data element until 

transition to management by UII is complete across the Department of Defense.

3

 That 

is the context in which the term “serial number/UII” is used in this chapter.

C30.1.1.2. These procedures require record keeping by both the owner and 

storage activity and the constant transaction exchange at the item instance level (serial 

number/UII) to ensure that the records of both reflect the correct serial numbers/UIIs, by 

storage location, owner, and supply condition code (SCC).

C30.1.2. Transactions. This chapter addresses the following DLMS transactions 

with their functions identified by their beginning segment and transaction type code. 

Transactions identified support the business process, but may not actually be used to 

exchange serial number/UII. The procedures in this chapter require that a system 

transact business interchanges using DLMS transactions, The DLMS Implementation 

Conventions (IC) are available on the Enterprise Business Standards Office Website

www.dla.mil/HQ/InformationOperations/DLMS/elibrary/Transformats/140_997/.

C30.1.2.1. Receipt Transaction is DLMS 527R with beginning segment 

(1/BR02/020) Transaction Type Code D4 – Receipt. 

 

3 The UII is an identifier used to uniquely identity an individual item used within the Department of 

Defense. The UII may be a DoD Recognized IUID equivalent [e.g., Vehicle identification number 

(VIN)] or a composite structure defined by the Department of Defense [refer to UII Construct 1 and UII 

construct 2]. Refer to DoD policy and supporting documentation for specific IUID guidance at 

www.acq.osd.mil/dpap/pdi/uid/index.html. Refer to the most current version of MIL-STD-130 for 

specific guidance marking of U.S. Military property.
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 2

C30.1.2.2. Standard Supply Discrepancy Report is DLMS 842A/W with 

beginning segment (1BNR06/0200) Transaction Type C1 – Claim Information. 

C30.1.2.3. Storage Quality Control Report (SQCR) is DLMS 842S/Q with 

beginning segment (1BNR06/0200) Transaction Type 03 – Report Message. Use 

beginning segment (1/BNR01/0200) Transaction Set Purpose Code to distinguish the 

purpose. 

C30.1.2.4. Physical Inventory Request is DLMS 846P with beginning 

segment (1/BIA02/020) Report Type Code TC – Physical Inventory Request. 

C30.1.2.5. Response to Physical Inventory Request is DLMS 846P with 

beginning segment (1/BIA02/020) Report Type Code DD – Distributor Inventory Report. 

This transaction is only used as a Response to Physical Inventory or follow-up when 

there is no record of stock number or no record of ownership (Management Code R), 

when physical inventory is in workload bank or in process (Management Code S), or 

when responding to follow-up when inventory is already complete (Management Code 

Y). The usual response to a request for inventory is a 947I Inventory Adjustment in 

accordance with Chapter 6.

C30.1.2.6. Transaction History Request Transaction (from owner/manager to 

distribution) is DLMS 846P with beginning segment (1BIA02/020) Report Type Code 

TF – Transaction History Request. 

C30.1.2.7. Response to Transaction History Request Transaction (when no 

history available) is DLMS 846P with beginning segment (1BIA02/020) Report Type 

Code AD – Agent/Distributor Inventory Report. 

C30.1.2.8. End of Day Transaction Count is DLMS 846P with beginning 

segment (1/BIA02/020) Report Type Code B1 – Batch Report. 

C30.1.2.9. Location Reconciliation Request is DLMS 846R with beginning 

segment (1BIA02/020) Report Type Code LC – Location Reconciliation Request. 

C30.1.2.10. Location Reconciliation Notification is DLMS 846R with 

beginning segment (1BIA02/020) Report Type Code X4 – Summary Report. 

C30.1.2.11. Location Reconciliation History Notification is DLMS 846R with 

beginning segment (1BIA02/020) Report Type Code ZZ – Mutually Defined. 

C30.1.2.12. Shipment Status is DLMS 856S with beginning segment 

(1/BSN06/0200) Transaction Type Code AS – Shipment Advice. 

C30.1.2.13. Shipment Status Materiel Returns is DLMS 856R with beginning 

segment (1/BSN06/0200) Transaction Type Code FT – Material Return. For other types 

of materiel returns such as retrograde shipment for return of discrepant/deficient 

materiel or repair outside of the MILSTRIP Returns Program, use Transaction Type 
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 3

Code RD – Returns Detail. Must use the ASC X12 Version 4030 as this version allows 

the UII to be carried in single data field

C30.1.2.14. Acceptance Report is DLMS 861 with beginning segment 

(1/BRA04/020) Receiving Advice or Acceptance Certificate Type Code 9 – Authorized 

Representative in Receipt of an Acceptance Alert.

C30.1.2.15. Materiel Release Confirmation is DLMS 945A with beginning 

segment (1/W0611/0200) Transaction Type Code NJ – Material Release Confirmation. 

Must use the ASC X12 Version 4030 as this version allows the UII to be carried in 

single data field.

C30.1.2.16. Inventory Adjustment is DLMS 947I with beginning segment 

(1/W1505/0200) Transaction Type Code NU – Inventory Adjustment and use of 

2/W1901/0200 Quantity or Status Adjustment Reason Code. Must use ASC X12 

Version 4030 as only this version includes the capability to carry UII.

C30.2. APPLICABILITY AND SCOPE.

C30.2.1. The provisions of this chapter apply to the Military Departments including 

Coast Guard and Defense Agencies (hereafter referred to as the DoD Components).

C30.2.2. This Chapter’s procedures supplement (are additive) the procedures in 

DLM 4000.25, Volume 2, Chapters 4, 5, 6, 7, 11, 13, 14, and 17.

C30.2.3. The procedures in this chapter can only be implemented by Automated 

Information Systems (AIS) that have implemented the DLMS ANSI ASC X12 ICs or the 

equivalent DLMS XML business partner interchange transactions.

C30.3. EXCLUSIONS.

C30.3.1. Classified activities that determine the visibility of specific items may 

compromise operational security must request guidance from their DoD Components.

C30.3.2. DoD Small Arms and Light Weapons (SA/LW) Serialization Program. 

The DOD SA/LW Serialization Program unique item tracking (UIT) program has unique 

transaction requirements and procedures documented in Chapter 18. The SA/LW 

program is also subject to the item unique identification (IUID) transaction requirements, 

which are identified at paragraph C30.13.

C30.3.3. Items that are not assigned a national stock number (NSN) in the 

Federal Logistics Information Systems (FLIS).

C30.3.4.The procedures in this chapter do not directly address update of the IUID 

registry. The procedures for updating the IUID registry are contained in the DoD 

Procurement Toolbox found on the “Unique Identification” link at 

https://dodprocurementtoolbox.com. Wide Area Work Flow (WAWF) eBusiness Suite 
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 4

web based training video tutorials of different aspects of the IUID registry and baseline 

functionality are available at https://wawf.eb.mil (click on “Help/Training”).

C30.4. POLICY.

C30.4.1. DoD Instruction 8320.04, Item Unique Identification (IUID) Standards for 

Tangible Personal Property, dated September 3, 2015 states, “The unique item 

identifier (UII) will be used globally as the common data key in financial, property, 

acquisition, and logistics (including supply and maintenance) automated information 

systems to enable asset accountability, valuation, life-cycle management, and 

counterfeit materiel risk reduction.”

C30.4.2. DoD Components will follow the IUID procedures identified in DODM 

4140.01, Volume 9, “Materiel Programs”, and Volume 11, “Inventory Accountability and 

Special Management and Handing.

C30.4.3. The DoD Integrated Requirements Set (IRS) for IUID in Supply Business 

Processes documents the ODASD(SCI) vision for the integration of IUID at the 

transactional level.

C30.4.4. DOD established overarching guidance for the serial number convention

and only alpha numeric (A-Z, 0-9), dashes, and forward slashes are allowed with a 

maximum field length of 30 characters. Spaces are not allowed. DOD Components 

must ensure future procurement actions require vendors to follow serial number 

convention guidance as applicable. ODASD (SCI) will update appropriate DOD policies 

to reflect these changes followed by the implementation of this change. Consequently, 

EBSO will develop a change to incorporate these changes in all applicable DLMS 

transactions and manuals.

C30.5. CATEGORIES OF SERIALLY MANAGED MATERIEL COVERED BY THIS 

CHAPTER

C30.5.1. DoD Unique Item Tracking Programs. The procedures in this chapter 

apply to items within a DoD level (inter-DoD Component) unique item tracking (UIT) 

program4. 

C30.5.1.1. Unique Item Tracking Designator Codes.

C30.5.1.1.1. The UIT designator code indicates that an item is part of 

an established UIT program. In accordance with DODM 4140.01 policy, the DoD 

Components will not establish any new UIT programs. The FLIS is the authoritative 

source for UIT designator codes.

 

4 This chapter does not apply to the DoD Small Arms and Light Weapons Serialization Program 

(DoDSALWSP) pending implementation of weapon transaction reporting using standard supply logistic 

transactions. The Enterprise Business Standards Office will address DoDSALWSP use of standard 

logistics transactions by a proposed DLMS change.
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 5

C30.5.1.1.2. DoD Components apply the appropriate FLIS UIT 

designator codes to NSNs in existing UIT programs. Table C30.T1. shows authorized 

UIT designator codes. Ensure that the integrated materiel manager (IMM) applies the 

UIT designator code to every NSN comprising the DoD level program, for which a UIT 

designator code is not already assigned. The IMM assigns UIT designator codes to a 

NSN based on direction by the DoD Component UIT central control point. The UIT 

designator code, in conjunction with FLIS IUID Indicator Y, provides the DoD 

Components a systemic means to identify that an NSN is subject to these procedures. 

For system to system updates of the UIT designator code, activities should subscribe to 

the UIT data through the FLIS Portfolio Data Warehouse which is Logistics Information 

Services Master Data Capability. To negotiate this XML Data Exchange/Subscription, 

send an e-mail request to DLISRMDEPMO@dla.mil.

C30.5.1.1.3. Table C30.T1. shows the UIT Designator Codes

Table C30.T1. Unique Item Tracking Designator Codes

Code Explanation 

AAA DoD Small Arms and Light Weapons Serialization Program (DoDSALWSP)

AAB Security Risk Category I Non-Nuclear missiles and Rockets 

AAC Radiation Source Tracking System (RASTS) Program

AAD Navy Depot Level Reparables (NDLR) Program

AAF Aviation Component Tracking Program

AAG Tritium Unique Item Tracking Program

AAH Controlled Cryptographic Items (CCI) 

AAJ Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM)

C30.5.1.2. DoD Small Arms and Light Weapons Serialization Program 

(DoDSALWSP). This chapter identifies DoDSALWSP as a placeholder. The future vision 

is to transition the DoDSALWSP to use of standard logistics transactions under these 

procedures where possible. However due to the existing unique small arms and light 

weapons (SA/LW) procedures and transactions, the Enterprise Business Standards Office, 

working in conjunction with the Joint Small Arms and Light Weapons Coordinating Group, 

will develop a separate proposed DLMS change to address this transition. Accordingly,

these procedures do not apply to DoDSALWSP at this time. Refer to Chapter 18 for 

DoDSALWSP procedures and transactions.

C30.5.1.3. Security Risk Category I Non-Nuclear missiles and Rockets. Items 

subject to Security Risk Category I Non-Nuclear missiles and Rockets UIT program have a 

FLIS IUID Indicator (Y) and FLIS UIT Designator Code AAB.
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 6

C30.5.1.4. Radiation Source Tracking System Program (RASTS)5

C30.5.1.4.1. Radiation Source Tracking System Program (RASTS) is a 

program established to provide regulatory and statutory compliance with Federal, state, 

and local regulations for the use of radioactive materiel in fielded chemical defense 

equipment and in industrial applications. It is designed to provide strict control and 

identification of all radioactive sources to comply with relevant Nuclear Regulatory 

Commission (NRC) license requirements. 

C30.5.1.4.2. Identifying RASTS Items: Items subject to the RASTS UIT 

program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code AAC.

C30.5.1.5. Navy Depot Level Reparable (NDLR) Program 

C30.5.1.5.1. The NDLR UIT program is the recognized inter-DoD 

Component program for select Navy-managed Depot Level Reparables (DLR). 

C30.5.1.5.2. Identifying NDLR UIT Program Items: Items subject to the 

Navy DLR UIT program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code 

AAD.

C30.5.1.5.2. Interim Process for NDLR UIT Program. Navy and DLA 

Distribution previously activated the NDLR UIT program with a limited set of DLMS 

transactions. Navy and DLA Distribution will continue that process as an interim 

process, until they implement Chapter 30 procedures. DLMS will eliminate this interim 

procedure at that time. Navy’s target implementation date to transition to the Chapter 30 

procedures for the NDLR UIT program is [Navy provide target implementation date to 

use here]. 

Staffing Note: Navy provide target implementation date to implement Chapter 30 

procedures for NDLR with DLA Distribution, in response to PDC 1244.

Table C30.T2. Interim Navy Depot Level Reparable Program UIT transactions

Transaction Title

527R Receipt

856S Shipment Status

945A Materiel Release Confirmation/Disposal Release Confirmation

C30.5.1.6. Aviation Component Tracking Program 

C30.5.1.6.1. The Aviation Component Tracking Program is designed to 

ensure unique identification for U.S. Army Aviation equipment flight safety parts and for 

 

5 Radiation Testing and Tracking System (RATTS) was replaced by Radiation Source Tracking System 

(RASTS). NRC licenses 12-00722-13 and 12-00722-14 covering Chemical Detection Equipment 

(CDE) and Tritium are obsolete terminated licenses and are replaced by NRC license 21-32838-01.
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 7

life managed or special interest items. It provides for control, improved accountability, 

and visibility of U.S. Army Aviation equipment. 

C30.5.1.6.2. Identifying Aviation Component Tracking Program UIT Items: 

Items subject to the Aviation Component Tracking Program have a FLIS IUID Indicator 

(Y) and FLIS UIT Designator Code AAF.

C30.5.1.7. Tritium Unique Item Tracking Program 

C30.5.1.7.1. The Tritium UIT Program identifies all primary and secondary 

items comprised of tritium throughout the Army, Army Reserve, National Guard, and 

Marines. This program is necessary to meet an Army requirement for location visibility 

of all tritium sources at all times.

C30.5.1.7.2. Identifying Tritium UIT Program Items: Items subject to the 

Tritium UIT Program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code

AAG. 

C30.5.1.8. Controlled Cryptographic Items (CCI)

C30.5.1.8.1 Controlled Cryptographic Items UIT Program. The CCI UIT 

program was established to meet National Security Agency requirements to maintain 

visibility of controlled cryptographic end items. 

C30.5.1.8.2. Identifying CCI Items: Items subject to the CCI UIT 

program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code AAH.

C30.5.1.9. Positive Inventory Control (PIC) Nuclear Weapon Related Materiel 

(NWRM)

C30.5.1.9.1. Air Force program for providing positive inventory control 

for NWRM.

C30.5.1.9.2. Identifying PIC NWRM Items: Items subject to the PIC 

NWRM UIT program have a FLIS IUID Indicator (Y) and FLIS UIT Designator Code 

AAJ.

C30.5.1.9.3. Air Force Integrated Logistics Solution-Supply (ILS-S) 

(Retail Supply) and Supply Status. Air Force will use Supply Status (DLMS 870S) in Air 

Force ILS-S (Retail Supply), on an intra-Air Force basis to provide the latest status to 

the intended receiving activity, including UII and/or serial number in support of the PIC 

NWRM UIT program. For legacy items where the UII has not been marked in 

accordance with IUID policy, the serial number alone will be passed. The Defense 

Automatic Addressing System (DAAS) will enable transmission of information copies of 

the ILS-S Supply Status to the NWRM PIC Fusion Module to ensure the PIC NWRM 

UIT program has near real time access to UIIs and the associated serial numbers of 

NWRM item movements.
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 8

C30.5.1.9.4. Retail Supply and Transportation Interchange. (See DLM 

4000.25, “Defense Logistics Management Standards Manual,” Volume 3, Chapter 2.) 

For designated supply trading partners (currently limited to the Standard Base Supply 

System (SBSS) – Cargo Movement Operations System (CMOS) interface):.

C30.5.1.9.4.1. Use the DLMS 940R Materiel Release Order

(MRO) to support the PIC NWRM UIT program. Pass UIIs and the associated serial 

number in the MRO for each item meeting the PIC NWRM UIT program criteria. For 

legacy items where the UII has not been marked in accordance with IUID policy, the 

serial number alone will be passed.

C30.5.1.9.4.2. Use an information copy (image) of the DLMS 

940R MRO and DLMS 945A Materiel Release Confirmation in support of Air Force PIC 

Fusion program data requirements. The routing of an additional information only copy 

of the DLMS standard transactions (940R and 945A) is authorized for forwarding PIC 

Fusion data needed for the Air Force UIT registry. This is a specific authorized use with 

unique identifiers to flag the transaction as information only.

Table C30.T3. PIC NWRM Retail Supply and Transportation Interchange

Transaction TITLE

870S6 Supply Status

940R7 Materiel Release (Distribution Code 111) (approved for limited use)

945A8 Materiel Release Advice (Distribution Code 111)

C30.5.1.9.4. Interim Process for PIC NWRM UIT Program. Air Force 

and DLA Distribution previously activated the PIC NWRM UIT program with the limited 

set of DLMS transactions shown in Table C30.T4. Air Force and DLA Distribution will 

continue that process as an interim process, until they implement Chapter 30. DLMS 

will delete this interim procedure at that time. The Air Force target implementation date 

to transition to the Chapter 30 procedures for the PIC NWRM UIT program is [Air Force 

provide target implementation date to use here]. 

Staffing Note: Air Force provide target implementation date to implement Chapter 30 

procedures for PIC NWRM, in response to PDC 1244.

 

6 Refer to ADC 407, Requirements for Unique Item Tracking (UIT) in the DLMS Supply Status (870S) 

Supporting the Cargo Movement Operations System (CMOS) Interface 

(MILSTRIP/Supply/Transportation Interchange)

7 Refer to ADC 316C, Revise DLMS 940R Material Release and DLMS 945A Material Release Advice, to 

Support UIT for Air Force Positive Inventory Control (PIC) under the Retail Transportation and Supply 

Receipt and Acknowledgement Interchange

8

Ibid
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 9

Table C30.T4. Interim PIC NWRM UIT transactions

Transaction TITLE

527R9 Receipt

856S Shipment Status

867I10 Issue 

945A11 Materiel Release Confirmation, Disposal Release Confirmation, and 

MRO Denials

947I12 Inventory Adjustment (only version 4030 can provide the UII)

C30.5.2. Capital Equipment. Capital equipment does not fall under DODM 

4140.01 IUID policy and is addressed separately within the affected Volume 2 

chapters.13

C30.5.3. Other categories of serially managed materiel requiring owner visibility at 

distribution centers may be identified in the future.

C30.6. OBJECTIVES.

C30.6.1. Establish visibility by serial number/UII, from point of entry into the DoD 

logistics systems through disposal, demilitarization, or shipment outside the control of 

the Department of Defense.

C30.6.2. Reestablish serial number/UII visibility over materiel previously shipped 

outside the DoD’s control when it is reintroduced to DoD control.

C30.6.3. Require the use of standard logistics transactions to interface serial 

number/UII reporting between/among owners, the DoD Components, and suppliers. 

The objective is to populate accountability and owner records using standard DLMS 

logistics transactions.

C30.7. ESTABLISH INITIAL VISIBILITY BY SERIAL NUMBER/UII

C30.7.1. Establishing serial number/UII visibility may begin at any point in the 

supply chain. Customarily, “cradle to grave” serial number/UII tracking begins at the 

time of Government acceptance from the supplier/manufacturer.

 

9 Refer to ADC 347, Revise DLMS 527R Receipt, 867I Issue, 945A Materiel Release Advice, and 947I 

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

DLA Distribution Standard System (DSS) has implemented ADC 347.

10 Ibid.

11 Ibid.

12 Ibid.

13 Refer to ADC 1198, Establishing and Maintaining Accountability for Service Owned Capital Equipment 

Stored at DLA Distribution Centers.
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 10

C30.7.2. Alternatively, serial number/UII visibility may begin after items are 

already in the DoD logistics system. Examples are items that meet the criteria and are 

already in the inventory, or returns to inventory at any time after the item was originally 

accepted by the Government.

C30.8. REQUIREMENTS FOR SERIALLY MANAGED MATERIEL REQUIRING 

OWNER VISBILITY AT DLA DISTRIBUTION CENTERS

C30.8.1. General Requirements. The DoD Components will:

C30.8.1.1. Maintain AIS(s) necessary to apply management in accordance 

with DODM 4140.01 IUID requirements. Maintain visibility by serial number/UII, within 

owner, and DoD storage activity AISs to include the custodian’s system of record which 

is the official auditable quantity for an item of inventory.

C30.8.1.2. Use DLMS transactional interfaces among AISs to ensure that 

visibility exists in all AISs at the serial number/UII level.

C30.8.1.3. Apply the appropriate FLIS IUID indicator to NSNs for which they 

have PICA responsibility. The IUID indicator provides the DoD Components a systemic 

means to identify whether an NSN requires tracking by serial number and the UII when 

available. The FLIS IUID indicator currently has two values (Y) indicating that IUID 

marking is required and (N) indicating IUID marking is not required. For system to 

system updates of this data, activities should subscribe to the IUID data through the 

FLIS Portfolio Data Warehouse which is DLA Logistics Information Services Master 

Data Capability. To negotiate this XML Data Exchange/Subscription, send an e-mail 

request to DLISRMDEPMO@dla.mil.

C30.8.1.4. An item’s NSN, in conjunction with the serial number/UII will be 

the means for tracking an item in a logistics AIS. Management is not possible if there is 

no NSN recorded in the FLIS. Item visibility will be by NSN, owner, SCC, serial 

number/UII. DLMS provides flexibility to accommodate tracking by NSN, serial number 

and UII.

C30.8.1.5. Owner visibility tracking by serial number/UII will cease when DLA 

Disposition Services acknowledges receipt of serially managed materiel. DLA 

Disposition Services will validate serial number/UII for serially managed materiel during 

receipt processing and provide an SDR to the turn-in activity for any discrepancies.

C30.8.1.6. Retention of Source Documents and Transaction History. 

Activities may require audit capability for a period of time following the processing of 

documents and transactions for serially managed materiel. Activities will maintain and 

dispose of documents and transaction history records in accordance with DoDI 5015.02, 

DoD Records Management Program.

C30.8.2. Specific Serial Number/UII Requirements. DLMS Transactions will 

always be sent to the owner when the NSN, quantity, ownership code, SCC, or serial 
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 11

number/UII is affected. Except as noted for receipt processing, DLMS transactions will 

always include the serial number.

C30.8.2.1. Requisitioning. Requisitioning will be in accordance with the 

procedures contained in Chapter 4. There is no documented requirement for 

requisitioning of items by serial number/UII. Therefore, serial number/UII procedures 

are not applicable to the requisition, requisition modification, MRO, redistribution order, 

or disposal release order. With the exception of the processes documented in 

paragraph C30.5.1.9. supporting the intra-Air Force use in the NWRM PIC Fusion 

Module UIT Registry, the MRO and supply status transactions will not include serial 

number/UII. 

C30.8.2.2. Due-In and Prepositioned Materiel Receipt (PMR), Activities will 

follow the procedures in Chapter 12 for establishing due-in records and processing

PMRs. Do not include serial number/UII in the PMR.

C30.8.2.3. Shipping Activity Processes 

C30.8.2.3.1. Advance Shipment Notice (From Procurement Source). 

When the procuring DoD Component orders UII items from a vendor, the procuring DoD 

Component must ensure that the applicable clause requiring the vendor to provide IUID 

information in accordance with Defense Federal Acquisition Regulations Supplement 

(DFARS), “Item Unique Identification” clause is included in the contract.14 The 

contractor must submit IUID information to the WAWF e-Business Suite – Invoicing, 

Receipt, Acceptance, and Property Transfer (iRAPT) in accordance with the iRAPT 

Implementation Guides for the 856, Ship Notice/Manifest; 857 Shipment and Billing 

Notice; direct online input; or another comparable information exchange method 

supported by iRAPT. iRAPT will disseminate the vendor shipment information to the 

procuring activity to satisfy the shipment performance notice requirement for the vendor 

to provide notification of shipment to the procuring activity using DLMS 856, Advance 

Shipment Notice (ASN), including UII(s) and serial numbers, or comparable 856 

transaction. DLMS-compliant receiving activities must coordinate with iRAPT for 

dissemination of the vendor shipment information to the receiving system using the 

DLMS 856 ASN, including UII(s) and serial numbers.

C30.8.2.3.2. Shipment Status

C30.8.2.3.2.1. Chapter 5 contains procedures to prepare and 

report the shipment status. The shipping activity will report shipment status with the 

serial numbers/UIIs selected for shipment, to the receiving DoD Component activity. 

The receiving DoD Component will enter the data in its AIS as a due-in and when the 

items are actually received, confirm that the serial numbers/UIIs match the numbers 

reported as shipped by the shipment status transaction. Resolve mismatched serial 

numbers/UIIs following the procedures in Chapters 6, 17, and the additive procedures 

under discrepancy reporting processes below.

 

14 See www.acq.osd.mil/dpap/pdi/uid for specific UID DFARS clause information to include in the contract.
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 12

C30.8.2.3.2.2. DLA Disposition Services Shipment Status. 

C30.8.2.3.2.3. Shipment Status Materiel Returns. Chapter 11 

contains procedures to prepare and report the shipment status materiel returns. 

Shipping activities will provide the serial number/UII in the shipment status material 

returns transactions for materiel being returned.

C30.8.2.3.3. Storage Activity Shipments

C30.8.2.3.3.1 Materiel Release Confirmations. Chapter 4 contains 

the procedures to prepare and report the materiel release confirmation. The storage 

activities will confirm materiel release to the owner and report shipped serial 

numbers/UIIs. Must use the 4030 version of the materiel release confirmation. 

C30.8.2.3.3.2. The AIS supporting the owner will use the materiel 

release confirmation to record which serial numbers/UIIs have been shipped and 

decrement those serial numbers/UIIs from its record as no longer available and in 

storage at that location.

C30.8.2.4. Receiving Storage Activity. Receiving storage activities will 

maintain records of materiel received in its custodial system of record by NSN, owner, 

SCC, serial number/UII and its location.

C30.8.2.4.1. Acceptance Report (Procurement). When acceptance at 

origin is applicable, the shipment status or comparable transactions, forwarded to the 

procuring and receiving activity, will contain accepted IUID information. When 

acceptance at destination is applicable, the receiving system must report acceptance

using the acceptance report, or use direct input to iRAPT. The IUID information will be 

provided in the acceptance report only when partial acceptance occurs, and will include 

those items which were accepted. Responsibility for Government acceptance may also 

be contractually assigned to an alternative organization which may use the acceptance 

report or direct input to iRAPT for acceptance reporting. iRAPT will extract the IUID 

information for all Government accepted IUID items and use to establish the birth record 

in the IUID registry. Additional information and guidance on the IUID registry can be 

found on the UID Website http://www.acq.osd.mil/dpap/pdi/uid.

C30.8.2.4.2. Receipt. Chapter 13 contains procedures to prepare and 

report receipts. Receiving activities will use the receipt transaction to record receipts; 

the receipt transaction will report the serial numbers/UIIs that were actually received. If 

the serial numbers/UIIs did not match the serial numbers/UIIs on the shipment notice, 

then the Components will follow discrepancy reporting procedures below. A missing 

serial number at receipt will stop the item in the supply chain, and must follow the 

discrepancy reporting procedures below. Missing serial number(s) and mismatches on 

serial number/UII will be considered discrepancies.

C30.8.2.4.2.1. Receiving storage activities will maintain locator 

records within their supporting AIS of the location where each serial number/UII is 

stored at that activity.
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 13

C30.8.2.4.2.2. The storage activity will send the receipt 

transaction to the owner and include the serial numbers/UIIs. The owner will record the 

serial numbers/UIIs on the owner record.. The owner will update the IUID registry using 

existing IUID registry procedures.

C30.8.2.5. Supply Discrepancy Reporting (SDR) Processes

C30.8.2.5.1. Serially managed items requiring owner visibility at the 

storage activity, that are received without a serial number will not only require an SDR, 

but will stop the item in the supply chain until a serial number is identified and the 

materiel is marked. If the storage activity cannot determine the serial number using the 

associated shipment notice and marks/labels on the item or packaging, DLA Distribution 

Centers will receipt the materiel without a serial number in a suspended condition and 

submit the SDR under Chapter 17 SDR procedures. The materiel owner is responsible 

for determining the appropriate serial number and providing disposition for marking the 

item. Upon positive resolution of the missing or mismatched serial number/UII scenario, 

separate dual inventory adjustment transactions are required to update the serial 

number/UII and update the SCC of the suspended item to the appropriate SCC.

C30.8.2.5.2. SDRs reporting discrepant receipt will contain the serial 

numbers/UIIs when reporting missing or mismatched serial number/UII data (including 

shortage, overage, mismatch with no quantity discrepancy, condition other than 

expected, and wrong item receipt) as well as when the materiel condition is 

misrepresented or otherwise deviates from the original condition shipped. WebSDR will 

ensure that the owner/manager has visibility of SDRs sent to the shipper. The receiving 

activity will submit an SDR in accordance with Chapter 17 procedures showing the 

appropriate discrepancy code, inclusive of the IUID discrepancy code when reporting

missing or mismatched IUID data. 

C30.8.2.5.3. SDRs reporting non-compliant serial number will be 

reported using Discrepancy Code U14 (Serial number convention invalid). This code is 

distinguished from other similar U-series discrepancy codes in that this code specifically 

informs the owner that a serially managed item was received with an invalid serial 

number convention. The receiving activity must annotate the non-compliant serial 

number in the SDR comments field since the DLMS 842A/W SDR transaction will not 

allow for an invalid serial number convention to be transmitted in the transaction.

C30.8.2.5.4. Reporting and action activities must ensure SDRs follow 

the time standard requirements for submission and response in accordance with 

Chapter 17. Chapter 17, Table C17.T1 provides a decision matrix identifying when an 

SDR is required for UIT program items, based on missing or mismatched IUID data 

during receipt processing.

C30.8.2.6. Physical Inventory Control Processes. The procedures for 

processing and reporting transactions to maintain physical inventory control in Chapter 

6 apply with the following additions:
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 14

C30.8.2.6.1. To increase auditability of physical inventory requests, 

serially managed items will include a unique document number. The document number 

will help relate a physical inventory request with it appropriate response. The owner will 

provide a document number in the Physical Inventory Request. The storage activity will 

perform the necessary physical research as described in Chapter 6 Physical Inventory 

Control. The physical inventory response will carry the same document number 

provided by the owner. These procedures are required for UIT programs and 

recommended for all other commodities.

C30.8.2.6.2. The response to a transaction history request transaction 

(No History Available), and end of day transaction count transaction will not contain UIIs 

or serial numbers. However, when the owner initiates a physical inventory request to 

assist in resolving discrepancies, where the only difference between the owner records 

and the storage activity records is on serial number and/or UII, the request will contain 

Type of Physical Inventory Code B. Owners will initiate a physical inventory due to 

mismatched serial numbers or UIIs when the owner identifies a mismatched condition 

on serial number and/or UII between its records and transactions received.

C30.8.2.6.3. Owner/manager processing a materiel release 

confirmation from a storage activity where the owner does not have a matching record 

of the serial number and/or UII or the owner/manager records have that serial number 

and/or UII located at other than the storage activity reporting the release/issue of the 

item. Either of these conditions may necessitate a complete inventory be taken at all 

storage locations for all owners and supply condition codes.

C30.8.2.6.4. Owner/manager processing receipts, issues, or inventory 

adjustments from storage activities where there is a mismatch on serial number/UII

between the owner records and storage activity transactions reporting which serial 

number and/or UII may at a minimum necessitate an inventory and research to resolve 

the discrepancy.

C30.8.2.6.5. Inventory Adjustments. The inventory adjustment function 

encompasses increases, decreases, or dual adjustments. The C6.4 procedures for 

processing and reporting Inventory Adjustments (Physical Inventory) are applicable with 

the following additions:

C30.8.2.6.5.1. Inventory adjustment (gain, loss, or dual) 

transactions will include the serial number/UII when adding, removing, or correcting a 

serial number/UII.

C30.8.2.6.5.2. When a discrepancy exists solely on mismatched 

serial number and/or UII, the storage activity will transmit a DLMS 947I Inventory 

Adjustment, Inventory Transaction Type Code DU (Inventory Adjustment Dual), 

Quantity or Status Adjustment Reason Code AQ (Inventory Adjustment (UII and/or 

serial number mismatch)) to correct the serial number/UII in question. The storage 

activity will collaborate with the materiel owner(s) to research inventory adjustments due 

to serial number/UII discrepancies resulting in a mismatch (Quantity or Status 
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 15

Adjustment Reason Code AQ) in accordance chapter 6. When the item was previously 

suspended, two inventory adjustment transactions are required to correct the serial 

number/UII, and to update the SCC.

C30.8.2.6.5.3. Items where a discrepancy exists solely on missing 

serial number/UII requires a dual inventory adjustment transaction. The storage activity 

will transmit a DLMS 947I Inventory Adjustment, Inventory Transaction Type Code DU 

(Inventory Adjustment Dual), Quantity or Status Adjustment Reason Code AM (Missing 

Unique Item Identifier (UII)/Serial Number) to add the serial number/UII in question to 

the existing records. The storage activity may add multiple missing serial number/UII 

using a single transaction. When the item was previously suspended, a dual inventory 

adjustment transaction will be required to cite the impacted serial number(s)/UII(s) to 

update the suspended item(s) from the suspended SCC to the appropriate SCC.

C30.8.2.6.5.4. In response to a Physical Inventory Request, the 

storage activity will transmit to the owner a DLMS 947I Inventory Adjustment with zero 

quantity, Quantity or Status Adjustment Reason Code AA (Physical Count) by line item 

indicating the completion of the inventory. Inventory adjustment transactions with 

Quantity or Status Adjustment Reason Code AA and zero quantity must include all 

serial number/UII(s) associated to the NSN, Condition Code, and Owner from the initial 

request. The storage activity will send all gain, loss, or dual adjustment transactions 

prior to sending the final inventory adjustment transaction (Reason Code AA, zero 

quantity) containing all serial numbers/UIIs. The owner will process all inventory 

adjustments prior to processing the final inventory adjustment. 

Staffing Note: DSS transmits inventory adjustment gains and losses and the final 

inventory adjustment sequentially, however DAAS processing time for individual 

transactions may vary. It is not clear at this time whether transactions could exit DAAS 

out of sequence. EBSO is will work with DAAS to determine whether there is an issue 

and identify a potential solution.

C30.8.2.6.5.5. Owner/managers processing location reconciliation 

history transactions resulting from End-of Day processing or an owner initiated location 

reconciliation request where there is a mismatch on serial number/UII between the 

owner records and the transactions received from the storage activity. The history 

transactions will perpetuate the serial numbers/UIIs included in the original transactions.

C30.8.2.7. Location Survey

C30.8.2.7.1. Chapter 6 contains the procedures for location surveys. 

Location survey requires a physical verification, other than actual count, between assets 

and recorded location data to ensure that all assets have their locations accurately

recorded. 

C30.8.2.7.2. Serially managed items requiring owner visibility may be in 

individual storage locations within the storage activity. The storage activity may, for 

items of this nature, include the serial number/UII verification as part of the location 

survey. When the storage activity identifies a discrepancy during the location survey 
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 16

program (Type I or Type II error (see subparagraphs C6.8.1.2.1. and C6.8.1.2.2.)), the 

storage activity will conduct prompt research and assess the need for a special 

inventory Physical Inventory Request Transaction with Type of Physical 

Inventory/Transaction History Code K). 

C30.8.2.8. End-of-Day Reconciliation. Storage activities and materiel owners 

will perform End-of-Day (EOD) reconciliation in accordance with Chapter 6 C6.2.6. End 

of the Day Processing. In addition storage activities and owners will reconcile all 

associated serial numbers/UII to ensure proper accountability of serially-managed 

items. For mismatches between system records, the owner, in collaboration with the 

storage activity, will take the necessary steps to ensure proper research and resolution. 

It is the responsibility of the owner to submit any necessary updates as applicable to the 

IUID Registry.

C30.9. RETAIL SUPPLY AND TRANSPORTATION INTERCHANGE. (See Volume 3, 

Chapter 2). The transportation office will perpetuate the serial numbers/UIIs (when 

available with the associated transportation control number (TCN) in the materiel 

release confirmation (Distribution Code 111). This data content will be used by the 

supply activity to perpetuate this information to the shipment status.

C30.10. MATERIEL RETURNS, REDISTRIBUTION OF ASSETS, DIRECTED 

DISCREPANT/DEFICIENT MATERIEL RETURNS, AND RETROGRADE RETURNS

C30.10.1. Materiel return, redistribution of assets, directed discrepant/deficient 

materiel returns, and retrograde procedures are contained in Chapter 11. The following 

paragraphs identify the additional requirements for total visibility items. 

C30.10.2. Activities shipping returns of any kind or responding to redistribution 

orders will include the serial number/UII in the shipment status materiel return 

transaction.

C30.10.3. Storage activities receiving returns or redistributed items will include the 

serial numbers/UIIs in the receipt transaction. Missing serial number(s) and 

mismatches on serial number/UII will be considered discrepancies. Refer to the SDR 

processing section in this chapter. 

C30.11. REINTRODUCTION OF UNIQUE ITEM IDENTIFIER ITEM PREVIOUSLY 

SHIPPED OUTSIDE THE CONTROL OF THE DEPARTMENT OF DEFENSE. When 

an item previously shipped outside DoD control is reintroduced to DoD control, the 

receiving activity will report the receipt, including serial number/UII, to the owner. If the 

UII is available on the receipt transaction, the owner will update the IUID registry using 

IUID registry procedures.

C30.12. DOD STOCK READINESS PROGRAM. 

C30.12.1. Under the Stock Readiness program, the Department of Defense 

requires uniform care of supplies, including the inspection and reporting of materiel 

condition and serviceability, and the scheduling, controlling, and reporting of packaging 
Enclosure 3, PDC 1244

DLM 4000.25, Volume 2, Chapter 30

Page 17

and other cost reimbursable actions supporting care of supplies in storage (COSIS). 

For serially managed materiel the storage activity will report storage quality issues 

requiring COSIS work to the materiel owner via the storage quality control report

(SQCR), including the serial numbers/UIIs, for approval in accordance with DoD 

Component "Stock Readiness" Policy.

C30.12.2. Missing serial number. Serially managed items requiring owner visibility

that are located in storage without a serial number will stop the equipment in the supply 

chain until a serial number is identified and the materiel is marked. If the 

remarking/relabeling exceeds the dollar threshold for pre-authorized corrective action or 

the storage activity cannot identify the serial number using inventory records and other 

available information, the storage activity will suspend the item in SCC J and prepare an 

SQCR. Cite the applicable discrepancy code and provide clarifying remarks with 

descriptive information for the item. The materiel owner is responsible for determining 

the appropriate serial number and providing disposition for marking the item 
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 1

ENCLOSURE 3 TO ADC 1244

Chapter Updates to Provide Links to Chapter 30 and Additive 

Processing Procedures

Make the following updates to the affected chapters to identity the requirements for total 

visibility items and the additive processing procedures applicable to them are identified in 

Chapter 30.

Volume 2 Supply Standards and Procedures

C4. CHAPTER 4 REQUISITIONING

C4.1. GENERAL 

C4.1.1. This chapter prescribes procedures for the preparation and submission 

of requisitions with specific requisitioning requirements involving Not Mission Capable 

Supply (NMCS), Anticipated NMCS (ANMCS), Pre-Positioned War Reserve Materiel 

Stock (PWRMS), conventional ammunition, subsistence, and GSA non-mailable items. 

This chapter also provides procedures for requisition cancellations, modifications, and 

inquiries.

C4.1.2. In addition, this chapter prescribes the source of supply and storage 

activity processing procedures of the aforementioned transactions including the 

preparation and processing of the materiel release, materiel release advice, and DAAS 

edits associated with requisition processing. 

C4.1.3. Specific requisition requirements involving Government Furnished 

Materiel and Contractor Furnished Materiel are identified in DLM 4000.25 Volume 2, 

Chapter 26.

C4.1.4. There are additional processing procedures over and above those 

contained in this chapter that must be applied for serially managed materiel

requiring owner visibility at DLA Distribution Centers. The identity of the materiel

and the additive procedures are in Chapter 30.

C5. CHAPTER 5 STATUS REPORTING

C5.1. SUPPLY AND SHIPMENT STATUS – GENERAL

C5.1.1.3. Item Unique Identification. Shipment Status for NSNs containing an 

IUID Indicator Yes (Y), indicating that DoD IUID Supply Policy is required, must contain 

the Unique Item Identifier (UII) and/or serial number for each item when available. See 

Section C5.1.3.5 for specific shipment status requirements for IUID.

C5.1.1.4. There are additional processing procedures over and above 

those contained in this chapter that must be applied for serially managed materiel 
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 2

requiring owner visibility at DLA Distribution Centers. The identity of the materiel 

and the additive procedures are in Chapter 30.

C6. CHAPTER 6 PHYSICAL INVENTORY CONTROL

C6.1 GENERAL

C6.1.1. Purpose. 

C6.1.1.1. This chapter provides procedures, performance objectives, and 

reporting requirements for maintaining accurate records of the physical inventory, 

conducting physical inventory counts, and reconciling record variance for materiel within 

the supply system of the Department of Defense.

C6.1.1.2. There are additional processing procedures over and above 

those contained in this chapter that must be applied for items identified as serially 

managed materiel requiring owner visibility at DLA Distribution Centers. The 

identity of the materiel and the additive procedures are in Chapter 30.

[Proceeding text not shown]

C6.2.6.4. Reconciliation of Serially-Managed Items

C6.2.6.4.1. In addition to the responsibilities described under 

paragraph C6.2.6, storage activities and owners/managers will include the 

UII/serial number when reconciling records to ensure proper accountability of 

serially-managed items. For mismatches between system records, the storage 

activity will collaborate with the owner/manager to ensure proper research and 

resolution. 

C6.2.6.4.2. The combination of UII and serial number increases the 

accuracy of inventory records across the DOD. When a serially managed item 

lacks a UII, there is a potential for duplicate serial numbers. A duplicate serial 

number may surface as a result of the record reconciliation. For mismatches due 

to a duplicate serial number, the owner is responsible for taking the necessary 

steps to resolve the discrepancy.

[Proceeding text not shown]

C6.3.6.2. To increase auditability of physical inventory requests, serially 

managed items will include a unique document number. The document number 

will help relate a physical inventory request with the appropriate response. The 

owner will provide a document number in the Physical Inventory Request. The 

storage activity will perform the necessary physical research as described in 

Chapter 6 Physical Inventory Control. The physical inventory response will carry 

the same document number provided by the owner. These procedures are 

required for UIT programs and recommended for all other commodities. For DLA 
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 3

internal controls only, the storage activity may include a second document 

number as necessary in the response to a physical inventory request. 

[Proceeding text not shown]

C6.13.2.4. To increase auditability of physical inventory requests, 

serially managed items will include a unique document number. The document 

number will help relate a physical inventory request with the appropriate 

response. The owner will provide a document number in the Physical Inventory 

Request. The storage activity will perform the necessary physical research as 

described in Chapter 6 Physical Inventory Control. The physical inventory 

response will carry the same document number provided by the owner. These 

procedures are required for UIT programs and recommended for all other 

commodities.

[Proceeding text not shown]

C6.13.4. Location Reconciliation. Reconciliation of Serially-Managed Items

C6.13.4.1. Storage activities will prepare location reconciliation requests by 

line item. For capital equipment candidates, the line item = NSN + SCC + serial number 

+ UII (when available).

C6.13.4.2. In addition to the responsibilities described under paragraph 

C6.2.6, storage activities and owners/managers will include the UII/serial number 

when reconciling records to ensure proper accountability of serially-managed 

items. For mismatches between system records, the storage activity will 

collaborate with the owner/manager to ensure proper research and resolution. 

C6.13.4.3. The combination of UII and serial number increases the 

accuracy of inventory records across the DOD. When a serially managed item 

lacks a UII, there is a potential for duplicate serial numbers. A duplicate serial 

number may surface as a result of the record reconciliation. For mismatches due 

to a duplicate serial number, the owner is responsible for taking the necessary 

steps to resolve the discrepancy.

[Proceeding text not shown]

C6.13.5. Inventory Adjustments under Capital Equipment Candidates Inventory 

Adjustments. The inventory adjustment function encompasses increases, decreases, or 

dual adjustments. The C6.4 procedures for processing and reporting of Inventory 

Adjustments (Physical Inventory) are applicable also apply to apply to Inventory 

Adjustments (UII and/or Serial Number Mismatch) with the following additions:

C6.13.5.1. Capital equipment candidate items inventory adjustment (gain, 

loss, or dual adjustment) transactions will include the serial number/UII (and UII if 

available). Adjustments due solely to the need to when adding, removing, or 

correcting a serial number/UII and/or UIIs will always be for a quantity of 1.
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 4

C6.13.5.2. Capital equipment candidate items wherewhen a discrepancy 

exists solely on mismatched serial number and/or UII, the storage activity will 

transmit a DLMS 947I Inventory Adjustment, Inventory Transaction Type Code DU 

(Inventory Adjustment Dual), Quantity or Status Adjustment Reason Code AQ 

(Inventory Adjustment (UII and/or serial number mismatch)) to correct the serial 

number/UII in question. The storage activity will collaborate with the materiel 

owner(s) to research inventory adjustments due to serial number/UII 

discrepancies resulting in a mismatch (Quantity or Status Adjustment Reason 

Code AQ).will include Quantity or Status Adjustment Reason Code AQ (Inventory 

Adjustment (UII and/or serial number mismatch)) in the inventory adjustment 

transaction, Chapter 7, Table C7.T1 contains the quantity or status adjustment reason 

codes. Two inventory adjustment transactions are required to correct the mandatory 

serial number/UII and, when available, the associated UII, and to update the SCC.

C6.13.5.2.1. The storage activity will prepare a separate dual inventory 

adjustment transaction for each item to identify the original “from” and corrected “to” 

IUID values. Only one item will be identified in each dual inventory adjustment.

C6.13.5.2.2. A dual inventory adjustment transaction will be required to 

cite the impacted serial number(s)/UII(s) to update the suspended item(s) from the 

suspended SCC to the appropriate SCC.

C6.13.5.3. Capital equipment candidate items where a discrepancy exists 

solely on missing serial number/UII and/or UII requires a dual inventory adjustment 

transaction. will include The storage activity will transmit a DLMS 947I Inventory 

Adjustment, Inventory Transaction Type Code DU (Inventory Adjustment Dual), 

Quantity or Status Adjustment Reason Code AM (Inventory Adjustment (UII and/or serial 

number missing)) (Missing Unique Item Identifier (UII)/Serial Number) to add the 

serial number/UII in question to the existing records. The storage activity may 

add multiple missing serial number/UII for the same item using a single 

transaction. The storage activity response will contain all related serial 

numbers/UIIs.in the inventory adjustment transaction, Chapter 7, Table C7.T1 contains 

the quantity or status adjustment reason codes. Two inventory adjustment transactions 

are required to identify the mandatory serial number and, when available, the associated 

UII, and to update the SCC.

C6.13.5.3.1. The storage activity will prepare a dual inventory 

adjustment transaction to identify missing IUID values for each applicable item. Multiple 

items may be identified in each dual inventory adjustment transaction.

C6.15.5.3.2. A dual inventory adjustment transaction will be required to 

cite the impacted serial number(s)/UII(s) to update the suspended item(s) from the 

suspended SCC to the appropriate SCC.

C6.13.5.4. In response to a Physical Inventory Request, the storage 

activity will transmit to the owner a DLMS 947I Inventory Adjustment with zero 

quantity, Quantity or Status Adjustment Reason Code AA (Physical Count) by line 
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 5

item indicating the completion of the inventory. Inventory adjustment 

transactions with Quantity or Status Adjustment Reason Code AA and zero 

quantity must include all serial number/UII(s) associated to the NSN, Condition 

Code, and Owner from the initial request. The storage activity will send all gain, 

loss, or dual adjustment transactions prior to sending the final inventory 

adjustment transaction (Reason Code AA, zero quantity) containing all serial 

numbers/UIIs. The owner will process all inventory adjustments prior to 

processing the final inventory adjustment. 

Staffing Note: DSS transmits inventory adjustment gains and losses and the final 

inventory adjustment sequentially, however DAAS processing time for individual 

transactions may vary. It is not clear at this time whether transactions could exit DAAS 

out of sequence. EBSO is will work with DAAS to determine whether there is an issue 

and identify a potential solution.). 

C6.13.5.5. Owner/managers processing location reconciliation history 

transactions resulting from End-of Day processing or an owner initiated location 

reconciliation request where there is a mismatch on serial number/UII between 

the owner records and the transactions received from the storage activity. The 

history transactions will perpetuate the serial numbers/UIIs included in the 

original transactions.

C7. CHAPTER 7 INVENTORY ADJUSTMENTS

C7.1. GENERAL

C7.1.1. Purpose

C7.1.1.1. Adjustment/Change Procedures. This chapter provides procedures 

relating to the following types of adjustment and change actions:

C7.1.1.1.1. Adjustments caused by catalog change actions.

C7.1.1.1.2. Reidentification of improperly identified materiel.

C7.1.1.1.3. Offsetting adjustments to purpose and condition codes.

C7.1.1.1.4. Discrepancies disclosed by physical inventory.

C7.1.1.1.5. Ownership gains and losses applicable to the Single 

Manager for Conventional Ammunition (SMCA).

C7.1.1.2. This chapter also provides procedures relating to the Asset 

Reclassification transaction.

C7.1.1.3. There are additional processing procedures over and above 

those contained in this chapter that must be applied for items identified as
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 6

serially managed materiel requiring owner visibility at DLA Distribution Centers. 

The identity of the materiel and the additive procedures are in Chapter 30.

C11. CHAPTER 11 MATERIEL RETURNS, REDISTRIBUTION OF ASSETS, 

DIRECTED DISCREPANT/DEFICIENT MATERIEL RETURNS AND RETROGRADE 

RETURNS

C11.1. GENERAL

C11.1.1. Purpose. This chapter provides procedures for the interchange of 

information between the owning organization and the integrated materiel manager 

(IMM) on the reporting and distribution of assets. This chapter provides procedures for 

inventory control point (ICP)/IMM directed lateral redistribution of retail assets identified 

by an inter- or intra-Component retail asset visibility system. In addition, this chapter 

provides special procedures for returns to DLA from selected sites in support of base 

realignment and closure (BRAC) retail supply, storage and distribution (SS&D)/inventory 

management and stock positioning (IMSP) and national inventory management strategy 

(NIMS). These procedures also establish the necessary controls to ensure timely 

processing of related transactions and provide for the automatic return of materiel under 

specified conditions.

C11.1.1.2. There are additional processing procedures over and above those 

contained in this chapter that must be applied for items identified as serially 

managed materiel requiring owner visibility at DLA Distribution Centers. The 

identity of the materiel and the additive procedures are in Chapter 30.

C13. CHAPTER 13 MATERIEL RECEIPT

C13.1. GENERAL

C13.1.1. Purpose. This chapter prescribes standard procedures for processing 

materiel receipt information between and storage activities and between losing 

inventory managers (LIM) and gaining inventory managers (GIM). The procedures 

require expeditious showing of assets in the property accountability records and related 

financial accounts. Documentation covering consignment of materiel to storage 

activities is prescribed in other DoD and DoD Component regulations. These 

documents are used, together with information developed by inspection and 

classification procedures, as source data for documenting transactions in terms of this 

manual. The distribution of disbursement, procurement, and transportation 

documentation by storage activities is also governed by existing regulations and is, 

therefore, not a consideration here.

C13.1.2. There are additional processing procedures over and above those 

contained in this chapter that must be applied for items identified as serially 

managed materiel requiring owner visibility at DLA Distribution Centers. The 

identity of the materiel and the additive procedures are in Chapter 30.
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 7

C17. CHAPTER 7 SUPPLY DISCREPANCY REPORTING

C17.1 GENERAL

C17.1.1. Purpose 

C17.1.1.1. This chapter establishes information requirements for reporting 

and processing of discrepancy reports under the supply discrepancy report (SDR) 

Program. The SDR is a tool used to report shipping or packaging discrepancies 

attributable to the responsibility of the shipper, (including U.S. Government sources and 

contractors/manufacturers/vendors) and to provide appropriate responses and 

resolution, including financial action when appropriate. The purpose of the SDR 

exchange is to determine the cause of such discrepancies, effect corrective action, and 

prevent recurrence.

C17.1.1.2. There are additional processing procedures that must be 

applied for items identified as serially managed materiel requiring owner visibility 

at DLA Distribution Centers. Refer to Chapter 30 for overview. See paragraph 

C17.3.8. for detailed SDR procedures.

(Intervening text not shown)

C17.3.8. Discrepancies in Item Unique Identification (IUID) Data.

15

 

C17.3.8.1. Report supply-related discrepancies involving IUID under DoD 

IUID Supply policy, including but not limited to Unique Item Tracking (UIT) programs, 

capital equipment candidates, or as contractually required. SDRs identifying 

discrepancies in unique identification will be prepared citing both UII and/or 

corresponding serial number, when both are available. Until UII is implemented as 

the primary identifier under full IUID implementation across the Department of 

Defense, the human readable serial number is mandatory in the SDR for 

discrepancy scenarios identified in this chapter, as is the UII when available. The 

intent is to capture both serial number and UII, however not all items are marked 

and the UII cannot be considered a mandatory element at this time. That is the 

context in which the term “serial number/UII” is used in this chapter. Applicability 

under DoD IUID Supply Policy is identified by NSNs with IUID Indicator Yes (Y). For 

missing or mismatched unique item identification of items that are DoD seriallymanaged/tracked, use the applicable U-series discrepancy code (see Table C17.T1.). 

Report missing or mismatched materiel identification unrelated to IUID (e.g. missing or 

mismatched part number or NSN) using the applicable packaging (labeling/marking), 

documentation, technical data, or wrong item discrepancy code(s). Report qualityrelated deficiencies involving IUID, (e.g., improperly constructed unique item identifier 

within the 2D data matrix), using Product Quality Deficiency Report (PQDR) procedures 

under DLA Regulation 4155.24, et al.

 

15 Refer to ADC 1030.
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 8

C17.3.8.2. In order to facilitate reporting of discrepancies, particularly those 

involving discrepancies where inclusion of the serial number/UII IUID information is 

required/desirable, the SDR submission process should be integrated with the receiving 

process, allowing receipt data to be captured once and reused. IUID discrepancies may 

be related to the packaging label, including automated information technology (AIT) 

readable content; the item marking, including AIT readable marks; supply 

documentation; the due-in record; and/or a mismatch between the item and any of 

these. When reporting an IUID missing or mismatch (including shortage, overage, and 

incorrect item) the serial number/UII IUID content may be specifically identified as 

applicable to items received or not received using the IUID Received/Not Received 

Indicator. If the SDR does not include the indicator, the UII and/or serial number will be 

interpreted as applicable to the materiel received. Pending integrated capability to 

support IUID reporting in SDRs, the submitter should include remarks text to clarify the 

specific mismatched data. Additionally, attachment files may be uploaded/transmitted 

to DoD WebSDR to identify UIIs and/or serial numbers/UIIs.

16

 

C17.3.8.3. Discrepancies involving missing or mismatched unique 

identification identified during receipt of new procurement materiel (including direct 

vendor delivery (DVD)) must be reported prior to acceptance. Receipt new 

procurement materiel requiring IUID or serial number tracking in a suspended condition 

pending resolution. 

C17.3.8.4. Pending full transition to DoD IUID Supply Policy procedures, 

only report Mmissing serial number/UII IUID content in DLMS shipment status

transactions (Discrepancy Code U04) will not be reported for stock shipments pending 

full transition to DoD IUID Supply Policy procedures except as applicable to for

shipment of UIT program items and capital equipment candidates originating at DLA 

Distribution Centers.

C17.3.8.5. The materiel owner is responsible for IUID Registry updates 

associated with discrepancies for mismatched IUID information.

C17.3.8.6. In support of Financial Improvement and Audit Readiness (FIAR) 

compliance for accountability and management of capital equipment, capital equipment 

candidates require serialization data visibility.17 The materiel owner also requires

serialization data visibility for UIT program items at DLA Distribution Centers.

18

 

Thus, capital equipment candidates and UIT program items received at DLA 

Distribution Centers without a serial number will not only require an SDR, but will stop 

the equipment in the supply chain until a serial number is identified and the materiel is 

marked. For redistribution/returns, DLA Distribution Centers will receipt capital 

equipment candidates without a serial number in SCC K and submit the SDR. Cite the 

applicable discrepancy code and provide clarifying remarks with descriptive information 

for the item received. If the distribution center cannot determine the serial number 

 

16 Discrete data entries (rather than attachment files) for serial number/UII identification are 

required under PDC 1244 beginning December 2018. 

17 Refer to ADC 1198/ADC 1198A

18 Refer to PDC 1244.
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 9

using the associated shipment notice and marks/labels on the item or packaging, 

the distribution center will report the receipt in a suspended condition) and 

submit the SDR to the owner citing the Discrepancy Code U13 and other 

applicable discrepancy code(s) with clarifying remarks. The materiel owner is 

responsible for determining the appropriate serial number and providing disposition for 

marking the item. SDR Reply Codes 603 (remark and return to stock) and 611 

(Reidentify unique identification (UII/serial number) and return to stock) apply. Upon 

positive resolution of the missing or mismatched serial number/UII scenario, separate 

dual inventory adjustment transactions are required to update the serial number/UII and 

update the SCC of the suspended item to the appropriate SCC.

C17.3.8.7. SDRs prepared for a mismatch with no discrepancy in quantity or 

stock number received should will include the UII and/or serial number/UII identifying 

the mismatch. That is, identify the UII and/or serial number/UII for item(s) received that 

do not correspond to the shipment status, as well as the UII and/or serial number/UII for 

the expected item(s) NOT received. Serial number is mandatory for capital 

equipment candidates and UIT program items. Cite the IUID discrepancy code.

C17.3.8.8. SDRs prepared for a shortage of items identified by IUID Indicator 

Y should will include the UII and/or serial number/UII for the item(s) NOT received 

based upon comparison with the shipment status (when available) or shipping 

documentation. Serial number is mandatory for capital equipment candidates

and UIT program items. Cite the applicable discrepancy code for the shortage and the 

IUID discrepancy code.

C17.3.8.9. SDRs prepared for an overage of items identified by IUID 

Indicator Y should will include the UII and/or serial number/UII for the extra item(s) 

received based upon comparison with the shipment status (when available) or

shipping documentation. Serial number is mandatory for capital equipment

candidates and UIT program items. Cite the applicable discrepancy code for the 

overage and the IUID discrepancy code.

C17.3.8.10. SDRs prepared for receipt of an incorrect item where the item 

received is identified by an NSN with a IUID Indicator Y should will include the UII 

and/or serial number/UII for the wrong item. Serial number is mandatory for capital 

equipment candidates and UIT program items. Cite the applicable discrepancy code 

for the incorrect item receipt and the IUID discrepancy code

C17.3.8.11. SDRs prepared for receipt of a condition discrepancy (i.e., 

the materiel condition is misrepresented or otherwise deviates from the original 

condition on the shipping document or the prepositioned materiel receipt) where 

the item received is a capital equipment candidate or UIT program item will

include the serial number/UII for the discrepant item. Serial number is mandatory 

for capital equipment candidates and UIT program items. Cite the applicable 

discrepancy code for the condition discrepancy and the IUID discrepancy code.
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 10

C17.3.8.12. SDRs reporting non-compliant serial number will be 

reported using Discrepancy Code U14 (Serial number convention invalid). This 

code is distinguished from other similar U-series discrepancy codes in that this 

code specifically informs the owner that a serially managed item was received 

with an invalid serial number convention – the serial number maximum field 

length may not exceed 30 characters and may only include alpha numeric (A-Z, 

0-9), dashes and forward slashes. Spaces are not allowed. The receiving activity 

must annotate the non-compliant serial number in the SDR comments field since 

the DLMS 842A/W SDR transaction will not allow for an invalid serial number 

convention to be transmitted in the transaction.

C17.3.8.13. Table C17.T1 provides a decision matrix for the principal 

scenarios when an SDR is required based on missing or mismatched IUID data during 

receipt processing. Current guidance requires UIT and capital equipment candidate 

discrepancy reporting based upon missing or mismatched serial numbers (rather than 

UII) pending full implementation of IUID requirements, UII will be included when 

available.

Table C17.T1. SDR Decision Matrix: Discrepant IUID Data

Procurement 

Source

(IUID 

contractually 

required)

Approved 

UIT

Capital 

Equipment 

Candidate 

(DLA 

Distribution

Receipt) 4

Wrong 

Item 

Received 

w/IUID 

Indicator 

Y

Missing 

IUID 

(item or 

packaging)

Mismatch 

IUID with 

shortage/ 

overage

Mismatch 

IUID no 

shortage/ 

overage

Create 

SDR

SDR 

Action 

Code

Y Y/N Y/N N N Y N Y 1A or 2A

Y Y/N Y/N N N N Y Y 1A

Y Y/N Y/N N Y N N Y 1A

Y Y/N Y/N N N N Y Y 1A

Y Y/N Y/N N Y N N Y 1A

Y/N Y/N Y/N Y Y/N Y/N Y/N Y 1A or 2A

N N N N N N Y Y 3B

N N N N N Y N Y 1A or 2A

N N N N Y N N N No SDR

N Y N N N N Y Y 1A

N Y N N N Y N Y 1A or 2A

N Y N N Y N N Y 1A 

N N Y N N N Y Y 1A

N N Y N N Y N Y 1A

N N Y N Y N N Y 1A

C17.3.8.14. Table C17.T.2 identifies selected discrepancy scenarios for 

UIT program items that DoD WebSDR will edit for missing serial number on the 

SDR submission. Rejection criteria is for specific discrepancy codes as shown 
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 11

and is applicable regardless of originator or action activity. This does not 

preclude the inclusion of serial numbers for other discrepancies involving UIT

program items.19

Table C17.T.2. UIT Program Mandatory Serial Number by Discrepancy Code

Discrepant Condition

C1 Quantity received less than quantity indicated on supply documentation

C2 Expired shelf life item

C3 Damaged U.S. Postal Service shipment 

C4 Materiel received stripped of parts or components (cannibalized) 

(applicable to materiel returns or repairs only)

C5 Incomplete item received. Do not use for incomplete sets/kits/outfits 

H1 Hazardous item in a condition other than shown on supply document or on 

the supporting inspection/test certificate

H5 Expired hazardous shelf life item

Shortage

S1 Quantity received less than quantity indicated on supply documentation

S2 Quantity received is less than quantity requested minus variance (other 

than unit of issue or unit of pack)

S8 Concealed shortage discovered upon opening a sealed vendor's pack 

Overage

O1 Quantity received is more than quantity shown on the supply document

O2 Quantity received is more than quantity requested plus variance, if 

applicable (other than unit of issue or unit of pack)

O5 Concealed overage discovered in a sealed shipping container

IUID Mismatch

U07 Mismatch between unique identification (UII/serial number) on item and 

label

U08 Mismatch between unique identification (UII/serial number) on item or 

packaging marks/labels and the associated shipping documentation

U09 Mismatch between unique identification (UII/serial number) on item or 

packaging marks/labels and the associated due-in/shipping notice

 

19 Refer to PDC 1244
Enclosure 3, ADC 1244

DLM 4000.25, Volume 2, Various Chapter Updates to link to chapter 30

Page 12

(Intervening text not shown)

C17.3.20. Defense Automatic Addressing System (DAAS) SDR Processing

(Intervening text not shown)

C17.3.20.1.2. Edit SDR transactions in accordance with business rules 

specified below. Additionally, DoD WebSDR will edit SDRs to improve data consistency 

and the appropriateness of data content as follows:

(Intervening text not shown)

C17.3.20.1.2.8. Edit new submission SDRs (transactions and 

direct input) to ensure the requirement for mandatory inclusion of serial number 

for UIT program items is met. Reject SDRs identifying a discrepant condition, 

shortage, overage, or IUID data mismatch with no identified serial number using 

Reply Code 946. Refer to Table C17.T.2 for applicable discrepancy codes.

C17.3.20.1.2.9. Edit new submission SDRs (transactions and 

direct input) to enforce the serial number convention that the serial number 

maximum field length may not exceed 30 characters and may only include alpha 

numeric (A-Z, 0-9), dashes and forward slashes. Spaces are not allowed. Reject 

SDRs with serial numbers not meeting this convention using new Reply Code 947 

(Transaction Rejected. Invalid serial number length or convention. 

DLMS VOLUME 1, APPENDIX 3 ACRONYMS AND APPREVIATIOS

Update the Acronyms list as shown

RATTSRASTS Radiation Source Testing and Tracking System
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 1

ENCLOSURE 4 TO ADC 1244

Delete Chapter 19 (as revised by ADC 1253) in its entirety, and reserve the chapter. 

Changes are identified by bold, red, italics; deletions are identified by double strikethrough.

C19. CHAPTER 19

RESERVED

UNIQUE ITEM TRACKING

C19.1. SCOPE. 

C19.1.1. The provisions of this chapter apply to the Military Departments including Coast 

Guard and Defense Agencies (hereafter referred to as the DoD Components) responsible for 

unique item tracking (UIT). 

C19.1.2. This chapter addresses the existing DoD level (inter-DoD Component) UIT 

programs identified in paragraphs C19.25 and C19.26. In accordance with DODM 4140.01, 

“DoD Supply Chain Materiel Management Procedures, Volume 9, Materiel Programs,” no new 

UIT programs will be established.

C19.1.3. This chapter covers procedures to report, populate, update, and reconcile UIT 

items as required by existing UIT programs, in the DoD Component systems related to or 

impacted by those programs.

C19.2. EXCLUSIONS

C19.2.1. Classified activities that determine the visibility of specific UIT items may 

compromise operational security will request guidance from their DoD Components.

C19.2.2. DoD Small Arms and Light Weapons (SA/LW) Serialization Program. The DOD 

SA/LW Serialization UIT program has unique transaction requirements and procedures 

documented in Chapter 18. The SA/LW program is subject to the Item Unique Identification 

(IUID) transaction requirements, which are identified in paragraph C19.25.4. SA/LW must also 

meet the requirements described in this chapter for assignment of a UIT designator code, 

assignment of the IUID Indicator Y (yes), and transition from uniquely identifying items by serial 

number to the use of unique item identifier (UII) as required by DOD policy.

C19.3. POLICY. In accordance with DODM 4140.01 policy:

C19.3.1. No new UIT programs will be established.

C19.3.2. DoD Components will transition from uniquely identifying UIT items by serial 

number, to the use of UII.
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 2

C19.3.3. DoD Components will review existing UIT programs for possible transition to 

IUID Registry functionality.

C19.4. OBJECTIVES

C19.4.1. Establish visibility over UIT items from their point of entry into the DoD logistics 

systems through disposal, demilitarization, or shipment outside the control of the Department of 

Defense, as required by existing UIT programs.

C19.4.2. Reestablish visibility over a UIT item previously shipped outside the Department 

of Defense’s control when it is reintroduced to DoD control.

C19.4.3. Require the use of standard logistics transactions to interface UIT reporting 

between/among owners, the DoD Components, and suppliers. The objective is to populate 

accountability and, if required, visibility records using standard DLMS logistics transactions. 

These procedures do not dictate whether the DoD Component systems accomplish UIT through 

an integrated automated information system (AIS) accommodating UIT data or through use of 

stand-alone UIT data registries.

C19.5. SAFEGUARDING AND PHYSICAL SECURITY OF UNIQUE ITEM TRACKING DATA 

RECORDS

C19.5.1. Secure AIS records as required by DoDM 5200.01, Volume 1, “DoD Information 

Security Program: Overview, Classification, and Declassification,” February 24, 2012.

C19.5.2. Safeguarding AIS UIT recorded data does not relieve units and activities from 

the DoD Component requirements for physical, electronic, and procedural security of items 

subject to UIT.

C19.6. VISIBILITY OF UNIQUE ITEM TRACKING ITEMS. Establishing visibility of items 

comprising a UIT program (hereafter referred to as UIT items) may begin at any point in the 

supply chain. Customarily, for “cradle to grave” UIT programs, initial tracking begins at time of 

shipment from the supplier/manufacturer. Alternatively, a UIT program may begin after UIT 

items are already in the DoD logistics system.

C19.7. RESPONSIBILITIES FOR UNIQUE ITEM TRACKING. The DoD Components will

C19.7.1. not establish new UIT programs,

C19.7.2. maintain AIS necessary to track UIT items for which the owner has or had 

accountability/visibility, 

C19.7.3. apply the appropriate Federal Logistics Information System (FLIS) UIT 

designator codes to national item identification numbers (NIINs) in existing UIT programs. Refer 

to C19.27, Table C19.T5. for authorized UIT designator codes. Ensure that the integrated 

materiel manager (IMM) applies the UIT designator code to every NIIN comprising the DoD 

level program, for which a UIT designator code is not already assigned. The IMM assigns UIT 

designator codes to a NIIN based on direction by the DoD Component UIT central control point. 

The UIT designator code provides the DoD Components a systemic means to identify that a 

NIIN is subject to UIT and subject to these procedures. For system to system updates of this 

data, activities should subscribe to the UIT data through the FLIS Portfolio Data Warehouse 
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 3

which is Logistics Information Services Master Data Capability. To negotiate this XML Data 

Exchange/Subscription, send an e-mail request to DLISRMDEPMO@dla.mil.

C19.7.4. include an IUID Indicator value Y (yes ) in the FLIS field “IUID Indicator”, for UIT 

items with a national stock number (NSN) assigned. The IUID yes/no indicator provides DoDwide visibility of IUID applicability for NSN items. The IUID Indicator is available through the 

Logistics Information Services Master Data Capability.

C19.8. NATIONAL STOCK NUMBERS, UNIQUE ITEM IDENTIFIERS, AND SERIAL 

NUMBERS. If known, an item’s national stock number (NSN), in conjunction with the UII and/or 

serial number, will be the preferred means for tracking an item in logistics AIS.20 If there is no 

NSN, the owner(s) or an accountable officer will assign a local control number (LCN) until a 

valid management control number (MCN) or NSN can be obtained. DLMS provides flexibility to 

accommodate tracking by NSN and UII, or by NSN and serial number, until such time as IUID 

policy and use of UIIs is fully implemented. UIT by NSN and serial number is a transitional 

requirement until the Components fully implement the IUID concept for serially managed assets, 

and tracking by UII, across the Department of Defense. Pending DoD-wide implementation of 

IUID, AIS should pass both the UII and serial number in logistics transactions when both are 

available. 

C19.9. VISIBILITY OF ITEMS. Visibility tracking will cease when UIT items are shipped outside 

the control of the Department of Defense, or when demilitarization and/or disposal are 

confirmed. Historical UIT transactions will be retained in an inactive file accessible through an 

automated means.

C19.10. RETENTION OF SOURCE DOCUMENTS AND TRANSACTION HISTORY. Activities 

will maintain and dispose of documents and transaction history records in accordance with the 

National Archives and Records Administration (NARA) General Records Schedule (GRS) or the 

NARA-approved Component Records Disposition Schedule. These are the only approved 

sources for implementing disposition of DoD Component records.

C19.11. DUE-IN AND PREPOSITIONED MATERIEL RECEIPT INFORMATION. Establish 

due-in records in accordance with due-in procedures in Chapter 12. Upon establishing a due-in, 

provide a DLMS 527D Prepositioned Materiel Receipt (PMR) transaction to each intended 

storage activity in accordance with the PMR procedures in Chapter 12. Do not include UIIs 

and/or serial numbers in the PMR transaction.

C19.12. ADVANCE SHIPMENT NOTICE. When the procuring DoD Component orders UIT 

items from a vendor, the procuring DoD Component must ensure that the applicable clause 

requiring the vendor to provide IUID information in accordance with Defense Federal Acquisition 

Regulations Supplement (DFARS), “Item Unique Identification” clause is included in the 

contract.21 The contractor must submit IUID information to the Wide Area Workflow e-Business 

Suite – Invoicing, Receipt, Acceptance, and Property Transfer (iRAPT) in accordance with the 

iRAPT Implementation Guides for the 856, Ship Notice/Manifest; 857 Shipment and Billing 

 

20 The UII is an identifier used to uniquely identity an individual item used within the DoD. The UII may be a DoD 

Recognized IUID equivalent [e.g., Vehicle identification number (VIN)] or a composite structure defined by the 

Department of Defense [refer to UII Construct 1 and UII construct 2]. Refer to DoD policy and supporting 

documentation for specific IUID guidance at www.acq.osd.mil/dpap/pdi/uid/index.html. Refer to the most 

current version of MIL-STD-130 for specific guidance marking of U.S. Military property.

21 See www.acq.osd.mil/dpap/pdi/uid for specific UID DFARS clause information to include in the contract.
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 4

Notice; direct online input; or another comparable information exchange method supported by 

iRAPT . iRAPT will disseminate the vendor shipment information to the procuring activity to 

satisfy the shipment performance notice requirement for the vendor to provide notification of 

shipment to the procuring activity using DLMS 856, Advance Shipment Notice (ASN), including 

UII(s), or comparable 856 transaction. DLMS-compliant receiving activities must coordinate 

with iRAPT for dissemination of the vendor shipment information to the receiving system using 

the DLMS 856 ASN, including UII(s). 

C19.13. AIR FORCE INTEGRATED LOGISTICS SOLUTION-SUPPLY RETAIL STATUS. Air 

Force Integrated Logistics Solution-Supply (ILS-S) (Retail Supply) Supply Status (DLMS 870S) 

will be used on an intra-Air Force basis to provide the latest status to the intended receiving 

activity, including UII and/or serial number in support of UIT for positive inventory control (PIC) 

nuclear weapon related materiel (NWRM). For legacy items where the UII has not been marked 

in accordance with IUID policy, the serial number alone will be passed. The Defense Automatic 

Addressing System (DAAS) will enable transmission of information copies of the ILS-S Supply 

Status to the NWRM PIC Fusion Module UIT Registry to ensure the PIC NWRM program has 

near real time access to UIIs and the associated serial numbers of NWRM item movements.

C19.14. ACCEPTANCE REPORT. When acceptance at origin is applicable, the DLMS 856 or 

comparable 856 transaction, forwarded to the procuring and receiving activity, will contain 

accepted IUID information. When acceptance at destination is applicable, the receiving system 

must report acceptance, including UII(s) (as applicable), using the DLMS 861, Acceptance 

Report, or direct input to iRAPT. Responsibility for Government acceptance may also be 

contractually assigned to an alternative organization which may use the DLMS 861 or direct 

input to iRAPT for acceptance reporting. iRAPT will extract the IUID information for all 

Government accepted IUID items and use to establish the birth record in the IUID Registry. 

Additional information and guidance on the IUID registry can be found on the UID Website 

http://www.acq.osd.mil/dpap/pdi/uid.

C19.15. MATERIEL RECEIPT. The receiving activity will notify the owner when UIT items are 

received to include UII(s) and/or serial number(s) for the UIT programs for Navy Depot Level 

Reparables and Positive Inventory Control Nuclear Weapon Related Materiel (UIT Designator 

Codes AAD and AAJ). Submit receipt using DLMS 527R Receipt Transaction, in accordance 

with the receipt procedures in Chapter 13. 

C19.16. UNIQUE ITEM IDENTIFIER RECEIPT DISCREPANCIES. When received UIIs do not 

match accompanying UII documentation (e.g., quantity and/or UIIs), the receiving activity will 

record the actual quantity and UIIs received, and notify the shipping activity or inventory control 

point (ICP)/IMM, as applicable, of the discrepancy. The receiving activity will submit a supply 

discrepancy report (SDR) showing the appropriate discrepancy code for quantity and IUID 

discrepancies in accordance with SDR procedures. For shortages, overages, or mismatched 

UIIs in shipments of controlled inventory items, arms, arms parts, ammunitions, and explosives, 

report within 24 hours of discovery (see SDR response timeframes). Action activities will reply 

to SDRs in accordance with Chapter 17 time standards. See Chapter 17 for SDR procedures.

C19.17. REINTRODUCTION OF UNIQUE ITEM IDENTIFIER ITEM PREVIOUSLY SHIPPED 

OUTSIDE THE CONTROL OF THE DEPARTMENT OF DEFENSE. When a UIT item(s) 

previously shipped outside DoD control is reintroduced to DoD control, the receiving activity will 

report the receipt, including UIIs and/or serial numbers, to the owner when required by the UIT 

program. The receiving activity will submit the receipt using DLMS 527R Receipt transaction.
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 5

C19.18. MATERIEL REDISTRIBUTION AND RELEASE

C19.18.1. The shipping activity will release the appropriate quantity and supply condition 

code of UIT items without regard to the UIIs and/or serial numbers selected. This also applies 

to disposal release orders (DRO). There is currently no documented requirement for an owner 

to direct release of specific UIIs and/or serial numbers by specifying applicable UIIs/serial 

numbers within the MRO/DRO.

C19.18.2 Defense Logistics Management Standards Retail Transportation and Supply 

Receipt And Acknowledgement Interchange. (See DLM 4000.25, “Defense Logistics 

Management Standards Manual,” Volume 3, Chapter 2.) For designated supply trading 

partners (currently limited to the Standard Base Supply System (SBSS) – Cargo Movement 

Operations System (CMOS) interface), the DLMS 940R Materiel Release will be used to 

support the UIT program for PIC NWRM. UIIs and the associated serial number will be passed 

in the DLMS 940R for each item meeting the PIC NWRM program criteria. For legacy items 

where the UII has not been marked in accordance with IUID policy, the serial number alone will 

be passed.

C19.18.3. For designated supply trading partners (currently limited to SBSS – CMOS 

interface), an information copy (image) of the Materiel Release 940R and Materiel Release 

Advice 945A will be used in support of Air Force PIC Fusion program data requirements. The 

routing of an additional information only copy of the DLMS standard transactions (940R and 

945A) is authorized for forwarding PIC Fusion data needed for the Air Force UIT registry. This 

is a specific authorized use with unique identifiers to flag the transaction as information only.

C19.19. CANCELLED MATERIEL RELEASE ORDER/DISPOSAL RELEASE ORDER 

SUPPORTING UNIQUE ITEM IDENTIFIER MATERIEL RELEASE

C19.19.1. The storage activity will confirm materiel release order (MRO) or DRO 

cancellation to the owner. The storage activity will confirm MRO or DRO cancellations in 

accordance with DLMS 945A materiel release cancellation advice or disposal release 

cancellation advice in accordance with Chapter 4.

C19.19.2. The owner will confirm MRO cancellation with Status Code BQ using DLMS 

870S Supply Status via DAAS to eligible status recipients. Data are entered in the eligible 

status recipient’s AIS.
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 6

C19.20. MATERIEL RELEASE CONFIRMATION

C19.20.1. The shipping activity will confirm materiel release to the owner and report 

shipped UIIs and/or serial numbers for the UIT programs for Navy Depot Level Reparables and 

Positive Inventory Control Nuclear Weapon Related Materiel (NWRM). For these two UIT 

programs, the storage activity will submit a Materiel Release Confirmation, including UIIs and/or 

serial numbers, using DLMS 945A, processed in accordance with Chapter 4.

C19.20.2. DLMS Retail Transportation and Supply Receipt and Acknowledgement 

Interchange. (See DLM 4000.25 Volume 3, Chapter 2). The transportation office will 

perpetuate the UIIs and/or serial numbers with the associated transportation control number 

(TCN) in the Materiel Release Confirmation (distribution code 111). This data content will be 

used by the supply activity to perpetuate this information to the Shipment Status. 

C19.21. CONFIRMATION OF SHIPMENT TO DEMILITARIZATION AND/OR DISPOSAL. The 

shipping activity will report UIIs and/or serial numbers to the owner, for shipment of items to 

demilitarization and/or disposal for the UIT programs for Navy Depot Level Reparables and 

Positive Inventory Control NWRM. The storage activity will include the UIIs and/or serial 

numbers on the DLMS 945A Materiel Release Advice for these two UIT programs. 

C19.22. SHIPMENT STATUS. For all UIT programs, the shipping activity will report shipment 

status, with UIIs and/or serial numbers selected for shipment, to the receiving DoD Component. 

The receiving DoD Component will enter the data in its AIS to confirm that received UIIs and/or 

serial numbers are the UIIs/serial numbers reported shipped. 

C19.23. PHYSICAL INVENTORY OF UNIQUE ITEM IDENTIFIER ITEMS. Physical inventory 

of UIT items will be conducted in accordance with Chapter 6 physical inventory procedures. 

With the exception of the SA/LW program, there is currently no UIT program with a DoD 

requirement to inventory by UII or serial number. 

C19.24. DOD STOCK READINESS PROGRAM. Under the Stock Readiness program, the 

Department of Defense requires uniform care of supplies, including the inspection and reporting 

of materiel condition and serviceability, and the scheduling, controlling, and reporting of 

packaging and other cost reimbursable actions supporting care of supplies in storage (COSIS). 

Upon implementation of IUID, the distribution center will report storage quality issues requiring 

COSIS work to the materiel owner via the Storage Quality Control Report, for IUID-required 

items including UII, for approval in accordance with DoD Component "Stock Readiness" Policy 

using DLMS 842SQ Storage Quality Control Report and DLMS 842S/R Storage Quality Control 

Report Reply.

C19.25. ACTIVE DOD-LEVEL UNIQUE ITEM TRACKING PROGRAMS. The following active 

UIT programs use DLMS transactions to exchange UIT UII and/or serial number on an interComponent basis. In addition, see Table C19.T4. for DLMS transactions required for IUID. All 

UIT items are subject to IUID.

C19.25.1. DoD Small Arms and Light Weapons Serialization Program. Refer to Chapter 

18, for the DoD SA/LW Serialization Program UIT procedures. The DoD SA/LW Serialization 

Program, UIT Designator AAA, uses the following DLMS transactions for UIT. 
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 7

Table C19.T1. DoD SA/LW Serialization Program UIT transactions

Transaction Title

140A Small Arms and Light Weapons Reporting

888A Small Arms and Light Weapons Data Change

C19.25.2. Navy Depot Level Reparable Program. The Navy Depot Level Reparable 

program is the recognized inter-DoD Component UIT program for select Navy-managed DLRs. 

The Navy Depot Level Reparable UIT program, UIT Designator AAD, uses the following DLMS 

transactions for UIT. 

Table C19.T2. Navy Depot Level Reparable Program UIT transactions

Transaction Title

140B RESERVED22 

527R Receipt

856S Shipment Status

888B RESERVED23 

945A Materiel Release Confirmation/Disposal Release Confirmation

C19.25.3. Positive Inventory Control of Nuclear Weapons Related Materiel. Air Force program 

for providing positive inventory control for nuclear weapons related materiel (NWRM). The 

Positive Inventory Control NWRM UIT program, UIT Designator AAJ, uses the following DLMS 

transactions for UIT.

Table C19.T3. Positive Inventory Control for NWRM UIT transactions

Transaction TITLE

527R 24 Receipt

856S Shipment Status

867I 25 Issue 

 

22 No documented procedures for 140B UIT Report. DLA to submit PDC documenting UIT use to include Chapter 

19 procedures.

23 Ibid.

24 Refer to ADC 347, Revise DLMS 527R Receipt, 867I Issue, 945A Materiel Release Advice, and 947I Inventory 

Adjustment to Support Unique Item Tracking (UIT) for Air Force Positive Inventory Control. DLA DSS has 

implemented ADC 347.

25 Ibid.
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 8

Table C19.T3. Positive Inventory Control for NWRM UIT transactions

Transaction TITLE

940R26 Materiel Release (Distribution Code 111) (approved for limited use)

945A

Materiel Release Advice (Distribution Code 111),27

Materiel Release Confirmation, Disposal Release Confirmation, and MRO 

Denials28

947I 29

Inventory Adjustment (only version 4030 can provide the UII)

If using 947I version 4010, must migrate to version 947I version 4030 no later 

than year 2019.

C19.25.4. IUID Transactions. In addition to the UIT transaction requirements identified by 

specific UIT programs, the following are associated with IUID requirements. All UIT items fall 

under DoD IUID requirements.

Table C19.T4. IUID Transaction Requirements

Transaction TITLE

527R30

Receipt. Approved for limited IUID scope applicable only to the return to 

inventory items previously issued to a commercial activity for repair (DLMS 

527R with 2/LIN01/010 Code E)

842A/W31,32 Supply Discrepancy Report (SDR) Follow-up, Correction, Cancellation, & 

Reconsideration Request

842S/Q33 Storage Quality Control Report

 

26 Refer to ADC 316C, Revise DLMS Implementation Convention (IC) 940R Material Release and DLMS IC 945A 

Material Release Advice, to Support UIT for Air Force Positive Inventory Control (PIC) under the Retail 

Transportation and Supply Receipt and Acknowledgement Interchange

27 Ibid.

28 Refer to ADC 347.

29 Ibid.

30 Refer to ADC 1042, Revise WAWF Advance Shipment Notice (ASN) to Accommodate DLA Interface for 

Reparable Government Furnished Property (GFP). Limited Receipt applicability; DLA Distribution Centers will 

include the UII in those DLMS 527R Receipt transactions with 2/LIN01/10 Code E (MILSTRAP legacy D4M 

functionality) when machine readable at time of receipt.

31 Refer to ADC 1030, Implementation of UID in the DLMS Shipment Status Supporting DOD IUID Supply 

Procedures and Associated SDR Procedures. Approved for staggered implementation no later than December 

2015.

32 Refer to ADC 1095, Enhanced Guidance for submitting SDRs for IUID Discrepancies. The target date for 

system edits to enforce appropriate discrepancy reporting based upon the FLIS IUID indicator is December 2015.

33 Draft PDC 1045 under development documenting IUID requirements for Storage Quality Control Report/Reply.
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 9

Table C19.T4. IUID Transaction Requirements

Transaction TITLE

842S/R34 Storage Quality Control Report Reply

842P35 Product Quality Deficiency Report Data Exchange

85636 Advance Shipment Notice

856R37 Shipment Status Materiel Returns

856S38 Shipment Status

86139 Acceptance Report

940R40 Materiel Release for retail transportation and supply receipt and 

acknowledgement interchange (approved for limited IUID use)

945A41 Materiel Release Advice (approved for limited IUID use)

C19.26. INACTIVE DOD-LEVEL UNIQUE ITEM TRACKING PROGRAMS. The following UIT 

programs were never activated as inter-DOD Component UIT programs using DLMS 

transaction exchange of UII and/or serial number. To activate these programs at the DOD-level,

a proposed DLMS change (PDC) is required to document the procedures and associated DLMS 

transaction exchange requirements for inter-DoD Component use.

C19.26.1. Radiation Testing and Tracking System Program 

C19.26.1.1. The Radiation Testing and Tracking System (RATTS) is a program 

established to provide regulatory and statutory compliance with Federal, state, and local 

 

34 Ibid.

35 Refer to ADC 1007, PQDR Data Exchange and Enhanced Exhibit Tracking via Standard Logistics Transactions. 

ADC 1007 established a DLMS transaction for the PQDR and supports IUID functionality.

36 Refer to ADC 129, New DLMS Supplement for DLMS ASN Following Federal IC 856, Shipment 

Notice/Manifest

37 Refer to ADC 1071, Implementation of DOD IUID Supply Policy in Version 4030 DLMS 856R Shipment Status 

Materiel Returns. Approved for staggered implementation no later than December 2017.

38 Refer to ADC1030, Implementation of UID in the DLMS Shipment Status Supporting DOD IUID Supply 

Procedures and Associated SDR Procedures. Approved for staggered implementation no later than December 

2015.

39 Refer to ADC 132, DS for Acceptance Report for Unique Identification (UID) and New Shipment/ Acceptance 

Discrepancy

40 Refer to ADC 1073, Implementation of IUID in the DLMS 940R/945A Supporting the SupplyTransportation Interface; Creation of New DLMS 945A Implementation Convention (IC) Version 4030; 

Administrative Update to the DLMS 945A IC Version 4010 (Supply/Transportation/IUID). ADC 1073 

addresses very limited implementation of UII in the 940R/945A, in response to a gap within Air Force 

retail supply-transportation interchange to exchange UII data in the 940R/ 945A so that USAF system can 

pass the UII on the 856S with the applicable TCN assigned by transportation. This ADC targets Air Force 

so they can implement ADC 1030; staggered implementation for December 2017. 

41 Ibid.
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 10

regulations for the use of radioactive materiel in fielded chemical defense equipment and in 

industrial applications. It maintains visibility of radioactive source UIIs and/or serial numbers 

and wipe test results. It is designed to provide strict control and identification of all radioactive 

sources to comply with Nuclear Regulatory Commission (NRC) license requirements.

C19.26.1.2. The cell, detector chemical (a component of the M43A1 detector), and 

drift tube module (a component of the chemical agent monitor (CAM)) are reportable. In turn, 

the M43A1 detector and M43 alarm are components of the M8A1 chemical agent alarm. The 

drift tube module in the CAM is the key component of the end item. Hereafter the cell, detector 

chemical, and CAM drift tube module are identified as radioactive “sources.” The requirements 

for these reporting standards are as set forth in NRC License 12-00722-13 and 12-00722-14.

C19.26.1.3. NRC licenses require UII and/or serial numbers control of the 

radioactive source throughout its life cycle. NRC requires a wipe test on an annual basis for the 

M43A1 detector radioactive source and CAM radioactive source. In addition, the M43A1 

detector radioactive source and the CAM radioactive source must be wipe tested within six 

months of transfer to another activity.

C19.26.2. Aviation Component Tracking Program. The Aviation Component Tracking 

Program is comprised of a set of procedures and databases designed to ensure unique part 

identification for flight safety parts and for life managed or special interest items. It provides for 

control, improved accountability, and visibility of U.S. Army Aviation equipment. The 

maintenance consolidated database contains the life cycle installation/removal/repair data for all 

life managed and special interest items. By maintaining the central repository for historical 

component data, the Army maintenance consolidated database allows for the recovery of critical 

data and continued use of parts with missing or erroneous data that would otherwise have to be 

scrapped. 

C19.26.3. Tritium UIT Program. This program identifies all primary and secondary items 

comprised of tritium throughout the Army, Army Reserve, National Guard, and Marines. This 

program is necessary to meet a requirement for location visibility of all tritium sources at all 

times.

C19.26.4. Controlled Cryptographic Items Program. The controlled cryptographic items 

(CCI) program was established to meet National Security Agency requirements to maintain 

visibility of controlled cryptographic end items, standalone CCI, and embedded CCI. The CCI 

program will perform a complete physical inventory at periodic intervals not to exceed 12 

months between successive inventories in accordance with National Security 

Telecommunications and Information Systems Security Instruction (NSTISSI) 4001, Controlled 

Cryptographic Items, July 1996. This inventory must include all CCI equipment and uninstalled 

CCI components. This is necessary to guard against preventable losses of un-keyed CCI to an 

actual or potential adversary.

C19.27. UNIQUE ITEM TRACKING DESIGNATOR CODES. The FLIS is the authoritative 

source for UIT designator codes. The UIT designator code indicates that an item is part of an 

established UIT program. In accordance with DODM 4140.01 policy, no new UIT programs will 

be established. Table C19.T5. shows the UIT Designator Codes.
Enclosure 4, ADC 1244

DLM 4000.25, Volume 2, Chapter 19 UIT

Page 11

Table C19.T5. Unique Item Tracking Designator Codes

Code Explanation 

AAA DoD Small Arms and Light Weapons Serialization Program (DoDSALWSP)

AAB Security Risk Category I Non-Nuclear missiles and Rockets 

AAC Radiation Testing and Tracking System (RATTS) Program

AAD Navy Depot Level Reparables (NDLR) Program

AAF Aviation Component Tracking Program

AAG Tritium Unique Item Tracking Program

AAH Controlled Cryptographic Items (CCI) 

AAJ Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM)
Enclosure 5, ADC 1244

Inventory Scenarios

Page 1

ENCLOSURE 5 TO ADC 1244 

Inventory Transaction Scenarios

Owner Storage Activity 

846P

System

Physical Inv.

Warehouse

Physical Inv. 

Results

947I Type= AJ 

RC=AA QTY=1

947I Type AJ RC=AA QTY=0**

** Transaction will include all serial numbers associated 

to the NSN, Cond. Code, and Owner.

DLMS 846P Physical Inventory Request Transaction

Scenario: Inventory gain after a physical inventory . No dual inventory adjustment necessary.

System Balance = 5 Physical Count 6 

1

2 3
Enclosure 5, ADC 1244

Inventory Scenarios

Page 2

Owner Storage Activity 

846P

System

Physical Inv .

Warehouse

Physical Inv . 

Results

947I Type= AJ 

R C=AA QTY=1

947I Type AJ RC=AA QTY=0* *

** Transaction will include all serial numbers associated 

to the NSN, Cond. Code, and Owner.

DLMS 846P Physical Inventory Request Transaction

Scenario: Inventory gain after a physical inventory . No dual inventory adjustment necessary .

System Balance = 5 Physical Count 6 

1

2 3

Scenario: Inventory loss after a physical inventory . No dual inventory adjustment necessary . 

System balance = 5 Physical Count = 4

Owner APSR Storage Activity 

System

846P

Physical Inv.

Warehouse

Physical Inv. 

Results

947I Type AD 

R C=AA QTY= 1

** Transaction will include all serial numbers associated 

to the NSN, Cond. Code, and Owner.

947I Type AJ RC=AA QTY=0* *

1

2

3
Enclosure 5, ADC 1244

Inventory Scenarios

Page 3

Scenario: Inventory mismatch after a physical inventory. Dual inventory adjustment required. 

System Balance = 5 Physical Count 5 (1 serial number/UII mismatch)

Scenario: Missing serial number/UII marking. Dual inventory adjustment required. 

System Balance = 5 Physical Count 5 (1 serial number/UII missing)

Owner Storage Activity 

System

Physical Inv.

Warehouse

Physical Inv. 

Results

947I Type= DU 

RC=AQ QTY=1

846P

947I Type = AJ RC=AA QTY=0**

** Transaction will include all serial numbers associated 

to the NSN, Cond. Code. , and Owner.

Owner Storage Activity 

System

Physical Inv.

Warehouse

Physical Inv. 

Results

947I Type= DU 

RC=AM QTY=1

846P

947I Type AJ RC=AA QTY=0**

** Transaction will include all serial numbers associated 

to the NSN, Cond. Code, and Owner.

1

2 3

1

2 3
Enclosure 5, ADC 1244

Inventory Scenarios

Page 4

Storage Activity

System

SDR Dispo provides 

mismatch SN/UII

Warehouse

Results

Owner

842A/R

Scenario: Materiel previously suspended at receiving. 

Two separate dual inventory adjustment required. 

System Balance = 5 Physical Count 4 / Suspended QTY 1 (1 serial number/UII missing)

947I Type= DU 

R C=AM QTY=1

947I Type= DU 

R C=AC QTY=1

** Transaction will include all serial numbers associated 

to the NSN, Cond. Code, and Owner.

1

2

3