Unbalanced hierarchies in OBIEE+

Hi everyone,
We're starting to research and learn OBIEE+ in an effort to see if it can compliment what we're currently doing with the Hyperion toolset and the first stumbling block that I've encountered is with unbalanced (ragged) hierarchies. Does OBIEE+ natively support building a business model with unbalanced hierarchies? My data model is basically a star schema and my dimensions are stored in parent / child relationship tables rather than generational tables. Second question is if there is any native functionality within the product to handle parent / child relationship tables.
Thanks!

do search - There're few excellent blog posts describing in detail how to implement rugged hierarchies...
www.rittmanmead.com/2007/06/21/obiee-data-modeling-tips-3-ragged-hierarchies/
this one to get you started
Message was edited by:
wildmight

Similar Messages

Hierarchies in obiee

Hi. I am new to this environment.
Can anybody help me out in "How many types of hierarchies are there in obiee?"

There are two types of hierarachies.They are
Gerneral hie like year->month->Weak->day
Ragged hierac follow this link or multiple hie for a single dimension
http://www.rittmanmead.com/2008/08/27/ragged-hierarchy-handling-in-obiee
Venkat V

Modelling Multiple Hierarchies in OBIEE 11g

Hi all,
I have a Product dimension:
Product Lv1 (the highest) to Product Lv4 (the lowest). Each has Code and Name columns. So in total, I have 8 columns for Product.
What I need is from Answers, if I drill on one of the Code column, I want the drill always on the Code columns (the 1st path below). But if I drill on one of the Name column, I want the drill always on the Name columns (the 2nd path below).
The 2 drill down paths that I need:
1st path:
Product Lv1 Code --> Product Lv2 Code --> Product Lv3 Code --> Product Lv4 Code
2nd path:
Product Lv1 Name --> Product Lv2 Name --> Product Lv3 Name --> Product Lv4 Name
Any advise on how to do this in the business model layer of the RPD? Thanks a lot!

Hi Stewart,
If I understand the question correctly you should be able to create a logical dimension to solve the problem. With a top level called total with the grand total property checked. Then create two child levels one for the code path and the other for the name path.
Total
+ Product level 1 code
+ Product level2 code
+ etc
+ Product level 1 name
+ Product level 2 name
+ etc
This should define the different behaviour you describe.
Regards,
James
Edited by: user13059716 on May 23, 2012 3:44 PM

Performance issue with two unbanalnced hierarchies in a single report

