Skip to Content

Background:     

Suppose we have a Bex query with hierarchy node variable for a characteristic(like Profit Center) in the filter screen.

We have a Webi report(BO 3.x) created on the Universe on top of this Bex query.

Now in order to view the hierarchy node values for the characteristic in the prompt window of Webi report, we need to either have the same characteristic(in this case Profit Center) in the rows or in the Free characteristics restricted with the same hierarchy.

If we do not restrict the characteristic to the hierarchy in the Bex query, then we would get an error ( “A database error occurred. The database error text is: (WIS 10901)” ) while selecting values for the hierarchy node variable in the prompt window of the Webi report.

Below are the steps that reproduce the error:

BEX Query:

     We have a hierarchy node variable on Profit Center(0PROFIT_CTR) in the filters:

      Pic 1.png

     However 0PROFIT_CTR is displayed as Key and Text in the query.

      Pic 2.png

  

     When we execute the query in Bex Analyzer, we see a hierarchy selection for Profit Center.

     Pic 3.png

Limitation:

     The above requirement does not work in Webi unless the characteristic on which you have a hierarchy node variable is also restricted on the same hierarchy.

We have created a Universe on top of the OLAP query (Bex query).

We have based a Webi report on top of the Universe.


Webi Report:

          When you execute the Webi query and click on the Refresh Data button, you get the following error while refreshing the LOVs for the prompt Profit Center.

      Pic 4.png        

Possible Solutions:

    Solution A:

                                 

  1. Create a new Z* object with Reference characteristic as 0PROFIT_CTR.
  2. Add this Z* object in the Infoprovider on which your Bex query will be based.
  3. Map it with the 0PROFIT_CTR infoobject coming from the source.
  4. So now you have 2 objects mapped to 0PROFIT_CTR coming from the source:
    0PROFIT_CTR and Z* object.
  5. In the Bex query, create a hierarchy node variable on the Z* object.
  6. Display 0PROFIT_CTR as Key and Text in the query.

   

     Solution B:

  1. Create a new Z* object with Reference characteristic as 0PROFIT_CTR.
  2. Add this Z* object as a navigational attribute of 0PROFIT_CTR master data.
  3. In the transfer rules (or transformation) between the Datasource 0PROFIT_CTR_ATTR and master data 0PROFIT_CTR, map this to the same ECC field (PRCTR) to which 0PROFIT_CTR is mapped.
  4. Now in the Bex query you will have both the infoobjects 0PROFIT_CTR and Z* object.
  5. Create a hierarchy node variable on the Z* object in the Bex query.
  6. Display 0PROFIT_CTR as Key and Text in the query.

                                        Using any one of the above mentioned solutions, we can have the hierarchy node variable used in the Bex query work for the Webi report without having to restrict the characteristic on the hierarchy itself.

Hope that this blog proves helpful 🙂 !!                                               

To report this post you need to login first.

8 Comments

You must be Logged on to comment or reply to a post.

  1. Kumar S

    Hi Saxena…Good you started with first blog.

    The above requirement does not work in Webi unless the characteristic on which you have a hierarchy node variable is also restricted on the same hierarchy.

    but after that in your solution proposal you are asking for new object creation from source level. For report level display, we can customize in WEBi even.

    Can you propose resolution based on existing objects itself & it might be recommended too.

    (0) 
    1. Sabal Saxena Post author

      Hi Kumar,

      Thanks for your comments.

      Unfortunately there is nothing that can be done at the Webi level for this. We had tried out various things without any success.

      Also what I mean by new object creation from the source level is in the Business Transformation Logic layer of the LSA structure.

      This is what we had done as the number of reports where this requirement was needed were less and also the reporting layers were common to some of the reports.

      So we went ahead with Solution A.

      Solution B would come into picture if the number of reports are many built on top of different reporting layers.

      Please do let me know if you are able to find a solution at the Webi level itself.

      Thanks

      Sabal

      (0) 
      1. Ingo Hilgefort

        Hello Sabal,

        Web Intelligence supports a hierarchy and hierarchy node variable already in XI 3.1 and the steps you outlined above are not needed.

        regards

        Ingo Hilgefort, SAP

        (0) 
    2. Ingo Hilgefort

      Hello Kumar,

      Web Intelligence does support a hierarchy and a hierarchy node variable without all the steps outlined above.

      regards

      Ingo Hilgefort, SAP

      (0) 
  2. Ingo Hilgefort

    Hello Sabal,

    a hierarchy variable is supported in Web Intelligence XI 3.1 with or without the usage of a hierarchy node variable and there is absolutely no need for all the steps you outlined above.

    regards

    Ingo Hilgefort, SAP

    (0) 
    1. Sabal Saxena Post author

      Hi Ingo,

      Yes I agree that a hierarchy variable is supported in Web Intelligence XI 3.1.

      But over here I am not talking about the hierarchy variable.

      And the hierarchy node variable is supported in Webi only if the corresponding characteristic(present in either rows or Free characteristics of the Bex query) for which you have created a hierarchy node variable is also restricted on the same hierarchy.

      If the characteristic is not restricted with the hierarchy(like in the above case), then this would work at Bex level but it gives an error when a Webi report is created.

      I hope I am able to put forth my point clearly here.

      Thanks

      Sabal

      (0) 
      1. Ingo Hilgefort

        Hello Sabal,

        >>> And the hierarchy node variable is supported in Webi only if the corresponding characteristic(present in either rows or Free characteristics of the Bex query) for which you have created a hierarchy node variable is also restricted on the same hierarchy.

        That is not correct. Web Intelligence also supports a scenario where you have a hierarchy node variable without a hierarchy variable or where you have a hierarchy and hierarchy node variable together.

        regards

        Ingo Hilgefort, SAP

        (0) 

Leave a Reply