Alternate hierarchy on parent members

We have a hierarchy in a sparse dim
parent1
     Child01
     child02
parent2
     child03
     child04
We need to create a alternate hierarchy on parent members
AltHier1
     parent1(Shared)
     parent2(shared)
Can we create a alt hierarchy on on parent members?
Thanks

I would go with the alternate hierarchy -- you'll get much better performance that way. Sparse member calcs that touch lots of blocks tend to not perform very well and force you to go with CALC DIM instead of AGG.
I think you could use a METAREAD filter to only give them access to the parent. I'm not 100% sure of this because the base parents would have read rights. I have to say that isn't something I have tried so you'd have to give it a test before you went down that path. Or if you are doing this in a canned report, simply don't show anything below the alternate parents' parent.
Regards,
Cameron Lackpour

Similar Messages

Load rule to update alternate hierarchy with shared members more than once

I have a aso cube with an alternate hierarchy that is not stored because the shared members appear more than once. Below is how my alternate hierarchy looks.
Dept
Class
VolumeLevel
StoreNum
where StoreNum is the shared member.
I build the cube using eis every weekend. The VolumeGroup changes everyday, so I was thinking of using a sql load rule to update the outline everyday. Assuming that the data and the aggregation does not get cleared. Is it possible to do it using sql load rule?
Thanks,

You can check here if you are satisfying the conditions for creating shared members under the Hierarchy (refer to Alternate Hierarchies). Plz note that rules for shared members are different in ASO world.
http://docs.oracle.com/cd/E17236_01/epm.1112/esb_dbag/frameset.htm?acrtapdb.html
Otherwise there is no reason why you should not be able to create a shared member.
I am able to create a hierarchy using a sample file like this ->
EN_MAIN, EN_500000
EN_500000, EN_49999
EN_ALT, C_500000
C_500000, EN_49999
ENTITY (Multiple Hierarchies Enabled)
|-EN_MAIN (Stored)
|--EN_500000
|---EN_49999
|-EN_ALT (Stored)
|--C_500000
|---EN_49999 (Shared)
The rule file has only "Allow Property Changes" on.
Thanks,
Sunil

HOW TO BUILD AN ALTERNATE HIERARCHY IN HFM WITH SHARED MEMBERS

Hi All,
Could some one suggests the steps to build an Alternate Hierarchy in HFM via Shared Memebers. I am facing the problem while selecting options for "IMember" or "Idescendant"?
It is urgent, any help is highly appreciated.
Thanks in advance.
Regards,
SM

It sounds to me that you are trying to create the entity again as opposed to re-using it from the Member List. Follow steps below:
#1 - Start Hyperion Financial Management Client (Start-->Programs-->Hyperion-Financial Management-->Financial Management)
#2 - Click on the Manage Metadata option to the left
#3 - Click on the Open File button (assuming you have an existing file)
#a - Browse and locate your metadata file
#4 - Click on the Metadata Item drop down box and select entity
#5 - If Parent 1, Parent 2, Co A, Co B have not been created, create them now. Place Co A and Co B as children of Parent 1.
#6 - click on the tab that says Member List (by default its on Member Attributes)
#7 - Locate Co A and Co B and drag them to Parent 2. This will add them to Parent 2.
#8 - Save your file of course
Hope that helps.

Essbase Studio Alternate Hierarchy Creation error

Hi All,
I'm using Essbase Studio to create an alternate hierarchy. I have a dim which has shared members and I'm getting the following error msg during cube deployment:
1. Record #1- Member Name (SKU) already used i.e. the member for which I m trying to create shared member
     I m following the same procedure mentioned in the user guide i.e.
        Step1: create a copy of the dimension element that you want to designate as a shared member(Renamed SKU_copy with SKU_Diet). By making a copy, the binding expression for this element is the same as the original dimension element (SKU_Diet).
       Step2: when you create the second hierarchy in the chain, which is the alternate hierarchy, add a user-defined membas the parent and add the new dimension element (SKU_Diet) as the child, which will be the shared member.
     Even I m able to see the shared members (SKU_Diet) under user defined member "Diet" under the preview window (both by key binding and caption binding) as wel..
     But I m unable to see the shared members in EAS console after deploying the cube from Essbase Studio to EAS Console.
