DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 1 April 02, 2024

517 Material Obligation Validation

Functional Group=MV

Purpose: This Draft Standard for Trial Use provides the format and establishes the data contents of the Material Obligation Validation

Transaction Set (517) for use within the context of an Electronic Data Interchange (EDI) environment. The material obligation validation

transaction set may be used to: (1) verify the continued need for open orders, (2) confirm open order quantities and order priority, (3) request

reinstatement of erroneously cancelled open orders, and (4) validate Government Furnished Material (GFM) orders. The transaction set may

convey a description of the material, the urgency of need associated with the transaction and quantity of required material. This transaction set

is bi-directional between trading partners.

DLMS Note:

1. Organizations use this transaction set to validate the continued need and priority of requirements held in backorder status or on direct

vendor delivery (DVD) (e.g., Materiel Obligation Validation (MOV)), provide responses to MOV requests, notify organizations of failures to

respond to MOV requests, notify organizations of exemptions from validation cycles, and request reinstatements of requirements

erroneously cancelled due to failures to respond to validation cycles. Organizations also use this transaction set to validate apparent

excessive requisition quantities and respond to excessive quantity validations. Use a single occurrence of this transaction set to transmit

single or multiple MOV requests, MOV responses, notifications of non-response to MOV cycles, MOV exemptions, MOV reinstatement

requests, excessive quantity verification inquiries, or excessive quantity verification responses to one organization.

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

Conversion Table and the Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data

Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS.

3. This DLMS Implementation Convention 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. Legacy MILSTRIP data which must be retained in the DLMS for a transition period to support transaction conversion in a mixed legacy

MILSTRIP/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 field size above existing legacy MILSTRIP capability which may not be supported by the

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

e. Repetition of data (using multiple iterations or loops) which is not compatible with existing legacy MILSTRIP capability. Although

supported by the use of the ANSI X12 standard, such data is not compatible with legacy MILSTRIP/DLMS conversion and may not be

supported by the recipient's automated processing system. Components must coordinate implementation of enhanced capability with

DEDSO prior to use.

f. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data

(including expanded field sizes) should be adopted during, or subsequent, to modernization when applicable to the Component’s business

process. Prior coordination is not required. Components should ensure that inclusion of this data in a DLMS transaction does not cause

inappropriate rejection of the transaction.

4. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDCs) and Approved DLMS Changes (ADCs) listed. PDCs/ADCs

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

- ADC 49, Revision to DS 517M, MOV

- ADC 49A, Revision to DS 517M, MOV

- ADC 49B, Revision to DS 517M, MOV

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

- ADC 78, Addendum Revision to DS 517M, Material Obligation Validation MOV

- ADC 99, Revision to DS 517G, and 517M to Accommodate Requirement of Distribution Code

- ADC 281, Administrative Revision to DLMS Supplement (DS) 517M, Material Obligation Validation (MOV), to Include Qualifier for Material

Identification

- ADC 435, DLMS Revisions for SFIS Compliance

- 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

- ADC 1043, DLMS Revisions for Department of Defense (DoD) Standard Line of Accounting (SLOA)/Accounting Classification

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

- ADC 1043A, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Support Transaction Rejection Requirements

- ADC 1043B, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Modify Business Rules for Beginning Period of Availability

1. Organizations use this transaction set to validate the continued need and priority of requirements held in backorder status or on direct

vendor delivery (DVD) (e.g., Materiel Obligation Validation (MOV)), provide responses to MOV requests, notify organizations of failures to

respond to MOV requests, notify organizations of exemptions from validation cycles, and request reinstatements of requirements

erroneously cancelled due to failures to respond to validation cycles. Organizations also use this transaction set to validate apparent

excessive requisition quantities and respond to excessive quantity validations. Use a single occurrence of this transaction set to transmit

single or multiple MOV requests, MOV responses, notifications of non-response to MOV cycles, MOV exemptions, MOV reinstatement

requests, excessive quantity verification inquiries, or excessive quantity verification responses to one organization.

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

Conversion Table and the Transportation Mode of Shipment Conversion Table which can be found on the Defense Enterprise Data

Standards Office (DEDSO) Web site at www.dla.mil/does/DLMS.

3. This DLMS Implementation Convention 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. Legacy MILSTRIP data which must be retained in the DLMS for a transition period to support transaction conversion in a mixed legacy

MILSTRIP/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 field size above existing legacy MILSTRIP capability which may not be supported by the

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

