Oracle Business Intelligence Applications

Home› Oracle Analytics› Oracle Analytics Forums› More Solutions› Oracle Business Intelligence Applications

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
4
Views
2
Comments
Naeem Akhtar
Naeem Akhtar Rank 3 - Community Apprentice
in Oracle Business Intelligence Applications

Hello,

I have created a custom dimension (Custom Group Account) in OBIA and made necessary joins in Physical and Logical Layer. Further I have created a hierarchy for the same dimension and defined levels.

In Fact LTS, logical levels are also defined appropriately under content tab. So far so good and everything is working fine in answers for the column where levels are defined through hierarchy.

There is one columns where I have not defined levels since hierarchy nodes are not required for the column.

custom column.JPG

Now when I use this column in answer then getting below error.

"No fact table exists at the requested level of detail:"

However same column in OOTB logical table also dont have logical level set but working fine in answers.

standard column.JPG

Can you please suggest what is the issue?

Regards

Naeem K.

Answers

  • [Deleted User]
    [Deleted User] Rank 2 - Community Beginner

    Well then the difference between out-of-the-box and custom must be somewhere else. Fact LTS content for example. Cross-fact queries rather than single-fact queries are a prime example where that will break.

    Without seeing your RPD there's about 5 to 50000 places where things can go wrong depending on how many facts are in your model and / or involved in your queries

  • Naeem Akhtar
    Naeem Akhtar Rank 3 - Community Apprentice

    Hi Christian,

    Thanks for your response. There are 2 facts involved in the query and both have proper physical and logical joins. (same joins as with OOTB dimention)

    The column which has issue is not part of Fact LTS contents for both custom & OOTB dimension. If I create new level in the hierarchical dimension for this custom column and set content level in the Fact LTS accordingly then the error is not coming. But I am wondering why OOTB column is working fine where it is not part of hierarchy and no content level set for Fact. I have tried to compared all properties of both dimensions but couldn't found difference here in my search.

    Can you please tell me other possible reasons for this error?

    Regards

    Naeem K.