Message type: E = Error
Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation
Message number: 382
Message text: Entry in BSIS_BCK without BKPF and no archiving flag: &1 message(s)
There are line items in the index table BSIS_BCK without header
information in table BKPF which are not marked as partially archived
(field xarch) in the index table BSIS_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_RECON382
- Entry in BSIS_BCK without BKPF and no archiving flag: &1 message(s) ?The SAP error message FINS_RECON382 indicates that there are entries in the BSIS_BCK table (which is a backup table for the BSIS table that stores line items for accounts) that do not have corresponding entries in the BKPF table (the accounting document header table). This situation typically arises when there are inconsistencies in the data, often due to missing or incomplete document postings.
Cause: Missing BKPF Entries: The most common cause is that the accounting documents were not created properly, or they were deleted or not archived correctly. Data Inconsistencies: This can occur due to system errors, manual data manipulation, or issues during data migration or upgrades. Archiving Issues: If the archiving process did not complete successfully, it could lead to orphaned entries in the BSIS_BCK table.
Solution: Check for Missing Documents: Investigate the missing entries in the BKPF table. You can do this by running a query to find the missing document numbers that should
Get instant SAP help. Sign up for our Free Essentials Plan.
FINS_RECON379
&1: Entry in FAGLBSAS_BCK with missing archiving flag (field xarch)
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
FINS_RECON378
&1: Entry in FAGLBSIS_BCK with missing archiving flag (field xarch)
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
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_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...
Click on this link to search all SAP messages.