OFFICE OF THE ASSISTANT SECRETARY OF DEFENSE

 3500 DEFENSE PENTAGON

 WASHINGTON, DC 20301-3500

 

 

 SUSTAINMENT

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE

SUBJECT: Approved Defense Logistics Management Standards Change 1415, New Defense 

Logistics Management Standards 536R Transaction to Support Required Acquisition 

and Valuation Data Elements

 The Defense Logistics Management Standards change, as outlined in the attachment, is 

approved for implementation. 

 Addressees may direct questions to Rafael Gonzalez, e-mail: DEDSO.Supply@dla.mil. 

Others must contact their designated Process Review Committee representative available at 

https://www.dla.mil/Defense-Data-Standards/Committees/Contacts/. 

 Leigh E. Method, SES 

 Deputy Assistant Secretary of Defense 

 for Logistics 

Attachments:

As stated

cc:

OUSD(C)

DPC

DLA J6DS
Attachment, ADC 1415

Page 1 

Approved Defense Logistics Management Standards Change 1415 

New Defense Logistics Management Standards 536R Transaction to 

Support Required Acquisition and Valuation Data Elements

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: United States Special Operations Command (USSOCOM), Aaron 

Bauer, aaron.bauer.ctr@socom.mil

b. Functional POC: USSOCOM, J4, J44-JPOB, Jeffrey Lucowitz, 

jeffrey.l.lucowitz.civ@socom.mil

2. REASON FOR CHANGE: Substantive updates after staffing are identified in green 

highlighting. 

a. Bottom Line Up-Front: 

(1) This change introduces a new transaction under the Defense Logistics 

Management Standards (DLMS) environment to exchange acquisition and valuation history data 

between two accountable property systems of records (APSR). The transaction will also allow 

the exchange of information between an APSR and the Procurement Integrated Enterprise 

Environment (PIEE). The DLMS 536R Acquisition and Valuation transaction will enable 

Department of Defense (DoD) Components to exchange critical information needed for a gaining 

materiel owner to value assets considering financial history provided by the losing materiel 

owner. This transaction supports all required data elements under DoD Instruction 5000.64 

(Reference 10.a) and DD Form 3042 (Reference 10.b). 

(2) This change was originally submitted by USSOCOM as a service specific 

change. However, after further review, the Defense Enterprise Data Standards Office (DEDSO) 

expanded the scope of this change to all DoD Components and concluded the new DLMS 536R 

Acquisition and Valuation transaction is best suited to fulfill the requirements in this change.

b. Background: 

(1) The USSOCOM is a Joint Headquarters (HQ), Functional Combatant

Command under Title 10 Unites States Code, Section 167, responsible for Major Force Program 

- 11 funding for assets under source of supply Routing Identifier Code H9D. USSOCOM HQ 

uses the Defense Property Accountability System (DPAS) as the APSR. However, subordinate 

commands use the APSR appropriate to their Military Service. When USSOCOM conducts an 

electronic transfer between different APSRs, the gaining systems lack the required acquisition 

and valuation data elements to properly value the asset(s). No existing DLMS transaction 

contains the complete set of APSR data elements as required by DoDI 5000.64 (Reference 10.a).

(2) DPAS Property Accountability (DPAS-PA) to Global Combat Support 

System - Army (GCSS-A) electronic data transfers testing was conducted and completed using 

the DLMS 856S Shipment Status Electronic Data Interchange (EDI) transaction between the 

USSOCOM Operated DPAS-PA Module and U.S. Army Special Operations Command operated 
Attachment, ADC 1415

Page 2 

GCSS-A APSRs. DPAS-PA conducted a test to see if GCSS-A could receive a DLMS 

transaction. The test conducted was successful and provided proof that the gaining unit can 

successfully receive and post a USSOCOM capital asset from DPAS in GCSS-A.

(3) During the testing process, only the serial number (SN) and unique item 

identifier (UII) transferred to GCSS-A from DPAS-PA using the DLMS 856S transaction. This 

represents only two of the 16 data elements required by DoDI 5000.64 (Reference 10.a) and 

identified in Block 12 of DD Form 3042 (Reference 10.b). The complete set of 16 APSR data 

elements, including the Value/Acquisition Cost, Depreciation Value, Useful life, and Acquisition 

Date (or Date Placed in Service), are not currently available in a DLMS transaction. Lack of the 

complete set of APSR data elements has caused USSOCOM to be cited by DoD Auditors issuing 

Notices of Findings and Recommendations (NFRs) for assets transitioned between different 

Military Service APSRs.

(4) The initial proposal submitted by USSOCOM was limited in scope and 

recommended the DLMS 856S transaction to communicate valuation history between systems. 

After further review, DEDSO expanded the scope of this change to all DoD Components and 

concluded the new DLMS 536R Acquisition and Valuation transaction is best suited to fulfill the 

requirements in this change.

(5) After the formal staffing process, there were some concerns with this 

transaction and the possibility for contractor inventory control points (C-ICP) to use it. C-ICPs, 

even when acting on behalf of the government, are not responsible for the valuation of assets. 

The responsibility for valuation lies only with the government. Consequently, DEDSO updated 

this change and the appropriate implementation convention to restrict its use only to government 

APSRs and PIEE. 

3. CHANGE IN DETAIL: 

a. Technical Details:

(1) This change introduces a new DLMS transaction. The DLMS 536R 

Acquisition and Valuation History transaction enables a losing materiel owner to transmit 

essential acquisition and valuation data to a gaining materiel owner when transferring assets and 

ownership between two DoD Components. Contractor ICP’s are not authorized to use this 

transaction. The transaction also supports the exchange of information between DoD 

Component APSRs and PIEE. 

(a) The DLMS 536R Implementation Convention (IC) enables materiel 

owners to submit (Qualifier J – Record in 1/BR01/0200) and correct historical data (Qualifier 

CO - Correction in 1/BR01/0200). 

(b) In addition, this transaction enables a gaining materiel owner to send a 

request/inquiry for acquisition and valuation information to the losing materiel owner (Qualifier 

7 - Request in 1/BR01/0200). The request/inquiry must identify the item in question by either 

the national stock number (NSN) and supply condition code (SCC) or the local stock number 

(LSN), SCC, manufacturer part number, and commercial and government Entity (CAGE). In 

addition, the gaining owner must cite the document or contract number associated to the asset 
Attachment, ADC 1415

Page 3 

transfer. In response, the losing materiel owner must convey the acquisition and valuation of the 

item/shipment in question via the DLMS 536R (Qualifier J – Record in 1/BR01/0200). 

(c) The use of the LSN must only be used under limited circumstances. 

LSNs are not allowed for inter-component shipments. All DoD Components are responsible for 

catalog qualifying items as described in DoDM 4100.39, Federal Logistics Information System 

(FLIS) Procedures. 

(2) DoD Components are required to record and maintain the following data 

elements in their respective APSRs as stated in DoDI 5000.64 (Reference 10.a.) and DoD 

Manual 4140.01, Volume 11 (Reference 10.c.). All data elements required under reference 10.a. 

and 10.c. are available in the new DLMS 536R IC.

DoD Data Element X12 Qualifier Name Notes Location

Document Number Transaction Reference Required 1/N901/0300

Transportation Control 

Number (TCN)

Transportation Control 

Number 

Required when 

available in the 

Originating APSR

1/N901/0300 

Procurement 

Instrument Identifier

(PIID) or 

PIID/Call/Order 

Number (Parent)

Contract Number Required for New 

Procurement 1/N901/0300 

Contractor Inventory 

Control Point (ICP) 

Procurement Instrument

Agent Contract Number

Optional. Applies only 

when the losing APSR 

is communicating 

Government Furnished 

Property (GFP) data to 

the gaining APSR

1/N901/0300 

Shipment Number

Shipper's Identifying 

Number for Shipment 

(SID)

Required for New 

Procurement 1/N901/0300 

National Stock Number

(NSN) National Stock Number

Required when 

available in the 

originating APSR

2/LIN02/0200 

Local Stock Number 

(LSN) Stock Number 

Required for noncapital assets. NSN is 

mandatory when 

available.

2/LIN02/0200 

Management Control 

Number Mutually Defined

Required for noncapital assets. NSN is 

mandatory when 

available.

2/LIN02/0200 

Original Part Number Manufacturers Part 

Number

Required for LSN and

serially managed items 2/LIN04/0200 

