How To Fix FINS_RECON522 - &1: Entry in BSEG_ADD without corresponding entry in ACDOCA

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 522

• Message text: &1: Entry in BSEG_ADD without corresponding entry in ACDOCA

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_RECON522 - &1: Entry in BSEG_ADD without corresponding entry in ACDOCA ?

  The SAP error message FINS_RECON522 indicates that there is an entry in the BSEG_ADD table (which is used for additional line items in accounting documents) that does not have a corresponding entry in the ACDOCA table (the universal journal entry table). This inconsistency typically arises during the reconciliation process in SAP S/4HANA, particularly when dealing with the new Universal Journal.
  Cause:
  
  Data Migration Issues: If data was migrated from an older version of SAP or from another system, there may be inconsistencies between the BSEG_ADD and ACDOCA tables.
  Manual Adjustments: Manual entries or adjustments made directly in the BSEG_ADD table without corresponding updates in ACDOCA can lead to this error.
  System Errors: Bugs or issues during document posting or processing can result in orphaned entries in BSEG_ADD.
  Inconsistent Configuration: Configuration settings that do not align with the expected behavior of the Universal Journal can also lead to this error.
  
  Solution:
  
  Data Consistency Check: Perform a consistency check between the BSEG_ADD and ACDOCA tables. You can use transaction codes like SE16 or SE11 to analyze the entries in both tables.
  Reconcile Entries: Identify the specific entries in BSEG_ADD that do not have corresponding entries in ACDOCA. You may need to create the missing entries in ACDOCA or remove the orphaned entries in BSEG_ADD, depending on your business requirements.
  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 SAP Support: If the issue persists or if you are unsure about how to proceed, it may be beneficial to consult with SAP Support or your internal SAP team for further assistance.
  Review Custom Code: If there are any custom developments or enhancements in your SAP system, review them to ensure they are not causing the inconsistency.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like FB03 (Display Document), FB02 (Change Document), and SE16N (Data Browser) to investigate the entries in the relevant tables.
  SAP Documentation: Review SAP documentation related to the Universal Journal and the reconciliation process to understand the expected behavior of the system.
  Testing Environment: If possible, replicate the issue in a testing environment to analyze the root cause without affecting the production system.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.