Undesirable impact of Std role 'Manager' while routing to occupied Position
As specified at the following link
A new entry was created in table T77S0 by using t-code 00V2, with the following values.
GRPID=WFLOW, SEMID=VAPOS, and GSVAL=X
So that vacant positions can be avoided.
We were successful to avoid routing at vacant positions, but ever since this has been configured, the relationship A 002 [Reports (Line) to] has lost its precedence in standard role Manager [t-code PFAC, role 00000157].
Before making the changes in T77S0, the Manager for any position X [whose relationship A-002 was maintained with another position Y which was not the Chief Z] was being correctly evaluated by the standard role 00000157 [Manager].
After the changes in T77S0, standard role 00000157 [Manager] is showing an awkward behavior by only returning the Chief Z of the org. Unit for that position X even though it has its relationship A-002 maintained with position Y.
Can anyone help to fix this issue, so that both the constraints can be simultaneously achieved i.e.
1. Routing to occupied position
2. Relationship A-002 should have its precedence over the Chief