How To Fix FTI_LDB_MESSAGE090 - &1 in company code &2, valuation area &3 is only initialised for &4

SAP Error Message - Details

• Message type: E = Error

• Message class: FTI_LDB_MESSAGE - Messages for TR OLTP Reporting Using Logical Databases

• Message number: 090

• Message text: &1 in company code &2, valuation area &3 is only initialised for &4

Trados = TR

What causes this issue?

The information system for the Transaction Manager can only deliver
information for this selection after the initialization key date.

System Response

In the case of reporting for a specific period, if the selection period
is before the initialization key date of a product group in one company
code and valuation area, then this period is not evaluated. If the
initialization key date is within the selection period, this date is
then taken as the start of the evaluation.
In the case of reporting for a specific date, if the key date is before
the initialization key date of a product group in one company code and
valuation area, then it is not evaluated.

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FTI_LDB_MESSAGE090 - &1 in company code &2, valuation area &3 is only initialised for &4 ?

  The SAP error message FTI_LDB_MESSAGE090 typically indicates an issue related to the initialization of a valuation area in the context of Financial Accounting (FI) or Controlling (CO) modules. This error message suggests that the valuation area specified in the message is not fully initialized, which can lead to problems when trying to perform certain transactions or processes.
  Cause:
  
  Initialization Not Completed: The valuation area (which could be a plant, company code, or other organizational unit) has not been fully initialized in the system. This means that the necessary configuration or master data setup has not been completed.
  Missing Configuration: There may be missing configuration settings in the Financial Accounting or Controlling modules that are required for the valuation area to function properly.
  Data Inconsistencies: There could be inconsistencies in the data related to the valuation area, such as missing entries in relevant tables.
  
  Solution:
  
  Check Initialization Status: Verify the initialization status of the valuation area in question. You can do this by navigating to the relevant configuration settings in SAP and checking if all necessary steps have been completed.
  Complete Configuration: If the initialization is incomplete, follow the necessary steps to complete the configuration for the valuation area. This may involve setting up master data, defining valuation methods, or ensuring that all required settings are in place.
  Run Initialization Programs: If applicable, run any initialization programs or transactions that are designed to set up the valuation area properly.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on initializing the valuation area in question.
  Check for Notes: Look for any SAP Notes related to this error message, as they may provide additional insights or patches that can resolve the issue.
  Contact Support: If the issue persists after checking the above steps, consider reaching out to SAP support or your internal SAP support team for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in checking or configuring the valuation area, such as OX15 (for company code settings) or OX16 (for plant settings).
  Master Data: Ensure that all necessary master data (e.g., cost centers, profit centers, etc.) is correctly set up and linked to the valuation area.
  Configuration Guides: Review configuration guides specific to your version of SAP, as the steps may vary between different releases.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.