How To Fix FIN_FB_RECON003 - Balance in BSEG is not zero in second local currency &2

FIN_FB_RECON003 - Overview

• Message type: E = Error

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

• Message number: 003

• Message text: Balance in BSEG is not zero in second local currency &2

What causes this issue?

You have performed a reconciliation after data migration to <LS>SAP
Accounting powered by SAP HANA</>. For document &V1&, second local
currency &V2&, the balance is not zero:
Sum of debit amounts: &V3& &V2&
Sum of credit amounts: &V4& &V2&

System Response

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

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FIN_FB_RECON003 - Balance in BSEG is not zero in second local currency &2 ?

  The SAP error message FIN_FB_RECON003 indicates that there is a discrepancy in the balance of the BSEG (Document Segment) table for a specific document in the second local currency. This error typically arises during the reconciliation process, where the system expects the balance to be zero but finds that it is not.
  
  Cause:
  
  Currency Conversion Issues: There may be issues with how the amounts in the second local currency are being calculated or converted.
  Incomplete Transactions: Transactions may not have been fully processed or posted, leading to an imbalance.
  Manual Adjustments: Manual entries or adjustments may have been made that do not align with the expected balances.
  
  Configuration Issues: Incorrect configuration in the currency settings or in the financial document settings can lead to discrepancies.
  Data Integrity Issues: There may be data integrity issues, such as missing or incorrect entries in the BSEG table.
  
  
  Solution:
  
  Check Document Entries: Review the document entries in the BSEG table for the