Org Unit with more than one Chief Position

Question

Hi,
we have implemented MSS via the portal using a one-to-one relationship between Org Units and Chief Positions, and we would now like to have multiple Chief positions attached to one Org Unit.
As far as I can tell from the SAP documentation, this should be straightforward, but the results we are getting do not seem correct.
I have an Org Unit that has position 1 and position 2 assigned to it with relationship A/B 012 denoting that they are Chief Positions.
User 1 is holder of position 1 and user 2 is holder of position 2. 
Both users have the same security roles.
The views used on the portal are configured using the MSS Object and Data Provider functionality, using the standard ORGEH view, evaluation path for root objects SAP_MANG and evaluation path objects SBES.  The checkbox 'Excl. Managers' is ticked.
The problem is this - both users can see all the subordinate employees in the Org Unit when they log on to MSS but user 1 can also see user 2 in his list of employees, which is not correct as user 1 and user 2 are both chiefs.  User 2 cannot see user 1 in his list of employees, which we would expect.
The only logic we can see for user 1 being able to see user 2's details is that user 1 must be somehow defined as the 'superior' Chief Position, but we have not defined this as far as we know.
Any ideas as to why this is happening for us?
Many thanks,
Fran.

Answer 1

Hi Fran,
Sounds like you have set up the reporting structures and MSS properly.  I do question why two chiefs for one org unit.  As you stated, both can see all employees and so both can approve time, give pay increases, etc. without the approval of the other.  If this is want you want, then you have set it up properly.  Usually, one has to approve the actions of the other, thus, is in a superior relationship.  This can be handled by having a higher level new org unit with the higher person as chief and the lower stay as head of the lower org unit which reports to it. 
As you have it now, both individuals have the same rights and access.  They should both be excluded from iViews if you checked the "Excl. Managers" box.  Since, you just recently made one a manager, have you checked for any date dependencies?  If the Chief #1 is selecting a view for "Current Year", for example, he would be able to see all persons who reported to him for this year, which includes Chief #2.  There are no 'superior chief' designations (except by structure), so without being able to view your configuration, my suggestion is to check all dates for the assignments and relationships vs. dates of the view.