e. Repetition of data (using multiple iterations or loops) which is not compatible with existing legacy MILSTRIP capability. Although

supported by the use of the ANSI X12 standard, such data is not compatible with legacy MILSTRIP/DLMS conversion and may not be

supported by the recipient's automated processing system. Components must coordinate implementation of enhanced capability with

DEDSO prior to use.

f. Data associated with a DLMS enhancement authorized for implementation by modernized systems under DLMS migration. This data

(including expanded field sizes) should be adopted during, or subsequent, to modernization when applicable to the Component’s business

process. Prior coordination is not required. Components should ensure that inclusion of this data in a DLMS transaction does not cause

inappropriate rejection of the transaction.

4. This revision to the DLMS IC incorporates Proposed DLMS Changes (PDCs) and Approved DLMS Changes (ADCs) listed. PDCs/ADCs

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

- ADC 49, Revision to DS 517M, MOV

- ADC 49A, Revision to DS 517M, MOV

- ADC 49B, Revision to DS 517M, MOV

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

- ADC 78, Addendum Revision to DS 517M, Material Obligation Validation MOV

- ADC 99, Revision to DS 517G, and 517M to Accommodate Requirement of Distribution Code

- ADC 281, Administrative Revision to DLMS Supplement (DS) 517M, Material Obligation Validation (MOV), to Include Qualifier for Material

Identification

- ADC 435, DLMS Revisions for SFIS Compliance

- 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

- ADC 1043, DLMS Revisions for Department of Defense (DoD) Standard Line of Accounting (SLOA)/Accounting Classification

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

- ADC 1043A, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Support Transaction Rejection Requirements

- ADC 1043B, Revised Procedures for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting Classification to

Modify Business Rules for Beginning Period of Availability
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 2 April 02, 2024

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

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

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

September 28, 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 Updates

- 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

Office (DEDSO) - Completed on February 23, 2022

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

Indicator to Wide Area Workflow

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

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

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

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

September 28, 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 Updates

- 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

Office (DEDSO) - Completed on February 23, 2022

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

Indicator to Wide Area Workflow

- ADC 1465, G-Invoicing Federal Intragovernmental Data Standards

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 G62 Date/Time O 10 Used

LOOP ID - LM LOOP ID - LM 10

40 LM Code Source Information O 1 Used

50 LQ Industry Code M 100 Must use

LOOP ID - N1 LOOP ID - N1 >1

60 N1 Name O 1 Must use

* 70 N2 Additional Name Information O 2 Not Used

* 80 N3 Address Information O 2 Not Used

* 90 N4 Geographic Location O 1 Not Used

100 G61 Contact O 5 Used

Detail:

Pos Id Segment Name Req Max Use Repeat Notes Usage

LOOP ID - QTY LOOP ID - QTY >1

10 QTY Quantity O 1 Used

20 N9 Reference Identification O 30 Must use

40 G62 Date/Time O 30 Used

* 50 DD Demand Detail O 100 Not Used

* 60 GF Furnished Goods and Services O 1 Not Used

LOOP ID - LM LOOP ID - LM 10

70 LM Code Source Information O 1 Used

80 LQ Industry Code M 100 Must use

* LOOP ID - N1 * LOOP ID - N1 >1

* 90 N1 Name O 1 Not Used

* 100 N2 Additional Name Information O 2 Not Used

* 110 N3 Address Information O 2 Not Used

* 120 N4 Geographic Location O 1 Not Used

* 130 G61 Contact O 5 Not Used

LOOP ID - FA1 LOOP ID - FA1 >1

135 FA1 Type of Financial Accounting Data O 1 Used

136 FA2 Accounting Data M >1 Must use

140 SE Transaction Set Trailer M 1 Must use
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 3 April 02, 2024

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

Code Name

517 Material Obligation Validation

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) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 4 April 02, 2024

BR Beginning Segment for Material

Management

Pos: 20 Max: 1

Heading - Mandatory

Loop: N/A Elements: 9

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

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

Code Name

AN Material Obligation Inquiry

DLMS Note:

Use alone to indicate an original MOV request. Also may use with BR06 codes A3 and RU and T.

AP Material Obligation Advice

DLMS Note:

1. Use to indicate the transaction set contains MOV response transactions.

2. Use with BR06 Code 9 to identify organization(s) exempt from the current MOV cycle.

3. Use with BR06 Code V to confirm receipt of MOV request(s).

4. Use with BR06 Code 51 to indicate that all MOV requests requiring changes are considered

complete and verified as valid.

