How to Use FDMEE Cloud to Load Multi-Column Data Files to FCCS

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

KScope16 and FDMEE: Everything You Need to Know

KScope, ODTUG’s annual conference for Oracle Developers, was held just a couple of weeks ago.  And Oracle product managers were out en masse to reveal new offerings, application features, and product roadmaps. The Oracle mantra was pretty simple: cloud, cloud, cloud, and more cloud. In fact, if you drank a shot every time you heard the word “cloud” at KScope16, you would have been in a drunken stupor 5 minutes into Sunday’s EPM Symposium. Really, though, this is no surprise. Cloud services was the centerpiece of Larry Ellison’s Oracle OpenWorld 2015 keynote address. So, if you’re a Hyperion customer or implementation specialist using FDMEE what does all of this cloud rhetoric mean for you?  Here’s what you need to know. FDMEE and Hybrid Support Oracle mothership doesn’t see companies taking all of their EPM applications to the cloud right away. In fact, Oracle expects most companies will go for a hybrid approach – a mix of cloud-based applications and on-premises or hosted applications – for the foreseeable future.  In a hybrid world, companies need a simple, efficient solution to collect, transform and load data to all of their EPM applications.  This is where FDMEE comes into play.                       As of Release 11.1.2.4.200, on-premises FDMEE can integrate with on-premises and cloud-based EPM applications.  So, now you can use on-prem FDMEE to load your actuals data to Hyperion Financial Management (HFM) and to load your budgeting and forecast data to Oracle Planning and Budgeting Cloud Service (PBCS).  Yeah, this is kind of a big deal. It’s so significant that we re-worked our Peloton FDMEE Hands-on Training for this year’s KScope to highlight cloud...

How to Use FDMEE Data Sync to Copy Plan Data from HP to HFM

So, you need to copy data from one EPM application to another, specifically plan data from Hyperion Planning (HP) to Hyperion Financial Management (HFM). In a pre-Oracle Hyperion 11.1.2.4 world this could involve a few moving parts: An Essbase report script to export Plan data to a flat file, FDM Classic to transform and load Plan data to HFM, and Technology X, Y, and Z for end-to-end automation With Oracle Hyperion Enterprise Performance Management Release 11.1.2.4 all you need is FDMEE Data Synchronization. Note: Before getting started, make sure your Planning and HFM applications are registered as target applications in FDMEE. Step 1 – Create your EPM to EPM import format. Important: To ensure the data is loaded as periodic vs. year-to-date (YTD), you may need to hardcode “Periodic” Value dimension in the import format. View Image Step 2 – Create a location and associate it with your new import format. View Image Step 3 – Create a data load rule to stipulate data extract parameters. View Image Step 4 – Define the source to target application mappings. View Image Unit test, fine-tune as necessary, and you’re done! Need to copy Actuals to Planning? See How to Use FDMEE Data Sync to Copy HFM Actuals to...

How to Use FDMEE Data Sync to Copy HFM Actuals to Planning

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

Part 6 – Legacy FDM to FDMEE: Where to Start

As you can see from the previous posts in this series, there are some complexities when going from FDM Classic to FDMEE.   If your company ever did a conversion from Hyperion Enterprise (HE) to Hyperion Financial Management (HFM), conceptually, it’s a similar effort.  Both HE and HFM are used for reporting and consolidations but are distinctive tools. When considering your upgrade project, we recommend engaging a consulting team with the following qualifications: Referenceable experience with Legacy FDM to FDMEE upgrade projects A solution architect with deep FDM Classic and FDMEE expertise A documented audit and migration process A consulting partner team with proficiency using the FDM Migration Utility You and your consulting organization will collaborate to determine the most effective method for upgrading your FDM Classic applications. The Utility can deliver a tremendous advantage when upgrading a large volume of FDM artifacts. A complete rebuild also has its advantageous. Depending on your Classic apps, a rebuild can be the faster, more direct way to FDMEE. If you do use the Utility, don’t overlook the opportunity to perform some spring cleaning. Also, we suggest introducing some simple enhancements to get your FDM end users more excited about making the leap to FDMEE. Blog Series: Choose the Best Way to Migrate FDM Classic to...