by Doug Correa | 09 04, 2014 | FDM, FDM Classic, FDMEE
FDMEE PSU 520 is Here! Oracle has released FDMEE Patch Set Update (PSU) 11.1.2.3.520. You can download PSU 520 from the My Oracle Support portal. PSU 520 applies to all supported platforms for FDMEE, including Windows, Oracle Solaris, and Linux. See the corresponding Read Me file for details on My Oracle Support. Features and Fixes Galore PSU 520 fixes a fair number of reported defects – 50 in all. Patch Set Update 11.1.2.3.520 also introduces 5 new features for FDMEE. One feature creates even greater parity between FDM Classic and FDMEE – Point-of-View Locking. POV Locking The inclusion of Point-of-View (POV) Locking will be of great interest to customers considering an upgrade from FDM Classic to FDMEE. As FDM users are aware, locking the POV prevents locations from modifying their data. For many FDM customers POV locking is an integral part of the close. I’ll have more info on this feature in a future blog post as I have a couple of clients upgrading from FDM Classic to FDMEE that rely on this feature. Updated Admin Guide An updated FDMEE Administrator’s Guide hast been released. You can find the .520 administrator’s guide on the Oracle EPM Release 11.1.2.3 Documentation Library. I’ll keep you up to date on findings as I test 520 in our lab...
by Doug Correa | 06 17, 2014 | EPM, FDM, FDM Classic, FDMEE
One of the great things about FDM is scripting. Sometimes certain actions cannot be performed by standard application functionality alone. That’s where scripting comes in. You can customize and enhance your FDM application with scripts. Scripting is vital to nearly all FDM Classic applications I’ve worked on. So, when it comes to FDMEE, you keep hearing about this new scripting language called “Jython“. You’ve got other questions, too. Here are answers to your most common FDMEE scripting questions. 1) When we upgrade from FDM Classic to FDMEE, will we need to rewrite our scripts? Yes, some of your scripts will need to be re-written. Learn More Unlike FDM Classic which exclusively uses VBScript, FDMEE offers various scripting options depending on the type of script. The following diagram shows a breakdown from Old World (FDM Classic) to New World (FDMEE). It’s possible to leverage existing FDM Classic event scripts and custom scripts when upgrading to FDMEE. I’ve done it before. But you’ll have to re-develop your import scripts, mappings scripts, and custom scripts. 2) So, the de facto scripting language for FDMEE is Jython. What is Jython? Jython is the Python scripting language integrated with the Java platform. Learn More You can find plenty of resources out there for Jython programming. Check out Jython.org for starters. Also, the FDMEE Administrator’s Guide has several Jython script examples to get you started. 3) For our upgrade, we have to transform some of our existing FDM Classic scripts from VBScript to Jython. How difficult will this be? It shouldn’t be too hard. To precisely gauge the level of effort requires an audit of your...
by Doug Correa | 06 11, 2014 | EPM, FDM, FDM Classic, FDMEE
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,...
by Doug Correa | 05 29, 2014 | FDM, FDM Classic, FDMEE
Oracle Hyperion EPM folk know that Financial Data Quality Management Classic (FDM Classic) is the ideal data transformation tool for getting your data into Oracle Hyperion applications. But it takes some effort to get things up and running. In particular, installing and configuring FDM adapters (FDM Classic software modules for communicating with target Hyperion apps) can be a chore. Well, Hyperion target application setup is different with FDM Enterprise Edition (FDMEE). FDMEE makes things a lot easier. FDM Classic Setup Here’s a rundown of how things typically go in the FDM Classic world. Your infrastructure resource installs the FDM Classic software. Now, you’re ready to create a FDM Classic application. You can do this via the FDM Classic web console. After you create a new application, you need to configure FDM to communicate with your Hyperion target applications. For this, you use the Workbench Win32 desktop client. Most likely, you’re using Workbench on the FDM application server. Using Workbench, you perform Steps 1 through 4. You execute Steps 5 and 6 on the web. Register the adapter file (e.g. fdmFM11XG6C.dll) , Import the corresponding metadata interface file (e.g. FM11X-G6-C.xml) , Configure COM settings for the adapter, Add a machine profile, Specify the application name in Integration Settings, and Validate that FDM Classic is communicating with the target app FDMEE Setup FDMEE is fully integrated in Oracle EPM Workspace; it’s not a stand-alone application like FDM Classic. There are some real benefits to this. For starters, out of the box, FDMEE is ready to talk to Oracle Hyperion applications registered in Workspace. In FDMEE you will simply do the following. Go...
by Doug Correa | 04 28, 2014 | FDM Classic, FDMEE
You’ve heard with FDMEE Oracle has combined the architecture of ERPi (Enterprise Resource Planning Integrator) and the functionality of FDM Classic. Now, you’re wondering, What’s it look like? If you’ve used ERPi in Oracle Enterprise Performance Management System 11.1.2.1 or 11.1.2.2 – interface-wise – FDMEE will be very familiar. If you’ve never used ERPi, or you’ve had some exposure to ERPi release 11.1.1.3, then the look-and-feel of FDMEE will be new, but easy to grasp. Under the hood FDMEE is a revolutionary step forward. However, when it comes to the user experience, the Oracle development team wanted to make it more of an evolutionary step. Let’s take a look. User Interface The most obvious difference between FDM Classic and FDMEE is the user interface (UI). FDM Classic has it’s own web address (URL) and opens in an entirely separate window from Oracle EPM Workspace. FDMEE, on the hand, is fully integrated in Workspace. So, how do I launch FDMEE? Once you’re in Workspace, you might be inclined to search for a menu item labeled “FDMEE”. Lose that inclination. Instead look for “Data Management”. You launch FDMEE from the Navigation menu – Navigation > Administer > Data Management. Task Panes The FDM Classic Web interface consists of a number of drop-down menu lists. (There’s an alternate menu pane, as well.) FDMEE has a more simplified interface with just two task panes: Workflow and Setup. Administrators are the primary users of tasks on the Setup pane. Power users may also have access to some Setup pane tasks, for instance, to create new locations. End users will spend all of their time in...
by Doug Correa | 04 22, 2014 | FDM Classic, FDMEE
So, you’re considering upgrading your Oracle Hyperion application software. Perhaps your current version is out of support. Maybe your IT department has a new enterprise standard requiring you to move your Hyperion applications to the cloud. Whatever the reason, you’ve been doing your due diligence and you’ve now heard about this “FDMEE” as a replacement for your current FDM software. You can’t seem to figure out which way to go: FDMEE or FDM Classic. Here are six reasons you should seriously consider getting on board with FDMEE. 1) Out to Pasture Well, for starters Oracle is retiring FDM Classic. Oracle Enterprise Performance Management System 11.1.2.3 is the terminal release for FDM Classic. (In fact if you’re a new Oracle Hyperion customer, you can no longer purchase a license to FDM Classic.) Oracle Hyperion Financial Data Quality Management Enterprise Edition – FDMEE – is the successor to FDM Classic. 2) Workspace Integration Since the introduction of the Hyperion System 9 platform in 2006, Workspace has been the portal for nearly all Hyperion applications. Since that time, FDM Classic has never been integrated into Workspace; for the most part, it’s remained a stand-alone product. (This is probably due to its Windows constraints. See below.) FDMEE, on the other hand, is accessible from and fully integrated with Workspace. 3) ODI Under the hood, FDMEE uses the world-class Oracle Data Integrator (ODI) as the engine for data processing. With ODI, you get more advanced data integrations (think direct connections to general ledger systems) and faster processing times. 4) Lifecycle Management Unlike FDM Classic, FDMEE supports the use of Oracle EPM Lifecycle Management (LCM). Using LCM, administrators...
Recent Comments