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

FINS_RECON389 - Overview

• Message type: E = Error

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

• Message number: 389

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

  The SAP error message FINS_RECON389 indicates that there is an inconsistency in the financial accounting data, specifically related to the General Ledger (G/L) accounts. This error occurs when there are entries in the table FAGLBSAS_BCK (which is a backup table for the G/L line items) that do not have a corresponding entry in the BKPF table (the accounting document header table) and the archiving flag is not set.
  
  Cause:
  
  Missing BKPF Entries: The entries in the FAGLBSAS_BCK table are supposed to have corresponding entries in the BKPF table. If they do not, it indicates that there may have been an issue during document posting or data migration.
  Data Inconsistency: This can occur due to incomplete data processing, system errors, or issues during data archiving or migration.
  Archiving Issues: If the archiving process was not completed correctly, it could lead to orphaned entries in the FAGLBSAS_BCK table.
  
  
  Solution:
  
  Check for Missing Entries: Use transaction codes like SE16