Planning Function & Characteristics Relationship

[former_member210674]

Hi Experts,

I need a help in some basics of Planning functions.

We have a Planning cube on which several aggregation level built. Among them only one aggregation level (say example ALVL1)has an additional InfoObject (Say example CHSBS)which is used as changeable object in the Planning function created over ALVL1.

Since the infoObject CHSBS not included in other aggregatoin levels we have written a Characteristics relationship to derive the value. Now the Planning function on ALVL1 is not running as the InfoObject is being changed by both Planning function and Characteristics Relationship.

My questions is as below:

Is there any possibility that we can change value of an InfoObject by both Planning function and Characteristics Relationship ?

or

Is there any document which explains changeability of InfoObject by both Planning function and Characteristics Relationship is not possible ?

Thanks,

Gopi R

[Former Member]

Hi Gopi ,

I am not sure i understood your question.

When characteristic relationships is activated this means that the target characteristic can have only 1 result either by characteristic relationships or by lanning function in both cases it is validated against the same possible value (in planning function you will recieve an error if the value is different from CR ).

Now are you asking if you can set a different logic for the target characteristic from CR and planning function?

Eitan.

[former_member210674]

Hi Eitan,

We have implemented the same logic in Planning function and in Characteristics Relationship(CR). But while running the Planning sequence it got failed. When we make CR inactive then the Planning sequence works fine.

Thanks,

Gopi R

[Former Member]

Gopi,

Your CR is cutomer exit? in the CR settings try to change the EXCL # setting

Regards,

Eitan.

[former_member210674]

Hi Eitan,

Thanks for your reply.

Yes, I am using Customer Exit. But from your previous answer I could understand that the Infoobject can be filled either by Planning function or by CR..Is by understanding right ?

Also I will try the option Exclude # and let you know..

Thanks,

Gopi R

[gregor_dieckmann]

Hi Gopi,

a planning function is linked to an aggregation level. Thus a planning function is responsilbe to handle all characteristics of the aggregation level. Characteristics relationships will be used to check the consistency of the records. You cannot fill a value of a characteristic contained in an aggregation level with a characteristic relationship.

But you can fill a value of a characteristic not contained in an aggregation level with a characteristic relationship of type derivation.

Depending of the aggregation level and the characteristics used in relations the system decides whether a relation can or has to be used for a 'check' or a 'derive'.

The 'EXCL #' has nothing to do with this topic.

Regards,

Gregor

[former_member210674]

Hi Gregor,

Thanks for your inputs. In my one of the Planning functions (Fox Formula) the infoObject is checked as changeable and for the same Object a Characteristics Relationship (customer exit) derivation is maintained in underlying InfoCube.

In other Planning functions the same InfoObject is unchecked for changeable characteristics and that planning function works fine with the Characteristics Relationship derivation.

So from the above analysis I could understand that characteristics value can not be changed by Planning function and Charateristics relationship at a time. Please correct me if my understanding is wrong.

Thanks,

Gopi R

[gregor_dieckmann]

Hi Gopi,

I think the misunderstanding comes fact that we are talking about different topis using the same word 'changing'.

Characteristic Relationships:

The 'check' and 'derive' methods work on a record basis. 'Check' checks whether a given combination of characteristic values are consistent with characteristic relationships. This is done for characteristics used in the current aggregation level. 'Derive' takes a record and fills characteristic values for characteristics not contained in the aggregation level. The characteristics used in the aggregation level are the sources for derivation.

Planning Functions:

The characteristics used in the aggregation level split in two kinds of characteristics

- characteristics to be changed

- and the complement with respect to the aggregation level, i.e. the block characteristics

The algorithm of a planning function is call per packages; in a package the block characteristics are constant. In a block only the non-block characteristics can be 'changed'. But here 'changed' means a different thing. In a planning function you can only change key figure values of existing records or create new records. You cannot change a characteristic value in a given record!

The output of a planning functions is a set of records. These records then are checked for consistency with respect to characteristic relationships.

Regards,

Gregor