Consolidations Planning using BCS PCtr 'Entire Hierarchy time dependant'

Hi All,
We are doing CONS planning using BCS Profit Center and this infoobject has the 'Entire Hierarchy time dependant' property and we have two hierarchies one for 2010 and one for 2011.
If '0PLANDAT' variable used for the 'Key Date' in the Input Ready Query prooerties, would it take care of bringing up the hierarchy appropriately depending the Plan Year (Fiscal Year) or the period chosen for the planning.
Is there some place I can find the documentation and the logic for the '0PLANDAT' SAP Exit variable?
Thanks in advance,
- Shashi

Hi,
a key date in BW is the date that will be used to read time dependent objects as master data attributes or time dependent hierarchy nodes. These time dependend objects all have valid_from, valid_to fields, when the key date is in the interval the corresponding record will be taken. Observe, that a key date has no link to a time characteristic here.
The idea of 0PLANDAT is to have a variable the can be used in the customizing of time dependent objects in the planning model as characteristic relationships and in a query. The 0PLANDAT settings can be found in the planning specfic settings for an InfoCube in the planning modeler; to use 0PLANDAT in the query ensures that the same key date is used in the planning model and in the query.
Regards,
Gregor

Similar Messages

XmlA Discover members of hierarchy time-dependent

Hello, I have a problem with xmla web service on BW 3.1.
I've to retrieve the hierarchy members of a hierarchy time-dependant via xmla.
The method Discover havn't any parameter like key date. On SAP Documentation I found out the note 834196 that suggest to use BAPI_MDPROVIDER_SET_KEY_DATE in order to set the key date of session logon.
I've tried but the following call of Discover method doesn't take any key date (it use the current date).
Have anyone work with something like this ?
Regards.
MAX

Hi Siswono,
Ok, I see what you mean.
Then I would suggest that you determine the hierarchy end date first.
read the hierarchy table by determine its technical name, then find the hierarchy with your date that's between the start date and end date, then you can use the end date for the next step.
use get_hier_of_mbr with the determined end date.
Andy

Hierarchy Time Dependent ABAP code

Dear Experts,
I want to ask a custom BADI ABAP code to get the hierarchy of a dimension member where Time Dependent Hieararchy is implemented in that dimension.
Currently we are using Interface method IF_UJA_DIM_DATA->get_hier_of_mbr to get the hierarchy reference.
Sample Code:
DATA: o_test     TYPE REF TO if_uja_dim_data.
CALL METHOD o_test->get_hier_of_mbr
     EXPORTING
       i_member = lv_member
*      i_dateto = lv_datum
     RECEIVING
       ro_hier = lo_hierarchy.
However after we implement the time dependent on the dimension, this method returns nothing unless we specified the i_dateto parameter to the method (which is optional).
While my requirement is to get the hierarchy of the member with the date when this logic is executed, putting SY-DATUM to this parameter does not give me the result that I need. I need to put the i_dateto as '99991231' so the hierarchy returned by this method is the latest hierarchy, but not the current date where this logic is executed.
Is there any way to make that the time hierarchy obtained is the one when the logic is executed? Or is there any other method that is feasible to meet with my requirements?
Thanks
Regards,
Siswono

Hi Siswono,
Ok, I see what you mean.
Then I would suggest that you determine the hierarchy end date first.
read the hierarchy table by determine its technical name, then find the hierarchy with your date that's between the start date and end date, then you can use the end date for the next step.
use get_hier_of_mbr with the determined end date.
Andy

Issue making Cost Center Hierarchy Time Dependent

Hi,
We have three hierarchies on top of cost center and cost center was not time-dependent. There is a new requirement to make one of the hierarchies time dependent. To faclitate it, I changed the hierarchy property in cost center infoobject to "Hierarchy structure is time-dependent" and then loaded the hierarchy.It took the validity dates of 1.1.1000 to 31.12.999. A costcenter was changed from one node to another in ECC and was extracted into BI. As time-dependency is set, I thought that node will have two entries now one with validity period 1.1.1000 to 30.10.2009 and another with 31.10.2009 to 31.12.999. But instead the hierarchy was overwritten and only the latest change is refelcted.
Can someone please help in figuring out the issue. Should some change be done in ECC for time-dependency to reflect.
Thanks
Achyuta

