Formulas & Shared Member

My formula is a % of total. (What % does the child represent to the immediate parent?) Formula tested: Member%@parentval(dimension,Member)If the numerator is a shared member, it automatically pulls the parent of the stored member. Basically the level 0 data is being consolidated in two different ways. I need a % of total formula that will divide by the immediate parent versus the stored parent. @parentval and @sparentval will not work. My problems would be solved if there was a function called @ISShared. Any thoughts?

I'm not sure what you mean by the "immediate parent" - but I assume it means the parent of the shared member vs the parent of the Real member. If this is the case, then the following:@SPARENTVAL() % @PARENTVAL()should work. According to the documentation, the @SPARENTVAL function looks to the parent of the shared member rather than to the parent of the real member.However, you asked about an ISSHARED function - there isn't one, but I assume what you need this for is to calculate the ratio differently IF there is a shared member. Is this the case?Regards,Jade---------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Similar Messages

How to determine if shared member is descendant

I have an account dimension that has several different alternate hierarchies. All of the leaf level accounts are in the Base Accounts hierarchy; these leaf members are then shared in the other hierarchies. What I would like to do is build a calculated measure that performs a particular formula if the current member is a descendant of a specific member, say X. I have tried to use IsAncestor and also the Count(Intersect(Descendants())) formula, but it apparently doesn't consider the shared members at the bottom as a descendant of X. I have also tried adding a UDA to the members in question and using the IsUDA function, but again, I can't use UDAs on the shared members. Note this is an ASO cube being built in EIS. Is there a way to determine whether a shared member is a descendant of a particular member in a hierarchy? Thanks, Matt

In general, shared members need careful handling in MDX. A couple of mechanical observations and a question. Yup, there's a paradox at hand. The query SELECT Filter ( Descendants ( [Diet] ), IsAncestor ( [Product].CurrentMember, [Diet] ) ) on axis (0) FROM [Sample.Basic] returns an empty set, while the following formula only returns 1 for those shared versions that are in fact under the share, so the [100-20] under [Colas] does not get a 1. Count ( Intersect ( { [Accounts].CurrentMember }, Descendants ( [[[Account Parent 1]]], [Accounts].Levels(0) ), ALL ) ) Somehow, IsAncestor() returns FALSE even for members obtained as descendants of the Ancestor, while intersecting that member with the set of Descendants returns identity. But it's a different member somehow, since Intersect ( { [Accounts].Levels(0) }, Descendants ( [[[Account Parent 1]]], [Accounts].Levels(0) ), ALL ) only returns 1 instance of each member, not 2. Intersect(x,y, ALL) should return duplicates found in x when they exist. It seems like you can use Count(Intersect(Descendants())) for all "shared" versions of the member, but not the first, "non-shared" use of the member. Meanwhile, it would be great to avoid the set construction/counting overhead. OK, enough of mechanics. What I'd like to inquire about is what you're trying to do. Are you trying to factor out logic into the shared parents, and then combine it based on what set of ancestors a member has? That would be clever, but maybe there's another approach. If you are trying to have different formulas for different shares, keep in mind that since a shared member is a shared instance of a member, it should have the same formula to calculate itself regardless of the parent it is under (since it is under all parents equally and simultaneously. A little more insight into your goals could give us a path to a solution.

Shared Member Error

I need to tag a member as a shared member. When I tag it as shared member, the duplicate shared member dialog box pops up.
But there is only one base member listed.
I double click on the base member, the member gets tagged as a shared member. However after saving and reopening the outline, the member is no longer tagged as shared.
What could be the error.

Hi user,
Make sure you meet the following requeriments while creating share members:
- Shared members and the associated stored member must be in the same dimension
- In the outline, stored members should be above their associated shared members.
- Stored members can be at any level in the hierarchy
- Shared members must be level 0, even if their stored member is not.
- You cannot assign UDAs or formulas to shared members.
- You cannot associate attributes with shared members.
Please let me know.
J.-

Can't add Shared Member using API

I would like to create a lot of shared members.Using API I do it as following according to documentation: ESS_MBRINFO_T MbrInfo; memset(&MbrInfo, '\0', sizeof(MbrInfo)); strcpy(MbrInfo.szMember, (char*)mbrName); MbrInfo.usShare = ESS_SHARE_SHARE; sts = EssOtlAddMember(getOutline(), &MbrInfo, ESS_NULL, hMbr, &hNewMember); When I try to add shared member, then sts = 1060051.So I have to change names and after correct them manually.Using HAB API I can't add shared member too.Regards,Georgy

Hi and Welcome to the Forums!
To really help, you should come and create an account on these forums...there are many unanswered questions from your initial inquiry...come here, create an account, and open a thread so that it all can be resolved:
http://supportforums.blackberry.com/rim/
Cheers!
Occam's Razor nearly always applies when troubleshooting technology issues!
If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
Join our BBM Channels
BSCF General Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Issue with User Variable Due Shared Member Security Access

