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

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

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

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/

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

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

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

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.

Essbase Error log issue for Shared Members

I am loading Shared members for a custom dimension in Essbase.
Error log is getting created as below.
\\Record #1 - Warning: Account Only attributes cannot be set in non-Accounts dimensions
PR0011,APP_PR,Shared Member,
But that specific member is getting loaded.
I am loading only shared member in this load and all records are shown as getting rejected even though most of them are getting loaded.This is causing issues in finding out real rejects.
-app

Hi, check this
http://oraclebizint.wordpress.com/2008/12/14/hyperion-essbase-931-obe-series-designing-essbase-databases-bso-outlines-data-load-global-schema-part-2-building-dimensions/
in the dimension build settings don't set allow moves property and use parent/child references
I have tested it & it works
Regards

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

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.

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

Building alt hier w/ shared members

Similar Messages

Maybe you are looking for