Rollup calculations in Account hierarchy (parent-child type)

Hi,
I want to create a parent-child relationship type Account hierarchy using Universe. The hierarchy has to support different set of calculations for roll ups action for different branches in the same level.
Eg.
      Balance Sheet
          (+)Assets
          (-)Liabilities and Owners Equity
      Net Income
       (+)Operating Profit
       (+)Other Income and Expenses
       (-)Taxes
Balance Sheet = Assets -Liabilities and Owners Equity
Net Income = Operating Profit + Other Income and Expenses - Taxes
Regards, Sujeev

Measures automatically roll up.
Whether you define your measure with an aggregate or not, if the projection is set to Sum, it will roll up.
Measures that are to be summed should have Sum() wrapped round them at the universe level though.
What you may have is a lot of positive values in your database and no negatives.
If that's the case, you will need to use a case statement to determine the sign of the value.
E.g.
Sum(CASE WHEN Type='Asset' THEN table.value WHEN Type='Liability' THEN -1*table.value ELSE 0 END)

Similar Messages

OBIEE11g - Hierarchy parent-child with a factable measure(poor performance)

Hi
I have a star model with a hierarchy parent child, joined to the fact table.
Creating a new analysis, and adding the hierarchy column with any other field from any dimension (on selected columns or filters) all works fine, and the hierarchy displays every level very fast.
But adding a measure from the fact table, the hierarchy performance drops dramatically and I have to wait 20-30 seconds to see each new level displayed.
Taking a look at the SQL launched, seems to be all right:
The measure is a COUNT(DISTINCT factable.field) and the group by is done by Parent,Child fields in the hierarchy table.
Is there any other way to set up this hierarchy? Why the measures are reducing the performance?
Any comment will be helpful.
Thanks in advance.

Try these
Use Oracle Enterprise Manager (EM) URL to monitor end to end OBIEE real time performance: http://<server>:7001/em
In Oracle Business Intelligence 11g, the perfmon URL is still valid to use i.e. http://<server>:9704/analytics/saw.dll?Perfmon
Check these
http://www.rittmanmead.com/files/biforum2012/ranka_performance.pdf
http://docs.oracle.com/cd/E17904_01/web.1111/e13814/jvm_tuning.htm
https://blogs.oracle.com/pa/entry/obiee_ibm_jdk_tuning_for
Support note OBIEE 11g Infrastructure Performance Tuning Guide Doc ID 1333049.1
If helps mark and update back :)

Hierarchy Parent Child Relation Storage

Hello All,
            I need to display hier. info in parent-child format. Any ideas on how to store parent child relationship in an ODS....I can view this format in the infoobject display screen for hierarchy...but cannot get this format to display..
EX: Parent - child1,2,3,4
      child1- child 1-1,1-2,...
      child2 - child 2-1,2-2...
thanks

Spanyal,
You will have to write a program to store this information in an ODS object. You will have to use /BIC/h<IO> Table to read the data and update a custom table. You will have to do some basic checks like business content or not, plan version, time dependency etc in the entry screen and then the program can read the hierarchy table in the format you want.
I am not aware of any simpler way to populate hierarchy data into an ods object in a meaningful fashion.
-Saket

Value based hierarchy (parent-child)

Does anybody have any experience in modeling a parent-child dimension ( value based hierarchy instead of level based ) in OBIEE?
Swapan.

I've done some work with this, and it hasn't been easy going. There is no built-in ability to form a hierarchy of measure columns, at least nothing that can be predefined as the drill for a fact column. For example: I have 220 details of expense that have an exact arrangement with 5 levels and subtotals. Besides the expense detail there are say 4 dimensions, so the expense detail would be the 5th dimension. I have both arrangements in my rpd: 4D and 5D. They can be used together or separately. The 4D basically has 1000's of measures and there is no relationship between them besides the display arrangement in Answers. The 5D has a 5 column dimension that can drill the expense column from Total_Expense down to the 220 rows of detail expense.

PDW : Hierarchy parent/child

Hi,
I'm working with a PDW Appliance as source and destination.
I need to create a parent/child hierarchy.
My child surrogate key is generated inside my dataflow, then I'm doing the initial loading of all my data minus the surrogate key for the parent column.
I'd like to avoid to run update statements against my destination table (because of the replication) and/or have to create temp tables.
I thought about keeping in memory (Recordset Destination) all my dataset and then doing the look up in a script component before doing the final insert in append mode but the performance are awful.
Any idea ?
Thx for your help.
Bertrandr

