How To Fix FIN_FB_RECON378 - Entry in FAGLBSIS with missing archiving flag (field xarch)

FIN_FB_RECON378 - Overview

• Message type: E = Error

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

• Message number: 378

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

What causes this issue?

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

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

  The SAP error message FIN_FB_RECON378 indicates that there is an issue with the Financial Accounting (FI) module, specifically related to the General Ledger (G/L) and the archiving of documents. The error occurs when there is an entry in the FAGLBSIS table (which is used for storing line items for the new G/L) that is missing the archiving flag (field XARCH). This flag is important for identifying whether the data has been archived or not.
  
  Cause:
  The primary cause of this error is that there are entries in the FAGLBSIS table that do not have the archiving flag set, which can happen due to:
  
  Incomplete or incorrect archiving processes.
  Data inconsistencies or corruption in the database.
  Issues during the migration from classic G/L to new G/L.
  Manual changes or updates to the database that bypassed standard processes.
  
  
  Solution:
  To resolve this error, you can follow these steps:
  
  
  Check Archiving Status: Verify the archiving status of the entries in the FAGLBSIS