Expanded hierarchies in workbook...

Hi All,
We are getting a weird problem when we are refreshing a query in workbook
When data is refreshed, the values pull into the hierarchy top level, but not the detail level. After expanding and collapsing the hierarchy node, the values is then displayed.
This is kind of confusing!!!!
Any ideas will be really appreciated !!!
Thanks

Hi........
Hierarchy Active
You use this function to switch display hierarchies on and off.
Hierarchy Node Expanded
Select Hierarchy Node Expanded if you want to expand a hierarchy node. If you want to collapse the hierarchy node, deselect the indicator. You can also expand or collapse the hierarchy node by choosing the hierarchy icon.
Expand Hierarchy :
Choose Expand Hierarchy ® Level <1> if you want to display more levels of the hierarchy. You can also expand the hierarchy by choosing the hierarchy icon. For more information
Also check this link :
http://help.sap.com/saphelp_nw70/helpdata/en/f1/0a5543e09411d2acb90000e829fbfe/content.htm
It may help you........
Regards,
Debjani......

Similar Messages

WorkBook Formatting.

Hello All,
Can i get parent child relation of hierarchies in Workbook if i need to do further formatting of hierarchies in Workbook.
If yes how where can i get these relationship.
Thanks in advance,

Hello Gill,
I have to give option to the user to diplay the hierarchy level depending on there requirement not with BEX display level option.
Lets say maximum of 8 levels in hierarchy. I have to display only the 1st level and rest will be when workbook is executed first time. Now depending upon the user option it can be expanded and collapsed.
I have done this with presently depending on the indentation.
But is there any other way to get this in workbook.
Also can i get the default level of hierarchy which is set in the query.
Let me know if it is still not clear.
Thanks,

EVGTS to get data from multi-applications in a workbook of multi-worksheet?

Dear all:
Situation
I am trying to build a financial report that consists of:
1. Balance Sheet (Finance App)
2. Profit and Loss (Finance App)
3. Sales Analysis (Sales App)
4. Inventory Flow (Sales App)
5. Expense Report (Finance App)
Basically, I need the data from No.2 to No. 5 to get No.1 Balance Sheet.
Problem
When I refreshed or expanded the entire workbook, sometimes the other application's EVGTS would not get refreshed, and the cells either showed 0 or #RFR.
Question
1. For my EVGTS, I noticed that for the dimensions shared by both Finance and Sales Applications, I didn't include those members in my function. Could this be the reason? But I thought EVGTS would fill in the missing memebers directly from the Current View, or it has the limitation to one single Application?
2. Also, EVGTS sometimes seems to refresh itself upon any change in my current view, and sometimes not. What is causing this behavior?
Thank you!
Have a nice long weekend to some of you...
Brian

There is a golden principle, Excel (Not BPC Excel client software) itself will take care about order of calculation. So, if your first sheet uses 2nd sheet's data, Excel will refresh 2nd sheet prior to 1st sheet. I am sure about it but what I am not sure is possibility of bug. Because I already heard similar issue as yours from other customer/consultant.
If one of your sheet in workbook required other sheets' refresh, I suggest to use VB macro to make sure refresh sheet 2-5 then refresh sheet 1.
But to do that, you should use EVDRE instead of EVGTS because BPC do not provides refresh by sheet macro but EVDRE.
For your first question, you are true. If your applications sharing a dimension, you do not need to fill that dimension's member. BPC client will use CV member automatically.
For second question, it depends on setting. If your BPC client has data that associated to your CV, it will be appeared. For example, you have refresh input schedule with Entity:SalesKorea. And refresh again with Entity:Sales. Then change VB again to Entity:SalesKorea. In this case, CV change to SalesKorea will make cell data change by data in cache. If you change CV to Entity:Worldwide1, your data will not be changed.

OBIEE 11g - issue when export hierarchy to a csv

Hello,
I have an issue when I try to export to a csv file a report containing a Logical Dimension field, when I export just the first level of hierarchy is exported and not all the records. When I export to another format (such as excel) all the records are exported correctly. Do you know what can I do in order to have all the records exported to a csv?
Thanks!
Solange.

