DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

October 01, 2014 

MEMORANDUM FOR SUPPLY AND FINANCE PROCESSS REVIEW COMMITTEES 

(PRCs) 

SUBJECT: Approved Addendum to Approved Defense Logistics Management Standards 

(DLMS) Change (ADC) 1043B, Revised Procedures for Department of Defense 

(DOD) Standard Line of Accounting (SLOA)/Accounting Classification to 

Modify Business Rules for Beginning Period of Availability Fiscal Year Date 

(Finance/Supply/SDR) 

The attached addendum change to DLM 4000.25, Defense Logistics Management 

System, is approved for staggered implementation. 

Addressees may direct questions to Mr. Robert Hammond, Chair, Finance PRC, email 

financehq@dla.mil; Ms. Ellen Hilert, Co-Chair, Supply PRC, email: ellen.hilert@dla.mil or; Ms. 

Heidi Daverede, DOD MILSTRIP Alternate, 703-767-5111 ; DSN 427-5111, e-mail: 

heidi.daverede@dla.mil. Others must contact their Component/ Agency designated 

representative shown at www.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp (DOD 

Common Access Card restricted). 

Attachment 

As stated 

cc: 

ODASD (SCI) 

ODASD DPAP (PDI) 

OUSD(C) 

ODCMO 

"" 

ON1]t0~ irector 

- Defense Logistics Management 

Standards Office 
Attachment to Approved Addendum to ADC 1043B, 

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

Accounting (SLOA)/Accounting Classification to Modify Business Rules for 

Beginning Period of Availability Fiscal Year Date

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC Per Reference 3.a.:

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

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

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

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

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

2. FUNCTIONAL AREAS: Finance and Supply

3. REFERENCES:

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

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

September 18, 2013

b. ADC 1043A, Revised Procedures for Department of Defense (DOD) Standard Line of 

Accounting (SLOA)/Accounting Classification to Support Transaction Rejection Requirements, 

dated August 20, 2014

c. Web Fund Code File Layout. (Included as Enclosure 1)

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

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

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

Enclosure 1 of Reference 3.a.)

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

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

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

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

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

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

Attachment, ADC 1043B

Page 1
4. REQUESTED CHANGE(S):

a. Brief Overview: This change amends ADC 1043 (Reference 3.a.) to revise the 

business rules within the DLMS and the Web Fund Code Application to allow the SLOA data 

element, Beginning Period of Availability Fiscal Year Date, to be used in DLMS transactions to 

represent Program Year when the Availability Type Code is X, which indicates No Year, nonexpiring funds.

b. Background:

(1) The Web Fund Code Application that Component Fund Code Monitors use to 

manage their Components’ fund codes incorporated Business Enterprise Architecture (BEA) 

10.0 business rules for the SLOA data elements identified in reference 3.d.. Web Fund Code 

business rules are reflected in the Web Fund Code Master File Layout.

(2) Subsequent to staffing of ADC 1043, DLMSO learned of an internal conflict 

within the BEA regarding dual use of the field for Beginning Period of Availability (SFIS 

reference A27) and Program Year (SFIS reference A30). Program Year is not a SLOA data 

element listed in reference 3.d.

(3) The conflict between SFIS data element business rules in the BEA is as 

follows:

BEGINNING PERIOD OF AVAILABILITY 

• SFIS BR# 720604: If used for no-year funding, Beginning Period of Availability must be 

blank.

PROGRAM YEAR

• SFIS BR# 1005185: Program Year is only applicable to no-year funds which require fiscal 

accountability.

• SFIS BR# 1005187: When applicable, the Program Year must be exchanged in the 

Beginning Period of Availability Field.

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

(1) There is no capability or requirement to exchange Program Year in DLMS 

transactions as a discrete data field.

(2) The Web Fund Code Application was placed into production for Fund Code 

Monitor use on August 4, 2014. Fund Codes loaded into the Web Fund Code database prior to 

that date do not contain a Program Year in the Beginning Period of Availability Fiscal Year Date 

field.

(3) Web Fund Code Application internal data edits are based on the BEA 10.0 

business rules without consideration of Program Year, such that Beginning Period of Availability 

Fiscal Year Date is not allowed in conjunction with Availability Type Code X.

Attachment, ADC 1043B

