August 20, 2014
Attachment, PDC 1043A 

page 1 

Attachment to Approved Addendum to ADC 1043A, 

Revised Procedures for Department of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support Transaction Rejection Requirements 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC Per Reference 3.a.:

(1) Office of the Under Secretary of Defense (Comptroller) (OUSD(C)) 

(2) Office of the Deputy Chief Management Officer (ODCMO) 

b. Functional POC: Defense Logistics Management Standards Office (DLMSO)

(1) Finance: Robert Hammond, Chair, Finance PRC, email: financehq@dla.mil

(2) Supply: Ellen Hilert, Co-Chair, Supply PRC, email: ellen.hilert@dla.mil

2. FUNCTIONAL AREAS: Finance and Supply

3. REFERENCES:

a. Approved DLMS Change (ADC) 1043, Revisions for Department of Defense (DOD)

Standard Line of Accounting (SLOA)/Accounting Classification (Finance/Supply), dated 

September 18, 2013 

b. ADC 179, Revision to DLMS Supplement 824R, Reject Advice, to Include DAASC

Narrative Rejects, and Expansion for Rejection of Additional DLMS Transactions, dated 

September 13, 2005 

c. ADC 1103, Revise DLMS 824R, Reject Advice, to include Finance in scope and

administrative adjustments, dated August 20, 2014 

d. Joint Deputy Chief Management Officer and Under Secretary of Defense

(Comptroller) Chief Financial Officer memorandum of September 14, 2012, subject 

“Department of Defense Standard Line of Accounting/Accounting Classification” (Included as 

Enclosure 1 of Reference 3.a.) 

e. DLM 4000.25, Defense Logistics Management System, linked at

www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp 

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

linked at www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp 

g. DLM 4000.25-2, Military Standard Transaction Reporting and Accountability

Procedures (MILSTRAP), linked at www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp 
Attachment to ADC 1043A 

Page 2 

4. APPROVED CHANGE(S): 

a. Brief Overview: This change amends ADC 1043 (Reference 3.a.) guidance regarding 

rejection transactions returned when DLMS transactions include discrete SLOA data elements 

that do not correspond to the entries in the SFIS Fund Code to Fund Code Account Conversion 

Table for the Fund Code in the transaction. The requirements to inform a sender when failing 

the edit identified under ADC 1043 were specific only to the requisition and requisition-related 

transactions; this addendum revises procedures for the other functional processes included in 

ADC 1043 to use the DLMS 824R, Reject Advice, except for DLMS 842A/W, which will use a 

DLMS 842A/R transaction. Significant changes from PDC 1043A are highlighted in green

b. Background: 

(1) ADC 1043 (Reference 3.a.) incorporates required SLOA data elements in 

logistics transactions with a financial implication in support of Reference 3.b. ADC 1043 

includes an edit to be implemented at DLA Transaction Services for DLMS transactions 

providing discrete SLOA data elements, to compare the SLOA elements in the transaction to the 

entry in the SFIS Fund Code to Fund Code Account Conversion Table for the Fund Code cited in 

the transaction. Any discrepancy between the SLOA data in the transaction versus the table will 

result in the transaction being rejected. Status Code CF was identified for use in the rejection 

notice. 

(2) As DLA Transaction Services prepared to implement the edit, it was noted 

that not all of the transactions to which ADC 1043 applies would normally be rejected using an 

870S (DIC AE9) to process the CF rejection status. 

(3) DLMS 824R was initially developed for use for rejection of DLMS 

transactions associated with MILSTRAP transactions, providing specific reject advice codes. 

However, the 824R scope was expanded under the DLMS concept of operations and was 

authorized for use with other DLMS supply transactions (Reference 3.b.). It is also intended to 

be used by DLA Transaction Services for narrative message type rejects for all DLMS 

transactions subject to rejection by Defense Automatic Addressing System (DAAS) narrative 

messages.

(4) This change was developed concurrent to ADC 1103 (Reference 3.c.), which 

documents the use of DLMS 824R for finance transactions and updates guidance for its use for 

supply transactions. 

(5) This change is applicable to DLMS-compliant systems and, therefore, does 

not address legacy systems/transactions. 

(6) Also, an administrative action has been completed since ADC 1043 was 

published. In August of 2014, the technical assessment committee of Accredited Standard 

Committee (ASC) X12 informed DLMSO that the local codes for SLOA in ADC 1043 had been 

approved for publication in version 7020 of the X12 standard. As described in Volume 1 of 

Reference 3.e. the local codes of ADC 1043 are now migration codes since they are published in 

a future X12 standard. 
Attachment to ADC 1043A 

Page 3 

c. Procedures, Transactions, Data Elements, and Processing Details in Use Today:

(1) The rejection requirement of ADC 1043 is compatible with using the DLMS 

870S (MILSTRIP legacy DIC AE9) to transmit the MILSTRIP requisition rejection supply status 

for SLOA relevant transactions: DLMS 511M, 511R, 517M, and 869F. Although documented 

for SLOA, these procedures have not been implemented. 

(2) There are no defined MILSTRIP procedures for DAAS transactional rejection 

of a shipment status to the inventory control point (ICP) from the reporting activity for ICPdirected lateral redistribution order shipments of retail assets using the DLMS 856S. Rejection 

would default to a narrative message. 

(3) There are no defined MILSTRIP procedures for DAAS transactional rejection 

of a disposal release order using the DLMS 940R. Rejection would default to a narrative 

message. 

(4) Rejection of an issue transaction, DLMS 867I (MILSTRAP legacy DIC D7_), 

is made with the DLMS 824R (MILSTRAP legacy DIC DZG) and may use a status code 

(published in MILSTRIP). 

(5) The rejection of automatic return notifications and customer asset reporting 

transactions DLMS 180M (MILSTRIP legacy DICs FTA/FTE/FTG) is performed by an 870M 

with a customer asset reporting status code. 

(6) The Supply Discrepancy Report (SDR) program has a specific reply 

transaction, DLMS 842 A/R, with its own code list for transaction processing rejection reasons. 

Additionally, SDRs do not process through the same DAAS programs used for other 

supply/finance transactions. 

(7) Logistics bills, DLMS 810L (MILSBILLS legacy DIC F-series/G-series), are 

rejected by returning the rejected bill with a narrative reason for rejection. DLA Transaction 

Services rejects bills using the DLMS 824R with the appropriate narrative, but there are no 

rejection code qualifiers to facilitate automation and analysis. DLA Transaction Services also 

includes a one record position (RP) reject reason code in RP 4 of the legacy Summary Bill and in 

MILSINQ. 

d. Approved Change in Detail: ADC 1043 states: “For DLMS transactions providing

discrete SLOA data elements, DAAS is to compare SLOA elements in the transaction to the 

entry in the SFIS Fund Code to Fund Code Account Conversion Table for the Fund Code in the 

transaction. Any discrepancy between the SLOA data in the transaction versus the table will 

result in the transaction being rejected ...” The following revises the implementation of this 

requirement defined in ADC 1043 for the transactions other than requisitions, which will 

continue to use the DLMS 870S and the CF status code for rejections associated with SLOA 

edits.

(1) Expand the applicability of requisition status code CF to customer asset 

reporting status codes for use in DLMS 870M to identify SLOA rejections of DLMS 180M 
Attachment to ADC 1043A 

Page 4 

containing discrete SLOA elements not matching the SFIS Fund Code to Fund Account 

Conversion Table for the Fund Code cited in the transaction. 

(2) Establish new Reject Advice Code BU, for use on the DLMS 824R Reject 

Advice to provide notification of rejection of the DLMS 810L, 856S, 867I, or 940R containing 

discrete SLOA elements not matching the SFIS Fund Code to Fund Account Conversion Table 

for the Fund Code cited in the transaction. 

(3) Establish new Reply Code 943 for use with DLMS 842A/R reporting 

