Can you suggest an Evaluation Path for this output?

[Mithun_Kumar]

Hi Friends,

I'm new to HCM and not sure about the evaluation paths. Tried my hand in OOAW with some understanding, but not really able to achieve the desired output from the FM RH_STRUC_GET.

My Org Hierarchy (Sample) is like this:

Please ignore the 'US' entries in this.

The output from the FM above, required is something like this: (Basically, it's a bottom up reporting line starting from the input user, and we need the position 'S' and 'P' (or 'US' if possible), in the bottom-up order.

Input could be either a 'US' user.

Can anyone please suggest if any standard eval path already provides this output? If not, can you suggest the eval path that I can create to achieve this?

PS: The closest I could get with some trial and error Eval Path:

Is like this:

But I'm also getting unwanted positions due to them being at the same level.

Please help to refine or change entirely, to achieve the output I mentioned above.

[Tenorio]

Mithun Kumar if you need the object: user "US" to be shown in your report, you have to take into account that it is necessary to create a record in infotype 105, to be able to read it in OM reports.

When you want to modify or create an evaluation route it can work from the highest or lowest level, all this depends on the way you take the links "from A to B or from B to A". If you use HCM report S_AHR_61016528, you can choose the different evaluation paths of the standard system. When you run the report, in the evaluation route section, you can choose the evaluation route depending on the main object for query, here you can review the routes you have available depending on the object for which you want to consult.

[Mithun_Kumar]

Thanks tenorio .

The report you mentioned as the same as transaction PPST. I do check the eval paths in this.

The infotype 105 is also maintained, so that part is not the issue.

Anyway, after a lot of trial and error I've finally realized that my requirement is not met with a single eval path, due to it's recursive nature by default. So now I'm using 2 separate eval paths, P-S-O-O and MAN_O called separately in ABAP code, to achieve my requirement.