Infosys’ blog on industry solutions, trends, business process transformation and global implementation in Oracle.

« Telecommunications as a Service | Main | Automating file based data loads for Hyperion Cloud applications »

Write-Back of Budget Data from PBCS to Fusion-GL through FDMEE

Introduction

PBCS is the latest release from Oracle which is a user friendly tool with less amount of efforts needed to the taken care from a developer point of view. It has been made so user friendly to developers that there is no need of installation and maintenance that needs to be performed. Only creation of application and artifacts which are required in a functional perspective needs to be developed.

For PBCS there are few ways to load data into the application.

1)   Loading directly through planning data load utility, by creating a load file in a planning format and loading into application.

2)   Through EPM Automate Utility, in this the load format file can be uploaded to planning INBOX and from there the automation can be done to load into planning application.

3)   Through Data Management (FDMEE), in this we can integrate the source application with the target application by creating the mappings between two systems.

Post loading source data into the PBCS application, and after performing budgets in Hyperion Planning application, we can write back the budget data to source system through Data Management (FDMEE).

 


Brief level of writing back of budget data from PBCS to Fusion GL.

Steps to create of Write back of budget data from PBCS to Fusion GL.

As a start first extract all the information required from Fusion environment to map with PBCS. We are required with Ledger IDs, Accounting calendar, Ledger currency and Chart of Accounts.

Login into Fusion cloud system, and after logging in from NavigatoràToolsàSetup and Maintenance, search for the task Manage primary ledgers. And note down the information regarding the Ledger IDs created in Fusion GL, which are required to map in FDMEE to a target Hyperion Planning application.

Once all the information has been gathered now login into PBCS workspace.

Login into PBCS, click on Navigateà AdministeràData Management as per below.

PBCS Cloud Workspace.png

From Data Management, setup the Source system as General-ledger.

Note: Both the Source and Target system naming convention should be the same.

Setup the Target Application as below General-Ledger, the application type while creating should be Custom Application, and map all the dimensions.

Note: Custom Application is the one which extracts the data from PBCS.

Map the Account dimension to Budget Name and Ledger as Entity, which are required in future while performing data load mappings.

Mappings.png

Set up the Import Format.

Create the Location for the respective Import format by selecting General-Ledger as a Target application from the list of applications.

Set up the Period Mappings for the General-Ledger application and select Application mappings. And select the target application from the list of applications as General-Ledger.

Set up the Category Mappings to Budget.

Note: The Category name should be the same as per the Fusion GL Category name.


Create a Data load rule as per below.


Data Load Rule.png

After creation of Data Load rule, create the data load mappings.

Note: Budget Name should be mapped to Accounts, and Ledgers (Ledgers are the Entities in Fusion GL application, which define the business areas), should be mapped to Entities in PBCS as per below.

And map all rest of the dimensions to fusion segments.

Mappings1.png

After all the setups are done, below is the process of writing back the budget data from PBCS to Fusion GL.

 

Login into PBCS, click on NavigateàAdministeràData Management as per below.

From Data Management go to workflow tab and click on Data load rule.

Select the required Location, period and Category.

POV.png

Click on Location to select. Select the Location, select the Category as Budget. And for period select the period for which budget data needs to be written back to GL.

Data can also be filtered by applying filter options to each dimension members, so that only restricted data can be written back for only particular combinations.

Click on Execute option to load data.

Another window appears as per below screenshot. Select the options required Import from Source (which import the data file from PBCS). Export to target (which exports the data to Target system Fusion GL). Select period and Import mode as required.

Rule.png

Click on Run, and after running FDMEE provides and Process ID which can be viewed from Process Details tab as per below.

Process Details.png

Click on Refresh option to refresh the data load process.

Refresh.png

From Data Load Workbench below.

Data Load Workbench.png

In data load workbench all the steps of data loads are in Orange color, which states that data has been loaded successfully, and also we can reconcile the data loaded in export mode as per below screenshot.


Data Load Workbench1.png

Metadata Members and data columns are divided into different columns.

Data Load Workbench2.png

Now to view the same data in Fusion GL, Connect to Fusion GL URL workspace: -

After Connecting, navigate through NavigatoràToolsàScheduled Process

From Schedule process, check that whether Validate and Upload Budgets schedules have been running and succeeded. These are the schedules which run after data has been written back from FDMEE to Fusion GL.

Once these schedules are succeeded.

Go to NavigatoràGeneral Accounting àFinancial Reporting Center.

From Financial Reporting Center go to Tasksà Balance InquiryàInquire of Detail Balances.

From the detail balances screen, first select the Data Access set for which the data needs to be viewed. And select all the combinations of members from each segments.

And for scenario member select the Budget member, as data written back from PBCS will be stored in Budget member of Fusion GL.

Once all the segment members have been selected, the data can be viewed.

And data can also be compared between two systems PBCS and Fusion GL for reconciliation.

Note: The process of Writing back of Budget data from PBCS to Fusion application helps in maintaining the Budgetary Control. As Planning applications are mainly for budgeting the data and after budgeting if that data is written back to Fusion for an example below.

Example: If an end user orders to buy a Computer, and if he enters an entry for 40K, then if the budgeting authority must have fixed the price of computer to 35K, then the user gets an alert that the computer price exceeds beyond the limit which is the data from PBCS. And so he can send it further for exceptional approval process. In this way Write-Back helps in configuring the Budgetary Control.

Reference:

Oracle Hyperion Planning and Budgeting Cloud Services admin guide.

https://docs.oracle.com/cd/E60665_01/pbcs_common/CSDMA/ch02s02s04s05.html

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles