DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 1 May 11, 2023

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. DoD Components may use this transaction set to facilitate exchange of acquisition and valuation history between two accountable

systems of record (APSR)s. DoD Components may also use this transaction set between an APSR and the Procurement Integrated

Enterprise Environment (PIEE). This transaction is not authorized for contractors. 

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 1415, New DLMS 536R to Support Required Acquisition and Valuation Data Elements

1. DoD Components may use this transaction set to facilitate exchange of acquisition and valuation history between two accountable

systems of record (APSR)s. DoD Components may also use this transaction set between an APSR and the Procurement Integrated

Enterprise Environment (PIEE). This transaction is not authorized for contractors. 

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 1415, New DLMS 536R to Support Required Acquisition and Valuation Data Elements

Heading:

Pos Id Segment Name Req Max Use Repeat Notes Usage

0100 ST Transaction Set Header M 1 Must use

0200 BR Beginning Segment for Material

Management

M 1 Must use

0300 N9 Reference Identification O 20 Must use

0400 G62 Date/Time O 10 Must use

* LOOP ID - LM * LOOP ID - LM 20

* 0500 LM Code Source Information O 1 Not Used

* 0600 LQ Industry Code M 100 Not Used

LOOP ID - N1 LOOP ID - N1 20

0700 N1 Name O 1 Must use

* 0800 N2 Additional Name Information O 2 Not Used

* 0900 N3 Address Information O 2 Not Used

* 1000 N4 Geographic Location O 1 Not Used

1100 G61 Contact O 10 Used
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 2 May 11, 2023

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - HL LOOP ID - HL >1

0100 HL Hierarchical Level M 1 Must use

0200 LIN Item Identification O 1 Used

0300 CS Contract Summary O 1 Used

0400 QTY Quantity O >1 Used

* 0500 RCD Receiving Conditions O 1 Not Used

0600 N9 Reference Identification O >1 Used

* 0700 CON Contract Number Detail O >1 Not Used

0800 G62 Date/Time O 50 Used

0900 CTP Pricing Information O 10 Used

1000 G69 Line Item Detail - Description O 30 Used

1100 DD Demand Detail O 100 Used

1200 LDT Lead Time O 3 Used

* 1300 MEA Measurements O 5 Not Used

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

* 1500 PWK Paperwork O 1 Not Used

* 1600 MSG Message Text O 10 Not Used

LOOP ID - LM LOOP ID - LM 20

1700 LM Code Source Information O 1 Used

1800 LQ Industry Code M 100 Must use

LOOP ID - N1 LOOP ID - N1 50

1900 N1 Name O 1 Must use

* 2000 N2 Additional Name Information O 2 Not Used

* 2100 N3 Address Information O 2 Not Used

* 2200 N4 Geographic Location O 1 Not Used

* 2300 G61 Contact O 10 Not Used

2400 SE Transaction Set Trailer M 1 Must use
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 3 May 11, 2023

ST Transaction Set Header Pos: 0100 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) is used by the translation routines of the interchange partners to select the appropriate transaction

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

2. The implementation convention reference (ST03) is used by the translation routines of the interchange partners to select the appropriate

implementation convention to match the transaction set definition.

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

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) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 4 May 11, 2023

BR Beginning Segment for Material

Management

Pos: 0200 Max: 1

Heading - Mandatory

Loop: N/A Elements: 5

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

Code Name

00 Original

BR02 640 Transaction Type Code

Description: Code specifying the type of

transaction

M ID 2/2 Must use 1

Code Name

TS Transfer Statement

DLMS Note:

Use for Acquisition and Valuation History Data. Use BR06 to identify the type of action.

BR03 373 Date

Description: Date expressed as

CCYYMMDD where CC represents the first

two digits of the calendar year

DLMS Note: This date corresponds to the

Universal Time Coordinate (UTC). 

M DT 8/8 Must use 1

BR06 306 Action Code

Description: Code indicating type of action

O ID 1/2 Must use 1

Code Name

7 Request

DLMS Note:

Request for Acquisition and Valuation History Data (Inquiry).

J Record

DLMS Note:

Original Acquisition and Valuation Data.

CO Correct

DLMS Note:

Corrected Acquisition and Valuation Data.

BR09 337 Time

Description: Time expressed in 24-hour

O TM 4/8 Used 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F536R0RA00 5 May 11, 2023

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)

DLMS Note: 1. Express the originating

activity's time in UTC. 

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

format. 
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 6 May 11, 2023

N9 Reference Identification Pos: 0300 Max: 20

Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): Must use

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:

Must use to identify the shipment. Repeat the loop as necessary to provide additional information. For non-new procurement, the transaction

reference is required. For new procurement, the contract number and the shipment number are required. For GFP items, you must identify

