Question:
Hi,
I've a need to derive characteristic values from reference data.
reason for this is, end user don't need this information so these characteristics are not included in the level.
As these characteristics are not included in the level, these are left with blank when user saves planning data to planning cube.
Should I write an exit funciton or can I achieve this using "Reference Data : Characteristic Relationship".
This is what am trying to do..
let's say following data already exists in the planning cube for version 001.
MATERIAL VER SGRP
=================
MATERAL1 001 1234
MATERAL2 001 7890
where VER = Version & SGRP = Sales Group
let's say following data is being planned for version 002 without Sales Group.
MATERIAL VER
============
MATERAL1 002
MATERAL2 002
I expect the following records be stored into planning cube by deriving Sales Group from version 001.
MATERIAL VER SGRP
=================
MATERAL1 002 1234
MATERAL2 002 7890
Can I achieve this using reference data characteristic relationship or should I go for exit function?
Is there any documentation for Char Relationship? Can someone share your experience on this?
Appreciate your help
Answer:
Yes you should be able to use a Reference Data characteristic relationship to derive and post the Sales Group based on your transactional data.
Remember that you need to get your reference data selection in the char rel to select only that data your relationship is based on. Also, make sure reference data is unique for each combination.
Note also Note # 837716 which is short dump with this sort of relationship. we are having this problem at the moment.
Good luck!
Answer:
Matty,
I couldn't able to make it work.
Could you please share your scneario & how you are doing the same?
Appreciate your help.
Answer:
We did not get the scenario working, probably due to the problem in the note that I mentioned.
Since we no longer have a requirement for this type of relationship, I have not followed it up.
Check if the note applies to your system version and maybe raise an OSS note if it doesn't provide a solution.
Answer:
Hi,
Include the sales group in the level and as well as field to change .
It should work without the char relationship.
let us knowthe result.
Thanks
Sekar
BPS Consultant
Answer:
If we include Sales Group in the level, it will be visible to end users with a blank value which we wanted to avoid.
We can't even put sales group in the header where we have option of hiding it from end user.
that'z why, we don't want to include in the level but sytem has to derive it from reference data.