How To Fix REP_EAPS_CZ_MSG026 - Old customizing node '&1/&2/&3' has not supported column type '&4' set

REP_EAPS_CZ_MSG026 - Overview

• Message type: E = Error

• Message class: REP_EAPS_CZ_MSG - PS-CZ Reports

• Message number: 026

• Message text: Old customizing node '&1/&2/&3' has not supported column type '&4' set

What causes this issue?

In the old Customizing, the node '&V1&/&V2&/&V3&' has a not supported
column type '&V4&' set. The following column types are not supported:
CM,,,,Fund: Compare Per. - Old
CB,,,,Fund: Fiscal Per. - Old
CS,,,,Fund: Fisc. + Comp. Per. - Old
CO,,,,Fund: Fisc. - Comp. Per. - Old

System Response

The node is converted to an
<DS:DE.REP_EAPS_ITEM_GROUP>item group</> with prefix '&V4&'.

How to fix this error?

You must change the old Customizing and convert the data again, or you
must make manual settings in the <DS:SIMG.REP_EAPS_RFBILVC>Set Up Data
Connector for Reporting Framework
</> Customizing activity.

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.

REP_EAPS_CZ_MSG026 - Details

• The SAP error message REP_EAPS_CZ_MSG026 indicates that there is an issue with a customizing node in the SAP system. Specifically, it suggests that an old customizing node has a column type that is not supported. This can occur during the execution of certain reports or transactions that rely on specific data structures.
  
  Cause:
  
  Outdated Customizing Node: The customizing node referenced in the error message (&1/&2/&3) is likely outdated or has been modified in a way that it no longer aligns with the expected data structure.
  Unsupported Column Type: The column type (&4) set in the customizing node is not recognized or supported by the current version of the SAP application or the specific report being executed.
  Data Model Changes: Changes in the underlying data model or database schema may have rendered certain column types obsolete.
  
  
  Solution:
  
  Check Customizing Settings: Review the customizing settings for the node specified in the error message. Ensure that the column types