Академический Документы
Профессиональный Документы
Культура Документы
Community WIKI SAP Community Welcome, Guest Login Register Search the Community
Purpose
This document is a technical document, so it is only for the user with technical background.
Overview
Workflow is running is background, so when any issue, it is hard for user to analysis. The only appearance is no task received. And now, please follow this document to analysis. Because most of PC
workflows are triggered by Planner, so this document will start from Planner and then go together with other scenarios.
1 of 7 10/13/2017, 11:21 AM
Trouble Shooting - Workflow Item Not Triggered - Governance, Risk an... https://wiki.scn.sap.com/wiki/display/GRC/Trouble+Shooting+-+Workf...
PS: here, the job name is the guid for the planner. If you would like to find its name input from frontend. You can check table GRFNTASKPLAN and GRFNTASKPLANGRP.
The job status should be green. Or there should be something wrong, then please look at next chapter.
Input grpc into object, planner into subobject.And if we obtain the planner id from above chap, input it into external ID. And also choose the time restriction.
Green means all thing go well. If any red light, it means something wrong, and the message will supply more detail information.
From the planner log, we can also obtain the case id. See also the last line of the message.
From front chapter, in the planner log, we can obtain the case id. Input the case id into ’Creator’ object instance, and if you are experienced enough, you can also input ‘Creator’ object type and Event
as filter.
2 of 7 10/13/2017, 11:21 AM
Trouble Shooting - Workflow Item Not Triggered - Governance, Risk an... https://wiki.scn.sap.com/wiki/display/GRC/Trouble+Shooting+-+Workf...
We can see two events are triggered for this case. And this entry is wild event, because it is “No receiver entered”, which means after this event nothing happen. And the second entry works, and it is the
“CREATE” event. Just as its name, this event will create a workflow instance.
The best news for us is showing an Object Key, whose another name is workflow item id.
3 of 7 10/13/2017, 11:21 AM
Trouble Shooting - Workflow Item Not Triggered - Governance, Risk an... https://wiki.scn.sap.com/wiki/display/GRC/Trouble+Shooting+-+Workf...
System shows us the workflow log, where we can find the agent information.
Here we can check who received the task. If it is not as you expected, go to next chapter.
4. Agent determination
Different scenario may have different solution. However, most of them use the agentslot approach.
From the Business Event Name, it shows this is for “perform assessment“.
4 of 7 10/13/2017, 11:21 AM
Trouble Shooting - Workflow Item Not Triggered - Governance, Risk an... https://wiki.scn.sap.com/wiki/display/GRC/Trouble+Shooting+-+Workf...
From the Subentity, see also below F4 help, it shows it is for “Subprocess Design Assessment“.
From Role, it shows the role “cross subprocess owner“ will receive the task.
So, in one word, “cross subprocess owner“ will receive the task of “perform subprocess design assessment“.
Because authorization engine is able to clumb the master data tree to find recipient until getting one. So it is possible that a role in high level received the task on a lower level object. For example, we can
assign subprocess owner to perform control design assessment.
5 of 7 10/13/2017, 11:21 AM
Trouble Shooting - Workflow Item Not Triggered - Governance, Risk an... https://wiki.scn.sap.com/wiki/display/GRC/Trouble+Shooting+-+Workf...
Input the created date and time. And click execute or F8.
At last, choose the entry and click Restart workflow, to restart the workflow.
Related Content
Related Documents
6 of 7 10/13/2017, 11:21 AM
Trouble Shooting - Workflow Item Not Triggered - Governance, Risk an... https://wiki.scn.sap.com/wiki/display/GRC/Trouble+Shooting+-+Workf...
Related Notes
1621649 - Workflow Initial configuration
No labels
7 of 7 10/13/2017, 11:21 AM