Posts

Showing posts from July, 2019

Write Back Budgets from PBCS to Fusion ERP Cloud

Image
As explained in my previous blog on loading Actuals from Fusion ERP Cloud to PBCS , the GL Actuals data is stored in an ASO Essbase cube, referred to as the GL Balances cube. What we didn’t cover in the previous blog is that, as well as holding the GL Actuals values, this Essbase cube can be configured to also hold Budget and/or Forecast data, which can be sourced from PBCS. The main advantage of doing this, is that the Budget and Forecast data would be available alongside real-time Actuals for FRC/OTBI reporting. Integration Pre-requisites Before this integration can be setup in Data Management: The ERP Essbase cube must have been created using job ‘Create General Ledger Balances Cube’ when configuring the ERP system Budget/Forecast Scenarios must be added to the CoA via ‘Manage Chart of Accounts Value Sets’ tasks Scenarios must be deployed to the ERP cube using job ‘Create Scenario Dimension Members’ – these should be visible in Smart View under the ERP Scenario...

Loading Actuals from Fusion ERP Cloud to PBCS

Image
If you’re looking to set up a data load of Actuals from ERP to PBCS and have heard this is an “Out of the box” integration, then good news! Not only is the OOTB connector included within PBCS Data Management but the integration is simple to setup and to schedule using EPM Automate. This blog will detail how to setup the ERP to PBCS connector in Data Management and some of the common errors found when running the data load. The first thing to know about this integration is that the data source is actually the ASO Essbase cube which sits underneath the Fusion ERP tables, holding the period Actuals values. This ERP Essbase cube is created using job ‘Create General Ledger Balances Cube’ when configuring the ERP system. This cube must be created before the integration can be set up correctly and can be accessed directly via Smart View for reconciliations. Set up the Source System As this is an Oracle built connector, it’s as simple as providing a name for the source system ...