BIA and master data p-table

[Former Member]

Dear All,

some infocubes here contain some infoobjects, e.g. 0material ,0BPARTNER, with large number of attributes. Such infoobjects are marked as 'line item' dimension in the cube defintion due to the large number of records.

All these infocubes are BIA indexed.

Some queries based up these infocubes need to display many attributes from these master data ( technically speaking , from the p-table). when I observe the query execution in SM50, I saw that huge amount of run time was spent on reading master data P-table.

My question is: I have two options below, which one will work with BIA index to speed up the reporting speed further?(by avoid reading the p-table)

A. pull all these attributes from the p-table into the dimensions of infocube

B. mark all the needed attributes as navigational attributes in master data

Thanks for your help in advance

[Vitaliy-R]

Mr/Mrs Hard Worker,

Changing display attributes into navigational attributes will have some impact on the report as well, because with nv. attributes you will have aggregation/grouping by these nav. attributes on the reports.

May be additional secondary indexes on P* tables would help?

BW7.3 with BWA7.2 will allow to index master data as well; but I haven't tested this yet, so cannot tell you if this is going to resolve your situation or not.

Cheers,

-Vitaliy

[former_member93896]

Hello,

option A won't change the runtime significantly because the (display) attributes would still need to be read by the OLAP engine from the database.

Option B will move the load from database to BW Accelerator. However, the BWA will need to move more data over the network to BW. If you have many records in the result set that will negatively impact overall runtime. Another side effect: BWA will require more memory since more data will need to be processed.

Overall, there are too many variables to give a general recommendation to model display attributes as navigation attributes.

Please test option B. And it would be great if you could post your results here

Regards,

Marc

SAP NetWeaver RIG

[Former Member]

Thanks Marc and Vitaliy for your kind suggestion

I have tested option B. The result shows that the query still reads the p-table to get the attributes, which are navigational attributes.

Index on p-table won't help in such situation since the access of p-table is done via primary index.

I think this problem can only be sovled once the p-table is loaded into BWA in the further releases.

[Vitaliy-R]

Just to make sure we are discussing complete scenario in option B - it would require not only change of disp.attrinbutes into nav.attributes in master data, but as well marking them as nav.attributes in InfoCube, re-indexing InfoCube, and changing them in query to use nav.attributes i/o disp.attributes. Is that what you have done?

Only X-tables with atrributes marked as navigational in BWA-indexed InfoCubes are indexed in BW/BWA 7.0.

Cheers,

-Vitaliy

[Former Member]

HI Vitaliy,

I went through the exact processes described by you. thanks for your thoughtful reply.

best regards