DEFENSE LOGISTICS AGENCY HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

June 15, 2017

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

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

Revision to DLMS 846D and 846S Logistics Reassignment Transactions to Support 

Government Furnished Property (GFP) Accountability during Logistics 

Reassignment between Air Force Contractor Inventory Control Points (CICP) and 

Air Force or DLA ICPs (Supply)

We are forwarding the attached approved change to DLM 4000.25, Defense Logistics 

Management Standards (DLMS), for implementation. The Enterprise Business Standards 

Office will post updated DLMS Implementation Conventions (IC) to the DLMS Web at 

www.dlmso.dla.mil/elibrary/TransFormats/140_997.asp, within 10 days from the above date.

Addressees may direct questions to Ms. Mary Jane Johnson, or Mr. Rafael Gonzalez, at 

email: DLMSSupply@dla.mil. Others must contact their designated Supply PRC representative 

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

 

HEIDI M. DAVEREDE

Program Manager

Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD (SCI)

ODASD (SCI) Integrated Materiel Management Committee Chair

and Nonconsumable Item Program Chair

OUSD DPAP (PDI)

Air Force Finance PRC representative
Attachment, ADC 1232

Page 1

Attachment to ADC 1232

Revision to DLMS 846D and 846S Logistics Reassignment Transactions to Support 

Government Furnished Property (GFP) Accountability during Logistics Reassignment between 

Air Force Contractor Inventory Control Points (CICP) and Air Force or DLA ICPs

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Mr. John “Jack” Dillon, HAF/A4PT; 937-904-0815; DSN: 674-0815; 

or email: john.dillon.2.ctr@us.af.mil

b. Functional POC: Mr. Colquitt “Quitty” Lawrence, HAF/A4LR; 703-692-2348; 

DSN: 222-2348; or email: colquitt.lawrence.civ@mail.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply/Finance/Logistics Reassignment

b. Primary/Secondary Functional Process: Government Furnished PropertyAccountability (GFP-A)

3. REFERENCES:

a. DOD 4140.26-M, Defense Integrated Materiel Management Manual for Consumable 

Items, Volume 4, Logistics Reassignment, September 24, 2010

b. DODM 4140.68, Integrated Materiel Management of Nonconsumable Items, Enclosure 6, 

Procedures for Migration of a NIMSC Code, September 2, 2014

c. DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 2, Supply 

Standards and Procedures, Chapter 9, Logistics Reassignment

d. Air Force Instruction (AFI) 23-119 Exchange, Sale or Temporary Custody of Nonexcess Personal Property, 

http://static.e-publishing.af.mil/production/1/af_a4/publication/afi23-119/afi23-119.pdf

e. DODM 4140.01, DoD Supply Chain Materiel Management Procedures, Volume 6, 

Materiel Returns, Retention, and Disposition

f. DODM 4140.01, DoD Supply Chain Materiel Management Procedures, Volume 5, 

Delivery of Materiel

g. ADC 1224, Requirements for Air Force Government Furnished Property (GFP) 

Accountability including Identification of the Contractor Inventory Control Point (CICP), the 

Physical Location of Property, the Authorizing Procurement Instrument Identifier (PIID), 

Disposal Information in the Issue Transaction, and Enhanced Data Content in Inventory-Related 

Transactions (Supply/Contract Administration), March 1, 2017
Attachment, ADC 1232

Page 2

h. ADC 1225, Revise DLMS 527R Receipt Transaction for Intra-Air Force Government 

Furnished Property (GFP) Accountability to Include Identification of the Contractor Inventory 

Control Point (CICP), Addition of Moving Average Cost (MAC), and Authorization to Use Latest 

Acquisition Cost (LAC) and Acceptance Date (Supply), March 7, 2017

i. ADC 1226, Revise DLMS 824R Reject Advice Transaction in Support of Intra-Air Force 

Government Furnished Property-Accountability (GFP-A) (Supply), March 10, 2017

j. ADC 1227, DLMS 832N Catalog Data Support Transaction to Add Catalog Data 

Elements for Air Force Contractor Inventory Control Point (CICP) Use under GovernmentFurnished Property-Accountability (GFP-A) Capability Initiative (Supply), June 2, 2017

k. ADC 1228, Revise DLMS 846P Physical Inventory Request and 846R Location 

Reconciliation Request to Enhance End of Day/Reconciliation Process, June 9, 2017

l. ADC 1238, Revise DLMS 527R Materiel Receipt Acknowledgement (MRA) and 

Disposition Services Turn-In Receipt Acknowledgement (TRA) Transactions to Allow Air Force 

Contractor Inventory Control Points (CICP) to Forward Transaction Images in Support of Air 

Force Government Furnished Property (GFP) Accountability (Supply), March 1, 2017

m. Office of the Under Secretary of Defense for Acquisition, Technology and Logistics 

(OUSD (AT&L)) Memo of January 11, 2010, Subject: Government Furnished Property (GFP), 

Describes the requirements for strengthening the accountability 

n. DODI 5000.64, Accountability and Management of DOD Equipment and Other 

Accountable Property

o. DODI 4161.02, Accountability and Management of Government Contract Property

p. Request for Implementation Date for ADC 12, Revised Procedures for Logistics 

Reassignment, June 3, 1998 (to be reissued as ADC 1141)

q. AFI 23-101, Air Force Materiel Management, December 14, 2016,

http://static.e-publishing.af.mil/production/1/af_a4/publication/afi23-101/afi23-101.pdf

4. APPROVED CHANGE(S): Substantive changes from PDC 1232 are highlighted in green.

a. Brief Overview of Change: In order to establish Air Force GFP accountability, Air 

Force Contractor Inventory Control Points (CICPs) are now required to share inventory accounting 

transactions and logistics reassignment transactions with the Air Force accountable property system 

of record (APSR). The APSR will maintain the Air Force accountable property record for all Air 

Force-owned contractor managed and possessed property. Air Force defines the term ‘inventory 

accounting transactions’ used in this ADC, as DLMS transactions that impact the Air Force owned 

inventory in possession of the CICP and impact the financial statement for the Air Force. This 

change revises DLMS 846D Logistics Reassignment Transfer and Decapitalization and DLMS 

846S Logistics Reassignment Storage Information transactions to allow the CICP to send an image 
Attachment, ADC 1232

