Do you have any question about this error?
Message type: E = Error
Message class: FTI_LDB_MESSAGE - Messages for TR OLTP Reporting Using Logical Databases
Message number: 024
Message text: Access optimization is deactivated -> long runtimes
The field table used to optimize access to the logical database is not
filled.
Possible causes:
Access optimization has been explicitly deactivated for the query
The logical database call in a report was incomplete
The logical database was called via transactions such as SE38
The field list contains all the fields that were selected in a report.
This logical database needs such a list for two reasons:
The logical database is not suitable for pure master data reporting. If
only characteristics and attributes have been selected for a master data
report, the internal logic is likely to output the wrong data. At least
one key figure must be selected (such as the no. of units
, book value, NPV, ...).
In addition, selecting and calculating the data for many of the
attributes and key figures can be very time-consuming. In such cases,
the field list helps to optimize the use of the runtime - only the
requested logical database fields are filled.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
To improve runtimes, reactivate access optimization or fill the field
table from within the report.
Alternatively, you can just continue. In this case, the field list is
filled in retrospect with all the fields from the logical database. If
you choose this option, all the fields are selected or calculated,
including fields that may not be required for the report. The runtime is
therefore longer than if the fields are requested by the report.
Error message extract from SAP system. Copyright SAP SE.
FTI_LDB_MESSAGE024
- Access optimization is deactivated -> long runtimes ?The SAP error message FTI_LDB_MESSAGE024 indicates that access optimization is deactivated, which can lead to long runtimes when executing queries or reports. This message is typically associated with the use of the SAP Business Warehouse (BW) or SAP HANA systems, where performance optimization is crucial for efficient data retrieval.
Cause:
- Access Optimization Deactivation: The primary cause of this error message is that the access optimization feature is turned off. This feature is designed to improve the performance of data access by optimizing how data is retrieved from the database.
- Configuration Issues: There may be configuration settings in the BW or HANA system that prevent access optimization from being enabled.
- Data Model Design: Inefficient data model design or poor indexing can also contribute to long runtimes, especially if access optimization is not utilized.
Solution:
Activate Access Optimization:
- Go to the relevant settings in the SAP BW or HANA system.
- Navigate to the settings for the InfoProvider or query where the error is occurring.
- Enable access optimization if it is currently deactivated.
Check Configuration:
- Review the configuration settings for the data model and ensure that all necessary parameters for access optimization are correctly set.
- Consult the SAP documentation or your system administrator for specific steps to enable access optimization.
Performance Tuning:
- Analyze the query performance and identify any bottlenecks.
- Consider optimizing the data model, such as creating appropriate indexes, aggregations, or partitions to improve performance.
- Use transaction codes like RSRT (for query performance analysis) to monitor and analyze query execution times.
Consult SAP Notes:
- Check for any relevant SAP Notes that may address this specific error message or provide additional guidance on performance optimization.
Testing:
- After making changes, test the queries or reports to ensure that the performance has improved and that the error message no longer appears.
Related Information:
By addressing the access optimization settings and ensuring that your data model is well-designed, you can significantly reduce query runtimes and resolve the error message FTI_LDB_MESSAGE024.
Get instant SAP help. Start your 7-day free trial now.
FTI_LDB_MESSAGE023
Enter the number of the secondary index for the class
What causes this issue? In the report definition (research, query) you have selected the characteristic: Index Class To specify the characteristic, t...
FTI_LDB_MESSAGE022
Inconsistent Selections for Product Type, Product Cat. or Contract Type
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FTI_LDB_MESSAGE025
Key Date field is missing in the report definition
What causes this issue? You have defined a report for determining postions with several key dates and you now want to run this report. However, the &...
FTI_LDB_MESSAGE026
Enter a key date
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.