Calculation in Secondary Hierarchies

Hi
Can anyone help me to apply a different calculation for a secondary hierarchy ? I have designed a BSO cube and the one of the Dimensions has a an Secondary Hierarchy . The requirement is that when a user look at the data for the Sec Hierarchy I want to apply a different calculation using cross dimension (than the Primary One) .
Thanks in advance
Unnimon

A different calculation for a member or a different aggregation to a parent?
A different calculation would have to have a different member name (could not be shared member) that could reference the original member in the calculation if you wish. And, really, if "one member" has two different calculations, the two instances really shouldn't have the same name anyway as they obviously mean (at least) two different things.
A different aggregation, you just put different aggregation on the shared member.
Have Fun!

Similar Messages

Disable Gain/Loss calculation for Secondary Ledger (SLA)

Hi Apps Gurus,
Currently I have the following functional SLA requirement:
I need to disable the Gain/Loss calculation in Secondary (subledger type) Ledger for AR invoice receipts in local/ledger currency. Below is the example, as it works now:
In the source primary ledger, on the AR invoice Receipt, there is NO gain/loss line, when paying ledger currency invoice on different date. But in the subledger accounting for secondary ledger there is calculated Gain/Loss line:
Example with Invoice No: 77775 in Receivables:
o     Primary Ledger currency: AUD
o     Secondary Ledger currency: USD
o     Invoice currency: AUD
     Invoice accounting entries for Primary Ledger:
-     GL date: 19-DEC-2012
-     Australia Spot rate for Primary ledger
Accounted_Currency=AUD, Entered_Currency=AUD
Revenue: Accounted_CR=4500.00 Entered_CR=4500.00
Recoverable Tax: Accounted_CR=450.00 Entered_CR=450.00
Receivable: Accounted_DR=4950.00 Entered_DR=4950.00
     Invoice accounting entries for Secondary Ledger:
-     USA Spot rate for Secondary ledger
Accounted_Currency=USD, Entered_Currency=AUD
Revenue: Accounted_CR=4325.00 Entered_CR=4500.00
Recoverable Tax: Accounted_CR=435.00 Entered_CR=450.00
Receivable:     Accounted_DR=4760.00 Entered_DR=4950.00
     Receipt accounting entries for Primary Ledger:
-     GL date: 20-DEC-2012
-     Australia Spot rate for Primary ledger
Accounted_Currency=AUD, Entered_Currency=AUD
Cash: Accounted_DR=4950.00 Entered_DR=4950.00
Receivable:     Accounted_CR=4950.00 Entered_CR=4950.00
     Payment accounting entries for Secondary Ledger:
-     USA Spot rate for Secondary ledger
Accounted_Currency=USD, Entered_Currency=AUD
Cash: Accounted_DR=4855.00 Entered_DR=4950.00
Receivable:     Accounted_CR=4760.00 Entered_CR=4950.00
Exchange Gain: Accounted_CR=95.00 Entered_CR=0.00
And we do not need the Gain line, despite the Receivable account would not be closed for this AR Invoice in Secondary Ledger.
Is there any option, functional setup in SLA, to disable calculation of Gain/Loss in such cases?
Many thanks in advance!
Krasen

Hi Ivruksha,
Thank you for looking into this case.
Of course if the Invoice was in foreign currency, there have to be a Gain/Loss line in the Primary Ledger.
But provided that in the Primary Ledger for NON-foreign currency invoice there is no FX lines, we don’t need such in the Secondary Ledger too. It’s a quite strange requirement, given the fact that the Receivable account balance will NOT be closed for this Invoice in the Sec. Ledger:
Dr: (Invoice) 4760.00$ and Cr: (Receipt) 4855.00$
So on the receipt I need the following acc. Entries for the Sec. Ledger (USD)
Dr: Cash 4855.00$
     Cr: Receivable 4855.00$
