1 of 3 

ADC 301 

Attachment 

ATTACHMENT TO ADC 301 

Recognize Use of Ownership Code in Migrated Navy Serial Number and Lot Number 

Transactions (NAVSUP P-724 BG1/BG2) Associated with DLMS 527R, 846R, 867I, and 947I 

(Supply) (Staffed as PDC 322) 

1. ORIGINATOR: 

 a. Service/Agency: Army in conjunction with Navy

 

 b. Originator: 

(1) Army: Logistics Modernization Program (LMP), commercial phone: (856) 988-4878. 

(2) Navy: Navy Supply Process Review Committee representative, NAVSUP 421, 

DSN 430-7510; commercial (717) 605–7510; the Navy Supply Information Systems Activity

(NAVSISA); and, the Naval Operational Logistics Support Center (NOLSC). 

2. FUNCTIONAL AREA: Supply 

3. REFERENCES: 

 a. NAVSUP P-724, Rev 12, Conventional Ordnance Stockpile Management, Volume I Ashore 

 b. Approved DLMS Change (ADC) 261, Migrate Navy Serial Number and Lot Number 

Transactions (NAVSUP P-724 BG1/BG2) to DLMS 527R Receipt, 867I Issue, and 947I Inventory 

Adjustment 

 c. Approved DLMS Change (ADC) 283, Migrate Serial Number and Lot Number Transactions 

(NAVSUP P-724 BG1/BG2) to DLMS 846R Location Reconciliation Request 

4. REQUESTED CHANGE: 

 a. Title: Recognize Use of Ownership Code in Migrated Navy Serial Number and Lot Number 

Transactions (NAVSUP P-724 BG1/BG2) Associated with DLMS 527R, 846R, 867I, and 947I 

 b. Description of Change: ADC 261 and 283 (references 3.b and 3.c) did not reflect 

that the NAVSUP P-724 BG1/BG2 transaction formats could have an ownership code. The 

BG1/BG2 transaction format showed purpose code only. This change recognizes and 

documents for mapping purposes, that the field in DI Code BG1/BG2 identified as ‘purpose 

code’ is used for either ownership code or purpose code. This dual use of a single field for 

ownership/purpose code is consistent with dual use of the field in the Defense Logistics 

Standard System (DLSS) (aka MILS) transactions. Accordingly, the BG1/BG2 field 

previously identified for ‘purpose’ code shall map to both the ownership code and purpose 

code for the mixed DLSS/DLMS environment. DAASC maps shall be updated to reflect 

LQ01 = A1 (Ownership Code) for 527R, 846R, 867I and 947I, and LQ01 = RD (Property 

Ownership Type Code) in the DAASC map for 947I, as shown below (this is in addition to 
2 of 3 

ADC 301 

Attachment 

purpose code which is already reflected in the DAASC map): 

BG1/BG2 Record 

Position 527R Mapping 527R Position/Loop 

Header Transaction 

(D6_) Positions 

Ownership 

Code 

22 Perpetuate from 

LQ01 = A1 

130/LM 70 

BG1/BG2 Record 

Position 846R Mapping 846R Position/Loop 

Header Transaction 

(DZH) Positions 

Ownership 

Code 

22 Perpetuate from 

LQ01 = A1 

376/LM 70 

BG1/BG2 Record 

Position 867I Mapping 867I Position/Loop 

Header Transaction 

(D7_) Positions 

Ownership 

Code 

22 Perpetuate from 

LQ01 = A1 

270/LM 70 

Field Name Record 

Position 947I Mapping 947I Position/Loop 

Header Transaction 

(D8_/D9_) Positions 

Header Transaction 

(DAC/DAD) Positions

Previous 

Ownership 

Code 

21 Perpetuate from 

LQ01 = RD 

1000/0310 N/A 70 

Previous 

Purpose Code 

21 Perpetuate from 

LQ01 = RE 

1000/0310 N/A 70 

Ownership 

Code 

22 Perpetuate from 

LQ01 = A1 

1000/0310 70 65 

Purpose Code 22 Perpetuate from 

LQ01 = 99 

1000/0310 70 65 

 c. DAASC Mapping: Revise DAASC maps to accommodate Ownership Code, in 

addition to purpose code, for mapping between DLMS 527R/846R/867I/947I and DI Code 

BG1/BG2. 

 d. Alternatives: None known. 

5. REASON FOR CHANGE: Supports the BG1/BG2 use of an ownership/purpose code 

field vice purpose code only, and updates DAASC mapping for 527R, 846R, 867I and 947I 

to BG1/BG2 in a mixed DLSS/DLMS environment to reflect this. In order to accurately 

transmit Lot Number and Serial Number information, the correct Ownership code needs to be 

perpetuated to the Navy BG1/BG2 transactions, where applicable. This change recognizes 

and document that the Navy BG1/BG2 formats entry for purpose code can also be an 

ownership code, so that DASC maps can be updated as needed. 

6. ADVANTAGES AND DISADVANTAGES: 

 

 a. Advantages: Incorporating the BG1/BG2 data in DLMS, and providing DAASC 

mapping guidance for use in converting to DLSS receipt, issue, location reconciliation 

request, or inventory adjustment transactions, with supporting Navy BG1/BG2 serial/lot 

number reporting transactions, is in keeping with the intent of utilizing the DLMS format and 
3 of 3 

ADC 301 

Attachment 

DAASC’s mission of translating and routing various supply actions to and from trading 

partners. This change supports that effort by updating DAASC maps to support the true 

BG1/BG2 requirement for a dual BG1/BG2 ownership/purpose code field. 

 b. Disadvantages: None known.

7. IMPACT: Modify DAASC conversion maps for DLMS Supplements 527R, 846R, 867I 

and 947I as noted to add ownership code associated with NAVSUP P-724 DI Code 

BG1/BG2 fields previously identified as purpose code only. The DI Code BG1/BG2 field 

previously identified as ‘purpose code’ can be either ownership code (numeric), or purpose 

code (alpha), consistent with dual use of the ownership/purpose code field in DLSS.