Hey Achyuta,
The hierarchy needs to be time dependent in the source system and then the datasource for the time dependent hierarchy would then need to be replicated again. You'll know if it's right after the replication if you view the datasource in BW and the Data is Time Dependent check box is checked on the General Info Tab. Once the datasource is time-dependent, loads should populate the DateTo and DateFrom as you expect. Consult your R/3 expert if you need help over on the source system side.
Peace,
Dan Glick

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

How to: from time independent hierarchy to time dependent hierarchy in BW

Hello goeroes outthere,
I am facing the following problem and was wondering if some of you have faced the same issue.
In ECC we have a time independent hierarchy on Profit Center. Our customer wants to perform time DEPENDENT reporting in BW.
As the standard datasource does not support to be loaded via PSA in the datasource definition (only IDOC) we cannot enhance the datasource with fields such as DATEFROM and DATETO. I've tried doing so but this results in the following error message when loading : Selected number does not agree with transferred number of records.
So I have cancelled out this as being an option.
I am analyzing the following two options :
1. Making the hierarchy time dependent. (globally). The idea would be to create a custom ABAP program that would copy the loaded hierarchy to a hierarchy in which we define the datefrom as the actual system date and the dateto as 31.12.9999.
Prior to doing so the abap program should change the already loaded hierarchy by modifying the dateTO as actual system date -1 in the header of the hierarchy.
In theory this seems to be a good option, but I am afraid of the complexity of the ABAP program to be created by looking in debug how the copying process is handled in SAP.
2. Making the hierarchy structure TIme dependant. THis has as a consequence that the table /BI0/HPROFIT_CTR is adjusted to include DATETO and DATEFROM fields. A custom program could read the entries and perform the same activities as described above. So meaning finding and modifying the existing entries with DATETO fields with as an entry 31.12.9999 to adjust to sysdatum -1 and modfying all entries that don't have dateto and datefrom entries by putting datefrom (=sysdate) and the dateto (=31.12.9999).
The issue here is that first we need to find the link between the hierarchy ID and the Hierarchy loaded and that I am not sure how SAP will deal with this SID wise.
Option 1 seems feasable as the hierarchy does'nt change every single day and doesn't require to be loaded every single day. But before going in this direction, I would appreciate some confirmation of my approach.
Thanks in advance for sharing your lights on this topic.
Rgds,
Bvpe

Hi Bart,
I just solved this very problem today in a two step process:
In our implementation, we only want to control when a new version of the hierarchy is created. If nothing changes, whatever is brought in from the source system will just replace the current version. We imagine we'll only create versions at month end or major re-organization.
1) I created a Select Options variable in tcode: stvarv called ZPROFCTR_FROMDATE. I added a value to the low position and set the option to equals.
2) Open the infoPackage that is used to load the hierachy from the source system. Go to the Hierarchy Selection Tab and click on the button at the bottom of the tabbed frame "Dynamic Hierarchy Selections".
You should see two check boxes, place a check in the second box: "Determine Using Routine" Click on the create icon and put this in the routine
p_s_sel_hier = l_s_presel_hier.
data: tempfrom type tvarv_val.
select single low
from tvarvc
into tempfrom
where name = 'ZPROFCTR_FROMDATE'.
move tempfrom to p_s_sel_hier-datefrom.
p_s_sel_hier-dateto = '99991231'.
clear p_subrc.
I've include the entire subroutine for context, and so you can see the SAP generated coments in the form that attempt to explain what the form is going to do.
Long story short, the hierarchy you have selected with the radio button on the Hierarchy Selection tab will be the one that is affected by this logic.
form compute_hier
tables l_t_all_hier structure rshiertrsf
using l_s_presel_hier like rshiertrsf
        l_infopackage   type rslogdpid
