1 of 12 

ADC 261 

Attachment 

ATTACHMENT TO 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 (Staffed by PDC 261) 

1. ORIGINATOR: 

a. Service/Agency: Army and Navy 

 b. Originator: 

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

(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. NAVSUP P-485, Naval Supply Procedures 

 c. Teleconference, December 4, 2007, among Army, Navy, DAASC and DLMSO, subject: PDC 

261. Results of the teleconference discussion are highlighted in gray on page 3 of this attachment. 

4. REQUESTED CHANGE: 

 a. Title: Migrate Serial Number and Lot Number Transactions (NAVSUP P-724 BG1/BG2) to 

DLMS 527R Receipt, 867I Issue, and 947I Inventory Adjustment 

 b. Description of Change: 

(1) Serial Number and Lot Number Reports (Navy Document Identifier (DI) Codes BG1 

and BG2) are presently submitted in a Defense Logistics Standard System (DLSS) environment, as 

supplemental information for MILSTRAP receipt (Document Identifier (DI) Code D6_), issue 

(DI Code D7_), and inventory adjustment (DI Code D8_/D9_/DAC) transactions. These DLSS 

transactions correspond to DLMS 527R (receipt), 867I (issue), and 947I (inventory adjustment). 

The DLMS transactions contain data elements for serial number and lot number. 

Navy currently has a second version of DI Code BG1/BG2 format documented in NAVSUP 

P-485. However Navy has indicated they plan to remove the formats from NAVSUP P-485, and 

defer to NAVSUP P-724. Accordingly, this change addresses only the NAVSUP P-724 formats. 

(2) Army has identified a requirement for using the NAVSUP P-724 BG1/BG2 data 

in DLMS under the Army Logistics Modernization Program (LMP) to support an existing 

interface between Army and the Naval Operational Logistics Support Center (NOLSC) 

Ordnance Information Systems (OIS). Army developed this change in conjunction with 

Navy NAVSISA and NOLSC. Army will not be the recipient of BG1/BG2 transactions, and 
2 of 12 

ADC 261 

Attachment 

has no other requirement for their use other than sending the BG1/BG2 information to Navy 

for the stated Navy interface. 

(3) This change updates DS 527R, 867I, and 947I to add data elements unique to 

NAVSUP P-724 BG1/BG2 transactions to the standard DLMS transactions. Army LMP will 

include the data as required for the Navy NOLSC interface. Until such time as Navy 

transitions to DLMS, there is a requirement for DAASC to convert the DLMS transactions 

created by LMP into the corresponding MILSTRAP and BG1 or BG2 transaction formats 

when required for NOLSC. This will require DAASC to extract multiple transactions 

when translating from DLMS to MILS format. For example, when converting a DLMS 527R 

receipt which has BG1 or BG2 data for a non-DLMS NOLSC trading partner, the single 527R 

receipt would translate into a D6_ receipt with multiple BG1 or BG2 transactions for serial/lot 

number information for the items received by the D6_. Navy has confirmed that either BG1 or 

BG2 transactions are used for a given corresponding MILS transaction (D6_, D7_, D8_/D9_), 

but not both. The BG1/BG2 transactions are not sent TO Army, so the DAASC conversion will 

be one-way for this interface, from the DLMS to MILSTRAP transaction and BG1 or BG2 

transactions. 

(4) A summary of the data elements that are unique to the BG1/BG2 transactions are 

below: 

(a) Action Code – Identifies the action taken on the reported item. Identical to 

the last 2 digits of header document identifier (DI) code. DLMSO NOTE: No DLMS 

change required. The last 2 positions of the MILSTRAP DI Code equate to particular 

DLMS data for each transaction as shown in the mapping table at Enclosure 1. This 

information can also be derived from positions 2 and 3 of the DI Code (LQ02 when LQ01 = 

0) when DI Code is provided during a mixed DLSS/DLMS environment. 

(b) Navy Management Code – Designated the type of posting. Values are “P” 

(Maintenance Due Date Posting) or “E” (Expiration Date Posting). DLMSO NOTE: No 

DLMS change required. This information can be derived from the date qualifier. Unlike 

the BG1/BG2 transactions, DLMS transactions will provide distinct qualifiers for 

‘maintenance due-date’ and ‘expiration date’. An additional ‘management’ code, which 

means ‘posting of maintenance due date’ or, ‘posting of expiration date,’ would be redundant 

and is not required under DLMS. 

DLMSO NOTE: Navy publication refers to these as management codes; however, these are 

not DLMS/MILS management codes (see MILSTRAP AP 2.6 Management Codes or DLMS 

data dictionary), accordingly LQ qualifier 84 does not apply. 

For DLMS Data Dictionary see: http://www.dla.mil/j-6/dlmso/eApplications/LogDataAdmin/dlmsdicdir.asp. For MILSTRAP Management Codes see http://www.dla.mil/j6/dlmso/elibrary/Manuals/MILSTRAP/default.asp. 

(c) Maintenance Due Date – Identifies the Maintenance Due Date of the 

reported item. This represents the date that maintenance is due on the item. Corresponds to 

Navy “Management” Code of ‘P’. This change adds the date to the DLMS 527R, 867I, and 

947I unique item tracking (UIT) loops. 

(d) Expiration Date – Identifies the expiration date of the reported item. 

Corresponds to Navy “Management” Code of ‘E’. This change adds the date to the DLMS 

527R, 867I, and 947I UIT loops. 
3 of 12 

ADC 261 

Attachment 

(e) Lot Number Size Quantity – Identifies the quantity of the item by Lot 

Number. This is the individual quantity associated with that lot number, not the total 

quantity of the associated transaction. The total number of BG1 quantities would be the total 

quantity on the entire transaction, since the BG1 quantity is implied as "1". Similarly, the 

total of the quantities on the BG2 transactions would be the total quantity on the entire 

transaction.

Under the 80 record position BG1 transaction, NAVSUP P-724 states that blank or “1” is 

acceptable, while the actual Lot Size Quantity is used in the BG2 transactions. This is the 

quantity for the lot. There can be multiple lots associated with a single DLMS transaction. 

The sum of the lot quantities should be the total quantity of the transaction. Under DLMS, 

Lot Size Quantity is added for use with lot number only. DAASC mapping will populate 

the BG1 with ‘1’ in the Lot Size Quantity field when converting from DLMS to BG1. 

This is consistent with current BG1 use of this field. This solution was addressed during 

the reference 3.c December 4, 2007, teleconference among Army, Navy, DAASC, and 

DLMSO.

(5) The following BG1/BG2 data requirements are accommodated by existing 

DLMS, but require specific DAASC mapping guidance for conversion from DLMS to 

BG1/BG2: 

Lot and Serial Number – Serial (BG1), Lot (BG2), or Lot and Serial Number (BG1) of the 

reported item. Existing DLMS 527R, 867I, and 947I accommodate reporting of serial number 

and/or lot number. However when both a Lot and Serial number are reported in DI Code BG1, a 

period separates the Lot and Serial Numbers as they appear in a single field (rp 45-65). The lot 

number appears first followed by the serial number. Army noted that in today’s environment, 

using BG1, Army does not, and never has, provided a lot number in the BG1 transaction, however 

Army LMP will put both batch and lot number, when applicable, into the DLMS transaction at the 

appropriate qualifiers. DAASC will develop mapping logic that when both the batch and lot 

number appear in 527R, 867I, or 947I going from LMP to NOLSC OIS, DAASC shall 

provide both the batch and lot numbers in the BG1, with a period separator, and with the lot 

number appearing first. There had initially been some concern that both lot and serial 

number might not fit in the BG1 rp 45-65 field, for select stock numbers, requiring the lot 

number to be truncated, however Navy reported during the referenced teleconference that 

there were no combinations that would exceed the BG1 field size for lot number, serial 

number and the period separator, so truncation will not be required. 

(6) The following data requirements were reviewed, and it was determined a revision to 

DLMS was not required as data was already accommodated or not required: 

(a) Consignee – Identifies the DODAAC of the consignee of the material. 

DLMSO NOTE: This equates to the 527R 2/N101/210/RC -Receiving Location, which is the 

organization designated to receive the materiel, and 867I 2/N101/050/CN-Consigneee.

Consignee is not applicable to 947I Inventory Adjustment transactions.

 

(b) NIIN – Identified the National Item Identification Number of the item being 

reported. DLMSO NOTE: NIIN is not present in DLMS, but National Stock Number (NSN) 

is. When converting from DLMS 527R, 867I, 947I, DAASC to corresponding MILS with 

accompanying BG1 or BG2 transactions, DAASC shall derive the NIIN from the NSN at 
4 of 12 

ADC 261 

Attachment 

527R: 2/LIN02/010 FS = NSN; 867I: 2/REF01/30 NS = NSN; and 947I: 2/N901/0400 NS 

= NSN. 

(c) DAASC Mapping: Revise DAASC maps to accommodate converting from 

DLMS 527R, 867I and 947I, to DI Code BG1/BG2 as shown at Enclosure 1. The format for 

the NAVSUP P-724 BG1/BG2 transaction is provided at Enclosure 2 as background. 

(d) Procedures: Revise DLMS Supplements for 527R, 867I and 947I as 

follows: 

(1) DS 527R, Receipt, Inquiry, Response and MRA

Item # Location Revision to 

527R, Receipt, Inquiry, Response and 

MRA 

Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Note: 

Revise last sentence of DLMS introductory 

note 1 to add NAVSUP P-724 BG1/BG2:

DLMS Note 1 (last sentence): 

....This transaction also accommodates the 

functionality of non-DLSS DI Codes as 

follows: DI Codes C2J, C2K, and C3D in 

support of Medical requirements; DI Code 

BAY in support of Army Total Package 

Fielding; and Distribution Standard System 

DI Codes Z4S, Z6S, and Z6T supplemental 

receipt data; and NAVSUP P-724 BG1/BG2 

serial/lot number reporting transactions. 

To identify BG1/BG2 

transaction functionality 

accommodated in DS. 

No update 

needed. 

2. DLMS 

Introductory 

Note: 

Added ADC 261to DLMS Introductory note 

5.

- 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 

To identify DLMS 

changes included in the 

DS 

No update 

needed. 

3. 2/LQ01/130 Add new DLMS note 2 to qualifier ‘0-Document 

Identification Code’ and renumber exiting note 2 

as note 3:

0 Document Identification code 

New DLMS Note 2: In a mixed DLSS-DLMS 

environment, when including BG1/BG2 data for 

Army/Navy interface, Army must use 2 iterations 

of LQ to provide DI Code D6_ as well as either 

DI Code BG1 or BG2 as applicable, to alert 

DAASC of BG1/ BG2 requirement for nonDLMS Navy trading partner: Naval Operational 

Logistics Support Center (NOLSC) Ordnance 

Information Systems (OIS). 

To identify BG1/BG2 data 

is included in transaction 

during mixed 

DLSS/DLMS 

environment to assist with 

DAASC mapping from 

Army LMP generated 

527R to DLSS D6_ with 

BG1/BG2 transactions for 

Navy trading partner 

operating in DLSS. 

No update 

needed. 
5 of 12 

ADC 261 

Attachment 

Item # Location Revision to 

527R, Receipt, Inquiry, Response and 

MRA 

Reason Federal IC 

Impact 

4. 2/REF04/250 Open REF04 for optional use: 

Ref: REF04 

ID: C040 

Element Name: Reference Identifier 

Description: To identify one or more reference 

numbers or identification numbers as 

specified by the Reference Qualifier 

Ref: C04001 

ID: 128 

Element Name: Reference Identification 

Qualifier 

Description: Code qualifying the Reference 

Identification 

Req: M 

Type: ID 

Min/Max: 2/3 

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following 

codes are authorized. 

Code: 0N Attached To 

DLMS Note: Authorized DLMS enhancement 

for Army and Navy use. Use when REF01 = 

BT to identify the Lot Size for the lot number 

identified in REF02. DLMS Component 

unique enhancement (DI Code BG1/BG2, rp 

25-29). See introductory DLMS note 5.e. See 

ADC 261. 

Ref: C04002 

ID: 127 

Element Name: Reference Identification 

Description: Reference information as defined 

for a particular Transaction Set or as 

specified by the Reference Identification 

Qualifier 

Req: M 

Type: AN 

Min/Max: 1/30 

Using REF to convey a 

quantity for a given lot 

number since no quantity 

segment is available in the 

transaction structure UIT 

loop (LOOP ID -REF) for 

use with lot number. 

There could be multiple 

lot numbers associated 

with a given receipt 

transaction. Total receipt 

quantity is conveyed at 

2/RCD02/040. 

Update 

required. 

5. 2/N101/210 Add new DLMS note 2 to RC-Receiving 

Location: 

RC Receiving Location 

DLMS Note 2. Authorized DLMS enhancement 

for Army and Navy use with receipts to identify 

the consignee (DI Code BG1/BG2 rp 66-71). Use 

with N103 code 10-DODAAC. (See ADC 261.)

To acknowledge 

requirement for consignee 

in support of BG1/BG2 

data requirement. 

No update 

needed. 
6 of 12 

ADC 261 

Attachment 

Item # Location Revision to 

527R, Receipt, Inquiry, Response and 

MRA 

Reason Federal IC 

Impact 

6. 2/N103/210 Add new DLMS note 3 to 10-DODAAC

10 DODAAC 

DLMS Note: 

3. Authorized DLMS enhancement for Army and 

Navy use with N101 code RC to identify 

consignee DODAAC (DI Code BG1/BG2 rp 66-

71). (See ADC 261.) 

To provide for consignee 

DODAAC in support of 

DI Code BG1/BG2 data 

requirement. 

No update 

needed. 

7. 2/G6201/260 Add new qualifiers ‘BX-Action’ and ‘36-

Expiration’ with DLMS notes: 

BX Action 

DLMS Note: Use to identify the maintenance 

due date (the date that maintenance is due on the 

item). Authorized DLMS enhancement for Army 

and Navy use. DLMS Component unique 

enhancement (DI Code BG1/BG2, rp 9-11). See 

introductory note 5.e. See ADC 261. 

36 Expiration Date 

DLMS Note: Authorized DLMS enhancement 

for Army and Navy use to identify the 

expiration date of the reported item. DLMS 

Component unique enhancement (DI Code 

BG1/BG2, rp 9-11). See introductory note 5.e. 

See ADC 261. 

To add date requirement 

associated with Navy 

BG1/BG2 serial/lot 

number reporting 

transaction. 

No update 

needed. 

(2) DS 867I Issue: 

Item # Location Revision to 

867I, Issue 

Reason Federal IC 

Impact 

1. DLMS 

Introductory 

Note: 

Revise DLMS Introductory Note 1 to add 

BG1/BG2:

DLMS Note 1. Storage organizations use this 

transaction set to report material issues to 

Inventory Control Points (ICPs) or Integrated 

Material Managers (IMMs). This transaction 

encompasses functionality of MILSTRAP 

Document Identifier (DI) Code D7_. This 

transaction also accommodates the 

functionality of non-DLSS DI Codes BG1/BG2 

serial/lot number reporting transactions 

(published by NAVSUP P-724).

To identify BG1/BG2 

transaction functionality 

accommodated in DS. 

No update 

needed. 
7 of 12 

ADC 261 

Attachment 

Item # Location Revision to 

867I, Issue 

Reason Federal IC 

Impact 

2. DLMS 

Introductory 

Notes 

Add new DLMS introductory note 5.f and 

5.g:

f. Data required to accommodate 

Component-unique transaction 

requirements (e.g, C-series transactions). 

Data does not apply to DLSS transactions. 

g. Repetition of data (using multiple 

iterations or loops) which is not compatible 

with existing DLSS capability. Although 

supported by the use 

of the ANSI X12 standard, such data is not 

compatible with DLSS/DLMS conversion 

and may not be supported by the recipient's 

automated processing system. Components 

must coordinate implementation of 

enhanced capability with DLMSO prior to 

use. 

Administrative update to 

add standard DLMS 

introductory notes to 867I 

for consistency with other 

DS. 

No update 

needed. 

3. DLMS 

Introductory 

Notes 

Add ADC 261 to DLMS Introductory note 7.

- 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. 

To identify DLMS changes 

included in the DS 

No update 

needed. 

4. 2/N101/050 Added the following DLMS note 3 for 

existing qualifier “CN”

CN Consignee 

DLMS Note: 

3. Authorized DLMS enhancement for Army 

and Navy use to identify consignee (DI 

Code BG1/BG2 rp 66-71). Use with N103 

code 10-DODAAC. DLMS Component 

unique enhancement. See introductory 

DLMS note 5.f. See ADC 261. 

To acknowledge requirement 

for consignee in support of 

BG1/BG2 data requirement. 

No update 

needed. 

5. 2/N103/050 Added DLMS note 2 for qualifier “10”

10 Department of Defense Activity Address 

Code (DODAAC) 

DLMS Note: 

2. Authorized DLMS enhancement for Army 

and Navy use with N101 code CN to 

provide consignee DODAAC (DI Code 

BG1/BG2, rp 66-71). DLMS Component 

unique enhancement. See introductory 

DLMS note 5.f. See ADC 261. 

To provide for consignee 

DODAAC in support of DI 

Code BG1/BG2 data 

requirement. 

No update 

needed. 
8 of 12 

ADC 261 

Attachment 

Item # Location Revision to 

867I, Issue 

Reason Federal IC 

Impact 

6. 2/LQ01/270 Add new DLMS note 2 to qualifier ‘0-

Document Identification Code’ and 

renumber exiting note 2 as note 3:

0 Document Identification code 

DLMS Note: 

2. In a mixed DLSS-DLMS environment, 

for the Army/Navy interface, when 

including BG1/BG2 data, Army must use 2 

iterations of LQ to provide DI Code D7_ as 

well as either DI Code BG1 or BG2 as 

applicable, to alert DAASC of BG1/BG2 

requirement for non-DLMS Navy trading 

partner: Naval Operational Logistics 

Support Center (NOLSC) Ordnance 

Information Systems (OIS). 

To identify BG1/BG2 data 

is included in transaction 

during mixed DLSS/DLMS 

environment to assist with 

DAASC mapping from 

Army LMP generated 867I 

to DLSS D7_ with Navy 

BG1/BG2 transactions for 

Navy trading partner 

operating in DLSS. 

No update 

needed. 

7. 2/REF04/290 Open REF04 for optional use: 

Ref: REF04 O COMP 

ID: C040 

Ref: C04001 

ID: 128 Reference Identification Qualifier 

Description: Code qualifying the Reference 

Identification 

Req: M 

Type: ID 

Min/Max: 2/3 

Federal Note: Use any code.

DLMS Note: For DLMS use, only the 

following codes are authorized. 

Code: 0N Attached To 

DLMS Note: Authorized DLMS 

enhancement for Army and Navy use. Use

when REF01 = BT to identify the Lot Size 

for the lot number identified in REF02. 

DLMS Component unique enhancement (DI 

Code BG1/BG2, rp 25-29). See 

introductory DLMS note 5.f. See ADC 261. 

Ref: C04002 

ID: 127 

Element Name: Reference Identification 

Description: Reference information as 

defined for a particular Transaction Set or 

as 

specified by the Reference Identification 

Qualifier 

Req: M 

Type: AN 

Min/Max: 1/30 

Using REF to convey a 

quantity for a given lot 

number since no quantity 

segment is available in the 

transaction structure for the 

UIT loop (LOOP ID-LX) 

for use with lot number. 

There could be multiple lot 

numbers associated with a 

given issue transaction. 

Total issue quantity is 

conveyed at 2/QTY01-

02/110/V3. 

Update 

required. 
9 of 12 

ADC 261 

Attachment 

Item # Location Revision to 

867I, Issue 

Reason Federal IC 

Impact 

7. 2/DTM01/300 Add new qualifier ‘036-Expiration Date’ with 

DLMS Note:

036 Expiration Date 

DLMS Note: Authorized DLMS 

enhancement for Army and Navy use to 

identify the expiration date of the reported 

 item. DLMS Component unique enhancemen

(DI Code BG1/BG2, rp 9-11). See introductor

DLMS note 5.f. See ADC 261. 

To add date requirement 

associated with Navy BG1/ 

BG2 serial/lot number 

reporting transaction. 

No update 

needed. 

8. 2/DTM01/300 Add new qualifier ‘302-Maintenance’ with 

DLMS note: 

302 Maintenance 

DLMS Note: Use to identify the 

maintenance due date (the date that 

maintenance is due on the item). 

Authorized DLMS enhancement for Army 

and Navy use. DLMS Component unique 

enhancement (DI Code BG1/BG2, rp 9-11). 

See introductory note 5.f. See ADC 261. 

To add date requirement 

associated with Navy BG1/ 

BG2 serial/lot number 

reporting transaction. 

No update 

needed. 

(3) DS 947I Inventory Adjustment (version 4010 is shown below, 

corresponding changes will be made to version 4030): 

Item # Location Revision to 

947I, Inventory Adjustment 

Reason Federal IC 

Impact 

1. DLMS Introductory 

Note: 

Revise DLMS Introductory Note 1 to add 

BG1/BG2:

DLMS Note 1. Use a single occurrence of 

this transaction set to exchange inventory 

adjustment transactions between a single 

ICP or IMM and a single or multiple storage 

organizations, between a single ICP or IMM 

and a single or multiple ICPs or IMMs, or 

between a single storage organization and a 

single or multiple ICPs or IMMs. This 

transaction encompasses functionality of 

MILSTRAP DI Codes D8_, D9_, DAC, 

DAD, and DAS. This transaction also 

accommodates the functionality of nonDLSS DI Codes BG1/BG2 serial/lot number 

reporting transactions (published by 

NAVSUP P-724). 

To identify BG1/BG2 

transaction functionality 

accommodated in DS. 

No update needed. 
10 of 12 

ADC 261 

Attachment 

Item # Location Revision to 

947I, Inventory Adjustment 

Reason Federal IC 

Impact 

2. DLMS Introductory 

Notes 

Add new DLMS introductory note 4.f and 

4.g:

f. Data required to accommodate 

Component-unique transaction requirements 

(e.g, C-series transactions). Data does not 

apply to DLSS transactions. 

g. Repetition of data (using multiple 

iterations or loops) which is not compatible 

with existing DLSS capability. Although 

supported by the use of the ANSI X12 

standard, such data is not compatible with 

DLSS/DLMS conversion and may not be 

supported by the recipient's automated 

processing system. Components must 

coordinate implementation of enhanced 

capability with DLMSO prior to use. 

Administrative update to 

add standard DLMS 

introductory notes to 947I 

for consistency with other 

DS. 

No update needed. 

3. DLMS Introductory 

Note 

Added ADC 261 to DLMS Introductory note 

6.

- ADC 261, Migrate Navy Serial Number 

and Lot Number Transactions (NAVSUP P724 BG1/BG2) to DLMS 527R Receipt, 867I 

Issue, and 947I Inventory Adjustment. 

To identify DLMS changes 

included in the DS 

No update needed. 

4. 2/LQ01/100 Add new DLMS note 2 to qualifier ‘0-

Document Identification Code’ and 

renumber exiting note 2 as note 3:

0 Document Identification code 

DLMS Note: 

2. In a mixed DLSS-DLMS environment, 

for the Army/Navy interface, when including 

BG1/BG2 data, Army must use 2 iterations 

of LQ to provide DI Code D8_/D9_ as well 

as either DI Code BG1 or BG2 as 

applicable, to alert DAASC of BG1/ BG2 

requirement for non-DLMS Navy trading 

partner: Naval Operational Logistics 

Support Center (NOLSC) Ordnance 

Information Systems (OIS). 

To identify BG1/BG2 data 

is included in transaction 

during mixed DLSS/DLMS 

environment. This will 

assist with DAASC 

mapping from Army LMP 

generated 947I to DLSS 

D8_ , D9_, or DAC with 

Navy BG1/BG2 

transactions, for Navy 

trading partner operating in 

DLSS. 

No update needed. 

5. 2/N901/160 Add Federal and DLMS note to version 

4010 (version 4030 is already updated):

Federal Note: Use any code.

DLMS Note: For DLMS use only the 

following codes are authorized. 

Administrative update for 

version 4010. 

Update required 

for 4010. 

No update needed 

for 4030. 

6. 2/N907/C0401/160 Add Federal and DLMS note to version 

4010 (version 4030 is already updated):

Federal Note: Use any code.

DLMS Note: For DLMS use, only the 

following codes are authorized. 

Administrative update for 

version 4010. 

Update required 

for 4010. 

No update needed 

for 4030. 
11 of 12 

ADC 261 

Attachment 

Item # Location Revision to 

947I, Inventory Adjustment 

Reason Federal IC 

Impact 

7. 2/N907/C0401/160 Add qualifier with DLMS note (to both 4010 

and 4030): 

Code: 0N Attached To 

DLMS Note: Authorized DLMS 

enhancement for Army and Navy use. Use

when N90101 = BT to identify the Lot Size 

for the lot number identified in N902. 

DLMS Component unique enhancement

(DI Code BG1/BG2, rp 25-29). See 

introductory DLMS note 4f. See ADC 

261. 

Using N9 segment to 

convey a quantity for a 

given lot number since no 

quantity segment is 

available in the transaction 

structure for the UIT loop 

(LOOP ID-0330) for use 

with lot number. There 

could be multiple lot 

numbers associated with a 

given inventory adjustment 

transaction. Total inventory 

adjustment quantity is 

conveyed at 2/W1902/20. 

8. 2/G6201/170 Add Federal and DLMS note to version 

4010 (version 4030 is already updated):

Federal Note: Use any code.

DLMS Note: For DLMS use only the 

following codes are authorized. 

Administrative update for 

version 4010. 

Update required 

for 4010. 

No update needed 

for 4030. 

9. 2/G6201/170 Add new qualifier ‘36-Expiration Date’ with 

DLMS note: 

36 Expiration Date 

DLMS Note: Authorized DLMS 

enhancement for Army and Navy use to 

identify the expiration date of the reported 

item. DLMS Component unique 

enhancement (DI Code BG1/BG2, rp 9-11). 

See introductory DLMS note 4.f. See ADC 

261. 

To add date requirement 

associated with Navy 

BG1/BG2 serial/lot number 

reporting transaction. 

No update needed. 

10. 2/G6201/170 Add new qualifier ‘BX-Action’ with DLMS 

note: 

BX Action 

DLMS Note: Use to identify the 

maintenance due date (the date that 

maintenance is due on the item). 

Authorized DLMS enhancement for Army 

and Navy use. DLMS Component unique 

enhancement (DI Code BG1/BG2, rp 9-11). 

See introductory DLMS note 4.f. See ADC 

261. 

To add date requirement 

associated with Navy 

BG1/BG2 serial/lot number 

reporting transaction. 

No update needed. 

(e) Alternatives: None known. 

5. REASON FOR CHANGE: Existing DLMS ICs 527R, 867I and 947I do not contain 

all the data elements necessary to support BG1/BG2 requirements, and the existing 

DAASC mappings do not accommodate the Navy-unique DI Code BG1/BG2 

transactions. 
12 of 12 

ADC 261 

Attachment 

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 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 DAASC’s mission of translating and routing various supply actions 

to and from trading partners. Without this change, the Army LMP system would be required to 

continue generating 80-record position BG1/BG2 transactions for the Navy trading partner 

operating in DLSS, after Army LMP has implemented DLMS. This change also supports future 

Navy DLMS implementation by accommodating Navy’s NAVSUP P-724 BG1/BG2 data in 

standard DLMS transactions. 

 b. Disadvantages: None known.

7. IMPACT: Modify DOD 4000.25-M, DLMS Supplements 527R, 867I and 947I and 

DAASC conversion maps.
1 of 6 

ADC 261 

Enclosure 1 

ENCLSOURE 1 to ADC 261 

BG1/BG2 Mapping to DLMS 527R, 867I, 947I 

1. BG1/BG2 Mapping for 527R: 

BG1/BG2 

Field Name 

Record 

Positions 

527R Mapping 527R 

Position/Loop 

Header Transaction 

(D6_) Positions 

Document 

Identifier Code 

1 – 3 LQ01 = 0 

LQ02 = BG1 or BG2 

130/LM N/A 

Routing 

Identifier 

4 – 6 Perpetuate from N101 = Z4 

N103 = M4 

N104 = RP 4 – 6 

N106 = TO 

210/N1 4 - 6 

Management 

Code 

7 If G6201=BX, RP 7=P 

If G6201=36, RP 7=E 

260/REF N/A 

Blank 8 

Date to be 

posted 

9 – 11 Maintenance (Inspection) Due Date 

G6201 = BI 

G6202 = RP 9-11 (format MYY. Month 1 – 9 

represents January – September, O – October, N – 

November, D – December) 

Expiration Date 

G6201 = 36 

G6202 = RP 9-11 (format MYY. Month 1 – 9 

represents January – September, O – October, N – 

November, D – December) 

260/REF N/A 

NIIN 12 – 20 Derived from Positions 5-13 of 

LIN02=FS 

10/LIN Positions 5 – 13 of 

8 – 22 

Blank 21 

Purpose Code 22 Perpetuate from 

LQ01 = 99 

130/LM 70 

Action Code 23 – 24 Derived from position 2-3 of 

LQ01=0 

OR 

If LIN01 = B, RP 23 – 24 = 6U 

 C 6V 

 D 6L 

 E 6M 

 F 6G 

 G 6H 

 H 6N 

 I 6A 

 J 6B 

 K 6C 

 L 6D 

 M 6E 

 N 6K 

 P 6J 

 Q 6Q 

 R 6R 

 S 6T 

 T 6X 

 Z 6Z 

130/LM Positions 2 – 3 of 1 – 3 
2 of 6 

ADC 261 

Enclosure 1 

BG1/BG2 

Field Name 

Record 

Positions 

527R Mapping 527R 

Position/Loop 

Header Transaction 

(D6_) Positions 

Quantity 25 – 29 For BG1, DAASC enter deafult value 1 

For BG2: 

REF04/C04001 = 0N 

REF04/C04002 = RP 25 – 29 (No Leading Zeroes) 

If first position is “-“ sign, must convert to 5 

position number with leading zeroes and the first 

number to Alpha Character: } = 0, J=1, K=2, L=3, 

