How To Fix FIN_FB_RECON374 - Entry in BSID with missing archiving flag (field xarch)

FIN_FB_RECON374 - Overview

• Message type: E = Error

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

• Message number: 374

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

What causes this issue?

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

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

  The SAP error message FIN_FB_RECON374 indicates that there is an entry in the BSID table (which stores open items for customer accounts) that is missing the archiving flag (field XARCH). This can occur due to various reasons, such as inconsistencies in the database or issues during the archiving process.
  
  Cause:
  
  Inconsistent Data: The entry in the BSID 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.
  Database Corruption: In rare cases, database corruption could lead to missing or inconsistent data.
  
  
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Check for Inconsistencies:
  
  Use transaction code SE16 or SE16N to check the BSID table for entries that are missing the XARCH flag.
  Identify the specific entries that are causing the issue.
  
  
  
  Update the Archiving Flag:
  
  If you have identified specific entries that are