IN REPLY 

REFER TO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

March 04,2013 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Approved Defense Logistics Management System (DLMS) Change (ADC) 1040, 

Migrate Inter-Service Ammunition Serial Number and Lot Number Transactions 

(NA VSUP P-724 Document Identifier Code (DIC) BG 1/BG2) to DLMS 945A 

Materiel Release Advice 

The attached approved change to Defense Logistics Manual (DLM) 4000.25, Defense 

Logistics Management System (DLMS) is approved for implementation May 2013. The updated 

DLMS Supplements will be posted to the DLA Logistics Management Standards Web at 

www.dla.mil/j-6/dlmso/elibrary/TransFom1ats/formats.asp within 10 days from the above date. 

Addressees may direct questions to Ms. Ellen Hilert, DOD MILSTRIP Administrator, 

703-767-0676 or DSN 427-0676, e-mail: ellen.hilert@dla.mil or Ms. Heidi Daverede, DOD 

MILSTRIP Alternate, 703-767-5111; DSN 427-5111, e-mail: heidi.daverede@dla.mil. Others 

may direct questions to their Service or Agency designated Supply PRC representative available 

at: www.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp. 

Attachment 

As stated 

cc: 

ODASD(SCI) 

DONALD C. PIPP 

Director 

DLA Logistics Management 

Standards Office 

Federal Recycling Program G Printed on Recycled Paper 
Attachment, ADC 1040

Page 1

Attachment to ADC 1040

Migrate Inter-Service Ammunition Serial Number and Lot Number Transactions 

(NAVSUP P-724 DIC BG1/BG2) to DLMS 945A Materiel Release Advice

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: PEO EIS Army Logistics Modernization Program (LMP), (856) 988-

4878

b.Functional POC: 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:

a. Primary/Secondary Functional Area: Supply/Logistics

b. Primary/Secondary Functional Process: Order Fulfillment/Requisition Processing 

3. REFERENCES:

 a. DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures (MILSTRIP) 

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

Ashore

c. 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, dated January 7, 2008

d. ADC 283, Migrate Serial Number and Lot Number Transactions (NAVSUP P-724 

BG1/BG2) to DLMS 846R Location Reconciliation Request, dated May 12, 2008

e. ADC 445, Adopt Navy Serial Number and Lot Number Transactions (NAVSUP P-724 

BG1/BG2) to Air Force and Marine Corps Ammunition System Use for DLMS 527R Receipt, 

846R Location Reconciliation Request, 867I Issue, and 947I Inventory Adjustment, dated 

September 8, 2011

f. DLM 4000.25-2, Military Standard Transaction Reporting and Accounting Procedures 

(MILSTRAP)

4. APPROVED CHANGE: 

 a. Overview: This change updates the DLMS 945A, Materiel Release Advice, to 

incorporate data contained in Navy NAVSUP P-724 Serial Number and Lot Number Reports for 

Inter-Service Ammunition (Reference 3.b.). It requires DLA Transaction Services’ Defense 

Automatic Addressing System (DAAS) conversion mapping to move the data from the DLMS 
Attachment, ADC 1040

Page 2

format to the legacy format in support of legacy ammunition systems.

 b. Background: ADC 261 (Reference 3.c.) previously added Navy BG1/BG2 data to 

the DLMS 527R Receipt, 867I Issue, and 947I Inventory Adjustment. ADC 283 (Reference 

3.d.) added Navy Document Identifier Code (DIC) BG1/BG2 data to the DLMS 846R Location 

Reconciliation. Finally, ADC 455 (Reference 3.e.) extended the previous Navy BG1/BG2 data 

to the Air Force and Marine Corps.

 c. Intent of the transaction: Military Services require the capability to report interservice ammunition lot and serial number information related to the Materiel Release 

Confirmation (DLMS 945A/ DIC AR_) transactions and utilize the Navy DIC BG1/BG2 data to 

transmit this information. The USAF and USMC have agreed to use the NAVSUP P-724

BG1/BG2 format, which is given in Enclosure 1. 

Staffing Note: The ammunition lot number will be mapped to the DLMS Qualifier BT Batch 

