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

Similar Messages

In my planning application.I have 100 members in account dimensions.Those members are used in 100 forms.suddenly my bussiness was changed.so i want replace those 100 members into new name of 100 memebers.but how i can chnage in 100 forms.how to handle

In my planning application.I have 100 members in account dimensions.Those members are used in 100 forms.suddenly my business was changed.so i want replace those 100 members into new name of 100 members.but how i can change those 100 members in 100 forms.how to handle this?

Hi joshi and jharvey,
Thanks for you are reply.I am new for this lcm.Can you explain detail.about above problem.I mean in share service i didn't find any export option.I had seen only migration.or share any blog for detail about lcm.

Loading Essbase Members for [ Accounts ] Dimension in ODI 11.1.1.3 ?

Hi
My source is Oracle Database tables and Target is Essbase Members of Dimension ('Accounts') i m trying to load Data to Accounts member (Employee Rate) When i perform Reverse Engineering I am only able to view Dimensions not is members. So in my interface i am not able to perform mapping cause Members are not showing up.
Problem Example:
1- Essbase Dimensions and Members
Accounts <--------------- Dimension
| Employee Rate <---------- Members
| Headcount
| Over Time Rate1
| Employee Salary
Currency <--------------- Dimension
Entity <--------------- Dimension
Period <--------------- Dimension
2- IN ODi After Reverse Engineering when i drag and drop to Target i only see Dimension Properties NOT members
Example: Parent, Two Pass Calculation
but my goal is to insert data into Memember (Employee Rate) of Accounts Dimension
So i am not able to see Members of Accounts Dimesion so i cant perform mapping with my source table.
Looing for your help.
Regards

Hi John,
Yes you are right, that was issue.
Now How i am going to get sub Members: what should be format.
Accounts Dimension ----> Dimension
|
Employee Rate -----> Member
|
Over Time1 ------> Sub Member of "Employee Rate"
|
Shift Rate ---->Sub member of "Over Time1"
I am having above hierarchy than what should be Format that i have to put in:
DATA_COLUMN_DIMENSION = ??
DATA_COLUMN_MEMBERS = ????
Thank u john, you are always helping.
Regards
Sher
Edited by: Sher Ullah Baig on Jul 5, 2012 12:27 PM

Error when addding members in account dimension

Hi all,
I am working on consolidation.for currency translation and inte-company elimination in consolidation i want use business rules.can some body tell me which business rules can i use and what are the business rules exist total.is writing a script is easy or using business rules easy for consolidation.can some body tell me how to write sample script logic.
does any docs or books are present in detail for script logic in total..
waiting for your answer....
Regards,
Naresh.K

Start with reading the documentation at:
http://help.sap.com
SAP Business User > EPM Solutions > Business Planning and Consolidation
Consult withe the BusinessObjects Knowledge Center at:
http://help.sap.com/content/bobj/bobj/index.htm
Also check with the BPC install guides at:
http://service.sap.com/instguidescpm-bpc
Finally, read the How-to-Guides at:
https://wiki.sdn.sap.com/wiki/display/BPX/EnterprisePerformanceManagement%28EPM%29How-to+Guides
Best regards,
[Jeffrey Holdeman|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/profile/jeffrey+holdeman]
SAP BusinessObjects
Enterprise Performance Management
Regional Implementation Group

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.

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

Duplicate members in EPMA dimension library

Hi,
There are two instances of many members in Account dimension in EPMA dimension library in UAT environment. I am trying to migrate the Account dimension to Dev using LCM. When i do the LCM import, all the second instances are getting imported as shared members and the import fails as the children are orphaned. However there are no errors in UAT when i validate the application. The hierarchies of two instances are associated to different planning applications.
The error is
The 'Member' section contains a duplicate entry; the subsequent input line 'NB AWP|Revenue||||||None|Currency||False|False|False|False|N|False|||False|False|N|Default|0|0|Default|None||Plan2|1|Balance|False|Numeric|||||False|NonExpense|False||' will not be processed.
Is there a way to import the dimension as it is in the UAT environment?
Regards,
Ragav.