It is normal to have such functional behavior, provided that for the similar case in Payables there is NO FX line. See the example with AP Invoice in Sec. Ledger (USD):
Invoice GL date: 19-Dec-2012
Dr: Item Expense 4500.00 AUD / 4725.59$
Dr: Recoverable Tax 450.00 AUD / 472.56$
Cr: Liability 4950.00 AUD / 5198.15$
Payment Gl date: 20-Dec-2012
Dr: Liability 4950.00 AUD / 5184.46$
Cr: Cash 4950.00 AUD / 5184.46$
Fully balanced acc. entries, while the Liability account is definitely not closed from the both GL entries, which is accepted for the Secondary Ledger.
Hope this clears a bit more the case. I’ll appreciate any useful suggestions.
Of course the using “special” account code combination for recording the FX Gain/Loss in Sec. Ledger in the Account Derivation Rule as an workaround is a good option, if there isn’t any other.
Thanks and regards
Krasen

MDX calculations using multiple hierarchies

In previous versions of BPC (easpecially earlier versions of v5.1) it was not possible to have an MDX calculation (like a KPI in the form of A/B) when account A was part of Hierarchy1 and account B was part of hierarchy2.
Do anyone of you have experience in newer version of 5 (like sp7 or 8) or v7 and know if this issue has been solved ?
The thing is, in v4 these type of calculations worked.....
But in the beginning of v5 it did not.
Edwin van Geel

Actually in this version you can specify the hierachy and it is recommended to that every time when you are writting an MDX formula.
I think it should work but I never tried to be honest.
Regards
Sorin Radulescu

How to skip secondary window if main window goes to next page

hi gurus,
i m having a table in main window which lists items and its rate n quantity.
the total price,discount and discount is calculated in secondary window.
now if the list of item get more than window size it goes to next page but with calculation in both page in secondary window . i want to skip the calculation on 1st page.the calculation should only apear in scond page.
thnx in advance.

Hi..
******Case 1******************
Suppose if you want display the Totals only in Last page :
In the Secondary window:
/: IF &NEXTPAGE(C)& = '0'
<<DISPLAY YOUR TOTALS HERE>>
/: ENDIF
***********case 2**************
Suppose if you want display the Totals only in Last page :
In the Secondary window:
/: IF &PAGE(C)& = '2'
<<DISPLAY YOUR TOTALS HERE>>
/: ENDIF
reward if Helpful.

Functional and performance testing on Forms 6.0 and higher

I want to make functional tests on GUI Oracle Forms ver. 6.0 and higher.
I'm thinking in a IBM tool called Rational Robot but it's seems not very good. HP also has this type of tool with forms support but I haven't tested it, yet.
Does Oracle have some tool like this ?
Thanks !

Hi..
Following is the information that you need to know about how rules are used in Financial
Management. You use rules to automate the calculations of data within an application. You can
use rules for these purposes:
● Calculate data entry level amounts for a specific entity, scenario, and period.
● Prevent data entry for a specific cell in a specific entity, scenario, and period.
● Allow input at the Parent entity level.
● Calculate data that cannot be calculated through a hierarchical aggregation, such as ratios
or variance analysis.
● Perform allocations from a parent entity to a list of base entities.
● Perform complex currency conversions, calculate exchange rate differences, or perform
other calculations necessary for your consolidation.
● Define formulas to dynamically calculate accounts.
● Specify the accounts in the application that support intercompany transactions.
You can write rules in a text editor, or you can use the Financial Management Rules Editor to
create rules.
For more information on rules pls refer hfm_admin.pdf
Best Regards
Edited by: Naveen Vasa on Jul 9, 2010 10:10 AM

ASO update of attribute associations causes Data to be "converted"?

Has anyone seen the issue in 11.1.2.3(.506) where associating attributes with a dimension causes Essbase to reorganize the data (it is referred to as convert)?
e.g.
import database app.db dimensions connect as user identified by password using server rules_file 'DimFuel' on error write to '/essapp/subject/sos/logs/sosp04_dims.build_dim_sosp04_sosp04_dimopen.20150429011053.err':
OK/INFO - 1270086 - Restructuring converted [5.72103e+08] input cells and removed [0] input cells.
OK/INFO - 1270087 - Restructuring converted [32] and removed [0] aggregate views.
OK/INFO - 1007067 - Total Restructure Elapsed Time : [1944.88] seconds.
Previoiusly this process ran in 3 seconds in 11.1.2.2(.100)