AQ Quantity Verification Inquiry

DLMS Note:

Use to indicate the transaction set contains excessive quantity verification inquiry transactions.

AV Quantity Verification Advice

DLMS Note:

Use to indicate the transaction set contains excessive quantity verification response transactions.

AW Material Obligation Reinstatement
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Code Name

004010F517M3MA12 5 April 02, 2024

DLMS Note:

Use to indicate the transaction set contains MOV reinstatement requests.

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

BR06 306 Action Code

Description: Code indicating type of action

DLMS Note: Use as needed with either

BR02 code AN or AP to further qualify the

intended purpose of the transaction set.

O ID 1/2 Used 1

Code Name

9 Not Capable of Taking Action

DLMS Note:

Use with BR02 Code AP to indicate the organizations specified in the 1/N1/060 loop are exempt from

the current MOV reporting cycle.

T Status Query

DLMS Note:

Use with BR02 code AN to indicate a follow-up to an original MOV.

V Respond

DLMS Note:

Use with BR02 Code AP to indicate the transaction set is a confirmation of receipt of MOV requests.

51 Complete

DLMS Note:

Use with BR02 Code AP to indicate all MOV requests requiring changes are considered and verified as

valid.

A3 Not Certified

DLMS Note:

Use with BR02 Code AN to indicate the organization, specified in the 1/N1/060 loop, failed to provide an

MOV response for materiel scheduled for direct delivery from procurement.

RU Return

DLMS Note:

Use with BR02 code AN to indicate customer nonresponse to MOV requests for backordered materiel in

preaward (BZ) status.

BR07 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

X ID 2/3 Used 1

Code Name

X7 Batch Sequence Number

DLMS Note:

1. Use to identify the batch control number assigned to each batch of transactions forwarded to a

single activity for validation. The first two positions will contain the batch number and the second two

positions will contain the total number of batches being forwarded.

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

BR08 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
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F517M3MA12 6 April 02, 2024

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)

DLMS Note: 1. Express the originating

activity's time in UTC.

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

format.

O TM 4/8 Must use 1

BR10 128 Reference Identification Qualifier

Description: Code qualifying the

Reference Identification

X ID 2/3 Used 1

Code Name

XM Issuer Number

DLMS Note:

1. Use to identify the actual number of individual detail transactions included in this batch from 001 to

493 maximum.

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

BR11 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
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 7 April 02, 2024

G62 Date/Time Pos: 30 Max: 10

Heading - Optional

Loop: N/A 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 this 1/G62/030 segment to indicate dates that are applicable to the entire transaction set.

2. Use to identify dates applicable to the MOV request and excessive quantity verification inquiries.

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

64 Must Respond By

DLMS Note:

Use in quantity verification inquiries to indicate the response due date.

BS Product Receipt Date

DLMS Note:

Use in MOV responses to indicate date of receipt of MOV requests.

CA Cutoff Date

DLMS Note:

Use for MOV requests to identify the last date of record against which the open orders were obtained

from the supply source's records.

G6202 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Must use 1
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 8 April 02, 2024

LM Code Source Information Pos: 40 Max: 1

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

DLMS Note:

Must use this 1/LM/040 loop to identify coded information maintained in department or agency documentation.

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) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 9 April 02, 2024

LQ Industry Code Pos: 50 Max: 100

Heading - 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: The following codes are

authorized.

O ID 1/3 Used 1

Code Name

0 Document Identification Code

DLMS Note:

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

MILSTRIP/DLMS environment. Continued support of the DIC in a full DLMS environment will be

assessed at a future date. (Applicable only to DIC AP8 and AP9).

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

AK Distribution Code

DLMS Note:

Use to identify the distribution of the MOV transaction set.

COG Cognizance Symbol

DLMS Note:

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.

LQ02 1271 Industry Code

Description: Code indicating a code from a

specific industry code list

X AN 1/30 Used 1
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 10 April 02, 2024

N1 Name Pos: 60 Max: 1

Heading - Optional

Loop: N1 Elements: 5

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:

1. Must use this 1/N1/060 loop to identify the organization originating the transaction set and the organization to recieve the transaction set.

2. Use additional iterations to identify other organizations related to 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

DLMS Note: The following codes are

authorized.

M ID 2/3 Must use 1

Code Name

97 Party Waiving Requirements

DLMS Note:

Use multiple iterations for MOV exemption transactions to identify those organizations exempt from the

current MOV cycle.

BG Buying Group

DLMS Note:

