How To Fix FIN_FB_RECON339 - Item in BSEG but missing in index tables BSIS and BSAS

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 339

• Message text: Item in BSEG but missing in index tables BSIS and BSAS

What causes this issue?

There are line items in table BSEG which are neither available in the
index table BSIS nor in the index table BSAS.

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_RECON339 - Item in BSEG but missing in index tables BSIS and BSAS ?

  The SAP error message FIN_FB_RECON339 indicates that there is a discrepancy between the line items in the BSEG table and the index tables BSIS (for open items) and BSAS (for cleared items). This typically occurs during financial reconciliation processes, where the system expects to find a corresponding entry in the index tables for a line item in BSEG, but it cannot.
  Causes:
  
  Data Inconsistency: This can happen due to inconsistencies in the database, such as incomplete postings or issues during data migration.
  Index Table Updates: If the index tables (BSIS/BSAS) were not updated correctly after a posting, it could lead to this error.
  Custom Programs or Modifications: Custom developments or modifications to standard SAP processes may inadvertently cause discrepancies.
  Database Issues: Corruption or issues in the database can lead to missing entries in the index tables.
  
  Solutions:
  
  Rebuild Index Tables: You can use transaction codes like SARA (Archive Administration) or SDBA (Database Administration) to rebuild the index tables. This may involve running specific programs to regenerate the index.
  Check for Incomplete Documents: Use transaction FB03 to check the document in BSEG and ensure that it is complete and correctly posted.
  Run Reconciliation Programs: Use the standard SAP reconciliation programs to identify and correct discrepancies. For example, you can run the program RFBLG (Reconciliation of G/L Accounts) to check for inconsistencies.
  Database Consistency Check: Perform a consistency check on the database to identify and resolve any underlying issues.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide guidance on how to resolve it.
  Contact SAP Support: If the issue persists, consider reaching out to SAP support for assistance, especially if it involves complex data integrity issues.
  
  Related Information:
  
  BSEG: This table contains line item details for accounting documents.
  BSIS: This table contains open item management data for G/L accounts.
  BSAS: This table contains cleared item management data for G/L accounts.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FBRA (Reset Cleared Items), and FBL1N/FBL3N/FBL5N (Vendor/Customer/GL Account Line Items) for further investigation.
  
  Always ensure to back up your data before performing any corrective actions, and if necessary, test solutions in a development or quality assurance environment before applying them in production.