Page 2
(4) Treasury does not require Program Year for reporting. ODCMO reports 

Defense Finance and Accounting Service (DFAS) Central Accounts Office financial reporting 

systems are programmed to strip Program Year from the Beginning Period of Availability Fiscal 

Year Date field prior to Treasury reporting. A staffing note asked Components to confirm with 

their DFAS Central Account Offices that the Program Year is stripped from the Beginning 

Period of Availability Fiscal Year Date field prior to reporting to the Department of Treasury,

but no responses were received.

(5) DAAS edits (prescribed by ADC 1043) for comparing the beginning period 

of availability and ending period of availability values in the transaction to corresponding values 

on the SFIS Fund Code to Fund Account Conversion Table will not result in rejection when 

either of these fields contain a value in the transaction but the corresponding field in the SFIS 

Fund Code to Fund Account Conversion Table is null (blank).

(6) Program Year is distinguishable in the Beginning Period of Availability 

Fiscal Year Date field by the presence of Availability Type Code X included in the SLOA and 

absence of Ending Period of Availability Fiscal Year Date in the SLOA.

(7) BEA Business Rules for Program Year are as shown in the table below.

SFIS Element Description

PROGRAM YEAR

BEA Definition: The Program Year is required for appropriations that never expire, yet 

require fiscal year accountability because of the language in the Appropriation Act.

Example(s):

FY2012 - 2012

FY2013 - 2013

Values: Values are updated yearly. 

Legacy Equivalent Terminology: None.

Syntax: Four numeric

Business Rules:

• Program Year is only applicable to no-year funds which require fiscal accountability.

• Program Year must be 4 numeric characters. ex. 2013

• Program Year must be used be stored and maintained.

• Program Year must be used for accounting classification.

• Program Year must be used for financial reporting.

• Program Year must be used for funds control.

• When applicable, the Program Year must be exchanged in the Beginning Period of 

Availability Field.

d. Approved Change in Detail: 

(1) Office of the Deputy Chief Management Officer and Office of the Under 

Secretary of Defense (Comptroller) revise the BEA business rules for Beginning Period of 

Availability to read: “If used for no-year funding, Beginning Period of Availability 

must be blank, except when used to exchange Program Year.

Attachment, ADC 1043B

Page 3
(2) DLMSO revise the Web Fund Code Master File Layout and add the Web 

Fund Code Master File Layout to MILSBILLS as Appendix 4, as shown in Enclosure 1.

(3) DLA Transaction Services disable the Web Fund Code edits as indicated in 

Enclosure 1 to allow the Program Year to be exchanged in the Beginning Period of Availability

Fiscal Year Date field.

(4) Component Fund Code Monitors update fund code data to reflect a Program 

Year as applicable and as you have sufficient fund codes to do so.

(5) Components implementing DLMS must incorporate logic to store beginning 

period of availability in their internal system as Program Year when Availability Type Code is 

equal to X indicating no-year funds.

(6) Revise DLMS notes in applicable transactions for Beginning Period of 

Availability Fiscal Year Date to reflect that Program Year may be exchanged in that field, when 

applicable, as shown in Enclosure 2.

e. Alternatives: The DLMSO preferred method is generally not to direct dual use of a 

data field, but rather to carry each data element as a discrete data field with its own ANSI X12 

qualifier. This alternative of exchanging Program Year as a discrete data element in DLMS and 

adding it to the Web Fund Code Table was discussed, but is not being pursued in this case, 

because the BEA convention for Program Year has already been implemented by other 

functional domains.

5. REASON FOR CHANGE: This change is needed to prescribe DLMS business rules for 

entering the Program Year in data elements for “Beginning Period of Availability Fiscal Year 

Date” and to enable Program Year to be entered into the Web Fund Code Application in the 

Beginning Period of Availability Fiscal Year Date field.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Enables Program Year to be exchanged in logistics transactions.

b. Disadvantages: None identified.

4. ADDITIONAL COMMENTS TO CONSIDER: Fund Code Monitors should consider the 

availability of sufficient fund codes before adding Program Year in the Beginning Period of 

Availability Fiscal Year Date in the SFIS Fund Code to Fund Account Conversion Table. There 

is a risk of running out of fund codes in the future. The risk of not adding Program Year is that it 

will not be visible/available for systems/processes relying on 80 record position transactions that 