Hi All
We are facing the performance issue with one of the report which houses two unbalanced hierarchies (having 18 levels) - skipped & ragged. Basically its a part of OBIAPPS financila analytics .
The query is below :
Could anyone let me know how to improve the performane. Any parameter that should be looked at while using unbalanced hierarchies.
WITH SAWITH0
AS ( SELECT SUM (T91707.OTHER_LOC_AMT) AS c1,
MAX (T314768.HIER2_CODE) AS c2,
MAX (T314768.HIER3_CODE) AS c3,
MAX (T314768.HIER4_CODE) AS c4,
MAX (T314768.HIER5_CODE) AS c5,
MAX (T314768.HIER6_CODE) AS c6,
MAX (T314768.HIER7_CODE) AS c7,
MAX (T314768.HIER8_CODE) AS c8,
MAX (T314768.HIER9_CODE) AS c9,
MAX (T314768.HIER10_CODE) AS c10,
MAX (T314768.HIER11_CODE) AS c11,
MAX (T314768.HIER12_CODE) AS c12,
MAX (T314768.HIER13_CODE) AS c13,
MAX (T314768.HIER14_CODE) AS c14,
MAX (T314768.HIER15_CODE) AS c15,
MAX (T314768.HIER16_CODE) AS c16,
MAX (T314768.HIER17_CODE) AS c17,
MAX (T314768.HIER18_CODE) AS c18,
MAX (T314768.HIER19_CODE) AS c19,
MAX (T314768.HIER20_CODE) AS c20,
T314768.HIER1_NAME AS c21,
T314768.HIER1_CODE AS c22,
T314914.HIER1_NAME AS c24,
T314914.HIER10_NAME AS c25,
T314914.HIER11_NAME AS c26,
T314914.HIER12_NAME AS c27,
T314914.HIER13_NAME AS c28,
T314914.HIER14_NAME AS c29,
T314914.HIER15_NAME AS c30,
T314914.HIER16_NAME AS c31,
T314914.HIER17_NAME AS c32,
T314914.HIER18_NAME AS c33,
T314914.HIER19_NAME AS c34,
T314914.HIER2_NAME AS c35,
T314914.HIER20_NAME AS c36,
T314914.HIER3_NAME AS c37,
T314914.HIER4_NAME AS c38,
T314914.HIER5_NAME AS c39,
T314914.HIER6_NAME AS c40,
T314914.HIER7_NAME AS c41,
T314914.HIER8_NAME AS c42,
T314914.HIER9_NAME AS c43,
T314914.HIER20_CODE AS c44,
T314914.HIER1_CODE AS c45,
T314914.HIER10_CODE AS c46,
T314914.HIER11_CODE AS c47,
T314914.HIER12_CODE AS c48,
T314914.HIER13_CODE AS c49,
T314914.HIER14_CODE AS c50,
T314914.HIER15_CODE AS c51,
T314914.HIER16_CODE AS c52,
T314914.HIER17_CODE AS c53,
T314914.HIER18_CODE AS c54,
T314914.HIER19_CODE AS c55,
T314914.HIER2_CODE AS c56,
T314914.HIER3_CODE AS c57,
T314914.HIER4_CODE AS c58,
T314914.HIER5_CODE AS c59,
T314914.HIER6_CODE AS c60,
T314914.HIER7_CODE AS c61,
T314914.HIER8_CODE AS c62,
T314914.HIER9_CODE AS c63
FROM W_HIERARCHY_D T314768 /* Dim_W_HIERARCHY_D_Segment11 */
W_GL_SEGMENT_D T315677 /* Dim_W_GL_SEGMENT_D_Segment11 */
W_HIERARCHY_D T314914 /* Dim_W_HIERARCHY_D_Segment13 */
W_GL_SEGMENT_D T315731 /* Dim_W_GL_SEGMENT_D_Segment13 */
W_GL_ACCOUNT_D T91397 /* Dim_W_GL_ACCOUNT_D */
W_GL_OTHER_F T91707 /* Fact_W_GL_OTHER_F */
WHERE ( T91397.ROW_WID = T91707.GL_ACCOUNT_WID
AND T91397.ACCOUNT_SEG11_CODE = T315677.SEGMENT_VAL_CODE
AND T91397.ACCOUNT_SEG13_CODE = T315731.SEGMENT_VAL_CODE
AND T91397.ACCOUNT_SEG11_ATTRIB = T315677.SEGMENT_LOV_ID
AND T91397.ACCOUNT_SEG13_ATTRIB = T315731.SEGMENT_LOV_ID
AND T314768.HIER_CODE = T315677.SEGMENT_LOV_ID
AND T314768.HIER_NAME = T315677.SEGMENT_LOV_NAME
AND T314768.HIERARCHY_ID = T315677.SEGMENT_VAL_CODE
AND T314914.HIER_CODE = T315731.SEGMENT_LOV_ID
AND T314914.HIER_NAME = T315731.SEGMENT_LOV_NAME
AND T314914.HIERARCHY_ID = T315731.SEGMENT_VAL_CODE
AND T315677.SEGMENT_LOV_NAME =
'Responsibility_Centre_Functional'
AND T315677.SEGMENT_LOV_ID = 1000163
AND T315731.SEGMENT_LOV_NAME = 'Account_Master'
AND T315731.SEGMENT_LOV_ID = 1000165
AND ( T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER11_CODE IS NULL)
AND (T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER12_CODE IS NULL)
AND ( T314914.HIER8_CODE IN ('S000005160')
OR T314914.HIER9_CODE IN ('S000000187')
OR T314914.HIER10_CODE IN ('S526003000')
OR T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER8_CODE IS NULL)
AND ( T314914.HIER9_CODE IN ('S000000187')
OR T314914.HIER10_CODE IN ('S526003000')
OR T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER9_CODE IS NULL)
AND ( T314914.HIER10_CODE IN ('S526003000')
OR T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER10_CODE IS NULL)
AND ( T314914.HIER1_CODE IN ('ALL_LI')
OR T314914.HIER2_CODE IN ('S000000001')
OR T314914.HIER3_CODE IN ('S000005150')
OR T314914.HIER4_CODE IN ('S000005151')
OR T314914.HIER5_CODE IN ('S000005153')
OR T314914.HIER6_CODE IN ('S000005154')
OR T314914.HIER7_CODE IN ('S000005062')
OR T314914.HIER8_CODE IN ('S000005160')
OR T314914.HIER9_CODE IN ('S000000187')
OR T314914.HIER10_CODE IN ('S526003000')
OR T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022'))
AND ( T314914.HIER2_CODE IN ('S000000001')
OR T314914.HIER3_CODE IN ('S000005150')
OR T314914.HIER4_CODE IN ('S000005151')
OR T314914.HIER5_CODE IN ('S000005153')
OR T314914.HIER6_CODE IN ('S000005154')
OR T314914.HIER7_CODE IN ('S000005062')
OR T314914.HIER8_CODE IN ('S000005160')
OR T314914.HIER9_CODE IN ('S000000187')
OR T314914.HIER10_CODE IN ('S526003000')
OR T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER2_CODE IS NULL)
AND ( T314914.HIER3_CODE IN ('S000005150')
OR T314914.HIER4_CODE IN ('S000005151')
OR T314914.HIER5_CODE IN ('S000005153')
OR T314914.HIER6_CODE IN ('S000005154')
OR T314914.HIER7_CODE IN ('S000005062')
OR T314914.HIER8_CODE IN ('S000005160')
OR T314914.HIER9_CODE IN ('S000000187')
OR T314914.HIER10_CODE IN ('S526003000')
OR T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER3_CODE IS NULL)
AND ( T314914.HIER4_CODE IN ('S000005151')
OR T314914.HIER5_CODE IN ('S000005153')
OR T314914.HIER6_CODE IN ('S000005154')
OR T314914.HIER7_CODE IN ('S000005062')
OR T314914.HIER8_CODE IN ('S000005160')
OR T314914.HIER9_CODE IN ('S000000187')
OR T314914.HIER10_CODE IN ('S526003000')
OR T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER4_CODE IS NULL)
AND ( T314914.HIER5_CODE IN ('S000005153')
OR T314914.HIER6_CODE IN ('S000005154')
OR T314914.HIER7_CODE IN ('S000005062')
OR T314914.HIER8_CODE IN ('S000005160')
OR T314914.HIER9_CODE IN ('S000000187')
OR T314914.HIER10_CODE IN ('S526003000')
OR T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER5_CODE IS NULL)
AND ( T314914.HIER6_CODE IN ('S000005154')
OR T314914.HIER7_CODE IN ('S000005062')
OR T314914.HIER8_CODE IN ('S000005160')
OR T314914.HIER9_CODE IN ('S000000187')
OR T314914.HIER10_CODE IN ('S526003000')
OR T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER6_CODE IS NULL)
AND ( T314914.HIER7_CODE IN ('S000005062')
OR T314914.HIER8_CODE IN ('S000005160')
OR T314914.HIER9_CODE IN ('S000000187')
OR T314914.HIER10_CODE IN ('S526003000')
OR T314914.HIER11_CODE IN ('S526002012')
OR T314914.HIER12_CODE IN ('S000001022')
OR T314914.HIER7_CODE IS NULL)
AND T314768.HIER1_CODE IS NOT NULL
AND T314914.HIER20_CODE IS NOT NULL
AND T314914.HIER13_CODE IS NULL
AND T314914.HIER14_CODE IS NULL
AND T314914.HIER15_CODE IS NULL
AND T314914.HIER16_CODE IS NULL
AND T314914.HIER17_CODE IS NULL
AND T314914.HIER18_CODE IS NULL
AND T314914.HIER19_CODE IS NULL)
GROUP BY T314768.HIER1_CODE,
T314768.HIER1_NAME,
T314914.HIER1_CODE,
T314914.HIER1_NAME,
T314914.HIER2_CODE,
T314914.HIER2_NAME,
T314914.HIER3_CODE,
T314914.HIER3_NAME,
T314914.HIER4_CODE,
T314914.HIER4_NAME,
T314914.HIER5_CODE,
T314914.HIER5_NAME,
T314914.HIER6_CODE,
T314914.HIER6_NAME,
T314914.HIER7_CODE,
T314914.HIER7_NAME,
T314914.HIER8_CODE,
T314914.HIER8_NAME,
T314914.HIER9_CODE,
T314914.HIER9_NAME,
T314914.HIER10_CODE,
T314914.HIER10_NAME,
T314914.HIER11_CODE,
T314914.HIER11_NAME,
T314914.HIER12_CODE,
T314914.HIER12_NAME,
T314914.HIER13_CODE,
T314914.HIER13_NAME,
T314914.HIER14_CODE,
T314914.HIER14_NAME,
T314914.HIER15_CODE,
T314914.HIER15_NAME,
T314914.HIER16_CODE,
T314914.HIER16_NAME,
T314914.HIER17_CODE,
T314914.HIER17_NAME,
T314914.HIER18_CODE,
T314914.HIER18_NAME,
T314914.HIER19_CODE,
T314914.HIER19_NAME,
T314914.HIER20_CODE,
T314914.HIER20_NAME),
SAWITH1
AS (SELECT SUM (D1.c1) OVER () AS c1,
MAX (D1.c2) OVER (PARTITION BY D1.c22) AS c2,
MAX (D1.c3) OVER (PARTITION BY D1.c22) AS c3,
MAX (D1.c4) OVER (PARTITION BY D1.c22) AS c4,
MAX (D1.c5) OVER (PARTITION BY D1.c22) AS c5,
MAX (D1.c6) OVER (PARTITION BY D1.c22) AS c6,
MAX (D1.c7) OVER (PARTITION BY D1.c22) AS c7,
MAX (D1.c8) OVER (PARTITION BY D1.c22) AS c8,
MAX (D1.c9) OVER (PARTITION BY D1.c22) AS c9,
MAX (D1.c10) OVER (PARTITION BY D1.c22) AS c10,
MAX (D1.c11) OVER (PARTITION BY D1.c22) AS c11,
MAX (D1.c12) OVER (PARTITION BY D1.c22) AS c12,
MAX (D1.c13) OVER (PARTITION BY D1.c22) AS c13,
MAX (D1.c14) OVER (PARTITION BY D1.c22) AS c14,
MAX (D1.c15) OVER (PARTITION BY D1.c22) AS c15,
MAX (D1.c16) OVER (PARTITION BY D1.c22) AS c16,
MAX (D1.c17) OVER (PARTITION BY D1.c22) AS c17,
MAX (D1.c18) OVER (PARTITION BY D1.c22) AS c18,
MAX (D1.c19) OVER (PARTITION BY D1.c22) AS c19,
MAX (D1.c20) OVER (PARTITION BY D1.c22) AS c20,
D1.c21 AS c21,
D1.c22 AS c22,
SUM (
D1.c1)
OVER (
PARTITION BY D1.c46,
D1.c47,
D1.c48,
D1.c49,
D1.c50,
D1.c51,
D1.c52,
D1.c53,
D1.c54,
D1.c55,
D1.c45,
D1.c44,
D1.c56,
D1.c57,
D1.c58,
D1.c59,
D1.c60,
D1.c61,
D1.c62,
D1.c63,
D1.c22)
AS c23,
D1.c24 AS c24,
D1.c25 AS c25,
D1.c26 AS c26,
D1.c27 AS c27,
D1.c28 AS c28,
D1.c29 AS c29,
D1.c30 AS c30,
D1.c31 AS c31,
D1.c32 AS c32,
D1.c33 AS c33,
D1.c34 AS c34,
D1.c35 AS c35,
D1.c36 AS c36,
D1.c37 AS c37,
D1.c38 AS c38,
D1.c39 AS c39,
D1.c40 AS c40,
D1.c41 AS c41,
D1.c42 AS c42,
D1.c43 AS c43,
D1.c44 AS c44,
D1.c45 AS c45,
D1.c46 AS c46,
D1.c47 AS c47,
D1.c48 AS c48,
D1.c49 AS c49,
D1.c50 AS c50,
D1.c51 AS c51,
D1.c52 AS c52,
D1.c53 AS c53,
D1.c54 AS c54,
D1.c55 AS c55,
D1.c56 AS c56,
D1.c57 AS c57,
D1.c58 AS c58,
D1.c59 AS c59,
D1.c60 AS c60,
D1.c61 AS c61,
D1.c62 AS c62,
D1.c63 AS c63
FROM SAWITH0 D1)
SELECT DISTINCT
38 AS c1,
D1.c24 AS c2,
D1.c25 AS c3,
D1.c26 AS c4,
D1.c27 AS c5,
D1.c28 AS c6,
D1.c29 AS c7,
D1.c30 AS c8,
D1.c31 AS c9,
D1.c32 AS c10,
D1.c33 AS c11,
D1.c34 AS c12,
D1.c35 AS c13,
D1.c36 AS c14,
D1.c37 AS c15,
D1.c38 AS c16,
D1.c39 AS c17,
D1.c40 AS c18,
D1.c41 AS c19,
D1.c42 AS c20,
D1.c43 AS c21,
D1.c21 AS c22,
NULL AS c23,
NULL AS c24,
NULL AS c25,
NULL AS c26,
NULL AS c27,
NULL AS c28,
NULL AS c29,
NULL AS c30,
NULL AS c31,
NULL AS c32,
NULL AS c33,
NULL AS c34,
NULL AS c35,
NULL AS c36,
NULL AS c37,
NULL AS c38,
NULL AS c39,
NULL AS c40,
NULL AS c41,
D1.c44 AS c42,
D1.c45 AS c43,
D1.c46 AS c44,
D1.c47 AS c45,
D1.c48 AS c46,
D1.c49 AS c47,
D1.c50 AS c48,
D1.c51 AS c49,
D1.c52 AS c50,
D1.c53 AS c51,
D1.c54 AS c52,
D1.c55 AS c53,
D1.c56 AS c54,
D1.c57 AS c55,
D1.c58 AS c56,
D1.c59 AS c57,
D1.c60 AS c58,
D1.c61 AS c59,
D1.c62 AS c60,
D1.c63 AS c61,
NULL AS c62,
D1.c22 AS c63,
NULL AS c64,
NULL AS c65,
NULL AS c66,
NULL AS c67,
NULL AS c68,
NULL AS c69,
NULL AS c70,
NULL AS c71,
NULL AS c72,
NULL AS c73,
NULL AS c74,
NULL AS c75,
NULL AS c76,
NULL AS c77,
NULL AS c78,
NULL AS c79,
NULL AS c80,
NULL AS c81,
D1.c23 AS c82,
CASE WHEN 1 = 1 THEN 1 ELSE 0 END AS c83,
CASE
WHEN D1.c2 IS NULL
AND D1.c3 IS NULL
AND D1.c4 IS NULL
AND D1.c5 IS NULL
AND D1.c6 IS NULL
AND D1.c7 IS NULL
AND D1.c8 IS NULL
AND D1.c9 IS NULL
AND D1.c10 IS NULL
AND D1.c11 IS NULL
AND D1.c12 IS NULL
AND D1.c13 IS NULL
AND D1.c14 IS NULL
AND D1.c15 IS NULL
AND D1.c16 IS NULL
AND D1.c17 IS NULL
AND D1.c18 IS NULL
AND D1.c19 IS NULL
AND D1.c20 IS NULL
THEN
1
ELSE
0
END
AS c84
FROM SAWITH1 D1
WHERE ( D1.c44 IS NOT NULL
AND D1.c50 IS NULL
AND D1.c49 IS NULL
AND D1.c22 IS NOT NULL
AND D1.c51 IS NULL
AND D1.c52 IS NULL
AND D1.c53 IS NULL
AND D1.c54 IS NULL
AND D1.c55 IS NULL)
/* Formatted on 12/17/2012 7:49:44 PM (QP5 v5.139.911.3011) */
WITH OBICOMMON0
AS (SELECT T156337.ROW_WID AS c2,
T156337.MCAL_PERIOD_WID AS c3,
ROW_NUMBER ()
OVER (PARTITION BY T156337.MCAL_PERIOD_WID
ORDER BY T156337.MCAL_PERIOD_WID DESC)
AS c4,
T156337.MCAL_PERIOD_NAME AS c5,
T156337.MCAL_PER_NAME_YEAR AS c6
FROM W_MCAL_DAY_D T156337 /* Dim_W_MCAL_DAY_D_Fiscal_Day */
WHERE (T156337.MCAL_CAL_NAME = 'Accounting')),
SAWITH0
AS (SELECT CASE
WHEN CASE D1.c4 WHEN 1 THEN D1.c2 ELSE NULL END
IS NOT NULL
THEN
RANK ()
OVER (
ORDER BY
CASE D1.c4 WHEN 1 THEN D1.c2 ELSE NULL END ASC NULLS LAST)
END
AS c1,
D1.c2 AS c2,
D1.c3 AS c3
FROM OBICOMMON0 D1),
SAWITH1
AS (SELECT DISTINCT
MIN (D1.c1) OVER (PARTITION BY D1.c3) AS c1, D1.c2 AS c2
FROM SAWITH0 D1),
SAWITH2
AS (SELECT CASE
WHEN CASE D1.c4 WHEN 1 THEN D1.c2 ELSE NULL END
IS NOT NULL
THEN
RANK ()
OVER (
ORDER BY
CASE D1.c4 WHEN 1 THEN D1.c2 ELSE NULL END ASC NULLS LAST)
END
AS c1,
D1.c3 AS c2,
D1.c5 AS c3,
D1.c6 AS c4
FROM OBICOMMON0 D1),
SAWITH3 AS (SELECT DISTINCT MIN (D1.c1) OVER (PARTITION BY D1.c2) AS c1,
D1.c2 AS c2,
D1.c3 AS c3,
D1.c4 AS c4
FROM SAWITH2 D1),
SAWITH4
AS ( SELECT SUM (T91707.TD_OTHER_REP_AMT) AS c1,
T314914.HIER1_NAME AS c2,
D2.c3 AS c3,
T314914.HIER1_CODE AS c4,
D2.c2 AS c5
FROM W_HIERARCHY_D T314914 /* Dim_W_HIERARCHY_D_Segment13 */
W_GL_SEGMENT_D T315731 /* Dim_W_GL_SEGMENT_D_Segment13 */
W_GL_ACCOUNT_D T91397 /* Dim_W_GL_ACCOUNT_D */
W_GL_OTHER_F T91707 /* Fact_W_GL_OTHER_F */
SAWITH1 D4,
SAWITH3 D2
WHERE ( T314914.HIER_CODE = T315731.SEGMENT_LOV_ID
AND T314914.HIER_NAME = T315731.SEGMENT_LOV_NAME
AND T91397.ROW_WID = T91707.GL_ACCOUNT_WID
AND T91707.ACCT_PERIOD_END_DT_WID = D4.c2
AND T314914.HIERARCHY_ID = T315731.SEGMENT_VAL_CODE
AND T91397.ACCOUNT_SEG13_CODE = T315731.SEGMENT_VAL_CODE
AND T91397.ACCOUNT_SEG13_ATTRIB = T315731.SEGMENT_LOV_ID
AND T315731.SEGMENT_LOV_NAME =
'Account_Retail_Distribution'
AND T315731.SEGMENT_LOV_ID = 1000165
AND D2.c1 = D4.c1
AND (D2.c4 IN ('2011', '2012')))
GROUP BY T314914.HIER1_CODE,
T314914.HIER1_NAME,
D2.c2,
D2.c3)
SELECT D1.c1 AS c1,
D1.c2 AS c2,
D1.c3 AS c3,
D1.c4 AS c4,
D1.c5 AS c5,
D1.c6 AS c6
FROM ( SELECT DISTINCT 0 AS c1,
D1.c2 AS c2,
D1.c3 AS c3,
D1.c4 AS c4,
D1.c1 AS c5,
D1.c5 AS c6
FROM SAWITH4 D1
ORDER BY c2 NULLS FIRST, c4 NULLS FIRST, c3) D1
WHERE ROWNUM <= 65001

Hello Gurus, Experts
Any help/tips here ...

Export OLAP 11G AW/Cubes to OBIEE 11g

Hi Experts,
If anyone has handled this assignment of exporting OLAP 11G AW/Cubes to OBIEE 11g, Please share all details. Currently we use BO for reporting requirements and before going ahead with OBIEE 11g would like to make sure there is not much of a gap. As of now we see a lot of incompatibility while exporting like some dims and cubes cannot be exported and so on. Any white paper/docs/information on this from experienced folks are welcome.
We are on 11.2.0.3 db release.
Thanks in advance,
MS

Here is some basic information about importing 11g analytic workspace cube and dimension metadata into OBIEE.
There are two basic options as I suspect you already know:
Option 1) Before the release of OBIEE 11.1.1.5 (I believe), there was no native support for the OLAP option within the administrator tool of OBIEE, and
one needed to use the AwM plug-in to OBIEE. The AwM plug-in generates a UDML file which can be imported into OBIEE using the OBIEE admin tool.
The AwM plug-in to OBIEE generates metadata for the source, business model, and presentation layers. The very latest version of the AwM plug-in will specially
handle calculated measures created in AwM and create the proper calculcated measure expression in OBIEE. This is very important if you are querying above the cube
to get the correct aggregation results. One area that has limited support is if a dimension only has value-based hierarchies. The plug-in will create a very simple level-based
hierarchy to at least allow the dimension to be successfully created. You then need to do more work within the OBIEE administration tool to create the fully baked
value-based hierarchies. I do not have any real-world experience with value-based hierarchies in OBIEE. Again, the AwM plug-in to OBIEE works with level-based hierarchies
and supports multiple hierarchies per dimension. The AwM plug-in to OBIEE is available on the OTN download page for the OLAP option.
Here is the link: Oracle OLAP Downloads: Software & Samples
Option 2) OBIEE 11.1.1.5 and later allows for native integration for accepting OLAP 11g dimension and cube metadata as a supported source.
This integration makes the AwM plug-in somewhat obsolete (except for the calculated measure expression integration which is unique to the AwM plug-in and using
AwM to create calculated measures including time-based calculated measures)
Please expand on the incompatibility issues you are running into. Is this related to a lot of value-based hierarchies or other issues?

