In Oracle EPM Planning, we often have a requirement to move data from one cube to another. Earlier, we mostly used calculation scripts or other data movement processes for this purpose.
For example, we may need to move data from BSO to BSO, or more commonly from a BSO planning cube to an ASO reporting cube.
In newer versions of Oracle Planning and EPM Cloud, we have a useful feature called Smart Push which makes this process much easier.
What is Smart Push?
Smart Push allows us to move data from one cube to another directly from the Planning application.
For example, let's say we have:
Plan1 – BSO Cube
This is where users enter data and calculations are performed.
Reporting – ASO Cube
This cube is mainly used for reporting and analysis.
After users enter or update the data in the BSO cube, we can use Smart Push to move the required data to the ASO reporting cube.
So the flow will be:
Plan1 (BSO) → Smart Push → Reporting (ASO)
This is much easier compared to creating and maintaining separate calculation scripts just for moving the data.
Using Smart Push with Data Forms
One useful thing about Smart Push is that we can associate it with the data form itself.
Smart Push can be used with Planning forms, including Simple Forms and, depending on the Planning version and configuration, Composite Forms.
We can define what data needs to be moved and map the source and target dimensions accordingly.
Run Smart Push When the Form is Saved
Another useful option is Run on Save.
When this option is enabled, Smart Push will run automatically after the user saves the data form.
For example:
User enters data → Saves the form → Smart Push runs → Data moves to the target cube
This is useful when we want the reporting cube to receive the latest data immediately after users update their planning data.
If we don't want Smart Push to run every time the form is saved, we can also allow users to run it manually when required.
Where I Find Smart Push Useful
In my experience, Smart Push is particularly useful when we have a BSO cube for planning and calculations and an ASO cube for reporting.
Instead of creating a separate process every time we need to move data, Smart Push gives us a simpler way to push the required data from the Planning form.
Of course, calculation scripts and other data movement methods are still required in many situations. Smart Push doesn't replace every data movement process.
But when the requirement is simply to move the required planning data from one supported cube to another, Smart Push can make the process much easier.
Things to Check When Configuring Smart Push
Whenever I configure or troubleshoot Smart Push, I normally check:
- Source and target cubes
- Dimension mappings
- Members selected for the data movement
- Smart Push data region
- Run on Save option
- User access and security
- Job status if Smart Push fails
If Smart Push is not working as expected, checking the mappings and the selected data region is a good place to start.
Final Thoughts
Smart Push is a simple but very useful feature in Oracle EPM Planning.
Earlier, we depended more on calculation scripts and other processes to move data between cubes. With Smart Push, we can configure the data movement as part of the Planning form and push data when required.
It is especially useful when working with a BSO planning cube and an ASO reporting cube, where users need their latest planning data available for reporting.
I am documenting this here based on my Oracle EPM experience, and I will continue adding more Smart Push tips and troubleshooting scenarios as I come across them.
Thanks,
Mady
