Moving Shared Members, Possible?

I know I can use load rule to "Allow Move" in order to make parent/child changes to the hierarchy. However, is there a way to use load rule to do the same for an alternate hierarchy (i.e. a hierarchy with shared members). I want to be able to move shared members around the alt hierarchy but could find a way of doing it.
Is this not possible?

the only automated way I know of to do it is to delete the dimension members and re-add them. I lie of course, you could write a routine using the API to do it. Of course you know you can do it manually in EAS, but that too can be a lot of work

Similar Messages

  • Moving shared members in EIS

    I have two alternate hierachies in the customer dimensions with shared members on STORE at Level 0. And I need to perform incremental outline update and data load on the nightly basis using EIS. What happened is if a store is moved to a different parent, EIS can only added the store into the new parent, without deleting the older one, i.e. EIS can't move shared member to new parents. Thus causes us a wrong calculation. Does anyone have a technique or tips to move members on shared alternate hierarchy in EIS?Thanks.Sam

    You have the option of "Deleting the Members First" when you run a Member Load.Only the outline is affected, the data itself remains unaffected until you run a calc. Then it will roll up properly.Good Luck,Tim

  • Moving Shared Members

    Hi Guys.
    Is there anyway to move shared members with load rules?
    I mean like this...
    M1
    shared member1
    shared member2
    shared member3
    M2
    shared member4
    shared member5
    I want to move "shared member3" to M2, for example.
    Thanks in advanced

    it does not quite work like that.
    create a text file with the same format as a file that is used to build the dimension.
    For example, Say the dimension is product and you are using a level build. Assume the first column is the level zero member of product.
    Create a file with one member called "delete_Me" (or any non-member of the data base).
    Set the dimension settings to remove unspecified members. When you run this rule with this test data file, it will delete ALL of the members of product and add the member "Delete_me" as a child of Product.
    Then run your regular build(s), which builds both the primary and shared member roll-ups and it will re-add all the members and if you use the same load rule, will delete the member called "Delete_Me".
    This can all be coupled in one Import dimension statement so data does not get lost.

  • Moving of Shared members

    Hi,
    I have to move shared members within a dimension in outline from one hierarchy to other, using a dimension build rule. I am doing this through flat file, using Parent-Child relationship, and unchecked the option of "Do Not Share" and "Allow Moves". But This is not working out, as my stored members are getting moved first.
    Its like I want to cut an existing Shared member from one hierarchy in a dimension and paste to another hierarchy in same dimension.
    Also the entire dimension is statically built and we can't re-create the entire dimension with dimension rule file and add the shared member where needed and then using "Remove Unspecified" option delete the shared member which is not required.
    Is there any other settings or is there any possibility of achieving this without building the entire dimension through rule file as I have lots of generations and children involved in it.
    Experts, please help me out.!!!

    Well, you sure don't want to add them manually. :)
    How about a source table for this dimension in parent/child format?
    You can have the "master" a & b in the first rollup to a parent, and then the shared reference as many times as you want.
    Of course don't sum the parents or you will count the values of a and b multiple times and get a really screwy number.
    For an excellent review of how to do this through a dimension load rule, see our old friend the DBAG.
    Regards,
    Cameron Lackpour

  • How to see Shared Members in Smart View on Ad-hoc Analysis mode

    Hi All,
    We are using Hyperion Planning v 11.1.1.3.
    For the alternate hierarchy we have created shared members. But in Smart View we are unable to see Shared members hierarchy in Ad-hoc analysis mode.
    Is this limitation in Hyperion Planning?
    Or
    Is there any way to see shared members Hierarchy in Smart View in Ad-hoc analysis mode?
    It is urgent requirement Please let me know as early as possible
    Thanks in Advance!!!

    When you say open data form in Ad-hoc mode, can you do that? I think when you select Ad-hoc mode, you are basically connecting to Essbase and therefore need to manually select the members. (of course, I've got a 11.1.2 env right now so not too sure of 11.1.1.3)
    I'm able to just go to Member Selection and select whatever hierarchy i want, Shared or Stored, when I'm connected to Essbase. When connecting to Planning, I dont have any option of opening the form as Ad-hoc mode.
    Can you see the hierarchy if selecting the members using Essbase connection and not planning?
    Cheers,
    Abhishek

  • Shared Members

    Is there any way in which you can use a filter to look at just Shared Members and not the original members?we have looked at this and believe that it is not possible on the basis that whenever you drill down in Excel, you can see the values for the shared members and the original members as well.It would be great to confirm that the above is True, or even better, provide a solution to the problem.

    When you drill down from a parent member, you should be viewing the child members and if that is shared memebers then that is what you will see.The data value of the shared member and the origianl member is always the same. The roll ups will have differnet values. So I am not sure what you mean when you say the shared value and the origianl value are visible. Please clarify.Thanks.

  • Shared Members Alias

    Hello,
    I am facing problems while creating / removing aliases of shared members in Essbase outline.
    1) What is the best possible way to create aliases for shared members (already present in the outline not new ones) ?
    2) What is the best possible way to remove aliases for exisitng shared members in the outline ?
    Any leads greatly appreciated.
    Thanks,
    Neetesh

    Hi.
    The Easiest Way of Doing it is by Parent-Child References..
    COnstruct a Data File using Parent child Reference and then Add a Third Column in which you provide Alias name.
    In the Field Property of Third Column make is as Alias and tag it to proper dimension and in Dimension build Setting go to Dimension Build tab and check "Allow property changes".
    In case of Removing Alias just create Another Column in Rule File And Leave it Blank
    Then in its Field Propety Check "Delete When Field is Empty".

  • ODI - Delete Shared Members?

    Hello,
    I load a node in a Planning dimension with Shared Members using an ODI Interface. We have a need to remove all of these Shared Members before we perform the load. Is it then possible to remove all Shared Members from specific locations using ODI? I know that we can run the Delete Shared Members utility from the server where Planning is installed, but that is not possible for admin users who do not have admin rights to the server. Version 11.1.1.2, ODI version 10.1.3.
    Thanks in advance,
    Steve

    John,
    Thanks for the reply. The dimension is in a Planning Application/database. I have a parent/child/Alias txt file that I used to load the dimension node with. Are you saying that it is possible to create an ODI interface that can "Delete Level 0" members? Below is a sample of the dimension via planning/dimensions. In this example, I would want to remove all members under the "COGS" node....or all "Shared Members". Below is also a sample of the file used to load the Shared Members.
    Thanks again,
    Steve
    DEPT_SEC All Departments Depts Store View 4
         COGS Cost of Sales Depts Store 4
              D00400(Shared) Management Buffer - COGS (D00400) Shared 4
              D10013(Shared) ELE Las Vegas - COGS (D10013) Shared 4
              D10020(Shared) IT Infrastructure Eng COGS-SJC (D10020) Shared 4
              D10030(Shared) CCV Call Ctr-Customer Service (D10030) Shared 4
    Parent     Child     Description     Status
    Entities     DEPT_SEC     All Departments     
    DEPT_SEC     COGS     Cost of Sales     
    DEPT_SEC     G&A     G&A     
    DEPT_SEC     NO_DEPTID     No DeptID     
    DEPT_SEC     R&D     R&D     
    DEPT_SEC     S&M     S&M     
    COGS     00400     Management Buffer - COGS     A
    COGS     10013     ELE Las Vegas - COGS     A

  • Building alt hier w/ shared members

    Hi all,I have a question about building alternate hierarchies with shared members.Here's my situation:* I have a location dimension containing all stores, their districts, regions, etc. This is the primary hierarchy and the stores (level 0) are not shared members.* I have several alternate hierarchies under the location dimension containing store groupings. These store groupings contain stores as shared members.What I'd like to know is can I build and update the alternate hierarchies using load rules? And does this require that I rebuild the primary dimension each time I update the alternate hierarchies? The alternate hierarchies (store groupings) change on a frequent basis. Hence, I'm looking for an automated solution using load rules.Thank you in advance.

    Since alternate heirarchies are shared, if you try to just rebuild them, it will only add members to the existing heirarchies and possibly duplicate members in them. You will need to rebuild the primary heirarchy to get the alternate heirarchies to build properly. The way I do it is1.create a dummy file with one member in it. 2, Build a load rule that removes unspecified3. do a dimension build of this file followed by your normal build of primary and alternate dimensions as one build request, either through esscamd within a beginincbuild endincbuild routine or through maxl as ONE import dimension statement

  • Shared members' properties not flowing automatically

    Hi,
    We are developing hierarchies in Drm11.1.2.2
    Wherein we have primary members and also shared members in our hierarchy to be built on ...for the properties part let's say for ex I have description-lob as a local property that inherits a global property description-input ...note:values at global properties not to be changed...hence lob ...when the members are created as primary members with their respective properties... The shared members do not inherit the properties from the primary member... How do we get inherit it automatically... Note: description-lob is a overridden property... Please help me asap with your ideas...
    Thanks

    Hello Scorp,
    I've tried to understand and here's what i understood.. The Description-LOB is a defined Inheriting or probably a Overridable derived property.  Now taking each case differently -
    Note- The Shared members will not "Inherit" the values from their primaries unless they are among its descendants and which typically doesn't make sense from an alternate structure view.
    If it is a defined property it will not reflect on the Shared member automatically, if my memory serves me right the Leaf property is the only one which is common.
    Now having said that, the only possibility is that of a overridable derived property, now for that you need to put in a condition in your formula to check for Shared members separately, Check for the Core.SharedFlag_MDM  which is True for Shared members and False for Primaries you can do something like this.
    If(PropValue(Core.SharedFlag_MDM),
    NodePropValue(PropValue(Core.PrimaryName_MDM),Custom.YourProperty),
    PropValue(Custom.YourProperty))
    Let me know if I have deviated from your question.
    Thanks
    Denzz

  • Financial Reporting Studio - Suppress Shared Members During Entity Prompt

    I am trying to create a Financial Reporting Studio report where the entity members that are displayed as a prompt only reflect the entities the user has access to with only one occurrence in the list. I have tried the following scenarios with no luck.
    In Workspace, the Financial Reporting Preference, the Setup User POV option "Member Selection Displays" is set to "Only Members I Can Access" and not "All Members Regardless of Access".
    The Financial Report is set up so that the user is prompted for the Entity so they can select multiple entities to run the report.
    This works fine, except this is also displaying the shared members in the alternate hierarchies when responding to the Entity prompt.
    As part of Defining the prompt, I have included the main entity structure in the "Choices List" in hopes that the shared members wouldn't display as an option to select, but this ends up displaying all of the entities in the hierarchy overriding what is the Financial Reporting Preference (acts like "All Members Regardless of Access"). I have also tried the Union of "Suppress shared members" and "Same level as" a level zero entity, but I'm still seeing all of the members of the main entity hierarchy, rather than a list of entities the user has access to.
    Is there a way to display all of the entities only once that a user has access to during a prompt for a report? I would greatly appreciate any advice. Thanks in advance!!

    I don't think there's a native way to do this in HFR. How could it be done other than through creating a custom selection list? Okay, I guess that is one way but it hurts my brain to think about maintaining it unless it could maybe be done through IDESCENDANTS of 1 and 2.
    Here are two other thoughts:
    1) Write a report against the Planning (I could be wrong about you using Planning as you specify Essbase, but the question is in the Planning board) tables to get this information. I don't know how to do it, but I'm guessing with some SQL gyrations it should be possible.
    2) Stick an attribute against hierarchies 1 & 2 and report on them that way. You the designer already know that they are related. More maintenance on the front end, but a surefire way to get the member list out.
    Regards,
    Cameron Lackpour

  • ASO - Time Functionality - MDX for Shared Members

    Hi
    I have create an ASO cube with two time hierarchies and I am currently trying to get the WTD To Date Functionality working.
    The hierarchies are as follows
    Hier1: Year->HalfYear->Quarter->Month->Week->Date (Date is stored)
    Hier2: Year->HalfYear->Quarter->Month->Date (Date is shared)
    In Hierarchy 1 the month of Jun contains the following days 27/05 - 30/06 due to the way the weeks fall.
    In Hierarchy 2 the month of Jun contains the following days 01/06 - 30/06 as this shows the actual days in the month of June.
    My problem is, in hierarchy 2, the shared members are taking on the WTD to values of the hierarchy 1 and my MDX is not recalculating for shared members.
    Is it possible to recalculate for shared members?
    Hierarchy1
    Hier1 Value - WTD
    Hierarchy 2
    Hier2 Value - WTD
    Jun-Wk1-27/05/13
    100
    May-27/05/13
    100
    Jun-Wk1-28/05/13
    200
    May-28/05/13
    200
    Jun-Wk1-29/05/13
    300
    May-29/05/13
    300
    Jun-Wk1-30/05/13
    400
    May-30/05/13
    400
    Jun-Wk1-31/05/13
    500
    May-31/05/13
    500
    Jun-Wk1-01/06/13
    600
    Jun-01/06/13
    600 (This should reset back to 100 but instead it is taking on the value from Hierarchy 1 because it is shared)
    Jun-Wk1-02/06/13
    700
    Jun-02/06/13
    700 (This should be the sum of 01/06 +02/06 but instead it is taking the value of Hierarchy 1)
    Below is a sample of the MDX I have
    WHEN IsLeaf([Calendar].[ReportingYear].CurrentMember) AND Count ( Intersect (Descendants([ReportingYear]) ,{ [Calendar].[ReportingYear].CurrentMember  })) > 0
    THEN
    sum((ANCESTOR( [Calendar].[ReportingYear].CurrentMember,1).Firstchild: [Calendar].[ReportingYear].CurrentMember), [View].[Periodic])
    WHEN IsLeaf([Calendar].[CalendarYear].CurrentMember) AND Count ( Intersect (Descendants([CalendarYear]) ,{ [Calendar].[CalendarYear].CurrentMember  })) > 0
    THEN
    /*1*/
    sum((ANCESTOR([Calendar]. [CalendarYear].CurrentMember,1).Firstchild:[Calendar]. [CalendarYear].CurrentMember))
    Thanks
    Michelle

    If you use the IsUda function within an IIF statement then you would have to specify a true part and a false part.IIF (Search condition,true part,false part)

  • Load Bulk shared members in EPMA

    Hi,
    We need to develop the process to be able to load members in bulk, thus manual addition will not help. I specifically want to (1) load exisitng dimension members where the parent has changed, and ensure these members are MOVED and not duplicated as shared, and (2) load shared members.
    Any guidance in this regard will be helpful.s ma

    Hi John
    I can't map the IsPrimary to any property in EPMA?
    I added the column in my flat file, but in my import profile I can't map it, so in the load it is giving 'The 'IsPrimary' column is not present in the import source for dimension 'Entity'. Creating all imported members as primary instances.'
    Is the property only applicable to the Account dimension? I'm trying to load the shared members in Entity dimension.
    Cheers,
    Omar

  • Move Shared Members

    Do you know of a setting to allow restructuring of the shared members?
    When setting the rules files, I have selected ALLOW MOVES which restructures the main hierarchy... but I am unsure how to restructure the shared members. I have tried a lot of combinations and so far my only two choices have been to not allow shared members to moved or to add a second shared member and manually remove the original shared member.
    Any suggestions?

    VK, is that you? Or just an incredible coincidence?
    Assuming it's not:
    1) Create two views of your dimension: with shares and without shares and their parents
    2) Create two dim load rules: One with removed unspecified and allow moves checked, one with remove unspecified and allow moves unchecked
    Load the dimension using the without shares and remove unspecified/allow moves option checked. This should remove all of the shared hierarchy (okay, I am assuming a pretty share hierarchy below the master hierarchy -- it would get more difficult if they were shared within a hierarchy that didn't get deleted).
    Load the dimension using the with shares data and the remove unspecified/allow moves options unselected. This should add back the alternate hierarchy parents and their shared members.
    It's ugly no matter how you do it, but the above shouldn't be too painful.
    Regards,
    Cameron Lackpour

  • Delete shared members (lots of them)

    Hi!
    We have a account hierarchy with lots of members. At the end of the account dimension we have a lot of shared members, which are located as direct children of Account dimension. In Planning web we can delete those member by member, but it is a time consuming exercise.
    Is it possible (and safe) to delete those at this point unnecessary shared membes in Essbase admin console? We would then load a new P&L hierarchy (using shared members) into Planning using HAL (our version is 9.3.1. and we are using classic administration)
    Kind regards

    It is best to remove via HAL or some tool that allows communication with the SQL repository. Best to try to keep essbase and planning in sync........hope this helps.

Maybe you are looking for