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

SAP Error Message - Details

• 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 flag correctly.
  
  Solution:
  To resolve the FIN_FB_RECON372 error, you can follow these steps:
  
  
  Check Archiving Status: Verify the archiving status of the entries in the BSIS table. You can use transaction codes like SARA (Archive Administration) to check the archiving logs and see if there were any issues during the archiving process.
  
  
  Run the Archiving Program Again: If you find that the archiving process was incomplete, you may need to rerun the archiving program for the relevant financial documents. Ensure that the archiving job completes successfully.
  
  
  Update the Archiving Flag Manually: If you have identified specific entries that are missing the archiving flag, you may need to update the XARCH field manually. This should be done with caution and ideally under the guidance of an SAP Basis or ABAP consultant to avoid further data inconsistencies.
  
  
  Database Consistency Check: Perform a consistency check on the database to identify and rectify any other potential issues. You can use transaction code SE14 (Database Utility) to check and repair inconsistencies.
  
  
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates available that can resolve the issue.
  
  
  Contact SAP Support: If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance. They can provide more specific guidance based on your system configuration and the nature of the error.
  
  
  Related Information:
  
  BSIS Table: This table contains line items for accounts in the general ledger. It is crucial for financial reporting and reconciliation.
  Archiving in SAP: Archiving is a process in SAP that helps manage data volume by moving data that is no longer needed for daily operations to an archive. This helps improve system performance and manage database size.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (for archiving), SE14 (for database utility), and SE11 (for data dictionary) to manage and troubleshoot issues related to database tables.
  
  Always ensure that you have proper backups and that you are following your organization's data management policies when making changes to the database.