DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 1 July 6, 2022

536 Logistics Reassignment

Functional Group=LR

Purpose: This Draft Standard for Trial Use contains the format and establishes the data contents of the Logistics Reassignment Transaction

Set (536) for use within the context of an Electronic Data Interchange (EDI) environment. This transaction set is used to provide information

necessary to transfer management responsibility between an old and new managing organization. This transaction set may be used to convey a

description and quantity of the transferred material, specific inventory locations, product quality information, technical data, open contract

information, demand data, procurement history, and other information necessary for the new managing organization to evaluate and meet the

material needs of customers.

DLMS note:

1. Organizations use this transaction set to provide general management information, backorder and demand data, onhand data, due-in

data, contract history data, and Product Quality Deficiency Report (PQDR) history data in conjunction with the transfer of inventory

management responsibility during logistics reassignment. Losing Inventory Managers (LIM) use a single occurrence of this transaction set to

transmit logistics reassignment management data to one or more Gaining Inventory Managers (GIM). Use one occurrence of this transaction

set to transmit a single or multiple transactions.

2. Reserved.

3. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table which can be found on the Defense Enterprise Data Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS.

4. This DLMS Implementation Convention (IC) contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system.

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or

understood by the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

c. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support transaction

conversion in a mixed DLSS/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components

may coordinate with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded files size above existing DLSS capability which may not be supported by the recipient's

automated processing system. Components must coordinate implementation with DEDSO prior to use.

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

5. This revision to the DLMS IC incorporates Proposed DLMS Change (PDC) and Approved DLMS Changes (ADCs) listed. PDCs and

ADCs are available from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/ 

 - ADC 77, Air Force Unique Management Coding for Materiel Management Aggregation Code (MMAC)

 - ADC 118, Revision to DLMS Supplement 536L Logistics Reassignment Management Data

 - ADC 185, Administrative revision to DLMS Supplement (DS) 536L, Logistics Reassignment Management Data

 - ADC 221A, Revised Procedures associated with the DLMS Enhancement for Communication of Unit Price

 - ADC 349, Revise DLMS Supplement (DS) 536L Logistics Reassignment Management Data Transaction to Establish a Moving Average

Cost (MAC) Field (Supply/Finance)

 - ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

 - Organizational Name and Other Non-Substantive (Administrative) Updates Completed on March 11, 2014

 - ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

 - ADC 1161A, Update Uniform Procurement Instrument Identifier (PIID) Numbering System in the Federal/DLMS Implementation

Conventions and DLMS Manuals (Supply/SDR/DoDAAD/Finance/Contract Administration)

- ADC 1161B, Modify DLMS 536L Logistics Reassignment Management Data to Identify the Procurement Instrument Identifier

(PIID)Associated with a Base Contract Number in Logistics Reassignment Contract History Data Transactions (Supply/Contract

Administration)

 - Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 21, 2016

 - ADC 1254, Remove Unit of Measure Code Validation from DLMS XML Schemas

 - Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

August 09, 2018

- ADC 1287, DLMS Implementation Convention (IC) Revisions for Data Element Mapping (Form Stock Number and Manufacturer's Part

Number), Removal of Plant Equipment Number, and Administrative Update

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards 

1. Organizations use this transaction set to provide general management information, backorder and demand data, onhand data, due-in

data, contract history data, and Product Quality Deficiency Report (PQDR) history data in conjunction with the transfer of inventory

management responsibility during logistics reassignment. Losing Inventory Managers (LIM) use a single occurrence of this transaction set to

transmit logistics reassignment management data to one or more Gaining Inventory Managers (GIM). Use one occurrence of this transaction

set to transmit a single or multiple transactions.

2. Reserved.

3. Users operating under the Defense Logistics Management Standards (DLMS) must reference the Unit of Issue and Purchase Unit

Conversion Table which can be found on the Defense Enterprise Data Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS.

4. This DLMS Implementation Convention (IC) contains:

a. Data associated with a DLMS enhancement which may not be received or understood by the recipient's automated processing system.

DLMS procedures may not have been developed. Components must coordinate requirements and business rules with DEDSO prior to use.

b. Data associated with an Approved Change which may not have an established implementation date. This data may not be received or

understood by the recipient's automated processing system. Components must coordinate implementation with DEDSO prior to use.

c. Defense Logistics Standard System (DLSS) data which must be retained in the DLMS for a transition period to support transaction

conversion in a mixed DLSS/DLMS environment. This data will be streamlined out once full DLMS implementation is reached. Components

may coordinate with DEDSO for early termination (or retention) of specific data requirements for users operating in a full DLMS environment.

d. Data elements which have an expanded files size above existing DLSS capability which may not be supported by the recipient's

automated processing system. Components must coordinate implementation with DEDSO prior to use.

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

5. This revision to the DLMS IC incorporates Proposed DLMS Change (PDC) and Approved DLMS Changes (ADCs) listed. PDCs and

ADCs are available from the DEDSO Web site: http://www.dla.mil/HQ/InformationOperations/DLMS/eLibrary/Changes/processchanges/ 

 - ADC 77, Air Force Unique Management Coding for Materiel Management Aggregation Code (MMAC)

 - ADC 118, Revision to DLMS Supplement 536L Logistics Reassignment Management Data

 - ADC 185, Administrative revision to DLMS Supplement (DS) 536L, Logistics Reassignment Management Data

 - ADC 221A, Revised Procedures associated with the DLMS Enhancement for Communication of Unit Price

 - ADC 349, Revise DLMS Supplement (DS) 536L Logistics Reassignment Management Data Transaction to Establish a Moving Average

Cost (MAC) Field (Supply/Finance)

 - ADC 436, Administrative Revisions to DLMS Supplements to Remove Obsolete Routing Identifier Code (RIC) “Streamline” Notes and

Update MILSTRIP/DLMS Documentation Associated with Routing Identifiers

 - Organizational Name and Other Non-Substantive (Administrative) Updates Completed on March 11, 2014

 - ADC 1043C, Administrative Corrections for SLOA Data in the 810L Logistics Bill and other DLMS ICs

 - ADC 1161A, Update Uniform Procurement Instrument Identifier (PIID) Numbering System in the Federal/DLMS Implementation

Conventions and DLMS Manuals (Supply/SDR/DoDAAD/Finance/Contract Administration)

- ADC 1161B, Modify DLMS 536L Logistics Reassignment Management Data to Identify the Procurement Instrument Identifier

(PIID)Associated with a Base Contract Number in Logistics Reassignment Contract History Data Transactions (Supply/Contract

Administration)

 - Administrative Update to Reflect Realignment to Recognize DLMS Program Office Completed on December 21, 2016

 - ADC 1254, Remove Unit of Measure Code Validation from DLMS XML Schemas

 - Administrative Update to Reflect Realignment of DLMS Program Office to Enterprise Business Standards Office (EBSO) - Completed on

August 09, 2018

- ADC 1287, DLMS Implementation Convention (IC) Revisions for Data Element Mapping (Form Stock Number and Manufacturer's Part

Number), Removal of Plant Equipment Number, and Administrative Update

- ADC 1367, Administrative Update to Convert Federal Notes to DLMS Notes within DLMS Implementation Conventions

- Administrative Update to Reflect Realignment of Enterprise Business Standards Office (EBSO) to Defense Enterprise Data Standards 
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 2 July 6, 2022

Office (DEDSO) - Completed on February 24, 2022

- ADC 1412, Replacement of Data Universal Numbering System Number with Unique Entity Identifier and Electronic Funds Transfer

Indicator to Wide Area Workflow

