Message type: E = Error
Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation
Message number: 388
Message text: Entry in FAGLBSIS_BCK without BKPF and no archiving flag: &1 message(s)
There are line items in the index table FAGLBSIS_BCK without header
information in table BKPF which are not marked as partially archived
(field xarch) in the index table FAGLBSIS_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_RECON388
- Entry in FAGLBSIS_BCK without BKPF and no archiving flag: &1 message(s) ?The SAP error message FINS_RECON388 indicates that there is an inconsistency in the financial accounting data, specifically related to the table FAGLBSIS_BCK. This table is used for storing line items in the General Ledger (G/L) accounting. The error suggests that there are entries in the FAGLBSIS_BCK table that do not have corresponding entries in the BKPF table (the accounting document header table), and there is no archiving flag set for these entries.
Cause: Data Inconsistency: The primary cause of this error is a data inconsistency where line items exist in the FAGLBSIS_BCK table without a corresponding header entry in the BKPF table. This can happen due to various reasons, such as: Manual data manipulation or incorrect data uploads. Issues during data migration or system upgrades. Incomplete document postings or failed transactions. Archiving Issues: The absence of an archiving flag indicates that the system is not recognizing these entries as archived, which means they should still have
Get instant SAP help. Sign up for our Free Essentials Plan.
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...
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_RECON389
Entry in FAGLBSAS_BCK without BKPF and no archiving flag: &1 message(s)
What causes this issue? There are line items in the index table FAGLBSAS_BCK without header information in table BKPF which are not marked as partial...
FINS_RECON390
CoCd &1: Check for shifted buzei started at &2 and ended at &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.