Do you have any question about this error?
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
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.
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.
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.
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 simplifying it or breaking it down into multiple steps.
- Implement SQLScript: If possible, implement the calculation using SQLScript. This may involve creating a new calculation view or modifying the existing one to ensure that it can be executed in SQLScript.
- Use Standard Functions: Ensure that the functions used in the calculated column are supported by SQLScript. Refer to the SAP documentation for a list of supported SQLScript functions.
- Recreate the InfoProvider: If the above steps do not resolve the issue, consider recreating the InfoProvider with a focus on ensuring that all calculated columns are compatible with SQLScript.
- Consult SAP Notes: Check for any relevant SAP Notes or updates that may address this issue. Sometimes, there are known issues or patches that can resolve specific error messages.
Related Information:
By following these steps, you should be able to address the RSR_PE058 error and ensure that your InfoProvider is functioning correctly with SQLScript.
Get instant SAP help. Start your 7-day free trial now.
RSR_PE057
CRs in InfoProvider &1; cannot run scenario as SAP HANA-optimized
What causes this issue? InfoProvider &1 contains characteristic relationships that prevent the whole scenario from running HANA-optimized in PAK....
RSR_PE056
InfoProvider &1 with data slice &2; cannot run scenario in PAK
What causes this issue? InfoProvider &1 containing data slice &2 prevents the whole scenario from running as SAP HANA-optimized in PAK.System...
RSR_PE059
Cube &1 contains CR &2 of type "hierarchy". Cannot run scenario in PAK.
What causes this issue? InfoProvider &1 contains character relationship &2 of type "hierarchy". This prevents the whole scenario fr...
RSR_PE060
Logging BADI for InfoProvider &1 is not PAK enabled; cannot run in PAK
What causes this issue? InfoProvider &1 contains logging BADI. This prevents the whole scenario from running as SAP HANA-optimized in PAK.System ...
Click on this link to search all SAP messages.