Number which is defined as identifying the applicable manufacturer’s batch/lot number or other 

number identifying the production run.

 d. Scenario for which the transaction is used: When a materiel release confirmation 

from the Army to the Air Force, Marine Corps, or Navy for ammunition items that are serial 

and/or lot number managed, the serial number and/or lot number of the items are reported in 

separate Navy DIC BG1 or BG2 transactions.

 e. Procedures, transactions, data elements, processing details in use today: 

(1) Current DLA Transaction Services mappings do not include BG1/BG2 data in 

association with a materiel release confirmation. 

(2) The activities that are receiving materiel release confirmation transactions 

(without serial number/lot data content) are:

• Combat Ammunition System (CAS) (Ogden/Warner Robins Air Logistics 

Center – Routing Identifier Code (RIC) FG5, FGZ, FL5, FLZ)

• Ordnance Information System – Marine Corps (OIS-M) (Program 

Manager for Ammunition, Marine Corps Systems Command – RIC MHQ)

• Ordnance Information System OIS – Wholesale (OIS-W) (Naval 

Operational Logistics Support Center – RIC NCB)

 f. Approved procedures: The Army LMP will generate the materiel release 

confirmation containing the additional data content for serial number/lot reporting. DLA 

Transaction Services will convert the DLMS, as needed, to separate legacy transactions for the 

materiel release confirmation and the lot/serial number reporting transactions. The logic for the 

routing of these transactions will be based on the DLMS 945A RIC-To: (2/N1/80: N101=Z4, 

N103=M4, N104 = FG5, FL5, FGZ, FLZ, MHQ, NCB), N106=TO.
Attachment, ADC 1040

Page 3

g. DLMS Supplement revisions: Revise DLMS 945A Materiel Release as follows. 

# Location Revision to

945A, Materiel Release Advice

Reason

1. DLMS 

Introductory 

Notes

Add new DLMS Introductory Note 2 and renumber 

remaining notes:

DLMS Note:

2. This transaction also accommodates the functionality 

for serial/lot number reporting transactions (based on nonDLSS Document Identifier Code (DIC) BG1/BG2 

published by NAVSUP P-724).

To identify additional 

transaction functionality 

accommodated in 

DLMS Supplement.

2. DLMS 

Introductory 

Notes

Add paragraph 4f. to existing DLMS Introductory Note:

f. Data required to accommodate a Component-unique 

transaction requirement. Data does not apply to DLSS 

transactions.

To indicate inclusion of

component unique 

transactions.

3. DLMS 

Introductory 

Notes

Add PDC 1040 to DLMS Introductory note 6:

- ADC 1040, Migrate Inter-Service Ammunition Serial 

Number and Lot Number Transactions (NAVSUP P- 724 

DIC BG1/BG2) to DLMS 945A, Materiel Release Advice

To identify DLMS 

changes included in the 

DLMS Supplement.

4. 2/LQ01/100 Revise DLMS note 1 for Qualifier 0 and replace existing 

note 2 with new note 2:

0 Document Identification Code

DLMS Note:

1. The DLSS DI Code DIC is retained in the DLMS to 

facilitate transaction conversion in a mixed DLSS/DLMS 

environment. Continued support of the DI Code DIC in a 

full DLMS environment will be assessed at a future date.

2. In a mixed legacy-DLMS environment, for the interservice ammunition interfaces, when including BG1/BG2 

data, Army must use 2 iterations of LQ to provide DIC AR_ 

as well as either DIC BG1 or BG2 as applicable, to alert 

DAAS of the BG1/ BG2 requirement for inter-service 

ammunition transactions. See ADC 1040.

To identify BG1/BG2 

data is included in 

transaction in a mixed 

environment. This will 

assist with DAAS 

mapping from Army 

LMP generated 945A to 

DLSS AR0, ARA and 

ARB with inter-Service 

ammunition BG1/BG2 

transactions, for trading 

partner operating in 

DLSS.

Also editorial 

corrections to remove 

note about streamlining 

and ensure consistent 

use of the abbreviation 

“DIC” for Document 

Identification Code.
Attachment, ADC 1040

Page 4

# Location Revision to

945A, Materiel Release Advice

Reason