Thanks to have remind me about the CacheTransform component :)
The dataset is about 200 000 rows.
I have also tested another option.
Instead of performing an initial load and then look up
I'm doing a multicast pointing to 2 RecordSet Destination.
Both are the same except it's 2 differents object variables.
Then in another dataflow I read both dataset and use a MergeJoin on the business key to get my parent surrogate key.
It works but I need to compare performances with your solution.
Thanks a lot !
Bertrandr

Calculating value based on parent/child relations for a column..

Hi Friends,
I have a requirement thus,
sample table, parts,
ppart cpart qty
990 1234 200
100 100_1 150
100 100_2 2
100_1 120 100
100_1 121 200
100_2 130 50
where qty is a number and the rest are varchar fields. Here the ppart 100 is a parent value for cpart values 100_1 and 100_2. So, I need to multiply the qty value for a child with the parent's qty values. The final result would look like,
ppart cpart qty
990 1234 200
100 100_1 150
100 100_2 2
100_1 120 15000
100_1 121 30000
100_2 130 100
I have only a basic understanding of SQL but I couldnt figure out a way for this. My best try was to join the table with itself and equate the ppart and cpart columns to retrieve the qty. However, the actual table has about 50 million records and I guess my idea is not going to please my DBA! I would appreciate if you could suggest better ideas.
Thanks.

Hi,
you forgot nvl()
SQL> with parts as (select '990' ppart, '1234' cpart, 200 qty from dual union all
2                select '100' , '100_1', 150 from dual union all
3                select '100' , '100_2', 2   from dual union all
4                select '100_1', '120' , 100 from dual union all
5                select '100_1', '121' , 200 from dual union all
6                select '100_2', '130' , 50 from dual)
7 select p.ppart parent_part, c.ppart child_part, p.qty parent_qty, p.qty * c.qty child_quantity
8 from   parts c
9 left join parts p on c.ppart = p.cpart
10 /
PAREN CHILD PARENT_QTY CHILD_QUANTITY
100   100_1        150          30000
100   100_1        150          15000
100   100_2          2            100
      990
      100
      100
6 rows selected.
SQL> with parts as (select '990' ppart, '1234' cpart, 200 qty from dual union all
2                select '100' , '100_1', 150 from dual union all
3                select '100' , '100_2', 2   from dual union all
4                select '100_1', '120' , 100 from dual union all
5                select '100_1', '121' , 200 from dual union all
6                select '100_2', '130' , 50 from dual)
7 select p.ppart,p.cpart, p.qty * nvl(c.qty,1) qty
8 from   parts p,parts c
9 where p.ppart = c.cpart(+)
10 /
PPART CPART        QTY
100_1 121        30000
100_1 120        15000
100_2 130          100
990   1234         200
100   100_2          2
100   100_1        150
6 rows selected.

Hierarchy (Parent-Child) drill-down report

Good morning,
I use Crystal Reports v12.3.0.601 & backend is Oracle - And I am a beginner.
Attached JPG details my question/ problem - Thank you for your time.
Regards,
Sridhar Lam

Hi Abilash,
I tried what you suggested...it returns the entire tree stucture. (returns ALL folder structure with indent....runs into hundreds of pages)
The problem I face is that...for a specific folder 'D7'...I need the structure....
(possibly a drill-down or drill-up structure or both if it is in the middle of the tree structure)
Let me explain....
My question is not that simple:
1. If I am given a FOLDER_RSN = D7 (could be any...but I am picking one as required by my business here)
2. Objective is to display drill-down/ drill-up/ or both structure of D7
Scenarios:
a. D7 could be a top-node parent
b. D7 could be a sub-parent under top-node parent.
c. D7 could be a sub-parent under another sub-parent
I would prefer a SQL statement referring the image...makes it easy to solve !!!
Thank you,
Regards,
Sridhar Lam

Parent Child Hierarchy for Type 2

I have read the articles on Parent Child hierarchy setup in OBIEE 11g, however, most are based on what seems to be a current snapshot of the Employee-Manager relationship. Has anyone tried to build out a Parent-Child hierarchy/table off a Type 2 dimension. Being able to navigate what the hierarchy may have been on a specific date.
I would welcome any feedback, thanks.

