DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

February 23, 2017

MEMORANDUM FOR SEE DISTRIBUTION

SUBJECT: Approved Defense Logistics Management Standards (DLMS) Change (ADC) 

1161A, Update Uniform Procurement Instrument Identifier (PIID) Numbering 

System in the Federal/DLMS Implementation Conventions and DLMS Manuals 

(Supply/SDR/DoDAAD/Finance/Contract Administration)

The attached change to DLM 4000.25, Defense Logistics Management Standards, DLM 

4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP), and DLM 

4000,25-2 Military Standard Transaction Reporting and Accountability (MILSTRAP) is approved. 

Implementation is no later than March 31, 2017. This document replaces ADC 1161 in its entirety.

Addressees may direct questions to the DLMS point of contact: Ms. Tonja Daniels-Carter, 

DLMS Contract Administration Lead, (269) 961-5227, DSN 661-5227, or e-mail 

Tonja.Daniels-Carter@dla.mil. Others must contact their Component designated representative 

available at www.dlmso.dla.mil/eLibrary/ServicePoints/allpoc.asp.

HEIDI M. DAVEREDE 

Program Manager

Enterprise Business Standards Office

Attachment

As stated

DISTRIBUTION: 

SUPPLY PROCESS REVIEW COMMITTEE (PRC) 

SUPPLY DISCREPANCY REPORT (SDR) PRC

DOD ACTIVITY ADDRESS DIRECTORY (DoDAAD) PRC

FINANCE PRC

cc:

ODASD(SCI)

OUSD (AT&L) PDI

WAWF PM
Attachment, ADC 1161A

Page 1

ADC 1161A

Update Uniform Procurement Instrument Identifier (PIID) 

Numbering System in the Federal/DLMS Implementation 

Conventions and DLMS Manuals

1. ORIGINATORS:

a. Functional POC: Bruce Propert, Defense Procurement and Acquisition Policy 

(DPAP), (703) 697-4384, e-mail: david.b.propert2.civ@mail.mil

b. Technical POC: Tonja Daniels-Carter, Defense Logistics Management Standards, 

(269) 961-5277, e-mail: Tonja.Daniels-Carter@dla.mil.

2. FUNCTIONAL AREAS:

a. Functional Areas: Contract identification in supply (MILSTRIP/MILSTRAP), SDR, 

DoDAAD and contract administration

b. Functional Processes: The goal of this standardized format is to ensure uniformity 

and consistency of data, thereby enhancing the transparency of Federal spending data to the 

public.

3. REFERENCES: 

a. ADC 1052, DOD Web Supply Discrepancy Report (WebSDR) Processes 

Enhancement and Interface with Electronic Document Access (EDA) System

b. ADC 1157A Update uniform Procurement Instrument Identification (PIID) 

Numbering system in the Federal/DLMS Implementation Conventions and DLMS Manual 

(Supply/Contract Administration), (ADC 1157 was originally issued on April 22, 2015, ADC 

1157A issued on February 23, 2017.)

c. DLM 4000.25, Defense Logistics Management Standards (DLMS) Manual, 

Volume 1 – Concepts and Procedures, Volume 2 – Supply Standards and Procedures,

Volume 6 – DoD Activity Address Directory and Volume 7 – Contract Administration

d. DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP)

e. DLM 4000.25-2, Military Standard Transaction Reporting and Accountability 

Procedures (MILSTRAP)

f. Defense Federal Acquisition Regulation Supplement (DFARS) Case 2015-D011, Final 

Rule Published February 26, 2016

g. DFARS Procedures, Guidance, and Information (PGI) 204.16, Uniform Procurement 

Instrument Identifiers
Attachment, ADC 1161A

Page 2

h. Federal Acquisition Regulation (FAR) Subpart 4.16, Unique Procurement Instrument 

Identifiers

i. Federal Acquisition Regulation (FAR) Case 2012-023, “Uniform Procurement 

Identification”, published as a final rule effective October 14, 2014

j. WAWF Engineering Change Proposal (ECP 0794) PIID Number Format (Contract & 

Delivery Order Numbers)

4. APPROVED CHANGE(S): Yellow highlight is applicable to ADC 1161A. Substantive 

updates subsequent to staffing the original PDC staffing are highlighted in green. 

a. Brief Overview of Change: ADC 1161A removes an incorrect business rule in 

position 10 of the PIID, updates the list of references to reflect approved (rather than draft)

documents, and updates the implementation date to no later than March 31, 2017. There are no 

additional changes to the procedures or DLMS transactions identified in ADC 1161. ADC 

1161A replaces ADC 1161 in its entirety. This change updates DLMS procedures to 

accommodate the procurement instrument identifier (PIID) numbering system, which must be 

implemented as soon as possible, but no later than March 31, 2017. This change will impact the 

Defense Logistics Manual (DLM) 4000.25 series, including the DLMS (Reference 3.c.),

MILSTRIP (Reference 3.d.), MILSTRAP (Reference 3.e.) manuals, Federal/DLMS 

Implementation Conventions (ICs), and Logistics Data Resource Management System 

(LOGDRMS). Additionally, this change provides guidance for legacy procurement instrument 

identification number (PIIN)/legacy call/order number during the initial transition.

b. Background:

(1) This is a mandated change required by recent changes to the FAR and DFARs. 

Components are encouraged to transition to the PIID numbering schema as soon as possible, but

no later than March 31, 2017. By that date, all Components must comply with the PIID 

numbering requirements of DFARS subpart 204.16 (Reference 3.g.), for all new solicitations, 

contracts, delivery calls/orders, and agreements issued, and any amendments and modifications 

to those new actions.

(2) DFARS subpart 204.70, Procurement Instrument Identification Number 

(PIIN)/Supplemental Procurement Instrument Identification Number (SPIIN) terminology was 

removed on February 26, 2016. SPIIN has dual meaning under the legacy format and is used in 

conjunction with the PIIN to identify (1) six-position contract modification, or (2) four-position 

call order number. Under the PIID format, contract modification is replaced with Supplementary 

PIID, PIIN and call/order are known as PIID, the new identifier for call/order number under the 

PIID is designated with F in the 9th position (PIID call/order number). Although the PIIN and 

the legacy four-position call/order number are superseded by the PIID, the term PIIN is still used 

in this change, where applicable, to associate with the legacy four-position call/order number. 

Continued use of the legacy PIIN/legacy call/order number terminology in the DLMS and legacy 

procedures is necessary to clarify expected data content in transaction formats during the initial 

transition. DLMSO will revisit these procedures no later than two years from the issuance of the 

approved change to remove the legacy PIIN and related terms.
Attachment, ADC 1161A

Page 3

(3) ADC 1157 (Reference 3.b.) incorporated the initial PIID changes into the DLM 

4000.25, Volume 7, Contract Administration, the Ship Notice/Manifest Receiving Report (856 

Federal IC), the Shipment and Billing Notice (857 Federal IC) and the DLMS 856 Advanced 

Shipment Notice. The Federal 857 and DLMS 856 will be modified to incorporate the updated 

wording in this change. The basic construct rules for the PIID assignment are repeated here to 

provide context for this change.

(a) The DOD PIID format will consist of a combination of thirteen 

alphanumeric characters, (13/13):

• Positions 1 – 6 identify the department/agency and office issuing the instrument. Use 

the DoDAAC assigned to the issuing office for positions 1 through 6. This DoDAAC 

must have the Procurement Authority Flag and Sub Tier code in the DoDAAD. 

• Positions 7 – 8 are the last two digits of the fiscal year in which the procurement 

instrument is issued or awarded. This is the date the action is signed.

• Position 9 indicates the type of instrument issued.

• Positions 10 – 13 are a four-character alphanumeric serial number. All “0s” (zeroes) 

are prohibited.

• The PIID may not contain special characters or spaces.

(b) The Federal non-DOD PIID format will consist of a combination of 

thirteen to seventeen alphanumeric characters, (13/17):

1

• Positions 1 – 6 identify the department/agency and office issuing the instrument. Use 

the Activity Address Code assigned to the issuing office for positions 1 through 6. 

This AAC must have the Procurement Authority Flag and Sub Tier code in the 

DoDAAD. 

• Positions 7 – 8 are the last two digits of the fiscal year in which the procurement 

instrument is issued or awarded. This is the date the action is signed.

• Position 9 indicates the type of instrument issued.

• Positions 10 – 17 are a four- to eight-character alphanumeric serial number. All “0s” 

(zeroes) are prohibited.

• The PIID may not contain special characters or spaces.

(4) Contract writing systems generally have the necessary logic to make the

distinction in the type of procurement instrument issued, whereas Component legacy 

supply/logistics systems that have not been modernized to be DLMS-compliant are still required 

to accommodate data exchanges between PIID and the legacy PIIN/call order number. Under 

the legacy format, when the four-position legacy call/order number is issued against a contract, it 

is always accompanied by the legacy PIIN (contract number). However, under the PIID

numbering system, this is no longer the case; the PIID call/order number does not have to 

associate with the base contract number. It will follow the 13 character PIID format, with F

designation in the 9th position (Type of Instrument) and will be treated as a contractual 

agreement even when the base contract number is available. A receiving report provided by the 

 1 Federal Acquisition Regulation Subpart 4.16 – Unique Procurement Instrument Identifiers
Attachment, ADC 1161A

Page 4

vendor may contain the PIID call/order number without the associated contract number. As a 

result, both DLMS and legacy formatted transactions must be able to support transactions that 

contain only the PIID call/order number (see Enclosure 4). Components are advised that these

requirements may affect Components’ ability to exchange DLMS and legacy 80 record position 

transactions.

c. Approved Change in Detail: 

(1) Update specified references, inclusive of data element field names, for 

procurement source data elements identified by the terms “contract number” or “PIIN” with the 

term “PIID”. Replace references to “call/order” with the term “PIID call/order”. These changes 

apply to MILSTRIP/MILSTRAP under legacy guidance and all DLMS procedures and 

transaction formats. 

(a) When a procurement instrument is issued under a PIID call/order, 

provide the value in the PIID field of either the DLMS or legacy formatted transaction. The 

PIID call/order is identified by F in 9th position. However, there is an exception authorized for 

DLA procurement instruments generated out of EBS for FEDMALL orders. In response to a 

customer order, FEDMALL will send a DLMS 511R to EBS with the base contract number for a 

FEDMALL ordering instrument. This triggers EBS to generate the PIID call/order number (EDI 

850 Purchase Order) to the vendor with the base contract PIID and the delivery order identified 

by the “M-PIID” (explicitly established to identify FEDMALL purchase/delivery orders 

generated out of EBS). Any required association can be found systemically in other sources such 

as Electronic Document Access (EDA).

(b) The call/order field in DLMS and legacy-formatted transactions will

only be used for the legacy four-position call/order number associated with the legacy PIIN.

(c) Remove instructions for the unimplemented DLMS enhancement to 

provide a call/order modification number in DLMS transactions.

Staffing Note: 

1. All Components (including Federal) must ensure that their systems can support the uniform 

number system for contract numbering (no conflicting edits based upon current numbering 

structure).

2. All Components (including Federal) must ensure there are no database constraints that will 

negatively impact use of the thirteen-position PIID call/order number in the data field currently 

used for the contract number.

(2) WebSDR Revisions: 

(a) Make comparable changes to those identified above to replace 

terminology and data field usage in input screens, query selection, and management reports. 

Data fields currently labeled “contract number” will be revised to read “PIID”. New SDR 

submissions containing a thirteen position number with the F or M designation in the 9th position

in the call/order number data field will be rejected using Reply Code 940 (Transaction rejected. 

Improper or missing either contract number or contractor-assigned shipment number on SDR

associated with vendor shipment) and remarks: “Thirteen-position PIID Call/Order Numbers 
Attachment, ADC 1161A

Page 5

must be provided in the PIID (contract number) data field.” WebSDR will provide additional

help screen display for the contract number and call/order number to include the following 

information: “Procurement Instrument Identifier (PIID): FAR and DFARS requires transition to 

the PIID numbering schema. Refer to DFARS subpart 204.16 for additional information. 

WebSDR requires the 13-character PIID call/order number (F or M designation in the 9th

position) to be carried in the PIID (contract number) field. The base contract number will not be 

reported on the SDR. SDRs containing legacy contract numbers with associated call/order 

numbers may continue to be reported.”

(b) SDR Reply Code 940 will be updated for use as described above:

940 Transaction rejected. Improper or missing either contract number or contractor-assigned 

shipment number on SDR associated with vendor shipment.

(c) WebSDR Interface with EDA. The EDA Web Service was designed 

to match the contract number from the SDR to the contract field in EDA and, if there is a match, 

EDA will respond with the contract administration office (CAO) DoDAAC and vendor CAGE to 

populate in the SDR record (Reference 3.a.). Under the new PIID numbering system, the 13-

position PIID call/order number (identified by F in the 9th position) will be used independently 

on a shipment (unlike the legacy four-position number call/order number that must always be 

associated with the PIIN). Regardless of vendor usage (alone or in conjunction with the 

governing contract number), the PIID call/order must be provided on the SDR in the existing 

field used for the contract number (to be labeled as the PIID). The base contract number will not 

be identified in the SDR; this is consistent with the receipt transaction for procurement source 

receipts. The PIID call/order number is the data element that will be matched to EDA. 

Staffing note: The WebSDR EDA interface will continue to extract the CAO DoDAAC and 

vendor CAGE for properly formatted PIID call/orders maintained by EDA and reported via SDR

to WebSDR. However, because the PIID call/order number is stored in the contract number field 

in EDA and the “procurement reference number” (the base contract number) is not provided in 

the current EDA Web Service, WebSDR will no longer be able to provide management reports 

or query results based upon the base contract number. DLMSO is in contact with DPAP 

concerning this gap, but no resolution is available at this time. Components should contact the 

DLMSO to confirm their interest in restoring this functionality.

d. Revisions to DLM 4000.25 Manuals: 

(1) Update the Terms & Definitions: Revise PIIN to retain legacy requirements and 

usage pending transition to the PIID, update Call/Order Number to clarify the legacy usage and 

the PIID call/order number usage, add PIID and Supplementary PIID in the following Defense 

Logistics Manuals (DLM):

• DLM 4000.25, Defense Logistics Management Standards (see Enclosure 1), 

Volume 1 – Concepts and Procedures

Volume 2 – Supply Standards and Procedures, including Appendix 7.28, 

Supply Discrepancy Report Relevant Data Element, and 

Volume 7 – Contract Administration

• DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP) (See Enclosure 2)
Attachment, ADC 1161A

Page 6

• DLM 4000.25-2, Military Standard Transaction Reporting and Accountability 

Procedures (MILSTRAP) (see Enclosure 3)

(2) Revise the following Federal/DLMS ICs to clarify the data fields (see Enclosure 

4).

Version 4010 Version 4030

DLMS ICs:

511M, 511R, 517G, 527D, 527R, 536L, 

567C, 810L, 812L, 812R, 824R, 846A, 

846D, 846I, 856, 861, 867I, 869C, 869F, 

870S, 945A, 947I

Federal IC: 857

DLMS ICs:

842A/R, 842A/W, 842C/I, 842C/R, 

842P, 842S/Q, 856R, 856S, 856W, 

940R, 945A, 947I

