FDMEE more —

Oracle Enterprise Performance Management (EPM) Release includes the debut of Hyperion Financial Data Quality Management Enterprise Edition, dubbed “FDMEE”. For existing Hyperion customers, FDMEE represents the evolution of Financial Data Quality Management (FDM). (The soon-to-be-retired Windows-based data integration tool has now been re-branded “FDM Classic”.)

With, existing Oracle Hyperion customers have a choice: you can continue to use FDM Classic for one last go-round or you can go to FDMEE. For new customers, your only option is FDMEE. With the release of and beyond, it’s FDMEE – no ifs, ands, or buts.

For those customers using a previous release of Enterprise Resource Planning Integrator (ERPi), FDMEE is a big leap forward. Oracle states that FDMEE represents the integration of both FDM Classic and the former ERPi. Really, though, Oracle integrated the look-and-feel and overall functionality of FDM Classic into ERPi and re-branded it FDMEE.
From FDM Classic, you get most of the key features you’ve come to rely on:

  • Workflow Process (Yes, you still have your gold fish, one for each Workflow step, i.e. Import, Validate, Export, and Check.)
  • Locations
  • Mapping Tables (now “Member Mappings”)
  • Import Formats
  • Validation Entity Groups (now “Check Entity Groups”)
  • Validation Rules Groups (now “Check Rule Groups”)
  • Batch Loader (now “Batch Execution”)
  • Scripting – Import format Scripting, event scripting, and custom scripting
  • File-based data loads

From the ERPi side, here are the main features incorporated into FDMEE:

  • Like previous versions of ERPi, FDMEE is fully baked into the Oracle EPM Workspace portal
  • Support for direct data integration with general ledger (ERP) source systems
  • Drill Through from EPM target applications back to transaction-based ERP applications
  • Data Write-Back – You can take budget data from a target EPM Planning application and write-back to a supported ERP application, e.g. Oracle e-Business Suite
  • Data Load Rules, used to customize the data extraction process for a location
  • ERP metadata integration to Oracle EPM target applications

In future blog posts, I will get into what’s involved in an upgrade from FDM Classic to FDMEE and I’ll discuss various FDMEE features in detail.  Stay tuned.



FDMEE Upgrade – reasons to switch from FDM classic to 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 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 can easily migrate application components from one environment to another.  LCM is part of Shared Services and has been around for years.  It’s now available to FDM administrators for FDMEE.


5) Multi-platform Support

Any infrastructure resource that has ever installed FDM Classic is fully aware that it is a Windows only product.  Back in the early 2000′s when FDM (then known as UpStream WebLink) was coming onto the scene, this was acceptable.  But these days, IT departments have come to expect that any world-class software can run on alternate operating systems, such as Linux. Like most other products in the Oracle EPM Suite, FDMEE can be installed on various platforms.

6) Multi-browser Support

Let’s face it.  People like options.  When it comes to using FDM Classic, the browser options are limited… to just one.  FDM Classic works on Internet Explorer only.  With FDMEE, like other Oracle EPM applications, you can use Internet Explorer or Firefox.  (Sorry Apple folks: no Safari support just yet.)


FDMEE- The future of Hyperion Integrations

FDMEE stands for Financial Data Quality Management, Enterprise Edition, introduced in the latest EPM release, It is the latest version of Oracle’s Financial Data Quality Management. It is a data integration tool majorly used for integrating financial data.

It is one of the favorite tools for business users and administrators because of its user friendly web interface and audit capabilities. A major advantage of using this tool is the drill through capability to Oracle GL and various other source systems which includes Oracle Fusion Financials, PeopleSoft, SAP ERP Financial to name few. This tool is a seamless integration of ERPi and FDM. It is based on the ODI engine with the FDM workflow. The tool was released in a phased approach and targets to cover all the FDM functionalities by the end of last patch.

I would like to introduce the functionalities of this application based on our implementation experience in this blog.

