NQSError: 14020  : Fact Table Incompatible with Query Request

Hi All,
I am trying to add a new join to existing fact and dimension tables.
These tables are already part of some star schemas.
Now when I add the join , RPD doesn't show any consistency errors/warnings but when I create an analysis in OBIEE 11g, Measure from fact shows only null.
When I looked at the log, the physical query just has a select statement querying the dimension table and following message :
"COUNT converted to NULL because [nQSError: 14020] None of the fact tables are compatible with the query request COUNT:[DAggr(CF_FACT1.COUNT by [ CD_DATE_4.DATE_KEY.. "
Has anyone encountered similar problem ?   
Few threads spoke about settign the content level but its not set for any date dimension we are using but it still works. Facing this problem only for the new join I am trying to add now.
Thanks for any pointers
Sujana                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Back up your repository before following these steps:
1 Reduce the problem report to minimum number of columns required to generate the error. This will usually identify which dimension and which fact are incompatible.
2 Open the repository in the Administration tool and verify that the dimension and fact table join at the physical layer of the repository
3 Verify that there is a complex join between the dimension and the fact in the business layer.
4 Check the logical table sources for the fact table. At least one of them must have the Content tab set to a level in the hierarchy that represents the problem dimension. This is usually the detailed level.
5 Check the logical table source Content tab for the dimension table. Unless there is a valid reason, this should be set to blank.
6. Save any changes to the repository.

