How To Fix /ACCGO/CAS_FLLW_MSG079 - Rule &1 evaluated and tolerance percentages from &2 to &3 found

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/CAS_FLLW_MSG -

• Message number: 079

• Message text: Rule &1 evaluated and tolerance percentages from &2 to &3 found

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 /ACCGO/CAS_FLLW_MSG079 - Rule &1 evaluated and tolerance percentages from &2 to &3 found ?

  The SAP error message /ACCGO/CAS_FLLW_MSG079 typically relates to the Financial Closing cockpit or the Financial Accounting (FI) module, particularly in the context of tolerance limits for financial transactions. This message indicates that a specific rule (denoted by &1) has been evaluated, and the tolerance percentages have been found to be outside the defined limits (from &2 to &3).
  Cause:
  
  
  Tolerance Limits: The error is triggered when the financial transaction being processed exceeds the predefined tolerance limits set in the system. This could be due to:
  
  Incorrect configuration of tolerance limits in the system.
  A transaction that legitimately exceeds the tolerance limits due to business requirements.
  Data entry errors leading to unexpected values.
  
  
  
  Rule Evaluation: The rule mentioned (&1) is likely a specific business rule or validation rule that checks for compliance with financial policies. If the transaction does not meet the criteria defined by this rule, the error will be raised.
  
  
  Solution:
  
  
  Review Tolerance Settings:
  
  Navigate to the configuration settings for tolerance limits in SAP. This can typically be found under the Financial Accounting (FI) module settings.
  Check the tolerance limits defined for the relevant accounts or transaction types and adjust them if necessary.
  
  
  
  Analyze the Transaction:
  
  Review the specific transaction that triggered the error. Check the amounts involved and see if they are correct.
  If the transaction is valid but exceeds the tolerance, consider whether an exception can be made or if the tolerance limits need to be adjusted.
  
  
  
  Adjust Rules:
  
  If the rule (&1) is too strict or not aligned with current business practices, consider modifying the rule to better fit the operational needs.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for more detailed information on the specific rule and tolerance settings.
  
  
  
  Engage with SAP Support:
  
  If the issue persists or if you are unsure about making changes, consider reaching out to SAP support or your internal SAP team for assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OB29 (for tolerance groups) and OBY6 (for tolerance limits).
  SAP Notes: Check for any SAP Notes related to this error message for additional guidance or patches that may address known issues.
  Testing: After making any changes, ensure to test the transactions in a development or quality environment before applying changes to the production system.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.