the shipment and provide the authorizing PIID (agent contract number). Only one instance of GFP data may be conveyed per transaction.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N901 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

M ID 2/3 Must use 1

Code Name

6L Agent Contract Number

DLMS Note:

Must use to identify the authorizing procurement instrument identifier (PIID) for the item(s) referenced in

the parent/child loop(s). Applicable to GFP. This is not the contract number for the item. 

CT Contract Number

DLMS Note:

Must use to identify the procurement instrument identifier (PIID) or PIID Call/Order Number applicable

to the property in question. Applicable to new procurement.

SI Shipper's Identifying Number for Shipment (SID)

DLMS Note:

Use in combination with the contract number to identify the shipment number when available. 

Applicable to new procurement. 

TG Transportation Control Number (TCN)

DLMS Note:

Use to identify the transportation control number associated to the shipment.

TN Transaction Reference Number

DLMS Note:

Must use to identify the document number associated to the shipment. Required for all action codes in

BR06. Do not use for new procurement.

N902 127 Reference Identification

Description: Reference information as

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier

X AN 1/50 Must use 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 7 May 11, 2023

G62 Date/Time Pos: 0400 Max: 10

Heading - Optional

Loop: N/A Elements: 2

User Option (Usage): Must use

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:

Must use to identify the date in which the shipment/item was shipped. For GFP only, use qualifier PE or 17 to communicate GFP period of

performance expiration data and/or expected property return date. Applies to GFP items. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

G6201 432 Date Qualifier

Description: Code specifying type of date

X ID 2/2 Must use 1

Code Name

11 Shipped on This Date

17 Estimated Delivery Date

DLMS Note:

Use to indicate the expected property return date (when different from period of performance). 

Applicable to GFP items only.

PE Period End

DLMS Note:

Use to indicate the period of performance expiration date. Applicable only to GFP items.

G6202 373 Date

Description: Date expressed as

CCYYMMDD where CC represents the first

two digits of the calendar year

X DT 8/8 Must use 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 8 May 11, 2023

N1 Name Pos: 0700 Max: 1

Heading - Optional

Loop: N1 Elements: 4

User Option (Usage): Must use

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 to identify the originating organization.

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

Code Name

41 Submitter

DLMS Note:

Must use to identify the reporting activity when different than the materiel owner initiating the property

transfer.

ZN Losing Inventory Manager

DLMS Note:

Must use to indicate the materiel owner initiating the property transfer. Required for shipments between

DoD organizations.

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

Code Name

10 Department of Defense Activity Address Code (DODAAC)

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

Code Name

FR Message From

DLMS Note:

Must use in combination with N101 to indicate the originating DODAAC. Only one loop with N106=FR. 
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 9 May 11, 2023

G61 Contact Pos: 1100 Max: 10

Heading - Optional

Loop: N1 Elements: 4

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:

Use to indicate the originating organization point of contact. Use qualifier CD to indicate a point of contact for GFP items.

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

Code Name

CD Contract Contact

DLMS Note:

Use to indicate the recipient point of contact. Applicable to GFP items only.

MG Manager

G6102 93 Name

Description: Free-form name

M AN 1/60 Must use 1

G6103 365 Communication Number Qualifier

Description: Code identifying the type of

communication number

X ID 2/2 Must use 1

Code Name

EM Electronic Mail

TE Telephone

DLMS Note:

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

G6104 364 Communication Number

Description: Complete communications

number including country or area code

when applicable

X AN 1/256 Must use 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 10 May 11, 2023

HL Hierarchical Level Pos: 0100 Max: 1

Detail - Mandatory

Loop: HL Elements: 2

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:

Must use to identify the line item and other information as necessary. The first loop must identify the line item. Use subsequent loops to

provide any information that is unique to each item.

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

HL03 735 Hierarchical Level Code

Description: Code defining the

characteristic of a level in a hierarchical

structure

DLMS Note: Use as appropriate to identify

the line item and any specific attributes that

pertaining to the asset. Use at least one

iteration of the parent and one child loop in

each transmission. Only identify the asset

by line item when transmitting a request.

DLMS Note: Use as appropriate to identify

the line item and any specific attributes that

pertaining to the asset. Use at least one

iteration of the parent and one child loop in

each transmission. Only identify the asset

by line item when transmitting a request.

M ID 1/2 Must use 1

Code Name

I Item

DLMS Note:

Must use for the parent loop to identify the line item.

PI Property Identification

DLMS Note:

Must use for the child loop to identify additional information unique to the item. Do not use when

BR06=7.
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 11 May 11, 2023

LIN Item Identification Pos: 0200 Max: 1

Detail - Optional

Loop: HL Elements: 8

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:

Use in Item loop to identify the line item.

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

Code Name

FS National Stock Number

DLMS Note:

Must use the National Stock Number when known.

SW Stock Number

