How To Fix FARR_RAI370 - Incompatible change of decimal places of field &1 in class &2

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_RAI - Revenue Accounting Item

• Message number: 370

• Message text: Incompatible change of decimal places of field &1 in class &2

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_RAI370 - Incompatible change of decimal places of field &1 in class &2 ?

  The SAP error message FARR_RAI370 indicates that there is an incompatible change in the decimal places of a field in a specific class. This typically occurs in the context of financial accounting or asset accounting modules where precision in numerical values is critical.
  Cause:
  The error is usually caused by one of the following:
  
  Field Definition Change: The decimal places of a field have been changed in the data dictionary (DDIC) or in the configuration settings, which is incompatible with existing data or processes.
  Data Migration Issues: If data has been migrated from one system to another, and the decimal places of certain fields were not aligned correctly, this error can occur.
  Custom Development: If there are custom programs or enhancements that rely on specific field definitions, changing the decimal places can lead to inconsistencies.
  
  Solution:
  To resolve the error, consider the following steps:
  
  
  Check Field Definition:
  
  Go to the Data Dictionary (transaction SE11) and check the field definition for the field mentioned in the error message. Ensure that the decimal places are set correctly and consistently across all relevant tables and structures.
  
  
  
  Review Configuration:
  
  If the field is part of a configuration setting (like in Financial Accounting), review the configuration to ensure that it matches the expected decimal places.
  
  
  
  Data Consistency:
  
  If data migration is involved, ensure that the data in the target system matches the expected format and decimal places. You may need to adjust the data or re-migrate it.
  
  
  
  Custom Code Review:
  
  If there are custom programs or enhancements, review the code to ensure that it is compatible with the current field definitions. Update the code if necessary.
  
  
  
  Transport Requests:
  
  If the issue arose after a transport request, check if the transport included changes to the field definitions. If so, ensure that all systems are aligned with the same definitions.
  
  
  
  Consult Documentation:
  
  Review SAP notes and documentation related to the specific error message for any additional guidance or patches that may be available.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide guidance on handling changes in field definitions.
  Transaction Codes: Familiarize yourself with transaction codes like SE11 (Data Dictionary), SE80 (Object Navigator), and SE37 (Function Module) for debugging and analysis.
  Testing: After making changes, conduct thorough testing to ensure that the issue is resolved and that no new issues have been introduced.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis or ABAP team for further investigation.