How To Fix FINS_RECON335 - &1: Open item in BSEG, missing in BSID_BCK (but available in BSAD_BCK)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 335

• Message text: &1: Open item in BSEG, missing in BSID_BCK (but available in BSAD_BCK)

What causes this issue?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

How to fix this error?

Details about this issue (possible missing clearing information) can be
found in the summary at the end of the application log (message number
345).

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FINS_RECON335 - &1: Open item in BSEG, missing in BSID_BCK (but available in BSAD_BCK) ?

  The SAP error message FINS_RECON335 indicates a reconciliation issue between the open items in the BSEG table and the backup tables BSID_BCK (for open items in accounts receivable) and BSAD_BCK (for cleared items in accounts receivable). This error typically arises during the reconciliation process when the system detects that there is an open item in the BSEG table that is not present in the BSID_BCK table but is found in the BSAD_BCK table.
  Cause:
  
  
  Data Inconsistency: The primary cause of this error is a data inconsistency between the BSEG and the backup tables (BSID_BCK and BSAD_BCK). This can occur due to various reasons, such as:
  
  Manual data manipulation or incorrect postings.
  Issues during data migration or system upgrades.
  Incomplete or failed batch jobs that process financial data.
  Errors during the archiving process.
  
  
  
  Cleared Items: The error suggests that the item is marked as cleared in the BSAD_BCK table, which means it has been settled or cleared, but it still appears as an open item in BSEG.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Data Consistency:
  
  Use transaction codes like SE16 or SE11 to check the entries in the BSEG, BSID_BCK, and BSAD_BCK tables.
  Identify the specific open item in BSEG that is causing the issue.
  
  
  
  Analyze the Open Item:
  
  Determine why the open item exists in BSEG but not in BSID_BCK. Check the document flow and any related postings.
  Look for any inconsistencies in the document status.
  
  
  
  Reconcile the Data:
  
  If the item is indeed cleared, you may need to update the status in the BSEG table or ensure that the item is correctly reflected in the BSID_BCK table.
  You may need to run a program or transaction to reconcile the data. This could involve reprocessing the relevant documents or correcting any discrepancies.
  
  
  
  Consult SAP Notes:
  
  Check for any relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  
  
  
  Engage SAP Support:
  
  If the issue persists and you cannot resolve it, consider reaching out to SAP support for assistance. Provide them with detailed information about the error and the steps you have taken to troubleshoot.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like FB03 (Display Document), FBL1N (Vendor Line Item Display), FBL3N (G/L Account Line Item Display), and FBL5N (Customer Line Item Display) to analyze the documents and their statuses.
  Backup Tables: Understand the purpose of the backup tables (BSID_BCK and BSAD_BCK) and how they relate to the main BSEG table.
  Data Migration: If this issue arose after a data migration or system upgrade, review the migration logs and processes to identify any potential issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.