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.

Similar Messages

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/

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.

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.

Reporting on shared members financial reporting studio

We have multiple hierarchies in our entity dimension where the members are shared between hierarchies. Is there a way to create a report that shows the intersections of hierarchies. ie- hierarchy a has products 1, 2, 3,4. hierarchy b has products 1,2,5,6. I need a report that shows the intersection of the two hierarchies- products 1 and 2. this is using essbase in financial reporting studio.

I don't think there's a native way to do this in HFR. How could it be done other than through creating a custom selection list? Okay, I guess that is one way but it hurts my brain to think about maintaining it unless it could maybe be done through IDESCENDANTS of 1 and 2.
Here are two other thoughts:
1) Write a report against the Planning (I could be wrong about you using Planning as you specify Essbase, but the question is in the Planning board) tables to get this information. I don't know how to do it, but I'm guessing with some SQL gyrations it should be possible.
2) Stick an attribute against hierarchies 1 & 2 and report on them that way. You the designer already know that they are related. More maintenance on the front end, but a surefire way to get the member list out.
Regards,
Cameron Lackpour

Multiple shared members in ASO outline

 I am building an outline with one primary and three alternate hierarchies within one of the dimensions of an Aggregate Storage (ASO) cube. All of the leaf members in each of the alternate hierarchies are shared members of a member in the primary hierarchy. The non-shared member is a leaf in some cases and a summary point in others. All hierarchies are stored. When I try to save the outline, I get a long list of verification errors. For the stored members to which the shared members refer, Essbase is complaining that "This member has multiple copies of same shared member in at least one stored hierarchy. See other messages for which members and which hierarchies." For the shared members, Essbase complains that "Aggregate storage outlines only allow a shared member once in a stored hierarchy." For the alternate hierarchies, Essbase complains that "This stored hierarchy has multiple copies of same shared member. Remove extra member or change hierarchy to be dynamic." However, I did a find on a handful of the members that Essbase was complaining about and in all cases have found only one instance of each shared member in each alternate hierarchy. The same shared member might appear in two or more alternate hierarchies, but I have not found a case where it appears more than once in the same hierarchy. I have also ensure the following: <UL>The primary hierarchy occurs first in the outline, so non-shared members always appear before any instances of any of the shared members.</UL> <UL>There are no shared members in the primary hierarchy.</UL> <UL>All members, non-shared and shared, are in the same dimension.</UL> <UL>Non of the stored hierarchies contain both a non-shared instance and a shared instance of the same member.</UL> I have tried making the alternate hierarchies dynamic, but query retrievals are so slow that they're completely unacceptable to the client. Has anyone encountered a similar problem? Is there a solution to this? 

I heard back from Hyperion Tech Support again. Turns out it's not a defect after all. It's actually a subtle technicality in the restrictions on shared members with ASO. The first restriction, which is explained in the outline verification error message, is that you can only have one instance of a shared member within a given stored alternate hierarchy. The second restriction is that you cannot have any shared members within a given stored alternate hierarchy where the non-shared instances of the members are ancestors/descendants of each other. Unfortunately, when this restriction is violated, EAS gives the same error message as it does for the first restriction, so it's a bit harder to debug. Hope this saves someone some grief. -Silvester

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 duplicate member enabled EPMA outlines

Hi all,
I have created an EPMA ASO "allow duplicate members application". I want to create an alternate shared hierarchy but all teh shared members are getting deployed in essbase as stored members. Do I need to enable any other property also so that shared members are treated as shared members only and not stored members.
Thanks in advance.

Can anyone please answer this...its very urgent

Duplicate Members in Essbase

