How To Fix FINS_RECON624 - Missing entry in ACDOCA but existing in BSEG_ADD: &1 message(s)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 624

• Message text: Missing entry in ACDOCA but existing in BSEG_ADD: &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_RECON624 - Missing entry in ACDOCA but existing in BSEG_ADD: &1 message(s) ?

  The SAP error message FINS_RECON624 indicates that there is a discrepancy between the entries in the ACDOCA table (the Universal Journal) and the BSEG_ADD table (which contains additional line item data for accounting documents). Specifically, this error occurs when there is a missing entry in ACDOCA that exists in BSEG_ADD.
  Cause:
  
  
  Data Inconsistency: This error typically arises due to inconsistencies in the data between the two tables. It may occur if:
  
  An accounting document was created or modified, but the corresponding entry in ACDOCA was not updated correctly.
  There was a failure during a data migration or system upgrade process.
  Manual changes or custom developments that bypass standard processes may have led to this inconsistency.
  
  
  
  Missing Data: The system expects that every entry in BSEG_ADD should have a corresponding entry in ACDOCA, and if it does not, this error will be triggered.
  
  
  Solution:
  
  
  Check for Missing Entries: 
  
  Use transaction codes like SE16 or SE11 to check the entries in both ACDOCA and BSEG_ADD. You can run queries to identify which entries are missing in ACDOCA.
  Compare the document numbers and other relevant fields to identify discrepancies.
  
  
  
  Reconcile Data: 
  
  If you find missing entries, you may need to manually create the corresponding entries in ACDOCA. This should be done with caution and ideally under the guidance of a functional consultant or SAP support.
  If the missing entries are due to a failed process, you may need to re-run the relevant processes (like document posting or data migration) to ensure that all entries are correctly created.
  
  
  
  Check Custom Developments: 
  
  If there are custom programs or enhancements that interact with these tables, review them to ensure they are functioning correctly and not causing inconsistencies.
  
  
  
  SAP Notes and Support: 
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues related to this error message.
  
  
  
  Consult SAP Support: 
  
  If the issue persists and you are unable to resolve it, consider reaching out to SAP Support for assistance. They can provide guidance based on the specific details of your system and configuration.
  
  
  
  Related Information:
  
  ACDOCA: This is the table for the Universal Journal in SAP S/4HANA, which consolidates various financial data into a single line item table.
  BSEG_ADD: This table contains additional line item data for accounting documents, which may include additional fields not present in the standard BSEG table.
  Transaction Codes: Familiarize yourself with transaction codes like SE16 (Data Browser), SE11 (Data Dictionary), and others that can help you analyze the data in these tables.
  
  By following these steps, you should be able to identify the cause of the error and take appropriate action to resolve it.