Tabular - Parent/Child hierarchy - hide duplicated rows problem

Hi All, in all the Tabular parent-child hierarchy examples I could find a measure is created to calculate current node depth. Later that measure [CurrentNodeDepth] is compared with aggregated node depth using MAX/MIN functions. The current node depth measure
uses ISFILTERED DAX functions like
CurrentNodeDepth :=     IF (ISFILTERED ('Hierarchy'[Level3]), 3,IF (ISFILTERED ('Hierarchy'[Level2]), 2,     IF (ISFILTERED ('Hierarchy'[Level1]), 1)))
All works ok until you start filtering the hierarchy - that might happen with very big hierarchies - showing only part of hierarchy to speed up calculations. Once you set a filter there, [CurrentNodeDepth] measure gives wrong output and whole parent-child hierarchy
doesn't work as it should.

Can you provide more info on this, how have you modeled the hierarchy with the fact table, are you rolling up the measures for the child to the parent level (modeling as measures) or each employee is showing its own revenue only (modeled as attribute)? If it is modeled as measures where you join the employee table to the closure table and then that to fact table then are you applying any filters in your report ? If you are applying filters in your report and somehow only parent is filtered (and not its children) then you won't be able to drill down, though you will see the + sign against it.

Similar Messages

  • Problem creating standard ECC Parent-Child Hierarchy in HANA

    Hi all -
    I've been trying to get a hierarchy to work on the front end of a stand alone HANA system using profit center hierarchy data from SETLEAF / SETNODE tables from ECC. Here is how my test hierarchy looks:
    Following another post I found around here, I created an attribute view and filtered SETNAME to 'TST_HANA'.
    The resulting data when connected to my attribute view caused an error that there was no root node, so I manually inserted the last row shown here (where PCA_PARENT = SETNAME and PCA_CHILD = SUBSETNAME):
    Finally, I created my parent-child hierarchy in the attribute view and connected that view to my data foundation in the analytic view via left-outer join between Profit Center and VALFROM. However, when I go to connect to my view via MDX in excel, I get the following message:
    "Hierarchy create error: Multiple parents not allowed for hierarchy node TST_ND1" Clearly from the data, there aren't multiple parents for TST_ND1. It's already a pain that to use a standard hierarchy I have to manually insert a root node, but that doesn't even seem to fix the problem.
    Can anyone suggest how to fix this to get a standard profit center hierarchy working?
    Thank you!
    AZ

    Hi,
    According to me, Hierarchy level will work fine in ms excel  for all analytical, calculation view using MDX Provider..
    Do you have any composite primary key or composite foreign key in the tables....
    r u getting correct level hierarchy output in Hana studio... plz check with all types of permutation possible.if u r getting correct output in analytical view w.r.t hana but fails to get in Ms excel..
    please create Calculation view of that.. & then check the output in ms-excel..
    Thanks,

  • Hide parents in a parent-child hierarchy with dynamic rights

    Hi all,
    I'm facing the following issue with dynamic rights on a parent-child hierarchy:
    scenario:
    - a cube with a company parent-child hierarcy
    - dynamic security on through a role on dimension data based on a list with user (login names) and their
    departments, with Enable
    Visual Total is switched ON 
    - Multiple facts connected to this hierarchy.
    When a user connects to the cube (in this case with Excel or through a dashboard in Performance Point services) he/she is allowed to see the facts belonging to theirs departments and all child departments, so far so good. But the totals of the facts are
    repeated for all higher parents. Now i know thats nog 'wrong' but our users think thats very confusing in some cases, so is there a way
    - to hide the parents in the hierarhcy
    - or to set all the parent measures to null/empty?
    I prefer to make a solution in the cube so that all client programs can benefit from this solution.
    thanx in advance for all input!

     so that User A have scope: [Dimension_Name].[Attribute XYZ] and User B: [Dimension_Name].[Attribute ABC] ?
    Hi Wilfred,
    If I understanding correctly, you want different user can see different dimension attributes based on the different right on role, right? 
    Based on my research, it seems that there is no a directly way to achieve this requirement. What we can do is that "Deselect all members" for each attribute of the dimension in Dimension Data tab, which will hide all members of the dimension for the role.
    Even the dimension metadata is visible in the cube in clients, its members can't be seen. Here are some useful links for your reference.
    http://saysmymind.wordpress.com/2013/01/15/hide-a-specific-attribute-hierarchy-in-role-playing-dimension-ssas-multidimensional/
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/e2596eec-7c2d-48c0-8e81-538a8c632360/hide-dimension-based-on-roles
    Hope this helps.
    Regards,
    Charlie Liao
    TechNet Community Support

  • No Results after build a Parent-Child Hierarchy in OBIEE11G

    Hi All:
    Here's an problem. I followed the "http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/" this article step by step to create a parent-child hierarchy in admin tool in OBIEE11G.
    But after check in and try to retrieve the hierarchy data in Answer. There's always displays "No Results."
    Is there any suggestions for this ? Really urgent and thanks for your help.
    Best regards
    Sunny

    @Aketi
    It is One way that We derive
    "sys_connect_by_path(RowIDToChar(RowID),'.') as
    RowIDList"
    Then
    We use Left Join Using
    "instr(RowIDList,RowIDToChar(RowID))".sorry, didn't catch what you mean.
    my site :-)
    http://oraclesqlpuzzle.hp.infoseek.co.jp/4-13.html
    pity, I don't know Japanese :(
    @Rob
    your query is good and simple :) probably it's the best alternative for the OP.
    But it won't work with not a plain hierarchy, e.g.:
          1
        2   3
          4
        5   6
    SQL> create table hierarchy (child,parent)
      2     as
      3     select 1, null from dual union all
      4     select 2, 1 from dual union all
      5     select 3, 1 from dual union all
      6     select 4, 3 from dual union all
      7     select 4, 2 from dual union all
      8     select 5, 4 from dual union all
      9     select 6, 4 from dual
    10  /
    Table created
    SQL>
    SQL> create table data (hierarchyid,value)
      2    as
      3    select 5, 10 from dual union all
      4    select 6, 25 from dual
      5  /
    Table created
    SQL>
    SQL> select h.child
      2           , sum(connect_by_root d.value)
      3        from hierarchy h
      4           , data d
      5       where h.child = d.hierarchyid (+)
      6     connect by prior h.parent = h.child
      7       group by h.child
      8       order by h.child
      9  /
         CHILD SUM(CONNECT_BY_ROOTD.VALUE)
             1                          70
             2                          35
             3                          35
             4                          70
             5                          10
             6                          25
    6 rows selected
    SQL>

  • Parent Child Hierarchy - Display other dimension fields against parent

    Hi,
    I have a Dimension for Customer with a parent child hierarchy.  The problem I have is with additional fields within the dimension.  See data below:
    Row Labels
    Customer Group   Description
    Value
    500116 - OOO "Starline"
    30
       500116 - OOO "Starline"
    A - Dealer
    5
       818781 - OKNO
    Direct / End User
    10
       400464 - OKNO TV
    Other
    15
    500123 - VIDAU SYSTEMS
    300
      500123 - VIDAU SYSTEMS
    A - Dealer
    100
      400396 - VIDAU SYSTEMS
    Other
    200
    Grand   Total
    330
    I want the Customer Group to show "A - Dealer" for the parent of the first row (against "500116 - OOO "Starline"), but its shown blank.  Also, I would like other fields to do the same.  As the parent relates to a row in
    my dimension table, this should be possible?
    Thanks in advance,
    Dominic

    Hi,
    Sorry it took me a while to come back to this.
    My dimension has the following columns:
    ID
    Customer
    Customer Group
    Parent
    1
    500116
    A - Dealer
    NULL
    2
    818781
    Direct / End User
    1
    2
    400464
    Other
    1
    My measure has 3 rows:
    customerKey
    value
    1
    5
    2
    10
    3
    15
    So when this is presented in the cube, the 3 items with values are correctly presented but my problem is that the "Customer Group" doesnt show against record 1 (the parent).  In usual circumstances my users will not expand the hierarchy, i
    just want the associated row value shown.
    Does this make more sense?  I hope so, and i hope somebody can help me resolve it.
    Thanks,
    Dom

  • No data for Parent-child hierarchy column in Pivot table view

    Hi all,
    I used OBIEE 11.1.1.6.2 Version.
    I drag one Parent-child hierarchy column and one measure and show result with a pivot table view.
    But when I click "+" icon to show detail level data,
    It messaged that: "*the layout of this view combined with the data,selections,drills,or prompt values chosen resulted in no data*."
    But it can show every-level data when I used table view.
    It was so strange..
    Did anybody meet this before?
    Thanks in advance.
    regards,
    Anne

    Hi,
    Yes, I have the same problem with pivot table for hierarchy dimension.
    If you use a normal table (not pivot) it seem to work. Unfortunatley with restrictions as normal table view have.
    Same problem still exist in 11.1.1.6.5
    I have logged a SR to Oracle about this.

  • Parent Child Hierarchy Issue in OBIEE 11g

    Hi All,
    I am in OBIEE 11G v6. I have a sales fact table where the grain is one sale. So I have one row for every sale done.
    Now I have a ragged employee hierarchy like this with David at the root node.
    David >>Richard>>Sean
    David >>James
    Also, I have a role dimension which gives me what role each employee has performed on a sale. Only one employee can be associated with one sale. This is the way Roles have been asssigned
    David = Manager
    Richard = Off1
    Sean = Off2
    James = Off2
    Both Sean and James can have same Roles. Now I have created a parent child hierarchy for my employee dimension and the closure table. Defined the member key, ancestor key relationship in the parent child setting etc.
    Now in the report when I pull the parent child hierarchy and the sales_amount in the report, it comes out perfect with all the ragged hierarchy resolved. But the issue comes when I try to limit the report on Role = Off2. It gives me an error saying " The layout of this view combined with the data, selection , drills resulted in no data. Undo drill and view prompt values". Basically what i want is to be able to select any role type and then my hierarchy should be adjusted to show me that data. Like when I select Off2, I want to see David at the Top level and Sean and James under him because they are both Off 2 and David is their manager.
    Is that possbile? Also, am I getting this error because when I select Off2 though it gets Sean and James but since David is not Off2, I don't get the data?
    I hope I was able to explain the issue, any help on this would be greatly appreciated.
    Thanks
    Ronny

    So basically this means that if I build a parent child hierarchy on table A having the stucture like
    --David (Manager)
    -----James (Off1)
    --------Bill (Off2)
    and in my sales fact table for let's say today, I have only rows for Bill (Off2) because he is the only officer who did the sales today. Now when I will join my fact table to parent child hierarchy table A I will NOT get any data ? because there is no James who is the parent of Bill. So obiee need to have parent pulled off in the data (ANCESTOR) to be able to roll up the child.(IS_LEAF = 1)
    I testes this and if my data only contains only rows for Bill (or I limit on ROLE = Off2) then it won't show the hierarchy. The query which OBIEE fires is to look for either ANCESTOR_KEY = NULL OR (DISTANCE = 1 AND ANCESTOR KEY IN (Bill). Therefore it doesn't I am wondering then what is the use of builiding the parent child hierarchy when we need to pull in all the ancestors (like in this case James for bill and David for james) because in real scenarios there can be cases wherein we would want to filter the data based on other dimensions to which the parent child hierarchy joins ?

  • Parent Child Hierarchy for Type 2

    I have read the articles on Parent Child hierarchy setup in OBIEE 11g, however, most are based on what seems to be a current snapshot of the Employee-Manager relationship. Has anyone tried to build out a Parent-Child hierarchy/table off a Type 2 dimension. Being able to navigate what the hierarchy may have been on a specific date.
    I would welcome any feedback, thanks.

    Hi,
    Thanks for the reply, I'm actually using snapshots. But even with the Type 2 Dim I don't think it will work.
    When OBIEE generates the very first sql against the Parent-Child table the fact table is not included in the query. It seems to create 2 queries - one to find the top level parent (ancestor key is null) and then one to find all the leaf nodes.
    It does not have any join to the fact table when it does this. So if you have multiple rows in the table (with date stamps) for a single row (person in this case) - it picks up both rows. Therefore, when you have a person who was, say, promoted to manager, and WAS a leaf node, and is now a manager, they show up in the leaf query and don't display in the hierarchy as a manager.
    Once it has the leaf nodes and it joins to the fact table everything works (ie the surrogate key join).
    I'm trying to figure out if there is any way to influence those initial queries against the parent-child table.
    Hopefully that made sense.
    Thanks,
    Tori

  • Parent-Child hierarchy based on two-column key

    Hello
    Is it possible to create a parent-child hierarchy, if the primary key of the table consists of two columns?
    My table looks like:
    TRACE_ID | DIAG_ID | SUPER_DIAG_ID
    with TRACE_ID and DIAG_ID as PK.
    If I define only DIAG_ID as PK, I can add a logical dimension (PC-hierarchy) without problems.
    However when I also add TRACE_ID to my PK, I cannot select a member key in the new logical dimension window and therefore not create a logical dimension.
    Is this a limitation of OBIEE and I have to merge the two colums (which would be rather bad, as there are FK relations to DIAG_ID) or is there a solution?
    Regards
    Matthias

    Dear Gowtham  ,
    I am very well aware of the level based hierarchy available in BO .
    The issue that i have raised is all about the Parent Child Hierarchy which creates the recursive query.
    I.e Every Parent has a child and that child can be parent of some other . (See the original example for more illustration)

  • OBIEE 11g Parent Child hierarchy

    Hi,
    I'm trying to setup a parent-child hierarchy dimension. I have setup a new hierarchy dimension using numeric keys but want to display another field in the hierarchical column on a report e.g. employee fullname & not the member_key based on a numeric value. Can this be done & how do you do it? All the examples I have seen use varchar2 type columns as the keys to do this.
    Thanks in advance, Phil
    My Setup
    =============
    Dimension - logical level
    ===============
    member key = employee_id
    parent-child table source
    ===============
    member key = employee_id
    parent key = supervisor_id
    relationship distance = levels_removed
    leaf node identifier = isleaf
    Employee logical folder
    ==============
    employee_id ( number)- primary key
    full_name (varchar2) - unique key
    supervisor_id ( number)
    Closure table
    =========
    employee_id ( number)
    supervisor_id ( number)
    level ( number)
    isleaf ( number)

    Thanks for the link Suresh but the aggregations are working correctly.
    My problem is only at the display level. I need to create a dashboard that displays the complete hierarchy.
    So for example if I have this hierarchy:
    - Steven King
    - Adam Frip
    Alexis Bull
    Anthony Cabrio
    Alberto Erraruriz
    Den Raphaely
    I want the dashboard to display immediately that complete hierarchy. If someone adds a member to the hierarchy in the database, the dashboard should display this new member without having to manually modify the dashboard.
    - Steven King
    - Adam Frip
    Alexis Bull
    Anthony Cabrio
    - Alberto Erraruriz
    Mozhe Atkinson
    Den Raphaely
    Also, if I just manually open the hierarchy and save the dashboard, if "Steven King" is replaced by "Shanta Vollman", the dashboard doesn't like it and returns a result looking like:
    - Adam Frip
    Alexis Bull
    Anthony Cabrio
    - Alberto Erraruriz
    Mozhe Atkinson
    Den Raphaely
    + Shanta Vollman
    So I'm looking for some option that will tell OBIEE to open the hierarchy without having to specify "Drill down on member "Steven King"", "Drill down on member "Adam Frip"...
    I hope I'm explaining correctly...

  • Script populate parent-child hierarchy not running

    Hallo guys
    I have problem when running script populate Parent-Child Relationship Table.
    Here is the script.I don't even change the script.just run it in PL/SQL
    declare
    v_max_depth integer;
    v_stmt varchar2(32000);
    i integer;
    begin
    select max(level) into v_max_depth
    from V_D_BRANCH
    connect by prior BRANCH_KEY=PARENT_BRANCH_KEY
    start with PARENT_BRANCH_KEY is null;
    v_stmt := 'insert into DM_ANALYTICS.BRANCH_HIERARCHY (MEMBER_KEY, ANCESTOR_KEY, DISTANCE, IS_LEAF)
                select BRANCH_KEY as member_key, null, null, 0 from V_D_BRANCH where PARENT_BRANCH_KEY is null
                union all
                select  member_key,
                replace(replace(ancestor_key,''\p'', ''|''), ''\'', ''\'') as ancestor_key,
                case when depth is null then 0
                else max(depth) over (partition by member_key) - depth + 1
                end as distance, is_leaf
    from
    select member_key,depth,
    case     when depth is null then '' || member_key
    when instr(hier_path, ''|'', 1, depth + 1) = 0 then null
       else substr(hier_path, instr(hier_path, ''|'', 1, depth) + 1, instr(hier_path, ''|'', 1, depth + 1) - instr(hier_path, ''|'', 1, depth) - 1)
    end ancestor_key,
    is_leaf
    from
        (    select BRANCH_KEY as member_key, PARENT_BRANCH_KEY as ancestor_key, sys_connect_by_path(replace(replace(BRANCH_KEY, ''\'', ''\''), ''|'', ''\p''), ''|'') as hier_path,
          case when BRANCH_KEY in (select PARENT_BRANCH_KEY from V_D_BRANCH ) then 0 else 1 end as IS_LEAF
    from V_D_BRANCH 
    connect by prior BRANCH_KEY = PARENT_BRANCH_KEY
    start with PARENT_BRANCH_KEY is null
      ( select null as depth from dual;
    for i in 1..v_max_depth - 1 loop
    v_stmt := v_stmt || union all select '' || i || '' from dual;
    end loop;
    v_stmt := v_stmt || ) )
    where ancestor_key is not null;
    execute immediate v_stmt;
    end;
    but I got errors like following:
    Error report -
    ORA-06550: line 19, column 12:
    PLS-00103: Encountered the symbol "insert into DM_ANALYTICS.BRANCH_HIERARCHY (MEMBER_KEY, ANCESTOR_" when expecting one of the following:
       ( - + case mod new not null <an identifier>
       <a double-quoted delimited-identifier> <a bind variable>
       continue avg count current exists max min prior sql stddev
       sum variance execute forall merge time timestamp interval
       date <a string literal with character set specification>
       <a number> <a single-quoted SQL string> pipe
       <an alternatively-quoted string
    06550. 00000 -  "line %s, column %s:\n%s"
    *Cause:    Usually a PL/SQL compilation error.
    *Action:
    what should I do guys?any idea,any solution would be appreciated.thanks alot guys

    956850 wrote:
    hi,
    i tried making "Dimension with Parent-Child Hierarchy" as described in your tutorials.
    i finished with the admin tool and database changes and with no errors.
    when trying to create a new answer, by only puting the hierarchy column in the answer.
    the result show "no result" exist.
    i am not sure what i am doing wrong. maybe you can point me to the problem?
    thanks
    Mirit.Hi Mirit,
    What is the table that you created hierarchy on?
    Which column in the hierarchy you pulled into your reports to see the No Result message?
    Please query the table and see if has data.
    Thanks,
    G. SK

  • Parent Child Hierarchy in OBIEE 11G

    Hi All,
    I am working on the parent child hierarchy in OBIEE 11g Source ESSBASE ..followed some of the blogs.
    http://www.rittmanmead.com/2010/07/obiee-11gr1-enhancements-to-essbase-support/
    I followed the following steps.
    1.Imported the Cubes from ESSBASE.
    2.Selected Accounts Hirearchy and changed the Hierarchy type to Value.
    3.Dragged the subject area to BMM and to Presentation.
    4.Now when i checked the Account Hierarchy from in the dashboard its not drilling down.
    If i change the Hierarchy type to Unbalanced ...then the Account hiearchy is working fine.
    Is there is any settings or process i have to follow..inorder to implement the Value based Hierarchy in OBIEE 11G source ESSBASE.
    Thanks

    So basically this means that if I build a parent child hierarchy on table A having the stucture like
    --David (Manager)
    -----James (Off1)
    --------Bill (Off2)
    and in my sales fact table for let's say today, I have only rows for Bill (Off2) because he is the only officer who did the sales today. Now when I will join my fact table to parent child hierarchy table A I will NOT get any data ? because there is no James who is the parent of Bill. So obiee need to have parent pulled off in the data (ANCESTOR) to be able to roll up the child.(IS_LEAF = 1)
    I testes this and if my data only contains only rows for Bill (or I limit on ROLE = Off2) then it won't show the hierarchy. The query which OBIEE fires is to look for either ANCESTOR_KEY = NULL OR (DISTANCE = 1 AND ANCESTOR KEY IN (Bill). Therefore it doesn't I am wondering then what is the use of builiding the parent child hierarchy when we need to pull in all the ancestors (like in this case James for bill and David for james) because in real scenarios there can be cases wherein we would want to filter the data based on other dimensions to which the parent child hierarchy joins ?

  • Empty parent-child hierarchy if a date attribute is "1800-01-01 00:00:00.000"!

    I have an Employees dimension that contains a parent-child hierarchy as the supervisor->employees (Org. chart. starts from the CEO to the lowest level of employees). The hierarchy is built on a relation between the employee_id (as the primary and
    surrogate key) and supervisor_id (as a foreign key). There are many other attributes in this dimension one of them is the Termination_Date. The value for Termination_Date for the current employees in the source
    system is "1800-01-01 00:00:00.000" (which is also the default value). The weird thing is that keeping this value in the employee dimension will cause the previously mentioned parent-child hierarchy to show nothing! if I change it to any other
    value or NULL, the hierarchy works fine and shows the expected tree of employees!
    I can change "1800-01-01 00:00:00.000"  to Null in the ETL stage and solve the problem, but I want really to know what causes this ?  why ?!

    I have an Employees dimension that contains a parent-child hierarchy as the supervisor->employees (Org. chart. starts from the CEO to the lowest level of employees). The hierarchy is built on a relation between the employee_id (as the primary and
    surrogate key) and supervisor_id (as a foreign key). There are many other attributes in this dimension one of them is the Termination_Date. The value for Termination_Date for the current employees in the source
    system is "1800-01-01 00:00:00.000" (which is also the default value). The weird thing is that keeping this value in the employee dimension will cause the previously mentioned parent-child hierarchy to show nothing! if I change it to any other
    value or NULL, the hierarchy works fine and shows the expected tree of employees!
    I can change "1800-01-01 00:00:00.000"  to Null in the ETL stage and solve the problem, but I want really to know what causes this ?  why ?!

  • Parent Child Hierarchy Issue

    Guys,
    I have a parent-child hierarchy and users would select a randomn level from the prompt (Hierarchical column used in the prompt). So for the level selected I need to capture all the leaves and put a top n function on them.. Any ideas??
    Things that i have tried are using Selection steps with hierarchical columns.
    Step 1: Start with all Memebers
    New step: Step 2 is Selected Members based on hierarchy relation Ship (Keep only members of leaves of hierarchy)
    But the problem is I am not able to override the Step -2 with dashboard prompt. I was able to do only fior STEP -1
    So any ideas??
    If i can atleast capture all the leaves of selecte level from the prompt that would solve my problem to a large extent?/ Thought abt Hierarchical Navigation Functions but didnt succeed?? Any suggestions really appreciated
    Thanks..
    Prash
    Edited by: Prash11 on Aug 6, 2012 11:14 AM

    I have got lot of hierarchies which are atleast 20 levels deep. So its not really feasible for me to create multiple views for multiple levels.
    I tried to use hierarchical column functions and it works but not able to override the values from prompts in the selection steps. So still trying few things
    Step 1: Start with All members (over ride with prompt checked)
    Step 2: Select a level with in the hierarchy and Keep only leaves of the selected level
    Step 3: Apply Condition do a TOP 10 and keep only that result set.
    This works fine with out any issues from an ad-hoc stand point. Only problem there is no way for me to over ride the dashboard prompt value in Step - 2 as it expects me to select a value from the hierarchy. Any alternativeS?

  • Except function with parent child hierarchy using mdx query

    HI,
    I need to remove some items using mdx query in parent child hierarchy.
    I tried with below query,it is not removeing ,could you please help me.
    SELECT
    {[Measures].[Amount]} ON
    COLUMNS
     NonEmpty([Account].[Accounts].[Account Level 01],[Measures].[Amount])
    ON ROWS
    FROM (SELECT
    -Descendants({[Account].[Accounts].&[47]},,Leaves)
    } ON COLUMNS
    FROM [Adventure Works])
    indu

    Hi Indu,
    Why do you remove some itmes using
    Descendants function? Generally, we use FILTER function to achieve the requirement.
    WITH SET [CustomAccounts] AS
    FILTER ([Account].[Accounts].[Account Level 01].Members , [Account].[Accounts].CurrentMember.Name<>'Net Income')
    SELECT {[Measures].[Internet Sales Amount]} ON 0
    [CustomAccounts] ON 1
    FROM [Adventure Works]
    WITH SET [CustomAccounts] AS
    FILTER ([Account].[Accounts].[Account Level 01].Members , [Account].[Accounts].CurrentMember.Name='Net Income')
    SET [RemainingAccount] AS
    [Account].[Accounts].[Account Level 01]- [CustomAccounts]
    SELECT {[Measures].[Reseller Sales Amount]} ON 0
    [RemainingAccount] ON 1
    FROM [Adventure Works]
    Results.
    References.
    http://www.databasejournal.com/features/mssql/article.php/3306101/MDX-Essentials-Basic-Set-Functions-The-Filter-Function.htm
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/c0149678-97f2-4066-903f-7f9e9ff09b56/filtering-out-dimension-members-with-mdx?forum=sqlanalysisservices
    Regards,
    Charlie Liao
    If you have any feedback on our support,
    please click here.
    Charlie Liao
    TechNet Community Support

Maybe you are looking for