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)
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.
The system informs about this inconsistency which has to be corrected in
your productive system before starting the data migration.
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.
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.
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
Get instant SAP help. Sign up for our Free Essentials Plan.
FINS_RECON345
Open item in BSEG, missing in BSID_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 BSID_BCK but these open...
FINS_RECON344
Open item in BSEG, missing in BSIS_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 BSIS_BCK but these open...
FINS_RECON347
Open item in BSEG, missing in FAGLBSIS_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 FAGLBSIS_BCK but these ...
FINS_RECON348
Open item in BSEG_ADD, missing in FAGLBSIS_BCK: &1 message(s)
What causes this issue? There are open line items in table BSEG_ADD which are <ZH>not</> available in the index table FAGLBSIS_BCK but th...
Click on this link to search all SAP messages.