Hi All,
One of my client is using User variable in data form to define POV.
Now if user has access to 2 member in the Dimension, he should able to see 2 member when he try to assign the value to this "user variable"
but he can see some of the parent member name ,this parent name has only one child which is a shared member of the 2 base member for which he has access.
For Example:
Entity Dimension:
E1 (user has access)
E2
E3(user has access)
E4
Alt_Entity
Alt_Entity1E1 (sharedmember)
Alt_Entity2E2 (sharedmember)
Alt_Entity3E3 (sharedmember)
Alt_Entity4E4 (sharedmember)
User is able to see below members, when he try to assign value
E1 (user has access)
E3(user has access)
Alt_Entity1
Alt_Entity3
Now if I add another member under this parent, than user are unable to see this parent member.
For Example:
Entity Dimension:
E1 (user has access)
E2
E3(user has access)
E4
Alt_Entity
Alt_Entity1
E1 (sharedmember)
E2 (sharedmember)
Alt_Entity2E2 (sharedmember)
Alt_Entity3
E3 (sharedmember)
E2 (sharedmember)
Alt_Entity4E4 (sharedmember)
User is able to see below members, when he try to assign value
E1 (user has access)
E3(user has access)
Any idea?

Sorry, but actually its the parent that needs tagging with "Never Share", not the level 0 member, so Alt_Entity1 and Alt_Entity2 etc, see Essbase DBA guide
understanding Implied
Sharing
The shared member property defines a shared data relationship explicitly. Some
members are shared even if you do not explicitly set them as shared. These
members are said to be implied shared members.
If you do not want a member to be shared implicitly, mark the parent as Never Share so
that the data is duplicated, and is not shared. See Understanding Shared Members for an
explanation of how shared members work.
So in the example above
Entity Dimension:
E1 (user has access)
E2
E3(user has access)
E4
Alt_Entity
Alt_Entity1 - Set to "Never Share"E1 (sharedmember)
Alt_Entity2E2 (sharedmember)
Alt_Entity3 - Set to "Never Share"E3 (sharedmember)
Alt_Entity4E4 (sharedmember
Thanks
Anthony

Still need a password to update apps purchased by another Family Sharing member!

On iOS 8.1, I can enter App Store app, tap on the Purchased tab at the bottom, and then tap the upper-left corner to choose one of the members in the same Family Sharing members, then tap on the "download cloud" icon next to any apps purchased by that member. Doing so, I don't need to enter the password that Family Sharing member's Apple ID. But, whenever apps, those purchased by other Family Sharing members, have an update, I would need to change the Apple ID to that Family Sharing member and enter the password, in order to enable the app update. Or, those apps will stay on the Updates page of the App Store app, waiting to be updated, forever.
How can the app update of apps purchased by other Family Sharing members be set automatic?

No. To update apps you have to sign intot he account that purchased them.
I have multiple Apple IDs. Is there a way for me to merge them into a single Apple ID?
Apple IDs cannot be merged. You should use your preferred Apple ID from now on, but you can still access your purchased items such as music, movies, or software using your other Apple IDs.
Just purchase the apps with your account

EIS 9.3.1 shared member error

Installed EIS 9.3.1 using SQL 2005. Everythign works fine with the exception of one dimension. My Period dimension (months) has one part built with a SQL view, which is used in the drill through reports, and the rest, which is not drillable, is build directly in the Metaoutline.
Any member shared within the "manually" built members give me the following error:
A shared member (member name) must be at the leaf level and cannot appear before its primary member.
Now for the funny part. This exact architecture and outline builds in EIS 7.1.6 with no errors.
Oracle Support suggested that I use a sort order to insure that it is built in the correct order. I do this in all my views in SQL itself, but these are not in the SQL view.
Any thoughts woudl be helpful.
THANKS!!!!!!

Hi,
I experienced (& luckily got it resolved) this error earlier!
From your query, I understand, you were ensuring sorting would be done based on your key/functional columns.
However, what Oracle seems to be suggesting you is: "Use an additional *column* (say, Sort_Order) to let the sort order ensure that- Base member always comes before Shared member". You may control the Sort_Order column using something like CASE statements...
Correct me if you intend to ask something else!
Greetings,
- Natesh

Giving filter to a Allias member only ,not to shared member with the same name

I have a situation that i have to give access to allias member ,with the same name there r a lot of shared member.
Please let me know ,if there is any syntex where i can give access to the member which is tagged as allias .

Access to member ?? Please be clear on it !!
Assuming that you are using Maxl scripts to create filter
create or replace filter 'App'.'db'.'Group Name ' read on '@IDESC("Dimensions") , @IDESC( ) ....';
Later use :
grant filter 'App'.'db'.'Group Name' TO 'Group Name in Shared services';
May be you can create a new Group for the shared members , or it really does not matter .
I am assuming that I got your question correct.

Can i use a Dynamic Calc member as a Shared member

Can i use a Dynamic Calc member as a Shared member in other hierarchy?
is it mandatory to make a member as Stored type if we want to use the same member in other hierarchy as a shared member.?
-KK

Yes we can create a shared member of a Dynamic Calc member.

"Zoom out" on shared member defaults to different hierarchy??

Hi Guys,
I've created a shared member Cost Centre hierarchy in my outline. When I "zoom in" to the shared member hierarchy to level 0, then try zoom back out, level 1 is no longer the shared members level 1 as I've defined in my new shared member hierarchy.
Instead, level 1 (from zooming out of the level 0 shared member) defaults to the rollup associated with the member that the shared member points to?? Is there a way to make the zoom out of a shared member from level 0, zoom to the level 1 in the shared members hierarchy and not the associated member that the shared member point to?
I really hope that makes sense to you guru's :-)
Thanks
Dermott.

user1113036 wrote:
That's the way Essbase has worked from time immemorial. Annoying, isn't it?You think it's annoying in the UI? It is really annoying in the API.. A standard way to walk a tree structure is the 'preorder walk algorithm' which essentially walks down the children of the tree, the next sibling(s), then back to the parent, etc until eventually the original root node is encountered signaling that all nodes have been visited. With the behavior of Essbase described in this thread, a preorder walk actually goes into an endless loop when the 'parent' is the 'real' parent of a member and not the shared member 'parent'.
Tim Tow
Applied OLAP, Inc
Edited by: timtow on Aug 24, 2008 5:37 PM

Consolidation Property on Shared Member

Can you set the consolidation property to a shared member different than its stored member? If I edit the outline I seem to have no problem setting a "-" on a shared member where its "+" on the stored member. When I try to do this via a load rule I am unable to do this.

Yes, this is possible. It sounds like your issue has to do with trying to do the build in one load rule.
If you want the same "member" to have different aggregation properties, it is all about location, location, location. You need to add your properties at the same time you are building the hierarchy so it knows that the property in the file belongs to the member under a given parent.
My usual methodology is to...
1) build the primary hierarchy in one build, with the properties for the stored lev0 in that load rule.
2) Secondary build for the shared rollups. Set the properties for the shared member in this load rule.
If you just mention a lev0 member in a build and say it is a has a "+" property, Essbase won't know which one you are referring to, but it definitely won't result in the two members with different properties.
Good Luck!!
Kevin

