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

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, 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

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.

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

How to build shared members using Rules file

hi all,
we have a source file like below,in that Bold members are shared member. we doknow how to modify the source file for building shared members using Rules file.
Conf Total,~,Config A,*Lightbolt 365 A*
Conf Total,~,Config A,*Lightbolt 540 A*
Conf Total,~,Config A,*Lightbolt 730 A*
Conf Total,~,Config A,*Thunderball 365 A*
Conf Total,~,Config A,*Thunderball 270 A*
Conf Total,~,Config A,*Roadranger 123 A*
Can anyone give suggestion to resolve this issue.
Thanks in Advance

hi John,
Here i'm building the dimension through generation build method.
setting the properties as
Field, Dimension, Field Type, Field Number
Field1,Product,Generation,2
Field2,Product,property,2
Field3,Product,Generation,3
Field4,Product,Generation,4
After mapping it shows dimensions are correctly mapped.
When i load the source file and the rule file, it shows error partially loaded data,.And it doesn't shows the shared member property. That is what asked How to modify the source file for building shared members using Rules file.
Thanks,
Edited by: user@99 on 25-May-2010 15:37

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

Level building/shared members

Can you generate shared members when level building your dimensions?

I'm afraid I have to disagree with the previous 2 posters. You can build shared members when you use a level build method. I do it all the time. Assume your level zero member is in a primary and secondary rollup and that there are 3 parents in the firs rollup and 2 in the second, the format of the load rule would be:
Lev0,Lev1,Lev2,Lev3,lev1,Lev2

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

Is there any API for Shared Members

Hi All ,
Can any one let me know whether there is any API function for Shared Members? I could not find anything from http://download.oracle.com/docs/cd/E12032_01/doc/epm.921/html_api/api_c/mac/tocmacfa.htm
Please do help...Thanks in advance

I am assuming you are on 9.2 as that is the link you posted, all the details you need are in the docs - http://download.oracle.com/docs/cd/E12032_01/doc/epm.921/html_api/topapilist.htm
Cheers
John
http://john-goodwin.blogspot.com/

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.

Building RULES file to load shared members in Aggregate storgage outline

Hi there
I posted this yesterday (sorry, somewhat different subject description). I am trying to create an alternate hierarchy containing shared members using a load rule and flat file in an Aggregate Storage outline. One response was to remove the "allow moves" option and use parent child build in the load rule. I tried that and it did not work. i was pointed to a section in the essbase guide (which is about as clear as mud), and still cannot get this to work. First of all - can you do this with an ASO outline? If so, how? I tried a simple 6 line flat file and recreated the load rule based on the above recommendations and it will not the shared members. Can someone out there help?
thanks

Here is an example in the simplest form.
Create Aso db (duplicate members names not selected)
Create Product dimension member, set to "Multiple Hieararchies Enabled", (though probably would work if dynamic)
Create load rule, set as parent/child dimension build for product, make sure allow moves is not ticked.
Data file
Parent,Child
100,100-20
200,200-20
Diet,100-20
Assign field properties in rule for Parent.Child
Load data, 100-20 will be created as shared.
Cheers
John
http://john-goodwin.blogspot.com/

Multiple hierarchies with shared members

Hello,
is it just a common practice to have unique parents for hierarchies built on the same Essbase dimension, or it is a system level restriction?
Only in Hyperion Planning, or this is true also on Essbase level?
Is it right that only the leaf nodes can be shared members?
(automatic shared members are created on higher levels for parents with 1 child, so why other shared members not allowed?)
Thank you for your answer!

I'm not sure I follow your question completely, but for shared member rollups the lowest level of the shared rollup can be a level zero or higher member or another dimension. The requirement is that a shared member can not have descendants in the shared rollup, it would be the lowest level.
For example If I have the following primary rollup
Geography
East
NJ
NY
PA
West
Ca
OR
WA
I could have an alternamte rollup like
Bob's Total
NY (Shared)
West (Shared)
You see thar NY is a level zero member and West is a level 1 member but under the alternate rollup the are both level zero members

EPMA Shared Members not reflecting in Planning application post deployment

Hi,
I have added a member in 'Entity' dimnesion. The same member is also added in an alternate hiererchy as shared member (Using Insert member option in dimension library). When I refresh the application view, I do see both the original member and shared member in application vieiw. But post deployment, only the base member is reflected in planning application and not the shared member.
I have redeployed the application multiple times now, but i am still not able to see the shared members reflected in Planning application.
Kindly let me know if you have any idea on the same or faced a similar issue?
Regards
Meenal

Hi,
Have you patched up EPMA with patches from Metalink3
9.3.1.1 Patch includes -
6897835 SHARED MEMBERS IN ENTITY DIMENSION CAN NOT BE DEPLOYED TO ASO/BSO APPS
It is advisable to keep a look out for patch fixes with EPMA
Hope this helps
John
http://john-goodwin.blogspot.com/

Moving of Shared members

Similar Messages

Maybe you are looking for