have not yet migrated to DLMS variable length transactions.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: This change will be 

effective upon issuance of the Approved DLMS Change.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified.

Attachment, ADC 1043B

Page 4
9. IMPACT:

a. DLMS Data Elements/LOGDRMS: Add Program Year as a new DLMS data 

element for SLOA as defined in 4.c.(6) above.

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

Agency AIS is required to support the logic to translate Program Year as appropriate in DLMS 

transactions.

c. DLA Transaction Services: Modify the edit in the Web Fund Code application for 

Beginning Period of Availability Fiscal Year Date, allowing it to be populated when Availability 

Type Code is “X”.

10. Proposed DLMS Change (PDC) 1147 Response Table:

Component Response Resolution

1. DPAP Concur

It's a logical approach, and 

mirrors what many of the legacy 

data formats did

Noted.

2. DLA Finance Does DoD have any multi-year 

funds requiring program year 

tracking - MILCON maybe? I 

don't know, but if so, this 

solution doesn't work, never 

mind that it really inappropriate 

from a data architecture 

perspective. It also 

complicates/slows interfaces 

further because they will have to 

be able to determine which 

records the value is correct for 

the attribute and which it needs 

to ignore and assign to the 

proper attribute. Is this being 

viewed as a short term solution?

Noted.

DOD does have some of these 

program year situations. USMC 

brought this to our attention. As 

noted in the alternatives section,

DLMSO normal approach would 

be to have a separate data 

element for program year. But, 

the convention is already in the 

BEA and it has been 

implemented in other systems. 

If the transaction comes in that 

way with BEG POA populated 

and Availability Type Code = X, 

you will have to have some 

program logic to store the value 

in separately in your system. If 

Program Year is in the incoming 

DLMS variable length 

transaction, you will perpetuate 

it down stream in your outgoing 

transactions. Note this is only 

applicable to DLM variable 

Attachment, ADC 1043B

Page 5
Component Response Resolution

length transactions. The fund 

code table will contain Program 

Year in BEG POA, when 

populated by the fund code 

monitors.

3. DFAS-IN Concur Noted.

4. USASAC Concur Noted.

Attachment, ADC 1043B

Page 6
ENCLOSURE 1

Web Fund Code Layout

The following is a new Appendix 4 for DoD 4000.25, Volume 4. Note change to the current 

business rules implemented in the Web Fund Code application for the Beginning Period of 

Availability Fiscal Year Date data field to accommodate it being used for Program Year when 

Availability Type Code is X.

AP4. APPENDIX 4

Web Fund Code Master File Layout

AP4.1. Layout for SFIS Fund Code to Fund Account Conversion Table. The Type 

column identifies the data type and, when applicable, the maximum number of 

characters in parentheses. For the Use column: M = Mandatory, O = Optional, and C = 

Conditional.

Field Name Type Use Definition Business Rule

Service_Code varchar2

(2)

M Service and Agency 

Code. Designates the 

military service or other 

government element of 

ownership or sponsorship. 

The code is used to 

identify the service or 

agency monitoring the 

fund code.

• Per MILSTRIP business rules 

under DLMS Volume 2, Appendix 

7.2, the service and agency (S/A) 

code is a one or two character 

alphanumeric.

Signal_Code varchar2

(1)

M Signal Code. A code 

designation identifying the 

intended consignee and 

activity to receive and 

effect bill payment.

• Allowed values are A, B, C, J, K 

and L

Refer to MILSTRIP business rules 

under DLMS Volume 2, Appendix

7.10 for an explanation of signal 

code.

Fund_Code varchar2

(2)

M Fund Code. Designation 

of the fund account to be 

charged (disbursed) or 

credited (refunded). When 

used with Signal Code C 

or L also designates the

Billed Office DoDAAC.

• Must be unique per 

Service_Code and Signal_Code.

• A fund code of ** is an indicator 

of the default account. One per 

S/A + Signal code.

• When used with Signal Code C 

or L an entry is required on the 

Fund Code to Billed Office 

DoDAAC Table. 

Enclosure 1, ADC 1043B

Page 1
Field Name Type Use Definition Business Rule

Appropriation varchar2

(11)

C Appropriation/Fund 

Account. Constructed line 

of accounting