rejection of an 842 A/W containing discrete SLOA elements not matching the SFIS Fund Code 

to Fund Code Account Conversion Table for the Fund Code cited in the SDR transaction. DOD 

WebSDR will reject incoming SDR transactions for creation of the SDR, correction, follow-up, 

and requests for reconsideration that contain mismatched SLOA data elements using Reply Code 

943 and clarifying remarks: “Discrete values for the Standard Line of Accounting (SLOA) data 

elements in the transaction do not match data elements from the SFIS Fund Code to Fund 

Account Conversion Table for the Fund Code cited in the transaction.” 

(4) The following table represents the relationship between SLOA relevant 

DLMS transactions and the means by which a rejection will be reported back due to a mismatch 

between the SFIS Fund Code to Fund Code Account Conversion Table for the Fund Code cited 

in the transaction. The yellow highlighted rows are accomplished through this DLMS change: 

SLOA Transactions Rejection Transaction 

DLMS 

Legacy DIC(s) 

Functionality DLMS 

Legacy DIC(s) 

Functionality Reject Code 

511R A0_/A3_/A4_ 870S AE9 CF 

511M AM_ 870S AE9 CF 

517M APR 870S AE9 CF 

869F AT_ 870S AE9 CF 

180M FTA/FTE/FTG 870M FTQ CF 

842A/W --- 842A/R --- 943 

810L F-series/G-series 824R --- BU 

856S AS6 824R --- BU 

867I D7_ 824R DZG BU 

940R A5J 824R --- BU 
Attachment to ADC 1043A 

Page 5 

(5) Apply administrative updates to reflect SLOA local codes are now migration 

codes, published in X12 version 7020, as represented in Enclosure 3. 

e. Revisions to DLM 4000.25 Manuals: 

(1) Modify DLM 4000.25, Volume 1 Appendix 2 to reflect the billed error 

mismatch with the SFIS Fund Account to Fund Conversion Table. 

BILLED ERROR. An error in a bill, at the bill or detail billing record level, which has one or 

more of the following characteristics: duplicates a previous bill or detail record; contains an error 