This is a bug see below.
Bug 13083479 : EXPORT DATA TO CSV FORMAT DOES NOT DOWNLOAD EXPANDED HIERARCHICAL COLUMNS
Proposed workaround : OBIEE 11.1.1.5: Pivot Table Report Export To Csv Does Not Include Hierarchical Data [ID 1382184.1]
Mark if answered.!
Thanks,
SVS

Performance problem to retrieve the report

hi gurus
i am working in BW support, i got a issue regarding reports.
query taking to much time to retrieve the report, and the same probs arise when u try to drill down in report.
can anyone plz give me a solution to solve my problem.
thanks in advance
z

Hi Zammy:
do a search on "performance", you will got lot of answers which pertains to queries. there are lot of things involved when a query takes a lot of time :
install BW stats and analyze the queries
may be an option to use aggregates is a good idea to consider
you can multi providers to do reporting for better query performance
try to avoid " excludes" in BEx
Query Read Mode - Read when navigating and expanding hierarchies
Check if indices under ORACLE are degenerated. OSS Note 323090
OLAP Cache OSS Note # 456068
Assign points if helpful
Kalyan

OBIEE 11g - issue when export to a csv file

Hello,
I have an issue when I try to export to a csv file a report having numeric feild, when I export and open the file in notepad the trailing zeros to the right of decimal points do not show up. When export to another formats (such as excel, pdf) the trailing zeros appears correctly. e..g, 100.00 appears as 100, 100.50 appears as 100.5.
Do you know what can be done in order to have trailing zeros to the right of decimal points to appear in a csv?
Thanks

This is a bug see below.
Bug 13083479 : EXPORT DATA TO CSV FORMAT DOES NOT DOWNLOAD EXPANDED HIERARCHICAL COLUMNS
Proposed workaround : OBIEE 11.1.1.5: Pivot Table Report Export To Csv Does Not Include Hierarchical Data [ID 1382184.1]
Mark if answered.!
Thanks,
SVS

Regarding Reports performance

Hi All,
Now i am working in Production system.
How can i check the performance for reports.
How can i find the report performance is low/high?
Please let me know the details.
Thanks
Vasu.

Hi Vasu,
Use the search on the word "performance", you will got lot of answers which are related to queries.
There are lot of factrors involved regarding query performance :
1. Install BW stats and analyze the queries
2. Option of using aggregates is a good idea to consider
3. you can multi providers to do reporting for better query performance
4. Query Read Mode - Read when navigating and expanding hierarchies
5. Check if indices under ORACLE are degenerated. OSS Note 323090
OLAP Cache OSS Note # 456068
Also take a look to the OSS Note 567746 'Composite note BW 3.x performance: Query & Web' in which you can find all the info required...
Assign points if helpful
Bye
Dinesh

Global cache

Hi Experts
I want to create Global Cache on a Query to improve the performance of the Query.In RSRT we have the options of
Read Mode
         A Query to read all data at once
         X Query to read data during navigation
         H Quert to read when you navigate or expand hierarchies
Cache Mode
           1 main memory cache without swapping
           2 main memory cache with swapping
           3 persistent cache per application server
           4 persistent cache across each application server
Persistence Mode
           1 flat file
           2 cluster table
           3 transparent table(BLOB)
Optimization Mode
      0 query will be optimised after generation
Could you tell me which Mode I need to choose for the Query and how it affects.
I have created one of these options and executed , and then reun my query many times, But still it takes same amount of time to run, Could you tell me whether it is caching or not and what is the procedure to set query for caching.

files are only loaded in the system cache when specifically imported into the system cache using:
javaws -import -system <url>
/Andy

Query Read mode

HI Experts,
What is QueryReadMode? In which Scenario we have to use QueryReadMode?
1.In which situation we have to create Aggregates and how do u know weather the cube has Aggregates or not?
2.In which situation we have to create Indexes and how do u see the indexes bitmap r Btree explain me Briep
3.In which situation we have to do Compression?how can i delete requests and how can i delete records from single request & from Multiple requests based on the fixed value.
4.In which situation we have to create Partitions and how do u know weather the cube has partions or not?
5.4.In which situation we have to create LINE-ITEM Dimentions.
please any body explain me these topics with example...................
what is BW STATISTICS explain me brief......
THANKS IN ADVANCE,
PriyaKodali

