Question:
Hi,
we would like to avoid use of flat file for building our employee hierarchies based on self-defined org. unit.
We actually have an HR table for our staff ID and its org. unit assignment (we have it in our BW employee master data as well where org. unit is an attribute).
What is the best way to build a hierarchy automatically where staff ID would be the child and org. unit being the parent (source might be R/3 or BW master data).
We would like to avoid the use of flat file and we would have multiple employee assignments like cost center etc...
Thanks
Answer:
perhaps you could use nice a function, I found yesterday, while searching for the differences between 2.0 and 3.0.
I try to explain:
in query definition, you can put several characteristics for example in the rows.
Put your staff_id and your org_id there directly- without a structure.
then - in the header, where you can read "Rows" and where you click for "New Structure", you find an item in the pop-up called "display as hierarchie" or something like that.
than, all the characteristics in that box are displayed like that.
try it and let me know...
Rello
Answer:
Thanks rello,
it works fine and it will help for sure...
The question was more on the extraction/infosource build process in order to handle multiple hierarchies over time...
We could play with the key data as well in bex.
Thanks,
Ph.