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

FINS_RECON383 - Overview

• Message type: E = Error

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

• Message number: 383

• Message text: 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 archived
(field xarch) in the index table BSAS_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_RECON383 - Entry in BSAS_BCK without BKPF and no archiving flag: &1 message(s) ?

  The SAP error message FINS_RECON383 indicates that there is an entry in the table BSAS_BCK (which is a backup table for accounting documents) that does not have a corresponding entry in the BKPF table (the accounting document header table) and does not have the archiving flag set. This situation typically arises during data reconciliation or when trying to access financial documents.
  
  Cause:
  
  
  Data Inconsistency: The most common cause of this error is data inconsistency, where entries in the backup table (BSAS_BCK) exist without corresponding entries in the main accounting document table (BKPF). 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 backup table.
  
  
  
  Solution:
  
  
  Check for Orphaned Entries: 
  
  Use transaction codes like SE16 or SE11 to check the contents of the BSAS_BCK and BKPF tables. Look for entries