Invoke method com.sap.ip.bi.bics.dataaccess.consumer.queryview.hierarchy failure

[Former Member]

Hi Experts,

I face one very strange issue

I created one BEx query and link to one Webi Document via BICS

In Webi side, I choose hierarchy A and only tick level 2.

It could be schedule well and work correctly.

Today I change the hierarchy from A to B in Webi query side and still tick level 2.

Then I face issue as below:

***********************************************************************

while trying to invoke the method com.sap.ip.bi.bics.dataaccess.consumer.queryview.hierarchy.IQvDrillPathElement.getCharacteristicMemberType() of an object loaded from local variable 'pathElement' (WIS 00000)

***********************************************************************

So I create one new webi document and using same query.

After building query element for webi then choose run query, BO could display correct data.

Then I re-schedule this document again and instance fail.

Then I choose edit data-provider and run query, above error message occurs

The only thing I change in Webi side is I just changed the hierarhcy we used in Webi document. Others keep same

Could you kindly provider your comment?

Thanks and best regards

Alex yang

[Former Member · Accepted solution]

Hi Experts,

We have found the root cause

This is our mistakes not related to prodcution issue

I will close this topic now

Best regards

Alex yang

[former_member188911 · Accepted solution]

Hi Alex,

would you like to share the solution so it may be of use to others that face the same problem?

Thanks!

[Former Member · Accepted solution]

Hi Simone,

No problem.

I cannot find the place to put the answer.

Please see below part for the root cause.

At first, in query side, we use hierarchy A in Webi side, we select hierarchy A as well

Then we change the hiearchy B in Webi side without changing hierarchy setting in query side (This means that in query side, it is still using A)

This difference leanding the issue

After we change the setting in query side, it works well now

Thanks and best regards

Alex yang

[former_member188911 · Accepted solution]

thank you Alex, marking this as correct

best regards,

Simone

[Henry_Banks]

Hi,

What SP and Patch are you using?  I haven't seen an error like this since 2011.

Else, if you have a reproducible workflow, you should open up your SAPRouter service connection to BW and log a support message, referencing your BEx query, and providing your webi .wid document.

Regards,

H

[Former Member]

Hi Expert,

Do you have any suggestion?

Best regards

Alex yang