Do you have any question about this error?
Message type: E = Error
Message class: RSR_PE - TREX Planning Engine
Message number: 060
Message text: Logging BADI for InfoProvider &1 is not PAK enabled; cannot run in PAK
InfoProvider &1 contains logging BADI. This prevents the whole scenario
from running as SAP HANA-optimized in PAK.
As described in SAP Note 1637199, this logging 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.
Either deactivate the logging BADI or modify it<(>,<)> so that it can
run as SAP HANA-optimized in PAK. See the standard SAP documentation or
SAP Note 1802658.
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.
RSR_PE060
- Logging BADI for InfoProvider &1 is not PAK enabled; cannot run in PAK ?The SAP error message RSR_PE060 indicates that the Logging BAdI (Business Add-In) for a specific InfoProvider is not PAK (Performance Analysis Kit) enabled. This means that the system cannot run the logging functionality in the context of PAK, which is used for performance analysis in SAP BW (Business Warehouse).
Cause:
- BAdI Not Implemented: The BAdI for logging is not implemented or activated for the specific InfoProvider.
- InfoProvider Configuration: The InfoProvider may not be configured to support PAK logging.
- Version Compatibility: The version of the InfoProvider or the BAdI may not be compatible with PAK.
Solution:
Implement the BAdI:
- Go to transaction
SE19
(BAdI Implementation).- Check if the BAdI for the specific InfoProvider is implemented. If not, you may need to create an implementation for it.
- Ensure that the implementation is activated.
Check InfoProvider Settings:
- Go to the InfoProvider settings in the Data Warehousing Workbench (transaction
RSA1
).- Verify that the InfoProvider is configured to support PAK. This may involve checking the settings related to logging and performance analysis.
Update or Upgrade:
- If you are using an older version of SAP BW, consider upgrading to a newer version that supports PAK logging for your InfoProvider.
Consult Documentation:
- Review the SAP documentation for the specific InfoProvider and the BAdI to ensure that all necessary configurations are in place.
Contact SAP Support:
- If the issue persists after checking the above steps, consider reaching out to SAP support for further assistance.
Related Information:
By following these steps, you should be able to resolve the RSR_PE060 error and enable logging for your InfoProvider in the context of PAK.
Get instant SAP help. Start your 7-day free trial now.
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_PE058
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 ...
RSR_PE061
InfoProvider &1 contains virtual char. or key figure; cannot run in PAK
What causes this issue? InfoProvider <(>&<)>1 contains virtual key figure or characteristic <(>&<)>2.System Response ...
RSR_PE062
InfoProvider &1 contains key figure &2 with aggr. &3; cannot run in PAK
What causes this issue? InfoProvider <(>&<)>1 contains key figure <(>&<)>2 with a standard aggregation <(>&...
Click on this link to search all SAP messages.