How To Fix FINS_RECON552 - &1: Non-GL entries of ACDOCA have balance in HSL of &2 (&3)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 552

• Message text: &1: Non-GL entries of ACDOCA have balance in HSL of &2 (&3)

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_RECON552 - &1: Non-GL entries of ACDOCA have balance in HSL of &2 (&3) ?

  The SAP error message FINS_RECON552 indicates that there are non-General Ledger (non-GL) entries in the ACDOCA table (the universal journal) that have a balance in the local currency (HSL) that is not zero. This typically occurs during reconciliation processes or when trying to close financial periods.
  Cause:
  
  Non-GL Entries: The error specifically points to non-GL entries, which could be related to sub-ledgers (like Accounts Payable, Accounts Receivable, Asset Accounting, etc.) that have not been properly reconciled or cleared.
  Uncleared Items: There may be uncleared items in the sub-ledgers that are causing the balance to remain.
  Configuration Issues: There could be issues with the configuration of the financial settings in SAP, leading to discrepancies in the balances.
  Data Entry Errors: Incorrect postings or data entry errors could lead to non-zero balances in the ACDOCA table.
  
  Solution:
  
  Identify Non-GL Entries: Use transaction codes like SE16N to view the ACDOCA table and filter for non-GL entries. Check for entries that have a balance in HSL.
  Reconcile Sub-Ledgers: Ensure that all sub-ledger accounts are reconciled. This may involve clearing open items in Accounts Payable, Accounts Receivable, or other relevant modules.
  Check for Open Items: Use transaction codes like FBL1N (for vendor accounts) or FBL5N (for customer accounts) to check for open items that may need to be cleared.
  Review Configuration: Check the configuration settings in the Financial Accounting (FI) module to ensure that everything is set up correctly.
  Consult with Finance Team: Work with your finance team to understand the nature of the entries and determine if any adjustments or corrections are needed.
  Run Reconciliation Reports: Use SAP standard reports to identify discrepancies and take corrective actions.
  
  Related Information:
  
  ACDOCA Table: This table is part of the Universal Journal in SAP S/4HANA and contains all financial transactions, including both GL and non-GL entries.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FBL1N, FBL5N, and FBL3N (for GL accounts) to analyze the entries.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional insights or solutions for specific scenarios.
  Documentation: Review SAP documentation related to financial reconciliation and the Universal Journal for best practices and troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate actions to resolve it.