I need to have duplicate members in one of my dimensions, without adding a qualifying prefix or sufix. For example, suppose my dimension is as follows:
Country->State->City->Zip. I want to have duplicate member names at the City level, without having something like "MA_Springfield". I want the city name to just be "Springfield"
So in order to accomplish this, I modify the key binding for City in Essbase Studio to the following:
*"[" || connection : \'OBIEEDEV'::'ENTERPRISEBI.COUNTRYDIM.'Country' || "].[" || connection : \'OBIEEDEV'::'ENTERPRISEBI.COUNTRYDIM.'State' || "].[" || connection : \'OBIEEDEV'::'ENTERPRISEBI.COUNTRYDIM.'City' || "]"*
I then enable duplicate members in Essbase properties and deploy the cube, but the Cities that are duplicates get dropped during the outline build.. The error messages say that *"duplicate members are not allowed at this generation level"*
What am I doing wrong?
Appreciate any advise.
Fyi - I'm building an ASO cube in EPM 11.1.2 using Essbase Studio. Also, in my Essbase properties Outline Build, I'm choosing the Move duplicate members (and their descendants) setting
Edited by: 806008 on Nov 11, 2010 11:19 AM
Edited by: 806008 on Nov 11, 2010 11:22 AM

Hello,
Create a new member down the first one in your dimension. Put the value 'shared member' in DataStorage options.
Regards

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.

Financial Reporting Studio - Suppress Shared Members During Entity Prompt

I am trying to create a Financial Reporting Studio report where the entity members that are displayed as a prompt only reflect the entities the user has access to with only one occurrence in the list. I have tried the following scenarios with no luck.
In Workspace, the Financial Reporting Preference, the Setup User POV option "Member Selection Displays" is set to "Only Members I Can Access" and not "All Members Regardless of Access".
The Financial Report is set up so that the user is prompted for the Entity so they can select multiple entities to run the report.
This works fine, except this is also displaying the shared members in the alternate hierarchies when responding to the Entity prompt.
As part of Defining the prompt, I have included the main entity structure in the "Choices List" in hopes that the shared members wouldn't display as an option to select, but this ends up displaying all of the entities in the hierarchy overriding what is the Financial Reporting Preference (acts like "All Members Regardless of Access"). I have also tried the Union of "Suppress shared members" and "Same level as" a level zero entity, but I'm still seeing all of the members of the main entity hierarchy, rather than a list of entities the user has access to.
Is there a way to display all of the entities only once that a user has access to during a prompt for a report? I would greatly appreciate any advice. Thanks in advance!!

I don't think there's a native way to do this in HFR. How could it be done other than through creating a custom selection list? Okay, I guess that is one way but it hurts my brain to think about maintaining it unless it could maybe be done through IDESCENDANTS of 1 and 2.
Here are two other thoughts:
1) Write a report against the Planning (I could be wrong about you using Planning as you specify Essbase, but the question is in the Planning board) tables to get this information. I don't know how to do it, but I'm guessing with some SQL gyrations it should be possible.
2) Stick an attribute against hierarchies 1 & 2 and report on them that way. You the designer already know that they are related. More maintenance on the front end, but a surefire way to get the member list out.
Regards,
Cameron Lackpour

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.

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

Duplicate Member Outline and Loading Shared Members

I have an outline where I want to allow duplicate member names but in some cases I will need shared members. I am trying to build the outline parent child and I cannot get it to understand the fact that I want a shared member.
Here is an example:
[market],east
[market],west
[market],other
[market].[east], nj
[market].[east], ny
[market].[west], ca
[market].[west], lv
[market].[other],[market].[west].[lv] <--- this should be shared
[market].[other],ny <--- this should not be shared
Does anyone know how to do this?

If you would like to less the charecters and if you are retrieving the data using SQL, then you could using the Substr function to restrict the characters to 80 substr( string, start_position, [ length ] )

How to load shared members into a duplicate outline using load rules

Hello, I am trying to load an alternate hierarchy into the same dimension in an outline that accepts duplicate members using EAS load rules ... there is no property for shared members so i can't specify it in the load rule .. i tried using parent child and it is not working - no shared members are loaded in the alternate hierarchy .. any ideas? would another utility make it happen?
thx

You might find this useful: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm
Especially the Building Shared Members by Using a Rules File section: http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_dbag/dotdimb.htm#dotdimb1061244
Cheers,
Mehmet

Enabling Duplicates / Disabling Shared Members in Essbase Studio

Similar Messages

Maybe you are looking for