1 of 11 

ADC 283 

Attachment 

ATTACHMENT TO ADC 283 

Migrate Navy Serial Number and Lot Number Transactions 

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

1. ORIGINATOR: 

a. Service/Agency: Army in conjunction with Navy

b. Originator: 

(1) Army: Logistics Modernization Program (LMP), Support Contractor, 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. DLMSO memorandum, January 7, 2008, subject: 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 (Supply) 

(Staffed by PDC 261), http://www.dla.mil/j-6/dlmso/eLibrary/Changes/approved3.asp. 

 

c. NAVSUP P-485, Naval Supply Procedures

4. REQUESTED CHANGE: 

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

to DLMS 846R Location Reconciliation Request

b. Description of Change: 

(1) This change revises the Federal Implementation Convention (IC) and DLMS Supplement 

(DS) 846R, Location Reconciliation Request, to incorporate data contained in Navy NAVSUP P-724 

(reference 3.a) Serial Number and Lot Number Reports (Navy Document Identifier requirement has 

only been identified for an existing Army and Navy). 

(2) Army has identified a requirement for using the 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 has no other requirement for their use other than sending the 

BG1/BG2 information to Navy for the stated Navy interface. The inclusion of serial/lot number data 
2 of 11 

ADC 283 

Attachment 

is, therefore, identified and approved for Navy and the Army/Navy interface. Any additional 

requirements for serial/lot number use in DLMS 846R by/with other DoD Components should be 

identified to DLMSO by a separate PDC. 

(3) ADC 261 (reference 3.b.) previously added Navy BG1/BG2 data to DS 527R (receipt), 

867I (issue), and 947I (inventory adjustment). The rationale for the additions of BG1/BG2 data to 

DLMS 846R is identical to that documented under ADC 261. As documented in ADC 261, Navy 

BG1 and BG2 transactions are presently submitted in a Defense Logistics Standard System (DLSS) 

environment, as supplemental information for receipt (DI Code D6_), issue (DI Code D7_), and 

inventory adjustment (DI Code D8_/D9_/DAC) transactions. In addition, BG1/BG2 transactions 

are also submitted with MILSTRAP DI Code DZH, Location Reconciliation Request transactions. 

(4) This change updates DS 846R Location Reconciliation Request to add data elements to 

support BG1/BG2 functionality. Army LMP will include the data in DS 846R 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 DI CODE DZH and BG1 or BG2 transaction formats when required for 

NOLSC. This may require DAASC to extract multiple transactions when translating from 

DLMS to MILS format. For example, when converting a DS 846R location reconciliation 

request transaction which has BG1 or BG2 data for a non-DLMS NOLSC trading partner, a single 

846R for a quantity of 100 could translate into a single DZH for a quantity of 100, with 100 BG1 

transactions, one BG1 for each serial number. Navy has confirmed that either BG1 or BG2 

transactions are used for a given corresponding MILS transaction, but not both. The BG1/BG2 

transactions are not sent to Army, so the DAASC conversion will be one-way for this Army-Navy 

interface, from the DLMS to MILSTRAP DZH transaction with BG1 or BG2 transactions. 

(5) The DLMS transactions addressed under ADC 261 already had existing segments and 

data elements for serial number and lot number. Unlike the ADC 261 transactions, DS 846R does 

not currently include lot/serial number information. No requirement for use of lot or serial number 

had previously been identified for location reconciliation requests. Accordingly, considerable 

changes are required to include the applicable segments to accommodate the data in the 846R. 

This PDC aligns the DLMS 846R transaction format with the existing DLMS 846 transactions 

containing unique identification (UID) and Unique Item Tracking (UIT) data to include serial/lot 

number data: 846A, 846F, and 846I. This change to the 846R will require the opening of the 

following segments: 

 (a) Loop Header (2/LS/380) 

 (b) Reference Identification (2/REF/390 loop) 

(c) Date/Time Reference (2/DTM/400) 

(d) Name (2/N1/410) 

(e) Code Source Information (2/LM/420) 

(f) Industry Code (2/LQ/420) 