Similar Messages

  • [nQSError: 14025] No fact table exists at the requested level of detail:

    Hi All,
    I am using OBIEE 11.1.1.6.8.
    I have below senario...My fact table contains 3 LTS(yearly, Monthly, Weekly) and TimeDim contains3 LTSs(yearly, Monthly, Weekly)
    Fact-Weekly joins with (D1,D2,D3) & TimeDimWeekly
    Fact-Monthly joins with (D1,D2,D3) & TimeDimMonthly
    Fact-Yearly joins with (D1,D2,D3) & TimeDimYearly
    I hv also set the Fact source content to appropriate level of TimeDIM and details level of other Dimensions.
    when i build a report using only year_code or month_code_or week_code as filter the query is going to appropriate physical sources
    ie. if i take week_code as filter then the query firing to FactWeek, TimeDimWeekly & other Dimensions
    if i take Month_code as filter then the query firing to FactMonthk, TimeDimMonthly & other Dimensions
    Problem is when I use dynamic filter its is giving [nQSError: 14025] No fact table exists at the requested level of detail: error.
    My filter is something like this using presentation variable pvTime (filter is prompted)
    case '@{pvTime}'
    when 'Weekly' Then "Calendar"."Week - WYYYY"
    when 'Monthly' Then "Calendar"."Month - MONYYYY"
    when 'Yearly' Then "Calendar"."Year ID" end
    Please help me if I missed any step
    Thanks
    Smita

    Its a guess but try the below.. As you are using the CASE statement in your filter, use it in the below way.
    Store the value that is prompted into a presentation Variable
    YOUR WAY
    case '@{pvTime}'
    when 'Weekly' Then "Calendar"."Week - WYYYY"
    when 'Monthly' Then "Calendar"."Month - MONYYYY"
    when 'Yearly' Then "Calendar"."Year ID" end
    SUGGESTED WAY
    (case '@{pvTime}'='Weekly' and "Calendar"."Week - WYYYY" = '@{new PV}' THEN 1
    when '@{pvTime}'='Monthly' and "Calendar"."Month - MONYYYY" = '@{new PV}' THEN 1
    when '@{pvTime}'='Yearly'  and "Calendar"."Year ID" = '@{new PV}' THEN 1 ELSE 0 END) =1
    This might correct the way your are using your CASE statement in Filters..

  • OBI Joining two lookup tables. [nQSError: 14025] No fact table exists at the requested level of detail

    Hello,
    I basically have only fact tables that I need for my analysis. No dimensions, no hierarchies.
    When add two tables in OBI Answers to start the analysis I see this error:
    [nQSError: 14025] No fact table exists at the requested level of detail
    I have them defined as lookup tables. How can I join lookup tables?
    In order to pre-filter them using the user_name session variable.

    Hi Nagireddy.
    As described:
    open your rpd. go to "manage" -> Variable Manager / New / Session / Variable.  so to create a new session variable in the .rpd.
    then you create a variable NO_FORCE_TO_DETAIL_BIN and se the default to 1.
    BUT....this did actually not do the trick
    I have created a logical table that is a table made up of the two that I just want to join and as soon as I create a bi answers report that contain columns from those two tables I see the  error 14025.

  • No fact table exists at the requested level of detail Error.

    Hi Everybody,
    Facing a issue on the using  Fact less Fact tables.
    Scenario:
    ========
    Using two subject areas to develop a report.OBIEE 11g
    Fact1 --> Compensation Plan Assignments Real Time
    Fact2 --> Participant Detail Real Time"."Participant Details
    On both facts we created dummy metrics on respective table id's and aggregated to ROWCOUNT.
    As i said in earlier we are using the above 2 subject areas to develop reports.
    Logical SQL:
    ===========
    SELECT
    0 s_0, "Incentive Compensation - Compensation Plan Assignments Real Time"."Role"."Role Name" s_1,
    "Incentive Compensation - Participant Detail Real Time"."Participant Details"."Cost Center" s_2,
    "Incentive Compensation - Participant Detail Real Time"."Participant Details"."Country Code" s_3,
    "Incentive Compensation - Participant Detail Real Time"."Participant"."Participant First Name" s_4,
    "Incentive Compensation - Participant Detail Real Time"."Participant"."Participant Last Name" s_5,
    "Incentive Compensation - Participant Detail Real Time"."Participant"."Party Number" s_6
    FROM "Incentive Compensation - Earnings Real Time" FETCH FIRST 65001 ROWS ONLY
    Error Message:
    ==============
    Expression 'RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]' converted to NULL because [nQSError: 14020] None of the fact tables are compatible with the query request RowCount:[DAggr(Fact - Compensation Plan Assignment.RowCount by [ Dim - Participant Details.Cost Center, Dim - Compensation Role.Role Name, Dim - Participant.Participant Name] )]..
    [2013-10-21T12:18:45.000-05:00] [OracleBIServerComponent] [TRACE:2] [USER-34] [] [ecid: 004uJx90aHO9lZ73VJJNB80007eh000gl_,0:2:1:9:5] [tid: 457c2940] [requestid: f2e001b] [sessionid: f2e0000] [username: [email protected]] -------------------- Query Status: [nQSError: 14025] No fact table exists at the requested level of detail:
    Please share some ideas on this or any guidelines will be very much helpfull.

    Govardhan,
    Did u configured any Dimension Hierarchy please set the levels in that particular Fact LTS.
    For more info,check the below thread
    https://forums.oracle.com/thread/2134934
    Thanks,

  • No fact table exists at the requested level of detail

    We have two fact tables F1,F2 and D1, D2, D3, D4, D5 dimensions.
    They are connected line this.
    F1 to D1, D2, D3 and self dimension D_of_F1
    F2 to D2, D3 and self dimension D_of_F2
    Means D2 and D3 are common dimensions between two facts.
      D_of_F1
             |
             |
    D1--F1--D2
             |      |
             |      |
            D3   |
            |       |
            |       |
            |-F2-|
            |
            |
            |
       D_of_F2
    Hierarchies
    H1 for D1
    H2 for D2
    H3 for D3
    H_of_F1 for D_of_F1
    H_of_F2 for D_of_F2
    and pinned LTS of F1 --> H1 detail, H2 Detail,H3 Detail, H_of_F1 Detail
    and pinned LTS of F2 --> H2 Detail,H3 Detail, H_of_F2 Detail
    We are selecting these columns
    D1.C1, D1.C2, D2.C1, D2.C2,D3.C1 and report works perfactly.
    But when I add D_of_F2.C1 then report gives this error
    Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 14025] No fact table exists at the requested level of detail
    Please help me to solve this error....
    I m new in OBIEE concepts so not able to trubleshoot...
    Thank you.

    i'm try to do an analysis between two tables (that have a relatinship), we had inclued first the FACTURA.FACTURA_COD, then columns from COBRANCAS and it work's. When we inclued the FACTURA.COMISSIONISTA_ID it return the fowlling error :check the level set in content tab in fact table.it can happen that FACTURA.COMISSIONISTA_ID is at a lower level than specified in fact table.
    Regards,
    Sandeep

  • No Fact Table exits at the requested leve of detials

    Hi All,
    I am getting the follwoing error..while am into Oracle Answers...
    Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
    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: [[AP Invoice Payments.Payment Terms.Payment Term Name],,,,,,,,,,[Suppliers.Suppliers.Supplier Name],,,,,,,,]. (HY000)
    SQL Issued: SELECT 0 s_0, "Business Area : Accounts Payable"."Payment Terms"."Payment Term Name" s_1, "Business Area : Accounts Payable"."Suppliers"."Supplier Name" s_2 FROM "Business Area : Accounts Payable"
    any ideas to correct this problem ?
    Thanks in advance,

    Hi,
    You have to go to the fact LTS and set granularity for each dimension associated with it. You might be bringing a column from a dimension in your report, for which you didn't set up granularity in the facts LTS.
    Thanks
    Venkat
    OBIEEDeveloper

  • No fact table exists at the requested level of detai error

    Hi Gurus,
    Gud Evening,
    There is a report with 10 columns and its coming fine when ever we are adding new column some date column (Start Date) it is showing the below 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:
    Can any give some suggestions..
    Regards

    Hi,
    You have to go to the fact LTS and set granularity for each dimension associated with it. You might be bringing a column from a dimension in your report, for which you didn't set up granularity in the facts LTS.
    Thanks
    Venkat
    OBIEEDeveloper

  • OBIEE 11g - No fact table exists at the requested level of detail

    My dimesion tables are snow-flake.
    Table1 has Key, ProductName, ProductSize, Table2Key
    Table2 has Key, ProductDepartment, Table3Key
    Table3 has Key, ProductDivision
    I have created 2 hierarchies (in same dimension Product). Note: ProductSize is in Table1.
    ProductDivision > ProductDepartment > ProductName (shared level)
    ProductSize > ProductName (shared level)
    There are 2 fact tables
    Fact1 is at ProductName level
    Fact2 is at ProductDepartment level
    When I create a request with columns as ProductSize and some measure; and filter it on ProductDepartment. The request fails with error "No fact table exists at the requested level of detail", but the request can ideally be answered using fact with ProductName level.
    I have properly defined logical level keys in the hierarchies and logical level in the LTS (content tab)
    Can anyone point me what I am doing wrong here?

    Since both fact tables are at same granular level I would suggest to map each other (Signon_A maping Signon_B) in BMM layer logical fact @source.
    Considering them as Fact and with fact extension.
    BTW: Did you try by setting implicit fact at subject area properties?
    Edited by: Srini VEERAVALLI on Feb 1, 2013 9:04 AM

  • No Fact Table Exists at the request level of Detail

    Hi,
    I'm new to BI.can anybody come across more than one fact table in BMM layer,currently i working with AP module,i am getting the error Error NO:14025 No Fact Table Exists at the request level of Detail.
    Even i check with content tab where i have given detail level for confirming tables and total for non-confirming tables.
    can any one have document related more than fact table in BMM layer, any body give me the right solution.
    Thanks in advance !

    thanks for your response,i did for the selected measures also. in Account payable model i have two fact.
    F1 with dimension D1,D2,D3,D4
    F2 with Dimension D5,D6,D7,D8
    when i'm trying to generate reports F1 with D1,D2,D3,D4 i am getting the output,but with the non-conforming table D5,D6,D7 i am getting the error. can you give some document to work more than 1 fact table.

  • No fact table exists at the requested level

    Hi,
    I have a 3 dimension tables and D_CANDIDATE, D_QUALIFICATION, D_SERIES. D_CANDIDATE is linked with D_QUALIFICATION and D_SERIES. If i create a analysis with all the 3 dimensions i am getting this error. no fact table exists at the requested level. When i remove D_SERIES from the analysis it is fine. What i might have done wrong. Can anyone help me out please.
    Regards,
    Natesh

    So I'm assuming your joins are like
    D_CANDIDATE--> D_QUALIFICATION
    D_CANDIDATE--> D_SERIES
    Then treat D_CANDIDATE as logical fact in BMM and use reports, it is nice to have default hierarchies for D_QUALIFICATION and D_SERIES. in this case D_QUALIFICATION and D_SERIES are logical dimension tables in BMM
    Edited by: Srini VEERAVALLI on Apr 4, 2013 8:05 AM

  • How to change the fact table in backend query

    Hi
    I have a criteria where f1 is the fact table comming in backend query, how can I change/modify so that if i select same criterian it should come different fact table f2.
    Please suggest.

    Hi Hussain,
    I have a measure 'po amount' which is comming from two fact tables cost_f and line_f from physical layer. I have a implict fact column in presentation layer on a column(internal-row count) from cost_f table.
    Now, when I take only 'po amount ' in criteria, in the backend query it should have cost_f table, but i am seeing line_f table.
    The reason I am checking in this direction is.
    I have criteria with 4 columns and measure column 'po amount' and run the result it is fecting from line_f table.
    The same 4 columns and measure column 'po amount' and one new column 'cost center' is added to the critera the fact table changes to cost_f table.
    In both the cases the result should result from cost_f table, not sure why line_f is comming in backend query.
    Please suggest.

  • Fact table enriched with hierachy information

    Hi Guys,
    I have a fact table design question.
    The fact data table (oracle10g) on bottom level RelationshipManager (RM) contains the data columns
    for the RM dimension:
    FACT TABLE
    ID¦RM¦DEPARTMENT¦AGENCY¦REGION¦SALES
    1---23--Bronx------------NY---------US-------23232
    2---24 ---------------------NY---------US-------87878
    3---25-----------------------------------US------ 9999999
    This means the fact has been enriched with hierachy information, this is not whats usually done.
    Why have I done it? Because the RM is not necessarily always part of a department BUT can also
    be directly placed under an agency or a region (agency or region leads).
    Have I made the right choice by chosing to enrich the fact table? I could have also build a snow flake
    schema by storing hierachy information in a seperate table.
    Thanks.

    with your problem, it might be best to split the dimension into multiple dimensions or multiple attribute dimensions with default values where you do not have a value for example set up RM with a N0_RM and when you don't have data load it there. If I'm looking at this correctly, the problem it appears you have is you have an inconsistent hierarchy. where the rollups can change. having them in the same dimesion would be problematic. If therewere consistancy then you could add members into a single hierarchy something like
    US
    --No_State
    --NY
    -----Bronx
    ------RM23
    ------No_RM
    but from your example I don't see it. If they are seperate dimensions(not attribute dimensions) then you could load based on date. If they are attribute dimensions, then look at varying attributes

  • Multiple Date Fields (Fact Table) - Linking with Time Dimension

    I have a fact table that has multiple date columns.
    I can make a time dimension, but it has to be joined to a particular date column. This becomes difficult because of the limit in having multiple date fields reference one time dimension. I can see possibly
    creating a date table which contains all dates, link to fact as well as time dimension table. I am trying to better visualize the table layout on this one. Or are there possibily better ways of looking at this senerio
    Any idea's

    Figured this one out; going to use one time dimension - what looking too much into the details in regard to this scenerio

  • Joining two fact tables with different dimensions into single logical table

    Hi Gurus,
    I try to accomplish in Oracle Business Intelligence 11.1.1.3.0:
    F1 (D1, D2 and D3)
    F2 (D1 and D2 and D4)
    And we want to build a report F1 F2 D1 D2 D3 D4 to have data for:
    F1 that match only for D1-D2-D3
    and data for
    F2 that match only D1-D2-D4
    all that in one row, so D3 and D4 are not common dimensions.
    I can only do:
    F3 (D1, D2)
    F4 (D1, D2 and D4)
    And report
    F3 F4 D1,D2,D4 (all that in one row, and only D4 is not a common dimension)
    Here is the very good example how to accomplish the scenario 1
    http://108obiee.blogspot.com/2009/08/joining-two-fact-tables-with-different.html
    But looks like it does not work in 11.1.1.3.0
    I get
    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: [,,Clients,,Day,ROI,,,,EW_Names,,,,,,,,,,,,,,,,,]. (HY000)
    I am sure I set up everything correctly as advised in the blog but it works with only one not a common dimension
    Is it a bug in 11.1.1.3.0 or something?
    Thanks,
    Kate

    Thanks for all your replies.
    Actually, I've tried the solutions you guys mentioned. Generally speaking, the result should be displayed. However, my scenario is a little bit tricky.
    table Y's figures are not the aggregation of table X for D dimension. Instead, table Y's figures include not only D dimension total, but also others (others do not mean A, B, C dimension). For example, table Y stores all food's figure, while table X stores only drink's figure. D dimension is only about drink's detail. In my scenario, other foods' figure is not provided.
    So, even if I set D dimension to all/total for table X, table X's result is still not the same as table Y.
    Indeed, table Y does not have a column key to join to D dimension's key. So, if I select D dimension and table Y's measures at the same time in BI Answer, result returns no data. Hence, I can't compare table X and table Y's results with selection of D dimension.
    Is there any solution to solve this problem?
    Edited by: TomChan on Jun 3, 2009 9:36 AM

  • Using 2 fact tables with different granularity against calendar dimension

    Hello gurus,
    I have a requirement to provide a report to show the consumption of available capacity per month and also YTD.
    I have two fact tables:
    Fact table ‘Capacity’ with columns:
    - Site_id
    - Month_id
    - Capacity
    Ie.
    001, 2010M01, 50
    001, 2010M02, 50
    001, 2010M12, 75
    002, 2010M01, 60
    002, 2010M02, 65
    002, 2010M12, 80
    Etc
    Fact table ‘Consumption’ with columns
    - Site_id
    - Day_id
    - Consumption
    Ie
    001, 20100101, 2
    001, 20100102, 3
    001, 20100131, 1
    001, 20100201, 5
    001, 20100212, 6
    001, 20100228, 4
    Etc
    As can be see above, my ‘Capacity’ table contains monthly volumes, and the ‘Cunsumption’ table contains daily volumes.
    My Calendar dimension is straightforward:
    Year
    Quarter_id
    Month_id
    Day_id
    Ie
    2010, 2010Q1, 2010M01, 20100101
    2010, 2010Q1, 2010M01, 20100102
    2010, 2010Q1, 2010M01, 20100103
    2010, 2010Q1, 2010M01, 20100104
    Etc
    The MfgSite dimension is also simple:
    Site_id
    Site_name
    Group
    These are the steps I have taken sofar:
    - Imported the four tables
    - Created following joins:
         MfgSite.Site_id = Capacity.Site_id
         MfgSite.Site_id = Consumption.Site_id
         Calendar.Month_id = Capacity.Month_id
         Calendar.Day_id = Consumption.Day_id
    - Created Business Model Diagram in BMM
    - Created Calendar hierachy:
         Year, Quarter, Month, Day
    - Created MfgSite hierarchy:
         Group, SiteName
    - Setup Logical Table Source / Content settings as follows:
         Fact table Capacity:
              Dimension MfgSite: Logical Level = Site
              Dimension Calendar: Logical Level = Month
         Fact table Consumption:
              Dimension MfgSite: Logical Level = Site
              Dimension Calendar: Logical Level = Day
    - Set Default Aggregation Rule to Sum on Logical Columns:
    Capacity.Capacity
    Consumption.Consumption
    - Created following YTD Logical Columns:
         YTDCapacity = TODATE(Capacity.Capacity, Calendar.Year)
         YTDConsumption = TODATE(Consumption.Consumption, Calendar.Year)
    - Created Presentaion layer
    I then built a few reports to test it out and found that I have an issue with the Capacity object: When I build a simple report to show capacity per month:
    SiteName, Month, Capacity
    the capacity for each month is multiplied by the number of calendardays in that months, so I get
    Site      Month      Capacity
    001      2010M01      1550 (= 31 x 50)
    001      2010M02     1400 (= 28 x 50)
    Etc
    In addition, when I add YTDCapacity to my report, the report fails with the following message:
    Unable to navigate requested expression: ToDate(Capacity:[DAggr(Capacity.Capacity by [ Calendar.Year, Calendar.Month_id, MfgSite.Site_id, MfgSite.SiteName] )], [Level Year]). Please fix the metadata consistency warnings. (HY000)
    Did I miss any steps? Any help is greatly appreciated!
    Thanks!
    Randall

    hi in the capacity fact table remove the level set for the calendar dim and see.

Maybe you are looking for