Page 3

transaction to the Air Force APSR, identify the CICP, identify the authorizing procurement 

instrument identifier (PIID), and authorize use of the transaction set preparation date and time. 

b. Background:

(1) Overarching logistics reassignment policy is published by the Office of the 

Deputy Assistant Secretary of Defense Supply Chain Integration (ODASD SCI) in DOD 4140.26-

M, Defense Integrated Materiel Management Manual for Consumable Items, Volume 4 (Reference 

3.a.) and DODM 4140.68, Integrated Materiel Management of Nonconsumable Items (Reference 

3.b.). Air Force CICPs are the integrated materiel managers (IMM) for specific Air Force owned 

materiel and are listed as source of supply in Federal Logistics Information Service (FLIS). As 

the IMM for an item changes from the CICP to an Air Force or DLA inventory control point (ICP), 

as a result of logistics reassignment in accordance with either Reference 3.a or 3.b, the DLMS, 

Volume 2, Chapter 9 (Reference 3.c.), logistics reassignment process occurs between Air Force 

CICP as the losing item manager (LIM) and either an Air Force or DLA ICP as the gaining item 

manager (GIM). Likewise, as the IMM for an item changes to a CICP, in accordance with either 

Reference 3.a or 3.b, the logistics reassignment process occurs between an Air Force CICP as the 

GIM and Air Force or DLA ICP as the LIM.

(2) Logistics Reassignment of assets managed by an Air Force CICP will only be 

done between a CICP and Air Force for nonconsumables, or between a CICP and DLA for 

consumables. The CICP managed items of supply that become common, i.e., used by another Air 

Force or another Service weapon system, must transfer to DLA or organic Air Force management 

in accordance with AFI 23-119 (Reference 3.d.).

(3) At Supply Process Review Committee (PRC) Meeting 16-1, October 19, 2016, 

ODASD (SCI) noted that DODM 4140.01, Volume 6 (Reference 3.e), was updated to address

government inventory management by contractors. Volume 6 requires that with respect to 

sustainment contracts in which the contractor manages government inventory, the buying DoD 

Components will assign a materiel manager to provide oversight of government inventory that is 

managed by contract.

(4) The term CICP is used to represent a contractor assigned primary 

responsibility for materiel management of a group of items, either for a particular Military Service 

or for the Department of Defense as a whole. In addition to IMM or ICP functions, a CICP may 

perform other logistics functions in support of a particular Military Service or for a particular end 

item (e.g. centralized computation of retail requirements levels and engineering tasks associated 

with weapon system components). 

(5) CICPs are required to maintain and report accountability for Air Force-owned 

contractor-managed and possessed property. However, Air Force accountability is incomplete 

for contractor-managed and possessed Air Force-owned property (Operating Materials and 

Supplies/Spares). The Air Force is unable to track end-to-end logistics and financial 

transactions, provide total asset visibility (TAV), and report property inventory values accurately 

and timely. DODM 4140.01 Volume 5 (Reference 3.f.), Subparagraph 2.b.(4)(e). requires 

services to:
Attachment, ADC 1232

Page 4

“Take applicable actions necessary to ensure that the physical on-hand quantity and the total 

item property record quantity are in agreement for all DoD materiel that is not in the physical 

custody of DoD storage activities. For example, owning materiel managers will ensure 

accuracy for property records where contractors are responsible for the physical custody of 

government-owned inventory located at contractor facilities or DoD storage activities.” 

(6) The Air Force chartered the GFP–Accountability (GFP-A) capability initiative 

to provide property accountability/control of contractor-managed and possessed Air Force-owned 

property (inclusive of materiel and equipment) through implementation of standard and integrated 

Air Force logistics and contractor processes to address a material weakness on the Air Force 

Financial Statements. This capability will establish and maintain accountable inventory records 

for GFP that reflects current quantity, status, location, condition and authorizing contract, as well 

as establish an audit trail to update and track end-to-end logistics and financial transactions. This 

change is one of a series of DLMS changes supporting the Air Force GFP-A capability initiative 

(refer to References 3.g., 3.h., 3.i., 3.j., 3.k., and 3.l.).

(7) Contractor managed and possessed GFP is one type of GFP and is the sole 

focus of this capability initiative. The above problem statement does not apply to the other types 

of GFP, as the Air Force has solutions in place for the reporting of logistics and financial data. 

Air Force will only report Air Force-owned property in the Air Force GFP-A APSR. Air Force

CICPs often use commercially available inventory management systems to manage Air Forceowned property. The CICPs record inventory impacting accounting transactions in these 

systems. The Air Force has selected the Defense Property Accountability System (DPAS) as its 

APSR for contractor managed and possessed Air Force-owned GFP. 

(8) Air Force CICPs, using their own inventory management systems, will 

provide their transactions and images of their transactions, in DLMS formats, to DPAS via the 

Defense Automatic Addressing System (DAAS). Note that this is over and above the 

transmission of the applicable DLMS transactions between the CICP and the CICP’s warehouse 

or subcontractor when external communication (outside the inventory management system) is 

used for the various logistics reassignment processes discussed in this change. DPAS will be a 

mirror image of the CICPs inventory management systems. To maintain this accuracy, the CICP 

requires capability to:

(a) send DPAS images of logistics reassignment transactions, which the 

CICP sends to, or receives from, a GIM/LIM external system;

(b) identify to DAAS via party to receive copy, when DAAS must make 

an image for DPAS of a logistics reassignment transaction the CICP sends to external systems;

(c) authorize the transaction set date/time stamp in the beginning 

segment, and add a functional transaction preparation date/time to the detail table;

(d) identify the PIID authorizing GFP issued to the CICP (if GFP is 

authorized on a PIID call/order, the PIID call/order number will be included).
Attachment, ADC 1232

Page 5

(9) ADC 1238 (Reference 3.l.) allows the Air Force CICP to transmit images of 

DLMS 527R Materiel Receipt Acknowledgement (MRA) and Disposition Services Turn-in 

Receipt Acknowledgement (TRA) transactions, which the CICP receives from external systems,

to the Air Force APSR for GFP, (i.e., DPAS). This change leverages that concept to allow the 

CICP to send to the APSR images of DLMS 846D and 846S logistics reassignment transactions, 

which the CICP received from an external system.

