Do you have any question about this error?
Message type: E = Error
Message class: R7B - BW Metadata (InfoCube, InfoObject, InfoObject catalog)
Message number: 658
Message text: Indicator for high precision has been reset
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
R7B658
- Indicator for high precision has been reset ?The SAP error message R7B658, which states "Indicator for high precision has been reset," typically relates to issues with the precision settings in the SAP system, particularly in the context of financial or logistics data processing. This message indicates that the system has reset the high precision indicator, which can affect calculations and data accuracy.
Cause:
- Data Type Limitations: The error may occur if the system is trying to process data that exceeds the precision limits of the defined data types.
- Configuration Settings: The high precision indicator may have been reset due to changes in configuration settings or updates in the system.
- Incompatibility: There may be incompatibility between different modules or components of the SAP system that handle high precision data.
- User Actions: Manual changes made by users in the configuration or data entry processes can also lead to this error.
Solution:
- Check Configuration: Review the configuration settings related to high precision in the relevant modules (e.g., Financial Accounting, Controlling). Ensure that the settings are correctly defined to allow for high precision calculations.
- Data Validation: Validate the data being processed to ensure it does not exceed the precision limits. This may involve checking the formats and types of data being entered or processed.
- System Updates: Ensure that your SAP system is up to date with the latest patches and updates, as these may contain fixes for known issues related to precision handling.
- Consult Documentation: Refer to SAP documentation or notes related to the specific module you are working with to understand any specific requirements or limitations regarding high precision.
- Contact SAP Support: If the issue persists, consider reaching out to SAP support for assistance. They can provide insights based on the specific version of SAP you are using and any known issues.
Related Information:
By following these steps, you should be able to identify the cause of the R7B658 error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
R7B657
Report for finding InfoObjects is already running
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
R7B656
Error while building the selection screen
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
R7B659
Invalid transfer: I_READ_ALL or I_T_INFOCUBES or I_IOBJNM
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
R7B660
InfoObject &1 is used as an attribute in InfoProvider &2 (IOBJ)
What causes this issue? The master data index of InfoProvider &V2& has to be be rebuilt due to changes made to &V1&.System Response ...
Click on this link to search all SAP messages.