1. Use to identify the G-Invoicing Group Name Description. Refer ADC 1465.

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

BT Bill-to-Party

DLMS Note:

1. Use for SFIS compliant systems to identify the BPN of the party to receive the bill. BPN may only be

used when the corresponding DoDAAC is also provided. This will require a second iteration of the N1

loop with the same qualifier.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

PK Party to Receive Copy

Z4 Owning Inventory Control Point

ZK Reporter

DLMS Note:

Use to identify the organization accomplishing actions on behalf of the customer.

ZR Validating Party

DLMS Note:

Use to identify the party to affirm the validity of the requirement.

N102 93 Name X AN 1/60 Used 1
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F517M3MA12 11 April 02, 2024

Description: Free-form name

DLMS Note: Use with N101 Code BG to

identify the G-Invoicing Group Name

Description. The format for DoD

Components is the DoDAAC followed by a

hyphen; followed by the DoDAAC

description. Refer to ADC 1465.

DLMS Note: Use with N101 Code BG to

identify the G-Invoicing Group Name

Description. The format for DoD

Components is the DoDAAC followed by a

hyphen; followed by the DoDAAC

description. Refer to ADC 1465.

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)

DLMS Note:

DLMS enhancement; see introductory DLMS note 3a.

50 Business License Number

DLMS Note:

1. Use for SFIS to map to SFIS Data element “Business Partner Number TP3”. Enter the buyer’s BPN

in N104.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

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

require additional codes cited elsewhere in the transaction.

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

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

Code Name

FR Message From

DLMS Note:

Use with the appropriate 1/N101/060 code to indicate that the organization cited in N104 is originating

the transaction set.

TO Message To

DLMS Note:

Use with the appropriate 1/N101/060 code to indicate that the organization cited in N104 is the action

organization receiving the transaction set.
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 12 April 02, 2024

G61 Contact Pos: 100 Max: 5

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 only under exceptional circumstances when requiring direct communication with the party originating the transaction set.

2. Use multiple repetitions as needed to identify a point of contact (POC) and multiple communication numbers. When using multiple

repetitions to identify different communication numbers for a single POC, repeat the name cited in G6102.

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

IC Information Contact

DLMS Note:

Must use in the first repetition to identify the primary POC and their primary communication number.

G6102 93 Name

Description: Free-form name

DLMS Note: Provide the last name, first

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

required, 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

required, 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 Used 1

Code Name

AU Defense Switched Network

DLMS Note:

Use to identify the Defense Switched Network (DSN) telephone number.

EM Electronic Mail
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Code Name

004010F517M3MA12 13 April 02, 2024

EX Telephone Extension

DLMS Note:

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

FX Facsimile

DLMS Note:

Use to identify the facsimile (FAX) telephone number.

IT International Telephone

DLMS Note:

Include country and city code.

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 Used 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) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 14 April 02, 2024

QTY Quantity Pos: 10 Max: 1

Detail - Optional

Loop: QTY 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 the 2/QTY/010 loop for MOV request, MOV response, notification of nonresponse, materiel obligation reinstatement request, excessive

quantity verification inquiry, and excessive quantity verification response transactions to identify information associated with the validation

process.

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

38 Original Quantity

DLMS Note:

Use for excessive quantity verification inquiry transactions to indicate the quantity requisitioned.

40 Remaining Quantity

DLMS Note:

Use for MOV response, MOV reinstatement request, and excessive quantity verification advice

transactions to indicate the quantity still required by the validating organization. (Note: The quantity

cited for MOV reinstatement request transactions cannot exceed the quantity cancelled.)

63 On Order Quantity

DLMS Note:

Use for MOV requests to indicate the unfilled quantity of items being validated by the source of supply.

AA Unacknowledged Quantity

DLMS Note:

Use to indicate quantity that will be supplied from procurement for which an MOV response was not

received.

QTY02 380 Quantity

Description: Numeric value of quantity

DLMS Note: 1. Express as a whole

number with no decimals.

2. A field size exceeding 5 positions (7

positions for FSG 13, ammunition) may not

be received or understood by the recipient's

automated processing system. See

introductory DLMS note 3d. 

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)

O Comp Used 1
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F517M3MA12 15 April 02, 2024

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

taken

DLMS Note: 1. Use to identify the unit of

issue for the materiel validated.

2. DLMS users see the Unit of Issue and

Purchase Unit Conversion Table for

available codes. 

M ID 2/2 Must use 1
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 16 April 02, 2024

