by Doug Correa | 07 13, 2016 | EPM, FDM, FDMEE
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...
by Doug Correa | 04 19, 2016 | EPM, FDM, FDMEE
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...
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 | 03 07, 2016 | FDM
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...
by Doug Correa | 03 07, 2016 | EPM, FDM, FDM Classic, FDMEE
Since the release of the FDM Migration Utility in September 2015, we’ve worked on several FDM Classic to FDMEE upgrade projects. We’ve elected to use the Utility for a handful of those implementations. Why? Rebuild Experience Oracle debuted FDMEE Release 11.1.2.3.0 in Spring 2013. The FDM Migration Utility was delivered more than 2 years later. During this time, you can say, we’ve become pretty good at rebuilding FDM Classic artifacts in FDMEE. We know the success factors for FDMEE upgrade projects. We’ve developed our own methods and home-grown utilities to accelerate the rebuild process. Most importantly, we know the benefits of rebuilding FDM in FDMEE from the ground up. There’s additional justification for manually re-creating all FDM content from scratch. Spring Cleaning and Simple Application Enhancements Remember the last time you moved from one place to another? Maybe it was a local move to a bigger place or maybe you moved to a different state for a new job. Either way, one of the major tasks when moving is determining what stays and what goes. If an item is useful – it gets packed. If it isn’t, it gets purged. Think of your upgrade from FDM Classic to FDMEE in the same way. Most Legacy FDM applications can benefit from some spring cleaning. Spending the time to examine your existing FDM Classic application(s) and associated processes can yield some worthwhile benefits. The main objectives of the application evaluation phase of your project is: Purge Outdated Content – Minimize application clutter by omitting outdated artifacts. Enhance Existing Integration Processes – Look for opportunities where FDMEE can offer a more efficient or effective way...
Recent Comments