- ADC 1420, Other Transaction (OT) Agreements Instrument Type and Procurement Instrument Identifier (PIID) Construct (Supply/Contract

Administration

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

10 ST Transaction Set Header M 1 Must use

20 BR Beginning Segment for Material

Management

M 1 Must use

* 30 N9 Reference Identification O 20 Not Used

* 40 G62 Date/Time O 10 Not Used

* LOOP ID - LM * LOOP ID - LM 20

* 50 LM Code Source Information O 1 Not Used

60 LQ Industry Code M 100 Must use

LOOP ID - N1 LOOP ID - N1 20

70 N1 Name O 1 Used

* 80 N2 Additional Name Information O 2 Not Used

* 90 N3 Address Information O 2 Not Used

* 100 N4 Geographic Location O 1 Not Used

110 G61 Contact O 10 Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL LOOP ID - HL >1

10 HL Hierarchical Level M 1 Must use

20 LIN Item Identification O 1 Used

30 CS Contract Summary O 1 Used

40 QTY Quantity O >1 Used

50 RCD Receiving Conditions O 1 Used

60 N9 Reference Identification O >1 Used

70 CON Contract Number Detail O >1 Used

80 G62 Date/Time O 50 Used

90 CTP Pricing Information O 10 Used

100 G69 Line Item Detail - Description O 30 Used

* 110 DD Demand Detail O 100 Not Used

120 LDT Lead Time O 3 Used

130 MEA Measurements O 5 Used

* 140 PKG Marking, Packaging, Loading O 5 Not Used

150 PWK Paperwork O 1 Used

160 MSG Message Text O 10 Used

LOOP ID - LM LOOP ID - LM 20

170 LM Code Source Information O 1 Must use

180 LQ Industry Code M 100 Must use

LOOP ID - N1 LOOP ID - N1 50

190 N1 Name O 1 Used

* 200 N2 Additional Name Information O 2 Not Used

* 210 N3 Address Information O 2 Not Used

* 220 N4 Geographic Location O 1 Not Used

* 230 G61 Contact O 10 Not Used

240 SE Transaction Set Trailer M 1 Must use
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 3 July 6, 2022

ST Transaction Set Header Pos: 10 Max: 1

Heading - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

Purpose: To indicate the start of a transaction set and to assign a control number

Semantics: 

1. The transaction set identifier (ST01) used by the translation routines of the interchange partners to select the appropriate transaction set

definition (e.g., 810 selects the Invoice Transaction Set).

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

ST01 143 Transaction Set Identifier Code

Description: Code uniquely identifying a

Transaction Set

M ID 3/3 Must use 1

CodeList Summary (Total Codes: 298, Included: 1)

Code Name

536 Logistics Reassignment

ST02 329 Transaction Set Control Number

Description: Identifying control number

that must be unique within the transaction

set functional group assigned by the

originator for a transaction set

DLMS Note: A unique number assigned by

the originator of the transaction set, or the

originator's application program.

M AN 4/9 Must use 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 4 July 6, 2022

BR Beginning Segment for Material

Management

Pos: 20 Max: 1

Heading - Mandatory

Loop: N/A Elements: 4

User Option (Usage): Must use

Purpose: To indicate the beginning of a material management transaction and transmit identifying numbers and dates

Syntax Rules: 

1. C0504 - If BR05 is present, then BR04 is required.

2. P0708 - If either BR07 or BR08 is present, then the other is required.

3. P1011 - If either BR10 or BR11 is present, then the other is required.

Semantics: 

1. BR03 is the date of the transaction set preparation.

2. BR09 is the time of the transaction set preparation

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

BR01 353 Transaction Set Purpose Code

Description: Code identifying purpose of

transaction set

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 65, Included: 2)

Code Name

00 Original

77 Simulation Exercise

DLMS Note:

Use to identify a simulated mobilization exercise transaction set. Activities initiating simulated

mobilization exercises must ensure complete coordination with all activities involved. All transaction set

recipients must use extreme caution to ensure that individual transactions do not process as action

documents which affect accountable records.

BR02 640 Transaction Type Code

Description: Code specifying the type of

transaction

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 446, Included: 1)

Code Name

LR Logistics Reassignment

DLMS Note:

Use to indicate this transaction set provides logistics reassignment management information.

BR03 373 Date

Description: Date expressed as

CCYYMMDD

DLMS Note: This date corresponds to the

Universal Time Coordinate (UTC).

M DT 8/8 Must use 1

BR09 337 Time

Description: Time expressed in 24-hour

clock time as follows: HHMM, or HHMMSS,

or HHMMSSD, or HHMMSSDD, where H =

hours (00-23), M = minutes (00-59), S =

integer seconds (00-59) and DD = decimal

seconds; decimal seconds are expressed

as follows: D = tenths (0-9) and DD =

hundredths (00-99)

O TM 4/8 Must use 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F536L3LA12 5 July 6, 2022

DLMS Note: 1. Express the originating

activity's time in UTC.

2. Express time in a four-position (HHMM)

format.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 6 July 6, 2022

N1 Name Pos: 70 Max: 1

Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

Must use this 1/N1/070 loop to identify the organization originating the transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

M ID 2/3 Must use 1

CodeList Summary (Total Codes: 1312, Included: 2)

Code Name

GP Gateway Provider

DLMS Note:

Future streamlined data needed for transition period to support transaction conversion in a mixed

DLSS/DLMS environment. Use to identify DAASC as originator during conversion when the DLSS

transaction does not contain a "From" Losing Inventory Manager (LIM).

ZN Losing Inventory Manager

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Must use 1

CodeList Summary (Total Codes: 215, Included: 2)

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; see introductory DLMS

note 4a.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Must use 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Must use 1

CodeList Summary (Total Codes: 1312, Included: 1)
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 7 July 6, 2022

Code Name

FR Message From

DLMS Note:

Must use to indicate the organization cited in N104 is originating the transaction set.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 8 July 6, 2022

G61 Contact Pos: 110 Max: 10

Heading - Optional

Loop: N1 Elements: 5

User Option (Usage): Used

Purpose: To identify a person or office to whom communications should be directed

Syntax Rules: 

1. P0304 - If either G6103 or G6104 is present, then the other is required.

Comments: 

1. G6103 qualifies G6104.

DLMS Note:

1. Use multiple repetitions to identify the POC and multiple communication numbers. When using multiple repetitions to identify different

communication numbers for a single POC, repeat the name cited in G6102.

2. Use in the 1/N1/070 From loop to identify the LIM point of contact (POC) when direct communications are required.

3. DLMS enhancement; see introductory DLMS note 4a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

G6101 366 Contact Function Code

Description: Code identifying the major

duty or responsibility of the person or group

named

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 230, Included: 1)

Code Name

MG Manager

DLMS Note:

Use to identify the LIM point of contact.

G6102 93 Name

Description: Free-form name

DLMS Note: Provide the last name, first

name, middle initial, and rate/rank/title, as

needed, of the individual named as POC. 

Include blank spaces between name

components and periods after initials. Do

not include NMN or NMI when a middle

initial is not available.

DLMS Note: Provide the last name, first

name, middle initial, and rate/rank/title, as

needed, of the individual named as POC. 

Include blank spaces between name

components and periods after initials. Do

not include NMN or NMI when a middle

initial is not available.

M AN 1/60 Must use 1

G6103 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

DLMS Note: 1. Use to identify the

preferred method of communication in the

first repetition. Use additional repetitions

when identifying alternate communication

methods.

DLMS Note: 1. Use to identify the

preferred method of communication in the

first repetition. Use additional repetitions

when identifying alternate communication

methods.

2. Do not include blank spaces, dashes, or

parentheses between numbers.

X ID 2/2 Must use 1

CodeList Summary (Total Codes: 40, Included: 8)

Code Name

AU Defense Switched Network

DLMS Note:
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Code Name

004010F536L3LA12 9 July 6, 2022

Use to identify the DSN telephone number.

EM Electronic Mail

EX Telephone Extension

DLMS Note:

Use immediately following codes AU, IT or TE to identify a telephone extension.

FX Facsimile

DLMS Note:

Use to identify the facsimile (FAX) telephone number.

IT International Telephone

TE Telephone

DLMS Note:

Use to identify the commercial telephone number. Include the area code and number.

TL Telex

TX TWX

G6104 364 Communication Number

Description: Complete communications

number including country or area code

when applicable

X AN 1/80 Must use 1

G6105 443 Contact Inquiry Reference

Description: Additional reference number

or description to clarify a contact number

DLMS Note: Use to indicate the office

symbol or activity code for the party

identified.

O AN 1/20 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 10 July 6, 2022

HL Hierarchical Level Pos: 10 Max: 1

Detail - Mandatory

Loop: HL Elements: 3

User Option (Usage): Must use

Purpose: To identify dependencies among and the content of hierarchically related groups of data segments

Comments: 

1. The HL segment is used to identify levels of detail information using a hierarchical structure, such as relating line-item data to shipment

data, and packaging data to line-item data.

2. The HL segment defines a top-down/left-right ordered structure.

3. HL01 shall contain a unique alphanumeric number for each occurrence of the HL segment in the transaction set. For example, HL01

could be used to indicate the number of occurrences of the HL segment, in which case the value of HL01 would be "1" for the initial HL

segment and would be incremented by one in each subsequent HL segment within the transaction.

4. HL02 identifies the hierarchical ID number of the HL segment to which the current HL segment is subordinate.

5. HL03 indicates the context of the series of segments following the current HL segment up to the next occurrence of an HL segment in

the transaction. For example, HL03 is used to indicate that subsequent segments in the HL loop form a logical grouping of data referring

to shipment, order, or item-level information.

6. HL04 indicates whether or not there are subordinate (or child) HL segments related to the current HL segment.

DLMS Note:

1. The transaction set hierarchical data structure is general management and materiel description information (product description) followed

by subordinate backorder and demand (quantity), onhand inventory (item), due-in resources (order), historical contract (contract), and

product quality deficiency report (quality characteristics) information loops. The product quality deficiency report loop is followed by

subordinate PQDR complaint (line detail) loops.

2. Must use a single 2/HL/010 product description loop iteration to identify each item of supply (e.g., National Stock Number (NSN)) for

which subsequent logistics reassignment information is furnished and the GIM.

3. Use a single 2/HL/010 quantity loop, as needed, for each 2/HL/010 product in description loops to identify backorder and demand

quantities associated with each NSN undergoing logistics reassignment.

4. Use multiple 2/HL/010 item loops, as needed, in 2/HL/010 product description loops to identify the onhand quantity information associated

with each NSN undergoing logistics reassignment.

5. Use multiple 2/HL/010 order loops, as needed, in 2/HL/010 product description loops to identify due-in quantity information associated

with each NSN undergoing logistics reassignment.

6. Use up to 25 2/HL/010 contract loops, as needed, for each 2/HL/010 product description loop to identify contract history information

associated with each NSN undergoing logistics reassignment.

7. Use multiple 2/HL/010 quality characteristics loops, as needed, for each 2/HL/010 product description loop to identify the summary

contents of PQDRs associated with each NSN undergoing logistics reassignment.

8. Use multiple 2/HL/010 line detail loops, as needed, for each quality characteristics loop to identify each complaint cited on each PQDR.

1. The transaction set hierarchical data structure is general management and materiel description information (product description) followed

by subordinate backorder and demand (quantity), onhand inventory (item), due-in resources (order), historical contract (contract), and

product quality deficiency report (quality characteristics) information loops. The product quality deficiency report loop is followed by

subordinate PQDR complaint (line detail) loops.

2. Must use a single 2/HL/010 product description loop iteration to identify each item of supply (e.g., National Stock Number (NSN)) for

which subsequent logistics reassignment information is furnished and the GIM.

3. Use a single 2/HL/010 quantity loop, as needed, for each 2/HL/010 product in description loops to identify backorder and demand

quantities associated with each NSN undergoing logistics reassignment.

4. Use multiple 2/HL/010 item loops, as needed, in 2/HL/010 product description loops to identify the onhand quantity information associated

with each NSN undergoing logistics reassignment.

5. Use multiple 2/HL/010 order loops, as needed, in 2/HL/010 product description loops to identify due-in quantity information associated

with each NSN undergoing logistics reassignment.

6. Use up to 25 2/HL/010 contract loops, as needed, for each 2/HL/010 product description loop to identify contract history information

associated with each NSN undergoing logistics reassignment.

7. Use multiple 2/HL/010 quality characteristics loops, as needed, for each 2/HL/010 product description loop to identify the summary

contents of PQDRs associated with each NSN undergoing logistics reassignment.

8. Use multiple 2/HL/010 line detail loops, as needed, for each quality characteristics loop to identify each complaint cited on each PQDR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

HL01 628 Hierarchical ID Number

Description: A unique number assigned by

the sender to identify a particular data

segment in a hierarchical structure

DLMS Note: In the first 2/HL/010 loop

iteration, cite numeric 1. In each

subsequent loop iteration, increase

incrementally by 1.

M AN 1/12 Must use 1

HL02 734 Hierarchical Parent ID Number

Description: Identification number of the

next higher hierarchical data segment that

the data segment being described is

subordinate to

O AN 1/12 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F536L3LA12 11 July 6, 2022

DLMS Note: 1. Must use in every 2/HL/010

quantity, item, order, contract, and quality

characteristics loop iteration to identify the

product description loop with which the

current loop is associated. Data element

content is the sequential number assigned

to the 2/HL/010 product description loop

iteration and serves as the cross-reference

between the item of supply and all other

information provided in the transaction. 

DLMS Note: 1. Must use in every 2/HL/010

quantity, item, order, contract, and quality

characteristics loop iteration to identify the

product description loop with which the

current loop is associated. Data element

content is the sequential number assigned

to the 2/HL/010 product description loop

iteration and serves as the cross-reference

between the item of supply and all other

information provided in the transaction. 

2. Must use in every 2/HL/010 line detail

loop iteration to identify the quality

characteristics loop with which the current

loop is associated. 

3. Data element content is the sequential

number assigned to the applicable

2/HL/010 quality characteristics loop

iteration and serves as the cross-reference

between the PQDR and the various

complaints cited in the PQDR.

3. Data element content is the sequential

number assigned to the applicable

2/HL/010 quality characteristics loop

iteration and serves as the cross-reference

between the PQDR and the various

complaints cited in the PQDR.

HL03 735 Hierarchical Level Code

Description: Code defining the

characteristic of a level in a hierarchical

structure

M ID 1/2 Must use 1

CodeList Summary (Total Codes: 170, Included: 7)

Code Name

9 Line Detail

DLMS Note:

1. Use to identify the individual complaints for each PQDR.

2. DLMS enhancement; see introductory DLMS note 4a.

D Product Description

DLMS Note:

Use to identify the individual item of supply (e.g., NSN) and all general management and descriptive

information.

G Quality Characteristics

DLMS Note:

1. Use to identify the individual completed PQDRs associated with the item of supply.

2. DLMS enhancement; see introductory DLMS note 4a.

I Item

DLMS Note:

Use to identify the onhand asset data stratified by storage location, ownership, and materiel condition

for the item of supply.

O Order

DLMS Note:

Use to identify the due-in asset data stratified by storage location, type of due-in, and date due for the

item of supply.

R Quantity

DLMS Note:

Use to identify the backorder and demand data for the item of supply.

IB Contract

DLMS Note:

Use to identify contract history data for the item of supply.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 12 July 6, 2022

LIN Item Identification Pos: 20 Max: 1

Detail - Optional

Loop: HL Elements: 12

User Option (Usage): Used

Purpose: To specify basic item identification data

Syntax Rules: 

1. P0405 - If either LIN04 or LIN05 is present, then the other is required.

2. P0607 - If either LIN06 or LIN07 is present, then the other is required.

3. P0809 - If either LIN08 or LIN09 is present, then the other is required.

4. P1011 - If either LIN10 or LIN11 is present, then the other is required.

5. P1213 - If either LIN12 or LIN13 is present, then the other is required.

6. P1415 - If either LIN14 or LIN15 is present, then the other is required.

7. P1617 - If either LIN16 or LIN17 is present, then the other is required.

8. P1819 - If either LIN18 or LIN19 is present, then the other is required.

9. P2021 - If either LIN20 or LIN21 is present, then the other is required.

10. P2223 - If either LIN22 or LIN23 is present, then the other is required.

11. P2425 - If either LIN24 or LIN25 is present, then the other is required.

12. P2627 - If either LIN26 or LIN27 is present, then the other is required.

13. P2829 - If either LIN28 or LIN29 is present, then the other is required.

14. P3031 - If either LIN30 or LIN31 is present, then the other is required.

Semantics: 

1. LIN01 is the line item identification

Comments: 

1. See the Data Dictionary for a complete list of IDs.

2. LIN02 through LIN31 provide for fifteen different product/service IDs for each item. For example: Case, Color, Drawing No., U.P.C. No.,

ISBN No., Model No., or SKU.

DLMS Note:

1. Must use in every 2/HL/010 product description loop to identify the item of supply.

2. Use data element 235/234 pairs to identify data pertinent to the transaction. Unless otherwise specified, the multiple codes listed for a

single qualifier data element identify the range of possible data requirements. When needed, use the next available combination of data

element 235/234 pairs to provide the necessary data.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LIN02 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 477, Included: 4)

Code Name

F4 Series Identifier

DLMS Note:

Use to identify the manufacturer's series number of the end item.

FS National Stock Number

DLMS Note:

Must use to identify the National Stock Number (NSN).

MN Model Number

DLMS Note:

Use to identify the manufacturer's model number of the end item.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Code Name

004010F536L3LA12 13 July 6, 2022

SN Serial Number

DLMS Note:

Use to identify the manufacturer's serial

number of the end item.

LIN03 234 Product/Service ID

Description: Identifying number for a

product or service

M AN 1/48 Must use 1

LIN04 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

DLMS Note: 1. Use codes EQ, F7, MN, or

SW only during review periods 1 and 2.

2. Use only one of codes EQ, F7, MN, or

SW to describe a single end item

application associated with the item of

supply.

3. Use up to five repetitions of the data

element 235/234 pairs to describe multiple

different end item applications for the item

of supply. Sequence applications in

descending order of critical priority.

X ID 2/2 Used 1

CodeList Summary (Total Codes: 477, Included: 5)

Code Name

EQ Equipment Type

DLMS Note:

Use to identify an end item type associated with the item of supply.

F7 End-Item Description

DLMS Note:

Use to identify an end item name associated with the item of supply.

MN Model Number

DLMS Note:

Use to identify an end item model number associated with the item of supply.

SW Stock Number

DLMS Note:

Use to identify an end item NSN associated with the item of supply.

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

LIN05 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1

LIN06 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

All valid standard codes are used. (Total

Codes: 477)

X ID 2/2 Used 1

LIN07 234 Product/Service ID X AN 1/48 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F536L3LA12 14 July 6, 2022

Description: Identifying number for a

product or service

LIN08 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

All valid standard codes are used. (Total

Codes: 477)

X ID 2/2 Used 1

LIN09 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1

LIN10 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

All valid standard codes are used. (Total

Codes: 477)

X ID 2/2 Used 1

LIN11 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1

LIN12 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

All valid standard codes are used. (Total

Codes: 477)

X ID 2/2 Used 1

LIN13 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 15 July 6, 2022

CS Contract Summary Pos: 30 Max: 1

Detail - Optional

Loop: HL Elements: 9

User Option (Usage): Used

Purpose: To provide information about a contract

Syntax Rules: 

1. P0405 - If either CS04 or CS05 is present, then the other is required.

Semantics: 

1. CS09 is the permissible overage as a percentage of the total contract line item number (CLIN) quantity.

2. CS10 is the permissible shortage as a percentage of the total contract line item number (CLIN) quantity.