e. Proposed Transaction Flow: No changes identified.

f. Alternatives: DLMSO considered retaining separate data fields to accommodate 

concurrent identification of the base contract PIID and PIID call/order number, when both are 

available or independent identification of the PIID call/order number is a uniquely defined 

call/order number data field in DLMS-formatted transactions. However, this approach was not 

employed as it was not consistent with guidance from OUSD (AT&L) DPAP PDI that clarified 

the use of the PIID call/order number to uniquely identify a procurement action independent 

from a “base contract” identifier.

5. REASON FOR CHANGE: 

a. Identify DLMS and legacy process changes required to support the PIID 

implementation in accordance with FAR subpart 4.16 (Reference 3.h.), DFARS subpart 204.16 

(Reference 3.g.) and DFARS Case 2015-D011 (Reference 3.f.). 

b. Rejection of improperly formatted SDR transactions is necessary to ensure that data 

content in WebSDR and the Component system is reliable and equal. It would not be 

appropriate for WebSDR to move the value since the SDR reply transaction would no longer 

match the original submission. Data needs to be in the appropriate data field for consistent use in

reports, extracts, and generation of the EDA Web Service request.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: The uniformity and consistency of data in the published FAR/DFARS 

will promote achievement of rigorous accountability of procurement dollars and processes, and 

compliance with regulatory and statutory acquisition requirements such as those of the Federal 

Funding Accountability and Transparency Act of 2006.

b. Disadvantages: 

(1) The new PIID call/order number format is not supported in the legacy 

transactions; systems currently using the legacy four-position call/order number may need 
Attachment, ADC 1161A

Page 7

modification to support the PIID call/order number using the contract number data field. 

Components may not be able to update legacy systems scheduled to be replaced or modernized 

in the near term. 

(2) Variations in vendor implementation of the PIID may cause confusion in that 

some vendors may continue to provide both the base contract PIID while others provide only the 

PIID call/order number (F PIID). Users attempting to record receipts or report discrepancies will 

need to be trained to capture the PIID call/order only (when applicable) for submission of DLMS 

transactions.

(3) The Components use a screening process to identify materiel in stock or during 

receipt processing to locate materiel subject to suspension for various reasons such as contractor 

non-compliance. Materiel screened by the base contract number may not be picked up during 

screening actions if the vendor provides only the PIID call/order on the individual shipment 

documentation/packaging.

7. ASSUMPTIONS: Components should note that the PIID of the ordering instrument (base 

contract number) and PIID call/order number may appear in two separate fields on contractrelated documents, such as standard form (SF) 1449, and DOD form (DD) 1155. For example, 

the PIID base contract/ordering instrument goes in the contract number field, and the PIID 

call/order number goes in the call/order or delivery/order field. However, even when this is the

case, under current policy and guidance from OUSD (AT&L) PDI, only the PIID call/order 

number should be tracked in the Component applications and therefore, only the PIID call/order 

will be transmitted in DLMS and legacy formatted transactions

8. ADDITIONAL FUNCTIONAL REQUIREMENTS: None identified

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Implement as soon as 

possible, but no later than March 31, 2017. Components should provide their implementation 

schedule in response to this ADC.

10. IMPACT:

a. New DLMS Data Elements: None

b. Changes to DLMS Data Elements: 

(1) Update the metadata of PIIN, PIID, Supplementary PIID, and Call/Order Number 

in LOGDRMS (see Enclosure 5). 

(2) Update SDR Discrepancy Disposition/Status (Reply) Code 940 explanation as 

shown above.

c. Defense Automatic Addressing System (DAAS): 

(1) Revise Defense Automatic Addressing System (DAAS) conversion maps for all 

transactions for revised terminology and usage. 
Attachment, ADC 1161A

Page 8

(2) Revise WebSDR terminology and usage as described above. Establish new reject 

condition associated with revised code definition for Reply Code 940.

(3) The Global Exchange (GEX) supporting extract mapping of Invoicing, Receipt, 

Acceptance, and Property Transfer (iRAPT) transactions will move the PIID call/order number 

to the contract number field in the DLMS 856 Advance Shipment Notice transmitted to DLA 

Distribution Standard System (DSS) (applicable when the vendor/contractor provides both the 

base contract PIID and PIID call/order in the same transaction).

d. Automated Information Systems (AIS): Component applications must be updated 

to process both the legacy and new formats for contract data as defined in this DLMS change. 

e. Non-DLM 4000.25 series Publications: 

(1) Process and terminology revisions will require update to internal operating 

procedures and other published guidance.

(2) DLA and Services must provide standard operating procedures and training for 

receiving personnel to recognize when a vendor/contractor documents a shipment using both a 

base contract PIID and the associated PIID call/order (identified by F or M in the 9th position) on 

the receiving report, only the PIID call/order number must be populated on the receipt and SDR 

(when applicable) (rather than entering the base contract number and dropping the PIID 

call/order number, as may happen due to field length constraints).

11. PDC 1161 Response Table:

Component Component Responses Received DLMSO Response

Air Force Concurs without comment. Noted.

Army Concurs without comment. Noted.

USMC Concurs without comment. Noted.

Navy Navy concurs with PDC 1161, with the following comments:

1. This PDC will affect Navy ERP. Navy ERP will require a 

mapping change to the SPS interface, and implementing the 

PDC could possibly impact other Navy ERP logic (research 

underway). Planned implementation of the mapping change 

is Nov 2016.

2. This PDC will affect ITIMP, specifically the DIC 

PK9/DLMS 567C transaction. Current projection for ITIMP 

to be PIID compliant is Feb 2018.

Noted

Noted
Attachment, ADC 1161A

Page 9

Component Component Responses Received DLMSO Response

DLA 1. DLA implementing in EBS under BPR-C15-0011. Other 

RFCs are yet to be developed. Implementation date will be 

provided when the project schedule is complete; cannot 

confirm 1OCT16 at this time.

2. Revise DLMS note for qualifier CT on 511M, 511R from 

"Use to identify the procurement instrument identifier (PIID) 

associated with FedMall/part numbered catalog order." To 

"Use to identify the procurement instrument identifier (PIID) 

of the ordering instrument associated with the FedMall/part 

numbered catalog order." FedMall would not be passing the 

Represented Contract PIID, so by leaving out that 

qualification it can be left open to interpretation.

3. FEDMALL currently uses PIIN/SPIN labels and will need 

to be modified.

Noted 

Change made to 

511M and 511R.

Noted

Transaction 

Services

Concurs without comment. Noted

USTRANSCOM Abstains Noted.
Enclosure 1, ADC 1161A

Page 1

Enclosure 1, DLM 4000.25, Defense Logistics Management Standards

Revise the DLMS Manual as shown:

DLM 4000.25, Volume 1

AP2. APPENDIX 2 TERMS AND DEFINITIONS

PROCUREMENT INSTRUMENT IDENTIFICATION NUMBER (PIIN). Identifies legacy 

contractual documents. (See DFARS subparagraph 204.70.) Use of the PIIN is 

authorized in the DLMS and legacy MILSTRIP/MILSTRAP procedures, pending 

transition to the procurement instrument identifier (PIID). 

PROCUREMENT INSTRUMENT IDENTIFIER (PIID). A standard unique identifier

for a solicitation, contract, agreement, or order and related procurement 

instruments, see DFARS Subpart 204.16. The new identifier for call/order number 

under the PIID rules is designated by F in the 9th position. However, there is an 

exception authorized for DLA procurement instruments supporting FEDMALL to 

identify the delivery/call order using an M in the 9th position. The PIID call/order 

number is always treated as a contractual agreement even when the base 

contract number is available. If a base PIID contract number and PIID call/order 

number are available, provide the PIID call/order number (F or M PIID) only. 

SUPPLEMENTARY PROCUREMENT INSTRUMENT IDENTIFIER (Supplementary 

PIID). Identify amendments or modifications to the procurement instrument. The 

Supplementary PIID must be used in conjunction with the PIID.

CALL/ORDER NUMBER. A release against a basic contract. This is a legacy four 

-position field (that must be used in conjunction with a legacy PIIN). The new 

identifier for call/order number under the PIID rules is designated by F or M in the 

9th position of the PIID and is treated as a contractual document. See PIID 

definition.

AP3. APPENDIX 3 ACRONYMS AND 

ABBREVIATIONS

PIID Procurement Instrument Identifier
Enclosure 1, ADC 1161A

Page 2

C4. CHAPTER 4

FUNCTIONAL APPLICATION ERRORS

C4.2. DLMS 824R REJECT ADVICE

C4.2.1. Implementation Convention Content. The DLMS 824R, Reject Advice 

shallwill convey the following information when reporting errors to the originator:

C4.2.1.1. Table 1 Data. Identifies the originator of the DLMS 824R and the 

recipient, which is the originator of the erroneous transaction being rejected.

C4.2.1.2. Table 2 Data

C4.2.1.2.1. Identifies the erroneous transaction, specifically including 

the following data:

C4.2.1.2.1.1. Document number or procurement instrument 

identifier (PIID).2 When a contract is authorized under a PIID call/order number (F 

in 9th position), provide the value in the PIID field.

C4.2.1.2.1.2. Transaction set control number.

 2 Use the legacy PIIN pending transition to the PIID.
Enclosure 1, ADC 1161A

Page 3

Volume 2 – SUPPLY STANDARDS AND 

PROCEDURES

C4. CHAPTER 4

REQUISITIONING

C4.7.14.1.1. MROs directing shipment of requisitioned GFM will 

perpetuate contract data to include the contract number procurement instrument 

identifier (PIID) authorizing GFP. , and the call/order and CLIN when available. When 

GFM is authorized under a PIID call/order number (F in 9th position), provide the 

value in the PIID field.3 Include the CLIN when available and directed by the 

authorizing Component. Contract data will be provided by the source of supply for 

pushed GFM not initiated by a requisition.

C4.7.14.1.2. MROs directing shipment of reparables for induction for 

commercial maintenance will include the contract number PIID authorizing GFP, and 

the call/order and CLIN when available.

C4.7.14.1.3. MROs directing shipment of GFP in contractor custody will 

include the contract number PIID authorizing GFP, and the call/order and CLIN when

available.

 3 Use the legacy PIIN pending transition to the PIID. When GFM is authorized under a PIIN, include 

the legacy four-position call/order number associated with the PIIN when available and directed by 

the authorizing Component. Refer to ADC 1161A.
Enclosure 1, ADC 1161A

Page 4

CH17. CHAPTER 17

SUPPLY DISCREPANCY REPORTING

(preceding text not shown)

C17.3.1.2. Shipment Information. SDRs must contain a document number. 

Identify the original requisition document number when known; otherwise a constructed 

document number is required. DoD requisitioners reporting discrepant shipments may 

only use a constructed document number for selected discrepancies as discussed 

below. A constructed document number identifying the receiving distribution center is 

required for depot receipts reported electronically, including new procurement receipts. 

A constructed document number may also be prepared by a transshipper based upon 

the CCP or port DoDAAC. Additional information, such as transportation numbers 

(TCN, bill of lading number, etc.) may be provided in accordance with the DLMS IC. 

Procurement information (procurement instrument number (contract number), when 

available, call/order number, contract line item number, and vendor shipment number)

must be provided for wholesale level procurement source receipt discrepancies (SDR 

Document Type 9 or P). Procurement information will include the procurement 

instrument identifier (PIID) (this term is inclusive of the PIID call/order), contract 

line item number (CLIN), and vendor shipment number.4 When a PIID call/order 

number (F or M in 9th position) is used, provide the value in the PIID field. When 

reporting new procurement receipts, the distribution center will cite a “pseudo shipment 

number,” equivalent to that cited on the receipt, when the actual vendor shipment 

number is not available from shipping documentation. The pseudo shipment number 

will be constructed to identify the receiving depot and a constant 01 (that is, the serial 

number will not be incremented; therefore, the pseudo shipment number will not be 

unique). In order to systematically identify pseudo shipment numbers, the third position 

must be numeric (vendor assigned shipments use a three digit alpha prefix to identify 

the vendor). For example, pseudo shipment numbers prepared by Distribution Center 

San Joaquin, California (DDJC), will be reported as DD1JC01. Action activities must 

have the capability to update procurement information via the SDR reply when not 

populated by the submitter on procurement source receipt discrepancies involving direct 

vendor/contractor delivery to the customer (SDR Document Type 6).

(intervening text not shown)

C17.3.2.6.2. Concealed Overage/Shortage. U.S. Government 

customers must report overages or shortages discovered while opening a sealed 

vendor pack regardless of dollar value or shipper. These reports must contain, if 

available, the PIID contract number from the packaging, the lot number, and original 

document number. A constructed document number must be provided when the 

 4 Use the legacy PIIN pending transition to the PIID. When using the PIIN, include the fourposition call/order number. Refer to ADC 1161A.
Enclosure 1, ADC 1161A

Page 5

original number is not known. When using a constructed document number in an SDR 

coordinate with the applicable Component finance office and follow MILSBILLS 

procedures citing Code U in the first position of the constructed document number serial 

number (DLMS Utilization Code U), include fund code and credit-to/bill-to DoDAAC, to 

ensure that credit/billing is appropriate. Conformance with standard line of accounting 

(SLOA)/accounting classification requires any initiation of a financial business event 

(e.g., credit or debit) to include SLOA mandated standard financial information system 

(SFIS) elements.5 The DLMS SDR transaction supports inclusion of SLOA required 

elements.

(intervening text not shown)

C17.3.2.11.2. Incorrect item discrepancies discovered while opening a 

sealed vendor pack will be reported regardless of dollar value or shipper. These reports 

must contain the contract number PIID from the packaging and, if available, the lot 

number and the original document number. A constructed document number will be 

provided when the original number is not known. When using a constructed document 

number in an SDR coordinate with the applicable Component finance office and follow 

MILSBILLS procedures citing Code U in the first position of the constructed document 

number serial number (DLMS Utilization Code U), include fund code and credit-to/bill-to 

DoDAAC to ensure that credit/billing is appropriate. Conformance with standard line of 

accounting (SLOA)/accounting classification requires any initiation of a financial 

business event (e.g., credit or debit) to include SLOA mandated standard financial 

information system (SFIS) elements.6 The DLMS SDR transaction supports inclusion of 

SLOA required elements. Include identity of the incorrect item received in the 

discrepancy report.

(intervening text not shown)

C17.3.12.1.2. Replies. Action activities will reply to SDRs by 

submission of a DLMS 842A/R to WebSDR or via direct WebSDR input. SDR replies 

will indicate the appropriate disposition, (e.g., acknowledgment of the report, disposition 

of the materiel, validation of the report with authorization of financial adjustment, and/or 

instructions for repackaging, repair or other types of corrective action). SDR replies 

must contain the appropriate discrepancy code consistent with all information provided 

by the customer. This may require updating of the discrepancy codes used by the 

customer to assign the appropriate discrepancy code for the scenario described in the 

SDR remarks. The action activity will identify the disposition/status using the 

appropriate Reply Code (Appendix 3). Action activities will ensure that inappropriate 

reply codes are blocked from use when responding to transshipper SDRs (Document 

Type Code W)7. Shipment information applicable to direct vendor deliveries, new 

procurement, etc., must be completed by the action activity where incomplete or 