Current Part Number Part Number Required for LSN and

serially managed items 2/N901/0600 

Model number Model Number Optional 2/LIN08/0200
Attachment, ADC 1415

Page 4 

DoD Data Element X12 Qualifier Name Notes Location

Manufacturer 

Commercial and 

Government Entity 

(CAGE)

Commercial and 

Government Entity

(CAGE) Code 

Required for LSN and

serially managed items 2/LIN06/0200 

Description Free-form Description 

(Min/Max: 1/45) 

Required when using 

LSN 2/G6901/1000 

Capital Equipment 

Indicator 

Yes/No Condition or 

Response Code 

Required for Capital 

Equipment items 2/DD08/1100 

Supply Condition Code

(SCC) Supply Condition Code Required 2/LQ01/1800 

Project Code Project Code Optional – Perpetuate 

when available 2/LQ01/1800 

Controlled Inventory 

Item Code (CIIC)

Controlled Inventory 

Item Code 

Optional – Perpetuate 

when available in the 

originating ASPR

2/LQ01/1800 

Serial Number Serial Number Required for serially 

managed items

2/N901/0600 

Unique Item Identifier 

(UII)

Department of Defense 

Unique Item Identifier

Required for serially 

managed items when 

available in the 

originating APSR. Use 

only with qualifier JRecord.

2/N901/0600 

Invoice Number Invoice Number 

Required when 

available in the 

originating APSR

2/N901/0600 

Government Bill of 

Lading (GBL)

Government Bill of 

Lading 

Required when 

available in the 

originating APSR

2/N901/0600 

Bill of Lading Number Bill of Lading Number 

Required when 

available in the 

originating APSR

2/N901/0600 

PIID or PIID Call/Order 

Number Contract Number (Item)

Required when 

available in the 

originating APSR

2/CS01/0300 

PIID or PIID Call/Order 

Number (modification)

Change Order Sequence 

Number 

Required if available in 

the originating APSR 

when procurement is 

authorized under a PIID 

call/order number, 

provide the value in the 

PIID field.

2/CS02/0300 

Quantity Shipped Shipped Quantity Required when using 

qualifier J-Record 2/QTY01/040

Unit of Issue Unit or Basis for 

Measurement Code Required for LSN 2/QTY03-01/0400 
Attachment, ADC 1415

Page 5 

DoD Data Element X12 Qualifier Name Notes Location

Date Placed in Service Effective Date

Required when 

available in the 

originating APSR

2/G6201/0800 

Date Shipped Shipped on This Date Required 1/G6201/0400

Acceptance Date Acceptance

Required when 

available in the 

originating APSR

2/G6201/0800 

Depreciation Start Date Accrual Start Date

Required when 

available in the 

originating APSR

2/G6201/0800 

Last Depreciation Date Accrual End Date

Required when 

available in the 

originating APSR

2/G6201/0800 

Unit Price Unit Cost Price Required when using 

qualifier J-Record 2/CTP02/0900 

Acquisition Price Purchase 

Required when 

available in the 

originating APSR

2/CTP02/0900 

Accumulated 

Depreciation Value Changed Price 

Required when 

available in the 

originating APSR

2/CTP02/0900 

Current Valuation Price Discount Price

Required when 

available in the 

originating APSR

2/CTP02/0900 

Salvage Value Unsalable Item List Cost

Required when 

available in the 

originating APSR

2/CTP02/0900 

Depreciation Period From Date of Award to 

Date of Completion 

Required when 

available in the 

originating APSR

2/LDT01/1200 

Estimated Useful Life 

(years) Service Estimate Number

Required when 

available in the 

originating APSR

2/LDT01/1200 

Losing Materiel Owner Losing Inventory 

Manager

Required when 

shipment originated 

from government ICP 

1/N101/0700 

Gaining Materiel Owner Gaining Inventory 

Manager

Required when the 

recipient of the 

shipment is government 

ICP

2/N101/1900 

Recipients point of 

contact Contract Contact 

Optional. Applies only 

when the losing APSR 

is communicating GFP 

data to the gaining 

APSR

1/G6101/1100 

Period of performance 

expiration date Period End

Optional. Applies only 

when the losing APSR 

is communicating GFP 

1/G6201/0400 
Attachment, ADC 1415

Page 6 

DoD Data Element X12 Qualifier Name Notes Location

data to the gaining 

APSR

Expected property 

return date (when 

different from period of 

performance)

Estimated Delivery Date 

Optional. Applies only 

when the losing APSR 

is communicating GFP 

data to the gaining 

APSR

1/G6201/0400 

(3) Multiple instances of the procurement instrument identifier (PIID): 

Under the Acquisition and Valuation transaction, there are multiple instances where a PIID can 

be used. However, each instance has a different purpose. 

• New procurement shipment– to uniquely identify the shipment as 

new procurement, use qualifier CT Contract Number (PIID) in 

1/N9/0300. The shipment number is also required. Do not use CS01. 

• Non-New Procurement shipment– to identify the contract number 

(PIID) in which each individual item was first acquired/purchased, use 

segment 2/CS01/0300 Contract Number. Do not use 1/N9/0300. 

• GFP Authorizing Contract – to identify the authorizing contract 

(PIID) for items managed by a contractor, use qualifier 6L Agent 

Contract Number 1/N9/0300. In addition, provide a recipient point of 

contact (1/G61/1100), period of performance expiration date, and/or 

the expected property return date (1/G62/0400). This is not the 

contract number in which an item of supply was first acquired. 

Contractor ICP’s are not authorized to use this transaction. GFP data 

elements can only be used at the header level and applies to all items 

referenced in the parent/child loop(s). Only one instance of GFP data 

may be conveyed per transaction. 

(4) Multiple instances of the CAGE and Part Number: Under the Acquisition 

and Valuation transaction, there are 2 instances of CAGE and 3 instances of part number. 

• Local Stock Numbers (LSN) and Management Control numbers 

(MCN)– to uniquely identify an item by a LSN or MCN, you must 

identify the part number and manufacturer CAGE as well. Use 

2/LIN02/0200 to indicate the LSN, 2/LIN04/0200 to indicate the 

manufacturer part number, and 2/LIN06/0200 to indicate the 

manufacturer CAGE. Do not use 2/N9/0600.

• Materiel under a cataloged National Stock Number (NSN) – to 

identify the manufacturer part number and CAGE for a cataloged item, 

use the N9 segment under details (2/N9/0600). 
Attachment, ADC 1415

Page 7 

• Serially managed items – to uniquely identify the item, you must cite 

the NSN in the LIN segment (2/LIN02/0200) and cite each individual 

serial number, manufacturer part number, and CAGE under the N9 

segment (2/N9/0600). To identify the current part number, use 

2/N9/0600.

b. Revised Transaction Flow: The DLMS 536R Acquisition and Valuation History

transaction supports three functions:

(1) Submitting information for the first time to the gaining materiel owner – 

The losing materiel owner will prepare the item(s) for shipment. After the transmission of the 

DLMS 856S Shipment Status transaction, the losing materiel owner will also transmit the DLMS 

536R Acquisition and Valuation History transaction (BR06=J). The gaining owner will then 

establish the initial property record in the appropriate APSR. When the materiel arrives, 

warehouse personnel will complete the receipt process and report to the appropriate APSR via 

DLMS 527R Receipt. The gaining materiel owner will then confirm receipt to the losing 

materiel owner via the DLMS 527R Materiel Receipt Acknowledge (MRA) as appropriate. In

addition, the gaining materiel owner will complete the pre-established property record using the 

information received in the receipt transaction. 

(2) Submitting a correction to the receiving activity/ICP – The losing materiel 

owner may submit a correction (BR06=CO Correct) as necessary to the gaining materiel owner. 

The correction will replace the original transaction in its entirety. 

(3) Submitting a request/inquiry to the shipping activity/ICP – the gaining 

owner will submit a request via the DLMS 536R, BR06=7 Request, to the losing materiel owner. 

In response, the materiel owner will provide all available acquisition and valuation history, 

(BR06=J).

4. IMPLEMENTATION TARGET: Impacted systems are expected to provide a proposed 

target implementation date along with their respective responses to this change. The target 

implementation should not exceed 2 years.

5. TECHNICAL IMPACT: 

a. Additions or Changes to Data Elements: 

(1) Incorporate the following new data elements to the DLMS environment: 

Capital Equipment Indicator (Y), Depreciation Start Date (62), Last Depreciation Date (63), 