M=4, N=5, O=6, P=7, Q=8, R=9 

250/REF N/A 

Document 

Number 

30 – 43 Perpetuate from 

N901=TN 

N902=RP 30-43 

30/LIN 30 – 43 

Blank 44 

Serial or Lot 

Number 

45 – 65 If N901 is present, 

RP 45 – 65 = N902, “.”, REF02 

Else 

If N901 = BT or SE 

RP 45 – 65 = N902 

270/REF N/A 

Consignee 66 – 71 N101=RC 

N103=10 

N104=RP 66 -71 

210/N1 N/A 

Routing 

Identifier 

72 – 74 Perpetuate from 

N101=RC 

N103=M4 

N104=RP 72-74 

N106=FR 

70/N1 67 – 69 

Blank 75 

Current 

Condition Code 

76 Perpetuate from 

LQ01 = 83 

LQ01 = RP 76 

130/LM 71 

Transaction 

Date 

77 – 79 G6201=BB 

G6202=CCYYMMDD 

50/RCD NA 

Blank 80 

2. BG1/BG2 Mapping for 867I: 

BG1/BG2 

Field Name 

Record 

Positions 

867I Mapping 867I 

Position/Loop 

Header Transaction 

(D7_) Positions 

Document 

Identifier Code 

1 – 3 LQ01 = 0 

