Oracle Analytics and AI

ClaudiaManea

I have a report in FDI that uses the HCM Succession Management subject area, and when I try to add from the candidate column the Person Full Name and from the incumbent column the Person Full Name, I receive an error saying that the report is attempting to combine dimensions at a level of granularity that doesn’t exist in the fact table.

"Error during query processing (SQLExecDirectW).

State: HY000. Code: 14025. [nQSError: 14025] No fact table exists at the requested level of detail: [,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,[

1. Dim - HCM - Succession Plan Details.Plan Name
2. , Dim - HCM - Succession Plan Details.Plan Type
3. , Dim - HCM - Succession Plan Details.Plan Type Code],,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,[
4. Dim - HCM - Worker (Role Playing).Person Full Name],,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,[
5. Dim - Job.Job Name],,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,[
6. Dim - Worker.Person Full Name
7. , Dim - Worker.Gender Code
8. , Dim - Worker.Gender],,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,[
9. Dim - Grade.Grade Name],,,,,[
10. Dim - Worker Location.Country
11. , Dim - Worker Location.Country Code],,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,].
    (HY000)
    State: HY000. Code: 14081. [nQSError: 14081] You may be able to evaluate this query if you remove one of the following column references: Dim - Grade.Grade Name, Dim - HCM - Succession Plan Details.Plan Name, Dim - HCM - Succession Plan Details.Plan Type, Dim - HCM - Succession Plan Details.Plan Type Code, Dim - HCM - Worker (Role Playing).Person Full Name, Dim - Job.Job Name, Dim - Worker Location.Country, Dim - Worker Location.Country Code, Dim - Worker.Gender, Dim - Worker.Gender Code, Dim - Worker.Person Full Name (HY000)
    SQL Issued: SET VARIABLE ENABLE_DIMENSIONALITY=1;SELECT
    0 s_0,
    "HCM - Succession Management"."Basic Information"."Person Full Name" s_1,
    "HCM - Succession Management"."Diversity"."Gender" s_2,
    "HCM - Succession Management"."Grade"."Grade Name" s_3,
    "HCM - Succession Management"."Incumbent - Basic Information"."Person Full Name" s_4,
    "HCM - Succession Management"."Job"."Job Name" s_5,
    "HCM - Succession Management"."Location"."Country" s_6,
    "HCM - Succession Management"."Succession Plan Details"."Plan Name" s_7,
    "HCM - Succession Management"."Succession Plan Details"."Plan Type" s_8,
    DESCRIPTOR_IDOF("HCM - Succession Management"."Diversity"."Gender") s_9,
    DESCRIPTOR_IDOF("HCM - Succession Management"."Location"."Country") s_10,
    DESCRIPTOR_IDOF("HCM - Succession Management"."Succession Plan Details"."Plan Type") s_11
    FROM "HCM - Succession Management"
    FETCH FIRST 500001 ROWS ONLY"

Nehemias-Oracle

Hello @ClaudiaManea

Please review some best practice and Guidelines for Cross Subject Area

Best Practices and Guidelines for Cross-Subject Area Analysis Using Conforming Dimensions

• If all the required metrics and attributes for the report are available in a single subject area and fact, use that single subject area only and don’t create a cross-subject area query.
• When you want to bring the data from more than one subject area, you must choose metrics from all the subject areas in the analysis.
• Start with the necessary filters before you start building visualizations to ensure you use the best performing queries when you add the necessary metrics required in the visualization.
• Always start by selecting all the columns in one subject area, including the facts and dimensions, and then add the facts from the second subject area.
• Always start by adding the Accounting Calendar and Time Dimensions filters first. Restrict the data for one period, and then build on to the report by adding facts and columns one-by-one from one or more subject areas.
• When joining two subject areas in a report, use at least one attribute from a common dimension. Refer to bus matrix for common (conforming) dimensions.

For More details please review following documentation for Cross-Subject Area Report Authoring Tips

https://docs.oracle.com/en/cloud/saas/analytics/25r3/faiae/appendix-report-authoring-tips-erp.html#GUID-AC96F315-4385-49F8-9EB2-7ECFCB15AB64