on 07-16-2012 9:13 AM
Hi
I am considering performance for our publications of webi reports, we will be publishing one webi report 300 times using dynamic receipients.
I need trend data for current year and prior year for Actuals, budget , forecast. All numbers will be reported in 1000's.
I can create one Bex query that retrives both Prior Year and Current Year data or two queries one for Prior Year and another for current year.
Which is better from performance when considering publication for webi reports. Considering I can update OLAP cache using EP 7.0 functionality and hence not worry too much about the Bex query run times.
1. One Bex query for Current and Prior Yr data and do most of the calculations in the BW Query and not in the BO WEbi report or
2. Split the Bex queries inot Prior Yr and Current Yr and do most of the calculations and merging of queries in BO Webi.
Note the query/queries are based on a multi cube.
Currently, I am consider option 1. What works better in BO compared with Bex.
We are using BO 3.1 SP 2 FP 2.2
Thanks
Hi,
Good question.
You want to delegate a maximum of calculations 'outside' of BusinessObjects.
whether that means pushing calcs into the BEx query, or lower still into the Cube, then this is the correct approach.
It's worth noting however, that the MDX interface of BW has many 'interoperatbility' enhancements with WebI & OLAP universes - so long as you are using 7.01 SP03 and BOE XI3.1 SP02 FP2.19 (absolute minimum) .
I have to stress however, that reference XI3.1 customers are using BW 7.01 SP08->10 with BOE XI3.1 SP03 FP3.7, or SP04 FP4.1, or SP05 .
Here's a great doc to help you proof and tune your implementation/design: https://service.sap.com/~sapidb/011000358700000750762010E
Best of luck
Regards,
H
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Henry
Thanks very much for your reply and that document is awesome !!! Will be certainly implementing some of the performance tips mentioned in our design.
the process that we will be implementing will be that power user will execute the webi report (for all possible combinations ie business lines) and review the overall numbers. Once they approve they will give the go ahead to run the publication (by business line), so for the publication we will not be refreshing the queries just using the data from the microcube/microcubes.
Now what I need to understand in a bit more detail is what happens during the publication run. I need to minimize the publication run time. I will move as much of the calculation to Bex, and minimise formulas/filters.
I know that each publication will apply the filter (we are using dynamic recipient) on the micro cube and perform the calculations for each publication. I also now that the dynamic recipient list must be sorted.
With regards to merging dimensions, does it also perform the merging of dimensions during the publication as well or has that already taken place when the queries were executed? This is the key question as that will then determine if I should split my queries (PY queries and current year queries etc) and then merge in BO or not.
Thanks
I just also want to add a link to another thread on the same topic from Matthew as he also gave an great response. http://scn.sap.com/thread/3208125
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.