Undesirable impact on 'Manager' role [t-code PFAC, role '00000157']

[kaukabr@yahoo.com]

I think you should use rule '00000168' instead of 157.
I hope this helps.
Cheers
--- K_Asim at ppl.com.pk wrote:

> Hi all,
> 
> As specified at the following link
> 
>
http://mailman.mit.edu/pipermail/sap-wug/2005-December/020717.html
> 
> 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'].
> 
> 
> 
> For example,
> 
>     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
> 
> 
> 
> (I am using SAP R/3 4.6c)
> 
> 
> Best regards,
> Asim Khan
> ' +92(21)111-568-568, Ext: 578
> 
> 
>
K_Asim at ppl.com.pk_________________________________________________________________________________________________________________________________________________________________________
> Disclaimer: The emails contains confidential
> information intended only for the addressee. Any
> unintended recipient of this email should delete it
> without copying , distributing or disseminating it's
> contents.
> The sender does not accept liability for any errors
> or omissions in the contents of this message, which
> arise as a result of email transmission. The user
> assumes the entire risk as to the accuracy and the
> use of this email.
> The company shall in no way be liable for any
> damages, whatever their nature, arising out of
> transmission failures, viruses, external influence,
> delays and the like.
> 
> 27/11/2007K_Asim at ppl.com.pkK_Asim@ppl.com.pk
> 
> > _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>