Symptom
A user who should have access to the ticket is unable to see it.
Environment
SAP Cloud for Customer
Reproducing the Issue
- Go to the Service work center
- Go to the Tickets view
- Search for Ticket 123 (Where 123 refers to the Ticket ID) that the user should have access to it based on the configuration
Result: Ticket 123 couldn't be found.
Cause
By a data corruption, if you see the Access context 5 for the user is 88888888888888888888888888888888.
To check the Access context 5;
- Go to the Administrator work center
- Go to the General Settings view
- Click Check User's Authorization
- Select the Business User XYZ (Where XYZ refers to the Business User ID)
- Enter the Business Object ID 123 (Where 123 refers to the Ticket ID)
- Select 118 - Ticket in the Business Object Type
- Click Go
- Check Document Access
- You see Access context 5 is 88888888888888888888888888888888
Resolution
Edit the ticket (e.g. To change the ticket status) and check the user's authorization again to see if Access context 5 is no longer 88888888888888888888888888888888.
See Also
access, restriction, access context, access context 5, 88888888888888888888888888888888, unable, ticket, visible
Keywords
KBA , LOD-CRM-SRP , Service Request Processing , Problem
Product
SAP Cloud for Customer core applications 2402