Hierarchy in obiee 11g

Hi All,
we have a to create a hierarchy for the below type.
H1-->H2-->H3-->H5
-->H4
H1
|
H2
| |
H3 H4
|
H5
How to create this type of hierarchy..?
When we click on H1, H2 will display, when we click on H2, H3 and H4 should display, then clicking on H3 should disply H5.
Also how to restrict to either H3/H4 when we click on H2..???
Thanks.

Hi,
you have to create ragged hyrearchy
see this link fo rdetails
http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/
http://sandybi.wordpress.com/2010/08/18/hierarchies-in-obiee-11g-part-2/

New Hierarchies in 11g

Hi All,
I have been trying to figure out the new hierarchies in 11g and I am having some difficulties.
I have the following:
Products Sales
Prod 1 100
Prod 2 100
Prod 3 100
So I have set up a hierarchy for my products with Sales as a measure
When I see this in BI
- All Products -- 300
-- Prod 1 100
-- Prod 2 100
-- Prod 3 100
For some reason it is rolling up the total to 300. When I try and chart this pivot table it includes this rolled up amount ...
So in a bar graph i will get on the x axis
All Products Prod1 Prod2 Prod3
I only want to show Prod1 Prod2 Prod3
How do I stop this from rolling up. I am using a level based hierarchy
Should I be using a parent - child?
Thanks in advance