(10) Prior to submission of this approved change, the DLMS Program Office 

identified a future requirement for transition from routing identifier codes (RIC) to DoDAACs. 

This transition will require DAAS to route and process DLMS transactions based upon the 

DoDAAC-To (rather than the current RIC-To) in the transaction and use the communication 

routing identifier (COMMRI) associated with the DoDAAC in the DOD Activity Address Directory 

(DoDAAD). While developing the series of Air Force GFP-A approved changes, the DLMS 

Program Office initially attempted to authorize use of the DoDAAC-To on a limited basis to 

identify the Air Force program manager account in DPAS. However, the DLMS Program Office 

subsequently recognized the affected systems could not implement this change within the required 

timeline for implementation. The DLMS Program Office, DAAS, and the Air Force agreed on an

alternate approach to facilitate immediate implementation. This alternate approach will 

accommodate the potential lack of available RICs within the required Air Force series as the Air 

Force establishes new program managers’ accounts in DPAS. Therefore, pending development of 

functionality for DoDAAC-based routing/processing, the Air Force will use RICs to identify both 

CICPs and program managers. This change authorizes the Air Force to use a single generic RIC 

representing the Air Force APSR if insufficient program manager RICs are available to identify all 

program managers. DAAS will use this RIC/DoDAAC/COMMRI combination for transaction 

processing while DPAS will use the supplemental identification of the specific program manager 

DoDAAC required within each transaction. This change reflects the interim solution described. 

c. Approved Change in Detail. Revise DLMS 846D Logistics Reassignment Transfer 

and Decapitalization and 846S Logistics Reassignment Storage Information /Reply 

implementation conventions (IC) to:

(1) Provide DLMS notes and new data fields as needed to clarify that these 

transactions are transmitted between the Air Force CICP and the Air Force program manager for 

the purpose of GFP accountability. For the logistics reassignment function, the CICP can be 

either the LIM or the GIM, and will be identified as such in the transaction as appropriate using 

existing qualifiers. The Air Force will assign each CICP to a program manager identified by a 

unique DoDAAC in DPAS. DAAS will use the COMMRI for the RIC associated with the 

program manager’s DoDAAC in the DoDAAD to pass the transaction to DPAS. Alternatively, 

if the Air Force has insufficient RICs available to identify the specific program manager in the 

transaction RIC-To, this change authorizes the Air Force CICP to identify the Air Force APSR 

by its generic RIC for DAAS routing/processing and separately include the CICP DoDAAC so 

DPAS can post the record to the appropriate program manager account.

(2) Authorize use of the DLMS enhancement for the beginning segment date 

and time for creation of the transaction set (BIA Beginning Segment, BIA04 Date and BIA05 

Time). This change identifies the date and time as authorized DLMS enhancements per 
Attachment, ADC 1232

Page 6

standard DLMS modernization procedures to provide a systemic beginning segment transaction 

set preparation date/time stamp for all transactions. This date and time is not for functional use 

even though they may coincide with the date and time of a business process.

(3) Establish two new data elements for the Transaction Preparation Date and 

Time. These data fields are applicable for functional use. 

(4) Add a data field for identification of the authorizing PIID (formerly contract 

number). This is the DFARS PIID authorizing GFP to be issued to the Air Force CICP as 

required by Office of the Under Secretary of Defense for Acquisition, Technology and Logistics 

(OUSD (AT&L)) Memorandum of January 11, 2010, Subject: Government Furnished Property 

(GFP) (Reference 3.m). Adding this field will allow the Air Force CICP to identify the

authorizing PIID, as applicable, in the 846D and 846S transaction images sent to the Air Force 

program manager’s APSR (DPAS). If GFP is authorized under a PIID call/order number (F in 

9th position), the value of the PIID call/order will be provided in the PIID field. Inclusion of the 

PIID will strengthen the accountability and management of government owned property when 

property is possessed by contractors. This change also allows identification of legacy-formatted 

call/order numbers for CICP use, pending implementation of the PIID-formatted contract number. 

(5) Allow the Air Force CICP to transmit images of the 846D and 846S logistics 

reassignment transactions to DPAS. There are 2 scenarios for the image transaction: 

Scenario 1: If the CICP is receiving the logistics reassignment transaction from an 

external system, the CICP generates an image of that transaction using the Action Code FI (same 

concept was used for the MRA and TRA under ADC 1238).

Scenario 2: If the CICP is generating the logistics reassignment transaction, the CICP

would send one transaction with an extra N1 loop for an additional transaction recipient. The 

additional receipient is identified by “Party to Receive Reports” (2/N101/450/code ZD) and Party 

to Receive Copy (2/N106/450/code PK). DAAS would then make the image, inserting Action 

Code FI for image, and forward the transaction image to DPAS. The scenario 2 approach for 

CICP generated transactions would eliminate the need for the CICP to send the transaction twice 

(one for the live transaction to external GIM or LIM system, and one for the image to DPAS). 

(a) Action Code FI image transaction. Open the beginning segment

action code (1/BIA06/020) and add qualifier FI to identify an image transaction. Conveying 

qualifier FI 

1. provides the Air Force CICP, acting as the GIM, a mechanism 

to identify an image of a logistics reassignment 846D transaction to send to DPAS, when the 

CICP receives the 846D from an external system (i.e., the DLA or Air Force LIM), and

2. allows DAAS to insert Action Code FI to identify an image to 

DPAS, when the CICP generates an 846D or 846S transaction to send to an external system, and 

identifies DPAS an additional party to receive copy. Air Force CICP acting as a LIM generates
Attachment, ADC 1232

Page 7

846D transactions to the external systems for the Air Force and DLA GIM; Air Force CICP 

acting as a LIM may send 846S to an external storage activity system. 

(b) Party to Receive Reports and Party to Receive Copy. Add new at

2/N101/450 Code ZD – Party to Receive Reports, for Air Force GFP accountability to identify 

the RIC representing the Air Force program manager. The Party to Receive Reports at

2/N101/450, is used in conjunction with new 2/N106/450 Code PK-Party to Receive Copy, when 

the CICP generates an 846D or 846S transaction, as a way to alert DAAS to provide an image of 

the logistics reassignment transaction to DPAS so that DPAS can update the record associated 

with the CICP DoDAAC in the APSR.