Shared Member

Hi people,
I'd like to get some information about sharing members, for example, sharing a base- entity.
When you define the properties of an entity, you define a parent too. So, my question is: can the shared member aggregate to both parents? Or it will only aggregate to the parent defined in the properties?
Please, advice!
Thank you!
Lu

When you define an entity you can assign a Default parent, this entiy however can be shared under a different parent in an alternative rollup, and if you are using default consolidation it will agregate to both parents.

Shared member dimension build

I am trying to create a load rule that creates a shared member at a different generation. I looked at the dbag and it mentioned using the Parent/Child method with "Do Not Share" unchecked. But during testing, it moves the member instead of creating a shared member. Am I leaving something out? thanks

You cannot move shared members with a load rule. It will always end up moving the original member. What we had to do was to load a file with DummyParent DummyChild to delete all the members in the dimension (remove unspecified checked), and then rebuild the dimension with a new file where the shared member appears under its new parent.BKhanna

Shared member equivalent to EssVGetMemberInfo?

in excel - is there a way to do=EssGetMemberInfo([sheet];"value";8;TRUE/FALSE;[cell]) for shared members as well?i need the parent of a bottom level shared member but until now i have no clue how. there is no problem with the members, but i just couldn't find anything (macros, VBA functions, whatsoever) that works for shared members as well.any idea?marco

user1113036 wrote:
That's the way Essbase has worked from time immemorial. Annoying, isn't it?You think it's annoying in the UI? It is really annoying in the API.. A standard way to walk a tree structure is the 'preorder walk algorithm' which essentially walks down the children of the tree, the next sibling(s), then back to the parent, etc until eventually the original root node is encountered signaling that all nodes have been visited. With the behavior of Essbase described in this thread, a preorder walk actually goes into an endless loop when the 'parent' is the 'real' parent of a member and not the shared member 'parent'.
Tim Tow
Applied OLAP, Inc
Edited by: timtow on Aug 24, 2008 5:37 PM

EPMA - Changing a 'Shared' member to 'Primary'

Hi,
We need to modify a dimension. We have a alternate rollup where all the members are 'Shared'. However that rollup in the desired dimension becomes the 'primary' dimension and the current primary dimension needs to be removed. If we just change the current shared members to 'primary' and delete the new 'shared' members, the data is lost on restructure. We also have removed all ALIASES too.
When we goto deploy we get an error that the member was rejected and Shared Member LOC_1138 can not be added or updated.
Is it possible to change/modify the primary and shared within same dimension and deploy and not lose data?

To receive the discount you the account has to be in the employee's name and SSN. You can call 611 or visit a corporate store and ask for an Assumption Of Liabilty. The current account owner and the potential new account owner should be together. Keep in mind that there will be a credit check for the new account owner and you may have to change to one of the new More Everything plans.

Formulas & Shared Member

Similar Messages

Maybe you are looking for