in amount; contains a SLOA data mismatch (discrete values for the SLOA data elements in the 

transaction do not match data elements from the SFIS Fund Code to Fund Account 

Conversion Table for the Fund Code in the transaction); assigns the wrong billed office, (i.e., 

designates the billed office in a manner that violates the requirements of Volume 4, Finance; was 

not billed under the proper method (noninterfund versus interfund); should not have been billed, 

(e.g., was nonreimburseable, the requisition was cancelled, or accessorial charge was 

inappropriate). 

(2) Modify DLM 4000.25, Volume 1 Appendix 3 ACRONYMS and 

ABBREVIATIONS to add “SLOA Standard Line of Accounting”. 

(3) Revise DLM 4000.25, Volume 4, Chapter 6 to include the edit for discrete 

SLOA elements in the transaction matching the SLOA elements for the SFIS Fund Code to Fund 

Account Conversion Table based on the fund code provided in the transaction: 

 C6.2.2.1.6. Discrete values for the Standard Line of Accounting data elements 

in the transaction match data elements from the SFIS Fund Code to Fund Account 

Conversion Table for the Fund Code in the transaction. 

(4) Modify DLM 4000.25-1, MILSTRIP Appendix 2.16 to add Status Code CF 

to the customer asset reporting status codes: 

 “CF Rejected. Discrete values for the Standard Line of Accounting (SLOA) data elements 

in the transaction do not match data elements from the SFIS Fund Code to Fund 

Account Conversion Table for the Fund Code in the transaction. (Use on DLMS 

870M/DIC FTQ.)”

(5) Revise DLM 4000.25, Volume 2, Appendix 3, Supply Discrepancy Report 

Relevant Data Elements, paragraph AP3.4 to include the new Discrepancy Status or Disposition 

(Reply) Code 943.

Reply Codes 

943 Transaction rejected. Standard Line of Accounting (SLOA) data elements do not 

match SFIS Fund Code to Fund Account Conversion Table. 
Attachment to ADC 1043A 

Page 6 

(6) Modify DLM 4000.25-2, MILSTRAP Appendix 2.8, and corresponding 

DLMS Data Dictionary for ASC X12 Data Element 1270 qualifier ET, Reject Advice Code, to 

add Reject Advice Code BU. 

BU Rejected. Discrete values for the SLOA data elements in the transaction do not match 

data elements from the SFIS Fund Code to Fund Account Conversion Table for the Fund 

Code cited in the transaction.

(7) Update DLM 4000.25, Volume 2, Chapter 4: 

“C4.2. PREPARATION OF REQUISITIONS. Requisitioning organizations must use the 

DLMS 511R, Requisition, to submit requisitions for all materiel requirements. Conformance 

with standard line of accounting (SLOA)/accounting classification requires any initiation of a 

financial business event to include SLOA mandated standard financial information system 

(SFIS) elements.[1] DLMS requisition transactions support inclusion of SLOA required 

elements. Pending full implementation of SLOA, DLA Transaction Services will facilitate 

interoperability by updating selected SLOA data fields based upon the requisitioner's 

Service/Agency and Fund Code. If discrete values for the SLOA data elements in the 

transaction do not match data elements from the SFIS Fund Code to Fund Account 

Conversion Table for the Fund Code in the transaction, reject with the DLMS 870S Supply 

Status citing Status Code CF.

---- 

[1] Refer to ADC 1043/ADC 1043A.”

(8) Revise DLM 4000.25, DLMS, Vol. 2, Chapter 8: 

C8.1.2. Materiel Obligation Reinstatement Request. This is a request by an organization to 

reinstate requisition(s) previously canceled due to that organization's nonresponse to an MOV 

request. Use the DLMS 517M, to reinstate previously canceled requisition(s). Conformance 

with standard line of accounting (SLOA)/accounting classification requires any initiation of a 

financial business event to include SLOA mandated standard financial information system 

(SFIS) elements.[1] The DLMS requisition reinstatement transaction supports inclusion of SLOA 

required elements. Pending full implementation of SLOA, DLA Transaction Services will 

facilitate interoperability by updating selected SLOA data fields based upon the requisitioner's 

Service/Agency and Fund Code. If discrete values for the SLOA data elements in the 

transaction do not match data elements from the SFIS Fund Code to Fund Account 

Conversion Table for the Fund Code in the transaction, reject with the DLMS 870S Supply 

Status citing Status Code CF.

---- 

[1] Refer to ADC 1043/ADC 1043A.” 
Attachment to ADC 1043A 

Page 7 

(9) Revise DLM 4000.25, DLMS, Vol. 2, Chapter 11: 

“ C11.9.1. Items Designated by a Supply Source for Automatic Return. DLMS 180M 

Automatic Return Notification is used for items by a source of supply for automatic return. 

Supply sources shall notify reporting activities of the location to which items so designated are to 

be shipped. Conformance with standard line of accounting (SLOA)/accounting classification 

requires any initiation of a financial business event to include SLOA mandated standard financial 

information system (SFIS) elements.[1] The DLMS shipment status for ICP/IMM-directed lateral 

redistribution supports inclusion of SLOA required elements. Pending full implementation of 

SLOA, DLA Transaction Services will facilitate interoperability by updating selected SLOA data 

fields based upon the returning activity’s Service/Agency and Fund Code. If discrete values for 

the SLOA data elements in the transaction do not match data elements from the SFIS Fund 

Code to Fund Account Conversion Table for the Fund Code in the transaction, reject with the 

DLMS 870M Materiel Returns Supply Status citing Status Code CF.

---- 

[1] Refer to ADC 1043/ADC1043A.”

[Intervening text not shown.] 

 “C11.17.3.3. Ensure Shipment. Ensure materiel is shipped, using DD Form 

1348-1A, to the activity identified in the LRO as the “ship-to” addressee. When the materiel is 

shipped, send DLMS 856S, Shipment Status (To ICP/IMM From Reporting Activities for LRO 

Shipments of Retail Assets), to the activity identified as the receiving activity in the LRO. The 

DLMS 856S shall must include the DoDAAC and fund code of the activity to which the credit 

for the materiel and reimbursement for the packing, crating, handling, and transportation 

(PCH&T) costs is to be provided; and Signal Code B and Distribution Code 2 or 3. 

Conformance with SLOA/accounting classification requires any initiation of a financial business 

event to include SLOA mandated standard financial information system (SFIS) elements.[1] The 

DLMS shipment status for ICP/IMM-directed lateral redistribution supports inclusion of SLOA 

required elements. Pending full implementation of SLOA, DLA Transaction Services will 

facilitate interoperability by updating selected SLOA data fields based upon the reporting 

activity’s Service/Agency and Fund Code. If discrete values for the SLOA data elements in the 

transaction do not match data elements from the SFIS Fund Code to Fund Account 

Conversion Table for the Fund Code in the transaction, reject with the DLMS 824R Reject 

Advice citing Reject Advice Code BU. Retail activities shall will use Uniform Materiel 

Movement and Issue Priority System (UMMIPS) time standards for processing LROs directed 

by the ICP/IMM. 

---- 

[1] Refer to ADC 1043/ADC 1043A.” 
Attachment to ADC 1043A 

Page 8 

(10) Revise DLM 4000.25, DLMS, Vol. 2, Chapter 14: 

“C14.2. ISSUE 

 C14.2.1. General 

 C14.2.1.1. This section provides a standard procedure for processing Issue 

information to owner/inventory control point (ICP) for the purpose of: 

 C14.2.1.1.1. Updating the owner/ICP record. 

 C14.2.1.1.2. Recording the appropriate financial transaction. Conformance 

with standard line of accounting (SLOA)/accounting classification requires any initiation of a 

financial business event to include SLOA mandated standard financial information system 

(SFIS) elements.[1] The DLMS issue transaction supports inclusion of SLOA required elements. 

Pending full implementation of SLOA, DLA Transaction Services will facilitate interoperability 

by updating selected SLOA data fields based upon the initiating activity’s Service/Agency and 

Fund Code. If discrete values for the SLOA data elements in the transaction do not match 

data elements from the SFIS Fund Code to Fund Account Conversion Table for the Fund 

Code in the transaction, reject with the DLMS 824R Reject Advice citing Reject Advice Code 

BU. 

---- 

[1] Refer to ADC 1043/ADC 1043A.” 

(11) Revise DLM 4000.25, DLMS, Vol. 2, Chapter 16: 

“C16.4.2. Requirements for Shipments of Hazardous Materiel and Hazardous Waste. The 

following guidance outlines basic documentation requirements for turn-in of Hazardous Materiel 

(HM), Hazardous Waste (HW), and other types of wastes (e.g., Polychlorinated Biphenyl 

(PCBs), Friable Asbestos, etc.). The turn-in activity will enter the bill-to fund code for 

reimbursable actions associated with the disposal, (e.g., HW contractor costs, in the DD Form 

1348-1A or DD Form 1348-2), in order to provide reimbursement to DLA Disposition Services. 

To ensure compliance with federal, state, DoD, and host nation regulations, turn-in activities will 

obtain and become familiar with applicable Code of Federal Regulations (CFR), state 

regulations, DoD regulations, and Overseas Environmental Baseline Guidance Documents 

(OEBGD), or the Final Governing Standards (FGS) for the host nation. When initiated 

electronically the HM/HW turn-in will be directed using the DLMS 940R, Disposal Release 

Order (DRO). Conformance with standard line of accounting (SLOA)/accounting classification 

requires any initiation of a financial business event to include SLOA mandated standard financial 

information system (SFIS) elements.[1] The DLMS DRO transaction supports inclusion of SLOA 

required elements. Pending full implementation of SLOA, DLA Transaction Services will 

facilitate interoperability by updating selected SLOA data fields based upon the initiator’s 

Service/Agency and Fund Code. If discrete values for the SLOA data elements in the 

transaction do not match data elements from the SFIS Fund Code to Fund Account 

Conversion Table for the Fund Code in the transaction, reject with the DLMS 824R Reject 

Advice citing Reject Advice Code BU. 

---- 

[1] Refer to ADC 1043/ADC 1043A.” 
Attachment to ADC 1043A 

Page 9 

(12) Revise DLM 4000.25, DLMS, Vol. 2, Chapter 17: 

“ C17.3.20.1.2. Edit SDR transactions in accordance with business rules 

specified below. Additionally, DoD WebSDR will edit SDRs to improve data consistency and 

the appropriateness of data content as follows:

[Intervening text not shown.] 

 “C17.3.20.1.2.6. If discrete values for the SLOA data elements in the 

transaction (new SDRs, correction, follow-up, and request for reconsideration) do not match 

data elements from the SFIS Fund Code to Fund Account Conversion Table for the Fund 

Code in the transaction, reject with the DLMS 842A/R SDR Reply citing Reply Code 943.

---- 

[1] Refer to ADC 1043/ADC 1043A.”

(13) See Enclosure 1 for modifications to DLMS 824R enabling the unique 

identification of rejected DLMS 940R transactions that fail the SLOA edit. 

f. Alternatives: When considering this change the authors decided to staff PDC 1043A 

recommending the DLMS 824R for almost all DLMS transactions with SLOA data (including 

the requisition related transactions) as the 824R provided a consistent approach for DLA 

Transaction Services to report edit failures back to the sender and the edit has no legacy 80 

column mapping impact. In the PDC an exception was made for the DLMS 842 A/R as the 

proper rejection of DLMS 842 A/W transactions, since it provides consistency with existing 900 

series Discrepancy Status or Disposition (Reply) Codes for system/application processing errors 

also used by WebSDR. As a result of valid Navy concerns (shown in comments resolution at 

Enclosure 2) about using the 824R vice the 870M and 870S for these SLOA rejections the 

original alternative approach is approved for implementation and procedures are documented 

herein. 

g. Proposed DLMS Change (PDC) 1043A Staffing Response/Comment Resolution: 

Concurrence and resolution of comments is shown at Enclosure 2. 

5. REASON FOR CHANGE: This change is needed to enable systems to receive notification 

for certain transactions when the discrete SLOA elements provided in transactions do not match 

the SLOA data in the entries in the SFIS Fund Code to Fund Code Account Conversion Table for 

the Fund Code in the transaction. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Ensures a requirement to reject transaction back to the sender when 

there is an inconsistency in the discrete SLOA data to the SFIS Fund Code to Fund Code 

Account Conversion Table. Notification of such inconsistencies at the earliest possible 

opportunity is important to ensure transactions are applied against the correct SLOA data. 

b. Disadvantages: None identified. 
Attachment to ADC 1043A 

Page 10 

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Staggered implementation 

will be permitted. The target implementation date for SLOA is September 30, 2014. 

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified. 

9. IMPACT: 

a. DLMS Data Elements/LOGDRMS: 

(1) Include Status Code CF as a valid customer asset reporting status code as 

described above. 

(2) Update Reject Advice Codes with new code BU as described above. 

(3) Update Discrepancy Status or Disposition (Reply) Codes with new Reply 

Code 943 as described above. 

b. Automated Information Systems (AIS): Modification to Military Service and 

Agency AIS is required to support the new rejection transaction scenarios. 

c. DLA Transaction Services:

(1) For DLMS transactions providing discrete SLOA data elements, DAAS will 

code additional rejection status transaction scenarios when there is a discrepancy between the 

SLOA data in the transaction versus the table. 

(2) For MILSINQ new reject advice code BU will have to be programmed as a 

new code U. See ADC 1103 regarding MILSINQ programing to ignore the first character in 

inserting the reject code in rp 4. 

(3) Update DOD WebSDR for interface with the SFIS Fund Code to Fund Code 

Account Conversion Table and rejection of inconsistent SLOA data content in SDRs. 
Enclosure 1, ADC 1043A 

page 1 

ENCLOSURE 1 

Revisions to DLMS 824R 

# Location DLMS 824R Reject Advice Reason 

1. Introductory 

Notes 

Add ADC 1043A to DLMS Introductory note 6: 

- ADC 1043A, Revised Procedures for Department of 

Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements 

Identifies changes 

included in DLMS 

IC. 

2. 2/OTI12/010 Add a second note to the DLMS Note for the data 

element: 

DLMS Note: 

1) Use to identify the Transaction Set Purpose Code from 