5. 2/LX/110 Add new DLMS Note 2, renumber remaining notes:

2. Use for serial/lot number reporting of ammunition. 

Authorized DLMS enhancement for inter-service 

ammunition use. See DLMS introductory note 4f. See 

ADC 1040.

Identifies authorized 

use.

6. 2/N907/120

2/N907-

01/120

Open N907 for use. 

Add the new Qualifier 0N and DLMS notes:

0N Attached To

DLMS Note: 

1. Use with N901=BT (Batch Number) for Inter-Service 

Ammunition to identify the Lot Size for the lot number 

identified in N902. Authorized DLMS enhancement for 

inter-service ammunition use. 

2. DLMS Component unique enhancement (DIC

BG1/BG2, rp 25-29). See introductory DLMS note 4f. See 

ADC 1040.

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-0312) for use with 

lot number. There could 

be multiple lot numbers 

associated with a given 

materiel release 

transaction. Total 

materiel release quantity 

is conveyed at 

2/QTY02/55.

7. 2/G62/130 Move Federal Note to DLMS Note level for the segment and 

delete existing DLMS Note at segment level.

DLMS Note:

Use to identify dates associated with the UIT item.

Administrative 

correction.
Attachment, ADC 1040

Page 5

# Location Revision to

945A, Materiel Release Advice

Reason

8. 2/G6201/130 Revise notes for existing Qualifiers BK and BL and add new 

Qualifier 36 and BX with DLMS note:

36 Expiration Date

DLMS Note: 

1. Use for Inter-Service Ammunition to identify the 

expiration date of the reported item or batch/lot. 

Authorized DLMS enhancement for inter-service 

ammunition

2. DLMS Component unique enhancement (DIC 

BG1/BG2, rp 9-11). See introductory DLMS note 3f. See 

ADC 1040.

BK Warranty Expiration

DLMS Note:

1. Use to indicate the date when the materiel warranty 

expires.

2. DLMS enhancement; See introductory DLMS note 3a.

BL Manufacture

DLMS Note:

1. Use to identify the date of manufacture of the materiel 

identified.

2. DLMS enhancement; See introductory DLMS note 3a.

BX Action

DLMS Note: 

1. Use for Inter-Service Ammunition to identify the 

maintenance due date (the date that maintenance is due on 

the item). Authorized DLMS enhancement for interservice ammunition. 

2. DLMS Component unique enhancement (DIC 

BG1/BG2, rp 9-11). See introductory DLMS note 3f. See 

ADC 1040.

Adds date functionality

associated with interservice ammunition 

BG1/BG2 serial/lot 

number reporting 

transaction.

Administrative updates 

to identify enhancement 

notes with existing 

qualifiers. Warranty 

Expiration Date and 

Manufacture Date are 

unrelated to the 

ammunition 

requirement.

h. Approved transaction flow: No new transactions are required, with the exception of 

the addition of the BG1/BG2 trailer transactions to accompany the 945A Materiel Release 

Confirmation transactions.
Attachment, ADC 1040

Page 6

i. Alternatives: Systems migrating to DLMS, or already processing other transactions in 

DLMS would be required to continue to follow the limitations and processes of the legacy DLSS 

processes.

5. REASON FOR CHANGE: Documents and incorporates DLSS and DLMS requirements 

to support the ammunition processing between the Army and Air Force, Marine Corps and Navy; 

and to facilitate ammunition accountability.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Incorporating the BG1/BG2 data into the DLMS 945A, and providing 

DAAS mapping guidance for use in converting to DLSS location reconciliation request 

transactions, with supporting inter-service ammunition BG1/BG2 serial/lot number reporting 

transactions, is in keeping with the intent of utilizing the DLMS format and DLA Transaction 

Service’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 Air Force, Marine Corps, and Navy ammunition trading 

partners operating in DLSS, after Army LMP has implemented DLMS.

 b. Disadvantages: None known.

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

DEVELOPMENT: Trading partner systems are currently DLSS compliant for the affected 

transactions, and will require translation by DLA Transaction Services. Upon conversion to 

DLMS, the receiving systems will no longer require DLA Transaction Services translation 

performed.

