after SAP BI 7.0 upgrade BW 3.5 work books taking long time

[Former Member]

Hi Experts,

Reecently we have upgraded our BW system from 3.5 to 7.0 version and we are using BW 3.5 bex only. AFter upgrade when users trying to refresh old work books its taking very long time to get the result. Its taking long time if we give different selections in variables and its taking normal time when we give same selections what we gave last time.

Example : If I give year 2011 and Period as 11 first time its taking long time ,if I give the same selections it taking normal time.

If I change again selections as 2011 and 10 then its taking very long time.

Please help us

Thanks and Regards,

Mahendra

[ravi_chandra3 · Accepted solution]

HI

Can u tell me what is the version of the analyzer ? Is it 2007 .

If it is 2007 then plz follow the below link

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/60bc017e-865a-2d10-0b86-9d42a5582...

In that above pdf doc refer page No 8.

Hope u got it,

Thanx & Regards,

RaviChandra

[Former Member]

initial running report workbook take time , after executing the report once again you run the report reports will come very quickly becase of cache data ,same report output kept in buffer thats why its execute very quickly.before upgrade to bi7 , did you checked the workbook .

[Former Member]

HI Rama,

Thanks for your answer . Yes thats what happening . But I need solution for this. Why its taking long time with diferent selections.

I understand that it is storing in cache and it will give quickly next time if you refresh with the same selections.But I want solution if any there first time also with quich response.

Thanks ,

Mahendra

[former_member211907]

Mahendra-

The shape rendering solution is to upgrade to a newer version of SAP-GUI. 7.2 Patch 4 to 9 (I would avoid level 0 through 3). To test this you can turn OFF the properties of your analysis grid's Display Hierarchy Icons or set them to +/-. That will avoid using the rendering engine for the graphical shapes.

We also have had serve problems with our database and how it works with the Bex 7 alternate unit of measure approach.. are you using UOM conversions ? We have not yet solved that issue, but the solution appears to be a series of database settings.