LQ02 = BG1 or BG2 

270/LM N/A 

Routing 

Identifier 

4 – 6 Perpetuate from 

N101 = Z4 

N103 = M4 

N104 = RP 4 – 6 

N106 = TO 

50/N1 4 – 6 

Management 

Code 

7 If DTM01=302, RP 7=P 

If DTM01=036, RP 7=E 

300/LX N/A 

Blank 8 
3 of 6 

ADC 261 

Enclosure 1 

BG1/BG2 

Field Name 

Record 

Positions 

867I Mapping 867I 

Position/Loop 

Header Transaction 

(D7_) Positions 

Date to be 

posted 

9 – 11 Maintenance (Inspection) Due Date 

DTM01 = 302 

DTM02 = RP 9-11 (format MYY. Month 1 – 9 

represents January – September, O – October, N – 

November, D – December) 

Expiration Date 

DTM01 = 036 

DTM02 = RP 9-11 (format MYY. Month 1 – 9 

represents January – September, O – October, N – 

November, D – December) 

300/LX N/A 

NIIN 12 – 20 Derived from Positions 5-13 of 

REF01=NS 

30/PTD Positions 5 – 13 of 8 – 

22 

Blank 21 

Purpose Code 22 Perpetuate from 

LQ01 = 99 

270/LM 70 