HI
What is QueryReadMode?
We use the query monitor to test or regenerate queries and query views, and to check or change query properties. With the query monitor you have the option of displaying technical information about queries
Query Properties.
In the Query Properties window of the Query Monitor, we can configure settings for the Read Mode, Cache Mode etc.
The read mode of a query determines how often the OLAP Processor retrieves data from the database during query navigation. The read mode contains three types of read processes:
Read all data (setting A: Query to Read All Data At Once)
Reread the data (setting X: Query to Read Data During Navigation)
Reread the data when expanding a hierarchy (setting H: Query to Read When You Navigate or Expand Hierarchies)
WE USE T-CODE RSRT.
(H) u2013 Query to read, when you read or expand hierarchies: In H mode, the detailed information within the nodes and sub-nodes of a hierarchy are read on demand (i.e., when you expand a hierarchy node). The amount of data transferred to the OLAP processor is the least of all the three categories. The downside is that the number of database reads increases as you keep expanding hierarchy nodes. SAP recommends setting queries to the H read mode. This is based on the empirical evidence of the relative performance of queries set to each of these modes.
(X) u2013 Query to read data during navigation: In this mode, data are requested by the OLAP processor as
dictated by every navigational step. The difference between X mode and H is that in the case of hierarchies, all the data on a leaf level are completely retrieved by the OLAP processor.
(A) u2013 Query to read all data at once: There is only one read process in this mode. When you execute the query in the Business Explorer, all data in the main memory area of the OLAP processor that is needed for all possible navigational steps of this query is read. During navigation, all new navigational states are aggregated and calculated from the data from the main memory.
The read mode Query to be read when you navigate or expand hierarchies significantly improves performance in almost all cases compared to the other two modes. The reason for this is that only the data the user wants to see is requested in this mode.
What Is An Aggregate?
An aggregate stores the dataset of an InfoCube redundantly in a summarized form. In this instance, summarization means the condensing of the original fact table of an Infocube to an aggregate table. This table no longer contains certain characteristics of the Infocube and has been summarized across attributes, or to characteristic values, or a hierarchy level.
The summarization enables you to access the data of an InfoCube quickly when reporting. Aggregates are, therefore, tools for enhancing performance.
Aggregates are created from logical data packets (requests). You can distinguish between the processes of filling and rolling up
http://wiki.sdn.sap.com/wiki/display/BI/Aggregates--SAPBWQueryPerformance
3. In which situation we have to create Indexes and how do u see the indexes bitmap r Btree explain me Briep
Bit map and B-tree index - It is related to Cardinality.
Cardinality means no. of predefined options for perticular Info Object.
e.g *** of person - Male or Female - we have only two options - so it will be considered as Low Cardinality.
Document Number : their can be many document numbers depends on the no. of users. so it is considered as high cardinaltiy
If low cardinality is their, Bit map index is used.
If high cardinalty is their, B tree index is used.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0b28d18-f383-2c10-a780-a52349715b54?QuickLink=index&overridelayout=true
http://help.sap.com/saphelp_erp2004/helpdata/en/cf/21eb47446011d189700000e8322d00/frameset.htm
4. In which situation we have to do Compression?how can i delete requests and how can i delete records from single request & from Multiple requests based on the fixed value.*
Compression improves Performance Tuning as it removes the redundant data. This improvement in the performance can be checked by RSRT and running the query with compression & without compression.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c035d300-b477-2d10-0c92-f858f7f1b575?QuickLink=index&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c09b7019-4885-2e10-e2b8-fe1fef0643db?QuickLink=index&overridelayout=true
deletion of compressed cube data
Delete compressed request from cube.
5.In which situation we have to create LINE-ITEM Dimentions.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/005f3197-d3da-2e10-1a94-a5c62342f2aa?QuickLink=index&overridelayout=true

Query read mode-Cache mode

Hi,
Can u explain me the functionalities of the options:
A-Query to read all data at once
X-Query to read data during navigation
H-Query to read when u navigate or expand hierarchies
I am not clear of the diff. bet. the X,H options....
<b>Cache Mode:</b>
0-Cache is Inactive
1-Main memory cache without swapping
2-Main memory cache without swapping
3-Main memory cache with swapping
4-Persistent cache for each application server
5-Persistent cache across each application server
<b>Optimization Mode:</b>
0-Query will be optimised after generation
1-Query optimization with individual periods in days
9-Query optimization inactive
Can u explain these functionalities in detail...
Max.points will be assigned

