IN REPLY 

REFER TO DLMSO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR. VIRGINIA 22060-622 1 

MEMORANDUM FOR: SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS AND 

INTEGRATED MATERIEL MANAGEMENT COMMlTTEE CHAIR 

SUBJECT: Approved DLMS Change 11 8, Revision to DLMS Supplement 536L Logistics 

Reassignment Management Data (Staffed by PDC 1 19) 

This memorandum forwards an approved change to DoD 4000.25-M, Defense Logistics 

Management System (DLMS). DAASC and DLA have authorization to employ these procedures 

immediately under Business Systems Modernization (BSM); however, configuration management1 

version control procedures must be observed. This change incorporates desired functionality in the 

Logistics Reassignment Management Data transaction. The Defense Logistics Management 

Standards Office (DLMSO) will coordinate necessary revisions to the governing Federal 

Implementation Convention with DoD Electronic Data Interchange Standards Management 

Committee (EDISMC) and the Federal ED1 Standards Management Coordinating Committee 

(FESMCC) for Federal approval. 

Addressees may direct questions to the DLMSO point of contact, Ms. Mary Jane Johnson, 

703-767-0677, DSN 427-0677, or e-mail: Mary.Jane.Johnson@dla.mil. Others must contact their 

Component designated representative. 

Po Defense Logi u s Management 

Attachment 

cc: 

ADUSD(L)SCI 

LMI 
1 ADC 118

 Attachment

Approved DLMS Change 118

Revision to DLMS Supplement 536L Logistics Reassignment Management Data

1. ORIGINATOR:

a. Service/Agency: Air Force and Defense Logistics Agency

(1) Air Force Point of Contact: Bobbie Ziolek, HQ AFMC/LGIA

(2) DLA Point of Contact: Lora Conrad

b. Sponsor: Defense Logistics Management Standards Office (DLMSO), Mary Jane Johnson, (703) 

767-0677 (DSN 427), email: Mary.Jane.Johnson@dla.mil. 

2. FUNCTIONAL AREA: Supply

3. REQUESTED CHANGE:

a. Title: Revision to DLMS Supplement 536L Logistics Reassignment Management Data. 

b. Description of Change: 

(1) This change modifies the DLMS Supplement for the 536L Logistics Reassignment Management Data 

to incorporate data elements necessary to carry data contained in MILSTRAP Document Identifier (DI) 

Code DLT, LR Backorder and Demand Data transaction, Record 4. This change accommodates in DLMS, 

the data approved by Approved DLMS Change (ADC) 115 for MILSTRAP DLT Record 4, and supports 

the Defense Logistics Agency, Business Systems Modernization (BSM) SAP use of the DLMS 536L to pass 

LR backorder and demand data.

(2) This change includes modifications to 2/CS01/030 and 2/LIN04/020 necessary to facilitate DAASC 

DLSS to DLMS conversion while in a mixed DLSS/ DLMS environment.

c. Procedures: Make the following revisions to the 536L Logistics Reassignment Management Data, 

DLMS Supplement and revise the Federal IC as noted. A document showing data mapping from DI Code 

DLT Record 4 to DLMS 536L is at the enclosure. 

# Location Revision to DLMS Supplement Reason Federal IC impact
ADC 118

Attachment

2

# Location Revision to DLMS Supplement Reason Federal IC impact

1. 2/LIN04/020 Add code and code note to LIN04

Add code ZZ – Mutually Defined 

DLMS Note: For temporary use during DLSS 

to DLMS conversion, to facilitate conversion 

of MILSTRAP DLX (record 1, record 

positions 33-45) data to DLMS 536L. Qualifier 

‘ZZ’ should not be used in a DLMS to DLMS 

environment or when generating a 536L out of 

a Component system. Use of qualifier ‘ZZ’ 

will be eliminated in a pure DLMS 

environment.” 

To accommodate 

DLSS to DLMS 

conversion.

Revision required.

2. 2/CS01/030 Change Data Element 367 from “Must Use” to 

“Optional”

1. Must use with the 2/HL/010 contract loop.

2. CS01 is optional to accommodate DLSS to 

DLMS conversion. The 536L is intended to 

accommodate all MILSTRAP DI Codes DLS 