d. Revisions to DLM 4000.25 Manuals: Revise DLMS 846D and 846S as shown in 

Enclosure 1.

e. Approved Transaction Flow: See Enclosure 2 for transaction flow diagram and 

narrative. The LIM processes logistics reassignment in accordance with requirements of the 

logistics reassignment policy referenced in DOD 4140.26-M or DODM 4140.68, and the 

procedures in DLM 4000.25, Volume 2, Chapter 9. 

(1) Prior to the logistics reassignment effective transfer date (ETD), the Air Force 

LIM moves all assets to the GIM’s storage activity. On the ETD, the LIM sends the 846S

Logistics Reassignment Storage Information transaction to the storage activity to request transfer 

of quantities between the LIM and GIM ownership accounts on the storage activity records as a 

result of a logistics reassignment. If the CICP is the LIM, the CICP sends the DLMS 846S

Logistics Reassignment Storage Information transaction, including PIID, and party to receive 

reports/party to receive copy, to DAAS, which routes the transaction to the GIM’s storage 

activity, and DAAS creates and sends an image of that 846S to DPAS (based on CICP inclusion 

of the second N1 loop for party to receive reports/party to receive copy). If the CICP is the GIM, 

the LIM sends the 846S through DAAS to the CICP, and the CICP sends an image (1/BIA06/020 

Code FI) of that 846S through DAAS to DPAS. The image of 846S Logistics Reassignment 

Storage Information transaction notifies DPAS to change the DPAS master record for the 

logistically reassigned assets, to the GIM ownership. 

(2) On the effective transfer date, the LIM sends the GIM 846D Logistics Reassignment

Transfer transaction to transfer on-hand balances, from appropriation accounts other than stock fund of 

the loser. If the Air Force CICP is the LIM, the CICP processes DLMS 846D Logistics Reassignment

Transfer with the transfer quantities, including PIID and the party to receive reports/party to receive 

copy, and sends to DAAS, who routes the transaction to the GIM and creates the image to send to 

DPAS. The 846D identifies the on-hand item quantities that are being logistically reassigned to the 

GIM. If the CICP is the GIM, the LIM sends the 846D to the CICP and the CICP sends an image of 

the 846D to DPAS. Air Force CICP processes DLMS 947I (version 4030) Inventory Adjustment 

(Logistics Transfer) (with 2/W1901/0200 code AK) to decrease/increase their inventory and sends to 

DAAS, which routes the transaction to DPAS. The 947I decrements/increments the inventory balances 

to reflect the 846D quantities being logistically reassigned to the GIM. DPAS also verifies that the 

DLMS 846D quantities match the DLMS 947I. If for any reason the quantities do not match, the Air 

Force Program Manager and Air Force CICP are notified to take corrective action. Note: There are 
Attachment, ADC 1232

Page 8

many other steps in the process of a logistics reassignment, but they are not relevant to adding the

transaction set preparation date and time to the DLMS 846D and 846S transactions.

f. Alternatives: None.

5. REASON FOR CHANGE: This change addresses a material weakness on the Air Force financial 

statements and supports Financial Improvement and Audit Readiness (FIAR). The new procedures 

also allow Air Force CICPs to interface with the Air Force’s APSR. Finally, they support compliance 

with DODI 5000.64 (Reference 3.n.) and DODI 4161.02 (Reference 3.o.) to trace transactions 

involving GFP electronically and cite the Air Force CICP’s PIID.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: More detailed inventory accounting logistics reassignment transactions and 

records allows the Air Force to automatically match DLMS 846D logistics reassignment transfer 

transactions and the corresponding 947I Inventory Adjustment (Logistics Transfer) transactions to 

ensure accurate asset valuation and maintain key supporting documents used by FIAR auditors for 

contractor managed and possessed Air Force-owned GFP in DPAS.

b. Disadvantages: Requires resources for Air Force, DPAS, and DAAS, system 

modifications to accommodate the Air Force’s CICP related requirements and additional data 

content described in this change. 

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

DEVELOPMENT: The Enterprise Business Standards Office will reissue ADC 12, Revised 

Procedures for Logistics Reassignment (Reference 3.p.) as ADC 1141, to update this approved change 

to incorporate DLMS transactions and procedures, and to establish an implementation date. ADC 12 

was written against legacy MILS transactions and procedures only. ADC 12 revisions provide for 

more accurate accountability during logistics reassignment and support audit readiness. ADC 1141 is 

under development and target date for reissue of ADC 12 as ADC 1141 is calendar year 2017. The 

DLMS Program Office will release ADC 1141 to the Supply PRC and request Component 

implementation dates as this implementation requires DLMS capability. The Air Force GFP-A CICP 

process will need to transition to the revised logistics reassignment procedures in the future and the 

implementation date is unknown at this time.

8. ADDITIONAL COMMENTS TO CONSIDER:

a. As part of the PDC staffing, the Enterprise Business Standards Office asked ODASD(SCI) 

if DODM 4140.68 and DOD 4140.26-M logistics reassignment policy applied to Air Force CICPs. 

ODASD(SCI) advised that if the Air Force has identified a CICP in FLIS as a wholesale ICP, then 

DODM 4140.68 and DOD 4140.26-M apply.

b. Air Force GFP-A relies on DLMS transactions from the Air Force CICPs to accurately 

record asset quantities and valuation. Without the date and time of transaction, the Air Force will 

need to manually research the Air Force GFP-A APSR to identify matching transactions from the 

Air Force CICP.
Attachment, ADC 1232

Page 9

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Target implementation 

date is June 2017.

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Air Force is unable to estimate at this time and 

does not have adequate data to calculate cost of manual workaround. 

11. IMPACT:

a. New DLMS Data Elements: There are no new DLMS data elements.

b. Changes to DLMS Data Elements: There are no revised DLMS data elements.

c. Automated Information Systems (AIS):

(1) Identified changes are applicable to Air Force, Air Force CICP, and DPAS.

There is no impact on the Losing Inventory Manager/Gaining Inventory Manager systems other 

than the Air Force and the CICP inventory management system.

(2) While the CICP may exchange logistics reassignment transactions with DLA, 

the additional data content described in this change is only required for, 846D and 846S 

transactions exchanged between Air Force and DPAS.

(3) Other Component systems may implement the authorized DLMS enhancements 