DLMS Note:

Use to identify a local stock number (LSN). Do not use for Capital Equipment.

ZZ Mutually Defined

DLMS Note:

Use to identify management control number (MCN). Do not use for Capital Equipment.

LIN03 234 Product/Service ID

Description: Identifying number for a

product or service

M AN 1/48 Must use 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F536R0RA00 12 May 11, 2023

LIN04 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

X ID 2/2 Used 1

Code Name

MG Manufacturer's Part Number

DLMS Note:

Use in combination with LSN to further identify the item.

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)

X ID 2/2 Used 1

Code Name

ZB Commercial and Government Entity (CAGE) Code

DLMS Note:

Use in combination with LSN and manufacturer part number to further identify the item.

LIN07 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1

LIN08 235 Product/Service ID Qualifier

Description: Code identifying the

type/source of the descriptive number used

in Product/Service ID (234)

X ID 2/2 Used 1

Code Name

MN Model Number

LIN09 234 Product/Service ID

Description: Identifying number for a

product or service

X AN 1/48 Used 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 13 May 11, 2023

CS Contract Summary Pos: 0300 Max: 1

Detail - Optional

Loop: HL Elements: 2

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:

Use in property identification loop to identify the contract number. Only applies to new procurement shipments.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

CS01 367 Contract Number

Description: Contract number

DLMS Note: Use to identify the

procurement instrument identifier (PIID) for

the item.

O AN 1/30 Must use 1

CS02 327 Change Order Sequence Number

Description: Number assigned by the

orderer identifying a specific change or

revision to a previously transmitted

transaction set

DLMS Note: Use to identify a modification

number to the cited procurement

instrument. This is the Supplementary

Procurement Instrument Identifier

(Supplementary PIID).

DLMS Note: Use to identify a modification

number to the cited procurement

instrument. This is the Supplementary

Procurement Instrument Identifier

(Supplementary PIID).

O AN 1/8 Used 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 14 May 11, 2023

QTY Quantity Pos: 0400 Max: >1

Detail - Optional

Loop: HL Elements: 3

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:

Use in item loop to identify the quantity shipped.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

QTY01 673 Quantity Qualifier

Description: Code specifying the type of

quantity

M ID 2/2 Must use 1

Code Name

39 Shipped Quantity

QTY02 380 Quantity

Description: Numeric value of quantity

X R 1/15 Must use 1

QTY03 C001 Composite Unit of Measure

Description: To identify a composite unit of

measure(See Figures Appendix for

examples of use)

Comments: 

1. If C001-02 is not used, its value is to be

interpreted as 1.

2. If C001-03 is not used, its value is to be

interpreted as 1.

3. If C001-05 is not used, its value is to be

interpreted as 1.

4. If C001-06 is not used, its value is to be

interpreted as 1.

5. If C001-08 is not used, its value is to be

interpreted as 1.

6. If C001-09 is not used, its value is to be

interpreted as 1.

7. If C001-11 is not used, its value is to be

interpreted as 1.

8. If C001-12 is not used, its value is to be

interpreted as 1.

9. If C001-14 is not used, its value is to be

interpreted as 1.

10. If C001-15 is not used, its value is to be

interpreted as 1.

O Comp Must use 1

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

M ID 2/2 Must use 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F536R0RA00 15 May 11, 2023

taken

All valid standard codes are used.
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 16 May 11, 2023

N9 Reference Identification Pos: 0600 Max: >1

Detail - Optional

Loop: HL Elements: 2

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:

Use in property identification loop. Repeat the loop as necessary to transmit the necessary information.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

N901 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

M ID 2/3 Must use 1

Code Name

BL Government Bill of Lading

DLMS Note:

GBL required when available in the originating APSR.

BM Bill of Lading Number

DLMS Note:

Required when available in the originating APSR.

IK Invoice Number

DLMS Note:

Required when available in the originating APSR.

MF Manufacturers Part Number

DLMS Note:

Use to indicate the manufacturer part number. Do not use when using 2/LIN/0200. 

PM Part Number

DLMS Note:

Use to indicate the current part number. This is not the manufacturer part number.

SE Serial Number

DLMS Note:

Use to indicate the serial number assigned to the item. The serial number is required for serially

managed items.

W7 Commercial and Government Entity (CAGE) Code

DLMS Note:

Use to indicate the manufacturer CAGE code.

UII Unique Item Identifier

DLMS Note:

1. UII required for serially managed items. Use only with action code J (Record) in 1/BR06/0200.

2. Migration code from version/release 005050 of the X12 EDI standard. 

N902 127 Reference Identification

Description: Reference information as

X AN 1/50 Must use 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004030F536R0RA00 17 May 11, 2023

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 18 May 11, 2023

G62 Date/Time Pos: 0800 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:

