Move Shared Members

Do you know of a setting to allow restructuring of the shared members?
When setting the rules files, I have selected ALLOW MOVES which restructures the main hierarchy... but I am unsure how to restructure the shared members. I have tried a lot of combinations and so far my only two choices have been to not allow shared members to moved or to add a second shared member and manually remove the original shared member.
Any suggestions?

VK, is that you? Or just an incredible coincidence?
Assuming it's not:
1) Create two views of your dimension: with shares and without shares and their parents
2) Create two dim load rules: One with removed unspecified and allow moves checked, one with remove unspecified and allow moves unchecked
Load the dimension using the without shares and remove unspecified/allow moves option checked. This should remove all of the shared hierarchy (okay, I am assuming a pretty share hierarchy below the master hierarchy -- it would get more difficult if they were shared within a hierarchy that didn't get deleted).
Load the dimension using the with shares data and the remove unspecified/allow moves options unselected. This should add back the alternate hierarchy parents and their shared members.
It's ugly no matter how you do it, but the above shouldn't be too painful.
Regards,
Cameron Lackpour

Similar Messages

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

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.

(ESSBASE) How to move shared member into hyerachy

Hi, i've this question: How can I move a shared member into the Essbase Outline hyerarchy when I load metadata?
I've tried using the "Allow Move" option into "Dimension Builiding" session of the rule, but the system gives me an error...

I have a dimension called "clienti" structured in this way:
Clienti
- GER1
-XXXXX 1
-A
-XXXXXX 2
-GER2
- YYYY1
- YYYY2
- A (shared)
-GER3
- ZZZZZ1
- ZZZZZ2
- A (shared)
Now, using a rule that reads form SQL source, I wanto to transofrm my hyerarchy in this way (the member "A" changes his parent in all hyerarchies [Ger1, 2 and 3]):
Clienti
- GER1
-XXXXX 1
-XXXXXX 2
-A
-GER2
- YYYY1
- A (shared)
- YYYY2
-GER3
- ZZZZZ1
- A (shared)
- ZZZZZ2
The way I follow it's:
1) load ONLY GER1 members filtering by SQL statement (Select * form "TABLE" where "FILED_NAME" ="GER1") with "ALLOW MOVE" option checked into rule properties -> IT'S OK, the member "A" changes its partent correctly
2) load GER2 in the same way, but the system gives me this error: Dimension build failed. Error code[1060053]. Check the server log and the dimension duild log for more information. Unexpected essbase error1007083
The log dont give me any info and the dimension build log is not created
The same when I try to load GER3 and if I try to load ALL (Ger1 + 2 +3)
My doubt is that is not possible to move shared members..
Thaks!!

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/

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.

Moving shared members in EIS

I have two alternate hierachies in the customer dimensions with shared members on STORE at Level 0. And I need to perform incremental outline update and data load on the nightly basis using EIS. What happened is if a store is moved to a different parent, EIS can only added the store into the new parent, without deleting the older one, i.e. EIS can't move shared member to new parents. Thus causes us a wrong calculation. Does anyone have a technique or tips to move members on shared alternate hierarchy in EIS?Thanks.Sam

You have the option of "Deleting the Members First" when you run a Member Load.Only the outline is affected, the data itself remains unaffected until you run a calc. Then it will roll up properly.Good Luck,Tim

Shared Members in Custom can have different aggregation weight?

Hi guys,
I have created a Flow dimension to track the cash flow movements. Under TotalFlows, I have the different movements (OpBalance, CloBalance, Variation, Gain, Loss), all with aggregation weight of 1. But I have to create an additional structure (sibling of TotalFlows), called TotalFlows2, with shared members (OpBalance, CloBalance...) but with aggregation weight of zero.
Can I used the Shared Member with different aggregation weight? Or should I rename them (for ex., TF2_OpBalance)?
Please, advise.
Thanks!
Jai

Absolutely use the shared member and set the aggregation weight to zero in your duplicate structure, this is the key benefit to custom dimensions.

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

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

How do you find the movies shared on a mac?

I know how to find the movies shared from one of my family members on the app but I don't know how to find them on a MacBook Pro.
I don't need to find 'My Purchass' but I need to find my family-members purchases.
Please help.

There is no Windows side on a Mac unless you install a version of Windows in a virtual machine or use Boot Camp to partition the drive and install Win 7 (if you are using a Macbook Pro that came with OS X Lion installed).
If you use a virtual machine you can install just about any version of Windows that you have a retail disc of and a legal license key to go with it.

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.

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

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

Move Shared Members

Similar Messages

Maybe you are looking for