Accumulated Depreciation Value (CHG), Current Valuation Price (DPR), Salvage Value (ULC), 

Depreciation Period (AX), and Estimated Useful Life (QO).

(2) Data Dictionary Metadata:

Data Element X12 Data Element Definition / Authoritative Source Data Type Min / Max

Capital Equipment 

Indicator

Yes 

(Element ID: 1073 – 

Yes/No Condition or 

Response Code)

Indicates whether the item in 

reference was considered capital 

Alpha character 1/1. Y 

is the only character 

allowed.
Attachment, ADC 1415

Page 8 

Data Element X12 Data Element Definition / Authoritative Source Data Type Min / Max

equipment by the losing item 

manager

Depreciation Start Date Accrual Start Date

(Element ID: 432 – 

Date Qualifier)

The start date in which an asset is 

depreciated.

Date CCYYMMDD

Last Depreciation Date Accrual End Date

(Element ID: 432 – 

Date Qualifier)

The last date in which an asset is 

depreciated.

Date CCYYMMDD

Accumulated 

Depreciation Value

Changed Price

(Element ID: 236 – 

Price Identifier Code)

The aggregated dollar amount 

depreciated 

Currency, 2 decimal 

values

Current Valuation Price Discount Price

(Element ID: 236 – 

Price Identifier Code)

The current valuation after 

depreciation as applicable to the 

item. 

Currency, 2 decimal 

values

Recipients point of 

contact 

 

Contract Contact 

(Element ID: CD – 

Contract Contact) 

An alpha value indicating the 

contactor ICP point of contact. 

Applicable to GFP/See DoDI 

5000.64 

Alpha, 1/60 characters

Period of performance 

expiration date 

Period End

(Element ID: PE – 

Period End)

Date value indicating the period of 

performance expiration date. 

Applicable to GFP/ See DoDI 

5000.64. 

Date, 8/8 values

Expected property return 

date (when different 

from period of 

performance)

Estimated Delivery 

Date (Element ID: 

17 Estimated 

Delivery Date)

Date value indicating the expected 

property return date. Applicable to 

GFP/ See DoDI 5000.64.

Date, 8/8 values

Salvage Value Usable Item List 

Cost

(Element ID: 236 – 

Price Identifier Code)

See DoD 7000.14-R FMR Vol. 4, 

Chapter 25, 2.6 Depreciation

Currency, 2 decimal 

values

Depreciation Period From Date of 

Award to Date of 

Completion

(Element ID: 345 – 

Lead Time Code)

A numeric value that represents 

days, month, or years.

Alpha character, 2/2

Estimated Useful Life Service Estimate 

Number

(Element ID: 345 – 

Lead Time Code; 

a data maintenance 

action will be submitted 

for establishment of 

‘QO – Service Estimate 

Number’)

A numeric value that estimates the 

remaining useful life for the item

Numeric 1/15

b. Automated Information Systems (AIS): 

(1) This change will impact all DoD APSRs with the need to communicate 

acquisition and valuation data between APSRs and/or PIEE. The submitter identified the 

following systems will be impacted: DPAS, GCSS-Army, and GCSS-Marine Corps. 

(2) Update Logistics Data Resources Management System (LOGDRMS) to 

recognize new data elements and transaction types.

c. Defense Automatic Addressing System (DAAS): Implement the new DLMS 536R 

as described under Enclosure 2. DAAS will use the N1 segments to identity the originator 
Attachment, ADC 1415

Page 9 

(FROM) as well as the destination (TO). Create new DLMS 536R mapping document with any 

routing rules, as necessary. Reject the transaction when the sender or the receiver matches a 

contractor DODAAC (1/N1/0700 or 2/N1/1900). 

6. PUBLICATION/POLICY IMPACT: 

a. Defense Logistics Manual (DLM) 4000.25: Update Volume 2, Chapter 13, Materiel 

Receipt as shown in Enclosure 1. 

b. Non-DLM 4000.25 Publications: Changes to the following publications may be 

necessary to reinforce compliance: 

(1) DoDI 5000.64, Accountability and Management of DoD Equipment and 

Other Accountable Property, section 4 Requirements and Procedures 

(2) DoDM 4140.01, Volume 11, DoD Supply Chain Materiel Management 

Procedures: Inventory Accountability and Special Management and Handling, Section 3.2 

Accountable Record for Inventory 

7. ASSUMPTIONS: This change was developed under the assumption that all impacted 

systems are under a variable length environment that can support X12 transactions. 

8. FINANCIAL IMPROVEMENT AND AUDIT REMEDIATION (FIAR), MATERIAL 

WEAKNESS, AND AUDIT-RELATED INFORMATION: 

a. Notices of Findings and Recommendations (NFR): 

(1) NFR-2019-General Equipment-03 - General Equipment Existence and 

Completeness Testing Exceptions 

(2) NFR-2020-General Equipment-03 - General Equipment Existence and 

Completeness Testing Exceptions 

b. Corrective Action Plan (CAP) References: CAP-2018-General Equipment (GE)-

03-SOF AT&L - GE Existence and Completeness (E&C) Testing Exceptions 

c. Other FIAR, Material Weakness, and Audit-Related Information: This change 

addresses materiel weaknesses identified by USSOCOM as their systems of record were not in 

compliance with References 10.a. and 10.b.

9. END-TO-END TESTING REQUIREMENTS: Proper testing must take place between 

DoD Components and DAAS before the changes in this document are implemented in a DAAS 

production environment. In addition, DAAS will capture the results and participants of the 

testing in a work order. Only DoD Components who have successfully tested transmission with 

DAAS may use this functionality. 
Attachment, ADC 1415

Page 10

10. REFERENCES: 

a. DoD Instruction 5000.64, “Accountability and Management of DoD Equipment and 

Other Accountable Property,” April 27, 2017, as amended. 

b. DD Form 3042, “Accountable Property System of Records (APSR) Equipment 

Requirements Checklist,” June 1, 2017

c. DoD Manual 4140.01, Volume 11, “DoD Supply Chain Materiel Management 

Procedures: Inventory Accountability and Special Management and Handling,” March 8, 2017, 

as amended.

11. PROPOSED DLMS CHANGE (PDC) 1415 RESPONSE/COMMENT RESOLUTION:

Component Response/Comment Disposition

1. DLA Concur with comment.

Comment:

Concern that the proposed change was limited the 536R to only 

NSN and CAGE/PART. DPAS believes this is far too limited 

when assets are being transferred between APSRs for the same 

Service. With standard catalogs such as AESIP, the receiving 

APSR will know what the MCN or LSN is, if they are using the 

same master catalog as they should be. If the change is approved 

as is, it will result in continued manual processing that this 

proposed change was to automate the reporting for all to become 

more FIAR compliant.

As noted. 

DEDSO added ZZ to 

support MCNs.

2. Navy Concur without comment. As noted. 

3. Air Force Concur with comment. 

Comment: 

"Convey" should be "conveyed" 

"Change as follows:

Optional. Applies only when the losing APSR is communicating 

Government Furnished Property (GFP) data to the gaining 

APSR"

Change "contractor inventory control points (ICP)" to contractor 

inventory control points (C-ICP)"

"""government accountable property systems of records (APSR) 

and PIEE.""

Change to: ""government APSR and PIEE."""

Move (TCN) to first column 

Remove extra ) at the end of UII))

Remove extra space between "PIID and or" 

Change to "Acceptance"

As noted.

All comments 

addressed. 
Attachment, ADC 1415

Page 11

4. US Army Concur. As noted.

5. USMC Concurs. As noted. 

6. DAAS Concur. As noted. 

7. USTRANSCOM Abstain. As noted. 

8. GSA No response. None noted. 

9. DPC DPC provided comments. 

Comments:

See enclosure 4 for DPC comments and DEDSO responses.

As noted. All 

comments addressed 

in the change. Please 

see enclosure 4.
Enclosure 1, ADC 1415

Page 1

Enclosure 1

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

Make the following change to Volume 2. Additions are shown in red italics.

Chapter 13, Materiel Receipt

Intervening text not shown

C13.1.3. Transactions. (Text not shown)

Intervening text not shown

C13.1.6. Acquisition and Valuation History transaction is identified by the 

DLMS 536R ASC X12, beginning segment (1/BR02/0200) Transaction Type Code 

TS – Transfer Statement, J-Record. There is no legacy equivalent transaction. A 

