Is our BPC version eligible for the BPC4HANA migration? How can the BPC environment move from the current landscape to SAP BPC 11.1 for BW/4HANA? What do we get from moving to SAP BPC11.1 for BW/4HANA?
These are the top three questions we receive from customers when discussing potential SAP BW/4HANA roadmaps and the impact on their BPC solutions. This blog attempts to help customers understand the options available to them.
What are BPC customers getting from moving to SAP BPC11.1 for BW/4HANA?
Although SAP’s primary strategic solution for planning is SAP Analytics Cloud, it is important to note that SAP Business Planning and Consolidation continues to be a key part of SAP Analytics portfolio, especially for stand-alone on-premise deployments.
SAP Business Planning and Consolidation Road Map November 2019
And, the SAP BPC11 for BW/4HANA version is getting most of the attention in terms of recent innovations and production direction
Each customer, depending on where their journey starts, will get a distinct flavour of SAP BPC11.1 benefits. With HANA adoption, customers can expect a better performance for processes that are run on the HANA Database layer, such as data integration and data retrieval in reporting.
With BPC11.1, users will benefit from a modern UI and enhanced visualizations with web reporting using SAP Belize. They will also be able to use SAP BPC Embedded Models with tighter integration with BW/4HANA
Is the customer BPC version eligible for the BPC4HANA migration? What are the paths to BPC 11.1 for BW/4HANA?
SAP provides distinct paths to SAP BPC11.1. However, only BPC 10.x solutions on NetWeaver are eligible to be converted to SAP BPC11.1 for BW/4HANA.
Points of Attention:
- BPC 11.1 has the same BPC features as BPC 11.0, which means it’s purely a technical/platform upgrade, no migration effort is expected from BPC side.
- SAP does not provide a migration solution for customers on BPC Microsoft or add-on for S/4HANA (optimized). Therefore, a new BPC implementation will be required.
- When migrating the BPC environment to BPC11.1, the model type can’t be changed. In other words, a standard model will remain the same post migration to BPC11. Therefore, a new BPC implementation will be required to use the embedded model type.
What is the recommended migration path to SAP BPC 11.1? What does it concretely mean in terms of preparation, realization and deployment?
BPC 10.x Customers on NetWeaver platform will be able to migrate their standard and embedded models to BPC11.1 for BW/4HANA using two conversion types:
- Remote Conversion is based on the new installation of SAP BW/4HANA, and enables the transfer of selected objects including transaction data from SAP BW 7.3 on any database to a new SAP BW/4HANA system
The recommended path to SAP BPC 11.1 for BW/4HANA will depend of two main factors:
- What is my BW/4HANA migration path? Does the customer need a brand-new BW/4HANA system?
- What is the existing BPC model type?
Let’s take two scenarios into consideration:
Customer A is running on SAP BW 7.5 powered by SAP HANA with BPC 10.1 environment on Embedded Model type.
This BW version is using objects already compatible with SAP BW/4HANA (Advanced DataStore Objects, Composite Providers, etc.), meaning that the system is almost ready for the final transition to BW/4HANA. Therefore, the In-place Conversion in the existing system is the highly recommended way to go for SAP.
In this case, our recommendation would be to follow an In-place Conversion approach for BPC environment.
At the same time as the system conversion to BW/4HANA, the existing BPC environment will be converted to be objects compatible with SAP BW/4HANA using Transfer Cockpit
The sequence below provides an overview of the activities for the Preparation, Realize and Deployment phases when performing an In-Place Conversion to SAP BPC11.1 for BW/4HANA of an Embedded Model.
The main point of attention when going for the In-Place conversion is the risks on the production downtime, as the existing system is fully converted.
Customer B is running on SAP BW 7.4 with BPC 10.0 environment on a Standard Model type.
Converting the current BW system to BW/4HANA (In-Place conversion) is a possible option, but would require tremendous effort and time spent to complete the BW upgrades to 7.5 and then BW/4HANA, transfer to HANA-optimized objects, etc., increasing risks on business disruption, thus resulting in longer production system downtime. Therefore, Remote Conversion into a brand-new BW/4HANA system is the highly recommended way to go for SAP.
In this case, our recommendation would be to follow a Remote Conversion approach for BPC environment.
Following the installation of a new SAP BW/4HANA with BPC4HANA add-on, the BPC environment (Standard Model type) will be backed-up and restored from the existing production system. The migration program ‘UJT_MIGRATE_101_TO_BPC4’ is integrated into the BPC environment restore, which means the data migration will be executed automatically when running the restore function.
The sequence below provides an overview of the activities for Preparation, Realize and Deployment phases when performing a Remote Conversion to SAP BPC11.1 for BW/4HANA of a Standard Model.
The key benefits of this approach are the risk mitigation and reduced production system down time due to system parallelization. It also gives a good opportunity to carve-out the BPC environments relevant going forward. The counterpart is it requires an additional hardware for a new SAP BW/4HANA system.
This topic and associated activities should not be underestimated. It is extremely important to plan the upgrade path comprehensively and identify areas of risk that could affect the engagement. In particular, it is important to consider the significant disruptions that could arise if the wrong conversion approach is taken, or if insufficient time or inexperienced resources are used on BW and BPC activities.