How To Fix FIN_FB_RECON343 - Item in BSEG_ADD but missing in tables FAGLBSIS and FAGLBSAS

FIN_FB_RECON343 - Overview

• Message type: E = Error

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

• Message number: 343

• Message text: Item in BSEG_ADD but missing in tables FAGLBSIS and FAGLBSAS

What causes this issue?

There are line items in table BSEG_ADD which are neither available in
the index table FAGLBSIS nor 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_RECON343 - Item in BSEG_ADD but missing in tables FAGLBSIS and FAGLBSAS ?

  The SAP error message FIN_FB_RECON343 indicates that there is a discrepancy between the BSEG_ADD table and the FAGLBSIS and FAGLBSAS tables. This typically occurs during the reconciliation process, particularly when dealing with financial documents and their associated line items.
  
  Cause:
  
  
  Data Inconsistency: The error usually arises when there are entries in the BSEG_ADD table that do not have corresponding entries in the FAGLBSIS (General Ledger Document Segment) and FAGLBSAS (General Ledger Document Segment for Account Balances) tables. This can happen due to:
  
  Incomplete or failed postings.
  Manual changes or deletions in the database that were not properly reflected in all related tables.
  Issues during data migration or system upgrades.
  
  
  
  Missing Data: If the financial documents were posted without the necessary updates to the balance sheet or if the reconciliation process was interrupted, it could lead to missing entries.
  
  
  
  Solution:
  
  
  Check for Missing Entries: 
  
  Use transaction codes like SE16 or SE11 to check the contents of the BSEG_ADD, FAGLBSIS,