No fact table exists at the requested level of detail — Oracle Analytics

Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

No fact table exists at the requested level of detail

Received Response
52
Views
6
Comments
Md. Altas
Md. Altas Rank 3 - Community Apprentice
edited Aug 13, 2024 6:13PM in Oracle Analytics Cloud and Server

Hi All,

We store some additional work order data in DFF and this is loaded to our ETL tables.

But the additional details are maintained in the lookup tables.

For example: In Work Order DFF, we have got 'Released To' this indicates the line to which work order is released.

There is lookup for LINE_DATA. We store some information about the assembly line there. For example: - MAINTAIN_DATE.

In my RPD, in BMM layer I created table WORK ORDERS with WORK_ORDER,LINE_ID and MAINTAIN_DATE ( There are many more but these are key fields for this problem)

I established physical join LINE_ID from Work orders = LINE_ID in lookup table.

After RPD deployment, everything works very well exception of MAINTAIN_DATE.

When I try to add 'MAINTAIN_DATE to report I get following error -


State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 14025] No fact table exists at the requested level of detail:


I need some help to resolve this. This is the only thing which is stuck right now.

Does lookup work in OBIEE properly?


Thanks

Answers

  • AkanshAgarwal
    AkanshAgarwal Rank 4 - Community Specialist

    Hi,

    Can you send more details about your BMM layer star.

    Is maintain_date joined to any other table?

    Regards,

    Akansh agarwal

  • Md. Altas
    Md. Altas Rank 3 - Community Apprentice

    No MAINTAIN_DATE is NOT joined to any other table.

    The WORK_ORDER table is Fact table.

    Expected behavior is when we are pulling in the work orders data then we should be able to pull in the MAINTAIN_DATE.

    This is linked through the LINE_ID column.

  • AkanshAgarwal
    AkanshAgarwal Rank 4 - Community Specialist

    Hi,

    Please check the content level of the fact table. You need to assign a level of detail for every dimension connected to the fact.

    Regards,

    Akansh

  • 1036082
    1036082 Rank 2 - Community Beginner

    Hi,

    Please check in fact table whether all the hierarchies are added to the content level.

    If not please set the content level.

    Regards,

    Venkatesh.

  • Md. Altas
    Md. Altas Rank 3 - Community Apprentice

    Hi,

    I was able to resolve this by using the lookups.

    I used dense lookup and I get the MAINTAIN_DATE as expected.

    Thanks

  • user7638003
    user7638003 Rank 2 - Community Beginner

    Hello 1430724,

    Please elaborate how you accomplished this issue? thanks