for transaction set date and time without further coordination by a DLMS change.

d. Defense Automatic Addressing System (DAAS): Requires mapping updates as shown 

in Enclosure 1, to include:

(1) An additional N1 loop for the Party to Receive Reports/PK, to allow DAAS to 

create and send an image to DPAS. When the CICP is generating the transaction to an external 

source, the CICP will already be identified (as either the LIM or the GIM); the CICP will include 

an additional 2/N1/450 loop for the N106 Party to Receive Copy/PK, but the CICP will not include 

Action Code FI. DAAS will insert the 1/BIA06/020 Action Code FI in the image DAAS creates to 

send to the APSR (DPAS). DAAS routes the image transaction to the APSR using a RIC, not a 

DoDAAC.

(2) When the CICP, as the LIM or GIM, receives a 846D/846S transaction from an 

external system, the CICP sends an image (by including 1/BIA06/020 Code FI) to DAAS to send to 

the APSR (DPAS). The CICP image transaction will also identify the DPAS APSR as the 

2/N101/450 Party to Receive Reports (ZD) with 2/N106/PK Party to Receive Copy. DAAS routes

the image transaction to the APSR using a RIC, not a DoDAAC.

(3) DAAS/Logistics Metrics Analysis Reporting System (LMARS) does not include

Logistics Reassignment transactions, and so is not impacted by this change. There is no requirement 

to display 846D (legacy DEE/DEF, DLA) or 846S (legacy DZC/DZD) logistics reassignment 

transactions in the Web Visual Logistics Information Processing System (WebVLIPS), and this 

ADC does not change that. 
Attachment, ADC 1232

Page 10

(4) The 846D/846S image transaction, based on beginning segment BR06 Action 

Code FI, should appear in Logistics Data Gateway (LDG) (but should not populate WebVLIPS). 

Inclusion in LDG will provide a record of what was sent to the Air Force APSR should there ever 

be a need for research. Note: Currently DAAS will only show MILS transactions in LDG (along 

with extended data/user defined file (UDF) data). DAAS advised that legacy logistics reassignment 

transactions MILSTRAP Document Identifier Codes DICs DEE/DEF, DLA/DLB, and DZC/DZD 

(DLMS 846D and 846S) currently populate LDG. There is no change to that existing requirement 

for the original transactions.

e. Non-DLM 4000.25 Series Publications:

(1) The Air Force must take action as needed to update DPAS and Air Force 

procedures documenting the applicable requirements contained herein, to include updating 

AFI 23-101, Air Force Materiel Management (Reference 3.q.).

(2) OUSD(AT&L)/ARA, Property & Equipment Policy, is in the process of 

coordinating a revision to DODI 5000.64, Accountability and Management of DOD Equipment and 

Other Accountable Property, to address use of the DLMS for equipment, among other updates. The 

approved wording will recognize use of the DLMS for electronic interfaces between DOD supply 

systems and the APSR to facilitate accountable property management. By virtue of the contractual 

requirements levied by the Air Force on the CICP, the procedures discussed in this change for 

managing Government-owned equipment fall within the scope of the pending update to DODI 

5000.64 establishing authoritative guidance for use of the DLMS.

12. PDC 1232 RESPONSES:

Originator Response/Comment Disposition

1. Air Force Concurs with PDC as written. Noted.

2. Army Concurs without comments. Noted.

3. Marine 

Corps

Concur without comment. Noted.

4. Navy Concur without comment. Noted.

5. DLA Concur without comment. Noted

6. DAAS This would require DMARS to check the 

transactions (DEE/DEF, DLA, DZC,DZD)

in Beginning Segment in ext. data first for 

BIA06=FI. If found then go look for N1*ZD 

to identify DoDAAC for routing. There 

would be no "normal" routing , just the 

image.

Check for BIA06 FI (image). When the 

CICP sends 846SD/846S image, by 

including 1/BIA06/020 Code FI, the 

CICP image transaction will identify the 

AF program manager in the APSR as the 

2/N101/450 Party to Receive Reports 

(ZD) with 2/N106/PK Party to Receive 

Copy. However, the intent is to route 

the transaction to a RIC not 

DoDAAC. The N101/ZD DLMS Note 

specifies: Must identify the program 

manager by RIC. The CICP may 
Attachment, ADC 1232

Page 11

Originator Response/Comment Disposition

include a second iteration of N101/ZD 

to identify the program manager 

DoDAAC when the program manager 

does not have an assigned RIC, and a 

generic AF GFP APSR RIC was used for 

routing to program manager on the 

APSR (DPAS).

The 2nd iteration of N1*ZD to identify 

DoDAAC, does not include N106 PK as 

it is for DPAS information, not DAAS 

routing.

Corrected DLMS note in 846S at 

2/N101/450 to highlight use if RIC as 

noted in change table.

7. DAAS Comment 2: The second scenario would be 

if you do not find BIA06=FI then you must 

route as normal but also look for the 

presence of N1*ZD to identify DoDAAC for 

image routing. Also in that image 

transaction insert BIA06=FI

The second scenario would be if you do 

not find BIA06=FI then you must route 

as normal but also look for the presence 

of N1*ZD to identify RIC, with 

2/N106/PK Party to Receive Copy, for 

image routing. Also in that image 

transaction insert BIA06=FI

8. DAAS Comment 3: Para 11.d(4) states DAAS will 

populate LDG with the image transactions 

sent to DPAS although requirement does not 

seem to include the original.

It is not clear what is meant by 

“requirement does not seem to include 

original”. Only images of 846D and 

846S are sent to DPAS, either an image 

from the AF CICP through DAAS to 

DPAS, or DAAS creates image to send 

DPAS. Per DAAS (Ms. Bernace Collier 

email, March 10, 2017/4:28pm), DAAS 

advised that legacy logistics 

reassignment transactions MILSTRAP 

DICs DEE/DEF, DLA/DLB, and 

DZC/DZD (DLMS 846D and 846S)

currently populate LDG. There is no 

change to that existing requirement for 

original transactions.

DLMS office added italicized statement 

above to ADC at paragraph 11.d.(4).

Enclosures
Enclosure 1, ADC 1232

Page 1

ENCLOSURE 1 TO ADC 1232

A. 846D, Logistics Reassignment Transfer and Decapitalization