changing p_s_sel_hier like rshiertrsf
           p_subrc like sy-subrc.
*Insert Source Code to decide which Hierarchy shall be loaded.
*The Hierarchy you select from table l_t_all_hier and fill
*into p_s_sel_hier will be loaded.
*The Structure l_s_presel_hier contains the pre-selection of the
*BW-Scheduler - just to inform you what the BW wll load
*if you change nothing.
*$*$ begin of routine - insert your code only below this line        *-*
p_s_sel_hier = l_s_presel_hier.
data: tempfrom type tvarv_val.
select single low
from tvarvc
into tempfrom
where name = 'ZPROFCTR_FROMDATE'.
move tempfrom to p_s_sel_hier-datefrom.
p_s_sel_hier-dateto = '99991231'.
clear p_subrc.
*$*$ end of routine - insert your code only before this line         *-*
endform.                    "compute_hier
Hope this helps,
Quack

Time Dependent Hierarchy for Cost Center

I have searched the entire SDN for this so any help would be really appreciated.
I am a BI consultant and I am trying to look around for the exact steps on how to make a Cost Center Hierarchy "Time Dependent" in ECC system.
I am aware of changes to do in BI system but there is no way that I can know what needs to be done in ECC side since we dont have any FI Consultant to help us. All the posts show that there is something to be done on ECC but it seems even no body is sure on what to do. I think the hierarchy is created in KSH1.
Please provide any documentation or exact steps on how to do it. I will assign full points to the correct and precise answer.
Regds
Girish

Hi,
Creation of cost centre:
Path: Accounting  Controlling  Cost centre accounting  Master data  Cost centre  Individual processing  Create (T. Code KS01)
Cost centre: Dept A
Valid from: 01.04.2009 to 31.12.9999
Enter
Name: Dept A
Depart Cost centre: Department A
Person responsible: A
Cost centre category: 1 (Production)
Hierarchy area: XXXXXX
Business area: XXXX
Currency: INR
Save (or) (Ctrl + s)
Ignore the warning message, press enter
Cost centre: Dept B
Valid from: 01.04.2009 to 31.12.9999
Reference cost centre: Dept A
Controlling area: XXXX
Enter
Name: Department B
Description: Cost centre department B
Basic data
Person responsible: B
Save (or) (ctrl + s)
Ignore the warning message, press enter
Cost centre: Dept C
Valid from: 01.04.2006 to 31.12.9999
Reference cost centre: Dept A
Controlling area: XXXX
Enter
Name: Department C
Description: Cost centre department C
Basic data
Person responsible: C
Save (or) (ctrl +s)
Ignore the warning message, press enter
Creation of Cost centre group:
Path: Accounting  controlling  Cost centre Accounting  Master data  Cost centre group  Create (T. Code KSH1)
Cost centre group: XXX Produ
Enter
XXX Produ u2013 Production department for Co. area XXXX
Select insert cost centre button (Shift + F4)
Give the cost centre: Dept A, Dept B
Save
Hope It will clear.
Regards,
Kishore K
Edited by: kishore babu on Nov 12, 2009 1:14 PM

Effect from build time dependent 2 attribute in info object master data

Dear all,
i creat time dependent 2 attributes in info object master data (ZCURRLUM) which use in info cube. after that i open workbook or query, it has short dump which error message
   "UNCAUGHT_EXCEPTION" "CX_RSR_X_MESSAGE"
   "CL_RSBOLAP_BICS_SERVICES======CP" or "CL_RSBOLAP_BICS_SERVICES======CM003"
   "HANDLE_UNCAUGHT_EXCEPTION"
Question: info object master data can't use more than a attribute time dependent???
i use in BI 7.0 level 14
thanks for your help
regards,
Joy

Hi Chandamita Sarmah,
I copy error code to you from line 1 to line 28
METHOD handle_uncaught_exception.
data:
    l_r_program_error TYPE REF TO cx_rsbolap_program_error.