Action Code 23 – 24 Derived from position 2-3 of 

LQ01=0 

OR 

If PTD01 = SS, RP 23 – 24 = 7A 

 BD 7B 

 BC 7C 

 BE 7D 

 BF 7E 

 BG 7G 

 BH 7H 

 BI 7J 

 BJ 7K 

 BK 7L 

 BL 7M 

 BM 7N 

 BN 7P 

 BO 7Q 

 BR 7R 

 BQ 7Z 

270/LM Positions 2 – 3 of 1 – 3 

Quantity 25 – 29 For BG1, DAASC enter deafult value of 1 

For BG2: 

REF04/C04001 = 0N 

REF04/C04002 = RP 25 – 29 (No Leading Zeroes) 

If first position is “-“ sign, must convert to 5 

position number with leading zeroes and the first 

number to Alpha Character: } = 0, J=1, K=2, L=3, 

M=4, N=5, O=6, P=7, Q=8, R=9 

290/RLX N/A 

Document 

Number 

30 – 43 Perpetuate from 

REF01=TN 

REF02=RP 30-43 

30/PTD 30 – 43 

Blank 44 

Serial or Lot 

Number 

45 – 65 If both REF01 = BT and SE are present, 

RP 45 – 65 = REF02 (REF01=BT), “.”, REF02 