Hi,
Thanks for the reply, I'm actually using snapshots. But even with the Type 2 Dim I don't think it will work.
When OBIEE generates the very first sql against the Parent-Child table the fact table is not included in the query. It seems to create 2 queries - one to find the top level parent (ancestor key is null) and then one to find all the leaf nodes.
It does not have any join to the fact table when it does this. So if you have multiple rows in the table (with date stamps) for a single row (person in this case) - it picks up both rows. Therefore, when you have a person who was, say, promoted to manager, and WAS a leaf node, and is now a manager, they show up in the leaf query and don't display in the hierarchy as a manager.
Once it has the leaf nodes and it joins to the fact table everything works (ie the surrogate key join).
I'm trying to figure out if there is any way to influence those initial queries against the parent-child table.
Hopefully that made sense.
Thanks,
Tori

Do the custom rollup member formulas work recursively for parent child dimension?

Hi
We have custom rollup set up for Account dimension which is parent child.
It seems to work fine when the custom member formula refers to a base account member i.e. if the formula for MemberKey4 is (MemberKey1 + MemberKey2) then it shows the sum of the underlying members 1 and 2.
But if the formula for MemberKey10 is (MemberKey3 + MemberKey4) then it should evaluate the value for MemberKey4 first and then add to it value for MemberKey3 to come up with final number for MemberKey10.
Do the custom rollup work fine with the recursive calculations? Is this recursion limited to some level?
Thanks
Shailesh

Hi Jorg,
Thanks for your input.
Actually the hierarhcy is more determined by the parent child relationship. So we cannot move the members as per the formula. And further the formulas are not always additive, there are divisions and multiplactions happening also.
Further the calculated members (account members) are used in different places, the usage level of calculated members could be 3 in some cases i.e. MemberKey15 = (calculated using MemberKey10 = (calculated using MemberKey7 = (Calculated using MemberKey4 = (calculated using base members)))). Now inserting the base members in place of a calcuated member becomes more of string manipulation.
And on the top of above complexity, the formulas are not static and they are more user defined, they may change between time periods, which forces us to write a dynamic procedure to translate the 'business formula' into SSAS formula. We expect the custom rollup to work as expected (i.e. if the formula contains a calculation involving the calculated member, it should resolve that first and so on) and we have written generic procedure to replace the Account Code in the 'business formula' with the accont key value with the account hierarchy char string.
In the link http://doc.ddart.net/mssql/sql2000/html/olapdmad/agmdxadvanced_6jn7.htm for AS2000, it talks about the calculation pass deapth, it says:
.......If a cube has custom rollup formulas or custom rollup operators, a second calculation pass is performed to handle the computations needed to calculate these features.......
Now from the above, it is obvious that the OLAP engine will automatically go into recursion if the formula contains a cacluated member and it knows that the calculated member has to be resolved first before calculating the final formula result. The above article also talks about 'Calculation Pass Number' property in the AdvanceCube Editor (AS2000), which can be set to the value depending on the expected number of passes required in a given scenario. I don't find such an equivalent peoperty for SSAS 2005.
Would anybody please throw some more ideas / insights on this issue?
Jorg, thanks again for your input...
Shailesh

Parent Child Hierarchy in OBIEE 11G

Hi All,
I am working on the parent child hierarchy in OBIEE 11g Source ESSBASE ..followed some of the blogs.
http://www.rittmanmead.com/2010/07/obiee-11gr1-enhancements-to-essbase-support/
I followed the following steps.
1.Imported the Cubes from ESSBASE.
2.Selected Accounts Hirearchy and changed the Hierarchy type to Value.
3.Dragged the subject area to BMM and to Presentation.
4.Now when i checked the Account Hierarchy from in the dashboard its not drilling down.
If i change the Hierarchy type to Unbalanced ...then the Account hiearchy is working fine.
Is there is any settings or process i have to follow..inorder to implement the Value based Hierarchy in OBIEE 11G source ESSBASE.
Thanks

So basically this means that if I build a parent child hierarchy on table A having the stucture like
--David (Manager)
-----James (Off1)
--------Bill (Off2)
and in my sales fact table for let's say today, I have only rows for Bill (Off2) because he is the only officer who did the sales today. Now when I will join my fact table to parent child hierarchy table A I will NOT get any data ? because there is no James who is the parent of Bill. So obiee need to have parent pulled off in the data (ANCESTOR) to be able to roll up the child.(IS_LEAF = 1)
I testes this and if my data only contains only rows for Bill (or I limit on ROLE = Off2) then it won't show the hierarchy. The query which OBIEE fires is to look for either ANCESTOR_KEY = NULL OR (DISTANCE = 1 AND ANCESTOR KEY IN (Bill). Therefore it doesn't I am wondering then what is the use of builiding the parent child hierarchy when we need to pull in all the ancestors (like in this case James for bill and David for james) because in real scenarios there can be cases wherein we would want to filter the data based on other dimensions to which the parent child hierarchy joins ?

