How To Fix FINS_RECON346 - Open item in BSEG, missing in BSIK_BCK: &1 message(s)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 346

• Message text: Open item in BSEG, missing in BSIK_BCK: &1 message(s)

What causes this issue?

There are open line items in table BSEG which are <ZH>not</> available
in the index table BSIK_BCK but these open line items are already
available in the index table BSAK_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?

This inconsistency can be corrected by program 'FIN_CORR_MIG_ERROR_SFIN'
in the original source system (i. e. your productive system):
If you want to correct inconsistencies concerning clearing information
found in migration to S/4HANA Finance, then you have to start program
FIN_CORR_MIG_ERROR_SFIN in the original source system. The
inconsistencies which have to be corrected are determined by a RFC-call
from the original source system to this system. For more information,
read the program documentation of program FIN_CORR_MIG_ERROR_SFIN in the
original source system.
This procedure of correction in the original source system will ensure
that these inconsistencies will not occur in future test migrations any
more.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FINS_RECON346 - Open item in BSEG, missing in BSIK_BCK: &1 message(s) ?

  The SAP error message FINS_RECON346 indicates that there is an inconsistency between the open items in the BSEG (Accounting Document Segment) table and the BSIK_BCK (Accounting Document Segment for Open Items) table. Specifically, it means that there are open items in the BSEG table that are not found in the BSIK_BCK table.
  Cause:
  
  Data Inconsistency: This error typically arises due to data inconsistencies between the accounting documents and the open item management. It can occur after a data migration, system upgrade, or if there were manual changes made to the database.
  Incomplete Processing: If a transaction was not fully processed or if there was an error during the posting of documents, it could lead to discrepancies.
  Custom Developments: Custom programs or enhancements that manipulate accounting documents may inadvertently cause inconsistencies.
  
  Solution:
  
  Check for Missing Entries: Investigate the specific entries in the BSEG table that are causing the issue. You can use transaction codes like SE16 or SE11 to view the contents of the tables.
  Reconcile Open Items: Use transaction code FBL1N (Vendor Line Item Display) or FBL3N (G/L Account Line Item Display) to check the open items and reconcile them with the entries in BSIK_BCK.
  Run Consistency Checks: Use the SAP standard report RFBLG (for clearing open items) or RFUMSV00 (for clearing open items in the vendor account) to identify and resolve inconsistencies.
  Rebuild BSIK_BCK Table: If the issue persists, you may need to rebuild the BSIK_BCK table. This can be done using the program RFBKBL00 to regenerate the open item data.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes like SE16, SE11, FBL1N, FBL3N, and RFBLG for troubleshooting and data analysis.
  SAP Support: If the issue cannot be resolved internally, consider reaching out to SAP Support for assistance, providing them with detailed information about the error and the steps taken to troubleshoot.
  Documentation: Review SAP documentation related to financial accounting and open item management for best practices and guidelines.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve the inconsistency between the BSEG and BSIK_BCK tables.