N9 Reference Identification Pos: 20 Max: 30

Detail - Optional

Loop: QTY Elements: 4

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:

Use multiple repetitions to identify the transaction number and materiel identification associated with the transaction.

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: 1. Use only one of codes 1I,

FQ, MF, NS, S6, WL, XD or ZZ to identify

the materiel requisitioned. Must use

National Stock Number (NSN) when known.

2. The following codes are authorized.

M ID 2/3 Must use 1

Code Name

1I Department of Defense Identification Code (DoDIC)

DLMS Note:

Use to identify ammunition items.

FQ Form Number

DLMS Note:

Use to identify the form stock number. Enter the form stock number in N903. Refer to ADC 1287.

MF Manufacturers Part Number

DLMS Note:

Use to identify nonstandard materiel. Enter the manufacturer’s part number in N903. Refer to ADC

1287.

NS National Stock Number

S6 Stock Number

DLMS Note:

Use to identify the publication stock number.

TN Transaction Reference Number

DLMS Note:

Must use to identify the transaction number of the original requisition for the item being validated.

WL Federal Supply Classification Code

DLMS Note:

Use to identify the FSC for nonstandard materiel when a part number is not available and materiel can

only be ordered by description (e.g., non-NSN lumber products).

XD Subsistence Identification Number

DLMS Note:

Use to identify subsistence items.
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Code Name

004010F517M3MA12 17 April 02, 2024

ZZ Mutually Defined

DLMS Note:

Use to identify nonstandard materiel when all other authorized codes do not apply (Includes

management control numbers and locally assigned control numbers). May be used for legacy

MILSTRIP-to-DLMS conversion when the translator cannot determine a more appropriate code.

GTC General Terms and Conditions Identifier 

DLMS Note:

1. Use to identify the Fiscal Service (FS) Form 7600A General Terms and Conditions (GT&C) number in

G- Invoicing related transactions. Refer to ADC 1465.

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

3. At this time a local code GTC is established for use in 517M version 4010. A data maintenance

action will be submitted to ASC X12 to establish GTC, General Terms and Conditions Identifier, in a

future version.

1. Use to identify the Fiscal Service (FS) Form 7600A General Terms and Conditions (GT&C) number in

G- Invoicing related transactions. Refer to ADC 1465.

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

3. At this time a local code GTC is established for use in 517M version 4010. A data maintenance

action will be submitted to ASC X12 to establish GTC, General Terms and Conditions Identifier, in a

future version.

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/30 Used 1

N903 369 Free-form Description

Description: Free-form descriptive text

DLMS Note: Use with N901 codes FQ and

MF. Refer to ADC 1287.

X AN 1/45 Used 1

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: Use with N101 code WL to

identify the materiel name or description.

M ID 2/3 Must use 1

Code Name

PG Product Group

DLMS Note:

1. Use to identify materiel name or description

2. Use with N901 code WL to identify the materiel name or description.

W7 Commercial and Government Entity (CAGE) Code

DLMS Note:

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

W8 Suffix

DLMS Note:

Use with N901 code TN to identify the transaction number suffix.

N907-02 127 Reference Identification

Description: Reference information as

X AN 1/30 Must use 1
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Ref Id Element Name Req Type Min/Max Usage Rep

004010F517M3MA12 18 April 02, 2024

defined for a particular Transaction Set or

as specified by the Reference Identification

Qualifier
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 19 April 02, 2024

G62 Date/Time Pos: 40 Max: 30

Detail - Optional

Loop: QTY 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.

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

17 Estimated Delivery Date

DLMS Note:

Use for MOV and excessive quantity verification inquiries to identify the estimated shipping date (ESD).

G6202 373 Date

Description: Date expressed as

CCYYMMDD

X DT 8/8 Must use 1
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 20 April 02, 2024

LM Code Source Information Pos: 70 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.

DLMS Note:

Must use this 2/LM/070 loop to identify coded information maintained in department or agency documentation.

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) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 21 April 02, 2024

LQ Industry Code Pos: 80 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: The following codes are

authorized.

O ID 1/3 Must use 1

Code Name

0 Document Identification Code

DLMS Note:

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

MILSTRIP/DLMS environment. Continued support of the DIC in a full DLMS environment will be

assessed at a future date.

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

78 Project Code

DLMS Note:

1. Use to identify special programs, exercises, projects, operations, and other purposes.

2. For DoD SLOA/Accounting Classification compliance the Project Code may be repeated as a Project

