Strategic Modeling, as the cloud version of Hyperion Strategic Finance, is a forecasting product that creates a comprehensive financial statement with out of the box treasure capability, scenario analysis, debt modeling and robust consolidation capability. It allows you to quickly understand the major impact of the strategic decisions on your future financials which is valuable for the C suite, investors, and higher level people that analyzing the company.
To have a better understanding of Strategic Modeling, check the following previous post.
EPM Cloud Lab – Configure Prebuilt Frameworks 5 – Strategic Modeling
Even though Strategic Modeling is a standalone product for financial statement forecasting and modeling, you typically have a planning application at the same time to help you manage the detailed budgeting and forecasting processes, and make more tactical decisions. Being said, having a better integration solution to transfer data back and force between strategic modeling and planning is critical.
This time, we would take a look at a few integration solutions. Each of them has their own strength and limitations, utilizing different solutions together could be a better approach. We will check the following three hot topics.
- Data Map/ Smart Push
- Excel Map Loading
- Groovy Rules
1.Data Map / Smart Push
The common option is always Data Map. To learn more about Data Map and Smart Push, check the previous post.
Using Data Map, we will be able to push data between Strategic Modeling and Planning. The two options are:
- from a Strategic Modeling model or consolidation to a Planning cube
- from a Planning cube to a Strategic Modeling model
For strategic modeling, there is an advanced option. It defines complex mappings to/from multiple dimensions to/from a single dimension and between members. Advanced data map options are available only if Strategic Modeling is enabled and is a source or target in the data map. Also, keep in mind that, only administrators have privileges to create, edit, and run data maps.
When we use data map, the following dimensions are automatically mapped:
Model/Entity: Model in Strategic Modeling, and Entity in planning
We can select multiple models as a target. Multiple selections must have a one to one mapping between model and entity
Scenario/Business Case: Scenario/Business case(if the source is a consolidation) in Strategic Modeling, and Scenario in planning
Multiple selections must have a one to one mapping between Scenario in Strategic Modeling and Scenario in planning
Account: Account in Strategic Modeling and in Planning. We can select multiple accounts.
Account members with the same name are automatically mapped (based on the Description in Strategic Modeling and the Name in planning)
Dimensions with the same name:
Other dimensions are in the Unmapped Dimensions list.
For example, from planning to Strategic Modeling, map multiple dimensions to a single dimension
Check the detailed account map.
Data Map can be triggered by Strategic Models and Consolidations.
Models:
Consolidations:
2.Excel Map Loading
If we need to manage complex mappings, to simplify defining an advanced data map, we are able to use Microsoft Excel to define the data map.
From the web, we see the following tabs.
From the Excel map loading file, we see similar tabs.
Update the mappings and then load them back.
3.Groovy Rules
The Data map is a good option. However, it does have limitations. If our target is a planning cube, when we open up a planning form, we cannot run a Smart Push when saving the form. Because Smart Push will be using the current data form as the source and push data to somewhere else. In our case, we would like to push data from Strategic Modeling to the current planning form. Also, another example is, if the source is an ASO cube, the data map or smart push cannot work.
Groovy rules provide the flexibility to move data as we expected. We could create Groovy rules in Calculation Manager. It is available with Enterprise PBCS or PBCS Plus One licenses. We are able to run Groovy rules:
- on the Rules page
- within the context of a form
- using job scheduler
- in Dashboards and task lists
- using EPM Automate
To learn more on Groovy, check the previous post.
Groovy Lab – Groovy in EPM Introduction (EPBCS & Hyperion)
We will be creating the groovy rules from two directions.
- Planning to Strategic Modeling
- Strategic Modeling to Planning
The general logics of creating these Groovy rules are:
- Get the Planning cube, define the data region, and build the data grid definition
- Build the Planning grid, and collect data based on the grid definition
- Form the Strategic Model grid based on the Planning grid and include calculations
- Save to Strategic Model
Planning to Strategic Modeling
Firstly, we push data from Planning to Strategic Modeling.
The data cells are:
Create Groovy rule to push data to Strategic Modeling.
After running the rule on save, we can see the data has been pushed to 2019.
Strategic Modeling to Planning
Similarly, push data from Strategic Modeling to Planning.
The data cells are:
Create Groovy rule to push the data to Planning.
After running the rule on save, we can see the data has been pushed to FY20.
Hopefully, these data integration options give you some new ideas. Happy modeling and see you next time.