materiel owner may use this functionality when there is a need to report any 

acquisition and valuation data upon shipment or in response to a request/inquiry. 

C13.1.7. Acquisition and Valuation transaction is identified by the DLMS 

536R ASC X12, beginning segment (1/BR02/0200) Transaction Type Code TS –

Transfer Statement, CO-Correction. There is no legacy equivalent transaction. A 

materiel owner may use this functionality when there is a need to make a 

correction to previously submitted data. 

C13.1.8. Acquisition and Valuation transaction is identified by the DLMS 

536R ASC X12, beginning segment (1/BR02/0200) Transaction Type Code TS –

Transfer Statement, 7-Request. There is no legacy equivalent transaction. A 

materiel owner may use this functionality to request acquisition and valuation 

information from the last organization who own the materiel. 

Intervening text not shown.

C13.7. ACCOUNTABLE PROPERTY SYSTEM OF RECORD TRANSFERS. Upon 

ownership transfer of materiel, the sending and receiving activities may use the 

Acquisition and Valuation transaction to facilitate exchange of acquisition and 

valuation data between APSRs. The losing activity may transmit the appropriate 

information upon shipment, or the gaining activity may request the data to the 

losing activity. The losing activity may also send a correction to the gaining 

activity when there is a need to modify any information previously transmitted.
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 1 

Enclosure 2

DLMS 536R Acquisition and Valuation History Transaction Implementation Convention

536 Logistics Reassignment

Functional Group=LR

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Logistics Reassignment Transaction Set 

(536) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to provide information 

necessary to transfer management responsibility between an old and new managing organization. This transaction set may be used to convey a 

description and quantity of the transferred material, specific inventory locations, product quality information, technical data, open contract 

information, demand data, procurement history, and other information necessary for the new managing organization to evaluate and meet the 

material needs of customers.

DLMS Note:

1. DoD Components may use this transaction set to facilitate exchange of acquisition and valuation history between two accountable systems 

of record (APSR)s. DoD Components may also use this transaction set between an APSR and the Procurement Integrated Enterprise 

Environment (PIEE). This transaction is not authorized for contractors. 

2. Reserved.

3. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit 

Conversion Table which can be found on the Defense Enterprise Data Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS. 

4. This DLMS Implementation Convention (IC) contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system. 

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or 

understood by the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

c. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support transaction 

conversion in a mixed DLSS/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components 

may coordinate with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded files size above existing DLSS capability which may not be supported by the recipient's automated 

processing system. Components must coordinate implementation with DEDSO prior to use.

e. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data 

(including expanded field sizes) should be adopted during, or subsequent, to modernization when applicable to the Component’s business 

process. Prior coordination is not required. Components should ensure that inclusion of this data in a DLMS transaction does not cause 

inappropriate rejection of the transaction.

5. This revision to the DLMS IC incorporates Proposed DLMS Change (PDC) and Approved DLMS Changes (ADCs) listed. PDCs and ADCs 

are available from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/ 

- PDC 1415, New DLMS 536R to Support Required Acquisition and Valuation Data Elements 

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

0100 ST Transaction Set Header M 1 Must use

0200 BR Beginning Segment for Material 

Management

M 1 Must use

0300 N9 Reference Identification O 20 Must use

0400 G62 Date/Time O 10 Used

* LOOP ID – LM 20

* 0500 LM Code Source Information O 1 Not Used
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 2 

* 0600 LQ Industry Code M 100 Not Used

LOOP ID - N1 20

0700 N1 Name O 1 Must use

* 0800 N2 Additional Name Information O 2 Not Used

* 0900 N3 Address Information O 2 Not Used

* 1000 N4 Geographic Location O 1 Not Used

1100 G61 Contact O 10 Used

 

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID – HL >1

0100 HL Hierarchical Level M 1 Must use

0200 LIN Item Identification O 1 Used

0300 CS Contract Summary O 1 Used

0400 QTY Quantity O >1 Used

* 0500 RCD Receiving Conditions O 1 Not Used

0600 N9 Reference Identification O >1 Used

* 0700 CON Contract Number Detail O >1 Not Used

0800 G62 Date/Time O 50 Used

0900 CTP Pricing Information O 10 Used

1000 G69 Line Item Detail - Description O 30 Used

1100 DD Demand Detail O 100 Used

1200 LDT Lead Time O 3 Used

* 1300 MEA Measurements O 5 Not Used

* 1400 PKG Marking, Packaging, Loading O 5 Not Used

* 1500 PWK Paperwork O 1 Not Used

* 1600 MSG Message Text O 10 Not Used

LOOP ID – LM 20

1700 LM Code Source Information O 1 Used

1800 LQ Industry Code M 100 Must use

LOOP ID - N1 50

1900 N1 Name O 1 Must use

* 2000 N2 Additional Name Information O 2 Not Used

* 2100 N3 Address Information O 2 Not Used

* 2200 N4 Geographic Location O 1 Not Used

* 2300 G61 Contact O 10 Not Used

2400 SE Transaction Set Trailer M 1 Must use
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 3 

ST Transaction Set Header Pos: 0100 Max: 1

Heading - Mandatory

Loop: N/A Elements: 2

 

User Option (Usage): Must use

Purpose: To indicate the start of a transaction set and to assign a control number 

 

Semantics: 

1. The transaction set identifier (ST01) is used by the translation routines of the interchange partners to select the appropriate transaction 

set definition (e.g., 810 selects the Invoice Transaction Set).

2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate 

implementation convention to match the transaction set definition. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

ST01 143 Transaction Set Identifier Code

 

Description: Code uniquely identifying a 

Transaction Set 

M ID 3/3 Must use 1

Code Name

536 Logistics Reassignment 

ST02 329 Transaction Set Control Number

 

Description: Identifying control number that 

must be unique within the transaction set 

functional group assigned by the originator 

for a transaction set 

DLMS Note: A unique number assigned by 

the originator of the transaction set, or the 

originator's application program. 

M AN 4/9 Must use 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 4 

BR Beginning Segment for Material 

Management

Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 5

 

User Option (Usage): Must use

Purpose: To indicate the beginning of a material management transaction and transmit identifying numbers and dates 

Syntax Rules: 

1. C0504 - If BR05 is present, then BR04 is required.

2. P0708 - If either BR07 or BR08 is present, then the other is required.

3. P1011 - If either BR10 or BR11 is present, then the other is required.

 

Semantics: 

1. BR03 is the date of the transaction set preparation.

2. BR09 is the time of the transaction set preparation 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BR01 353 Transaction Set Purpose Code

 

Description: Code identifying purpose of 

transaction set 

M ID 2/2 Must use 1

Code Name

00 Original

 

BR02 640 Transaction Type Code

 

Description: Code specifying the type of 

transaction 

M ID 2/2 Must use 1

Code Name

TS Transfer Statement 

DLMS Note:

Use for Acquisition and Valuation History Data. Use BR06 to identify the type of action. 

BR03 373 Date

 

Description: Date expressed as 

CCYYMMDD where CC represents the first 

two digits of the calendar year 

DLMS Note: This date corresponds to the 

Universal Time Coordinate (UTC). 

M DT 8/8 Must use 1

BR06 306 Action Code

 

Description: Code indicating type of action 

O ID 1/2 Must use 1

Code Name

7 Request 

DLMS Note:

Request for Acquisition and Valuation History Data (Inquiry).

J Record 

DLMS Note:

Original Acquisition and Valuation Data.

CO Correct 

DLMS Note:

Corrected Acquisition and Valuation History Data. 

BR09 337 Time

 

Description: Time expressed in 24-hour 

O TM 4/8 Used 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 5 

clock time as follows: HHMM, or HHMMSS, 

or HHMMSSD, or HHMMSSDD, where H = 

hours (00-23), M = minutes (00-59), S = 

integer seconds (00-59) and DD = decimal 

seconds; decimal seconds are expressed as 

follows: D = tenths (0-9) and DD = 

hundredths (00-99) 

DLMS Note: 1. Express the originating 

activity's time in UTC. 

 

2. Express time in a four-position (HHMM) 

format. 
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 6 

N9 Reference Identification Pos: 0300 Max: 20

Heading - Optional

Loop: N/A Elements: 2

 

User Option (Usage): Must use

Purpose: To transmit identifying information as specified by the Reference Identification Qualifier 

Syntax Rules: 

1. R0203 - At least one of N902 or N903 is required.

