by Doug Correa | 10 26, 2016 | EPM, FDM, FDM Classic, FDMEE
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...
by Doug Correa | 03 28, 2016 | EPM, FDM, FDMEE
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....
by Doug Correa | 04 16, 2014 | FDM Classic, FDMEE
Oracle Enterprise Performance Management (EPM) Release 11.1.2.3 includes the debut of Hyperion Financial Data Quality Management Enterprise Edition, dubbed “FDMEE”. For existing Hyperion customers, FDMEE represents the evolution of Financial Data Quality Management (FDM). (The soon-to-be-retired Windows-based data integration tool has now been re-branded “FDM Classic”.) With 11.1.2.3, existing Oracle Hyperion customers have a choice: you can continue to use FDM Classic for one last go-round or you can go to FDMEE. For new customers, your only option is FDMEE. With the release of 11.1.2.4 and beyond, it’s FDMEE – no ifs, ands, or buts. For those customers using a previous release of Enterprise Resource Planning Integrator (ERPi), FDMEE is a big leap forward. Oracle states that FDMEE represents the integration of both FDM Classic and the former ERPi. Really, though, Oracle integrated the look-and-feel and overall functionality of FDM Classic into ERPi and re-branded it FDMEE. From FDM Classic, you get most of the key features you’ve come to rely on: Workflow Process (Yes, you still have your gold fish, one for each Workflow step, i.e. Import, Validate, Export, and Check.) Locations Mapping Tables (now “Member Mappings”) Import Formats Validation Entity Groups (now “Check Entity Groups”) Validation Rules Groups (now “Check Rule Groups”) Batch Loader (now “Batch Execution”) Scripting – Import format Scripting, event scripting, and custom scripting File-based data loads From the ERPi side, here are the main features incorporated into FDMEE: Like previous versions of ERPi, FDMEE is fully baked into the Oracle EPM Workspace portal Support for direct data integration with general ledger (ERP) source systems Drill Through from EPM target applications back to transaction-based...
Recent Comments