One of the most common error message that is seen while creating reports is shown below.
The first thing we check in case of this error is whether we have given proper levels in the content tab. Sometimes levels were not properly given in rpd and correcting it solves the problem. But this might not be the case in all scenarios. One such scenario is explained below.
I am using oracle HR schema for the demo purpose.
Physical Diagram
BMM Diagram
Dim - Employee is sourced from the physical tables Fact_Employee & Dim_Department. This is done so as to bring the employee information and department information in a single logical table.
Fact - Employee is sourced from Fact_Employee.
Dim - Location is sourced from Dim_Location which contains the geographic information.
Now lets try creating some reports.
The above mentioned criteria gives the desired result.
Now include the location information as well in the analysis.
Now when we click on the Results tab, we are not getting the desired result, instead we receive an error message stating " No fact table exists at the requested level of detail".
We received this error message after including a column from the Dim - Location table. Now when the logical request is sent to BI server, BI server gets is unable to find join between Dim_Location and Fact_Employee. The join between Location and Employee happens via Department table. So we should include this information in design so that BI server is able to generate proper physical query for the incoming logical request.
Add Dim_Department as an LTS to the Dim - Location table.
Check in the changes in rpd and try creating the report again. After making the above mentioned change, BI server will now be able to understand how to create join between Dim - Location and Fact - Employee.
The first thing we check in case of this error is whether we have given proper levels in the content tab. Sometimes levels were not properly given in rpd and correcting it solves the problem. But this might not be the case in all scenarios. One such scenario is explained below.
I am using oracle HR schema for the demo purpose.
Physical Diagram
BMM Diagram
Dim - Employee is sourced from the physical tables Fact_Employee & Dim_Department. This is done so as to bring the employee information and department information in a single logical table.
Fact - Employee is sourced from Fact_Employee.
Dim - Location is sourced from Dim_Location which contains the geographic information.
Now lets try creating some reports.
Now include the location information as well in the analysis.
Now when we click on the Results tab, we are not getting the desired result, instead we receive an error message stating " No fact table exists at the requested level of detail".
We received this error message after including a column from the Dim - Location table. Now when the logical request is sent to BI server, BI server gets is unable to find join between Dim_Location and Fact_Employee. The join between Location and Employee happens via Department table. So we should include this information in design so that BI server is able to generate proper physical query for the incoming logical request.
Add Dim_Department as an LTS to the Dim - Location table.
Check in the changes in rpd and try creating the report again. After making the above mentioned change, BI server will now be able to understand how to create join between Dim - Location and Fact - Employee.
