Shared Members in ASO

All - I am migrating outlines from 6.5(BSO) to 7.1.2 (ASO).When Imigrate I am unable to migrate shared members from BSO to ASO evenafter assigning the DIMENSION as Multiple Hierarchies Enabled. For Ex: DIM 1 (Multiple Hierarchy Enabled)..... Member 1(Dynamic Hierarchy) Child1 Child2 Child3 Child4 Member 2(Stored Hierarchy) Child3 (Shrared Member) Child4(Shared Member) I get an Error message as ASO does not support Shared Membersbut I have read that if you enable a dimension as MultipleHierarchy Enabled you can assing members of a Stored hierarchy asshared members.Please help with any inputs.Thanks in advance. Jeeva

Had similar problem. Solved it doing these: in BSO outline, temporarily rename your shared members - just so the Conversion wizard can work. Change Dimension to Dynamic Calc. Once converted, change Dimension to Dynamic Hierarchy. Restore shared members to original names.

Similar Messages

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

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)

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/

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/

Shared members in duplicate member enabled EPMA outlines

Hi all,
I have created an EPMA ASO "allow duplicate members application". I want to create an alternate shared hierarchy but all teh shared members are getting deployed in essbase as stored members. Do I need to enable any other property also so that shared members are treated as shared members only and not stored members.
Thanks in advance.

Can anyone please answer this...its very urgent

Enabling Duplicates / Disabling Shared Members in Essbase Studio

I am building an ASO cube using Essbase Studio in EPM 11.1.2. I need to check the *"Ignore duplicate members, do not move*" option in the outline build properties for one of my dimensions. However, the check-box for this is greyed out for some reason. How do I activate this option? Also, is there any other way to disable shared-members? I want my dimension to contain duplicate members and not shared members. But the build rule is currently treating two members with the same name as shared members.

We've figured out how it works. You should set minischema first for txt file.

Load rule to update alternate hierarchy with shared members more than once

I have a aso cube with an alternate hierarchy that is not stored because the shared members appear more than once. Below is how my alternate hierarchy looks.
Dept
Class
VolumeLevel
StoreNum
where StoreNum is the shared member.
I build the cube using eis every weekend. The VolumeGroup changes everyday, so I was thinking of using a sql load rule to update the outline everyday. Assuming that the data and the aggregation does not get cleared. Is it possible to do it using sql load rule?
Thanks,

You can check here if you are satisfying the conditions for creating shared members under the Hierarchy (refer to Alternate Hierarchies). Plz note that rules for shared members are different in ASO world.
http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/frameset.htm?acrtapdb.html
Otherwise there is no reason why you should not be able to create a shared member.
I am able to create a hierarchy using a sample file like this ->
EN_MAIN, EN_500000
EN_500000, EN_49999
EN_ALT, C_500000
C_500000, EN_49999
ENTITY (Multiple Hierarchies Enabled)
|-EN_MAIN (Stored)
|--EN_500000
|---EN_49999
|-EN_ALT (Stored)
|--C_500000
|---EN_49999 (Shared)
The rule file has only "Allow Property Changes" on.
Thanks,
Sunil

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.

Maximum number of members in ASO outline

Hi All,
We are using Essbase 11.1.2.1. We have ASO cube with 11 dimensions, 1 dimension is expected to have more than 30 million members. Is that allowed ? What is the maximum limit for members in ASO cube ?
Also how to improve performance for such cube ?
Kindly advice.

I believe the answer is no. The maximum number of members is 20 million: http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/frameset.htm?limits.html#limits_8
Cheers,
Mehmet

Shared Members in ASO

Similar Messages

Maybe you are looking for