3. CS11 is the permissible overage dollar value specified by the contract above which discrepancy action is taken.

4. CS14 is the Unit of Measure stipulated in the contract.

5. CS15 is the contract line item number (CLIN) unit price specified in the contract.

6. CS17 conveys the Critical Application Indicator. A "Y" indicates that a Critical Application Indicator is specified in the contract; an "N"

indicates that no Critical Application Indicator is specified in the contract.

7. CS18 conveys the Special Requirements Indicator. A "Y" indicates that a Special Requirements Indicator (requiring special testing and

or evaluation) is specified in the contract; an "N" indicates that no Special Requirements Indicator is specified in the contract.

Comments: 

1. CS04 may be used to identify the Contract Line Item Number (CLIN) or Extended (or Exhibit) Line Item Number (ELIN).

2. CS07 and CS13 can be used to indicate two different types of special services required.

DLMS Note:

1. Use in the 2/HL/010 product description loop to identify the place of inspection established for the item of supply.

2. Must use in every 2/HL/010 contract loop to identify historical contract information for the item of supply.

3. Must use in every 2/HL/010 quality characteristics loop to identify PQDR contract information for the item of supply. This is a DLMS

enhancement; see introductory DLMS note 4a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

CS01 367 Contract Number

Description: Contract number

DLMS Note: 1. Must use with the 2/HL/010

contract loop to identify the procurement

instrument identifier (PIID). When

procurement is authorized under a PIID

call/order number (F in 9th position),

provide the value in the PIID field. For

Other Transaction (OT) agreements, the

type of instrument (9th position of PIID) will

be a 3 for Research OTs or 9 for Prototype

and Production OTs. Refer to ADC 1161A

or ADC 1420.

DLMS Note: 1. Must use with the 2/HL/010

contract loop to identify the procurement

instrument identifier (PIID). When

procurement is authorized under a PIID

call/order number (F in 9th position),

provide the value in the PIID field. For

Other Transaction (OT) agreements, the

type of instrument (9th position of PIID) will

be a 3 for Research OTs or 9 for Prototype

and Production OTs. Refer to ADC 1161A

or ADC 1420.

2. Use only with Logistics Reassignment

Contract History Data Transaction to

provide the PIID of the base contract

number. In CS06, provide the PIID of the

call/order associated with the base contract.

 Refer to ADC 1161B.

2. Use only with Logistics Reassignment

Contract History Data Transaction to

provide the PIID of the base contract

number. In CS06, provide the PIID of the

call/order associated with the base contract.

 Refer to ADC 1161B.

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

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

O AN 1/30 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F536L3LA12 16 July 6, 2022

use” in this situation. 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.

use” in this situation. 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.

CS03 328 Release Number

Description: Number identifying a release

against a Purchase Order previously placed

by the parties involved in the transaction

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

loop to identify the six- position

Supplementary PIID when applicable.

Refer to ADC 1161A or ADC 1420.

O AN 1/30 Used 1

CS04 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

X ID 2/3 Used 1

CodeList Summary (Total Codes: 1503, Included: 1)

Code Name

C7 Contract Line Item Number

DLMS Note:

Use only in the 2/HL/010 contract loop to identify the line item number consisting of the Contract Line

Item Number (CLIN), including the respective Subcontract Line Item Number (SUBCLIN), as applicable.

CS05 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

X AN 1/30 Used 1

CS06 324 Purchase Order Number

Description: Identifying number for

Purchase Order assigned by the

orderer/purchaser

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

loop, only with Logistics Reassignment

Contract History Data Transaction to

provide the PIID of the call order

associated with the base contract identified

in CS01. Refer to ADC 1161B.

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

loop, only with Logistics Reassignment

Contract History Data Transaction to

provide the PIID of the call order

associated with the base contract identified

in CS01. Refer to ADC 1161B.

O AN 1/22 Used 1

CS09 954 Percent

Description: Percentage expressed as a

decimal

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

loop to identify the percentage of positive

quantity variance permitted.

O R 1/10 Used 1

CS10 954 Percent

Description: Percentage expressed as a

decimal

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

loop to identify the percentage of negative

quantity variance permitted.

O R 1/10 Used 1

CS13 560 Special Services Code

Description: Code identifying the special

service

O ID 2/10 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F536L3LA12 17 July 6, 2022

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

description loop, for review periods 1 and 2

only, to identify the inspection location.

CodeList Summary (Total Codes: 168, Included: 2)

Code Name

IM Inspect at Destination

DLMS Note:

Use to indicate that inspection takes place at destination.

IO Inspect at Origin

DLMS Note:

Use to indicate that inspection takes place at origin.

CS14 355 Unit or Basis for Measurement Code

Description: Code specifying the units in

which a value is being expressed, or

manner in which a measurement has been

taken

DLMS Note: 1. Must use in the 2/HL/010

contract loop to identify the contract unit of

issue. 

2. DLMS users see the Unit of Issue and

Purchase Unit Conversion Table for

available codes. 

O ID 2/2 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 18 July 6, 2022

QTY Quantity Pos: 40 Max: >1

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To specify quantity information

Syntax Rules: 

1. R0204 - At least one of QTY02 or QTY04 is required.

2. E0204 - Only one of QTY02 or QTY04 may be present.

Semantics: 

1. QTY04 is used when the quantity is non-numeric.

DLMS Note:

1. Use in the 2/HL/010 product description loop to identify the total number of resources available (onhand and on order) for the item of

supply.

2. Use multiple repetitions in the 2/HL/010 quantity loop to identify demand and backorder data for the item of supply.

3. Use in the 2/HL/010 item loop, in conjunction with the 2/LM/170 and 2/N1/190 loops, to stratify the onhand inventory quantity (QTY01

code 17) by materiel condition, ownership or purpose, and storage location.

4. Use in the 2/HL/010 order loop, in conjunction with 2/G62/080, and the 2/LM/170 and 2/N1/190 loops, to stratify the due-in inventory

quantity (QTY01 code 63) by due date, storage location, and type of due-in.

5. Must use in every 2/HL/010 contract loop to identify the contract quantity (QTY01 code YX) for the item of supply.

1. Use in the 2/HL/010 product description loop to identify the total number of resources available (onhand and on order) for the item of

supply.

2. Use multiple repetitions in the 2/HL/010 quantity loop to identify demand and backorder data for the item of supply.

3. Use in the 2/HL/010 item loop, in conjunction with the 2/LM/170 and 2/N1/190 loops, to stratify the onhand inventory quantity (QTY01

code 17) by materiel condition, ownership or purpose, and storage location.

4. Use in the 2/HL/010 order loop, in conjunction with 2/G62/080, and the 2/LM/170 and 2/N1/190 loops, to stratify the due-in inventory

quantity (QTY01 code 63) by due date, storage location, and type of due-in.

5. Must use in every 2/HL/010 contract loop to identify the contract quantity (QTY01 code YX) for the item of supply.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier

Description: Code specifying the type of

quantity

DLMS Note: The following codes are

authorized.

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 832, Included: 33)

Code Name

17 Quantity on Hand

DLMS Note:

Must use in every 2/HL/010 item loop to identify the on hand wholesale inventory.

1Q Total Resource (Quantity)

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.

A data maintenance action was approved in version 5030. The approved code/name is "XR – Stockage

Objective and Insurance Quantity".

3U Total Transactions

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.

A data maintenance action was approved in version 5030. The approved code/name is "TQ - Total

Quality of All Buys".

63 On Order Quantity

DLMS Note:

Must use in every 2/HL/010 order loop to identify the wholesale due-in inventory.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Code Name

004010F536L3LA12 19 July 6, 2022

69 Incremental Order Quantity

DLMS Note:

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.

BA Due-In

DLMS Note:

Use in the first 2/HL/010 order loop to identify the total due-in wholesale inventory quantity without

regard to due date, receiving storage location or type of due-in.

BQ Backorder Quantity

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the total backorder quantity.

PP Purchase of Product

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.

RY Requirement Quantity

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.

XA Total of Issuable Assets

DLMS Note:

Use in the first 2/HL/010 item loop to identify the total on hand wholesale assets without regard to

ownership or purpose or storage location.

XG On Hand and Due-In

DLMS Note:

Use in the 2/HL/010 product description loop, for review periods 1 and 2, to identify the total number of

onhand plus on order wholesale inventory assets.

XJ Other War Reserve Material Requirements Protectable (OWRMRP) Quantity

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the Other War Reserve Material, Recurring, Protected

(OWRMRP) quantity.

XZ Backorder Lines

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the number of backorder requisitions.

YA Total Demand Quantity

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the total recurring plus nonrecurring demand quantities for

the past four quarters.

YB Total Demand Orders

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the total recurring plus nonrecurring demand frequencies

for the past four quarters.

YC First Quarter Recurring Demand

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly recurring demand quantity.

YD First Quarter Recurring Orders

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly recurring demand frequency.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Code Name

004010F536L3LA12 20 July 6, 2022

YE First Quarter Non-recurring Demand

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly nonrecurring demand quantity.

YF First Quarter Non-recurring Orders

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly nonrecurring demand frequency.

YG Second Quarter Recurring Demand

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly recurring demand quantity.

