Skip to Content

Variable for key date for char derivation depending on version

Hi all,

I want to write data records for budget and forecast within the same planning cube.

some characteristics shall be derived from time dependent navigation attributes. Therefore I need to define a key date that fits to the version

- for budget I want to use the 01.01. from planning year

- for forecast I want to use the 01. of the current month (current date might also do)

Did anyone ever use the key date like this - depending on the version?

Could we implement a variable that delivers for each data record it´s own key date depending on the version that is included in the data record and then use standard attribute derivations?

Or should we rather leave the key data as current date but define an exit derivation, that is reading the correct time dependent attribute value depending on the version?

thanks for your ideas


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Aug 23, 2017 at 12:49 PM

    Hi Cornelia,

    the planning key date used in derivation is fix in the user session. What you need is to determine the key date (to be used for the attribute lookup) from the record. You need an exit implementation for this. You can check the standard implementation in class CL_RSPLS_CR_MASTER_DATA but this class uses a factory GET_INSTANCE where I_DATETO is not part of the 'key' to reuse already existing instances.



    Add comment
    10|10000 characters needed characters exceeded

    • Hello Gregor,

      to clarify our requirements: we have one cube on which we plan both forecast and budget. In the planning query, we have a customer exit variable, in which the planner can enter the planning year. This planning year should determine the master data key date and does so already for the query key date. Depending on whether the planning year variable is for FC or budget, the key date is 01.01. (budget) or 31.12. (FC) of the planning year.

      If I understand you correctly, I need to retreive the entered value from the year variable and then call the CL_RSPLS_CR_MASTER_DATA->GET_INSTANCE in the FM of our variable determination (Step 2) and the returned instance will be used for the validation?

      Thanks and kind regards, Jochen