Regarding performance issue in time dependent hierarchie.

hai
we are loading time dependent hierarchies from flatfile to bw,it is weekely load,we have nearly one million records loaded,we got an issues regarding change of these hierarchies timely.when ever there occurs a change in hierarchy a new row is added to the table,it is degrading the performance,can any one of you please suggest how to over come performance related issues regarding time dependent hierarchies.
Regards
Srinivas.G

hello deven,
if you are only focusing on your application's performance
on the aspect of usability i.e. less waiting time, fast
response UI, i would personally suggest you to use AJAX.
put some processing part on the browser side and making
data retrieval from MI asynchronous... this way, your user
don't have to wait for all data to be presented, but rather
could work on the data presented in pieces (i.e. asynchronously).
anyway try googling for AJAX...
regards
jo

Similar Messages

Is BPCNW 7.5 supports Time dependent Hierarchies ?

Hi,
We are maintaing 4 hierarchies for Profit center dimension. Depends on business structure nodes(profitcenters) will move from one parent to another.
For e.g:
In 2009 my PC hierarchy looked like
RBU1
-- PC1
-- PC2
RBU2
-- PC3
-- PC4
And in 2010, PC2 moved under RBU2, and the hierarchy looked like
RBU1
-- PC1
RBU2
-- PC2
-- PC3
-- PC4
So, now the requirement is if they want to look at 2009 numbers they would want to see the hierarchy roll up of 2009 and if they look at 2010 numbers, they would like to look at the new hierarchy.
Is this requirement possible in BPC NW7.5 with out maintaining new hier for 2010.
thanks in advance...
regards,
Raju

Hi,
As such time dependent hierarchies are not supported by SAP BPC 7.5.
This will be deffinately covered in SAP BPC 8.0 release. BPC 8.0 is the major release of SAP BPC NW version.
Regads,
Mahesh

Regarding Performance Issue in MI Application

Hii All,
We have made a SmartSync MI Application.Everything thing is working fine.But the scenario is this that when we try to navigate through the application from one page to another ,for example if i click on one link to get details corresponding to that link(i.e) we are retreiving the data from the local database, but this is taking a lot of time and according to our buisness need we have to reduce this time to fetch the data.
Can anyone help me regarding this issue what can be done either in coding part, what parameters & standards to follow to improve the performance.
Thanks,
Devendra Phate

hello deven,
if you are only focusing on your application's performance
on the aspect of usability i.e. less waiting time, fast
response UI, i would personally suggest you to use AJAX.
put some processing part on the browser side and making
data retrieval from MI asynchronous... this way, your user
don't have to wait for all data to be presented, but rather
could work on the data presented in pieces (i.e. asynchronously).
anyway try googling for AJAX...
regards
jo

Changing to time-dependent hierarchie of 0CUSTOMER

Dear Experts,
I like to change 0CUSTOMER to "entire hierarchie is time-dependent" without losing any existing hierarchy or data. Is that somehow possible? I tried changing the Radio Button, but could not activate the InfoObject;
"The Hierarchy Table /BI0/HCUSTOMER must be converted incompatibly with an activation of characteristic 0CUSTOMER (changes to the key in the table). Table /BI0/HCUSTOMER contains data. Parts of this data were lost in the conversion."
I already checked the whole forum and the SAP help, but could not find a suitable note.
Can someone plase help?
Thank you very much in advance
Martina

Hello Amit,
Try reading the help documentation for such queries. e.g. Publishing Time-Dependent XML Documents - Knowledge Management - SAP Library
Regards,
Lorcan.

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 ...

Determine key date at runtime for time-dependant hierarchies

Hello all,
I have to develop a query based on time-dependant and version-dependant hierarchy.
I have selection variables for -
Fiscal year
posting period
version
and hierarchy .
I want to achieve this -
First I want to enter Fiscal Period and posting period and version as user input.
Once this input is done I want to determine the key date based on fiscal year and posting period.
Once the key date is determined i want the hierarchy variable dropdown to show only correct hierarchy in that time for selection.
Is it possible? Please suggest the ways.
Many thanks and best regards,
Surekha

I have written following code for determining key date based on fisc year and posting period.
It may be useful for someone
WHEN 'key date variable'.
    REFRESH e_t_range.
    CLEAR l_s_range.
    IF i_step = 2.
      READ TABLE i_t_var_range INTO loc_var_range WITH KEY vnam = 'fisc year variable'.
      l_date(4) = loc_var_range-low.
      CLEAR loc_var_range.
      READ TABLE i_t_var_range INTO loc_var_range WITH KEY vnam = 'posting period variable'.
      IF loc_var_range-low >= 12.
        l_date+4(4) = '1201'.
      ELSE.
        l_date+6(2) ='01'.
        l_date4(2) = loc_var_range-low1(2).
      ENDIF.