HI,
PLease check this..
1.      Query to be read when you navigate or expand hierarchies (H)
The amount of data transferred from the database to the OLAP processor is the smallest in this mode. However, it has the highest number of read processes.
In the following mode Query to read data during navigation, the data for the fully expanded hierarchy is requested for a hierarchy drilldown. In the Query to be read when you navigate or expand hierarchies mode, the data across the hierarchy is aggregated and transferred to the OLAP processor on the hierarchy level that is the lowest in the start list. When expanding a hierarchy node, the children of this node are then read.
You can improve the performance of queries with large presentation hierarchies by creating aggregates on a middle hierarchy level that is greater or the same as the hierarchy start level.
       2.      Query to read data during navigation (X)
The OLAP processor only requests data that is needed for each navigational status of the query in the Business Explorer. The data that is needed is read for each step in the navigation.
In contrast to the Query to be read when you navigate or expand hierarchies mode, presentation hierarchies are always imported completely on a leaf level here.
The OLAP processor can read data from the main memory when the nodes are expanded.
When accessing the database, the best aggregate table is used and, if possible, data is aggregated in the database.
       3.      Query to read all data at once (A)
There is only one read process in this mode. When you execute the query in the Business Explorer, all data in the main memory area of the OLAP processor that is needed for all possible navigational steps of this query is read. During navigation, all new navigational states are aggregated and calculated from the data from the main memory.
The read mode Query to be read when you navigate or expand hierarchies significantly improves performance in almost all cases compared to the other two modes. The reason for this is that only the data the user wants to see is requested in this mode.
Compared to the Query to be read when you navigate or expand hierarchies, the setting Query to read data during navigation only effects performance for queries with presentation hierarchies.
Unlike the other two modes, the setting Query to Read All Data At Once also has an effect on performance for queries with free characteristics. The OLAP processor aggregates on the corresponding query view. For this reason, the aggregation concept, that is, working with pre-aggregated data, is least supported in the Query to read all data at once mode.
We recommend you choose the mode Query to be read when you navigate or expand hierarchies.
Only choose a different read mode in exceptional circumstances. The read mode Query to read all data at once may be of use in the following cases:
      The InfoProvider does not support selection. The OLAP processor reads significantly more data than the query needs anyway.
         1.      Cache is Inactive (0)
The cross-transactional cache is deactivated.
The following modes are possible for the active cache: The cross-transactional cache is activated.
       2.      Main Memory Cache Without Swapping (1)
The cache data is stored in the main memory. When the cache memory has been exhausted, excess data is removed according to the LRU algorithm, i.e. deleted from the memory. When a query is subsequently requested, the result is read from the InfoProvider once again.
       3.      Main Memory Cache with Swapping (2)
The cache data is stored in the main memory. When the caching memory is used up, the excess data is written to a background and can be loaded back into the cache memory when making another request.
After query-relevant data has been loaded again, the background store can no longer be used.
       4.      Persistent Cache per Application Server (3)
The cache data is stored persistently as a database table or as a file in a directory attainable from the application server. We recommend that you choose a directory that is proximate to the application server.
When you save the cache data in a database table this puts a strain on the database. However, it is also then quicker to access uncached data in the database. In comparison to storing data in, for example, a star schema (see InfoCube), fewer tables are read and fewer indexes are accessed.
       5.      Cross-Application Server Persistent Cache (4)
The cache data is stored persistently as a cross-application server database table or file in a file system in the network, accessed from the application server. In this mode there is no displacement of data and no restriction on memory size. More space is required but this method also saves time.
¡        Database table: Strain is put on the database instance for the table.
¡        File: Strain is put on the network node operating system for the file.
¡        In addition, the application server that calculates the data and network communication has to be taken into account with both storage types.
If you do not make any other settings the OLAP processor determines the optimal initial size of the table SP, that is the memory structure in which data is held and processed in the OLAP processor (see Cache Structure). This is done after the first execution and again after a period of 31 days since the last optimization. It automatically generates a report afterwards.
In the Query Properties dialog box in the Query Monitor you can implement, modify of deactivate this function. Choose one of the following options:
·        Query is optimized after generation (0)
·        Query optimization with individual periods in days (1) Here you can determine the optimization period yourself.
·        Query optimization inactive (9)
Hope this helps..
Bye,
Shashikanth.