8. NOTE ANY REGULATIONS OR GUIDANCE: None identified.

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Implementation is

requested by May 2013 to ensure ammunition inventory accountability is maintained through the 

Joint Services.

10. IMPACT:

a. New DLMS Data Elements: See Reference 3.c. for the detailed descriptions of the 

data elements. No additional data elements are required. 

b. Changes to DLMS Data Elements: None.

c. Integrated Data Environment (IDE)/Global Transportation Network (GTN) 

Convergence (IGC). Expanded correlation of the DLMS 945A to the BG1/BG2. No special 

processing applicable.

d. Automated Information Systems (AIS). DLMS compliant initiating systems will

incorporate release confirmation data and BG1/BG2 data, as applicable, into a single 
Attachment, ADC 1040

Page 7

transmission. Sample formats for batch number and lot size (with and without integrated item 

tracking) are shown at Enclosure 2.

 e. DLA Transaction Services: Revise DAAS maps to accommodate converting from 

DLMS 945A, to DIC BG1/BG2 as follows. The format for the NAVSUP P-724 BG1/BG2 

transaction is provided at Enclosure 1 as background. Note that unlike the transactions 

addressed in previous similar DLMS changes, Routing Identifier Code (From), Condition Code 

and Ownership/Purpose Code are not in the header transaction, thus are required to be included 

in the N1 segment (position 40/0100) and LQ segment (position 100/0311), respectively, 

utilizing the existing qualifiers identified in the DLMS Supplement. DAAS will convert DLMS 

CCYYMMDD date formats to the required DIC BG2 format.

Field Name Legacy 

Format

Positions

Revision to 945A 

Mapping

945A 

Position/Loop

Header 

Transaction (AR_) 

Positions

Document 

Identifier 

Code

1 –3 LQ01 = 0 

LQ02 = BG1 or BG2

100/0311 N/A

Routing 

Identifier

4 –6 Perpetuate from 

N101 = Z4

N103 = M4

N104 = RP 4 – 6

N106 = TO

80/0310 4–6

Management 

Code

7 If G6201=BX, RP 7=P

If G6201=36, RP 7=E

Staffing Note: These 

codes are applicable to the 

legacy process and will 

not be perpetuated to the 

DLMS transaction. These 

codes are not reflected in

MILSTRAP.

N/A N/A

Blank 8
Attachment, ADC 1040

Page 8

Date to be 

posted

9 – 11 Maintenance (Inspection) 

Due Date

G6201 = BX

G6202 = RP 9-11 (convert 

to format MYY. Month 1 

– 9 represents January –

September, O – October, 

N – November, D –

December)

Expiration Date 

G6201 = 36

G6201 = RP 9-11 (convert 

to format MYY. Month 1 

– 9 represents January –

September, O – October, 

N – November, D –

December)

130/0312 N/A

NIIN 12 – 20 Derived from Positions 5-

13 of W1207=FS

020/0310 Positions 5 – 13 of 

8 – 22

Blank 21

Purpose 

Code

22 LQ01 = A1 or 99

LQ02= RP 22

100/0311 N/A

Action Code 23 – 24 Always 7Z
Attachment, ADC 1040

Page 9

Quantity 25 – 29 For BG1, DAAS enter 

default value of 1

For BG2:

If N907/C040-01 = 0N 

N907/C040-02 = 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

Staffing Note: Reversal 

capability will not be 

applicable to the BG2 

originated as a DLMS 

945A.

120/0312 N/A

Document 

Number

30 – 43 Perpetuate from

N901=TN

N902=RP 30-43

040/0310 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

120/0312 N/A

Consignee

(same as 

MRO ShipTo)

66 – 71 N101 = ST

N103=10

N104=RP 66 -71

80/0310 NA

Routing 

Identifier

72 – 74 N101 = SB

N103 = M4

N104 = RP 72-74

N106 = FR

040/0100 N/A

Blank 75
Attachment, ADC 1040

Page 10

Current 

Condition 

Code

76 LQ01 = 83

LQ02 = RP 76

100/0311 N/A

Transaction 

Date

77 – 79 G6201=BB 

G6202=CCYYMMDD

110/0100 NA

