How to use different evaluation paths within 1 scenario?

[Former Member]

Hello SRM'ers,

I have a question concerning the inheritance of attributes in the org. structure (PPOMA_BBP)...

Currently, we have specified evaluation path EBP-DOWN in the scenario BBP, which means that inheritance starts at the top root, from object O to object O and from object O to object S.

However, we would like to adjust the inheritance behaviour of one attribute (CNT) in the scenario BBP, so that it can only be inherited from object O to object S (the other attributes in the scenario should stick to EBP-DOWN)

Does anyone have experience with this? Can we use the Check FM on the scenario for this?

Thanks!

Elisabeth

[Former Member]

"Check FM" is to check and evaluate whether the value is permitted or not, we can't change values. Example -'RH_OM_ATTRIBUTES_VALCK_EXAMPLE' .

Why can't we try to change the Inheritance type to "O" in T77OMATTR in SM30, against to Cost Center attribute.

All the best,

-Vamsi

[Former Member]

Hello Vamsi,

Thanks for your reaction, but unfortunately the O-setting doesn't exactly do what we would like. With that setting, attributes are either inherited OR you have to maintain them manually (as soon as you maintain anything manually in an attribute, the inheritence is deactivated)

We actually need a combination of inheritance and manual maintenance:

• a user must inherit the cost centre (only) from the org. unit he/she directly belongs to AND

• it must be possible to manually add other cost centres

The problem with the O-setting is that if we manually add cost centres, we also have to manually (re-)add the cost centre of the org. unit he/she belongs to.

Moreover, updating cost centres on org. units is a completely automatic process in our system, so if the cost centre on the org. unit changes, it's not updated automatically in the user's attributes...

Do you have experience with that situation?

Kind regards,

Elisabeth