BI 4.1 - BICS Issue

[Former Member]

There is an issue in converting a few UNV based WEBI reports (BW data source) from 3.1 to BICS based WEBI reports (BW data source) in 4.1. This is because of a limitation of BICS that it cannot handle the measure / detail objects in query filters.

Please can you advise on the possible workarounds to handle this limitation.

[Former Member]

Hi,

I think you are right and that you cannot filter in the BICS on measures.

what you might do is have a restricted keyfigure with the filter included.

on the detail object point , I think BICS does not allow it . Maybe declaring the detail as navigational attribute?

G

[Former Member]

Thanks Gaetan.

Not sure whether restricted key figure would work as it restricts the key figure based on certain dimension values, however in our case we would need to restrict based on the constants like "Measure 1 > 250"

Navigational attribute is definitely a viable option and we are exploring the downside if it in the specific scenarios.

[Former Member]

BICS is pretty limitted in functionality compared to relational middleware in that way...

you know that what you are asking on measures is not really advised , even in relational universes.

and this because your filter will filter out different things out depending on what objects you have selected in your query panel, technically it works. usually the workaround is having a dimension object on your measure , the downside is you cannot filter on the aggregated result but on the individual item.

the alternative is a derived table joined with the measures aggregated at the correct level, joined with the fact table and then filtered as dimension, downside is performance.

[IngoH]

Hello Prakash,

you should be able to use restricted keyfigures for that - for both scenarios:

limiting it on dimension members or on measures.

regards

Ingo Hilgefort, Visual BI