Exporting Financial Management Data into Essbase Using Data Management


Hello! Welcome to this step-by-step tutorial on Exporting Financial Management Data into Essbase using Data Management. This demonstration was created using a desktop recording application. Starting in Data Management, select the Setup tab. First, I’ll register my Essbase BSO target application. For Type, select Essbase. I’ll be exporting to the Basic database in my TS-STAT application. Let’s take a look at the Application Details. The Dimension Details tab lists the dimensions you can export to. The Target Dimension Class, is determined by the dimension type. The Data Table Column Name contains the name of the column in the Data Management staging table. Click Save. The target application name is listed using the Essbase application name and the database it will be exporting to. Next, I’ll define an import format. Import Formats determine which data columns are extracted from the source system and how they are stored in Data Management staging tables. The name identifies the import format when you assign it to other configurations such as location. Descriptions are optional. Set the source type to EPM and select your source application. For target type, select EPM. Then, select the target application you defined. Drill URLs are not required for this integration. Verify and save your entries. Make sure your import format is selected and scroll down. This is where you define the relationship between your source dimensions and target columns of your custom application. For each row, select the source dimension that maps to the target dimension. You can choose to load data into a specific member by specifying a default in the Expression text box. Now, I’ll add a location. The location links the import format to the source and target systems. Enter a name. Descriptions are optional. Then, select the import format you defined. The source and target systems are selected for you. Verify and save your entries. Let’s talk about period mappings. You use period mappings to match period formats between the source and target system. Global mappings are shared by applications in your EPM System. The mappings that you create on the Application Mapping tab apply to the target application you select. In this example, I added a mapping named Mar 07 using the 3/1/2007 Period Key. The target period month is set to March, and the year target is set to 2007. On the Source Mapping tab, I’m adding an explicit period mapping between the Quarter1 period key used by my Financial Management source application and the March 2007 period in my target Essbase application. Save your entries. Let’s create data load mappings. Make sure you select the location you defined and the period you’ll be importing from. You use data load mappings to derive the target members for each dimension based on source values. You must create a mapping for each dimension you want to export. Options available in the Dimension drop-down list depend on the dimensions you configured in your import format. In this example, I’ve created mappings using the Like and Explicit mapping types. Save your entries. Let’s create our data load rule. You run data load rules to push data into target applications. First, verify that you have the correct location and POV selected. Enter a data load rule name. Descriptions are optional. Select your category and period mapping type. You can filter the data you want to import using Source Filters. In this example, I added a source filter for the Scenario and View dimensions. In Source Parameters, make sure the extract type is set to Data and click Save. When you execute the data load rule, make sure Import from Source & Export to Target are selected, and verify your period selections. The Status column displays the current state of the import and export process. Click Refresh until you see a checkmark. I’ll navigate to the workbench to view the results. The data is staged in Data Management prior to exporting to Essbase. Now, let’s take a look at the exported data in Essbase Administration Services Console. I’ll run a report script to verify that data was loaded. The data was loaded to my Essbase application. In this tutorial, you saw how to export Financial Management data into Essbase using Data Management. To learn more, visit cloud.oracle.com.

One thought on “Exporting Financial Management Data into Essbase Using Data Management

  1. Thanks this give us a high level of data movement. I am new to the FDMEE world. Could you please let me know whether the metadata should be synch between the Essbase and HFM before we move the Data ? Any help would be appreciated.

Leave a Reply

Your email address will not be published. Required fields are marked *