SRM Workflow Deadline Escalation BRF 7.0 Process Controlled

[Sudhir Pargaonkar]

Thanks Mark for your reply. Appreciate it. 

Basically, you are just changing the agent of Active workitem and updating the workitem text. I am assuming, you are using Agents Change FM instead of just forwarding the workitem so that you have multiple recipients. 

I started on similar approach in the beginning but started digging more to achieve some solution that gives more ability to track / trace escalations. 

But it seems that we will have to go ahead with this type of solution. 

Thanks.
Sudhir

Sent from Mail for Windows 10



From: Mark Pyc
Sent: Thursday, October 8, 2015 5:08 PM
To: SAP Workflow Users' Group
Subject: Re: SRM Workflow Deadline Escalation BRF 7.0 Process Controlled


G'day Sudhir,

We've handled it via a scheduled report which uses SWW_WI_AGENTS_CHANGE to update the existing item and sap_wapi_write_container to set some control flags. In the WI long text you can use IF statements to dynamically include text indicating its been escalated. 

We actually have a complex arrangement where we spiral escalations up a chain of command with dynamic levels based on the previous actual agent. 

When escalating it's always better to increase the number of recipients rather than take it off one and give it to another. 

It's all a bit fiddly but it's been live 4 months and going smoothly so far. 

Have fun,
Mark

Sent from my phone

> On 9 Oct 2015, at 7:16 am, Sudhir Pargaonkar <pargov at gmail.com> wrote:
> 
> Hi All,
> 
> I am working on a requirement of sending email reminder after 2 days and escalate workitem to manager after 5 days for SRM Shopping  Cart, PO, Contracts workflow. 
> 
> As per my research, deadline config / BADI is useful only to send out 1 message / alert after certain number of hours. It doesn't happen repeatedly untill approved / rejected. I also didn't see any option of ESCALATION. 
> 
> I can easily do this by creating a batch program and monitoring workitems for a certain task based on creation date and forwarding the workitem to manager if deadline reaches. But this approach won't show anything in UWL approval tab for the SC. 
> 
> Is there any way to achieve a solution that would display on approval tab of the document that it was escalated to current approver as original manager didn't take action. (Both names show up in the chain, with status obsolete for original manager)..
> 
> I created a batch program to add an ADHOC level with user's manager as agent AFTER the current level. But trying to figure out a solution to get current workitem / process level to become obsolete such that the workitem moves to ADHOC. Tried different methods of class *WF*PROCESS*MANAGER but didn't help. Also tried to 'manually complete' the workitem using workflow tools, but in that case, even though the workflow moved to NEXT ADHOC manager, in the UWL SC approval tab view, original manager level just disappeared. 
> 
> My doubt:
> - Restarting process level will just determine new approver with proper BADI implementation, so it can't have both users listed
> - Using workflow function modules to manually complete the step doesn't work as it removes that step from approval tab of SC. 
> 
> Has anyone done this before? Any pointers / suggestions?
> 
> Thanks. 
> Sudhir
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20151009/68f53840/attachment.html