Parent Child Hierarchy causes numbers to be different

Hello,
We have a parent child hierarchy in our chart of account dimensions. When the hierarchy is included in an analysis, the numbers are correct. If the hierarchy is not included in the analysis and a column from the dimension with the hierarchy is included, the numbers are very different. They are overstated by a large amount.
For Example, I have two analysis:
-In the first analysis the hierarchy is included and the grand total is 2,383,080,784.
-The second analysis has simply excluded the hierarchy from the analysis and the total shoots all the way up to 6,901,729,527.
I have screen shots but don't know how to include them in this kind of a post.
Has anybody else seen such behavior? This seems like it would be a big deal so either we are doing something wrong or this is a bug that needs fixed.
We are on 11.1.1.6
Thanks in advance,
Brian

Hi,
Thanks for the reply, I'm actually using snapshots. But even with the Type 2 Dim I don't think it will work.
When OBIEE generates the very first sql against the Parent-Child table the fact table is not included in the query. It seems to create 2 queries - one to find the top level parent (ancestor key is null) and then one to find all the leaf nodes.
It does not have any join to the fact table when it does this. So if you have multiple rows in the table (with date stamps) for a single row (person in this case) - it picks up both rows. Therefore, when you have a person who was, say, promoted to manager, and WAS a leaf node, and is now a manager, they show up in the leaf query and don't display in the hierarchy as a manager.
Once it has the leaf nodes and it joins to the fact table everything works (ie the surrogate key join).
I'm trying to figure out if there is any way to influence those initial queries against the parent-child table.
Hopefully that made sense.
Thanks,
Tori

Problem creating standard ECC Parent-Child Hierarchy in HANA

Hi all -
I've been trying to get a hierarchy to work on the front end of a stand alone HANA system using profit center hierarchy data from SETLEAF / SETNODE tables from ECC. Here is how my test hierarchy looks:
Following another post I found around here, I created an attribute view and filtered SETNAME to 'TST_HANA'.
The resulting data when connected to my attribute view caused an error that there was no root node, so I manually inserted the last row shown here (where PCA_PARENT = SETNAME and PCA_CHILD = SUBSETNAME):
Finally, I created my parent-child hierarchy in the attribute view and connected that view to my data foundation in the analytic view via left-outer join between Profit Center and VALFROM. However, when I go to connect to my view via MDX in excel, I get the following message:
"Hierarchy create error: Multiple parents not allowed for hierarchy node TST_ND1" Clearly from the data, there aren't multiple parents for TST_ND1. It's already a pain that to use a standard hierarchy I have to manually insert a root node, but that doesn't even seem to fix the problem.
Can anyone suggest how to fix this to get a standard profit center hierarchy working?
Thank you!
AZ

Hi,
According to me, Hierarchy level will work fine in ms excel for all analytical, calculation view using MDX Provider..
Do you have any composite primary key or composite foreign key in the tables....
r u getting correct level hierarchy output in Hana studio... plz check with all types of permutation possible.if u r getting correct output in analytical view w.r.t hana but fails to get in Ms excel..
please create Calculation view of that.. & then check the output in ms-excel..
Thanks,

Parent Child Hierarchy Issue in OBIEE 11g

Hi All,
I am in OBIEE 11G v6. I have a sales fact table where the grain is one sale. So I have one row for every sale done.
Now I have a ragged employee hierarchy like this with David at the root node.
David >>Richard>>Sean
David >>James
Also, I have a role dimension which gives me what role each employee has performed on a sale. Only one employee can be associated with one sale. This is the way Roles have been asssigned
David = Manager
Richard = Off1
Sean = Off2
James = Off2
Both Sean and James can have same Roles. Now I have created a parent child hierarchy for my employee dimension and the closure table. Defined the member key, ancestor key relationship in the parent child setting etc.
Now in the report when I pull the parent child hierarchy and the sales_amount in the report, it comes out perfect with all the ragged hierarchy resolved. But the issue comes when I try to limit the report on Role = Off2. It gives me an error saying " The layout of this view combined with the data, selection , drills resulted in no data. Undo drill and view prompt values". Basically what i want is to be able to select any role type and then my hierarchy should be adjusted to show me that data. Like when I select Off2, I want to see David at the Top level and Sean and James under him because they are both Off 2 and David is their manager.
Is that possbile? Also, am I getting this error because when I select Off2 though it gets Sean and James but since David is not Off2, I don't get the data?
I hope I was able to explain the issue, any help on this would be greatly appreciated.
Thanks
Ronny

