Recent Posts

Archive

Tags

No tags yet.

SAP BPC Version for NW on HANA: Uncovered


Communication is key. Understanding relevant SAP terminology is the fundamental principle for conversing in the industry. Accurately transposing technical topics across functional and tech teams is the foundation for project success. The cruciality of precisely conveying the subject at hand should go without saying. However, many times tech and functional team members fall short on embodying this notion. And depending on the magnitude of the conversation, this could be just a small blimp or detrimental to the task at hand. Working in SAP for the past 5 years, I know how common it is to misrepresent a system issue or requirement due to the sheer complexity of the environment in play – which is no different in the SAP BPC arena. In an aim to educate and mitigate potential confusion, this blog will break down an SAP BPC version for NetWeaver (standard model) on HANA environment using the EPM Add-In as the frontend reporting tool, primarily from a reporting lens.

To set the stage, let’s start with the backend which, for this blog’s purpose, consists of the Application and DB layer.

Backend:

Most commonly, the backend is referred to as both the application and the database. However, they’re independent of one another and to ensure precision in communication, they should be called out separately.

Within the application, we have the Product, NetWeaver and amongst others, the following installed software components: BW, CPMBPC & HANABPC. In the standard model of BPC, there is no modeling done within BW. The work takes place in the BPC Web Client which is then passed down to the data warehouse. The BPC component (CPMBPC) is compiled of a series of t-codes (all starting with UJ), tables, programs, etc. enabling SAP Business Planning and Consolidations to be possible. HANABPC is an additional component required and a pre-requisite to make your environment a BPC powered by HANA system. Once the HANABPC component is installed, you will need to run program BPC_HANA_MIGRATE_FROM_10 in SE38 and flip the value of parameter ENABLE_ACCELERATOR or ACCELERATOR_ON to “X” or “Y”, to enable a BPC powered by HANA system. Further HANA functionality can be leveraged once this step is complete - for example, passing the MDX parsing / execution down to HANA via the ENABLE_HANA_MDX parameter.

While the above is just an example of what one environment could look like, it’s vital to understand exactly how your system is configured to: communicate across functions and throughout organizational levels, efficiently troubleshoot, understand resource needs and to work with SAP on issues – to name a few reasons.

This blog won’t be going into much detail on the HANA DB (or the Web Client). The only aspect I want to reiterate to those who work in the industry, the HANA DB is where the data is originally stored and unless caching is in affect above the DB, each call will need to fetch data from HANA.

Frontend:

The EPM Add-In, in its core, is nothing more than an Excel Add-In. While it’s a client install like Analysis for Office, unlike AO, EPM doesn’t have a dedicated server or separate platform outside of the application and DB layer. It’s purely a stand-alone client tool. Users log-in via an HTTPS entry to initially connect to the application servers. If an individual decides to save an EPM report to the server, they will be saving to the File Store via the UJFS t-code, in the BPC component of NetWeaver. EPM reports and the tool itself should not be referred to as BPC, as that’s incorrect and will mislead colleagues & management.