hi cluless,
Follow these for hierarchies in obiee 11g.
http://blogs.oracle.com/robreynolds/2010/07/obiee11g_new_feature_-hierar.html
http://obieetalk.com/obiee-11gr1-support-ragged-skip-level-value-based-hierarchies#
Cheers,
KK

Value based hierarchies, Skip Level Hierarchies

Hello,
I need to create hierarchy based on column value , Please give me some details on implementing value based hierarchies and skip level hierarchies in obiee 10.1.3.
Thank you

With 10.3 i do not think we have a inbuilt solution to build value based hierarchies, you have to flatten the hierarchy and build a level based hierarchy.
OBIEE 11g has value based hierarchies feature.
refer this one for 11g.
http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/
- Madan
Edited by: Madan Thota on Sep 14, 2010 11:15 AM

Custom DataSources for Hierarchies / Missing entry in ROOSGEN

Hi,
I have created a master data dataSource and
changed the corresponding entries in the customizing tables.
The extractors works fine. In the monitor
I can see the records of the request, but
after a while the monitor shows a red light.
I got the following message:
Syntax error in generated program, row 0
Message RSAR683
The corresponding generation template is RSAPTH3.
At the beginning of the template a function module
is called. This function module get its information
form ROOSGEN.
How to get entries in ROOSGEN (RSTRANSACTIVATE*ALL)
does not work.)? Are there other approaches?
Can you help me to become the lights green?
Regards & Thanks,
Guido
P. S.: I have done the same in BW2.0
and has been working.
Okay not for intervals in a hierarchy
P. P. S.: I need to supply intervals. Otherwise
the hierarchy will be to huge for reporting ( >= 200.000 elements).
P. P. P. S.: Other ideas/approaches to makes
a hierarchy with more than 100.000 elements reportable.
For balanced hierarchies: navigation attributes, ...
For unbalanced hierarchies: ?

