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.

Similar Messages

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

APD query key date with variable for time dependent MD display attributes

Hello,
In a APD I use a query as a source with a query key date that is filled with a customer exit variable.
When I run the query as a user, the time dependent MD display attributes look fine. However, when I use the query in an APD, I get no values for the time dependent display attributes.
Any suggestions?
Thanks

Hi,
Try to run query using RSCRM_BAPI Tcode, this you can also schedule in background
Thanks
Reddy

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

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.

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.

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.

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.

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

Time-dependent BW hierarchies in Analysis for OLAP

Hi all,
We are using time-dependent hierarchies in combination with a key date variable.
Tools used: Query designer based on SAP BW 7.4 and BO 4.0.
The following steps are executed:
Report is executed and key date is prompted
According to the key date, the correct time-dependent organisation hierarchy will be used in drill-down
Bring up variable screen again and select different key date
The drill-down changes according to the now correct time-dependent organisation hierarchy
The above scenario works for BEx Analyzer, BEx Web, Analysis for Office - but not for Analysis for OLAP.
Whenever I run through this scenario and confirm the updated key date, the following error is displayed:
cube.get.dimension.info.runtime.error : java.lang.IllegalStateException: There is no default hierarchy for dimension [ORG].
In the user guide I don't find any specifics about the hierarchies and since it works in all the other applications, I wonder where the error is coming from. I also could not find it anywhere else in the forum.
Has anyone experienced the same error or any suggestions?

Hi Peter,
This issue is captured in SAP Note 1941865. Resolved in 4.0 (8.5, 9.2 or SP10) and 4.1 (1.6 or SP03).
Symptom
In BI 4.1, Analysis for OLAP returns errors similar to:"An error occurred in the MDAS service while processing a request from Analysis, edition for OLAP. Try the operation again. If the problem persists, please contact your administrator. (AOC00041)" and/or "cube.get.dimension.info.runtime.error: java.lang.IllegalStateException: There is no default hierarchy for dimension [DIMENSIONNAME]"
The BW Query the AOLAP workspace is created against has 2 different hierarchies that have the same text description
Environment
SAP BusinessObjects Business Intelligence platform 4.0
SAP BusinessObjects Business Intelligence platform 4.1
Analysis, edition for OLAP
Reproducing the Issue
In CMC, create an OLAP BICS connection to a multi provider
Connect to BI launchpad and launch Analysis, edition for OLAP.
Use the connection to create a new workspace.
The error is observed
Cause
This issue has been logged as a defect under ADAPT01720287 for BI4.0 and ADAPT01713663 for BI4.1
Resolution
A fix for this issue is included in the following maintenance releases:
BI4.0:
Patch 8.5
Patch 9.2
Support Pack 10
BI4.1:
Patch 1.6
Support Pack 03

Hierarchies for time dependent

hi,
i want the use of time dependent hierarchies.. and what is the difference between TIME DEPENDENT HIERRACHIE STRUCTURE... AND.... ENTIRE HIERARCHIES IS TIME DEPENDENT
I done with HIERARCHIES NOT TIME DEPENDENT.. So, plz explain the use for that.. and if possible give me any scenarios...
with regards
prakash

Hi
See this
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a6702e07211d2acb80000e829fbfe/frameset.htm
Two clear examples are given
Bye
N Ganesh

SAP BPC - Legal entity/Profit Center hierarchies - Time dependency

Hello,
Usually Organizational structure (legal entity/ Profit center) hierarchies are time dependent in EC-CS and BCS.
Are these hierarchies time dependent in BPC?
If yes, How these settings should be made in BPC?
Kind regards,
RJ

BPC NW does NOT support time dependent hierarchies. However in 7.5NW, you can use dynamic hierarchy editor that will enable you to do time dependent BPC reports.
http://aiokeh.wdf.sap.corp:50000/SAPIKS2/contentShow.sap?_SCLASS=XDP_STRUCT&_SLOIO=66348113C47B4AE7B2F068B88047D02B&TMP_IWB_TASK=PREVIEW2&RELEASE=610&LANGUAGE=EN&_SEQNUM=307&_LOIO=6983A56B1CE34F89A016C8E795C773BF&_CLASS=BCO_COMMON
Regards
Pravin

