When using additional Accounting Scenarios in your Oracle Cloud ERP GL Essbase database to hold non-Actuals data (e.g. Plan, Budget or Forecast data from Planning in the Oracle EPM Cloud (PBCS)), it is occasionally necessary to clear out an entire Accounting Scenario in Oracle Cloud ERP, for example:
- The data is incorrect and must be cleared out
- The data pushed from Planning in the Oracle EPM Cloud (PBCS) was mapped to the wrong version
- The data needs to be overwritten completely e.g. a “Latest Forecast” scenario which is updated monthly
When pushing Plan, Budget or Forecast data from Planning in the Oracle EPM Cloud (PBCS) to a defined Accounting Scenario in Oracle Cloud ERP, the data will only be overwritten for combinations which have non-zero data in the push. This means that if data has been cleared to #missing in the Planning in the Oracle EPM Cloud (PBCS) source data, then existing values in Oracle Cloud ERP will not be overwritten. See my previous blog for more on pushing from Planning to ERP: HERE
Unfortunately, in Oracle Cloud ERP this isn’t as simple as running a business rule to clear out a specified slice of data, unlike in the agile world of Oracle Planning. However (luckily) there is a way!
Important Note! This method of clearing an accounting scenario will clear data for the specified scenario for ALL Ledgers, Accounts, Currencies, COA segments, etc. We are essentially deleting and re-adding the scenario in the Oracle Cloud ERP Essbase database.
To clear out an Accounting Scenario in Oracle Cloud ERP, follow the instructions below:
1. Log into the Oracle Cloud ERP system
2. Go to Tools > Setup and Maintenance
3. Search for Manage Chart of Accounts Value Sets and go to the task
4. Search for Accounting Scenario and click Manage values
5. Search for the relevant Scenario and untick the Enabled box so that it is now blank, to disable this Scenario
6. Click Save
7. Go to Tools > Scheduled Processes and click to Schedule a New Process
8. Search for the process Create Scenario Dimension Members and click OK
9. Under the options select Yes from the drop down for Delete Disabled Members and Dimensions.
10. Then click Submit
11. This will refresh the Oracle Essbase database, deleting the Scenario that was disabled in step 5
12. Go back to Manage Values (step 4) and find the disabled Scenario
13. Tick the Enabled tick box to re-enable the scenario
14. Go to Tools > Scheduled Processes and click to Schedule a New Process
15. Search for the process Create Scenario Dimension Members and click OK
16. Under the options select Yes from the drop down for Delete Disabled Members and Dimensions
17. Then click Submit
18. This will re-add the enabled Scenario back into the Oracle Cloud ERP Essbase database as a new, empty Scenario.
Once this process is complete, the newly added Scenario is empty and ready for data to be pushed from Planning in the Oracle EPM Cloud (PBCS) to Oracle Cloud ERP. In other words, problem solved!
Until next time