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

« Oracle Financial Accounting Hub in Banking Industry | Main | The new improved Multi-Load functionality in FDMEE »

FDMEE - The future of Hyperion Integrations

Part 2

Mappings Redefined

Co Author : Payal Kapoor(payal_kapoor@infosys.com)

In previous part we discussed the recently launched tool FDMEE (Financial Data Quality Management, Enterprise Edition) that was introduced in the EPM release, 11.1.2.3.

In this part we are going to cover some great mapping features introduced in FDMEE that were not available in its predecessor FDM. 

 

 

 FDMEE Mappings: Mapping module of FDMEE allows a user to map the source and target values in different ways. There are 5 different types of mappings available:

1.      Explicit: For each source value there is a target value mapped using this mapping type.

2.      Between: It maps the range of source values to a target value.

3.      In: It maps a non-sequential list of source values to a target value.

4.      Multi-Dimension: This new feature has been added in FDMEE to enable it to map a combination of source values to a target value. E.g. A target account value can be derived based on a combination of source account and entity value.

5.      Like: This mapping uses the wild characters to match a string in the source value and maps it to a target value.

Using the Multi-Dimension mapping feature, various complex mappings can be created in a few clicks.

FDMEE_Blog2_Pic1.png

The above example shows the account dimension members getting mapped based on combination of account member and user defined dimension member.

Bulk mappings can also be created in FDMEE using Map Loader. It is a standard excel template that is now available for download directly from Data Load Mapping screen. The

format is similar to the one in FDM. Using this template, all the source and target values for a dimension can be imported in one go.

Another way to maintain the bulk mappings is through export/import of mappings in Data Load Mapping screen. An xml file is generated using the export that is editable and then can be imported to apply the bulk changes.

In addition to above functionalities, mappings can also be exported to a flat file (excel) directly from the Data Load Mapping screen.

 

FDMEE_Blog2_Pic2.pngMapping script:

FDMEE also has a mapping script that can be used to implement complex mapping logic. Anything that cannot be implemented directly using the above mapping types can be done using a mapping script.

Jython is the scripting language in FDMEE for most of the scripts - including mapping scripts.

Mapping scripts are written inside the "Like" mappings in the following manner: 

FDMEE_Blog2_Pic3.png

Source value: *

Target value: #SCRIPT

Script: Click on the Expression Editor - the script logic is written there. FDMEE_Blog2_Pic4.png  

 

 

 

Comments

Hi Payal,
I came across your blog on FDMEE mapping while researching for information on how to import maps for multiple locations in one file in FDMEE. In the classic FDM, it is possible to do this by specifying the partition key for the different dimensions in the mapping file but I don't know if this is possible in FDMEE. I was wondering if you might have some ideas on how to accomplish this.
Thank you in advance for any information/advice.

regards,
Winsor Li

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