2. C0605 - If N906 is present, then N905 is required.

 

Semantics: 

1. N906 reflects the time zone which the time reflects.

2. N907 contains data relating to the value cited in N902. 

DLMS Note:

Must use to identify the shipment. Repeat the loop as necessary to provide additional information. For non-new procurement, the transaction 

reference is required. For new procurement, the contract number and the shipment number are required. For GFP items, you must identify 

the shipment and provide the authorizing PIID (agent contract number). Only one instance of GFP data may be conveyed per transaction. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N901 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification 

M ID 2/3 Must use 1

Code Name

6L Agent Contract Number 

DLMS Note:

Must use to identify the authorizing procurement instrument identifier (PIID) for the item(s) 

referenced in the parent/child loop(s). Applicable to GFP. This is not the contract number 

for the item. 

CT Contract Number 

DLMS Note:

Must use to identify the procurement instrument identifier (PIID) or PIID Call/Order Number

applicable to the property in question. Applicable to new procurement.

SI Shipper's Identifying Number for Shipment (SID) 

DLMS Note:

Use in combination with the contract number to identify the shipment number when available. 

Applicable to new procurement. 

TG Transportation Control Number (TCN) 

DLMS Note:

Use to identify the transportation control number associated to the shipment.

TN Transaction Reference Number 

DLMS Note:

Must use to identify the document number associated to the shipment. Required for all action 

codes in BR06. Do not use for new procurement. 

N902 127 Reference Identification

 

Description: Reference information as 

defined for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier 

X AN 1/50 Must use 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 7 

G62 Date/Time Pos: 0400 Max: 10

Heading – Optional

Loop: N/A Elements: 2

 

User Option (Usage): Must Use

Purpose: To specify pertinent dates and times 

Syntax Rules: 

1. R0103 - At least one of G6201 or G6203 is required.

2. P0102 - If either G6201 or G6202 is present, then the other is required.

3. P0304 - If either G6203 or G6204 is present, then the other is required.

 

DLMS Note:

Must use to identify the date in which the shipment/item was shipped.

For GFP only, use qualifier PE or 17 to communicate GFP period of performance expiration data and/or expected property return 

date. Applies to GFP items. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

G6201 432 Date Qualifier

 

Description: Code specifying type of date 

X ID 2/2 Must use 1

Code Name

11 Shipped on This Date

PE Period End

DLMS Note: 

Use to indicate the period of performance expiration date. Applicable only to GFP items.

17 Estimated Delivery Date

DLMS Note:

Use to indicate the expected property return date (when different from period of 

performance). Applicable to GFP items only. 

G6202 373 Date

 

Description: Date expressed as 

CCYYMMDD where CC represents the first 

two digits of the calendar year 

X DT 8/8 Must use 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 8 

N1 Name Pos: 0700 Max: 1

Heading – Optional

Loop: N1 Elements: 4

 

User Option (Usage): Must use

Purpose: To identify a party by type of organization, name, and code 

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

 

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID 

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101. 

DLMS Note:

Must use to identify the originating organization. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual 

M ID 2/3 Must use 1

Code Name

41 Submitter 

DLMS Note:

Must use to identify the reporting activity when different than the materiel owner initiating the 

property transfer.

ZN Losing Inventory Manager 

DLMS Note:

Must use to indicate the materiel owner initiating the property transfer. Required for shipments 

between DoD organizations. 

N103 66 Identification Code Qualifier

 

Description: Code designating the 

system/method of code structure used for 

Identification Code (67) 

X ID 1/2 Must use 1

Code Name

10 Department of Defense Activity Address Code (DODAAC) 

N104 67 Identification Code

 

Description: Code identifying a party or 

other code 

X AN 2/80 Must use 1

N106 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual 

O ID 2/3 Used 1

Code Name

FR Message From 

DLMS Note:

Must use in combination with N101 to indicate the originating DODAAC. Only one loop with 

N106=FR. 
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 9 

G61 Contact Pos: 1100 Max: 10

Heading - Optional

Loop: N1 Elements: 4

 

User Option (Usage): Used

Purpose: To identify a person or office to whom communications should be directed 

Syntax Rules: 

1. P0304 - If either G6103 or G6104 is present, then the other is required.

 

Comments: 

1. G6103 qualifies G6104. 

DLMS Note:

Use to indicate the originating organization point of contact. Use qualifier CD to indicate a point of contact for GFP items. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

G6101 366 Contact Function Code

 

Description: Code identifying the major 

duty or responsibility of the person or group 

named 

M ID 2/2 Must use 1

Code Name

MG Manager

CD Contract Contact

DLMS Note: 

Use to indicate the recipient point of contact. Applicable to GFP items only. 

G6102 93 Name

 

Description: Free-form name 

M AN 1/60 Must use 1

G6103 365 Communication Number Qualifier

 

Description: Code identifying the type of 

communication number 

X ID 2/2 Must use 1

Code Name

EM Electronic Mail

TE Telephone 

DLMS Note:

Use to identify the commercial telephone number. Include the area code and number. 

G6104 364 Communication Number

 

Description: Complete communications 

number including country or area code when 

applicable 

X AN 1/256 Must use 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 10

HL Hierarchical Level Pos: 0100 Max: 1

Detail - Mandatory

Loop: HL Elements: 2

 

User Option (Usage): Must use

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments 

 

Comments: 

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment 

data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01 

could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL 

segment and would be incremented by one in each subsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

5. HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in the 

transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring to 

shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment. 

DLMS Note:

Must use to identify the line item and other information as necessary. The first loop must identify the line item. Use subsequent loops to 

provide any information that is unique to each item. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

HL01 628 Hierarchical ID Number

 

Description: A unique number assigned by 

the sender to identify a particular data 

segment in a hierarchical structure 

DLMS Note: In the first 2/HL/010 loop 

iteration, cite numeric 1. In each subsequent 

loop iteration, increase incrementally by 1. 

M AN 1/12 Must use 1

HL03 735 Hierarchical Level Code

 

Description: Code defining the 

characteristic of a level in a hierarchical 

structure 

DLMS Note: Use as appropriate to identify 

the line item and any specific attributes that 

pertaining to the asset. Use at least one 

iteration of the parent and one child loop in 

each transmission. Only identify the asset by 

line item when transmitting a request. 

M ID 1/2 Must use 1

Code Name

I Item 

DLMS Note:

Must use for the parent loop to identify the line item.

PI Property Identification 

DLMS Note:

Must use for the child loop to identify additional information unique to the item. Do not use 

when BR06=7.
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 11

LIN Item Identification Pos: 0200 Max: 1

Detail - Optional

Loop: HL Elements: 8

 

User Option (Usage): Used

Purpose: To specify basic item identification data 

Syntax Rules: 

1. P0405 - If either LIN04 or LIN05 is present, then the other is required.

2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

3. P0809 - If either LIN08 or LIN09 is present, then the other is required.

4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.

6. P1415 - If either LIN14 or LIN15 is present, then the other is required.

7. P1617 - If either LIN16 or LIN17 is present, then the other is required.

8. P1819 - If either LIN18 or LIN19 is present, then the other is required.

9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.

11. P2425 - If either LIN24 or LIN25 is present, then the other is required.

12. P2627 - If either LIN26 or LIN27 is present, then the other is required.

13. P2829 - If either LIN28 or LIN29 is present, then the other is required.

14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

 

Semantics: 

1. LIN01 is the line item identification 

Comments: 

1. See the Data Dictionary for a complete list of IDs.

2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No., 

ISBN No., Model No., or SKU. 

DLMS Note:

Use in Item loop to identify the line item. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LIN02 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234) 

M ID 2/2 Must use 1

Code Name

FS National Stock Number 

DLMS Note:

Must use the National Stock Number when known.

SW Stock Number 

DLMS Note:

Use to identify a local stock number (LSN). Do not use for Capital Equipment.

ZZ Mutually Defined

DLMS Note:

Use to identify management control number (MCN). Do not use for Capital Equipment. 

LIN03 234 Product/Service ID

 

Description: Identifying number for a 

product or service 

M AN 1/48 Must use 1

LIN04 235 Product/Service ID Qualifier

 

X ID 2/2 Used 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 12

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234) 

Code Name

MG Manufacturer's Part Number 

DLMS Note:

Use in combination with LSN to further identify the item. 

LIN05 234 Product/Service ID

 

