SAP BPC for S/4 HANA – Consolidation set up from a technical standpoint
This blog talks about a quick overview on the consolidation set up that has to be done from the BPC front-end through S4 HANA 1610.
In BPC Classic model, Dimensions and Data models within environment where defined in the BPC front end. Data load used to happen from BW to BPC with multiple data staging and the data transformation and conversion also takes place in BPC. Data manager packages are available for the planning functions that are aided with logic scripts for customizations.
Then embedded analytics was leveraged and BPC embedded modeling was introduced in which the model was not created directly in BPC front end but by linking the info providers created in BW.
With Simple Finance, IBPF was introduced which aids Financial Planning in the transaction system and no Legal or Financial Consolidation. With 1610, IBPF was named as ‘BPC optimized for HANA’ where BPC is an add-on and the Real Time Consolidation (RTC) was introduced with tight integration with BPC Embedded model.
The RTC model is created in S4 Finance in SPRO. This model is then integrated with the BW info Providers. These providers are virtual objects and hence there will be no data load from transaction to the BI system.
The universal journal ACDOCA is the source for the transaction data. The consolidated data in turn is written back to the table ACDOCC.
The following should be set-up in the BPC front-end once the BW modelling is complete:
- Dimension and Model mapping
- Ownership Manager
- Business Rules
- Task Sequences
- Consolidation Monitor
- Journals (Optional)
- BPF (Optional)
Dimensions and Model Mapping:
After logging onto the BPC portal, go to the Administration tab and select ‘Models’.
Provide the name of the model and link the composite provider created in the BW model. Then click the ‘Review Mapping’ option. (You will have to link the Ownership model with the same steps)
In the Review Mapping, Link the aggregation Level to allow the dimension values to map to the BW info Objects. Further click on Review mapping to map all the BPC properties to the BW attributes.
For example: map all the mandatory properties to the attributes as shown for the Dimension – ‘Audit’.
Ensure that all the required dimension types for Consolidation (A,T,E,C,S, I, D, R and G) are mapped, else the system wont allow you to proceed further.
Additional settings: Additional parameters which include – Integration Mode, Inter company and dimensions having compounding objects (Fiscal Year Variant, Chart of Accounts) have to be maintained in ‘Additional Settings’.
Once done, the consolidation and ownership model will have a ‘VALID’ status.
Note: once all these settings are done, we will have to activate the RTC Model (which is created in the t-code RTCMD).
Please note that the settings here are similar to the Classic BPC version. But we do not need Logic Scripts to call the Business rules via DM packages, the business rules will process automatically through the consolidation monitor.
Are a set of rules defined, to allow the consolidation process to calculate and post some monetary amounts through accounting activities such as – Net income calculation, Inter company Eliminations, currency translations etc.
Methods and Method Based Multipliers are defined –
And then we can define the required business rules such as – Net Income Calculations, Inter company Eliminations, Balance Carry forward, Consolidation of Investments, etc.
Note: The 1610 version gives you an option of performing currency conversion in S4 system itself, rather than the BPC front-end. It is recommended that it is performed in S4 system through the t-code RTCCT.
We can define Business rules as shown below.
Once completed, the Business rules will have a ‘Valid’ status against them.
The Ownership manager is used to maintain the share-holdings of each Entity, based on a selected Category and Time. It can be set in the Consolidation tab -> Ownership Manager.
As shown below, each entity and its holdings are defined based on a Category, Fiscal/Year and Group.
the holdings are defined based on the Methods and Method based multipliers defined in the business rules.
This is a new feature added to the Embedded model. here we define the sequence in which each business rule has to be executed for the consolidation to process.
Task sequences are defined to provide the sequence in which the Business Rules should be executed. (For ex: Net Inc cal, Carry Forward, Eliminations, consolidation of investments)
Note: Ensure that the Controls are also enabled for the Business rules to function.
The Consolidation Monitor can be executed under the tab Consolidation -> Consolidation Monitor.
This in-turn calls the business rules defined in the back-end and validates the rules during execution.
Click on Execute. The job can be checked in ‘Display Running Processes’ or further can be monitored in sm37.
Once completed, the status will be marked as ‘Done’.
The data should now be written back to the ACDOCC table.
Journals and BPF’s are optional depending on the business requirement, and the set-up is very similar to the Classic model.
Analysis for Office Reports can also be built on top of the BPC model. Planning mode in the report enables write-back to the ACDOCC table in S4.
Finally, the consolidated data would be available in ACDOCC table.
Good one Lavanya
Thank you Ravindra
Any idea as to why the data from ACDOCA isn't read into UNION view which is called into Virtual provider and composite provider? While we can post and read records from ACDOCC but not able to read records from ACDOCA. We have tested the foundation view for Actual. In there, we can read the actual data from ACDOCA but not further upwards.