Aliases on Shared Members not in Essbase

<p>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?</p>

<p>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.</p>

Similar Messages

Aliases for shared members in Smartview

Hi All Gurus,
I am using Oracle EPM 11.1.2.3. I migrated an EPMA planning application from 11.1.2.2 to 11.1.2.3. The Alias for Shared members are not getting displayed When I access through Smartview ,instead it is showing as [Parent].[child] . But When I access the same application in 11.1.2.2, I can see the Alias.
How to fix this?

It is been identified as a bug have a read of this Oracle - Hyperion Labs......: Smart View issues with alternate Hierarchy - Surprises in Essbase Part V
Regards
Celvin
http://www.orahyplabs.com

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/

Access on Shared Members not working in reports

In our entity dimensions, we have all of our base members listed in under a parent folder, with permission assigned to each base member to allow access (not at the folder level).
We then have another parent folder which includes Regions, and then the base members are included under the appropriate region as a shared members. On the Region folders, we have iDescendants access setup for all the shared members.
When running reports, if a user who has access to the Region folders selects the Region folder, then they can see a consolidated report for all the shared members, but if they click on a specific shared member, they cannot see any numbers.
It looks like those shared members are not inheriting permissions from the parent folder. This was working before, and recently stopped.
Does anyone know what needs to be done to get the permission to start inheriting from the parent folder to the shared members?

Did a Refresh on Shared Members from Planning > Administration > Manage Database and this solved this issue.

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

Multiple hierarchies with shared members

Hello,
is it just a common practice to have unique parents for hierarchies built on the same Essbase dimension, or it is a system level restriction?
Only in Hyperion Planning, or this is true also on Essbase level?
Is it right that only the leaf nodes can be shared members?
(automatic shared members are created on higher levels for parents with 1 child, so why other shared members not allowed?)
Thank you for your answer!

I'm not sure I follow your question completely, but for shared member rollups the lowest level of the shared rollup can be a level zero or higher member or another dimension. The requirement is that a shared member can not have descendants in the shared rollup, it would be the lowest level.
For example If I have the following primary rollup
Geography
East
NJ
NY
PA
West
Ca
OR
WA
I could have an alternamte rollup like
Bob's Total
NY (Shared)
West (Shared)
You see thar NY is a level zero member and West is a level 1 member but under the alternate rollup the are both level zero members

Aliases of Members not getting retrieved

Hello all
     I want to retrieve members from an Essbase Database/outline of my application with their Aliases(want to retrieve only Aliases), I've used Smart View API for VBA to achieve the same, but somehow Aliases are not getting retrieved instead member names are getting retrieved, also I want to achieve this by replacing the below Essbase add-in function
     aryMarket = EssVGetMemberInfo(Null, "Member_Name", 1, True)
     I've used following Smart View function to replace above mentioned function
     aryMarket = HypQueryMembers(Empty, "Member_Name", HYP_SEARCH, HYP_ALIASESONLY, Null, "", "", vt)
can some one provide me the correct combinations of the parameters that I should be providing?