through DLX transaction data for a given NSN 

and review period, in a single 536L transaction.

CS01 would be a “must use” under this concept. 

However during DLSS to DLMS conversion some 

systems may be converting each individual 

MILSTRAP transaction to individual 536L 

transactions, in which case CS01 may not always 

be required.

To accommodate 

DLSS to DLMS 

conversion.

Revision required

3. 2/QTY01/040 Add Federal Note: Use any code.

Add DLMS Note: For DLMS, only the 

following codes are authorized

DLMS code list to be 

removed from Federal 

IC.

Revision required.

4. 2/QTY01/40 Add code and code note to QTY01

Add code 69 -Incremental Order Quantity and 

DLMS Notes: Use in the 2/HL/010 quantity 

loop to indicate Economic Order Quantity.

An ANSI data maintenance action will be 

taken to obtain a more appropriate code for 

use in a future version/release.

Indicates Economic 

Order Quantity.

No impact
ADC 118

Attachment

3

# Location Revision to DLMS Supplement Reason Federal IC impact

5. 2/QTY01/40 Add code and code note to QTY01

Add code PP - Purchase of Product and 

DLMS Note: Use in the 2/HL/010 quantity 

loop to indicate Procurement Cycle Quantity.

An ANSI data maintenance action will be 

taken to obtain a more appropriate code for 

use in a future version/release.

Indicates Procurement 

Cycle Quantity.

No impact

6. 2/QTY01/40 Add code and code note to QTY01

Add code 3U -Total Transactions and DLMS 

Note: Use in the 2/HL/010 quantity loop to 

indicate Total Quantity of All Buys for Price 

Break Buy; Life of Type Buy; and Minimum 

Buy Quantities.

An ANSI data maintenance action will be 

taken to obtain a more appropriate code for 

use in a future version/release.

Indicates Total 

Quantity of All Buys 

for Price Break Buy; 

Life of Type Buy; and 

Minimum Buy 

Quantities.

No impact.

7. 2/QTY01/40 Add code and code note to QTY01

Add code RY - Requirement Quantity and 

DLMS Note: Use in the 2/HL/010 quantity 

loop to indicate Funded Planned Requirement 

Quantity not included in reorder point 

quantity computation.

An ANSI data maintenance action will be 

taken to obtain a more appropriate code for 

use in a future version/release.

Indicates Funded 

Planned Requirement 

Quantity.

No impact.

8. 2/QTY01/40 Add code and code note to QTY01

Add code 1Q -Total Resources - Quantity and 

DLMS Note: Use in the 2/HL/010 quantity 

loop to indicate total quantity of all buys for 

numeric stockage objective quantity and 

insurance quantity, only is not included in 

reorder point quantity computation.

An ANSI data maintenance action will be 

taken to obtain a more appropriate code for 

use in a future version/release.

Indicates Total 

Quantity of all Buys.

No impact.

9. 2/N9/60 Add DLMS Note 5: 

Use in 2/HL/010 quantity loop to identify 

demand and backorder data for item of 

supply. 

To indicate that 

segment may be used 

in 2/HL/010 quantity 

loop.

No impact.
ADC 118

Attachment

4

# Location Revision to DLMS Supplement Reason Federal IC impact

10. 2/N901/60 Add Federal Note: Use any code.

Add DLMS Note: For DLMS, only the 

following codes are authorized

DLMS code list to be 

removed from Federal 

IC.

Revision required.

11. 2/N901/60 Add code and code note to N901

Add code M2 - Major Force Program and 

DLMS Note: Use in 2/HL/010 quantity loop to 

indicate if Demand Quantity is Program 

Driven.

An ANSI data maintenance action will be 

taken to obtain a more appropriate code for 

use in a future version/release.

Indicates If Demand 

Quantity is Program 

Driven.

No impact.

12. 2/N901/60 Add code and code note to N901

Add code S2 - Data Source and DLMS Note: 

Use in 2/HL/010 quantity loop to indicate 

Diminishing Manufacturing Source Item.

An ANSI data maintenance action will be 

taken to obtain a more appropriate code for 

use in a future version/release.

Indicates Diminishing 

Manufacturing Source 

Item.

No impact.