I agree with everything that Tim has said. Let me elaborate some more that might be helpful:
The fact that agg views are not based on query tracking makes no difference in the analysis. Query tracking only affects WHICH views are selected. Once views are selected by whatever means they are handled in the same way. Is there a reason you think otherwise?
Let's divide the question into two parts:
1. What is a restructure and Why is a restructure needed?
2. Why must the agg views be converted
But first realize there are two possibilities concerning WHICH agg views actually exist:
a. All views might be on the primary hierarchy only. (You told Essbase to consider alternate hierarchies when creating aggregates) - let's call that the Agg_Primary option
b. Views might be based on both primary and alternate (which includes attribute) hierarchies - let's call that the Agg_Any option
All of this is is discussed in my Chapter "How ASO Works and How to Design for Performance" in the book "Developing Essbase Applications" edited by Cameron Lackpour. You will also find a discussion of the bitmap in the section of the DBAG entitled "An aggregate storage database outline cannot exceed 64 bits per dimension" (Essbase Administrators Guide Release 11.1.2.1 Chapter 62 page 934). and in a presentation I made at Kscope 20120 which you can find on ODTUG.com
1. Why a restructure? As Tim says the outline has changed and anytime the number of levels per hierarchy or the width of the hierarchy changes then the coding system used for the data changes. OK what do i mean by this? The binary system by which each piece of data in your cube is described is called the "BitMap". In actuality, this bitmap only reflects the data's position in the primary hierarchy for each dimension. The primary hierarchy for a specific dimension is not necessarily the first hierarchy seen in your outline. It is the "widest" hierarchy - the one requiring the greatest number of bits to represent all Level 0 (L0) members found in that hierarchy and each L0's full ancestry within that hierarchy.
If you read the references above you will see that the number of bits used to determine the "widest" hierarchy is a function of the number of levels and the size of the largest "family" in a hierarchy. A hierarchy of 5 levels where the largest family has 17 members will require 3 bits more than a hierarchy of 5 levels with 4 members in the family (17 requires 5 bits and 4 requires 2 bits). So you can see that any time you add more members you could be causing the size of the largest family to exceed a power of 2 boundary.
Additionally, if the primary hierarchy is NOT all inclusive - i.e. it contains all L0 members for that dimension then you have to add a sufficient number of bits to enumerate the hierarchies.
So, in summary changes to the width or the height (number of levels) will require a restructure forcing the the identifying bits on every piece of data to be updated.
In the case the OP mentions where the ONLY changes are to add attribute associations you normally would NOT expect to see a change in the bitmap due to the number of bits required. This is because attribute dimensions can never have new unique L0 members (you can not associate to something that does not exist). If you go thru the math (and realize that the bitmap for an attribute dimension does NOT have consider size of the L0 families of the primary hierarchy - or whichever Level the association is based on) you will find that there is no possible attribute dimension that can require more bits than the primary hierarchy. UNLESS you have been sloppy and you have a primary dimension with x L0 members and a very large secondary hierarchy with x-n members UNIQUE L0 members (i.e. L0 members not appearing in the primary hierarchy).
So the answer is to inspect the statistics tab before and after your addition of member associations.
Note - (and this does NOT pertain in the OP's Case) a similar situation exists if all secondary hierarchies contain ONLY members that already exist within the primary hierarchy. However, remember that the FIRST hierarchy in your outline is not necessarily the primary hierarchy. Most people however consider the first hierarchy as the de-facto primary. If one is in a hurry and adds the member to that first hierarchy but does not add it to ALL of the alternate hierarchies (one of which is the true primary), then bits will have to be added to each piece of data to enumerate the hierarchies - thus triggering a restructure.
Finally, I am relying on the OP's description of the conditions where it was stated that ONLY associations were added and that no upper level attribute members created. If upper level attribute members are added it is possible that the number of levels for the attribute dimension is changed. In this case a mini restructure would be required - one that would not change the bitmap on every data item but a change to the mapping table that relates alternate hierarchies to the primary hierarchy. Note the existence of this table and its exact structure is not acknowledged by Oracle - I (Dan Pressman) have postulated it as one possible implementation of the observed functionality.
2. Aggregate View Conversion: Each data item is tagged not only with a bitmap indicating its position within each primary hierarchy but with a "View ID". This is the number that is seen in the ASO version of the .CSC file created whenever the view definition is saved. The input data is always identified by a View ID of 0. The view ID of other views is a function of the number of levels and the bits required therefore of ALL hierarchies of ALL dimensions. Therefore any restructure will require that the View IDs of all aggregate views be translated (or converted) from the old scheme to the new scheme. Note that this is purely a translation and no aggregation is required.
Please excuse me if I post this now and add some more later on this second question - actually let me know if anyone has actually read this far and is interested.
Please note in the above whenever i have said "Each data item" I am referring to the situation where no dimension has been tagged as the "compression" dimension. If a compression dimension has been used then replace the phrase "Each data item" with the phrase "each data bundle". I will leave it to the reader to find the section of the DBAG that describes compression and data bundles.

Essbase Studio Cube Stores data as integer, drops decimals

I have an Essbase cube that I am developing in Essbase Studio 11.1.2.1. If I preview the data in Essbase Studio I can see the decimals for the number. However, when I deploy the cube the numbers are not stored in the Essbase cube with the decimal places. So for example I have a value of 106,257.58 on a certain intersection of data that I can see when I preview the data. However, when I querry the data in the cube after it is built it shows as 106,527.00. It is not rounding up, but instead just dropping the decimals.
I have also noticed that if I take a numeric field and do a math equation in the dimmension element, when I preivew the data in key bindings it also drops the decimals. But if I view the data in caption bindings the decimals show.
Is there a global setting where the numeric format is set? It almost seems like it is default to store numeric fields as integers and not with decimals. Any help is appreciated.

The first error is because you have the dimension set as stored either change it to multiple hierarchies or dynamic and it will allow shared members
The second error is because the first instance is getting tagged as the shared member. in 11.1.2 this is changed so Essbase automatically detects this issue and corrects it automatically
You are probably getting it because both your primary and secondary hierarchies are getting build intermingled
suppose you have your example
PRODUCT (Gen1)
Soda (Gen2)
123 (Gen 3)
747 (Gen 3)
Juice (Gen2)
555 (Gen 3)
747 (Gen 3) (shared member)
Water (Gen2)
111 (Gen 3)
747 (Gen 3) (shared member)
If you build this as a parent child recursive build and the order of your data file is
Parent Child
Product Soda
Product Juice
Product Water
Juice 747
Soda 747
yiou see it would add the 747 to juice first so the Soda would get shared. You would need to change it so the Soda 747 would be seen first

TBW20 Reporting and Analysis

Howdy All,
Does the second week of the BW academy course (Reporting and Analysis) cover using key figures (calculated and restricted), hierarchies, properties, that sort of stuff???
it's not on the course description but it is on the non academy BW reporting and analysis course.
Would someone who's done the course mind telling me? Basically I'm wondering whether to do the 2nd week of the academy OR the standard BW reporting and analysis course.
Thanks

It sounds like you have installed a second instance of the R&A Framework Agent. This is a known bug in 11.1.2.1 and can be resolved by following the steps in patch# 12552933.

Functional and Performance Testing in HFM, FDM, HFR

Does anyone know how to write test scripts relating to functional testing of HFM, FDM, Hyperion Financial Reporting applications including testing of HFM Business Rules.
I would very much appreciate if you give me step-by-step on how to go about achieving the project goal and how to write these scripts including any recommendation you may have.

Hi..
Following is the information that you need to know about how rules are used in Financial
Management. You use rules to automate the calculations of data within an application. You can
use rules for these purposes:
● Calculate data entry level amounts for a specific entity, scenario, and period.
● Prevent data entry for a specific cell in a specific entity, scenario, and period.
● Allow input at the Parent entity level.
● Calculate data that cannot be calculated through a hierarchical aggregation, such as ratios
or variance analysis.
● Perform allocations from a parent entity to a list of base entities.
● Perform complex currency conversions, calculate exchange rate differences, or perform
other calculations necessary for your consolidation.
● Define formulas to dynamically calculate accounts.
● Specify the accounts in the application that support intercompany transactions.
You can write rules in a text editor, or you can use the Financial Management Rules Editor to
create rules.
For more information on rules pls refer hfm_admin.pdf
Best Regards
Edited by: Naveen Vasa on Jul 9, 2010 10:10 AM

Outline Error Message

When I try to change the Hierarchy under Hierarchy Information any of the choices to stored, dynamic or hierarchies enabled in the member properties tab for a Gen1 member it gives me the following message.
Invalid Aggregate Level Usage. Primary hierarchies cannot have usage 'Consider Bottom Level Only', secondary hierarchies cannot have usage 'Consider Top Level Only' or 'Never Aggregate to Intermediate Levels'
Unable to figure out if this is an error message, if it is do I need to change anything in the hierarchy of that dimension?
Thanks for any help!

This is what I meant
SCENARIO Multiple Hierarchies Enabled <3> (Label Only)
          Actuals Stored # Default # (~)
          Forecasting Stored # Default # (~) <4> (Label Only)
               Forecast1 (~)
               Forecast2 (~)
               Forecast3 (~)
               STFCST (~) (Alias: Short Term Forecast)
          Variance Dynamic (~) <7> (Label Only)
               FTFVAR (~)
                    Forecast3 (Shared Member)
                    Forecast2 (Shared Member)
I Mean something like this
Regards
Amarnath

Error trying to set Do Not Aggregate through JAPI

Hi
API Version :11.1.2
API Version Detail :Essbase JAPI version: 11.1.2.0.0.615
I have an ASO outline with a two level dimension as follows:
[-]-Unit Stored # Default # <1> (Label Only)
L___dummy_u (+)
I want to change the Level Usage for Aggregation to 'Do Not Aggregate' because once the dimension has a full complement of children, showing data against the "Unit" member will make no sense. Using EAS it's no problem and I end up with
[-] Unit Stored # Do Not Aggregate # <1> (Label Only)
L___dummy_u (+)
But using the following JAPI method:
member.setAggregationLevelUsage(IEssMember.ESS_AGGLEVELUSAGE_NOAGGREGATION);I get:
I get:
com.essbase.api.base.EssException: Cannot set aggregate level usage. Essbase Error(1060243): Invalid Aggregate Level Usage. Primary hiearachies cannot have usage 'Consider Bottom Level Only', Secondary hierarchies cannot have usage 'Consider Top Level Only' or 'Never Aggregate to Intermediate Levels'
Does anyone know why it's possible through EAS but not the JAPI?

I assume you're passing a numerical width value and not css attributes.
I usually get this exception when I'm attempting to convert from a String to a numeric value and there is a leading or trailing space. Is there some white space in your properties file around this value?

Roles and Tasks around Essbase

Hi, Everyone,
Currently in our company our controllers are the users of Essbase and the administrators of this products as well. Unfortunately, they are facing some performance problems and other administrative problems. In the future the idea will be, IT department should take over some of the tasks from Controllers.
My question is, what are the tasks for ITs and what can be done by controllers? I can think of these tasks:
System upgrade
Server Performance
System Performance
System administration
Application configuration
Database configuration
Maybe further details, CALC scripts, automatic calculation etc.,
I am not familiar with Essbase at all. Could anyone tell me what the situation looks like in your company? Or, what is your suggestion?
Thanks and looking forward to your replay.
Linda

I Agree with this, of course.
The IT department is there to run the "process", while the business units have a functional perspective. This is not as clean a division within Essbase as with traditional relational databases, but it's getting closer all the time.
Things like automation, data transformation/loading/calculations and such are more of an IT thing than a functional unit thing. Same with backups, dissaster recovery, and such.
Where I have a slightly different perspective is on the outline maintenance -- I believe the IT group should handle the outline management and the functional unit should handle the hierarchy definition itself. For instance, while finance and accounting dictates the account and organizational hierarchies, IT uses the tools and techniques to transfer this into the database structures. The reason for this separation is fairly clear in my mind, and is based on the distinction between business knowledge and technical knowledge (both sides need a bit of both, but each maintains their respective areas of expertise). I wouldn't expect finance or accounting to determine which members can/should be dynamically calculated, or which hierarchies should be shared vs. stored, for instance.
The biggest risk of not using both skill sets is that you just let the functional groups do everything, and end up with a loss of infrastructure support (like invalid or insufficient backup and D/R support). The other side also exists, giving it all to IT runs the risk of the functional units becoming disengaged with the management of hierarchies or confusion on data content/meaning. I have seen both conditions exist, and it's more common than it should be.
That said, there is a lot of room for flexibility in terms of who does what, and allowing the functional units to manage things directly is not necessarilly a bad thing. It's just better to have the subject matter experts handling the tasks they do best. IT is better at infrastructure support, and the overhead associated with it is better off not taking up the business units' time.

Combines Hierarchy

Hi All,
I have recuirement to change the hierarchy vakue at run time to match it with the other source system. We currently load cost center hierarchy from two source system and combine them now I need to change the cost center element value at extraction time based on my other system hierarchy.
I know we can use user exit to change the hierarchy content but I am not sure if thats the process to do it or is that a valid thing to do?
Regards
SS

If you rewrite the cube in Tabular, usually it's better using a different approach in calculation. By its nature, DAX always performs leaf-level calculations. If you need to change calculations at different hierarchical levels, you should consider doing
that in measures by using iterations. For example, if I have to compute the average at monthly level, and I have to sum the data at the month level, I'll write something like:
AVERAGEX ( VALUES ( 'Date'[YearMonth] ), CALCULATE ( SUM ( Sales[Amount] ) ) )
If you just try to translate MDX in DAX, you might create more complex calculations that are useless because no longer get any advantage by the hierarchical nature of cache system you have in Multidimensional.
Marco Russo http://www.sqlbi.com http://www.powerpivotworkshop.com http://sqlblog.com/blogs/marco_russo

How to prevent BPC from automated calculating for hierarchies / nodes?

Hi experts,
I am looking for a practicable way to prevent the system from automated calculating for hierarchies, and especially for nodes within hierarchies?
Let's say, I have ENTITIES (AS A HIERACHY) in rows and ACCOUNTS in COLUMNS. Now I want the system to block adding up the values for one specific account on node XY. Instead of the sum of all base member entities, the cell for account XY should be left empty.
Is there a practicable way to deal with this?

Hi Stefan,
you can prevent the system to calculate a node by editing the Formula Property in the Dimension.
You can insert 0 or null to the Formula field for the specific element.
But in this case the values from your leaf elements lying under your node wont be calculated even in higher hierarchy nodes.
For ex.: with the following structure
-A
---A1
A11
A12
---B1
B11
B12
If you set A1 to 0, the top node A will only be calculated by values of B1
Regards
Jörg

The item Hierarchical Context Menu does not support pre-calculation

Hello,
Trying to download pre-calculated web templates via RepAgent, using the Hierarchical Context Menu feature within the template (populated via control query with Hierarchy) the system returned the following message upon file download:
"The item Hierarchical Context Menu does not support pre-calculation"
As a result the Hierarchical Context Menu is not displayed on the downloaded html-files. Navigation not possible.
Could not find any constraints documented in the online help, at this point.
Question: is there something missing on our setup or is this really out of scope for precalculation with navigation?
Any other experiences on that or shall we open OSS-message?
Best regards,
Markus
(We are on BW3.1)

Hi,
we have the same problem. Does anybody have any hint or workaround? Is there a solution for this in 3.5 or any upcoming version.
Any input is appreciated.
Thanks,
Stefan

Calculation in Secondary Hierarchies

Similar Messages

Maybe you are looking for