The basic release of FDMEE covered the below mentioned functionalities:
1. Core FDM features
2. FDM Workflow – Import, Validate, Export and Check
3. Partial HFM adapter parity – Data Protection and Line item details
4. Drill through to source
5. Open Batch Loader
6. Reports
7. Process Monitor

In addition to above mentioned functionalities, following features are added to core FDM features in FDMEE:
1. FDMEE is accessible from Workspace directly
2. ODI is installed and configured automatically
3. Adapters are configured with in the ODI
4. An added functionality of Data load rule to define the Source filter options
5. Scripting supported in Jython
6. Batch processing natively supported via ODI
7. Shell scripts supported to run for lights out automation
8. A central process monitoring for all the FDMEE processes

Following are some of the gaps in the current version of FDMEE. Some of these are planned to be addressed in the upcoming patch 2 while a few others will be addressed in later releases.
1. Control Process
2. Multi Load
3. Custom Scripts
4. Tab delimiter
5. No options to save UI settings in Workbench
6. LCM Issues – While importing the backup, Import for Data load rules and Application Period mappings fail
7. No Object for Period Name for scripting

Apart from these changes following features have been excluded from FDMEE:
1. Tax adapter
2. Enterprise adapter
3. Currencies in Control Tables

I will follow up with some more details on the above mentioned functionalities where I will use our implementation experience to call out some items you might want to watch out for while designing EPM landscape which leverages FDMEE for integrations and data quality management purposes.


What is Oracle/Hyperion FDM

Every Now and then i have been asked this question about what is FDM and why its used for, so i thought of sharing this.

Oracle/Hyperion Financial Data Quality Management (FDM as affectionately known) is an out-of-the-box Data Transformation Tool that feeds source-level financial data to consolidation, reporting, planning, and analytical applications. More than just a data translation tool, FDM provides an audit trail to the source financial data, helping to ensure data integrity and mapping consistency that allows for easy reconciliation of financial data. Providing an audit trail to the source financial data saves end-users, administrators, and auditor’s time associated with data error investigation, identification, and correction.

FDM offers a consistent, end user-friendly environment that provides a uniform data collection process for all reporting units within the organization. Hyperion FDM also contains financial controls functionality to assist corporations with their internal financial controls process.

FDM features and benefits include the following:

  • Acting as a central repository of all source financial data.
  • Drill-down audit trail
  • Ability to archive source files, error logs, and load files
  • Internal controls assessment and certification feature aids in compliance with sections 302 and 404 of the Sarbanes-Oxley Act
  • Corporate-wide process monitoring
  • Ability to import source data from any formatted text file or data source
  • Multiple dimension mapping and validating capability
  • Data validation and quality checking
  • Error identification and notification
  • Consolidation of target system data
  • Validation and reporting on target system data
  • Load adjustments capability through Excel journals
  • Budget data loading for multiple periods
  • Advanced reporting and audit functions
  • “Lights out” batch loading



DRM – Database Requirement

If you are deploying a reasonably large environment for Data Relationship Management or Data Relationship Governance, I recommend following industry best practices for your database server:

  • Provision as much RAM as possible.
  • Locate the servers close together with a low-latency high-bandwidth network.
  • Place the temp database, index files, and data files on separate storage partitions.
  • If possible you can even split tables onto separate partitions; the transaction history and global/local property value tables are good candidates.
  • Use high-bandwidth storage (such as fiber-channel) as many in parallel as you can
  • Use Solid State disks
  • If you haven’t guessed, the them is to spread the disk load onto as many separate SSDs as you can, then to pair the SSDs into stripes behind high-bandwidth link.


  • You might be surprised at how much this can affect your database performance for all applications, not just DRM.


Recover Essbase Application

It is possible for a database in Essbase to become corrupt. This can be caused by server hangs, software glitches, and a variety of other reasons. Although infrequent, if a database cannot be loaded for any reason, and it needs to be restored, the following actions can be a quick resolution. Keep in mind that this will remove the data and it will need to be imported from a backup export.

