How To Fix FIN_FB_RECON399 - Third local currency &2 in BKPF inconsistent (should be &3)

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 399

• Message text: Third local currency &2 in BKPF inconsistent (should be &3)

What causes this issue?

There are FI documents with currency keys for the third local currency,
which do not match the currency setting for the company code.

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_RECON399 - Third local currency &2 in BKPF inconsistent (should be &3) ?

  The SAP error message FIN_FB_RECON399 indicates an inconsistency in the third local currency (often referred to as "currency type 30") in the BKPF (Accounting Document Header) table. This error typically arises during financial reconciliation processes, such as when running reports or executing transactions that involve currency conversions.
  Cause:
  The error occurs when the value stored in the third local currency field (currency type 30) in the BKPF table does not match the expected value. The expected value is usually derived from the conversion of the document amount in the document currency to the third local currency based on the exchange rate defined in the system.
  Common causes include:
  
  Incorrect Exchange Rates: The exchange rates for the third local currency may not be set up correctly in the system.
  Manual Adjustments: Manual entries or adjustments made to the document may have led to inconsistencies.
  Data Migration Issues: If data was migrated from another system, there may have been issues with how currency values were transferred.
  Configuration Issues: The configuration for currency types in the financial settings may not be set up correctly.
  
  Solution:
  To resolve the FIN_FB_RECON399 error, you can follow these steps:
  
  
  Check Exchange Rates:
  
  Go to the transaction code OB08 to review the exchange rates for the third local currency. Ensure that the rates are correctly maintained.
  
  
  
  Review Document Entries:
  
  Use transaction code FB03 to display the document in question. Check the amounts in the document currency and the third local currency to identify any discrepancies.
  
  
  
  Recalculate Currency Values:
  
  If you find discrepancies, you may need to recalculate the third local currency value. This can often be done by reversing the document and re-entering it with the correct values.
  
  
  
  Use Transaction Code FBRA:
  
  If the document is incorrect, you can reverse it using transaction code FBRA and then re-enter it with the correct amounts.
  
  
  
  Check Configuration:
  
  Ensure that the configuration for currency types is correct in the financial settings. This can be checked in the configuration menu under Financial Accounting (FI) > General Ledger Accounting > Master Data > G/L Accounts > Prepare G/L Account Creation.
  
  
  
  Consult with SAP Support:
  
  If the issue persists after checking the above points, it may be necessary to consult with SAP support or your internal SAP team for further investigation.
  
  
  
  Related Information:
  
  Transaction Codes: FB03 (Display Document), FBRA (Reverse Document), OB08 (Maintain Exchange Rates).
  Tables: BKPF (Accounting Document Header), BSEG (Accounting Document Segment).
  Currency Types: Understand the different currency types in SAP (e.g., local currency, group currency, and hard currency) and how they are configured in your system.
  
  By following these steps, you should be able to identify and resolve the inconsistency causing the FIN_FB_RECON399 error.