Performance Architects Insider’s Guide to Oracle’s Planning and Budgeting Cloud March 2019 Update
Oracle recently released the March 2019 update to Oracle Planning and Budgeting Cloud. This update is currently scheduled to be applied to non-Production instances on Friday, March 1, 2019, starting 23:00 UTC (18:00 EST), and applied to Production instances on Friday, March 15, 2019 starting 22:00 UTC (18:00 EDT).
The highlight of the update is that it brings no new features to the service. Instead, the release contains fixes to issues from the February 2019 (19.02) update to the service. The details of these fixes can be found in the My Oracle Support portal.
Even though there are no new features in this update, it is advisable to test all processes in the non-Production environment after the update is applied, because it is always a good idea to verify that nothing unexpectedly changed.
Other than these fixes, the following rules are being discontinued from the Enterprise Planning and Budgeting Cloud version of the service, in the Capital Planning framework:
Calculate All Existing Intangible Assets (OCX_ Calculate All Existing Intangible Assets) – This rule is now obsolete. Use this rule instead: OCX_Calculate Intangible Asset
Calculate All Existing Tangible Assets (OCX_ Calculate All Existing Tangible Assets) – This rule is now obsolete. Use this rule instead: OCX_Calculate Tangible Assets
Oracle is also releasing new learning paths for Planning and Budgeting Cloud with this release:
This update also provides a video for those who “want to know more about the methods underlying Predictive Planning so they can be more confident of their forecasts…This video takes a look behind the scenes at the statistical forecasting methods that are applied to the variety of historical patterns found in Planning data.”
Have any questions about how to work with these changes in your Oracle Planning and Budgeting Cloud environment? Leave a note below this post or email the Performance Architects team and we’ll follow up with you directly.