• Must use unless Noninterfund

billing.

• This field is constructed from: 

Last 2 characters of 

Department_Regular_Code + 

Fiscal_Year_Indicator + 

Main_Account_Code + 

Appropriation_Limit_Subhead. 

(NOTE that

Deptartment_Regular_Code is

actually 3 characters, but the 

leading zero is deleted for 

purposes of this element.)

• Blank appropriation data displays 

as Noninterfund on reports

Agency_Narr varchar2

(20)

O Agency Narrative. Name 

or common acronym for 

further agency delineation 

from the Service code. 

Generally, a breakdown 

for H-series fund code 

assignments.

• Web Application input is limited 

to 5 characters. This is to conform 

to report format limitations.

Department_

Regular_

Code

varchar2

(3)

C Department Regular 

Code. U.S. Treasury 

designated code 

representing the 

government agency 

accountable for one or 

more fund accounts 

established and 

maintained by the 

Treasury.

• Must use unless Noninterfund

billing.

• Department Regular Code must 

be 3 numeric characters. ex. 097 

(NOTE: This element used to be 2 

characters. Current codes are 

going to be pre-fixed by a zero.)

• If any of 

Department_Regular_Code, 

Main_Account_Code and/or 

Sub_Account_Code are present 

than the others are required.

• Blank field indicates 

Noninterfund.

Enclosure 1, ADC 1043B

Page 2
Field Name Type Use Definition Business Rule

Department_

Transfer_

Code

varchar2

(3)

O Department Transfer 

Code. Identifies the 

federal agency of 

obligation authority to the 

DoD or one of its 

components

• 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).

• May be blank if no department 

transfer is applicable

Main_Account

_Code

varchar2

(4)

C Main Account. 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.

• Must use unless Noninterfund

billing.

• Blank field indicates 

Noninterfund.

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

• If any of 

Department_Regular_Code, 

Main_Account_Code and/or 

Sub_Account_Code are present 

than the others are required.

Enclosure 1, ADC 1043B

Page 3
Field Name Type Use Definition Business Rule

Sub_Account

_Code

varchar2

(3)

C Sub-account Code. 

Specify subsidiary level 

accounts associated to the 

main account of the TAFS.

• Must use unless Noninterfund

billing.

• Blank field indicates 

Noninterfund.

• Unless Noninterfund, 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)

• If any of 

Department_Regular_Code, 

Main_Account_Code and/or 

Sub_Account_Code are present 

than the others are required.

Treasury_Sub

_Class

varchar2

(2)

O Treasury Sub Class 

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

• May be blank. Business Rules 

need to be developed.

• Business Event Type Code 

(BETC) in effect replaces the 

transaction codes and standard 

sub-classes that were used on the 

old central accounting reports, 

such as the Statements of 

Transactions (FMS Form 224) and 

the Undisbursed Ledger and Trial 

Balance Reports (FMS Forms 

6653 and 6654). As a result, the 

subclass field is being renamed to 

“Sub-level Prefix” and will only be 

used for programmatic 

breakdowns of the TAS for 

Treasury publication purposes. 

Sub-level Prefixes have a unique 

meaning or a unique need for sub 

classification that is NOT based on 

transaction types or business 

events as described previously.

Enclosure 1, ADC 1043B

Page 4
Field Name Type Use Definition Business Rule

Appropriation

_Limit_

Subhead

varchar2

(4)

O Limit/Subhead. Legacy 

identifier of an 

organization to which 

funds have been suballocated.

• May be blank. 

Fiscal_Year_

Indicator

varchar2

(1)

C Fiscal Year Indicator. 

Denotes fiscal year 

chargeable

• Must use unless Noninterfund

billing.

• Values: 

• {numeric}, or

• X = no year funding, or;

• # = Beg_Fiscal_Year_ Avail

and End_Fiscal_

Year_Avail determined by 

FY of transaction document 

number, or;

• * = Beg_Fiscal_Year_ Avail

and End_Fiscal_

Year_Avail determined by 

FY of the Summary billing 

transaction or;

• Blank field indicates 

Noninterfund.

• If Fiscal Year Indicator is X 

Availability_Type_Code will also 

be X.

Legacy_Multi_

Yr_Fund_Cde

_Ind

varchar2

(1)

C Legacy Multi Year Fund 