the Beginning Segment of the transaction being rejected. 

2) When the rejected transaction is a DLMS 940R, the 

following codes must be translated from 1/W0501/0200 

to their OTI12 equivalents: 

W0501 code N is equal to code 00 (zero, zero), 

W0501 code X is equal to code 77 (seven, seven) 

W0501 code Z is equal to code ZZ

In DLMS 940R, the 

element W0501 

provides the 

transaction purpose 

code that is equivalent 

to the more common 

purpose code of 

beginning segments, 

X12 data element 

353. However, codes 

in the 940R have to 

be converted to the 

equivalent code 

available at OTI12. 
Enclosure 2, ADC 1043A 

page 1 

ENCLOSURE 2 

Coordination/Comment Disposition 

# Component/ 

Agency 

Response/Comment Disposition 

1 DLA Concur. Noted. 

2 DLA Transaction 

Services 

Concur with comment. 

DLA Transaction Services does not 

populate OTI12 in 824. The customer is 

already provided X12 reference 

information in OTI08 and OTI09 to 

locate the specific transaction being 

rejected. There is no real value added 

from requiring populating OTI12.

Noted. 

The OTI12 was included to ensure clarity 

as to the type of originating transaction 

being rejected. The reference information 

cited is available in the recipient’s system 

that created the transaction envelop for the 

rejected transaction, which is not 

necessarily the same application that the 

ultimate user is accessing the received 

824R error message information. This 

sub-optimally assumes the user ultimately 

receiving the error message has access to 

the outbound transaction information. 

DLA Transaction Services agreed to apply 

this change. 

3 Marine Corps Concur. Noted. 

4 AFAFO Concur. Noted. 
Enclosure 2 to ADC 1043 

Page 2 

# Component/ 

Agency 

Response/Comment Disposition 

5 Navy Navy ERP disagrees with the use of an 

824 transaction to provide reject status to 

customer orders. Without recoding an 

interface, this will cause the Navy much 

manual effort. The Navy has automation 

in place to process 870S transactions and 

update the orders in our system. This 

allows end-users to review their orders 

and see the status (being fulfilled, 

backordered, cancelled, etc.). We do not 

currently have any automated method of 

utilizing 824 transactions to update 

orders since they don't contain the 

identifying information needed to match 

them up with an outbound DLMS 

transaction. The current process requires 

parsing text strings in Excel to see what 

DOCIDs are being rejected and what the 

cause for the rejection is. While this 

works fine for the small number of 

rejects we receive today (which are just 

checked to see if there is any new critical 

problem occurring, otherwise they are 

mostly trailer records that dropped off), 

this will not work for end-users to keep 

track of the status of their orders. We 

consider rejected orders to be a critical 

problem that needs to be reviewed 

immediately. It would be possible to 

design a new set of interface logic that 

would process the subset of 824s that 

contain requisition reject information. 

However this still does not seem optimal. 

How would the rejected status be 

displayed in the various tools that 

customers use to check on their status in 

DAAS reports? How would parties that 

receive copies of status in other than the 

sending system know that the requisition 

had been rejected? Would the BU status 

then have to be sent by the system that 

received the 824?

Noted. ADC adjusted above to the 

alternative approach from the PDC. 
Enclosure 3, ADC 1043A 

page 1 

ENCLOSURE 3 

Administrative Update for Approved X12 Migration Codes 

# Location 180M Material Returns Reporting Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043A 

- ADC 1043A, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements 

Identifies DLMS Changes 

included in the DLMS IC 

2. 2/FA201/226 Modify DLMS notes for the following existing 

qualifiers: 

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 2f. 

3. Qualifier AI is a migration code approved for use 

in X12 version 7020.At this time a local code ‘AI’ 

is established for use in the 180M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘AI-Activity Identifier’ in a future 

version. 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting 

Classification use to identify “Business Event Type 

Code”. Refer to ADC 1043. 

2. Business Event Type Code is a potential future 

DLMS enhancement; see introductory DLMS note 

2a. 

3. Qualifier BE is a migration code approved for use 

in X12 version 7020.A local code ‘BE’ is 

established for use in the 180M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘BE- Business Event type Code’ 

in a future version. 

CC Cost Center Identifier 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Center Identifier”. Refer to ADC 

1043. 

Administrative update to 

reflect local codes are now 

migration codes, available 

in X12 standard 7020. 
Enclosure 3 to ADC 1043A 

Page 2 

# Location 180M Material Returns Reporting Reason 

2/FA201/226 2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. Qualifier CC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘CC’ 

is established for use in the 180M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘CC-Cost Center Identifier’ in a 

future version. 

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 2f. 

3. Qualifier FA is a migration code approved for use 

in X12 version 7020.A local code ‘FA’ is 

established for use in the 180M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘FA-Functional Area’ in a future 

version. 

FC Funding Center Identifier 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Funding Center Identifier”. Refer to 

ADC 1043. 

2. A local code ‘FC’ is established for use in the 

180M, version 4010. A data maintenance action 

has been submitted for establishment of ‘FCFunding Center Identifier’ in a future version. 

23. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

3. Qualifier FC is a migration code approved for 

use in X12 version 7020. 

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 2f. 

3. Qualifier IA is a migration code approved for use 

in X12 version 7020.A local code ‘IA’ is 
Enclosure 3 to ADC 1043A 

Page 3 

# Location 180M Material Returns Reporting Reason 

2/FA201/226 established for use in the 180M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘IA- Security Cooperation 

Implementing Agency’ in a future version. 

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 

2d. 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.A local code ‘S1’ is 

established for use in the 180M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘S1- Security Cooperation 

Customer Code’ in a future version. 

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 2f. 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.A local code ‘S2’ is 

established for use in the 180M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘S2- Security Cooperation Case 

Designator’ in a future version. 

WO Work Order Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Work Order Number”. This is the Work 

Order Number applicable to the original 

requirement for the materiel being returned. Refer 
Enclosure 3 to ADC 1043A 

Page 4 

# Location 180M Material Returns Reporting Reason 

2/FA201/226 to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

Qualifier WO is a migration code approved for use in 

X12 version 7020.A local code ‘WO’ is established for 

use in the 180M, version 4010. A data maintenance 

action has been submitted for establishment of ‘WOWork Order Number’ in a future version. 

YB Beginning Period of Availability Fiscal Year 

Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. Qualifier YB is a migration code approved for use 

in X12 version 7020.A local code ‘YB’ is 

established for use in the 180M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YB- Beginning Period of 

Availability Fiscal Year Date’ in a future version. 

YE Ending Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Ending Period of Availability Fiscal Year 

Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. Qualifier YE is a migration code approved for use 

in X12 version 7020.A local code ‘YE’ is 

established for use in the 180M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YE- Ending Period of 

Availability Fiscal Year Date’ in a future version.

# Location 511M Requisition Modifier Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043A 

- ADC 1043A, Revised Procedures for Department of 

Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements

Identifies DLMS 

Changes included in the 

DLMS IC 
Enclosure 3 to ADC 1043A 

Page 5 

# Location 511M Requisition Modifier Reason 

2. 2/FA201/286 Modify DLMS notes for the following existing 