Blank 80
Enclosure 1, ADC 1040

Page 1

ENCLOSURE 1 TO ADC 1040

Excerpt from NAVSUP P-724 REV 12, CONVENTIONAL ORDNANCE 

STOCKPILE MANAGEMENT

VOLUME I ASHORE

SPLIT 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 the reported item. 

DUE OR CONTAINER 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.

22 PURPOSE CODE The current Purpose Code of the item being 

reported.

23-24 ACTION CODE Identifies the action taken on the reported item.
Enclosure 1, ADC 1040

Page 2

Card Entry Remarks

Column

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.

Staffing Note: Reversal capability will not be

applicable to the BG2 originated as a DLMS 945A.

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 

materiel.

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
ADC 1040, Enclosure 2

Page 1

Enclosure 2, Sample Mapping DLMS Materiel Release Advice (945A)

Staffing Note: This mapping solution is provided for illustration only. It is anticipated that the DLMS 945A will be migrated to a higher X12 standard if DOD supply policy requires the use of this transaction for the application of item unique identification (IUID) in logistics 

processes. This is due to the field length restriction of the reference segment location that would be used for mapping of the unique item identifier (UII).

Description Loop Header

(position)

Segment ID

(position)

Data

Value 1

Data

Value 2

Data

Value 3

4 5 6 Data

Value 7

Data 

Value 8

1. One lot, no serial 

numbers, no UIIs 

(one internal LMP

batch not mapped)

LS (105) -

Loop Header

LX (110) -

Assigned Number

00001

N9 (120) -

Reference Identification

BT LT001 0N 3

Lot Expiration Date G62 (130) -

Date / Time

36 20130915

LE (165) -

Loop Trailer

2. One lot, serial 

numbers, no UIIs

(one internal LMP 

batch not mapped)

LS (105) -

Loop Header

Item 1 LX (110) -

Assigned Number

00001

-Lot Number N9 (120) -

Reference Identification

BT LT001 0N 3

-Serial Number N9 (120) -

Reference Identification

SE SR001

-Item Expiration Date G62 (130) –

Date / Time

36 20130915

Item 2 LX (110) -

Assigned Number

00002

-Lot Number N9 (120) -

Reference Identification

BT LT001 0N 3

-Serial Number N9 (120) -

Reference Identification

SE SR002

-Item Expiration Date G62 (130) –

Date / Time

36 20130915

Item 3 LX (110) -

Assigned Number

00003
ADC 1040, Enclosure 2

Page 2

Description Loop Header

(position)

Segment ID

(position)

Data

Value 1

Data

Value 2

Data

Value 3

4 5 6 Data

Value 7

Data 

Value 8

-Lot Number N9 (120) -

Reference Identification

BT LT001 0N 3

-Serial Number N9 (120) -

Reference Identification

SE SR003

-Item Expiration Date G62 (130) –

Date / Time

36 20130915

LE (165) -

Loop Trailer

3 - One lot, serial 

numbers, UIIs (one 

internal LMP batch 

not mapped)

LS (105) -

Loop Header

Item 1 LX (110) –

Assigned Number

00001

-Lot Number N9 (120) -

Reference Identification

BT LT001 0N 3

-Serial Number N9 (120) -

Reference Identification

SE SR001

-UII N9 (120) –

Reference Identification

U3 UI001

-Item Expiration Date G62 (130) –

Date / Time

36 20130915

Item 2 LX (110) -

Assigned Number

00002

-Lot Number N9 (120) -

Reference Identification

BT LT001 0N 3

-Serial Number N9 (120) -

Reference Identification

SE SR002

-UII N9 (120) –

Reference Identification

U3 UI002

-Item Expiration Date G62 (130) –

Date / Time

36 20130915

Item 3 LX (110) -

Assigned Number

00003

-Lot Number N9 (120) -

Reference Identification

BT LT001 0N 3

-Serial Number N9 (120) -

Reference Identification

SE SR003

-UII N9 (120) –

Reference Identification

U3 UI003

-Item Expiration Date G62 ( 130) –

Date / Time

36 20130915
ADC 1040, Enclosure 2

Page 3

Description Loop Header

(position)

Segment ID