(REF01=SE) 

Else 

If REF01 = BT or SE 

RP 45 – 65 = REF02 

290/LX N/A 

Consignee 66 – 71 N101=CN 

N103=10 

N104=RP 66 -71 

50/N1 N/A 
4 of 6 

ADC 261 

Enclosure 1 

BG1/BG2 

Field Name 

Record 

Positions 

867I Mapping 867I 

Position/Loop 

Header Transaction 

(D7_) Positions 

Routing 

Identifier 

72 – 74 Perpetuate from 

N101=RC 

N103=M4 

N104=RP 72-74 

N106=FR 

80/N1 67 – 69 

Blank 75 

Current 

Condition Code 

76 Perpetuate from 

LQ01 = 83 

LQ01 = RP 76 

270/LM 71 

Transaction 

Date 

77 – 79 DTM01=140 

DTM02=CCYYMMDD 

20/PTD 

Blank 80 

3. BG1/BG2 Mapping for 947I: 

Field Name DLSS 

Positions 

Revision to 

947I Mapping 

947I 

Position/Loop 

Header Transaction 

(D8_/D9_) Positions 

Header Transaction 

(DAC/DAD) Positions

Document 

Identifier Code 

1 – 3 LQ01 = 0 

LQ02 = BG1 or BG2 

