Wrong data in cube for time dependent nav attribute

Hi Experts,
I am facing a strange problem.
One of the navigational attr used in one cube was not time dependent before.
Now we have changed it to time dependent.
But after that the cube is fetching wrong data for the nav attr.
In the Master data table (Q table) data is fine.
Kindly suggest.
Regards,
Debjani

Hi Debjani,
As Federico said, when you display the content of the cube (or when you execute a query) you enter the reference date on which the time-dependant attribute will be searched. This unique reference date will be used whatever the cube data is.
Ex :if the reference date is 2010/02/14, you will have the time-dep attribute value for 2010/02/14,for 2011 data, 2010 data or whatever.
If you want to change dynamically the reference date depending on a date on the cube, things become a lot more difficult. The only possibility I can think of is "virtual characteristics" (you will find a lot of litterature on the subject on sdn).
Regards,
Fred

Similar Messages

  • Error activating 0person - Time dependant Nav attribute

    Hello,
    Theres a Custom made XObj (navigational attribute) for 0person which is <b>time dependant.</b>
    I have removed Check for "Time dependant" and saved & activated.But the object became inactive.Again i have placed the check for "Time Dependant" then the object is not getting activated.
    Removing of Check for time dependant navigational attribute has created inconsistency in the table.
    Now how to over come this ? somebody pls throw light on this ?
    How to repair the table ?? and how to analyse the table by comparing the ABAP Dictionary version with the database version ?
    Its urgent.
    Regards.

    Hi,
    The problem is resolved by myself.
    Just follow the instructions provided in the note :408317.
    Also observe the instructions in the note:325296 if you observe if theres any conversion lock on your info onject.
    Regards
    Ellora

  • 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

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

  • Best practices for loading apo planning book data to cube for reporting

    Hi,
    I would like to know whether there are any Best practices for loading apo planning book data to cube for reporting.
    I have seen 2 types of Design:
    1) The Planning Book Extractor data is Loaded first to the APO BW system within a Cube, and then get transferred to the Actual BW system. Reports are run from the Actual BW system cube.
    2) The Planning Book Extractor data is loaded directly to a cube within the Actual BW system.
    We do these data loads during evening hours once in a day.
    Rgds
    Gk

    Hi GK,
    What I have normally seen is:
    1) Data would be extracted from APO Planning Area to APO Cube (FOR BACKUP purpose). Weekly or monthly, depending on how much data change you expect, or how critical it is for business. Backups are mostly monthly for DP.
    2) Data extracted from APO planning area directly to DSO of staging layer in BW, and then to BW cubes, for reporting.
    For DP monthly, SNP daily
    You can also use the option 1 that you mentioned below. In this case, the APO cube is the backup cube, while the BW cube is the one that you could use for reporting, and this BW cube gets data from APO cube.
    Benefit in this case is that we have to extract data from Planning Area only once. So, planning area is available for jobs/users for more time. However, backup and reporting extraction are getting mixed in this case, so issues in the flow could impact both the backup and the reporting. We have used this scenario recently, and yet to see the full impact.
    Thanks - Pawan

  • 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

  • What exactly is Update method Master data attrib with a Time dependency ?

    Hi Experts,
    I have a Update rule in which i have an Update Method  "Master Data Attrib of " with Time dependency
    basically we are loading (update rule of )   0PAYROLL AREA ,
                  at Master data attribute of  we have 0EMPLOYEE
                  at Time Dependency When reading Master Data  END radio button is checked
                  frm it is mention as 0CALDAY.
    please explain what is function of 0calday here?
    I understand that 0PAYROLL AREA is a attribute of 0Employee and since from R/3 we are getting only 0EMPLOYEE so we are filling it from 0employee but  what is the significance of 0CALDAY here?
    Regards,
    RG

    Hi RG,
    It fills the valid value of 0PAYROLL for a particular 0EMPLOYEE in a particular time frame.
    Elaboration.
    Say  Employee          Payroll                  Valid from          Valid to
            RG                    1000000                 01.01.2007        31.12.2007
            RG                    2000000                 01.01.2008        31.12.2008
            RG                    3000000                 01.01.2009        31.12.2009
    The if your transaction data has RG employee in it with a transaction on 0CALDAY = 12.05.2007 then the valid payroll at that time would be 100000.
    On Calday 05.05.2009 your payroll would be 300000.........
    So for different days different payroll values would be valid.
    You require calday to find out which payroll value is valid in the timeframe of a transaction.
    In your update rule it is bringin the value of valid attribute value for the time of the transaction.
    Hope it helps,
    Regards,
    Sunmit.

  • Real time Example for Time depend Characterstics...

    Real time Example for Time depend Characterstics.
    In which Situation we have to swith to time dependent.

    hi ,
    for ex. employee designation which changes over a period of time but not frequently , also headcount and also stock etc .
    which is related to change over a period of time .
    regards .... kumar Sarvepalli ///// honor points if helpful

  • Wrong data in Cube

    I am getting data from two ODS(Budget and line items) flowing into Infocube....There are wrong results displayed in the report due to wrong data in cube...what are the best options to go ahead in such situations??

    Hi Shreya,
    If the data is wrong in the cube, but correct in the ODS then you need to check the update rules from the ODS to the cube to see how the data is being mapped. If you have any code in the update rules, you can try to debug the update them from the monitor screen. Is the data being doubled?

  • Time dependent navigational attribute

    Hi all,
       I am new to BW, i would like to know what is time dependent navigational attribute and when we go for it.
    with regards,
    a.fahrudeen

    Hi Fahrudeen,
    You will go for a time dependant nav attr when the attribute values change with time and you need to maintain the history. When you use time dep nav attr, the value is always valid from a date to a certain date. Like for 0COSTCENTER, 0RESP_PERS is a time dependant attr becasue it is possible that for the same costcenter ABC was responsible person from 01.01.2004 to 12.31.2005, and then you have XYZ from 01.01.2006 till 21.31.2008.
    Hope this helps...

  • Time Dependent Navigational Attributes in Query

    Hi,
      Location & Job are the Time Dependent Navigational Attributes of an Emp No and
    Created a Info Set (outer Join) based on Emp No and DSO....
    Created a Query based on the infoset and the Location * Job are Free Chars in the report
    In the query property setting entered KEYDATE as 31.12.999
    When i executed report and drilldown on Job or location it is displaying me 2 records for each employee one with Blank and the other with information.....
    It should display only one record..most recent record avaliable in Emp master data
    Where was i doing wrong

    Hi,
    Thanks for the update.
    I can't do a innerjoin as per my requirment it should be a outer join
    Thanks

  • Bex Report for time dependent master data

    Hi Gurus,
    I hav created a report based on a mutliprovider having 1 DSO and 2 CUBEs with has a common characteristics 0SALEEMPLY which is timedependent master data
    it has following records
    Validfrom===== To======== SE == Division
    05.05.2006 ===14.10.2007 == 709== 32
    15.10.2007 ===19.10.2007 == 709== 33
    20.10.2007 === 31.12.9999 ==709 ==34
    In report wen i fetch the data month wise it shud show the division(time dependent) according to its validity in master data
    But in my report it shows division 34 in all the months
    what is wrong here and do i need to hav any restriction at query level ?

    Hello Experts,
    please update

  • Bex query-KEY date for time dependent objects

    Hi
    I have one infoobject called 0customer that has one time dependent attribute .called status. I would know how the system works in the following senario for the a given key date(which in bex properties).
    question 1)
    customer todate          fromdate    status
    1            20071231     20070101     Y
    1            20081231     20080101      N
    1            20091231     20081101      X
    can the data in the infoobject be overlapped? is the 3 rd record is  valid in the above example - as months(11&12of2008)  overlapping with second record? ? pls advise
    question 2)
    customer todate          fromdate    status
    1            20071231     20070101     Y
    1            20081231     20080101      N
    1            20091231     20090101      X
    If the keydate is 20080201 which record will it return?would it return the record that has status 'N'?
    what does the keydate is compared against? is it with from date or todate or between fromdate and todate? does the query return only one customer record for a given customer when it runs in the query?
    Please advise.
    Thanks
    Vennela

    1) Normally you cannot activate the data with this constellation. If you have inconsistent master data you can repair with transaction RSRV.
    2) The system returns N for key data 20080201.
    Best regards
    Dirk
    Edited by: Dirk Herzog on Nov 19, 2008 1:16 PM

  • Combining records for time dependent master data

    Good Day,
    We have a characteristic with turned on time dependency for master data.
    Bringing in data from the source generated a number of entries for the master data.
    Here is an example:
    Line 1: [Date 1] - [Date 2]
    Line 2: [Date 2] - [Date 3]
    Line n: [Date x] - [Date y]
    Any thoughts on how we can converge/aggregate Line 1 through Line n for the history, so that we have
    Line 1: [Date 1] - [Date y]...
    and then, going forward we can, use time dependency for any changes to master data that might come up.
    Thank You for your input,
    Dmitriy

    Hi Dmitriy,
    As far as I know, it is not possible, unless you delete the master data and reload.
    I don't think you will be able to delete the master data at this stage, because it will not possible to delete the master data without deleting the transaction data.
    Thanks,
    Krishnan

  • 0CALDAY for time dependent master data lookup unknown when migrated to 7.0

    I am in the process of migrating a number of InfoProviders from the 3.x Business Content to the new methodology for BI 2004s.
    When I try to create a transformation from the Update Rules for 0PA_C01, all of the rules that use a master data lookup into 0EMPLOYEE give me the error such as "Rule 41 (target field: 0PERSON group: Standard Group): Time char. 0CALDAY in rule unknown". 
    How do I fix the transformation rule that is generated from the update rule for these time-dependent master data attributes?

    Hi Mark,
    look at http://www.service.sap.com/. I guess you need to implement some corrections or newer supp-packages.
    kind regards
    Siggi
    PS: take a look: https://websmp104.sap-ag.de/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=941525&_NLANG=EN
    Message was edited by:
            Siegfried Szameitat

Maybe you are looking for