BPC v5 and evcom

Hello all,
Hoping you can help.....
I have recently completed an implementation of a budgeting/forecasting solution in BPC v5 and have a couple of recurring issues.
As this is my first implementation using SAP BPC these may simply be down to inexperience.
1) EVcom - I am successfully using the evcom function to send comments to the database but when the linked cell contents is amended and data resent I do not get the last comment retreived. I realise that more that one record is created in the comments table in the database, how can I get the evcom to display the last record or somehow display all comment records for that intersection of dimensions?
"my first comment" - 1 comment sent fine
"my second comment" - 1 comment sent fine but on refresh I get
"my ...(2)" reflecting that there are two records for that intersection
2) Intermittent error message when expanding/refreshing an input schedule, "EVDRE encountered an error retrieving data from the webserver" - sometimes it works sometimes not
I realise this could be down to a whole host of reasons but was wondering is there is a top 5 common reasons for this error?
Many thanks
Phil

Hello Phil,
I do not have a concrete solution to your first problem, but I have experienced the EVCOM issue as well. I am not 100% sure that this is exact issue, but when users of our application append an exisiting comment (on a input schedule w/ EVDRE), then send and expand/refresh the workbook, the previously appended comment text is pasted back into the input cell.
When this happens in our application, the cell that actually holds the EVCOM formula shows the latest comment text, while the input cell still contains the previously appended comment. If I expand/refresh the workbook a second time, the correct comment is then posted into the input cell.
From what I have been able to test, it appears that when EVCOM is used in conjunction with EVDRE, the order of the procedures that are run by BPC when the workbook is expanded/refreshed is incorrect. Apparently, the appended comment text is sent to the comment tables (database) correctly, but when the workbook is subsequently expanded/refreshed, the system first, copies the current EVCOM formula value (from the cache) into the EVCOM input cell, then retrieves the EVDRE values, and finally, refreshes the EVCOM formula values from the database (with latest comment text). The problem is that once the procedure is finished, the "latest" version of the appended comment is not pasted into the EVCOM input cell.
To check to see if this is your exact issue, the next time you duplicate the problem, check the EVCOM formula itself, and see if it shows the "latest" comment text.
One workaround is to refresh the workbook twice. I have another workaround that I use, but it is somewhat more complicated and involves VBA. If you would like to hear about it, just let me know.
I have not had a chance to open a ticket with SAP support on this issue yet, but you may wish to do so.
As for the second problem, the EVDRE web-error can result from a number of things. Check to make sure your EVDRE formula and criteria are setup correctly. Also, whenever my users experience that error, the user's security rights are usually not setup correctly to view certain data being retreived by the EVDRE function.
Hope this helps clarify the issue,
Jared Thornton

Query Performance on ODS

Hi all,
        I have an ODS with around 23000 records. The ODS has around 20 fields in it (3 key fields). I built a query on the ODS. The User only inputs Cost center Hierarchy. The report does not have any calculations. It is a direct view of the fields, but the report is taking a long time to run if I select first 2nd or 3rd level of the hierarchy as the starting point. If I select the 5th or 6th level for the hierarchy then the query output is fast. With just 23000 records on the ODS I thought query performance should be fast for any level of hierarchy.
I even created an index on Costcenter, even then no improvement in performance. Is there any way to achieve faster query performance on the ODS.
Thanks,
Prabhu.

Technical content cubes[ if installed ] gives more generic statistics of query run time...
RSRT option mentioned by Sudheer is more targeted approach.
The same RSRT can be help full to do the following....[ from help.sap]
Definition
The read mode determines how the OLAP processor gets data during navigation. You can set the mode in Customizing for an InfoProvider and in the Query Monitor for a query.
Use
The following types are supported:
       1.      Query to be read when you navigate or expand hierarchies (H)
The amount of data transferred from the database to the OLAP processor is the smallest in this mode. However, it has the highest number of read processes.
In the following mode Query to read data during navigation, the data for the fully expanded hierarchy is requested for a hierarchy drilldown. In the Query to be read when you navigate or expand hierarchies mode, the data across the hierarchy is aggregated and transferred to the OLAP processor on the hierarchy level that is the lowest in the start list. When expanding a hierarchy node, the children of this node are then read.
You can improve the performance of queries with large presentation hierarchies by creating aggregates on a middle hierarchy level that is greater or the same as the hierarchy start level.
       2.      Query to read data during navigation (X)
