The Power of FDM Reporting

There are a number of products in the EPM suite.  In my mind, the core products are

  • Hyperion Financial Management (HFM)
  • Planning & Essbase
  • Financial Data Quality Management (FDM)

While there are clearly other very important products in the EPM suite (HSF, Financial Reports, DRM), the core products have a wide installation base and continually see enhancements and new functionality.  Of these core, and to some degree most EPM products, FDM is the only application to include a myriad out of the box reports.

Out of the box, FDM includes 90+ reports that function without any additional configuration!  If you consider the average time it can take to create a Financial Report (.5-2 days depending on complexity), the value of these pre-built reports cannot be understated.  In this post, I explore these reports and highlight those that, in my experience, have the highest utility.

Report Set Purpose
Trial Balance Detailed information about source data processed through FDM
Process Monitor Detailed status reporting of the workflow process
Location Analysis Mapping & System Log information
Trend Trended views of source/trial balance information
Variance Period/Category differences for source/trial balance information
Audit Trial balance investigation; Map changes
Listing FDM application metadata information
Security User security & usage
System Application & adaptor settings
Journal Detailed information about data processed as journal entries
Archive Detailed information about documents archived during the workflow
Batch Detailed information about batch processes
Dimension Grouping Provides pivot table like views of source/trial balance information

The trial balance reports allow a user to view the source (often general ledger/trial balance) data in a reporting format. These reports will usually show the source & target in a single record which is the equivalent of the Import & Validate screens being combined into 1 report.

TB Converted Current Loc, By Target Entity-Acct

This report displays the source and target accounts & entities. The true value add of this report is the 2 data columns. The first shows the data that was imported from the source system and the second shows the data that FDM loaded to the target application. This dual data column allows a user to quickly identify any records that required the sign flip flag to be adjusted.

The process monitor reports allow administrators & key users to track the process of data submissions. These reports can be thought of as a pseudo Close Status Dashboard.

Process Monitor Report Sorted By Location Hierarchy

This report displays the workflow status of each location in the application. The report respects the location hierarchy. Each location has 5 steps (yes 5) that are tracked. The Export workflow step is broken into 2 steps as an export may complete successfully but the load to the target system may fail. The date & time stamp of the last process executed is also displayed.

The audit reports allow a user to trace data as well as mapping changes, additions & deletions. These reports “audit” the typical FDM end-user interaction with the system.

Account Chase – Wildcards

This report allows a user to enter a target account – or a target account pattern (ex: account begins with 51) – and the report will show all the records in FDM for all the locations that make up the balance of that target account. The records are filtered based on the location security that a user has in FDM. This report was the precursor to drill through and still has great utility because it does not require an input level intersection across any dimension except account.

Map Monitor For Location

This report displays each of the addition, changes & deletions to the mapping for a particular location. This is highly efficient way to determine who changed a map, when and from what-to what.


The Listing reports provide a summary of the location metadata & their settings. These reports are a convenient way to review location settings without navigating to each location.

Location Listing

This report displays the key settings (Import Format, Validation Rule, Parent, etc) for each location in the system.


The security reports in FDM are invaluable to understanding system utilization and ensuring that the right level of licensing is being maintained.

Last Logon Time

This report shows the last time a user actually logged into the application. This report can help you assess for which users a license should be maintained.





The system reports of FDM are geared toward administrators to audit the various events that occur within FDM. These reports can be used to track users actions, system performance as well as detailed information about application/process errors.

System Activity Log for Key

This report will provide detailed information about each of the events that are captured in the FDM application log. This report can be used to determine when and action was performed and by whom. In the event of an error, this report is critical to gathering additional information about the error.

Import Analysis

I saved my favorite report for last! This report is critical to identifying the source of slow import performance. The report displays the elapsed time for each step performed during a data file import. Utilizing this report can help an administrator understand if there is a database performance issue or if the maps are simply inefficient. For any FDM shop, this report is a MUST use!

You may be asking yourself – “What about the batch reports?” While the batch reports provide good information about the batch process, I prefer to develop email status reporting that distills the information into a more user-friendly format. See my post on enabling lights out automation for more information and a sample email format that I use to augment the batch reporting in FDM.

Don’t let this post be the end of your learning. I encourage each of my clients to explore the report sets and each of the reports that are available. You may uncover a report that gives you exactly what you need!

This entry was posted in Out of the Box Functionality, Reporting and tagged , , , . Bookmark the permalink.

4 Responses to The Power of FDM Reporting

  1. Pingback: Using the Check Report to Proactively Identify Data Quality Issues | The FDM Information Source

  2. RobynC says:

    Tony –
    First off, really impressed with your work (and of course your passion for all-things-FDM). One area in FDM reporting I’m struggling with is the security reports — I’ve got a situation where security levels for some users vary by location, yet the location specific security levels (or, overrides) do not display on the standard reports. I’ve gone to the table level to see if I’d have success joining tables to get the data, but I can’t even find the table that has the level by location. I’ve tried all the tsecs and tPOV / partitions, and have come up empty. Have you experienced this or are you able to share any tricks for reporting on the location overrides in order to spare me the effort it would take to screenprint location level access for each user? Or, is this truly something I need to report as an improvement area for FDM?

    – Robyn

    • Tony Scalese says:


      Thanks for the compliment, I appreciate it.

      This can be pretty easily accomplished if you are comfortable with creating & modifying SQL queries and the report layouts. The information you need about which users have which access to which locations is stored in tSecUserPartition.

      If you still require assistance, feel free to contact me and we can explore how I might be able to help.


      • RobynC says:

        Thanks.. not sure how I missed that one! I found the information and created the report with the information I need. Appreciate the quick response!

Leave a Reply