Alternate Rollups

Hope someone can help....We have a cube with the Time dimension going down to weeks tracking sales cycle changes (which is a regular dimension)Jan_2003week1 - cycle 1 to cycle 2week2 - cycle 2 to cycle 3...week4 - cycle 4 to cycle 5Feb_2003week1 - cycle 5 to cycle 6etc...Users would also like to see Monthly/Quarterly/Annual rollup of cycle changes. So for example above..Monthly Jan rollup would indicate:cycle 1 to cycle 5Monthly Feb rollup would indicate:cycle 5 to cycle 6Quarterly rollup would indicate:cycle 1 to cycle 6I can find a way to track this information in SQL (we're using EIS to load the cube) but I'm not sure how I can represent it in Essbase. Would this involve alternate rollup's in the Time dimension?The Time dimension is also being used by other Scenarios.Any thoughts would be greatly appreciated.Thanks.

not sure I understand the cycling part entirely but you should be able to do your monthly and quarterly roll-ups by using the cycles as shared members under them..

Similar Messages

Alternate rollups missing aliases

i have just spent a lot of time cleaning up the aliases on several alternate rollups. i then update my database in planning and i open essbase and the aliases are gone. how can i keep the aliases attached to the alternate rollups

I've solved this by putting an esscmd job to import aliases at the end of my HAL outline.

Creating Alternate Rollups in Planning

Hi,
I need to use ODI to load entities in a way that alternate rollups (shared members) can be created.
For example, if District_4312 currently exists in Branch_4312 and I subsequently try to load District_4312 to Branch_5312 (a different rollup), I would want to load it to Branch_5312 as a shared member.
When I try to add a pre-existing member to a new parent, it moves the member instead of Sharing it.
Is there a way to get the existing KM to create alternate rollups automatically ?
Do you know of any documentation about the default behaviors for this type of situation ?
If it needs to be done "manually", my guess is that I need to take the parent child format out of Planning into a table....
Then compare my new (incoming) entity list to what pre-exists in Planning. This will make a list of the member that need to be loaded as "shared"....
Then do the load.
Does anyone have an easier way to accomplish this (an existing KM perhaps).
If I need to go with the manual approach, Is there an existing knowledge module I can use to take the members out of Planning into a SQL table?

Hi,
I am not sure what you mean by custom events, is it possible you can expand. If it involves manipulating the data that already exists in the planning app then business rules are perfect for that.
Cheers
John

Entity data in alternate rollup not rolling up to parent.

We have a number of different entity hierarchies in our application. In our main entity hierarchy we have system rules setup to pull specific account data down to STAT accounts for particular entities and then that same STAT account data is pulled over to another entity multiplied by -1 as an offset so when the two entities rollup to a common parent the result is 0. This offset entity exists in other hierarchies. In the other hierarchies this offset entity STA account data does not rollup to the parent. The data only shows up to Parent Currency Total in the value dimension. Anything above that is empty, but viewing the parent.child combo in the main hierarchy and we can see data populated all the way up to Contribution Total, therefore roling up to the parent. Below is the rules we have setup.
Here in simplier terms is what we see.
Hierarchy 1
Entity A = $10
Entity B = -$10
Parent Entity C = $0
Hierarchy 2
Entity B = -$10 (Entity A does not exist in this hierarchy)
Parent Entity D = $0 (should be -$10)
Has anyone see an issue like this before?
Rule
If HS.Scenario.Member <> "ProForma" Then
 If HS.Value.Member <> "[Elimination]" Then
If HS.Entity.Member() = "E261" Then
 HS.Clear "A#AC90285"
 HS.Exp "A#AC90285 = A#AC76740"
 HS.Clear "A#AC90286"
 HS.Exp "A#AC90286 = A#AC70160"
End If
If HS.Entity.Member() = "E271" Then
 HS.Clear "A#AC90285"
 HS.Exp "A#AC90285 = A#AC76740"
 HS.Clear "A#AC90286"
 HS.Exp "A#AC90286 = A#AC70160"
End If
'E103 - Corporate offset
If YearPOV > "2013" Then
If EntityPOV = "E103" Then
 HS.Clear "A#AC90285"
 HS.Exp "A#AC90285.I#[ICP None] = (E#E300.A#AC90285.I#[ICP Top] + E#E104.A#AC90285.I#[ICP Top]) * (-1)"
 HS.Clear "A#AC90286"
 HS.Exp "A#AC90286.I#[ICP None] = (E#E300.A#AC90286.I#[ICP Top] + E#E104.A#AC90286.I#[ICP Top]) * (-1)"
 HS.Clear "A#AC90287"
 HS.Exp "A#AC90287.I#[ICP None] = (E#E300.A#AC90287.I#[ICP Top] + E#E104.A#AC90287.I#[ICP Top]) * (-1)"
 HS.Clear "A#AC90288"
 HS.Exp "A#AC90288.I#[ICP None] = (E#E300.A#AC90288.I#[ICP Top] + E#E104.A#AC90288.I#[ICP Top]) * (-1)"
End If
End If

There are trigger account rules, but not for this scenario. This also occurred before we added those rules. If you see below in our main hierarchy E100 we have a corporate offset for -2,695,080 which goes against the data rolling up in E104 and E300. In the secondary hierarchy only E103 exists with one other entity E428 and for some reason that offset data does not roll up to the parent E060.

EPMA 11.1.2.1 (Interface Tables) Working with Shared Upper Level Members

Hi Everyone,
I am building a hierarchy with interface tables in which I specify a shared member. In the interface table, I assign a null datastorage and a 0 for the ISPrimary to designate the shared member. The stored member has a datastorage of storedata and an ISPrimary of 1. The sort order for the shared member is set at 999999 and the sort order for the stored member is 6.
We have an org hierarchy that goes Division->Business Group->Department. Please reference the member that is highlighted for the two questions I have below.
I just made up some hierarchy names and placed in parenthesis what the member name would look like in our real hierarchy.
Example Hierarchy:
Organization
|--Main_Hierarchy
|--|--Division1 (DV_XYZ)
|--|--|--BusinessGroup1 (BG_ABCD)
|--|--|--|--Department1 (DP_1234)
|-Alternate Rollup
*|--|--Division2 (DV_ABC) [stored]*
|--|--|--BG_123
|--|--|--|--DP_9999
|--|--|--|--DP_9876
|--|--Research Division (DV_ZZZ)
*|--|--|--Division2(DV_ABC) [shared]*
I have 2 issues with this setup.
1) When I run an import into the shared library, I see the shared member with children underneath it (the same children that are under the stored member) Is this supposed to look like that, or is there an additional configuration that I need to make? When I look in the application library, I see it correctly with the shared members having no children, but the shared library shows the shared members with children.
2) When I run a deploy to the application, the application library shows the hierarchy correctly, but Planning and the Essbase Outline reversed the members (The stored member comes in as shared and the shared member comes in as stored in essbase and planning, but the application library shows it the correct way). Just wondering if someone could suggest a starting point for me to try and troubleshoot this issue.