So basically this means that if I build a parent child hierarchy on table A having the stucture like
--David (Manager)
-----James (Off1)
--------Bill (Off2)
and in my sales fact table for let's say today, I have only rows for Bill (Off2) because he is the only officer who did the sales today. Now when I will join my fact table to parent child hierarchy table A I will NOT get any data ? because there is no James who is the parent of Bill. So obiee need to have parent pulled off in the data (ANCESTOR) to be able to roll up the child.(IS_LEAF = 1)
I testes this and if my data only contains only rows for Bill (or I limit on ROLE = Off2) then it won't show the hierarchy. The query which OBIEE fires is to look for either ANCESTOR_KEY = NULL OR (DISTANCE = 1 AND ANCESTOR KEY IN (Bill). Therefore it doesn't I am wondering then what is the use of builiding the parent child hierarchy when we need to pull in all the ancestors (like in this case James for bill and David for james) because in real scenarios there can be cases wherein we would want to filter the data based on other dimensions to which the parent child hierarchy joins ?

Parent/Child Master Data Type

I recently created a new master data type in my model, which included one attribute with the 'parent' check box checked - to signify that it was to be used as the parent.
Upon activating the master data type - the system auto generated several other attributes within the master data type. My question is, what is the purpose of these additional attributes and how are they to be used?
Before Activation:
Attribute
Description
Notes
ID
ID
<< marked as key and as required
DESCR
Description
<< no special check boxes checked
PID
Parent ID
<< marked with parent check box
After activation:
Attribute
Description
Notes
ID
ID
<< marked as key and as required
DESCR
Description
<< no special check boxes checked
PID
Parent ID
<< marked with parent check box
IDA
Ancestor: ID
<< auto added after activation
IDL
Level: ID
<< auto added after activation
IDLA
Ancestor: Level: ID
<< auto added after activation
IDPTH
Path: ID
<< auto added after activation
IDPTHA
Ancestor: Path: ID
<< auto added after activation
DEACRA
Ancestor: Description
<< auto added after activation
PIDA
Ancestor: Parent ID
<< auto added after activation

https://share.sap.com/a:r2l29c/MyAttachments/38b00c31-a7f4-404c-8247-1a99ef4b0509/
Hey JJ,
The purpose of these attributes is for parent-child hierachy relationship.
In addition to above mentioned attributes, you should also notice (via HANA studio), that another Planning object gets generated automatically. The new planning object should be the name of your parent-child object plus "_ANC" prefix at the end.
If you take a look at this planning object, you will notice that the object contains all the generated attributes (your attriubute plus "A" prefix at the end) in the definition.
Once you load data into your parent-child hiearchy object the "_ANC" object will automatically get populated with parent-child node relationship.
"A-prefix" attriubutes essentially represents the attributes of ancestor in this case.
In addition, in order to do Ancestor rolllup in your calculation you will also need to create an ancestor planning level which contains all the attriubutes of your base planning level as well as these "A-Prefix" attributes.
Please take a look at the document we created for "How to configure Parent-Child Hiearchy" from the share link
It has more detailed information.
Thanks.
Daniel.

Parent child hierarchy and measure using lookup

Hi,
I'm using OBIEE 11.1.1.5 and I have an issue with a parent child hierarchy, which is setup like case 4 in this example . When I create a simple analysis using the hierarchy and a simple measure, it works fine. But when I try to use a calculated measure using a lookup formula, I get the following error:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 46036] Internal Assertion: Condition pTableRef->GetLeftTable() && pTableRef->GetLeftTable()->IsTableReference(), file server/Query/Optimizer/ServiceInterfaceMgr/Src/SQOIDriveJoinGenerator.cpp, line 568. (HY000)
Does anyone know how to get past this error?
Thanks,
Mihai

Hi,
I'm using OBIEE 11.1.1.5 and I have an issue with a parent child hierarchy, which is setup like case 4 in this example . When I create a simple analysis using the hierarchy and a simple measure, it works fine. But when I try to use a calculated measure using a lookup formula, I get the following error:
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 46036] Internal Assertion: Condition pTableRef->GetLeftTable() && pTableRef->GetLeftTable()->IsTableReference(), file server/Query/Optimizer/ServiceInterfaceMgr/Src/SQOIDriveJoinGenerator.cpp, line 568. (HY000)
Does anyone know how to get past this error?
Thanks,
Mihai

Rollup calculations in Account hierarchy (parent-child type)

Similar Messages

Maybe you are looking for