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

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 387

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

  The SAP error message FINS_RECON387 indicates that there are entries in the BSAK_BCK table (which is used for storing cleared items) 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 or issues with data archiving.
  Cause:
  
  Missing BKPF Entries: The most common cause is that there are entries in the BSAK_BCK table that do not have a corresponding entry in the BKPF table. This can happen if documents were deleted or if there was an error during the posting process.
  Data Archiving Issues: If the archiving process was not completed correctly, it could lead to inconsistencies where cleared items are present without their corresponding accounting documents.
  Manual Deletions: If entries were manually deleted from the BKPF table without properly clearing the related entries in BSAK_BCK, this error can occur.
  
  Solution:
  
  Check for Missing Entries: Use transaction codes like SE16 or SE11 to check the BSAK_BCK and BKPF tables. Look for entries in BSAK_BCK that do not have corresponding entries in BKPF.
  Reconcile Data: If you find discrepancies, you may need to reconcile the data. This could involve restoring missing BKPF entries if they were deleted or correcting any posting errors.
  Archiving Process: Ensure that the archiving process is functioning correctly. If necessary, re-run the archiving jobs to ensure that all relevant data is archived properly.
  Consult SAP Notes: Check for any relevant SAP Notes that might address this specific error. SAP frequently releases notes that provide solutions or workarounds for known issues.
  Data Consistency Check: Use transaction code SARA to perform a data consistency check. This can help identify and resolve inconsistencies in the data.
  Contact SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP support for assistance.
  
  Related Information:
  
  BSAK_BCK Table: This table contains cleared items in accounts payable and accounts receivable.
  BKPF Table: This table contains the header data for accounting documents.
  Archiving: The archiving process in SAP is crucial for data management and performance. It involves moving old data to an archive to keep the database size manageable.
  Transaction Codes: Familiarize yourself with transaction codes like SE16 (Data Browser), SE11 (Data Dictionary), and SARA (Archive Administration) for troubleshooting.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.