Is this an essbase only application? It seems like the property is defaulting to stored and then flipping the initial stored member to shared because Essbase isn't interpreting the deployment correctly. I would try using ShareData as the datastorage property (I think that is the correct spelling). Also, I believe the correct way to set IsPrimary is Y/N and not 0/1.
If that did not work I would try the following in this order:
1 - I would first extract the dimension in question using the file generator and confirm that the properties are indeed correct.
2 - If they were correct. I would toggle the dimension from shared->local->shared. EPMA is still a little nutty and this will fix a fair amount of issues as it will 'refresh' the application's version of the dimension. I would then deploy
3 - deploy from EPMA->Planning only (no essbase creation), then deploy to essbase separately after ensuring the property represents itself in planning. If it is essbase only - create the outlnie instead of refresh.
4 - create a duplicate app in EPMA and deploy the copy of the app - and see if it has the same problem
Try that and see how it goes.

Hyperion Planning Data forms - conditionally/dynamically populate rows

I am building a budgeting data form which I am trying to invoke some dynamic capabilities so that it is either not one giant for, or one that users have to load to multiple pages through a drop-down, which they will essentially see as too cumbersome and not accept it as a good solution.
The basic relationship is one entity owns multiple cost centers. I am trying to find way that a user can select their entity in the header row drop-down, and from that have the data form only pull in their relevant cost centers into the rows, then repeat the set of accounts we have defined for each group.
Essentially i want it to provide something such as below (the spacing is not being recognized, but the accounts should all be justified into a row). The set of entities are pre-defined. No problem. As are the set of accounts. The issue is getting it to vary which cost centers are on the page to load to. There are thousands of cost center in the system, so again I can't list them all. Also there are hundreds of entities so I can't have a different form for each. Way too much maintenance. I have a few ideas on how to link the relationship between the entity and cost centers. Probably an attribute on each cost center to tell it which entity owns it. Or worst case an alternate rollup in the Cost center dimension, grouping them together under a CC-Entity parent. Problem again is how do I use this in the form? Open to any suggestions at all. Thanks
Mark
Sample
Entity (user selected)
Cost Center 1 Account 1
Account 2
Account 3
Cost Center 2 Account 1
Account 2
Account 3
Cost Center 3 Account 1
Account 2
Account 3

