How To Fix FB_CORR106 - Inconsistent GL-account &1/&2 in SKB1 (xkres) --> contact SAP support

SAP Error Message - Details

• Message type: E = Error

• Message class: FB_CORR - Analysis and correction of inconsistencies (FI)

• Message number: 106

• Message text: Inconsistent GL-account &1/&2 in SKB1 (xkres) --> contact SAP support

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 FB_CORR106 - Inconsistent GL-account &1/&2 in SKB1 (xkres) --> contact SAP support ?

  The SAP error message FB_CORR106 indicates that there is an inconsistency in the General Ledger (GL) account data in the SKB1 table, which contains the master data for GL accounts. The error typically arises when there is a mismatch or inconsistency in the account settings or configurations.
  Cause:
  
  Inconsistent Data: The GL account specified in the error message may have inconsistent data in the SKB1 table. This could be due to manual changes, data migration issues, or system errors.
  Missing Entries: The GL account may not have the necessary entries in the SKB1 table for the company code or other relevant configurations.
  Configuration Issues: There may be issues with the configuration of the GL account in the Financial Accounting (FI) module, such as incorrect account types or missing settings.
  Data Corruption: In rare cases, data corruption in the database could lead to inconsistencies.
  
  Solution:
  
  Check the GL Account: Verify the GL account specified in the error message. Check the SKB1 table for the account and ensure that all necessary entries exist and are consistent.
  Review Configuration: Review the configuration settings for the GL account in the SAP system. Ensure that the account is properly set up for the relevant company code and that all required fields are filled out correctly.
  Data Consistency Check: Run a data consistency check in the SAP system to identify any inconsistencies in the GL account data. This can often be done using transaction codes like SE16 or SE11 to view the SKB1 table.
  Recreate the Account: If the account is found to be corrupted or incorrectly configured, consider deleting and recreating the GL account, ensuring that all settings are correct.
  Contact SAP Support: If the issue persists after checking the above points, it may be necessary to contact SAP support for further assistance. Provide them with the error message details and any relevant information about the steps you have taken to resolve the issue.
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like FS00 (to display/change GL account master data) and OBY6 (to check company code settings) to investigate the issue further.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review SAP documentation related to GL account management and error handling for more insights.
  
  By following these steps, you should be able to identify and resolve the inconsistency causing the FB_CORR106 error.