Identifier (FA201 Qualifier 90). Refer to ADC 1043.

79 Priority Designator Code

80 Advice Code

81 Status Code

DLMS Note:

Use for MOV requests to identify the current supply status of the transaction.

A9 Supplemental Data

DLMS Note:

1. Use to identify supplemental address/data.

2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the

MILSTRIP Supplemented Address (SUPAAD) field. During this time, field size is restricted to 6

positions; see introductory DLMS note 3d.

3. Expanded use of this field for supplemental data

with out size restriction is a DLMS enhancement; see introductory DLMS note 3a.

4. Under full DLMS, the requirement to pass activity address information within the supplement data

field will be streamlined. Activity address data previously contained in the SUPAAD will be reflected

exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 3c.

1. Use to identify supplemental address/data.

2. During the legacy MILSTRIP/DLMS transition, this field will be used to perpetuate/populate the

MILSTRIP Supplemented Address (SUPAAD) field. During this time, field size is restricted to 6

positions; see introductory DLMS note 3d.

3. Expanded use of this field for supplemental data

with out size restriction is a DLMS enhancement; see introductory DLMS note 3a.

4. Under full DLMS, the requirement to pass activity address information within the supplement data

field will be streamlined. Activity address data previously contained in the SUPAAD will be reflected

exclusively in the N1 segment. Future streamlined data; see introductory DLMS note 3c.

AK Distribution Code

DLMS Note:

Future streamlined data; see introductory DLMS note 3c.

DE Signal Code
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Code Name

004010F517M3MA12 22 April 02, 2024

DLMS Note:

Future streamlined data; see introductory DLMS note 3c.

DF Media and Status Code

DLMS Note:

Future streamlined data; see introductory DLMS note 3c.

GQ Group Qualifier Code

DLMS Note:

Use to identify the Materiel 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. The code source is identified as the Air Force Manual (AFMAN) 23-110, Volume 1.

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

Management Aggregation Code".

Use to identify the Materiel 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. The code source is identified as the Air Force Manual (AFMAN) 23-110, Volume 1.

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

Management Aggregation Code".

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.

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) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 23 April 02, 2024

FA1 Type of Financial Accounting Data Pos: 135 Max: 1

Detail - Optional

Loop: FA1 Elements: 2

User Option (Usage): Used

Purpose: To specify the organization controlling the content of the accounting citation, and the purpose associated with the accounting citation

Semantics: 

1. FA101 Identifies the organization controlling the assignment of financial accounting information.

2. FA102 Identifies the purpose of the accounting allowance or charge information.

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

FA101 559 Agency Qualifier Code

Description: Code identifying the agency

assigning the code values

DLMS Note: This data element is required

for X12 syntax. Select the code that

corresponds to the organization that is

responsible for the assignment of the

DoDAAC used to construct the controlling

document number for the transaction.

DLMS Note: This data element is required

for X12 syntax. Select the code that

corresponds to the organization that is

responsible for the assignment of the

DoDAAC used to construct the controlling

document number for the transaction.

M ID 2/2 Must use 1

Code Name

DF Department of Defense (DoD)

DLMS Note:

Use to indicate that the Component is a Department of Defense agency, including Defense Logistics

Agency. Refer to ADC 1043.

DN Department of the Navy

DLMS Note:

Includes the United States Marine Corps.

DY Department of Air Force

DZ Department of Army

FG Federal Government

FA102 1300 Service, Promotion, Allowance, or

Charge Code

Description: Code identifying the service,

promotion, allowance, or charge

O ID 4/4 Must use 1

Code Name

A170 Adjustments

DLMS Note:

Use only for adjustments not specified by any other code.

A520 Base Charge

DLMS Note:

Use for materiel charges only.

C930 Export Shipping Charge

D340 Goods and Services Charge

DLMS Note:

Use for both materiel and related services.

F060 Other Accessorial Service Charge

F560 Premium Transportation

I260 Transportation Direct Billing

DLMS Note:

Use for non-premium transportation.
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Code Name

004010F517M3MA12 24 April 02, 2024

R060 Packing, Crating, and Handling Charge
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 25 April 02, 2024

FA2 Accounting Data Pos: 136 Max: >1

Detail - Mandatory

Loop: FA1 Elements: 2

User Option (Usage): Must use

Purpose: To specify the detailed accounting data

DLMS Note:

1. Use this segment to identify G-Invoicing 7600EZ Federal Intragovernmental Data Standards (FIDS) data elements.

