How To Fix FI_E036 - Revenue/Statistical and OI/Actual resource account missing 0/&1/&2/&3/&4

FI_E036 - Overview

• Message type: E = Error

• Message class: FI_E - Message Class for FM English Developers

• Message number: 036

• Message text: Revenue/Statistical and OI/Actual resource account missing 0/&1/&2/&3/&4

What causes this issue?

You are using the funds management system integrated with the budgetary
ledger (BL) for FM area &V1&. Postings in the budgetary ledger require
an FI-GL account for one of the lines in the BL interface table which
correspond to each of the lines in the document created. However, no
account for this key has been defined yet for the budgetary ledger area
in the account derivation process.
Since you are using the budgetary ledger with account derivation for the
US federal government, you need to customize an entry for this key in
the revenue/statistical postings and open items/actuals budget resources
posting section.
According to the United States federal government model, a proprietary
ledger account is optional but the budgetary ledger entry is always
required. This means that, for every line in the BL interface table, at
least one line will exist for the budgetary ledger. At your option,
there can be more than one budgetary and proprietary ledger line.
The entry for the revenue/statistical postings and open items/actuals
budget resources account missing in US federal government customizing is
for ledger area '0' (Budgetary ledger), FM area '&V1&', company code '
&V2&', fiscal year/posting period '&V3&', fund type, value type,
business transaction, amount type, fund status, BL document type,
carryforward value, and trading partner '&V4&'.
You must create the customizing entries with "from year"/"from period"
values earlier than or equal to '&V3&' derived from the posting date. No
generic values are allowed for year/period.
For the revenue/statistical postings and open items/actuals budget
resources customizing, generic "*" entries are permitted for the fund
type, value type, business transaction, amount type, document type, and
partner ID fields. The priority for the generic entries goes from left
to right, the highest one being the fund type. You cannot have generic
entries for value type and document type in the same line, since this
causes problems with reconciliation.
The US federal government account derivation consists of the following
sections:
Former Budgeting
Budget Control System (BCS)
Revenue/statistical postings and open items/actuals budget resources
Open items/actuals accounts for budget status
In this particular case, the account customizing entry must be created
in the second section.

How to fix this error?

Use transaction OFBL to maintain the revenue/statistical postings and/or
open items/actuals budget resources account derivation for the budgetary
ledger. You can access the transaction using the link below.
This entry has to be created in the third option (revenue/statistical
and OI/actuals) of the dialog structure in the customizing view.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

<DS:TRAN.OFBL>Execute US federal government BL account derivation</>
ENDIF

Error message extract from SAP system. Copyright SAP SE.

FI_E036 - Details

• The SAP error message FI_E036 indicates that there is a missing resource account for a specific combination of parameters in the context of revenue/statistical and operating income (OI)/actual postings. This error typically arises in the Financial Accounting (FI) module when the system cannot find the appropriate account for a given transaction.
  
  Cause:
  
  Missing Configuration: The most common cause of this error is that the required resource account has not been configured in the system. This could be due to missing entries in the relevant configuration tables.
  Incorrect Account Assignment: The account assignment for the transaction may not be set up correctly, leading to the system being unable to find the necessary account.
  Data Inconsistencies: There may be inconsistencies in the master data or transaction data that prevent the system from identifying the correct account.
  Missing Master Data: The relevant master data (like cost centers, internal orders, etc.) may not be set up properly or may