data: lBExDebug type rs_bool.
GET PARAMETER ID 'BEXDEBUG' FIELD lBExDebug.
if lBExDebug = rs_c_true or CL_RSTT_TRACE=>GET_TRACEMODE_CURRENT_TRACE( ) = rstt0_c_tracem
Break-point for debugging, e.g. during running a trace
    break-point. "#EC NOBREAK
endif.
Subcall?
if P_RFC_CALL_DEPTH > 1.
Forward the exception
    subtract 1 from P_RFC_CALL_DEPTH.
    DATA: l_r_x TYPE REF TO cx_no_check.
    TRY.
       l_r_x ?= i_r_exception.
      CATCH cx_root.
        CLEAR l_r_x.
    ENDTRY.
    IF l_r_x IS INITIAL.
      RAISE EXCEPTION TYPE cx_rsr_propagate_x
        EXPORTING
          previous = i_r_exception.
    ELSE.
    RAISE EXCEPTION l_r_x.
    ENDIF.
endif.
All exceptions should have been caugth -> X-Message
Thanks a lot for your help
Joy

DSO as a time dependent Master Data infoprovider

Hi All
I am looking for a "How To" document on how to use a DSO as a time dependent MD provider.
I want to load a non time dependent Master Data from a non SAP source and update the DSO daily.
When ever an attribute is changing, I want to update the last status "To Date" from 31.12.9999 to today.
Hope I am clear on this one.
I don't want to use regular master data capabilities...
Thanks, Dror

Jurgen is right...
For an after image based extractor containing the latest view of the world - you basically can do this
DSO 1
Customer - Key
Sales Persion
Date to
Date From
last_date = 31.12.9999 (constant)
load date = sy-datum
First load:
customer A, Sales Person X, To Date = 31.12.9999 , from date = 12.03.2010
Second load a week later
customer A, Sales Person Y, To Date = 31.12.9999 , from date = 19.03.2010
Change log generated is
customer A, Sales Person X, To Date = 31.12.9999 , from date = 12.03.2010 record mode before image
customer A, Sales Person Y, To Date = 31.12.9999 , from date = 19.03.2010 record mode after image
What you can do now is feed master data timedependant object or another dso.
If it is another DSO then the structure is this
DSO 2
Customer - Key
Date from - Key
Sales Persion
Date to
You need the date_from as part of the key because you are going to use the overwrite facility to play with the data depending on the record mode of the changelog entries
but in the start routine make sure the semantic keys are correct so you get both images in the same packet
Then use field symbols to load the data package in to sort and then find the opposing after image and before image then
if record mode = before image
To date = from date from after image MIINUS 1 day
endif
Then the data going out of the start routine is this
customer A, Sales Person X, To Date = 18.03.2010 , from date = 12.03.2010 record mode before image
customer A, Sales Person Y, To Date = 31.12.9999 , from date = 19.03.2010 record mode after image
And the records stored will be this
After initial load
customer A, Sales Person X, To Date = 31.12.9999 , from date = 12.03.2010
After next weeks load
customer A, Sales Person X, To Date = 18.03.2010 , from date = 12.03.2010
customer A, Sales Person Y, To Date = 31.12.9999 , from date = 19.03.2010
Or something like that - but you get the idea.. and yes I have done it before

Reorganization of time dependent master data

I am using reorganization of time dependent master data and it does not merge overlapped period as suggested by SAP. Any suggestions please.
http://help.sap.com/saphelp_nw04s/helpdata/en/c7/b05e3cc3a1a62ce10000000a114084/frameset.htm
Best Regards
Vikash

Hi,
you have used the processvariante "reorganization of time dependent master data" in a process chain and it doesn't work?
I don't think so.
1. it works perfekt. so, you can reduce the data in the master data table.
2. you don't have overlapping periods - you have one-after-another time intervals.
=> Please check the attributs again. I think there is a change in one attribut.
Sven

Issue while creating a heirarchy using Hierarchy Structure Time dependent

Hi every body
I created an Info object(SREP) with Heirarchy Strututre Time Dependent property. When i am creating an Heirarchy for the info object(SREP) i am not able to see any text node by default, do we need to create it explicitly or system would propose one node by defalut..
I created a text node manually then and tried to assign an another info object(SREG) as a child using an option of "Insert Characterstic", but i am getting a message as "InfoObject SREG is not entered for InfoObject SREP as a Foreign Heirarchy Characterstic", and system is again proposing to assign some info object as a child.
Thanks in advance..
sekhar

ok

0CS_Item with time-dependent hierarchy

Dear Experts,
we are discussing pros and cons for a time-dependent item catalog (characteristic 0CS_item with time dependent hierarchy in BW) within consolidation SEM BCS 4.0. Does anybody has experiences on this topic?
I am quite sure it will be a performance issue and it means additional reporting effort (e.g. using reference period/year in the report comparing different hierarchies).
I am not sure if there are any other risks so I it would be great if anybody has some hints.
Thanks in advance,
Birgit Laux
Message was edited by: Birgit Laux

Birgit,
Some other things to consider:
- frequency of changes to item hierarchy. Could lead to a lot of item hierarchies in BW over time.
- hierarchy validity date does not seem to be displayed when running web queries and thus makes it difficult for the user to select the correct hierarchy when executing the query. Still looking for a fix for this.
- greater complexity in overall design. Is it really necessary to achieve correct financial statement presentation?
Virtual cube performance is not great but you could implement the data mart which provides typical BW query performance.
I stayed away from setting the item as time dependent for these reasons.
Brian

BPC 10.0 - Time Dependent Hierarchy?

Dear All,
In BPC 10, is time-dependent hierarchy allowed/used?
Any pointers will be appreciated.
Thank you!
Regards,
Peri

Hi Peri,
Please, read here: Time dependent hierarchy with BPC10 NW - Planning and Consolidations Use cases
B.R. Vadim

Can I use my external HD for Time Machine and still use it for storage?

I have a 1TB external HD and my computer has yet to arrive. I was planning on backing it up via Time Machine and I'm wondering if my external HD will still be useable as a storage device once I pair it with Time Machine.
There's no way the backup will take up the full 1TB of space, so I'm hoping it doesn't just go to waste >.<

If you really only want backups of the current contents, don't use Time Machine.
It's designed to keep copies of things you've changed or deleted for as long as possible. This allows you an excellent chance to recover a previous version of something you changed or deleted in error.
It also allows you to revert your entire system to the exact state it was in at the time of any previous backup, even if that's a different version of OSX. It's rare, but if an OSX update, or installation of a kernel extension or 3rd-party app makes a huge mess, it's much easier and more reliable than rebuilding everything.
You might want to review the [Time Machine Tutorial|http://www.apple.com/findouthow/mac/#timemachinebasics] and perhaps browse [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum). See #1 there for size considerations.
For alternatives, see Kappy's post on [Basic Backup|http://discussions.apple.com/thread.jspa?messageID=12366915#12366915].

Time-dependent hierarchy in query selection screen

Hello all
I am running query where input selection has following fields -
Fiscal year variable ( e.g. i can enter 2008)
Period variable ( e.g. i can enter 12)
Hierarchy Node variable
The hierarchy is time-dependent. I want that if I enter year and period as 2008 , 12 then
my hierachy node selction pop-up should show me only that hierarchy structure which was valid in 12.2008.
But my hierarchy selection always shows me hierachy structure that is valid on current date.
Can anyone help me on how to achieve this?
I have already coded keydate variable based on fisc year and period. But then how to make use of this key date variable so as to get correct selection of hier?
Regards,
Sanjyot

Hi Marcio
RSRHIERARCHYVIRT is for maintaining time-characteristics hierarchy.
My hierarchy is based on Consolidation Groups and Units.
But the hier is time-dependent.
So I want that when selection pop-up opens for a hier node , it should show me correct hier depending on year and period i have enetered.
Regards,
Sanjyot

Consolidations Planning using BCS PCtr 'Entire Hierarchy time dependant'

Similar Messages

Maybe you are looking for