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

Similar Messages

Shared Members in Duplicate Members Hierarchy

It seems that many people have asked this question on this forum but I am yet to find a solution. Most of the posts were about 5 years old so I am hoping maybe something new has happened since.
I have a dimension that has a regular and alternate hierarchy (shared members). I have changed this dimension to duplicate members enabled. Once I have this turned on, my regular dimension build rule no longer creates shared members but instead creates a new member of the same name. I cannot find any property that I can put in the dimension load rule to specifically tag members as shared. The only way that I can change it is in EAS one by one. Is there any fix that allows me to load shared members through a load rule with duplicate members enabled?

You may have seen my posts on this on Network54 from 2007 or so while you were searching. I could never find a way to do this, and there is no property to tag members as "Shared" to the best of my knowledge. I tried it again quite recently (in 11.1.2.3.500) and got the same result.

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

Duplicate Member Outline and Loading Shared Members

I have an outline where I want to allow duplicate member names but in some cases I will need shared members. I am trying to build the outline parent child and I cannot get it to understand the fact that I want a shared member.
Here is an example:
[market],east
[market],west
[market],other
[market].[east], nj
[market].[east], ny
[market].[west], ca
[market].[west], lv
[market].[other],[market].[west].[lv] <--- this should be shared
[market].[other],ny <--- this should not be shared
Does anyone know how to do this?

If you would like to less the charecters and if you are retrieving the data using SQL, then you could using the Substr function to restrict the characters to 80 substr( string, start_position, [ length ] )

How to load shared members into a duplicate outline using load rules

Hello, I am trying to load an alternate hierarchy into the same dimension in an outline that accepts duplicate members using EAS load rules ... there is no property for shared members so i can't specify it in the load rule .. i tried using parent child and it is not working - no shared members are loaded in the alternate hierarchy .. any ideas? would another utility make it happen?
thx

You might find this useful: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm
Especially the Building Shared Members by Using a Rules File section: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm#dotdimb1061244
Cheers,
Mehmet

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.

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/

EPMA interface load for shared members

Hi,
Iam trying to load metadata to EPMA shared library through interface tables. was able to load everything except the shared members. I checked with IsPrimary value and set it to N/0 values also kept datastorage type to shareData. But still not getting updated. Import result gives the follwoing warning.
"The import section 'Hierarchies' contains multiple primary instances of member '698035' in dimension 'Account_Shared'. Only the first instance will be processed"
Please help me out.
thanks,

am still not able to sort out the above problem. can some one please help me to load shared members to EPMA shared library ?
thanks,

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

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.

Duplicate member name

Hi Everyone,
My database currently set to Allow duplicate names None. Now I want to enable it. (Its a planning application 9.3.1).
What are the impacts in doing so. Does duplicate members Store data?? Or are they like Shared members????
Can I create another hierarchy under a duplicate member??? Any inputs would be appreaciated.
Regards,
Anil

Agree with both posts.
Don't do it for the reasons Glenn stated and I agree you wouldn't be able to actually create any duplicates anyway for the other stated reasons.
but don't think that means it will not have an impact. Enabling duplicate members will impact other areas such as your ability to partition (you cannot create a partition between a duplicate enabled and a non duplicate enabled database.
So you will receive no benefits and face potential consequences.

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

Need help in Shared Members

Hi All,
Could you please help me how to assign the Shared members for bottom level members in a dimension using rule files. will Allow moves and Allow property changes will this help us in assign shared members for bottom level members ?
Thanks,
Raj.

Could anybody please help me out in building out shared members in an outline where *"Duplicate Member names allowed"* is set to true ?
As an example, Suppose I've the below hierarchy:
DIM_I
- Parent-I
- Child-I
- Child-II
- Child-III
- Parent-II
- Child-IV
- Child-II (Shared Member)
In the above example, as is obvious, I'd like to share the member Child-II of Parent-I with its clone in Parent-II.. Please note that this outline has some other dimensions wherein duplicate members are required but not as shared ones.
Any help would be greatly appreciated!
Thanks

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

Shared members in duplicate member enabled EPMA outlines

Similar Messages

Maybe you are looking for