report on escalation path

[#1]

Hi,

Is there a way to report on the escalation path that a workflow has followed during its lifetime/

Cheers,

Ross Goodman

[Former Member]

Hi,

It is possible to create such a report, all of the data is there, workflow logs and sap_wapi* function modules etc etc etc.

However! Before you embark on creating a custom report taking 120 hours + to complete.

Please tell us the functional requirement first, I think there is probably a way better solution to your problem.

Kind regards, Rob Dielemans

[ross_goodman]

Hi Rob and Sue,

The client sees occasions where the escalation appears to be going somewhere they think it should not. The workflow is set to use the standard escalation methods by step increment in the org structure as far as I can tell. There certainly appears to be no custom development in the modeled escalation branch of the workflow.

So they have asked if there is a report that will show them what the escalation path has been for a "workflow". So when a particular vendor Invoice has past its required and latest deadlines who did the invoice approval get forwarded to?

If the org structure suggets that the item should have escalated to Joe but it has in fact gone to Debbie is there a way to see the workings of the escalation process to see why Debbie has been chosen?

Ross

[Former Member]

Hello,

You could make a custom report to show the escalation path for each workflow instance, SAP_WAPI_WORKITEM_GET_DETAIL would be helpful there, otherwise the tables (e.g. to show that the workflow exceeded its deadline and started escalating).

As to why it picked Debbie over Joe, that's all the the agent assignment rules. I don't see any easy way of showing its inner workings in a report, maybe just input and output would be enough?

regards

Rick Bakker

hanabi technology

[Former Member]

This sounds more like an ad-hoc requirement.

So just fulfil it, through using the workflow log and viewing the containers etc. You will find out where the workitems have been to etc. etc.

Kind regards, Rob Dielemans