(g) Loop Trailer (2/LE/440) 

c. DAASC Mapping: Revise DAASC maps to accommodate converting from DLMS 846R 

to DI Code BG1/BG2 as shown at Enclosure 1. The NAVSUP P-724 BG1/BG2 format is provided 

at Enclosure 2 as background. Navy currently has a second version of DI Code BG1/BG2 format 

documented in NAVSUP P-485 (reference 3.c.). However, during ADC 261 discussions, Navy has 

indicated they plan to remove the formats from NAVSUP P-485, and defer to NAVSUP P-724. 

Accordingly, this change, as well as ADC 261, addresses only the NAVSUP P-724 formats. 
3 of 11 

ADC 283 

Attachment 

d. Procedures: Revise DS 846R for Location Reconciliation Request as follows: 

Item 

# 

Location Revision to 

846R, Location Reconciliation Request 

Reason Federal 

IC 

Impact 

1. DLMS 

Introductory 

Note 

Revise last sentence of DLMS introductory note 1 to add 

NAVSUP P-724 BG1/BG2:

1. Distribution depots and storage activities use a single 

occurrence of this transaction set to transmit either 

location reconciliation request, location reconciliation 

notification, or location reconciliation history 

notification transactions to one owner/manager. This 

transaction encompasses the functionality of MILSTRAP 

Document Identifier (DI) Codes DZH, DZN, DZP and 

NAVSUP P-724 BG1/BG2 serial/lot number reporting 

transactions. 

To identify 

BG1/BG2 

transaction 

functionality is 

accommodated in 

DS. 

No update 

needed. 

2. DLMS 

Introductory 

Note 

Add new DLMS introductory note 4.e:

4.e. Data required to accommodate Component- unique 

transaction requirements (e.g., B-series transactions). 

Data does not apply to DLSS transactions. 

Administrative 

update to add 

standard DLMS 

introductory note 

to DS. 

No update 

needed. 

3. DLMS 

Introductory 

Note 

Add new DLMS introductory note 4.f:

4.f. Data associated with a DLMS enhancement 

authorized for implementation by modernized systems 

under DLMS migration. This data (including expanded 

field sizes) should be adopted during, or subsequent to, 

modernization when applicable to the Component’s 

business process. Prior coordination is not required. 

Components should ensure that inclusion of this data in a 

DLMS transaction does not cause inappropriate rejection 

of the transaction. 

Administrative 

update to add 

standard DLMS 

introductory note 

to DS. 

No update 

needed. 

4. DLMS 

Introductory 

Note 

Add new DLMS introductory note 5 and renumber note 5 

as 6:

5. This transaction may be used to provide Unique Item 

Identifier (UII) information. Refer to the Unique 

Identification (UID) web at URL: 

http://www.acq.osd.mil/dpap/sitemap.html for DoD 

policy and business rules.

To identify website 

for UID policy. 

No update 

needed.

5. DLMS 

Introductory 

Note 

Added ADC 283 to DLMS Introductory note 6 

(renumbered from 5).

- ADC 283, Migrate Navy Serial Number and Lot 

Number Transactions (NAVSUP P-724 BG1/BG2) to 

DLMS 846R Location Reconciliation Request. 

To identify DLMS 

changes included 

in the DS 

No update 

needed. 
4 of 11 

ADC 283 

Attachment 

Item 

# 

Location Revision to 

846R, Location Reconciliation Request 

Reason Federal 

IC 

Impact 

6. 1/LQ01/150 Add new DLMS note 3 to qualifier ‘0-Document 

Identification Code’:

0 Document Identification code 

DLMS Note 3: 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 

DZH 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 846R to 

DLSS DZH with 

BG1/BG2 data for 

Navy trading 

partner operating in 

DLSS. 

No update 

needed. 

7. 2/LS/380 Open the 2/LS/380 loop for optional use: 

Federal Note: Use as needed in each 2/QTY/320 loop to 

prevent a syntax error in the use of the 2/REF/390 loop. 

Change LS loop 

from ‘not used’ to 

‘used’ to provide 

the structure 

necessary to 

