Problem with Planning Functions on Standard ADSO with Change Log

[former_member867156]

Hello.

We are having a problem while running planning functions on a Planning-Enabled Standard ADSO with Change Log.

Every time we try to run even the most simple Copy function through RSPLAN, it shows the following message:

So, Infoprovider is a Planning enabled standard ADSO with change log, used as partprovider on a composite provider over which my aggregation level is created. Composite Provider has 2 part providers. Every day stuff.

The field which the message is calling an "attribute" is just a non-key characteristic (date 😎 in the ADSO. If I remove it from the aggregation level (just testing) the same message will show, with the next non-key field it finds.

- I was not able to find any info regarding RSPLS_CR076 message anywhere.

- The ADSO is in Planning mode. Triple checked.

- I swear I remember planning on standard ADSOs without any kind of trouble, but now I doubt everything as this is a very specific and controlled error message.

- I have found no information at all regarding any such limitation (that is, not being able to plan on non-key characteristics in standard ADSOs with change log).

- I cannot change it to a Data-Mart ADSO.

BPC Embedded version is the following:

Thanks a lot.

[gregor_dieckmann]

Hi,

the whole planning function design treats characteristics as key fields, e.g. a copy function usually creates new data records based on the copy from -> copy to rule. A non-key field characteristic C (this is called attribute in the message RSPLS_CR076) would break this rule since 'new' records are determined by the key fields only.

E.g. having key characteristics A, B and a record (a1,b1) with a copy rule b1 -> b2 would create a new record (a1,b2) where the attribute value in the first record fully determines the attribute value in the copied record.

In other words, non-key characteristics have to be treated in the same way as key figures and this is why such a characteristic C can be exposed as a key figure 1KYF_C only in the aggregation level. This is another reason why non-key characteristics would lead to problems in planning functions as the same 'object' could be 'changed' as C or in the role of 1KYF_C.

Summing up, C is not of any use in a planning function, in the copy case it would be anyway fully determined by the real key characteristics. So remove it from the aggregation level as characteristic. To change non-key characteristic value expose 1KYF_C in the aggregation level ('characteristic as key figure').

Regards,

Gregor

[former_member288457]

Hi Daniel

We are experiencing the same issue.

I found this note 2636614 - Constant characteristic in the key of a plannable DataStore object (advanced) - SAP for Me which we still need to apply and test whether it is applicable to us as we are on

DW4CORE 200 0014 SAPK-20014INDW4CORE DATA Warehouse

I hope this is of use.

Regards

Marthinus Viljoen