(position)

Data

Value 1

Data

Value 2

Data

Value 3

4 5 6 Data

Value 7

Data 

Value 8

LE (165) -

Loop Trailer

4. Two lot numbers, 

serial numbers, UIIs

LS (105) -

Loop Header

Item 1 LX (110) –

Assigned Number

00001

-Lot Number N9 (120) -

Reference Identification

BT LT001 0N 2

-Serial Number N9 (120) -

Reference Identification

SE SR001

-UII N9 (120) –

Reference Identification

U3 UI001

-Item Expiration Date G62 (130) –

Date / Time

36 20130915

Item 2 LX (110) -

Assigned Number

00002

-Lot Number N9 (120) -

Reference Identification

BT LT001 0N 2

-Serial Number N9 (120) -

Reference Identification

SE SR002

-UII N9 (120) –

Reference Identification

U3 UI002

-Item Expiration Date G62 (130) –

Date / Time

36 20130915

Item 3 LX (110) –

Assigned Number

00003

-Lot Number N9 (120) -

Reference Identification

BT LT002 0N 3

-Serial Number N9 (120) -

Reference Identification

SE SR003

-UII N9 (120) –

Reference Identification

U3 UI003

-Item Expiration Date G62 (130) –

Date / Time

36 20131015

Item 4 LX (110) -

Assigned Number

00004

-Lot Number N9 (120) -

Reference Identification

BT LT002 0N 3

-Serial Number N9 (120) -

Reference Identification

SE SR004

-UII N9 (120) - Reference 

Identification

U3 UI004
ADC 1040, Enclosure 2

Page 4

Description Loop Header

(position)

Segment ID

(position)

Data

Value 1

Data

Value 2

Data

Value 3

4 5 6 Data

Value 7

Data 

Value 8

-Item Expiration Date G62 (130) –

Date / Time

36 20131015

Item 5 LX (110) -

Assigned Number

00005

-Lot Number N9 (120) -

Reference Identification

BT LT002 0N 3

-Serial Number N9 (120) -

Reference Identification

SE SR005

-UII N9 (120) - Reference 

Identification

U3 UI005

-Item Expiration Date G62 (130) –

Date / Time

36 20131015

LE (165) -

Loop Trailer
ADC 1040, Enclosure 3

Page 1

Enclosure 3, Comment Resolution

Originator Response/Comment Disposition

1. DLA Concur. Noted.

2. DLA 

Transaction 

Services

1. Reference the BG1/BG2 mapping in the 

attachment, isn't the correct mapping for the 

NIIN (12-20) of the BG1/BG2 to W1207 vice 

W1217 ? W1207 is the primary materiel 

identification.

2. Request clarification regarding the 

"reversal" of the quantity functionality shown 

for the quantity mapping related to the BG2? 

Is that in play for the 945A or can we just do 

straight mapping of the quantity field from the 

945A to the BG2? 

1. Updated. Initial mapping was a 

typographic error; correct mapping 

is W1207.

2. By agreement with the Army, 

reversal capability will not be 

required at this time.

3. Army Concur. 

1. Since the LMP team is unsure of our 

reversal plans at this time, please go ahead 

with

the PDC without the reversal. If/when the 

time comes, we will re-visit another PDC.

2. LMP preference is for repeating the LX 

loop for lots that are split among multiple 

internal LMP batch numbers. The internal 

LMP batch number could be included or 

excluded from the transaction; however, it has 

no significance to the transaction recipient. 

Preference is to map the lot size as the 

quantity applicable to the internal batch; 

however, these values could be summed for 

all applicable internal batches so that only the 

total lot size is transmitted.

3. We believe the DLMS translation to MILS 

for the field Serial or Lot Number is 21 

characters long (including a decimal point) as 

defined in NAVSUP-724. However when 

LMP sends both a serial number and a lot 

number, that value can exceed 21 characters. 

We have heard that this is a pre-existing issue 

and, perhaps, is not something to be addressed 

here, but we wanted to point it out.

Noted.

1. ADC updated to reflect no 

reversal capability applies.

2. If the LMP internal batch has no 

meaning to the organization 

receiving the transaction it should 