YH Second Quarter Recurring Orders

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly recurring demand frequency.

YJ Second Quarter Non-recurring Demand

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly nonrecurring demand quantity

YK Second Quarter Non-recurring Orders

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly nonrecurring demand frequency.

YL Third Quarter Recurring Demand

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly recurring demand quantity.

YM Third Quarter Recurring Orders

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly recurring demand frequency.

YN Third Quarter Non-recurring Demand

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly nonrecurring demand quantity.

YP Third Quarter Non-recurring Orders

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly nonrecurring demand frequency.

YQ Fourth Quarter Recurring Demand

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly recurring demand quantity.

YR Fourth Quarter Recurring Orders

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly recurring demand frequency.

YS Fourth Quarter Non-recurring Demand

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly nonrecurring demand quantity.

YT Fourth Quarter Non-recurring Orders

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the appropriate quarterly nonrecurring demand frequency.

YW Reorder Point Quantity

DLMS Note:

Use in the 2/HL/010 quantity loop to identify the computed reorder point quantity.

YX Contract Line Item Quantity

DLMS Note:

Use in the 2/HL/010 contract loop to identify the total quantity delivered on the CLIN/SUBCLIN.

QTY02 380 Quantity

Description: Numeric value of quantity

X R 1/15 Must use 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F536L3LA12 21 July 6, 2022

DLMS Note: A field size exceeding 5

positions (seven for FSG 13, ammunition)

may not be received or understood by

recipient's automated processing system.

See introductory DLMS note 4d.

DLMS Note: A field size exceeding 5

positions (seven for FSG 13, ammunition)

may not be received or understood by

recipient's automated processing system.

See introductory DLMS note 4d.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 22 July 6, 2022

RCD Receiving Conditions Pos: 50 Max: 1

Detail - Optional

Loop: HL Elements: 5

User Option (Usage): Used

Purpose: To report receiving conditions and specify contested quantities

Syntax Rules: 

1. R020406 - At least one of RCD02, RCD04 or RCD06 is required.

2. P0203 - If either RCD02 or RCD03 is present, then the other is required.

3. P0405 - If either RCD04 or RCD05 is present, then the other is required.

4. P060708 - If either RCD06, RCD07 or RCD08 are present, then the others are required.

5. P091011 - If either RCD09, RCD10 or RCD11 are present, then the others are required.

6. P121314 - If either RCD12, RCD13 or RCD14 are present, then the others are required.

7. P151617 - If either RCD15, RCD16 or RCD17 are present, then the others are required.

8. P181920 - If either RCD18, RCD19 or RCD20 are present, then the others are required.

Semantics: 

1. RCD01 is the receiving advice line item identification.

2. RCD21 is the cumulative quantity of goods received for a specific time period.

Comments: 

1. See the Data Element Dictionary for a complete list of receiving condition IDs.

2. RCD06 through RCD20 provide for five different quantities whose condition upon receipt is under question.

DLMS Note:

1. Must use in every 2/HL/010 quality characteristics loop to identify quantity information associated with each PQDR.

2. DLMS enhancement; see introductory DLMS note 4a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

RCD02 663 Quantity Units Received or Accepted

Description: Number of Units Received or

Accepted

DLMS Note: Use to identify the total

quantity received as reported on the PQDR.

Express as a whole number with no

decimal.

X R 1/9 Must use 1

RCD03 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for

examples of use)

X Comp Must use 1

RCD03-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in

which a value is being expressed, or

manner in which a measurement has been

taken

DLMS Note: 1. Use to identify the unit of

issue for the materiel

2. DLMS users see the DLMS Unit of Issue

and Purchase Unit Conversion Table for

available codes. .

M ID 2/2 Must use 1

RCD06 667 Quantity in Question X R 1/9 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F536L3LA12 23 July 6, 2022

Description: Number of units contested

because of physical condition or status of

units

DLMS Note: Use to identify the total

quantity reported as deficient. Express as a

whole number with no decimal.

RCD07 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for

examples of use)

X Comp Used 1

RCD07-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in

which a value is being expressed, or

manner in which a measurement has been

taken

DLMS Note: 1. Use to identify the unit of

issue for the materiel. 

2. DLMS users see the DLMS Unit of Issue

and Purchase Unit Conversion Table for

available codes. 

M ID 2/2 Must use 1

RCD08 412 Receiving Condition Code

Description: Code designating physical

condition or status of units received in a

specific shipment

X ID 2/2 Used 1

CodeList Summary (Total Codes: 15, Included: 1)

Code Name

04 Quality Problem
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 24 July 6, 2022

N9 Reference Identification Pos: 60 Max: >1

Detail - Optional

Loop: HL Elements: 4

User Option (Usage): Used

Purpose: To transmit identifying information as specified by the Reference Identification Qualifier

Syntax Rules: 

1. R0203 - At least one of N902 or N903 is required.

2. C0605 - If N906 is present, then N905 is required.

Semantics: 

1. N906 reflects the time zone which the time reflects.

2. N907 contains data relating to the value cited in N902.

DLMS Note:

1. Use in the 2/HL/010 product description loop to identify general logistics reassignment information associated with the item of supply.

2. Must use in every 2/HL/010 contract loop to identify the materiel ordered.

3. Must use in every 2/HL/010 quality characteristics loop to identify the control numbers associated with the PQDR.

4. Must use with every 2/HL/010 line detail loop to distinguish between complaints cited on each PQDR.

5. Use in 2/HL/010 quantity loop to identify demand and backorder data for item of supply. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N901 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

CodeList Summary (Total Codes: 1503, Included: 11)

Code Name

1R Storage Information Code

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.

55 Sequence Number

DLMS Note:

1. Must use in every 2/HL/010 line detail loop to identify the complaint sequence number for each

complaint cited on the PQDR. In the first 2/HL/010 line detail loop iteration, cite numeric 1 in N902. In

each subsequent 2/HL/010 loop iteration, increase the N902 value incrementally by 1.

2. DLMS enhancement; see introductory DLMS note 4a.

8X Transaction Category or Type

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.

9H Packaging Group Number

DLMS Note:

1. For use with the Item, Order, Quantity, and Contract loops to identify the MILSTRAP Package

Sequence Number. 
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Code Name

004010F536L3LA12 25 July 6, 2022

2. Future streamlined data; see introductory DLMS note 4c.

M2 Major Force Program

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.

MF Manufacturers Part Number

DLMS Note:

Must use in every 2/HL/010 contract loop to identify the manufacturer's part number for the materiel

being supplied. Enter the manufacturer’s part number in N903. Refer to ADC 1287.

NZ Critical Application

DLMS Note:

Use in the 2/HL/010 product description loop, for review periods 1 and 2, to indicate that the item has a

critical application as defined by Defense Logistics Agency Regulation (DLAR) 3200.1, et al; otherwise,

do not use. Cite one of the following codes in N902, as appropriate:

1 - Item is essential to a weapon system.

2 - Item is essential to the preservation of life in emergencies.

3 - Item is essential to the safety of operating personnel.

Use in the 2/HL/010 product description loop, for review periods 1 and 2, to indicate that the item has a

critical application as defined by Defense Logistics Agency Regulation (DLAR) 3200.1, et al; otherwise,

do not use. Cite one of the following codes in N902, as appropriate:

1 - Item is essential to a weapon system.

2 - Item is essential to the preservation of life in emergencies.

3 - Item is essential to the safety of operating personnel.

QR Quality Report Number

DLMS Note:

1. Must use in every 2/HL/010 quality characteristics loop to identify the PQDR report control number

assigned by the originator of the PQDR.

2. DLMS enhancement; see introductory DLMS note 4a.

S2 Data Source

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.

TP Test Specification Number

DLMS Note:

Use in the 2/HL/010 product description loops for review periods 1 and 2, to identify the first article

testing requirement for the item of supply; otherwise, do not use. Cite one of the following codes in

N902, as appropriate:

U - Undetermined.

Y - First article testing is required.

N - First article testing is not required.

Use in the 2/HL/010 product description loops for review periods 1 and 2, to identify the first article

testing requirement for the item of supply; otherwise, do not use. Cite one of the following codes in

N902, as appropriate:

U - Undetermined.

Y - First article testing is required.

N - First article testing is not required.

WC Contract Option Number

DLMS Note:

Use in the 2/HL/010 product description loop, for review periods 1 and 2, to identify the number of

option years available past the current expiration date for the term or requirement contract identified in

2/CON/070; otherwise, do not use. Express N902 as a whole number beginning with 0 (e.g., 0

indicating that no contract extension is possible, 1 indicating a one year extension).

N902 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

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

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

X AN 1/30 Must use 1

N903 369 Free-form Description

Description: Free-form descriptive text

X AN 1/45 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F536L3LA12 26 July 6, 2022

DLMS Note: Use with N901 code MF. 

Refer to ADC 1287.

N907 C040 Reference Identifier

Description: To identify one or more

reference numbers or identification

numbers as specified by the Reference

Qualifier

Syntax: 

1. P0304 - If either C04003 or C04004 is

present, then the other is required.

2. P0506 - If either C04005 or C04006 is

present, then the other is required.

