nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle AI and Analytics

Child Item

Enable a Single Employee Report Across Goals, Performance Management and Talent Profile

Jacopo Giacco

Many organizations need to produce a single employee-level report that combines information from multiple Oracle Fusion Data Intelligence HCM subject areas, including:

Workforce Core
Goals and Career Development
Performance Management
Talent Profile
Talent Profile Trends

A common requirement is to extract, in a single report:

Employee information
Organization and manager hierarchy
Goals and goal completion status
Performance document information
Performance task status and completion dates
Talent profile attributes
Skills and competencies
Career development information

Today, when analysts attempt to combine attributes and metrics coming from these subject areas within a single analysis or visualization, Oracle Analytics frequently returns errors such as:

No fact table exists at the requested level of detail (nQSError: 14025)

As a result, customers must implement custom solutions, such as datasets, database views, data augmentation processes, or external integration layers. These workarounds increase implementation effort, maintenance costs, and create additional challenges around HCM row-level security.

Requested Enhancement

Provide a native FDI capability that allows users to build a single employee-centric report across Workforce, Goals, Performance, and Talent subject areas while preserving Oracle-delivered security.

The solution should enable reporting across HCM domains without requiring custom data models, custom database objects, or complex security reimplementation.

Business Benefits

360° employee reporting
Simplified HCM analytics
Reduced implementation effort
Reduced maintenance costs
Faster dashboard and report development
Consistent row-level security
Better talent and performance analytics
Improved adoption of Oracle Fusion Data Intelligence

Find more posts tagged with

Submitted

Goals

Performance Management

Workforce Analytics

Talent Profile

Talent Management

Status: Submitted

Comments

mgoswami

@Jacopo Giacco You are definitely not alone here—handling requests that span multiple functional areas is a very common challenge.

In many cases, trying to combine all of these dimensions into a single tabular report causes more friction than it solves. When stakeholders need wide, multi-domain extracts, it is often more practical to extract the datasets separately and handle the consolidation in a downstream reporting tool. (not recommended approach).

If keeping the solution within Oracle FDI is preferred, consider these approaches:

Canvas Layout with Shared Prompts: Instead of one massive table, build a dashboard canvas featuring separate, focused visuals for each subject area tied together by common filters (e.g., filtering by Employee, Manager, or Organisation to simultaneously update distinct visuals for Goals, Performance, and Talent side by side).
Resolving the Subject Area Error: If you do need to keep multiple subject areas in a single analysis, ensure you include at least one metric/fact measure from each subject area you pulled attributes from. When referencing dimension attributes across subject areas without a corresponding measure from each will trigger a query error.

Hopefully, this provides a clearer path forward for your design!!

Jacopo Giacco

Thank you, @mgoswami , for the suggestions and for taking the time to provide guidance.

We did test the approach of including measures from each subject area to avoid the "No fact table exists at the requested level of detail" error. While this helps in some scenarios, we are still encountering another limitation when building employee-centric reports spanning multiple HCM domains.

Based on our observations, when attributes and measures from different subject areas are combined, the resulting dataset appears to be restricted to records that exist across all participating subject areas. In practice, this behaves similarly to an inner join, causing valid employee records to be excluded whenever related information is missing in one of the domains.

For many HR reporting requirements, the expected behavior would be closer to a left outer join or even a full outer join, where employee records can still be returned even if certain Goals, Performance, Talent, or Career Development information is not available. This would allow analysts to produce complete employee-level reports without losing records due to data availability differences between subject areas.

The ability to combine Workforce, Goals, Performance, and Talent data while preserving all relevant employee records and Oracle-delivered security is the main enhancement we are hoping to see in FDI.

Thanks again for sharing your recommendations and perspective on this topic.

Raghavendra Raghunath-Oracle

Hi @Jacopo Giacco Do you have a mock of what report you want to build using all these subject areas? Note that you can still get this all of the combined but the data will repeat for data at the lowest grain. For example: If there are two performance document in Performance subject area and 3 goals in Goals subject area then the report will have 6 rows with a cartesian join. Is this acceptable?

Hence, a sample report that you have envisaged would be helpful for us to evaluate. Please be detailed as much as possible.

Thanks

Raghu

Top Leaders

mgoswami 385

Jay Pearson-Oracle 111

Victor H 36

Raghavendra Raghunath-Oracle 34

Daniel Ryan 32

Top Ideas

FDI Connectors - Enable Multiple Connections of the Same Type
I have a use case for FDI connectors whereby I need to use the EPM Integrator to include planning data in my environment but I have 2 separate EPM environments, one for ERP and one for HCM. Once you create a connection using a connection type, the option to create a new one disappears. This creates an issue where customers…
FDI Workbook Default Values
In the out of the box workbooks, many have default filters for items such as Ledger and Business Unit. Most of these default to the first value alphabetically. This can be incredibly frustrating for users who, when logging in for the first time often get no results or results they are not expecting when they first log in.…
Add Native "View Selector" Visualisation / Container in Oracle Analytics (DV) & FDI
With continuous capabilities being brought into the modern Data Visualisation (DV) experience in OAC and FDI, a native equivalent to the View Selector from Classic Analysis / OBIEE is needed. In Classic reporting, the View Selector allowed users to dynamically swap between different chart types, tables, or analytical views…
Option to store saved states in dva export
OAC saved states are lost when the workbook is moved / migrated to another environment. This feature is intended mostly for personal user preferences but it is also useful for providing preset selecitons for users. If we want to make these presets available for all users , the only way is opening the workbook in the new…
Enable a Single Employee Report Across Goals, Performance Management and Talent Profile
Many organizations need to produce a single employee-level report that combines information from multiple Oracle Fusion Data Intelligence HCM subject areas, including: Workforce Core Goals and Career Development Performance Management Talent Profile Talent Profile Trends A common requirement is to extract, in a single…