Deploying SAP Analytics Cloud

In modern SAP environments, SAP Analytics Cloud (SAC) is considered as the default analytics tool. Earlier we have discussed how you should plan SAC deployment. In this article, we look into the main aspects of the deployment that you should take into consideration.

Deployment possibilities

Each company might have a quite unique approach to data warehousing, analytics, reporting, planning and visualisation. In some cases this solution stack might be built on top of multiple vendors’ products over a long period of time, which also usually means that data is being replicated and scattered across multiple different systems. 

When migrating to S/4HANA, it is a good point to rethink how this stack should be constructed in order to simplify the landscape and better meet the future demands. This is why planning in advance is the key. Here we discuss a couple deployment options from where to continue with different starting points for SAC. 

S/4HANA already in use

If S/4HANA has already been implemented earlier and the SAC is being introduced into the scope afterwards, SAC provides unique capabilities to support gradual implementation and leavering existing developments in the SAP landscape. For example, SAC could be rolled out as the primary front end for reporting while still utilising existing data models and queries from SAP Business Warehouse (SAP BW), SAP BW/4HANA or SAP Business Objects via live connection. Progressing this way, business users can be introduced to SAC and get them involved with new user-friendly ways and tools for carrying out analytics without first reworking everything natively to the new SAC system. Any new development needs, such as reports and planning solutions, can be implemented to SAC utilising the systems planned in to-be architecture.

One driver for the to-be architecture could be for example cloud transition, which in SAP landscape would mean that data warehousing is moving towards SAP Data Warehouse Cloud (DWC) from on-premises SAP BW. This transition is supported with SAP BW Bridge for Data Warehouse Cloud.

SAC as part of a S/4HANA migration

If SAC is planned to be implemented as part of a S/4HANA migration, the deployment can depend on the S/4HANA change impact. In some cases S/4HANA migration can be seen almost as a pure technical SAP version upgrade, although to benefit more on the S/4HANA migration, some process changes should be implemented as well. In this approach, SAC can be deployed in similar fashion as in the previous example.

When S/4HANA migration is approached more as a transformation where additional benefits are sought for by redefining business processes and leavering new S/4HANA capabilities and perhaps also changing the financial reporting model details or the company is moving to SAP S/4HANA from other ERP platforms. S/4HANA and SAC deployment could be considered as greenfield implementations.

Depending on business and data storage needs, SAC deployment can stretch to support reporting, analytics, planning and data warehousing needs. In big data warehousing needs coming from non-SAP sources, a dedicated DWC or BW/4HANA should be considered for data storage while SAC would handle reporting, analytics and planning needs. Especially in greenfield type implementations, free SAC accelerators can reduce required development time and costs. In the SAP analytics world these accelerators are known as business content and they are industry and line of business specific predefined stories, dashboards and data models for existing SAP data sources (like S/4HANA and BW/4HANA to name a few). Business content can be used as they are or they can be leveraged at starting point when fulfilling individual requirements.

Impacts on data pipeline architecture

Whichever deployment approach is chosen, it impacts the data pipeline architecture. Ensure that the documentation clearly shows what data sources you will be using in SAC. It is important to identify potential sources of data duplication and ways to address them, review master data management processes and analyse user requirements on data granularity level and data refresh frequency when imported data is involved. If the SAC deployment has phasing in use regarding data sources or structures, it is important to keep the business users updated about the changes.

Execute the plan

Make sure that the deployment approach for SAC has been analysed for pros and cons, risks identified and mitigated and the phasing is aligned with the overall S/4HANA migration plan. Thorough planning is the key to success and helps meeting the set goals. When executing the plan, keep all business and IT stakeholders involved along the deployment phases.

Change management

It is important to consider the following aspects in planning the change from end user’s perspective:

• Identify key business cases to address in communications and training. The cases should showcase data modelling, data visualisation, planning and predictive analytics.

• Conduct initial user testing within main groups – for example, Finance, Tax, Internal Control – early in the deployment phase to identify training needs. The testing results will help you create role-based training materials that address detailed use cases in planning and analytics.

• Setup a channel to gather enhancement ideas from end users and report any issues during the pilot phase. Our team can help you with deploying SAC as a part of S/4HANA migration and ensuring smooth transition to a modern analytics environment.

This blog is a part of PwC blog series on SAP Analytics Cloud deployment.

Authors:

Alexandra Shtromberg
Peitsa Helin