# Location Revisions to DLMS 846D Logistics Reassignment 

Transfer and Decapitalization

Reason

1. IC cover page 

DLMS 

Introductory 

Notes

Add ADC 1232 to DLMS Introductory Note 6: 

- ADC 1232, Revision to DLMS 846D and 846S 

Logistics Reassignment Transactions to Support 

Government Furnished Property (GFP) 

Accountability during Logistics Reassignment 

between Air Force Contractor Inventory Control 

Points (CICP) and Air Force or DLA ICPs.

Identifies DLMS Changes 

included in the DS

2. IC cover page 

DLMS 

Introductory 

Notes

Add new introductory note 5e:

e. Data associated with a DLMS enhancement 

authorized for implementation by modernized 

systems under DLMS migration. This data 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.

Adds the introductory note for

authorized DLMS 

enhancements.

3. 1/BIA04/020 Change Federal note to a DLMS note and revise 

note 2:

DLMS Note:

Federal Note: 1. This date is the date of

transaction set preparation and corresponds to the 

Universal Time Coordinate (UTC).

2. Authorized DLMS enhancement; see 

introductory DLMS note 5ea.

Allows for use of the 

transaction set preparation date

as an authorized DLMS 

enhancement, as needed, 

without further coordination at 

the DOD level.

4. 1/BIA05/020 Change Federal notes to DLMS notes, and revise 

DLMS Note 3:

Federal Note: DLMS Note:

1. Express the originating activity's time of 

transaction set preparation in UTC.

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

format.

3. Authorized DLMS enhancement; see 

introductory DLMS note 5.ea.

Allows for use of the 

transaction set preparation 

time as an authorized DLMS 

enhancement, as needed, 

without further coordination at 

the DOD level.
Enclosure 1, ADC 1232

Page 2

# Location Revisions to DLMS 846D Logistics Reassignment 

Transfer and Decapitalization

Reason

5. 1/BIA06/020 Open BIA06 Action Code and add qualifier FI:

FI File 

DLMS Note: 

1. Authorized for Air Force contractor inventory 

control point (CICP) use to provide an image of 

the LR transfer/decapitalization transaction to the 

Air Force accountable property system record 

(APSR), only when the CICP is providing the 

APSR an image of a transaction that the CICP 

received from an external system. There will be no 

2/N106/450 code TO for this transaction image. 

Refer to ADC 1232.

2. Authorized for DAAS use when DAAS creates 

an image for the Air Force APSR, of a transaction 

that the Air Force CICP sent to a GIM or LIM. 

DAAS creates the image when CICP sends an 

846D transaction to an external system other than 

the APSR and includes 2/N101/450/ZD and 

2/N106/450/PK. There will be no 2/N106/450 code 

TO for this transaction image. Refer to ADC 1232.

Provides image capability for 

logistics reassignment 

transactions which Air Force 

requires for GFP-A.

The CICP only cites the 

Action Code FI when the 

CICP received the transaction 

from an external source 

(comparable to the ADC 1238 

MRA image), and is providing 

an image of that transaction to 

the APSR.

DAAS creates image using FI 

as noted. 

6. 2/DTM01/100 Add new code 097 with DLMS notes:

097 Transaction Creation

DLMS Notes:

1. Use to identify the transaction preparation date. 

Correspond date to the Universal Time Coordinate 

(UTC).

2. Authorized DLMS enhancement; see 

introductory DLMS note 5e on IC cover page.

Establishes a new DLMS 

enhancement for functional 

transaction preparation date, 

for use as needed without 

further coordination at the 

DOD level. 

7. 2/DTM03/100 Open DTM03 for use and add the DLMS notes: 

Time 

DLMS Note: 1. Use with Code 097 (Transaction 

Creation) to provide the time associated with the 

transaction preparation date. 

2. Express time in UTC using a four-position 

(HHMM) format. 

3. Authorized DLMS enhancement; see 

introductory DLMS note 5e on IC cover page.

Establishes a new DLMS 

enhancement for functional 

transaction preparation time, 

for use as needed without 

further coordination at the 

DOD level. 
Enclosure 1, ADC 1232

Page 3

# Location Revisions to DLMS 846D Logistics Reassignment 

Transfer and Decapitalization

Reason

8. 2/REF/140 Revise segment level DLMS note:

DLMS Note:

Use up to 2 repetitions. Must use the first at least

one repetition to identify the controlling transaction

document number for this transaction. Use 

additional repetitions as needed. such as Use a 

second repetition only when processing an LR 

transfer/decapitalization transaction for a 

nonprocurement source receipt processed after the 

ETD, to identify the transaction number of the 

receipt thereby establishing an audit trail between 

the receipt of the item and its subsequent 

transfer/decapitalization. 

Administrative update.

Moved details of the DLMS 

Note for the receipt document 

number to REF01 code 43 

where it applies.

9. 2/REF01/140 Add new Code 6L and associated DLMS Notes:

6L Agent Contract Number

DLMS Note:

1. The Air Force uses for Air Force GFP 

accountability transactions to identify the 

Procurement Instrument Identifier (PIID) 

applicable to the contract authorizing the Air 

Force CICP to have custody of GFP. Use the 

legacy procurement instrument identification 

number (PIIN) pending transition to the PIID.

2. If GFP is authorized under a PIID call/order 

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

call/order number in this field.

3. Required for Air Force GFP accountability. 

4. Authorized DLMS enhancement. Refer to ADC 

1232.

DO Delivery Order Number

DLMS Note: 

1. Use in conjunction with the PIIN (Code 6L) for 

GFP-related transactions to identify the legacy 

four position call/order number associated with the 

PIIN applicable to the contract authorizing the 

contractor to have custody of GFP.

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

PIID call/order number is mapped to Code 6L.

3. Authorized DLMS enhancement. Refer to ADC 

1232.

Supports GFP accountability 

requirement for identification 

of the authorizing PIID.

10. 2/REF01/140 Revise DLMS notes for existing qualifiers 43 and 

TN:

43 Supporting Document Number

DLMS Note:

1. Must use to identify the transaction number

(document number) from the associated receipt 

Administrative update for 

consistency with DLMS 

terminology for document 

number.
Enclosure 1, ADC 1232

Page 4

# Location Revisions to DLMS 846D Logistics Reassignment 