*get the last day of the posting period month
     CALL FUNCTION 'SLS_MISC_GET_LAST_DAY_OF_MONTH'
        EXPORTING
          day_in            = l_date
        IMPORTING
          last_day_of_month = l_date
        EXCEPTIONS
          day_in_not_valid = 1
          OTHERS            = 2.
      l_s_range-low = l_date.
      l_s_range-sign = 'I'.
      l_s_range-opt = 'EQ'.
      APPEND l_s_range TO e_t_range.
    ENDIF.

Time dependant hierarchical display

Hello Everyone!
I'm reporting from a Cube with Organizational Unit (0ORGUNIT). I want to to display it in hiearchical view (ORGEH). My question is this: Since this is a time-dependant hierarchy, what date does the system use to determine the correct node/time interval? The system date, or some other key date? If so, where is this key date defined?
Best Regards,
Luís Andrade.

Dear Luis,
In query designer, goto, query properties tab. Here, you will have the option to give query Key date. Here you can give a fixed date value or and SAP delivered date variable or a customer exit variable or a user entry variable.
Hope this helps you.
Best Regards,
Nithin Reddy.

Validity period merging issue for time dependent master data

Hello All,
I am trying to load the data from DSO ZDSO1 to Master data object ZCASE1. Attribute "ZATR1" of ZCASE1 is the time dependent attribute of ZCASE1.
ZDSO1 contains "Changed On" field which defines the "Valid From" period for attribute "ZATR1" of case ZCASE1.
For eg.
ZDSO1 contains below records for Case 'C1':
Case ID     Changed On ZATR1
C1              01.01.2014     01
C1              02.01.2014     01
C1              02.15.2014     07
C1              02.17.2014     07
My transformation from ZDSO1 to infoobject ZCASE1 contains below mapping:
Case ID - Direct Mapping - ZCASE1 object
Constant value '12/31/'9999' - VALID TO field
Changed on - Direct Mapping - DATE FROM field
ZATR1 - Direct Mappint - ZATR1 object
After loading the data from ZDSO1 to ZCASE1 below results are obtained:
Case ID     VALID FROM VALID TO   ZATR1
C1             01.01.1000    12.31.2013 BLANK
C1             01.01.2014    01.31.2014 01
C1             02.01.2014    02.14.2014 01
C1             02.15.2014    12.31.9999 07
Time-Dependency is define correctly however my concern is why second and third records were not merged together. Instead of having four records, I should have ideally received THREE records. As shown above, third and fourth record (value 07) from ZDSO1 are merged into SINGLE record in infoobject ZCASE1.
For the subsequent data, it again does the same thing.
For eg. If I receive below Delta record from ZDSO1:
C1   03.01.2014 07
I get FIVE records in infoobject ZATR1 as shown below:
Case ID     VALID FROM VALID TO   ZATR1
C1             01.01.1000    12.31.2013 BLANK
C1             01.01.2014    01.31.2014 01
C1             02.01.2014    02.14.2014 01
C1             02.15.2014    02.28.2014 07
C1             03.01.2014    12.31.9999 07
In my understanding, BW system should have merged this Delta record with the last record present in infoobject because both the records have same ZATR1 value.
I would really appreciate your help/suggestions to understand/resolve this issue.
Thank You,
Nilima

Hey Arun,
While there wasn't any other time-dependent attribute apart from ZATR1, there is another time-independent attribute ZATR2 of ZCASE1 whose value was changed and hence somehow system was not able to merge the validity range.
Thank You.
Nilima

Time Dependent Hierarchies in Bex

Hello All,
I have a time dependent hierarchy with the same leaf in two different nodes i.e,
Mr. Jones was a part of cost center A from 1/1/2001 to 12/31/2003 and he is a part of cost center B from 1/1/2004 to 12/31/2006.
When I want to run the report for time period 1/1/2001 to 12/31/2006, will the report show Mr. Jones as part of cost center A from 1/1/2001 to 12/31/2003 and as a part of cost center B from 1/1/2004 to 12/31/2006.
Or do I have to model this as a time dependent navigational attribute. If I do this, can I still display it as a hierarchy.
Please pour in your inputs.
Thanks.
In the infoObject i chose time-dependent hierarchy structure. I've built a new hierarchy, with the same leave in two different nodes. Each leave got different time interval but when i run a report on a period which include the time interval of the two leaves i get only one node...
Please advice.

Hello All,
I have a time dependent hierarchy with the same leaf in two different nodes i.e,
Mr. Jones was a part of cost center A from 1/1/2001 to 12/31/2003 and he is a part of cost center B from 1/1/2004 to 12/31/2006.
When I want to run the report for time period 1/1/2001 to 12/31/2006, will the report show Mr. Jones as part of cost center A from 1/1/2001 to 12/31/2003 and as a part of cost center B from 1/1/2004 to 12/31/2006.
Or do I have to model this as a time dependent navigational attribute. If I do this, can I still display it as a hierarchy.
Please pour in your inputs.
Thanks.

Double leafs in non-time dependant hierarchies

