BIA residual Benefits to Master Data and Flexible MD ?

[Former Member]

Dear BIA Colleagues:

I understand that BIA can only be built on top of InfoProviders at this time but that those BIA indexes include master data. Question about benefits of BIA for Master data:

1/ Flexible MD in a MultiProvider

We have a Multiprovider with 6 base cubes plus one flexible master data object (0COORDER) .

Is there a method to set up BIA indexes on that large master data table for performance optimization of the multiprovider (beyond having the COORDER Master data index within each cube's index)?

2/ BIA and flexible master data queries e.g. 0COORDERWill queries on a flexible master data object be faster with BIA compared to before BIA (if that master data is part of a BIA indexed Cube) e.g. is there a residual advantage of BIA on master data e.g. navigtional attributes?

3/ BIA benefit to master data in non BIA indexed cubes

Say we have two cubes A and B who share common master data and only cube A has a BIA index, will queries on Cube B see a BIA benefit for master data objects that are included within the BIA index of Cube A?

Thank you for shedding some light on this one,

Catherine

[Vitaliy-R · Accepted solution]

Hi Catherine

Re 1: InfoObject-as-InfoProvider will still be read from the database. I remember Mark Bernard from SAP RIG mentioned once that it will be optimized in the future, but not in existing release.

Re 2: Same as 1.

Re 3: Cube B will not benefit from BIA-indexed MD, because it is single statement that joins transactional and master data.

Regards,

-Vitaliy

[former_member93896]

Hi Catherine,

there's not much to add to Vitaly. Give him 10 points

If you want to make the MultiProvider faster, put all 6 Basic InfoCubes on BIA. The 0COORDER master data will be indexed only once.

In 7.0 only queries against InfoCubes will be faster with BIA. There's no impact on queries against DSO, master data (including F4-help), and InfoSets. These are topics for future BI releases.

Regards,

Marc

SAP NetWeaver RIG

[Former Member]

Hi Marc/Vitaly:

Thank you so much for the answer, that confirms what I thought. I am giving you both a 10.

One more question about master data and BIA indexing since we are on that topic:

• What are the pros and cons of making the /S table as a delta BIA index (especially for a large object such as 0COORDER)? *

SAP recommendation is to have delta BIA index only for fact tables and navigational attributes (/X and /Y). I already have setup /X and /Y for 0COORDER as a delta BIA index.

What about S tables? The last index check in BIA Monitor recommended making the /S table for master data object 0COORDER (also flexible master data in the MultiProvider) as a delta BIA index.

Due to the large size of the 0COORDER master data table, I see that it could be an issue when we do full load of the Orders since I have not seen a way to do a merge Delta Index for master data (as there is for Cubes). In that case, not sure how that impacts the indexes/cubes that share that master data.

Thank you again,

Catherine