inaccurate on the original report. This includes identification of the shipping activity or 

 5 Refer to ADC 1043.

6 Refer to ADC 1043.

7 Refer to Approved DLMS Change 317B, Action Activity Replies to Transshipper-Prepared SDRs.
Enclosure 1, ADC 1161A

Page 6

vendor (by CAGE), contract number PIID, and identifying shipment numbers. DLMS 

compliant applications must also ensure that direct vendor delivery shipments are 

identified by Document Type Code 6 on the SDR reply, regardless of what the customer 

originally designated. 

(intervening text not shown)

C17.3.20.1.2.5. SDRs that contain a contract number PIID (not 

including the contract reference number) will be edited to ensure that the shipper is 

populated correctly. DoD WebSDR will match the contract number PIID against the 

Electronic Document Access (EDA) System contract files to identify the 

vendor/contractor CAGE code and the applicable CAO DoDAAC. If a match is found, 

these values from the EDA contract information will update in the SDR record. User 

input will be overridden by the EDA values if different.8

(intervening text not shown)

C17.3.20.1.3.1.1. Abridged SDR. The abridged unencrypted

version of the SDR e-mail will include the following data content. Coded information will 

not include the corresponding clear-text explanation. The submitter and action activities 

will not be identified by clear-text addresses.

• DoD Web SDR Report Control Number

• Additional System SDR Control Number

• Customer-Assigned Control Number

• Document Number/Suffix

• Contract Number PIID

• Transportation Control Number

• Date of Preparation

• Document Type Code

• DLA Disposition Services SDR Type Code

• Discrepancy Code(s)

• Action Code

• Submitter (Activity From)

• SDR Point of Contact

o Name

o Commercial Phone or DSN

o E-mail

• Attachment/Off-line Flag

 8 Ibid.
Enclosure 1, ADC 1161A

Page 7

C17.3.20.1.3.1.2. Abridged SDR Reply. The abridged 

unencrypted version of the SDR Reply e-mail will include the following data content. 

Coded information will not include the corresponding clear-text explanation with the 

exception of the Reply Disposition Code which must include text for understanding. The 

submitter and action activities will not be identified by clear-text addresses.

• DoD WebSDR Report Control Number

• Additional System SDR Control Number(s)

• Original Reference Number 

• Document Number/Suffix

• Contract NumberPIID

• Transportation Control Number

• Reply Date

• Document Type Code

• DLA Disposition Services SDR Type Code

• Reply Code(s)

• Action Activity (Activity From) Submitter (Activity To)

• Comments/Remarks

• Reply POC

o Name

o Commercial Phone or DSN

o E-Mail

• Attachment/Off-line Flag

(intervening text not shown)

C17.3.20.2.15. SDRs associated with new procurement (Document 

Type 9 or P) must contain the applicable contract numberPIID and contractor-assigned 

shipment number. Reject with Discrepancy Disposition/Status (Reply) Code 940. New 

SDR submissions containing a thirteen position number with the F or M designation in the 9th

position in the call/order number data field will be rejected using Reply Code 940 and 

clarifying remarks stating that the thirteen-position PIID Call/Order Number must be 

provided in the PIID (contract number) data field.
Enclosure 1, ADC 1161A

Page 8

CH20. CHAPTER 20 

MEDICAL UNIT ASSEMBLY PROGRAM

(preceding text not shown)

C20.4. DUE-IN ESTABLISHMENT. The assembly manager shallwill use the Defense 

Logistics Management SystemStandards (DLMS) 527D, Due-in/Advance Receipt/Due 

Verification transaction to establish pre-positioned materiel receipt (PMR) information at 

the assembly activity. DLMS 527D PMR provides the procurement instrument 

identifier (PIID)1 procurement instrument identification number (PIIN) (i.e., contract 

number), contract line item number, call order serial number, national stock number 

(NSN), part number, build directive number, and other information necessary to ensure 

that the assembly activity receipts the item in the correct build directive number. When 

a PIID call/order number (F in 9th position) is used, provide the value in the PIID 

field. The PMR also provides data to prepare the DLMS 527R Receipt transaction 

upon receipt of the materiel. Assembly managers and assembly activities shallwill 

follow procedures in Chapter 12, Due-in PMR, to establish advance receipt information 

and to maintain control of due-in materiel.

_______________________________

1 Use the legacy PIIN pending transition to the PIID. When using the PIIN, include the fourposition call/order number. Refer to ADC 1161A.

C21. CHAPTER 21

STOCK READINESS PROGRAM

C21.3.6 Detailed Requirements. The owner/manager preparing the stock 

screening request shallwill assign a suspense date based on the inspection type. The 

owner/manager shallwill specify screening criteria as appropriate. Only one

procurement instrument identifier (PIID)9 contract number (optionally including call 

number and CLIN), vendor, or batch/lot may be specified per request. When a PIID 

call/order number (F in 9th position) is used, provide the value in the PIID field.

The materiel owner/manager may specify up to five CAGE/part number combinations 

associated with an NSN, (e.g., for CSI inspections). The owner/manager shallwill

assign an internal reference number for identification of the stock screening request,

that may be used to associate the request with the triggering event. This reference 

number may be systemically assigned and shallwill be perpetuated to the stock 

screening reply and any resulting SQCRs. A document number is required to ensure a 

 9 Use the legacy PIIN pending transition to the PIID. When using the PIIN, may include the fourposition call/order number. Refer to ADC 1161A.
Enclosure 1, ADC 1161A

Page 9

DoD-wide unique control number. Both the stock screening reference number and the 

document number must be included in all transactions. In addition, when applicable, 

the Product Quality Deficiency Report (PQDR) report control number (RCN) or the SDR 

document number shallwill be included to provide a cross reference when the 

screening action is triggered by a PQDR or SDR.

(intervening text not shown)

C21.4.10. DAAS Query Capability. WebSS and WebSQCR will include 

capability to query to provide historical information by: NSN, CAGE/part number, control 

numbers, PIIDcontract number or CAGE, date open, date closed, storage activity, and 

owner/manager. The query function may be used to monitor storage activity responses 

to requested stock screening actions, displaying which activities have responded and 

which are outstanding. The stock screening request query will support drill down 

capability to review the associated SQCRs.

CH26. CHAPTER 26

CONTRACTOR ACCESS TO GOVERNMENT 

SOURCES OF SUPPLY

(preceding text not shown)

C26.3.3.6. Contract Information. All GFM requisitions for or by 

contractors must identify the contract number procurement instrument identifier 

(PIID)10 and other appropriate contract data, as required. Components authorizing 

GFM may direct the inclusion of the manufacturing directive number (MDN) as 

supplemental to the authorizing contract number PIID.

11

C26.3.3.6.1. Identification of the contract numberPIID in 

(2/GF03/70). When GFM is authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. In MILSTRIP legacy, the last eight 

positions of the procurement instrument identification number (PIIN)PIID are mandatory 

in rp 73-80.12

C26.3.3.6.2. When applicable, provide the legacy call/order 

number associated with the PIIN, in (2/GF07/70), (MILSTRIP legacy rp 69-72). Leave 

blank when the call/order number is the PIID with ‘F’ in the 9th position.

 10 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A. 11 Refer to ADC 1014. Staggered implementation is authorized for the transition to the mandatory 

inclusion of the contract numberPIID (rather than MDN as an alternative to the contract numberPIID).

12 Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS 

compliant contract number PIID (rather than the abbreviated contract number authorized under legacy 

MILSTRIP procedures).
Enclosure 1, ADC 1161A

Page 10

(intervening text not shown)

C26.3.3.7. GFM non-national stock number (NSN) requisitions are 

identified by the applicable code qualifier at 2/LIN02/100. In MILSTRIP legacy, they 

must be identified with an E in rp 68; the legacy call/order number, if appropriate, in rp 

69-72; and the last eight positions of the PIIDPIIN in rp 73-80 (the MDN is optional).

(intervening text not shown)

C26.5.4.3. Perpetuate all applicable contract data. Under DLMS, the 

MCA must include the PIID DFARS contract number. Where required by the 

Component, the MCA may also perpetuate the MDN consisting of the MCA’s 

distribution code and two other alpha/numeric characters as assigned.13

(intervening text not shown)

C26.5.5.2. If the requisition has not been previously validated and the 

legacy call/order number/PIID/PIIN (or MDN and/or CLIN, if required by the Component 

in addition to the legacy call/order number/ PIIN) is not present, cite Advice Code 2U.

C26.5.5.3. If the requisition has not been previously validated and the 

call/order number/PIID/PIIN is present, validate the data elements as indicated in Table 

C26.T1, and generate the GFM Validation Response as follows:

Table C26.T1. MCA Validation Process for GFM Transactions

CODE OR DATA ELEMENT VALIDATION OF ENTRY

(preceding text not shown)

Contract Call or Order 

Number (four-position 

legacy value)

If specified by S/A contract, and entry is blank or incorrect, reject with 

Status Code DB. 

Contract Line Item Number 

(CLIN) 

If specified by S/A contract, and entry is blank or incorrect, reject with 

Status Code DB. 

Procurement Instrument 

Identification Number

Identifier (PIID)

If blank, or contract is not on MCA file, or contract has expired, reject 

with Status Code DB. (If requisition originated in the MILSTRIP 

legacy format, then only the last eight positions of the PIIDPIIN are 

mandatory.). When the procurement instrument is issued under 

the PIID call/order number (F in 9th position), this value must be 

provided in the PIID field.

(intervening text not shown)

C26.10.3. The ICP/IMM will prepare materiel release orders for stock shipment 

using document numbers based upon a DLA-established DoDAAC. The ship-to 

location cited in the release order will identify the contractor DoDAAC authorized to 

receive GFM. Under DLMS processing, the Materiel Release Order will include the 

 13 Refer to ADC 1014. Staggered implementation is authorized for the transition to the full DFARS 

compliant contract numberPIID (rather than the abbreviated contract numberPIID authorized under legacy 

MILSTRIP procedures) and for the transition to the mandatory inclusion of the contract number (rather 

than MDN as an alternative to the contract numberPIID).
Enclosure 1, ADC 1161A

Page 11

authorizing contract numberPIID14, and the call/order and CLIN, when applicable; this is 

not applicable to MILSTRIP legacy processing. When a PIID call/order number (F in 

9th position) is used, provide the value in the PIID field. The storage activity will 

provide shipment confirmation to the ICP/IMM for monitoring GFM shipments and will 

prepare shipment status; under DLMS processing, the shipment status will perpetuate 

applicable contract data. For contractors without capability to accept legacy 80 record 

position/DLMS transactions, status of the GFM component delivery will be provided 

upon request by the contractor. The assembled/manufactured end items may be 

shipped directly to customers or shipped to a storage location for future use.

 14 Use the legacy PIIN pending transition to the PIID. When using the PIIN, may include the fourposition call/order number. Refer to ADC 1161A.
Enclosure 1, ADC 1161A

Page 12

DLM 4000.25, VOLUME 7 CONTRACT 

ADMINISTRATION

CH4. CHAPTER 4

CONTRACT COMPLETION STATUS REPORTING

(preceding text not shown)

C4.8. CANCELLATIONS. Conditions may necessitate the cancellation of a contract 

completion status transaction. Cancellation is done by sending the procurement 

instrument identifier (PIID)15 and procurement instrument identification number (PIIN),

Supplementary PIID Procurement Instrument Identification Number (SPIIN) (when 

applicable), CAO, and PO of the original transaction and a Transaction Status Indicator 

Code K. When a PIID call/order number (F in 9th position) is used, provide the 

value in the PIID field. 

(intervening text not shown)

C4.10.3.4. Cancellation Report. A cancellation report is identified by the 

Transaction Status Indicator Code K in a 1/LQ/110 data segment. A cancellation report 

must be sent at least one calendar day before its replacement report. A cancellation 

report requires the To, the From, the PIIDPIIN and the Supplementary PIIDSPIIN (if 

applicable), the code for the type transaction, and the cancellation code.

 15 Use the legacy PIIN pending transition to the PIID. When using the PIIN, may include the fourposition call/order number. Refer to ADC 1161A.
Enclosure 2, ADC 1161A

Page 1

Enclosure 2, DLM 4000.25-1, Military Standard Requisitioning and Issue 

Procedures (MILSTRIP)

Revise the MILSTRIP Manual as shown:

MILSTRIP ABBREVIATIONS AND 

ACRONYMS

PIID Procurement Instrument Identifier

DEFINITIONS

PROCUREMENT INSTRUMENT IDENTIFICATION NUMBER (PIIN). Identifies 

legacy contractual documents. Use of the PIIN is authorized in the DLMS and 

legacy MILSTRIP/MILSTRAP procedures, pending transition to the procurement 

instrument Identifier (PIID). 

PROCUREMENT INSTRUMENT IDENTIFIER (PIID). A standard unique identifier 

for a solicitation, contract, agreement, or order and related procurement 

instruments, see DFARS Subpart 204.16. The new identifier for call/order number 

under the PIID rules is designated by F in the 9th position. However, there is an 

exception authorized for DLA procurement instruments supporting FEDMALL to 

identify the delivery/call order using an M in the 9th position. The PIID call/order 

number is always treated as a contractual agreement even when the base 

contract number is available. If a base PIID contract number and PIID call/order 

number are available, provide the PIID call/order number (F or M PIID) only. 

SUPPLEMENTARY PROCUREMENT INSTRUMENT IDENTIFIER (Supplementary 

PIID). Identify amendments or modifications to the procurement instrument. The 

Supplementary PIID must be used in conjunction with the PIID.

CALL/ORDER NUMBER. A release against a basic contract. This is a legacy four 

-position field (that must be used in conjunction with a legacy PIIN). The new 

identifier for call/order number under the PIID rules is designated by F or M in the 

9th position of the PIID and is treated as a contractual document. See PIID 

definition. 
Enclosure 2, ADC 1161A

Page 2

C3. CHAPTER 3

REQUISITION PROCESSING AND RELATED ACTIONS

(preceding text not shown)

C3.29. SOURCE OF SUPPLY SUBMISSION OF SINGLE LINE CANCELLATION/ 

DIVERSION REQUESTS TO PROCUREMENT

C3.29.1. These requests may be in mechanical record format or by manual 

instructions; however, electronic submission of the requests is recommended.

C3.29.2. Prepare transactions using the Appendix AP3.9 format. Use DIC ACP to 

identify the transactions submitted to procurement. Entry of the procurement 

instrument identifier (PIID)

16 /procurement instrument identification number (PIIN) or 

purchase request Nnumber (PRN) will be dependent upon whether a PIIDPIIN has 

been assigned to a contract and is known to the source of supply at the time of receipt 

of cancellation requests. When the PRN is used, the DoDAAC of the consignee to 

which shipment is to be diverted should be reflected in rp 45-50. When the source of 

supply does not desire diversion, rp 45-50 will be left blank.

(intervening text not shown)

C3.29.3.7. The PIIDPIIN, if known; otherwise, the PRN and date of the 

purchase request.

C4. CHAPTER 4

STATUS

(preceding text not shown)

C4.3.4. Direct delivery notice17, DICs AB1, AB2, AB3, and AB8 provide notice to 

eligible status recipients that materiel shallwill be supplied by direct vendor delivery 

