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.

Similar Messages

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/

Multiple shared members in ASO outline

 I am building an outline with one primary and three alternate hierarchies within one of the dimensions of an Aggregate Storage (ASO) cube. All of the leaf members in each of the alternate hierarchies are shared members of a member in the primary hierarchy. The non-shared member is a leaf in some cases and a summary point in others. All hierarchies are stored. When I try to save the outline, I get a long list of verification errors. For the stored members to which the shared members refer, Essbase is complaining that "This member has multiple copies of same shared member in at least one stored hierarchy. See other messages for which members and which hierarchies." For the shared members, Essbase complains that "Aggregate storage outlines only allow a shared member once in a stored hierarchy." For the alternate hierarchies, Essbase complains that "This stored hierarchy has multiple copies of same shared member. Remove extra member or change hierarchy to be dynamic." However, I did a find on a handful of the members that Essbase was complaining about and in all cases have found only one instance of each shared member in each alternate hierarchy. The same shared member might appear in two or more alternate hierarchies, but I have not found a case where it appears more than once in the same hierarchy. I have also ensure the following: <UL>The primary hierarchy occurs first in the outline, so non-shared members always appear before any instances of any of the shared members.</UL> <UL>There are no shared members in the primary hierarchy.</UL> <UL>All members, non-shared and shared, are in the same dimension.</UL> <UL>Non of the stored hierarchies contain both a non-shared instance and a shared instance of the same member.</UL> I have tried making the alternate hierarchies dynamic, but query retrievals are so slow that they're completely unacceptable to the client. Has anyone encountered a similar problem? Is there a solution to this? 

I heard back from Hyperion Tech Support again. Turns out it's not a defect after all. It's actually a subtle technicality in the restrictions on shared members with ASO. The first restriction, which is explained in the outline verification error message, is that you can only have one instance of a shared member within a given stored alternate hierarchy. The second restriction is that you cannot have any shared members within a given stored alternate hierarchy where the non-shared instances of the members are ancestors/descendants of each other. Unfortunately, when this restriction is violated, EAS gives the same error message as it does for the first restriction, so it's a bit harder to debug. Hope this saves someone some grief. -Silvester

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.

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?

Shared Members

Similar Messages

Maybe you are looking for