Code Indicator. Used to 

indicate that funding is 

associated with a multiyear appropriation for 

which the 

Beg_Fiscal_Year_Avail

and 

End_Fiscal_Year_Avail

are blank due to 

overlapping periods of 

multiple periods of 

availability associated with 

the fund code. 

• Must use unless Noninterfund

billing.

• Default to false. 

• If true, accounting systems 

cannot accurately derive the 

beginning and ending periods of 

availability for this fund code solely 

from the fund code. 

• Would be used in conjunction 

with Fiscal_Year_ Indicator = # or 

*.

Enclosure 1, ADC 1043B

Page 5
Field Name Type Use Definition Business Rule

Availability_

Type_Code

varchar2

(1)

C Availability Type Code. 

Identifies no-year TAS, 

clearing/suspense TAS, 

and canceled TAS.

• Availability Type Code must be 1 

alpha character.

• Valid values include: C and X.

• If used for canceled Main 

Accounts, Availability Type Code 

C may be derived at the time of 

reporting.

• For Annual or Multi-Year funding, 

Availability Type Code must be 

blank. 

• If Availability Type Code is X, 

Fiscal_Year_Indicator will also be 

X

Beg_Fiscal_

Year_Avail

varchar2

(4)

C Beginning Period of 

Availability Fiscal Year 

Date. In annual and multiyear accounts, identifies 

the first year of availability 

under law that an account 

may incur new obligations. 

May also be used to 

represent Program Year, 

when applicable.

• If Availability_Type_Code is X, 

then Beginning Period of 

Availability must be must be blank.

• If the Beginning Period of 

Availability is associated with an 

unavailable receipt account, then it 

must be blank.

• If Fiscal_Year_Indicator is either 

# or * then Beginning Period of 

Availability must be blank

End_Fiscal_

Year_Avail

varchar2

(4)

C Ending Period of 

Availability Fiscal Year 

Date. In annual and multiyear accounts, identifies 

the last year of availability 

under law that an account 

may incur new obligations.

• Must use unless Noninterfund

billing.

• If Availability_Type_Code is X, 

then Ending Period of Availability 

must be blank.

• If the Ending Period of 

Availability is associated with an 

unavailable receipt account, then it 

must be blank.

• If Fiscal_Year_Indicator is either 

# or * then Ending Period of 

Availability must be blank

Effective_

Date

date M Effective Date. The start 

date for the latest action 

taken on a record.

• The record is not valid until the 

effective date.

Action_Code varchar2

(1)

M Action Code. System 

maintained code indicating 

type of action last taken 

on a record.

• Values: A, C, D (Add, Change, 

Delete)

Create_Date date M Creation Date. System 

maintained date a record 

was created.

Enclosure 1, ADC 1043B

Page 6
Field Name Type Use Definition Business Rule

Last_Update date M Last Update Date. 

System maintained date a 

record was last updated.

Customer_

Userid

varchar2

(20)

M Customer User 

Identifier. System 

maintained identifier of a 

system user who updated 

the record.

AP4.2. Layout for Fund Code to Billed Office DoDAAC Table (Applicable to Signal 

Codes C or L). The Type column identifies the data type and, when applicable, the 

maximum number of characters in parentheses. For the Use column, M = Mandatory

Field Name Type Use Definition Business Rule

Service_Code varchar2

(2)

M Service and Agency 

Code. Designates the 

military service or other 

government element of 

ownership or sponsorship. 

The code is used to 

identify the service or 

agency monitoring the 

fund code.

• Per DLMS Volume 2, Appendix 

7.2, the service and agency (S/A) 

code is a one or two character 

alphanumeric.

Fund_Code varchar2

(2)

M Fund Code. Designation 

of the fund account to be 

charged (disbursed) or 

credited (refunded). When 

used with Signal Code C 

or L also designates the 

Billed Office DoDAAC.

• Must be unique per 

Service_Code and Signal_Code.

• A fund code of ** is an indicator 

of the default account. One per 

S/A + Signal code.

• When used with Signal Code C 

or L an entry is required on the 

Fund Code to Billed DoDAAC 

Table. If there is no corresponding 

entry on the SFIS Fund Code to 

Fund Account Conversion Table, 

billing is via Noninterfund

DODAAC varchar2

(6)