100/0310 N/A N/A 

Routing 

Identifier 

4 – 6 Perpetuate from 

N101 = Z4 

N103 = M4 

N104 = RP 4 – 6 

N106 = TO 

110/0320 4 – 6 4 – 6 

Management 

Code 

7 If G6201=BX, RP 7=P 

If G6201=36, RP 7=E 

170/0330 N/A N/A 

Blank 8 

Date to be 

posted 

9 – 11 Maintenance (Inspection) Due 

Date 

G6201 = BX 

G6202 = RP 9-11 (format 

MYY. Month 1 – 9 represents 

January – September, O – 

October, N – November, D – 

December) 

Expiration Date 

G6201 = 36 

G6201 = RP 9-11 (format 

MYY. Month 1 – 9 represents 

January – September, O – 

October, N – November, D – 

December) 

170/0330 N/A N/A 

NIIN 12 – 20 Derived from Positions 5-13 of 

W1905=FS 

020/0300 Positions 5 – 13 of 

8 – 22 

Positions 5 – 13 of 

8 – 22 

Previous 

Purpose Code 

21 Perpetuate from 

LQ01 = RD or RE 

100/0310 70 

Purpose Code 22 Perpetuate from 

LQ01 = A1 or 99 

100/0310 70 65 
5 of 6 