Concept of Time-Dependency in BW

Hello Masters,
What is the Concept of Time-Dependency in BW?
What are
          1.     Time-Dependent Attributes
          2.     Time-Dependent Hierarchies
          3.     Time-Dependent Aggregates
And when why and when do we need/use them?
Please quote an example in your explanation.
I am bound to give points
Thanks and Best wishes,
I-BI

Time dependent attribute:
Have a look into the below records:
Cost center    Valid to         Valid from   Business Area compay code profitcenter
100AE79          04/30/2005    01/01/1000     A           100                 9056
100AE79          12/31/9999    05/01/2005     A           100                 2000
From the above 2 records, profit center values are different for the same cost center for different periods. If you run a BEx report and if it runs for the current period, profit center displayed is 2000. If the same query runs for prior period say 05/12/2003 then the profit center displayed is 9056 for the same 2 cost centers.
The above concept is same for the other 2 cases as well.
Hope this helps..
Narendra

Time dependent Hirarchy Structure

Hi,
I need to create Hirarchy, i did not create before,
Please some one explaine me how to create     Time dependent Hirarchy Structure in CostCenter InfoObject.
Please, please help me.
Thanks

HI
Find the below link
http://help.sap.com/saphelp_nw2004s/helpdata/EN/0e/fd4e3c97f6bb3ee10000000a114084/frameset.htm
Time-Dependent Hierarchies
Use
In a hierarchy that is not time dependent, the characteristic values are always the same.
If you want to create views of a hierarchy that are valid for a specific time period, you need to create the entire hierarchy as time dependent.
If you want to model relationships that change time-dependently, you need to create the hierarchy structure time-dependently.
Functions
In InfoObject maintenance, you can set whether and in which ways a hierarchy is time dependent. You can choose from the following:
·         whether the hierarchy is not time dependent (Hierarchy Not Time-Dependent). This is set by default.
·         whether the entire hierarchy is time dependent (Entire Hierarchy Time-Dependent).
·         whether individual node relationships are time dependent (Hierarchy Structure Time-Dependent)
·         whether a temporal hierarchy join is used with time-dependent hierarchy structures (Use Temporal Hierarchy Join)
Entire Hierarchy is Time-Dependent
You can either load time-dependent hierarchies (see Loading Time-Dependent Hierarchies) or create them in the BI system (see Creating a Hierarchy). When you create a time-dependent hierarchy, you have to enter a validity interval (valid to and valid from fields).
If an entire hierarchy is time dependent, the system creates hierarchy versions that are valid for separate intervals. The system automatically uses the current valid version in this case. The hierarchy valid in each case can be uniquely identified by its technical name and the From-To Date.
In the InfoObject tree of the Data Warehousing Workbench, all time-dependent hierarchies under the associated InfoObject are displayed with the corresponding To Date, for example Time-Dependent Hierarchy 05/31/2000.
In reporting, the system returns the valid hierarchy when a query is executed using the query key date.
Within a restructuring company areas, you can create time-dependent versions of a hierarchy for the Main Area InfoObject. This enables you to compare the restructuring over different time periods in a query.
Time-dependent hierarchy 01/01/1999 - 05/31/1999
Time-Dependent Hierarchy 06/01/1999 - 12/31/1999
Main Area NORTH
Main Area NORTH
Area 1
Area 2
Area 2
Main Area SOUTH
Main Area SOUTH
Area 1
Area 3
Area 3
Area 4
Area 4
In reporting, you can work in the individual columns of the report structure with fixed date values. You may want to do this to compare Main Area North in the Time-Dependent Hierarchy 05/31/2000 with Main Area North in the Time-Dependent Hierarchy 06/01/2000 (simulation).
Time-Dependent Hierarchy Structures
You can either load time-dependent hierarchies (see Loading Time-Dependent Hierarchies) or create them in the BI system (see Creating a Hierarchy).
In hierarchy maintenance, you can determine a valid time interval for each hierarchy node (Valid to and Valid from fields).
In reporting, a hierarchy with time-dependent hierarchy structures is created either for the current key date or for the key date defined for the query. In addition, you can evaluate a hierarchy historically using the temporal hierarchy join.
You can assign an employee to different cost centers at different times within the context of a restructuring.
In the context menu of a hierarchy, choose Display Hierarchy to access the hierarchy display: Each node and leaf has been given a date symbol. Hierarchy nodes that are assigned to different places in the hierarchy structure, depending on the time, are displayed more than once. By double clicking on a hierarchy node, you can display the associated validity period for the node relation.
In the following example, you can double click on the Jones leaf to see that the worker Jones was assigned to region USA between 01/01/1999 and 05/31/1999 and Puerto Rico from 06/01/1999 to 12/31/1999.
In order to use a hierarchy with a time-dependent hierarchy structure in reporting, you require the following settings in the BEx Query Designer:
                            a.      If you want to evaluate a hierarchy with a time-dependent hierarchy structure for a fixed key date, enter the key date in query definition.
                            b.      If you want to evaluate a hierarchy with a time-dependent hierarchy structure historically, for a key date that is to be derived from the data, choose the temporal hierarchy join option and specify the derivation type for the key date.
