How To Fix FINS_RECON384 - Entry in BSID_BCK without BKPF and no archiving flag: &1 message(s)

FINS_RECON384 - Overview

• Message type: E = Error

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

• Message number: 384

• Message text: 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 archived
(field xarch) in the index table BSID_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 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.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FINS_RECON384 - Entry in BSID_BCK without BKPF and no archiving flag: &1 message(s) ?

  The SAP error message FINS_RECON384 indicates that there is an inconsistency in the financial documents related to accounts receivable. Specifically, it points out that there is an entry in the BSID_BCK table (which is a backup table for open items in accounts receivable) 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 due to data inconsistencies, which can occur during data migration, system upgrades, or if there were issues during the posting of financial documents.
  Missing Document Header: The entry in the BSID_BCK table is expected to have a corresponding document in the BKPF table, which contains the header information for accounting documents. If the header is missing, it leads to this error.
  Archiving Issues: If the archiving process was not completed correctly, it might leave orphaned entries in the backup tables.
  
  
  Solution:
  
  
  Check