As you are talking about a planning application then duplicate members are not supported but Shared members are.
Cheers
John
http://john-goodwin.blogspot.com/

Time series / account dimension

Hi,
Kindly let me know what additional benefits we get if we declare a dimension as time series or accounts .
Is it in time series we can consolidate first and last, none
and in accounts - we can give 2 pass calc ,
I am not sure whether to make a dimension year in the outline as time dimension or simply leave it as normal dimension .
Any help will be appreciated.
Regards,
Sushmita

Hi,
Sandeep is right here.But this will give more straight forward idea.
The time dimension enables several accounts dimension functions, such as first and last time balances. These tags, called "time balance tags" or "properties".These tags provide instructions to Analytic Services "how to calculate the data in a dimension tagged as accounts".
To use the tags, you must have a dimension tagged as accounts and a dimension tagged as time. The first, last, average, and expense tags are available exclusively for use with accounts dimension members.
You can also use Two Pass calculation on members of account dimension if member contains formula.
Thanks & Regards,
Ram.

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/

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.

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

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

When one or more family members who have been sharing one iTunes account wants to create their own iTunes account can they each upload the music/apps from the shared iTunes on their devices to the new iTunes account?

When one or more family members who have been sharing one iTunes account wants to create their own iTunes account can they each upload the music/apps from the shared iTunes on their devices to the new iTunes account?

Yes. I would clarify your statement about the "shared" iTunes Library though. If you want each iOS device to have its own music library, you should create separate user accounts for them. Read:
iTunes: How to share music between different accounts on a single computer
How to use multiple iPods, iPads, or iPhones with one computer

Account Dimension not showing all members in the cube in Analysis Services

Hi,
         In SAP - BPC 5.1 after processing account dimension all the members are created under account dimension in analysis services but the same cannot be found in the data cube. Hence the reports generated through SAP - BPC is not showing all the members.
         The issue looks very strange as we can see the members getting created but the same is not getting populated in the cubes. I am not able to visualize what exacly the issue is? Is it with the application or with the analysis services?
Thanks
Sharath

Your sixth sense is correct, there is definitely support in MSAS and BPC 5.1 for multiple hierarchies in the account dimension.
I'm also referring to parentH1 and parentH2, but perhaps we're still speaking of different things.
In the past, I faced a very similar problem as you, and the root cause was because I had one member, let's call it FancyParent, which, in H1, had children Child1 and Child2.
But in H2 it had children Child1, Child2 and Child3. I forget now if that was how I wanted the setup to be, or if it was a mistake on my part, but either way, MSAS doesn't allow this. The admin consol didn't complain when processing the dimension -- this was in Outlooksoft 5.0; perhaps validation has improved now.
But the cube was completely unworkable. Certain things were calculating correctly, but everything in the account dimension in the area around FancyParent (above and below it, in both hierarchies) was quite unpredictable.
By disabling first one, and then the other, of the two hierarchies, and disabling blocks of accounts, I was eventually able to pinpoint the problem. But it took days to figure out what was the problem. (The account dimension had 2500 members and 4 hierarchies, and it was not a pretty sight.)
A parent must have the same definition of children in all hierarchies. It can't, as another example, have children in H1, and be a base member in H2. Each member can have different parents in the two hierarchies, but must always have the same children in both.
To work around this problem, I had to create two separate accounts NetIncomeH1 and NetIncomeH2 (and PretaxIncomeH1, PretaxIncomH2, etc. all the way down to the point where they branched off), to get the two separate aggregations of the P&L in the two hierarchies. Once I did that, it made sense to me why, but I also swore off on frivolous extra hierarchies ever again.

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.

Shared members in Accounts dimension

Similar Messages

Maybe you are looking for