How To Fix FINS_RECON590 - &1: Field OSL of FAGLFLEXT does have a non initial amount &2&3&4

FINS_RECON590 - Overview

• Message type: E = Error

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

• Message number: 590

• Message text: &1: Field OSL of FAGLFLEXT does have a non initial amount &2&3&4

&Diagnosis&
There are entries in the totals table (FAGLFLEXT) for which at least one
of the fields OSLVT, OSL01, OSL02, OSL03, OSL04, OSL05, OSL06, OSL07,
OSL08, OSL09, OSL10, OSL11, OSL12, OSL13, OSL14, OSL15 or OSL16 is
filled although the amount is not maintained in customizing
(FINSC_LD_CMP). To identify the related entry of FAGLFLEXT the object
numbers are &V2&&V3&&V4& (OBJNR00/OBJNR01/OBJNR02/OBJNR03/OBJNR04/OBJNR0
5/OBJNR06/OBJNR07/OBJNR08).

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 FINS_RECON590 - &1: Field OSL of FAGLFLEXT does have a non initial amount &2&3&4 ?

  The SAP error message FINS_RECON590 typically indicates an issue related to the reconciliation of financial data in the General Ledger (G/L) accounts. Specifically, the error message states that the field OSL (which stands for "Open Item Amount") in the table FAGLFLEXT (the extension table for the General Ledger) has a non-initial amount, which means that there are open items that need to be addressed.
  
  Cause:
  
  Open Items: The primary cause of this error is that there are open items in the G/L account that have not been cleared or reconciled. This can happen if there are transactions that have not been processed correctly or if there are discrepancies in the accounting entries.
  Data Inconsistencies: There may be inconsistencies in the data between different modules (e.g., FI, CO) or between the G/L and sub-ledgers.
  
  Configuration Issues: Incorrect configuration settings in the financial accounting module can also lead to this error.
  
  
  Solution:
  
  Check Open Items: Review the open