Impact if I add many shared members...

Hi,
I currently have a dim say Mgttax..
There is a requirement now to maintain a new roll up under Mgttax which is going to have all the leaf members which are currently now under Mgttax..
All the current leaf members are stored now...
As they are going to be duplicate they will be as Shared members..
So if I add all these members to a new rollup which has all the lead members as shared members...will theere be any impact on the calc time..i mean will it increase the calc time??
I'll have only two roll ups under the new roll up...
Say original dim is mgttax which has many roll ups and all the leaf members are stored...
I add a new rollup(say NEW) just below the top parent Mgttax under which i have only 2 roll ups(say X and Y)
and all the leaf children which are now will go to any one of the 2 roll ups(either X or Y) under the new roll up(NEW)
By this will there be any major impact???
Thanks in advance..

If the shared members are split evenly between the two parents, thats 1000 members per parent, It's worse if it's uneven. If possible I would suggest adding more levels in your share (If possible) to reduce the number of blocks that have to be read to create a perent. If you can't then try calcfrombottomup (Look for the correct spelling in the function reference and read the disclamer). At any rate 2000 members is not terrible depending on the number of dimension and the number of members in the other dimensions of your cube.

Similar Messages

Shared Members with Integration Server

Hi all,I need to add as shared members some member in an alternative hierarchy, but when I perform an outline update IS adds members as shered again in my alternative hierarchy.I have two ways:first: say to IS to add as shared only new members, but I don't know how;second: remove all members from my alternative hierarchy before perform the outline update, but I need to do that automatically, not manually.Who can help me?thanksciao

--->1)during INTEGRATION SERVER CONFIGURATION thru SXMB_MONI
i got an error message "CORRRESPONDING INTEGRATION SERVER NOT MAINTAINED" on execution of the configuration.
Ans : It seems at the time of creating Business systems and Tech Systems . you missed to assign the business system with XI integration server.
2)When i select ROLE OF BUSINESS SYSTEM AS ->APPLICATION SYSTEM and
RELATED INTEGRATION SERVER -> (While assigning INTEGRATION SERVER)
i got an error :could not update the business system JAVA.LANG.NULLPOINTER EXCEPTIONS.
Ans : XI not installed properly.
3)in SXI_CACHE t.code when i choose menu path ENVIRONMENT -> CACHE NOTIFICATIONS i got an error : UNABLE TO DETERMINE THE NAME OF THE CENTRAL ADAPTER ENGINE FROM THE SLD.
And : Since the type of scenario you are running is using Inernal adapter engine which is with in Integration Server...so this is an obvious error.
4)during PERFORMANCE MONITORING
errors: A)APPLICATION ERRORS: INTEGRATION SERVER UNABLE TO FETCH DATA
B)ERROR CLASS:COM.SAP.AII.RWB.WEB.PERFORMANCEMONITORING.AGGREGATE.....
C) NO COMPONENTS AVAILABLE IN THE INTEGRATION SERVER...
Conclusion : Either your XI is not installed properly or the integration engine of XI is not configured properly. Consult Basis team for this.

Add shared members to interfaces tables

Hi guys
I need to load shared members to a generic dimension using interface tables?
How can I do it?
Regards

Hi John
Thanks for your help. I can add shared member to the generic dimension called PCM_Prod, however I am getting the following issue
at validate one application that I used:
Error : Last generation 2 member of dimension PCM_Prod is Total Productos. Expected member name "NoMember".
Error : Dimension 'PCM_Prod' does not support shared members because the dimension hierarchy type is set to 'Stored'. Member: '3032182'.
Error : Shared member '3032182' cannot exist under generation 2 ancestor member 'Total Productos' in dimension 'PCM_Prod' because it does not belong to a StoreData hierarchy. Either set the dimension-level Hierarchy Type property to 'StoreData', or else set the Hierarchy Type property of generation 2 ancestor of this member to 'StoreData'
If I upload using ADS I did not get the issue.
So I do not why using interface tables I got the error.
Regards

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 Problem

Hi,I want to start using the Shared Members option for one of my applications in EAS 7.1.0, but have amended the outline and loaded data but the Shared members are appearing in my data twice, therefore duplicating my sales figures in excel add-in, which isn't what I want, I just want the part to be added once, so almost as if one part doesn't get calculated. Can anyone help me with this?? Many ThanksSarah

As Sreenivas said, change the consolidation to tilde.However, I would put a word of caution on what/how you do this.Typically, a hierarchy has one "primary" roll-up, where all the members are listed only once, and the hierarchy has an organized rollup. In addition, there may be "alternate" roll-ups. These hierarchies have internal consistencies that roll-up to a given point, but no further.What I mean by this is, that you should consider finding the 'root' location of the shared roll-ups, and mark it as non-aggregating (~), but the shared members themselves should aggregate to provide the alternate hierarchy it's own internal consistency.After working out the reason for the distinction between the main and alternate hierarchies, it becomes fairly obvious that your main roll-up will be 100% of your non-shared members, and the alternates may contain subsets.Example:Product has children "All Products", and "Discount Products", "All Products" will contain them all and aggregate to the Product root member. "Discount Products" contains a subset that aggregate up to itself, but it doesn't aggregate to the Product root member. You may have additional "alternate hierarchies", but only one will be your "full roll-up".Note: This example ignores the use of UDA's or attribute dimensions for doing this same thing, for illustrative purposes.-Doug

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

Shared members in Accounts dimension

Is there a problem with having shared members in the Accounts dimension? I received no errors while saving the outline but I am not sure of the effect this would have on database size, performance, etc. My user wants to view the same measures grouped under two different categories.Thanks for your help.Bela

No, having shared members in the measures dimension (or any other dimension) should not have any impact on database size or performance, except where you have new stored or dynamic calc member rollups of those shared members. It sounds to me like you have taken the correct approach, although I do recommend recording before and after stats (db size, calc times, restructure times, retrieval times) for any and all changes to important Essbase databases, it's often times difficult to predict the impact of changes, after all, Essbase is an art, not a science! HTH, Jeff McAhren Dallas, Texas

Shared members issue

Hi to all,
I've a Problem with the shared members in a excel spreadsheet. I need to see all members in a specific dimension (shared members included). using members selection dialog box, i'm using the view method "by generation name" and the output option Supress shared members (cleared) but the shared members are filtered in the results. Using by level name is the same result.
could you help me?
I'm usign essbase 9.0 and add in vs 9.0
Thanks in advance

Certainly sounds odd... did you check the preview to see if they show up there?
I'm just thinking it might be a post processing issue, because I haven't heard of this being an issue before so if it is there may be some option setting that is tripping it up.
Let us know if they show up in the preview -- and if you have a suitable way to test other outlines or dimensions with similar circumstances it might help to check the preview on them as well.

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

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.

Aliases on Shared Members not in Essbase

I used HAL to create alternate rollups using shared members inmy Accounts dimension and in a custom dimension (Customers). The aliases for the shared members appear in Planning, butafter refreshing Essbase, the aliases are not in Essbase; only themember names. When I add a shared member manually inPlanning, the alias is populated in Essbase. Does anyone havean idea of how to get the aliases in Essbase?

I realize that the alias will display when reporting on it. The reason it came up is because you can't see the alias whenperforming a member selection. It's an inconvenience, not ashow stopper. I just thought it was strange that the aliaswould go into Essbase when the shared member was added manually,but not when added using HAL. Seems like a bug to me.

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

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.

Impact if I add many shared members...

Similar Messages

Maybe you are looking for