Before performing this, verify that the database is not attempting to recover. To determine if this is occuring, open the application log file. If it states that it is recovering free space, be patient as it may correct itself.
File Structure

Essbase has a simple file structure that it follows. It can vary with each application depending on the options used. The area to focus on for this process is below. The application and database that is being restored would take the place of appname and dbname.

Restoring To A Usable State

In this directory, files with the following extensions will need to be removed. This will delete all of the data and temporary settings that are causing the application to function improperly. It will NOT delete the database outline, calc scripts, load rules, or business rules.

.ind (index files)
.pag (data files)
.esm (Essbase kernel file that manages pointers to data blocks, and contains control information that is used for database recovery)
.tct (Essbase database transaction control file that manages all commits of data and follows and maintains all transactions)

After these files are removed, verify that the application and database is functioning. This can be done in Essbase Administration Services by starting the application. If the application doesn’t start, more research will have to be performed. If the application loads, import the most recent data backup and run an aggregation.

There are a number of other possible file types in this directory. Below is some information that may be helpful.

Audit Logs

.alg: Spreadsheet audit historical information
.atx: Spreadsheet audit transaction

Temporary Files

.ddm: Temporary partitioning file
.ddn: Temporary partitioning file
.esn: Temporary Essbase kernel file
.esr: Temporary database root file
.inn: Temporary Essbase index file
.otm: Temporary Essbase outline file
.otn: Temporary Essbase outline file
.oto: Temporary Essbase outline file
.pan: Temporary Essbase database data (page) file
.tcu: Temporary database transaction control file


.csc: Essbase calculation script
.mxl: MaxL script file (saved in Administration Services)
.otl: Essbase outline file
.rep: Essbase report script
.rul: Essbase rules file
.scr: Essbase ESSCMD script


.apb: Backup of application file
.app: Application file, defining the name and location of the application and other application settings
.arc: Archive file
.chg: Outline synchronization change file
.db: Database file, defining the name, location, and other database settings
.dbb: Backup of database file
.ddb: Partitioning definition file
.log: Server or application log
.lro: LRO file that is linked to a data cell
.lst: Cascade table of contents or list of files to back up
.ocl: Database change log
.ocn: Incremental restructuring file
.oco: Incremental restructuring file
.olb: Backup of outline change log
.olg: Outline change log
.sel: Saved member select file
.trg: Trigger definition file.XML (Extensible Markup Language) format
.txt: Text file, such as a data file to load or a text document to link as a LRO used for database recovery
.xcp: Exception error log
.xls: Microsoft Excel file


EPMA File Generator

EPMA File Generator is a tool which enables to get the Metadata Extract of a EPMA based Hyperion Planning and Hyperion Financial Management Applications by providing the respective credentials on the Tool.
The Output provided by the tab From EPMA application would be in the .ads format.

In order to access to the tool you can use one of the below options:

  1. From the start menu: Start Menu -> All Programs -> Oracle EPM System -> Foundation Services -> Start EPMA File Generator
  2. From the file system: C:\Oracle\Middleware\EPMSystem11R1\products\Foundation\BPMA\EPMAFileGenerator\bin\EPMAFileGenerator.exe

You can also find additional information
here: http://docs.oracle.com/cd/E12825_01/epm.111/epma_file_gen_user.pdf
here: http://www.oracle.com/webfolder/technetwork/tutorials/obe/hyp/HFM11.1.2_MExtract/MetadataExtract-Files.htm


Implied Share- Concept In Essbase

What is implied share?
Implied share is the data storage method for Essbase when there is only one consolidating child for a given parent. In such a case, Essbase only stores data once for these two members.
Even if you have many children under the parent, but only one of them consolidating to, this situation will also result in the implied share mechanism to take action.

What is wrong with implied share?
If you create a data form with @ICHILDREN function to this member (or @IDESCENDANTS) both the only child and the parent will be represented.
In this case, when you enter data to the child, data will not be saved, due to data for parent being #missing and also being saved.
Of course you can enter data twice to overcome this issue, but it doesn’t feel right

