Do you have any question about this error?
Message type: E = Error
Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation
Message number: 385
Message text: Entry in BSAD_BCK without BKPF and no archiving flag: &1 message(s)
There are line items in the index table BSAD_BCK without header
information in table BKPF which are not marked as partially archived
(field xarch) in the index table BSAD_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 missing archiving
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_RECON385
- Entry in BSAD_BCK without BKPF and no archiving flag: &1 message(s) ?The SAP error message FINS_RECON385 indicates that there is an inconsistency in the financial accounting data, specifically related to the reconciliation of accounts. The message states that there is an entry in the BSAD_BCK table (which is used for storing backup data for cleared items) that does not have a corresponding entry in the BKPF table (the accounting document header table) and that the archiving flag is not set.
Cause:
Data Inconsistency: This error typically arises when there are entries in the BSAD_BCK table that should have been archived or deleted but still exist without a corresponding entry in the BKPF table. This can happen due to:
- Manual deletions or modifications of accounting documents.
- Issues during data migration or system upgrades.
- Incomplete archiving processes.
Archiving Issues: If the archiving process did not complete successfully, it could leave orphaned entries in the BSAD_BCK table.
Solution:
Check for Orphaned Entries: You can run a report or SQL query to identify the orphaned entries in the BSAD_BCK table that do not have corresponding entries in the BKPF table.
Data Consistency Check: Use transaction SE38 to run the program RFSEPA00 (or similar programs) to check for inconsistencies in the financial documents.
Archiving Process: Ensure that the archiving process for financial documents is correctly configured and executed. You may need to re-run the archiving job if it was interrupted.
Manual Deletion: If you confirm that the entries in BSAD_BCK are indeed orphaned and not needed, you may consider manually deleting them. However, this should be done with caution and ideally under the guidance of your SAP Basis or Finance team.
Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
System Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it involves complex data integrity issues.
Related Information:
Always ensure that you have proper backups and that you follow your organization's data management policies when making changes to the database.
Get instant SAP help. Start your 7-day free trial now.
FINS_RECON384
Entry in BSID_BCK without BKPF and no archiving flag: &1 message(s)
What causes this issue? There are line items in the index table BSID_BCK without header information in table BKPF which are not marked as partially a...
FINS_RECON383
Entry in BSAS_BCK without BKPF and no archiving flag: &1 message(s)
What causes this issue? There are line items in the index table BSAS_BCK without header information in table BKPF which are not marked as partially a...
FINS_RECON386
Entry in BSIK_BCK without BKPF and no archiving flag: &1 message(s)
What causes this issue? There are line items in the index table BSIK_BCK without header information in table BKPF which are not marked as partially a...
FINS_RECON387
Entry in BSAK_BCK without BKPF and no archiving flag: &1 message(s)
What causes this issue? There are line items in the index table BSAK_BCK without header information in table BKPF which are not marked as partially a...
Click on this link to search all SAP messages.