include Unique 

identification 

(UID)/unique item 

tracking (UIT) 

information. 

Update 

required.

8. 2/LS01/380 Add Federal Note to LS01: 

Federal Note: Cite REF to indicate the 2/REF/390 loop. 

To provide the 

structure necessary 

to include 

UID/UIT 

information. 

Update 

required 
5 of 11 

ADC 283 

Attachment 

Item 

# 

Location Revision to 

846R, Location Reconciliation Request 

Reason Federal 

IC 

Impact 

9. 2/REF/390 Open the 2/REF/390 segment for optional use and add 

Federal and DLMS notes: 

Federal Note: Use the 2/REF/390 segment when needed 

to provide Unique Identification (UID) information. 

DLMS Notes: 

1. The entire 2/REF/390 loop is a DLMS enhancement 

and was added for use with location reconciliation 

request transactions to support a requirement identified 

by Army and Navy to support a Naval Operational 

Logistics Support Center (NOLSC) Ordnance 

Information Systems (OIS) requirement. No other 

Component has identified a requirement for use of 

serial/lot number or UII information with location 

reconciliation requests. See introductory DLMS notes 4a 

and 4e. See ADC 283 

2. Must use 2/REF/390 loop in Location Reconciliation 

Request transactions when including unique item 

identifier (UII), serial number, and/or batch/lot number. 

3. This transaction will support item identification based 

upon the UII or the serial number, and provides 

flexibility to accommodate tracking by UII or serial 

number. This transaction also provides for use of a 

batch/lot number when applicable. 

4. The 2/REF/390 loop is repeated for each item to be 

identified by UII, serial number or batch/lot number. 

5. If UII and serial number, and/or batch/lot number are 

required for the item, enter the UII in REF01, and enter 

the serial number and/or batch/lot number in REF04. If 

UII is not used, enter the serial number in REF01 and 

enter the batch/lot number in REF04. If only batch/lot 

number is required, enter the batch/lot number in REF01. 

To provide the 

structure necessary 

to include UID 

information, 

consistent with 

other DLMS 846 

transactions with 

UID/UIT data (DS 

846A, 846F, and 

846I). Supports 

stated Army/Navy 

requirements for 

BG1/BG2 data. 

Update 

required

10. 2/REF01/390 Open REF01 with Federal and DLMS notes: 

Federal Note: Use any code 

DLMS Note: For DLMS use, only the following codes 

are authorized. 

To add standard 

notes and provide 

the structure 

necessary to 

include UID/UIT 

information. 

Update 

required
6 of 11 

ADC 283 

Attachment 

Item 

# 

Location Revision to 

846R, Location Reconciliation Request 

Reason Federal 

IC 

Impact 

11. 2/REF01/390 Add qualifiers BT, SE, and U3 with DLMS notes:

BT Batch Number 

DLMS Notes: 1. Use to identify the manufacturer's 

batch/lot number or other number identifying the 

production run when UII and/or serial number are not 

required. If UII and/or serial number are required in 

addition to the batch/lot number, enter the batch/lot 

number in REF04. The batch/lot number may not exceed 

20 characters in accordance with IUID policy. 

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

3. Supports Navy BG1/BG2 data requirement. See 

introductory DLMS note 4.e. When used with Navy 

BG1/BG2 transactions, this qualifier implies that the 

transaction is a BG2 (Lot Number Controlled Item 

Transaction). See ADC 283. 

SE Serial Number 

DLMS Notes: 1. Use to identify the serial number when 

UII is not required. If UII is required in addition to the 

serial number, enter serial number in REF04. 

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

3. Supports Navy BG1/BG2 data requirement. See 

introductory DLMS note 4.e. When used with Navy 

BG1/BG2 transactions, this qualifier implies that the 

transaction is a BG1 (Serial Number or Lot and Serial 

Number Controlled Item Transaction). See ADC 283. 

U3 Unique Supplier Identification Number (USIN) 

DLMS Notes: 1. Use to identify the UII Place UII value 

in REF03. The UII may not exceed 50 characters in 