M Department of Defense 

Activity Address Code 

(DoDAAC). A is a six 

position code that uniquely 

identifies a unit, activity, or 

organization. See DLM 

4000.25, Volume 6, 

Chapter 2

• Used to denote the Billed Office. 

Enclosure 1, ADC 1043B

Page 7
Field Name Type Use Definition Business Rule

Effective_Date date M Effective Date. The start 

date for the latest action 

taken on a record.

• The record is not valid until the 

effective date.

Action_Code varchar2

(1)

M Action Code. System 

maintained code indicating 

type of action last taken 

on a record.

• Values: A, C, D (Add, Change, 

Delete)

Create_Date date M Creation Date. System 

maintained date a record 

was created.

Last_Update date M Last Update Date. 

System maintained date a 

record was last updated.

Customer_

Userid

varchar2

(20)

M Customer User 

Identifier. System 

maintained identifier of a 

system user who updated 

the record.

Enclosure 1, ADC 1043B

Page 8
ENCLOSURE 2

DLMS IC Updates

# Location 180M Material Returns Reporting Reason

1. DLMS 

Introductory 

Notes

Add ADC 1043B

- ADC 1043B, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Modify 

Business Rules for Beginning Period of Availability

Identifies DLMS Changes 

included in the DLMS IC

2. 2/FA201/226 Insert new DLMS note for the existing qualifier YB:

YB Beginning Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to 

ADC 1043B.

3. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

4. Qualifier YB is a migration code approved for use 

in X12 version 7020.

Explains the use of the 

Beginning Period of 

Availability Fiscal Year 

Date field for carrying 

Program Year.

Enclosure 2, ADC 1043B

Page 1
# Location 511M Requisition Modifier Reason

1. DLMS 

Introductory 

Notes

Add ADC 1043B

- ADC 1043B, Revised Procedures for Department of 

Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Modify Business 

Rules for Beginning Period of Availability

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/286 Insert new DLMS note for the existing qualifier YB:

YB Beginning Period of Availability

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. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to ADC 

1043B.

3. Authorized DLMS enhancement; see introductory 

DLMS note 3g.

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

X12 version 7020.

Explains the use of the 

Beginning Period of 

Availability Fiscal Year 

Date field for carrying 

Program Year.

# Location 511R Requisition Reason

1. DLMS 

Introductory 

Notes

Add ADC 1043B

- ADC 1043B, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Modify Business 

Rules for Beginning Period of Availability

Identifies DLMS 

Changes included in 

the DLMS Supplement

2. 2/FA201/286 Insert new DLMS note for the existing qualifier YB:

YB Beginning Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to 

ADC 1043B.

3. Authorized DLMS enhancement; see introductory 

DLMS note 3f.

4. Qualifier YB is a migration code approved for use 

in X12 version 7020.

Explains the use of the 

Beginning Period of 

Availability Fiscal 

Year Date field for 

carrying Program 

Year.

Enclosure 2, ADC 1043B

Page 2
# Location 517M Material Obligation Validation Reason

1. DLMS 

Introductory 

Notes

Add ADC 1043

- ADC 1043B, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Modify Business 

Rules for Beginning Period of Availability

Identifies DLMS 

Changes included in 

the DLMS Supplement

2. 2/FA201/136 Insert new DLMS note for the existing qualifier YB:

YB Beginning Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to ADC 

1043B.

3. Authorized DLMS enhancement; see introductory 

DLMS note 3f.

4. Qualifier YB is a migration code approved for use 

in X12 version 7020.

Explains the use of the 

Beginning Period of 

Availability Fiscal 

Year Date field for 

carrying Program 

Year.

# Location 810L Logistics Bill Reason

1. DLMS 

Introductory 

Notes

Add ADC 1043B

- ADC 1043B, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Modify Business 

Rules for Beginning Period of Availability

Identifies DLMS 

Changes included in 

the DLMS Supplement

2. 1/FA201/300 Insert new DLMS note for the existing qualifier YB:

YB Beginning Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043.

2. Used in association with the billing office line of 

accounting (Qualifier 58).

3. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to 

ADC 1043B.

4. Authorized DLMS enhancement; see introductory

DLMS note 6e.

5. Qualifier YB is a migration code approved for use 

in X12 version 7020.

Explains the use of the 

Beginning Period of 

