Outline Extractor - Attributes - Implied Shared members

I am attempting to extract the attributes from one cube to load into another cube. Some of our attributes are at the level 0 and others are at level 1. We have many parents that have one child, essentially an implied share.
When I run the outline extractor, the implied shared parent attributes are assigned to the child. When you have a implied share scenario, is there a way to get the attributes extracted to the proper level?
Forgot to mention... We are 9.3.1.
Thanks.
Edited by: GlennH on Jan 31, 2011 8:40 AM

Hi Glenn,
Send email to [email protected] and my OlapUnderground support guys can take a look at it..
Tim Tow
Applied OLAP, Inc

Similar Messages

Shared Members in ASO

All - I am migrating outlines from 6.5(BSO) to 7.1.2 (ASO).When Imigrate I am unable to migrate shared members from BSO to ASO evenafter assigning the DIMENSION as Multiple Hierarchies Enabled. For Ex: DIM 1 (Multiple Hierarchy Enabled)..... Member 1(Dynamic Hierarchy) Child1 Child2 Child3 Child4 Member 2(Stored Hierarchy) Child3 (Shrared Member) Child4(Shared Member) I get an Error message as ASO does not support Shared Membersbut I have read that if you enable a dimension as MultipleHierarchy Enabled you can assing members of a Stored hierarchy asshared members.Please help with any inputs.Thanks in advance. Jeeva 

Had similar problem. Solved it doing these: in BSO outline, temporarily rename your shared members - just so the Conversion wizard can work. Change Dimension to Dynamic Calc. Once converted, change Dimension to Dynamic Hierarchy. Restore shared members to original names.

Missing parent members in 3.1 Outline Extractor

All, I am using OLAP Underground 3.1 Outline extractor. The server is windows 2003 and I am using Hyperion Essbase 6.5.7 I am taking a dimension that has been updatred and manipulated and trying to get it into 50 other databases in a automated process. I have built the automated process but the problem is with the outline that is extracted using 3.1 outline extractor, it is missing several parent members. This dimension has 27,598 members. Thanks Anthony

I was running into the same issue on dimensions with a large number of members. If I remember correctly it is a known bug that they plan to address in some future release of the Outline Extractor.

Building RULES file to load shared members in Aggregate storgage outline

Hi there
I posted this yesterday (sorry, somewhat different subject description). I am trying to create an alternate hierarchy containing shared members using a load rule and flat file in an Aggregate Storage outline. One response was to remove the "allow moves" option and use parent child build in the load rule. I tried that and it did not work. i was pointed to a section in the essbase guide (which is about as clear as mud), and still cannot get this to work. First of all - can you do this with an ASO outline? If so, how? I tried a simple 6 line flat file and recreated the load rule based on the above recommendations and it will not the shared members. Can someone out there help?
thanks

Here is an example in the simplest form.
Create Aso db (duplicate members names not selected)
Create Product dimension member, set to "Multiple Hieararchies Enabled", (though probably would work if dynamic)
Create load rule, set as parent/child dimension build for product, make sure allow moves is not ticked.
Data file
Parent,Child
100,100-20
200,200-20
Diet,100-20
Assign field properties in rule for Parent.Child
Load data, 100-20 will be created as shared.
Cheers
John
http://john-goodwin.blogspot.com/

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

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

Outline Load Utility - associating attributes when loading members

Hi - simple one this I'm sure.
I'm trying to use the Outline Load Utility to load members to a simple custom dimension, which already exists. I want to assign an attribute to each member I am adding.
So I have my data file with the requisite headers including "Attribute Dimension Name" as per the HP admin guide.
I specify member name, parent, alias, and the attribute member I want to associate with the dimension member I am adding, but the utility does not like the header & returns *"unrecognized column header value "Attribute Dimension Name" "*
here is the script:
OutlineLoad -f:h:\HYSL\password.txt /S:demodrive /A:MikeTest /U:demoadmin /M /N
/I:c:\Bootcamp/OLUtest\Dim3.csv /D:Customers /-C /L:c:\Bootcamp\OLUtest\Dim3Load.log
/X:c:\Bootcamp\OLUtest\Dim3Ldex.exc
here is the top of the file:
Customers,Parent,Alias: Default,Attribute Dimension Name
Cust 3,Top 10 Customers,,North
Cust 4,Top 10 Customers,,South
Cust 5,Top 10 Customers,,East
Thx

You have to give the attribute dimension name, so if you have an attribute dimension called "Shop", then your head would be
Customers,Parent,Alias: Default,Shop
The attribute dimension already has to exist as well.
Cheers
John
http://john-goodwin.blogspot.com/

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

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

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

Issue on the Data Form - Implied Sharing

Hello,
We have a data form on which the user can drill down till Level 0 Customer in rows to input data. The issue is for some customers when the user is trying to input the data at Level 0 Customer it is not saving the input number but was getting overridden with the parent value automatically. If the user was inputting at parent customer it was filling the same value to the level 0 customer too.
When I checked in the outline...I noticed that these were the Customers that had only a single child and I am guessing that this is happening because of the implied share property. I am not sure if there could be any other reason for this to happen. If I am wrong please do correct me.
Now I know if you change the property of the parent customer to Never Share it might resolve the issue.But the problem here is - there are a lot of such customers. And every month we do get new customers that could belong to the same case. It would be tough to manually go and change the property to Never Share for all those Customers and keep a track of it. It might be a maintenance issue.
So are there any other solutions? Can we somehow resolve it? Please let me know your suggestions or ideas on what you think would be the best way to get this fixed.
Any ideas are appreciated.
Thank you !
~ Adella

Thanks a lot Robb for your suggestions.
Yes you are right since both the parent and the children are set to store in our outline more blocks are being created.
Taking the parent off the data form might not be the best solution as there are many such customers and in that case they might have to keep a track to not include such parents on the dataform specially while designing it..and also then its like some of the customers will show parent and children both and some only children in rows. I think they wouldnt like it and it might hurt consistency. But yes I will surely check on the option of turning on the Implied Sharing in the Essbase.cfg
Thanks once again !
~ Adella

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

Outline Extractor - Attributes - Implied Shared members

Similar Messages

Maybe you are looking for