Question:
Hi,
Anybody face problems with the exit which is supposed to derive characteristics.
I have a function whereby I copy Actuals from a Base cube to Plan in a transactional cube. In the derivation rule I derive certain characteristics from the Profit Center. These characteristics are not in the Planning Level.
When I do a Manual Planning these characteristics are derived properly. However when I use a function eg. the copy function described above the derivation rule is not hit.
Any ideas / suggestions are welcome.
thx
Atw
Answer:
Hi,
I think you have have your characteristic that is being derived in your planning level. Characteristic relationships only derive if it is not in the planning level....
Cheers,
Mary H
Answer:
Hello,
I am using ch derivation (based on atributtes) and both ch are in the level. It works fine!
It makes sense that ch are in the level - all functions that belong to that level only apply to those CH and KF...
_________________
SemWave
FI/CO/SEM Consultant
Answer:
According to the BPS Help pages on help.sap.com:
A characteristic relationship, which supports the derivation of values of the target characteristic, can only then achieve the defined derivation when the basis characteristic but not the target characteristic is contained in the planning level. Otherwise the effect of the characteristic relationship on the combination check and proposal is limited.
Are you using your characteristic relationship to derive values or to chek valid combinations?
Answer:
Hello Fans,
This topic is very useful for me...
In my case, I have a combination check and derivation of a Ch from Material Sales (0mat_sales).
Since i need material and its attribute to be presented in the layout I have to include both in the level/package (no selection for material).
But - I must agree with Guille - probably the system is not deriving but only checking....
Anyway I would like to understand better atw problem:
- does it make sense to derive the characteristic from Profit Center? Since you are copying between two cubes, we assume that the metadata is equal and consistent. Therefore, you should not need to derive in the first place.
Bye,
Answer:
Hello Fans,
This topic is very useful for me...
In my case, I have a combination check and derivation of a Ch from Material Sales (0mat_sales).
Since i need material and its attribute to be presented in the layout I have to include both in the level/package (no selection for material).
But - I must agree with Guille - probably the system is not deriving but only checking....
Anyway I would like to understand better atw problem:
- does it make sense to derive the characteristic from Profit Center? Since you are copying between two cubes, we assume that the metadata is equal and consistent. Therefore, you should not need to derive in the first place.
Bye,
Sorry, it was me posting withou log on...
_________________
SemWave
FI/CO/SEM Consultant
Answer:
Hi,
It worked like this - you have to ensure that any of the DERIVED characteristics are not there in the Planning level.
with regards
Atw
_________________
boonchai
Answer:
Hi,
I think delivered functions behanve the way u said, i.e they only work on chars defined on the planning level, when it come to manual we are over riding the way things should work so it can acess other charecteristics.
Manu
biwcafe@yahoo.com