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.
Hi
ReplyDeleteThis is not valid in case if you are using BI apps RPD in that case you have to define the level details in the BMM layer
Are you coming across 18778462817 errors while withdrawing the funds from the MyEtherWallet ? MyEtherWallet has user-friendly interface but some users because of less knowledge get stuck in such issues. If you’re one of such users and looking for guidance to handle all troubles all at one place under the assistance of experts, you can always have conversation with the team via calling on MyEtherWallet customer care number which is MyEtherWallet Customer Service Number working all the time globally and users from any part of the nation can contact them and discuss their queries immediately.
ReplyDeleteAre you surrounded by troubles 18778462817 at the time of opening and working on the Binance exchange? Errors like login issues, sign up issues, password issues come across the path of many users and in order to deal with them, one need guidance from the experienced experts who are there to handle Binance Customer Service Number all your worries. You can always call on Binance customer care number which is functional and the team is ready to assist you at every step. You can connect with the team anytime for availing results that are easy to execute.
ReplyDelete