How To Fix FINS_RECON353 - Item in BSEG_ADD without FAGLBSIS_BCK/FAGLBSAS_BCK: &1 message(s)

SAP Error Message - Details

• Message type: E = Error

• Message class: FINS_RECON - SAP S/4HANA Finance Migration: Reconciliation

• Message number: 353

• Message text: Item in BSEG_ADD without FAGLBSIS_BCK/FAGLBSAS_BCK: &1 message(s)

What causes this issue?

There are line items in table BSEG_ADD which are neither available in
the index table FAGLBSIS_BCK nor in the index table FAGLBSAS_BCK.

System Response

The system informs about this inconsistency which has to be corrected in
your productive system before starting the data migration.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FINS_RECON353 - Item in BSEG_ADD without FAGLBSIS_BCK/FAGLBSAS_BCK: &1 message(s) ?

  The SAP error message FINS_RECON353 indicates that there is an issue with the reconciliation of line items in the BSEG_ADD table, specifically that there are items present without corresponding entries in the FAGLBSIS_BCK or FAGLBSAS_BCK tables. This typically occurs in the context of the New General Ledger (New G/L) accounting in SAP.
  Cause:
  
  
  Missing Entries: The error suggests that there are entries in the BSEG_ADD table that do not have corresponding entries in the FAGLBSIS_BCK (for balance sheet) or FAGLBSAS_BCK (for account statement) tables. This can happen due to various reasons, such as:
  
  Data inconsistencies during document posting.
  Issues during the migration from classic G/L to New G/L.
  Manual adjustments or corrections that were not properly reflected in the necessary tables.
  
  
  
  Configuration Issues: There may be configuration issues in the New G/L settings that prevent proper reconciliation.
  
  
  Data Migration Issues: If the system was recently migrated or upgraded, there may be data integrity issues that need to be addressed.
  
  
  Solution:
  
  
  Check for Missing Entries: Use transaction codes like SE16 or SE11 to check the BSEG_ADD, FAGLBSIS_BCK, and FAGLBSAS_BCK tables for the specific item mentioned in the error message. Identify if there are indeed missing entries.
  
  
  Reconcile Data: If you find discrepancies, you may need to reconcile the data. This could involve:
  
  Running the reconciliation programs provided by SAP.
  Manually adjusting entries if necessary.
  
  
  
  Check Configuration: Review the configuration settings for the New G/L to ensure that everything is set up correctly. This includes checking the settings for document splitting, account determination, and other related configurations.
  
  
  Use SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues.
  
  
  Consult with SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP Support for assistance. Provide them with the error message details and any relevant information about your system configuration.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with transaction codes such as:
  
  SE16: Data Browser to view table contents.
  FB03: Display Document to view accounting documents.
  FBL1N/FBL3N/FBL5N: Vendor/Customer/GL Account Line Item Display for further analysis.
  
  
  
  Documentation: Review SAP documentation on New G/L accounting and reconciliation processes to understand the underlying principles and best practices.
  
  
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.