OLAP Universe after refresh, not showing LOV values and filters giving parse errors.

[Former Member]

Hi,

After reinstallation of BO XI 3.1 on client machine, I refresh the structure of an OLAP Universe.

But after refresh, it is not showing LOV values.

and while parsing all the filters are giving errors, since they are using LOV values .

Please help.

Thanks

Rahul

[Former Member · Accepted solution]

Hi,

Thanks for the replies.

Actually the Universe is using BW infocube for datasource, not BEX query.

Here are the values for two of the LOV objects:

LovVendor: [!V000005].[NAME]

LovVendorBase: [!V000005].[CAPTION]

And the filter on the same Vendor Object is:

<OPTIONAL><FILTER KEY="[!V000005]"><CONDITION OPERATORCONDITION="InList"><CONSTANT TECH_NAME="@Prompt('Vendor','A','Vendor\LovVendorBase',multi,primary_key)"/></CONDITION></FILTER></OPTIONAL>

I am not sure what [!V000005] is.

Can it be a variable from BW side or its an object in the Universe itself and i should create it.

Please suggest.

Thanks

Rahul

[Former Member · Accepted solution]

Hi Rahul,

If your universe is sourced out of infocube then, bex variables/universe prompts cannot be part of the universe, as variables are applicable for Bex layer and would work fine if the universe is sourced out of BEx layer.

Check if there was any change in connection for the universe which makes it point to BW infocube instead of Bex query?

if you are sure universe is pointing to right connection and  it has to be on top of Infocube, then you can delete the prompts from universe and do a refresh structure and export universe to reflect changes that ensure universe is in Sync with Infocube.

Thanks

Mallik

[Former Member · Accepted solution]

Hi Mallik,

I am trying to create a new Universe in Test environment, using the same Infocube.

But in the new Universe, i am not able to see the LOV variables and filters.

Does it signify something?

Please suggest.

Thanks

Rahul

[Former Member · Accepted solution]

Yes Rahul, It suggests that Infocube does not have the variables for which you are seeing prompts in the old copy of universe. Technically infocube can hold only characteristics, units, key figures. All variables/prompts, calculations(CKF and RKF) are specific to BEx layer and you would see these only in BEx universes.

As I understand, your action item would be the one mentioned above, check if universe is using right connection, if so clean off the LOV objects and prompts from universe layer and do a refresh structure and export universe. After that you can create report level prompts on same objects.

Thanks

Mallik

[Former Member · Accepted solution]

Hi Mallik,

Attached are the connection details for the Universe. I think it's using Infocube only, not BEX query.

Please check the screenshot once.

I have asked BW team to check the LOV values in their query.

Thanks

Rahul

[Former Member · Accepted solution]

Hi Rahul,

You cannot get the Universe prompts on Bex Variables working if your universe is pointing to Multiprovider and you are comparing BEx for testing the LOV of bex Variables.

You need to point the connection to BEx and refresh the universe to get the Universe prompts on Bex Variables working. or delete the Universe prompts on Bex Variables leaving the connection and universe pointing to Multiprovider and use report level prompts.

Thanks

Mallik

[Former Member · Accepted solution]

Hi Mallik,

We have found out that our Universe should be connecting to a BEX query, not a multiprovider.

We could see that BEX query in BW database.

But the problem is while creating connection to BW, i am not seeing that InfoProvider, which has the BEX query.

What could be the issue to not display the required InfoProvider and BEX query, while creating the connection.

Thanks

RAhul

[Former Member · Accepted solution]

You have to enable the below options on Query properties>Extended tab to have the query listed in the connections window.Also search by technical name

Allow external access to this query

By OLEDB for OLAP

BY Easy Query

Thanks

Mallik

[Former Member · Accepted solution]

Thanks Mallik,

The issue was with the connection only. The Universe should be connecting to a BEX query only, not a multiprovider. But somehow due to BW access issue, the BEX query was not available in the connection pool. Hence the BAPI connection pool was showing the Universe connected with Multiprovider itself.

Once we provided the proper permissions to the BEX query to be visible in BAPI connection list, and connected the Universe to it, all the objects went fine.

Thanks for all your help.

Regards

Rahul

[Former Member]

Hello Rahul,

instead of refreshing the structure, what happens when you first delete the LOV object, then refresh the structure?

Best regards,

Victor

[Prabhith]

Hi,

Please check with your BW consultant and see whether the underlying Bex query is working fine.(RSRT)

See whetr the LOVs are listed there.

If everthing is fine at the BW side, think about the BO changes like reimporting a fresh copy and so on..

Br

Prabhith

[Former Member]

Hi Rahul,

First thing would be to check if Bex still holds all those variables and also execute bex to see if there is any issue from bex side.

If everything is good on Bex side, one comparison you could do is whether you have installed the same version of client tools(including SP and FP) as you had before.

If the above BEx, Installation side is fine, and if you still have issue, take a backup copy of universe, import a fresh copy from repository, delete all filters from filters pane and LOV objects from classes pane and do a refresh structure, so that everything gets reset back to normal.

Thanks

Mallik