How To Fix FIN_FB_RECON379 - Entry in FAGLBSAS 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: 379

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

What causes this issue?

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

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

  The SAP error message FIN_FB_RECON379 indicates that there is an issue with the Financial Accounting (FI) module, specifically related to the General Ledger (G/L) account balance table (FAGLBSAS). The error suggests that there is an entry in the FAGLBSAS table that is missing the archiving flag (field XARCH), which is used to indicate whether the data has been archived or not.
  Cause:
  
  
  Data Inconsistency: The primary cause of this error is usually data inconsistency in the FAGLBSAS table. This can occur due to various reasons, such as:
  
  Incomplete or failed archiving processes.
  Manual changes to the database that bypassed standard SAP processes.
  Issues during data migration or system upgrades.
  
  
  
  Configuration Issues: There may be configuration issues in the archiving settings for the Financial Accounting module.
  
  
  Solution:
  To resolve the FIN_FB_RECON379 error, you can follow these steps:
  
  
  Check Archiving Status:
  
  Use transaction code SARA to check the archiving status of the relevant objects. Ensure that the archiving process has been completed successfully.
  
  
  
  Run the Archiving Process:
  
  If the archiving process has not been completed, run the archiving program for the relevant financial documents. This can be done through transaction code SARA and selecting the appropriate archiving object.
  
  
  
  Data Consistency Check:
  
  Use transaction code FBRA to perform a reconciliation of the G/L accounts. This can help identify and correct inconsistencies in the data.
  
  
  
  Manual Update:
  
  If you have identified specific entries in the FAGLBSAS table that are missing the archiving flag, you may need to manually update these entries. However, this should be done with caution and ideally under the guidance of an SAP Basis or FI consultant.
  
  
  
  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 detailed guidance based on your specific system configuration and version.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SARA: Archive Administration
  FBRA: Reset Cleared Items
  SE16N: Data Browser (to view FAGLBSAS entries)
  
  
  
  Tables:
  
  FAGLBSAS: G/L Account Balances (for New G/L)
  FAGLFLEXA: G/L Account Line Items (for New G/L)
  
  
  
  Documentation: Review SAP documentation related to archiving in Financial Accounting for best practices and guidelines.
  
  
  Always ensure that you have proper backups and that you are following your organization's change management procedures when making changes to the database or system configurations.