Description: Identifying number for a 

product or service 

X AN 1/48 Used 1

LIN06 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234) 

X ID 2/2 Used 1

Code Name

ZB Commercial and Government Entity (CAGE) Code 

DLMS Note:

Use in combination with LSN and manufacturer part number to further identify the item. 

LIN07 234 Product/Service ID

 

Description: Identifying number for a 

product or service 

X AN 1/48 Used 1

LIN08 235 Product/Service ID Qualifier

 

Description: Code identifying the 

type/source of the descriptive number used 

in Product/Service ID (234) 

X ID 2/2 Used 1

Code Name

MN Model Number 

LIN09 234 Product/Service ID

 

Description: Identifying number for a 

product or service 

X AN 1/48 Used 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 13

CS Contract Summary Pos: 0300 Max: 1

Detail - Optional

Loop: HL Elements: 2

 

User Option (Usage): Used

Purpose: To provide information about a contract 

Syntax Rules: 

1. P0405 - If either CS04 or CS05 is present, then the other is required.

 

Semantics: 

1. CS09 is the permissible overage as a percentage of the total contract line item number (CLIN) quantity.

2. CS10 is the permissible shortage as a percentage of the total contract line item number (CLIN) quantity.

3. CS11 is the permissible overage dollar value specified by the contract above which discrepancy action is taken.

4. CS14 is the Unit of Measure stipulated in the contract.

5. CS15 is the contract line item number (CLIN) unit price specified in the contract.

6. CS17 conveys the Critical Application Indicator. A "Y" indicates that a Critical Application Indicator is specified in the contract; an "N" 

indicates that no Critical Application Indicator is specified in the contract.

7. CS18 conveys the Special Requirements Indicator. A "Y" indicates that a Special Requirements Indicator (requiring special testing and or 

evaluation) is specified in the contract; an "N" indicates that no Special Requirements Indicator is specified in the contract. 

Comments: 

1. CS04 may be used to identify the Contract Line Item Number (CLIN) or Extended (or Exhibit) Line Item Number (ELIN).

2. CS07 and CS13 can be used to indicate two different types of special services required. 

DLMS Note:

Use in property identification loop to identify the contract number. Only applies to new procurement shipments. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

CS01 367 Contract Number

 

Description: Contract number 

DLMS Note: 

1. Use to identify the procurement 

instrument identifier (PIID) for the item.

2. When procurement is authorized under a 

PIID call/order number, provide the value in 

the PIID field. 

O AN 1/30 Must use 1

CS02 327 Change Order Sequence Number

 

Description: Number assigned by the 

orderer identifying a specific change or 

revision to a previously transmitted 

transaction set 

DLMS Note: Use to identify a modification 

number to the cited procurement instrument. 

This is the Supplementary Procurement 

Instrument Identifier (Supplementary PIID). 

O AN 1/8 Used 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 14

QTY Quantity Pos: 0400 Max: >1

Detail - Optional

Loop: HL Elements: 3

 

User Option (Usage): Used

Purpose: To specify quantity information 

Syntax Rules: 

1. R0204 - At least one of QTY02 or QTY04 is required.

2. E0204 - Only one of QTY02 or QTY04 may be present.

 

Semantics: 

1. QTY04 is used when the quantity is non-numeric. 

DLMS Note:

Use in item loop to identify the quantity shipped. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier 

Description: Code specifying the type of 

quantity 

M ID 2/2 Must use 1

Code Name

39 Shipped Quantity 

QTY02 380 Quantity

 

Description: Numeric value of quantity 

X R 1/15 Must use 1

QTY03 C001 Composite Unit of Measure

 

Description: To identify a composite unit of 

measure (See Figures Appendix for 

examples of use) 

Comments: 

1. If C001-02 is not used, its value is to be 

interpreted as 1. 

2. If C001-03 is not used, its value is to be 

interpreted as 1. 

3. If C001-05 is not used, its value is to be 

interpreted as 1. 

4. If C001-06 is not used, its value is to be 

interpreted as 1. 

5. If C001-08 is not used, its value is to be 

interpreted as 1. 

6. If C001-09 is not used, its value is to be 

interpreted as 1. 

7. If C001-11 is not used, its value is to be 

interpreted as 1. 

8. If C001-12 is not used, its value is to be 

interpreted as 1. 

9. If C001-14 is not used, its value is to be 

interpreted as 1. 

10. If C001-15 is not used, its value is to be 

interpreted as 1. 

O Comp Must use 1

QTY03-01 355 Unit or Basis for Measurement Code

 

Description: Code specifying the units in 

which a value is being expressed, or manner 

in which a measurement has been taken 

All valid standard codes are used. 

M ID 2/2 Must use 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 15

N9 Reference Identification Pos: 0600 Max: >1

Detail - Optional

Loop: HL Elements: 2

 

User Option (Usage): Used

Purpose: To transmit identifying information as specified by the Reference Identification Qualifier 

Syntax Rules: 

1. R0203 - At least one of N902 or N903 is required.

2. C0605 - If N906 is present, then N905 is required.

Semantics: 

1. N906 reflects the time zone which the time reflects.

2. N907 contains data relating to the value cited in N902.

DLMS Note:

Use in property identification loop. Repeat the loop as necessary to transmit the necessary information. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N901 128 Reference Identification Qualifier

 

Description: Code qualifying the Reference 

Identification 

M ID 2/3 Must use 1

Code Name

BL Government Bill of Lading

DLMS Note:

GBL required when available in the originating APSR.

BM Bill of Lading Number

DLMS Note:

Required when available in the originating APSR.

IK Invoice Number

DLMS Note:

Required when available in the originating APSR.

SE Serial Number 

DLMS Note:

Use to indicate the serial number assigned to the item. The serial number is required for 

serially managed items.

UII Department of Defense Unique Item Identifier 

DLMS Note: 

1. UII required for serially managed items. Use only with action code J (Record) in 

1/BR06/0200.

2. Migration code from version/release 005050 of the X12 EDI standard. 

MF Manufacturers Part Number

DLMS Note:

Use to indicate the manufacturer part number. Do not use when using 2/LIN/0200. 

PM Part Number

DLMS Note: 

Use to indicate the current part number. This is not the manufacturer part number.

W7 Commercial and Government Entity (CAGE) Code

DLMS Note: 

Use to indicate the manufacturer CAGE code.

 

N902 127 Reference Identification

 

Description: Reference info as defined for a 

particular Transaction Set or as specified by 

the Reference Identification Qualifier 

X AN 1/50 Must use 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 16

G62 Date/Time Pos: 0800 Max: 50

Detail - Optional

Loop: HL Elements: 2

 

User Option (Usage): Used

Purpose: To specify pertinent dates and times 

Syntax Rules: 

1. R0103 - At least one of G6201 or G6203 is required.

2. P0102 - If either G6201 or G6202 is present, then the other is required.

3. P0304 - If either G6203 or G6204 is present, then the other is required.

 

DLMS Note:

Use in property identification loop. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

G6201 432 Date Qualifier

 

Description: Code specifying type of date 

X ID 2/2 Must use 1

Code Name

07 Effective Date 

DLMS Note:

Use to indicate Date Placed in Service.

62 Accrual Start Date 

DLMS Note:

Use to indicate Depreciation Start Date.

63 Accrual End Date 

DLMS Note:

Use to indicate Last Depreciation Date.

BT Acceptance 

G6202 373 Date

 

Description: Date expressed as 

CCYYMMDD where CC represents the first 

two digits of the calendar year 

X DT 8/8 Must use 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 17

CTP Pricing Information Pos: 0900 Max: 10

Detail - Optional

Loop: HL Elements: 2

 

User Option (Usage): Used

Purpose: To specify pricing information 

Syntax Rules: 

1. P0405 - If either CTP04 or CTP05 is present, then the other is required.

2. C0607 - If CTP06 is present, then CTP07 is required.

3. C0902 - If CTP09 is present, then CTP02 is required.

4. C1002 - If CTP10 is present, then CTP02 is required.

5. C1103 - If CTP11 is present, then CTP03 is required.

 

Semantics: 

1. CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10% discount is given.

2. CTP08 is the rebate amount. 

Comments: 

1. See Figures Appendix for an example detailing the use of CTP03 and CTP04.

2. See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07. 

DLMS Note:

Use in property identification loop. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

CTP02 236 Price Identifier Code

 

Description: Code identifying pricing 

specification 

