How To Fix FIN_FB_RECON372 - Entry in BSIS with missing archiving flag (field xarch)

FIN_FB_RECON372 - Overview

• Message type: E = Error

• Message class: FIN_FB_RECON - Conversion to S/4HANA: Reconciliation

• Message number: 372

• Message text: Entry in BSIS with missing archiving flag (field xarch)

What causes this issue?

There are line items in the index table BSIS without header information
in table BKPF which are not marked as partially archived (field xarch)
in the index table BSIS.

System Response

The system informs about this inconsistency which must be corrected in
your productive system before starting the data migration.

How to fix this error?

For more information, see
<DS:URLA.HTTPS://LAUNCHPAD.SUPPORT.SAP.COM/#/NOTES/2714344>SAP Note
2714344.</>

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FIN_FB_RECON372 - Entry in BSIS with missing archiving flag (field xarch) ?

  The SAP error message FIN_FB_RECON372 indicates that there is an entry in the BSIS table (which stores line items for accounts) that is missing the archiving flag (field XARCH). This can occur during the reconciliation process or when trying to archive financial documents.
  
  Cause:
  The primary cause of this error is that the system has detected an inconsistency in the data stored in the BSIS table. Specifically, it means that there are entries that should have been archived but do not have the appropriate archiving flag set. This can happen due to:
  
  Incomplete Archiving Process: If the archiving process was interrupted or not completed properly, some entries may not have their flags updated.
  Data Corruption: There may be data integrity issues or corruption in the database that leads to missing or incorrect flags.
  Custom Development: If there are custom programs or modifications that interact with the BSIS table, they may not be setting the archiving