accordance with IUID Policy. An ANSI data maintenance 

was approved in version 5020. The approved code/name 

is “UII-Department of Defense Unique Item Identifier”. 

2. Authorized DLMS migration enhancement. See DLMS 

introductory note 4f. 

3. In a mixed DLSS/DLMS environment, UII is not used 

in Navy BG1/BG2 transactions. Only authorized values 

for Navy BG1/BG2 are BT and SE. 

To provide the 

structure necessary 

to include 

UID/UIT 

information, 

consistent with 

other DLMS 846 

transactions (DS 

846A, 846F, and 

846I). 

Supports stated 

Army/Navy 

requirements for 

BG1/BG2 data. 

No update 

required 

12. 2/REF02/390 Open REF02 with DLMS note:

DLMS Note: For use with REF01 codes BT 

and SE. 

To provide the 

structure necessary 

to include 

UID/UIT 

information. 

Update 

required
7 of 11 

ADC 283 

Attachment 

Item 

# 

Location Revision to 

846R, Location Reconciliation Request 

Reason Federal 

IC 

Impact 

13. 2/REF03/390 Open REF03 with DLMS note:

DLMS Note: Use to indicate UII value when 

REF01=U3. 

To provide the 

structure necessary 

to include 

UID/UIT 

information. 

Update 

required

14. 2/REF04/C040/

390 

Open REF04 with DLMS notes: 

Ref: REF04 

ID: C040 

Ref: C0401 

128 Reference Identification Qualifier 

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following codes 

are authorized. 

BT Batch Number 

DLMS Note 1: Use to identify the manufacturer's 

batch/lot number or other number identifying the 

production run, when UII or serial number is entered in 

REF01, and batch/lot is the only other identifying number 

in 2/REF/390. The batch/lot number may not exceed 20 

characters in accordance with IUID policy. 

2. Supports Navy DI Code BG1/BG2 data requirement. 

See introductory DLMS note 4.e. When used with Navy 

BG1/BG2 transactions, this qualifier implies that the 

transaction is a BG1 (Serial Number or Lot and Serial 

Number Controlled Item Transaction). See ADC 283. 

SE Serial Number 

DLMS Note: 1. Use to identify the serial number when 

UII is entered in REF01 and serial number is also used.

2. Not used in Navy BG1/BG2 transactions. For 

BG1/BG2 requirement, SE qualifier is only used in the 

REF01 segment. 

Ref: C0402 

127 Reference Identification 

To provide the 

structure necessary 

to include UID 

information, 

consistent with 

other DLMS 846 

transactions with 

UID/UIT data. 

Supports stated 

Army/Navy 

requirements for 

BG1/BG2 data. 

Update 

required. 
8 of 11 

ADC 283 

Attachment 

Item 

# 

Location Revision to 

846R, Location Reconciliation Request 

Reason Federal 

IC 

Impact 

Ref: C0403 

ID: 128 Reference Identification Qualifier 

Federal Note: Use any code.

DLMS Note: For DLMS use, only the following codes 

are authorized. 

BT Batch Number 

DLMS Note: 1. Use to identify the manufacturer's 

batch/lot number or other number identifying the 

production run when UII is entered in REF01 and serial 

number is entered in REF04-01. The batch/lot number 

may not exceed 20 characters in accordance with IUID 

policy. 

2. Not used with Navy DI Code BG1/BG2 transactions. 

For BG1/BG2 requirement, BT qualifier is only used in 

the REF01 and REF04/C00401 segments. 

0N Attached To 

DLMS Note: Army and Navy use when REF01 = BT to 

identify the Lot Size for the lot number identified in 

REF02. Supports Navy DI Code BG1/BG2, rp 25-29. 

See introductory DLMS note 4.e. See ADC 283. 

Ref: C0404 

127 Reference Identification 

To provide the 

structure necessary 

to include UID 

information, 

consistent with 

other DLMS 846 

transactions with 

UID/UIT data. 

By use of qualifier 

‘0N’, REF segment 

is used to convey a 

quantity for a given 

lot number since no 

quantity segment is 

available in the 

transaction 