Hi Guido,
this pretty much looks like a program error.
Depending on the BW release, sap notes 944842 or 500913 apply. I assume that as a consequence the roosgen entry is missing. Otherwise it is straightforward the transfer structure name should appear in field TFSTRUC.
If not I recommend to open a new message for the customer.
Regards, Matthias

Default expanded hierarchy in OBIEE

Hi,
I have designed product hierarchy. It's working as desired. Product Category is at first level with a drill down symbol (+). When I click on that '+', it drills down to Product Subcategory. Similarly I can navigate to products by clicking '+' symbol further. Now I have a requirement where in I have to show all levels opened at a time, so that end user can see detailed data first, then they can drill up to required level.
Thanks,

Hi Welcome,
Please refer the following links, Here step by step with screen shots.
https://blogs.oracle.com/robreynolds/entry/obiee_11g_new_feature_-_hierar
http://www.rittmanmead.com/2010/08/oracle-bi-ee-11g-parent-child-hierarchies-differing-aggregations/
http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/
Award Points it is useful.
Thanks,
Satya

Drill across multiple hierarchies

Hi
how we will drill across multiple dimensional hierarchies in obiee.pls explain
regards
mervin

Hi,
Use preffered drill path option in hierarchy,which helps you drill from one hierarchy to other hierarchy.
Go through this..will give yu good idea : http://download.oracle.com/docs/cd/E12096_01/books/admintool/admintool_BusModSetup20.html#wp1017814
Regards,
Srikanth

