Skip to Content
author's profile photo Former Member
Former Member

0WBS_ELEMT hierarchy through MDX universe populating random values in WebI

Hi Experts,

We are facing an issue in WebI 3.1, while creating a report on top of MDX universe with 0WBS_ELEMT hierarchy - coming from BEx query. All other hierarchies in other reports are working fine, but the issue seems to be particular to 0WBS_ELEMT hierarchy.

First of all, the WebI does not includes full project entries along with WBS hierarchy - this could be a limitation (2nd comment in https://cw.sdn.sap.com/cw/ideas/2084#comment-14280), and we found workaround as to display in seperate block.

Now the actual issue is, even hierarchy nodes of WBS element are not coming properly in the WebI. There are 5 nodes in universe (L00 to L04). We dragged all of them into the report and found that some nodes are missing. These are the L01 nodes which are not having any subordinate nodes.

Tried different combitions, and later found that if we are not keeping the nodes L02 to L04 in the query, all missing entries (in first report) are coming, but now some other nodes are getting dissapeared.

Can anyone tell the reason and/or solution for the issue. Is this the known issue with 0WBS_ELEMT hierarchy? If so, what SAP is recommending for this? This is really urgent, reply.

Regards,

Kshiteesh

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Dec 11, 2011 at 05:50 PM

    Anyone.. please suggest.

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi,

      I would go further - implement all and any correction available and relevant to you in the BW-BEX-OT-MDX component !

      So "Yes" for Note 1446246 - MDX: Composite SAP Note for flattening API based on basXML

      but also Yes for :

      a) Note 1156101 - MDX: Composite SAP note for incorrect data

      b) Note 1142664 - MDX: Composite SAP note about performance improvements

      Regards,

      H

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.