I m not able to understand what I m missing exactly,.and suggest me other ways as well for creating alternate hierarchies in Essbase Studio.
Thanks in advance..!!

looks like similar issue..
https://forums.oracle.com/thread/1555956
It will work in genaration 2 not in genration 1.
Thanks,
mady

Best Practice - HLevel for Alternate Hierarchy

Good morning,
Our Account dimension contains both a standard and alternate hierarchy. We currently use the HLevel property to drive a variety of formatting (hierarchy indentations, outline for "data bottom", bold for "parent", etc.). The formulas we've developed for the standard hierarchy work well, but they don't always work with the alternate hierarchy. I'm considering the creation of a new "Alt_HLevel" property that would contain the associated numerical hierarchy levels for the alternate. This would provide a level of simplicity in reporting as it would allow us to use consistent formulas. Downside is the added maintenance. Before proceeding, I'd like to know if anyone has a better solution. Thanks!

Hi Kim,
As far as my understanding says, HLEVEL will work with the 1st hierarchy of your dimension. So, if you want, you can definitely go ahead by adding another property for the second hierarchy. But yes, as you have already figured out, the cost would be at the maintenance. If you are having regular additions to your dimension, it might be difficult to maintain this property. If the addition of members is not frequent, then I dont see any challenge.
Alternatively, you can try using H2 when you are calling the HLEVEL property. I have never checked this, so not sure whether it will work or not. But worth trying.
Hope this helps.

Alternate hierarchy dimension build with load rules

Hi,
I am trying to build a alternate hierarchy dimension using load rules (I feel using EIS is easier to build ASO and multiple hierarchies but we r trying to get rid of EIS member loads). Looking at different posts my understanding is it has to be done using two different rules file first to build the stored hierarchies then use parent-child reference to build the shared hierarchy. Below is the link for the picture how I am trying to build the dimension. I've tried different possibilities but no luck, I am having a tough time to come up with a way to do this using rules file.
http://s24.postimg.org/u5hl4eyqt/basis.jpg

If your file is in a parent/child order, then you can build easily in one rule. make sure the primary (stored Hierarchy) gets built first followed by the alternate hierarchies. I suggest adding a SortID column to the source so you can sort the file to get it into the right order. You can also build the alternate hierarchies using level or generation builds in one load rule, but especially if you have a lot of alternate hierarchies or members, then the parent/child method is easiest.
Read in the DBAG about parent/child files and it will give you more info

BPC Alternate hierarchy rollup issue - require help

Hi All,
We are seeing a rollup issue on Alternate Hierarchies. We had set-up alternate hierarchies on our Country Dimension (DC) to assist some managerial reporting that is only relevant to one of our Operating segments.
To show the problem, I am listing an example of our Country dimension member sheet. I have put "**" delimiter between the pertinent values to show which columns the values land under.
ID*DescriptionPARENTH1PARENTH2FORMULAH1*FORMULAH2
MAIN_HIER*Main Hier* ** ** ** **
D1*DC EuropeMAIN_HIER* ** ** **
A*Country AD1SG1* ** **
B*Country BD1SG1* ** **
C*Country CD1SG2* ** **
D*Country DD1SG3* ** **
D2--DC India*MAIN_HIER* ** ** **
E*Country ED2--ALT_HIER* ** **
C1*Calc Eur* ** *DC.H1.D1+DC.H1.E* **
ALT_HIER*Alt Hier* ** ** ** **
SG1*Sub Reg 1* *ALT_HIER* ** **
SG2*Sub Reg 2* *ALT_HIER* ** **
SG3*Sub Reg 3* *ALT_HIER* ** **
We have our main Country hierarchy that comes under the root parent MAIN_HIER. In addition to that on our main hierarchy we had a calculated node for Calc Europe (C1) which is supposed to be a summation of DC Europe (D1) + Country E (E). We had created an alternate hierarchy to represent a breakdown by more subregions (SG1, SG2, SG3 and Country E) within DC Europe so basically the root node of the alternate Hierarchy (ALT_HIER) should show the same amounts as the calculated node C1 on the main hierarchy.
If we take a higher level Account dimension member like NET_SALES the values tie out but if we take a base member in the Account Hierarchy (e.g one representing Customer Sales), the values don't match with the ALT_HIER values seem being the wrong ones. It almost seems like the rollups of the Alternate Hierarchy are not accurate.
Could you pls. shed some light on if the dimension member set-up above is wrong from any angle.
BTW, we are on BPC 7.0M SP04 Patch 2 and SQLServer version is SQLServer 2005 EE SP3.
Your insights would be greatly appreciated. Thanks in advance.
Regards,
Abhay Shanbhag