If you have data tied for the cost centers of entities 'supression' options should only bring the related cost centers.
You can put all entities and accounts in a single form , member level access will only let the users see what they have access to...
There may be other solutions from experts here..
Thanks

Security/Filter on a Shared Member Parent

I have a few alternate rollups in my 'Organization' dimension. I have allowed Read access to the appropriate 'real' members. In my primary rollup, if all of the children for a parent have Read access then the parent can also be viewed, and so on up my hierarchy. However, this does not hold true in my alternate rollups. Under a parent where all of the children are shared members and the user has Read access to all of the shared members they cannot see the parent. I have to go through each alternate rollup and manually add the appropriate parents to my security filters. Is there a better way to do this?We're on Essbase 5.0.2. If this is fixed in later releases please let me know as we are planning an upgrade soon.Thanks,Damon

Would something like this work? EsbOtlFindMemberPass hMember to EsbOtlGetNextSharedMember While LoopPass hShared to EsbOtlGetParentPass hParent to EsbOtlGetMemberInfo (to get the szMembername)hShared = hHandleLoop Loop will continue until EsbOtlGetParent <> 0.

Question on best practice/optimization

So I'm working with the Custom 4 dimension and I'm going to be reusing the highest member in the dimension under several alternate hierarchies. Is it better to drop the top member under each of the alternate hierarchies or create a single new member and copy the value from the top member to the new base one.
Ex:
TotC4
--Financial
-----EliminationA
------EliminationA1
------EliminationA2
-----GL
-------TrialBalance
-------Adjustments
--Alternate
----AlternateA
-------Financial
-------AdjustmentA
-----AlternateB
-------Financial
-------AdjustmentB
In total there will be about 8 Alternate Adjustments(it's for alternate trasnlations if you're curious).
So should I repeate the entire Financial Hierarchy under each alternate rollup, or just write a rule saying FinancialCopy = Financial. It seems like it would be a trade off between performance and database size, but I'm not sure if this is even substantial enough to worry about.

You are better off to have alternate hierarchies where you repeat the custom member in question (it would become a shared member). HFM is very fast at aggregating the rollups. This is more efficient than creating entirely new members which would use rules to copy the data from the original member.
--Chris

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

Data is being triple-counted

For 2 members i see that data is being triple-counted.
What may be the reason...
How to solve it...
Can any one Help me tat.
Regards
BK

Do you have alternate rollups without the alternates being tagged as tilde(~)? is this an older database where you moved members around and perhaps you now have level zero members that used to be parents. Is the data being loaded with an additive load rule?
Unfortunatly, there are a lot of possibilities, with the limited information you have given it is hard give you an answer. The three guesses above are just that guesses

Need some ASO help

I am working with 14 dimensions overall. Essbase 9.3.1, outline built thru EIS.
My particular problem right now revolves around 3 different dimensions that are dynamic, with formulas on them.
Periods (Stored dimension, with multiple Hierarchies enabled)
-YearTotal
---Q1
------Jan
and so on up to Q4 and Dec
-YTD Members (alt dynamic hierarchy of Periods)
---Dec_YTD (Solve order 0; formula [Q1] + [Q2] + [Q3] + [Oct] + [Nov])
Views (Dynamic Dimension)
---Load (stored member)
---YTD (Solve Order 65; Formula Basically it's [Jan]:[&CurrentMonth])
Scenarios (Dynamic Dimension)
---Actual (stored)
---Forecast (stored)
---Reporting Forecast (solve order 1; Formula is basically When [Jan]:[&CurrentMonth] then [Actual] else [Forecast])
The [Reporting Forecast] member is new to the outline, and works fine at level 0 of Periods, but I can't get [YearTotal] or [Dec_YTD] to show the proper mix of [Actual] and [Forecast] members summed up. They are both showing the sum of [Forecast].
Of course there are other members of each dimension I have described, just trying to give you the simplest look into my issue.
Do I need to make the Scenrios dimension stored?
What do you think?
TIA,
Robert

Robert,
A couple of things I am unclear on.
1) Why do you have both alternate rollup for YTD and view dimension calculating YTD?
2) You stated +"The [Reporting Forecast] member is new to the outline, and works fine at level 0 of Periods, but I can't get [YearTotal] or [Dec_YTD]"+
Your member formula is written as +"When [Jan]:[&CurrentMonth] then [Actual] else [Forecast]"+
You are limiting the formula to level 0 members of periods, so it makes sense it is not doing anything for YearTotal or Dec_YTD

