User ABC (ABC represents the user name) is able to see tickets assigned to user XYZ (XYZ represents the user name).
SAP Cloud for Customer
Reproducing the Issue
Logged in with user ABC, go to the Service work center.
- Go to the Tickets view.
- Restrict field Assigned To = user XYZ.
- Some tickets appear.
User ABC belongs to Org Unit 123 (123 represents the Org Unit ID), and can see the tickets assigned to him and the Org Unit.
All the tickets assigned to user XYZ have a third user DEF (DEF represents the user name) assigned as an involved party. User DEF was part of Org Unit 123, however this assignment was deleted on a past date.
In tickets, the Employee and his/her Org Unit is always written in the access context. After master data changes (for example: Org Unit, Product...), transaction data (for example: ticket) will not be updated automatically. When these tickets were created, since user DEF was part of Org Unit 123, all the tickets also have its access context. User ABC being part of Org unit 123, is also able to see those tickets.
Any change made to the tickets re-determines the access context again, and the changed ticket will not be seen in user's ABC list. For example, adding an attachment to the ticket.
ticket ; access restrictions ; access context ; org unit , KBA , LOD-CRM-SRP , Service Request Processing , How To