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.

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..

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 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 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.

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 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

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

No fact table exists at the required level of detail

Hi All,
I am getting the below error in report level(11.1.1.6.4).
No fact table exists at the required level of detail.
Thanks & Regards,
Chandra

Hi Chandra,
One of the possibility for this error can be:
if you have 2 sets of dimension and fact say (D1 & F1) , (D2 & F2) and these are 2 sets are not connected to each other. In report criteria if you have columns from all the tables. Then the result will be.'No fact table exists at the required level of detail' error.
Regards,
Arjun.

NQS ERROR:14025 NO FACT TABLE EXISTS -after migrating from 10g to 11g

NQS ERROR:14025 NO FACT TABLE EXISTS AT THE REQUESTED LEVEL OF DETAIL in all the reports after migrating from 10g to 11g ...
then we applied the patch (One-off Patch for Bug: 11850704) for the error <<NQS ERROR:14025 NO FACT TABLE EXISTS AT THE REQUESTED LEVEL OF DETAIL>>
But after applying the above the above patch we are still getting the same error.
but in the above patch instructions file - Post deployment instructions to create the Variable
Post Install Instructions:
- To revert to the 10g navigator behavior for handling conforming dimensions,
you must set the following session variable via an init block in the RPD:
NO_FORCE_TO_DETAIL_BIN=1
The default value for the above variable is 0.
- Restart all servers (Admin Server and all Managed Server(s))
but we didn’t find the process to create the specified variable and Initialization block in the RPD
Can you please suggest us how to go further.
Our questions are:

Hi
Refer the below thread.
obiee 11g non-conforming dimensions and nQSError 14025
Might be help you/
Thanks,
satya

No fact table at the requested level error.

I have one dimension
Account
Two fact tables
Threshold and Transaction
These tables are joined to the Account Dim using Account Number.
Now when I create an analysis using Account Numbers from all three tables, it says no fact table at the requested level. If I include any other fact from both the fact tables, it populates null. It works right when I create an analysis from one dimension and either of the fact tables.
Why do we get this error and how else should it be modeled.
Edited by: 979130 on Dec 29, 2012 12:52 AM

I'm not sure about your data.. I give couple of options try them out any of one should work.
Assuming both facts are at same granular: You need to create Logical Fact table in BMM add first fact as source then, open properties wizard and add other fact table.
Assuming both facts are at Different or Same granular: You need to create Logical Fact table in BMM add first fact and then add 2nd fact as 2nd logical table source and set the content tab for both facts
Using any of the option you'll be going for metrics and use them in report.
In general: You need to let BI server let know how data is spread across tables so that BI Server can respond as you expected.
Hope this helps, Appreciate if you mark as correct/helpful
Edited by: Srini VEERAVALLI on Dec 29, 2012 12:58 PM

Date 01/01/1901 in W_DAY_D when joined to a date wid in a Fact Table

Hi
I noticed when w_day_d joined to a Fact table I am getting a CALENDER date as 10/10/1901. I have checked by joining these tables. When Fact Wid is '0',
Join is getting 01/01/1901 as date.
But I want to avoid this and display a 'NULL' value. How could I conver this date into a 'null' in Answers please.????
Thank you.

Hi,
We are using Dac Build AN 10.1.3.4.1.20090415.0146.
The start date is 01-Jan-1980 and end date 31-dec-2010.
I am interested to change the end date to 31-dec-2020.
For that I have created a custom container.
Design -> Task -> Query on SIL_DayDimension ->Parameters
Click on value, change the end_date to required value.
Save.
Setup -> Physical Datasource
Click on DataWarehouse.
Change W_DAY_D Refresh dates to null.
After running DAC W_DAY_D table is not having any record and end_date is showing as blank in paramter file
So I want to change it to original one that is as it was before.
When I de-clone it, the value for end_date is showing as Custom Format() @MM/DD/YYYY and if I add any value to it the after running dac end_date is showing as blank in paramter file and W_DAY_D table is not having any record.
Any help is greatly appreciated.
Regards,
Bhoomi