No Results after build a Parent-Child Hierarchy in OBIEE11G

Hi All:
Here's an problem. I followed the "http://sandybi.wordpress.com/2010/08/17/hierarchies-in-obiee-11g-part-1/" this article step by step to create a parent-child hierarchy in admin tool in OBIEE11G.
But after check in and try to retrieve the hierarchy data in Answer. There's always displays "No Results."
Is there any suggestions for this ? Really urgent and thanks for your help.
Best regards
Sunny

@Aketi
It is One way that We derive
"sys_connect_by_path(RowIDToChar(RowID),'.') as
RowIDList"
Then
We use Left Join Using
"instr(RowIDList,RowIDToChar(RowID))".sorry, didn't catch what you mean.
my site :-)
http://oraclesqlpuzzle.hp.infoseek.co.jp/4-13.html
pity, I don't know Japanese :(
@Rob
your query is good and simple :) probably it's the best alternative for the OP.
But it won't work with not a plain hierarchy, e.g.:
      1
    2   3
      4
    5   6
SQL> create table hierarchy (child,parent)
2     as
3     select 1, null from dual union all
4     select 2, 1 from dual union all
5     select 3, 1 from dual union all
6     select 4, 3 from dual union all
7     select 4, 2 from dual union all
8     select 5, 4 from dual union all
9     select 6, 4 from dual
10 /
Table created
SQL>
SQL> create table data (hierarchyid,value)
2    as
3    select 5, 10 from dual union all
4    select 6, 25 from dual
5 /
Table created
SQL>
SQL> select h.child
2           , sum(connect_by_root d.value)
3        from hierarchy h
4           , data d
5       where h.child = d.hierarchyid (+)
6     connect by prior h.parent = h.child
7       group by h.child
8       order by h.child
9 /
     CHILD SUM(CONNECT_BY_ROOTD.VALUE)
         1                          70
         2                          35
         3                          35
         4                          70
         5                          10
         6                          25
