CS_WF_SR_CANT_FIND_OWNER: Error in SERVEREQ workflow in TeleService because ex-employee is SR owner
(Doc ID 413344.1)
Last updated on JUNE 14, 2019
Applies to:Oracle Customer Support - Version 11.5.10 to 18.104.22.168 [Release 11.5]
Information in this document applies to any platform.
Why does the SR Workflow (SERVEREQ) is failing with the following message for a particular record:
The same workflow error occurs even after running Synchronize WF Local Tables concurrent program
Users not attach a workflow when defining a service request type, however they set up the notifications using the seeded notifiations rules through Customer Support > Setup > Servicerequest > Notification rules
Responsibility: Customer Support
Navigation: Customer Support -> Service Requests -> Create Service Request
1. Login as user affected by issue (for eg, xxxxx)
2. Customer Support(R)-> Create Service Request
3. Change the status of any SR where xxxxx is the SR owner
4. WF fires with the CS_WF_SR_CANT_FIND_OWNER error
When an SR is created and assigned to a specific employee (user1, userid = xxxxx, userid = 1111), or when he updates an SR, the system sends a CS_WF_SR_CANT_FIND_OWNER error.
The employee has a valid and active HR employee row, a valid and active userid, the person column is assigned to him, and he is an employee resource in CRM Administration.
The odd thing about the error message (see below) is that it refers to employee_id = 1111. There is no user with this number. If it refers to an HR employee row, it doesn't refer to anyone that handles service requests.
Workflow Administrator is able to rewind the workflow to the X step, and the error resolves, but leaves the workflow instances created in an Active state, not a Complete state as when assigned or updated by another employee.
However, a subsequent update to the workflow by the employee in question results in a new workflow error instance (same error message)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document