X ID 3/3 Must use 1

Code Name

CHG Changed Price 

DLMS Note:

Use to indicate accumulated depreciation valuation.

DPR Discount Price 

DLMS Note:

Use to indicate current valuation price.

PUR Purchase 

DLMS Note:

Use to indicate acquisition price.

UCP Unit cost price 

DLMS Note:

Use to indicate unit price.

ULC Unsalable Item List Cost 

DLMS Note:

Use to indicate salvage value. 

CTP03 212 Unit Price

 

Description: Price per unit of product, 

service, commodity, etc. 

X R 1/17 Must use 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 18

G69 Line Item Detail - Description Pos: 1000 Max: 30

Detail - Optional

Loop: HL Elements: 1

 

User Option (Usage): Used

Purpose: To describe an item in free-form format 

 

DLMS Note:

Use in item loop. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

G6901 369 Free-form Description 

Description: Free-form descriptive text 

M AN 1/45 Must use 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 19

DD Demand Detail Pos: 1100 Max: 100

Detail - Optional

Loop: HL Elements: 1

 

User Option (Usage): Used

Purpose: To describe the type of demand and the intended use of material 

Syntax Rules: 

1. C0201 - If DD02 is present, then DD01 is required.

2. P030405 - If either DD03, DD04 or DD05 are present, then the others are required.

3. C0605 - If DD06 is present, then DD05 is required.

4. C1009 - If DD10 is present, then DD09 is required.

 

Semantics: 

1. DD08 transmits the stock level indicator. A "Y" indicates that the material is normally carried in stock; an "N" indicates that the material is 

not normally stocked. 

DLMS Note:

Use in item loop. Use this segment to indicate the item is capital equipment. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DD08 1073 Yes/No Condition or Response Code

 

Description: Code indicating a Yes or No 

condition or response 

O ID 1/1 Must use 1

Code Name

Y Yes 

DLMS Note:

Use to indicate the item in the item loop is Capital Equipment.
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 20

LDT Lead Time Pos: 1200 Max: 3

Detail - Optional

Loop: HL Elements: 3

 

User Option (Usage): Used

Purpose: To specify lead time for availability of products and services 

 

Semantics: 

1. LDT04 is the effective date of lead time information. 

Comments: 

1. LDT02 is the quantity of unit of time periods. 

DLMS Note:

Use in property identification loop. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LDT01 345 Lead Time Code

 

Description: Code indicating the time range

M ID 2/2 Must use 1

Code Name

AX From Date of Award to Date of Completion 

DLMS Note:

Use to indicate Depreciation Period (Days, Month, and Year).

QO Service Estimate Number 

DLMS Note:

1. Use to indicate estimated useful life of the item. 

2. At this time a local code ‘QO’ is established for use in 536R, version 4030. A data 

maintenance action will be submitted for establishment of ‘QO - Service Estimate Number’ in 

a future version. 

LDT02 380 Quantity

 

Description: Numeric value of quantity 

M R 1/15 Must use 1

LDT03 344 Unit of Time Period or Interval

 

Description: Code indicating the time 

period or interval 

M ID 2/2 Must use 1

Code Name

CY Calendar Year

DY Day

MO Month
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 21

LM Code Source Information Pos: 1700 Max: 1

Detail - Optional

Loop: LM Elements: 1

 

User Option (Usage): Used

Purpose: To transmit standard code list identification information 

 

Comments: 

1. LM02 identifies the applicable industry code list source information. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

 

Description: Code identifying the agency 

assigning the code values 

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD)
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 22

LQ Industry Code Pos: 1800 Max: 100

Detail - Mandatory

Loop: LM Elements: 2

 

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes 

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

 

DLMS Note:

Must use to further describe the item. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

 

Description: Code identifying a specific 

industry code list 

O ID 1/3 Must use 1

Code Name

78

83

Project Code

DLMS Note:

Perpetuate project code when available.

Supply Condition Code

DLMS Note:

Supply condition code (SCC) is required.

EQ Controlled Inventory Item Code 

DLMS Note:

Perpetuate controlled inventory item code (CIIC) when available. 

LQ02 1271 Industry Code

 

Description: Code indicating a code from a 

specific industry code list 

X AN 1/30 Must use 1
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 23

N1 Name Pos: 1900 Max: 1

Detail - Optional

Loop: N1 Elements: 4

 

User Option (Usage): Must use

Purpose: To identify a party by type of organization, name, and code 

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

 

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID 

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual 

M ID 2/3 Must use 1

Code Name

ZP Gaining Inventory Manager 

DLMS Note:

Must use to indicate the materiel owner receiving property transfer. Required when the 

recipient of the shipment is Government ICP.

DIR Distribution Recipient 

DLMS Note:

Use to indicate the recipient organization when different from the materiel owner receiving 

property transfer. 

N103 66 Identification Code Qualifier

 

Description: Code designating the 

system/method of code structure used for 

Identification Code (67) 

X ID 1/2 Must use 1

Code Name

10 Department of Defense Activity Address Code (DODAAC) 

N104 67 Identification Code

 

Description: Code identifying a party or 

other code 

X AN 2/80 Must use 1

N106 98 Entity Identifier Code

 

Description: Code identifying an 

organizational entity, a physical location, 

property or an individual 

O ID 2/3 Used 1

Code Name

TO Message To 

DLMS Note:

Must use in combination with N101 to indicate the recipient DODAAC. Only one loop with 

N106=FR.
004030F536R0RP00 Enclosure 2, ADC 1415

 Page 25

SE Transaction Set Trailer Pos: 2400 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

 

User Option (Usage): Must use

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending 

(SE) segments)

 

 

Comments: 

1. SE is the last segment of each transaction set. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

SE01 96 Number of Included Segments

 

Description: Total number of segments 

included in a transaction set including ST 

and SE segments 

M N0 1/10 Must use 1

SE02 329 Transaction Set Control Number

 

Description: Identifying control number that 

must be unique within the transaction set 

functional group assigned by the originator 

for a transaction set 

DLMS Note: Cite the same number as the 

one cited in ST02. 

M AN 4/9 Must use 1
Enclosure 3, ADC 1415

Page 1 

Enclosure 3

DLMS 536R Acquisition and Valuation History Diagram. 

Item Attributes (Child) Max >1

Beginning Segment (Pos. 0200, Max 1)

BR01 00 Original

BR02 TS Transfer Statement

DLMS Note. Use for Acquisition and Valuation History Data

Use to transmit acquisition and valuation history data. 

Use BR06 to identify if this is an original, a correction or to request a record

BR03 Date

BR06 J – Record

DLMS Note: Original Acquisition and Valuation History Data

 CO – Correct

DLMS Note: Corrected Acquisition and Valuation History Data

 7 – Request 

DLMS Note: Request for Acquisition and Valuation History Data (Inquiry)

BR09 Time

Hierarchical Level (Pos. 0100, Max 1) 

HL01 Sequence Num

 DLMS Note: In the first 2/HL/010 loop iteration, cite numeric 1. In each

 subsequent loop iteration, increase incrementally by 1.

HL03 I Item (Parent)

PI Property Identifier(Attributes - Child)

LIN Item Identification (Pos. 0200, Max 1) 

LIN02 – FS National Stock Number

 SW Stock Number

 ZZ Mutually Defined

LIN03 - Value

LIN04 - MG Manufacturer's Part Number

LIN05 - Value

LIN06 - ZB CAGE Code

LIN07 - Value

LIN08 – Model Number

N9 Ref. Identification (Pos. 0600 Max >1) 

SE Serial Number

UII Unique Item Identifier (Real Code from 5050)

IK Invoice Number

BL Bill of Lading (Gov)

BM Bill of Lading Number

MG Manufacturer Part Number (Serially Managed Items Only)

PM Part Number (Serially Managed Items Only)

ZB Manufacturer CAGE Code (when LIN06 is not used)

G69 Line Item Detail (Pos. 1000, Max 1) 

G6901 – Free Form Text (up to 45 characters)

CTP Pricing Information (Pos. 0900, Max 10)

CTP02 – Price Identifier Code

 UCP Unit Cost Price (Unit Price)

 PUR Purchase Price (Acquisition Price)

 CHG Changed Price (Accumulated Depreciation Val.)

 DPR Discount Price (Current Valuation Price)

 ULC Useable Item List Cost (Salvage Value)

CTP03 – Value

G62 Date/Time Ref. (Pos 0800, Max 50) 