ADC 261 

Enclosure 1 

Field Name DLSS 

Positions 

Revision to 

947I Mapping 

947I 

Position/Loop 

Header Transaction 

(D8_/D9_) Positions 

Header Transaction 

(DAC/DAD) Positions

Action Code 23 – 24 Derived from position 2-3 of 

LQ01=0 

OR 

If W1916 = AJ AND 

W1901 = AA, RP 23–24 = 8A 

 AB 8B 

 AC 8C 

 AD 8D 

 AE 8J 

 AF or AN 8K 

 AG 8S 

 AH 8Z 

 AL 8F 

 AK 8E 

 AI 8H 

 AN 8K 

 AJ 8G 

If W1916 = AD AND 

W1901 = AA, RP 23–24 = 9A 

 AB 9B 

 AC 9C 

 AD 9D 

 AE 9J 

 AF or AN 9K 

 AG 9S 

 AH 9Z 

 AL 9F 

 AK 9E 

 AI 9H 

 AN 9K 

 AJ 9G 

If W1916 = DU AND 

W1901 = AC, RP 23-24 = AC 

 AD or AG AD 

100/0310 Positions 2 – 3 of 1 – 

3 

Positions 2 – 3 of 1 – 3 

Quantity 25 – 29 For BG1, DAASC enter deafult 