For a more detailed description of the functions and differences between the two evaluation views, see Time-Dependent Hierarchy Structures in the Query.
In maintenance of the key date derivation type (RSTHJTMAINT) determine the rule you want to use to determine the key date from the data. In this way you determine the time characteristic and way in which the key date is to be derived.
       1.      First determine the time characteristic.
If you choose a Basic Time Characteristic as a time characteristic (for example, 0CALDAY, 0CALMONTH, 0FISCPER), you can use a key date derivation type of this kind for all InfoProviders that contain exactly one time characteristic that references the selected basic time characteristic. If there are several time characteristics in an InfoProvider that reference the basic time characteristic, you have to either determine the time characteristic more specifically or select a particular time characteristic from a particular InfoSet (Time Characteristic from InfoSet).
       2.      Determine how you want the key date to be derived from the time characteristic.
The following derivation types are available:
¡        First day of the period
¡        Last day of the period
¡        Delay by number of days (you specify this in the Delay by Days field). In this case, the key date is calculated from the first day in the period plus the number of days specified minus 1. If the key date does not fall within the period, the last day of the period is used.
Key date derivation type with (basic characteristic = 0CALMONTH, derivation type = u201Cfirst day of periodu201C):
·         For January 2005 the key date is calculated as 1/1/2005.
·         For February 2005 the key date is calculated as 2/1/2005.
Key date derivation with (basic characteristic = 0FISCPER, derivation type = u201Cdelay by number of daysu201C and u201Ddelay u201C = 29):
·         For K4/01.2005 the key date is calculated as 1/29/2005.
·         For K4/02.2005 the key date is calculated as 2/28/2005.
·         For K4/03.2005 the key date is calculated as 3/29/2005.
Note that the way in which you determine the key date derivation type affects performance. The number of data records that the OLAP processor reads corresponds to the level of detail on which the time characteristic and the leaf level lie. For this reason, choose the time characteristic as approximately as possible in order to keep the hierarchy small.
A small hierarchy has 100 leaves. For a period of 12 months, the OLAP Processor reads 1200 data records at month level. At day level, it reads 36500 data records.
Regards,
kumar reddy.k
Edited by: kumar reddy on Nov 18, 2008 10:50 AM

Time Dependency issue

Hi Gurus,
                 I have User master data Info Object, and time dependency User group as navigational attribute. I checked navigational attributes in Info Cubes and MulitProviders. For testing purpose we have changed the validity period of User group like for example :
Output of Master Data.
__User       UserGRP      Validity From    Validity To__
MARKD   OCV             01/01/2010   06/17/2010
MARKD   PSV              06/18/2010 12/31/9999
                 But in the report it is showing current user group as PSA for all records. For old records which are before 06/17/2010 is suppose to be OCV but it is taking everything as PSA(before and after validity period).
                 Please any suggestions on this will appreciated.
Thanks
Ganesh Reddy.

Hi Ganesh,
The time dependant objects display the result based on key date.
By default the key date is current date.
So it will display the value of user group as of today in the whole data set.
If you set the key date to past date it will set the output of whole data set as on that day.
If you want it to be varying, you will have to add a user group field in the cube and populate it using ABAP lookuo on user master data.
-Vikram

Time dependant hierarchical display

Similar Messages

Maybe you are looking for