In FDMEE, multidimensional mappings are most commonly used to map a Source Value from one dimension to a Target Value from another dimension. This can be very useful in reducing the amount of scripts used in an application. A source value is the value (Account, Entity, etc.) that comes from the file you are importing through FDMEE. The target value is the value you would like that source to hit in HFM or Planning. You should make all mapping changes and adds in FDMEE or Notepad++.

There are two types of Source to Target Multidimensional mappings, “Like” and “Explicit”. Multidimensional mappings with the condition, “Like”, are not one-to-one. For example, if you want any source Entity “1*”  (any Source Entity that’s value begins with 1, a * signifies that to be a wildcard) to be associated with Target Account 300800, you would use an “Like”, multidimensional mappings.

Like Multidimensional mapping:

 

To create the following multidimensional mappings, go into the Account dimension (whichever dimension your target value is going to), under the Multidimensional mappings tab and click Add.

Rule Name (A001): The order of precedence that FDMEE reads the rules is alphabetically, starting with A, then alphanumerically, starting with zero.  Rule Names chosen should be based on the order FDMEE reads them.

Dimension (Entity): The dimension that your source value is in.

Condition (Like): Like implies that there is a group of source entities, such as 1*.

Value (1*): The source value.

Explicit Multidimensional mapping:

If the Value (200945) is explicitly stated (there is one value), choose “Explicit”, rather than “Like”.

Using a Target Value:

It is also possible to associate a target dimension with another target dimension. This means that you can use the target value of one dimension as the source value of another, using multidimensional mappings. Using notepad ++ or your text editor is the only way this can be done. For example, if you have Target Account values beginning in a 1* in the file you are importing through FDMEE to export into HFM or Planning to target Entity 4150, you will type them in as the following in Notepad++:

     ENTITY, #MULTIDIM ACCOUNTX=[1*], E-4150, E102,,

The “X” after the ACCOUNT specifies that the Entity mapping looks at the Target Value in Account rather than the Source Value. If the “X” was not present after the Account (i.e. ENTITY, #MULTIDIM ACCOUNT=[1*], E-4150, E102,,) then the mapping would look at Source Account value rather than Target Account value.

To import the mapping from Notepad++, you will first type in your mappings as stated above in Notepad++. The file you are loading needs to be delimited correctly. You can double check this in the Import Format Mappings for where you are trying to load the mappings to.

Once your file is ready with your mappings, you will go to Data Load Mappings and Import the file. If the file has mappings for one dimension, such as the example above, you will choose Current Dimension. If the file contains mappings for multiple dimensions, you will choose All Dimensions.

Use multidimensional mappings as a solution to solve many large mapping needs and to significantly reduce the overall number of maps needed. Any way to reduce the number of maps is a positive win, as we all know how tedious mappings can be!

Questions?  Comments?  Feel free to reach us at:

Brittany Peterson, bpeterson@ecapitaladvisors.com

Courtney Belden, cbelden@ecapitaladvisors.com

Courtney Belden

As an experienced consultant with eCapital Advisors, Courtney Belden specializes in delivering client success via collaboration, technical excellence, and client empowerment. Courtney has a background in Hyperion Planning, Essbase, cloud technologies, automation strategy, and FDMEE & Data Management solutions. Courtney has strong customer relationship management skills and a passion for helping organizations achieve measurable business results.

Leave a Reply

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