value of 1 

For BG2: 

N907/C04001 = 0N 

N907/C04002 = RP 25 – 29 (No 

Leading Zeroes) 

If first position is “-“ sign, must 

convert to 5 position number 

with leading zeroes and the first 

number to Alpha Character: } = 

0, J=1, K=2, L=3, M=4, N=5, 

O=6, P=7, Q=8, R=9 

160/0330 N/A N/A 

Document 

Number 

30 – 43 Perpetuate from 

N901=TN 

N902=RP 30-43 

040/0300 30 – 43 30 – 43 

Blank 44 

Serial or Lot 

Number 

45 – 65 If both N901 = BT and SE are 

present, 

RP 45 – 65 = N902 (N901=BT), 

“.”, N902 (N901=SE) 

Else 

If N901 = BT or SE 

RP 45 – 65 = N902 

160/0330 N/A N/A 

Consignee 66 – 71 NA NA NA 
6 of 6 

ADC 261 

Enclosure 1 

Field Name DLSS 

Positions 

Revision to 

947I Mapping 

947I 

Position/Loop 

Header Transaction 

(D8_/D9_) Positions 

Header Transaction 

(DAC/DAD) Positions

Routing 

Identifier 

72 – 74 Perpetuate from 

N101=RC 

N103=M4 

N104=RP 72-74 

N106=FR 

040/0100 67 – 69 67 – 69 

Original 

Condition Code 

75 Perpetuate from 

LQ01 = BG 

LQ01 = RP 76 

100/0310 71 

Current 

Condition Code 

76 Perpetuate from 

LQ01 = 83 

LQ01 = RP 76 

100/0310 71 66 

Transaction 

Date 

77 – 79 G6201=BB 

G6202=CCYYMMDD 

170/0330 NA NA 

Blank 80 
1 of 2 

ADC 261 

Enclosure 2 

NAVSUP P-724 BG1/BG2 Format 

ENCLOSURE 2 TO ADC 261 

Excerpt From NAVSUP P-724 REV 12, CONVENTIONAL ORDNANCE STOCKPILE 

MANAGEMENT 

VOLUME I ASHORE 

SLIT TRANSACTION REPORT FORMATS 

Card Entry Remarks 

Column 

1-3 BG1, BG2 Document Identifier 

BG1 – Serial Number or Lot and 

Serial Number Controlled Item 

Transaction 

BG2 – Lot Number Controlled 

Item Transaction 

4-6 NCB NCB for Navy or MHQ for 0T 

 Cog Assets 

7 MANAGEMENT CODE Designates the type of posting. 

 Used on the “YY” transaction 

 date (MDD) posting “P” 

Container Code “C” or 

Expiration Date (EXP) Posting 

“E”, otherwise leave blank. 

8 TYPE MAINTENANCE Type of Maintenance Due on 

DUE OR CONTAINER the reported item. To be 

reported on the code “YY” 

transaction for MK46 Torpedoes & 

ALMS. The Item of Record (AUR) 

or assembly) associated with a 

container. The Container Codes are 

provided in Attachment (2-28).

9-11 DATE TO BE POSTED The MDD or expiration date of 

 the reported item. The month 

 and year (MW) will be provided. 

 The type of date posting is 

 determined by the management 

 code in cc 7. Month – 1 through 

 9 represents January through 

 September, O – October, N – 

 November and D - December. 

 This applies to the date posting 

 “YY” transaction only. 

12-20 NIIN National Item Identification 

 Number – the NIIN of the item 

 being reported. 

21 PREVIOUS PURPOSE CODE The pervious purpose code of 

 the reported item. Used on the 

 purpose code change (AD 

 transaction only) otherwise 

 leave blank. 
2 of 2 

ADC 261 

Enclosure 2 

NAVSUP P-724 BG1/BG2 Format 

22 PURPOSE CODE The current Purpose Code of 

 the item being reported. 

23-24 ACTION CODE Identifies the action taken on the 

 reported item. 

25-29 QUANTITY BG1 transactions – blank or 

 00001 is acceptable. 

 BG2 transactions – the quantity 

 of the item by lot number 

 reported in cc 45 thru 65 of the 

 transaction. (right justified and 

 preceding zeros) The reversal 

 indicator is punched in cc 25. 

30-43 DOCUMENT NUMBER A non-duplicative number used 

to identify individual 

transactions. 

 See NAVSUP Pub 485 for more 

 details. 

44 BLANK 

 

45-65 SERIAL or LOT NUMBER Serial, Lot or Lot and Serial 

 Number of the reported item. 

 Left justify, no special 

 characters or spaces with the 

 exception of the dash and 

 period separator. The period will 

 separate Lot and Serial Number 

 for MCC “E” items. Local 

 activities with a slash should 

 report a period. 

66-71 CONSIGNEE Activity Address Code (ACC) of 

 consignee for material. 

72-74 ROUTING IDENTIFIER Routing Identifier of the 

 reporting activity. 

75 PREVIOUS CONDITION CODE Previous Condition Code of the 

 reported item. Used on the 

 Condition Code change 

 transaction “AC” only, otherwise 

 leave blank. 

76 CURRENT CONDITION CODE Current Condition Code of the 

 reported item. 

77-79 TRANSACTION DATE Three digits Julian date of the 

 report. 

80 BLANK