qualifiers: 

AI Activity Identifier 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Activity Identifier”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

3. Qualifier AI is a migration code approved for use 

in X12 version 7020.At this time a local code ‘AI’ is 

established for use in the 511M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘AI-Activity Identifier’ in a future 

version. 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify, or to modify, “Business Event Type 

Code”. Refer to ADC 1043. 

2. Business Event Type Code is a potential future 

DLMS enhancement; see introductory DLMS note 

3a. 

3. Qualifier BE is a migration code approved for use 

in X12 version 7020.A local code ‘BE’ is established 

for use in the 511M, version 4010. A data 

maintenance action has been submitted for 

establishment of ‘BE- Business Event Type Code’ in 

a future version. 

CC Cost Center Identifier 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Cost Center Identifier”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

3. Qualifier CC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘CC’ 

is established for use in the 511M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘CC-Cost Center Identifier’ in a 

future version. 

Administrative update to 

reflect local codes are 

now migration codes, 

available in X12 standard 

7020. 
Enclosure 3 to ADC 1043A 

Page 6 

# Location 511M Requisition Modifier Reason 

2/FA201/286 

FA Functional Area 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Functional Area”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

3. Qualifier FA is a migration code approved for use 

in X12 version 7020.At this time a local code ‘FA’ is 

established for use in the 511M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘FA-Functional Area’ in a future 

version. 

FC Funding Center Identifier 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Funding Center Identifier”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

3. Qualifier FC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘FC’ is 

established for use in the 511M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘FC-Funding Center Identifier’ in a 

future version. 

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

3. Qualifier IA is a migration code approved for use 

in X12 version 7020.A local code ‘IA’ is established 

for use in the 511M, version 4010. A data 

maintenance action has been submitted for 

establishment of ‘IA- Security Cooperation 

Implementing Agency’ in a future version. 

S1 Security Cooperation Customer Code 

DLMS Note: 
Enclosure 3 to ADC 1043A 

Page 7 

# Location 511M Requisition Modifier Reason 

2/FA201/286 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.A local code ‘S1’ is established 

for use in the 511M, version 4010. A data 

maintenance action has been submitted for 

establishment of ‘S1- Security Cooperation 

Customer Code’ in a future version. 

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 3g. 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.A local code ‘S2’ is established 

for use in the 511M, version 4010. A data 

maintenance action has been submitted for 

establishment of ‘S2- Security Cooperation Case 

Designator’ in a future version. 

WO Work Order Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Work Order Number”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

3. Qualifier WO is a migration code approved for use 

in X12 version 7020.At this time a local code ‘WO’ 

is established for use in the 511M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘WO-Work Order Number’ in a 

future version. 
Enclosure 3 to ADC 1043A 

Page 8 

# Location 511M Requisition Modifier Reason 

YB Beginning Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Beginning Period of 

Availability Fiscal Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

3. Qualifier YB is a migration code approved for use 

in X12 version 7020.A local code ‘YB’ is 

established for use in the 511M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YB- Beginning Period of 

Availability Fiscal Year Date’ in a future version. 

YE Ending Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Ending Period of 

Availability Fiscal Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

3. Qualifier YE is a migration code approved for use 

in X12 version 7020.A local code ‘YE’ is 

established for use in the 511M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YE- Ending Period of Availability 

Fiscal Year Date’ in a future version.

# Location 511R Requisition Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043A 

- ADC 1043A, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements

Identifies DLMS 

Changes included in 

the DLMS IC 

2. 2/FA201/286 Modify DLMS notes for the following existing 

qualifiers: 

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 

Administrative update 

to reflect local codes 

are now migration 

codes, available in 

X12 standard 7020. 
Enclosure 3 to ADC 1043A 

Page 9 

# Location 511R Requisition Reason 

2/FA201/286 in X12 version 7020.At this time a local code ‘AI’ 

is established for use in the 511R, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘AI-Activity Identifier’ in a future 

version. 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify, or to modify, “Business Event Type 

Code”. Refer to ADC 1043. 

2. Business Event type Code is a potential future 

DLMS enhancement; see introductory DLMS note 

3a. 

3. Qualifier BE is a migration code approved for use 

in X12 version 7020.A local code ‘BE’ is 

established for use in the 511R, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘BE- Business Event Type Code’ 

in a future version. 

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. 

3. Qualifier CC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘CC’ 

is established for use in the 511R, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘CC-Cost Center Identifier’ in a 

future version. 

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.At this time a local code ‘FA’ 

is established for use in the 511R, version 4010. A 

data maintenance action has been submitted for 
Enclosure 3 to ADC 1043A 

Page 10 

# Location 511R Requisition Reason 

2/FA201/286 establishment of ‘FA-Functional Area’ in a future 

version. 

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.At this time a local code ‘FC’ 

is established for use in the 511R, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘FC-Funding Center Identifier’ in a 

future version. 

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.A local code ‘IA’ is 

established for use in the 511R, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘IA- Security Cooperation 

Implementing Agency’ in a future version. 

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.A local code ‘S1’ is 

established for use in the 511R, version 4010. A 

data maintenance action has been submitted for 
Enclosure 3 to ADC 1043A 

Page 11 

# Location 511R Requisition Reason 

2/FA201/286 establishment of ‘S1- Security Cooperation 

Customer Code’ in a future version. 

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.A local code ‘S2’ is 

established for use in the 511R, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘S2- Security Cooperation Case 

Designator’ in a future version. 

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.At this time a local code ‘WO’ 

is established for use in the 511R, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘WO-Work Order Number’ in a 

future version. 

YB Beginning Period of Availability Fiscal Year 

Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

3. Qualifier YB is a migration code approved for use 

in X12 version 7020.A local code ‘YB’ is 

established for use in the 511R, version 4010. A 
Enclosure 3 to ADC 1043A 

Page 12 

# Location 511R Requisition Reason 

2/FA201/286 data maintenance action has been submitted for 

establishment of ‘YB- Beginning Period of 

Availability Fiscal Year Date’ in a future version. 

YE Ending Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Ending Period of Availability Fiscal Year 

Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

3. Qualifier YE is a migration code approved for use 

in X12 version 7020.A local code ‘YE’ is 

established for use in the 511R, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘Yr- Ending Period of Availability 

Fiscal Year Date’ in a future version.

# Location 517M Material Obligation Validation Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043A 

- ADC 1043A, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements

Identifies DLMS 

Changes included in 

the DLMS IC 

2. 2/FA201/136 Modify DLMS notes for the following existing 

qualifiers: 

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.At this time a local code ‘AI’ 

is established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘AI-Activity Identifier’ in a future 

version. 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify, or to modify, “Business Event Type 

Administrative update 

to reflect local codes 

are now migration 

codes, available in 

X12 standard 7020. 
Enclosure 3 to ADC 1043A 

Page 13 

# Location 517M Material Obligation Validation Reason 

2/FA201/136 

Code”. Refer to ADC 1043. 

2. Business Event Type Code is a potential future 

DLMS enhancement; see introductory DLMS note 

3a. 

3. Qualifier BE is a migration code approved for use 

in X12 version 7020.A local code ‘BE’ is 

established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘BE – Business Event Type Code’ 

in a future version. 

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. 

3. Qualifier CC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘CC’ 

is established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘CC-Cost Center Identifier’ in a 

future version. 

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.At this time a local code ‘FA’ 

is established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘FA-Functional Area’ in a future 

version. 

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. 
Enclosure 3 to ADC 1043A 

Page 14 

# Location 517M Material Obligation Validation Reason 

2/FA201/136 

3. Qualifier FC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘FC’ 

is established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘FC-Funding Center Identifier’ in a 

future version. 

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.A local code ‘IA’ is 

established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘IA- Security Cooperation 

Implementing Agency’ in a future version. 

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.A local code ‘S1’ is 

established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘S1- Security Cooperation 

