Universe on BEx Query via UDT tool

[former_member203111]

Hello All,

I am trying to create a universe on BEx query and getting the following error.

CONNECTION ERROR:

Error getting InfoObject detail for the following measure unique name [Measures].[47KS9OIF3QH1D6DKY8XDDZXBJ]. ( cube ZBCS_CV11/ZBCS_VC11_Q057_CR_1 ) ➐஘㿐୴

I have created the connection and tested it and it is responding successfully but as soon as I click OK on the universe parameter screen / window so it can populate the objects on the designer I get this message.

I even tried to remove that infoobject from the BEx query and tried again but it is not working.

Note: Allow external access option check box is selected.

Any suggestion and help will be appreciated.

Regards

[Henry_Banks]

Hi,

this is a really strange one. This error has never been reported before (internally & google) !

What's your BO version, SP, Fixpack level ?

What's your BW version, SP, and any significant MDX corrections?

FYI - the connection test will only ping the BW server with your credentials. It won't parse the integrity of the BEX/UNV.

Could this be a restricted key figure with an input variable processed by authorizations or other? Maybe the user coded in the connection doesn't have permissions for that object.

Does the KF have a unique name? (keep the descriptions distinct, BO doesn't like that)

What if you do a Refresh Structure on your OLAP universe ?

What if you save your BEx query with a new name ?

just some suggestions, but this is really unexpected behaviour.

Regards.

H

[former_member203111]

Henry

We are using BOBJ 4.0

BW version is 7.0 SP1

There is no restricted KF in the BEx query and as I mentioned I even removed that infoobject from the query and tried but failed.

I used both names, technical names of an objects and then I copied the same query with different name (more business related naming convention) but same result.

There is no object from BEx query that populate to OLAP universe and even I refresh it there is no use, the error is still there.

Do you think if this is something to do with Unix as a backend or some kind of authorization issue.

Regards

[Henry_Banks]

Hi,

still need more info about versions

What Patch2.x for Bi 4.0 ?

What SP level for BW 7.01 ? Any MDX corrections ?

You should try with a SAP_ALL profile in the Universe connection as a test . SM53 should help you identify authorizations, but not sure it's the right direction.

Regards,

H

[Former Member]

Hi

Run RSRT and regenerate the query - this fixes this error.