Abhay:
Please try below...
Add "RollupChildren(Account.Hx.CurrentMember,"+") to all non-base members who don't aggregate properly under FORMULAHx. For instance, I have below hierarchy PARENTH1 for Balance Sheet Total Asset
BALSHEET
TotalAsset
-CurrentAsset
-NonCurrentAsset
If CurrentAsset and NonCurrentAsset all roll up fine but TotalAsset doesn't add up. In your Dimension, put MDX formula RollupChildren(Account.H1.CurrentMember,"+") for TotalAsset and BALSHEET under FORMULAH1.
We have this issue when we created additional hierarchies, and it took us a while to debug before I got this hint from SAP Support. Ever since it works like a charm =)
Hope this helps
Brian

Attribute Dimension or Alternate Hierarchy

Hello,
We have a sparse dimension that has probably around 1500 members. We need to report on these members in different views then the current hierarchy holds. Is it best to create an alternate hierarchy with these 1500 members or to tag these members with various attributes and then use the attribute in the different reports. I did some research and found that attribute dimensions often have slow FR performance since they are dynamic, however, I feel like 1500 shared members is a lot. Any tips, tricks, advice would be greatly appreciated.

Hi,
I don't think 1500 shared members is a concern in and of itself (unless you are putting them all under one dynamic parent!). You are correct there could be some response time impact with attribute dimension retrievals, but then shared members under dynamic sparse parents may present similar concerns.
I would encourage you to think about the structure and navigability desired. You should keep in mind that shared member rollups can only be used in reports consistent with the dimension they are in. One advantage of attribute dimensions over shared rollups is that, only with attribute dimensions, can you cross-tab report against the base dimension. If your users care about being able to see certain alternate groupings across the main dimension, then I would suggest going with attribute dimensions.
There are other considerations. For instance, adding a large number of shared rollups in your BSO anchor dimension (the physically last dimension with hierarchy), you put more demand on Essbase calculator cache.
Out of time for now. Just sharing some initial thoughts I hope you will find helpful.
Darrell Barr

Alternate hierarchy with only the Leaf nodes

Hi,
I have an account hierarchy with multiple levels in it. Now I want to make an alternative hierarchy with only the leaf nodes of that hierarchy with using the same nodes. Can anyone please explain the steps how to do it.

Unless you have any special requirements it will be straight forward, get an export of all the leaf members in an action script format and execute the INSERT action on your alternate hierarchy, you can create your alternate hierarchy with only the TOP node and insert the leaf members under it, in case you have thousands of them, you can split them by introducing dummy parents, also if you wish to maintain any local properties, please have them updated accordingly.

Alternate Hierarchy's

Good Morning
Is there any way to create an alternate hierarchy without having to use shared members? I have users who want me to duplicate a hierarchy (1000 members) but remove 1 member only from the alternate. This means having to copy the original hierarchy and making all the children shared members and making the parents unique. Is there an easier way to do this? Using Reporting software is not an option as my users all use excel.
thanks

