How To Fix FINS_RECON349 - Item in BSEG without BSIS_BCK/BSAS_BCK: &1 message(s)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 349

• Message text: Item in BSEG without BSIS_BCK/BSAS_BCK: &1 message(s)

What causes this issue?

There are line items in table BSEG which are neither available in the
index table BSIS_BCK nor in the index table BSAS_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_RECON349 - Item in BSEG without BSIS_BCK/BSAS_BCK: &1 message(s) ?

  The SAP error message FINS_RECON349 indicates that there is an inconsistency in the financial documents, specifically that there are items in the BSEG table (which contains line items for accounting documents) that do not have corresponding entries in the backup tables BSIS_BCK (for open items) or BSAS_BCK (for cleared items). This can occur during reconciliation processes or when trying to analyze financial data.
  Cause:
  
  
  Data Inconsistency: The most common cause of this error is data inconsistency between the BSEG table and the backup tables (BSIS_BCK and BSAS_BCK). This can happen due to:
  
  Manual data manipulation or incorrect data uploads.
  Issues during the archiving process where entries were not archived correctly.
  Errors during the posting of financial documents.
  
  
  
  Missing Entries: If a document was posted but not properly updated in the backup tables, it can lead to this error.
  
  
  Custom Developments: Custom programs or enhancements that manipulate financial data may inadvertently cause inconsistencies.
  
  
  Solution:
  
  
  Check for Inconsistencies: Use transaction codes like SE16 or SE11 to check the BSEG, BSIS_BCK, and BSAS_BCK tables for inconsistencies. Look for entries in BSEG that do not have corresponding entries in the backup tables.
  
  
  Reconcile Data: If you find discrepancies, you may need to reconcile the data. This could involve:
  
  Running the program RFSEPA00 (for clearing open items) or RFSEPA01 (for clearing cleared items) to update the backup tables.
  Manually correcting entries if necessary.
  
  
  
  Check Archiving Settings: Ensure that the archiving settings are correctly configured and that the archiving process has been completed successfully.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that can resolve the issue.
  
  
  Engage SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance. They can provide guidance based on the specific details of your system and configuration.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SE16 (Data Browser), SE11 (Data Dictionary), and others that can help you analyze the data.
  Backup Tables: Understand the purpose of BSIS_BCK and BSAS_BCK tables in the context of financial data management.
  Data Integrity: Regularly perform checks on data integrity and consistency in your SAP system to prevent such issues from arising.
  
  By following these steps, you should be able to identify the cause of the FINS_RECON349 error and implement a solution to resolve it.