(DVD) from procurement. Direct delivery notice transactions provide a cross-reference 

between the requisition document number and the procurement instrument identifier 

(PIID)procurement instrument identification number (PIIN). DICs AB1, AB2, AB3, and 

AB8 transactions are generated when materiel is procured for direct shipment to 

consignee. The DIC AB_ transaction shallwill be furnished to applicable entries in the 

requisition (e.g., the requisitioner (rp 30-35), Supplementary Address (SUPADD) (rp 45-

 16 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A

17 Use of DIC AB_ changed from intra- to inter-Service for direct delivery from procurement last reported 

as not implemented by GSA. Refer to AMCL 155.
Enclosure 2, ADC 1161A

Page 3

50), and distribution code (rp 54)), regardless of the M&S code used. This enables 

customers to have a basis for reporting nonreceipt of materiel.

(intervening text not shown)

C4.8.5. Source of supply direct delivery notice18, DICs AB1, AB2, AB3, and AB8 

notify eligible status recipients that materiel shallwill be supplied by DVD from 

procurement. DIC AB_ transactions shallwill be provided to the consignee. This notice 

provides a cross-reference between the requisition number and the PIIDPIIN. See 

Appendix AP3.11 for the DIC AB_ format.

C11. CHAPTER 11

CONTRACTOR ACCESS TO GOVERNMENT SOURCES 

(preceding text not shown)

C11.3.3.6. Contract Information. All GFM requisitions for or by contractors 

must identify appropriate contract data as required. 

C11.3.3.6.1. The last eight positions of the procurement instrument 

identifier (PIID)19 procurement instrument identification number (PIIN) is mandatory, rp 

73-80. When GFM is authorized under a PIID call/order number (F in 9th position), 

provide the value in the PIID field. 

C11.3.3.6.2. When applicable, the legacy call/order number is in rp 69-

72. Leave blank when the call/order number is the PIID with ‘F’ in the 9th position.

(intervening text not shown)

C11.3.3.7. GFM non-national stock number (NSN) requisitions are identified 

with an E in rp 68; the call/order number, if appropriate, in rp 69-72; and the last eight 

positions of the PIIDPIIN in rp 73-80 (the MDN is optional).

(intervening text not shown)

C11.5.5.2. If the requisition has not been previously validated and the 

call/order number/PIIDPIIN (or MDN, if required by the Component in addition to the 

call/order number/PIIDPIIN) is not present, cite Advice Code 2U.

 18 Use of DIC AB_ changed from intra- to inter-Service for direct delivery from procurement last reported 

as not implemented by GSA. Refer to AMCL 155.

19 Use the legacy PIIN pending transition to the PIID. When using the PIIN, may include the fourposition call/order number. Refer to ADC 1161A
Enclosure 2, ADC 1161A

Page 4

C11.5.5.3. If the requisition has not been previously validated and the 

call/order number/PIIDPIIN is present, validate the data elements as indicated in Table 

C11.T1, and generate the GFM Validation Response transaction as follows:

(intervening text not shown)

C11.5.6. MCAs in receipt Supply Status with Status Code BF from the SoS will 

review for establishment of a valid requisition. If a valid requisition exists, Requisition 

Follow-Up (DIC AT_) transaction will be generated. If a valid requisition does not exist, 

a report will be generated for internal review. Subsequent receipt of a valid requisition 

will be processed under the procedures/validation process indicated in Table C11.T1.

Table C11.T1. MCA Validation Process for GFM Transactions

CODE OR DATA ELEMENT VALIDATION OF ENTRY

(preceding text not shown)

Contract Call/Order Number

(four-position legacy value)

If specified by S/A contract, and entry is blank or incorrect, reject with 

Status Code DB.

Last eight positions of the 

Procurement Instrument 

IdentifierProcurement 

Instrument Identification 

Number

If blank, or contract is not on MCA file, or contract has expired, reject 

with Status Code DB. (The last eight positions of the PIIDPIIN are 

mandatory.)

When GFM is authorized under a PIID call/order number (F in 9th

position), provide the last eight positions of the PIID call/order 

value in the PIID field. 
Enclosure 2, ADC 1161A

Page 5

AP3.2. APPENDIX 3.2

REQUISITION

Contract Call/Order 

Number

69-72 If required by the Component contracts, 

enter the appropriate contract legacy 

four-position call/order number 

associated with the PIIN; otherwise 

leave blank.

Contract Identification

Procurement 

Instrument Identifier 

(PIID)

73-80 Enter the last eight positions of the PIID

procurement instrument identification 

number (PIIN). This entry is 

mandatory.20, 21 When materiel is 

authorized under a PIID call/order 

number (F in 9th position), provide 

the last eight positions. 

AP3.4. APPENDIX 3.4

NON-NATIONAL STOCK NUMBER REQUISITION 

(MECHANICAL)

Contract Call/Order 

Number

69-72 If required by an Service/Agency (S/A) 

contract, enter the appropriate contract

legacy four-position call/order number

associated with the PIIN; otherwise 

leave blank.

Procurement Instrument 

Identifier Procurement 

Instrument Identification 

Number (PIID)

73-80 At the option of the S/A, enter last eight 

positions of the PIIDPIIN in lieu of the 

Manufacturing Directive Number (MDN) 

in rp 54-56. This entry is mandatory if the 

MDN is not entered in rp 54-56.

22, 23

When materiel is authorized under a 

PIID call/order number (F in 9th

position), provide the last eight 

positions.

 20 Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 1014.

21 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A. 22 Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 

1014.

23 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
Enclosure 2, ADC 1161A

Page 6

AP3.9. APPENDIX 3.9

SOURCE OF SUPPLY CANCELLATION

(DIRECT DELIVERY FROM PROCUREMENT)

Procurement Instrument 

Identifier (PIID) 

Procurement Instrument 

Identification Number

(51-63) Enter basic PIIDPIIN.

24 Enter the PIID 

call/order number (F in 9th position) if 

applicable.

AP3.11. APPENDIX 3.11

DIRECT DELIVERY NOTICE

Procurement Instrument 

Identifier

(PIID)Identification

60-72 Enter the basic PIIDPIIN.

25 Enter the PIID 

call/order number (F in 9th position) if 

applicable.

Call/Order Serial Number 73-76 Enter the legacy four-position call/order 

serial number associated with the PIIN, if 

applicable; otherwise; leave blank.

 24 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A. 25 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
Enclosure 2, ADC 1161A

Page 7

AP3.22. APPENDIX 3.22

DOCUMENT MODIFIER

(INVENTORY CONTROL POINT TO PROCUREMENT)

Procurement Instrument 

Identifier (PIID)Procurement 

Instrument Identification 

Number or Procurement 

Request Number

51-69 Enter the PIID when available, otherwise 

enter the PIIN or PRN. Enter the PIID 

call/order number (F in 9th position) if 

applicable.

Procurement Instrument 

Identifier (PIID)Procurement 

Instrument Identification 

Number

(51-63) Enter the PIID PIIN.

26 Enter the PIID 

call/order number (F in 9th position) if 

applicable.

AP3.23. APPENDIX 3.23

PASSING ORDER

Contract Call/Order Number 69-72 If required by the Component contracts, 

enter the appropriate contract legacy fourposition call/order number associated 

with the PIIN; otherwise leave blank.

Procurement Instrument 

Identifier (PIID)Contract 

Identification

73-80 Enter the last eight positions of the PIID

procurement instrument identification 

number (PIIN).. This entry is 

mandatory.27,28 When materiel is 

authorized under a PIID call/order 

number (F in 9th position) provide the 

last eight positions.

 26 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A. 27 Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 1014.

28 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
Enclosure 2, ADC 1161A

Page 8

AP3.24. APPENDIX 3.24

REFERRAL ORDER/LATERAL REDISTRIBUTION 

ORDER FOR RETAIL ASSETS

Contract Call/Order Number 69-72 If required by the Component contracts, 

enter the appropriate contract legacy fourposition call/order number associated with 

the PIIN; otherwise leave blank.

Procurement Instrument 

Identifier (PIID)Contract 

Identification

73-80 Enter the last eight positions of the

PIIDprocurement instrument identification 

number (PIIN). This entry is mandatory.

29, 30

When materiel is authorized under a PIID 

call/order number (F in 9th position) 

provide the last eight positions.

 29 Abbreviated contract number is mandatory, regardless of inclusion of the MDN. Refer to ADC 1014.

30 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
Enclosure 3, ADC 1161A

Page 1

Enclosure 3, DLM 4000.25-2, Military Standard Transaction Reporting and 

Accountability Procedures (MILSTRAP)

Revise the MILSTRAP manual as shown

ABBREVIATIONS AND ACRONYMS

PIID Procurement Instrument Identifier

DEFINITIONS AND TERMS

PROCUREMENT INSTRUMENT IDENTIFICATION NUMBER (PIIN). Identifies 

legacy contractual documents. Use of the PIIN is authorized in the DLMS and 

legacy MILSTRIP/MILSTRAP procedures, pending transition to the procurement 

instrument identifier (PIID). 

PROCUREMENT INSTRUMENT IDENTIFIER (PIID). A standard unique identifier 

for a solicitation, contract, agreement, or order and related procurement 

instruments, see DFARS Subpart 204.16. The new identifier for call/order number 

under the PIID rules is designated by F in the 9th position. However, there is an 

exception authorized for DLA procurement instruments supporting FEDMALL to 

identify the delivery/call order using an M in the 9th position. The PIID call/order 

number is always treated as a contractual agreement even when the base 

contract number is available. If a base PIID contract number and PIID call/order 

number are available, provide the PIID call/order number (F or M PIID) only. 

SUPPLEMENTARY PROCUREMENT INSTRUMENT IDENTIFIER (Supplementary 

PIID). Identify amendments or modifications to the procurement instrument. The 

Supplementary PIID must be used in conjunction with the PIID.

CALL/ORDER NUMBER. A release against a basic contract. This is a legacy four 

character field (that must be used in conjunction with a legacy PIIN). The new 

identifier for call/order number under the PIID rules is designated by F or M in the 

9th position of the PIID and is treated as a contractual document. See PIID 

definition. 
Enclosure 3, ADC 1161A

Page 2

AP3.1. APPENDIX 3.1

MATERIEL RECEIPT -

PROCUREMENT INSTRUMENT SOURCE

Procurement 

Instrument Identifier

(PIID) Identification 

Number or Due-In 

Document Number 

30-43 Enter the PIID31 PIIN, or the applicable 13-

position PIID call/order number 

(identified by F in the 9th position) in 

record positions 30-42 and leave record 

position 43 blank or, for intra-Component 

use only, enter or perpetuate the controlling 

document number in record positions 30-43.

Procurement 

Instrument Identifier

(PIID) Procurement 

Instrument 

Identification Number

(30-42) Enter (or perpetuate) the PIIDprocurement 

instrument identification number or the 

applicable 13-position PIID call/order 

number (identified by F in the 9th

position).

32

Call/Order Serial

Number

77-80 Enter applicable legacy four-position

call/order serial number associated with 

the PIIN; otherwise, leave blank.

AP3.8. APPENDIX 3.8 

INVENTORY ADJUSTMENT – DUAL 

(CONDITION/PURPOSE TRANSFER)

Document Number 30-43 For reclassification of previously suspended 

receipts, enter document number under 

which the materiel originally was received. 

For other adjustments, enter appropriate 

document number.

33

 31 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A. 32 Ibid. 33 For intra-DLA use only, if DAC is applicable to Supply Condition Code (SCC) L, enter the PIID PIIN in 

rp 30-42.
Enclosure 3, ADC 1161A

Page 3

AP3.10. APPENDIX 3.10

DUE-IN –PROCUREMENT INSTRUMENT SOURCE

Procurement 

Instrument Identifier

(PIID) Identification 

Number or Due-In 

Document Number

30-43

Procurement 

Instrument Identifier

(PIID) Procurement

Instrument 

Identification Number

(30-42) Enter (or perpetuate) the PIID procurement 

instrument identification number or the 

applicable 13-position call/order number 

(identified by F in the 9th position).

34

Call/Order Serial

Number

77-80 Enter applicable legacy four-position

call/order serial number associated with the 

PIIN; otherwise, leave blank.

AP3.18. APPENDIX 3.18

LOGISTICS REASSIGNMENT DELINQUENT DUE-IN 

FOLLOW-UP

Various 30-50 Perpetuate from DIC DDX or DFX 

memorandum due-in

Call/Order Serial

Number

51-54 Enter legacy four-position call/order serial

number associated with the PIIN, if 

applicable; otherwise, leave blank.

 34 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
Enclosure 3, ADC 1161A

Page 4

AP3.19. APPENDIX 3.19

LOGISTICS REASSIGNMENT DELINQUENT DUE-IN 

RESPONSE

Various Fields. 30-50 In reply to follow-up, perpetuate from DIC 

DLC transaction. When providing revised 

due-in EDDs as they occur, perpetuate data 

provided in DIC DDX or DFX memorandum 

due-in.

Call/Order Serial

Number

51-54 Enter legacy four-position call/order serial

number associated with the PIIN, if 

applicable; otherwise, leave blank.

AP3.20. APPENDIX 3.20

LOGISTICS REASSIGNMENT DUE-IN 

RECONCILIATION REQUEST

Various Fields. 30-50 Perpetuate from the DIC DDX or DFX 

memorandum due-in.

Call/Order Serial

Number

51-54 Enter legacy four-position call/order 

serial number associated with the PIIN, if 

applicable; otherwise, leave blank.

AP3.21. APPENDIX 3.21

Logistics Reassignment Due-In Reconciliation 

Response

Various Fields. 30-50 Perpetuate from the DIC DLE request. If 

no request received, perpetuate from DIC 

DD_ or DF_ due-in record.

Call/Order Serial

Number

51-54 Enter legacy four-position call/order serial

number associated with the PIIN, if 

applicable; otherwise, leave blank.
Enclosure 3, ADC 1161A

Page 5

AP3.26. APPENDIX 3.26

LOGISTICS REASSIGNMENT CONTRACT HISTORY 

DATA

RECORD 1

Package Sequence Number 21-23 Enter A01 indicating first record for Number

this procurement instrument

PIIN/supplementary PIIN CLIN. If record 

position 24 = N, enter Z01.

Procurement Instrument 

Identifier (PIID) 

Procurement Instrument 

Identification Number

25-37 Enter the PIID PIIN or the applicable 13-

position call/order number (identified by F 

in the 9th position).

Supplementary Procurement 

Instrument Identifier (PIID) 

Identification Number

38-43 Enter the six-position supplementary PIID

PIIN; otherwise, leave blank.

RECORD 2

Package Sequence Number 21-23 Enter A02 indicating second record for this 

procurement instrument PIIN/supplementary 

PIIN /CLIN.

Procurement Instrument 

Identifier (PIID) 

Procurement Instrument 

Identification Number

25-37 Enter the PIID PIIN or the applicable 13-

position call/order number (identified by F in 

the 9th position).

Supplementary Procurement 

Instrument Identifier (PIID) 

Identification Number

38-43 Enter the six-position supplementary PIID

PIIN; otherwise, leave blank.
Enclosure 3, ADC 1161A

Page 6

RECORD 3 

Package Sequence Number 21-23 Enter A03 indicating third record for this

