Over the years one of the more challenging things about FDM Classic and FDMEE is that both require a source data file to have one amount value per row. To address this limitation we had to develop some custom solution to pivot the data. See the example below. Finally, we can do away with this custom stuff. In a recent release of FDMEE Cloud – the version of FDMEE that comes with EPM cloud apps such as Financial Consolidation and Close Cloud (FCCS) and Planning and Budgeting Cloud Service (PBCS) – FDMEE can now handle multi-column data loads out of the box. FDMEE Cloud has several new file type formats, including 2 multi-column format options (see the image below). In this blog post we’re going to use the multi-column numeric data format option. Note: The following integration exercise was done using FCCS. First, here’s our multi-column data file with Accounts in the rows and Programs in the columns. We only want to load values for 4 of the eight data columns, those highlighted in red. To start, we want to define our import format, selecting file type: Multi Column – Numeric Data. Now, we go to the import mapping details and map the source columns to target dimensions. On the Amount field, we want to select the Expression Type of Driver. The Add Import Format Mapping Expression dialog box appears. In the dialog box we do the following: Specify the driver dimension: Program. Select the Program dimension members that correspond with each of the data...

Okay, first off, when it comes to the data synchronization feature in FDMEE, we’re not a fan of the name. Being techies, when we hear “synchronization” we think true two-way synchronization. That is, data is compared between two systems and reconciled with the latest changes in System A copied to System B and the updates in System B replicated in System A. That’s not how this works. You use this new FDMEE functionality to copy data from one EPM application to another EPM application. Consider it a one-way sync. So, the name might be a little misleading but this is still one killer feature. In fact, we think it’s the most significant new feature introduced in FDMEE Release 11.1.2.4. Why, you ask? Many of our clients have multi-product EPM environments with both HFM and Planning. And one of the most common monthly tasks is to copy Actuals from HFM to Planning for variance reporting. FDMEE Data Synchronization, more commonly known as “Data Sync”, makes this really easy. Data Synchronization isn’t a component with its own a menu item. Instead, Oracle has baked this functionality into the import format and data load rule components. Here’s a rundown of how to set up. Step 1 – Create your import format. The import format is used to instruct FDM how to interpret the incoming data from HFM. For the source application, pick your HFM application. For the target application, select your Planning application. From there, map the dimensions accordingly. View Image Step 2 – Assign your import format to a new location. Next, create a new location to associate with your new import format....

What happened to my data? Why are my totals off? Why the *@#%! do I have to reload the same set of data AGAIN!? I’ve heard these questions on many-a-implementation involving FDM data loads to HFM and Essbase. Here’s why. Re-loading Trial Balance Data – It’s not uncommon to load trial balance data multiple times during the close. After all, it typically takes accountants and controllers a few passes to finalize their month-end financial information. Supplemental Data – It’s also not uncommon to have information for a single entity come from multiple sources. Consider trial balance data from the general ledger system and statistical data loaded manually via Smart View or data forms. The above data load circumstances can often lead to data integrity issues. This is where a custom FDM data protection solution can help. Data protection is about protecting target system data from being overwritten by multiple data loads to the same point of view. FDM Data Load Options Both FDM Classic and FDM Enterprise Edition (FDMEE) support two data load methods: Replace and Merge. For illustration, consider this example. Statistical data, e.g. headcount and units sold, is loaded once during the close. Conversely, during the same month-end cycle trial balance data is loaded several times as the financial information refined and finalized. Loading Data with Replace Mode When data is loaded using the standard Replace mode, the data for the specific point of view (POV) – Scenario, Year, Period and Entity – is cleared in HFM before FDM loads the new data set. Drawback – All data for the entity is erased. Based on our example,...