O Comp Used 1

N907-01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

CodeList Summary (Total Codes: 1503, Included: 1)

Code Name

W7 Commercial and Government Entity (CAGE) Code

DLMS Note:

Use with N901 code MF to uniquely identify the manufacturer's part number.

N907-02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

M AN 1/30 Must use 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 27 July 6, 2022

CON Contract Number Detail Pos: 70 Max: >1

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To specify contract or reference number and status

DLMS Note:

Use in the 2/HL/010 product description loop, for review periods 1 and 2, to identify any current term or requirement contract number that is

available for placement of stock replenishment and or direct delivery orders for requisitioners.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

CON01 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

M ID 2/3 Must use 1

CodeList Summary (Total Codes: 1503, Included: 1)

Code Name

CT Contract Number

DLMS Note:

Use to identify the term or requirement contract indicator. Enter Y (yes) if a current term/requirement

type contract is available for placement of purchase orders for stock replenishment and/or direct

delivery to requisitioners; otherwise, leave blank.

CON02 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

M AN 1/30 Must use 1

CON03 846 Contract Status Code

Description: Code designating the current

status of the contract

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 39, Included: 1)

Code Name

VA Valid Open Contract
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 28 July 6, 2022

G62 Date/Time Pos: 80 Max: 50

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To specify pertinent dates and times

Syntax Rules: 

1. R0103 - At least one of G6201 or G6203 is required.

2. P0102 - If either G6201 or G6202 is present, then the other is required.

3. P0304 - If either G6203 or G6204 is present, then the other is required.

DLMS Note:

1. Use multiple repetitions in the 2/HL/010 product description loop to identify unique general management dates associated with the item of

supply.

2. Use in the 2/HL/010 order loop in conjunction with 2/G62/080, and the 2/LM/170 and 2/N1/190 loops, to stratify the due-in inventory

quantity by due date, storage location, and type of due-in.

3. Must use multiple repetitions in every 2/HL/010 contract loop to identify date information related to contract history for the item of supply.

4. Must use in every 2/HL/010 quality characteristics loop to identify dates associated with a PQDR.

1. Use multiple repetitions in the 2/HL/010 product description loop to identify unique general management dates associated with the item of

supply.

2. Use in the 2/HL/010 order loop in conjunction with 2/G62/080, and the 2/LM/170 and 2/N1/190 loops, to stratify the due-in inventory

quantity by due date, storage location, and type of due-in.

3. Must use multiple repetitions in every 2/HL/010 contract loop to identify date information related to contract history for the item of supply.

4. Must use in every 2/HL/010 quality characteristics loop to identify dates associated with a PQDR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

G6201 432 Date Qualifier

Description: Code specifying type of date

DLMS Note: The following codes are

authorized.

X ID 2/2 Must use 1

CodeList Summary (Total Codes: 137, Included: 12)

Code Name

02 Delivery Requested on This Date

DLMS Note:

Use in every 2/HL/010 contract loop to identify the original CLIN delivery date.

11 Shipped on This Date

DLMS Note:

Use in every 2/HL/010 contract loop to identify the date the last shipment was made.

17 Estimated Delivery Date

DLMS Note:

Use in every 2/HL/010 order loop to identify the due-in date for the due-in quantity reported.

36 Expiration Date

DLMS Note:

Use in the 2/HL/010 product description loop, for review periods 1 and 2, to identify the expiration date

of the term or requirement contract cited in 2/CON/070; otherwise, do not use.

85 Date Issued

DLMS Note:

Use in every 2/HL/010 contract loop to identify the date of contract award.

BD Required By

DLMS Note:

Indicates Date item is required.

BM Contract Physically Completed

DLMS Note:

Use in the 2/HL/010 contract loop to indicate the physical completion of the contract.

BS Product Receipt Date
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Code Name

004010F536L3LA12 29 July 6, 2022

DLMS Note:

Use in every 2/HL/010 contract loop to indicate the last receipt date.

BX Action

DLMS Note:

1. Use in every 2/HL/010 quality characteristics loop to identify the closing date of the PQDR

investigation.

2. DLMS enhancement; see introductory DLMS note 4a.

CA Cutoff Date

DLMS Note:

Use in every 2/HL/010 product description loop to identify the extract date of logistics reassignment

data from LIMs' files.

LA Last Acquisition

DLMS Note:

Use in the 2/HL/010 product description loop, for review periods 1 and 2, to identify the most recent

purchase request date.

LD Last Demand

DLMS Note:

Use in the 2/HL/010 product description loop, for review periods 1 and 2, to identify the most recently

recorded demand date.

G6202 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Must use 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 30 July 6, 2022

CTP Pricing Information Pos: 90 Max: 10

Detail - Optional

Loop: HL Elements: 2

User Option (Usage): Used

Purpose: To specify pricing information

Syntax Rules: 

1. P0405 - If either CTP04 or CTP05 is present, then the other is required.

2. C0607 - If CTP06 is present, then CTP07 is required.

3. C0902 - If CTP09 is present, then CTP02 is required.

4. C1002 - If CTP10 is present, then CTP02 is required.

5. C1103 - If CTP11 is present, then CTP03 is required.

Semantics: 

1. CTP07 is a multiplier factor to arrive at a final discounted price. A multiplier of .90 would be the factor if a 10% discount is given.

2. CTP08 is the rebate amount.

Comments: 

1. See Figures Appendix for an example detailing the use of CTP03 and CTP04.

2. See Figures Appendix for an example detailing the use of CTP03, CTP04 and CTP07.

DLMS Note:

1. Must use in every 2/HL/010 contract loop to identify the CLIN unit price from the award.

2. May use additional repetition in 2/HL/010 contract loop to provide the moving average cost (MAC).

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

CTP02 236 Price Identifier Code

Description: Code identifying pricing

specification

DLMS Note: The following codes are

authorized.

X ID 3/3 Must use 1

CodeList Summary (Total Codes: 165, Included: 6)

Code Name

ACT Actual

EST Estimated Price

FCH Flat Charge

DLMS Note:

Use to indicate that the item of supply is not separately priced.

FGP Free Goods Price

DLMS Note:

Use to indicate that the unit price is not applicable.

MAC Moving Average Cost

DLMS Note:

1. Use to indicate the moving average cost (MAC). Refer to ADC 349.

2. Authorized DLMS migration enhancement. See introductory DLMS note 4e. 

3. At this time a local code ‘MAC’ is established for use in 536L, version 4010. A data maintenance

action has been submitted for establishment of ‘MAC -Moving Average Cost code’ in a future version.

OAP Optional to Advise Unit Price

DLMS Note:

Use to indicate that the unit price is not available.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 31 July 6, 2022

CTP03 212 Unit Price

Description: Price per unit of product,

service, commodity, etc.

DLMS Note: 1. Do not use if no price

applies. Express the contract unit price in

dollars and cents, including the decimal.

2. DLMS transactions authorize an

expanded unit price field size of 9 digits for

dollars and 4 digits for cents. The decimal

point is passed in the transaction. If

conversion to MILS legacy format is

required, unit prices exceeding the legacy

field size constraint will not be perpetuated.

Authorized DLMS migration enhancement. 

Refer to ADC 221A. 

2. DLMS transactions authorize an

expanded unit price field size of 9 digits for

dollars and 4 digits for cents. The decimal

point is passed in the transaction. If

conversion to MILS legacy format is

required, unit prices exceeding the legacy

field size constraint will not be perpetuated.

Authorized DLMS migration enhancement. 

Refer to ADC 221A. 

X R 1/17 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 32 July 6, 2022

G69 Line Item Detail - Description Pos: 100 Max: 30

Detail - Optional

Loop: HL Elements: 1

User Option (Usage): Used

Purpose: To describe an item in free-form format

DLMS Note:

1. Use multiple repetitions in the 2/HL/010 product description loop, for review periods 1 and 2, to identify the clear text purchase

description.

2. Use in every 2/HL/010 quality characteristics loop to identify item nomenclature as reported on the PQDR.

3. DLMS enhancement; see introductory DLMS note 4a.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

G6901 369 Free-form Description

Description: Free-form descriptive text

M AN 1/45 Must use 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 33 July 6, 2022

LDT Lead Time Pos: 120 Max: 3

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To specify lead time for availability of products and services

Semantics: 

1. LDT04 is the effective date of lead time information.

Comments: 

1. LDT02 is the quantity of unit of time periods.

DLMS Note:

Use in the 2/HL/010 product description loop, for review periods 1 and 2, to identify production lead times for the item of supply.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LDT01 345 Lead Time Code

Description: Code indicating the time

range

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 30, Included: 1)

Code Name

AE From date of PO receipt to shipment

DLMS Note:

Use to indicate the production leadtime, defined as the time between the award of a contract and

materiel receipt into the supply system.

LDT02 380 Quantity

Description: Numeric value of quantity

DLMS Note: Use to identify the numeric

value of production lead time days.

M R 1/15 Must use 1

LDT03 344 Unit of Time Period or Interval

Description: Code indicating the time

period or interval

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 50, Included: 1)

Code Name

DY Day
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 34 July 6, 2022

MEA Measurements Pos: 130 Max: 5

Detail - Optional