Ah, another good use for the "Views" dimension.
I would go about this with a custom dimension, I've seen called "Views". For the most part it is only 1 stored member, say "Data". But then you can have all kinds of Dynamic Calc members that are some variation of what is actually stored. So in this case you could have a Dynamic Calc member with a formula that is basically
@sum(@Remove("@Relative("Dimension", 0), <member to be removed>)).
It will probably be a slow retrieval, if they need it faster then consider making it stored and putting the formula in the nightly calc.
Robert

How can I see different results for alternate hierarchy?

I have an outline with an accounts dimension with the following members (amongst others):
Total Expenses
Exp1 +
Exp2 +
Exp3 +
Exp31 + (child of Exp3)
Exp32 + (child of Exp3)
Exp33 + (child of Exp3)
I also have another dimension, let's call it DIM, with the following primary and alternate hierarchies (shares upper levels with primary):
Primary
A
A1 +
A2 +
A3 +
B
B1 +
B2 +
B3 +
Alternate
A + (shared member)
B + (shared member)
I want to be able to do the following:
When I select something from the primary hieararchy, I want to see the original values in Exp31, Exp32 and Exp33. When I select a member from the alternate hierarchy, I want to see these 3 expenses zeroed out. Is this possible? I can't find a way to do this since the values for shared members are taken from primary members. Is there another way to do this?
Thanks for your help.
Bela

I did think of creating an alternate hierarchy in the accounts dimension which excludes the expenses I do not want to include in the total, but I have 3 different categories of expenses I want to exclude depending on the members I'm viewing, so I'll have to create that many alternate hierarchies in accounts, each excluding a specific category of expenses.
If you have a brainwave, please let me know!
Bela

Inclue children and exclue children in a single hierarchy in parent child dimension in mdx

hi,
include children and exclude children in a single hierarchy in parent child dimension in mdx
*12-parent
**20-parent
- 9-parent
--250-child1
--210-child2
--240-child3
aggregation of 12-parent only
aggregation of 20-parent only
aggregation of 9 with children
regards,
Manish

Hi manishcal16PPS,
According to your description, you have a parent child dimension in your cube. Now you want to use one measure use show aggregation value including/excluding child member based on different parent level member. Right?
In this scenario, we could use IIF() in the calculated measure to apply different calculation depends on the current dimension member. Please refer to query below:
with member [x] as
IIF([Dim].[Hierarchy].CurrentMember is [Dim].[Hierarchy].[Parent].&[9]
sum(Descendants([Dim].[Hierarchy].CurrentMember,
[Date].[Calendar].[Parent]),
[Measures].[Amount])
sum([Dim].[Hierarchy].CurrentMember,[Measures].[Amount])
select [x] on 0,
[Date].[Calendar].[Parent].members on 1
from
[Cube]
Best Regards,
Simon Hou
TechNet Community Support

Having issues when creating alternate hierarchy in time dimension

Hi Everyone
I used How to guide of MS version 7.5 to build 2 hierarchies in time dimension.
It worked in MS version.7.5
But when i copied the same dimension members to NW version the alternate hierarchy (parenth2) doesn't work.
I mentioned all the required properties for both roll ups (like parenth2,timeid,usertimeid,ISBEGINNING).
Any idea?
thanks
reddy

"This sounds confusing to me as to how a stored hierarchy can contain a shared member from a dynamic hierarchy"
You just need to understand how things are stored in ASO for this to make sense.
A level 0 member with no formula, even though it is in a dynamic hierarchy is still a stored member.
-- All level 0 members that do not have formulas are stored in ASO.
Upper level members are all "dynamically calculated".
-- Upper level members of dynamic hierarchies are pure dynamic.
-- Upper level members of stored hierarchies are candidates to have their values pre-aggregated and stored in a view.

Loading alternate hierarchy

Hi,
We have a source file that contains only the alternate hierarchy(Shared members). Finding a way to load it in EPMA dimension library. Is that possible? I couldnt find a suitable option in the import profile.
we are on 11.1.2.2.300. However it was easier in 11.1.2.0 as there was an checked box "Shared" which could create all members as shared.
Regards,
Ragav.

Celvin,
Thanks for your reply.
We are trying to import in EPMA from interface tables. We are not able to use Merge as Primary as it is creating all members as Primary members even when my source as shared. It also duplicates members when the source has a member that moved to a different hierarchy. Even Merge as Move is not suitable as it will load only primary hierarchies. Replace is also not suitable as our source does not contain the whole dimension.
How else can we achieve loading just the alternate hierarchy? Looks like lack of functionality.
Regards,
Ragav.
Edited by: ragavhere on Apr 17, 2013 12:24 PM

Shared Hierarchy for DTS members

Hi,
Is it possible to create alternate hierarchy (Shared Member) for DTS members in planning application.
I am using Hyperion 11.1.2.1 version.
Regards,
Sunil.

Hi Amit,
Thanlks for your reply. But Iam facing some problem while creating it as below.
Whan I am creating a DTS shared member directly under period dimention (Sibling to YearTotal) I am able to create it. But when I am trying to create under alternate hierarchy, I am getting the following error.
"You cannot add or modify the main hierarchy members to the alternate hierarchy under time periods. Check the Administrator's Guide for more information"
Regards,
Sunil.

Alternate hierarchy on parent members

Similar Messages

Maybe you are looking for