G6201 – 07 Effective Date (Date Placed in Service)

 BT Acceptance

 62 Accrual Start Date (Depreciation Start Date)

 63 Accrual End Date (Last Depreciation Date)

G6202 – Date Value

N1 Name (Pos. 0700, Max 1)

N101 43 Submitter

ZN Losing Inventory Manager

N103 10 Department of Defense Activity Address Code (DODAAC)

N104 DODAAC Value

N106 FR Message From

LM Code Source Info. (Pos 1700, Max 1) 

DF Department of Defense (DoD)

LQ Industry Code (Pos. 1800, Max 100) 

LQ01 78 Project Code

 83 Supply Condition Code

 EQ CIIC

LQ02 – Value

Set Transaction Set Trailer (Pos. 2400, Max 1)

SE01 - Number of Included Segments

SE02 - Transaction Set Control Number

LDT Lead Time (Pos. 1200, Max 3)

LDT01 – AX From Date of Award to Date of Completion 

(Depreciable Period)

 (Days/Month, Year)

 QO Service Estimate Number (Est. Useful Life) 

LDT02 – Quantity (Depreciable Period numeric value )

LDT03 Unit of Time

 DY Calendar Days (Day)

 MO Month (Month)

 CY Calendar Year or ZZ Mutually Defined (Year)

DLMS 536R Acquisition and Valuation History 6/09/2022

G61 Contact (Pos. 1100 Max 10) 

G6101 MG – Manager

CD – Contract Contact

G6102 Free From Text

G6103 EM - Electronic Mail

 TE – Telephone

G6104 Value

N9 Reference Identification (Pos. 0300, Max 10)

N901 CT - Contract Number

TN – Transaction Reference

TG - Transportation Control Number (TCN)

6L - Agent Contract Number

SI - Shipment Number

N902 Value

CS Contract Summary (Pos. 0300, Max 1) 

CS01 – Contract Number (PIID)

CS02 – CS03 Release Number

QTY Quantity (Pos. 040, Max 1) 

QTY01 – 39 Shipped Quantity 

QTY02 – Quantity

QTY03 – Composite Unit of Measure

N1 Name (Pos. 1900, Max 1) 

N101 ZP Gaining Inventory Manager

N103 10 DODAAC)

M4 Department of Defense RIC

N104 DODAAC/RIC Value

N106 TO Message To

Set Header

ST01 536 Logistics Reassignment

ST02 Unique ID set by Originator

Parent Loop, Max 1 Child Loop, Max >1

DD Demand Detail (Pos 1100, Max 1) 

Yes/No Condition or Response Code

Y - Yes

G62 Date/Time (Pos. 0400, Max 10)

11 - Date Shipped

PE - Period End (Period of performance expiration date).

17 – Est. Delivery Date Expected property return date (when different from period of performance).
Enclosure 4, ADC 1415

Page 1

Enclosure 4 

DPC ADC 1415 Review Comments and DEDSO Responses.

Comments:

1.The X.12 title of the 536 transaction is Logistics Reassignment. I'm not sure it's appropriate to 

change the transaction title.

a. Rafael – the logistic Reassignment transaction is the DLMS 536L. This is a new DLMS 

transaction with a new name. 

2.What is the use case for APSR to PIEE? There is existing functionality to transmit new delivery 

data from PIEE WAWF to APSR upon DoD Acceptance. Is the intent to replace that current 

capability with the new transaction?

a. Rafael – No. The intent here is to provide a way for the DoD to obtain information from 

a procurement shipment at any time during the life cycle of the item. For example: An 

APSR may use this to inquiry about information that they never received, or they are 

missing. In this scenario, PIEE could’ve sent the transaction but either the transaction 

didn’t make it to the APSR or perhaps the information needed was not provided. The 

APSR would use this transaction to inquiry the information by PIID/CALL so they can 

complete their inventory record and therefore follow the DoDM 4140.01 Vol 11, as well 

as the DoDI 5000.64 regarding mandatory data elements. The organization that transmits 

the inquiry may not necessarily the one who originally purchased the item. 

3.This data is required primarily for serially managed items which have peculiar data such as date 

placed in service/acquisition date. If the request contains no individual item identifier (SN/UII) 

how will the losing APSR know for which item to provide the data?

a. Rafael- the intent is to allow the inquiry by shipment as opposed to by individual 

item. PIEE would response with the information available for that specific PIID/CALL 

or shipment document. 

4.Agree LSNs are a terrible idea. So why is LSN used as one of the request data elements?

a. Rafael – A Component may have one or more APSR and items under LSN. Policy 

allows LSNs but only internally to that organization/service. We want to make sure we 

provide as much flexibility as we can. In addition, weapons use materiel control 

numbers (MCN) which are also LSNs, and they are authorized to use. As opposed to 

LSNs, the MCNs are better controlled, and Army ensures no duplicates across the 

Enterprise.

5.Here is contract number reference 1 - New procurement (which could only be coming from WAWF 

and WAWF does not create this transaction). Where is the Order Number field for new 

procurement?

a. Rafael –Although this functionality is not available today at WAWF, the intent is for 

PIEE/WAWF to be able to respond to the inquiries sent by DoD Components. The 

Contractor ICP Procurement Instrument is NOT the PIID or contract number for the 

item. This is the PIID authorizing the contractor to act on behalf of the government. The 

PIID or PIID/Call/Order Number for the item is the Contract Number (all values in the 

same place as the PIID). 

6.Why would LSN ever be required?

a. Rafael- when using LSN, the transaction requires 3 elements to uniquely identify the 

item: the LSN, Part Number, and CAGE. 

7.N901 states that UII is required for serially managed items. There are many items in DoD inventory 

which are serially managed but lack UII and are tracked by Serial Number. This restriction should 

be removed. 
Enclosure 4 ADC 1415

Page 2

a. Rafael -The UII is today required when available. This requirement is also in support of 

Next Gen IUID. 

8.If the "Release Number" is in the PIID field, why is it a separately identified item here?

a. Rafael -I made the necessary correction to alleviate the confusion between the different 

types of PIID.

9.If quantity can be more than one, how are multiple date placed in service and SN/UII handled?

a. Rafael -The QTY is at the parent level and when including serial numbers, the QTY must 

match the total number of serial numbers and/or UII. It can be 1 or more. Each item by 

serial number/UII may have a different date place on service. 

10. Is the difference between "unit price" and "acquisition price" that the latter is related to new 

procurement? Why does it matter?

a. Rafael - They can be different. If you purchased the item 10 years from now, the unit 

price may be lower than the original acquisition cost. 

11. Why is this limited to ICP-to-ICP transactions - could there never be a different use case? Like 

identifying the DoDAAC of the owning org regardless.

a. Rafael – The idea with this transaction is for the services to be able to create their initial 

inventory record. The transaction only works by DODAAC but only government. Under 

GFP, the item is never owned by the contractor.

12. This is the fourth data element in the table, highlighted in yellow. I do not understand why this 

would be limited to a C-ICP. A losing org could transfer ownership of an asset to a gaining org 

that is GFP in a non C-ICP environment. However, in either case, why is the GFP contract 

number needed? It provides zero data about the item itself. Even in a C-ICP situation, DoD must 

have the record about the item in the DoD APSR. So this data should NEVER be coming from a 

contractor.

a. Rafael – the DoDI 5000.64 requires the PIID authorizing the contractor to act on behalf 

of the government and it should be on every transaction generated by the contractor. 

13. How are the other data (date placed in service, depreciation, etc) associated to the individual 

item?

a. Rafael – Each individual item may have different date placed in service or depreciation if 

these were purchased at different times. 

14. How can a "numeric value" have data type of "alpha character"?

a. Rafael – this is a qualifier that indicates if you are using days, months, or years for the 

depreciation. This is not the actual depreciation value. 

15. What is the use case here? Contractor does not need to know this data. 

a. Rafael – This would apply to contractor ICPs. They must indicate the PIID authorizing 

them to act on behalf of the government.

16. What is the use case here? The RR provided by the contractor upon delivery does not have 

depreciation period, etc. That is defined by DoD. The item and valuation data is already provided.

a. Rafael – We are simply identifying all known systems to be impacted. PIEE is listed as 

one. 

17. DAAS should use the GS segment to identify the from and to. That is how the X.12 standard is 

meant to work.

a. Rafael – Noted. However, all of our transactions use the N1 instead.