13. 2/N901/60 Add code and code note to N901

Add code 1R - Storage Information Code and 

DLMS Note: Use in 2/HL/010 quantity loop to 

indicate Provisioning Item.

An ANSI data maintenance action will be 

taken to obtain a more appropriate code for 

use in a future version/release.

Indicates Provisioning 

Item.

No impact.

14. 2/N901/60 Add code and code note to N901

Add code 8X - Transaction or Category Type 

and DLMS Note: Use in 2/HL/010 quantity 

loop to indicate Life of Type Buy.

An ANSI data maintenance action will be 

taken to obtain a more appropriate code for 

use in a future version/release.

Indicates Life of Type 

Buy.

No impact.

15. 2/N902/60 Add data element note to N902

DLMS Note: For Codes 1R, 8X, M2 and S2 

place “Y” or “N” in this field as appropriate

Adds clarity for 

specific codes.

No impact.
ADC 118

Attachment

5

# Location Revision to DLMS Supplement Reason Federal IC impact

16. 2/G6201/80 Add Federal Note: Use any code.

Add DLMS Note: For DLMS, only the 

following codes are authorized

DLMS code list to be 

removed from Federal 

IC.

Revision required.

17. 2/G6201/80 Add code to G6201

Add code: BD - Required By.

Add DLMS note: Indicates Date item is 

required.

Indicates Date Item 

Required.

No impact.

18. 2/LQ01/180 Add Federal Note: Use any code.

Add DLMS Note: For DLMS, only the 

following codes are authorized

DLMS code list to be 

removed from Federal 

IC.

Revision required.

19. 2/LQ01/180 Add code GQ - Group Qualifier Code

Federal Note: Use to identify the Materiel 

Management Aggregation Code (MMAC).

DLMS Note: Use to identify the MMAC for 

NSNs to be managed by a specific manager 

(i.e., system, program, aggregation, selected 

FSC, technology group). This is an Air Forceunique data element, meaningful to the Air 

Force only. Non-Air Force Components 

perpetuate without action. An ANSI data 

maintenance request has been prepared to 

request a new data element 1270 code 

qualifier assignment for the MAAC. The code

source is identified as the Air Force Manual 

(AFMAN) 23-110, Volume 1.

See ADC 77 No impact.

20. 2/N101/190 Add Federal Note: Use any code.

Add DLMS Note: For DLMS, only the 

following codes are authorized

DLMS code list to be 

removed from Federal 

IC.

Revision required.

4. REASON FOR CHANGE: This change supports component-level DLMS implementation. These 

data elements were approved for use in MILSTRAP by ADC 115 and also identified during a review of 

BSM processing needs and identified by DLA and DAASC as needed for DLSS to DLMS conversion. 

5. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Incorporates MILSTRAP DI Code DLT, record 4 data into DLMS and supports 

component-level DLMS implementation. 

b. Disadvantages: None identified.

6. IMPACT:
ADC 118

Attachment

6

a. Data Content/Procedures: DAAS maps and Component systems must incorporate additional 

capability.

b. Publication(s): DLMS; DLMS Supplement and corresponding Federal IC. Revisions to Federal 

IC will be submitted to the EDISMC/Logistics Functional Work Group for coordination/approval

c. ANSI ASC X12. Data Maintenance (DM) requests will be submitted ANSI to obtain more 

accurate ANSI ASC X12 qualifiers for the following data. In response to PDC 119, and now to ADC 

118, request the IMMC chair provide definitions or explanations for the following data currently 

published in DoD 4140.26-M. Request information be provided immediately, but no later than 14 

days from the date of this ADC. DLMSO will include the information in the DM rationale/ 

justification:

DOD 4140.26-M DATA DEFINITION OR EXPLANATION from IMMC Chair

(DLMS 536L DM Segment:)

Diminishing Manufacturing Source Item

Provisioning Item

Demand Quantity is Program Driven

Life of Type buy

(DLMS 536L QTY Segment:)

Numeric Stockage Objective Quantity

Insurance Quantity

Price Break Buy Quantity

Life of Type Buy Quantity

Minimum Buy Quantity

Funded Planned Requirement Quantity

Procurement Cycle Quantity

Economic Order Quantity

Enclosure