Analytics | Oracle EPM | Advanced Analytics | Many More...

It has come out of surprise that ASO doesn't have a Boolean function similar to @ISIDESC function in BSO for writing MDX formulas. But, how can I achieve it? There are two different ways of doing it. Using ISANCESTOR Function Using CONTAINS function with a combination of Descendants function [1] Using ISANCESTOR Function [ IsAncestor (Member1, Member2) ] As the name says, this function will check if Member1 is ancestor of Member2 . Let's take a simple example IsAncestor ([Market].CurrentMember, [Florida]) -    This will check if the CurrentMember in the retrieve is Ancestor for [Florida] . Now, If we switch the member1, member2 we will be able to achieve the @ISDESC functionality. IsAncestor ([Florida], [Market].CurrentMember) - This will check if [Florida] is ancestor of your CurrentMember and this condition will satisfy for all the members that fall under [Florida] . Using CONTAINS function with a combination of Descendants Function [ CONTAINS (Memb

TWOPASS... Why do i need TWO PASSES for a calculation to get it right? One of my colleague who was new to Essbase asked me.. What is TWOPASS?  As usual, I took the standard example of % Calculation and said that  "When you are performing % calculation using a member formula, you have to calculate again at Total level than to aggregate the percentages from child to parent. In such case, you have to re-calculate again at total level and in order for the essbase to do this, we tag the member as TWOPASS so that it will calculate again in the End. Below is the example i gave Calculation Without TWOPASS                  Jan        Feb      Mar      Q1 Sales        1000      1200    800      3000      Profit          20          50      20        90 Profit %      50          24     40        114 Profit % has to be re-calculated again at Q1 to provide the correct results Calculation With TWOPASS                   Jan        Feb      Mar      Q1

In the Last series of Posts Here (Part I) and Here (Part II), we have talked about the basics of Variance Reporting (Part I) and Variance Reporting Across Time Periods (Part II).  In this post, we will talk about variance reporting Across Scenarios (Actual, Plan, Forecast). Most of the Organizations who have been using Oracle EPM set of tools as part of their financial process would have the below process setup Fetch the Actuals (transaction level data) from different source systems for their reporting & analysis. Most of the actual data comes from oracle GL, Oracle EBS, PeopleSoft or any type of an OLTP system or it could even come from flatfiles or excel or could be any readable format Have a Planning application where users can input their PLAN data. Most of the organizations have long-term goals and target and plan to achieve it. What are the steps that are involved to achieve their goals and targets is part of their planning. I am not going to talk in detail