2. Use this 2/FA2/136 segment to identify the various components of the line of accounting.

3. Use this segment to comply with the DoD SLOA/Accounting Classification. Cost object elements Project Identifier, Funding Center

Identifier, Functional Area, Cost Element Code, Cost Center Identifier, Activity Identifier, and Work Order Number are used as appropriate

for the system. This information is applicable to requisition re-instatement only. 

Element Summary: 

Ref Id Element Name Req Type Min/Max Usage Rep

FA201 1196 Breakdown Structure Detail Code

Description: Codes identifying details

relating to a reporting breakdown structure

tree

M ID 2/2 Must use 1

Code Name

89 Budget Line Item Identification

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Budget Line Item”.

2. Qualifier 89 is a migration code approved for use in X12 version 4020. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3f.

90 Project/Task

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Project Identifier”. Refer to ADC 1043.

2. Qualifier 90 is a migration code approved for use in X12 version 4020. 

3. Authorized DLMS enhancement; see introductory DLMS note 3f.

A1 Department Indicator

DLMS Note:

1. Use to identify the Requesting Agency Component TAS AID (Agency Identifier) in G-Invoicing related

transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify “Department Regular”. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory note 3f.

A2 Transfer from Department

DLMS Note:

1. Use to identify the Requesting Agency Component TAS ATA (Allocation Transfer Agency Identifier)

in G-Invoicing related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify “Department Transfer”. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory note 3f.

A4 Basic Symbol Number

DLMS Note:

1. Use to identify the Requesting Agency Component TAS Main (Main Account Code) in G-Invoicing

related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify “Main Account”. Refer to ADC 1043.
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Code Name

004010F517M3MA12 26 April 02, 2024

3. Authorized DLMS enhancement; see introductory DLMS note 3f.

A5 Sub-class

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SP (Sub- Level Prefix Code) in G-Invoicing

related transactions. Refer to ADC 1465.

2. Reserved for DoD SLOA/Accounting Classification use to identify “Sub Class”. Refer to ADC 1043.

3. Sub Class is a potential future DLMS enhancement; see introductory DLMS note 3a.

A6 Sub-Account Symbol

DLMS Note:

1. Use to identify the Requesting Agency Component TAS SUB (Sub- Account Code) in G-Invoicing

related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify “Sub Account”. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3f.

AI Activity Identifier

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Activity Identifier”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

3. Qualifier AI is a migration code approved for use in X12 version 7020.

B2 Budget Sub-activity Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Sub-Allocation (formerly known as

Limit/Subhead)”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

B5 Fund Code

DLMS Note:

Use to modify, or in the case of an unmatched modification, to identify the fund code. Modifier

transactions may not be used to change this field for GFM requisitions.

BE Business Event Type Code

DLMS Note:

1. Use to identify the Business Event Type Code (BETC) in G- Invoicing related transactions. Refer to

ADC 1465.

2. Reserved for DoD SLOA/Accounting Classification use to identify “Business Event Type Code”.

Refer to ADC 1043.

3. Business Event Type Code is a potential future DLMS enhancement; see introductory DLMS note 3a.

4. Qualifier BE is a migration code approved for use in X12 version 7020.

1. Use to identify the Business Event Type Code (BETC) in G- Invoicing related transactions. Refer to

ADC 1465.

2. Reserved for DoD SLOA/Accounting Classification use to identify “Business Event Type Code”.

Refer to ADC 1043.

3. Business Event Type Code is a potential future DLMS enhancement; see introductory DLMS note 3a.

4. Qualifier BE is a migration code approved for use in X12 version 7020.

C3 Budget Restriction

DLMS Note:

1. Use to identify the Requesting Agency Component TAS A (Availability Type Code) in G-Invoicing

related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify “Availability Type”. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3f.

CC Cost Center Identifier

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Cost Center Identifier”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Code Name

004010F517M3MA12 27 April 02, 2024

3. Qualifier CC is a migration code approved for use in X12 version 7020.

F1 Object Class

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Object Class”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

FA Functional Area

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Functional Area”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

3. Qualifier FA is a migration code approved for use in X12 version 7020.

FC Funding Center Identifier

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Funding Center Identifier”. Refer to ADC

1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

3. Qualifier FC is a migration code approved for use in X12 version 7020.

FT Funding Type

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Reimbursable Flag”. Refer to ADC 1043. 

2. Qualifier FT is an X12 Version Release 004030 Migration Code. 

3. Authorized DLMS enhancement; see introductory DLMS note 3f.