procurement instrument PIIN/supplementary 

PIIN /CLIN.

Procurement Instrument 

IdentifierProcurement 

Instrument Identification 

Number

25-37 Enter the PIID PIIN or the applicable 13-

position call/order number (identified by F in 

the 9th position).

Supplementary Procurement 

Instrument Identifier (PIID) 

Identification Number

38-43 Enter the six-position supplementary PIID

PIIN; otherwise, leave blank.

RECORD 4

Package Sequence Number 21-23 Enter Z04 indicating last record for this 

Procurement Instrument PIIN/supplementary 

PIIN /CLIN.

Procurement Instrument 

IdentifierProcurement 

Instrument Identification 

Number

25-37 Enter the PIID PIIN or the applicable 13-

position call/order number (identified by F in 

the 9th position).

Supplementary Procurement 

Instrument Identifier (PIID) 

Identification Number

38-43 Enter the six-position supplementary PIID

PIIN; otherwise, leave blank.
Enclosure 3, ADC 1161A

Page 7

AP3.38. APPENDIX 3.38

PRE-POSITIONED MATERIEL RECEIPT –

PROCUREMENT INSTRUMENT SOURCE

Procurement 

Instrument Number or 

Due-In Document 

Number

30-43

Procurement 

Instrument Identifier 

(PIID) Source

(30-42) Enter (or perpetuate) the PIID procurement 

instrument number or the applicable 13-

position call/order number (identified by 

F in the 9th position)35 .

Call/Order Serial

Number

77-80 Enter applicable legacy four-position

call/order serial number associated with 

the PIIN; otherwise, leave blank.

AP3.40. APPENDIX 3.40

MATERIEL RECEIPT FOLLOW-UP

PROCUREMENT INSTRUMENT SOURCE

Procurement Instrument 

Identifier (PIID) 

Identification Number

30-42 Enter applicable PIID PIIN or the 

applicable 13-position call/order number 

(identified by F in the 9th position).36

Call/Order Serial

Number 

77-80 Enter applicable legacy four-position

call/order serial number associated with 

the PIIN; otherwise, leave blank.

 35 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A. 36 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
Enclosure 3, ADC 1161A

Page 8

AP3.42. APPENDIX 3.42

REPLY TO MATERIEL RECEIPT FOLLOW-UP 

PROCUREMENT INSTRUMENT SOURCE

Procurement 

Instrument 

Identifier(PIID)Procure

ment Instrument 

Identification Number

30-42 Enter applicable PIID PIIN or the 

applicable 13-position call/order number 

(identified by F in the 9th position).

37

Call/Order Serial

Number

77-80 Enter applicable legacy four-position

call/order serial number associated with 

the PIIN; otherwise, leave blank.

 37 Use the legacy PIIN pending transition to the PIID. Refer to ADC 1161A.
Enclosure 4, ADC 1161A

Page 1

Enclosure 4, Changes to DLMS Implementation Conventions

# Location DLMS 511M Requisition Modification (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 6 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract 

Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/N901/020

Data Element,

128 Reference 

Identification 

Qualifier

Modify existing DLMS note for code CT:

CT Contract Number

DLMS Note: Use to identify the procurement instrument identifier 

(PIID) of the ordering instrument contract number or obligation 

authority number associated with the requisition, when available the 

FedMall/part numbered catalog order.

Implement PIID for 

contract number and 

call/order number.

Staffing Note: Note

was modified to 

align with the 

existing note in the 

same location in the 

511R. Components 

review and advise if 

eliminating any of 

the words showing a 

double strike thru 

causes a problem.

3. 2/GF01/070

Data Element 

128 Reference 

Identification 

Qualifier

Modify existing the existing DLMS Note 1 for code CT and W3: 

C7 Contract Line Item Number

DLMS Note: 1. Use to associate a Contract Line Item Number with 

the PIID Contract Number.

2. Use in CAV transactions or as directed by the authorizing 

Service/Agency.

3. When both the CLIN and the MDN are applicable, identify the 

CLIN in GF09. Refer to ADC 1014A.

W3 Manufacturing Directive Number

DLMS Note: 1. Use to associate a Contract Line Item Number with 

the PIID Contract Number.

2. Use as directed by the authorizing Service/Agency. Refer to ADC 

1014.

3. When both the CLIN and the MDN are applicable, identify the 

CLIN in GF09. Refer to ADC 1014A.

Implement PIID for 

contract number and 

call/order number..
Enclosure 4, ADC 1161A

Page 2

# Location DLMS 511M Requisition Modification (Version 4010)

Revision

Reason

4. 2/GF03/070

Data Element, 

367 Contract 

Number

Add new DLMS Note 3 and modify existing DLMS Notes: 

DLMS Note: 1. Must use to identify the PIIDcontract number for 

GFM. Refer to ADC 1161.

2. Use as directed by the authorizing Service/Agency to identify the 

PIIDcontract number authorizing the contractor to purchase materiel 

from a Government source. Use the legacy procurement 

instrument identification number (PIIN) pending transition to the 

PIID. When GFM is authorized under a PIID call/order number 

(F in 9th position), provide the value in the PIID field.

4. Fully compliant DLMS applications must support identification of 

the DFARS thirteen-position PIIDcontract number, rather than the 

abridged contract number authorized for legacy MILSTRIP. Refer 

to ADC 1014.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

5. 2/GF07/070

Data Element 

328, Release 

Number

Remove Federal note; Add new DLMS notes 1 and 2 and renumber 

existing note: 

Federal Note: Use to identify the call or order number, or the call or 

order number including the respective call or order modification, as 

applicable, when using GF03.

DLMS Note: 

1. Use to identify the legacy four-position call/order number

associated with the legacy PIIN. 

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to GF03. Refer to ADC 1161.

3. Use as directed by the authorizing Service/Agency.

Implement PIID for 

contract number and 

call/order number.

6. 2/LIN02/0100

Data Element,

235 

Product/Service 

ID Qualifier

Remove Federal note; Add new DLMS note as follows:

CR Contract Number 

Federal Note: Use when specifying a Federal Supply Schedule 

contract number. 

DLMS Note: Use to identify the PIID of the Federal Supply 

Schedule or related instrument when ordering nonstandard 

materiel. When procurement is authorized under a PIID 

call/order number (F in 9th position), provide the value in the PIID 

field.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 3

# Location DLMS 511R Requisition (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 6 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/N901/020

Data Element, 

128 Reference 

Identification 

Qualifier

Modify existing DLMS note for code CT:

CT Contract Number

DLMS Note: Use to identify the procurement instrument identifier

(PIID) of the ordering instrument/procurement instrument 

identification number (PIIN)contract number associated with the 

DoD EMALL the FedMall/part numbered catalog order.

Implement PIID for 

contract number and 

call/order number.

3. 2/GF01/070

Data Element 

128 Reference 

Identification 

Qualifier

Modify existing the existing DLMS Note 1 for code C7 and W3: 

C7 Contract Line Item Number

DLMS Note: 1. Use to associate a Contract Line Item Number with 

the PIIDContract Number.

2. Use in CAV transactions or as directed by the authorizing 

Service/Agency.

3. When both the CLIN and the MDN are applicable, identify the 

CLIN in GF09. Refer to ADC 1014A.

W3 Manufacturing Directive Number

DLMS Note: 1. Use to identify the MDN, in addition to the 

PIIDContract Number.

2. Use as directed by the authorizing Service/Agency. Refer to ADC 

1014.

3. When both the CLIN and the MDN are applicable, identify the 

CLIN in GF09. Refer to ADC 1014A.

Implement PIID for 

contract number and 

call/order number.

4. 2/GF03/070

Data Element,

367 Contract 

Number

Modify existing DLMS notes 1-3.

DLMS Note: 1. Must use to identify the PIIDcontract number for 

GFP. Refer to ADC 1161.

2. Use as directed by the authorizing Service/Agency to identify the 

PIIDcontract number authorizing the contractor to purchase materiel 

from a Government source. Use the legacy procurement instrument 

identification number (PIIN) pending transition to the PIID. When 

GFP is authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. Refer the ADC 1161.

3. Fully compliant DLMS applications must support identification of 

the DFARS thirteen-position PIIDcontract number, rather than the 

abridged contract number authorized for legacy MILSTRIP. Refer to 

ADC 1014 and ADC 1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).
Enclosure 4, ADC 1161A

Page 4

# Location DLMS 511R Requisition (Version 4010)

Revision

Reason

5. 2/GF07/70

Data Element,

328 Release 

Number

Remove Federal note; Add new DLMS notes 1 and 2, renumber 

existing DLMS note as follows:

Federal Note: Use to identify the call or order number, or the call or 

order number including the respective call or order modification, as 

applicable, when using GF03.

DLMS Note: 1. Use to identify the legacy four position call/order 

number associated with the PIIN.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to GF03. Refer to ADC 1161.

3. Use as directed by the authorizing Service/Agency.

Implement PIID for 

contract number and 

call/order number.

6. 2/LIN02/100

Data Element,

235 Product/

Service ID 

Qualifier

Remove Federal note; Add new DLMS notes as follows:

CR Contract Number

Federal Note: Use when specifying a Federal Supply Schedule 

contract number

DLMS Note: 1. Use to identify the PIID of the Federal Supply 

Schedule or related instrument when ordering nonstandard materiel.

When procurement is authorized under a PIID call/order number (F 

in 9th position), provide the value in the PIID field. Refer to ADC 

1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 5

# Location DLMS 517G Government Furnished Materiel (GFM) Validation

(Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 4 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/GF01/060

Data Element, 

128 Reference 

Identification 

Qualifier

Modify existing the existing DLMS Note 1 for code C7 and W3: 

C7 Contract Line Item Number

DLMS Note: 1. Use to associate a Contract Line Item Number 

(CLIN) with the procurement instrument identifier (PIID)Contract 

Number.

2. Use in CAV transactions or as directed by the authorizing 

Service/Agency.

3. When both the CLIN and the MDN are applicable, identify the 

CLIN in GF09. Refer to ADC 1014A.

W3 Manufacturing Directive Number

DLMS Note: 1. Use to identify the MDN, in addition to the 

PIIDcontract number.

2. Use as directed by the authorizing Service/Agency. Refer to ADC 

1014.

3. When both the CLIN and the MDN are applicable, identify the 

CLIN in GF09. Refer to ADC 1014A.

Implement PIID for 

contract number and 

call/order number.

3. 2/GF03/060

Data Element,

367 Contract 

Number

Revise DLMS notes 1-3:

DLMS Note: 1. Must use to identify the PIIDcontract number. Use 

the legacy procurement instrument identification number (PIIN)

pending transition to the PIID. When GFM is authorized under a 

PIID call/order number (F in 9th position), provide the value in the 

PIID field. Refer to ADC 1161. 

2. MCA validation for GFM and CFM requisitions is required under 

DLMS procedures. Refer to ADC 1123. Pending full implementation, 

use as directed by the authorizing Service to identify the PIIDcontract 

number authorizing the contractor to purchase materiel from a 

Government source of supply.

3. Fully compliant DLMS applications must support identification of 

the DFARS thirteen-position PIIDcontract number, rather than the 

abridged contract number authorized for legacy MILSTRIP. Refer to 

ADC 1014 and ADC 1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).
Enclosure 4, ADC 1161A

Page 6

# Location DLMS 517G Government Furnished Materiel (GFM) Validation

(Version 4010)

Revision

Reason

4. 2/GF07/060

Data Element, 

328 Release 

Number

Revise DLMS notes 1, add new note 2 and renumber existing DLMS 

note:

DLMS Note: 1. Use to identify the legacy four position call/ or order 

number associated with the PIIN, or the call or order number 

including the respective call or order modification number when using 

GF03. 

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to GF03. Refer to ADC 1161. 

3. Use as directed by the authorizing Service/Agency.

Implement PIID for 

contract number and 

call/order number.

# Location DLMS 527D 

