How To Fix /CCIS/FICLR021 - Tolerance groups don't customize for & company code. See detail text.

SAP Error Message - Details

• Message type: E = Error

• Message class: /CCIS/FICLR -

• Message number: 021

• Message text: Tolerance groups don't customize for & company code. See detail text.

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 /CCIS/FICLR021 - Tolerance groups don't customize for & company code. See detail text. ?

  The SAP error message /CCIS/FICLR021 indicates that there is an issue with the configuration of tolerance groups for a specific company code in the SAP system. This error typically arises in the context of financial accounting or controlling modules, particularly when dealing with intercompany transactions or financial postings.
  Cause:
  The error message is triggered when the system cannot find a defined tolerance group for the specified company code. Tolerance groups are used in SAP to define limits for various financial transactions, such as payment differences, and they need to be configured for each company code that will use them.
  Solution:
  To resolve this error, you need to ensure that the tolerance groups are properly configured for the specified company code. Here are the steps to do this:
  
  
  Access the Configuration Settings:
  
  Go to the SAP Easy Access screen.
  Navigate to the following path: 
  SPRO -> SAP Reference IMG -> Financial Accounting (New) -> Accounts Receivable and Accounts Payable -> Customer Accounts -> Tolerance Groups -> Define Tolerance Groups
  
  
  
  
  Define Tolerance Groups:
  
  Check if the tolerance group exists for the company code in question.
  If it does not exist, you will need to create a new tolerance group or assign an existing one to the company code.
  Make sure to specify the necessary parameters, such as the maximum allowable differences for payments, discounts, etc.
  
  
  
  Assign Tolerance Groups to Company Code:
  
  After defining the tolerance group, ensure that it is assigned to the relevant company code.
  You can do this in the same configuration area where you defined the tolerance groups.
  
  
  
  Check for Other Dependencies:
  
  Ensure that there are no other configuration issues related to the company code that might be causing this error.
  Verify that the company code is active and properly set up in the system.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like OB52 (for fiscal year variant) or OBD2 (for tolerance groups) to navigate directly to the relevant configuration areas.
  Documentation: Refer to SAP Help documentation for detailed information on tolerance groups and their configuration.
  User Roles: Ensure that you have the necessary authorizations to make changes in the configuration settings.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or functional team for further investigation, as there could be additional underlying issues affecting the configuration.