H1 Cost Code

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Cost Element Code”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

IA Security Cooperation Implementing Agency

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Implementing

Agency”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

3. Qualifier IA is a migration code approved for use in X12 version 7020.

L1 Accounting Installation Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Agency Accounting Identifier”. Refer to

ADC 1043. 

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

P1 Disbursing Station Number

DLMS Note:

1. Use to identify the Agency Location Code (ALC) in G- Invoicing related transactions. Refer to ADC

1465.

2. For DoD SLOA/Accounting Classification use to identify “Agency Disbursing Identifier Code”. Refer

to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3f.

P5 Foreign Military Sales (FMS) Line Item Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Case Line Item 
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

Code Name

004010F517M3MA12 28 April 02, 2024

Identifier”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

S1 Security Cooperation Customer Code

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Customer Code”. 

Refer to ADC 1043.

2. DLMS enhancement; see introductory DLMS note 3d. A field size exceeding 2 positions is not

supportable under current MILSTRIP and MAPAC processes. Three character codes are not

authorized at this time.

3. Qualifier S1 is a migration code approved for use in X12 version 7020.

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Customer Code”. 

Refer to ADC 1043.

2. DLMS enhancement; see introductory DLMS note 3d. A field size exceeding 2 positions is not

supportable under current MILSTRIP and MAPAC processes. Three character codes are not

authorized at this time.

3. Qualifier S1 is a migration code approved for use in X12 version 7020.

S2 Security Cooperation Case Designator

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Case Designator”. 

Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f. A field size exceeding 3 positions is

not supportable under current MILSTRIP processes. Four character codes are not authorized at this

time.

3. Qualifier S2 is a migration code approved for use in X12 version 7020.

1. For DoD SLOA/Accounting Classification use to identify “Security Cooperation Case Designator”. 

Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f. A field size exceeding 3 positions is

not supportable under current MILSTRIP processes. Four character codes are not authorized at this

time.

3. Qualifier S2 is a migration code approved for use in X12 version 7020.

WO Work Order Number

DLMS Note:

1. For DoD SLOA/Accounting Classification use to identify “Work Order Number”. Refer to ADC 1043.

2. Authorized DLMS enhancement; see introductory DLMS note 3f.

3. Qualifier WO is a migration code approved for use in X12 version 7020.

YB Beginning Period of Availability

DLMS Note:

1. Use to identify the Requesting Agency Component TAS BPOA (Beginning Period of Availability) in

G-Invoicing related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify “Beginning Period of Availability Fiscal Year

Date”. Refer to ADC 1043.

3. Use as appropriate to represent Program Year. Availability Type Code must be “X”. Refer to ADC

1043B.

4. Authorized DLMS enhancement; see introductory DLMS note 3f.

5. Qualifier YB is a migration code approved for use in X12 version 7020.

1. Use to identify the Requesting Agency Component TAS BPOA (Beginning Period of Availability) in

G-Invoicing related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify “Beginning Period of Availability Fiscal Year

Date”. Refer to ADC 1043.

3. Use as appropriate to represent Program Year. Availability Type Code must be “X”. Refer to ADC

1043B.

4. Authorized DLMS enhancement; see introductory DLMS note 3f.

5. Qualifier YB is a migration code approved for use in X12 version 7020.

YE Ending Period of Availability

DLMS Note:

1. Use to identify the Requesting Agency Component TAS EPOA (Ending Period of Availability) in

G-Invoicing related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify “Ending Period of Availability Fiscal Year

Date”. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3f.

4. Qualifier YE is a migration code approved for use in X12 version 7020.

1. Use to identify the Requesting Agency Component TAS EPOA (Ending Period of Availability) in

G-Invoicing related transactions. Refer to ADC 1465.

2. For DoD SLOA/Accounting Classification use to identify “Ending Period of Availability Fiscal Year

Date”. Refer to ADC 1043.

3. Authorized DLMS enhancement; see introductory DLMS note 3f.

4. Qualifier YE is a migration code approved for use in X12 version 7020.

FA202 1195 Financial Information Code

Description: Code representing financial

accounting information

M AN 1/80 Must use 1
DLMS Implementation Convention (IC) 517M Materiel Obligation

Validation (MOV)

ADCs 49, 49A, 49B, 77, 78, 99, 281, 435, 436, 1043, 1043A, 1043B, 1043C, 1287, 1367, 1412

and 1265 DLM 4000.25

004010F517M3MA12 29 April 02, 2024

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