not be mapped to the DLMS 

transaction. The lot size should not 

be broken down by internal batch 

number since the receiving 

organization would not recognize 

why multiple lot size values are 

reflected for the same lot number. 

LMP should only transmit the sum 

total for the lot size applicable to 

the lot being reported. When not 

using UII/serial number, there is no

need to use separate LX loops 

repeating the lot number and lot 

size with no other distinguishing 

information. This would be 

redundant and confusing. Per 

agreement with the Army LMP will 

not transmit separate LX loops 

carrying the same information.
ADC 1040, Enclosure 3

Page 2

Originator Response/Comment Disposition

4. This PDC 1040 applies primarily to 

CAS/OIS. For non-CAS/OIS transaction, 

what would happen if we sent lot / serial 

number data to DLA-TS?

3. The DLMS maximum field 

length for serial number is 30, and 

the batch/lot maximum size is 20. 

These are the field lengths defined 

by OSD (in association with the 

documentation of IUID policy -

field lengths for the various 

elements that are coded separately 

and encoded in the UII were 

coordinated, particularly with 

commercial partners, and accepted 

by the Services). There is not 

decimal point in either of these 

fields.

4. The DLMS Change spells out 

the legacy conversion requirement 

for the 80rp transaction support. 

However, if populated outside the 

scope of the ammo trading partners, 

DLA Transaction Services would 

just perpetuate the content as 

provided to DLMS compliant 

systems. The receiving system 

might not accept the data since 

there was no underlying 

requirement or prior coordination. 

For non-DLMS receiving systems 

outside the scope, the data would 

drop out during conversion to the 

legacy MILSTRIP transaction.

4. Marine Corps Concur. Noted.

5. Air Force Concur. Noted.

6. USTRANSCOM Concur.

It was determined the impact to 

USTRANSCOM systems will be minimal and 

we will be able to support the ADC upon 

release. 

Noted.

7. Navy Concur. Noted.
ADC 1040, Enclosure 3

Page 3

Originator Response/Comment Disposition

8. DLA Logistics 

Management 

Standards Office 

1. When multiple serial numbers are 

provided, the batch number is repeated with 

the serial number to keep those two elements 

linked in the MRC. Is the Army planning for 

LMP to repeat the lot size every time the 

batch number is provided, or alternatively,

provide it once and the receiving system will

interpret the lot size as applicable to the lot 

number without needing to see it with each 

occurrence?

2. Request confirmation that LMP will send 

the BG2 dates in CCYYMMDD format

(DAAS will convert to the BG2 format for 

MDD or month and year). The alternative is 

to open the date segment to accommodate 

other formats, but I didn't see that being done 

for the 527R which was updated for the BG2,

so assumed the standard DLMS date format 

would be adopted. This could be an issue 

since Expiration Dates may be in MMYY 

format and would require internal formatting 

to structure as CCYYMMDD.

3. The Army provided mapping for the 

BG1/BG2 to the DLMS 945A shows a row 

for the consignee DoDAAC in rp 66-71 

mapped to DLMS N101=CN. The mapping 

may be incorrect because the ship-to on the 

MRO is identified by ST (Ship To) and not 

the CN (Consignee). In the DLMS 945A, the 

CN is only used for a materiel release 

cancellation. Please confirm that the intent is 

to identify in the BG_ the same ship-to 

identified in the MRO.

1. Subsequent to discussion with 

Army LMP developers, it was 

agreed that the lot size will be 

repeated for each occurrence of the 

batch/lot number. Each item will 

require a separate LX loop to 

identify the lot number, serial 

number, UII. Mapping illustration 

was employed to illustrate potential 

mapping solutions and is provided 

as an enclosure due to the 

complexity of the approved 

solution if employed in conjunction 

with IUID.

2. Army response: “For both the 

AR and the BG2, we send out the 

Actual PGI date in Gregorian date 

format CCCCYYMM. In the 

945A, this does go out in the G62 

segment.”

The ADC has been updated to 

identify the date conversion 

requirement for DLA Transaction 

Services.

3. Army response: We agree that 

the value of the consignee on the 

BG1 is not different from the shipto on the MRO.

Mapping now updated.

_