The OLAP processor only requests data that is needed for each navigational status of the query in the Business Explorer. The data that is needed is read for each step in the navigation.
In contrast to the Query to be read when you navigate or expand hierarchies mode, presentation hierarchies are always imported completely on a leaf level here.
The OLAP processor can read data from the main memory when the nodes are expanded.
When accessing the database, the best aggregate table is used and, if possible, data is aggregated in the database.
       3.      Query to read all data at once (A)
There is only one read process in this mode. When you execute the query in the Business Explorer, all data in the main memory area of the OLAP processor that is needed for all possible navigational steps of this query is read. During navigation, all new navigational states are aggregated and calculated from the data from the main memory.
The read mode Query to be read when you navigate or expand hierarchies significantly improves performance in almost all cases compared to the other two modes. The reason for this is that only the data the user wants to see is requested in this mode.
Compared to the Query to be read when you navigate or expand hierarchies, the setting Query to read data during navigation only effects performance for queries with presentation hierarchies.
Unlike the other two modes, the setting Query to Read All Data At Once also has an effect on performance for queries with free characteristics. The OLAP processor aggregates on the corresponding query view. For this reason, the aggregation concept, that is, working with pre-aggregated data, is least supported in the Query to read all data at once mode.
We recommend you choose the mode Query to be read when you navigate or expand hierarchies.
Only choose a different read mode in exceptional circumstances. The read mode Query to read all data at once may be of use in the following cases:
§         The InfoProvider does not support selection. The OLAP processor reads significantly more data than the query needs anyway.
§         A user exit is active in a query. This prevents data from already being aggregated in the database.

Where is my dimension member

I created a new dimension member in P_ACCT and create a dimension logic (very simple arithmetic). Saved to server and processed the dimension.
My EVDRE doesn't show the new member. tried ALL, BASEMEMBERS, DEP .. doesn't show up.
Restarted desktop assuming it is a cache issue. Expand All, Refresh Workbook ... nothing changed.
Yes, i made sure the member is part of the key & member range I provided in EVDRE.
Shilpa

Hi,
If you click on the dimension in the CV, does your newly added member appear there? If no, then you need to do a full processing of the dimension and then process your application also. Then login to excel through connection wizard. If this still doesnt solve the issue, then run the program UJA_REFRESH_DIM_CACHE in SAP GUI.
Hope this helps.

Reporting Performance

Hi All,
What are the reporting performance can we do ?
Ciao
Gigi

Kumar,
You recommend using Infosets to report on ODSs instead of multiproviders. (Bullet point #5) What is the performance benefit for this preference?
Thanks,
Cynara
> Hi Gigi,
>
> Basically, they do several functions:-
>
> 1)Aggregates
> 2)OLAP cache
> 3)Precalculated web templates
> 4)Use small amount or result data as starting point
> of any queries and do the drill down
> 5)Avoid reporting on ODS and use Infoset containing
> ODS for reporting
> 6)If you use exclusion in reporting (<>), the indices
> are not used; so avoid using the exclusion but use
> inclusion
> 7)Use read mode"H" read when navigating and expanding
> hierarchies.
>
>
> TQ
> Kumar

Problem with Hirerachies

Hi Experts,
I am facing problem regarding the execution time of dashboards. I have a couple of queries in my dashboard. The execution time of this dashboard is high. One of the query has hierarchies, i guess the problem might be due to this query.
Can anyone please suggest me if there are any OSS notes available for this kind of scenario or suggestions for improving the execution time of the dashboard.
Thanks in Advance,
KR

A couple of quick and easy things to check...
First, make sure that you are not opening the hierarchy at too low a level initially. The higher up you can start in the hierarchy, the faster the query will run. Of course, some extra time will be required for the user subsequently to open levels in the hierarchy, so it is a trade-off.
Second, check the query settings in RSRT to make sure the Read Mode of your query is NOT set to "A Query to Read All Data At Once". Either of the other two options available ("X Query to Read Data During Navigation", or "X Query to Read When You Navigate or Expand Hierarchies") will give much better performance.
Hope this helps...
Bob

Expanded hierarchies in workbook...

Similar Messages

Maybe you are looking for