Customer Code’ in a future version. 

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 
Enclosure 3 to ADC 1043A 

Page 15 

# Location 517M Material Obligation Validation Reason 

2/FA201/136 

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.A local code ‘S2’ is 

established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘S2- Security Cooperation Case 

Designator’ in a future version. 

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.At this time a local code ‘WO’ 

is established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘WO-Work Order Number’ in a 

future version. 

YB Beginning Period of Availability Fiscal Year 

Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

3. Qualifier YB is a migration code approved for use 

in X12 version 7020.A local code ‘YB’ is 

established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YB- Beginning Period of 

Availability Fiscal Year Date’ in a future version. 

YE Ending Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Ending Period of Availability Fiscal Year 

Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 
Enclosure 3 to ADC 1043A 

Page 16 

# Location 517M Material Obligation Validation Reason 

2/FA201/136 

DLMS note 3f. 

3. Qualifier YE is a migration code approved for use 

in X12 version 7020.A local code ‘YE’ is 

established for use in the 517M, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YE- Ending Period of Availability 

Fiscal Year Date’ in a future version.

# Location 810L Logistics Bill Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043A 

- ADC 1043A, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements

Identifies DLMS 

Changes included in 

the DLMS IC 

2. 1/FA201/300 Modify DLMS notes for the following existing 

qualifiers: 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify, or to modify, “Business Event Type 

Code”. Refer to ADC 1043. 

2. Used in association with the billing office line of 

accounting (Qualifier 58). 

3. Business Event Type Code is a potential future 

DLMS enhancement; see introductory DLMS note 

6a. 

4. Qualifier BE is a migration code approved for use 

in X12 version 7020.A local code ‘BE’ is 

established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘BE- Business Event Type Code’ 

in a future version. 

YB Beginning Period of Availability Fiscal Year 

Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043. 

2. Used in association with the billing office line of 

accounting (Qualifier 58). 

3. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

Administrative update 

to reflect local codes 

are now migration 

codes, available in 

X12 standard 7020. 
Enclosure 3 to ADC 1043A 

Page 17 

# Location 810L Logistics Bill Reason 

1/FA201/300 4. Qualifier YB is a migration code approved for use 

in X12 version 7020.A local code ‘YB’ is 

established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YB- Beginning Period of 

Availability Fiscal Year Date’ in a future version. 

YE Ending Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Ending Period of Availability Fiscal Year 

Date”. Refer to ADC 1043. 

2. Used in association with the billing office line of 

accounting (Qualifier 58). 

3. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

4. Qualifier YE is a migration code approved for use 

in X12 version 7020.A local code ‘YE’ is 

established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YE- Ending Period of Availability 

Fiscal Year Date’ in a future version. 

3. 2/FA201/360 Modify DLMS notes for the following existing 

qualifiers: 

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

3. Qualifier AI is a migration code approved for use 

in X12 version 7020.At this time a local code ‘AI’ 

is established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘AI-Activity Identifier’ in a future 

version. 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify, or to modify, “Business Event Type 

Code”. Refer to ADC 1043. 

2. Business Event Type Code is a potential future 

DLMS enhancement; see introductory DLMS note 

Administrative update 

to reflect local codes 

are now migration 

codes, available in 

X12 standard 7020. 
Enclosure 3 to ADC 1043A 

Page 18 

# Location 810L Logistics Bill Reason 

2/FA201/360 6a. 

3. Qualifier BE is a migration code approved for use 

in X12 version 7020.A local code ‘BE’ is 

established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘BE- Business Event Type Code’ 

in a future version. 

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

3. Qualifier CC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘CC’ 

is established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘CC-Cost Center Identifier’ in a 

future version. 

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

3. Qualifier FA is a migration code approved for use 

in X12 version 7020.At this time a local code ‘FA’ 

is established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘FA-Functional Area’ in a future 

version. 

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

3. Qualifier FC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘FC’ 

is established for use in the 810L, version 4010. A 
Enclosure 3 to ADC 1043A 

Page 19 

# Location 810L Logistics Bill Reason 

2/FA201/360 data maintenance action has been submitted for 

establishment of ‘FC-Funding Center Identifier’ in a 

future version. 

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

3. Qualifier IA is a migration code approved for use 

in X12 version 7020.A local code ‘IA’ is 

established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘IA- Security Cooperation 

Implementing Agency’ in a future version. 

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. Authorized DLMS enhancement; see introductory 

DLMS note 6d. 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.A local code ‘S1’ is 

established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘S1- Security Cooperation 

Customer Code’ in a future version. 

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 6e. A field size exceeding 3 positions 

is not supportable under current MILSTRIP 

processes. Four character codes are not authorized 

at this time. 
Enclosure 3 to ADC 1043A 

Page 20 

# Location 810L Logistics Bill Reason 

2/FA201/360 3. Qualifier S2 is a migration code approved for use 

in X12 version 7020.A local code ‘S2’ is 

established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘S2- Security Cooperation Case 

Designator’ in a future version. 

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

3. Qualifier WO is a migration code approved for use 

in X12 version 7020.At this time a local code ‘WO’ 

is established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘WO-Work Order Number’ in a 

future version. 

YB Beginning Period of Availability Fiscal Year 

Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

3. Qualifier YB is a migration code approved for use 

in X12 version 7020.A local code ‘YB’ is 

established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YB- Beginning Period of 

Availability Fiscal Year Date’ in a future version. 

YE Ending Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Ending Period of Availability Fiscal Year 

Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

3. Qualifier YE is a migration code approved for use 

in X12 version 7020.A local code ‘YE’ is 
Enclosure 3 to ADC 1043A 

Page 21 

# Location 810L Logistics Bill Reason 

established for use in the 810L, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YE- Ending Period of Availability 

Fiscal Year Date’ in a future version.

# Location 842 A/W Supply Discrepancy Report Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043A 

- ADC 1043A, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements

Identifies DLMS 

Changes included in 

the DLMS IC 

6. 2/FA201/1360 

2/FA201/1360 

Modify DLMS notes for the following existing 

qualifiers: 

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

3. Qualifier AI is a migration code approved for use 

in X12 version 7020.At this time a local code ‘AI’ 

is established for use in the 842A/W, version 4030. 

A data maintenance action has been submitted for 

establishment of ‘AI-Activity Identifier’ in a future 

version. 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting 

Classification use to identify, or to modify, 

“Business Event Type Code”. Refer to ADC 1043. 

2. Business Event Type Code is a potential future 

DLMS enhancement. Components must 

coordinate requirements and business rules with 

DLA Logistics Management Standards Office 

prior to use. 

3. Qualifier BE is a migration code approved for use 

in X12 version 7020.A local code ‘BE’ is 

established for use in the 842A/W, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘BE – Business Event Type Code’ 

in a future version. 

Administrative update 

to reflect local codes 

are now migration 

codes, available in 

X12 standard 7020. 
Enclosure 3 to ADC 1043A 

Page 22 

# Location 842 A/W Supply Discrepancy Report Reason 

2/FA201/1360 

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

3. Qualifier CC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘CC’ 

is established for use in the 842A/W, version 4030. 

A data maintenance action has been submitted for 

establishment of ‘CC-Cost Center Identifier’ in a 

future version. 

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

3. Qualifier FA is a migration code approved for use 

in X12 version 7020.At this time a local code ‘FA’ 

is established for use in the 842A/W, version 4030. 

A data maintenance action has been submitted for 

establishment of ‘FA-Functional Area’ in a future 

version. 

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

3. Qualifier FC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘FC’ 

is established for use in the 842A/W, version 4030. 

A data maintenance action has been submitted for 

establishment of ‘FC-Funding Center Identifier’ in 

a future version. 

WO Work Order Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Work Order Number”. Refer to ADC 
Enclosure 3 to ADC 1043A 

Page 23 

# Location 842 A/W Supply Discrepancy Report Reason 

