By TopDown Team on January 4th, 2017
Every year TopDown showcases our top content for the year with the Top 10 most popular blog posts. Some of these topics remain evergreen, making the list for multiple years. Other topics are more recent. To make things more interesting, this year our experts have looked at the content and weighed in on how the topic at hand fits in with the maturing of EPM in the cloud. Read on to find out what they have to say.
By Thomas Thuresson on December 21st, 2016
The release of 220.127.116.11 PSU 200 for FDMEE introduced some exciting new features, including the ability to add a Cloud application as a target application, eliminating the need for a file based approach at a recent client.
By TopDown Team on June 13th, 2016
Recently, we’ve implemented FDMEE version 18.104.22.168 at a major client. This client has been using FDM classic version 11.1.2.x for many years and needed to upgrade to version 22.214.171.124 for compliance and maintenance support reasons. When we started this project, we installed the base version of FDMEE 126.96.36.199 with the .100 patch. Through the course of our implementation we ran into some noteworthy findings that we’ll discuss in this blog post. Our guideline for the FDMEE build was to use built-in functionality and be fairly vanilla, so avoid any custom coding.
By Thomas Thuresson on April 6th, 2016
FDMEE comes installed with variety of standard reports, just like in FDM. Most of the reports that came with FDM are ported to FDMEE. The big difference is that the embedded engine that renders the reports now is Oracle BI Publisher. The core data tables remain the same, making it easier to convert old custom…
By TopDown Team on March 8th, 2016
What do you do when one line item provides more information than only one destination Point of View? For instance, assume that all of the trial balance accounts from an extract will load to a custom dimension member of “END”. However further assume that the trial balance has multiple members, typically in a custom dimension, for the balance sheet accounts that record movement.
By TopDown Team on March 1st, 2016
In old FDM if there was ever a need to source two fields for an exception mapping, it was required to write a script to resolve this issue so that the scripted member would then be able to be mapped accordingly. For instance, there might be a Long-Term liability account in HFM, “AccruedTax”, that in almost all instances is sourced from a G/L account, 290100. Let’s say however, that there is one exception to this based upon the Entity, “WestSales”, where instead of being a long-term liability, this instead is a long-term asset for HFM, “LongTermDefTaxAsset.”
By TopDown Team on February 24th, 2016
Let’s discuss the basic fundamental purpose of FDMEE. That is to say mappings. FDMEE has come a long way since its origins, and is at this stage is an ETL-like tool (Extract Transform Load). Mapping is the “T”, Transform, part of this acronym. This is where source system, typically General Ledgers, metadata members are transformed to a destination EPM application dimension member. Think of these as accounts, entities, cost centers, product members, and so on.
By TopDown Team on October 30th, 2015
Accounting means assigning the correct numbers to the correct accounts in the correct time period. Consolidation means combining the accounts of several entities according to accounting rules. Introduction As the administrator of Oracle Hyperion Financial Management (“HFM”), your job is to support the application that produces the consolidated results. Key to supporting the application is…
By TopDown Team on February 11th, 2014
Recently I had to update the HFM application server keys on a big HFM application running on version 188.8.131.52, running on a single dedicated Win2008 server (64 bit) CPU 2 X 8 way 3.0 GHz 32GB RAM. The backend is Oracle 11g. End user loads are moderate—the typical concurrent number of users topped out at around 10. The HFM application dimensionality was in the medium range:
By TopDown Team on November 22nd, 2013
FDMEE patch 184.108.40.206.200 is due out next week. It will add to the API library for scripting.