Transfer and Decapitalization

Reason

transaction when processing an LR 

transfer/decapitalization transaction for a 

nonprocurement source receipt processed after the 

ETD. Identifying the document number of the 

receipt establishes an audit trail between the 

receipt of the item and its subsequent 

transfer/decapitalization.

2. DLMS enhancement; see introductory DLMS note 

5a.

TN Transaction Reference Number

DLMS Note:

Use to identify the controlling transaction number 

(document number) for this transaction.

11. 2/N101/450 Add new qualifier ZD with DLMS Note:

ZD Party to Receive Reports 

DLMS Note: 

Authorized for use for Air Force GFP accountability 

to identify the Air Force program manager in the 

accountable property system of record (APSR) when 

the contractor inventory control point (CICP) must 

report an image of this transaction to a separately 

maintained property system. Must identify the 

program manager by RIC (2/N103 qualifier M4). If 

the program manager DoDAAC does not have an 

assigned RIC, use the generic Air Force GFP APSR 

RIC with 2/N106=PK and use a second iteration of 

the N1 loop (repeating Code ZD without 2/N106=PK) 

to provide the program manager DoDAAC. Use in 

conjunction with N106 Code PK to provide an image 

of the transaction (image is identified by 

1/BIA06/020 Action Code FI) to update the APSR 

associated with the CICP identified in 1/N101/080). 

Refer to ADC 1232. 

Provides capability to identify 

organization requiring an 

image of the 846D transaction.

The DLMS note highlights the 

use of the RIC for Air Force 

program manager in DPAS.

12. 2/N106/450 Add new qualifier PK with DLMS Note:

PK Party to Receive Copy 

DLMS Note:

Authorized for Air Force GFP accountability, use 

with N101Code ZD to provide an image of an LR 

Transfer/Decapitalization transaction to the APSR. 

Do not use N106 Code TO with the Air Force 

CICP transaction image sent to the APSR.

Specifies new code identifying 

the transmission of a 

transaction image.
Enclosure 1, ADC 1232

Page 5

B. 846S, Logistics Reassignment Storage Information

# Location Revisions to DLMS 846S Logistics 

Reassignment Storage Information 

Reason

1. IC cover page 

DLMS 

Introductory 

Notes

Add ADC 1232 to DLMS Introductory Note 6: 

- ADC 1232, Revision to DLMS 846D and 

846S Logistics Reassignment Transactions 

to Support Government Furnished 

Property (GFP) Accountability during 

Logistics Reassignment between Air Force 

Contractor Inventory Control Points 

(CICP) and Air Force or DLA ICPs.

Identifies DLMS Changes 

included in the DS

2. IC cover page 

DLMS 

Introductory 

Notes

Add new introductory note 5f:

f. Data associated with a DLMS 

enhancement authorized for implementation 

by modernized systems under DLMS 

migration. This data 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.

Adds the introductory note for 

authorized DLMS 

enhancements.

3. 1/BIA04/020 Change Federal note to a DLMS note and 

revise DLMS Note 2:

DLMS Note:

Federal Note: 1. This date is the date of

transaction set preparation and

corresponds to the Universal Time Coordinate 

(UTC).

2. Authorized DLMS enhancement; see 

introductory DLMS note 5fa.

Authorizes use of DLMS 

enhancement for transaction 

set preparation date, as needed,

without further coordination 

at the DOD level.

4. 1/BIA05/020 Change Federal notes to DLMS notes, 

renumber existing DLMS notes, revise DLMS 

Note 3:

Federal Note: DLMS Note:

1. Express the originating activity's time of 

transaction set preparation in UTC.

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

format.

3. Authorized DLMS enhancement; see 

introductory DLMS note 5fa..

Authorizes use of DLMS 

enhancement transaction set 

preparation time, as needed,

without further coordination 

at the DOD level.
Enclosure 1, ADC 1232

Page 6

# Location Revisions to DLMS 846S Logistics 

Reassignment Storage Information 

Reason

5. 1/BIA06/020 Open BIA06 Action Code and add qualifier FI:

FI File 

DLMS Note: 

1. Authorized for Air Force contractor 

inventory control point (CICP) use to provide 

an image of the LR transfer/decapitalization 

transaction to the Air Force accountable 

property system record (APSR), only when 

CICP is providing the APSR an image of a 

transaction which the CICP received from an 

external system. There will be no 2/N106/450 

code TO for this transaction image. Refer to 

ADC 1232.

2. Authorized for DAAS use when DAAS 

creates an image for the Air Force APSR, of a 

transaction which the Air Force CICP sent to a 

GIM or LIM. DAAS creates the image when 

CICP sends an 846D transaction to an external 

system other than the APSR and include 

2/N101/450/ZD and 2/N106/450/PK. There will 

be no 2/N106/450 code TO for this transaction 

image. Refer to ADC 1232.

Provides image capability for 

logistics reassignment 

transactions which Air Force 

requires for GFP-A.

The CICP only cites the Action 

Code FI when the CICP 

received the transaction from 

an external source (comparable 

to the ADC 1238 MRA and 

TRA image), and is providing 

an image of that transaction to 

the APSR. 

DAAS creates image using FI 

as noted. 

6. 2/DTM01/100 Add new code 097 with DLMS notes:

097 Transaction Creation

DLMS Notes:

1. Use to identify the transaction preparation 

date. Correspond date to the Universal Time 

Coordinate (UTC).

2. Authorized DLMS enhancement; see 

introductory DLMS note 5f on IC cover page.

Establishes a new DLMS 

enhancement for functional 

transaction preparation date, for 

use as needed without further 

coordination at the DOD level. 

7. 2/DTM03/100 Open DTM03 for use and add the DLMS notes: 

Time 

DLMS Note: 1. Use with Code 097 

(Transaction Creation) to provide the time 

associated with the transaction preparation 

date. 

2. Express time in UTC using a four-position 

(HHMM) format. 

3. Authorized DLMS enhancement; see 

introductory DLMS note 5f on IC cover page.

Establishes a new DLMS 

enhancement for functional 

transaction preparation time, 

for use as needed without 

further coordination at the 

DOD level. 
Enclosure 1, ADC 1232

Page 7

# Location Revisions to DLMS 846S Logistics 

Reassignment Storage Information 

Reason