Two different dates on a same fact table.

I use OBIEE and I got some difficulties with the times dimensions and the function AGO because I used two differents dates for my measure.
My fact table:
Ordered     Delivered Amount
1/1/2009     2/1/2009     20000
1/1/2009     3/1/2009     10000
*2/1/2009* 2/1/2009     50000
*2/1/2009* 3/1/2009     50000
1/1/2010     2/1/2010     25000
1/1/2010     3/1/2010     20000
1/1/2010     2/1/2010     20000
1/1/2010     3/1/2010     15000
I have two Times Dimensions (Ordered Times AND Delivered Times) and one fact table.
I want to compare the delivered situation (Amount Qty) for the same ordered day last year
I created a prompt with a date (ex.: Ordered date <=1/1/2010 AND Delivered date >=1/1/2010) and I want to compare one year ago with 1/1/2009 (Ordered Date situation…)
I wish the results below:
Delivered Month/Amount/Previous Amount Year Ago
2/     45000/          20000
3/     35000/          10000
I got some problem cause I had the 100 000 in my previous year (Ago) and I don’t want it because it was ordered after 1/1/2009 (Previous year). I know that the ago function concerns the Sum of Amount by Delivered Date, Year -1 ...
Does somebody has a solution for this ? Thank you
Edited by: user8898885 on Feb 8, 2010 1:01 PM
Edited by: user8898885 on Feb 8, 2010 1:05 PM
Edited by: user8898885 on Feb 8, 2010 1:05 PM

Ok, i created two facts table.
But now, what's the way to know this distribution (Delivered date) for the period (Ordered date).
Because, i got the sum of the amount by the deliverd date, and the sum for the ordered date AND i can't obtain the comparaison for the same period of ordered date.
Example:
Date Ordered || Date Delivered || Amount
janv 1, 2010 || feb. 25 2010 || 40 000
janv 5, 2011 || mar 23 2011 || 60 000
I want to compare for the ordered date, the delivered distribution
Promp = Janv. 2011
Delivered || This year || Previous year
Feb || 0 || 40 000
March || 60 000 || 0
That's my situation.
i hope than the explication is correct. I think than 1 fact table with 2 time dimension (Alias) is the way to do. But you have parhaps a best practice.

OBIEE-can we link two dimension tables belonging to different fact tables?

Hi ,
I have just started with OBIEE concepts....need your views on this issue:
Fact 1 -> Dim 1, Dim2,Dim3 and so on..
Fact 2 -> Dim a, Dim b,Dimc and so on...
If I link Dim1 and Dim a with a valid key ,would that distort the star schemas to slowflake in BMM layer?
Thanks in advance!
Neha

I don't see this that would make it snowflake more like what I think as conforming dimensions. You need to make sure the grain of the measures is at what level , the they are same grain then you should be good however if they are different then you would start seeing null values.
Fact Measures use the same, conformed dimensions like Dim1 and Dim a if you trying to generate from multiple facts, the BI server was able to automatically stitch them together into a single result set. If they came from the same fact table that's easy as its only one single table, but if you are pulling from different fact tables, the conformed dimensions would allow them to be stitched into the same report
Conformance means that these sources can be mapped to a common structure – the same levels – and also the same data members.
Mark if helps.
Thanks,
SVS

Incorrect defined log. table source- 2 differen fact tables but same source

Hi Guys,
I have been struggling with this error for a while and searching this forum led me to a few posts but people seem to have a different setup such
as with Dimension tables or joining multiple facts).
My issue is that I can not even select two column from one and the same fact table.
[[screen print of issue]|www.metallon.org/test/Incorrect_source.jpg]
Thanks,
metalray
note: Total is just a calulated/derived logical colum such as A+3

Total is calculated and the calculation takes values from a DIFFERENT fact tables BUT those fact tables have the same PHYSICAL source.
so yes, there is no link between the facts but they are the same physical source anyway.....hm

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

Similar Messages

Maybe you are looking for