In old FDM if there was ever a need to source two fields for an exception mapping, it was required to write a script to resolve this issue so that the scripted member would then be able to be mapped accordingly. For instance, there might be a Long-Term liability account in HFM, “AccruedTax”, that in almost all instances is sourced from a G/L account, 290100. Let’s say however, that there is one exception to this based upon the Entity, “WestSales”, where instead of being a long-term liability, this instead is a long-term asset for HFM, “LongTermDefTaxAsset.”
Assume that the data extract from the G/L looks like the following:
In FDM this would have required an Import Script to indicate the exception. For instance the script would have to pull the Entity and then the Account fields for this exception. In FDMEE there is a much simpler solution. This is in the mapping type “Multi Dimension.”
Keep in mind that there is a sequence in mappings, such that five mappings types have precedence. The mapping types are:
- Multi Dimension
Where 1, “Explicit,” has the “first say” precedence. That means that is there is a mapping that could apply to Explicit and is also in Multi Dimension, that the Explicit Type would already exist and be ignored in the Multi Dimension mapping. Also there is an alpha numeric precedence where a similar mapping named A1000 would precede B1000 and 1000 would precede 1001 named mappings. With this in mind we do not want a default “Explicit” mapping as this would “trump” the Multi Dimension mapping, but we could have a default “Like” mapping, as this takes lowest precedence. In this example, I will use the alpha numeric sequence within the Multi Dimension Type mapping.
For the Location that requires this mapping, navigate to Workflow > Data Load Mapping > Dimensions – Account and then select the Multi Dimension tab. Click on the Add icon.
The first example is to perform the exception mapping. This I have named 290100 with the Target Value my exception account LongTermDefTaxAsset. Click on Add to display the Dimensions and conditions. The first line will be for the Account, and since this is on the source account 290100, it is an Explicit condition. Click Add to add the Entity dimension, and this again is an Explicit case for WestSales only. If there were a few other exceptions, the “In” mapping could be used to identify those, separated by a comma. Once completed, click OK.
Next the default condition is added so that this would likewise be displayed. Because of the alpha- numeric precedence this is name with a lower sequence. From the Multi Dimension mapping, click the Add icon to add another Multi Dimension mapping.
Here this is named z290100, so that this default is preceded (trumped) by the specifc 290100 Multi Dimension mapping. The Target is the default account condition, “AccruedTax”. The account again is explicit, but the entity is now a “Like” condition, where the asterisk, “*”, is a wildcard for all. Click OK.
Now let’s review the results in a Data Load process. Note that for the account 290100 only that for the Entity “WestSales” goes to account “LongTermDefTaxAsset”. This has been resolved via a mapping rather than scripting!
Need help with your next EPM project? Contact our team today.