Use in property identification loop.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

G6201 432 Date Qualifier

Description: Code specifying type of date

X ID 2/2 Must use 1

Code Name

07 Effective Date

DLMS Note:

Use to indicate Date Placed in Service.

62 Accrual Start Date

DLMS Note:

Use to indicate Depreciation Start Date.

63 Accrual End Date

DLMS Note:

Use to indicate Last Depreciation Date.

BT Acceptance

G6202 373 Date

Description: Date expressed as

CCYYMMDD where CC represents the first

two digits of the calendar year

X DT 8/8 Must use 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 19 May 11, 2023

CTP Pricing Information Pos: 0900 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:

Use in property identification loop.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

CTP02 236 Price Identifier Code

Description: Code identifying pricing

specification

X ID 3/3 Must use 1

Code Name

CHG Changed Price

DLMS Note:

Use to indicate accumulated depreciation valuation.

DPR Discount Price

DLMS Note:

Use to indicate current valuation price.

PUR Purchase

DLMS Note:

Use to indicate acquisition price.

UCP Unit cost price

DLMS Note:

Use to indicate unit price.

ULC Unsalable Item List Cost

DLMS Note:

Use to indicate salvage value.

CTP03 212 Unit Price

Description: Price per unit of product,

service, commodity, etc.

X R 1/17 Must use 1
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 20 May 11, 2023

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

Detail - Optional

Loop: HL Elements: 1

User Option (Usage): Used

Purpose: To describe an item in free-form format

DLMS Note:

Use in item loop.

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) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 21 May 11, 2023

DD Demand Detail Pos: 1100 Max: 100

Detail - Optional

Loop: HL Elements: 1

User Option (Usage): Used

Purpose: To describe the type of demand and the intended use of material

Syntax Rules: 

1. C0201 - If DD02 is present, then DD01 is required.

2. P030405 - If either DD03, DD04 or DD05 are present, then the others are required.

3. C0605 - If DD06 is present, then DD05 is required.

4. C1009 - If DD10 is present, then DD09 is required.

Semantics: 

1. DD08 transmits the stock level indicator. A "Y" indicates that the material is normally carried in stock; an "N" indicates that the material

is not normally stocked.

DLMS Note:

Use in item loop. Use this segment to indicate the item is capital equipment.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

DD08 1073 Yes/No Condition or Response Code

Description: Code indicating a Yes or No

condition or response

O ID 1/1 Must use 1

Code Name

Y Yes

DLMS Note:

Use to indicate the item in the item loop is Capital Equipment.
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 22 May 11, 2023

LDT Lead Time Pos: 1200 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 property identification loop.

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

Code Name

AX From Date of Award to Date of Completion

DLMS Note:

Use to indicate Depreciable Period (Days, Month, and Year).

QO Service Estimate Number

DLMS Note:

1. Use to indicate estimated useful life of the item. 

2. At this time a local code ‘QO’ is established for use in 536R, version 4030. A data maintenance

action will be submitted for establishment of ‘QO - Service Estimate Number’ in a future version.

LDT02 380 Quantity

Description: Numeric value of quantity

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

Code Name

CY Calendar Year

DY Day

MO Month
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 23 May 11, 2023

LM Code Source Information Pos: 1700 Max: 1

Detail - Optional

Loop: LM Elements: 1

User Option (Usage): Used

Purpose: To transmit standard code list identification information

Comments: 

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

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

Code Name

DF Department of Defense (DoD)
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 24 May 11, 2023

LQ Industry Code Pos: 1800 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:

Must use to further describe the item.

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

O ID 1/3 Must use 1

Code Name

78 Project Code

DLMS Note:

Perpetuate project code when available.

83 Supply Condition Code

DLMS Note:

Supply condition code (SCC) is required.

EQ Controlled Inventory Item Code

DLMS Note:

Perpetuate controlled inventory item code (CIIC) when available.

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) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 25 May 11, 2023

N1 Name Pos: 1900 Max: 1

Detail - Optional

Loop: N1 Elements: 4

User Option (Usage): Must use

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.

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

Code Name

ZP Gaining Inventory Manager

DLMS Note:

Must use to indicate the materiel owner receiving property transfer. Required when the recipient of the

shipment is Government ICP. 

DIR Distribution Recipient

DLMS Note:

Use to indicate the recipient organization when different from the materiel owner receiving property

transfer.

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

Code Name

10 Department of Defense Activity Address Code (DODAAC)

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

Code Name

TO Message To

DLMS Note:

Must use in combination with N101 to indicate the recipient DODAAC. Only one loop with N106=FR.
DLMS Implementation Convention (IC) 536R Acquisition and Valuation ADC 1415 DLM 4000.25

004030F536R0RA00 26 May 11, 2023

SE Transaction Set Trailer Pos: 2400 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