Keeping up with EPM Cloud

If you’ve ever tried to send a direct link to a PBCS form or dashboard, you’ll know that it’s not as simple as copying the URL from within the webpage. This usually ends in an error or directs the recipient to the PBCS home page, instead of to the intended form or dashboard. Luckily, it is in fact possible to send a direct URL for a specific PBCS form or dashboard, but we must construct the URL in a precise way. This blog details how this can be done. The URL template differs slightly depending on whether you want to open a Form or a Dashboard. Data Forms: https://virtualhost/HyperionPlanning/faces/LogOn?Direct=True&ObjectType=FORM&ObjectName=FormName&POV=M1,M2 Dashboards: https://virtualhost/HyperionPlanning/faces/LogOn?Direct=True&ObjectType=DASHBOARD&ObjectName=DashboardName&POV=M1,M2 Where the parameters for the URL are as follows: ·          Virtualhost – this is the PBCS Instance URL (eg...

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...

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 ...

As well as staging table data, Data Management/FDMEE stores various setup components in SQL tables behind the scenes. We do not have direct access to these tables in PBCS, however there are a number of ‘System Maintenance Tasks’ within data management which can be used to update and maintain these hidden tables. This blog will focus on the ‘Maintain Setup Data’ task only. Maintain Setup Data This task is useful to clean up the setup component tables, including clearing invalid import formats, data load rules or locations from data management. Occasionally, “phantom” artefacts seem to get stuck in the background tables, with no way of deleting them from the front-end. For example, if there are rules which are selectable from the Workbench but do not appear in the Data Load Rules list and therefore can’t be removed. When this happens, the ‘Maintain Setup Data’ task can resolve the issue, providing a way to view and remove these stuck artefacts. There are ...