Hello Everyone,
To give you the most out of SAP Profitability and Performance Management Cloud (SAP PAPM Cloud), we have increased the versatility of our application by allowing you to use your own database as the foundation for your SAP PaPM Cloud subscription.
Yes, you read it right. you can now Bring Your Own Database(BYOD) to be the underlying database of your SAP PAPM Cloud subscription.
But what are the databases that we can use for the SAP PAPM Cloud subscription? To use this BYOD approach, you should have an existing:
Before I discuss the procedure on how you can make use of the BYOD, allow me to address some possible questions that might be helpful for you to understand more what is BYOD.
Note: Below is just a guide and must not be treated as a substitute of SAP PAPM Cloud Administration Guide. To ensure up-to-date information of the steps, always refer to Administration Guide for SAP Profitability and Performance Management Cloud.
As supplement of the blogpost for Entitlements and Default Plan Subscription. You may find the new option in Entitlement for: Plan byod, see example below .
Add the service Plan then Save Changes.
Once the entitlement is added, you may now proceed on the Database mapping of your SAP PaPM Cloud BYOD subscription. I have separated the two(2) procedures for Standalone HCDB and DSP HCDB.
Standalone HCDB needs to map the CF organization GUID and CF space GUID. To achieve the mapping and subscription you may follow the steps below:
1a.) In the subaccount’s navigation menu, choose Instance and Subscriptions.
1b.) Choose Create.
1c.) Provide the information below in the displayed popup window:
Attribute | Value |
Service | Choose “SAP Profitability and Performance Management Cloud”. |
Plan | Choose “byod (Subscription)”. |
1d.) Choose Next.
1e.) You are directed to the next page. In the Choose your PLAN once again field, select the “byod” option from the dropdown list.
1f.) The SAP HANA Cloud Database ID field is displayed. Choose I (SAP HANA Cloud Database ID: More Info) to see the CF organization GUID and the CF space GUID for both the Standard Model and the Universal Model.Remember
As these GUIDs are required for the subsequent instance mapping steps in SAP HANA Cloud, we recommend to copy them.
1g.) Perform the steps below to map the instance in SAP HANA Cloud:
In the popup window that appears, mark the Apply changes without a restart option, then choose Save Changes.
For more information, you may see Map an SAP HANA Database to Another Environment Context.
1h.) Once mapping is done, you may now get the SAP HANA Cloud Database ID to finalize the subscription on the next step.
Note: For Standalone HANA Cloud, get instance ID from SAP HANA Cloud Central, see image below for reference:1i.) Enter the Instance ID you just have copied in the SAP HANA Cloud Database ID field and choose Next then Create.
After this step, subscription screen will pop up and you can close it then wait for the Processing Status to finish. Then you will be all set with SAP PaPM Cloud using your own Standalone HCDB!
Subscription of SAP PAPM Cloud with DSP HCDB has a similar step from Standalone HCDB. Even so, I will still be putting here the steps in case you will be using Datasphere as your BYOD.
2a.) In the subaccount’s navigation menu, choose Instance and Subscriptions.
2b.) Choose Create.
2c.) Provide the information below in the displayed popup window:
Attribute | Value |
Service | Choose “SAP Profitability and Performance Management Cloud”. |
Plan | Choose “byod (Subscription)”. |
2d.) Choose Next.
2e.) You are directed to the next page. In the Choose your PLAN once again field, select the “byod” option from the dropdown list.
2f.) The SAP HANA Cloud Database ID field is displayed. Choose I (SAP HANA Cloud Database ID: More Info) to see the CF organization GUID and the CF space GUID for both the Standard Model and the Universal Model.
Note: By design, only SAP_PAPM_UM HDI can be used here in HDI Container mapping to SAP Datasphere.
Standard Model artifacts reside in a schema(not in a container) which can be leveraged by SAP Datasphere like any other Open SQL schema.
The SAP_PAPM_SM_HDI_* container, on the other hand, is mainly for SAP Analytics Cloud (SAC) and is not intended for SAP datasphere use. DWC roles are not set up on this container. Hence, an error will arise during deployment if you attempt to deploy the space using the SAP_PAPM_SM_HDI_*container.
2g.) Customer would need also to request the mapping of HDI Container to SAP Datasphere. Information can be found via 3057059 - Mapping HDI Container to SAP Datasphere.
2g.) Customer would need to perform the mapping of HDI Container on SAP Datasphere by following the steps below:
For more information, see Enable SAP HANA for SQL data warehousing on Your SAP Datasphere Tenant
2h.) Get the database ID of your SAP Datasphere by following the steps below:
2i.) You may now proceed on adding the SAP HANA Database Instance ID and finalize the subscription of your SAP PaPM Cloud BYOD plan with DSP HCDB.
Similar from the steps of Standalone HCDB, a subscription screen will pop up and you just need to wait for the Processing Status to finish and now you will have your SAP PaPM Cloud BYOD with DSP HCDB.
Easy right? I hope this blogpost helped you get enough information to prepare you for BYOD. Happy Modeling your use cases in SAP PAPM Cloud – whether with runtime database or on your own database. Both will still be fun!
See you in our next blogpost!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |