TopDown Blog

Tag: FDM Mapping

Working with FDMEE v11.1.2.4 and the .200 Patch

By on June 13th, 2016

Recently, we’ve implemented FDMEE version 11.1.2.4 at a major client. This client has been using FDM classic version 11.1.2.x for many years and needed to upgrade to version 11.1.2.4 for compliance and maintenance support reasons. When we started this project, we installed the base version of FDMEE 11.1.2.4 with the .100 patch. Through the course of our implementation we ran into some noteworthy findings that we’ll discuss in this blog post. Our guideline for the FDMEE build was to use built-in functionality and be fairly vanilla, so avoid any custom coding.

FDMEE / FDM – Map One Source Account to Multiple Target Accounts

By on March 8th, 2016

What do you do when one line item provides more information than only one destination Point of View? For instance, assume that all of the trial balance accounts from an extract will load to a custom dimension member of “END”. However further assume that the trial balance has multiple members, typically in a custom dimension, for the balance sheet accounts that record movement.

Using FDMEE Multi Dimension Mapping

By on March 1st, 2016

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.”

FDM / FDMEE Mapping – General Principles

By on February 24th, 2016

Let’s discuss the basic fundamental purpose of FDMEE. That is to say mappings. FDMEE has come a long way since its origins, and is at this stage is an ETL-like tool (Extract Transform Load). Mapping is the “T”, Transform, part of this acronym. This is where source system, typically General Ledgers, metadata members are transformed to a destination EPM application dimension member. Think of these as accounts, entities, cost centers, product members, and so on.

© Copyright 2019 TopDown Consulting. All Rights Reserved.