2/FA201/1360 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

3. Qualifier WO is a migration code approved for 

use in X12 version 7020.At this time a local code 

‘WO’ is established for use in the 842A/W, version 

4030. A data maintenance action has been 

submitted for establishment of ‘WO-Work Order 

Number’ in a future version. 

YB Beginning Period of Availability Fiscal Year 

Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

3. Qualifier YB is a migration code approved for use 

in X12 version 7020.A local code ‘YB’ is 

established for use in the 842A/W, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘YB- Beginning Period of 

Availability Fiscal Year Date’ in a future version. 

YE Ending Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Ending Period of Availability Fiscal Year 

Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

3. Qualifier YE is a migration code approved for use 

in X12 version 7020.A local code ‘YE’ is 

established for use in the 842A/W, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘YE- Ending Period of 

Availability Fiscal Year Date’ in a future version. 
Enclosure 3 to ADC 1043A 

Page 24 

# Location 856S Ship Notice/Manifest Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043A 

- ADC 1043A, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements

Identifies DLMS 

Changes included in the 

DLMS IC. 

2. 2/REF01/1500 Modify DLMS notes for the following existing 

qualifiers: 

AGY Agency DispersingDisbursing Identifier Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Agency DispersingDisbursing Identifier 

Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. Qualifier AGY is a migration code approved for 

use in X12 version 7020.A local code ‘AGY’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘AGY-Agency Dispersing 

Identifier Code’ in a future version. 

AGZ Agency Accounting Identifier 

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 2f. 

3. Qualifier AGZ is a migration code approved for 

use in X12 version 7020.A local code ‘AGZ’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘AGZ-Agency Accounting 

Identifier’ in a future version. 

AVT Availability Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Availability Type”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. Qualifier AVT is a migration code approved for 

use in X12 version 7020.A local code ‘AVT’ is 

Administrative update to 

reflect local codes are 

now migration codes, 

available in X12 

standard 7020. Correct 

“Dispersing” to 

“Disbursing”. 
Enclosure 3 to ADC 1043A 

Page 25 

# Location 856S Ship Notice/Manifest Reason 

2/REF01/1500 established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘AVT-Availability Type’ in a 

future version. 

BET Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify “Business Event Type Code”. Refer 

to ADC 1043. 

2. Business Event Type Code is a potential future 

DLMS enhancement; see introductory DLMS note 

2a. 

3. Qualifier BET is a migration code approved for 

use in X12 version 7020.A local code ‘BET’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘BET-Business Event Type Code’ 

in a future version. 

BLI Budget Line Item 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Budget Line Item”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. Qualifier BLI is a migration code approved for use 

in X12 version 7020.A local code ‘BLI’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘BLI-Budget Line Item’ in a future 

version. 

MAT Main Account 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Main Account”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. Qualifier MAT is a migration code approved for 

use in X12 version 7020.A local code ‘MAT’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘MAT-Main Account’ in a future 

version. 
Enclosure 3 to ADC 1043A 

Page 26 

# Location 856S Ship Notice/Manifest Reason 

REB Reimbursable Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Reimbursable Flag”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. Qualifier REB is a migration code approved for 

use in X12 version 7020.A local code ‘REB’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘REB-Reimbursable Code’ in a 

future version. 

SAT Sub Account 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Sub Account”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. Qualifier SAT is a migration code approved for 

use in X12 version 7020.A local code ‘SAT’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘SAT-Sub Account’ in a future 

version. 

SBA Sub Allocation 

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 2f. 

3. Qualifier SBA is a migration code approved for 

use in X12 version 7020.A local code ‘SBA’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘SBA-Sub-Allocation’ in a future 

version. 

SCC Security Cooperation Customer Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Security Cooperation Customer Code”. 
Enclosure 3 to ADC 1043A 

Page 27 

# Location 856S Ship Notice/Manifest Reason 

Refer to ADC 1043. 

2. DLMS enhancement; see introductory DLMS note 

2d. 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 SCC is a migration code approved for 

use in X12 version 7020.A local code ‘SCC’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘SCC- Security Cooperation 

Customer Code’ in a future version. 

SCI 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 2f. A field size exceeding 3 positions 

is not supportable under current MILSTRIP 

processes. Four character codes are not authorized 

at this time. 

3. Qualifier SCI is a migration code approved for use 

in X12 version 7020.A local code ‘IA’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘SCI- Security Cooperation 

Implementing Agency’ in a future version. 

SCL Sub Class 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify “Sub Class”. Refer to ADC 1043. 

2. Sub Class is a potential future DLMS enhancement; 

see introductory DLMS note 2a. 

3. Qualifier SCL is a migration code approved for 

use in X12 version 7020.A local code ‘SCL’ is 

established for use in the 856S, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘SCL-Sub Class’ in a future 

version. 

# Location 867I Issue Reason 
Enclosure 3 to ADC 1043A 

Page 28 

# Location 867I Issue Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043A 

- ADC 1043A, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements

Identifies DLMS 

Changes included in 

the DLMS IC 

2. 2/FA201/350 Modify DLMS notes for the following existing 

qualifiers: 

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

3. At this time a local code ‘AI’ is established for use 

in the 867I, version 4010. A data maintenance 

action has been submitted for establishment of ‘AIActivity Identifier’ in a future version. 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify, or to modify, “Business Event Type 

Code”. Refer to ADC 1043. 

2. Business Event Type Code is a potential future 

DLMS enhancement; see introductory DLMS note 

5a. 

3. A local code ‘BE’ is established for use in the 867I, 

version 4010. A data maintenance action has been 

submitted for establishment of ‘BE – Business 

Event Type Code’ in a future version. 

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

3. At this time a local code ‘CC’ is established for use 

in the 867I, version 4010. A data maintenance 

action has been submitted for establishment of ‘CCCost Center Identifier’ in a future version. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA. 
Enclosure 3 to ADC 1043A 

Page 29 

# Location 867I Issue Reason 

2/FA201/350 

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

3. At this time a local code ‘FA’ is established for use 

in the 867I, version 4010. A data maintenance 

action has been submitted for establishment of ‘FAFunctional Area’ in a future version. 

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

3. At this time a local code ‘FC’ is established for use 

in the 867I, version 4010. A data maintenance 

action has been submitted for establishment of ‘FCFunding Center Identifier’ in a future version. 

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

3. A local code ‘IA’ is established for use in the 867I, 

version 4010. A data maintenance action has been 

submitted for establishment of ‘IA- Security 

Cooperation Implementing Agency’ in a future 

version. 

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 

5d. A field size exceeding 2 positions is not 

supportable under current MILSTRIP and MAPAC 

processes. Three character codes are not authorized 
Enclosure 3 to ADC 1043A 

Page 30 

# Location 867I Issue Reason 

at this time. 

3. A local code ‘S1’ is established for use in the 867I, 

version 4010. A data maintenance action has been 

submitted for establishment of ‘S1- Security 

Cooperation Customer Code’ in a future version. 

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 5e. A field size exceeding 3 positions 

is not supportable under current MILSTRIP 

processes. Four character codes are not authorized 

at this time. 

3. A local code ‘S2’ is established for use in the 867I, 

version 4010. A data maintenance action has been 

submitted for establishment of ‘S2- Security 

Cooperation Case Designator’ in a future version. 

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

3. At this time a local code ‘WO’ is established for use 

in the 867I, version 4010. A data maintenance 

action has been submitted for establishment of 

‘WO-Work Order Number’ in a future version. 

YB Beginning Period of Availability Fiscal Year 

Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

3. Qualifier YB is a migration code approved for use 

in X12 version 7020.A local code ‘YB’ is 

established for use in the 867I, version 4010. A data 

maintenance action has been submitted for 
Enclosure 3 to ADC 1043A 

Page 31 

# Location 867I Issue Reason 

establishment of ‘YB- Beginning Period of 

Availability Fiscal Year Date’ in a future version. 

