cl_rsplfa_plan_buffer in IF_RSPLS_CR_METHODS~DERIVE

[Former Member]

Hi

I have a requirement to derive a date characteristic from a key figure value in Integrated Planning.

I put the characteristic as derived, but then the default class (based on CL_RSPLS_CR_EXIT_BASE) does not give me access to key figures from my aggregation level.

I thought I would be able to get to them via the planning buffer, using cl_rsplfa_plan_buffer, but when I call the read method get_data I get a short dump because cl_rsplfr_controller=>p_r_area IS NOT BOUND...

Is there a way to read the planning buffer in the derive class?

Regards

Yann

[gregor_dieckmann · Accepted solution]

Hi Yann,

in the interface of a characteristic relationship you only have characteristics, so even if you manage to read the buffer data it would not be possible to move change any key figure value in a derivation exit.

Your scenario seems to fit to 'attribute planning', i.e. to the feature 'characteristic as key figure' available since BW 7.40, SP08. To use it you have to use direct-update DSOs (in 7.50 you can also use direct-update advanced DSOs). The 'trick' here is that the characteristics are in the data part of the DSO (no key fields) an can be exposed as key figures in the query. You can also use derivation here since your 'source date' is a characteristic and also the target date.

Check the following:

https://help.sap.com/viewer/0ecf5244825c4742a7b062a89d11c2ac/7.5.10/en-US/5b86e6a1bd1642dea95b14daa3...

and

https://help.sap.com/viewer/0ecf5244825c4742a7b062a89d11c2ac/7.5.10/en-US/c8555caa741b4777b0a228e82d...

Regards,

Gregor

[Former Member · Accepted solution]

OK, thanks for the feedback.

[Former Member]

Hi Gregor

I saw that the standard derivation is based on characteristics only, hence my attempt at reading the planning buffer from the derivation class to get "access" to the key figure values.

The use case is as follows: changign characteristics values in IP is cumbersome, as basically this means a repost of the record. We are planning a "workaround" by using key figures for dates. In our model our characteristics are enough to define a single key for a record, so we can use key figures for dates, so that the user can input 20180102 for example.

Our planning data is initiated by a base calculation, where we can generate a "calculated date" as characteristic that we don't show the user, but that we use in the background for example for copies.

Now the problem is when the user creates brand new records - we'd like to derive, in the background, the calculated date from a specific date key figure that the user has to fill in when creating a new record. What to do when the user changes the date afterwards is another matter 🙂 - first if we are to go down that route we need to get access to the key figure value when deriving the characteristic. I tried to call the planning buffer class in the derive class, but it throws the error I mention above. Obviously the alternative is to have this calculated date as characteristic in the input layout and basta, but I wanted to explore this key figure access topic, just in case.

Regards

Yann

[gregor_dieckmann]

Hi,

derivation in characteristic relationships is based on characteristics, key figures are not supported. You can see this already in transaction RSPLAN where you have to choose source and target characteristics.

From the data model it would also be strange to 'derive' a characteristic from a key figure since a characteristic is a 'key' and then may lead to new records: this makes no sense e.g. in direct-update DSOs.

This use case is not clear.

Regards,

Gregor