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 | 05 29, 2016 | EPM, FDM, FDM Classic, FDMEE
Recently, I was training a new FDMEE administrator at a long-standing client. We spent most of the day covering every nuance of his company’s application – everything from data load workbench to GL integration with the open interface adapter. Around 4 o’clock in the afternoon we wrapped up and he said, “Doug, this was great! I think I’ve got a handle on things. I’m wondering, is there a some sort of ‘FDMEE for Dummies’ book I can get for reference.” My response: “Funny you should ask. There is now.” This past spring, Tony Scalese published the first ever non-Oracle FDMEE Book – The Definitive Guide To Oracle FDMEE. The book nicely fills the void between Oracle’s FDMEE Administrator’s Guide and Oracle’s FDMEE training course. Unlike Oracle’s own FDMEE admin guide, this book has some worthwhile anecdotal information to complement the technical detail you’d expect. If you’re new to the world of FDM, or an experienced FDM Classic administrator looking to get up to speed on FDMEE, The Definitive Guide To Oracle FDMEE offers up lots of useful information. Check it out. Note: For you e-book folk, currently the book is only available in paperback. The publisher says the e-book will be available sometime before the end of...
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 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...
by Doug Correa | 03 07, 2016 | EPM, FDM, FDM Classic, FDMEE
The FDM Migration Guide contains several FDM Artifacts and their Equivalents tables. The tables display a listing of the main FDM Classic artifacts and their counterparts in FDMEE. The tables also indicates if the Utility can convert each particular artifact to FDMEE. The information tables are a quick and easy way to understand old world to new world components and the migration options for each Legacy FDM component that you currently use. Right away, you can see the Migration Utility cannot migrate some artifacts, such as scripts, report objects, and security (User Maintenance and Object Maintenance) to FDMEE. Here’s a listing of some of the artifacts you will have to rebuild from scratch in FDMEE. Scripts Reports Security Batch Processing Task Flows For most upgrade projects, the most time-consuming effort is re-developing scripts for FDMEE. FDMEE uses Jython as its primary scripting language. For more information on re-writing scripts for FDMEE, see Your Top 6 FDMEE Scripting Questions, Answered. Next: Part 5 – Rebuild vs. Migration Utility: Pros and Cons Blog Series: Choose the Best Way to Migrate FDM Classic to...
Recent Comments