Loop: HL Elements: 3

User Option (Usage): Used

Purpose: To specify physical measurements or counts, including dimensions, tolerances, variances, and weights(See Figures Appendix for

example of use of C001)

Syntax Rules: 

1. R03050608 - At least one of MEA03, MEA05, MEA06 or MEA08 is required.

2. C0504 - If MEA05 is present, then MEA04 is required.

3. C0604 - If MEA06 is present, then MEA04 is required.

4. L07030506 - If MEA07 is present, then at least one of MEA03, MEA05 or MEA06 is required.

5. E0803 - Only one of MEA08 or MEA03 may be present.

Semantics: 

1. MEA04 defines the unit of measure for MEA03, MEA05, and MEA06.

Comments: 

1. When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any measurement where a positive (+) value cannot

be assumed, use MEA05 as the negative (-) value and MEA06 as the positive (+) value.

DLMS Note:

Use two repetitions in the 2/HL/010 product description loop, for review periods 1 and 2, to identify the maximum unit pack weight and cube

associated with the item of supply.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

MEA02 738 Measurement Qualifier

Description: Code identifying a specific

product or process characteristic to which a

measurement applies

O ID 1/3 Must use 1

CodeList Summary (Total Codes: 920, Included: 2)

Code Name

G Gross Weight

DLMS Note:

Use to identify the maximum gross weight of the unit pack.

UCB Cube

DLMS Note:

Use to identify the maximum cube of the unit pack.

MEA03 739 Measurement Value

Description: The value of the

measurement

DLMS Note: 1. Express both the unit pack

weight and cube values as a whole number

with decimal positions.

2. A field size exceeding 5 positions (seven

for FSG 13, ammunition) may not be

received or understood by recipient's

automated processing system. See

introductory DLMS note 4d. 

X R 1/20 Must use 1

MEA04 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for

X Comp Must use 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F536L3LA12 35 July 6, 2022

examples of use)

MEA04-01 355 Unit or Basis for Measurement Code

Description: Code specifying the units in

which a value is being expressed, or

manner in which a measurement has been

taken

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 794, Included: 2)

Code Name

CF Cubic Feet

DLMS Note:

Use to indicate the unit pack cube in cubic feet.

LB Pound

DLMS Note:

Use to indicate the unit pack weight in pounds.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 36 July 6, 2022

PWK Paperwork Pos: 150 Max: 1

Detail - Optional

Loop: HL Elements: 5

User Option (Usage): Used

Purpose: To identify the type or transmission or both of paperwork or supporting information

Syntax Rules: 

1. P0506 - If either PWK05 or PWK06 is present, then the other is required.

Comments: 

1. PWK05 and PWK06 may be used to identify the addressee by a code number.

2. PWK07 may be used to indicate special information to be shown on the specified report.

3. PWK08 may be used to indicate action pertaining to a report.

DLMS Note:

1. Use in the 2/HL/010 product description loop to identify general logistics reassignment information associated with the item of supply.

2. If either PWK04, PWK05, or PWK06 is present, then the others are required.

3. Must use in every 2/HL/010 quality characteristics loop to identify the PQDR report type and originator.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

PWK01 755 Report Type Code

Description: Code indicating the title or

contents of a document, report or

supporting item

DLMS Note: 1. Use one of codes S5 or S6

in every 2/HL/010 quality characteristics

loop to identify the PQDR as either a

category I or II report.

2. DLMS enhancement; see introductory

DLMS note 4a.

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 522, Included: 3)

Code Name

PG Packaging Specification

DLMS Note:

Use only in the 2/HL/010 product description loop, for review periods 1 and 2, to indicate that specific

preservation, packaging, packing and marking data is available. Cite the following codes in PWK07 as

applicable:

Y - Specifications are available.

N - Specifications are not yet available.

S5 Product Quality Deficiency Report Category I

S6 Product Quality Deficiency Report Category II

PWK04 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: Use in every 2/HL/010 quality

characteristics loop only to identify the

PQDR originator.

O ID 2/3 Used 1

CodeList Summary (Total Codes: 1312, Included: 1)

Code Name

41 Submitter
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Code Name

004010F536L3LA12 37 July 6, 2022

DLMS Note:

DLMS enhancement; see introductory DLMS

note 4a.

PWK05 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Used 1

CodeList Summary (Total Codes: 215, Included: 3)

Code Name

10 Department of Defense Activity Address Code (DODAAC)

DLMS Note:

DLMS enhancement; see introductory DLMS note 4a.

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

Use to indicate the Security Assistance (SA) structured address data. Interpretation of this data may

require additional codes cited elsewhere in the transaction.

M4 Department of Defense Routing Identifier Code (RIC)

PWK06 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Used 1

PWK07 352 Description

Description: A free-form description to

clarify the related data elements and their

content

DLMS Note: 1. Use in the 2/HL/010

product description loop, for review periods

1 and 2, to identify coded information

defined in PWK01 code PG; otherwise, do

not use.

DLMS Note: 1. Use in the 2/HL/010

product description loop, for review periods

1 and 2, to identify coded information

defined in PWK01 code PG; otherwise, do

not use.

2. DLMS enhancement; see introductory

DLMS note 4a. 

O AN 1/80 Used 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 38 July 6, 2022

MSG Message Text Pos: 160 Max: 10

Detail - Optional

Loop: HL Elements: 1

User Option (Usage): Used

Purpose: To provide a free-form format that allows the transmission of text information

Syntax Rules: 

1. C0302 - If MSG03 is present, then MSG02 is required.

Semantics: 

1. MSG03 is the number of lines to advance before printing.

Comments: 

1. MSG02 is not related to the specific characteristics of a printer, but identifies top of page, advance a line, etc.

2. If MSG02 is "AA - Advance the specified number of lines before print" then MSG03 is required.

DLMS Note:

Use multiple repetitions in the 2/HL/010 line detail loop only to identify the PQDR deficiency description, investigation results, and

disposition.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

MSG01 933 Free-Form Message Text

Description: Free-form message text

DLMS Note: DLMS enhancement; see

introductory DLMS note 4a.

M AN 1/264 Must use 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 39 July 6, 2022

LM Code Source Information Pos: 170 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Must use

Purpose: To transmit standard code list identification information

Comments: 

1. LM02 identifies the applicable industry code list source information.

DLMS Note:

1. Must use this 2/LM/170 loop to identify coded information maintained in departmental or agency documentation.

2. Must use in the 2/HL/010 product description loop to identify the type of transaction and general management and materiel description

information associated with the item of supply.

3. Must use in every 2/HL/010 item loop, in conjunction with 2/QTY/040 and the 2/N1/190 loop, to stratify the onhand inventory quantity by

materiel condition, ownership, and storage location.

4. Must use in every 2/HL/010 order loop in conjunction with 2/G62/080, and the 2/LM/170 and 2/N1/190 loops, to stratify the due-in

inventory quantity by due date, storage location, and type due-in.

5. Must use in every 2/HL/010 contract loop to identify coded information associated with the contract.

1. Must use this 2/LM/170 loop to identify coded information maintained in departmental or agency documentation.

2. Must use in the 2/HL/010 product description loop to identify the type of transaction and general management and materiel description

information associated with the item of supply.

3. Must use in every 2/HL/010 item loop, in conjunction with 2/QTY/040 and the 2/N1/190 loop, to stratify the onhand inventory quantity by

materiel condition, ownership, and storage location.

4. Must use in every 2/HL/010 order loop in conjunction with 2/G62/080, and the 2/LM/170 and 2/N1/190 loops, to stratify the due-in

inventory quantity by due date, storage location, and type due-in.

5. Must use in every 2/HL/010 contract loop to identify coded information associated with the contract.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LM01 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

M ID 2/2 Must use 1

CodeList Summary (Total Codes: 176, Included: 1)

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 40 July 6, 2022

LQ Industry Code Pos: 180 Max: 100

Detail - Mandatory

Loop: LM Elements: 2

User Option (Usage): Must use

Purpose: Code to transmit standard industry codes

Syntax Rules: 

1. C0102 - If LQ01 is present, then LQ02 is required.

DLMS Note:

Use to identify codes, as appropriate, consistent with management information requirements.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

LQ01 1270 Code List Qualifier Code

Description: Code identifying a specific

industry code list

DLMS Note: 1. Use either code 99 or A1

(but not both), except for ammunition where

both codes may be used. 

2. The following codes are authorized. 