How to fix for some parts of the hierarchy?
Option 1: A new aggregating member under the same parent can be created to disable the implied share for this hierarchy. But in this case, data forms showing the hierarchy will have a dummy member which is not always applicable.
Option 2: Parent member storage option can be changed to “Never Share” to avoid implied share for the specific part of the hierarchy. The drawback on this option would be that, parent member now can’t be a part of an alternate hierarchy.
Option 3: Parent member’s member formula can also be updated to the name of the only aggregating child member. The drawback on this option is that, maintenance work related to watch the hierarchy changes increases.

How to fix for the whole application?
There are eight steps to apply application wide fix:

  • Backup your data
  • Add below code to essbase.cfg file
  • Restart Essbase Server
  • Create a new application and database
  • Rebuild the outline
  • Reload the data
  • Run the aggregation scripts
  • Restart the application

For more information about this setting: http://docs.oracle.com/cd/E40248_01/epm.1112/essbase_tech_ref/frameset.htm?impliedshare.html

Drawback of turning implied share off
In such cases that you can’t avoid turning implied share off, this will result in a larger block size and relatively slower performance.


Hyperion Smart View – Extensions and Utilities Power Pack

Getting Query on Daily basis are there any shortcuts for smartview except writing Macros – so thought of writing this blog.

Oracle has several extensions and utilities to make your Hyperion Smart View navigation simple and more efficient. There are a variety of Power Pack downloads that can be used to enhance or extend Smart View to save time and make navigation more manageable.

Download and launch the msi installation on a Windows machine with Hyperion Smart View 11.1.2 or above installed along with Office 2003, Office 2007 and Office 2010.

Download link.





Once installed, each extension can be enabled or disabled:

Note to Install unzip the file and copy and paste all dll files to your smartview installation folder – C:\Oracle\SmartView\Bin or respective Installation path depending upon environment.


To access the extensions, go to the Hyperion Smart View Panel Home dropdown, select the extension to use:


Power Pack Adjust Data Extension
Simple data adjustment panel for use with Hyperion Smart View. This allows the user to select multiple cells and do simple addition, subtraction, multiplication, division. In addition, it allows for increasing or decreasing cells by a percentage. All data adjustment features work in cells whether the Smart View connection is active or not. Compatible with Smart View 11.1.2 and above.




Power Pack Quick Options Extension
This will allows the user to quickly change the most common options for Hyperion Smart View rather than launching the options dialog. Default options can be set or restored at any time. Compatible with Smart View 11.1.2 and above.


Power Pack Table of Contents Extension
Displays open workbooks and worksheets organized by connection type. Sheets can be sorted by sheet name, book name, or connection. This will also allow users to see if workbooks or worksheets are connected. Compatible with Hyperion Smart View 11.1.2 and above.


Power Pack MDX Script Library Extension
This allows users to view and launch MDX scripts stored on their local machine. Run MDX scripts and use them as a starting point for new queries. Results can be used for a starting point for new Essbase queries. Compatible with Hyperion Smart View 11.1.2 and above.

Power Pack Substitution Variables Extension
List and use Essbase substitution variables in ad-hoc operations. Compatible with Hyperion Smart

Power Pack Member Search Extension
Search for Essbase members in the Smart View panel without the need to open a dialog. Displays basic member information. Compatible with Hyperion Smart View and above.


Power Pack Smart Chart Extension
Link native Excel chart to ad-hoc grids. The chart will update as you zoom or pivot. Compatible with Hyperion Smart View and above.

Power Pack Grid Themes Extension
Format ad-hoc grids with pre-defined themes. Compatible with Hyperion Smart View and above.

Smart View VBA Conversion Tool
Tool that will assist in the conversion of Legacy (Classic) Add-In VBA code to equivalent Hyperion Smart View VBA Code.

Please revert in case of any queries.