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

Similar Messages

  • 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

  • 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

  • Create CRM customer/account hierarchy node thru abap code

    Hi,
    Any one can help me on how to Create CRM customer/account hierarchy node thru abap code?
    Is there any Class/methods, FMs that I can use to create node in customer/account hierarchy?
    Sample codes will greatly help me.
    I hope someone can help me on this since this is my urgent requirements on my project.
    Thanks,
    james

    James,
    You can find the FM, Class Lib and APIs under the package BUPA_HIERARCHY.

  • 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

  • How to reduce the run time of ABAP code (BADI) when it is reading huge data from BPC Cube and thus writing  back huge data to the cube.

    Hi All ,
    In Case of reading huge amount of record from BPC Cube  from BADI code , performing calculations and writing back huge amount of data into the cube , It takes lot of time . If there is any suggestion to read the data  from Cube  or writing data into the cube using some Parallel Processing  methods , Then Please suggest .
    Regards,
    SHUBHAM

    Hi Gersh ,
    If we have a specific server say 10.10.10.10 (abc.co.in) on which we are working, Then under RZ12 we make the following entry  as :
    LOGON GROUP          INSTANCE
    parallel_generators        abc.co.in_10         ( Lets assume : The instance number is 10 )
    Now in SM59 under ABAP Connections , I am giving the following technical settings:
    TARGET HOST          abc.co.in
    IP address                  10.10.10.10
    Instance number          10
    Now if we have a scenario of load balancing servers with following server details (with all servers on different instance numbers ) :
    10.10.10.11   
    10.10.10.13
    10.1010.10
    10.10.10.15
    In this case how can we make the RZ12 settings and SM59 settings such that we don't have to hardcode any IP Address.
    If the request is redirected to 10.10.10.11 and not to 10.10.10.10 , in that case how will the settings be.
    I have raised this question on the below thread :
    How to configure RZ12  and SM59 ABAP connection settings when we have work with Load Balancing servers rather than a specific server .
    Regards,
    SHUBHAM

  • 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

  • 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

  • Creation of Time Dependent Hierarchy in R/3

    Any ideas on how to create a time dependent Hierarchy in R/3?
    Do we have any existing functionality we can leverage in R/3 for creating and maintaing time dependent hierarchy or through ABAP coding in R/3?
    Any ideas or documentation will be helpful.

    Hi Jasmine,
    check this documents/links to get an idea how to set up hierarchy extractor in R/3
    [How to Create a Hierarchy Extractor for Employees and their Department Managers|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20a709c1-0a8e-2a10-21b4-f779728c63bf]
    Re: Build Hierarchy with ABAP
    How to create datasource for hierarchy
    Double post: Creation of Time Dependent Hierarchy in R/3
    Regards
    Andreas

  • Modify code to pull the time dependent master data

    I fully under stand the suggestion below for the requirement to add the time dependent attribute comp code
    thanks fo rthe help but please tell me if there is a way i can modify the abap code and make the user enter the value for the date on which he want to pull th emaster data for company code or keydate to and from and pull the master data, so how will i proceede should i create the variable on 0doc_date and how to modify the code. please help . i have opened another question with same desc as above to assign points
    thanks
    soniya
    The literal within <..> is supposed to be replaced by the actual field name (as I didn't know the fields). In this case, I am changing your code for costcenter/company-code.
    data : wa like /bi0/qcostcenter.
    select single * from /bi0/qcostcenter into wa
    where costcenter = comm_structure-costcenter
    and objvers = 'A'
    and datefrom le comm_structure-<keydatefield>
    and dateto ge comm_structure-<keydatefield>.
    if sy-subrc = 0.
    result = wa-comp_code.
    endif.
    abort = 0.
    You can use this code for update rule of company_code. You have to replace '<keydatefield>' with a field name that contains the date on which the company is to be derived. If there is a date in your comm_structure (eg aedat) which you can use, you can specify that field in place of this literal (instead of comm_structure-<keydatefld> use comm_structure-aedat). If you have no such field, and you wish to use current date for getting the company code from time-dependent master data, you can use sy-datum (ie replace comm_strucutre-<keydatefld> with sy-datum).
    And it should work.
    The 'master data attribute' option is one of the options when you create update rule (one of the radio button options).

    That the code is doing anyway.
    If your txn data in the cube doesn't have a date, how does it know it is Feb data, or, it is March data?
    If it has a date or month field, you should modify and use this code to update the company based on that date instead of system date.
    Other than that minor variation, it is already doing what you look for.

  • Time dependent employee  hierarchy

    HELLO GUYS
    I Need HELP ON CREATING 0EMPLOYEE time dependent Hierarchy in bw using r/3 data. i am trying to bring r/3 hr organization chart which has employee hierarchy into bw. i am wondering if anyone did this using functional module or extractor
    please LET ME KNOW  the process .i am not able to get this using  ABAP  and i need help on this.

    Following document might be helpful.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20a709c1-0a8e-2a10-21b4-f779728c63bf?quicklink=index&overridelayout=true

  • Time depend hierarchy of 0profit_ctr (set calday on EXIT_SAPLRSAP_004)

    Hi,
    I would like to set Time depend hierarchy (not by nodes, but all hierarchy) on the 0profit_ctr. but unfortunately, 0profit_ctr is not time depend. So I would like to add calday on the EXIT_SAPLRSAP_004(cmod) on the source system.
    But I am no idea how to code it...
    what I would like to do is to set DATETO and DATEFROM of the hierarhcy header.
    parameter of the  EXIT_SAPLRSAP_004 is below.
    *"       IMPORTING
    *"             VALUE(I_DATASOURCE) TYPE  RSAOT_OLTPSOURCE
    *"             VALUE(I_S_HIEBAS) TYPE  RSAP_S_HIEBAS
    *"             VALUE(I_S_HIEFLAG) TYPE  RSAP_S_HIEFLAG
    *"             VALUE(I_S_HIER_SEL) TYPE  RSAP_S_HIER_LIST
    *"             VALUE(I_S_HEADER3) OPTIONAL
    *"       TABLES
    *"              I_T_LANGU TYPE  SBIWA_T_LANGU
    *"              C_T_HIETEXT TYPE  RSAP_T_HIETEXT
    *"              C_T_HIENODE TYPE  RSAP_T_HIENODE
    *"              C_T_FOLDERT TYPE  RSAP_T_FOLDERT
    *"              C_T_HIEINTV TYPE  RSAP_T_HIEINTV
    *"              C_T_HIENODE3 OPTIONAL
    *"              C_T_HIEINTV3 OPTIONAL
    *"              C_T_MESSAGES STRUCTURE  BALMI OPTIONAL
    *"       EXCEPTIONS
    *"              RSAP_CUSTOMER_EXIT_ERROR
    I guess I_S_HIER_SEL seems to me the hierarhcy header. but I could not find which fields of the TABLES are corresponding this hierarchy header.
    Or is it impossible to set what I want to do on this exit?
    Hope your help..
    Kind regards,
    Masaaki

    Hi,
    In this FM EXIT_SAPLRSAP_004..
    see include program...
    INCLUDE ZXRSAU04..
    Write code
    data : l_s_[structurename] like [extractstructure name],
    l_tabix like sy-tabix.
    case i_datasource.
    when 'your datasource name'.
    loop at c_t_data into l_s_[structurename]
    l_tabix = sy-tabix.
    fill the new field
    select ... into l_zz...
    where ....
    l_s_[structurename]-[new field name, zz....] = l_zz...
    modify c_t_data from l_s_[structurename] index l_tabix.
    endloop.
    Hope this Help.. assign points...
    regards,
    raj

  • 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

  • Why time-dependent not work for cost center and profit center hierarchy

    Has anybody been able to successfully turn on time-dependent for cost center hierarchy? Looks like the R/3 datasource 0COSTCENTER_0101_HIER is defaulted to be NOT time-dependent, and I don’t know how to change the R/3 configuration to enable time-dependent for this datasource.
    Here is what I found. If you go to RSA2 in R/3 and enter datasource 0COSTCENTER_0101_HIER, and then select "Hierarchy Info", you will see that all the time-dependent properties are unchecked by default. By comparison, Cons Unit datasource 0CS_UNIT_CSCU_HIER has “Version Dependent Hierarchy” as selected, and we are able to load Cons Unit hierarchy as time-dependent, but have no luck so far with the Cost Center hierarchy.
    Can any BI guru tell me how I can make time-dependent work for the cost center hierarchy?
    Thanks a bunch!

    Check SETLEAF and SETNODE.
    Basically CO Master data groups dont have seperate tables. They will be available in above tables. Choose proper Set class to filter the results

Maybe you are looking for