KB 205 - PowerConnect Considerations for RISE Deployments
- Stephen Bangs
KB 205 (ABAP): PowerConnect Considerations for RISE Deployments
Category: Information | Priority: Normal |
|---|---|
Platform: ABAP | Version: 1 from 4.06.2024 |
Description
PowerConnect is certified and compatible for SAP RISE. However, there are some versions of SAP that do not support third-party add-on components (most commonly S/4 HANA Public Cloud Edition, and Multi-Tenant Edition). Below is a table indicating support and specific considerations for RISE deployments:
SAP Version | Supported | Special Considerations for Installation |
|---|---|---|
NetWeaver ABAP on RISE | Yes, as long as it is an SAP-supported version | See instructions below |
RISE with S/4HANA Private Cloud Edition | Yes, as long as it is an SAP-supported version | See instructions below |
RISE with S/4HANA Public Cloud Edition | Not supported - SAP does not support any third-party add-on installation in this environment | N/A - Not supported |
RISE - Multi-Tenant - Same Database, Same Schema with Column Discriminator for each customer ID | Not supported - SAP does not support any third-party add-on installation in this environment | N/A - Not supported |
RISE - Multi-Tenant - Shared Database, Separate Table/Schema for each customer ID | Not supported - SAP does not support any third-party add-on installation in this environment | N/A - Not supported |
RISE - Multi-Tenant - Shared Database, Separate Tenant Database for each customer | Not supported - SAP does not support any third-party add-on installation in this environment | N/A - Not supported |
If the customer is deploying PowerConnect in a supported RISE environment, here are specific steps that need to be followed:
The customer needs to confirm that the SAP system has the necessary outbound network connectivity to send data to the observability platform (port 8088 and/or 443).
The customer needs to send a support incident requesting that SAP installs the add-on component in their environment.
The SAP team needs to conduct the SAINT installation on behalf of the customer in Client 000 following these instructions: SAINT Installation.
The SAP team also needs to upload the authorization object transport data and cofiles into the respective application directories (/usr/sap/trans/data and /usr/sap/trans/cofiles): Authorization Object Transport.
The remaining installation steps should be conducted in the productive client by the customer’s team leveraging the provided installation guides: ABAP Installation Guide.