The HYP_ALIASESONLY setting in HypQueryMembers means that you are trying to search on the alias, not trying to retrieve the alias (that call can bring back more than one member matching the search term). You probably (I didn't check for certain) have to use HypGetMemberInformation instead.

How to load shared members in Essbase

Can anyone tell me how to load Shared Members in Essbase using ODI
-app

Did you not already ask the question :- Essbase Error log issue for Shared Members
You never answered my question to your original post.
Cheers
John
http://john-goodwin.blogspot.com/

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.

Handling HFM Shared Members in Essbase Analytics Link (EAL)

We have an entity dimension in HFM with Shared Members in an alternate hierarchy. The shared members happen to be parents and when the metadata is synchronized in EAL, only the shared parent is brought into the alternate hierarchy in our EAL cube. We'd like to find a way to bring all of the descendents of the shared parent into our cube but Essbase does not allow it. Is there a way to prefix the shared members during synchronization so the EAL cube contains the same structure as HFM while accommodating the need for unique member names in Essbase?

I've seen this kind of behaviour in EAL when using both 11.1.1.3 versions. Could you let me know what are your EPM and EAL versions?
May be your EAL will require a patch.
Cheers.

DRM and Shared Members in Essbase & Planning

Hi,
Many years ago we implemented Razza and one of the difficulties we had was in handling shared members in Essbase and Planning applications. The workaround as I recall was to use a prefix in alternate hierarchies, and strip it out before exporting. But this did not allow for a single place to maintain a node. Is there a best practice for handling shared members in DRM?
Thanks!

DRM now supports shared members in the application. This application functionality used configurable suffixes. You can read about this in the DRM User Guide.
This makes Essbase integration virtually seemless since Essbase will treat the first occurance of a member encountered during the dimension load process as the base member and any subsequent occurances of that member as shared members. Planning, however, requires shared members to be marked as such and thus depending on how the hierarchies are maintained in DRM and then exported, it is possible for the shared member to appear before the base member, which will cause Planning to raise an error. This can be accommodated with two pass loads and other techniques.
Also note that this information could be dated as I haven't personally been on a project that fed hyperion Planning for a couple of years. Regards.

Shared members' properties not flowing automatically

Hi,
We are developing hierarchies in Drm11.1.2.2
Wherein we have primary members and also shared members in our hierarchy to be built on ...for the properties part let's say for ex I have description-lob as a local property that inherits a global property description-input ...note:values at global properties not to be changed...hence lob ...when the members are created as primary members with their respective properties... The shared members do not inherit the properties from the primary member... How do we get inherit it automatically... Note: description-lob is a overridden property... Please help me asap with your ideas...
Thanks

Hello Scorp,
I've tried to understand and here's what i understood.. The Description-LOB is a defined Inheriting or probably a Overridable derived property. Now taking each case differently -
Note- The Shared members will not "Inherit" the values from their primaries unless they are among its descendants and which typically doesn't make sense from an alternate structure view.
If it is a defined property it will not reflect on the Shared member automatically, if my memory serves me right the Leaf property is the only one which is common.
Now having said that, the only possibility is that of a overridable derived property, now for that you need to put in a condition in your formula to check for Shared members separately, Check for the Core.SharedFlag_MDM which is True for Shared members and False for Primaries you can do something like this.
If(PropValue(Core.SharedFlag_MDM),
NodePropValue(PropValue(Core.PrimaryName_MDM),Custom.YourProperty),
PropValue(Custom.YourProperty))
Let me know if I have deviated from your question.
Thanks
Denzz

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

Currency members not displayed on Essbase

Environment:* EPMA version 11.1.2.1
As part of multicurrency, we have added the two members EUR and USD in *‘Currency’* dimension to perform currency conversion and then re-deploy application. Deployment has done successful without any error. But members not displayed in Essbase as expected.
We have setup default application currency and reporting currency as GBP.
Currency Dimension hierarchy in EPMA (Before Deployment)_
Local
GBP
EUR
USD
Currency and HSP_RATES hierarchy in Essbase (After Deployment)
Currency Dimension*
Local
GBP
Actual Problem:_ Missing EUR and USD member in Essbase
HSP_Rates
HSP_InputValue
HSP_InputCurrency
HSP_Rate_GBP
HSP_Rate_EUR
HSP_Rate_USD
Now you can see EUR and USD member not dislayed as expected in Essbase. Can anyone help in guiding or resolving the issue?
Thanks in Advance

1.     Yes. Outline created, we have used the option Refresh and Full Deploy
2.     Not having access to server. But if you particular log file then let me know the name. I will try to arrange the log file.
3.     I have added two new member RUB and CAD. But problem remain same, these member not displayed under currency dimension. But it will displayed successfully under HSP_Rates with names ‘HSP_Rate_RUB’ and HSP_Rate_CAD’. It means functionality working fine, but not displaying member. If it won’t display then I can’t create currency conversion script.
4.     Successfully deployed, no error messages

How to see Shared Members in Smart View on Ad-hoc Analysis mode

Hi All,
We are using Hyperion Planning v 11.1.1.3.
For the alternate hierarchy we have created shared members. But in Smart View we are unable to see Shared members hierarchy in Ad-hoc analysis mode.
Is this limitation in Hyperion Planning?
Or
Is there any way to see shared members Hierarchy in Smart View in Ad-hoc analysis mode?
It is urgent requirement Please let me know as early as possible
Thanks in Advance!!!

When you say open data form in Ad-hoc mode, can you do that? I think when you select Ad-hoc mode, you are basically connecting to Essbase and therefore need to manually select the members. (of course, I've got a 11.1.2 env right now so not too sure of 11.1.1.3)
I'm able to just go to Member Selection and select whatever hierarchy i want, Shared or Stored, when I'm connected to Essbase. When connecting to Planning, I dont have any option of opening the form as Ad-hoc mode.
Can you see the hierarchy if selecting the members using Essbase connection and not planning?
Cheers,
Abhishek

Aliases on Shared Members not in Essbase

Similar Messages

Maybe you are looking for