BO Universe XI 3.1 - OLAP on BW Query 7.31 - LoV x Virtual Provider Issue

[former_member339069]

Hi Gurus,

We have a few pre-existing BO Universes which were based on BW queries on top of MultiProviders.

Previously, each MultiProvider had a few basic BW InfoCubes as Part Providers.

Due to a new requirement, one custom Virtual Provider was added as a new Part Provider to each of the afore mentioned MultProviders, mapping existing characteristics and two new key figures.

NB: Virtual Provider is based on ABAP Function Module with parameter interface according to Variant 2 as per SAP definitions.

All related BW queries were maintained to include the two new keyfigues as new column elements.

All related BO Universes were properly updated to reflect queries changes.

During functional tests no performance issues were reported and the two new measures worked as expected.

However one issue was noticed, previously all List Of Values (LoVs) defined in these Universes were listing "Only Posted Values for Navigation" as defined in corresponding queries in BW, but after the inclusion of the Virtual Provider all of the LoVs are listing "Values in Master Data Table", which obvisously is not desired.

I have already checked every characteristic extended property in BW queries and in all of them "Only Posted Values for Navigation" is still checked.

I have already tried the second best option which would be to have LoVs listing "only Values in InfoProvider" - both the MultiProvider and Part Providers  had their Provider-specific Properties for each InfoObject set as follows: Query Exec.FilterVal = D; to no avail either.

I have also applied SAP Note 1224318 which covers the issue of "MDX InfoProvider restrictions on member rowset". The issue remains.

I have been reading countless SAP documents, white-papers and every post I could find in SCN to try to assert possible limitations in the use of Virtual Providers together with BO Universes, but I could not find any trustful reference on LoV limitations.

Q1) Can anyone say whether or not, Virtual Providers are fully compatible with LoVs?

Q2) And if so, how can I have LoVs back working as before, in other words, listing "Only Posted Values for Navigation"?

Well, facts are:

- BO ENTERPRISE XI 3.1

- BO Universe Designer version 12.3.0.601

- BO Web Intelligence Rich Client version 12.3.0 compilation 601

- SAP BW 7.31 SP 5 (on top of HANA)

- SAP BEx Query Designer 7.30 SP 3 revision 699

Thanks in advance for any clarifications.

Best Regards,

Ricardo Nunes

[former_member339069 · Accepted solution]

Hi All,

In case someone else ever bumps into the same issue.

We have created an OSS message and SAP's answer is, in summary, that up to this date whenever a Virtual Provider is added to a MultiProvider, LoVs in BO Universes and for that matter filters / selections in variables for BW queries will always default to "Values in Master Data Table".

Based on that limitation, we have chosen to go with a workaround in the BO Universes. Basically we have added "WHERE" clauses in the objects properties to limit the range of values displayed in LoVs.

In case someone is wondering whether or not BAdI RSR_VARIABLE_F4_RESTRICT_BADI could also be used as another possible workaround, the answer is: yes, it can; but we have opted out of it for other reasons.

Regards,

Ricardo Nunes

[Former Member · Accepted solution]

Hi Ricardo,

We are planning to develop WEBI reports on top of Multi-provider (It has several Info providers out if which 2 of them are Virtual Providers)

Did you see any challenges on this approach, how is the performance?

BO XI 3.1 SP6

BW 7.0

thanks,

Susheel