Showing member in different hierarchy level

hi all!
i have requirement to show data which on different level hierarchy.
my xml hierarchy : AsetHeader,AsetHdrDesc (lev1)
L Aset Number(lev0)
L Aset activation date(lev0)
i want to show all in format like this (all in same level):
AsetHeader|AsetHdrDesc|AsetNumber|AsetActivation
AsetHeader|AsetHdrDesc|AsetNumber|AsetActivation
fyi, aset number can be NULL value.
any help will be appreciated,
thx
Edited by: user13655637 on Apr 25, 2011 10:57 PM

Hi ganesh,
for this   same as normal procedure.. but in BEX analyser..  in the query  designer window  properties.. I mean select ur hierarchy and right click and > select Ristrict-> and there you can select particular level of nodes only...
so, there you can select all fourth level nodes..and  drag and drop it into right side window... and save it.. and execute the query..
so, now you can get only Fourth level nodes only in the reporting level...
i think this will helpfull to u..if it's ok ... Reward me points..
Thanks
@jay

Similar Messages

  • Aggregating data loaded into different hierarchy levels

    I have some problems when i try to aggregate a variable called PRUEBA2_IMPORTE dimensinated by time dimension (parent-child type).
    I read the help in DML Reference of the OLAP Worksheet and it said the follow:
    When data is loaded into dimension values that are at different levels of a hierarchy, then you need to be careful in how you set status in the PRECOMPUTE clause in a RELATION statement in your aggregation specification. Suppose that a time dimension has a hierarchy with three levels: months aggregate into quarters, and quarters aggregate into years. Some data is loaded into month dimension values, while other data is loaded into quarter dimension values. For example, Q1 is the parent of January, February, and March. Data for March is loaded into the March dimension value. But the sum of data for January and February is loaded directly into the Q1 dimension value. In fact, the January and February dimension values contain NA values instead of data. Your goal is to add the data in March to the data in Q1. When you attempt to aggregate January, February, and March into Q1, the data in March will simply replace the data in Q1. When this happens, Q1 will only contain the March data instead of the sum of January, February, and March. To aggregate data that is loaded into different levels of a hierarchy, create a valueset for only those dimension values that contain data. DEFINE all_but_q4 VALUESET time
    LIMIT all_but_q4 TO ALL
    LIMIT all_but_q4 REMOVE 'Q4'
    Within the aggregation specification, use that valueset to specify that the detail-level data should be added to the data that already exists in its parent, Q1, as shown in the following statement. RELATION time.r PRECOMPUTE (all_but_q4)
    How to do it this for more than one dimension?
    Above i wrote my case of study:
    DEFINE T_TIME DIMENSION TEXT
    T_TIME
    200401
    200402
    200403
    200404
    200405
    200406
    200407
    200408
    200409
    200410
    200411
    2004
    200412
    200501
    200502
    200503
    200504
    200505
    200506
    200507
    200508
    200509
    200510
    200511
    2005
    200512
    DEFINE T_TIME_PARENTREL RELATION T_TIME <T_TIME T_TIME_HIERLIST>
    -----------T_TIME_HIERLIST-------------
    T_TIME H_TIME
    200401 2004
    200402 2004
    200403 2004
    200404 2004
    200405 2004
    200406 2004
    200407 2004
    200408 2004
    200409 2004
    200410 2004
    200411 2004
    2004 NA
    200412 2004
    200501 2005
    200502 2005
    200503 2005
    200504 2005
    200505 2005
    200506 2005
    200507 2005
    200508 2005
    200509 2005
    200510 2005
    200511 2005
    2005     NA
    200512 2005
    DEFINE PRUEBA2_IMPORTE FORMULA DECIMAL <T_TIME>
    EQ -
    aggregate(this_aw!PRUEBA2_IMPORTE_STORED using this_aw!OBJ262568349 -
    COUNTVAR this_aw!PRUEBA2_IMPORTE_COUNTVAR)
    T_TIME PRUEBA2_IMPORTE
    200401 NA
    200402 NA
    200403 2,00
    200404 2,00
    200405 NA
    200406 NA
    200407 NA
    200408 NA
    200409 NA
    200410 NA
    200411 NA
    2004 4,00 ---> here its right!! but...
    200412 NA
    200501 5,00
    200502 15,00
    200503 NA
    200504 NA
    200505 NA
    200506 NA
    200507 NA
    200508 NA
    200509 NA
    200510 NA
    200511 NA
    2005 10,00 ---> here must be 30,00 not 10,00
    200512 NA
    DEFINE PRUEBA2_IMPORTE_STORED VARIABLE DECIMAL <T_TIME>
    T_TIME PRUEBA2_IMPORTE_STORED
    200401 NA
    200402 NA
    200403 NA
    200404 NA
    200405 NA
    200406 NA
    200407 NA
    200408 NA
    200409 NA
    200410 NA
    200411 NA
    2004 NA
    200412 NA
    200501 5,00
    200502 15,00
    200503 NA
    200504 NA
    200505 NA
    200506 NA
    200507 NA
    200508 NA
    200509 NA
    200510 NA
    200511 NA
    2005 10,00
    200512 NA
    DEFINE OBJ262568349 AGGMAP
    AGGMAP
    RELATION this_aw!T_TIME_PARENTREL(this_aw!T_TIME_AGGRHIER_VSET1) PRECOMPUTE(this_aw!T_TIME_AGGRDIM_VSET1) OPERATOR SUM -
    args DIVIDEBYZERO YES DECIMALOVERFLOW YES NASKIP YES
    AGGINDEX NO
    CACHE NONE
    END
    DEFINE T_TIME_AGGRHIER_VSET1 VALUESET T_TIME_HIERLIST
    T_TIME_AGGRHIER_VSET1 = (H_TIME)
    DEFINE T_TIME_AGGRDIM_VSET1 VALUESET T_TIME
    T_TIME_AGGRDIM_VSET1 = (2005)
    Regards,
    Mel.

    Mel,
    There are several different types of "data loaded into different hierarchy levels" and the aproach to solving the issue is different depending on the needs of the application.
    1. Data is loaded symmetrically at uniform mixed levels. Example would include loading data at "quarter" in historical years, but at "month" in the current year, it does /not/ include data loaded at both quarter and month within the same calendar period.
    = solved by the setting of status, or in 10.2 or later with the load_status clause of the aggmap.
    2. Data is loaded at both a detail level and it's ancestor, as in your example case.
    = the aggregate command overwrites aggregate values based on the values of the children, this is the only repeatable thing that it can do. The recomended way to solve this problem is to create 'self' nodes in the hierarchy representing the data loaded at the aggregate level, which is then added as one of the children of the aggregate node. This enables repeatable calculation as well as auditability of the resultant value.
    Also note the difference in behavior between the aggregate command and the aggregate function. In your example the aggregate function looks at '2005', finds a value and returns it for a result of 10, the aggregate command would recalculate based on january and february for a result of 20.
    To solve your usage case I would suggest a hierarchy that looks more like this:
    DEFINE T_TIME_PARENTREL RELATION T_TIME <T_TIME T_TIME_HIERLIST>
    -----------T_TIME_HIERLIST-------------
    T_TIME H_TIME
    200401 2004
    200402 2004
    200403 2004
    200404 2004
    200405 2004
    200406 2004
    200407 2004
    200408 2004
    200409 2004
    200410 2004
    200411 2004
    200412 2004
    2004_SELF 2004
    2004 NA
    200501 2005
    200502 2005
    200503 2005
    200504 2005
    200505 2005
    200506 2005
    200507 2005
    200508 2005
    200509 2005
    200510 2005
    200511 2005
    200512 2005
    2005_SELF 2005
    2005 NA
    Resulting in the following cube:
    T_TIME PRUEBA2_IMPORTE
    200401 NA
    200402 NA
    200403 2,00
    200404 2,00
    200405 NA
    200406 NA
    200407 NA
    200408 NA
    200409 NA
    200410 NA
    200411 NA
    200412 NA
    2004_SELF NA
    2004 4,00
    200501 5,00
    200502 15,00
    200503 NA
    200504 NA
    200505 NA
    200506 NA
    200507 NA
    200508 NA
    200509 NA
    200510 NA
    200511 NA
    200512 NA
    2005_SELF 10,00
    2005 30,00
    3. Data is loaded at a level based upon another dimension; for example product being loaded at 'UPC' in EMEA, but at 'BRAND' in APAC.
    = this can currently only be solved by issuing multiple aggregate commands to aggregate the different regions with different input status, which unfortunately means that it is not compatable with compressed composites. We will likely add better support for this case in future releases.
    4. Data is loaded at both an aggregate level and a detail level, but the calculation is more complicated than a simple SUM operator.
    = often requires the use of ALLOCATE in order to push the data to the leaves in order to correctly calculate the aggregate values during aggregation.

  • MDX Query to combine different hierarchy levels

    I have a cube that contains a dimension called "FirmBranch" that contains "Branch Name" as the leaf level attribute. It also contains an attribute called "Market" which is the market a branch rolls up to. My measures are "Firm"
    (the value for the host firm's branch at the lowest level), "OtherFirm" (the value for all other firms excluding the host firm - think of this as the host firm's peers), and "AllFirm" (Firm and OtherFirm combined). If I have a particular
    host firm on the slicer (which is another dimension called "SubjectFirm" related to "FirmBranch" via a many-to-many bridge table), Branch Name as part of the rows and I put Firm and OtherFirm as columns I always get
    NULL for OtherFirm. When I'm looking at the lowest level a branch either belongs to the host firm or it belongs to one of the "other" peer firms. Since I have the host firm on the slicer all of the branches belong to this firm so it does not display
    anything for OtherFirm.
    My question is - how can I get the higher level "OtherFirm" totaled at the Market level to display alongside the Firm value when looking at it at the Branch level?

    sorry, try switching the calculated measure
    ([Customer].[Customer].[All],[Measures].[Internet
    Sales Amount])

  • Dynamic reports for different access levels

    <p> </p><p>I want to create a report using Hyperion Report which will showthe data dynamically.</p><p>I have certain hierarchy in my dimesions and there are differentusers associated with different hierarchy levels.</p><p>E.g. Person1 can access only Level 0 data. Person 2 can accesslevel 1 and level 0 data. Person3 can access level 2, level 1 andlevel 0 data. Basically any user can access data of all itsdescendants.  </p><p> </p><p>All this needs to be done using same report becuase they areviewing same kind of reports , but just the different levels ofdata.</p><p> </p><p>Please guide me, how to implement this using Hyperion Reports.It would be a great help.</p><p> </p><p>Thank you.</p>

    Hi again
    Well, here's the way it may work for a compiled .CHM setup.
    If you are using compiled .CHM files, I'm guessing your software is
    modular. Meaning that at the time it is installed, the user has
    options of choosing between the following modules:
    Module 1
    Module 2 - 9
    Module 10
    In this setup, you would create help that is generic that all
    modules would need. That one would be the Master. Then you would
    create separate projects for the remaining modules. You would then
    provide it all to the person that handles the installation program
    for your application. That person would then handle configuring the
    installer application so that only help for the actually installed
    modules is installed. If a module has been excluded, help is not
    installed for that module and doesn't appear and is not available
    to the user.
    Hopefully that makes sense to you. If not, ping back and I or
    someone else will take a stab at another explanation.
    Cheers... Rick

  • Different Calculations based on Hierarchy Level

    Hi Experts,
    I have a requirement to do different calculations of results based on the hierarchy level.
    For example:
    Level A - (total of maximums)
                 Level B.1 - (maximum)
                 Level B.2 - (maximum)
                        Level C
    I need Level B to be the maximum and Level A to bo the total of the maximum values in Level B.
    For example I may have a maximum in B.1 of 100 and a maximum of 200 in B.2
    I then need to get a total of 300 in appearing in level A. Currently if I apply the maximum in the calculate results, it displays 200 in level A.
    I then need to use these numbers at each level in formulas.
    I am using BI 7.0.
    Any ideas?
    Thanks in advance!

    Hi GreenHorn123,
    According to your description, you want to apply condition with only one case statement which can affect any product region dimension. Right?
    In Analysis Services, it's not supported to use one reference pointing to all available dimensions which the lower level hierarchy has same name. In this scenario, it's better to create one dimension which combines all the products region. You can have a
    higher level for [Product-XX Region].
    If you have any question, please feel free to ask.
    Regards,
    Simon Hou
    TechNet Community Support

  • "Zoom out" on shared member defaults to different hierarchy??

    Hi Guys,
    I've created a shared member Cost Centre hierarchy in my outline. When I "zoom in" to the shared member hierarchy to level 0, then try zoom back out, level 1 is no longer the shared members level 1 as I've defined in my new shared member hierarchy.
    Instead, level 1 (from zooming out of the level 0 shared member) defaults to the rollup associated with the member that the shared member points to?? Is there a way to make the zoom out of a shared member from level 0, zoom to the level 1 in the shared members hierarchy and not the associated member that the shared member point to?
    I really hope that makes sense to you guru's :-)
    Thanks
    Dermott.

    user1113036 wrote:
    That's the way Essbase has worked from time immemorial. Annoying, isn't it?You think it's annoying in the UI? It is really annoying in the API.. A standard way to walk a tree structure is the 'preorder walk algorithm' which essentially walks down the children of the tree, the next sibling(s), then back to the parent, etc until eventually the original root node is encountered signaling that all nodes have been visited. With the behavior of Essbase described in this thread, a preorder walk actually goes into an endless loop when the 'parent' is the 'real' parent of a member and not the shared member 'parent'.
    Tim Tow
    Applied OLAP, Inc
    Edited by: timtow on Aug 24, 2008 5:37 PM

  • How to only display specific members from dissimilar hierarchy levels?

    Hi,
    I have a Business Partner that routinely wants to build a report that displays members from dissimilar hierarchy levels. For example, she wants to display member "210_UNASSIGNED EXP/ACC" from level 8 and member "E090_ADVISOR SERVICES" from level 1. When she filters on just those two members, the reports displays as such:
    She then must manually expand the "E020_CORPORATE AND EXECUTIVE" member 7 times to see "210_UNASSIGNED EXP/ACC":
    Is there anyway to make her life easier and have the report display only the "210_UNASSIGNED EXP/ACC" member and the "E090_ADVISOR SERVICES" member, even though they are from different levels?
    Thanks,
    Michael J Titera
    BI4.0 SP8.3
    SQL Server 2012

    Hello Michael
    Displaying information from mixed hierarchy levels without the context of the parent members is a reporting workflow best suited to WebI and CR. The AOLAP content can be exported as an Analysis View and then this becomes a data source for WebI and CR.
    Our previous product Voyager used to allow member selection from mixed levels without the context of parent members but it caused a lot of confusion and misinterpretation of the data, which is why we deliberately do not have it in AOLAP.
    Worth noting that BI4.1 was a big release for AOLAP with many enhancements. One is "Expand to Level". So instead of having to click 7 times to expand the hierarchy, it now just requires one mouse right-click to do the same thing.
    Regards
    Ian

  • Drill in BW hierarchy level in webi based on input control selection

    Hello Experts,
    I have a requirement in Webi. The Webi report is based on BW hierarchy and it is using hierarhcy both in the report output block and also in the report prompts. We are are BI 4.0 SP5,Patch 6. The report has input controls in it based on the BW Hierarchy. When the report is first executed,the user can drill down the hierarchy by clicking on the "+" nodes to the max level as shown in the screenshot below.
    Now, when the user selects an input control, the data gets filtered but the hierarchy level automatically expands. In other words, when they select a data hierarchy  showed in the input control the hierarchy in table is shown expanded and they want to see the  hierarchy in the table close automatically.
    So ideally its like this when a value from input control is selected.
    Whereas the user wants it to be like this automatically on selecting a particular value from the input control and not in expanded form.
    I'm aware of the Hierarchy depth function but that only takes us to a particular node based on depth and then doesn't allow further drilling after that.
    Is there any setting in webi/bex about always keeping all sub nodes closed to prevent this expansion on selection of input control?
    Thanks and regards,
    Abhishek

    Just did some research on on this and the SAP best practice: The question itself is logically incorrect.
    A report/table filter where there is a hierarchy may remove rows without respecting the hierarchy structure. For this reason, a filter can remove a parent node currently expanded and keep leaves or
      nodes collapsed. To avoid returning an empty table in this case the system automatically expands the hierarchy in the block to shows the resulting members
    Thats why it automoatically expands the hierarchy.
    Closing this thread. Thanks.

  • Hierarchy Level in report

    Hi GURUS,
    I have a requirement in report i.e. I need to display the Hierarchy level from the 4th level only, I do not want to see the first 3 levels, where do I do the settings for that in reporting.
    I was told that there can be some settings done in Hierarchy tab of that info object in report level in Values of Posted Nodes. But even that option is disabled. If this is the way I need to do it then how to enable that option or if there is a different option then would appreciate if you explain me in detail. Thanks in advance.

    Hi ganesh,
    for this   same as normal procedure.. but in BEX analyser..  in the query  designer window  properties.. I mean select ur hierarchy and right click and > select Ristrict-> and there you can select particular level of nodes only...
    so, there you can select all fourth level nodes..and  drag and drop it into right side window... and save it.. and execute the query..
    so, now you can get only Fourth level nodes only in the reporting level...
    i think this will helpfull to u..if it's ok ... Reward me points..
    Thanks
    @jay

  • Main item and Hierarchy level items in SAP EWM

    We use ERP SAP AFS and EWM 9.1
    ERP sales order 20000 - 5PCS ( Different grid values chosen and delivery is distrubuted to EWM)
    Outbound delivery order contains main item and corresponding SKU displayed with Grid values like Color, Cup and Size. (Hierarchy Level)
    20000
    20000-0001A30
    20000-0001A32
    20000-0001C34
    20000-0001B36
    20000-0001D38
    We create Warehouse tasks for SKU items ( Items 60,70,80,90,100) for picking.
    I need to process VAS activites for this.
    Price labeling and putting on plastic bag for all SKU's ( 2 VAS activity).
    I have maintained packaging specification and tried to process it.
    But here I get an error in VAS order. Because WR Qty from ODO to VAS order is not copied. It is getting deleted at the time of VAS order creation.
    Then I tried to maintain the packaging specification for item 20000 (main item) and process the VAS order. Here VAS order got created and WR Qty also displayed.
    But Picking Warehouse tasks are created for SKU items not for main items. In this case I am not able to process it also.
    Packaging specification for main item or SKU item I should consider? If it is for SKU , need to have lot of master data. Is there any link i can make maintaining packspec for main item and process the warehouse tasks for SKU.
    Which way i have to go now?
    Any suggestion please
    Please ask me if you need more inputs

    Hi Jobi,
    I agree to Juergen, you'll need individual pack specs per subitem in order to process VAS on this level. Did you think of using batches and depending characteristics for the grid values? This is how EWM for Fashion works. Then you could define only VAS pack spec for multiple grid values.
    Best regards,
    Christian
    Remark: did you consider EWM for Fashion for your implementation?

  • How to setup a 'duplicate/mirror view' with a different zoom level?

    Hi Photoshop Gurus,
    I constantly keep zooming in and out of the same images. It drives me crazy to view it at normal zoom level and zoom back into deep pixels.
    Is there a way so that I have a duplicate floating window/view that shows realtime editing of an image at a different zoom level? (Think of it like a display mirroring, but, I am trying to mirror the same document at a normal zoom level).
    This is my scenario:
    - I usually work with small images/icons.
    - I zoom deeply into an image at pixel level ~3000%.
    - Change some pixels and do editing
    - Zoom back out to 100% to view how it looks normally.
    - Repeat and repeat.
    Can I always have a 100% zoomed view along side the same document?
    Thanks for your help.
    PHOTOSHOP CS5 Mac Snow Leopard

    The navigator palette is just another document view.  Open it, put it where you want, resize it, and you can use it to control (and see) what part of the docuemnt your zoomed in view is showing.

  • We need to show User's subordinates hierarchy wise in Reports

    Hi,
    In CRM OD report Reporting level shows user's upper hierarchy..But we need Subordinates also.How can that be done in Report.

    Raju Madari wrote:
    Hi,
    In CRM OD report Reporting level shows user's upper hierarchy..But we need Subordinates also.How can that be done in Report.Most probably you post in wrong forum. this is Application Development in PL/SQL » Reports forum.

  • OBIEE 11g - formatting hierarchy levels

    Hi, I'm playing with the new hierarchy functionality in 11g. I've found in the criteria tab where it's possible to give the dimension members different formats based on what level of the hierarchy they are at (using the "Hierarchy Level Properties" dialog). This formats the dimension lables appropriately, But I also want the associated numbers to inherit the same formatting. Is there any way to do this?
    Thanks!
    Scott

    Ok, that's too bad. No way to format individual items, we're talking about thousands of accounts in an account hierarchy. I'll put in an enhancement request for this feature. I guess one related question, is there any way in answers to add a column that returns what level of a hierarchy the given row is at? If I could do that, then I could format the measures conditionally based on that column?
    Thanks,
    Scott

  • Totals not Displaying at hierarchy Level.

    Hi All,
    There are 2 questions.:
    1)I have a report G/L a/c wise profit center hierarchy report which shows as for this G/l ac this is the profit center hier and hence there corresponding currency key figure values.
    I am nt able to c the total for each G/L account..The Totals Row gets displayed randomly after Some G/L Accounts.
    Why is this??
    2)When i drill down the hierarchy, it shows the Currency value only for the expanded level but in result row it displays as * (Star) ..I can C the Currency value as it gets Expanded, but in the totals i c as *..Please advice me on this to resolve this issue. Asap
    Thanks

    Hi,
    1)I have a report G/L a/c wise profit center hierarchy report which shows as for this G/l ac this is the profit center hier and hence there corresponding currency key figure values.
    I am nt able to c the total for each G/L account..The Totals Row gets displayed randomly after Some G/L Accounts.
    Why is this??
    ---the hierarchy level the values will display like this and if you want gl accounts wise and total value then put GL account in the row section and take the remaining objects after that and see the results.
    2)When i drill down the hierarchy, it shows the Currency value only for the expanded level but in result row it displays as * (Star) ..I can C the Currency value as it gets Expanded, but in the totals i c as *..Please advice me on this to resolve this issue. Asap
    --- * will have some values. just place cursor and see the value.
    Regs,
    VAC
    Assign points if usefull

  • Dynamic hierarchy-level entering dashboard & drill-down

    Hi there,
    I have a requirement to create a report which, depending on the user that opens the report, needs to start at a specific level within an organisation hierarchy. Once the user has opened the report (which will be part of a dashboard), he should be able to drill-down the organisation hierarchy from his entry-point down. I've been able to create that report but when drilling-down it doesn't quite work. No matter at which level a user opens the report, when drilling it will drill-down immediately to the lowest level of the hierarchy, skipping (= not showing) intermediate levels.
    Here are the details:
    Organization hierarchy:
    - Org_Level_0
    - Org_Level_1
    - Org_Level_2
    - Org_Level_3
    - Org_Level_4
    - Org_Level_5
    - Org_Level_6
    - Org_Level_7
    - Org_Level_8
    Using an InitBlock each user is assigned it's a session variable ENTRY_LEVEL which contains the user's organization hierarchy level (i.e. '5'). For Testuser5 the session variable contains '5'.
    I've created the report containing two columns:
    - A dimension column called 'Organization'
    - A measure column called 'Availability%'
    In the dimension column I've entered the following formula:
    CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='0' THEN DIM_ORGANISATIE." Org_Level_0"
    ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='1' THEN DIM_ORGANISATIE." Org_Level_1"
    ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='2' THEN DIM_ORGANISATIE." Org_Level_2"
    ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='3' THEN DIM_ORGANISATIE." Org_Level_3"
    ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='4' THEN DIM_ORGANISATIE." Org_Level_4"
    ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='5' THEN DIM_ORGANISATIE." Org_Level_5"
    ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='6' THEN DIM_ORGANISATIE." Org_Level_6"
    ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='7' THEN DIM_ORGANISATIE." Org_Level_7"
    ELSE CASE WHEN VALUEOF(NQ_SESSION.ENTRY_LEVEL)='8' THEN DIM_ORGANISATIE." Org_Level_8"
    END END END END END END END END END
    In the Column properties/Column Format tab for the dimension column I've disabled Column Heading Interaction but I've set Value Interaction to 'Drill'.
    When opening the report as Testuser5, the Dimension column shows the correct dimension object from that user: Org_Level_5. However when then clicking on the dimensionvalue, the next dimension displayed is Org_Level_8, instead of Org_level_6.
    Any suggestion on how to obtain the desired result?
    Thanks!
    Edited by: The_Dutchman on Oct 7, 2009 5:31 PM

    Check in the RPD in the BMM in the dimension wheater all levels have a key that is set to use for drill down. It seems that only Org_Level_8 (the last level, detail) has key - use for drill down checked. This allow columns on the level to be displayed when driiling from up level to the current one. So maybe this is a reason that you get only Org_Level_8 data when driiling from any level from the case statement.
    Regards
    Goran
    http://108obiee.blogspot.com

Maybe you are looking for