How To Fix RSR_PE058 - InfoProvider &1 contains CR &2 and has no SQLScript implementation

RSR_PE058 - Overview

• Message type: E = Error

• Message class: RSR_PE - TREX Planning Engine

• Message number: 058

• Message text: InfoProvider &1 contains CR &2 and has no SQLScript implementation

What causes this issue?

InfoProvider &1 contains characteristic relationship &2 of type "exit"
<(>,<)> and there is no SQLScript-based implementation. This prevents
the whole scenario from running as SAP HANA-optimized in PAK.

System Response

As described in SAP Note 1637199, this characteristic relationship makes
the whole scenario run using classic IP-based planning, rather than as
SAP HANA-optimized with PAK. The performance of planning actions like
executing sequences is the same as in classic BW-IP.

How to fix this error?

Remove or deactivate characteristic relationship &2 using transaction
RSPLAN, in order to run the scenario as SAP HANA-optimized.
Alternatively, you can implement a PAK enabled exit either by using the
ABAP results as described in SAP Note 1956085 or by adding an
SQLScript-based solution as described in the SAP standard documentation
and/or SAP Note 1928715.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSR_PE058 - InfoProvider &1 contains CR &2 and has no SQLScript implementation ?

  The SAP error message RSR_PE058 indicates that the InfoProvider you are trying to access contains a calculated column (CR) that does not have a SQLScript implementation. This typically occurs in the context of SAP BW/4HANA or SAP BW on HANA, where SQLScript is used for performance optimization in data processing.
  
  Cause:
  
  Calculated Column (CR): The InfoProvider contains a calculated column that is defined in a way that is not compatible with SQLScript. This can happen if the calculation is complex or if it uses functions that are not supported in SQLScript.
  Lack of SQLScript Implementation: The InfoProvider may not have been properly configured to use SQLScript for the calculated column, or the calculation logic may need to be rewritten to be compatible with SQLScript.
  
  
  Solution:
  
  Check the Calculation Logic: Review the logic of the calculated column in the InfoProvider. Ensure that it can be expressed in SQLScript. If it uses complex functions or operations, consider