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

Similar Messages

Building shared members using rules file

How to build Shared members in the outline using load rule file.
I tried but it is not working correctly.

Hi,
If you are loading the build file in parent child format...you don't need to mention the member as shared or stored.
Essbase automatically makes the second one shared.
If you are using generations or levels format to build the dimension then I suggest you to refer the docs to understand it clearly.
http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/esb_dbag.pdf
Thanks,
Jeeth

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

Building alt hier w/ shared members

Hi all,I have a question about building alternate hierarchies with shared members.Here's my situation:* I have a location dimension containing all stores, their districts, regions, etc. This is the primary hierarchy and the stores (level 0) are not shared members.* I have several alternate hierarchies under the location dimension containing store groupings. These store groupings contain stores as shared members.What I'd like to know is can I build and update the alternate hierarchies using load rules? And does this require that I rebuild the primary dimension each time I update the alternate hierarchies? The alternate hierarchies (store groupings) change on a frequent basis. Hence, I'm looking for an automated solution using load rules.Thank you in advance.

Since alternate heirarchies are shared, if you try to just rebuild them, it will only add members to the existing heirarchies and possibly duplicate members in them. You will need to rebuild the primary heirarchy to get the alternate heirarchies to build properly. The way I do it is1.create a dummy file with one member in it. 2, Build a load rule that removes unspecified3. do a dimension build of this file followed by your normal build of primary and alternate dimensions as one build request, either through esscamd within a beginincbuild endincbuild routine or through maxl as ONE import dimension statement

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/

Smartview: shared members on level o has a prefix of level 1

Hi,
I'm using smartview 11.1.2.3. I have a dimension with multiple parallel hierarchies: level1a->level0, level1b->level0, level1c->level0,
as a result the level 0 members which apears below level1b and level1c are shared members. when I'm "zooming in" in"smartview" from
level1b/level1c, the shared members apears as level1a.level0 or level1b.level0. (zooming in from level1a gives a correct result ->level0),
did someone encounter this issue?
thanks,
Yuval

Yuval check this Oracle - Hyperion Labs......: Smart View issues with alternate Hierarchy - Surprises in Essbase Part V
Seems like something changed (maybe from a patch in 11.1.2.2, not sure about the patch because I've a vanilla 11.1.2.2 with this issue) from 11.1.2.2
Regards
Celvin
http://www.orahyplabs.com

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.

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.

Determiniung Shared Members

To all, I need to determine if a member is shared or not and when I call EsbOtlGetMemberInfo it always returns 0.Is this a bug?-Peter sts = EsbOtlGetMemberInfo(hOutline, hMemberProfit, MbrInfo) ' sts = EsbGetMemberInfo(hCtx, MbrName, MbrInfo) End If Debug.Print MbrInfo.usShare-Peter

Found this reply on Network 54 from 7 years ago. I can concur that Parent/Child will work as that is the method that I always use.
Depends on the build type...No score for this post July 26 2004, 9:56 PM
This is true of parent/child builds - not level or generation builds. If you add members more than once in a level or generation build, you get "Incorrect Parent" errors. If you check the "allow moves" box, you will not get shared members - duplicate members to where their last occurence in the data file specifies.
The only way to create shared rollups with level or generation builds are the awkward "duplicate level" or "duplicate generation" column types. Personally, I have never used them - I prefer to use parent/child builds to do the shared rollups.
Regards,
Jade
Jade Cole
Senior BI Consultant
Clarity Systems
[email protected]
www.claritysystems.com

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

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

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

Level building/shared members

Similar Messages

Maybe you are looking for