Hi I'd like to ask you if someone's dealt with double leafs in a non-time dependant hierarchy; this would be something like this:
|_Char.A_|_Chr.B_|_Chr.C
|_SERV_|_JEFE1_|_COMER1_|_100 EUR
|_SERV_|_JEFE2_|_COMER1_|_ 50 EUR
PROD
JEFE1
COMER1
_400 EUR
SERV..................150 EUR
____ JEFE1____ COMER1 100 EUR
____ JEFE2____ COMER1 50 EUR
PROD..................400 EUR
|____ JEFE1____ COMER1 400 EUR
As you can see the leaf COMER1 is repeated 3 times at the same moment; imagine a comercial that has a single boss and that boss belongs to diferent bussines lines; or another case, with a comercial that has 2 diferent bosses and each of these bosses belongs to a diferent bussines lines.
I'v tryed by making a hierarchy with external characteristics with the Ch.1 and Ch.2 but I can't repeat the Ch.2 JEFE1 cause a error message is thrown. Anyway It seems that external characteristics does not act like a filter in anyway as I've read in some posts of this forum.
¿Is there anyway where I can make a hierarchy with this structure of duplicated nodes and leafs?

Hi,
Maybe you can use compounding on the InfoObject C, compounding it with InfoObject A and B.
That way your salesman will be unique under each boss and business line.
Hope it helps,
David.

Regarding Performance Issue

Hi Friends,
i have a FI report, Main Cash Vocher Printing, the report is very slow so to check its performance i have done the SQL Trace in ST05.
in SQL trace i have found all the DB tables used and time taken to execute the select statement.... in that list i also found and Cluster Table RFBLG , but i did not used these cluster table in the program.
and i also found more than 500 entries of Obj.NameRFBLG in that ...
Though its duration is small , ,, can we control that so that my report performance van be increased
its Urgent...
Useful reply will be awarded maximum
Regards
Kumat M

Hi Kumat,
RFBLG is the Cluster table of the logical table BSEG. That means the table BSEG stores its rows in the database table RFBLG. If the access to RFBLG is fast enough, you could ignore those entries and concentrate on red lines in the trace.
Regards
Ralph Ganszky

Query Performance Issue - Max time spent on DB read

Hi Experts,
We have a big query which is having two levels and it is pulling data from 10 underlying cubes which have different sales organizations in each. Due to design of the query and amount of data in cubes the maximum time is being spent on DB read. Now we have checked the trace of the query execution and we have seen that the system goes and check , say a Cube A even when it does not contain data for the sales org that is requested by the user. Please note that we have mandatory selection for Sales org on the Level 1 query.
In order to resolve this issue we have maintained entry of SALESORG in the RRKMULTIPROVHINT table, but on running the trace again we are seeing that for Level 2 query the system is still querying the cubes which do not contain the data for the sales org requested by the user there by increasing the run time of the query many folds. Can you please help us out if you have faced similar issue?
Regards,
Prashant Shah

I think your Query data selection is expecting data from all the cubes. You have to analyze right from the Query definition and the variables selection to know further.
Please put "H" for your MP in RSDIPROP t-code and choose H in Query read mode in RSRT-->Properties.

Regarding Performance issues

Can anybody share pure BI Performance document of DB02, St02,RSRST analysis does purpose.
Can anyone share it., Thanks in advance.

HI,
check below links
http://www.sap-press.de/download/dateien/1049/sappress_bw_performance_optimization_guide_080.pdf
http://wiki.sdn.sap.com/wiki/display/BI/Aggregates--SAPBWQueryPerformance
http://sap.seo-gym.com/performance%20tuning%20for%20queries.pdf
Click on search button in SDN and Google you can find lots of docs
Regards
KP

Time Dependent Hierarchies in Bex Queries.

We are using Time depenedent Hierarchy structures.
year and period will be entered by the user in the query
Is there any simple solution where in based on the User entered year and period, corresponding hierarchy should be used in the query execution.

Hi Shashi,
One of the ways:
Create a variable type customer exit - in properties of the IO - in the 'select hierarchy' window there is a 'Variables' checkbox for key date.
Calculate the last date of the entered period/year in the exit.
Best regards,
Eugene

Regarding guarantee issue with Time Capsule in Russia

Hi there,
I`ve bought Time Capsule in LA last summer, it was working perfect and I`m absolutely satisfied by this device (wifi, time machine - brilliant!) but this Sunday something happened with my TC. It`s does`t work.
But the problem is that Apple authorized Moscow services can`t help me, as things turns out, in Russia Time Capsule is not certified so they can`t provide me with repair, spare-parts or any other support...
So it looks like I`ve spent my money for half-year working device ... ))))
Do I have any chance for real Apple support for my broken TC ?
Thank you in advance!

What's the exact problem? I've torn mine apart dozens of times and swapped out hard drives and never had an issue except for the lack of glue sticking to the rubber back pad.

Regarding performance issue in time dependent hierarchie.

Similar Messages

Maybe you are looking for