8. 2/REF/140 Change Federal level segment note to DLMS 

note and revise:

Federal DLMS Note:

Must use at least one repetition to identify the 

transaction document number. Use additional 

repetitions as needed.

Administrative update for 

consistency with DLMS 

terminology for document 

number and to note use of 

repetitions. 

9. 2/REF01/140 Add new Code 6L and associated DLMS 

Notes:

6L Agent Contract Number

DLMS Note:

1. Air Force uses for Air Force GFP 

accountability transactions to identify the 

procurement instrument identifier (PIID) 

applicable to the contract authorizing Air Force 

CICP to have custody of GFP. Use the legacy 

procurement instrument identification number 

(PIIN) pending transition to the PIID.

2. If GFP is authorized under a PIID call/order 

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

call/order number in this field.

3. Required for Air Force GFP accountability. 

4. Authorized DLMS enhancement. Refer to 

ADC 1232.

DO Delivery Order Number

DLMS Note: 

1. Use in conjunction with the PIIN (Code 6L) 

for GFP-related transactions to identify the 

legacy four position call/order number 

associated with the PIIN applicable to the 

contract authorizing the contractor to have 

custody of GFP.

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

The PIID call/order number is mapped to Code 

6L.

3. Authorized DLMS enhancement. Refer to 

ADC 1232

Supports GFP accountability 

requirement for identification 

of the authorizing PIID.

10. 2/REF01/140 Revise DLMS Note for existing qualifier TN:

TN Transaction Reference Number

DLMS Note:

Use to identify the document number.

Administrative update for 

consistency with DLMS 

terminology for document 

number.

11. 2/N101/450 Add new qualifier ZD with DLMS Note:

ZD Party to Receive Reports 

DLMS Note: 

Authorized for use for Air Force GFP 

accountability to identify the DoDAAC 

Provides capability to identify 

organization requiring an image of

the 846D transaction.

Correcting DLMS note to

document the use of the RIC to 
Enclosure 1, ADC 1232

Page 8

# Location Revisions to DLMS 846S Logistics 

Reassignment Storage Information 

Reason

representing the Air Force program manager in 

the accountable property system of record (APSR) 

when an image of this transaction must be 

reported when the contractor inventory control 

point (CICP) must report an image of this 

transaction to a separately maintained property 

system. Must identify the program manager by RIC 

(2/N103 qualifier M4). If the program manager 

DoDAAC does not have an assigned RIC, use the 

generic Air Force GFP APSR RIC with 2/N106=PK 

and use a second iteration of the N1 loop (repeating 

Code ZD without 2/N106=PK) to provide the 

program manager DoDAAC. Use in conjunction 

with N106 Code PK to provide an image of the 

transaction (image is identified by 1/BIA06/020 

Action Code FI) to update the APSR associated 

with the CICP DoDAAC (identified in

1/N101/080). Refer to ADC 1232. 

identify the Air Force program 

manager in DPAS, and for 

consistency with 846D DLMS 

note at 2/N101/450.

12. 2/N106/450 Add new qualifier PK with DLMS Note:

PK Party to Receive Copy 

DLMS Note:

Authorized for Air Force GFP accountability use 

with N101Code ZD to provide an image of an LR 

Storage Information Order/Reply transaction to 

the APSR. Do not use N106 Code TO with Air 

Force CICP transaction image sent to the APSR.

Specifies new code 

identifying the transmission of 

a transaction image.
Enclosure 2, ADC 1232

Page 1

Enclosure 2 GFP-A Logistics Reassignment Transaction Flow Diagram PDC 1232 

– Revise DLMS 846

D/846S 

(Logistics Reassignment)

CICP IMS Transaction Services APSR GIM

Route GFP asset reassignment information

Update GFP asset management position

Logistics reassignment 

direction

Asset financial information

Activity Information Flow

Performer

Transfer asset management

DLMS 846D

Add: AF CICP GFP 

Procurement Instrument 

Identifier

Authorize: Date/Time

DLMS 846S

Add: AF CICP GFP 

Procurement Instrument 

Identifier

Authorize: Date/Time

DLMS 846D 

Add: AF CICP GFP 

Procurement Instrument 

Identifier

Add: Action Code

Authorize: Date/Time

DLMS 846S

Add: AF CICP GFP 

Procurement Instrument 

Identifier

Add: Action Code

Authorize: Date/Time

Update asset management position

DLMS 846D 

Add: AF CICP GFP 

Procurement Instrument 

Identifier

Authorize: Date/Time

DLMS 846S

Add: AF CICP GFP 

Procurement Instrument 

Identifier

Authorize: Date/Time

Asset to be 

logistically reassigned

Reconciliation results 

recorded

Start Event End Event
Enclosure 2, ADC 1232

Page 2

Enclosure 2 GFP-A Logistics Reassignment Transaction Flow Narrative

Activity Description

1 Transfer asset management Prior to the effective transfer date, the Losing Inventory Manager (LIM) ships the assets to the 

appropriate storage activity for the Gaining Inventory Manager. On the effective transfer 

date, the LIM processes the DLMS 846D and 846S including date and time of transaction and 

PIID to accompany the logistics reassignment. If the Air Force CICP is the LIM, the CICP will 

send the 846D and 846S to the GIM and DPAS via DAAS. If the Air Force is the GIM, the LIM 

sends the 846D and 846S to the Air Force CICP. The Air Force CICP sends an image of the 846D 

and 846S to DAAS to be routed to the Air Force Government Furnished Property (GFP) 

Accountable Property System of Record (APSR). 

2 Route GFP asset logistics 

reassignment information

DAAS receives the DLMS 846D and DLMS 846S including date and time of transaction and PIID 

and routes them to the Air Force GFP APSR. DAAS splits the transaction so the action copy 

goes to the GIM and the image copy including the action code goes to APSR.

3 Update asset management 

position

The GIM receives the logistics reassignment information DLMS 846D and DLMS 846S including 

date and time of transaction and PIID from DAAS, records transaction and updates the 

balance.

4 Update GFP asset 

management position

AF GFP APSR receives the logistics reassignment information DLMS 846D and DLMS 846S 

including date and time of transaction from DAAS, record transaction and update the 

Government furnished property (GFP) balance. Air Force GFP APSR provides Air Force financial 

statements updated inventory balances and valuation.