(Use of both codes for ammunition is a

DLMS enhancement (see introductory

DLMS note 4a.) 

O ID 1/3 Must use 1

CodeList Summary (Total Codes: 558, Included: 23)

Code Name

0 Document Identification Code

DLMS Note:

1. The legacy MISTRAP DIC is retained in the DLMS to facilitate transaction conversion in a mixed

DLSS/DLMS environment. Continued support of the legacy MILSTRAP DIC in a full DLMS environment

will be assessed at a future date.

2. Future streamlined data; see introductory DLMS note 4c.

2 Type of Business Code

DLMS Note:

Use in the 2/HL/010 contract loop.

4 Type of Contract Code

DLMS Note:

Use in the 2/HL/010 contract loop.

5 Criticality Designator Code

DLMS Note:

Use in the 2/HL/010 contract loop.

79 Priority Designator Code

DLMS Note:

Recommend using in all requisitions.

83 Supply Condition Code

DLMS Note:

Must use in every 2/HL/010 item loop to identify the materiel condition of the on hand quantity reported.

99 Purpose Code

DLMS Note:

1. Use in 2/HL/010 item loops to identify the purpose of the on hand quantity reported.

2. DLMS enhancement; see introductory DLMS note 4a.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Code Name

004010F536L3LA12 41 July 6, 2022

A1 Ownership Code

DLMS Note:

Use in the 2/HL/010 item loops to identify the ownership of the on hand quantity reported.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

2. Future streamlined data; see introductory DLMS note 4c.

AH Acquisition Method Suffix Code

DLMS Note:

Use in the 2/HL/010 contract loop.

AI Acquisition Method Code

DLMS Note:

Use in the 2/HL/010 contract loop.

AJ Utilization Code

DLMS Note:

1. Under DLSS, this is the first position of the document serial number.

2. DLMS enhancement; see introductory DLMS note 4a.

AL Special Requirements Code

DLMS Note:

1. Under DLSS, this is carried in the required delivery date field.

2. DLMS enhancement; see introductory DLMS note 4a.

EH Type Due-In Indicator

DLMS Note:

Must use in every 2/HL/010 order loop to identify the type due-in indicator code for the due-in quantity

reported.

EV Review Period Indicator Code

DLMS Note:

Must use in every 2/HL/010 product description loop.

EZ Type Inspection Code

DLMS Note:

Use in the 2/HL/010 product description loop, only for review periods 1 and 2.

FF Essentiality Code

DLMS Note:

Use in the 2/HL/010 product description loop, only for review periods 1 and 2.

FG Source Maintenance and Recoverability Code

DLMS Note:

Use in the 2/HL/010 product description loop, only for review periods 1 and 2.

GQ Group Qualifier Code

DLMS Note:

Use to identify the Material Management Aggregation Code (MMAC) for NSNs to be managed by a

specific manager (i.e., System, program, aggregation, selected FSC, technology group). This is an Air

Force-unique data element meaningful to the Air Force only. Non-Air Force components perpetuate

without action.

A data maintenance action was approved in version 5010. The approved code/name is "MAC – Material

Management Aggregation Code". The code source is identified as the Air Force Manual (AFMAN)

23-110, Volumes 1 and 2.

Use to identify the Material Management Aggregation Code (MMAC) for NSNs to be managed by a

specific manager (i.e., System, program, aggregation, selected FSC, technology group). This is an Air

Force-unique data element meaningful to the Air Force only. Non-Air Force components perpetuate

without action.

A data maintenance action was approved in version 5010. The approved code/name is "MAC – Material

Management Aggregation Code". The code source is identified as the Air Force Manual (AFMAN)

23-110, Volumes 1 and 2.

COG Cognizance Symbol

DLMS Note:

1. Use to identify the material cognizance symbol (COG) of the end item. Indicate NSL for non-stock

numbered listed items. This is a Navy-unique data element meaningful to Navy only; Non-Navy

Components are to perpetuate without action.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Code Name

004010F536L3LA12 42 July 6, 2022

2. DLMS enhancement.

IMC Item Management Code

DLMS Note:

1. Use to identify the Item Management Code (IMC) for integrated material management. This is a

Navy-unique data element meaningful to Navy only; Non-Navy Components are to perpetuate without

action.

2. DLMS enhancement.

MCC Material Control Code

DLMS Note:

1. Use to identify the Material Control Code (MCC) for special inventory reporting. This is a Navy-unique

data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

2. DLMS enhancement.

SMI Special Material Identification Code

DLMS Note:

1. Use to identify the Special Material Identification Code (SMIC) for an end item. This is a Navy-unique

data element meaningful to Navy only; Non-Navy Components are to perpetuate without action.

2. DLMS enhancement.

LQ02 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

X AN 1/30 Must use 1
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 43 July 6, 2022

N1 Name Pos: 190 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Used

Purpose: To identify a party by type of organization, name, and code

Syntax Rules: 

1. R0203 - At least one of N102 or N103 is required.

2. P0304 - If either N103 or N104 is present, then the other is required.

Comments: 

1. This segment, used alone, provides the most efficient method of providing organizational identification. To obtain this efficiency the "ID

Code" (N104) must provide a key to the table maintained by the transaction processing party.

2. N105 and N106 further define the type of entity in N101.

DLMS Note:

1. Must use one iteration of this 2/N1/190 loop to identify the organization to receive the transaction.

2. Use additional iterations to identify other organizations associated with the transaction.

3. Must use in the 2/HL/010 item loop, in conjunction with 2/QTY/040 and the 2/LM/170 loop, to stratify the onhand inventory quantity by

materiel condition, ownership, and storage location.

4. Must use in the 2/HL/010 order loop, in conjunction with 2/G62/080 and the 2/LM/170 and 2/N1/190 loops, to stratify the due-in inventory

quantity by due date, storage location, and type due-in. 

5. Use in every 2/HL/010 contract loop to identify organizations associated with the contract.

6. Use in every 2/HL/010 quality characteristics loop to identify organizations associated with the PQDR.

1. Must use one iteration of this 2/N1/190 loop to identify the organization to receive the transaction.

2. Use additional iterations to identify other organizations associated with the transaction.

3. Must use in the 2/HL/010 item loop, in conjunction with 2/QTY/040 and the 2/LM/170 loop, to stratify the onhand inventory quantity by

materiel condition, ownership, and storage location.

4. Must use in the 2/HL/010 order loop, in conjunction with 2/G62/080 and the 2/LM/170 and 2/N1/190 loops, to stratify the due-in inventory

quantity by due date, storage location, and type due-in. 

5. Use in every 2/HL/010 contract loop to identify organizations associated with the contract.

6. Use in every 2/HL/010 quality characteristics loop to identify organizations associated with the PQDR.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N101 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

CodeList Summary (Total Codes: 1312, Included: 8)

Code Name

C4 Contract Administration Office

DLMS Note:

Use in the 2/HL/010 contract loop to identify the applicable contract administration services component

identifier.

DG Design Engineering

DLMS Note:

Use in the 2/HL/010 contract loop to identify the original equipment manufacturer or design control

activity.

MF Manufacturer of Goods

DLMS Note:

1. Must use in every 2/HL/010 quality characteristics loop to identify the manufacturer or prime

contractor for the materiel reported on the PQDR.

2. DLMS enhancement; see introductory DLMS note 4a.

PL Party to Receive Purchase Order

DLMS Note:
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

Code Name

004010F536L3LA12 44 July 6, 2022

Must use in every 2/HL/010 contract loop to identify the contract awardee.

RC Receiving Location

DLMS Note:

Must use in every 2/HL/010 order loop to identify the receiving storage location for the due-in quantity

reported.

SB Storage Area

DLMS Note:

Must use in every 2/HL/010 item loop to identify the storage location of the on hand quantity reported.

ZP Gaining Inventory Manager

DLMS Note:

Use in the 2/HL/010 product description loop to identify the gaining item manager to receive the

transaction.

ZQ Screening Point

DLMS Note:

1. Must use in the 2/HL/010 quality characteristics loop to identify the designated screening point for the

PQDR.

2. DLMS enhancement; see introductory DLMS note 4a.

N103 66 Identification Code Qualifier

Description: Code designating the

system/method of code structure used for

Identification Code (67)

X ID 1/2 Must use 1

CodeList Summary (Total Codes: 215, Included: 3)

Code Name

10 Department of Defense Activity Address Code (DODAAC)

33 Commercial and Government Entity (CAGE)

DLMS Note:

Use as needed with N101 codes DG, MF, and PL when no DODAAC is assigned.

M4 Department of Defense Routing Identifier Code (RIC)

N104 67 Identification Code

Description: Code identifying a party or

other code

X AN 2/80 Must use 1

N106 98 Entity Identifier Code

Description: Code identifying an

organizational entity, a physical location,

property or an individual

O ID 2/3 Used 1

CodeList Summary (Total Codes: 1312, Included: 1)

Code Name

TO Message To

DLMS Note:

Must use with the 2/N101/190 code ZP to indicate the organization cited in N104 is receiving the

transaction.
DLMS Implementation Convention (IC) 536L Logistics Reassignment

Management Data

ADC 77, 118, 185, 221A, 349, 436, 1043C, 1161A, 1161B, 1254, 1287, 1367, 1412 and

1420 DLM 4000.25

004010F536L3LA12 45 July 6, 2022

SE Transaction Set Trailer Pos: 240 Max: 1

Detail - Mandatory

Loop: N/A Elements: 2

User Option (Usage): Must use

Purpose: To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending

(SE) segments)

Comments: 

1. SE is the last segment of each transaction set.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

SE01 96 Number of Included Segments

Description: Total number of segments

included in a transaction set including ST

and SE segments

M N0 1/10 Must use 1

SE02 329 Transaction Set Control Number

Description: Identifying control number

that must be unique within the transaction

set functional group assigned by the

originator for a transaction set

DLMS Note: Cite the same number as the

one cited in ST02.

M AN 4/9 Must use 1