Could you please find the below symptoms and help us with any suggestions :
CASE 1 :
We had queries for COPA in 3.5 and the execution time was fine.once the output was delivered in the analyzer when we tried to do Drill down across charactersitics it was taking long time,but when we go for Filter option for the same characteristic the output was very fast.Both the options i am trying in 3.5 Analyzer once the initial output was displayed.
CASE 2 :
We have migrated the COPA data flow from 3.x to 7.0 and the user has created some test query in 7.0 Query designer.Offcourse it involves more calculations where it was taking time for execution and once after the initial dispaly,when we are trying for Filter option for the charactersitic,it was taking huge time to display the Values available for Filter as well as taking long time for the execution.
CASE 3 :
We also had queries for FI-AR which are completely created in BI 7.0 and the queries execution time was fine and even the Filter was working very fine.
offcourse we had only 1.3 Millions of records for FI-AR and we had nearly 16 Millions of records for COPA.
i have done some analysis at the BEX TAB at info object level for some Characteristics in both the Info providers where the Options are same like below :
Query Def.Filter Value Selection : Values In Master Data Table
Query Execution Filter Val.Selection : Only Posted Values for Navigation
Does the huge data in COPA causing the problem else please provide any valuable inputs to solve the issue.
Hi Sunil Kumar
Regarding the bex tab in the characteristic I would suggest to select "values in infoprovider".
Regarding the query execution in the copa do not look on the total records.
All the records that you mention are called during the query execution?
I assume that you have aggregates or not?
You have to debug the query execution in rsrt2 with different choices.
The first step i would suggest is to find where you have the big execution time (with or without aggregates).
You are familiar with the transaction rsrt2?
Yes i show that is the drill down slow. You can drill down also in rsrt2. The first run will be fast but the second one will take longer time.
Check what is the time on the different step that will produce (you have to select in debug mode "Display statistics data".
I would suggest to select also "Do not use cache"