SAP VIM workflow

[Former Member]

Hi

I have an issue with the VIM (vendor invoice management OpenText) work flow. A DP document is being processed and the report shows the task process control as READY.

The problem is that the current agent VIM indicates, hasn't got the dp document in her inbox. In other words the dp document is stuck somewhere in the WF.

In vim_analytics the following exceptopn reason appears: Invalid Reaquesetor ID (NPO)

I already trief reassigning the WI to another user without any succes.

Can jou help me finding the correct current agent so that we can continue processing this document?

Kind regards

Greg

[Colleen · Accepted solution]

Hi Gregory

Are you able to check the SWI2* transactions to see if it's unassigned. Within /OPT/VIM_WP you can see the item and might be able to process/forward it from there instead of SWIA.

I suggest you check Fail Safe configuration and put a user in there as fall back if the VIM logic cannot find an agent for next time round.

As a note, the current Agent in your screen shot is probably showing the firs agent in the list that meets the criteria. To the right of the VIM WP screen you can see details and check for the available agents. If in doubt that the item is in their inbox you could check SWI5 to see what unprocessed items are there.

But ultimately, as Sue has mentioned it's a bit hard to help without knowing OpenText business configuration and set up in your system.

Regards

Colleen

[Colleen · Accepted solution]

I forgot to add - you might need to add user to the COA User Table. If you need to process onbehalf of a user you can then add them and also set WF delegation (RMPS_SET_SUBSTITUTE).

If you don't have delegation of the user, you would need a S_WF_WI (whatever the workflow auth object access is) is to administer on behalf of the user.

[Former Member · Accepted solution]

Hi Colleen

Thank you for your helpful anwser.

I had already checked SWI2 without succes.

We have one fail safe user for all possible exceptions. I already checked her workload with SWI5, but I couldn't find the item.

I managed to complete the background step manually which apparently resolved my problem. The flow now continued by creating a new process step and it identified the correct user.

Regards,

Greg