SAP PaPM Cloud – Modeling Environment LifeCycle & Promotion
We are in the last leg of 2021, and I am back to hopefully answer some of your questions related to SAP Profitability and Performance Management Cloud (SAP PaPM Cloud) such as:
“How many tenants shall we subscribe into?”
“Shall we have multiple tenants or just one?”
“What is the transport strategy?”
To help others who are about to subscribe to SAP PaPM Cloud, let me share with you some strategies that you can consider while deciding which option is the best fit for your project.
Before I go straight to the point, let me give you some overview so you can understand better the rationale of the options that I am about to offer you —- SaaS or Solution as a Service approach eliminates implementation of SAP Note, upgrade or patching of the solution. Unlike in the On-Premise world where you as a customer decides when to implement solution related enhancements and changes, in the Cloud you will get new features and enhancements automatically without the need to worry about catastrophic technical implemenetation issues.
If you are not so technical and not aware of this approach, in the on-premise world, for every bug fixed, you or your administrator will have to decide if the note must be implemented or not. Same goes if there is a new support package or release, you will need to decide to patch or upgrade. So to capture possible issues with these implementation decision,
a DEV → QA → PRD system landscape setup is usually being suggested to ensure proper testing before reverting or implementing the changes into PRD (productive system).
Now the question is, do we need to do this 3 system landscape too in the Cloud version of SAP Profitability and Performance Management?
In the Cloud version you have 2 options to consider.
- Customers can use one tenant approach
- Customers can use multiple tenant (minimum 2) to split between development and production
Single Tenant Approach
SAP Profitability and Performance Management Cloud Solution offers a single tenant approach, this means you as a customer can subscribe into one tenant where environment modeling happens, while it is also the productive system where “live” calculation or processing happens.
Since we already eliminated the risk wrapped around note implementation or component patching as I described awhile ago, we can now focus on deciding whether single approach is better for you or not by weighing on the complexity of the content you are building and the requirements being requested by your stakeholders.
Please take note that there could be lots of factors that can be considered before deciding between single or multi, but below scenarios are some factors that can make you decide to go to Single Tenant Approach:
- the modelers who built the calculation logic of SAP PaPM Cloud are also part of the business users who will run the solution upon go-live. With this you dont need to worry that the possible productive datarecords are to be seen by modelers.
- If the modeled environment is not expected to be going through iterative implementation – meaning no changes is planned anymore from the released modeled environement version. Of course during live use it is not advisable that the same Environment and Version is being enhanced to avoid stability issue during productive use.
- If the datamodel connected is stable and not expected to be adjusted in the future or is not an external source. Unstable and external datamodels are prone to uncontrolled model adjustment. And regular adjustment to the datamodel can cause issue to the productive calculation environments and logics which can cause irregular calculation outputs too.
Multiple Tenant Approach
In case above approach seems to be not fitting well in your scenario or implementation requirements then, SAP Profitability and Performance Mangement Cloud still offers the tranditional Multi-tenant approach.This means you can subscribe to multiple tenants (one tenant per subaccount) under one Global account to have the DEV → PRD structure —- minimally two tenatns to separate Development with Productive environment and data. You can also decide to have 3 to 6 tenants just like in the On-Premise world if that is what you prefer.
I can imagine that next questions under multi-tenant setup are:
“How to import from one tenant to another in SAP PaPM Cloud?”
“Is the usual truck button, and SAP TMS work too?”
With this I want to give you a clear statement that the traditional SAP TMS or Transport Management System is not to be used in SAP PaPM Cloud. Instead, SAP PaPM Cloud is introducing Content Network, where you can download the created environment into a form of zipped json file and upload the same file into the next tenant. To know more about Content Network, check the published help documentation.
Alright, now that my blog post is almost at the end, I hope you are now more aware about the flexibility PaPM Cloud can offer including tenant/s setup.
I know it might be new for others, hence if you still cannot decide which option to take, I suggest that you check with your architect or deployment manager the approach that is better for your implementation project.
Thank you for reading through and good luck with your implementation activity. Til my next post!
Be safe everyone!