Attachment to ADC 1043 

Page 1 

Attachment to ADC 1043, 

Revisions for Department of Defense (DOD) Standard Line of Accounting (SLOA)/Accounting 

Classification (Finance/Supply)

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: DLA Logistics Management Standards Office 

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

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

2. FUNCTIONAL AREAS: Joint Finance and Supply 

3. REFERENCES:

a. 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” (see Enclosure 1) 

b. Approved DLMS Change (ADC) 435 DLMS Revisions for Standard Financial Information 

Structure (SFIS) (Supply/Finance), linked at www.dla.mil/j-6/dlmso/eLibrary/Changes/approved5.asp 

c. DLM 4000.25, Defense Logistics Management System (DLMS), linked at 

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

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

e. DOD 7100.14-R, The DOD Financial Management Regulation (DOD FMR), linked at 

comptroller.defense.gov/fmr/

f. November 7, 2012, Joint Supply and Finance PRC Meeting linked at www.dla.mil/j6/dlmso/Archives/Supply/meetings/20121107/FPRC_SPRC_Meeting_minutes_2012_11_13.pdf

g. ADC 143, Fund Code and other DLMS Support for Intra-governmental Transactions, linked 

at www.dla.mil/j-6/dlmso/elibrary/changes/dlms/ADC/ADC143_FundCodeIGT.PDF

h. Under Secretary of Defense Acquisition, Technology & Logistics memorandum of January 

14, 2013 “Traceability of Contract Execution Expenditures for Services”, linked at 

www.acq.osd.mil/dpap/policy/policyvault/USA005536-12-DPAP.pdf

i. Joint Finance/Supply Process Review Committee Meeting of June 20, 2013 , linked at 

www.dla.mil/j-6/dlmso/Archives/Finance/meetings/20Jun13/FPRC_SPRC_Meeting_minutes_2013-

06-20.pdf
Attachment to ADC 1043 

Page 2 

4. REQUESTED CHANGE(S): 

a. Brief Overview: This change adds discrete SLOA/Accounting Classification data elements 

to logistics transactions with financial implications to implement SLOA within DLMS. This is the first 

in a series of anticipated DLMS changes to accommodate SLOA requirements in logistics domain 

processes. This change also modifies X12 FA1 segment Qualifier DF for clarification. A focused 

Joint Finance/Supply PRC on June 20, 2013 addressed Proposed DLMS Change (PDC) 1043 

(Reference 3. i.) to gain resolution of open items. Resolution of staffing notes from PDC 1043 are 

addressed with each staffing note. Resolution of comments submitted during staffing is at Enclosure 7. 

Significant changes from PDC 1043 are highlighted in green.

b. Background: 

(1) Reference 3.a. establishes a DOD SLOA and directs updates to the SFIS. This 

memorandum also directs efforts to improve financial information, improve interoperability among 

business systems, provide better end-to-end funds traceability and linkage between budget and 

expenditures, comply with new Treasury (Government-Wide Accounting (GWA)) requirements, and 

help achieve audit readiness through business process reengineering (BPR). The target 

implementation date for SLOA is September 30, 2014 to support financial audit readiness. Initial 

Component level plans, which are outside the scope of this ADC, were due by January 14, 2013. 

Process voids requiring BPR were to be highlighted in Component level plans. During a November 7, 

2012 joint Supply and Finance PRC meeting (Reference 3.f. ), a draft version of this DLMS change 

was reviewed, including discussion of some process voids summarized below under additional 

functional requirements. 

(2) OUSD(C), Business Integration Office (BIO) and Defense Finance and Accounting 

Service (DFAS) Enterprise Solutions, Treasury’s Government-wide Treasury Account Symbol 

(GTAS) Adjusted Trial Balance System Project Office are leading DOD coordination for new 

Treasury GWA requirements, which is outside the scope of this ADC. Information regarding Interfund 

specific meetings may be found at www.dla.mil/j6/dlmso/programs/Committees/Finance/Documents/treasuryCommissionerLetterSFIS20120202.docx. 

(3) Reference 3.b. established procedures for meeting preliminary SFIS requirements 

applicable to logistics transactions and Interfund bill payment. At that time, the Components and 

Federal Agencies selected a referential data approach to add discrete data elements to the Fund Code to 

the Fund Account Conversion Table vice adding discrete data elements to the DLMS. This approach 

supports legacy processes that are only able to send or receive data via legacy 80 record position MILS 

transactions and does not require process changes. The enhanced capability for the SFIS Fund Code to 

the Fund Account Conversion Table is nearing completion. When completed, this table will include 

the current concatenated accounting string and the following discrete financial data elements: 

Department Regular Code, Department Transfer Code, Main Account Code, Sub-Account Code, SubClass Code, Limit/Subhead (legacy), Beginning Fiscal Year Period of Availability, Ending Fiscal Year 

Period of Availability, Availability Type Code, and Fiscal Year Indicator. These data elements support 

the Treasury Account Symbol (TAS) for reporting to Treasury. 

(4) To ensure harmonization of ANSI ASC X12 implementation for SLOA across 

functional communities, OUSD(C) BIO and Office of the Deputy Chief Management Officer 

(ODCMO) directed that all SLOA elements be mapped into the X12 FA2 Accounting Data segment 

for transactions that have an FA2 segment, and that migration codes be used where the underlying X12 
Attachment to ADC 1043 

Page 3 

version/release of the standard does not have semantically compatible codes to meet SLOA 

requirements. Where the implemented and later version of the standard lacks any sufficient code, a 

local code is proposed until a code request can be processed to add the code into a future version of the 

X12 standard. Codes to support financial data content will be requested for Budget and Accounting 

Classification Code Source 529 governed by Reference 3.e. OUSD(C) BIO and ODCMO have 

reviewed the data mapping at Enclosure 4. Selected codes applicable to Security Assistance retain 

their original code source. See Volume 1 of Reference 3.c. for an explanation of migration codes in 

DLMS implementation conventions (IC). 

(5) Product Service Code (PSC) is not included in DLMS at this time. Reference 3.a. 

updated the DOD Business Enterprise Architecture, Procurement Data Standard to include the 

federally defined PSC, which is also a data element required by the DOD Procurement Data Standard 

(PDS) that must be passed from contract writing systems (at the line item level) to financial 

management systems. Per Reference 3.h., the procurement community uses PSCs to track products and 

services acquired through contracts and the Financial Management community uses object classes, as 

defined by the Office of Management and Budget, as the method for identifying the types of items or 

services purchased. Initial assessment by OUSD(C) BIO, ODCMO and Office of Defense Acquisition 

and Procurement (ODPAP) in a December 20, 2012 meeting was that PSC could be added to the 

Procurement Request in contracting systems and need not be carried through DLMS at this time. 

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

address legacy systems/transactions, with the exception of the interim use of the SFIS Fund Code to 

Fund Account Conversion Table described in section 4.b.(3). 

(7) SFIS business rules and metadata will need to be approved by the SFIS Governance 

Board for SLOA to be fully implemented in DLMS processes. Compliance will be reviewed as part of 

the Investment Review Board (IRB) process, which is outside the scope of this change. 

(8) Modification of FA101 Agency Qualifier Code DF. The Federal note to the 

FA101 Qualifier DF, Department of Defense, has caused confusion. The X12 intent for the FA1 

Segment is to specify the organization controlling the content of the accounting citation and the 

purpose associated with the accounting citation. Where FA1 Segment is used in Federal ICs, the 

Federal note below has long been applied consistently to the Agency Qualifier Code (FA101) DF: 

“Use to indicate that the Component originating the funds is a Department of Defense 

agency, including DLA.” 

Taken literally, this note restricts code DF as identifying the originator of the funds. However, under 

DLMS, the Qualifier Code DF indicates nothing more than a DOD agency is responsible for the 

assignment of the DoDAAC used to construct the controlling document number for the transaction. 

Enclosure 5 addresses the modification to eliminate this confusion. 

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

(1) Interfund. Data needed for logistics billing originates in a supply transaction and 

is perpetuated to logistics bills. Logistics billing (excluding web-purchases paid via Government 

purchase card) may be accomplished two ways. In limited circumstances, billing may be 

accomplished through non-Interfund procedures. The predominant method for logistics billing in 

DOD is through Interfund billing procedures using DLMS/MILS transactions governed by 

MILSBILLS (Reference 3.c., Volume 4). The Interfund billing process currently supports 
Attachment to ADC 1043 

Page 4 

approximately $58 billion in billing transactions per year. It is DOD policy that customers shall 

authorize suppliers to use the Interfund billing system to reimburse themselves for materiel, hazardous 

materiel and waste services, and services related to materiel shipments. An overview of the Interfund 

billing system and identification of Logistics transactions with financial implications are provided: 

(a) Interfund billing is applicable to DOD and some authorized Federal Agency 

sources of supply, including General Services Administration, Federal Aviation Administration and 

National Oceanic and Atmospheric Administration. 

(b) The Interfund billing process is a highly automated billing process that 

allows sellers to reimburse themselves from appropriations designated by the buyer at the time of 

billing. 

(c) In the current environment, the appropriation chargeable for MILS/DLMS 

Interfund logistics transaction is derived from database tables managed by Component-assigned Fund 

Code Monitors and maintained in the DLA Transaction Services authoritative data source fund code 

tables. These tables use the bill-to DoDAAC, signal code, and fund code, which are carried in both 

legacy 80 record position MILS logistics and financial transactions and in variable length DLMS 

transactions. Using the service/agency code, which is the first position of the bill-to DoDAAC, the 

signal code, and the fund code, the Fund Code to Appropriation Conversion Table provides the 

concatenated department code (2 digits), fiscal year chargeable (1 digit), basic appropriation (4 digits) 

and limit/subhead (4 digits). The fiscal year chargeable may be the last digit of the fiscal year or may 

contain the symbol “#” to denote that the fiscal year chargeable is the fiscal year of the requisition 

ordinal date, the symbol “*” to denote the fiscal year of the billing date, or the symbol “X” to denote 

no-year funding. A separate table, the Fund Code to Billed DoDAAC Conversion Table, provides the 

billed DoDAAC to support third party billing when needed. A third table identifies Service/Agency 

Code H series DoDAACs authorized to use Interfund billing. 

(d) Interfund detail billing records are grouped together by sellers according to 

the buyer’s fund code in the Summary Billing Record, and are transmitted together via the DLMS 

810L Logistics Bill (or equivalent legacy transactions) to seller and buyer Central Accounts Offices 

(CAO). For bills that pass DLA Logistics Management Standards Office prescribed Defense 

Automatic Addressing System (DAAS) edits, the seller CAO is authorized to report summary level 

funds transfer for seller reimbursement and buyer disbursement to Treasury (currently at the end of the 

month). No detail bills are sent to Treasury. This is a self-balancing process. The buyer’s CAO is 

responsible for Interfund bill clearance, ensuring that buyer disbursements are correctly reported. For 

the buyer, the bill is both a bill and a notice of funds withdrawn (payment) from his account. The 

buyer must accept a billing and may seek adjustment from the seller if needed. While buyer CAOs 

may adjust the disbursement side of the seller reported Interfund transactions, neither buyers nor their 

CAOs can adjust, either directly or indirectly, the reimbursement side of the Interfund transactions 

reported by seller CAOs. 

(e) DLMS financial training, providing an overview of Interfund billing may be 

found at: www.dla.mil/j-6/dlmso/eapplications/training/dlmsmodules/Module4F. 

(2) Logistics Transactions with Financial Implications. Under ADC 435 (Reference 

3.b.), DLA Logistics Management Standards Office, OUSD(C) and the former Business 

Transformation Agency identified the processes and associated transactions with financial 
Attachment to ADC 1043 

Page 5 

implications. These are the same transactions identified as applicable for SLOA updates in this 

change. Specific transactions are listed in paragraph 4.d.(2) below.

(3) Security Assistance Data Elements. Reference 3.a. at Enclosure 1 defines a 

requirement for identification of specific Security Assistance related data elements that must be 

captured for SFIS compliance as independent data elements. 

(a) The Security Cooperation Customer Code (SFIS - T21) (previously known 

as the foreign military sales (FMS) country code) is currently embedded in the Security Assistance 

requisition document number (2nd and 3rd position) and is used to build the Military Assistance 

Program Address Code (MAPAC) (2nd and 3rd position). The document number is further 

perpetuated to build the transportation control number (TCN). The MAPAC is used to identify the 

consignee in transportation documents and to obtain clear-text address (e.g. for the ship-to and markfor) and other shipment information from the military assistance program address directory (MAPAD). 

Although the SFIS data element is defined as three positions to allow for expansion in the future, there 

are no current plans to modify the DLMS (or legacy) MAPAD/MILSTRIP/MILSTRAP/MILSBILLS 

transactions and procedures to accommodate a longer field length for the document number, TCN, or 

MAPAC. At this time, the independent SFIS/SLOA Security Cooperation Customer Code cannot be 

disassociated from the existing requirements for creation of the requisition document number and the 

MAPAC. If a three-position Security Cooperation Customer Code is to be adopted across DoD 

logistics systems, a transition plan must be identified and specific business rules and systems changes 

proposed. A separate DLMS change proposal must be submitted by DSCA for wide dissemination due 

to the wide-ranging impact. Until that time, three-position customer codes will not be authorized for 

the SLOA data associated with the MILSTRIP requisitioning process. Defense Automatic Addressing 

System (DAAS) conversion maps will continue to identify the SFIS/SLOA Security Cooperation 

customer code in the DLMS transaction based upon the value contained in the document number, 

pending separate systemic input of this data element. If input by the user as a separate distinct data 

element, the embedded data and the separate SFIS/SLOA data element must match. 

(b) Security Cooperation Case Designator (SFIS - T22) is currently embedded 

as the last three positions of the six position supplementary address (SUPADD) established in 

MILSTRIP requisitioning transactions. The legacy field length for the SUPADD is retained in DLMS 

to support interoperability. Although the SFIS data element is defined as four positions to allow for 

expansion in the future, there are no current plans to modify the DLMS (or legacy) 

MILSTRIP/MILSTRAP/MILSBILLS transactions and procedures to accommodate a longer field 

length for the SUPADD. At this time, the independent SFIS/SLOA case designator cannot be 

disassociated from the existing SUPADD. If the four-position case designator is to be adopted across 

DoD logistics systems, a transition plan must be identified and specific business rules and systems 

changes proposed. A separate DLMS change proposal must be submitted by DSCA for wide 

dissemination due to the wide-ranging impact. Until that time, four-position case designator will not 

be authorized for the SLOA data associated with the MILSTRIP requisitioning process. DAAS 

conversion maps will continue to identify the SFIS/SLOA Security Cooperation case designator in the 

DLMS transaction based upon the value contained in the SUPADD, pending separate systemic input of 

this data element. If input by the user as a separate distinct data element, the embedded data and the 

separate SFIS/SLOA data element must match. 

(c) Security Cooperation Implementing Agency Code: (SFIS - T27) is generally 

understood to be the first position of the Security Assistance document number (which is the 

Service/Agency Code authorized under MILSTRIP) when the case authorizes requisitioning under 
Attachment to ADC 1043 

Page 6 

MILSTRIP. However, due to a disconnect that occurred many years ago, the DLA implementing 

agency code does not correspond to the MILSTRIP Service/Agency code used for FMS requisitioning 

from DLA Disposition Services. This deviation is addressed by a DAAS conversion map instruction 

and the appropriate implementing agency code will be passed in the DLMS transaction. At this time 

the only implementing agency codes that are authorized for MILSTRIP requisitioning are B (Army), D 

(Air Force), I (Missile Defense Agency), P (Navy), T (DLA). The DAAS conversion map is shown at 

paragraph 11, Impact. If input by the user as a separate distinct data element, the Service/Agency code 

and the separate SFIS/SLOA data element must align properly. 

(d) Security Cooperation Case Line Item Identifier (SFIS T23) is a new data 

element established for DLMS use under this ADC. It will not be available in the legacy MILSTRIP 

format and cannot be captured though a DAAS conversion map. Because this data element is 

associated with SFIS/SLOA, it is only added to those transactions that initiate a financial event. If 

other transactions should also carry this data element or if specific business rules should be contained 

in the MILSTRIP guidance, DSCA should provide a separate DLMS change proposal to document this 

information. 

d. Requested Change in Detail: 

(1) Fund Code Process: 

(a) Retain the Interfund billing process based on fund code for bill processing 

through Treasury without change. Add additional SLOA data elements as a DLMS enhancement to the 

DLMS 810L detail bill and to the other transactions per 4.d.(2) below. 

(b) DLA Transaction Services will complete development and fielding of the 

Web-enabled application to support the SFIS Fund Code to Fund Account Conversion Table, which 

will provide enhanced SLOA data content. This capability will support transactions originated in 

legacy format and DLMS transactions missing SLOA content. Staffing Note: DLA Transaction 

Services was asked to provide projected Web application fielding date. Resolution: DLA Transaction 

Services is currently completing application development and will submit the application to the DLA 

Internet Council for approval. In the event that the DLA Internet Council does not complete review 

and approval prior to September 30, 2013 for the start of Fiscal Year 2014, the database will still be 

available and DLA Transaction Services will be able to accept and make fund code changes pending 

application approval. 

(c) Upon completion of the SFIS Fund Code to Fund Account Conversion 

Table, DAAS will edit the fund code in the transaction to the discrete SLOA data elements in the 

transaction for transactions included in 4.d.(2) below. If no discrete SLOA data is present, DAAS will 

map available SLOA data from the SFIS Fund Code to Fund Account Conversion Table to discrete 

SLOA data fields in the transaction. 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, the transaction will be rejected with newly designated Status Code CF, (see 

paragraph 4.e.(9)(14) of this ADC). 

(d) Upon notification by the Finance PRC Chair, Component Fund Code 

Monitors provide written appointment letters to the Finance PRC Chair and to DLA Transaction 

Services. Fund Code Monitors will then complete Systems Access Requests through DLA Transaction 

Services for access to the fund code Web application (https://www.daas.dla.mil/sar/sar_menu.html). 
Attachment to ADC 1043 

Page 7 

Once access is gained, Fund Code Monitors will add or modify the following discrete data elements 

for assigned fund codes: Department Regular Code, Department Transfer Code, Main Account Code, 

Sub-Account Code, Sub-Class Code, Limit/Subhead (legacy), Beginning Fiscal Year Period of 

Availability, Ending Fiscal Year Period of Availability, Availability Type Code and Fiscal Year 

Indicator (concatenated accounting string will be constructed). Note that new fund codes may be 

required for multi-year appropriations. Post-staffing, it was noted that it may be challenging for some 

Components to implement the beginning and ending periods of availability for multi-year 

appropriations. Components were tasked at a Joint Finance/Supply PRC on June 20, 2013 to provide a 

proposed alternative course of action if their Component is unable to fully implement beginning and 

ending periods of availability for multi-year appropriations. The SFIS Fund Code to Fund Account 

Conversion Table is being designed with a legacy indicator to flag these multi-year appropriations to 

note that this information is not available from the table. The SLOA data element Availability Type 

Code has also been added to the SFIS Fund Code to Fund Account Conversion Table design. 

(e) Withdraw ADC 143 (reference 3.g). Delete record formats for Fund Code to 

Appropriation Update Record (FCA), Fund Code to Billed Office DoDAAC Update (FCB), Text 

Header Record: Fund Code Changes (FCT) from MILSBILLS. Upon fielding, use the Web application 

for fund code changes. 

(2) Logistics Transactions Requiring SLOA Data. Add additional SLOA data 

elements to DLMS transactions as shown in Enclosure 3. To have a consistent approach across 

functional groups OUSD(C) and ODCMO directed that ASC X12 EDI mappings place all SLOA data 

elements into the FA2 segment and utilize the same X12 codes. An exception to the mapping is any 

transaction that does not have an X12 FA2 segment available (i.e. DLMS 856S); in this case, available 

X12 REF and DTM segments will be used to convey the SLOA data elements within a new loop 

structure. The business processes and specific transactions impacted by SLOA are identified as 

follows:

(a) Requisitioning Process: 

1. 511R Requisition. Applicable to requisition, referral order, and 

passing order, including image transactions and all other variants of the 511R.

2. 511M Requisition Modification. Applicable because it repeats 

information from original requisition due to MILSTRIP requirement to support capability to use 

modification as original requisition if original requisition is not on file. 

Staffing Note: DLA Logistics Management Standards Office proposed that most of the additional 

SLOA data elements will be modifiable when used on a requisition (comparable to current business 

rules for the fund code during requisitioning). Refer to DLMS notes in the DLMS 511M, Requisition 

Modification. Resolution: No objections were noted.

3. 869F Requisition Follow-Up. Applicable because it repeats 

information from original requisition due to MILSTRIP requirement to support capability to use 

follow-up as original requisition if original requisition is not on file.

(b) Materiel Obligation Validations: 517M Materiel Obligation Validation 

(MOV). Applicable to requisition re-instatement only. Repeats information from original requisition 

due to MILSTRIP requirement to support capability to re-instate a requisition cancelled by the source 

of supply during MOV.
Attachment to ADC 1043 

Page 8 

(c) Inventory Control Point-Directed Lateral Redistribution: 856S 

Shipment Status. Applicable only to shipment status to ICP from reporting activity for lateral 

redistribution order shipments of retail assets (equivalent to MILSTRIP legacy Document Identifier 

Code (DIC) AS6).

(d) Materiel Returns Program: 180M Materiel Returns Reporting. 

Applicable to automatic return notification (equivalent to MILSTRIP legacy DIC FTA and customer 

asset report/customer asset report for part-numbered items) (equivalent to MILSTRIP legacy DIC 

FTE/FTG). Retail reporting activity offers to sell back unneeded materiel to the ICP; depending upon 

the ICP’s asset position, the ICP may provide credit.

(e) Turn in to DLA Disposition Services: 940R Materiel Release.

Applicable to the disposal release order for hazardous materiel/waste and creditable turn-in only 

(equivalent to MILSTRIP legacy DIC A5J).

(f) Supply Discrepancy Reporting: 842A/W SDR. Applicable to DLMS 

enhancement capability to facilitate proper construct of the debit/credit billing where the original 

requisition document number is not known to the submitter. The submitter uses a constructed 

document number when reporting the discrepancy and provides the fund code to be credited. This is a 

restricted use process and is not applicable to Foreign Military Sales.

(g) 867I Issue Transaction. Applicable to post-post issue transactions where 

no prior transaction captured SLOA data.

(h) Billing: 810L Logistics Bill. The 810L Logistics Bill is unique in that it 

includes FA1/FA2 segments in both the header (Table 1) conveying summary bill information and the detail 

(Table 2) conveying supporting detail bills. The summary and detail bills are linked by a common billing 

number. Subsequent to staffing, DLMSO made a determination that applicable SLOA data for the billing office 

should be included in the FA2 of the 810L header (Table 1). Billed office SLOA data is provided in the detail 

(Table 2). 

(3) Miscellaneous DLMS Transactions without SLOA Update. The following 

transactions currently include the fund code as perpetuated from a prior transaction. None of these 

transactions was identified during ADC 435 staffing as having financial implications requiring 

additional data content. At this time, no requirement has been identified to perpetuate SLOA data or 

remove fund code. 

(a) 517G Government Furnished Material (GFM) Validation

(b) 527D Due-in/Advance Receipt/Due Verification 

(c) 527R Receipt, Inquiry, Response and MRA 

(d) 812R Logistics Bill Adjustment Request 

(e) 812L Logistics Bill Adjustment Request Reply 

(f) 842A/R Standard Supply Discrepancy Report Reply 

(g) 842C/I Stock Screening Request 

Staffing Note: PDC 1043 sought verification of whether SLOA data is needed for the business 
Attachment to ADC 1043 

Page 9 

process where the owning Service requests a special inspection by DLA Distribution Depots. No 

Component responses were received. Resolution: The current understanding is that SLOA data 

will be captured during creation of the MIPR and need not be included in the stock screening 

request. No further action will be taken at this time. If required in the future, SLOA-related data 

requirements will be identified by separate DLMS change documentation. 

(h) 856R Shipment Status Material Returns 

(i) 867D Demand Reporting 

(j) 869A Requisition Inquiry/Supply Assistance Request 

(k) 869C Requisition Cancellation 

(l) 870S Supply Status 

(m) 945A Material Release Advice 

(n) 947I Inventory Adjustment 

(4) SLOA Data Elements. DLMS definitions are shown in Enclosure 2 and specific 

applicability is shown in Enclosure 3. Staffing Note: Reference 3.a. identifies SLOA data elements; 

however, it does not prescribe specific transaction requirements. Reference 3.a. identifies cost objects 

associated with financial accounting, which have meaning only to the buyer. Moreover, acquiring cost 

objects for many logistics processes/support services where the customer’s requirement is initiated 

outside the Service-sponsored system will be problematic. Components were to validate the need to 

exchange cost objects between the buyer and the seller. OUSD(C)/ODCMO responded that the cost 

objects are used as a compensating control where the requisition cannot be identified. USMC 

responded they do not need to transact cost object data. Resolution: Cost objects will be carried in 

designated DLMS transactions as optional data elements. 

(5) Supply Documentation. MILSTRIP procedures require DOD shipments be 

accompanied by an Issue Release/Receipt Document (IRRD) (DD Form 1348-1A or DD Form 1348-

2). This document displays the legacy transaction format by record position including the Fund Code. 

There are currently no provisions for display of SLOA data elements. Additionally, there are specific 

rules for the inclusion of the bill-to DoDAAC in association with hazardous waste/materiel turn-in and 

the funds citation for reimbursement of scrap proceeds on the IRRD. SLOA enhancements for the 

IRRD will be addressed as a future requirement. 

(6) Obsolete FA201 Code I1. Remove existing code I1, Abbreviated Department of 

Defense (DoD) Budget and Accounting Classification Code (BACC), from the FA2 segment which is 

no longer relevant now that SLOA has been defined and has no identified legacy transition purpose. 

(7) FA101 Qualifier Federal Note: Replace the Federal note with a DLMS note as 

detailed in Enclosure 5. 

(8) FA201 Qualifier 18- Funds Appropriation. During staffing for ADC 435 

(reference 3.b.), DLA indicated a current need to retain FA201 qualifier 18 in the 527R to support 

legacy processes. This qualifier is used by DMLSS AMMA to assist in the communication of purchase 

card receipt data and in certain legacy processes supporting DLA Disposition Services. DLA was to 
Attachment to ADC 1043 

Page 10 

assess these legacy processes for conversion to use of SFIS data. Staffing Note: DLA was asked to 

research if this qualifier still needed to be retained and identify any business process reengineering 

requirements. No response was received. Resolution: Qualifier 18 will be retained on an interim 

basis pending future transition to SLOA data. 

(9) Security Cooperation Case Designator. As part of updating the Foreign Military 

Sales (FMS) elements related to SLOA, the DLMS IC changes in Enclosure 3 are removing a now 

obsolete DLMS enhancement for two repetitions of the case designator. There is no requirement to 

include both the Foreign Military Services Order (FMSO) I case identifier and the FMSO II case 

identifier in a single requisition. Linking the FMSO I case identifier to the FMSO II case identifier is 

accomplished via the Defense Security Assistance Management System (DSAMS). For consistency, 

Enclosure 6 removes the same obsolete enhancement from non-SLOA related supplement, 856N, 

Notice of Availability. 

e. Revisions to DLM 4000.25 Manuals: 

(1) Revise DLM 4000.25, Volume 1, Appendix 2, Terms and Definitions as shown. 

SECURITY COOPERATION CASE DESIGNATOR. The Security Cooperation case designator 

code is used to reflect a FMS contractual sales agreement (Letter of Offer and Acceptance) between 

the U.S. and an eligible foreign country. It is a unique code used with a country identification code to 

identify a particular foreign military sale. The Security Cooperation case designator is a minimum

three, maximum four-character designation; however, it is restricted to three positions under DLMS. 

SECURITY COOPERATION CUSTOMER CODE. The Security Cooperation (SC) customer code is a 

code used by Defense Security Cooperation Agency to represent the country, international organization, 

region or program authority associated with transactions recorded in Security Cooperation systems and 

associated with programs implemented in the Foreign Military Sales Trust Fund. The Security 

Cooperation customer code is a minimum two, maximum three-character designation; however, it is 

restricted to two positions under DLMS. Pending separation of the country and activity codes used for 

distribution and physical location in clear text addressing under the DLMS, the SC customer code values 

and the country and activity codes are maintained in a mixed-purpose table in LOGDRMS (in association 

with Qualifier 85 an 85*. 

SECURITY COOPERATION IMPLMENTING AGENCY. The implementing agency (IA) code 

identifies the military department or defense agency responsible for the execution of military 

assistance programs. With respect to FMS, this is the military department or defense agency 

assigned responsibility by the Defense Security Cooperation Agency to prepare a Letter of Offer and 

Acceptance (LOA) and to implement an FMS case. The implementing agency is responsible for the 

overall management of the actions that will result in delivery of the materials or services set forth in 

the LOA that was accepted by a foreign country or international organization. For Military Service 

and Missile Defense Agency sponsored FMS cases, the IA code is equivalent to the Service/Agency 

code used in the first position of the document number; for all other Defense Agencies the IA does 

not equate to the Service/Agency code . The only IA codes authorized for MILSTRIP requisitioning 

are B (Army), D (Air Force), I (Missile Defense Agency), P (Navy), and R (DLA).

(2) Revise DLM 4000.25, Volume 4, Chapter 2 to add the following statement 

recognizing the inclusion of SLOA discrete elements in DLMS bills and the use of the fund code table 

as a means to reference some line of accounting data which could not be captured directly within the 

bill: 
Attachment to ADC 1043 

Page 11 

 “C2.2.8. Standard Line of Accounting/Accounting Classification. The Office of the Under 

Secretary of Defense (Comptroller) identified Standard Financial Information System elements that 

make up the Standard Line of Accounting (SLOA)/accounting classification elements.[1] These 

SLOA elements are included in DLMS bills. Some elements may be acquired referentially through 

the authoritative data source SFIS Fund Code to Fund Account Conversion Table maintained at 

DLA Transaction Services. Updates to the fund code table are accomplished by Component Fund 

Code Monitors designated in writing by their respective Components. 

---- 

[1] 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”” 

(3) Revise DLM 4000.25, Volume 4, Chapter 6 to add a check for matching SLOA 

data between the transaction and the SFIS Fund Code to Fund Account Conversion Table: 

 “C6.2.2. Bill Editing 

 C6.2.2.1. DAAS shall edit and reject any bill that fails any of the following edits: 

 ....

C6.2.2.1.6. Discrete values for the Standard Line of Accounting[1] data elements in 

the 810L logistics bill match data elements from the SFIS Fund Code to Fund Account Conversion 

Table for the Fund Code in the 810L

---- 

[1] 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””

(4) Revise DLM 4000.25, Volume 4, Appendix 3 - Record Formats to delete the 

following formats for changes to the fund code table and delete from the Appendix 3 index: 

 Fund Code to Appropriation Update Record (FCA) 

 Fund Code to Billed Office DoDAAC Update (FCB) 

 Text Header Record: Fund Code Changes (FCT). 

(5) Revise DLM 4000.25, Volume 4, Chapter 6 as follows: 

“C6.7. OTHER DEPARTMENT OF DEFENSE ACTIVITY ADDRESS CODES AUTHORIZED 

INTERFUND 

 C6.7.1. DLA Transaction Services shall edit service code H requisitions to ensure that interfund 

procedures are appropriate for the requisitioner. Other DoD Components’ requisitions for which 

interfund billing is appropriate are those in which the requisitioning DoDAAC is identified as 

authorized interfund billing. See Appendix AP1 for more information. 
Attachment to ADC 1043 

Page 12 

 C6.7.2. If necessary, DLA Transaction Services will change the fund code cited on other DoD 

Components’ requisitions to XP when the H-Series requisitioning DoDAAC is not identified as 

authorized interfund billing. 

 C6.7.3. Other DoD Components may add their DoDAAC (to allow for interfund billing) or 

delete a listed DoDAAC (mandatory noninterfund billing). To request a change, use the comment 

form on the DLA Logistics Management Standards Website www.dla.mil/j6/dlmso/About/Comment/comment_form.php.” contact the H Series Fund Code Monitor at 

https://www.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp” 

(6) Revise DLM 4000.25-1, MILSTRIP, Chapter 2, Preparation and Submission of 

Requisitions, Modifiers, Cancellations and Follow-ups: 

“C2.1.14 Conformance with single line of accounting (SLOA)/accounting classification requires 

any initiation of an obligation to include SLOA mandated standard financial information system 

(SFIS) elements.[1] Transition to DLMS requisition transactions is required to support inclusion of 

SLOA required elements. Pending full implementation of SLOA under DLMS, DLA Transaction 

Services will facilitate interoperability by updating selected SLOA data fields based upon the 

requisitioner's Fund Code when moving from a legacy environment to a DLMS compliant system. 

---- 

[1] Refer to ADC 1043.”

(7) Revise DLM 4000.25, DLMS, Vol. 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.

---- 

[1] Refer to ADC 1043.”

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

---- 
Attachment to ADC 1043 

Page 13 

[1] Refer to ADC 1043.” 

(9) Revise DLM 4000.25-1, MILSTRIP, Chapter 7: 

C7.1.1.5. An MOV reinstatement request1 is submitted by a requisitioner to reinstate a previously 

canceled requisition due to the requisitioner’s nonresponse to an MOV request. 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.

---- 

[1] Refer to ADC 1043.

(10) 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.

---- 

[1] Refer to ADC 1043. 

... 

 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 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. Retail activities shall use Uniform 

 

1 Established procedures to reinstate canceled requisitions last reported as not implemented by USN. Refer to AMCL 

150C.
Attachment to ADC 1043 

Page 14 

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

directed by the ICP/IMM. 

---- 

[1] Refer to ADC 1043.” 

(11) Revise DLM 4000.25-1, MILSTRIP, Chapter 9: 

C9.10.6. 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. 

---- 

[1] Refer to ADC 1043. 

... 

 C9.19.3.3. Ensure that materiel is shipped using DD Form 1348-1A or DD Form 1348-2 to 

the activity identified in the LRO as the “ship-to” addressee. When the materiel is shipped, transmit a 

DIC AS6 to the activity identified in rp 74-76 of the LRO. The DIC AS6 shall include the DoD 

activity address code (DoDAAC) (rp 45-50) and fund code (rp 52-53) of the activity to which the 

credit for the materiel and reimbursement for the PCH&T costs are to be provided, Signal Code B (rp 

51), and Distribution Code 2 or 3 (rp 54). 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 when converting legacy 

formats to DLMS. Retail activities shall use UMMIPS time standards for processing LROs directed 

by the ICP/IMM. Refer to DoD 4140.1-R, Chapter 8 and Appendix AP9, UMMIPS time Standards 

(published electronically at www.dla.mil/j-6/dlmso/eLibrary/Manuals/regulations.asp).

---- 

[1] Refer to ADC 1043.” 

(12) 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. 
Attachment to ADC 1043 

Page 15 

 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. 

---- 

[1] Refer to ADC 1043.” 

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

“ C16.1.2.1.2. DTID Requisitions of Reutilization Property. All requisitions sent 

to DLA Disposition Services for property assigned Disposition Category Code RU are considered freeissue, except requisitions from foreign military sales (FMS) customers, which generate transportation 

costs. These transportation costs will be identified on the requisition transaction identified by a funds 

appropriation, (e.g., fund cite or line of accounting). These costs are determined by the RTD Web 

based on the FMS customer’s profile and passed to DLA Disposition Services on the Requisition. This 

funds appropriation/funds cite will be perpetuated to the field office on the DLMS 940R Materiel 

Release Order (MRO) at the time the item is issued. 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 MRO 

transaction supports inclusion of SLOA required elements. 

---- 

[1] Refer to ADC 1043. 

... 

 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. 

---- 
Attachment to ADC 1043 

Page 16 

[1] Refer to ADC 1043.” 

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

“ C17.3.2.6.2. Concealed Overage/Shortage. U.S. Government customers shall 

must report overages or shortages discovered while opening a sealed vendor pack regardless of dollar 

value or shipper. These reports must contain, if available, the contract number from the packaging, the 

lot number, and original document number. A constructed document number should must be provided 

when the original number is not known. When using a constructed document number in an SDR 

coordinate with the applicable Component finance office and follow MILSBILLS procedures citing 

Code U in the first position of the constructed document number serial number (DLMS Utilization 

Code U), include fund code and credit-to/bill-to DoDAAC, to ensure that credit/billing is appropriate. 

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

initiation of a financial business event (e.g., credit or debit) to include SLOA mandated standard 

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

SLOA required elements. 

---- 

[1] Refer to ADC 1043. 

... 

 C17.3.2.11.2. Incorrect item discrepancies discovered while opening a sealed 

vendor pack shall be reported regardless of dollar value or shipper. These reports must contain the 

contract number from the packaging and, if available, the lot number and the original document 

number. A constructed document number shall be provided when the original number is not known. 

When using a constructed document number in an SDR coordinate with the applicable Component 

finance office and follow MILSBILLS procedures citing Code U in the first position of the constructed 

document number serial number (DLMS Utilization Code U), include fund code and credit-to/bill-to 

DoDAAC to ensure that credit/billing is appropriate. Conformance with standard line of accounting 

(SLOA)/accounting classification requires any initiation of a financial business event (e.g., credit or 

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

DLMS SDR transaction supports inclusion of SLOA required elements. Include identity of the 

incorrect item received in the discrepancy report. 

---- 

[1] Refer to ADC 1043. 

... 

 C17.3.18. Follow-up on Credit Adjustments on SDRs. When an action activity has indicated 

that a credit adjustment has been authorized, reimbursement is normally provided to the fund code/line 

of accounting and bill-to address cited on the original requisition. When concerned about an apparent 

non-receipt of credit and 60 calendar days has elapsed, the SDR submitter should consult the bill-to 

finance office for verification. When non-receipt of credit is confirmed, the financial office shall will

submit a request for billing adjustment as prescribed by MILSBILLS procedures in DLM 4000.25, 

Volume 4, Finance. 
Attachment to ADC 1043 

Page 17 

... 

 C17.5.9.1. When an action activity has indicated that a credit adjustment has been 

authorized, reimbursement is normally provided to the fund code/line of accounting and bill-to 

address cited on the original requisition. When concerned about an apparent non-receipt of credit, the 

ILCO should consult with the appropriate finance office for verification. Allow a minimum of 60 

calendar days from the date of the SDR response before initiating a follow-up action. To facilitate 

research of supply and financial records, it is suggested that follow-up action for non-receipt of credit 

associated with the return of discrepant materiel occur within a reasonable period (e.g., not longer than 

45 calendar days after the ILCO provides the action activity the initial notice with evidence of 

discrepant materiel return). 

---- 

[1] Refer to ADC 1043.” 

(15) Revise DLM 4000.25-2, MILSTRAP Chapter 3, Issue, Backorder, Demand, Loan, 

and Single Manager for Conventional Ammunition Freeze/Unfreeze Actions: 

“C3.1. GENERAL 

 C3.1.1. This chapter provides a standard procedure for processing issue transaction 

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

 C3.1.1.1. Updating the central inventory control record. 

 C3.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] 

Transition to DLMS issue transactions is required to support inclusion of SLOA required elements. 

Pending full implementation of SLOA under DLMS, DLA Transaction Services will facilitate 

interoperability by updating selected SLOA data fields based upon the initiator’s Service/Agency and 

Fund Code when moving from a legacy environment to a DLMS compliant system. 

---- 

[1] Refer to ADC 1043.” 

(16) Update DLM 4000.25-1, MILSTRIP Appendix 2.16 for revised definition and 

new status code: 

“CD Rejected. Unable to process because of errors in the quantity, date, and/or serial number fields 

or inconsistency in data content.

 (1) If received in response to a requisition and the materiel is still required, submit a new 

requisition with correct data field entries. 

 (2) If other than FMS/Grant Aid or Navy initial outfitting, the requisition date shall not exceed 

one calendar year from the transaction processing date (current date) or be more than one day 

in the future. 
Attachment to ADC 1043 

Page 18 

 (3) If received in response to a cancellation request and materiel is not required, submit a new 

cancellation request with a valid quantity entry. 

(4) If received in response to an FMS requisition, the Security Cooperation Customer Code 

and Security Cooperation Case Designator embedded in the document number and 

supplementary address must correspond exactly to the values contained in the separate data 

elements provided under SFIS/SLOA procedures. The Security Cooperation Customer Code 

must align properly with the Service/Agency Code identified in the document number. 

CF Rejected. Discrete values for the Standard Line of Accounting[1] 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. If still required, submit a new 

requisition1 with valid data entries. 

---- 

[1] Submit a new requisition using a new document number with a current ordinal date.” 

(17) Update acronym lists in DLM 4000.25, DLM 4000.25-1, and DLM 4000.25-2 to 

include “SLOA – Standard Line of Accounting” 

f. Alternatives: None identified. 

5. REASON FOR CHANGE: This change is needed to add SLOA data elements to DLMS 

transactions in support of Reference 3.a. and clarify use of the FA1 Segment. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Provides preliminary guidance for DLMS capable DOD Components, 

participating Federal Agencies, and foreign trading partners who ultimately become DLMS capable to 

meet reference 3.a. requirements. 

b. Disadvantages: Potential for significant cost, system, business process, and warfighter 

impacts. Due to the evolving nature of this requirement, all information required to fully delineate the 

DLMS requirements are not available for inclusion in this change. 

7. ADDITIONAL COMMENTS TO CONSIDER: Legacy systems/business processes may be 

operational subsequent to the 2014 target implementation date, but there are no currently defined 

procedures that will support continued processing of customer orders lacking full SLOA content once 

the source of supply has transitioned to SLOA. Therefore, it should be recognized that dual processing 

techniques are required and interim solutions, including use of the SFIS Fund Code to the Fund 

Account Conversion Table, may be needed for an extended period. It is imperative that the lack of 

SLOA data not impact source of supply cash flow or warfighter support.

8. ADDITIONAL FUNCTIONAL REQUIREMENTS: No efficient, cost-effective solution has 

been identified at this time for the many logistics processes/support services where the customer’s 

requirement is initiated outside the Service-sponsored system. Because of this, the SLOA data is not 

available for inclusion in the DLMS transaction. The following paragraphs identify a few of the 

specific areas where business process re-engineering will be required. It is envisioned that separate 

DLMS Changes will be provided for each of these as they are evaluated and the process owner 
Attachment to ADC 1043 

Page 19 

determines the appropriate course of action. In some instances, this may require a coordinated 

approach with all trading partners to include consideration of potential new system 

development/interfaces. 

a. Post-Post Operations. A “post-post” issue involves accepting and updating records after 

the event (or issue) has occurred. DLA and the Components use post-post processing in various 

contexts, including high priority shipments requested through the DLA call center and procedures in 

support of maintenance operations. For DLA, one form of the post-post process includes the Directed 

Material Release Order (MRO) which may be entered by authorized personnel to direct release of 

materiel from a Distribution Standard System (DSS) storage site without prior ICP processing of the 

requisition. The customer initiating the requirement has no systemic interface with the system 

preparing the transaction to provide SLOA data content. When this process is used, the first 

transaction available is the DLMS 511R for the DLA Directed MRO (Requisition) (equivalent to DLA 

legacy C0A/C01) or DLA Directed MRO (Referral Order) (equivalent to DLA legacy CQA/CQ1). In 

other scenarios, the issue transaction is the first available DLMS transaction.

b. Tailored Vendor Relationship (TVRs), Industrial Prime Vendor (IPV), and Integrated 

Logistics Partnership (ILP) Programs. These are programs where there is a direct relationship 

between the customer and the vendor. Customers communicate the materiel requirement directly with 

the vendor, outside normal supply system requisitioning channels and may have no mechanism to 

provide SLOA data, even if it were readily available.

c. DLA Disposition Services. When customers use DLA Disposition Services for e-tools (e.g. 

Electronic Turn-in Document (ETID), Reutilization Transfer Donation (RTD)) or process their turn-in 

using a hand-written DD-1348-1A Issue Release/Receipt Document (IRRD), DLMS transaction 

exchange is bypassed and SLOA data elements are not available. This is only significant when the 

turn-in is eligible for credit from the proceeds of the sale or charges associated with reimbursable 

actions for hazardous waste/materiel disposal.

d. Web-Based Requisitioning. DLA and GSA sponsored web ordering applications, such as 

DOD EMALL and GSA Advantage, will need to be modified to capture SLOA data. Several 

approaches will need to be evaluated and a combination may be the best solution. More static data 

may be appropriate for inclusion in the customer’s profile information from which SLOA data could 

be pre-populated on the requisition. Some may be provided directly by the customer during the order 

and other information may require an on-line real-time interface with the customer’s supply/financial 

system to obtain the necessary information. For DOD EMALL, Web-orders may be input directly by 

the customer, may be a joint process combining data input by shoppers and then released by those 

authorized to order, or may be input by the DLA call center based upon off-line communication with 

the customer to support emergency requirements.

9. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Staggered implementation will 

be permitted for these authorized DLMS enhancements with the understanding that some systems may 

not be able to provide or process the enhancement data. Components should ensure that inclusion of 

this data in a DLMS transaction does not cause inappropriate rejection of the transaction. Target 

implementation date for SLOA is September 30, 2014. 

10. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified. 
Attachment to ADC 1043 

Page 20 

11. IMPACT: 

a. Automated Information Systems (AIS): Significant modification to Military Service and 

Agency AIS is required. 

b. DLA Transaction Services: 

(1) Upon completion of a Web-enabled application to support the SFIS Fund Code to 

Fund Account Conversion Table, DAAS will use the Fund Code provided by the transaction 

originator to extract and map from the table the corresponding discrete SLOA content. This applies 

when mapping from legacy formats and DLMS transactions missing SLOA content. 

(2) DAAS mapping updates for SLOA data elements are required when data is 

provided by the transaction originator. 

(3) 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 with Status 

Code CF. 

(4) Security Cooperation Data Elements. 

(a) DAAS mapping will adjust for Security Cooperation Implementing 

Agency, Security Cooperation Customer Code, and Security Cooperation Case Designator per the 

below table. DAAS mapping to convert the DLA S/A Code T to IA Code R is required. Other 

transactions containing these data elements but not listed in the mapping change will not be revised 

at this time. 

(b) Security Assistance Customer Code and Case Designator can be derived 

from the embedded values in the document number and SUPAAD, respectively, with no alteration. 

However, if input by the user, the values must match the corresponding embedded data. Reject 

unmatched data with Status Code CD. 

(c) If input by the user, the Security Cooperation Implementing Agency 

must be B, D, I, P, or R and must align properly with the S/A code in the document number 

allowing for input of S/A Code T for Implementing Agency Code R. Reject misaligned data with 

Status Code CD. 

 
Attachment to ADC 1043 

Page 21 

X12 Transaction Set Map adjustments (If RP30=B, D, I, P, T) 

Security Cooperation 

Implementing Agency 

Security Cooperation 

Customer Code 

Security Cooperation 

Case Designator 

511 Replace 

 LQ01=71, 

 LQ02 = RP 30 

With 

 FA201 = IA, 

 FA202 = RP 30 

(If RP 30=T assign R) 

Replace 

 LQ01=85, 

 LQ02 = RP 31-32 

With 

 FA201 = S1, 

 FA202 = RP 31-32 

Replace 

 LQ01=A4, 

 LQ02 = RP 48-50 

With 

 FA201 = S2, 

 FA202 = RP 48-50 

810 Replace 

 LQ01=71, 

 LQ02 = RP 30 

With 

 FA201 = IA, 

 FA202 = RP 30 

(If RP 30=T assign R) 

Replace 

 LQ01=85, 

 LQ02 = RP 31-32 

With 

 FA201 = S1, 

 FA202 = RP 28-29 

Replace 

 LQ01=A4, 

 LQ02 = RP 48-50 

With 

 FA201 = S2, 

 FA202 = RP 48-50 

869 Replace 

 LQ01=71, 

 LQ02 = RP 30 

With 

 FA201 = IA, 

 FA202 = RP 30 

(If RP 30=T assign R) 

Replace 

 LQ01=85, 

 LQ02 = RP 31-32 

With 

 FA201 = S1, 

 FA202 = RP 31-32 

Replace 

 LQ01=A4, 

 LQ02 = RP 48-50 

With 

 FA201 = S2, 

 FA202 = RP 48-50 

940 Replace 

 LQ01=71, 

 LQ02 = RP 30 

With 

 FA201 = IA, 

 FA202 = RP 30 

(If RP 30=T assign R) 

Replace 

 LQ01=85, 

 LQ02 = RP 31-32 

With 

 FA201 = S1, 

 FA202 = RP 31-32 

Replace 

 LQ01=A4, 

 LQ02 = RP 48-50 

With 

 FA201 = S2, 

 FA202 = RP 48-50 

c. Non-DLA Logistics Management Standards Publications: Military Services and 

Agencies may supplement DLMS procedures to the extent that such supplementation is not conflicting. 

d. DLMS Data Elements/LOGDRMS. Update Status Code with new code CF per 4.e.(12) 

above. The information in Enclosure 2 is reformatted from the SFIS elements in BEA 10.0, which is 

the source for the SLOA data element names, definitions, and syntax for use in the DLMS. 
ENCLOSURE 1 

Department of Defense Standard Line of Accounting/Accounting Classification 

ADC 1043 

Enclosure 1, page 1 

OFFICE OF THE SECRETARY OF DEFENSE

1 000 DEFENSE PENTAGON 

WASHINGTON, DC 20301-1000

SEP 1 4 2012

MEMORANDUM FOR SECRETARIES OF THE MILITARY DEPARTMENTS 

CHAIRMAN OF THE JOINT CHIEFS OF STAFF 

UNDER SECRETARIES OF DEFENSE

ASSISTANT SECRETARIES OF DEFENSE

GENERAL COUNSEL OF THE DEPARTMENT OF DEFENSE 

DIRECTOR, OPERATIONAL TEST AND EVALUATION 

DIRECTOR, COST ASSESSMENT AND PROGRAM EVALUATION 

INSPECTOR GENERAL OF THE DEPARTMENT OF DEFENSE 

ASSISTANTS TO THE SECRETARY OF DEFENSE

DIRECTOR, ADMINISTRATION AND MANAGEMENT 

DIRECTORS OF THE DEFENSE AGENCIES 

DIRECTORS OF THE DOD FIELD ACTIVITIES

SUBJECT: Department of Defense Standard Line of Accounting/Accounting Classification

References: (a) Secretary of Defense Memorandum, "Improving Financial Information and

Achieving Audit Readiness,"October 13, 2011

(b) Under Secretary of Defense (Comptroller)/Chief Financial Officer

(USD(C)/CFO) Memorandum, "Standard Financial Information Structure (SFIS) 

Implementation Policy," August 4, 2005

(c) Title 10, U.S.C., section 2222, as amended by the National Defense Authorization 

Act (NDAA) for Fiscal Year (FY) 201 0 (Public Law 111-84),section l072, and 

reiterated in the NDAA for FY 2012 (Public Law 112-81)

The Secretary of Defense memorandum, reference (a), asked for an "all hands" effort 

across the Department to improve our business practices, "ensuring that we are operating in a 

common sense, accountable, and modem business environment." This policy memo establishes a 

Department of Defense (DoD) Standard Line of Accounting (SLOA) and updates the Standard 

Financial Information Structure (SFIS), reference (b). This memo also directs efforts to improve 

financial information, improve interoperability between business systems, provide better end-to end 

funds traceability and linkage between budget and expenditures, comply with new Treasury 

requirements, and help achieve audit readiness through business process reengineering (BPR).

The BPR effort will require system interface evaluation with the goal to reduce the overall number 

of interfaces to maximum extent practicable as mandated by the NDAA,reference (c). Today, each

Component and functional area uses different structures to represent the Line of Accounting (LOA). 

The LOA is used to identify the funding source associated with an organization's budget and to 

ensure accurate accounting transactions. The SFIS was established and implemented to create a 

common business language within the Department. Interoperability between systems, for 

trat1sactional data exchange remains a problem for the enterprise, because the content of a DoD 

LOA is non-standard, creating errorsrejections, reconciliation problems, unmatched 

disbursements, unsupported eliminations, and higher costs to develop and maintain interfaces.
ADC 1043 

Enclosure 1, page 2 

Therefore, within 120 days from the memorandum's date, an initial SLOA implementation 

plan must be submitted to the action officers listed below using the attached template.

Components may begin implementation prior to the initial plan due date. The plan must address 

interfaces having financial accounting impacts,to include procurement, logistics, travel, human 

resource systems, etc. The plan should give priority to interfaces affecting auditability and provide 

implementation dates, targeting completion by September 2014-subject to Investment Review 

Board review, centralized Department or Component schedule coordination, and funding.

After receipt of the Component-level plans, the Office of the Under Secretary of Defense

(Comptroller) (OUSD(C)) and the Office of the Deputy Chief Management Officer (ODCMO)

will consolidate the plans to form an enterprise transition plan with targeted completion dates. The 

OUSD(C) and ODCMO will work with Components to identify business process changes and 

measure progress to ensure proper implementation.

Target environment systems will be required to implement the SLOA outlined in the 

attachment, where applicable. Target systems must send,receive, capture, store, and maintain the 

data constructed as discrete data. System owners must update their current SFIS implementation 

plans to address this new requirement. The SLOA requirement is incorporated into the Financial 

Management Functional Strategy, which includes progress metrics, and will be incorporated into

the Business Enterprise Architecture and the DoD Financial Management Regulation (DoD FMR).

Legacy systems that are integral to auditability should be included in the plan, on a case 

by-case basis. Each Component plan should be a joint, coordinated effort between the 

Component's offices of Financial Management, Chief Information Officer, Chief Management 

Officer, and any other relevant offices. System owners and Service Providers must also ensure 

that their systems are interoperable with their trading partners' or customers' systems with respect 

to this requirement. Further, Components and Functional Areas must determine how to apply 

SFIS in all phases of financial management: programming, budgeting, acquisition, and execution.

Policy contained in this memorandum remains in effect until DoD FMR, Volume I, 

Chapter 4 is updated. Questions regarding this guidance may be directed to Ms. Micky Chopra, 

OUSD(C), and/or Mr. Raymond Bombac, ODCMO. Ms. Chopra can be reached at

(703) 614-7253 or micky.chopra@osd.mil. Mr. Bombac can be reached at (571) 372-3092 or 

raymond.bombac@osd.mil.

Elizabeth A. McGrath

Deputy Chief Management Officer

Robert F. Hale

Under Secretary of Defense (Comptroller)/ 

Chief Financial Officer

Attachment: 

As stated

2
ADC 1043 

Enclosure 1, page 3 

Standard Line of Accounting (SLOA)/Accounting Classification

Data Element Name (Length); SFIS reference (http://dcmo.defense.gov/products-andservices/standard-financial-information-structure/); Examples

 Sub Classi (2): A7 in SFIS; Grouping of a transaction type, e.g., 46 Payments from Current 

Appropriations for Obligations of Closed Accounts; a.k.a. Sub-level Prefix (SP) 

 Department Transferi (3): A2 in SFIS; A transfer of obligation authority from DOE, e.g. 

089; a.k.a. Allocation Transfer Agency Identifier (ATA) 

 Department Regulari (3): A1 in SFIS; e.g., 021 Army, 017 Navy, 057 Air Force; 097 

ODOs; a.k.a. 

 Beginning Period of Availability Fiscal Year Datei (4); A27 in SFIS, e.g., 2012 

 Ending Period of Availability Fiscal Year Datei (4); A28 in SFIS, e.g., 2012 

 Availability Typei (1): A24 in SFIS; e.g., X = No-year TAS 

 Main Accounti (4): A3 in SFIS; Synonymous with Basic Symbol, Appropriation Symbol, 

e.g., 4930 

 Sub Accounti (3): A4 in SFIS; Indicates the relationship to the Main Account, e.g., 002 

 Business Event Type Codeii (8); T20 in SFIS; Replaces Transaction Codes, e.g., DISB - 

Disbursement 

 Object Classiii (6); B6 in SFIS; Will initially be implemented at the three-digit level as in 

SFIS with room to expand to six, e.g., 252 

 Reimbursable Flagi (1); A9 in SFIS; Examples: Direct, Reimbursable Code, e.g., D or R 

 Budget Line Itemiii (16); For MilPers, value will be Budget Sub-Activity (BSA) plus Budget 

Line Item (BLI). B4 in SFIS; Further sub-divides the Treasury Account Fund Symbol below 

sub-activity, e.g., 111 

 Security Cooperation (formerly Foreign Military Sales (FMS) Customer Code)iv (3); T21 

in SFIS; Security Cooperation (SC) Customer; The country, customer, or U.S. program 

receiving the product/service, e.g., EI IRELAND or F1 F-16 CO-PRODUCTION, or B4 

SECTION 1206 

 Security Cooperation Implementing Agency (IA) Code iv (1); T27 in SFIS; Identifies the 

U.S. MILDEP or agency which is executing the FMS sale on behalf of the U.S. Government; 

e.g., B-Army, D-Air Force, P-Navy

 Security Cooperation Case Designator (formerly known as “FMS Case Identifier”)iv (4); 

T22 in SFIS; Identifies the FMS or Security Cooperation contractual sales agreement 

between countries, e.g., UAK 

 Security Cooperation (formerly FMS) Case Line Item Identifieriv (3); T23 in SFIS; 

Security Cooperation (SC) Customer; Identifies a detailed line-item requirement, e.g., 001 

Attachment 
ADC 1043 

Enclosure 1, page 4 

 Sub-Allocation (formerly known as “Limit”)iii (4); Use of this data element is exclusive to 

sub-allocation purposes, useful for Financial Reporting; e.g., 2504

 Agency Disbursing Identifier Codeii (8); O2 in SFIS; Synonymous with Treasury DSSN 

definitions for each disbursing office, e.g., 1700 

 Agency Accounting Identifierv (6); O3 in SFIS; Fiscal Station Number; Comptroller 

defined; Identifies the accounting system responsible for the accounting event e.g., 021001 – 

DFAS Indianapolis (GFEBS) 

 Funding Center Identifiervi (16); Cost Object/Cost Accounting (CA) section in SFIS; e.g., 

Army = Funds Center, ASN; Air Force = OAC, OBAN; Navy = BCN 

 Cost Center Identifiervi (16); CA section in SFIS; e.g., Army = Cost Center, ASN; Air 

Force = Resource Center/Cost Center (RC/CC); Navy = BCN 

 Project Identifiervi (25); CA section in SFIS; e.g., Army = WBS; Air Force = Project; Navy 

= WBS (Cost Code) 

 Activity Identifiervi (16); CA section in SFIS; e.g., Army = Activity/Network; Air Force = 

Activity or Special Project; Navy = Activity 

 Cost Element Codevi (15); CA section in SFIS; e.g., Army = Commitment Item; Air Force = 

Element of Expense Investment Code (EEIC); Navy = Cost Element 

 Work Order Numbervi (16); CA section in SFIS; e.g., Army = Internal Order; Air Force = 

Job Order; Navy = Job Order (Cost Code) 

 Functional Areavi (16); CA section in SFIS; e.g., Army = Functional Area; Air Force = 

Budget/Project 

i Treasury Account Symbol (TAS) data elements requirement for the Treasury’s Central 

Accounting and Reporting System (CARS)/Government Wide Accounting (GWA); also a 

Payment Information Repository (PIR) requirement 

ii Requirement for the Treasury’s PIR

iii Office of Management & Budget; OUSD(C) Program/Budget for the AR(M) 1002 Report

iv Security Cooperation transaction requirements v DFAS requirement

vi Component requirements, based on the cost accounting standards in Statements of Federal 

Financial Accounting Standards (SFFAS) #4 

The data elements in italics will have either updates/corrections/SFIS Business Rules established 

in an update to the BEA, targeted to be in the BEA 10.0.
ADC 1043 

Enclosure 1, page 5 

Initial SLOA Implementation Plan Template (an Excel template will also be provided on 

http://dcmo.defense.gov/products-and-services/standard-financial-information-structure/):

The Plan should address unreconciled differences caused by interoperability with trading 

partners’ or customers’ systems by: 

(A) Analyzing existing functionality and cost-efficiency within a mixed Legacy and 

Target and/or Enterprise Resource Planning (ERP) systems environment. 

(B) Determining the best way forward to resolve inherent data exchange problems. 

(C) Consolidating functionality by reducing the overall number of systems and thereby 

interfaces, which pass transactional data. 

(1) This should be based on a DoDAF SV-6 structure outlining each of the 

system’s interfaces. 

(2) Each interface is required to be labeled as Target or Legacy. 

(D) Evaluating if those systems/interfaces can be subsumed by the Target and/or ERP 

systems. 

(1) Each interface is required to be labeled as Subsumed or Maintained. 

(2) Each interface is required to be labeled as SLOA Applicable or Not Applicable. 

(3) Rule of thumb: 

‐  Those that are Target (C)(2), which will be Maintained (D)(1), lead to 

postings between commitments and disbursements; and 

‐  Those that are Legacy (C)(2), which will be Maintained (D)(1), should 

be noted with a comment specifying why these Legacy interfaces are 

critical/applicable. 

(E) Implementing the SLOA for the remaining interfaces. 

(1) Projected dates (MM/YY) are required for subsumption or SLOA 

implementation. 

‐  System owners and Service Providers must also ensure that their 

systems are interoperable with their trading partners’ or customers’ 

systems with respect to this requirement. 

‐  Certain cases may require a business process reengineering effort to 

effectively execute this requirement. Components should identify this 

in their SLOA implementation plans. 

(2) Participating in SLOA coordination discussions with the Office of the Under 

Secretary of Defense (Comptroller)/Deputy Chief Financial Officer and the 

Office of the Deputy Chief Management Officer after their receipt of the 

Component-level plans to form an Enterprise SLOA Transition Plan with 

targeted completion dates. 
ADC 1043 

Enclosure 1, page 6 

Note: Items (C)(1) through (D)(1) should already exist, given that for (C)(1) and (C)(2) Target 

systems should have an SV-6 and given that (D)(1) was a requirement associated to FY2010 

National Defense Authorization Act (NDAA) IRB certification. If items (C)(1) through (D)(1) 

have been done properly, then items (D)(2) & (E)(1) should be an intelligible task. 

Additional Guidance & Information (Updates will also be provided on 

http://dcmo.defense.gov/products-and-services/standard-financial-information-structure/):

 In the current systems environment, legacy and target systems are either configured or crosswalked to SFIS for external reporting purposes, in accordance with title 31, U.S.C., 

section 3512(b), and the Federal Financial Management Information Act of 1996, section 

803(a) (Pub. Law 104-208, Div A, Title VIII, 31 USC sec 3512 note). These systems must 

be able to cross-walk trial balance data to the Defense Departmental Reporting System 

(DDRS) for DoD’s consolidated/enterprise-level reports, for external stakeholders. 

 Procurement and financial management communities developed the Financial Data in 

Procurement (FDIP) concept which linked financial data to contract documents 

(USD(C)/CFO and Under Secretary of Defense for Acquisition, Technology and Logistics 

Memorandum, “Linking Financial Data to Contract Documents,” March 18, 2009.) The 

establishment of a DoD SLOA expands the FDIP concept to all functional areas, across the 

DoD, that generate general ledger information. This SLOA will, at the line-item level, 

enhance interoperability and enable the enterprise to move forward toward a target 

environment, link budget to execution, assist with the reconciliation of multi-funded 

contracts, and reduce unsupported accounting adjustments for improved auditability. 

 Components have expressed the necessity to include the “Sub-Allocation” data element 

(formerly known as “Limit”) in the SLOA for financial statement reporting and audit 

readiness purposes. The “Sub-Allocation” data element is used solely to track the suballocation of funds. A benefit of including the Sub-Allocation data element, in the SLOA, is 

to allow the sub-allocation of funds to be visible below the Funding Authorization Document 

level. Further, to support the Office of Management and Budget initiatives and the 

requirement for agencies to evaluate efficiency data and provide transparency of costs, SFIS 

is updated to include the federally defined Product Service Code (PSC). PSC, which is also a 

data element required by the DoD Procurement Data Standard (PDS), must be passed from 

contract writing systems, at the line item level, to financial management systems. In 

addition, OUSD(C) will work with OUSD(AT&L) to ensure the Military Interdepartmental 

Purchase Request (MIPR) data is standardized and in alignment with the SLOA and the PDS. 

Specific SFIS business rules will address system configuration for these requirements. 

 To support this effort, the OUSD(C)/Office of the Deputy Chief Financial Officer (ODCFO), 

ODCMO, and Office of the Under Secretary of Defense for Acquisition, Technology, and 

Logistics (OUSD(AT&L))/Defense Procurement and Acquisition Policy will lead an effort 

with the functional communities and appropriate standards committees to update exchange 

standards (e.g., ANSI X12 and XML) that are needed to: 1) support the SLOA requirement; 

2) determine what data will be required to pass between financial accounting systems and 
ADC 1043 

Enclosure 1, page 7 

contract writing systems; and 3) recommend updates to DoD FMR chapters that drive 

specific data exchange requirements. 

 The DoD IT Portfolio Repository (DITPR) is the Department’s authoritative inventory of IT 

systems. Per the new Investment Review Board (IRB) Guidance, a system is either 

Target/Core or Legacy. “A Legacy DBS [Defense Business System] is a business system 

with a sunset date that is less than 36 months from the date of the DBSMC’s approval of 

funds certification.” “A Core DBS is an enduring business system with a sunset date greater 

than 36 months from the date of the DBSMC’s approval of funds certification.” 

 The SLOA will be a requirement in the overall SFIS Implementation Plan. The 

configuration and storing of separate data elements is already an SFIS requirement. 

 The SLOA should not affect the Legacy System configurations, unless the system is a 

fundamental enterprise system affecting auditability or it is a Component owned system 

which the Component deems necessary to upgrade to meet the SLOA requirement. 

 Not all data elements are to be populated for all transactions. The exact set is conditional 

based on the function, accounting system’s software package and specific configuration, and 

Component. 

 No fields need to be zero filled, unless stated as an allowable value for the field or by the 

SFIS business rules. 

 When communicating outside of the system, the SLOA data elements, in this attachment, 

must be exchanged between business partner systems using a discrete data exchange 

mechanism, e.g., X12 or XML. In situations where data cannot be exchanged using discrete 

data elements, a delimited data exchange may be used following the sequence of the data 

elements presented in this attachment. In these cases, the beginning and ending of each data 

element must be represented by the delimiter “^”, for system to system exchange. 

Specifically, if the beginning of the SLOA is 46 (Sub Class), null (Department Transfer), 097 

(Department Regular), 2012 (Beginning Period of Availability Fiscal Year Date), 2012 

(Ending Period of Availability), null (Availability Type), 0100 (Main Account)...; then it 

must be represented as ^46^^097^2012^2012^^0100^.... The sequential “^^”, in the 

preceding example, represents the value of null for Department Transfer and Availability 

Type. 

 The sequencing layout above is meant only for the outbound/inbound data exchanges which 

carry the LOA as a single data string, not using discrete data exchange. It is neither required 

internal to a system nor for discrete data exchanges. The enterprise sequencing facilitates 

standard edits and easier location of data. 

 If a Target to Legacy interface is deemed necessary, there may be no change to the current 

interface specification. GEX can convert the SLOA for a Legacy system that cannot handle 

the delineated exchange. In determining the SLOA Implementation Plan, system owners 

may identify which systems cannot utilize the delineated exchanges and determine whether it 

is necessary to utilize GEX to translate the data elements. 

 For delimited data exchange, the fields are variable lengths with carrots “^” designating starts 

and stops. Specifically, a six character value length in an eight character field is represented 
ADC 1043 

Enclosure 1, page 8 

by ^xxxxxx^. An example for the object class would be ^252^ even though the length is 

6 characters above. 

 Specific information on Cost Objects – There are seven Cost Object fields in this 

requirement: Funding Center, Cost Center, Project, Activity, Cost Element Code, 

Work 

Order Number, and Functional Area (Planned BEA 10.0 SFIS Addition). Not all Cost 

Object fields must be populated on a specific transaction. The Cost Object fields, in the 

SLOA, are meant to accommodate the use of seven different SFIS Cost Accounting data 

elements. 

These seven SFIS data elements will be used depending on the software package, 

specific configuration, and Component specific cost structure. 

o Oracle applications will carry the POET structure in most SLOA applicable 

transactions. POET is an acronym for Project, Organization, Expenditure Type 

and Task. Project, Organization, Expenditure Type and Task map to the SFIS 

data elements Project, Funding Center, Cost Element Code, and Activity, 

respectively. 

o SAP has various ways to set up a cost structure. However, for SAP-based systems, 

Funding Center will be carried in the LOA. In addition to Funding Center, up to 

three other Cost Objects will be carried. 

o Other Interim and Target software packages or GOTS-based systems that are still 

required to be SFIS Compliant and need to have the applicable SFIS data elements 

configured in the system. These systems will need to at least carry a Funding 

Center and one other SFIS Cost Object. 

 The SFIS Business Rules will be updated to specify that Fund Center must be used 

for accounting classification. 

 SFIS business rules will be updated to reference all 7 cost elements identified in 

this attachment. 

 A Referential Data structure, within a system, may be used as long as a system is capable 

of exchanging the SLOA directly with its business partner systems. The relationships 

between the SLOA component data elements as reflected in the accounting systems must 

be maintained and the system’s referential data structure should leverage this to the 

highest extent possible. 

 The SLOA is applicable to all Target system configurations carrying LOA information 

including short-keys, such as the Fund Code, to reference Treasury Account Symbol 

(TAS) data. For mission critical events, a transaction would happen in the field and later 

entered into the business system. At the time of entry into the business system, controls 

should be put in place to capture the necessary SLOA data. 

 There will be certain cases where the implementation of this requirement is not feasible 

without a Business Process Reengineering (BPR) effort, such as Sales or Credit 

Returns, Credit Card Purchases or Syncada. In this case, the BPR effort should be 

identified in the initial Component Level Plan. OSD(C)/CFO and ODCMO will work 
ADC 1043 

Enclosure 1, page 9 

with the affected Components to implement the necessary changes to meet the SLOA 

requirement. 

 DoD business functional communities must provide updates to exchange standards, such as 

ANSI X12, that are needed to accommodate this memo. 

 The Trading Partner (TP) Indicator is the Trading Partner’s Department Regular code. 

Department Regular is in the SLOA. Federal/Non-Federal indicator can be derived off of 

Vendor data. 

 Capturing TP data elements for reimbursable transactions with other Federal 

agencies/DoD Components will be found in incoming SLOAs. The SFIS Trading 

Partner (TP): Federal/Non-Federal Indicator (TP1), Trading Partner Indicator Code 

(TP2), Business 

Partner Number (TP3), and Trading Partner Main Account (TP4) data elements are 

implicitly included in the SLOA. The seller must provide its SLOA to the buyer. This will 

assist in inter/intra governmental reconciliations and departmental reporting. In addition, 

TP data elements will be required to ensure that the DoD quarterly trial balances submitted 

to Treasury, via DDRS, contain the trading partner information needed for GTAS 

reporting. 

o Trading Partner Indicator Code (TP2) is equal to Department Regular (A1). 

Depending on what side of the transaction you are looking at, TP2 is in the SLOA it 

is the Department Regular (A1). TP2 and A1 are the same data element on a 

transaction (though different for trial balance reporting). Whether it is TP2 or 

A1, depends on what side of the transaction an organization is. 

o TP1 can be derived off of a value for TP2, at the time of reporting. TP1 is the 

federal “F”/Non-federal “N” indicator. TP2 is the Department Regular Code of the 

other federal entity involved in the transaction. 

o TP3, the Business Partner Number, useful for intra-governmental transactions, 

must be associated with the transaction. This is the Data Universal Numbering 

System (DUNS) number at the federal level or “DOD” + DoDAAC for DoD 

organizations. 

o Trading Partner Main Account (TP4) is equal to Main Account (A3). Depending 

on which side of the transaction one is looking, TP4 is in the SLOA it is the Main 

Account (A3). TP4 and A3 are the same data element on a transaction (though 

different for trial balance reporting). Whether it is TP4 or A3, depends on what 

side of the transaction an organization is. 

 Federal interfaces and/or interfaces with other federal agencies should be evaluated on a 

case by case basis to address SLOA interoperability and audit readiness requirements. 

 Enterprise systems, such as Mechanization of Contract Administration Services (MOCAS), 

Centralized Master Edit Table (CMET), Automated Disbursing System (ADS), Defense 

Cash Accountability System (DCAS), etc. are required to update LOA maps to the SLOA 

format for applicable systems. DCAS will require one supplemental data screen to 

accommodate 

the supplemental data in the SLOA for cross-disbursements. 
ADC 1043 

Enclosure 1, page 10 

 For Transactions by Others; Transactions for Others, multiple pay offices will be 

identified by a breakout of Agencies Disbursing Identifier with each breakout indicating 

the specific pay office associated with the responsible Components. 

 Besides for the MilPers appropriation, Budget Sub-Activity and Budget Activity 

information can be derived from the BLI level. 

 For the Military Personnel Appropriation, the Budget Line Item field, for exchange, should 

include both the value for Budget Sub-Activity and Budget Line Item. For the system’s 

base configuration of the Budget Sub-Activity and Budget Line Item should still be 

separate fields as defined in the SFIS Business Rules. 

 The Enterprise Funds Distribution System (EFD) must be used for validating the values 

for the following data elements: 

o Main Account 

o Beginning Period of Availability FY 

o Ending Period of Availability FY 

o Budget Subactivity Code 

o Budget Line Item 

*EFD nomenclature is available at https://guidanceweb.ousdc.osd.mil/efd.aspx 

**Note: EFD deploying incrementally; as such not all accounts are currently 

represented within EFD. 

 This memo requires the updating of PDS to meet this requirement. For PDS, there will 

be new XML data tags for each of the SFIS data elements found in this SLOA. 

 Within 30 days subsequent to the signing of this policy memo, the OUSD(C) will 

recommend SLOA requirements to OUSD(AT&L) to update Block 14 on DD Form 

448, Military Interdepartmental Purchase Request. 

 Product Service Code (PSC), a planned BEA 10.0 SFIS addition, supports OMB 

requirements for agencies to submit efficiency data via PSC. 

 Document Numbers e.g., PO, PO/Contract Numbers are header level information; the 

SLOA is line-item level information. There is not a need to repeat the same document 

number/contract number for each line item. Those types of data elements will be included 

in the larger standard transaction set. 

 Recommended ERP configuration guidance will be incorporated in to the SAP and Oracle 

SFIS Configuration Guides, the development of transitions plans will be part of the 

Investment Review Board (IRB) process, and it will be discussed and validated as part of 

the SFIS Validation process. 

 The Defense Departmental Reporting System (DDRS) only receives Trial Balance data, 

not the SLOA. 

 Until specific business rules are identified for the data elements in italics, targeted to be 

in the BEA 10.0, systems will not be required to re-configure their system to include 
ADC 1043 

Enclosure 1, page 11 

those elements. The SFIS Governance Board will establish specific business rules to 

address the purpose and details for how systems should capture these elements. 

 As identified on the SFIS checklist, the elements required for this SLOA only include 

those required based on each individual system function(s). Thus, the requirement to provide the 

stated SLOA elements during outbound/inbound data exchange is only applicable to those 

elements required given a system’s function.
ADC 1043 

Enclosure 2, page 1 

Enclosure 2, SLOA Elements and DLMS Element Changes in LOGDRMS 

If not otherwise noted, the BEA source information will be perpetuated to LOGDRMS. The 

business rules outlined for the SFIS data elements are primarily for database storage and usage. 

They are included below for information regarding database configuration management and data 

element definitions in the buyer/seller’s Automated Information System. 
ADC 1043 

Enclosure 2, page 2 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(1) SUB CLASS CODE “Treasury 

Sub Class” 

is renamed 

to simply 

“Sub Class 

Code”. 

Definition is 

adjusted to 

the BEA 

10.0 

definition 

presented 

here.

BEA Definition: Sub Class Codes are assigned in certain cases for grouping 

designated disbursement and/or receipt transactions below the level of 

appropriation or fund account represented by the main account, Reference Item 

A3, Main Account for an Appropriation, Fund, or Receipt Account. Separate 

sub-class identification codes are assigned to agencies by the Treasury to be used 

as parenthetical prefixes to the main account when preparing Disbursing Officer 

Reports. 

 Example(s):

46 Payments from Current Appropriations for Obligations of Closed Accounts 

72 Unamortized Discount on Investments 

85 Repayment of Borrowing from U.S. Treasury 

98 Redemption (Sale) of U.S. Public Debt Securities 

Values: For a complete set of values, please visit: Treasury Financial Manual 

http://fms.treas.gov/tfm/index.html 

Legacy Equivalent Terminology: None. 

Syntax: Two numeric 

 Business Rules:

 Sub Class Code must be used for accounting classification and financial 

reporting. 

 Each system must store and maintain Sub Class Code values. 

Staffing Note: OUSD(C) and ODCMO were asked to comment on whether 

Sub-Class is being subsumed by Business Event Type Code (BETC) and 

whether it should be included in DLMS transactions. OUSD(C) and ODCMO 

responded that most DOD values are standard values that will ultimately be 

accommodated by the BETC. However, Treasury may assign additional values 

in the future. Currently, it is anticipated that the Sub-class Code field would be 

null when BETC is fully implemented. Until BETC is fully implemented, there 

is one current scenario for disbursements or adjustments for obligations that 

would have been properly made to a cancelled appropriation that would cite Subclass 46. These may be disbursed from an unexpired appropriation with the 

same purpose up to a cumulative limit of one percent of the unexpired 

appropriation. 

Resolution: Adoption of the sub-class code in DLMS transactions and on the 

SFIS Fund Code to Fund Account Appropriation Table is deferred. Additional 

research and coordination will be required to confirm logistics requirements and 

determine business rules for use of sub-class. Upon completion of this effort, 

requirements will be re-staffed as an addendum to ADC 1043. 
ADC 1043 

Enclosure 2, page 3 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(2) DEPARTMENT TRANSFER CODE None 

BEA Definition: The Department Transfer Code identifies the federal agency of 

obligation authority to the DoD or one of its components. For the transfer of 

obligation authority, the transfer agency retains responsibility for the fund account 

and the recipient agency charges against the fund account of the transfer agency.

 Examples:

089 In the above example, the Department Transfer Value "089"indicates transfer 

of obligation authority from the Department of Energy. 

Values: For a complete set of values, please visit Treasury FAST Book II 

http://fms.treas.gov/fastbook/ 

Legacy Equivalent Terminology: Transfer Department, Transfer Agency 

Syntax: Three numeric 

 Business Rules: 

 Department Transfer Code must be 3 numeric characters. ex. 097 (Note: 

Programs may use the two character code and derive the three character 

version - with a leading zero - at time of reporting if the software system 

in use has not yet been updated). 

 Department Transfer Code must be used for accounting classification, 

 Each system must store and maintain Department Transfer Code 

Staffing Note: OUSD(C)/ODCMO were asked if Department Transfer Code is 

applicable to Interfund billing. It was determined that it is applicable. 

Resolution. Department Transfer Code will be included in the SFIS Fund Code to 

Fund Account Conversion Table and passed in DLMS transactions as applicable. 
ADC 1043 

Enclosure 2, page 4 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(3) Department Regular Code None 

BEA Definition: Department Regular is the US Treasury designated code 

representing the government agency accountable for one or more fund accounts 

established and maintained by the Treasury. The Department Regular element is 

an integral part of the Treasury Appropriation Fund Symbol (TAFS).

Example(s): 097 DoD, Office of the Secretary of Defense 

 021 Department of the Army 

 017 Department of the Navy 

 057 Department of the Air Force 

 096 Corps of Engineers 

Values: For a complete set of values, please visit: Treasury Financial Manual 

http://fms.treas.gov/fastbook/ 

Legacy Equivalent Terminology: Treasury Index, Department Code 

Syntax: three numeric 

 Business Rules: 

 Department Regular Code must be 3 numeric characters. ex. 097 

 Each system must store and maintain Department Regular Code values. 

 A Department Regular Code must be established in the accounting 

classification structure when the appropriation is signed by the President 

and must be maintained until available funding has been canceled. 

 Department Regular Code must be used for accounting classification, 

general ledger posting, financial reporting, and funds control. 
ADC 1043 

Enclosure 2, page 5 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(4) BEGINNING PERIOD OF AVAILABILITY Definition is 

adjusted to 

the BEA 

10.0 

definition 

presented 

here. 

BEA Definition: In annual and multi-year accounts, identifies the first year of 

availability under law that an account may incur new obligations. 

Example(s): If multi-fiscal Year Period of Availability where the initial fiscal 

year of availability is FY2006 - 2006. 

Values: Values are updated yearly.

Legacy Equivalent Terminology: Beginning Year, Annual Year, Multi Year, 

Fiscal Year, Program Year, Appropriation Derived based on year values and 

appropriations. 

Syntax: four alpha-numeric 

 Business Rules: 

 For Annual or Multi-Year funding, Beginning Period of Availability must 

be four alpha-numeric characters. 

 If used for No-Year funding, Beginning Period of Availability must be 

must be blank. 

 If the Beginning Period of Availability is associated with a 

clearing/suspense Main Account, then it must be blank. 

 If the Beginning Period of Availability is associated with an unavailable 

receipt account, then it must be blank. 

 If used for Annual or Multi-Year funding, Beginning Period of 

Availability must be used for accounting classification, financial 

reporting, and funds control. 

 If used for Annual or Multi-Year funding, each accounting system must be 

able to store, maintain, and report the Beginning Period of Availability for 

annual and multi-year appropriations. 

 When the warrant is established by Treasury according to the signed 

appropriation bill, Beginning Period of Availability must be established 

and maintained in the accounting classification structure.
ADC 1043 

Enclosure 2, page 6 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(5) ENDING PERIOD OF AVAILABILITY Definition is 

adjusted to 

the BEA 

10.0 

definition 

presented 

here. 

BEA Definition: In annual and multi-year accounts, identifies the last year of 

availability under law that an account may incur new obligations.

Example(s): If multi-fiscal year Period of Availability where the ending fiscal 

year of availability is FY2008 - 2008. 

Values: Values are updated yearly.

Legacy Equivalent Terminology: Ending Year, Annual Year, Multi Year, 

Fiscal Year, Program Year, Appropriation Derived based on year values and 

appropriations. 

Syntax: four alpha-numeric 

 Business Rules: 

 Ending Period of Availability must be four alpha-numeric characters. 

 If the Ending Period of Availability is associated with no-year funding, 

then it must be blank. 

 If the Ending Period of Availability is associated with a clearing/suspense 

Main Account, then it must be blank. 

 If the Ending Period of Availability is associated with an unavailable 

receipt account, then it must be blank. 

 If used for Annual or Multi-Year funding, Ending Period of Availability is 

used for accounting classification, financial reporting, and funds control. 

 If used for Annual or Multi-Year funding, each accounting system must be 

able to store, maintain, and report the Ending Period of Availability for 

annual and multi-year appropriations. 

 When the warrant is established by Treasury according to the signed 

appropriation bill, Ending Period of Availability must be established and 

maintained in the accounting classification structure.
ADC 1043 

Enclosure 2, page 7 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(6) AVAILABILITY TYPE CODE New DLMS 

This is a component of the TAS. Identifies no-year TAS, clearing/suspense TAS, element 

and canceled TAS. This field is blank for TAS that have a beginning and ending 

period of availability and unavailable receipt TAS.

Values: C = Canceled TAS 

 F = Clearing/Suspense TAS 

 X = Identifies no-year TAS including Deposit Funds 

 Null = Annual, Multi-Year or unavailable/misc. receipt accounts 

Legacy Equivalent Terminology: None.

Syntax: one alpha-numeric 

 Business Rules: 

 Availability Type Code must be 1 alpha characters. 

 Each system must store and maintain Availability Type Code values. 

 If used for Annual or Multi-Year funding, Availability Type Code must be 

blank. 

 If used for No-Year funding, Availability Type Code must be X. 

 If used for clearing/suspense Main Accounts, Availability Type Code 

must be F. 

 If used for canceled Main Accounts, Availability Type Code C may be 

derived at the time of reporting. 

 If used for unavailable/miscellaneous receipt Main Accounts, Availability 

Type Code must be blank. 

 Availability Type Code must be used for accounting classification, 

financial reporting, and funds control. 

 When the warrant is established by Treasury according to the signed 

appropriation bill, Availability Type Code must be established and 

maintained in the accounting classification structure. 
ADC 1043 

Enclosure 2, page 8 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(7) MAIN ACCOUNT CODE None 

BEA Definition: The main account is identified by a four digit numeric data 

element representing a specific appropriation or fund account established by the 

U.S. Treasury for expenditure or receipt authority issued by the U.S. Congress.

Examples: 0740 Family Housing Construction, Air Force 

 2020 Operation & Maintenance, Army 

 2040 Research, Development, Test & Eval, Army 

 2050 Military Construction, Army 

 4557 Revolving Fund, National Defense Sealift 

 5095 Wildlife Conservation, Military Reservations 

 8097 Military Retirement Fund, Defense 

Values: For a complete set of values, please visit: Treasury Financial Manual 

http://fms.treas.gov/fastbook/ 

Legacy Equivalent Terminology: Basic Symbol, Appropriation Symbol 

Syntax: four numeric 

 Business Rules: 

 Each Main Account Code must be associated with only one Fund Type 

Code. 

 Each Main Account Code must be associated with only one Budget 

Function/Sub-Function Code. 

 Main Account Code must be 4 numeric characters. 

 Main Account Code must be used for accounting classification, general 

ledger posting, financial reporting, and funds control. 

 Each system must store and maintain Main Account Code values. 

 A Main Account Code must be established in the accounting classification 

structure when the appropriation is signed by the President and will be 

maintained until available funding has been canceled.
ADC 1043 

Enclosure 2, page 9 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(8) SUB-ACCOUNT CODE None 

BEA Definition: The Sub-Account symbol is used to specify subsidiary level 

accounts associated to the main account of the TAFS. The Sub-Account might 

indicate a series of subsidiary level receipt accounts or represent special 

subsidiary level accounts requested for use by an agency and approved by the US 

Treasury. Sub-account balances aggregate to the main account balance. The SubAccount has the potential for several relationships to the Main Account. 

Example(s): 000 – Default 

 001 – Defense Working Capital Fund, Army 

 002 – Defense Working Capital Fund, Navy 

Values: For a complete set of values, please visit: Treasury Financial Manual, 

http://fms.treas.gov/fastbook/ 

Legacy Equivalent Terminology: Derived from the Limit, Subhead, Receipt 

Indicator 

Syntax: three numeric 

 Business Rules: 

 Every financial transaction processed must have a valid Sub-Account 

Code. 

 The Sub-Account Code must be defaulted to “000” when one of the 

Treasury Sub-Account Code conditions does not apply. 

 Sub-Account Code must be 3 numeric characters. ex. 97X4930.001 (last 

3 positions following period) 

 Sub-Account Code must be used for accounting classification, general 

ledger posting, financial reporting, and funds control. 

 Each system must store and maintain Sub-Account Code values.
ADC 1043 

Enclosure 2, page 10 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(9) BUSINESS EVENT TYPE CODE (BETC) New DLMS 

Definition: Indicates the type of financial activity, such as payments, collections, element 

borrowings, etc., being reported in the Government-wide Accounting and 

Reporting (GWA) system. BETC in effect replaces the Treasury's transaction 

codes and standard sub-classes that are currently used on central accounting 

reports. New U.S. Treasury requirement effective 08/01/2006 per TFM Bulletin 

No. 2006-04, Volume I. 

Example(s): BETC Value Business Event 

 COLL Offsetting Collection 

 UNRLDISC Unrealized Discount 

 DISB Gross Disbursement 

Values: For a complete set of values, please visit: Treasury Fact Sheet 

http://fms.treas.gov/gwa/factsheet_betc.html 

Syntax: eight alpha characters 

 Business Rules: 

 Business Event Type Code (BETC) must be no more than 8 alpha 

characters. 

 Each system must store and maintain Business Event Type Code (BETC) 

values. 

 Business Event Type Code (BETC) must be used for general ledger 

posting, and financial reporting.

Staffing Note: Clarification was sought regarding if BETC would apply to 

logistics transactions or if it applied to only the financial Central Account Offices 

for Treasury reporting. This has not been fully resolved. 

Resolution. Adoption of the BETC in DLMS transactions is deferred. Additional 

research and coordination will be required to confirm logistics requirements and 

determine business rules for use of BETC. Upon completion of this effort, 

requirements will be re-staffed as an addendum to ADC 1043.
ADC 1043 

Enclosure 2, page 11 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(10) OBJECT CLASS CODE New DLMS 

BEA Definition: Object classes are categories in a classification system that element 

present obligations by the items or services purchased by the Federal 

Government. These are the major object classes: 

• 10 Personnel compensation and benefits. 

• 20 Contractual services and supplies. 

• 30 Acquisition of assets. 

• 40 Grants and fixed charges. 

• 90 Other. 

OMB divides these major classes into smaller classes and presents them in object 

class schedules. The classes present obligations according to their initial purpose, 

not the end product or service. For example, if you pay a Federal employee who 

constructs a building, classify the obligations for the employee’s wages under 

Personnel compensation and benefits, rather than Acquisition of assets. If you 

purchase a building, classify the contractual obligations under Acquisition of 

assets. 

 Example(s): 

 Series Code Description 

 (11-19) Personnel compensation and benefits. 

 11 Personnel Compensation 

 11.1 Full-Time Permanent (Civilian) 

 11.3 Other Than Full Time Permanent 

 11.5 Other Personnel Compensation 

 11.7 Military Personnel 

 11.8 Special Personal Services Payments 

 11.9 Total Personnel Compensation 

 12 Personnel Benefits 

 12.1 Civilian Personnel Benefits 

 12.2 Military Personnel Benefits 

 13 Benefits of Former Personnel 

Values: For a complete set of values, please visit: OMB Circular A11 

http://www.whitehouse.gov/omb/circulars/a11/current_year/a11_toc.html 

Syntax: six numeric 

 Business Rules: 

 The Office of Management and Budget (OMB) designated object 

classification codes must be used when posting general ledger transaction 

to record the effect of budgetary expenditures. 

 Object Class Codes must be used to present obligations by the items or 

services purchased by the Federal Government. 

 Object Class Code must be a maximum of 6 numeric characters. 

 Object Class Code must be used for financial reporting, accounting 

classification. 

 Each system must store and maintain Object Class Code values.
ADC 1043 

Enclosure 2, page 12 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(11) REIMBURSABLE FLAG INDICATOR New DLMS 

BEA Definition: The Reimbursable Indicator is used to flag those expenditures element 

incurred for a designated TAFS account that are considered reimbursable to the 

account. 

Example(s): An "R" affiliated with the items posted to the 4 digit main account 

of a TAFS indicates those recoverable expenditures associated with the following: 

 - Reimbursements for Sale of Material, e.g., Sale of Inventory Material, 

Replacement of Like-Items, and Free Assets, i.e., assets disposed of not requiring 

replacement 

 - Reimbursable Expenditures From General Funds Based on Customer Orders 

 - Defense Working Capital Funds- To indicate the expenditure items to be 

recovered through full recovery pricing, including the full (direct and indirect) 

actual costs incurred, including Reserve Material, Military Personnel, Operations 

and Maintenance, Base Support, RDT&E, Design/Development, Construction, 

Unplanned Losses, and other recoverable costs. 

Values: For a complete set of values, please visit USSGL Supplement to the 

Treasury Financial Manual 

http://fms.treas.gov/ussgl/selection_page.html

Legacy Equivalent Terminology: None. 

Syntax: Up to 1 alpha 

 Business Rules:

 When the funding source is a direct appropriation, the value must be 'D', 

otherwise the value is 'R'. 

 Reimbursable Flag Indicator must be used for financial reporting and 

accounting classification. 

 Each system must store and maintain Reimbursable Flag Indicator values. 

 Derivation of Reimbursable Flag values at the time of reporting based on a 

breakout at the Fund level is an acceptable practice. 

Staffing Note: Clarification was requested from OUSD(C)/ODCMO regarding 

the applicability of this data element for Interfind billing. OUSD(C)/ODCMO 

clarified that there are instances where it would apply. 

Resolution. Reimbursable Flag will be carried in DLMS transactions. In addition, 

this data element will be considered for inclusion in the SFIS Fund Code to Fund 

Account Conversion Table, if feasible, as a subsequent development phase. 
ADC 1043 

Enclosure 2, page 13 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(12) BUDGET LINE ITEM IDENTIFIER New DLMS 

BEA Definition: Identifies further sub-divisions of the Treasury Account Fund element 

Symbol appropriation, below the Budget Sub Activity Level.

Example(s): Sample Budget Line Items (BLI) for Aircraft BAs and BSAs: 

PROCUREMENT uses "Weapons System Code"- i.e. 8485A11000 JOINT 

CARGO AIRCRAFT (JCA) 

RDT&E uses "OSD Program Element" - i.e. BSA 0204136N F/A-18 Squadrons 

MILCON uses "Location & Project" - i.e. 4962 05057041 

O&M uses "SAG Code"- i.e. 1A1A OPERATIONAL FORCES 

MILPERS use is Optional 

WCF uses "Activity" - i.e. Accounting-Navy 

Values: For a complete set of values, please visit: Defense Budget Materials 

Website http://comptroller.defense.gov/Budget2013.html 

Legacy Equivalent Terminology: Same as examples listed above 

Syntax: Up to 16 alpha numeric characters 

 Business Rules: 

 Budget Line Item Identifier may be up to 16 alpha numeric characters. 

 Budget Line Item Identifier must be used for accounting classification, 

financial reporting, and funds control. 

 Each system must store and maintain Budget Line Item Identifier values. 

 A Budget Line Item Identifier must be established in the accounting 

classification structure when the appropriation is signed by the President 

and will be maintained until available funding has been canceled. 

 A Budget Line Item must be associated with at least one Program Code.
ADC 1043 

Enclosure 2, page 14 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(13) SECURITY COOPERATION CUSTOMER CODE Variant of 

existing 

DLMS 

element. 

Logistics 

transactions 

will retain a 

two 

character 

max for 

logistics 

transactions. 

BEA Definition: Represents the country receiving the product and/or service in 

the FMS transaction. 

DLMS Definition: Identifies the country, international organization, or account 

for security assistance purposes. This is the security cooperation customer that is 

the recipient of materiel or services sold, leased, loaned, transferred, exchanged, 

or furnished under Foreign Military Sales, or the recipient of materiel or services 

furnished under Grant Aid. The Security Cooperation Customer Code is 

restricted to two-positions under DLMS. 

Example(s): Code Customer 

 S3 SLOVENIA 

 EI IRELAND 

 UK UNITED KINGDOM 

Values: For a complete set of values, please visit Defense Security Cooperation 

Agency: 

http://www.samm.dsca.mil/table/table-c4t2a 

http://www.samm.dsca.mil/table/table-c4t2b 

http://www.samm.dsca.mil/table/table-c4t2c 

http://www.samm.dsca.mil/table/table-c4t2d 

Syntax: three alpha-numeric 

 Business Rules: 

 Security Cooperation Customer Code must be 3 alpha-numeric characters. 

 Security Cooperation codes must be used for financial reporting, 

accounting classification, and funds control. 

 If the system executes Foreign Military Sales transactions, then each 

system must store and maintain Security Cooperation Customer Code 

values.
ADC 1043 

Enclosure 2, page 15 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

Staffing Note: The Security Cooperation Customer Code is embedded as the 2nd

and 3rd position of the document number for Security Assistance transactions. It 

was already identified as a DLMS enhancement. SFIS matrix business rule 

requiring 3 alpha-numeric conflicts with current guidance for using two character 

code consistent with the listed authoritative DSCA source values. ODCMO was 

asked to confirm the proper syntax and business rule for this element and related 

SFIS element Country Code (T12). DSCA replied, indicating that while all 

current values are two characters, DSCA is allowing for future growth. However, 

because it is part of the document number and used to construct the military 

assistance program address code (MAPAC), expansion of the security 

cooperation customer code to three characters has significant impacts for 

MILSTRIP and MAPAC processes, as well as other processes that use or 

perpetuate this data. Such a change would essentially break the logistics process 

for security cooperation requisitioning and shipment. At a minimum, expanding 

the field length to three characters requires a PDC to communicate the business 

rules and procedure changes and define a proposed implementation strategy. 

Resolution: Logistics processes under the DLMS will retain a two character 

maximum length.
ADC 1043 

Enclosure 2, page 16 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(14) SECURITY COOPERATION IMPLEMENTING AGENCY CODE New DLMS 

Definition: A single character alpha code which identifies the US Military Element . 

Department or Agency which has negotiated or facilitated a foreign military sales 

case on behalf of the US Government. The majority of FMS cases are 

implemented by the Army (IA Code B), Navy (IA Code P) or Air Force (IA Code 

D). 

DLMS Definition: The Implementing Agency (IA) Code identifies the military 

department or defense agency responsible for the execution of military assistance 

programs. With respect to Foreign Military Sales (FMS), the military department 

or defense agency assigned responsibility by the Defense Security Cooperation 

Agency to prepare a Letter of Offer and Acceptance (LOA) and to implement an 

FMS case. The implementing agency is responsible for the overall management 

of the actions that will result in delivery of the materials or services set forth in 

the LOA that was accepted by a foreign country or international organization. 

For Military Service and Missile Defense Agency sponsored FMS cases, the IA 

code is equivalent to the Service/Agency code used in the first position of the 

document number; for all other Defense Agencies the IA does not equate to the 

Service/Agency code .The only IA codes authorized for MILSTRIP requisitioning 

are B (Army), D (Air Force), I (Missile Defense Agency), P (Navy), and R 

(DLA). 

Example(s): Code Implementing Agency 

 B Army 

 P Navy 

 D Air Force 

 F Defense Contract Management Agency (DCMA) 

 C Defense Information Systems Agency (DISA) 

 R Defense Logistics Agency (DLA) 

 Q Defense Security Cooperation Agency (DSCA) 

 Z Defense Threat Reduction Agency (DTRA) 

 I Missile Defense Agency (MDA) 

 U National Geospatial-Intelligence Agency (NGA) 

 M National Security Agency (NSA) 

Values: http://www.samm.dsca.mil/table/table-c5t2 

Syntax: one alpha-numeric 

 Business Rules: 

 Security Cooperation Implementing Agency Code must be 1 alphanumeric characters.

 Security Cooperation Implementing Agency Code must be used for 

financial reporting, accounting classification, funds control. 

 If the system executes Foreign Military Sales (FMS) transactions, then 

each system must store and maintain Security Cooperation Implementing 

Agency Code values. 
ADC 1043 

Enclosure 2, page 17 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

Staffing Note: This data element appeared initially to be a variant of the existing 

data element Service/Agency (S/A) Code when applicable to security cooperation 

due to the overlapping use of code values for organizations supported by 

MILSTRIP requisitioning activities. However, the BEA element is now 

considered a separate data element. There are IA values from the Security 

Assistance Management Manual (SAMM) (available from the E-SAMM Web at 

http://www.samm.dsca.mil/table/table-c5t2) that do not fully align with some 

logistics S/A codes. For example, the E-SAMM code for DLA (Code R) does not 

align with the S/A code for DLA FMS (Code T) and it conflicts with an S/A code 

for Navy. Some other security cooperation implementing agency codes (i.e. C, F, 

M, Q, U, Z) conflict with codes assigned for requisitioning purposes in the S/A 

code list; however, these are currently non-requisitioning implementing agencies. 

There is a S/A code for Marine Corps FMS (Code K), but since Marine Corps has 

no security cooperation cases a security cooperation implementing agency code is 

not assigned. Should the Marine Corps require, Code K is an available security 

cooperation implementing agency code which would simplify mappings for S/A 

code purposes. 

Resolution: DLM 4000.25-1 MILSTRIP Appendix 2.2 S/A codes are the 

authoritative source for supply transactions (e.g., requisitioning). DSCA has 

indicated that the SAMM codes cannot be de-conflicted with the S/A codes. 

DLMS will, therefore, require additional DAAS mapping to convert the DLA S/A 

Code T to IA Code R (additional coordination will be required if other IA codes 

must be used for requisitioning).
ADC 1043 

Enclosure 2, page 18 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(15) SECURITY COOPERATION CASE DESIGNATOR CODE “Foreign 

Military 

Sales (FMS) 

Case 

Designator 

Number” is 

renamed 

“Security 

Cooperation 

Case 

Designator”. 

Definition is 

adjusted to 

the BEA 

10.0 

definition 

presented 

here. 

Definition: Security Cooperation Case Designator code is used to reflect a FMS 

contractual sales agreement (Letter of Offer and Acceptance) between the U.S. 

and an eligible foreign country. 

The Security Cooperation Customer Code is restricted to two-positions under 

DLMS.

DLMS Definition: Security Cooperation case designator code is used to reflect a 

FMS contractual sales agreement (Letter of Offer and Acceptance) between the 

U.S. and an eligible foreign country. It is a unique code used with the Security 

Cooperation customer code to identify a particular foreign military sale. The 

Security Cooperation case designator is restricted to three-positions under DLMS. 

Values: For a complete set of values, please visit: 

http://comptroller.defense.gov/fmr/current/15/15_02.pdf

Syntax: four alpha-numeric 

 Business Rules: 

 Security Cooperation Case Identifier must be 4 alpha-numeric characters. 

 Security Cooperation Case Designator codes must be used for financial 

reporting, accounting classification, and funds control. 

 If the system executes Foreign Military Sales (FMS) transactions, then 

each system must store and maintain Security Cooperation Case 

Designator values. 

 Each Security Cooperation Case Designator must have at least one 

Security Cooperation Customer Code. 

 Each Security Cooperation Case Designator must have at least one 

Security Cooperation Case Line Item Identifier. 

 Each Security Cooperation Case Designator must have only one Security 

Cooperation Implementing Agency. 

Staffing Note: This element is embedded as the last three positions of the 

supplementary address in Security Assistance related transactions. It was already 

identified as a DLMS enhancement under the DLMS name. During staffing, it 

was identified that the SLOA element has a maximum length of four positions. 

This field length cannot be accommodated within the MILSTRIP supplementary 

address field, which must be retained for legacy MILSTRIP users (including the 

FMS countries transmitting and receiving legacy MILSTRIP transactions). 

DSCA has been advised of this issue and will review impact and re-assess the 

requirement. 

Resolution: The DLMS data element will be updated to align with the SLOA 

data element name recorded in the BEA. DAAS will derive from the last three 

positions of supplementary address for legacy conversion.
ADC 1043 

Enclosure 2, page 19 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(16) SECURITY COOPERATION CASE LINE ITEM IDENTIFIER New DLMS 

Definition: The Security Cooperation Case Line Item Identifier is used to Element 

identify a detailed line item requirement contained within the (Letter of Offer and 

Acceptance).

Values: For a complete set of values, please visit DoD Financial Management 

Regulation, Vol. 15:http://comptroller.defense.gov/fmr/current/15/15_02.pdf 

Syntax: three alpha-numeric 

 Business Rules: 

 Security Cooperation Case Line Item Identifier must be 3 alpha-numeric 

characters. 

 Security Cooperation Case Line Item Identifier must be used for financial 

reporting, accounting classification, and funds control. 

 If the system executes Foreign Military Sales (FMS)transactions, then 

each system must store and maintain Security Cooperation Case Line Item 

Identifier values. 

 Security Cooperation Case Line Item Identifier must be associated with 

only one Security Cooperation Case Identifier.
ADC 1043 

Enclosure 2, page 20 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(17) SUB-ALLOCATION HOLDER IDENTIFIER New DLMS 

Definition: Sub-Allocation Holder Identifies an organization to which funds Element. 

have been Sub-Allocated.

Example(s): 0010 Washington Headquarters Services Building Management 

Program 

 0020 US. Court of Military Appeals (USCMA) 

 0100 Department of the Army.0101 US Army Reserve (USAR) 

 0102 Army National Guard (ARNG) 

 0103 Supervision, Inspection and Overhead (SIO) 

Values: For a complete set of values, please visit: DFAS Manual 7097.01

http://asafm.army.mil/offices/BU/Dfas709701.aspx?OfficeCode=1200 

Legacy Equivalent Terminology: Limit/Subhead 

Syntax: up to 4 alpha-numeric characters 

 Business Rules: 

 Sub-Allocation Holder Identifier must be 4 alpha numeric characters. 

 Sub-Allocation Holder Identifier must be used for financial reporting and 

funds accounting classification.

 Sub-Allocation must be store and maintained.

Staffing Note: This element was previously known as Limit/Subhead. 

Limit/Subhead is a data element referentially provided via fund code. 

Limit/Subhead will be included in the SFIS Fund Code to Fund Account 

Conversion Table to ensure continuity of operations, even though values may 

duplicate those ultimately assigned to sub-allocation. This is necessary because 

potential assignment of additional sub-allocation values to a main account may 

cause the number of fund codes to exceed the maximum available from the two 

position fund code. Future coordination will be needed to determine if 

limit/subhead can be mapped to sub-allocation holder. Definitions and business 

rules will need to be approved via the SFIS Governance Board. 

Resolution: Limit/Subhead will be retained on the SFIS Fund Code to Fund 

Account Conversion Table. Sub-allocation holder will be included in DLMS. 

DAAS will not map between the SLOA and legacy data elements. 

OUSD(C)/ODCMO will notify the Finance PRC Chair upon forming a working 

group for sub-allocation holder. 
ADC 1043 

Enclosure 2, page 21 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(18) AGENCY DISBURSING IDENTIFIER CODE New DLMS 

Definition: The Agency Disbursing Identifier is assigned to each disbursing element 

office by the Treasury Department. The Agency Disbursing Identifier is an 

identification number that indicates authority to receive and disburse public funds 

and issue checks on the United States Treasury. 

Example(s): DSSN Installation/Activity 

 1700 Personnel Support Activity Detroit 

 5037 OPLOC Dayton 

 70051514 DEPARTMENT OF HOMELAND SECURITY 

Values: For a complete set of values, please visit: https://beis.csd.disa.mil/beisxml/sfiscombo.xml 

Syntax: eight numeric 

 Business Rules: 

 When an Agency Disbursing Identifier Code is associated with any other 

element, the association must be available throughout accounting 

lifecycle. 

 Agency Disbursing Identifier (DSSN/ALC) Code may be up to 8 numeric 

characters. 

 Agency Disbursing Identifier Code must be used for funds control. 

 Each system must store and maintain Agency Disbursing Identifier Code 

values.
ADC 1043 

Enclosure 2, page 22 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(19) AGENCY ACCOUNTING IDENTIFIER CODE “Accounting 

Station 

Code 

(Agency 

Accounting 

Identifier / 

Account 

Manager’s 

Code)” is 

renamed 

“Agency 

Accounting 

Identifier 

Code”. 

Definition is 

adjusted to

the BEA 

10.0 

definition 

presented 

here.

Definition: The Agency Accounting Identifier Code identifies the accounting 

system responsible for recording the accounting event. The Agency Accounting 

Identifier Code is intended to be an accounting system identifier, and therefore 

must be assigned to only one accounting system. 

Example(s): FSN /AAA/ADSN Installation 

 044311 DFAS INDIANAPOLIS DEFENSE 

AGENCY DAI/BTA ATTN: DFAS-AI-IS 

 021001 DFAS INDIANAPOLIS (GFEBS) 

 385300 EXPEDITIONARY COMBAT SUPPORT 

SYSTEM (ECSS) (DFAS COLUMBUS) 

Values: For a complete set of values, please visit: https://beis.csd.disa.mil/beisxml/sfiscombo.xml 

Syntax: six numeric 

 Business Rules: 

 Agency Accounting Identifier Code (FSN/AAA/ADSN) may be 6 

numeric characters. 

 When an Agency Accounting Identifier Code is associated with any other 

element, the association must be available throughout accounting 

lifecycle. 

 Agency Accounting Identifier Code must be used for accounting 

classification. 

 Each system must store and maintain Agency Accounting Identifier Code 

values. 

 If there are multiple reporting organizations managing accounting within 

the system, a single accounting system may have more than one Agency 

Accounting Identifier Code. 

 Different organizations may also use the same Agency Accounting 

Identifier Code, if managed within the same accounting system. 

 Each accounting system must be represented by at least one Agency 

Accounting Identifier Code. 

 An Agency Accounting Identifier Code must not represent more than one 

accounting system.

Staffing Note: Subsequent to staffing of PDC 1043, possible alternatives were 

sought for carrying AAI in DLMS transactions, including adding the AAI to the 

SFIS Fund Code to Fund Account Conversion Table or using an existing 

FSN/ADSN field in DoDAAD. At this time, neither alternative has materialized. 

Resolution: Carry AAI in applicable DLMS transactions.
ADC 1043 

Enclosure 2, page 23 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(20) FUNDING CENTER IDENTIFIER New DLMS 

Definition: Funding Center is a clearly defined responsibility area within an element 

organizational unit to which budget authority is assigned.

 Example(s): 

Values: There is no list of values applicable for this element. 

Legacy Equivalent Terminology: None 

Syntax: up to 16 alpha numeric characters 

 Business Rules: 

 At the time of budget execution, a Funding Center Identifier must be 

associated with at least one cost object. The SFIS Cost Objects are 

Funding Center, Cost Center, Project, Activity, Cost Element Code, Work 

Order Number, & Functional Area. 

 Funding Center Identifier must be no more than 16 alpha-numeric 

characters. 

 Funding Center Identifier must be used for funds control and accounting 

classification. 

 Each system must store and maintain Funding Center Identifiers.

(21) COST CENTER IDENTIFIER New DLMS 

Definition: A Cost Center is a clearly defined responsibility area where costs are element 

incurred.

 Example(s): 

Values: There is no list of values applicable for this element. 

Legacy Equivalent Terminology: Cost Center, Assigned and Performing Cost 

Center, Profit Center, Assigned and Performing Profit Center, Sub Cost Center, 

Project Directed Line Item, Task Code, Element of Cost, Responsibility Cost 

Center, Organizational Responsibility Center 

Syntax: up to 16 alpha numeric characters 

 Business Rules: 

 Cost Center Identifier must be associated with one or more Funding 

Center Identifiers. 

Cost Center Identifier must be no more than 16 alpha-numeric characters. 

 Each system must store and maintain Cost Center Identifiers.

 Where Applicable, if Cost Center Identifier is used as a Cost Object, Cost 

Center Identifier must be used for accounting classification. 
ADC 1043 

Enclosure 2, page 24 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(22) PROJECT IDENTIFIER New DLMS 

element 

(Note that 

SLOA’s 

Project 

Identifier is 

an element 

whose 

content may 

differ from 

the DLMS 

equivalent 

Project 

Code) 

Definition: A planned undertaking of work to be performed or product to be 

produced having a finite beginning and end. 

 Example(s): 

Values: There is no list of values applicable for this element. 

Legacy Equivalent Terminology: Program Element, Cost Account Code, 

RDT&E Project Unit, Special Interest, Project Task 

Syntax: up to 25 alpha numeric characters 

 Business Rules: 

 Project Identifier may be no more than 25 alpha-numeric characters. 

 The Work Breakdown Structure may be applied as a breakdown for the 

Project Identifier. 

 Each Project Identifier must be associated with one or more Funding 

Center Identifiers. 

 If Project Identifier is used as the cost object, then the Project Identifier 

must be directly aligned with one or more Program Codes. 

 If Project Identifier is used as the cost object, then the Project Identifier 

will be used for cost accumulation. 

 If Project Identifier is used as the cost object, then each system must store 

and maintain Project Identifiers.

 Where Applicable, if Project Identifier is used as a Cost Object, Project 

Identifier must be used for accounting classification. 

Staffing Note: The DLMS/MILS three position project code is retained as a 

separate data element to represent a subset of the SLOA project identifier, and is 

defined as follows: Identifies requisitions and related documentation as to special 

programs, exercises, projects, operations or other purposes; also used for the 

purpose of distinguishing requisitions and related documentation and shipments, 

as well as for the accumulation of intra-service performance and cost data related 

to exercises, maneuvers, and other distinct programs, projects and operations. 

Project Codes for internal use or for use between two trading partners may be 

assigned by the Components. The SLOA project identifier may be different or it 

may repeat the project code value identified for logistics purposes, making it is 

necessary to carry both codes in DLMS. OUSD(C)/ODCMO noted no issues with 

this approach. 

Resolution: Retain existing project code in the LQ01 = 78, and include SLOA 

project identifier in FA201 (or REF01 as applicable). DAAS will not map 

between the data elements. 
ADC 1043 

Enclosure 2, page 25 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(23) ACTIVITY IDENTIFIER New DLMS 

Definition: An Activity is a series of events, tasks, or units of work that are element 

linked to perform a specific objective.

 Example(s): 

Values: There is no list of values applicable for this element. 

Legacy Equivalent Terminology: Ship, Ship Class, Cost Account Code, 

Military Expense Reporting System Code, Resource Pool, RID, Element of Cost 

Syntax: up to 16 alpha numeric characters 

 Business Rules: 

 Activity Identifier must be no more than 16 alpha-numeric characters. 

 If Activity Identifier is used as the cost object, then the Activity Identifier 

must be directly aligned with one or more Program Codes. 

 Each Activity Identifier must be associated with one or more Funding 

Center Identifiers. 

 If Activity Identifier is used as the cost object, then Activity Identifier will 

be used for cost accumulation. 

 If Activity Identifier is used as the cost object, then each system must 

store and maintain Activity Identifiers.

 Where Applicable, if Activity Identifier is used as a Cost Object, Activity 

Identifier must be used for accounting classification. 

Staffing Note: SFIS matrix conflicts between the length characteristic (i.e. 15) 

and the business rule (i.e. 16). OUSD(C) was asked to clarify which was the 

correct max length. OUSD(C)/DCMO verified the proper maximum length is 16. 

Resolution: DLMS will implement the element with a maximum length of 16. 

DCMO noted they will correct typo for the maximum length in BEA.
ADC 1043 

Enclosure 2, page 26 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(24) COST ELEMENT CODE New DLMS 

Definition: Cost Element is a classification of an organization's revenues, element 

expenses or consumable resources. Cost Element Code only relates to primary 

cost. Cost Element Code does not relate to secondary cost which is identified as 

agency specific and not enterprise-level.

 Example(s): 

Values: There is no list of values applicable for this element. 

Legacy Equivalent Terminology: Expense Element, Expenditure Category, 

Expenditure Type, Material Group, Resource Pool, RID, Element of Cost, Cost 

Code 

Syntax: up to 16 alpha-numeric characters 

 Business Rules: 

 Cost Element Code must be no more than 16 alpha-numeric characters. 

 Each system must store and maintain Cost Element Codes. 

 Where Applicable, if Cost Element Code is used as a Cost Object, Cost 

Element Code must be used for accounting classification. 

Staffing Note: SFIS matrix conflicts between the length characteristic (i.e. 16) 

and the business rule (i.e. 15). OUSD(C) was asked to clarify which was the 

correct max length. OUSD(C)/DCMO verified the proper maximum length is 16. 

Resolution: DLMS will implement the element with a maximum length of 16. 

DCMO noted they will correct typo for the maximum length in BEA.
ADC 1043 

Enclosure 2, page 27 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(25) WORK ORDER NUMBER New DLMS 

element 

(Note 

SLOA’s 

Work Order 

Number as 

an element 

whose 

content may 

differ from 

the DLMS 

equivalents) 

Definition: Identifies an individual unit of work, batch, or lot of a distinct 

product or service. 

 Example(s): 

Values: There is no list of values applicable for this element. 

Legacy Equivalent Terminology: Job Order Number, Job Order Cost Code, 

Work Breakdown Structure, Project Task, Job Order Cost Code 

Syntax: up to 16 alpha-numeric characters 

 Business Rules: 

 Cost Element Code must be no more than 16 alpha-numeric characters. 

 A Work Order Number must be associated with one or more Fund Center 

Identifiers. 

 If Work Order Number is used as the cost object, then the Work Order 

Number must be directly aligned with one or more Program Codes. 

 Where Applicable, if Work Order Number is used as the cost object, then 

Work Order Number must be used for cost accumulation. 

 If Work Order Number is used as the cost object, then each system must 

store and maintain Work Order Numbers.

Staffing Note: Under DLMS the work order number, the job order number the 

work breakdown structure may also be carried for specific user communities as 

separate data elements in various transactions. 

Resolution: Retain the existing DLMS work order number and job order number 

in the REF/N9 segments. Include the SLOA work order number in FA201 (or 

REF01 as applicable) for optional use. DAAS will not map between the data 

elements. 
ADC 1043 

Enclosure 2, page 28 

SLOA 

# 

SFIS/SLOA Element Description DLMS 

Element 

Change 

(26) FUNCTIONAL AREA IDENTIFIER New DLMS 

Definition: Functional Area is a logical division of a Component's business element 

operations. It represents the Functions the Component performs.

 Example(s): 

Values: There is no list of values applicable for this element. 

Syntax: up to 16 alpha-numeric characters 

 Business Rules:

 Functional Area Identifier must be no more than 16 alpha-numeric 

characters. 

 A Functional Area must be associated with only one Fund Center 

Identifier. 

 If Functional Area is used as the cost object, then each system must store 

and maintain Functional Area. 

 Where Applicable, if Functional Area is used as a Cost Object, Functional 

Area must be used for accounting classification. 

 Functional Area must be associated to only one Budget Activity Identifier. 

 Functional Area must be associated to only one Budget Sub Activity 

Identifier. 

 Functional Area must be associated to only one Budget Line Item 

Identifier. 

 Functional Area must be associated to only one Security Cooperation 

Customer Code. 

 Functional Area must be associated to only one Security Cooperation Case 

Identifier. 

 Functional Area must be associated to only one Security Cooperation Case 

Line Item Identifier. 

 Functional Area must be associated to only one Security Cooperation 

Implementing Agency Code. 
ADC 1043 

Enclosure 3, page 1 

ENCLOSURE 3 

REVISIONS TO DLMS IMPLEMENTATION CONVENTIONS 

# Location 180M Material Returns Reporting Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043 

- ADC 1043, DLMS Revisions for Department of 

Defense (DoD) Standard Line of Accounting 

(SLOA)/Accounting Classification 

Identifies DLMS Changes 

included in the DLMS IC 

2. 2/LQ01/058 Add a second DLMS note to existing qualifier 78: 

78 Project Code 

DLMS Note: 

1. Use as needed to identify special programs, 

exercises, projects, operations, and other purposes. 

2. For DoD SLOA/Accounting Classification 

compliance the Project Code may be repeated as a 

Project Identifier (FA201 Qualifier 90). Refer to 

ADC 1043. 

SLOA compliance requires 

identification of the Project 

Identifier for which the 

Project Code is an 

authorized legacy 

equivalent. Project Code is 

retained as a separate data 

element for logistics 

business processes 

requiring specific 

identification of this 

information. 

3. 2/FA2/226 Modify the existing segment level DLMS note: 

DLMS Note: Use this segment to comply with the DoD 

SLOA/Accounting Classification. Cost object elements 

Project Identifier, Funding Center Identifier, 

Functional Area, Cost Element Code, Cost Center 

Identifier, Activity Identifier, and Work Order Number 

are used as appropriate for the system.All qualifiers 

listed below - with exception of B5, Fund Code - are 

associated with a DLMS enhancement, with the 

exception of B5, Fund Code; see introductory DLMS 

note 2a.

Clarifies the location of 

SLOA/Accounting 

Classification data. 

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

89 Budget Line Item Identification 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

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

2. Qualifier 89 is a migration code approved for use 

in X12 version 4020. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

These qualifiers have been 

mapped to specific SFIS 

data elements for SLOA. 
ADC 1043 

Enclosure 3, page 2 

# Location 180M Material Returns Reporting Reason 

2/FA201/226 A1 Department Indicator 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Department Regular”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

note 2f. 

A2 Transfer From Department 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Department Transfer”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

A4 Basic Symbol Number 

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. 

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

A6 Sub-Account Symbol 

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. 

B2 Budget Sub-activity Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Sub-Allocation (formerly known as 

Limit/Subhead)”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 
ADC 1043 

Enclosure 3, page 3 

# Location 180M Material Returns Reporting Reason 

2/FA201/226 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. A local code ‘BE’ is established for use in the 

180M, version 4010. A data maintenance action 

has been submitted for establishment of ‘BEBusiness Event type Code’ in a future version. 

C3 Budget Restriction 

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. 

F1 Object Class 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Object Class”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

FT Funding Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Reimbursable Flag”. Refer to ADC 

1043. 

2. Qualifier FT is a migration code approved for use 

in X12 version 4030. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

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. A local code ‘IA’ is established for use in the 

Staffing Note: MILSTRIP 

procedures for the Materiel 

Returns Program (MRP) do 

not recognize applicability 

for FMS customers. 

Military Services may 

independently authorize 

extending MRP procedures/ 

transaction to their FMS 

customers. Military 

Services were requested to 

comment on whether 

inclusion of Security 

Cooperation related 

SLOA/Accounting 

Classification elements 

were needed for MRP. No 

comments were received. 

Resolution: Security 

Assistance related SLOA 

elements are provided to 

support Service/Agency 

processes as needed. 
ADC 1043 

Enclosure 3, page 4 

# Location 180M Material Returns Reporting Reason 

2/FA201/226 180M, version 4010. A data maintenance action 

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

future version. 

P1 Disbursing Station Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Agency Dispersing Identifier Code”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

P5 Foreign Military Sales (FMS) Line Item Number 

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

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. 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. 
ADC 1043 

Enclosure 3, page 5 

# Location 180M Material Returns Reporting Reason 

2/FA201/226 3. 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. 

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. A local code ‘YB’ is established for use in the 

180M, version 4010. A data maintenance action 

has been submitted for establishment of ‘YBBeginning 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. A local code ‘YE’ is established for use in the 

180M, version 4010. A data maintenance action 

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

in a future version. 

5. 2/FA201/226 Modify existing code L1 to remove the Federal note 

and insert a new DLMS note, and remove code I1: 

L1 Accounting Installation Number 

Federal Note: 

Use to indicate the Accountable Station Number. The 

Accountable Station Code is the Fiscal Station Number 

(FSN) of both the Army and the Office of the Secretary 

of Defense (OSD), the Authorization Accounting Activity 

(AAA) of the Navy, or the Accounting and Disbursing 

Station Number (ADSN) used by the Air Force. The 

Accountable Station Codes (TAC3) are published in the 

DoD 7000.14-R (Financial Management Regulation). 

Civilian Agencies will cite their equivalent organization 

code. 

Identifies the qualifier as 

having been mapped to a 

specific SFIS data element 

for SLOA. 
ADC 1043 

Enclosure 3, page 6 

# Location 180M Material Returns Reporting Reason 

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. 

I1 Abbreviated Department of Defense (DoD) 

Budget and Accounting Classification Code (BACC) 

Obsolete code removed to 

avoid confusion with 

SLOA requirements 

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

90 Project/Task 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Project Identifier”. This is the Project 

Identifier applicable to the original requirement 

for the materiel being returned. Refer to ADC 

1043. 

2. Qualifier 90 is a migration code approved for use 

in X12 version 4020. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

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. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

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. A local code ‘FA’ is established for use in the 

180M, version 4010. A data maintenance action 

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

These qualifiers have been 

mapped to specific SFIS 

data elements for SLOA 

cost objects. 
ADC 1043 

Enclosure 3, page 7 

# Location 180M Material Returns Reporting Reason 

2/FA201/226 H1 Cost Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Element Code”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

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

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

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

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

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

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

Enclosure 3, page 8 

# Location 511M Requisition Modifier Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043 

- ADC 1043, DLMS Revisions for Department of 

Defense (DoD) Standard Line of Accounting 

(SLOA)/Accounting Classification

Identifies DLMS 

Changes included in the 

DLMS Supplement 

2. 2/N901/020 Revise to insert a new DLMS note for existing 

qualifier 9R and WO: 

9R Job Order Number 

DLMS Note: 

1. Use to identify the associated Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA 

industrial activity support agreement. Refer to ADC 

381. 

3. For DoD SLOA/Accounting Classification 

compliance the JO Number may be repeated as a 

Work Order Number (FA201 Qualifier WO). Refer 

to ADC 1043. 

WO Work Order Number 

DLMS Note: 

1. Use to identify a maintenance work order number. 

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

3. For DoD SLOA/Accounting Classification 

compliance the Work Order Number may be 

repeated at FA201 Qualifier WO. Refer to ADC 

1043. 

SLOA compliance 

requires identification of 

the Work Order Number 

for which the Job Order 

Number is an authorized 

legacy equivalent. Job 

Order and Work Order 

Number are retained as a 

separate data element for 

logistics business 

processes requiring 

specific identification of 

this information. 

3. 2/LQ01/140 Add a second DLMS note to existing qualifier 78 and 

remove qualifiers 71, 85 and A4: 

78 Project Code 

DLMS Note: 

1. Use to identify special programs, exercises, projects, 

operations, and other purposes. 

2. For DoD SLOA/Accounting Classification 

compliance the Project Code may be repeated as a 

Project Identifier (FA201 Qualifier 90). Refer to 

ADC 1043. 

71 Service and Agency Code 

DLMS Note: 

1. For all SA transactions, use to identify the Service 

ILCO managing the case or program line when the

ILCO is not identified in the coded address in the 

transaction number. 

SLOA compliance 

requires identification of 

the Project Identifier for 

which the Project Code is 

an authorized legacy 

equivalent. Project Code 

is retained as a separate 

data element for logistics 

business processes 

requiring specific 

identification of this 

information. 

Removing qualifier 71 as 

this current DLMS 

enhancement for the 

Service and Agency is 

duplicative of required 
ADC 1043 

Enclosure 3, page 9 

# Location 511M Requisition Modifier Reason 

2. 2. DLMS enhancement; see introductory DLMS 

note 3a. 

85 Country and Activity Code 

DLMS Note: 

1. Use to identify Security Cooperation Customer Code. 

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

A4 Case Designator Number 

DLMS Note: 

Must use in FMS transactions to identify the FMS case 

number. For Cooperative Logistics Supply Support 

Arrangements (CLSSAs), repeat up to two times to 

identify the FMS Foreign Military Services Order 

(FMSO) I and FMSO II case numbers. In this instance, 

the first occurrence will cite the FMSO I case number, 

and a second occurrence, if applicable, will reflect the 

FMSO II case number. 

Security Cooperation 

Implementing Agency 

mapping to the FA2 

Removing qualifier 85 as 

this current DLMS 

enhancement for the 

Country and Activity 

Code is duplicative of 

required Security 

Cooperation Customer 

Code mapping to the FA2 

Planned DLMS 

enhancement for two 

repetitions is obsolete. 

There is no requirement 

to include both the FMSO 

I case identifier and the 

FMSO II case identifier 

in a single requisition. 

Linking the FMSO I case 

identifier to the FMSO II 

case identifier is 

accomplished via the 

Defense Security 

Assistance Management 

System (DSAMS). The 

FMS case number is 

removed from the LQ 

Segment because the 

value is not associated 

with a code list. Moved 

to FA2 Segment. 

4. 2/FA2/286 Insert a new segment level DLMS note: 

DLMS Note: Use this segment to comply with the DoD 

SLOA/Accounting Classification. Cost object elements 

Project Identifier, Funding Center Identifier, Functional 

Area, Cost Element Code, Cost Center Identifier, Activity 

Identifier, and Work Order Number are used as 

appropriate for the system.

Clarifies the location of 

SLOA/Accounting 

Classification data. 
ADC 1043 

Enclosure 3, page 10 

# Location 511M Requisition Modifier Reason 

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

89 Budget Line Item Identification 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Budget Line Item”. 

2. Qualifier 89 is a migration code approved for use in 

X12 version 4020. Refer to ADC 1043. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

A1 Department Indicator 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Regular”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 3g. 

A2 Transfer From Department 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Transfer”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 3g. 

A4 Basic Symbol Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Main Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

A5 Sub-class 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify, or to modify, “Sub Class”. Refer to 

ADC 1043. 

2. Sub Class is a potential future DLMS 

enhancement; see introductory DLMS note 3a. 

A6 Sub-Account Symbol 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub Account”. Refer to 

ADC 1043. 

These qualifiers have 

been mapped to specific 

SFIS data elements for 

SLOA. 
ADC 1043 

Enclosure 3, page 11 

# Location 511M Requisition Modifier Reason 

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

DLMS note 3g. 

B2 Budget Sub-activity Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub-Allocation (formerly 

known as Limit/Subhead)”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

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. A local code ‘BE’ is established for use in the 

511M, version 4010. A data maintenance action 

has been submitted for establishment of ‘BEBusiness Event Type Code’ in a future version. 

C3 Budget Restriction 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Availability Type”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

F1 Object Class 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Object Class”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

FT Funding Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Reimbursable Flag”. Refer 

to ADC 1043. 

2. Qualifier FT is an X12 Version Release 004030 

Migration Code. 
ADC 1043 

Enclosure 3, page 12 

# Location 511M Requisition Modifier Reason 

2/FA201/286 3. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

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

P1 Disbursing Station Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Agency Dispersing 

Identifier Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

P5 Foreign Military Sales (FMS) Line Item Number 

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

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. 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. 
ADC 1043 

Enclosure 3, page 13 

# Location 511M Requisition Modifier Reason 

2/FA201/286 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. 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. 

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. A local code ‘YB’ is established for use in the 

511M, version 4010. A data maintenance action 

has been submitted for establishment of ‘YBBeginning 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. A local code ‘YE’ is established for use in the 

511M, version 4010. A data maintenance action 

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

a future version. 

6. 2/FA201/286 Modify existing code L1 to remove the Federal note 

and insert a new DLMS note, and remove code I1: 

L1 Accounting Installation Number 

Federal Note: 

Use to indicate the Authorization Accounting Authority 

Identifies the qualifier as 

having been mapped to a 

specific SFIS data 

element for SLOA. 
ADC 1043 

Enclosure 3, page 14 

# Location 511M Requisition Modifier Reason 

(AAA)/Accounting and Disbursing Station 

Number (ADSN)/Fiscal Station Number (FSN). 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Agency Accounting 

Identifier”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3 ag.

I1 Abbreviated Department of Defense (DoD) Budget 

and Accounting Classification Code (BACC) 

Obsolete code removed to 

avoid confusion with 

SLOA requirements 

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

90 Project/Task 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

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

to ADC 1043. 

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

X12 version 4020. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

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

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

These qualifiers have 

been mapped to specific 

SFIS data elements for 

SLOA cost objects. 
ADC 1043 

Enclosure 3, page 15 

# Location 511M Requisition Modifier Reason 

2/FA201/286 H1 Cost Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Cost Element Code”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3g. 

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

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. 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 ‘AIActivity Identifier’ 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. 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.
ADC 1043 

Enclosure 3, page 16 

# Location 511R Requisition Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043 

- ADC 1043, DLMS Revisions for Department of 

Defense (DoD) Standard Line of Accounting 

(SLOA)/Accounting Classification

Identifies DLMS 

Changes included in 

the DLMS Supplement 

2. 2/N901/020 Revise to insert a new DLMS note for existing 

qualifier 9R: 

9R Job Order Number 

DLMS Note: 

1. Use to identify the associated Job Order (JO) 

Number. 

2. Authorized DLMS enhancement under DLA 

industrial activity support agreement. Refer to ADC 

381. 

3. For DoD SLOA/Accounting Classification 

compliance the Job Order Number may be 

repeated as a Work Order Number (FA201 

Qualifier WO). Refer to ADC 1043.

WO Work Order Number 

DLMS Note: 

1. Use to identify a maintenance work order number. 

2. DLMS enhancement; see introductory DLMS note 

3a. 

3. For DoD SLOA/Accounting Classification 

compliance the Work Order Number may be 

repeated at FA201 Qualifier ‘WO’. Refer to ADC 

1043.

SLOA compliance 

requires identification 

of the Work Order 

Number for which the 

Job Order Number is 

an authorized legacy 

equivalent. Job Order 

and Work Order 

Number are retained as 

a separate data element 

for logistics business 

processes requiring 

specific identification 

of this information. 

3. 2/LQ01/140 Add a second DLMS note to existing qualifier 78 and 

remove qualifiers 71, 85 and A4: 

78 Project Code 

DLMS Note: 

1. Use to identify special programs, exercises, 

projects, operations, and other purposes. 

2. For DoD SLOA/Accounting Classification 

compliance the Project Code may be repeated as a 

Project Identifier (N901 Qualifier ‘90’). Refer to 

ADC 1043. 

71 Service and Agency Code 

DLMS Note: 

1. For all SA transactions, use to identify the Service 

ILCO managing the case or program line when the

ILCO is not identified in the coded address in the 

transaction number. 

SLOA compliance 

requires identification 

of the Project 

Identifier for which the 

Project Code is an 

authorized legacy 

equivalent. Project 

Code is retained as a 

separate data element 

for logistics business 

processes requiring 

specific identification 

of this information. 

Removing qualifier 71 

as this current DLMS 

enhancement for the 
ADC 1043 

Enclosure 3, page 17 

# Location 511R Requisition Reason 

2. 2. DLMS enhancement; see introductory DLMS 

note 3a. 

85 Country and Activity Code 

DLMS Note: 

1. Use to identify Security Cooperation Customer Code. 

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

A4 Case Designator Number 

DLMS Note: 

Must use in FMS transactions to identify the FMS case 

number. For Cooperative Logistics Supply Support 

Arrangements (CLSSAs), repeat up to two times to 

identify the FMS Foreign Military Services Order 

(FMSO) I and FMSO II case numbers. In this instance, 

the first occurrence will cite the FMSO I case number, 

and a second occurrence, if applicable, will reflect the 

FMSO II case number. 

Service and Agency is 

duplicative of required 

Security Cooperation 

Implementing Agency 

mapping to the FA2 

Removing qualifier 85 

as this current DLMS 

enhancement for the 

Country and Activity 

Code is duplicative of 

required Security 

Cooperation Customer 

Code mapping to the 

FA2 

Planned DLMS 

enhancement for two 

repetitions is obsolete. 

There is no 

requirement to include 

both the FMSO I case 

identifier and the 

FMSO II case 

identifier in a single 

requisition. Linking 

the FMSO I case 

identifier to the FMSO 

II case identifier is 

accomplished via the 

Defense Security 

Assistance 

Management System 

(DSAMS). The FMS 

case number is 

removed from the LQ 

Segment because the 

value is not associated 

with a code list. 

Moved to FA2 

Segment. 
ADC 1043 

Enclosure 3, page 18 

# Location 511R Requisition Reason 

4. 2/FA2/286 Modify existing segment level DLMS note: 

DLMS Note: Use this segment to comply with the DoD 

SLOA/Accounting Classification. Cost object elements 

Project Identifier, Funding Center Identifier, 

Functional Area, Cost Element Code, Cost Center 

Identifier, Activity Identifier, and Work Order Number 

are used as appropriate for the system. Use this 

2/FA2/286 segment to identify the various components 

of the line of accounting.

Clarifies the location 

of SLOA data. 

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

89 Budget Line Item Identification 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Budget Line Item”. 

2. Qualifier 89 is a migration code approved for use 

in X12 version 4020. Refer to ADC 1043. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

A1 Department Indicator 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Regular”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 3f. 

A2 Transfer From Department 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Transfer”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 3f. 

A4 Basic Symbol Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Main Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA. 
ADC 1043 

Enclosure 3, page 19 

# Location 511R Requisition Reason 

2/FA201/286 A5 Sub-class 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting 

Classification use to identify, or to modify, “Sub 

Class”. Refer to ADC 1043. 

2. Sub Class is a potential future DLMS 

enhancement; see introductory DLMS note 3a. 

A6 Sub-Account Symbol 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

B2 Budget Sub-activity Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub-Allocation (formerly 

known as Limit/Subhead)”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

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. A local code ‘BE’ is established for use in the 

511R, version 4010. A data maintenance action 

has been submitted for establishment of ‘BEBusiness Event Type Code’ in a future version. 

C3 Budget Restriction 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Availability Type”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 
ADC 1043 

Enclosure 3, page 20 

# Location 511R Requisition Reason 

2/FA201/286 F1 Object Class 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Object Class”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

FT Funding Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Reimbursable Flag”. 

Refer to ADC 1043. 

2. Qualifier FT is an X12 Version Release 004030 

Migration Code. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

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. A local code ‘IA’ is established for use in the 

511R, version 4010. A data maintenance action 

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

future version. 

P1 Disbursing Station Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Agency Dispersing 

Identifier Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

P5 Foreign Military Sales (FMS) Line Item Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Security Cooperation Case Line Item 

Identifier”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 
ADC 1043 

Enclosure 3, page 21 

# Location 511R Requisition Reason 

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

511R, 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 

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 

511R, version 4010. A data maintenance action 

has been submitted for establishment of ‘S2- 

Security Cooperation Case Designator’ 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. A local code ‘YB’ is established for use in the 

511R, version 4010. A data maintenance action 

has been submitted for establishment of ‘YBBeginning Period of Availability Fiscal Year Date’ 

in a future version. 
ADC 1043 

Enclosure 3, page 22 

# Location 511R Requisition Reason 

2/FA201/286 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. A local code ‘YE’ is established for use in the 

511R, version 4010. A data maintenance action 

has been submitted for establishment of ‘YrEnding Period of Availability Fiscal Year Date’ in 

a future version. 

6. 2/FA201/286 Modify existing code L1 to remove the Federal note 

and insert a new DLMS note, and remove code I1: 

L1 Accounting Installation Number 

Federal Note: 

Use to indicate the Authorization Accounting Authority 

(AAA)/Accounting and Disbursing Station 

Number (ADSN)/Fiscal Station Number (FSN). 

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

I1 Abbreviated Department of Defense (DoD) 

Budget and Accounting Classification Code (BACC) 

Identifies the qualifier 

as having been 

mapped to a specific 

SFIS data element for 

SLOA. 

Obsolete code 

removed to avoid 

confusion with SLOA 

requirements 

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

90 Project/Task 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Project Identifier”. Refer to ADC 1043. 

2. Qualifier 90 is a migration code approved for use 

in X12 version 4020. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

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. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA 

cost objects. 
ADC 1043 

Enclosure 3, page 23 

# Location 511R Requisition Reason 

2/FA201/286 3. 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. 

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

in the 511R, version 4010. A data maintenance 

action has been submitted for establishment of 

‘FA-Functional Area’ in a future version. 

H1 Cost Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Element Code”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

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

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. 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. 
ADC 1043 

Enclosure 3, page 24 

# Location 511R Requisition Reason 

2/FA201/286 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. 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.

# Location 517M Material Obligation Validation Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043 

- ADC 1043, DLMS Revisions for Department of 

Defense (DoD) Standard Line of Accounting 

(SLOA)/Accounting Classification

Identifies DLMS 

Changes included in 

the DLMS Supplement 

2. 2/LQ01/080 Revise to insert a new DLMS note for existing 

qualifier 78 

78 Project Code 

DLMS Note: 

1. Use to identify special programs, exercises, 

projects, operations, and other purposes. 

2. For DoD SLOA/Accounting Classification 

compliance the Project Code may be repeated as a 

Project Identifier (FA201 Qualifier 90). Refer to 

ADC 1043. 

SLOA compliance 

requires identification 

of the Project 

Identifier for which the 

Project Code is an 

authorized legacy 

equivalent. Project 

Code is retained as a 

separate data element 

for logistics business 

processes requiring 

specific identification 

of this information. 

3. 2/FA2/136 Insert a new segment level DLMS note: 

DLMS Note: Use this segment to comply with the DoD 

SLOA/Accounting Classification. Cost object elements 

Project Identifier, Funding Center Identifier, 

Functional Area, Cost Element Code, Cost Center 

Identifier, Activity Identifier, and Work Order Number 

are used as appropriate for the system. This information 

is applicable to requisition re-instatement only.

Clarifies the location 

of SLOA data. 

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

89 Budget Line Item Identification 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Budget Line Item”. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA. 
ADC 1043 

Enclosure 3, page 25 

# Location 517M Material Obligation Validation Reason 

2/FA201/136 2. Qualifier 89 is a migration code approved for use 

in X12 version 4020. Refer to ADC 1043. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

A1 Department Indicator 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Regular”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 3f. 

A2 Transfer From Department 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Transfer”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 3f. 

A4 Basic Symbol Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Main Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

A5 Sub-class 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting 

Classification use to identify, or to modify, “Sub 

Class”. Refer to ADC 1043. 

2. Sub Class is a potential future DLMS 

enhancement; see introductory DLMS note 3a. 

A6 Sub-Account Symbol 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 
ADC 1043 

Enclosure 3, page 26 

# Location 517M Material Obligation Validation Reason 

2/FA201/136 B2 Budget Sub-activity Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub-Allocation (formerly 

known as Limit/Subhead)”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

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

C3 Budget Restriction 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Availability Type”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

F1 Object Class 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Object Class”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

FT Funding Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Reimbursable Flag”. 

Refer to ADC 1043. 

2. Qualifier FT is an X12 Version Release 004030 

Migration Code. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 
ADC 1043 

Enclosure 3, page 27 

# Location 517M Material Obligation Validation Reason 

2/FA201/136 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. A local code ‘IA’ is established for use in the 

517M, version 4010. A data maintenance action 

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

future version. 

P1 Disbursing Station Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Agency Dispersing 

Identifier Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

P5 Foreign Military Sales (FMS) Line Item Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Security Cooperation Case Line Item 

Identifier”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

S1 Security Cooperation Customer Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Security Cooperation Customer Code”. 

Refer to ADC 1043. 

2. DLMS enhancement; see introductory DLMS note 

3d. A field size exceeding 2 positions is not 

supportable under current MILSTRIP and 

MAPAC processes. Three character codes are not 

authorized at this time. 

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

Enclosure 3, page 28 

# Location 517M Material Obligation Validation Reason 

2/FA201/136 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. 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. 

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. A local code ‘YB’ is established for use in the 

517M, version 4010. A data maintenance action 

has been submitted for establishment of ‘YBBeginning 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. A local code ‘YE’ is established for use in the 

517M, version 4010. A data maintenance action 

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

a future version. 

5. 2/FA201/136 Modify existing code L1 to remove the Federal note 

and insert a new DLMS note, and remove code I1: 

Identifies the qualifier 

as having been 

mapped to a specific 
ADC 1043 

Enclosure 3, page 29 

# Location 517M Material Obligation Validation Reason 

L1 Accounting Installation Number 

Federal Note: 

Use to indicate the Authorization Accounting Authority 

(AAA)/Accounting and Disbursing Station 

Number (ADSN)/Fiscal Station Number (FSN). 

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

I1 Abbreviated Department of Defense (DoD) 

Budget and Accounting Classification Code (BACC) 

SFIS data element for 

SLOA. 

Obsolete code 

removed to avoid 

confusion with SLOA 

requirements 

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

90 Project/Task 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Project Identifier”. Refer to ADC 1043. 

2. Qualifier 90 is a migration code approved for use 

in X12 version 4020. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

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

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

in the 517M, version 4010. A data maintenance 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA 

cost objects. 
ADC 1043 

Enclosure 3, page 30 

# Location 517M Material Obligation Validation Reason 

2/FA201/136 action has been submitted for establishment of 

‘FA-Functional Area’ in a future version. 

H1 Cost Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Element Code”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 3f. 

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

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

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. 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.
ADC 1043 

Enclosure 3, page 31 

# Location 810L Logistics Bill Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043 

- ADC 1043, DLMS Revisions for Department of 

Defense (DoD) Standard Line of Accounting 

(SLOA)/Accounting Classification

Identifies DLMS 

Changes included in 

the DLMS Supplement 

2. 1/FA201/300 Modify DLMS Note for existing qualifiers 18 and 58 

and add SLOA related qualifiers: 

18 Funds Appropriation 

DLMS Note: 

Use to indicate the basic appropriation of the billed 

office to be charged or disbursed. Only one use of 

qualifier is permitted per transaction.

(department code through appropriation limit). 

Example: 1717979818100400 

58 Credits 

DLMS Note: 

Use to indicate the basic appropriation of the billing 

office to be credited or reimbursed. Only one use of 

qualifier is permitted per transaction. 

89 Budget Line Item Identification 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Budget Line Item” 

2. Used in association with the billing office line of 

accounting (Qualifier 58). 

3. Qualifier 89 is a migration code approved for use 

in X12 version 4020. Refer to ADC 1043. 

4. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

A1 Department Indicator 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Regular”. 

Refer to ADC 1043. Used in association with the 

billing office line of accounting (Qualifier 58 

2. Used in association with the billing office line of 

accounting (Qualifier 58). 

3. Authorized DLMS enhancement; see introductory 

note 6e. 

Provides for discrete 

SLOA accounting data 

in the summary bill. 
ADC 1043 

Enclosure 3, page 32 

# Location 810L Logistics Bill Reason 

1/FA201/300 A2 Transfer From Department 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Transfer”. 

Refer to ADC 1043. 

2. Used in association with the billing office line of 

accounting (Qualifier 58). 

3. Authorized DLMS enhancement; see introductory 

note 6e. 

A4 Basic Symbol Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Main Account”. 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. 

A5 Sub-class 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting 

Classification use to identify, or to modify, “Sub 

Class”. Refer to ADC 1043. 

2. Used in association with the billing office line of 

accounting (Qualifier 58). 

3. Sub Class is a potential future DLMS 

enhancement; see introductory DLMS note 6a. 

A6 Sub-Account Symbol 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub Account”. 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. 

B2 Budget Sub-activity Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub-Allocation (formerly 

known as Limit/Subhead)”. Refer to ADC 1043. 

2. Used in association with the billing office line of 

accounting (Qualifier 58). 
ADC 1043 

Enclosure 3, page 33 

# Location 810L Logistics Bill Reason 

1/FA201/300 3. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

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. A local code ‘BE’ is established for use in the 

810L, version 4010. A data maintenance action 

has been submitted for establishment of ‘BEBusiness Event Type Code’ in a future version. 

C3 Budget Restriction 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Availability Type”. 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. 

FT Funding Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Reimbursable Flag”. 

Refer to ADC 1043. 

2. Used in association with the billing office line of 

accounting (Qualifier 58). 

3. Qualifier FT is an X12 Version Release 004030 

Migration Code. 

4. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

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. 
ADC 1043 

Enclosure 3, page 34 

# Location 810L Logistics Bill Reason 

1/FA201/300 2. Used in association with the billing office line of 

accounting (Qualifier 58). 

3. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

4. A local code ‘YB’ is established for use in the 

810L, version 4010. A data maintenance action 

has been submitted for establishment of ‘YBBeginning 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. A local code ‘YE’ is established for use in the 

810L, version 4010. A data maintenance action 

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

a future version.

3. 1/FA201/300 Modify the DLMS Note for existing code L1: 

L1 Accounting Installation Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Agency Accounting Identifier”. Refer to 

ADC 1043.Use to indicate the Accountable Station 

Number. The Accountable Station Code is the Fiscal 

Station Number (FSN) of both the Army and the 

Office of the Secretary of Defense (OSD), the 

Authorization Accounting Activity (AAA) of the 

Navy, or the Accounting and Disbursing Station 

Number (ADSN) used by the Air Force. The 

Accountable Station Codes are published in the DoD 

7000.14-R (Financial Management Regulation). 

Civilian Agencies will cite their equivalent 

organization code. 

2. Used in association with the billing office line of 

accounting (Qualifier 58).

Identifies the qualifier 

as having been 

mapped to a specific 

SFIS data element for 

SLOA. 
ADC 1043 

Enclosure 3, page 35 

# Location 810L Logistics Bill Reason 

4. 2/LQ01/310 Remove qualifiers 71, 85 and A4: 

71 Service and Agency Code 

DLMS Note: 

Must use in FMS transactions to identify the customer 

country's requisitioning Service Code: B, D, K, P or T. 

For all SA transactions , repeat a second time to 

identify the Service ILCO managing the case or 

program line when the ILCO is not identified in the 

coded address in the transaction number. 

85 Country and Activity Code 

DLMS Note: 

Use to identify Security Cooperation Customer Code. 

A4 Case Designator Number 

DLMS Note: 

1. Must use in FMS transactions to identify the FMS 

case number. For Cooperative Logistics Supply 

Support Arrangements (CLSSAs), repeat up to two 

times to identify the FMS Foreign Military Services 

Order (FMSO) I and FMSO II case numbers. In this 

instance, the first occurrence will cite the FMSO I 

case number, and a second occurrence, if 

applicable, will reflect the FMSO II case number.

Removing qualifier 71 

as this current DLMS 

enhancement for the 

Service and Agency is 

duplicative of required 

Security Cooperation 

Implementing Agency 

mapping to the FA2 

Removing qualifier 85 

as this current DLMS 

enhancement for the 

Country and Activity 

Code is duplicative of 

required Security 

Cooperation Customer 

Code mapping to the 

FA2 

Planned DLMS 

enhancement for two 

repetitions is obsolete. 

There is no 

requirement to include 

both the FMSO I case 

identifier and the 

FMSO II case 

identifier in a single 

requisition. Linking 

the FMSO I case 

identifier to the FMSO 

II case identifier is 

accomplished via the 

Defense Security 

Assistance 

Management System 

(DSAMS). The FMS 

case number is 

removed from the LQ 

Segment because the 

value is not associated 

with a code list. 

Moved to FA2 

Segment. 
ADC 1043 

Enclosure 3, page 36 

# Location 810L Logistics Bill Reason 

5. 2/LQ01/310 Add DLMS Note to existing qualifier DG: 

DG Fund Code 

DLMS Note: 

1. Fund Code is retained in 2/LQ01/310. Discrete 

DoD SLOA/Accounting Classification is provided 

in 2/FA2/360. Refer to ADC 1043. 

Clarifies use of the 

Fund Code. 

6. 2/FA1/350 Open FA1 loop, marking segment FA1 as must use: 

FA1 Type of Financial Accounting Data 

This FA1 segment is 

opened to SLOA 

required elements. 

7. 2/FA101/350 Mark as used and add the following qualifiers and 

DLMS Note: 

DF Department of Defense (DoD) 

DLMS Note: Use to indicate that the Component is a 

Department of Defense agency, including Defense 

Logistics Agency.

DN Department of the Navy 

DLMS Note: Includes the United States Marine 

Corps. 

DY Department of Air Force 

DZ Department of Army 

FG Federal Government

FA101 is opened to 

identify the agency 

related to the SLOA 

information to be 

provided 

8. 2/FA2/360 Open FA2 segment and include segment level DLMS 

note: 

DLMS Note: Use this segment to comply with the DoD 

SLOA/Accounting Classification. Cost object elements 

Project Identifier, Funding Center Identifier, 

Functional Area, Cost Element Code, Cost Center 

Identifier, Activity Identifier, and Work Order Number 

are used as appropriate for the system. Fund Code is 

included at 2/LQ01/310. Refer to ADC 1043.

Clarifies the location 

of SLOA data. 

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

89 Budget Line Item Identification 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Budget Line Item”. 

2. Qualifier 89 is a migration code approved for use 

in X12 version 4020. Refer to ADC 1043. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA. 
ADC 1043 

Enclosure 3, page 37 

# Location 810L Logistics Bill Reason 

2/FA201/360 A1 Department Indicator 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Regular”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 6e. 

A2 Transfer From Department 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Transfer”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 6e. 

A4 Basic Symbol Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Main Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

A5 Sub-class 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting 

Classification use to identify, or to modify, “Sub 

Class”. Refer to ADC 1043. 

2. Sub Class is a potential future DLMS 

enhancement; see introductory DLMS note 6a. 

A6 Sub-Account Symbol 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

B2 Budget Sub-activity Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub-Allocation (formerly 

known as Limit/Subhead)”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 
ADC 1043 

Enclosure 3, page 38 

# Location 810L Logistics Bill Reason 

2/FA201/360 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 

6a. 

C3 Budget Restriction 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Availability Type”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

F1 Object Class 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Object Class”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

FT Funding Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Reimbursable Flag”. 

Refer to ADC 1043. 

2. Qualifier FT is an X12 Version Release 004030 

Migration Code. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

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. A local code ‘IA’ is established for use in the 

810L, version 4010. A data maintenance action 

has been submitted for establishment of ‘IA- 
ADC 1043 

Enclosure 3, page 39 

# Location 810L Logistics Bill Reason 

2/FA201/360 Security Cooperation Implementing Agency’ in a 

future version. 

L1 Accounting Installation Number 

1. For DoD SLOA/Accounting Classification use to 

identify “Agency Accounting Identifier”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 6e.

P1 Disbursing Station Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Agency Dispersing 

Identifier Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

P5 Foreign Military Sales (FMS) Line Item Number 

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

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. 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. 
ADC 1043 

Enclosure 3, page 40 

# Location 810L Logistics Bill Reason 

2/FA201/360 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. 

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

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. A local code ‘YB’ is established for use in the 

810L, version 4010. A data maintenance action 

has been submitted for establishment of ‘YBBeginning 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. A local code ‘YE’ is established for use in the 

810L, version 4010. A data maintenance action 

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

a future version.

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

90 Project/Task 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Project Identifier”. Refer to ADC 1043. 

2. Qualifier 90 is a migration code approved for use 

in X12 version 4020. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA 

cost objects. 
ADC 1043 

Enclosure 3, page 41 

# Location 810L Logistics Bill Reason 

2/FA201/360 3. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

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

in the 810L, version 4010. A data maintenance 

action has been submitted for establishment of 

‘FC-Funding 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. 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. 

H1 Cost Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Element Code”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 6e. 

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. 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. 
ADC 1043 

Enclosure 3, page 42 

# Location 810L Logistics Bill Reason 

2/FA201/360 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. 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. 

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

# Location 842 A/W Supply Discrepancy Report Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043 

- ADC 1043, DLMS Revisions for Department of 

Defense (DoD) Standard Line of Accounting 

(SLOA)/Accounting Classification

Identifies DLMS 

Changes included in 

the DLMS Supplement 

2. 2/REF01/0700 Revise to insert a new DLMS note for existing 

qualifier 9R: 

9R Job Order Number 

DLMS Note: 

1. Use to identify the associated Job Order (JO) 

Number. 

2. Authorized DLMS enhancement under DLA 

industrial activity support agreement. Refer to 

ADC 381. 

3. For DoD SLOA/Accounting Classification 

compliance the Job Order Number may be 

repeated as a Work Order Number (FA201 

Qualifier WO). Refer to ADC 1043. 

SLOA compliance 

requires identification 

of the Work Order 

Number for which the 

Job Order Number is 

an authorized legacy 

equivalent. Job Order 

is retained as a 

separate data element 

for logistics business 

processes requiring 

specific identification 

of this information. 
ADC 1043 

Enclosure 3, page 43 

# Location 842 A/W Supply Discrepancy Report Reason 

3. 2/FA1/1350 Open loop, by marking segment FA1 as must use: 

FA1 Type of Financial Accounting Data 

This FA1 segment is 

opened to SLOA 

required elements. 

4. 2/FA101/1350 Mark as used and add the following qualifiers and 

DLMS Note: 

DF Department of Defense (DoD) 

DLMS Note: Use to indicate that the Component is a 

Department of Defense agency, including Defense 

Logistics Agency.

DN Department of the Navy 

DLMS Note: Includes the United States Marine 

Corps. 

DY Department of Air Force 

DZ Department of Army 

FG Federal Government

FA101 is opened to 

identify the agency 

related to the SLOA 

information to be 

provided 

5. 2/FA2/1360 Open FA2 segment and include new segment level 

DLMS note: 

DLMS Note: Use this segment to comply with the DoD 

SLOA/Accounting Classification only when submitting 

an SDR using a constructed document number (not 

applicable to Security Assistance). Cost object 

elements Project Identifier, Funding Center Identifier, 

Functional Area, Cost Element Code, Cost Center 

Identifier, Activity Identifier, and Work Order Number 

are used as appropriate for the system.

Clarifies the location 

of SLOA data. 

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

89 Budget Line Item Identification 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Budget Line Item”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

A1 Department Indicator 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Regular”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 5. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA. 
ADC 1043 

Enclosure 3, page 44 

# Location 842 A/W Supply Discrepancy Report Reason 

2/FA201/1360 A2 Transfer From Department 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Transfer”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 5. 

A4 Basic Symbol Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Main Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

A5 Sub-class 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting 

Classification use to identify, or to modify, “Sub 

Class”. Refer to ADC 1043. 

2. Sub Class is a potential future DLMS 

enhancement. Components must coordinate 

requirements and business rules with DLA 

Logistics Management Standards Office prior to 

use. 

A6 Sub-Account Symbol 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

B2 Budget Sub-activity Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub-Allocation (formerly 

known as Limit/Subhead)”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

BE Business Event Type Code 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting 

Classification use to identify, or to modify, 
ADC 1043 

Enclosure 3, page 45 

# Location 842 A/W Supply Discrepancy Report Reason 

2/FA201/1360 “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. 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. 

C3 Budget Restriction 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Availability Type”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

F1 Object Class 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Object Class”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

FT Funding Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Reimbursable Flag”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

L1 Accounting Installation Number 

Federal Note: 

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

Enclosure 3, page 46 

# Location 842 A/W Supply Discrepancy Report Reason 

2/FA201/1360 P1 Disbursing Station Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Agency Dispersing 

Identifier Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

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

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

90 Project/Task 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Project Identifier”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA 

cost objects. 
ADC 1043 

Enclosure 3, page 47 

# Location 842 A/W Supply Discrepancy Report Reason 

2/FA201/350 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. 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. 

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

H1 Cost Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Element Code”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5. 

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. 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. 
ADC 1043 

Enclosure 3, page 48 

# Location 842 A/W Supply Discrepancy Report Reason 

2/FA201/350 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. 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. 

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

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

# Location 856S Ship Notice/Manifest Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043 

- ADC 1043, DLMS Revisions for Department of 

Defense (DoD) Standard Line of Accounting 

(SLOA)/Accounting Classification

Identifies DLMS 

Changes included in the 

DLMS Supplement 

2. 1/BSN06/0200 Revise existing DLMS Note 1 for code AS: 

AS Shipment Advice 

DLMS Note: 

1. Use to indicate this transaction provides shipment 

status information related to requisitions . Also use 

with BSN07 to indicate shipment status to the 

ICP/IMM from the reporting activity for lateral 

redistribution of retail assets. 

2. Also applies to Army Total Package Fielding. 

3. Use with BSN07=WTP to identify CAV Shipment 

Status. 

4. Use with BSN07=014 for outbound non-MILS 

shipments (e.g., a DD1149). Refer to ADC 417

Admin fix for 

clarification. 
ADC 1043 

Enclosure 3, page 49 

# Location 856S Ship Notice/Manifest Reason 

2. 2/HL/0100 Revise existing segment level Federal Note 1 and add 

new Federal Note 6: 

Federal Note: 

1. The transaction set hierarchical data structure is 

address information, followed by transaction 

shipment status, followed interior/exterior packaging 

passive RFID and/or by UID and/or financial 

information as applicable. 

2. Use the first 2/HL/0100 loop iteration to provide 

transaction set originator address information. 

3. Use the second 2/HL/0100 loop iteration to identify 

shipment information. 

4. Use additional 2/HL/0100 loop iterations to identify 

RFID as applicable. 

5. Use additional 2/HL/0100 loop iterations to identify 

UID information as applicable. 

6. Use an additional 2/HL/0100 loop iteration to 

identify financial information in support of 

SLOA/Accounting Classification information 

requirements.

Establishes an HL loop 

specifically for SLOA 

information. 

3. 2/HL03/0100 Add new code and DLMS Note: 

FI Financial Information 

DLMS Note: 

Use to identify the Finance loop to provide DoD 

SLOA/Accounting Classification information. The 

Finance loop includes only the REF/1500 and 

DTM/2000 segments. This loop is applicable only for 

shipment status to the ICP from the reporting activity 

for ICP-directed lateral redistribution order shipments 

of retail assets (equivalent to MILSTRIP legacy DIC 

AS6). Refer to ADC 1043.

Identifies an HL loop 

within a transaction as 

the one providing the 

SLOA information. 

4. 2/REF/1500 Add new third DLMS note at the segment level: 

DLMS Note:

1. This transaction will support item identification 

based upon the UII or the serial number. Data 

elements associated with the UII may be identified 

separately. Use the appropriate data elements to 

satisfy the desired functionality. 

2. This transaction will support association of the IUID 

information with the RFID tag at the IUID 

packaging level and/or at each higher level of 

packing which has been tagged. 

Clarifies the location of 

SLOA data. 
ADC 1043 

Enclosure 3, page 50 

# Location 856S Ship Notice/Manifest Reason 

3. Use this segment to comply with the DoD 

SLOA/Accounting Classification. Cost object 

elements Project Identifier, Funding Center 

Identifier, Functional Area, Cost Element Code, 

Cost Center Identifier, Activity Identifier, and Work 

Order Number are used as appropriate for the 

system. Refer to ADC 1043. 

5. 2/REF01/1500 Add the following qualifiers and DLMS notes: 

2E Foreign Military Sales Case Number 

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. 

AGY Agency Dispersing Identifier Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Agency Dispersing Identifier Code”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. A local code ‘AGY’ is established for use in the 

856S, version 4030. A data maintenance action 

has been submitted for establishment of ‘AGYAgency 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. A local code ‘AGZ’ is established for use in the 

856S, version 4030. A data maintenance action 

has been submitted for establishment of ‘AGZAgency 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. 

These qualifiers have 

been mapped to specific 

SFIS data elements for 

SLOA. 
ADC 1043 

Enclosure 3, page 51 

# Location 856S Ship Notice/Manifest Reason 

2/REF01/1500 2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

3. A local code ‘AVT’ is established for use in the 

856S, version 4030. A data maintenance action 

has been submitted for establishment of ‘AVTAvailability 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. A local code ‘BET’ is established for use in the 

856S, version 4030. A data maintenance action 

has been submitted for establishment of ‘BETBusiness 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. A local code ‘BLI’ is established for use in the 

856S, version 4030. A data maintenance action 

has been submitted for establishment of ‘BLIBudget Line Item’ in a future version. 

DP Department Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Department Regular”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

note 2f. 

LI Line Item Identifier (Seller’s) 

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

Enclosure 3, page 52 

# Location 856S Ship Notice/Manifest Reason 

2/REF01/1500 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. A local code ‘MAT’ is established for use in the 

856S, version 4030. A data maintenance action 

has been submitted for establishment of ‘MATMain Account’ in a future version. 

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. A local code ‘REB’ is established for use in the 

856S, version 4030. A data maintenance action 

has been submitted for establishment of ‘REBReimbursable 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. 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. A local code ‘SBA’ is established for use in the 

856S, version 4030. A data maintenance action 

has been submitted for establishment of ‘SBASub-Allocation’ in a future version. 
ADC 1043 

Enclosure 3, page 53 

# Location 856S Ship Notice/Manifest Reason 

2/REF01/1500 SCC 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. A local code ‘SCC’ is established for use in the 

856S, version 4030. A data maintenance action 

has been submitted for establishment of ‘SCCSecurity 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. A local code ‘IA’ is established for use in the 

856S, version 4030. A data maintenance action 

has been submitted for establishment of ‘SCISecurity 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. 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. 

TF Transfer Number 

DLMS Note: 
ADC 1043 

Enclosure 3, page 54 

# Location 856S Ship Notice/Manifest Reason 

2/REF01/1500 1. For DoD SLOA/Accounting Classification use to 

identify “Department Transfer”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

note 2f. 

XX4 Object Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Object Class”. Refer to ADC 1043. 

2. Qualifier XX4 is a migration code approved for 

use in X12 version 4040. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

6. 2/REF01/1500 JB Job (Project) Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Project Identifier”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

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

9X Account Category 

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. 

91 Cost Element 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Element Code”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

79 Cost Account 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

These qualifiers have 

been mapped to specific 

SFIS data elements for 

SLOA cost objects. 
ADC 1043 

Enclosure 3, page 55 

# Location 856S Ship Notice/Manifest Reason 

2/REF01/1500 identify “Cost Center Identifier”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f. 

BE Business Activity 

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. 

WO Work Order Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Work Order Number”. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

7. 2/DTM/2000 Remove the segment level Federal Note and replace 

with two segment level DLMS Notes: 

Federal Note: 

1. Use only in the 2/HL/0100 shipment status loops to 

identify dates associated with the shipment status 

DLMS Note: 

1. Use in the 2/HL/0100 shipment status loop to 

identify dates associated with the shipment status 

2. Use in the 2/HL/0100 Finance loop to comply with 

DoD SLOA/Accounting Classification information 

requirements.

8. 2/DTM01/2000 Add the following qualifiers and DLMS notes: 

283 Funds Appropriation – Start 

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. 

284 Funds Appropriation – End 

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.

These qualifiers have 

been mapped to specific 

SFIS data elements for 

SLOA. 
ADC 1043 

Enclosure 3, page 56 

# Location 856S Ship Notice/Manifest Reason 

9. 2/LQ01/3500 Revise the DLMS note for existing qualifier 78 and 

remove qualifiers 85 and A4: 

78 Project Code 

DLMS Note: 

1. Must use to provide the project code when 

applicable. 

2. Required when applicable to communicate the 

project code associated with the Army Total 

Package Fielding Unit Materiel Fielding Point or 

staging site shipment document. 

3. For DoD SLOA/Accounting Classification 

compliance (2/HL/0100 Finance loop) the Project 

Code may be repeated as a Project Identifier 

(REF01 Qualifier JB). Refer to ADC 1043. 

4. Authorized DLMS migration enhancement; see 

introductory DLMS 2f. 

85 Country and Activity Code 

DLMS Note: 

1. Use to identify Security Cooperation Customer Code. 

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

A4 Case Designator Number 

DLMS Note: 

1. Must use in FMS transactions to identify the FMS 

case number. For Cooperative Logistics Supply 

Support Arrangements (CLSSAs), repeat up to two 

times to identify the FMS Foreign Military Services 

Order (FMSO) I and FMSO II case numbers. In this 

instance, the first occurrence will cite the FMSO I 

case number, and a second occurrence, if 

applicable, will reflect the FMSO II case number. 

2. DLMS enhancement; see introductory DLMS note 

2a. 

SLOA compliance 

requires identification of 

the Project Identifier for 

which the Project Code 

is an authorized legacy 

equivalent. Project Code 

is retained as a separate 

data element for logistics 

business processes 

requiring specific 

identification of this 

information. 

Removing qualifier 85 

as this current DLMS 

enhancement for the 

Country and Activity 

Code is duplicative of 

required Security 

Cooperation Customer 

Code mapping to the 

Finance Loop 

(HL03=FI) 

Planned DLMS 

enhancement for two 

repetitions is obsolete. 

There is no requirement 

to include both the 

FMSO I case identifier 

and the FMSO II case 

identifier in a single 

requisition. Linking the 

FMSO I case identifier 

to the FMSO II case 

identifier is 

accomplished via the 

Defense Security 

Assistance Management 

System (DSAMS). The 

FMS case number is 

removed from the LQ 

Segment because the 

value is not associated 

with a code list. Moved 

to HL03=FI loop. 
ADC 1043 

Enclosure 3, page 57 

# Location 867I Issue Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043 

- ADC 1043, DLMS Revisions for Department of 

Defense (DoD) Standard Line of Accounting 

(SLOA)/Accounting Classification

Identifies DLMS 

Changes included in 

the DLMS Supplement 

2. 2/REF01/030 Revise to insert a new DLMS note for existing 

qualifier 9R: 

9R Job Order Number 

DLMS Note: 

1. Use to identify the associated Job Order (JO) 

Number. 

2. Authorized DLMS enhancement under DLA 

industrial activity support agreement. Refer to ADC 

381. 

3. For DoD SLOA/Accounting Classification 

compliance the Job Order Number may be 

repeated as a Work Order Number (FA201 

Qualifier WO). Refer to ADC 1043.

SLOA compliance 

requires identification 

of the Work Order 

Number for which the 

Job Order Number is 

an authorized legacy 

equivalent. Job Order 

is retained as a 

separate data element 

for logistics business 

processes requiring 

specific identification 

of this information. 

3. 2/LQ01/270 Revise current note and insert a new DLMS note for 

existing qualifier 78: 

78 Project Code 

DLMS Note: 

1. Use for all issue transactions except issues to 

DRMO to identify special programs, exercises, 

projects, operations, and other purposes; except 

issues to DLA Disposition Services. 

2. For DoD SLOA/Accounting Classification 

compliance the Project Code may be repeated as a 

Project Identifier (FA201 Qualifier 90). Refer to 

ADC 1043.

SLOA compliance 

requires identification 

of the Project 

Identifier for which the 

Project Code is an 

authorized legacy 

equivalent. Project 

Code is retained as a 

separate data element 

for logistics business 

processes requiring 

specific identification 

of this information. 

4. 2/FA2/350 Insert a new segment level DLMS note: 

DLMS Note: Use this segment to comply with the DoD 

SLOA/Accounting Classification. Cost object elements 

Project Identifier, Funding Center Identifier, 

Functional Area, Cost Element Code, Cost Center 

Identifier, Activity Identifier, and Work Order Number 

are used as appropriate for the system. Refer to ADC 

1043. 

Clarifies the location 

of SLOA/Accounting 

Classification data. 
ADC 1043 

Enclosure 3, page 58 

# Location 867I Issue Reason 

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

89 Budget Line Item Identification 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Budget Line Item”. 

2. Qualifier 89 is a migration code approved for use 

in X12 version 4020. Refer to ADC 1043. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

A1 Department Indicator 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Regular”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 5e. 

A2 Transfer From Department 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Transfer”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 5e. 

A4 Basic Symbol Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Main Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

A5 Sub-class 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting 

Classification use to identify, or to modify, “Sub 

Class”. Refer to ADC 1043. 

2. Sub Class is a potential future DLMS 

enhancement; see introductory DLMS note 5a. 

A6 Sub-Account Symbol 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub Account”. Refer to 

ADC 1043. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA. 
ADC 1043 

Enclosure 3, page 59 

# Location 867I Issue Reason 

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

DLMS note 5e. 

B2 Budget Sub-activity Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub-Allocation (formerly 

known as Limit/Subhead)”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

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. 

C3 Budget Restriction 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Availability Type”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

F1 Object Class 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Object Class”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

FT Funding Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Reimbursable Flag”. 

Refer to ADC 1043. 
ADC 1043 

Enclosure 3, page 60 

# Location 867I Issue Reason 

2/FA201/350 2. Qualifier FT is an X12 Version Release 004030 

Migration Code. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

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. 

P1 Disbursing Station Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Agency Dispersing 

Identifier Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

P5 Foreign Military Sales (FMS) Line Item Number 

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

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 at this time. 

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

version 4010. A data maintenance action has been 
ADC 1043 

Enclosure 3, page 61 

# Location 867I Issue Reason 

2/FA201/350 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. 

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. A local code ‘YB’ is established for use in the 

867I, version 4010. A data maintenance action has 

been submitted for establishment of ‘YBBeginning 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. 
ADC 1043 

Enclosure 3, page 62 

# Location 867I Issue Reason 

6. 2/FA201/350 Modify existing code L1 to remove the Federal note 

and insert a new DLMS note, and remove code I1: 

L1 Accounting Installation Number 

Federal Note: 

Use to indicate the Authorization Accounting Authority 

(AAA)/Accounting and Disbursing Station 

Number (ADSN)/Fiscal Station Number (FSN). 

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

I1 Abbreviated Department of Defense (DoD) 

Budget and Accounting Classification Code (BACC) 

Identifies the qualifier 

as having been 

mapped to a specific 

SFIS data element for 

SLOA. 

Obsolete code 

removed to avoid 

confusion with SLOA 

requirements 

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

90 Project/Task 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Project Identifier”. Refer to ADC 1043. 

2. Qualifier 90 is a migration code approved for use 

in X12 version 4020. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

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 

‘FC-Funding 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 5e. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA 

cost objects. 
ADC 1043 

Enclosure 3, page 63 

# Location 867I Issue Reason 

2/FA201/350 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 

‘FA-Functional Area’ in a future version. 

H1 Cost Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Element Code”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 5e. 

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 

‘CC-Cost Center Identifier’ in a future version. 

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 

‘AI-Activity 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 

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.
ADC 1043 

Enclosure 3, page 64 

# Location 869F Requisition Follow-Up Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043 

- ADC 1043, DLMS Revisions for Department of 

Defense (DoD) Standard Line of Accounting 

(SLOA)/Accounting Classification

Identifies DLMS 

Changes included in 

the DLMS Supplement 

2. 2/REF01/105 Revise to insert a new DLMS note for existing 

qualifier 9R and WO: 

9R Job Order Number 

DLMS Note: 

1. Use to identify the associated Job Order (JO) 

Number. 

2. Authorized DLMS enhancement under DLA 

industrial activity support agreement. Refer to ADC 

381. 

3. For DoD SLOA/Accounting Classification 

compliance the Job Order Number may be 

repeated as a Work Order Number (FA201 

Qualifier WO). Refer to ADC 1043.

WO Work Order Number 

DLMS Note: 

1. Use to identify a maintenance work order number.

2. DLMS enhancement; see introductory DLMS note 

4g. 

3. For DoD SLOA/Accounting Classification 

compliance the Work Order Number may be 

repeated at FA201 Qualifier WO. Refer to ADC 

1043.

SLOA compliance 

requires identification 

of the Work Order 

Number for which the 

Job Order Number is 

an authorized legacy 

equivalent. Job Order 

and Work Order 

Number are retained as 

a separate data element 

for logistics business 

processes requiring 

specific identification 

of this information. 

3. 2/LQ01/180 Add a second DLMS note to existing qualifier 78 and 

remove qualifiers 85 and A4: 

78 Project Code 

DLMS Note: 

1. Use to identify special programs, exercises, 

projects, operations, and other purposes. 

2. For DoD SLOA/Accounting Classification 

compliance the Project Code may be repeated as a 

Project Identifier (FA201 Qualifier 90). Refer to 

ADC 1043. 

SLOA compliance 

requires identification 

of the Project 

Identifier for which the 

Project Code is an 

authorized legacy 

equivalent. Project 

Code is retained as a 

separate data element 

for logistics business 

processes requiring 

specific identification 

of this information. 
ADC 1043 

Enclosure 3, page 65 

# Location 869F Requisition Follow-Up Reason 

2/LQ01/180 71 Service and Agency Code 

DLMS Note: 

1. For all SA transactions, use to identify the Service 

ILCO managing the case or program line when the

ILCO is not identified in the coded address in the 

transaction number. 

2. 2. DLMS enhancement; see introductory DLMS 

note 4a. 

85 Country and Activity Code 

DLMS Note: 

1. Use to identify Security Cooperation Customer Code. 

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

A4 Case Designator Number 

DLMS Note: 

1. Must use in FMS transactions to identify the FMS 

case number. For Cooperative Logistics Supply 

Support Arrangements (CLSSAs), repeat up to two 

times to identify the FMS Foreign Military Services 

Order (FMSO) I and FMSO II case numbers. In this 

instance, the first occurrence will cite the FMSO I 

case number, and a second occurrence, if 

applicable, will reflect the FMSO II case number. 

Removing qualifier 71 

as this current DLMS 

enhancement for the 

Service and Agency is 

duplicative of required 

Security Cooperation 

Implementing Agency 

mapping to the FA2 

Removing qualifier 85 

as this current DLMS 

enhancement for the 

Country and Activity 

Code is duplicative of 

required Security 

Cooperation Customer 

Code mapping to the 

FA2 

Planned DLMS 

enhancement for two 

repetitions is obsolete. 

There is no 

requirement to include 

both the FMSO I case 

identifier and the 

FMSO II case 

identifier in a single 

requisition. Linking 

the FMSO I case 

identifier to the FMSO 

II case identifier is 

accomplished via the 

Defense Security 

Assistance 

Management System 

(DSAMS). The FMS 

case number is 

removed from the LQ 

Segment because the 

value is not associated 

with a code list. 

Moved to FA2 

Segment. 
ADC 1043 

Enclosure 3, page 66 

# Location 869F Requisition Follow-Up Reason 

4. 2/FA2/200 Insert a new segment level DLMS notes: 

DLMS Note: Use this segment to comply with the DoD 

SLOA/Accounting Classification. Cost object elements 

Project Identifier, Funding Center Identifier, 

Functional Area, Cost Element Code, Cost Center 

Identifier, Activity Identifier, and Work Order Number 

are used as appropriate for the system. Refer to ADC 

1043.

Clarifies the location 

of SLOA data. 

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

89 Budget Line Item Identification 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Budget Line Item”. 

2. Qualifier 89 is a migration code approved for use 

in X12 version 4020. Refer to ADC 1043. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

A1 Department Indicator 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Regular”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 4g. 

A2 Transfer From Department 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Transfer”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 4g. 

A4 Basic Symbol Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Main Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA. 
ADC 1043 

Enclosure 3, page 67 

# Location 869F Requisition Follow-Up Reason 

2/FA201/200 A5 Sub-class 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting 

Classification use to identify, or to modify, “Sub 

Class”. Refer to ADC 1043. 

2. Sub Class is a potential future DLMS 

enhancement; see introductory DLMS note 4a. 

A6 Sub-Account Symbol 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

B2 Budget Sub-activity Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub-Allocation (formerly 

known as Limit/Subhead)”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

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

C3 Budget Restriction 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Availability Type”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 
ADC 1043 

Enclosure 3, page 68 

# Location 869F Requisition Follow-Up Reason 

2/FA201/200 F1 Object Class 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Object Class”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

FT Funding Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Reimbursable Flag”. 

Refer to ADC 1043. 

2. Qualifier FT is an X12 Version Release 004030 

Migration Code. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

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. A local code ‘IA’ is established for use in the 

869F, version 4010. A data maintenance action 

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

future version. 

P1 Disbursing Station Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Agency Dispersing 

Identifier Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

P5 Foreign Military Sales (FMS) Line Item Number 

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

Enclosure 3, page 69 

# Location 869F Requisition Follow-Up Reason 

2/FA201/200 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. 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 at this time. 

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

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. A local code ‘YB’ is established for use in the 

869F, version 4010. A data maintenance action 

has been submitted for establishment of ‘YBBeginning Period of Availability Fiscal Year Date’ 

in a future version. 
ADC 1043 

Enclosure 3, page 70 

# Location 869F Requisition Follow-Up Reason 

2/FA201/200 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. A local code ‘YE’ is established for use in the 

869F, version 4010. A data maintenance action 

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

a future version.

6. 2/FA201/200 Modify existing code L1 to remove the Federal note 

and insert a new DLMS note, and remove code I1: 

L1 Accounting Installation Number 

Federal Note: 

Use to indicate the Authorization Accounting Authority 

(AAA)/Accounting and Disbursing Station 

Number (ADSN)/Fiscal Station Number (FSN). 

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

I1 Abbreviated Department of Defense (DoD) 

Budget and Accounting Classification Code (BACC)

Identifies the qualifier 

as having been 

mapped to a specific 

SFIS data element for 

SLOA. 

Obsolete code 

removed to avoid 

confusion with SLOA 

requirements 

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

90 Project/Task 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Project Identifier”. Refer to ADC 1043. 

2. Qualifier 90 is a migration code approved for use 

in X12 version 4020. 

3. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

FC Funding Center Identifier 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Funding Center Identifier”. Refer to 

ADC 1043. 

These qualifiers have 

been mapped to 

specific SFIS data 

elements for SLOA 

cost objects. 
ADC 1043 

Enclosure 3, page 71 

# Location 869F Requisition Follow-Up Reason 

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

DLMS note 4g. 

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

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

H1 Cost Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Element Code”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4g. 

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

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. 
ADC 1043 

Enclosure 3, page 72 

# Location 869F Requisition Follow-Up Reason 

2/FA201/200 3. 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. 

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

# Location 940R Material Release Reason 

1. DLMS 

Introductory 

Notes 

Add ADC 1043 

- ADC 1043, DLMS Revisions for Department of 

Defense (DoD) Standard Line of Accounting 

(SLOA)/Accounting Classification 

Identifies DLMS 

Changes included in the 

DLMS Supplement 

2. 2/N901/0400 Revise to insert a new DLMS note for existing 

qualifier 9R: 

9R Job Order Number 

DLMS Note: 

1. Use to identify the associated Job Order (JO) Number. 

2. Authorized DLMS enhancement under DLA industrial 

activity support agreement. Refer to ADC 381. 

3. For DoD SLOA/Accounting Classification 

compliance the Job Order Number may be repeated 

as a Work Order Number (FA201 Qualifier WO). 

Refer to ADC 1043.

WO Work Order Number 

DLMS Note: 

1. Use to identify a maintenance work order number. 

2. Authorized DLMS enhancement under DLA industrial 

activity support agreement. Refer to ADC 381. 

3. Also applicable to MRO Exception Data Transaction 

(ICP to DSS Storage Activity). Legacy mapping may 

populate with work order or job order number, 

pending full DLMS implementation Refer to ADC 

71A. 

SLOA compliance 

requires identification of 

the Work Order Number 

for which the Job Order 

Number is an authorized 

legacy equivalent. Job 

Order and Work Order 

Number are retained as a 

separate data element for 

logistics business 

processes requiring 

specific identification of 

this information. 
ADC 1043 

Enclosure 3, page 73 

# Location 940R Material Release Reason 

2/N901/0400 4. For DoD SLOA/Accounting Classification 

compliance the Work Order Number may be 

repeated at FA201 Qualifier WO. Refer to ADC 

1043.

3. 2/LQ01/1300 Add a third DLMS note to existing qualifier 78 and 

remove qualifiers 85 and A4: 

78 Project Code 

DLMS Note: 

1. Use in redistribution orders, material release orders, 

disposal release orders and historical material release 

orders, but only to identify special programs, 

exercises, projects, operations, and other purposes. 

Use in material release order modifications to identify 

the revised project code. 

2. Use of a project code in a disposal release order is an 

authorized DLMS enhancement; see introductory 

DLMS note 4b. 

3. For DoD SLOA/Accounting Classification 

compliance the Project Code may be repeated as a 

Project Identifier (FA201 Qualifier 90). Refer to 

ADC 1043. 

71 Service and Agency Code 

DLMS Note: 

1. For all SA transactions, use to identify the Service 

ILCO managing the case or program line when the

ILCO is not identified in the coded address in the 

transaction number. 

2. 2. DLMS enhancement; see introductory DLMS note 

4a. 

85 Country and Activity Code 

DLMS Note: 

1. Use to identify Security Cooperation Customer Code. 

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

A4 

DLMS Note: 

1. Must use in FMS transactions to identify the FMS 

case number. For Cooperative Logistics Supply 

Support Arrangements (CLSSAs), repeat up to two 

times to identify the FMS, FMSO I, and FMSO II case 

numbers. In this instance, the first occurrence will 

cite the FMSO O case number, and a second 

occurrence, if applicable, will reflect the FMSO II. 

SLOA compliance 

requires identification of 

the Project Identifier for 

which the Project Code 

is an authorized legacy 

equivalent. Project Code 

is retained as a separate 

data element for logistics 

business processes 

requiring specific 

identification of this 

information. 

Removing qualifier 71 

as this current DLMS 

enhancement for the 

Service and Agency is 

duplicative of required 

Security Cooperation 

Implementing Agency 

mapping to the FA2 

Removing qualifier 85 

as this current DLMS 

enhancement for the 

Country and Activity 

Code is duplicative of 

required Security 

Cooperation Customer 

Code mapping to the 

FA2 

Planned DLMS 

enhancement for two 

repetitions is obsolete. 

There is no requirement 

to include both the 

FMSO I case identifier 

and the FMSO II case 

identifier in a single 

requisition. Linking the 

FMSO I case identifier 
ADC 1043 

Enclosure 3, page 74 

# Location 940R Material Release Reason 

2/LQ01/1300 2. DLMS enhancement; see DLMS introductory note 4a. to the FMSO II case 

identifier is 

accomplished via the 

Defense Security 

Assistance Management 

System (DSAMS). The 

FMS case number is 

removed from the LQ 

Segment because the 

value is not associated 

with a code list. Moved 

to FA2 Segment. 

4. 2/FA2/3000 Insert a new segment level DLMS notes: 

DLMS Note: Use this segment to comply with the DoD 

SLOA/Accounting Classification. Cost object elements 

Project Identifier, Funding Center Identifier, Functional 

Area, Cost Element Code, Cost Center Identifier, Activity 

Identifier, and Work Order Number are used as 

appropriate for the system. This information is applicable 

to the disposal release order for hazardous materiel/waste 

and creditable turn-in only. Refer to ADC 1043.

Clarifies the location of 

SLOA data. 

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

89 Budget Line Item Identification 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Budget Line Item”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

A1 Department Indicator 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Regular”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 4f. 

A2 Transfer From Department 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Department Transfer”. 

Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

note 4f. 

These qualifiers have 

been mapped to specific 

SFIS data elements for 

SLOA. 
ADC 1043 

Enclosure 3, page 75 

# Location 940R Material Release Reason 

2/FA201/3000 A4 Basic Symbol Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Main Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

A5 Sub-class 

DLMS Note: 

1. Reserved for DoD SLOA/Accounting Classification 

use to identify, or to modify, “Sub Class”. Refer to 

ADC 1043. 

2. Sub Class is a potential future DLMS enhancement; 

see introductory DLMS note 4a. 

A6 Sub-Account Symbol 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub Account”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

B2 Budget Sub-activity Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Sub-Allocation (formerly 

known as Limit/Subhead)”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

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. 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. 
ADC 1043 

Enclosure 3, page 76 

# Location 940R Material Release Reason 

2/FA201/3000 C3 Budget Restriction 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Availability Type”. Refer to 

ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

F1 Object Class 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Object Class”. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

FT Funding Type 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Reimbursable Flag”. Refer 

to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

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. 

3. A local code ‘IA’ is established for use in the 940R, 

version 4030. A data maintenance action has been 

submitted for establishment of ‘IA- Security 

Cooperation Implementing Agency’ in a future 

version. 

P1 Disbursing Station Number 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify, or to modify, “Agency Dispersing Identifier 

Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 
ADC 1043 

Enclosure 3, page 77 

# Location 940R Material Release Reason 

2/FA201/3000 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. 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. 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 

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 940R, 

version 4030. A data maintenance action has been 

submitted for establishment of ‘S2- Security 

Cooperation Case Designator’ in a future version. 
ADC 1043 

Enclosure 3, page 78 

# Location 940R Material Release Reason 

2/FA201/3000 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. 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. A local code ‘YE’ is established for use in the 940R, 

version 4030. A data maintenance action has been 

submitted for establishment of ‘YE- Ending Period 

of Availability Fiscal Year Date’ in a future version.

6. 2/FA201/3000 Modify existing code L1 to remove the Federal note 

and insert a new DLMS note, and remove code I1: 

L1 Accounting Installation Number 

Federal Note: 

Use to indicate the Authorization Accounting Authority 

(AAA)/Accounting and Disbursing Station Number 

(ADSN)/Fiscal Station Number (FSN). 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Agency Accounting Identifier”. Applicable 

only to the Disposal Release Order for creditable or 

hazardous waste/materiel turn-in. Refer to ADC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4af.

I1 Abbreviated Department of Defense (DoD) Budget 

and Accounting Classification Code (BACC) 

Identifies the qualifier as 

having been mapped to a 

specific SFIS data 

element for SLOA. 

Obsolete code removed 

to avoid confusion with 

SLOA requirements 
ADC 1043 

Enclosure 3, page 79 

# Location 940R Material Release Reason 

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

90 Project/Task 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Project Identifier”. Refer to PDC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

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. 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 ‘FCFunding 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. 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 ‘FAFunctional Area’ in a future version. 

H1 Cost Code 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Element Code”. Refer to ADC 1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

CC Cost Center Identifier 

DLMS Note: 

1. For DoD SLOA/Accounting Classification use to 

identify “Cost Center Identifier”. Refer to ADC 

1043. 

These qualifiers have 

been mapped to specific 

SFIS data elements for 

SLOA cost objects. 

Staffing Note: Sought 

confirmation that Project 

Identifier (Qualifier 90) 

would be inappropriate 

for the Disposal Release 

Order, and thus not 

necessary to include in 

the 940R. No comments 

received. 

Resolution: Qualifier 90 

included to be available 

for SLOA if needed. 
ADC 1043 

Enclosure 3, page 80 

# Location 940R Material Release Reason 

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

DLMS note 4f. 

3. 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 ‘CCCost Center Identifier’ in a future version. 

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. 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 ‘AIActivity 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 PDC 

1043. 

2. Authorized DLMS enhancement; see introductory 

DLMS note 4f. 

3. 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 ‘WOWork Order Number’ in a future version.

Staffing Note: 

Sought confirmation that 

Work Order Number 

(Qualifier WO) would 

be inappropriate for this 

process, and thus not 

necessary to include in 

the 940R. No comments 

received. 

Resolution: Qualifier 

WO included to be 

available for SLOA if 

needed. 
Enclosure 4, Data Mapping Summary

This mapping is an assessment of the possible means for mapping the data elements listed as part the SLOA memo issued in September to the relevant DLMS supplements. Dependin

mapped to the best available structure of the X12 standard underlying the DLMS supplement. (* New code requests will be submitted to ASC X12 to add Sub Class, Availability Type, 

Code, Reimbursable Code, Budget Line Item, Security Cooperation Customer Code, Security Cooperation Implementing Agency, Sub‐Allocation, Agency Disbursing Identifier Code, and 

128, and Beginning Period of Availability Fiscal Year Date, Ending Period of Availability Fiscal Year Date, Activity Identifier, Cost Center Identifier, Functional Area, Funding Center Iden

Security Cooperation Implementing Agency, Security Cooperation Case Designator, Security Cooperation Case Line Item Identifier, and Work Order Number to date element 1196. Cod

final code values and names will be determined by ASC X12.)

NOTE: 842C/I Stock Screening Request. Discussion is ongoing to verify the SLOA requirement for this business process. In this process the owning Service requests a special inspectio

work is later associated with a funding MIPR provided by the materiel owner.

Mapping (Color) Key:I = These data elements were previously included in the supplement as a DLMS enhancement.A = The suggested mapping requires an existing X12 qualifier be added to the supplement.M = The suggested mapping requires the use of a code from a future version (referred to as a migration code) of the X12 standard or a local code to be added to X12 through 

Mapping Requisitioning MOV MRP Release Order Ship

( The mapping matrix codes: I = Implemented /

A = Available to be Added / M = Migration Code )

Rqn

Referral

Passing

Modification Follow‐up Rqn Reinstatement Offer HW Turn‐In AS6 ‐ 

ICP/I

of R

SLOA Element X12 Segment X12 Qualifier X12 Qualifier Value Source 529 Code? 511R (4010) 511M (4010) 869F (4010) 517M (4010) 180M (4010) 940R (4030) Sub Class (2): A7 in SFIS; Grouping

of a transaction type, e.g., 46

Payments from Current

Appropriations for Obligations of

Closed Accounts; a.k.a. Sub‐level

Prefix (SP)

FA2 DE 1196, A5 Sub‐class Y A A A A A A 

REF DE 128, SCL * Sub Class Y 

Department Transfer (3): A2 in

SFIS; A transfer of obligation

authority from DOE, e.g., 089;

a.k.a. Allocation Transfer Agency

Identifier (ATA)

FA2 DE 1196, A2 Transfer From Department Y A A A A A A 

REF DE 128, TF Transfer Number 

Department Regular (3): A1 in

SFIS; e.g., 021 Army, 017 Navy, 057

Air Force; 097 ODOs; a.k.a.

FA2 DE 1196, A1 Department Indicator Y A A A A A A 

REF DE 128, DP Department Number 

Beginning Period of Availability

Fiscal Year Date (4); A27 in SFIS,

e.g., 2012

FA2 DE 1196, YB*

BeginningPeriod ofAvailabilityFiscal Year Date

Y M M M M M M 

DTM DE 374, 283 Buy Period Date

‐ Start 

Ending Period of Availability Fiscal

Year Date (4); A28 in SFIS, e.g.,

2012

FA2 DE 1196, YE*

Ending Period ofAvailabilityFiscal Year Date

Y M M M M M M 

DTM DE 374, 284 Buy Period Date

‐ End 
Mapping Requisitioning MOV MRP Release Order Ship

( The mapping matrix codes: I = Implemented /

A = Available to be Added / M = Migration Code )

Rqn

Referral

Passing

Modification Follow‐up Rqn Reinstatement Offer HW Turn‐In AS6 ‐ 

ICP/I

of R

SLOA Element X12 Segment X12 Qualifier X12 Qualifier Value Source 529 Code? 511R (4010) 511M (4010) 869F (4010) 517M (4010) 180M (4010) 940R (4030) Availability Type (1): A24 in SFIS;

e.g., X = No‐year TAS

FA2 DE 1196, C3 Budget Restriction Y A A A A A A 

REF DE 128, AVT * Availability Type Y 

Main Account (4): A3 in SFIS;

Synonymous with Basic Symbol,

Appropriation Symbol, e.g., 4930

FA2 DE 1196, A4 Basic Symbol Number Y A A A A A A 

REF DE 128, MAT * Main Account Y 

Sub Account (3): A4 in SFIS;

Indicates the relationship to the

Main Account, e.g., 002

FA2 DE 1196, A6 Sub‐Account Symbol Y A A A A A A 

REF DE 128, SAT * Sub Account Y 

Business Event Type Code (8); T20

in SFIS; Replaces Transaction

Codes, e.g., DISB ‐ Disbursement

FA2 DE 1196, BE Business Event Type Code Y M M M M M M 

REF DE 128, BET * Business Event Type Code Y 

Object Class (6); B6 in SFIS; Will

initially be implemented at the

three‐digit level as in SFIS with

room to expand to six, e.g., 252

FA2 DE 1196, F1 Object Class Y A A A A A A 

REF DE 128, XX42 Object Code 

Reimbursable Flag (1); A9 in SFIS;

Examples: Direct, ReimbursableCode, e.g., D or R

FA2 DE 1196, FT3 Funding Type M M M M M A 

REF DE 128, REB * Reimbursable Code 

Budget Line Item (16); For MilPers,

value will be Budget Sub‐Activity

(BSA) plus Budget Line Item (BLI).

B4 in SFIS; Further sub‐divides the

Treasury Account Fund Symbol

below sub‐activity, e.g., 111

FA2 DE 1196, 894

Budget Line

ItemIdentification

M M M M M A 

REF DE 128, BLI * Budget Line Item 

Security Cooperation (formerly

Foreign Military Sales (FMS)

Customer Code) (3); T21 in SFIS;

Security Cooperation (SC)

Customer; The country, customer,

or U.S. program receiving the

product/service, e.g., EI IRELAND

or F1 F‐16 CO‐PRODUCTION, or B4

SECTION 1206

FA2 DE 1196, S1 *

SecurityCooperationCustomer Code

M M M M M M 

REF DE 128, SCC *

SecurityCooperationCustomer Code

2 DE 128, code XX4 is available as of X12 version/release 4040. Migration code for 4010 & 4030. 3 DE 1196, code FT is available in X12 version/release 4030. Migration code for 4010. 4 DE 1196, code 89 is available in X12 version/release 4030. Migration code for 4010.]
Mapping Requisitioning MOV MRP Release Order Ship

( The mapping matrix codes: I = Implemented /

A = Available to be Added / M = Migration Code )

Rqn

Referral

Passing

Modification Follow‐up Rqn Reinstatement Offer HW Turn‐In AS6 ‐ 

ICP/I

of R

SLOA Element X12 Segment X12 Qualifier X12 Qualifier Value Source 529 Code? 511R (4010) 511M (4010) 869F (4010) 517M (4010) 180M (4010) 940R (4030) Security CooperationImplementing Agency (IA) Code:

T27 in SFIS; Identifies the U.S.

MILDEP or agency which is

executing the FMS sale on behalf

of the U.S. Government; e.g., B‐

Army, D‐Air Force, P‐Navy

FA2 DE 1196, IA *

SecurityCooperationImplementingAgency Code

M

M

M

M

M

M

REF DE 128, SCI *

SecurityCooperationImplementingAgency Code

Security Cooperation Case

Designator (formerly known as“FMS Case Identifier”) (4); T22 in

SFIS; Identifies the FMS or Security

Cooperation contractual sales

agreement between countries,

e.g., UAK

FA2 DE 1196, S2 *

SecurityCooperationCase Designator

M

M

M

M

M

M

REF DE 128, 2E

Foreign Military

Sales Case

Number

Security Cooperation (formerly

FMS) Case Line Item Identifier (3);

T23 in SFIS; Security Cooperation

(SC) Customer; Identifies a detailed

line‐item requirement, e.g., 001

FA2 DE 1196, P5 *

SecurityCooperationCase Line ItemIdentifier

A A A A A M 

REF DE 128, LI

Line ItemIdentifier(Seller’s)

Sub‐Allocation (formerly known

as “Limit”) (4); Use of this data

element is exclusive to sub‐

allocation purposes, useful for

Financial Reporting; e.g., 2504

FA2 DE 1196, B2 Budget Sub‐ activity Number Y A A A A A A 

REF DE 128, SBA * Sub‐Allocation Y 

Agency Disbursing Identifier Code

(8); O2 in SFIS; Synonymous with

Treasury DSSN definitions for each

disbursing office, e.g., 1700

FA2 DE 1196, P1 Disbursing Station Number Y A A A A A A 

REF DE 128, AGY *

AgencyDisbursingIdentifier Code

Y 

Agency Accounting Identifier (6);

O3 in SFIS; Fiscal Station Number;

Comptroller defined; Identifies the

accounting system responsible forthe accounting event e.g., 021001

– DFAS Indianapolis (GFEBS)

FA2 DE 1196, L1

AccountingInstallationNumber

Y I I I I I I 

REF DE 128, AGZ *

AgencyAccountingIdentifier

Y 
Mapping Requisitioning MOV MRP Release Order Ship

( The mapping matrix codes: I = Implemented /

A = Available to be Added / M = Migration Code ) Rqn Referral

Passing

Modification Follow‐up Rqn Reinstatement Offer HW Turn‐ In AS6 ‐

ICP/

of R

SLOA Element X12 Segment X12 Qualifier X12 Qualifier Value Source 529 Code? 511R (4010) 511M (4010) 869F (4010) 517M (4010) 180M (4010) 940R (4030) Cost Object Element MappingsProject Identifier

FA2 DE 1196, 905 Project/Task M M M M M A 

REF DE 128, JB Job (Project) Number 

Funding Center Identifier

FA2 DE 1196, FC* Funding Center Identifier Y M M M M M M 

REF DE 128, ECA Fund Identifier 

Functional Area

FA2 DE1196, FA* Functional Area Y M M M M M M 

REF DE 128, 9X Account Category 

Cost Element Code

FA2 DE 1196, H1 Cost Code Y A A A A A A 

REF DE 128, 91 Cost Element 

Cost Center Identifier

FA2 DE 1196, CC* Cost Center Identifier Y M M M M M M 

REF DE 128, 79 Cost Account 

Activity Identifier

FA2 DE 1196, AI* Activity Identifier Y M M M M M M 

REF DE 128, BE Business Activity 

Work Order Number

FA2 DE 1196, WO* Work Order Number Y M M M M M M 

REF DE 128, WO Work Order Number 

5 DE 1196, code 90 is available in X12 version/release 4030. Migration code for 4010.
Mapping Requisitioning MOV MRP Release Order Shi

( The mapping matrix codes: I = Implemented /

A = Available to be Added / M = Migration Code )

Rqn

Referral

Passing

Modification Follow‐up Rqn Reinstatement Offer HW Turn‐ In AS6 

ICP/

of 

SLOA Element X12 Segment X12 Qualifier X12 Qualifier Value Source 529 Code? 511R (4010) 511M (4010) 869F (4010) 517M (4010) 180M (4010) 940R (4030) ERP Cost Object Mappings

Oracle

Cost Object 1 (16): Project

Identifier

FA2 DE 1196, 90 Project/Task

REF DE 128, JB Job (Project) Number

Cost Object 2 (16): Funding

Center Identifier

FA2 DE 1196, FC Funding Center Identifier

REF DE 128, ECA Fund Identifier

Cost Object 3 (16): Cost

Element Code

FA2 DE 1196, H1 Cost Code

REF DE 128, 91 Cost Element

Cost Object 4 (25): Activity

Identifier

FA2 DE 1196, AI Activity Identifier

REF DE 128, BE Business Activity

SAP

Cost Object 1 (16): Funding

Center Identifier

FA2 DE 1196, FC Funding Center Identifier

REF DE 128, ECA Fund Identifier

Cost Object 2 (16):Functional

Area

FA2 DE1196, FA Functional Area

REF DE 128, 9X Account Category

Cost Object 3 (16): Cost Center

Identifier

FA2 DE 1196, CC Cost Center Identifier

REF DE 128, 79 Cost Account

Cost Object 4 (25): Work Order

Number

FA2 DE 1196, WO Work Order Number

REF DE 128, WO Work Order Number

Others

Cost Object 1 (16): Funding

Center Identifier

FA2 DE 1196, FC Funding Center Identifier

REF DE 128, ECA Fund Identifier

Cost Object 2 (16): {Any but

Funding Center Identifier}

FA2 DE 1196, 90/FA /H1/CC/AI/WO

REF DE 128, JB/9X /91/79/BE/74

Cost Object 3 (16): {Any but

Funding Center Identifier}

FA2 DE 1196, 90/FA /H1/CC/AI/WO

REF DE 128, JB/9X /91/79/BE/74

Cost Object 4 (25): {Any but

Funding Center Identifier}

FA2 DE 1196, 90/FA /H1/CC/AI/WO

REF DE 128, JB/9X /91/79/BE/74
Attachment, ADC 1043 

Enclosure 5, page 1 

Enclosure 5, FA101 Qualifier Federal Note Fix 

(1) Where FA1 Segment is used in Federal ICs, remove the Federal note to the 

Agency Qualifier Code (position FA101) DF. Pending publication of the corrected Federal ICs, 

remove the Federal note from the associated DLMS Supplements. Additionally, for the Federal 

IC used independently (with no corresponding DLMS Supplement) for Wide Area Workflow, 

the Federal note will be revised to read: “Use to indicate a DoD service or agency.”

(2) Add the following new revised DLMS note “Use to indicate that the Component 

is a Department of Defense agency, including Defense Logistics Agency. Refer to ADC 1043.” 

to the Agency Qualifier Code (position FA101) DF in the DLMS Supplements listed below. 

Item 

# 

Location Revision Reason 

1. DLMS 

Introductory Notes 

If not already a supplement in enclosure 2, 

add ADC 1043 to DLMS Introductory 

notes to each updated DS. 

- ADC 1043, DLMS Revisions for 

Department of Defense (DOD) Standard 

Line of Accounting (SLOA)/Accounting 

Classification

Identifies DLMS 

Changes in the DLMS 

Supplement. 

2. See table below 

for specific 

locations 

Add new DLMS Note to FA101: 

DLMS Note: This data element is 

required for X12 syntax. Select the 

code that corresponds to the 

organization that is responsible for the 

assignment of the DoDAAC used to 

construct the controlling document 

number for the transaction. 

Adds new note to 

clarify the code 

selection. 

3. See table below 

for specific 

locations 

Remove Federal note and add new DLMS 

note to existing code DF for FA101: 

DF Department of Defense (DoD) 

Federal Note: 

Use to indicate that the Component 

originating the funds is a Department of 

Defense agency, including DLA.

DLMS Note: 

Use to indicate that the Component is a 

Department of Defense agency, 

including Defense Logistics Agency. 

Refer to ADC 1043.

Adds new revised 

DLMS note that 

clarifies that the DOD 

agency is responsible 

for the assignment of 

the DoDAAC used to 

construct the 

controlling document 

number for the 

transaction. 

 
Attachment, ADC 1043 

Enclosure 7, page 2 

DLMS Supplements to add new DLMS note 

Item 

# 

Location Revised DLMS Supplement 

1. 2/FA101/225 180M 

Material Returns Reporting 

2. 2/FA101/285 511M 

Requisition (Modification) 

3. 2/FA101/285 511R 

Requisition 

4. 2/FA101/135 517G 

Government Furnished Material (GFM) Validation 

5. 2/FA101/135 517M 

Material Obligation Validation (MOV) 

6. 2/FA101/345 527D 

Due-in, Advance Receipt, Due Verification 

7. 2/FA101/345 527R 

Receipt, Inquiry, Response and MRA 

8. 2/FA101/290 810L 

Logistics Bill 

9. 2/FA101/160 812L 

Logistics Bill Adjustment Request Reply 

10. 2/FA101/160 812R 

Logistics Bill Adjustment Request 

11. 2/FA101/4660 842A/R 

Standard Supply Discrepancy Report (SDR) Reply 

12. 2/FA101/340 867D 

Demand Reporting 

13. 2/FA101/340 867I 

Issue 

14. 2/FA101/190 869A 

Requisition Inquiry/Supply Assistance Request 

15. 2/FA101/190 869C 

Requisition Cancellation 

16. 2/FA101/190 869F 

Requisition Follow-Up 

17. 2/FA101/2900 940R 

Material Release 

18. 2/FA101/170 945A 

Material Release Advice 

19. 2/FA101/205

2/FA101/2050

947I (4010 & 4030) 

Inventory Adjustment 

Federal IC with no corresponding DLMS Supplement 

Item 

# 

Location Revised Federal IC 

1. 2/FA101/294 

2/FA101/507

Federal IC 857 

Shipment and Billing Notice 
Attachment, ADC 1043 

Enclosure 6, page 1 

Enclosure 6, Removal of the repetition for the FMS Case Designator FMSO I / FMSO II 

The Non-SLOA related supplement 856N, Notice of Availability is to be modified to remove the 

repetition of the FMS Case Designator for FMSO I and FMSO II, which is no longer a 

requirement. This change is being applied as part of ADC 1043 for consistency with the edits to 

LQ01 qualifier A4 in the SLOA related supplements per Enclosure 3. 

856N, Notice of Availability.

Item 

# 

Location Revision Reason 

1. DLMS 

Introductory Notes 

Add ADC 1043. 

- ADC 1043, DLMS Revisions for 

Department of Defense (DOD) Standard 

Line of Accounting (SLOA)/Accounting 

Classification

Identifies DLMS 

Changes in the DLMS 

Supplement. 

2. 2/LQ01/350 Revise DLMS Note for existing 

code A4: 

A4, Case Designator Number 

DLMS Note: 

1. Must use in FMS transactions to 

identify the FMS case number. 

For Cooperative Logistics Supply 

Support Agreements (CLSSAs), 

repeat up to two times to identify 

the Foreign Military Sales Order 

(FMSO) I and FMSO II case 

numbers. In this instance, the first 

occurrence will cite the FMSO I 

case number, and a second 

occurrence, if applicable, will 

reflect the FMSO II case number. 

Planned DLMS 

enhancement for two 

repetitions is obsolete. 

There is no 

requirement to include 

both the FMSO I case 

identifier and the 

FMSO II case 

identifier in a single 

requisition. Linking 

the FMSO I case 

identifier to the FMSO 

II case identifier is 

accomplished via the 

Defense Security 

Assistance 

Management System 

(DSAMS). 
DRAFT 

Attachment, ADC 1043 

Enclosure 7, page 1 

ENCLOSURE 7 

Coordination Comment Disposition 

# Component/ 

Agency 

Response/Comment Disposition 

1 DFAS (CL) Treasury Response: 

This initiative has been broached in our 

Interfund processing as Treasury is currently 

involved in discussions with DLA on the 

conversion of the DLA fund code file and 

those impacts to Navy and Marine Corps 

billing processes. 

Noted. 

2 Departmental Reporting BE/AFS does not 

use DLMS. 

Noted. 

3 STARS not SFIS compliant today and not 

impacted by DLMS SFIS execution, so 

DLMS migration to SLOA should have no 

impact as not directly feeder system. 

Noted. 

4 MOCAS, ADS, DCAS along with VISTA 

would need to consider any impacts, as they 

are highlighted as interfacing partners. Note 

to DCAS requesting update Supplemental 

Data Screen for Cross Disbursing to 

accommodate SLOA elements. 

Noted. 

5 DLMS will continue to dual process, as well, 

so even direct interfacing partners should be 

able to continue AS IS until they can become 

SLOA compliant. 

Noted. SLOA compliance is to be 

addressed in Component implementation 

plans to OUSD(C)/ODCMO. 

6 DFAS (CO) The Air Force Legacy systems currently fall 

into the category mentioned in 4.b.(3) on 

page 2. Therefore, they will be affected by 

the new Fund Code to the Fund Account 

Conversion Table. Based on information 

from the DEAMS Program Management 

Office, the Air Force ERP is currently able to 

send/receive SLOA/SFIS data elements. 

Noted. 
Attachment, ADC 1043 

Enclosure 7, page 2 

# Component/ 

Agency 

Response/Comment Disposition 

7 DFAS (CO) 

(cont.) 

In paragraph 4.d.(1)(c), the PDC indicates, 

‘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, the transaction will 

be rejected with Status Code CF.’ 

Currently, if a bill comes into DAAS with an 

invalid FC or without a FC, the system 

assigns the default FC and appropriation that 

belongs to the buyer component (For Air 

Force, that is FC 30, 57*3400). Will this 

process no longer be in place?

The default appropriation will be retained. 

However, under this DLMS change edits to 

preclude most instances of inconsistent 

data between the supply transactions and 

the SFIS Fund Code table. Additional 

DAAS edits will be required for 

transactions with invalid or missing fund 

codes; this will be addressed in a future 

PDC. 

8 Also, Defense Agencies currently uses a 

default appropriation: 4930.5999. Will this 

default appropriation be included in their FC 

table? Otherwise, the limit may be 

considered invalid and reject. The use of this 

appropriation as the default for all Defense 

Agencies creates a condition where the 

transactions are not identifiable to a specific 

Agency. This may hinder successful tracking 

of transactions. We may need to revisit the 

use of default appropriations, unless the plan 

is to reject them.

This default appropriation for 

Service/Agency Code H will not be 

included in the SFIS Fund Code table; per 

MILSBILLS Appendix 2.2, bill via noninterfund. DFAS research source of noncompliant use of the default appropriation 

and take corrective action with the 

violating system. DLA Transaction 

Services logistics reports and MILSINQ

are available for researching these. 

9 In paragraph 4.d.(1)(d). the PDC indicates, 

‘Fund Code Monitors will add or modify the 

following discrete data elements for assigned 

fund codes: concatenated accounting string, 

Department Regular Code, Main Account 

Code, Sub-Account Code, Treasury Sub 

Class, Limit/Subhead, Beginning Period of 

Availability, Ending Period of Availability. 

Note that new fund codes may be required 

for multi-year appropriations.’ We have a 

number of questions about this: 

1. These 7 data elements are only a small 

portion of the required SLOA/SFIS elements. 

Are there implementation plans underway to 

include the remaining elements in a discrete 

table? 

There are no plans to include all the SLOA 

data elements in the SFIS Fund Code table. 

When the initiating system does not 

provide all SLOA data elements in the 

transaction, only a limited number of 

SLOA data elements can be 

accommodated via the SFIS Fund Code 

Table. The remaining SLOA data elements 

can only be obtained from the initiating 

system. 
Attachment, ADC 1043 

Enclosure 7, page 3 

# Component/ 

Agency 

Response/Comment Disposition 

10 DFAS (CO) 

(cont.) 

2. Air Force will be able to supply the 

number of needed fund codes based on the 

appropriations currently in use. However, 

the Air Force components will need to 

submit their fund code requests in order for 

these new fund codes to be established. 

AFAFO will need to notify their bases. 

Noted. 

11 3. We currently have to submit fund code 

add/delete/change requests in a specific 

format. Will we still be submitting requests, 

or accessing the table directly? If we are 

submitting the requests, will the request 

format be included in the regulation update? 

When fully implemented, Fund Code 

Monitors will use the Web application to 

enter fund code add/delete/change. 

12 4. DFAS for Air Force is currently 

evaluating the cost and timeframes for 

updating their legacy systems to 

accommodate SFIS and SLOA. Once this is 

accomplished, and legacy systems no longer 

need the translation, will this table still be 

used to validate appropriations? 

The fund code table will be available until 

all trading partners are DLMS compliant. 

There are no plans to eliminate the fund 

code tables in the near future. 

13 5. Since SLOA elements do not include the 

Fund Code, will DAAS strip off the fund 

code before sending bills to the SLOAcompliant systems? And how will DAAS 

provide a fund code to non-SLOA compliant 

systems if a SLOA-compliant system 

provides data without a fund code? 

No. Both discrete data (where available) 

and fund code are required in DLMS 

transactions. 

14 6. Will appendices still be used for Signal 

Code C or L to determine the billable 

DoDAAC? Will the process for updating 

them remain the same?

Signal codes C/L will remain for third 

party billing to identify the bill-to party 

and applicable LOA. Updates will be via 

the Web application. PDC 1009 provides a 

transition plan to eliminate signal code 

upon full transition to DLMS. 

15 Enclosure 1: 

1. The implementation of the SLOA requires 

that all edit tables utilized for contract 

writing systems, payment systems and 

expenditure reporting and routing systems be 

required to include all data elements for 

validation within the SLOA. Without 

consistent validation of data, errors at the 

time of reporting may continue to cause 

rework. Is this what they are referring to on 

page 27/28?

Contact writing is outside the scope of 

DLMS and this PDC. Question referred to 

OUSD(C)/ODCMO. 
Attachment, ADC 1043 

Enclosure 7, page 4 

# Component/ 

Agency 

Response/Comment Disposition 

16 DFAS (CO) 

(cont.) 

2. IBOP requirements - SLOA requirements 

do not seem to include a location to identify 

and pass IBOP criteria requirements from 

contract writing to payment and expenditure 

reporting systems to be able to successfully 

report this requirement. How will the IBOP 

reporting requirements be met with the 

implementation of SLOA?

Contact writing is outside the scope of 

DLMS and this PDC. Question referred to 

OUSD(C)/ODCMO. 

17 DFAS (Rome) Who/how will the SFIS Fund Code to the 

Fund Account Conversion Table be 

maintained and kept current with other 

master tables such as the ones in GFEBS? 

Component Fund Code Monitors will 

maintain their fund codes via a Web 

application. The database will be available 

for system to system synchronization. 

18 Will interfaces with other systems such as 

Interfund be affected? Have interfaces been 

mapped properly so that data elements are 

not dropped as they are with some of the 

DCAS interfaces? 

The SFIS Fund Code Table/database will 

be available for system to system 

synchronization in a standard file layout. 

Internal mapping within Component 

systems is a Component responsibility. 

Note that the current process for providing 

fund code updates will remain available 

until all trading partners can achieve 

system to system synchronization; 

however, additional SLOA data will not be 

provided. Similarly, mapping from DLMS 

to Component systems is a Component 

responsibility. 

19 DLA Concur with PDC 1043 as required by OSD 

directives.

Noted. 

20 1. Paragraph 4.b.(3) 

a. New discrete data elements of Fund 

Code (Department Regular Code, Main 

Account Code, Sub-Account Code, 

Treasury Sub Class, Limit/Subhead 

(legacy), Beginning Period of 

Availability and Ending Period of 

Availability) 

QUESTIONS: 

i. Will the new fields be Mandatory? 

ii. Will there be field validation performed 

for new fields? 

iii. Will values be defined within EBS? 

iv. How will this data be maintained in 

EBS? 

i. No. Lack of SLOA data will not cause 

transactions to fail. 

ii. Select discrete SLOA data within 

DLMS transactions will be validated 

against values from the fund code table. 

Where there is inconsistency, PDC 1043 

calls for transactions to be rejected. The 

SFIS Web Fund Code application contains 

edits regarding the field length and type of 

characters that may be entered for a data 

element. There are also some consistency 

edits. However, these edits will not 

completely eliminate the potential for 

entry of incorrect data. 

iii & iv. EBS implementation and 

maintenance is a DLA responsibility. 
Attachment, ADC 1043 

Enclosure 7, page 5 

# Component/ 

Agency 

Response/Comment Disposition 

21 DLA 

(cont.) 

b. Current EBS Table (ZSFT_APPACCT) 

QUESTIONS: 

i. Will this table be modified to add the 

new discrete data elements? If not, then 

where will the new discrete data 

elements be added? 

ii. What is the impact to the current fields 

within ZDFT_APPACCT? 

i. EBS implementation and maintenance is 

a DLA responsibility. New SLOA data will 

be added to the DLA Transaction Services 

database. The database will be available 

for system to system synchronization. 

ii. EBS impact assessment is a DLA 

responsibility. The current fund code fields 

will be retained in the SFIS Fund Code 

table. As EBS is able to accept the discrete 

SLOA data elements from the SFIS Fund 

Code Table, it will be available for system 

to system synchronization. 

22 c. Existing fields (Fund Code, Service Bill 

Code, Signal Code, Appropriation 

Account Fund Code, and Constant F) 

QUESTIONS: 

i. How will this data be maintained in 

EBS? 

i. EBS implementation and maintenance is 

a DLA responsibility. Fund Code, Service 

Bill Code, Signal Code, Appropriation 

Account, Fund Code will be retained in 

DLMS and legacy transactions. Constant F 

is not a DLMS data field. 

23 d. All DLMS related fields 

QUESTIONS: 

i. Who (what Job/Role) will maintain in 

EBS? 

ii. What is the "current concatenated 

accounting string" referenced? 

i. EBS maintenance is a DLA 

responsibility. 

ii. The Line of Accounting (LOA) 

“concatenated string” currently available 

from the Fund Code Table consists of the 

Department Regular Code (2 characters), 

Fiscal Year Chargeable Indicator (1 

character), Main Account (4 characters) 

and Limit/Subhead (4 characters). This 11 

character concatenated LOA is based on 80 

record position limitations of MILS 

transactions. SLOA requires discrete data 

elements, vice concatenation of the LOA. 

The current concatenated LOA string will 

be maintained so as not to impact existing 

systems. 
Attachment, ADC 1043 

Enclosure 7, page 6 

# Component/ 

Agency 

Response/Comment Disposition 

24 DLA 

(cont.) 

2. Paragraph 4.b.(4) 

a. Codes to support financial data content 

will be requested for Budget and 

Accounting Classification Code Source 

529 governed by reference 3.e. OUSD(C) 

BIO and ODCMO have reviewed the 

data mapping at Enclosure 4 

QUESTIONS: 

i. How does Enclosure 4 fit to the new 

discrete data elements of Fund Code 

identified within 4.b.(3)? 

Enclosure 4 provides mapping for DLMS 

transactions which will carry SLOA data 

elements as applicable. The fund code is 

also required by DLMS. Only a limited 

subset of SLOA data will be available from 

the SFIS Fund Code table. DAAS will map 

available SLOA data from MILS to 

DLMS, but cannot convert from discrete 

SLOA data to a specific fund code. Only 

the fund code can be mapped from DLMS 

to MILS. Thus, the fund code must be 

retained. DAAS will reject DLMS 

transactions where the discrete SLOA data 

from the SFIS Fund Code Table is 

inconsistent with discrete SLOA data in a 

DLMS transaction. 

25 b. Selected codes applicable to Security 

Assistance retain their original code 

source. See Volume 1 of reference 3.c. 

for an explanation of migration codes in 

DLMS supplements. 

QUESTIONS: 

i. How does reference fit to the new 

FMS/Security Cooperative related data 

elements? 

The Volume 1 explanation of migration 

codes is a separate point applicable to how 

data elements are correlated with X12 for 

use in the DLMS. Selected Security 

Assistance data elements make use of the 

migration code. Others retain their original 

code and code source with updated data 

element names. 

26 3. Paragraph 4.b.(6) 

a. Interim use of the SFIS Fund Code to 

Fund Account Conversion Table 

described in section 4.b.(3). 

QUESTIONS: 

i. Where are the details regarding the 

conversion? 

ii. Will this conversion table be maintained 

within EBS? If not, why not? 

i. PDC 1043 provides an overview of the 

fund code conversion process, which will 

be incorporated into DLMS manuals See 

“Requested Change in Detail: (1) Fund 

Code Process”. Information is also 

available in the DLMS Finance Training 

Module on the FPRC Web page at 

http://www.dla.mil/j6/dlmso/Programs/Committees/Finance/fin

anceprc.asp. In addition, this will be a 

discussion topic at SPRC/FPRC on June 

20. Refer to slides attached to the agenda. 

ii. The authoritative fund code data base is 

maintained by DLA Transaction Services 

and will be available for system to system 

synchronization to update EBS. 
Attachment, ADC 1043 

Enclosure 7, page 7 

# Component/ 

Agency 

Response/Comment Disposition 

27 DLA 

(cont.) 

4. Paragraph 4.b.(8) 

a. Agency Qualifier Code DF 

QUESTIONS: 

i. Will this field be blank for non-DOD? 

The field will not be blank. Other codes 

are available in FA101 for Services and 

“FG” for Federal Government. As a result 

of further consideration DLMSO 

determined that clarification is needed for 

FG to include special programs (which are 

neither DOD or other Federal), and a new 

DLMS note will be added. 

28 5. Paragraph 4.d.(1)(c) 

a. SFIS Fund Code to Fund Account 

Conversion Table 

QUESTIONS: 

i. Will this table be in EBS? If not, why 

not? 

ii. Is this different from conversion table 

referenced in Paragraph 4.b.(6)? 

i. EBS implementation and maintenance is 

a DLA responsibility. The authoritative 

fund code data base is maintained by DLA 

Transaction Services and will be available 

for system to system synchronization to 

update EBS. 

ii. There is only one SFIS Fund Code to 

Fund Account Conversion Table 

29 6. Paragraph 4.d.(1)(d) 

a. Error Codes 

QUESTIONS: 

i. Does Status Code CF pertain to SLOA 

related rejects only? 

Yes. CF Rejected. Discrete values for the 

Standard Line of Accounting 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. If still 

required, submit a new requisition with 

valid data entries.

30 GSA At this time, GSA will not be DLMS capable 

before October 2015. As such, we will not 

be able to carry any of the additional SLOA 

data elements in our logistics transactions. 

Noted. 

31 FAA Note: Delphi is the DOT accounting system 

of record. Delphi is Oracle Federal 

Financials version 11i and will be upgraded 

to Oracle Federal Financials R12 sometime 

next calendar year. 

Noted. 

32 Lana Null, Branch Manager, AMZ-170, 

(405) 954-1599, 04/16/2013: The new fields 

listed below will be a part of R12. Currently 

Delphi is not set up to use the new format. 

However, in Treasury's IPAC System, we are 

already required to submit our TAS in the 

new format, and have been doing so for 

many months, so we are very familiar with 

the new Treasury requirements. 

Noted. 
Attachment, ADC 1043 

Enclosure 7, page 8 

# Component/ 

Agency 

Response/Comment Disposition 

33 FAA 

(cont.) 

The current LOA for FAA does not match 

the new format DoD is describing, but will in 

R12. 

Noted. 

 For example, currently the Franchise Fund 

(12X3000000) has a GWA Treasury Symbol 

of 69-X-4562. 

In the new format it is: 

 The TAS is currently the only segment of the 

LOA that DoD needs to issue an IPAC to 

collect funds from FAA. We can provide that 

info to them if needed; it would be the above 

information. 

34 Comments from the LCSS perspective: 

 DLA Memorandum for Supply and Finance 

Process Review committees (PRCs), 

Proposed DLMS Change PDC1043, DLMS 

Revisions for DoD Standard Line of 

Accounting(SLOA)/Accounting 

Classification (Finance/Supply), §4.d.(1) 

indicates that in future the web-enabled SFIS 

Fund Code to Fund Account Conversion 

Table will be updated to support Treasury 

mandates for Government-Wide Treasury 

Account Symbol (GTAS) reporting to 

Treasury and that DLA Transaction Services 

will populate the SFIS/GTAS information to 

the DLMS transaction during its translation 

between trading partners: 

 Does the SFIS Fund Code to Fund Account 

Conversion Table and the web service to be 

developed mean that DLA Transaction 

Services will be doing the conversion using 

the web-enabled application to 

add/perpetuate the SFIS information on the 

DLMS Transactions? 

Yes. DAAS will add/perpetuate 

SFIS/SLOA data. However, only limited 

SFIS data is available from the SFIS Fund 

Code table. 

 Note: LCSS transactions will be DLMS 

compliant. LCSS will be replacing legacy 

LIS. 

Noted. 
Attachment, ADC 1043 

Enclosure 7, page 9 

# Component/ 

Agency 

Response/Comment Disposition 

35 Joint OUSD(C) / 

ODCMO 

{Responding to Staffing Note at 4.d.(4)}

The Cost Objects are required to be carried 

from the point of requisition through to the 

Bill/Payment. They act as a compensating 

control for scenarios where Requisitions 

Numbers can’t be identified. Further, for 

external requisitioning scenarios, if the cost 

object is not identified by the requisitioner, 

then the accounting system will not have a 

way of determining it. 

Noted 

26 {Enclosure 1} If you need the final signed 

letter, please obtain it from the following 

link: 

http://dcmo.defense.gov/products-andservices/standard-financial-informationstructure/

Noted 

37 {Responding to Staffing Note at Enclosure 

2, Element (1)} Sub Class is a further 

Treasury Account Symbol (TAS) breakout 

below the Main Account. It is used to 

separate funding for a particular purpose or 

scenario. As an example, if a Federal 

Agency borrows funding from the Treasury 

or Federal Financing Bank (FFB). It needs 

to keep the borrowed funds segregated from 

its non-borrowed funds. The Sub Class is 

the data element which identifies this 

distinction. 

Noted 

 Sub Class & BETC will be rarely included in 

the SLOA before the point of disbursement. 

There are three scenarios where they could 

potentially be applicable: Borrowing from 

Treasury, Borrowing from Federal Financing 

Bank, and Payments from Current 

Appropriations for Obligations of Closed 

Accounts. Currently for the first two, there 

are no current DoD scenarios for 

Appropriations that may be obligated and 

also have borrowing authority. However, 

this has existed in the past such as in the 

working capital fund. 
Attachment, ADC 1043 

Enclosure 7, page 10 

# Component/ 

Agency 

Response/Comment Disposition 

 Joint OUSD(C) / 

ODCMO 

(cont.) 

For the third, Payments from Current 

Appropriations for Obligations of Closed 

Accounts, the A-11 Section 130.14 states: 

"Legitimately incurred obligations that have 

not been disbursed (i.e., paid) at the time a 

TAFS is canceled cannot be disbursed from 

the canceled obligated or unobligated 

balances of the canceled TAFS. 

After a TAFS is canceled, any obligations or 

adjustments to obligations that would have 

been properly chargeable to that TAFS may 

be disbursed from an unexpired TAFS that is 

available for obligation for the same purpose 

as the closed TAFS, provided that: 

Payment of obligations against canceled 

TAFSs from unexpired TAFSs are limited to 

one percent of the appropriation in the 

unexpired TAFS. No more than one percent 

of an unexpired TAFS may be used to pay 

any combination of canceled obligations. 

This is a single, cumulative limit. It applies 

to one percent of the annual appropriation 

(not total budgetary resources) for annual 

TAFSs and to unexpired appropriations for 

multi-year TAFSs." 

http://www.whitehouse.gov/sites/default/files

/omb/assets/a11_current_year/a_11_2011.pd

f 

 The Treasury requires that disbursement 

from unexpired TAFS that is available for 

obligation for the same purpose... be reported 

with a Subclass (46) or under GWA BETC 

DISBCA. TFM 4-7050.15 - "In cases where 

the liability is valid but the claim is placed 

after the appropriation account is closed and 

the balance canceled, the FPA/NTDO may 

use up to 1 percent of its current 

appropriation by reporting a 46 subclass on 

the Statement of Transactions or it may seek 

a reappropriation." 

http://www.fms.treas.gov/tfm/vol1/v1p4c700

.pdf 
Attachment, ADC 1043 

Enclosure 7, page 11 

# Component/ 

Agency 

Response/Comment Disposition 

 Joint OUSD(C) / 

ODCMO 

(cont.) 

Since, we use multiple disbursing systems, 

we are unaware of a way that a disbursing 

system would be able to control and 

calculate this value at the time of 

disbursement. 

The SFIS solution is to set aside the funding 

in a different account, front-load the 

subclass/BETC value on the Purchase 

Request, and carry it forward to the 

disbursing system. This would let the 

disbursing system know what the payment is 

for and allow it to properly classify/report 

the disbursement. 

Currently, there are two sets off Sub Class 

values Standard and Nonstandard. DoD 

currently only has Standard Values. 

Additionally, these standard values will be 

replaced under GTAS by the BETC. 

However, Treasury has stated it may add 

new Sub Class values for DoD in the future 

and DoD should be ready to execute and 

report by the values. Under the GTAS, we 

would expect the values to be Null until the 

Treasury adds values for DoD. 

38 {Responding to Staffing Note at Enclosure 

2, Element (2)}For Appropriation Transfers, 

the TAS needs to identify which Federal 

Agency is the owner of the funds with the 

value in the Department Transfer field. For 

example, Foreign Military Sales (FMS) 

appropriations are transferred to DoD from 

the Executive Office of the President. 

Therefore, for execution of these funds, DoD 

needs to identify Department Transfer value 

“011” - Executive Office of the President. 

This allows for proper segregation of other 

federal agencies funds from DoD’s. 

Noted. 
Attachment, ADC 1043 

Enclosure 7, page 12 

# Component/ 

Agency 

Response/Comment Disposition 

39 Joint OUSD(C) / 

ODCMO 

(cont.) 

{Responding to Staffing Note at Enclosure 

2, Element (9)}Sub Class is a further 

Treasury Account Symbol (TAS) breakout 

below the Main Account. It is used to 

separate funding for a particular purpose or 

scenario. As an example, if a Federal 

Agency borrows funding from the Treasury 

or Federal Financing Bank (FFB). It needs 

to keep the borrowed funds segregated from 

its non-borrowed funds. The Sub Class is 

the data element which identifies this 

distinction. 

Noted. 

 Sub Class & BETC will be rarely included in 

the SLOA before the point of disbursement. 

There are three scenarios where they could 

potentially be applicable: Borrowing from 

Treasury, Borrowing from Federal Financing 

Bank, and Payments from Current 

Appropriations for Obligations of Closed 

Accounts. Currently for the first two, there 

are no current DoD scenarios for 

Appropriations that may be obligated and 

also have borrowing authority. However, 

this has existed in the past such as in the 

working capital fund. 
Attachment, ADC 1043 

Enclosure 7, page 13 

# Component/ 

Agency 

Response/Comment Disposition 

 Joint OUSD(C) / 

ODCMO 

(cont.) 

For the third, Payments from Current 

Appropriations for Obligations of Closed 

Accounts, the A-11 Section 130.14 states: 

"Legitimately incurred obligations that have 

not been disbursed (i.e., paid) at the time a 

TAFS is canceled cannot be disbursed from 

the canceled obligated or unobligated 

balances of the canceled TAFS. 

After a TAFS is canceled, any obligations or 

adjustments to obligations that would have 

been properly chargeable to that TAFS may 

be disbursed from an unexpired TAFS that is 

available for obligation for the same purpose 

as the closed TAFS, provided that: 

Payment of obligations against canceled 

TAFSs from unexpired TAFSs are limited to 

one percent of the appropriation in the 

unexpired TAFS. No more than one percent 

of an unexpired TAFS may be used to pay 

any combination of canceled obligations. 

This is a single, cumulative limit. It applies 

to one percent of the annual appropriation 

(not total budgetary resources) for annual 

TAFSs and to unexpired appropriations for 

multi-year TAFSs." 

http://www.whitehouse.gov/sites/default/files

/omb/assets/a11_current_year/a_11_2011.pd

f 

 The Treasury requires that disbursement 

from unexpired TAFS that is available for 

obligation for the same purpose... be reported 

with a Subclass (46) or under GWA BETC 

DISBCA. TFM 4-7050.15 - "In cases where 

the liability is valid but the claim is placed 

after the appropriation account is closed and 

the balance canceled, the FPA/NTDO may 

use up to 1 percent of its current 

appropriation by reporting a 46 subclass on 

the Statement of Transactions or it may seek 

a reappropriation." 

http://www.fms.treas.gov/tfm/vol1/v1p4c700

.pdf

 Since, we use multiple disbursing systems, 

we are unaware of a way that a disbursing 

system would be able to control and 

calculate this value at the time of 

disbursement. 
Attachment, ADC 1043 

Enclosure 7, page 14 

# Component/ 

Agency 

Response/Comment Disposition 

 Joint OUSD(C) / 

ODCMO 

(cont.) 

The SFIS solution is to set aside the funding 

in a different account, front-load the 

subclass/BETC value on the Purchase 

Request, and carry it forward to the 

disbursing system. This would let the 

disbursing system know what the payment is 

for and allow it to properly classify/report 

the disbursement. 

 Currently, there are two sets off Sub Class 

values Standard and Nonstandard. DoD 

currently only has Standard Values. 

Additionally, these standard values will be 

replaced under GTAS by the BETC. 

However, Treasury has stated it may add 

new Sub Class values for DoD in the future 

and DoD should be ready to execute and 

report by the values. Under the GTAS, we 

would expect the values to be Null until the 

Treasury adds values for DoD. 

40 {Responding to Staffing Note at Enclosure 

2, Element (11)} Appropriations are broken 

out as reimbursable or direct. This is 

different than whether the transaction is a 

reimbursable activity. This should be 

included in the 511R. The 810L would just 

reference what came from the 511R. If it is 

not on the 511R, it could not be added at the 

point of the Bill. 

Noted. Carrying in DLMS; possible 

addition to the SFIS Fund Code table. 

41 USA The Army concurs with this PDC as written. Noted 

42 USAF AF concurs with comments. Noted 

43 1. These are our preliminary comments. Noted 

44 2. The DTEB is waiting for someone to 

bring in a requirement. So, we reiterate the 

need to make this a part of FIAR discussion 

and continue to search for a POC at USTC or 

OSD(TP) who thinks this is a worthy topic 

for discussion. AF response needs to 

identify the lack of synchronization between 

the supply and transportation communities. 

SLOA implementation in the 

transportation domain is outside the scope 

of DLMSO. Recommend coordinating 

with OUSD(C)/ODCMO action officers in 

the memorandum regarding FIAR for 

transportation implementation 

requirements. Agree with coordinating 

with USTRANSCOM and OSD(TP). 

45 3. PDC 1043 does have an impact to ILS-S. Noted 
Attachment, ADC 1043 

Enclosure 7, page 15 

# Component/ 

Agency 

Response/Comment Disposition 

46 USAF 

(cont.) 

4. In the interim until ILS-S can be modified 

for SLOA/SFIS data structure/functionality, 

ILS-S will have to be modified to accept the 

new status code of CF to indicate discrete 

values for 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. For this interim process the 

transaction would be cancelled and the user 

would need to obtain the correct fund code 

and resubmit. AF publications would 

require change to provide instructions on 

who is the AF Fund Code Monitor to ensure 

the table is correct. Based upon the PDC the 

Fund Code Table at DLA 

Transaction Services will be available 30 Sep 

2014 so ILS-S will be modified early 2014 

(Jan or June release) to accept CF status. 

Noted 

47 5. In the long term ILS-S will require a 

schema change to accommodate the 

SLOA/SFIS and will not be able to start until 

FY18 when the ILS-S code roll is projected 

to be completed. Also this PDC impacts 8 

DLMS transactions we currently do. We 

would need the finance systems to be on 

board with these changes as well since we 

cannot change those interfaces without them. 

It is imperative that the AF finance systems 

be included in the tiger team discussions 

with ILS-S. 

Noted 

48 6. Also in para 4.b.7 (SIFS) should be SFIS. Correction made. 

49 7. "SCS is not SLOA compliant at this time, 

so any proposed changes to the format would 

not affect us today. However, during our 

current Bluebook review, we have 

determined that FFM 

01.04.030 will require us to be SLOA 

compliant and when we write up the CSRD 

for this requirement, we will have to ensure 

that any new format or data changes will be 

included in our CSRD. " 

Noted. 

50 8. The AF is still reviewing this PDC and 

will more than likely have additional followon comments. 

Noted. No additional comments received. 
Attachment, ADC 1043 

Enclosure 7, page 16 

# Component/ 

Agency 

Response/Comment Disposition 

51 USAF 

(cont.) 

9. Do you have a complete list of the supply 

systems that are impacted (I'm assuming this 

was determined given the specific business 

processes and specific transaction 

information identified beginning on 

Attachment page 5)? Please provide us the 

list of systems if possible. 

Identification of impacted systems and 

process voids was to be made in initial 

SLOA implementation plans due to 

OUSD(C)/ODCMO in January 2013. 

Recommend coordinating with 

OUSD(C)/ODCMO action officers in the 

memorandum for additional information. 

52 10. Please provide the fund code and fund 

account conversion details (i.e. logic). There 

are several data elements with conversion 

information identified beginning on 

Attachment page 30, but I want to make sure 

we are aware of all recommendations. 

This will be a discussion topic at the joint 

SPRC/FPRC on June 2013, 2013.See 

slides attached to the agenda. A file layout 

for the SFIS Fund Code table will be 

provided. 

53 11. Please provide clarification on the 

use/requirement of the DLA transaction 

services. Also, who are the fund code 

monitors, are we talking about the 

appropriation managers (reference 

attachment page 5)? Given that we utilize 

the FMDQS as the authoritative source for 

validating and identifying financial 

information in our systems, we will have to 

ensure that we are not implementing a 

process that will circumvent the purpose/use 

of the FMDQS. Given today's process, the 

appropriation managers would provide us 

necessary and valid/approved information to 

update the FMDD, and in turn our users (to 

include systems) refer to the FMDD for valid 

values. Generally, if a data element/value is 

not in the FMDD, a user is not approved to 

carry/use that information. So we could 

implement a process where we could have 

our data management team be the central 

control point for providing information to 

update the transaction services validation 

tables if need be. 

DLA Transaction Services maintains the 

authoritative database of fund codes. Fund 

codes are used in DLMS/MILS logistics 

transactions to indicate non-interfund 

billing or in the case of Interfund billing 

provide LOA data from the SFIS Fund 

Code table. All Interfund bills are routed 

through DLA Transaction Services for edit 

validation. DAAS will validate discrete 

SLOA elements from the fund code table 

to the discrete elements in DLMS 

transactions for inconsistencies. For MILS 

to DLMS mappings DAAS will use the 

fund code to apply discrete SLOA data 

based on the SFIS Fund Code table. 

Fund Code monitors maintain fund codes 

on the Fund Code table. They are 

designated by the Components and 

Agencies. See https://www2.dla.millj6/dlmso/CertAccess/SvcPointsPOC/all 

poc.asp. 

There is a separate briefing on fund codes 

included in the briefing slides attached to 

the June 20, 2013 FPRC/SPRC meeting 

agenda. 
Attachment, ADC 1043 

Enclosure 7, page 17 

# Component/ 

Agency 

Response/Comment Disposition 

54 USAF 

(cont.) 

12. This information as a whole impacts our 

ongoing SLOA analysis/implementation 

efforts. We are in the process of 

identifying/validating the necessary 

mappings and translation logic for each 

system/interface given their current data 

elements (i.e. legacy) and required 

SLOA/SFIS data, as well as looking at the 

processes supported by the systems initially 

determined to be within scope for SLOA. So 

we need to be sure the universe of systems, 

as well as the mappings and translations we 

are recommending, are consistent with this 

DLA PDC. In addition, there are several 

data elements that we are in the process of 

reviewing/finalizing standardization on 

within the Air Force (i.e. the cost elements, 

project identifier, cost element code, etc). 

The standardization for these are up to the 

Component. The Component just has to 

clearly identify what we are capturing in 

these fields. So I would not want our 

systems to take the example mappings 

identified in this PDC and believe that this is 

the final/approved direction for the Air 

Force. 

Noted. 

55 13. DLA transaction services (i.e. GEX) is 

one of our recommended solutions for 

translation services for our Air Force 

systems. However, we have not made it 

mandatory yet for our systems to subscribe 

to this service for validation/translation. I 

want to also make sure we are not 

duplicating efforts by requesting our services 

to look into gaining access to DLA 

Transaction Services, and make sure that this 

direction is not premature. 

Use of DLA Transaction Services is 

required to implement the DLMS SLOA 

requirements. 
Attachment, ADC 1043 

Enclosure 7, page 18 

# Component/ 

Agency 

Response/Comment Disposition 

56 USAF 

(cont.) 

14. I understand from a DLMS perspective, 

we have to ensure the systems impacted will 

be postured and SLOA ready. So I agree 

with the DLMS requirements in regards to 

recognizing changes driven by the SLOA 

requirement and we will ensure we do our 

part from a data management perspective to 

provide an Air Force approach to support the 

DLMS standards and practices. However, 

without having and properly understanding 

the intent of all the details, I'm not sure we 

fully agree with the proposed way forward to 

implement the changes. As additional POCs 

review the information, we may have more 

comments/questions to provide you for 

coordination with the DLA POCs as 

necessary to ensure we implement an Air 

Force information/processes that support the 

DLMS standards and practices. 

Noted. 

57 15. The Air Force Legacy systems currently 

fall into the category mentioned in 4.b.(3) on 

page 2. Therefore, they will be affected by 

the new Fund Code to the Fund Account 

Conversion Table. Based on information 

from the DEAMS Program Management 

Office, the Air Force ERP is currently able to 

send/receive SLOA/SFIS data elements. 

Noted. 

58 16. In paragraph 4.d.(1)(c), the PDC 

indicates, ‘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, the transaction 

will be rejected with Status Code CF.’ 

Currently, if a bill comes into DAAS with an 

invalid FC or without a FC, the system 

assigns the default FC and appropriation that 

belongs to the buyer component (For Air 

Force, that is FC 30, 57*3400). Will this 

process no longer be in place? Also, Defense 

Agencies currently uses a default 

appropriation: 4930.5999. Will this default 

appropriation be included in their FC table? 

Otherwise, the limit may be considered 

invalid and reject. 

The default appropriation will be retained. 

However, under this DLMS change edits to 

preclude most instances of inconsistent 

data between the supply transactions and 

the SFIS Fund Code table. Additional 

DAAS edits will be required for 

transactions with invalid or missing fund 

codes; this will be addressed in a future 

PDC. 

This default appropriation for 

Service/Agency Code H will not be 

included in the SFIS Fund Code table; per 

MILSBILLS Appendix 2.2, bill via noninterfund. DFAS research source of noncompliant use of the default appropriation 

and take corrective action with the 

violating system. DLA Transaction 

Services logistics reports and MILSINQ

are available for researching these. 
Attachment, ADC 1043 

Enclosure 7, page 19 

# Component/ 

Agency 

Response/Comment Disposition 

59 USAF 

(cont.) 

17. In paragraph 4.d.(1)(d). the PDC 

indicates, ‘Fund Code Monitors will add or 

modify the following discrete data elements 

for assigned fund codes: concatenated 

accounting string, Department Regular Code, 

Main Account Code, Sub-Account Code, 

Treasury Sub Class, Limit/Subhead, 

Beginning Period of Availability, Ending 

Period of Availability. Note that new fund 

codes may be required for multi-year 

appropriations.’ We have a number of 

questions about this: 

60 a. These 7 data elements are only a 

small portion of the required SLOA/SFIS 

elements. Are there implementation plans 

underway to include the remaining elements 

in a discrete table? 

No. The remaining SLOA data elements 

will be contained inside the DLMS 

transaction. 

61 b. Air Force will be able to supply the 

number of needed fund codes based on the 

appropriations currently in use. However, 

the Air Force components will need to 

submit their fund code requests in order for 

these new fund codes to be established. 

AFAFO will need to notify their bases. 

Noted. 

62 c. We currently have to submit fund code 

add/delete/change requests in a specific 

format. Will we still be submitting 

requests, or accessing the table directly? If 

we are submitting the requests, will the 

request format be included in the regulation 

update? 

Fund Codes will be updated by 

Component/ Agency Fund Code 

monitors via a Web application. 

63 d. DFAS for Air Force is currently 

evaluating the cost and timeframes for 

updating their legacy systems to 

accommodate SFIS and SLOA. Once this is 

accomplished, and legacy systems no longer 

need the translation, will this table still be 

used to validate appropriations? 

Yes. 

64 e. Since SLOA elements do not include the 

Fund Code, will the DAAS strip off the fund 

code before sending bills to the SLOA 

compliant systems? And how will DAAS 

provide a fund code to non-SLOA compliant 

systems if a SLOA-compliant system 

provides data without a fund code? 

No. Both discrete data (where available) 

and fund code are required in DLMS 

transactions. 
Attachment, ADC 1043 

Enclosure 7, page 20 

# Component/ 

Agency 

Response/Comment Disposition 

65 USAF 

(cont.) 

f. Will appendices still be used for Signal 

Code C or L to determine the billable 

DoDAAC? Will the process for updating 

them remain the same? 

Signal codes C/L will remain for third 

party billing to identify the bill-to party 

and applicable LOA. Updates will be via 

the Web application. PDC 1009 provides a 

transition plan to eliminate signal code 

upon full transition to DLMS. 

66 18. The implementation of the SLOA 

requires that all edit tables utilized for 

contract writing systems, payment systems 

and expenditure reporting and routing 

systems be required to include all data 

elements for validation within the SLOA. 

Without consistent validation of data, errors 

at the time of reporting may continue to 

cause rework. Is this what they are referring 

to on page 27/28? 

Contact writing is outside the scope of 

DLMS and this PDC. Question referred to 

OUSD(C)/ODCMO. 

67 19. IBOP requirements - SLOA requirements 

do not seem to include a location to identify 

and pass IBOP criteria requirements from 

contract writing to payment and expenditure 

reporting systems to be able to successfully 

report this requirement. How will the IBOP 

reporting requirements be met with the 

implementation of SLOA? 

Contact writing is outside the scope of 

DLMS and this PDC. Question referred to 

OUSD(C)/ODCMO. 

68 USMC 1. Headquarters Marine Corps has reviewed 

the subject PDC and concurs with the 

concept of SLOA and with PDC 1043, 

however any required modifications to 

GCSS-MC, TMS, and SABRS to support 

SLOA are unfunded. 

Noted. 

69 2. Per Reference (a), the following are 

responses to PDC staffing notes. 

a. No requirement for exchanging cost 

objects between buyers and sellers in DLMS 

transactions has been identified. [Attachment 

to reference (a) page 7] 

Noted. 

70 b. No legacy requirement to retain budget 

and accounting classification code FA2O1 

has been identified (Attachment page 8) . 

There is no conflict with the adjustment of 

FA2O1 code Li to SLOA [Enclosure 3 to 

reference (a) page 5] 

Noted. 

71 c. No reason has been identified to preclude 

using either the business event type code or 

the sub class for DLMS logistics transactions 

[Enclosure 2 to reference (a) page 1] 

Noted 
Attachment, ADC 1043 

Enclosure 7, page 21 

# Component/ 

Agency 

Response/Comment Disposition 

72 USMC 

(cont.) 

d. No requirement for reimbursable flag has 

been identified for interfund billing 

[Enclosure 2 to reference (a) page 11] 

Noted. Clarification regarding 

reimbursable flag was provided by 

OUSD(C)/ODCMO. We will carry in 

DLMS and consider it as a possible 

addition to the SFIS Fund Code Table. 

73 e. No requirement for a Foreign Military 

Sales Material Returns Program has been 

identified therefore security coorperation 

related SLOA/Accounting Classification 

elements is not required [Enclosure 3 to 

reference (a) page 3] 

Noted. 

74 f. No adverse impact to moving the Fund 

Code mapping to the FA2 segment has been 

identified [Enclosure 3 to reference (a) page 

31] 

Noted. 

75 g. No requirement for “Project/Task” has 

been identified for disposal release orders 

[Enclosure 3 to reference (a) page 75] 

Noted. 

76 h. No requirement for “Work Order 

Number” has been identified for disposal 

release orders [Enclosure 3 to reference (a) 

page 76] 

Noted. Work Order Number and Job 

Order Number are retained in the REF/N9. 

Work Order Number will be included in 

FA201 (or REF01) for consistency across 

DLMS transactions and optional use, and 

DAAS will not map between the data 

elements. 

77 USN Concur. 

Note generalized concern about the size of 

this change and large amount of work that 

will be required to implement all the needed 

SLOA DLMS enhancements. Since this 

PDC describes a staggered implementation, 

Navy believes they can work through the 

challenges with the implementation timeline. 

Is there any sense that a timeline will be 

imposed to complete the DLMS 

enhancements at some point in the future? Is 

the current timeline that ALL DLMS 

enhancements must be complete is Sept 

2014? 

The OUSD(C)/ODCMO SLOA memo 

establishes a target SLOA implementation 

by the end of FY 2014. Per OSD(AT&L) 

functional strategy, DLMS compliance is 

required by 2019. 
Attachment, ADC 1043 

Enclosure 7, page 22 

# Component/ 

Agency 

Response/Comment Disposition 

78 USTRANSCOM USTRANSCOM 'approves' the attached 

PDC. USTRANSCOM is working to develop 

its own implementation plan to support 

SLOA reporting requirements. That being 

said, the mapping requirements for EDI 

transaction sets can be supported in the 

DTEB ICs as dictated by OSD(C) should 

USTRANSCOM identify a need for their 

modification. 

Noted. 

79 DLA Logistics 

Mgmt. Stds. 

Office 

The 810L Logistics Bill is unique in that it 

includes FA1/FA2 segments in both header 

(Table 1) conveying summary bill 

information and the detail (Table 2) 

conveying supporting detail bills. The 

summary and detail bills are linked by a 

common billing number. To be fully 

compliant, we believe that 810L Logistics 

Bill should include applicable SLOA data for 

the billing office in the FA2 of the 810L 

header (Table 1). Billed office SLOA data is 

provided in the detail (Table 2). 

Discussed at the FPRC/SPRC on June 

20,2013. Modify 810L to add billing office 

SLOA data in the header. 

80 Web Fund Code Application Current 

Status. DLA Transaction Services is 

completing application development and 

will submit the application to the DLA 

Internet Council for approval. In the 

event that the DLA Internet Council does 

not complete review and approval prior 

to September 30, 2013 for the start of 

Fiscal Year 2014, the database will still 

be available and DLA Transaction 

Services will be able to accept and make 

fund code changes pending application 

approval. 

Provided as information to address staffing 

note. 

81 PDC 1043 proposed FA201 code N1, 

Transaction Type, to identify the SLOA 

requirement for Business Event Type 

Code (BETC). During staffing 

USTRANSCOM noted they are using 

code N1 for a purpose not related to 

BETC. For interoperability, DLA 

Logistics Management Standards Office 

recommends creating a new FA201 code 

for BETC as no other existing code is 

appropriate. 

For all mappings of Enclosure 3 above, 

code N1 of FA201 has been replaced by a 

new code BE, Business Event Type Code. 

This new code will be noted as a local code 

until it can be included in the X12 

standard, at which point code BE will be a 

migration code in the DLMS 

implementation conventions. 
Attachment, ADC 1043 

Enclosure 7, page 23 

# Component/ 

Agency 

Response/Comment Disposition 

82 DLA Distribution 

Services 

Upon initial evaluation of this PDC, there 

will be extensive changes needed to 

include financial data within DSS. 

Historically DSS is classified as a 

financial feeder system, responsible for 

feeding Warehouse management System 

type transactions to the materiel 

management system which serves as the 

financial system for the ICP's. 

Today the DSS system records quantities 

of materiel and reports those quantities to 

the materiel management system and in 

no way conveys financial data for assets 

received, stored or shipped. DSS does 

pass fund code today, and based on the 

requirements of PDC 1043, DSS will 

continue to pass fund code with 

numerous additional data elements for 

the DLMS 511R, 940R, 842A and 867I. 

Possibly at a later date the DLMS 945A 

and 856S will also carry these elements. 

To support PDC 1043, a Post-Post 

processing addendum should consider 

the designation of DSS as a financial 

feeder system, and seek other avenues 

(EMALL, etc.) to accommodate the postpost process and not jeopardize the 

designation of DSS being a financial 

feeder. If financial data is required to be 

entered in the Post-Post process, and a 

financial validation (FV1/FV2) 

transaction must be sent and received 

prior to release of materiel, this process 

will put the designation of the DSS 

system at a high risk of being redesignated which will greatly increase 

the auditability and compliance 

applicability and staffing to meet the new 

requirements of a different designation. 

Noted.