

Re-triggering of the workflow should happen in SAP. If that is the case, you can still do the same approach or do the approval in the portals test environment. This means that they have little to zero SAP intervention when they execute approvals. For example, the use of Web DynPro Applications. Take note that there are some businesses that have a separate portal for the approval proper of VIM Documents. Note that this is automatically scheduled in the SAP System to run once daily.
OPEN TEXT WORKFLOW CODE
If you still encounter the same error, go to Transaction Code SWU_OBUF to Start Synchronization. If you encounter another error such as “no administrator found for this task”, click on Settings > Workflow Settings > Refresh Organizational Environment. Just locate the Document Number in concern and click on the Execute Button to approve. If you are sure that the workflow structure is accurate and the updates have been executed correctly, you can go to Transaction Code SBWP (another alternative is SO01) to proceed with the approval. This is usually seen in test environments. Most common error is the Error Executing Workitem in VIM Workplace. You might encounter an error during approval. Additional Information No Administrator Found for this Task / Error Executing Workitem If it is in Posted status, you should find the corresponding Document Number generated (highlighted in yellow).

The document status should now be updated from “Awaiting Approval” to “Posted”. Once all approvals are complete for the document, you can go back to VIM Analytics or click on the refresh button if you still have the screen open. You can then proceed with the approval proper.
OPEN TEXT WORKFLOW UPDATE
Your VIM Workplace screen should update to show the Other Users View. Going back to the VIM Workplace, you can click on the Switch Work View Button, Select Other Users View, Enter the User ID, then click on the Check Button. Here you can search for the Approver and enter your User ID as a Substitute. To proceed with Approver Substitution, go to Transaction Code /ORS/MAIN_SUBS. Proceed with Approver Substitution (if necessary) and Continue Approvals in Workplaceġ. You can take note and click on the Continue Button. If there is a following approver, you should see it in the approve confirmation screen. After selecting the narrowed down result and clicking on the execute button, click on the Approve button.Ĥ. Filter the Document ID accordingly so the results would narrow down.ģ. In the screenshot below, I have closed the Selection Pane and Detail Pane.Ģ. If you are testing or doing the actual approval, go to Transaction Code /OPT/VIM_WP. You should get a notification saying that the event was created. Click on the Object Key button, enter the Document ID / Document Processing Number in concern, then click on the Check button.ģ. To proceed with the workflow reset, create the event by going to Transaction Code SWUE and entering the details below:Ģ. Verify the Document Status prior to the workflow reset.

Go to Transaction Code /OPT/VIM_ANALYTICS and enter the Document Processing Number in concern.Ģ. Proceed with Approver Substitution (if necessary) and Continue Approvals in Workplaceġ.As such, please do the necessary checks beforehand. Note that this post will not cover additional validation and testing that need to be done prior to the re-trigger. This is most likely done in test environments to cover some test cases but it can be utilized in production as long as it is done with caution and the issue requires the reset workflow approach. There might be cases that will prompt you to retrigger or reset a workflow approval in OpenText VIM.