Consolidation PTD/YTD

On Consolidation Transfer Window you have the option to choose Amount Types (PTD/YTD)
What I understood from this is you can consolidate either PTD or YTD balances (beside other types).
I can see how PTD consolidation would work. PTD balances would be sent over to the Parent Ledger. Parent Ledger's YTD would be derived from this PTD activity.
What I don't understand is that how YTD consolidation looks like? How would PTD balances be derived in Parent Ledger?
Let me rephrase my question:
Shouldn't always period net activity (PTD) be transferred over to the parent? All other balance types like YTD, QTD etc would be derived from this period net activity? If we transfer YTD instead then how would period net activity be derived in parent?

A few things:WHat problem are you having with DTS? The calculation you describe looks like it could be solved with DTS without adding calculation overhead.Second, rather than create a new dimension, you could create an alternate rollup in your existing dimension, and use shared members to create the to-date totals.If you want to use a new dimension, you need 3 members in it, not 2:To Date - data - YTD - PTDYou need a placeholder to load the data into, then 2 members to apply the to date calculation to.The formula on YTD could look something like this:IF (@ISMBR (Jan)) YTD = data->Jan;ELSEIF (@ISMBR (Feb)) YTD = @SUMRANGE (data, Jan:Feb);... etc...ELSE YTD = @SUMRANGE (date, Jan:Dec);ENDIFThe formula takes the values stored in the data member and sums them across the appropriate range of months. The function for PTD could be similar, with slightly different logic.Hope that helps.Regards,Jade---------------------------------Jade ColeSenior Business Intelligence ConsultantClarity [email protected]

Dimension Build File - Member Property Codes

I am building a Dimension Build File.
What is the code to create a Shared Member?
I know the following codes:
Code
N Never Share
O Label Only
S Stored
V Dynamic Calc and Store
X Dynamic Calc
Or is there a different way to specify a member as a Shared Member in the dimension build file?
Thanks,
Dave

There is no property for a shared member. If you are using a parent/child build method it will automatically load shared members unless you specify don't share. To do a load as a level or generation build, you have to have the file in a particular order and use the dimension build tab of field properties. There is a section in the admin guide that shows you how to do it.
But for using level builds it would be something like
Lev 0, Product Lev 1, product Lev 2, Product Lev 1, product
100-20 100 Products Diet Colas
Notice how the second lev1 defines the alternate rollup and it would cause a shared member to be created

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.

METAREAD filter problem

Hi everyone, we’re using 11.1.1.3 and I’m having a Metaread problem in one of our BSO cubes.
I’ve created the following METAREAD filter:
"Actuals","3YP",@IDESCENDANTS ("Backups"),@remove(@IRDESCENDANTS ("store"),@uda(store,"restricted"))
When using the SV member selection, although I can not see the “restricted” members under the primary hierarchy, I can see the “restricted” shared names that are under an alternate rollup. Yet when I enter a “restricted” store manually, it doesn’t recognize it (which is good).
But when drilling down, or zooming in on a spreadsheet, the "restricted" shared member appears.
Shouldn’t the shared members that have a UDA "restricted' also not show up?
TIA

This should help explain how Metaread works when you're dealing with multiple filters & groups. Please let me know if you still have any questions, sounds like your filters are just overlapping. With Metaread once you assign access to a low level member he'll never see anything above it no matter how much higher access he has (basically).
From the Essbase Technical Reference guide:
Overlapping Metadata Filter Definitions:
You should define a MetaRead filter using multiple rows only when the affected member set in any given row (the metaread members and their ancestors) has no overlap with MetaRead members in other rows. It is recommended that you specify one dimension per row in filters that contain MetaRead on multiple rows. However, as long as there is no overlap between the ancestors and MetaRead members, it is still valid to specify different member sets of one dimension into multiple MetaRead rows.
For example, in Sample Basic, the following filter definition has overlap conflicts:
Access Member Specification:
MetaRead California
MetaRead West
In the first row, applying MetaRead to California has the effect of allowing access to California but blocking access to its ancestors. Therefore, the MetaRead access to West is ignored; users who are assigned this filter will have no access to West.
If you wish to assign MetaRead access to West as well as California, then the appropriate method is to combine them into one row:
Access Member Specification:
MetaRead California,West

Alternate Rollups

Similar Messages

Maybe you are looking for