Tier2-SAP Business Objects web intelligence technical tool functionality (authorization over what kind of buttons and functionality the BO Webi will present for each user)

Tier3– SAP Business Objects control on the list of folders available for each user

Training:

Training method was” train the trainer”- we have trained the Customer IT personal , they are responsible for User training.

Challenges:

1.We are the first service companies in the local market who went live with a full SAP BI project using SAP BW & SAP Business Objects 4, we had couple of problems with query performance, which eventually was stable after enhancement of SAP Notes , BO system tuning and last but not least we have established several of key development procedures for Business Object reporting over SAP BW Query as semantic layer.

2.There was several of Web intelligence functionality that wasn’t working over BW, some of them we have developed workaround, some of them reported to SAP and will be fixed in FP3 and future development

Summary:

Project went live as scheduled, SAP Business Objects reporting went live and kicking, good SAP support from SAP locally and globally

I think that the quest for better performance with webi over SAP BW yet still to be resolved

Once you understand that webi report is not BW Bex Analyzer or WAD report, you get into a new world that I call “web intelligence report modeling” .

After you have done balancing in the CMC – separated the BICS process and gave it enough memory, and maybe took the auditing off /statistics and so on

And After you take into account the advantages & disadvantages of stripping, after you realize that you have implemented SAP notes, and done you query filtering in Bex Query and not on webi ,and so on , you will figure from my opinion that you need to model you reports.

I now understand that the solution of building 1 Bex query report for all webi queries might not be the ultimate solutions as it was recommended, because of performance tuning

You need to think on how many queries you perform in 1 webi report , as you know 1 webi report has several of tabs , each tab can have several of queries which presents different type of data , it could by over one Bex query report that presents several of aggregation levels and maybe different types of data from the same query on webi . Then you might want to build several of queries that will run when necessary.

When you do refresh you will have the option to refresh each query separately or all together ,

you will also need consider query maintenance& support.You will think whether you want to do refresh when open or not.

Maybe you will need to go up to the BW info provider model and aggregates to see if its optimize for reporting and so on.

So my friend I don’t have a straight answer, it is complicated and depends on the customer requirements’, on the mass of data, on the SLA you need to be committed, and so on

I can tell you that I have done several of changes as I mentioned above in one customer and everything went fine and we have good performance, and for other customer it wasn’t enough , so I needed to change the BW model also.

I also think that BICS protocol is not 100% balanced from code writing and optimization ( you see it when you do trace in the system) and still have problems as #TOREFRESH after SP04 this is my own personal opinion