structure UID loop 

(LOOP ID -REF) 

for use with lot 

number. There 

could be multiple 

lot numbers 

associated with a 

given location 

reconciliation 

request transaction. 

Total quantity is 

conveyed at 

2/QTY02/320. 

15. 2/DTM/400 Open the 2/DTM/400 segment for optional use with 

DLMS segment level note:

DLMS Note: Use multiple repetitions as needed to 

identify dates related to data represented 2/REF/390. 

To provide the 

structure necessary 

to include 

UID/UIT 

information. 

Update 

Required.

16. 2/DTM01/400 Open DTM01 and add Federal and DLMS Notes:

Federal Note: Use any code

DLMS Note: For DLMS use, only the following codes 

are authorized. 

To add Standard 

notes. 

Update 

Required. 
9 of 11 

ADC 283 

Attachment 

Item 

# 

Location Revision to 

846R, Location Reconciliation Request 

Reason Federal 

IC 

Impact 

17. 2/DTM01/400 Add date qualifiers 036 and 302 to DTM01 with DLMS 

notes: 

036 Expiration Date 

DLMS Note: Use to identify the expiration date of the 

reported item. DLMS Component unique enhancement 

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

note 4.e. Authorized for Army and Navy use. See ADC 

 283. 

302 Maintenance 

DLMS Note: Use to identify the maintenance due date 

(the date that maintenance is due on the item). DLMS 

Component unique enhancement (DI Code BG1/BG2, rp 

9-11). See introductory note 4.e. Authorized for Army 

and navy use. See ADC 283. 

To add dates 

associated with 

Navy BG1/BG2 

serial/lot number 

reporting 

transaction. 

No update 

required. 

18. 2/DTM02/400 Open DTM02. To provide the 

structure necessary 

to include date 

value. 

Update 

required 

19. 2/N1/410 Open the 2/N1/410 segment for optional use with DLMS 

note: 

DLMS Note: Use to identify the manufacturer of the 

UIT item. 

To provide the 

structure necessary 

to include 

UID/UIT 

information. 

Update 

required 

20. 2/N101/410 Open N101 for optional use with Federal and DLMS 

note: 

Federal Note: Use any code 

DLMS Note: For DLMS use, only the following codes 

are authorized.

To add standard 

notes. 

Update 

required

21. 2/N101/410 Add code MF:

MF Manufacturer of Goods 

To include 

capability to 

identify 

manufacturer of 

goods consistent 

with other DS with 

UID/UIT data. 

No update 

required. 

22. 2/N103/410 Open N103 with DLMS and Federal notes and add qualifier 

33-CAGE:

Federal Note: Use any code 

DLMS Note: For DLMS use, only the following codes 

are authorized.

33 Commercial and Government Entity (CAGE) 

To provide for 

CAGE code. 

Update 

required

23. 2/N104/410 Open N104.

 

To provide the 

structure necessary 

to enter a CAGE 

code value. 

Update 

required 
10 of 11 

ADC 283 

Attachment 

Item 

# 

Location Revision to 

846R, Location Reconciliation Request 

Reason Federal 

IC 

Impact 

24. 2/LE/440 Open the 2/LE/440 segment for optional use with Federal 

note: 

Federal Notes: Use in each 2/QTY/320 loop to terminate 

any 2/REF/390 loop iterations. 

To provide the 

structure necessary 

to include 

UID/UIT 

information. 

Update 

required

25. 2/LE01/440 Open LE01 with Federal note: 

Federal Note: Repeat the content of 2/LS/380

To provide the 

structure necessary 

to include 

UID/UIT 

information. 

Update 

required 

e. Alternatives: None known. 

5. REASON FOR CHANGE: Existing DS 846R does 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 with DS 846R. 

6. DOD COMPONENT RESPONSES TO PDC 306: 

COMPONENT RESPONSE DLMSO RESPONSE 

Army Concur Noted. 

Navy Concur Noted. 

DLA EBS: No impact. 

DSS: 

DDC M concurs.

Please review and note 

comments from DDC 

Material Accountability 

(MA). Validation of serial 

