In a SAP BPC standard environment, the main interface to input data is MS Excel. In order to communicate with your SAP BPC model, the BPC EPM Add-in needs to be installed. In some cases, it would be an advantage to avoid this installation on all BPC users’ laptops. Here are some reasons:
SAP has released a full integration scenario between SAP Analytics Cloud and SAP BPC Standard (as of version 10.x). This scenario gives the opportunity to avoid installing the EPM Add-in for each user. Next to your BPC input forms, you can create SAC input forms available via your internet browser and communicating with your SAP BPC model.
Implementing this scenario is quite straightforward and should respect 3 main steps:
After enabling the communication between your BPC system and SAC in the SAP Cloud connector you can create a new SAP BPC connection.
When creating your connection, you will need to enter your BPC server address and port. The BPC user entered here will be used to transfer and import data.
This scenario is until now available for BPC Standard model only. An integration with BPC embedded is planned in the future SAC releases.
Once your connection is created, you need to import your model from BPC:
In order to be able to input data in SAC and publish them to BPC, you should select the option below :
Before Importing the model, you need to set the dimension mapping between your Source BPC dimensions and your SAC target dimensions. As BPC Standard is an account-based model, you need to identify a dimension type for each dimension (Account, Generic, Organization, Version and Time). This mapping is very important as you cannot change it easily afterwards.
Once your model is imported and saved, an initial synchronization will be executed. Your BPC model is now ready to be used in SAC:
With the help of Sap Analytics Cloud planning functionalities, we have Today a solution to input data in BPC in an easy and efficient way via your internet browser and without the need of an extra installation on your laptop.
Furthermore, SAC offered you planning functions like allocation and distributions that can fulfill most of the planning requirements.
Last year, our colleague Nico wrote a blog post on how to use the Open Hub technology in SAP BW to export BEx Query results. This was a handy solution as there was no need to store any additional data in the system and the Open Hub system is easy to deploy and use.
The blog ended with a list of limitations that would prevent you to use certain queries as an Info Provider and thus are unable to be used as a source for data transfer via Open Hub.
At one of my previous projects we ran into one of these limitations: they wanted to export the data from a set of queries that contained two structures. Alas, we could not enable these BEx Queries as Info Providers and had to scratch Open Hub from our design card. Due to this set back, we went back to a much older SAP BW component: the APD or Analysis Process & Designer. This a workbench that can be used to analyse, create and execute analysis processes.
However old this technology might be, you are able to use almost all (older) BW components as data source: Characteristic attributes, DSO’s, tables, flat files…
Read more >
That is the deadline when you are running a BW version 7.4 or older. SAP will end the mainstream maintenance for older BW products and encourage companies to move to newer versions, preferably BW/4HANA. If you read this and find yourself in this situation, don’t panic. Politicians would say that it’s way past 5 before 12. Luckily, we are consultants and see a solution instead of a problem.Read more >
Before starting my career in IT, I almost never went to online forums. However quickly after starting my career as an IT’er I came across multiple forums/communities in which I became (and still am) active.Read more >