This Hybrid Implementation Support feature enabled us to load data directly from HFM to PBCS using Data Synchronization, another neat feature introduced in the 126.96.36.199 release.
In addition to this scenario, these two features now enable new data integration possibilities, such as:
- Other On-Premise Applications to Cloud Data Synchronizations (PBCS, EPBCS, FCCS)
- Cloud applications to On-Premise Application Data Synchronizations
- Cloud Data Export to Custom Application (file)
- On-Premise ERP, Data Warehouse, Database or File to Cloud Applications.
- Cloud Application to On-Premise ERP writeback
Configuring Cloud support
To enable a secure communication channel with the cloud the PBCS Secure Sockets Layer (SSL) Certificate needs to be added to the on-premise FDMEE WebLogic server.
The configuration steps are detailed in the FDMEE Administration Guide 188.8.131.52.200, Deploying Hybrid EPM Applications section, found online at: http://docs.oracle.com/cd/E57185_01/nav/datamanagement.htm
Adding a new Cloud Target Application
Once the configuration is done and the FDMEE service is restarted a new target application option is available to be added.
You first enter the connection details to your PBCS pod. We experienced a few snags with this initial connection, mainly due to that the SSL configuration on the FDMEE server had not been done correctly at first. Another undocumented issue we ran into was that the URL needed a forward slash at the end.
Once these issues had been resolved the connection worked and we were able to successfully add the new target application.
Notice the Deployment Mode!
Setting up Data Synchronization
Once the new target application is created, FDMEE treats it like any other EPM application and the setup is identical to setting up an on-premise application, such as adding import formats, locations, and data load rules.
The first thing to configure, as with any new FDMEE data source, is a new Import Format.
Select the Source Type as EPM and select your source on-premise application. Select Target Type as EPM and select the new Target Cloud Application. Once you click Save you then need to map the Source dimensions to the relevant Target dimensions. Note that all dimensions of your PBCS application are displayed. However, you only need to map the dimensions that are used in your target Plan Type. You select your target plan type when creating the data load rule.
Now go ahead and add a new Location and select to use the newly created Import Format.
Data Load Rule
Now navigate to the new Location using the POV toolbar, select the Data Load Rule task and create a new data load rule.
This is where you select your Target Plan Type.
As this is not a file-based load rule we need to define the source query, in this case, what data we want to pull from our HFM application.
On the Source Options tab, you need to add Source Filters for all the dimensions of your source application. You can use the Select buttons for each dimension to define the member or member function to use, such as selecting all base members under a parent.
The last step we need to do is to add maps for all our relevant target dimensions following the usual FDMEE mapping logic as described in a couple of our previous blogs.
Congratulations, you are now ready to start using this Location and Data Load Rule to extract data from your on-premise HFM application and load it to the cloud.
Want to ask one of our experts a question? Contact us today.