How To Fix FMGL020 - Customer fields not identical in tables FMGLFLEXT and PSGLFLEXT

FMGL020 - Overview

• Message type: E = Error

• Message class: FMGL - New General Ledger for Public Sector

• Message number: 020

• Message text: Customer fields not identical in tables FMGLFLEXT and PSGLFLEXT

What causes this issue?

The system compares customer fields from totals record table FMGLFLEXT
with table PSGLFLEXT. This comparison determined that some fields do not
exist in PSGLFLEXT.

System Response

The move of the ledger to the totals record table PSGLFLEXT is
terminated.

How to fix this error?

Create customer fields of table FMGLFLEXT for table PSGLFLEXT also.
When doing this, note that table PSGLFLEXT is allowed to contain more
fields than table FMGLFLEXT, but the reverse is not allowed
.

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 FMGL020 - Customer fields not identical in tables FMGLFLEXT and PSGLFLEXT ?

  The SAP error message FMGL020 indicates that there is a mismatch in the customer fields between the tables FMGLFLEXT and PSGLFLEXT. This error typically arises in the context of Financial Management (FM) and General Ledger (GL) accounting when there are inconsistencies in the configuration or data between these two tables.
  
  Cause:
  
  Configuration Mismatch: The customer fields defined in the two tables may not be aligned. This can happen if changes were made to the field definitions in one table but not in the other.
  Data Inconsistency: If data was manually entered or imported into one of the tables without corresponding updates in the other, it can lead to discrepancies.
  Transport Issues: If changes were transported from one system to another (e.g., from development to production) and the transport did not include all necessary changes, it can result in this error.
  
  
  Solution:
  
  Check Configuration: Review the configuration settings for both FMGLFLEXT and PSGLFLEXT to ensure that the