How To Fix FIN_FB_RECON373 - Entry in BSAS with missing archiving flag (field xarch)

FIN_FB_RECON373 - Overview

• Message type: E = Error

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

• Message number: 373

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

What causes this issue?

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

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_RECON373 - Entry in BSAS with missing archiving flag (field xarch) ?

  The SAP error message FIN_FB_RECON373 indicates that there is an entry in the BSAS table (which stores line items for accounting documents) that is missing the archiving flag (field XARCH). This can occur due to various reasons, such as inconsistencies in the database, issues during data archiving processes, or problems with the configuration of the archiving settings.
  
  Cause:
  
  Inconsistent Data: The entry in the BSAS table may have been created or modified in a way that did not properly set the archiving flag.
  Archiving Process Issues: If the archiving process was interrupted or not executed correctly, it could lead to missing flags.
  Custom Development: Custom programs or modifications that interact with the BSAS table may not have handled the archiving flag correctly.
  Database Corruption: In rare cases, database corruption could lead to missing or incorrect data in the BSAS table.
  
  
  Solution:
  
  Check for Inconsistencies: Use transaction codes like SE16 or SE11 to check the entries in the