numbers during Location 

Reconciliation will be a 

systemic process. Our only 

concern is the rejects that 

occur as a result. The rejects 

will need to be worked. 

Serial number validations 

will likely become a new 

process at the Distribution 

Centers, most likely in the 

PPP&M arena. 

The PDC 306 BG1/BG2 data requirement was only used 

intra Navy or with an existing interface between Army 

and NOLSC OIS, and as such, DLA DDC/DSS would 

not be affected. As the PDC is written there is no DLA 

DSS interface. 

IF DLA is proposing that the serial/lot number and Item 

Unique Identification (IUID) data be available for use as 

part of standard location reconciliation process, thereby 

expanding use beyond the current Army/NOLSC OIS 

interface that exists under MILS today, a separate PDC 

must be submitted identifying this requirement for 

staffing with the DOD Components. PDC 306 had a 

limited scope/applicability to an Army/Navy interface. 

USTRANSCOM Abstains Noted. 
11 of 11 

ADC 283 

Attachment 

7. ADVANTAGES AND DISADVANTAGES: 

 

a. Advantages: Incorporating the BG1/BG2 data in DS 846R, and providing DAASC 

mapping guidance for use in converting to DLSS location reconciliation request 

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. 

b. Disadvantages: None known.

8. IMPACT: 

a. Modify DoD 4000.25-M, DS 846R and DAASC conversion maps. 

b. Army LMP and Navy ERP to accommodate the serial/lot number data in DLMS 

846R as addressed by this change. 

c. May impact other modernized systems if DLMS enhancements are identified as 

placeholders for future use as requirements are identified. 

Enclosures
1 of 2 

ADC 283 

Enclosure 1 

ENCLOSURE 1 to ADC 283 

BG1/BG2 Mapping to DLMS 846R 

1. BG1/BG2 Mapping for 846R: 

BG1/BG2 

Field Name 

Record 

Positions 

846R Mapping 846R 

Position/Loop 

Header Transaction 

(DZH) Positions 

Document 

Identifier Code 

1 – 3 LQ01 = 0 

LQ02 = BG1 or BG2 

376/LM N/A 

Routing 

Identifier 

4 – 6 Perpetuate from N101 = KA 

N103 = M4 

N104 = RP 4 – 6 

N106 = TO 

80/N1 4 - 6 

Management 

Code 

7 If DTM01=302 RP 7=P 

If DTM01=036, RP 7=E 

400/REF N/A 

Blank 8 

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 = 36 

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

represents January – September, O – October, N – 

November, D – December) 

400/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 

376/LM 70 

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

LQ01=0 

OR 

If BIA02 = LC, RP 23 – 24 = ZH 

150/LM Positions 2 – 3 of 1 – 3 

Quantity 25 – 29 For BG1, DAAASC enter default value of 1 

For BG2: 

REF04/C04005 = 0N 

REF04/C04006 = 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 

390/REF N/A 

Transaction 

Reference 

Number 

30 – 36 Perpetuate from 

REF01=TN 

REF02=RP 30-36 

140/REF 60 - 66 

Blank 44 

Serial or Lot 

Number 

45 – 65 If REF01 = BT and REF04/C0401 = SE, 

RP 45 – 65 = (REF02) , “.”, (REF04/C0402) 

Else 

If REF01 = BT or SE 

RP 45 – 65 = REF02 

390/REF N/A 
2 of 2 

ADC 283 

Enclosure 1 

BG1/BG2 

Field Name 

Record 

Positions 

846R Mapping 846R 

Position/Loop 

Header Transaction 

(DZH) Positions 

Consignee 66 – 71 NA NA N/A 

Routing 

Identifier 

72 – 74 Perpetuate from 

N101=SB 

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 

376/LM 71 

Transaction 

Date 

77 – 79 DTM01=600 

DTM02=CCYYMMDD 

100/LIN NA 

Blank 80 
1 of 2 

ADC 283 

Enclosure 2 

NAVSUP P-724 BG1/BG2 Format 

ENCLOSURE 2 TO ADC 283 

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 283 

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