How To Fix FINS_RECON654 - Incorrect GL-Balance for Correction ACDOCA [OSL]: &1 message(s)

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation

• Message number: 654

• Message text: Incorrect GL-Balance for Correction ACDOCA [OSL]: &1 message(s)

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 FINS_RECON654 - Incorrect GL-Balance for Correction ACDOCA [OSL]: &1 message(s) ?

  The SAP error message FINS_RECON654 indicates that there is an inconsistency in the General Ledger (GL) balance for a correction in the ACDOCA table, which is the Universal Journal in SAP S/4HANA. This error typically arises during the reconciliation process or when trying to post corrections to financial documents.
  Cause:
  
  Data Inconsistency: The error often occurs due to inconsistencies in the financial data, such as mismatched balances between the GL accounts and the line items in the ACDOCA table.
  Incorrect Posting: There may have been incorrect postings or adjustments made to the GL accounts that do not align with the expected balances.
  Missing or Incorrect Data: Missing entries or incorrect data in related tables can lead to discrepancies in the GL balance.
  Configuration Issues: Incorrect configuration settings in the financial module can also lead to this error.
  
  Solution:
  
  Check GL Balances: Verify the balances of the affected GL accounts. Use transaction codes like FS10N (Display Account Balance) to check the balances and ensure they match the expected values.
  Reconcile Data: Perform a reconciliation of the ACDOCA table with the GL accounts. This may involve running reports or using transaction codes like F.01 (Financial Statements) to identify discrepancies.
  Review Correction Documents: Check the correction documents that are being posted. Ensure that they are correctly configured and that the amounts are accurate.
  Use SAP Notes: Check for any relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide fixes or workarounds for known issues.
  Consult with Technical Support: If the issue persists, it may be necessary to consult with SAP support or a technical consultant who can analyze the underlying data and configuration in more detail.
  Data Consistency Check: Use transaction SARA to run data consistency checks and ensure that all financial data is consistent across the system.
  
  Related Information:
  
  ACDOCA Table: This table contains all the line items for the Universal Journal and is critical for financial reporting in SAP S/4HANA.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FBL3N (G/L Account Line Items), and F.01 for financial reporting.
  SAP Community: Engage with the SAP Community forums for insights and shared experiences from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.