How To Fix FINS_RECON350 - Item in BSEG without BSID_BCK/BSAD_BCK: &1 message(s)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 350

• Message text: Item in BSEG without BSID_BCK/BSAD_BCK: &1 message(s)

What causes this issue?

There are line items in table BSEG which are neither available in the
index table BSID_BCK nor in the index table BSAD_BCK.

System Response

The system informs about this inconsistency which has to be corrected in
your productive system before starting the data migration.

How to fix this error?

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

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_RECON350 - Item in BSEG without BSID_BCK/BSAD_BCK: &1 message(s) ?

  The SAP error message FINS_RECON350 indicates that there is an issue with the reconciliation of line items in the BSEG table, specifically that there are items in BSEG that do not have corresponding entries in the BSID_BCK (for open items in accounts receivable) or BSAD_BCK (for open items in accounts payable) tables. This can occur during the reconciliation process when the system expects to find a matching entry in the backup tables but does not.
  Causes:
  
  Data Inconsistency: There may be inconsistencies in the data due to incomplete postings, manual changes, or errors during data migration.
  Missing Entries: The entries in BSEG may not have been properly created in the BSID_BCK or BSAD_BCK tables, possibly due to issues during document posting.
  Document Deletion: If a document was deleted or reversed, it might leave orphaned entries in BSEG without corresponding entries in the backup tables.
  Custom Development: Custom programs or enhancements may have inadvertently caused discrepancies in the data.
  
  Solutions:
  
  
  Check for Missing Entries: Use transaction codes like SE16 or SE11 to check the BSEG, BSID_BCK, and BSAD_BCK tables for missing entries. You can run queries to identify which entries in BSEG do not have corresponding entries in the backup tables.
  
  
  Reconcile Data: If you find discrepancies, you may need to reconcile the data manually. This could involve creating the missing entries in BSID_BCK or BSAD_BCK or correcting the entries in BSEG.
  
  
  Run Reconciliation Programs: SAP provides standard reconciliation programs that can help identify and fix inconsistencies. You can use transaction codes like F.5 (for open item management) to run reconciliation.
  
  
  Check for Custom Code: If there are custom developments in your SAP system, review them to ensure they are not causing the issue. You may need to involve your ABAP developers to analyze the code.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message. There may be patches or updates that can resolve the issue.
  
  
  Contact SAP Support: If the issue persists and you cannot find a resolution, 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 relevant transaction codes such as SE16 (Data Browser), SE11 (Data Dictionary), and F.5 (Open Item Management).
  Backup Tables: Understand the purpose of BSID_BCK and BSAD_BCK tables, which are used for storing backup entries for open items in accounts receivable and payable, respectively.
  Data Consistency Checks: Regularly perform data consistency checks in your SAP system to prevent such issues from arising in the future.
  
  By following these steps, you should be able to identify the cause of the FINS_RECON350 error and implement a solution to resolve it.