6 rows selected
SQL>

0WBS_ELEMT hierarchy through MDX universe populating random values in WebI

Hi Experts,
We are facing an issue in WebI 3.1, while creating a report on top of MDX universe with 0WBS_ELEMT hierarchy - coming from BEx query. All other hierarchies in other reports are working fine, but the issue seems to be particular to 0WBS_ELEMT hierarchy.
First of all, the WebI does not includes full project entries along with WBS hierarchy - this could be a limitation (2nd comment in https://cw.sdn.sap.com/cw/ideas/2084#comment-14280), and we found workaround as to display in seperate block.
Now the actual issue is, even hierarchy nodes of WBS element are not coming properly in the WebI. There are 5 nodes in universe (L00 to L04). We dragged all of them into the report and found that some nodes are missing. These are the L01 nodes which are not having any subordinate nodes.
Tried different combitions, and later found that if we are not keeping the nodes L02 to L04 in the query, all missing entries (in first report) are coming, but now some other nodes are getting dissapeared.
Can anyone tell the reason and/or solution for the issue. Is this the known issue with 0WBS_ELEMT hierarchy? If so, what SAP is recommending for this? This is really urgent, reply.
Regards,
Kshiteesh

Hi Henry,
Thanks for reply.
We are on BI 7.1 SP 07. We are having other hierarchies working in expected manner, but only WBS element hierarchy is having issue.
After posting to SDN, I saw some other posts on the forum and checked the note 1446246. This note points to others notes, and 2 notes (0001562173 - flattening unbalanced hierarchies & 1432162 - MDX Flattening problems when using hierarchies) which seems to be relevant.
It seems to be case of unbalanced hierarchies, but to be sure please suggest if we can go with these notes.
Regards,
Kshiteesh

0WBS_ELEMT Hierarchy - accessing a level 2 or 3 WBSE as a starting point.

Hello,
I have a question related to using the 0WBS_ELEMT Hierarchy. We are on BW 3.1 and I have built a query using the WBSE Hierarchy.
I have set a selection option for 0PROJECT, and
I have set a selection option for 0WBS_ELEMT (in properties, Hierarchy is active)
This is just a simple query with those two items as rows and one column to bring in 0AMOUNT as a column.
<b>Example 1:</b>
When I input a Project Definition (0PROJECT) selection as SDVJ/2006/E/OUT (this is our WBS edit mask format).
I get a nice looking output, and I can drill down to the lowest level WBSE's in the hierarchy. (four or five levels deep)
In our hierarchy display we can see these levels:
SDVJ/2006/E/OUT
SDVJ/2006/E/OUT/U1
SDVJ/2006/E/OUT/U2
SDVJ/2006/E/OUT/U3
And we can drill into the level we wish to.
Now, I have been asked to do this kind of report, but to have the user start out at (for example) the Unit 2 level (SDVJ/2006/E/OUT/U2)
<b>Example 2:</b>
I input the SDVJ/2006/E/OUT/U2 into the selection option for 0WBS_ELEMT, but I only get a couple of levels and I cannot get to the details that I can ge to by using my first example.
I am at a loss as to why this is happening to me. I would appreciate any pointers, tips, or suggestions.
Thanks.
Lloyd
PS: I did a search of this message board but could not see one that provided me a fix. If there is one that I missed, I apologize.

Hi Henry,
Thanks for reply.
We are on BI 7.1 SP 07. We are having other hierarchies working in expected manner, but only WBS element hierarchy is having issue.
After posting to SDN, I saw some other posts on the forum and checked the note 1446246. This note points to others notes, and 2 notes (0001562173 - flattening unbalanced hierarchies & 1432162 - MDX Flattening problems when using hierarchies) which seems to be relevant.
It seems to be case of unbalanced hierarchies, but to be sure please suggest if we can go with these notes.
Regards,
Kshiteesh

Which Query features are supported

Hello together,
does somebody know if there is a existing list of the supported Bex Query features
with the new BICS connectivity (Direct connect from Xcelsius 2008 to BW Queries)
Thank you
Best Regards
Mike

Hello Mike,
There will soon be a detailed article on this, available from [https://wiki.sdn.sap.com/wiki/display/BOBJ/Xcelsius2008andSAPNetWeaverBIConnection] .
Going through your list, here are quick comments :
SAP Variables - Variable Type
- Single Value
- Multiple Single Value
- Range Value
All variable types are supported
Text Variable
- Keydate Variable
- Currency Variable
All of them are supported
Query Features
- Support for single Hierarchies
- Support for multiple Hierarchies
You will get prompted by a hierarchy variable but overall, hierarchy support is limited because there is no built-in tree control in Xcelsius ; there are components available from Partners though.
- Support for Calculated Keyfigures
- Support for Restricted Keyfigures
Yes, supported
- Support for Multiple Structures
- Support for Formulas
- Support for Selections
need to double check the two structure use case
- Support for Filter
Yes, supported
- Support for Display Attributes
- Support for Conditions
Yes, supported
- Support for Exceptions
No, not supported : BEx query is used as a data source for Xcelsius, any visualization setting (like alert colors with exception) are handled within Xcelsius. Exception Aggregations are however supported.
- Support for Navigational Attributes
- Support for compounded characteristics
Yes, supported
- Support for unbalanced Hierarchies
- Support for ragged Hierarchies
see comment on hierarchies above
patrice

Unbalanced hierarchies in OBIEE+

Similar Messages

Maybe you are looking for