Due-in/Advance Receipt /Due Verification (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 6 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. CS/020

Segment 

Contract 

Summary

Remove Federal notes: Add new DLMS notes 1 and 2, renumber 

existing DLMS note.

Federal Note:

1. Must use for all procurement source transactions. Identifies the 

contract number (when awarded) or the procurement request 

number(when no contract has been awarded).

2. Must use either CS01 or CS06 (but not both).

DLMS Note:

1. Must use for all procurement source transactions. Identifies the 

procurement instrument identifier (PIID) (when awarded) or the 

procurement request number (when no contract has been awarded).

2. Must use either CS01 or CS06 (but not both).

3. Do not use for MRA or inquiries on delinquent MRA

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 7

# Location DLMS 527D 

Due-in/Advance Receipt /Due Verification (Version 4010)

Revision

Reason

3. 2/CS01/020

Data Element,

367 Contract 

Number

Remove Federal note; Add new DLMS note:

Federal Note: Use to identify the contract number.

DLMS Note: Use to identify the PIID. Use the legacy procurement 

instrument identification number (PIIN) pending transition to the 

PIID. When procurement is authorized under a PIID call/order 

number (F in 9th position), provide the value in the PIID field. Refer 

to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

4. 2/CS02/020

Data Element 

327 Change 

Order 

Sequence 

Number

Remove Federal note; Add new DLMS Note

Federal Note: Use to identify a modification number to the cited 

contract.

DLMS Note: Use to identify a modification number to the cited 

procurement instrument. This is the Supplementary Procurement

Instrument Identifier (Supplementary PIID). Refer to ADC 1161.

Implement PIID for 

contract 

modification

5. 2/CS03/020

Data Element, 

328 Release 

Number

Remove Federal note; Add new DLMS note 1, 2 and 3:

Federal Note: Use to identify the call or order number, or the call or 

order number including the respective call or order modification, as 

applicable.

DLMS Note:

1. Use to identify the legacy four positon call/order number

associated with the PIIN.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

6. 2.GF/060

Segment GF –

Furnished 

Goods and 

Services 

Revise DLMS Note 2:

1. Use only with non-procurement source due-in transactions. Do not 

use when reversing a transaction.

2. Use either the Manufacturing Directive Number (MDN) or contract 

number procurement instrument identifier (PIID) (but not both) 

associated with a furnished materiel transaction to reference the 

associated contract. Identify the controlling transaction number in the 

2/N9/030 segment.

3. Segment is a DLMS enhancement. See introductory DLMS note 4a.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 8

# Location DLMS 527D 

Due-in/Advance Receipt /Due Verification (Version 4010)

Revision

Reason

7. 2/GF03/060

Data Element

367, Contract 

Number

Add new DLMS note 1 and renumber existing DLMS note:

Contract Number

DLMS Note: 1. Use to identify the PIID. Use the legacy PIIN 

pending transition to the PIID. When GFM authorized under a 

PIID call/order number (F in 9th position), provide the value in the 

PIID field. Refer to ADC 1161.

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

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

8. 2/GF07/060

Data Element, 

328 Release 

Number

Remove Federal note; Add new DLMS notes 1, 2 and 3, renumber 

existing note:

Federal Note: Use to identify the call or order number, or the call or 

order number including the respective call or order modification, as 

applicable, when using GF03.

DLMS Note: 

1. Use to identify the legacy four position call/order number

associated with the PIIN.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to GF03. Refer to ADC 1161.

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

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 9

# Location DLMS 527R 

Receipt, Inquiry, Response and MRA (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 7 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/020

Data 

Element, 367 

Contract 

Number

Remove Federal note; Add new DLMS note:

Federal Note: Use to identify the contract number.

DLMS Note: Use to identify the procurement instrument 

identifier (PIID). Use the legacy procurement instrument 

identification number (PIIN) pending transition to the PIID. When 

procurement is authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. Refer to ADC 1161

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2.CS02/020

Data Element 

327 Change 

Order 

Sequence 

Number

Remove Federal note; Add new DLMS note:

Federal Note: Use to identify a modification number to the cited 

contract.

DLMS Note: Use to identify a modification number to the cited 

procurement instrument. This is the Supplementary Procurement 

Instrument Identifier (Supplementary PIID). Refer to ADC 1161.

Implement PIID for 

contract 

modification

4. 2/CS03/020

Data 

Element, 328 

Release 

Number

Remove Federal note; Add new DLMS notes:

Federal Note: Use to identify the call or order number, or the call or 

order number including the respective call or order modification, as 

applicable.

DLMS Note:

1. Use to identify the legacy four positon call/order number

associated with the PIIN.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 10

# Location DLMS 527R 

Receipt, Inquiry, Response and MRA (Version 4010)

Revision

Reason

5. 2/GF03/060

Data Element

367, Contract 

Number

Modify DLMS Note 1`and add DLMS Note 2:

Contract Number

DLMS Note: 1. Must use with MRA and Receipt transactions 

associated with materiel issued to contractors as GFM, and with MRA 

associated with CFM, to cite the PIIDnumber of the DoD 

procurement instrumentcontract which authorized the contractor to 

receive GFM or CFM as applicable. Use the legacy PIIN pending 

transition to the PIID. Establishes an audit trail between the MRA or 

Receipt and the procurement instrumentcontract. Refer to ADC 

1161.

2. When GFM is authorized under a PIID call/order number (F in 

9th position), provide the value in the PIID field.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

6. 2/GF07/060

Data 

Element, 328 

Release 

Number

Remove Federal note; Add new DLMS notes1 and 2:

Federal Note: Use to identify the call or order number, or the call or 

order number including the respective call or order modification, as 

applicable, when using GF03.

DLMS Note:

1. Use to identify the legacy four position call/order number

associated with the PIIN.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to GF03. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

7. 2/N901/090

Data 

Element, 128 

Reference 

Identification 

Qualifier

Revise existing note for code CT and add note 2: 

CT Contract Number

DLMS Note: 1. Use with nonprocurement source transactions when a 

procurement instrument identifier (PIID)contract number is needed 

in addition to the transaction number for transaction tracking purposes. 

Use the legacy PIIN pending transition to the PIID. Identify the 

controlling transaction number in 2/N9/030.

2. When procurement is authorized under a PIID call/order number 

(F in 9th position), provide the value in the PIID field. Refer to ADC 

1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

8. 2/N901/090

Data 

Element, 128 

Reference 

Identification 

Qualifier

Revise existing note for code OR and add new DLMS Note 2:

OR Order/Paragraph Number

DLMS Note: 1. For use with CAV receipt, to identify the legacy 4-

position call/order number associated with a PIINcontract number. 

Authorized DLMS migration enhancement for CAV use. See DLMS 

introductory note 5g.

2. Do not use for the PIID call/order number. Refer to ADC 1161

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 11

# Location DLMS 536L 

Logistics Reassignment Management Data (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 5 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract 

Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/030

Data Element 

367 Contract 

Number

Remove Federal note and revise DLMS note 1:

Federal Note: Must use in every 2/HL/010 contract and quality 

characteristics loop to identify the contract number.

DLMS Note: 1. Must use with the 2/HL/010 contract loop to 

identify the procurement instrument identifier (PIID). When 

procurement is authorized under a PIID call/order number (F in 

9th position), provide the value in the PIID field. Refer to ADC 

1161.

2. CS01 is optional to accommodate DLSS to DLMS conversion. 

The 536L is intended to accommodate all MILSTRAP DI Codes 

DLS through DLX transaction data for a given NSN and review 

period, in a single 536L transaction. CS01 would be a “must use” in 

this situation. However during DLSS to DLMS conversion some 

systems may be converting each individual MILSTRAP transaction 

to individual 536L transactions, in which case CS01 may not 

always be required.

Implement PIID for 

contract number and 

call/order number.

3. 2/CS03/030

Data Element, 

328 Release 

Number

Remove Federal note; Add new DLMS note:

Federal Note: Use in the 2/HL/010 contract loop to identify the call 

or order number, including the respective call or order 

modification, as applicable.

DLMS Note: 1. Use in the 2/HL/010 contract loop to identify the 

six- position Supplementary PIID when applicable. Refer to ADC 

1161.

Includes administrative 

update to correct CS03 

note to accurately reflect 

corresponding legacy DIC 

DLW, rp 38-43, 

requirement for 

supplementary PIIN (now 

PIID) rather than 

call/order number. 

During the PDC 1161 

review process, it was 

noted that this a deviation 

from the standardized 

mapping decision but this 

administrative update is a 

more logical solution than 

DAAS and Component 

systems being required to 

modify their system maps.
Enclosure 4, ADC 1161A

Page 12

# Location DLMS 536L 

Logistics Reassignment Management Data (Version 4010)

Revision

Reason

4. 2/CON01/070

Data Element 

128, Reference 

Identification 

Qualifier

Revised DLMS notes for existing code CT:

CT Contract Number

DLMS Note: Use to identify the term or requirements contract 

indicator number. Enter Y (yes) if a current term/requirement 

type contract is available for placement of purchase orders for 

stock replenishment and/or direct delivery to requisitioners; 

otherwise, leave blank.

Clarify usage of CT 

during review of PDC 

1198 (not related to 

PDC 1161 PIID 

changes).

# Location DLMS 567C Contract Completion Status 

(DLMS Contract Completion Statement/Unclosed Contract 

Status/Contract Close-out Extension) (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 7 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 1/CS/050 Revise Seg2ment Level notes as follows:

DLMS Note:

1. Use this segment to identify the procurement instrument identifier 

(PIID)) contract number, i.e., the Procurement Instrument 

Identification Number (PIIN); and, if applicable, the contract

modification number; the call or order number, i.e., the 

Supplementary PIIN (SPIIN); or the call/ or order number including 

the respective call or order number modification, as applicable.

2. There can only be one occurrence of this loop.

Implement PIID for 

contract number and 

call/order number.

3. 2/CS01/050

Data Element, 

367 Contract 

Number

Revise the existing DLMS Note.

DLMS Note: Use to identify the PIID procurement instrument 

identification number (PIIN) of the procurement instrument being 

reported. Use the legacy procurement instrument identification 

number (PIIN) pending transition to the PIID. When procurement 

is authorized under a PIID call/order number (F in 9th position), 

provide the value in the PIID field. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).
Enclosure 4, ADC 1161A

Page 13

# Location DLMS 567C Contract Completion Status 

(DLMS Contract Completion Statement/Unclosed Contract 

Status/Contract Close-out Extension) (Version 4010)

Revision

Reason

4. 2/CS02/050

Data Element 

327 Change 

Order 

Sequence 

Number 

Revise existing DLMS Note:

DLMS Note: Use, as applicable, to identify the six position contract 

modification number of the procurement instrument being reported.

Use to identify a modification number to the cited procurement 

instrument. This is the Supplementary Procurement Instrument 

Identifier (Supplementary PIID). Refer to ADC 1161..

Implement PIID for 

contract number and 

call/order number.

5. 2/CS03/050

Data Element, 

328 Release 

Number

Delete the existing DLMS Note and add new notes 1 and 2.

DLMS Note: 1. Use to identify the four-position supplemental 

procurement instrument identification number (SPIIN) of the 

call/order being reported and when applicable, its two-position 

modification number.

1. Use to identify the legacy four positon call/order number

associated with the PIIN.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for

contract number and 

call/order number.

# Location DLMS 810L Logistics Bill (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 7 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number 

and call/order 

number

2. 2/REF01/120

Data Element, 

235 

Product/Service 

ID Qualifier

Revise the existing DLMS Note for CT:

CT Contract Number

DLMS Note: Use to identify the contract procurement instrument 

identifier (PIID) associated with this invoice billing line. When 

procurement is authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. Refer to ADC 1161.

Implement PIID for 

contract number and

call/order number
Enclosure 4, ADC 1161A

Page 14

# Location DLMS 812L

Logistics Bill Adjustment Request Reply (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 5 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number 

and call/order 

number

2. 2/LIN02/170

Data Element, 

235 

Product/Service 

ID Qualifier

Revise existing DLMS Note to existing code CR:

CR Contract Number

DLMS Note: Use to identify when specifying the procurement 

instrument identifier (PIID) for of a Federal Supply Schedule 

contract number or related instrument used to order nonstandard 

materiel. When procurement is authorized under a PIID call/order 

number (F in 9th position), provide the value in the PIID field.

Refer to ADC 1161.

Implement PIID for 

contract number and

call/order number

# Location DLMS 812R Logistics Bill Adjustment Request (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 6 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number 

and call/order 

number

2. 2/LIN02/0170

Data Element, 

235 

Product/Service 

ID Qualifier

Remove existing DLMS Note to existing code CR:

CR Contract Number

DLMS Note: Use to identify when specifying the procurement 

instrument identifier (PIID) for of a Federal Supply Schedule 

contract number or related instrument used to order nonstandard 

materiel. When procurement is authorized under a PIID call/order 

number (F in 9th position), provide the value in the PIID field.

Refer to ADC 1161.

Implement PIID for 

contract number and

call/order number
Enclosure 4, ADC 1161A

Page 15

# Location DLMS 824R Reject Advice (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 7 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/OTI02/010

DLMS Data 

Element, 128 

Reference 

Identification 

Qualifier

Add DLMS note to CT:

CT Contract Number

DLMS Note: Use to identify the procurement instrument identifier 

(PIID). Use the legacy procurement instrument identification 

number (PIIN) pending transition to the PIID. When procurement 

is authorized under a PIID call/order number (F in 9th position), 

provide the value in the PIID field. Refer to ADC 1161.

CT- Clarification 

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/REF04-01/020

Data Element, 

128 Reference 

Identification 

Qualifier

Revise existing DLMS Note and add DLMS Note 2

OQ Order Number

DLMS Note: Use to identify the legacy four position call/order 

number associated with the CLIN in 2/REF01/020 Code C7.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to OTI02 Code CT. Refer to ADC 1161.

Clarify that this is 

the legacy call/order 

number

# Location DLMS 842A/R 

Standard Supply Discrepancy Report (SDR) Reply (Version 4030)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 4 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/0750

Data Element, 

367 Contract 

Number

Add new DLMS note and in the existing note, revise field length to 

accommodate Federal procurement instrument identifiers (PIID):

Contract Number

DLMS Note: 1. Use to identify the procurement instrument 

identifier (PIID). Use the legacy procurement instrument 

identification number (PIIN) pending transition to the PIID. When 

procurement is authorized under a PIID call/order number (F or M 

in 9th position), provide the value in the PIID field.

2. WebSDR field length = 13 17

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).
Enclosure 4, ADC 1161A

Page 16

# Location DLMS 842A/R 

Standard Supply Discrepancy Report (SDR) Reply (Version 4030)

Revision

Reason

3. 2/CS03/0750

Data Element, 

328 Release 

Number

Modify DLMS Notes 1 and add DLMS Note 2.

Release Number

DLMS Note:

1. Use to identify the legacy four-position call/ or order number

associated with the PIIN if applicable.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID 

contract number and 

call/order number.

# Location DLMS 842AW Standard Supply Discrepancy Report (SDR), 

Follow-up, Correction, Cancellation, & Reconsideration Request

(Version 4030) 

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 6 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2CS01/0750

Data Element, 

367 Contract 

Number

Add DLMS Note

Contract Number

DLMS Note: Use to identify the procurement instrument identifier 

(PIID). Use the legacy procurement instrument identification 

number (PIIN) pending transition to the PIID. When a contract is 

issued under a PIID call/order number (F or M in 9th position), 

provide the value in the PIID field. 

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/CS03/0750

Data Element, 

328 Release 

Number

Add new DLMS notes 2 and 3:

DLMS Note:

1.Use to identify the call or order number if applicable.

2. Use to identify the legacy four-position call/order number

associated with the PIIN. 

3. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 17

# Location DLMS 842C/I Stock Screening Request (Version 4030)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 3 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/0750

Data Element, 

367 Contract 

Number

Revise notes 1 and 2:

DLMS Note: 1. Only one procurement instrument identifier (PIID)

contract number may be identified per stock screening request. Use the

legacy procurement instrument identification number (PIIN)

pending transition to the PIID. When procurement is authorized 

under a PIID call/order number (F or M in 9th position), provide the 

value in the PIID field if screening for a specific call/order. 

Otherwise use the base PIID. Refer to ADC 1161.

2. Field length =1317

Field length revised 

to accommodate 

Federal PIID.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/CS03/0750

Data Element, 

328 Release 

Number

Modify existing DLMS Note 1, add new DLMS Note 2, update and 

renumber existing Note 2 to Note 3:

DLMS Note: 

1. Used to identify the legacy four position call/ or order number

associated with the PIIN. for the contract.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

3. Field length = 4

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 18

# Location DLMS 842C/R Stock Screening Reply (Version 4030)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 3 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/0750

Data Element, 

367 Contract 

Number

Add DLMS Note:

Contract Number

DLMS Note: Use to identify the procurement instrument identifier 

(PIID). Use the legacy procurement instrument identification

number (PIIN) pending transition to the PIID. When procurement 

is authorized under a PIID call/order number (F in 9th position), 

provide the value in the PIID field if screening for a specific 

call/order. Otherwise use the base PIID. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/CS03/0750

Data Element, 

328 Release 

Number

Modify DLMS note 1 and add new DLMS note 2.

DLMS Note:

1. Used to identify the legacy four-position call/ or order number

associated with the PIIN for the contract.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 19

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

Exchange (Version 4030) Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 8 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/0750

Data Element, 

367 Contract 

Number

Modify existing DLMS Note:

Contract Number

DLMS Note: 1. Used to identify the procurement instrument 

identifier (PIID) contract number under which the nonconforming 

materiel was procured, i.e., N0010492340001. Use the legacy

procurement instrument identification number (PIIN) pending 

transition to the PIID. When procurement is authorized under a 

PIID call/order number (F in 9th position), provide the value in the 

PIID field.

Example provided 

was not properly 

constructed; no 

example is required. 

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/CS03/0750

Data Element, 

328 Release 

Number

Revise existing DLMS Note and add new notes 2:

DLMS Note: 1. Use to identify the Contract Number’s legacy fourposition call/ or order Number associated with the PIIN, i.e., 0012.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 20

# Location DLMS 842S/Q Storage Quality Control Report (Version 4030)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 5 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/0750

Data Element, 

367 Contract 

Number

Add DLMS Note:

Contract Number

DLMS Note: Use to identify the procurement instrument identifier 

(PIID). Use the legacy procurement instrument identification 

number (PIIN) pending transition to the PIID. When procurement 

is authorized under a PIID call/order number (F in 9th position), 

provide the value in the PIID field. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/CS03/0750

Data Element, 

328 Release 

Number

Modify existing DLMS note 1 and add note 2:

DLMS Note: 

1. Use to identify the legacy four-position call/ or order associated 

with the PIINnumber if applicable.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

# Location DLMS 846A Asset Reclassification (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 4 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/0240

Data Element, 

367 Contract 

Number

Add new DLMS note 2:

DLMS Note: 1. Use only for reclassification request transactions to 

identify the contract number procurement instrument identifier 

(PIID) previously assigned to the procurement receipt for which 

classification is requested. For suspended procurement receipts, cite 

the contract number PIID of the materiel receipt. For materiel 

previously transferred to a suspended condition as a result of an 

inventory adjustment, cite the adjustment contract number PIID. For 

suspect assets in a non-suspended condition, cite the applicable 

contract number PIID. Use the legacy procurement instrument 

identification number (PIIN) pending transition to the PIID. 

2. When procurement is authorized under a PIID call/order number 

(F in 9th position), provide the value in the PIID field. Refer to ADC 

1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).
Enclosure 4, ADC 1161A

Page 21

# Location DLMS 846A Asset Reclassification (Version 4010)

Revision

Reason

3. 2/CS03/0240

Data Element,

328 Release 

Number

Delete Federal Note and add new DLMS Notes 1 and 2:

Federal Note: Use as needed to identify the call number or order 

number, or the call or order number including the respective

call or order modification, associated with the contract number, if 

applicable.

DLMS Federal Note: 

1. Use to identify the legacy four-position call/order number

associated with the PIIN. 

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

# Location DLMS 846D Logistics Reassignment Transfer and 

Decapitalization (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 6 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/0240

Data Element, 

367 Contract 

Number

Delete the Federal Note and add new DLMS Note:

Federal Note: Use to identify the contract number of the associated 

receipt.

DLMS Note: Use to identify the procurement instrument identifier 

(PIID) of the associated receipt. Use the legacy procurement 

instrument identification number (PIIN) pending transition to the 

PIID. When procurement is authorized under a PIID call/order 

number (F in 9th position), provide the value in the PIID field.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/CS03/0240

Data Element, 

328 Release 

Number

Delete the Federal Note and add DLMS Notes 1 and 2:

Federal Note: Use to cite the call or order number, or the call or 

order number including the respective call or order modification, as 

applicable.

1. Use to identify the legacy four-position call/order number

associated with the PIIN. 

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 22

# Location DLMS 846I Asset Status Inquiry/ Report (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 5 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/0240

Data Element 

367, Contract 

Number 

Modify DLMS Note 1 and add DLMS Note 2: 

DLMS Note: 1. For Intra-Army use to identify the procurement 

instrument identifier (PIID) when reporting GFM consumption. This 

is a DLMS enhancement (contract number is not provided in the 

legacy BZE format and may not be available pending update to Army 

systems). Use the legacy procurement instrument identification 

number (PIIN) pending transition to the PIID. 

2. When procurement is authorized under a PIID call/order number 

(F in 9th position), provide the value in the PIID field. Refer to ADC 

1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/CS03/0240

Data Element, 

328 Release 

Number

Add new DLMS Note 2 and 3:

DLMS Note: 1. For Intra-Army use to identify the legacy four 

position call/order number associated with the PIIN, (may include the 

respective call or order modification) when reporting GFM 

consumption.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 23

# Location DLMS 856 

Advance Shipment Notice (ASN) (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 9 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/PRF01/050

Data Element,

324 Purchase 

Order Number

Remove existing Federal Notes and replace with new Federal Note; 

remove DLMS Note:

Federal Note: 1. Users that have implemented the Uniform 

Procurement Instrument Identifiers (PIID),enter the PIID of the 

contract, task or delivery order number (including Federal Supply 

Schedules,General Services Administration Schedules and all

other basic contracts), Blanket Purchase Agreement number, Grant, 

Lease, or Agreement number. This number must be transmitted 

without dashes.

2. Users that have not implemented Uniform Procurement Instrument 

Identifiers (PIID) enter the purchase order number, contract number 

(including Federal Supply Schedules, General Services Administration 

Schedules and all other basic contracts), Blanket Purchase Agreement 

number, Grant, Lease or Agreement number. This is always

the Procurement Instrument Identification Number (PIIN) for the 

Department of Defense or the equivalent expression for Civilian 

Agencies. This is never the number of a delivery order, call or release

against a basic award instrument. That number is carried in PRF02. 

This number must be transmitted without dashes.

Use to identify the procurement instrument identifier (PIID). Use 

the legacy procurement instrument identification number (PIIN)

pending transition to the PIID. When procurement is authorized 

under a PIID call/order number (F in 9th position), provide the value 

in the PIID field. Refer to ADC 1161.

DLMS Note: iRAPT field length will configure to 13 positions for 

initial implementation.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).
Enclosure 4, ADC 1161A

Page 24

# Location DLMS 856 

Advance Shipment Notice (ASN) (Version 4010)

Revision

Reason

3. 2/PRF02/050

Data Element, 

328 Release 

Number

Remove existing Federal notes and DLMS notes and add new DLMS 

Notes 1, and 2:

Federal Note: 1. Do not use PRF02 when a uniform PIID is entered in 

PRF01.

2. Users that have not implemented the Uniform PIID enter the 

number of a release, call, or delivery order against a basic award 

instrument. This is always the Supplemental Procurement Instrument

Identification Number (SPIIN) for the Department of Defense or the 

equivalent expression for Civilian Agencies. This number must be 

transmitted without dashes.

1. Use to identify the legacy four-position call/order number

associated with the PIIN. 

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to PRF01. Refer to ADC 1161.

DLMS Note: 1. For users that have implemented the Uniform PIID, 

iRAPT will configure to 13 positions.

2. For users that have not implemented the Uniform PIID, iRAPT will 

configure to 4 positions.

Implement PIID for 

contract number and 

call/order number.

4. 2/REF01/0150

Data Element 

128, Reference 

Identification 

Qualifier

For Code P1 – Previous Contract Number, update note and change 

Federal to DLMS note:

Federal DLMS Note: For iRAPT, use to indicate a contract

procurement instrument identifier (PIID) is being corrected. The 

vendor will enter the Contract Number PIID of the immediately 

preceding Corrected Receiving Report or Receiving Report, to which 

this correction applies. 

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 25

# Location DLMS 856R

Shipment Status Materiel Returns (Version 4030)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 5 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/GF03/060

Data Element,

367 Contract 

Number

Revise DLMS note 1:

DLMS Note: 1. Must use to identify the applicable contract number

procurement instrument identifier (PIID). Use the legacy

procurement instrument identification number (PIIN) pending 

transition to the PIID. When GFM is authorized under a PIID 

call/order number (F in 9th position), provide the value in the PIID 

field. Refer to ADC 1161

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification

purpose).

3. 2/GF07/3300

Data Element, 

328 Release 

Number

Modify DLMS note 1 and add new DLMS note 2:

DLMS Note: 1. Use to identify the legacy four-position call/order 

associated with the PIIN call or order number, or the call or order 

number including the respective call or order modification, as 

applicable.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to GF03. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 26

# Location DLMS 856S Shipment Status (Version 4030)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 6 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration))

Implement PIID for 

contract number and 

call/order number.

2. 2/REF04-

01/1500

Data Element, 

128 Reference 

Identification 

Qualifier

For Code CT – Contract Number, modify DLMS note 1

CT Contract Number

DLMS Note: 1. Must use for CAV shipment status, to identify the 

contract number procurement instrument identifier (PIID)

authorizing repair/return of GFP. Use the legacy procurement 

instrument identification number (PIIN) pending transition to the 

PIID. When procurement is authorized under a PIID call/order 

number (F in 9th position), provide the value in the PIID field. Refer 

to ADC 1161.

2. Under ADC 1014, GFP contract information is transitioned from the 

REF segment to the GF Segment. Delayed implementation is 

authorized. 

3. Authorized DLMS enhancement; see introductory DLMS 2a.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for

clarification 

purpose).

3. 2/REF04-03/

1500

Data Element, 

128 Reference 

Identification 

Qualifier

Revise existing DLMS note 1 and add new notes 2 and 3 and 

renumber existing notes for code OQ:

OQ Order Number

DLMS Note: 1. Must uUse for CAV shipment status with contract 

number (REF04-01 Code CT) to identify the legacy four-position call/

or order number associated with the PIIN in (REF04-01 Code CT). or 

the call or order number including the respective call or order 

modification associated with the applicable contract.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to REF01, Code CT. Refer to ADC 1161.

3. Under ADC 1014, GFP contract information is transitioned from 

the REF segment to the GF Segment. Delayed implementation is 

authorized.

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

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 27

# Location DLMS 856S Shipment Status (Version 4030)

Revision

Reason

4. 2/GF03/3300

Data Element, 

367, Contract 

Number 

Modify DLMS note: 

DLMS Note: Must use to identify the applicable contract number

procurement instrument identifier (PIID). Use the PIIN pending 

transition to the PIID. When GFP is authorized under a PIID 

call/order number (F in 9th position), provide the value in the PIID 

field. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

5. 2/GF07/3300

Data Element, 

328 Release 

Number

Modify DLMS note 1 and add new DLMS notes 2:

DLMS Note: 

1. Use to identify the legacy four-position call/ or order number

associated with the PIIN, or the call or order number including the 

respective call or order modification, as applicable.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to GF03. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number..

# Location DLMS 4030 856W Hazardous Material/Hazardous Waste 

(HM/HW) Shipment Status Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 5 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number 

and call/order 

number

2. 2/REF01/1500

Data Element, 

128 Reference 

Identification 

Qualifier

Add new DLMS notes2 and 3 for existing code CT:

CT Contract Number

DLMS Note: 1. Use in the HL03 code W loop to identify the 

procurement instrument identifier (PIID) contract number. When 

procurement is authorized under a PIID call/order number (F in 9th

position), provide the value in the PIID field. Refer to ADC 1161. 

Implement PIID for 

contract number and

call/order number
Enclosure 4, ADC 1161A

Page 28

# Location DLMS 861 Acceptance Report (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 2 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 1/PRF01/080

Data Element,

324 Purchase 

Order Number

Remove Federal note; Add DLMS Note:

Federal Note: Enter the purchase order number, contract number 

(including Federal Supply Schedules, General Services Administration 

Schedules and all other basic contracts), Blanket Purchase Agreement 

number, Grant, Lease or Agreement number. This is always the 

Procurement Instrument identification Number for the Department of 

Defense or the equivalent expression for Civilian Agencies. This is 

never the number of a delivery order, call or release against a basic 

award instrument. That number is carried in PRF02. This number 

shall be transmitted without dashes.

DLMS Note: Use to identify the procurement instrument identifier 

(PIID). Use the legacy procurement instrument identification

number (PIIN) pending transition to the PIID. When procurement 

is authorized under a PIID call/order number (F in 9th position), 

provide the value in the PIID field. Refer to ADC 1161. 

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 1/PRF02/080

Data Element, 

328 Release 

Number

Remove Federal note; Add DLMS Notes:

Federal Note: Enter the number of a release, call or delivery order 

against a basic award instrument. This is always the Supplemental 

Procurement Instrument Identification Number for the Department of 

Defense or the equivalent expression for Civilian Agencies. This 

number shall be transmitted without dashes.

DLMS Note:

1. Identify the four-position legacy call/order number associated with 

the PIIN.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to PRF01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 29

# Location DLMS 867I Issue (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 7 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/REF01/030

Data Element,

128 Reference 

Identification 

Qualifier

Add new DLMS note 3 and renumber existing DLMS notes 3 and 4:

CT Contract Number

DLMS Note: 1. Must use in GFP-related transactions.

2. Use to provide contract information for shipments of GFP to the 

contractor.

3. Use to identify the procurement instrument identifier (PIID). Use 

the legacy procurement instrument identification number (PIIN)

pending transition to the PIID. When GFP is authorized under a 

PIID call/order number (F in 9th position), provide the value in the 

PIID field.

4. Use for issue of contractor shipments of GFP into DoD inventory.

5. Authorized DLMS enhancement. Refer to ADC 1014

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/REF04-01/30

Data Element,

128 Reference 

Identification 

Qualifier

Update existing DLMS note 1 for Code OQ to add new notes 2 and 

renumber existing note 2:

OQ Order Number

DLMS Note: 1. Use as directed by the authorizing Service/Agency in 

GFP-related transactions with REF01 Code CT to identify the legacy 

four-position call/ or order number including the respective call or 

order modification associated with the PIIN applicable contract.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to REF01 Code CT. Refer to ADC 1161.

4. Authorized DLMS enhancement. Refer to ADC 1014.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 30

# Location DLMS 869C Requisition Cancellation (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory note 4 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/GF03/100

Data Element, 

367, Contract 

Number

Add DLMS Note:

DLMS Note: Use to identify the procurement instrument identifier 

(PIID) authorizing the contractor to receive materiel. Use the legacy

procurement instrument identification number (PIIN) pending 

transition to the PIID. When materiel is authorized under a PIID 

call/order number (F in 9th position), provide the value in the PIID 

field. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/GF07/100

Data Element, 

328 Release 

Number

Renumber existing note and add new note 2: 

DLMS Note: 1. Use to identify the legacy four-position call/ or order 

number associated with the PIINor the call or order number including 

the respective call or order modification, as applicable, when using

GF03.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to GF03. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

4. 2/REF01/0105

Data Element,

128 Reference 

Identification 

Qualifier

Revise the existing DLMS Note for code CT and add note 2

CT Contract Number

DLMS Note: Use to identify the contract number procurement 

instrument identifier (PIID), when available. Use the legacy PIIN 

pending transition to the PIID. When procurement is authorized 

under a PIID call/order number (F in 9th position), provide the value 

in the PIID field.

When using, do not use code W4.

2. When using, do not use code W4.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

5. 2/REF04-01/ 

0105

Data Element,

128 Reference 

Identification 

Qualifier

Add new note 2 for code OQ:

OQ Order Number

DLMS Note: 1. Use to identify the legacy four-position call/order

associated with the PIINnumber or order number, if applicable.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to REF01, Code CT. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 31

# Location DLMS 869C Requisition Cancellation (Version 4010)

Revision

Reason

6. 2/REF04-03/

0105

Data Element, 

128 Reference 

Identification 

Qualifier

Add new note 2 for code OQ:

OQ Order Number

DLMS Note: 1. Use to identify the legacy four-position call/order

associated with the PIINnumber or order number, if applicable.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to REF01, Code CT. Refer to ADC 1161

Implement PIID for 

contract number and 

call/order number.

7. 2/REF04-05/

0105

Data Element,

128 Reference 

Identification 

Qualifier

Add new note 2 for code OQ:

OQ Order Number

DLMS Note: 1. Use to identify the legacy four-position call/order

associated with the PIINnumber or order number, if applicable.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to REF01, Code CT. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

# Location DLMS 869F Requisition Follow-Up (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 7 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/GF01/100

Data Element 

128 Reference 

Identification 

Qualifier

Modify existing the existing DLMS Note 1 for code C7 and W3: 

C7 Contract Line Item Number

DLMS Note: 1. Use to associate a Contract Line Item Number 

(CLIN) with the procurement instrument identifier (PIID)Contract 

Number.

2. Use as directed by the authorizing Service/Agency.

3. When both the CLIN and the MDN are applicable, identify the 

CLIN in GF09. Refer to ADC 1014A.

W3 Manufacturing Directive Number

DLMS Note: 1. Use to identify the MDN, in addition to the 

PIIDContract Number.

2. Use as directed by the authorizing Service/Agency. Refer to ADC 

1014.

3. When both the CLIN and the MDN are applicable, identify the 

CLIN in GF09. Refer to ADC 1014A.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 32

# Location DLMS 869F Requisition Follow-Up (Version 4010)

Revision

Reason

3. 2/GF03/100

Data Element, 

367, Contract 

Number

Add DLMS Note:

DLMS Note: Use to identify the procurement instrument identifier 

(PIID) authorizing the contractor to receive materiel. Use the

legacy procurement instrument identification number (PIIN)

pending transition to the PIID. When materiel is authorized under 

a PIID call/order number (F in 9th position), provide the value in 

the PIID field.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is now 

known as PIID, the 

legacy PIIN is used 

here to associate with 

the legacy call/order 

number (for 

clarification purpose).

4. 2/GF07/100

Data Element,

328 Release 

Number

Removed Federal note; Add new DLMS notes1 and 2:

DLMS Note: 1. Use to identify the four-position legacy call/ or order 

number associated with the PIIN. as applicable, when using GF03.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to GF03. Refer to ADC 1161

Implement PIID for 

contract number and 

call/order number.

5. 2/REF01/105

Data Element 

123, 

Reference 

Identification 

Qualifier

Revise DLMS note for Code CT:

CT Contract Number

DLMS Note: Use to identify the contract number PIID or obligation 

authority number associated with the requisition. When procurement 

is authorized under a PIID call/order number (F in 9th position), 

provide the value in the PIID field.

Implement PIID for 

contract number and 

call/order number.

# Location DLMS 870S Supply Status (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 5 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS01/86

Data Element, 

367, Contract 

Number

Add DLMS Note:

DLMS Note: Use to identify the procurement instrument identifier 

(PIID). Use the legacy procurement instrument identification 

number (PIIN) pending transition to the PIID. When procurement

is authorized under a PIID call/order number (F or M in 9th

position), provide the value in the PIID field.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).
Enclosure 4, ADC 1161A

Page 33

# Location DLMS 870S Supply Status (Version 4010)

Revision

Reason

3. 2/CS03/86

Data Element,

328 Release 

Number

Remove Federal note; Add new DLMS Notes 1 and 2:

Federal Note: Use to identify the call or order number, or the call or 

order number including the respective call or order modification, as 

applicable.

DLMS Note: 1. Use to identify the legacy four-position call/order 

number associated with the PIIN. 

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.

# Location DLMS 940R Materiel Release (Version 4030)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 7 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/N901/0400

Data Element,

128 Reference 

Identification 

Qualifier

Modify DLMS note 1 for Code CT.

CT Contract Number

DLMS Note: 1. Must use in GFMGFP-related transactions to provide 

the (PIID). Use the legacy procurement instrument identification 

number (PIIN) pending transition to the PIID. When GFM is 

authorized under a PIID call/order number (F in 9th position), 

provide the value in the PIID field.

2. Use to provide contract information for shipments of GFP to the 

contractor.

3. Use for directed release of contractor shipments of GFP into DoD 

inventory.

4. Authorized DLMS enhancement. Refer to ADC 1014.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

3. 2/N907-

01/0400

Data Element,

128 Reference 

Identification 

Qualifier

Add new DLMS note 2 and renumber notes for Code OQ:

OQ Order Number

DLMS Note:

1. Use in GFPGFM-related transactions with N901 code CT to 

identify the legacy four-position call/ or order number including the 

respective call or order modification associated with the 

PIINapplicable contract.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to N901 Code CT. Refer to ADC 1161.

3. Authorized DLMS enhancement; see introductory DLMS note 4a.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 34

# Location DLMS 945A Materiel Release Advice (Version 4010) 

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 7 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number

2. 2/N901/0400

Data Element,

128 Reference 

Identification 

Qualifier

Revise existing DLMS note 1 for code CT:

CT Contract Number

DLMS Note: 1. Use to identify the procurement instrument 

identifier (PIID) on shipments of GFM to the contractor. When GFM

is authorized under a PIID call/order number (F in 9th position), 

provide the value in the PIID field.

Implement PIID for 

contract number and 

call/order number

# Location DLMS 945A Materiel Release Advice (Version 4030) 

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 7 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number

2. 2/N901/0400

Data Element,

128 Reference 

Identification 

Qualifier

Revise existing DLMS note 1 for code CT:

CT Contract Number

DLMS Note: 1. Use to identify the procurement instrument 

identifier (PIID) on shipments of GFM to the contractor. When GFM

is authorized under a PIID call/order number (F in 9th position), 

provide the value in the PIID field.

Implement PIID for 

contract number and 

call/order number
Enclosure 4, ADC 1161A

Page 35

# Location DLMS 947I Inventory Adjustment (Version 4010)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 6 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS/050

Segment, 

Contract 

Summary

Modify DLMS notes 1 and 2

DLMS Note:

1. Use only with W1901 code AC inventory adjustment transactions to 

identify the contract numberprocurement instrument identifier (PIID)

and Contract Line Item Number (CLIN), or the CLIN, including the 

Subcontract Line Item Number (SUBCLIN), associated with the 

transaction. Use of this segment is a DLMS enhancement. See 

introductory DLMS note 4a. and ADC 1161.

2. DLA has identified a requirement to use this segment for intra-DLA 

procurement related adjustments for condition transfer. DLA use the

contract number PIID, CLIN and Call Order Number for these 

transactions.

3. CAV has identified a requirement to use this segment when the 

repair vendor is a commercial contractor. Refer to ADC 461.

Implement PIID for 

contract number and 

call/order number.

3. 2/CS01/050

Data Element, 

367, Contract 

Number

Remove Federal Note and DLMS Note:

Contract Number

Federal Note: Use to identify the contract number of the associated 

adjustment.

DLMS Note: Use to identify the PIID of the associated adjustment. 

Use the legacy procurement instrument identification number (PIIN)

pending transition to the PIID. When procurement is authorized 

under a PIID call/order number (F in 9th position), provide the value 

in the PIID field.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

4. 2/CS03/050

Data Element,

328 Release 

Number

Turn the Federal note to DLMS Note and add new DLMS note 2:

Federal DLMS Note: 1. Use as needed to identify the legacy fourposition call/ or order number associated with the PIINor the call or 

order modification, as applicable.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 36

# Location DLMS 947I Inventory Adjustment (Version 4030)

Revision

Reason

1. DLMS 

Introductory 

Note

Add ADC to DLMS Introductory Note 6 to add:

- ADC 1161, Update uniform Procurement Instrument Identifier 

(PIID) numbering system in the Federal/DLMS Implementation 

Conventions and DLMS Manuals (Supply/Contract Administration)

Implement PIID for 

contract number and 

call/order number.

2. 2/CS/050

Segment, 

Contract 

Summary

Modify DLMS notes 1 and 2

DLMS Note:

1. Use only with W1901 code AC inventory adjustment transactions to 

identify the contract numberprocurement instrument identifier (PIID)

and Contract Line Item Number (CLIN), or the CLIN, including the 

Subcontract Line Item Number (SUBCLIN), associated with the 

transaction. Use of this segment is a DLMS enhancement. See 

introductory DLMS note 4a. and ADC 1161.

2. DLA has identified a requirement to use this segment for intra-DLA 

procurement related adjustments for condition transfer. DLA use the

contract number PIID, CLIN and Call Order Number for these 

transactions.

3. CAV has identified a requirement to use this segment when the 

repair vendor is a commercial contractor. Refer to ADC 461.

Implement PIID for 

contract number and 

call/order number.

3. 2/CS01/050

Data Element, 

367, Contract 

Number

Remove Federal Note and DLMS Note:

Contract Number

Federal Note: Use to identify the contract number of the associated 

adjustment.

DLMS Note: Use to identify the PIID of the associated adjustment. 

Use the legacy procurement instrument identification number (PIIN)

pending transition to the PIID. When procurement is authorized 

under a PIID call/order number (F in 9th position), provide the value 

in the PIID field.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

4. 2/CS03/0500

Data Element,

328 Release 

Number

Turn Federal note to DLMS Note and add new DLMS Note 2:

Federal DLMS Note: 1. Use as needed to identify the legacy four 

position call/ or order number associated with the PIIN, or the call or 

order number including the respective call or order modification, as 

applicable.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to CS01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 4, ADC 1161A

Page 37

# Location Federal 857 Shipment and Billing Notice (Version 4010)

Revision

Reason

1. 2/N901/110

Data Element,

128 Reference 

Identification 

Qualifier

Modify the note for Code CT

CT Contract Number

1. Use in Shipment loop (HL03 code S) to identify the Gaining 

Contract Number procurement instrument identifier (PIID) for 

Reparable Combo Reports. When procurement is authorized under a 

PIID call/order number (F in 9th position), provide the value in the 

PIID field. Refer to ADC 1161.

2. Use in Mark loop (HL03 code X) to identify the Mark content type 

Contract NumberPIID.

Implement PIID for 

contract number and 

call/order number.

2. 2/PRF/190 Revise Segment level notes as follows:

1. Use to identify the Procurement Instrument Identification Number 

(PIIN) and, if applicable the Supplemental Procurement Instrument 

Identification Number (SPIIN). Use to identify the Procurement 

Instrument Identifier (PIID). When procurement is authorized 

under a PIID call/order number (F in 9th position), provide the value 

in the PIID field. Refer to ADC 1161.

2. Use to identify additional contract information including a contract 

or order modification.

Implement PIID for 

contract number and 

call/order number.

3. 2/PRF01/0190

Data Element,

324 Purchase 

Order Number

Revise the existing Federal note:

Enter the purchase order number, contract number PIID. (including 

Federal Supply Schedules, General Services Administration Schedules 

and all other basic contracts). Use the legacy PIIN pending transition 

to the PIID. When procurement is authorized under a PIID 

call/order number (F in 9th position), provide the value in the PIID 

field.

This is always the Procurement Instrument Identification Number 

(PIIN) for the Department of Defense or the equivalent expression for 

Civilian Agencies. This is never the number of a delivery order, call or 

release against a basic award instrument, that number is carried in 

PRF02. Transmit this number will be transmitted without dashes.

Implement PIID for 

contract number and 

call/order number.

Although PIIN is 

now known as PIID, 

the legacy PIIN is 

used here to 

associate with the 

legacy call/order 

number (for 

clarification 

purpose).

4. 2/PRF02/050

Data Element, 

328 Release 

Number

Revise the existing Federal note and add new note 2.

1. Enter the number of a release, call or delivery order Use to identify 

the legacy four-position call/order number associated with the PIIN. 

against a basic award instrument. This is always the Supplemental 

Procurement Instrument Identification Number (SPIIN). Transmit this 

number shall be transmitted without dashes.

2. Do not use for the PIID call/order number. The PIID call/order 

number is mapped to PRF01. Refer to ADC 1161.

Implement PIID for 

contract number and 

call/order number.
Enclosure 5, ADC 1161A

Page 1

Enclosure 5, LOGISTICS DATA RESOURCES MANAGEMENT SYSTEM 

(LOGDRMS)

 NAME: Procurement Instrument Identification Identifier (PIID) 

(Contract Number)

DEFINITION:

A standard unique identification of a DoD procurement 

contract (contract number) that specifically 

differentiates one contract from all other contracts.

A standard unique identifier for a solicitation, 

contract, agreement, or order and related 

procurement instruments, see DFARS Subpart 

204.16. The new identifier for call/order number 

under the PIID rules is designated by F in the 9th

position. However, there is an exception 

authorized for DLA procurement instruments 

supporting FEDMALL to identify the delivery/call 

order using an M in the 9th position. The PIID 

call/order number is always treated as a 

contractual agreement even when the base 

contract number is available. If a base PIID 

contract number and PIID call/order number are 

available, provide the PIID call/order number (F or 

M PIID) only.

DATA CODE CHARACTERISTICS: TYPE: AN MIN: 13, MAX: 1317

SOURCE: DFARS Subpart 204.16

REMARKS:

The new DoD PIID is 13/13 characters in length, 

Federal non-DoD PIID is 13/17 character. Refer to

ADC 1157 ADC 1161A.

NAME: Procurement Instrument Identification Number (PIIN)

(contract number) 

DEFINITION:

A standard unique identification of a DoD procurement 

contract (contract number) that specifically 

differentiates one contract from all other contracts.

Identifies legacy contractual documents. DFAR 

203.70 was deleted. Use of the PIIN is authorized 

in the DLMS and legacy MILSTRIP/MILSTRAP 

procedures, pending transition to the procurement 

instrument Identifier (PIID). 

DATA CODE CHARACTERISTICS: TYPE: AN MIN: 13, MAX: 13 

SOURCE: DFARS Subpart 204.70 (deleted on February 26, 

2016)
Enclosure 5, ADC 1161A

Page 2

REMARKS:

The PIIN is being replaced by the Uniform 

Procurement Instrument Identifier (PIID) between 

October 1, 2015 and 31 March 2017, but the PIIN will 

still be used to reference existing contract numbers 

issued prior to the implementation. Refer to ADC 

1157ADC 1161A. DLMSO will revisit our 

procedures in 2 years to delete PIIN and related 

legacy terms.

NAME: Supplementary Procurement Instrument Identifier 

Identification (PIID)

DEFINITION:

A coded alpha-numeric representation that is used in 

conjunction with a PIID. Used to identify a modification 

to a contract or agreement. (reference FAR 4.16 and 

DFARS 204.16 (draft) amendments or modifications 

to the procurement instrument. The 

Supplementary PIID must be used in conjunction

with the PIID.

DATA CODE CHARACTERISTICS: TYPE: AN MIN: 6, MAX: 6

SOURCE: DFARS Subpart 204.16 (draft)

REMARKS:

NAME: Call/Order Serial Number

DEFINITION:

IDENTIFYIES A RELEASE AGAINST A BASIC 

CONTRACT (PROCUREMEMT INSTRUMENT 

IDENTIFICATION NUMBER (PIIN). (OFFICIALLY 

REFERRED TO AS A SUPPLEMENTAL PIIN).

A release against a basic contract. This is a legacy 

four-character field (that must be used in 

conjunction with a legacy PIIN). The new identifier 

for call/order number under the PIID rules is 

designated by F or M in the 9th position of the PIID

and is treated as a contractual document. See PIID 

definition.

DATA CODE CHARACTERISTICS: TYPE: AN MIN: 64, MAX: 6 13

SOURCE:

REMARKS:

The call/order numbers are being replaced by the 

uniform Procurement Instrument Identifier (PIID) 

between October 1, 2015 and March 31, 2017, but the 

four-character legacy Call/Order Nnumbers will still be 

used as a reference for existing contract numbers 

issued prior to the implementation. DLMSO will 

revisit our procedures no later than2 years from 

the date of ADC 1161A to delete PIIN and related 

legacy terms.