Availability Fiscal 

Year Date field for 

carrying Program 

Year.

Enclosure 2, ADC 1043B

Page 3
# Location 810L Logistics Bill Reason

3. 2/FA201/360 Insert new DLMS note for the existing qualifier YB:

YB Beginning Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to ADC 

1043B.

3. Authorized DLMS enhancement; see introductory 

DLMS note 6e.

4. Qualifier YB is a migration code approved for use 

in X12 version 7020.

Explains the use of the 

Beginning Period of 

Availability Fiscal 

Year Date field for 

carrying Program 

Year.

# Location 842 A/W Supply Discrepancy Report Reason

1. DLMS 

Introductory 

Notes

Add ADC 1043

- ADC 1043B, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Modify 

Business Rules for Beginning Period of Availability

Identifies DLMS 

Changes included in 

the DLMS Supplement

2. 2/FA201/1360 Insert new DLMS note for the existing qualifier YB:

YB Beginning Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to 

ADC 1043B.

3. Authorized DLMS enhancement; see introductory 

DLMS note 5.

4. Qualifier YB is a migration code approved for use 

in X12 version 7020.

Explains the use of the 

Beginning Period of 

Availability Fiscal 

Year Date field for 

carrying Program 

Year.

Enclosure 2, ADC 1043B

Page 4
# Location 856S Ship Notice/Manifest Reason

1. DLMS 

Introductory 

Notes

Add ADC 1043

- ADC 1043B, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Modify Business 

Rules for Beginning Period of Availability

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/DTM01/2000 Insert new DLMS note for the existing qualifier 283:

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. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to 

ADC 1043B.

3. Authorized DLMS enhancement; see introductory 

DLMS note 2f.

Explains the use of the 

Beginning Period of 

Availability Fiscal Year 

Date field for carrying 

Program Year.

# Location 867I Issue Reason

1. DLMS 

Introductory 

Notes

Add ADC 1043B

- ADC 1043B, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Modify Business 

Rules for Beginning Period of Availability

Identifies DLMS 

Changes included in 

the DLMS Supplement

2. 2/FA201/350 Insert new DLMS note for the existing qualifier YB:

YB Beginning Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to 

ADC 1043B.

3. Authorized DLMS enhancement; see introductory 

DLMS note 5e.

4. Qualifier YB is a migration code approved for use 

in X12 version 7020.

Explains the use of the 

Beginning Period of 

Availability Fiscal 

Year Date field for 

carrying Program 

Year.

Enclosure 2, ADC 1043B

Page 5
# Location 869F Requisition Follow-Up Reason

1. DLMS 

Introductory 

Notes

Add ADC 1043B

- ADC 1043B, Revised Procedures for Department 

of Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Modify Business 

Rules for Beginning Period of Availability

Identifies DLMS 

Changes included in 

the DLMS Supplement

2. 2/FA201/200 Insert new DLMS note for the existing qualifier YB:

YB Beginning Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to 

ADC 1043B.

3. Authorized DLMS enhancement; see introductory 

DLMS note 4g.

4. Qualifier YB is a migration code approved for use 

in X12 version 7020.

Explains the use of the 

Beginning Period of 

Availability Fiscal 

Year Date field for 

carrying Program 

Year.

# Location 940R Material Release Reason

1. DLMS 

Introductory 

Notes

Add ADC 1043B

- ADC 1043B, Revised Procedures for Department of 

Defense (DOD) Standard Line of Accounting 

(SLOA)/Accounting Classification to Modify Business 

Rules for Beginning Period of Availability

Identifies DLMS 

Changes included in the 

DLMS Supplement

2. 2/FA201/3000 Insert new DLMS note for the existing qualifier YB:

YB Beginning Period of Availability

DLMS Note:

1. For DoD SLOA/Accounting Classification use to 

identify “Beginning Period of Availability Fiscal 

Year Date”. Refer to ADC 1043.

2. Use as appropriate to represent Program Year. 

Availability Type Code must be “X”. Refer to ADC 

1043B.

3. Authorized DLMS enhancement; see introductory 

DLMS note 4f.

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

X12 version 7020.

Explains the use of the 

Beginning Period of 

Availability Fiscal Year 

Date field for carrying 

Program Year.

Enclosure 2, ADC 1043B

Page 6