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.

Similar Messages

  • 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

  • Deleting Shared members in DRM

    We are in DRM 11.1.2.1.1.0.1.
    We create some members as shared
    One of this members it is deleted.
    We create the same member below another parent, but now the shared member instead of have shared!1, it is defined as shared!2. But shared!1 was deleted before.
    Do you know the way to delete this shared member and if it is created again it should have the value shared!1
    thanks

    Hi,
    Looking at your post, I believe you actually removed the shared member. When you do a remove on "Shared!1" only that gets removed and it will be moved into the "Orphan Nodes" under the current version. Please check the Orphans list and delete "Shared!1" permanently from DRM. Now try to add it back, you should be able to add "Shared!1" now. The numbering will restart since you cleared the Orphans. Let me know if this works. As you might know, delete and remove are 2 different things.
    Thanks.

  • Shared Members Alias Names Need to be Deleted--Essabase Admin Console

    The company I work for set up shared members with alias names. I need to get rid of the alias names so that they are linked to their proper stored members and take on those names. How do I do this without haveing to go to every contton-picking shared member and delete the alias name?
    Thanks!

    981103 wrote:
    The company I work for set up shared members what do you mean by "shared members"?
    with alias names. what do you mean by 'alias names' and what do said 'alias names' refer to?
    I need to get rid of the alias names so that they are linked to their proper stored members and take on those names. How do I do this without haveing to go to every contton-picking shared member and delete the alias name?
    Thanks!And since you mention in the subject line 'essbase admin console', what does any of this have to do with oracle databases?

  • ODI and deleting shared accounts members in Planning

    Hey there,
    We have 1 account alternative hierarchy, which we remove all the level 0 tagged as shared member from the account dimension.
    The problem is to do it is taking ages, meanwhile to load back these members is doing in minutes , deleting is taking an hour.
    Do you know if there is any problem when ODI remove Shared members from Planning?
    Do you know what is doing in the background Oracle (we have Oracle as database)?
    Thanks,

    It is taking the same time.
    Also I tried with the command DeleteSharedMember because I want to delete only shared members, and it takes ages.
    The point is in the schema the shared members are only in one table, so I don't know why it is taking age to remove it, it has not to do any checking if it is in forms or another places.
    And is it possible to create a sql script to remove it directly in the schema and restart planning afterwards?.
    Thanks

  • HT5622 I have two iPhones synced with the same Apple ID and so the contacts are being shared in both of them. Is there any way to revert this?? The reason is that if I delete some contact from one device then it automatically erases from the second one as

    I have two iPhones synced with the same Apple ID and so the contacts are being shared in both of them. Is there any way to revert this?? The reason is that if I delete some contact from one device then it automatically erases from the second one as well

    Yes, you stop using the same Apple ID under Settings > iCloud.

  • 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

  • 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

  • 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

  • HOW can i delete the members in dim using MAXL

    Hi All,
    I want to delete the all the memebers for dimensions before reloading so how ca n i write the maxl script for this to delete the members in the dimensions
    plz can any one help on this its very urjent ,
    It would be appriciated ...
    Thanks

    There is no way to alter an outline with MaxL, MaxL is an admin language for processing. The only option, as Glenn mentioned is to issue the reset all command to blow away everything. But you probably don't want to do that, so instead you use Maxl to run a series of load rules to achieve your goal.
    Load rules do not have functionality to delete outline members, it does have a feature however that allows you to remove unspecified members from a dimension build, so when loading in your members, if existing members are not in the import, they are removed. So Glenn's point was to create a source file with a single dummy member. When you load using "Remove Unspecified" it will delete all the members and just keep the one dummy member. Then when you go back a second time and actually load the real members, the dummy member will be removed and you will have a clean dim with only your new members. This is a work around solution, but it's what a lot of people do.
    Now if you have 15 dimensions you need to do this with, you might want to take a slightly different approach. I'm assuming 15 dimensions is probably an ASO cube and this method will be preferable to avoid outline fragmentation.
    Create a copy of your outline with all the base dimensions that do not change intact. For the ones that do change, just have your dim root member. Consider this your starting outline template and save a copy of it. When you want to rebuild your cube have a server process that takes the copy of your template outline and copies it over your existing outline file in the directory structure. Then run your load rules to import your new members.

  • Shared members and dynamic calc

    I am trying to replicate a new cube from current GL cube and wish to remove unused shared members if they have any impact on essbase.
    2/3 of my accounts (dense) member is stored with the remainder being shared members. Shared members do not add to block size. But having so many of them, does it impact on calc scripts or retrievals or any other impacts?
    Secondly, in accounts and divisions, we have four levels. except for level 0, the remaining levels are all dynamic calc. Division is sparse member. Its not advisable to have dynamic calc on dense dimension. What about sparse dimension like division? Will it be better to change level 2&3 to dynamic and change level 1 to store as well?
    We have also been advised by our consultant to change accounts to sparse dimension considering the number of times we need to update outline for new members (stored and shared).
    Dimension          Type          Stored     Shared
    Measure               Dense     1378     796     rest
    Time               Dense     106     13     rest
    Year               Dense     9     8     
    Currency          Sparse     12     9     
    Scenario          Sparse     41     38     
    Market               Sparse     20     12     
    Division          Sparse     490     302     rest
    Product               Sparse     635     308     
    Reportcode          Sparse     327     299

    Hi,
    Having shared members in dense hierarchy will not have much of impact on Cube size or retrieval performance.
    but its always advisable to avoid unnecessary hierarchies (shared or stored or dynamic).
    Having top level dense members as dynamic lines is a good design but having sparse dynamic calc will impact retrieval performance.
    its not at all advisable to make sparse members as dynamic calc but if needed we can make sparse members with very few children as dynamic calc (or dynamic calc & store). yet again its not advisable to have a dynamic calc children to a sparse stored parent as this will affect the batch calculation while aggregating parent sparse member.
    And as suggested by your consultant it is feasible to make the dimension getting modified more often, as a sparse dimension as this will reduce the restructuring time (sparse restructure will take less time compared to dens restructure).
    But that alone cannot be considered as factor as there are many other factors to be considered for making a dimension sparse.
    - Krish

  • Drill down on shared members.

    Hi ,
    I have some filters associated to geography hierarchy in my essbase cube.
    my geography heirarchy looks like this.
    geography
    |_base_members
    |_am
    |_Apac
    |_shared_members
    |_am (Alias: America) (shared members)
    |_ ..etc
    |_Apac (Alias: Asia pac) (shared members)
    now i have created filters giving meta read access on shared members in the above case on .users of america will only see america region.
    but when i drill down and drill up on the member in the report in web analysis, it gives me an unknown member error "am".
    i tried by giving same access to the base members but the report shows the base members.
    is there any other way to handle this error.
    thanks.

    Try deleting Non-Corporate Income before you drill into Total Revenue. Or turn off Retain selected member in your drill options. The problem is that if Essbase sees Non-Corporate Income, then it knows it is the alternate roll up and correctly does not drill on Total Revenue. Remove Non-Corporate Income and Total Revenue, just becomes plain old Total Revenue and you should be able to drill on that.

  • Shared Members in Load Rules

    Hello,I am trying to build a dimension build load rule.How do you create shared members within a dimension? Does it have to be through a parent-child load rule? What if you have a subset of a dimension, (eg duplicate hierarchy) with more then two levels, ie parent child? How do you create shared memebers then?Any help would be greatly appreciated.Thanks.

    I'm a newbie in dim build using load rule too. I'd a bunch of products that had to be in 2 roll-up structures, apparently as shared members in one of them. It took little effort to build the first roll-up using a generation build method. Just when I thought it was gonna be a slam dunk, I couldn't create the second roll-up. I kept trying different load options but it just wouldn't work. I noticed the "Do Not Share" check box was always disabled. So I clicked on the different build method buttons. I noticed that the box become enable when I selected the parent/child method. I tried and it turned out to work fine. So, for the little knowledge I have, it seems you must use the parent/child rule to create shared members.

  • 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".

  • Shared Members on interface changes of Entity or account hierarchy

    Hello,
    Is there any scripted way to remove 'Shared Members' from the Account and Entity hierarchy, or if not, is there any means of finding them on mass, as we have set up a database interface to maintain account and entities, but the problem is after accounts or entity change parent they leave a 'Shared Member' on the original parent, which is not desired functionality as it throws totals out on forms / reports.
    thanks for your input, no blogs please as our security prohibits me seeing them.
    Robert.

    Thanks John, can I ask you a follow on also...
    If a member had never share as its property and you used the hierarchy interface to assign it to a new would would it; -
    a. Prevent update of its parent hierarchy via the interface
    b. Move it to whatever new parent you deemed and remove it from its original
    thanks for your input,
    Robert.

Maybe you are looking for