YE Ending Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Ending Period of Availability Fiscal Year 

Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

3. A local code ‘YE’ is established for use in the 867I, 

version 4010. A data maintenance action has been 

submitted for establishment of ‘YE- Ending Period 

of Availability Fiscal Year Date’ in a future version. 

# Location 869F Requisition Follow-Up Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043A 

- ADC 1043A, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements

Identifies DLMS 

Changes included in 

the DLMS IC 

2. 2/FA201/200 Modify DLMS notes for the following existing 

qualifiers: 

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 4g. 

3. Qualifier AI is a migration code approved for use 

in X12 version 7020.At this time a local code ‘AI’ 

is established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘AI-Activity Identifier’ in a future 

version. 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify, or to modify, “Business Event Type 

Code”. Refer to ADC 1043. 

2. Business Event Type Code is a potential future 

Administrative update 

to reflect local codes 

are now migration 

codes, available in 

X12 standard 7020. 
Enclosure 3 to ADC 1043A 

Page 32 

# Location 869F Requisition Follow-Up Reason 

2/FA201/200 

DLMS enhancement; see introductory DLMS note 

4a. 

3. Qualifier BE is a migration code approved for use 

in X12 version 7020.A local code ‘BE’ is 

established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘BE – Business Event Type Code’ 

in a future version. 

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 4g. 

3. Qualifier CC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘CC’ 

is established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘CC-Cost Center Identifier’ in a 

future version. 

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 4g. 

3. Qualifier FA is a migration code approved for use 

in X12 version 7020.At this time a local code ‘FA’ 

is established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘FA-Functional Area’ in a future 

version. 

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 4g. 

3. Qualifier FC is a migration code approved for use 

in X12 version 7020.At this time a local code ‘FC’ 
Enclosure 3 to ADC 1043A 

Page 33 

# Location 869F Requisition Follow-Up Reason 

is established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘FC-Funding Center Identifier’ in a 

future version. 

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 4g. 

3. Qualifier IA is a migration code approved for use 

in X12 version 7020.A local code ‘IA’ is 

established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘IA- Security Cooperation 

Implementing Agency’ in a future version. 

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 

4d. 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.A local code ‘S1’ is 

established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘S1- Security Cooperation 

Customer Code’ in a future version. 

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 4g. A field size exceeding 3 positions 

is not supportable under current MILSTRIP 

processes. Four character codes are not authorized 
Enclosure 3 to ADC 1043A 

Page 34 

# Location 869F Requisition Follow-Up Reason 

at this time. 

3. Qualifier S2 is a migration code approved for use 

in X12 version 7020.A local code ‘S2’ is 

established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘S2- Security Cooperation Case 

Designator’ in a future version. 

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 4g. 

3. Qualifier WO is a migration code approved for use 

in X12 version 7020.At this time a local code ‘WO’ 

is established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘WO-Work Order Number’ in a 

future version. 

YB Beginning Period of Availability Fiscal Year 

Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

3. Qualifier YB is a migration code approved for use 

in X12 version 7020.A local code ‘YB’ is 

established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YB- Beginning Period of 

Availability Fiscal Year Date’ in a future version. 

YE Ending Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Ending Period of Availability Fiscal Year 

Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

3. Qualifier YE is a migration code approved for use 
Enclosure 3 to ADC 1043A 

Page 35 

# Location 869F Requisition Follow-Up Reason 

in X12 version 7020.A local code ‘YE’ is 

established for use in the 869F, version 4010. A 

data maintenance action has been submitted for 

establishment of ‘YE- Ending Period of Availability 

Fiscal Year Date’ in a future version. 

# Location 940R Material Release Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043A 

- ADC 1043A, Revised Procedures for Department of 

Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Support 

Transaction Rejection Requirements 

Identifies DLMS 

Changes included in the 

DLMS IC 

2. 2/FA201/3000 Add the following qualifiers and DLMS notes: 

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 4f. 

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

X12 version 7020.At this time a local code ‘AI’ is 

established for use in the 842A/W, version 4030. A 

data maintenance action has been submitted for 

establishment of ‘AI-Activity Identifier’ in a future 

version. 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify, or to modify, “Business Event Type 

Code”. Refer to ADC 1043. 

2. Business Event Type Code is a potential future 

DLMS enhancement; see introductory DLMS note 4a. 

3. Qualifier BE is a migration code approved for use in 

X12 version 7020.A local code ‘BE’ is established for 

use in the 940R, version 4030. A data maintenance 

action has been submitted for establishment of ‘BE – 

Business Event Type Code’ in a future version. 

CC Cost Center Identifier 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

These qualifiers have 

been mapped to specific 

SFIS data elements for 

SLOA. 
Enclosure 3 to ADC 1043A 

Page 36 

# Location 940R Material Release Reason 

2/FA201/3000 

identify “Cost Center Identifier”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

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

X12 version 7020.At this time a local code ‘CC’ is 

established for use in the 940R, version 4030. A data 

maintenance action has been submitted for 

establishment of ‘CC-Cost Center Identifier’ in a 

future version. 

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 4f. 

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

X12 version 7020.At this time a local code ‘FA’ is 

established for use in the 940R, version 4030. A data 

maintenance action has been submitted for 

establishment of ‘FA-Functional Area’ in a future 

version. 

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 4f. 

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

X12 version 7020.At this time a local code ‘FC’ is 

established for use in the 940R, version 4030. A data 

maintenance action has been submitted for 

establishment of ‘FC-Funding Center Identifier’ in a 

future version. 

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 4f. 
Enclosure 3 to ADC 1043A 

Page 37 

# Location 940R Material Release Reason 

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

X12 version 7020.A local code ‘IA’ is established for 

use in the 940R, version 4030. A data maintenance 

action has been submitted for establishment of ‘IASecurity Cooperation Implementing Agency’ in a 

future version. 

P5 Security Cooperation Case Line Item Identifier 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Security Cooperation Case Line Item 

Identifier”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

3. Qualifier P5 is a migration code approved for use in 

X12 version 7020.A local code ‘P5’ is established for 

use in the 940R, version 4030. A data maintenance 

action has been submitted for establishment of ‘P5- 

Security Cooperation Case Line Item Identifier’ in a 

future version. 

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 

4d. 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.A local code ‘S1’ is established for 

use in the 940R, version 4030. A data maintenance 

action has been submitted for establishment of ‘S1- 

Security Cooperation Customer Code’ in a future 

version. 

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 4f. A field size exceeding 3 positions is 
Enclosure 3 to ADC 1043A 

Page 38 

# Location 940R Material Release Reason 

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.A local code ‘S2’ is established for 

use in the 940R, version 4030. A data maintenance 

action has been submitted for establishment of ‘S2- 

Security Cooperation Case Designator’ in a future 

version. 

WO Work Order Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Work Order Number”. Refer to PDC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

3. Qualifier WO is a migration code approved for use 

in X12 version 7020.At this time a local code ‘WO’ is 

established for use in the 940R, version 4030. A data 

maintenance action has been submitted for 

establishment of ‘WO-Work Order Number’ in a 

future version. 

YB Beginning Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

3. Qualifier YB is a migration code approved for use in 

X12 version 7020.A local code ‘YB’ is established 

for use in the 940R, version 4030. A data 

maintenance action has been submitted for 

establishment of ‘YB- Beginning Period of 

Availability Fiscal Year Date’ in a future version. 

YE Ending Period of Availability Fiscal Year Date 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Ending Period of Availability Fiscal Year 

Date”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

3. Qualifier YE is a migration code approved for use in 

X12 version 7020.A local code ‘YE’ is established for 
Enclosure 3 to ADC 1043A 

Page 39 

# Location 940R Material Release Reason 

use in the 940R, version 4030. A data maintenance 

action has been submitted for establishment of ‘YEEnding Period of Availability Fiscal Year Date’ in a 

future version.