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

FINS_RECON349 - Overview

• 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