How To Fix FGL_PRE_CHECK022 - Funct. area derivation logic has changed in S/4HANA and S/4HANA Finance

FGL_PRE_CHECK022 - Overview

• Message type: E = Error

• Message class: FGL_PRE_CHECK - Pre Transition Check FI-GL

• Message number: 022

• Message text: Funct. area derivation logic has changed in S/4HANA and S/4HANA Finance

What causes this issue?

In your ERP release before upgrade to S/4HANA you have defined in
<DS:TRAN.FINS_FAREA_FROM_COBL>transaction FINS_FAREA_FROM_COBL</> that
the functional area shall be derived during postings <zh>not</> on
entryscreen, but as late as during the <ls>Save</> event.

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

System Response

This setting obsolete: It is not evaluated any more by the system.
Instead, in S/4HANA the system always derives the functional area
already on the entry screen of posting transactions when you press
<ls>Enter</>.
Technically, the derivation of the functional area works now based on
DDIC structure COBL instead of ACCIT.
As a consequence the substitution for application FI,
<DS:TRAN.OBBZ>call-up point 0005</> is not supported any more. You can
use <DS:SIMG.V_T001Q_FI_0006_DC>call-up point 0006</> instead.

How to fix this error?

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 FGL_PRE_CHECK022 - Funct. area derivation logic has changed in S/4HANA and S/4HANA Finance ?

  The SAP error message FGL_PRE_CHECK022 indicates that there is an issue related to the derivation logic for functional areas in the context of S/4HANA and S/4HANA Finance. This error typically arises during the migration or upgrade process when the system detects that the functional area derivation logic has changed from the previous versions of SAP ERP to S/4HANA.
  
  Cause:
  
  Changes in Functional Area Logic: In S/4HANA, the way functional areas are derived has been modified. This can lead to inconsistencies if the existing configuration or data does not align with the new logic.
  Customizations: If there are custom developments or configurations in the previous system that are not compatible with the new derivation logic, this can trigger the error.
  Data Migration Issues: During data migration, if the functional area assignments are not correctly mapped or if there are missing entries, this error can occur.
  
  
  Solution:
  
  Review Functional Area Configuration: Check the configuration settings for functional areas