Multilevel deadline monitoring

Thu Oct 27 11:11:46 EDT 2005

  Ananth,

      There is a neat little trick that Rolf Gerstner taught me a #
of years back. If you have no more than 3 DM's to send out, which it
looks like you do (2, 4 & 6 hrs), you can set the 'Latest Start' in
Display Text to 2 hrs; the 'Requested End' in Display Text to 4 hrs;
and the 'Latest End' in Display Text to 6 hrs. The 3 messages will go
out at the DM's & the work item never needs to leave the Approver's
Inbox. Let me know how it fairs.

  Jeff

  Quoting Kjetil Kilhavn:

> Since a modelled deadline (at least the latest start/end ones)
makes
> the step inaccessible I thought it would be better with a parallell

> branch. However, I suppose the requested end deadline works 
> differently and allows you to start a branch which can continue in 
> parallell with the work item itself. That would be a better design 
> from a workflow log perspective I suppose. Thanks for that idea! I 
> don't think I have used a requested end deadline before.
> --
> Kjetil Kilhavn, Statoil ØFT KTJ ITS BKS SAP Basis - and I
appreciate
> it if you delete Statoil's (and other) company disclaimers when you

> reply to this message, since that helps the readability.
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On 
> Behalf Of Dart, Jocelyn
> Sent: 27. oktober 2005 15:25
> To: SAP Workflow Users' Group
> Subject: RE: Multilevel deadline monitoring
>
> Ananth,
> It's easier to do it with workflow, and easiest to change/pull
apart
> later when the level 2 managers decide they don't want to be
notified
> anymore, or only notified in certain cases, etc., etc.
>
> Copy the standard workflow, either use a modelled deadline or a 
> parallel fork as Kjetil suggested is good to.
>
> Add all your "send mail" steps into the escalation path - use 
> activity steps not send mail steps per se, so you can set requested

> start on all of them.  Workflow only ends when the notification is 
> resolved - use an appropriate status management event for the 
> notification like "alltaskscompleted".
>
> If you can, set up virtual attributes for your managers against a 
> delegated subcopy of BUS2038.
>
> Regards,
> Jocelyn Dart
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On 
> Behalf Of Ananth
> Sent: Thursday, 27 October 2005 8:46 PM
> To: SAP Workflow Users' Group
> Subject: Re: Multilevel deadline monitoring
>
> Hi Kjetil,
>
> Thanks for the reply.
>
> When I mean by escalation, i meant a notification mail needs to be 
> sent to the level 1 manager and subsequently to the level 2
manager.
>
> I also need to know, is workflow solution really required in this 
> scenario, since only notification mails needs to sent to the 
> concerned people. I have to convince the client, that everything
can
> be done background by an ABAP development by checking the status of

> the Maintenance Notification from the standard tables and checking 
> whether the issue is resolved within the specified time or not and 
> sending the notification mails subsequently.
>
> All your feedback will be really appreciated.
>
> Thanks
> Ananth
>
> On 10/27/05, Kjetil Kilhavn <KJETILK at statoil.com> wrote:
>> Sounds like a nice little challenge. I am not sure if you by 
>> escalation mean sending the job to the manager, or just sending a 
>> message to tell the manager to bring out the whip.
>>
>> How about forking into two branches, branch 1 being the task that 
>> goes to the handlers.
>> Branch 2 will have a first step with a deadline of two hours after

>> workflow creation, then a next step with deadline 4 hours after 
>> workflow creation and so on. I suppose you don't want to terminate

>> after the escalation branch has completed so after the final 
>> escalation message you should wait for a terminating event if
there
>> is one, or just wait for the world to end (object type world,
event
>> end).
>> --
>> Kjetil Kilhavn, Statoil ØFT KTJ ITS BKS SAP Basis
>>
>>
>> -----Original Message-----
>> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
>> Behalf Of Ananth
>> Sent: 26. oktober 2005 18:46
>> To: SAP Workflow Users' Group
>> Subject: Multilevel deadline monitoring
>>
>> Hi All,
>>
>> I have this scenario to be developed in Maintenance Notification 
>> (BUS2038). I need to know how to proceed on this. I am working on 
>> ECC 5.0 version. HR is not implemented here.
>>
>> User creates a breakdown notification.
>>
>> If the issue is resolved within 2 hours, then no escalation.
>>
>> If the issue is unresolved within 2 hrs, then escalation to level
1
>> mgr.  (sending notification mail to the manager)
>>
>> If the issue is still unresolved within 4 hrs, then escalation to 
>> level 1 mgr with critically indicator.
>>
>> If the issue is still unresolved within 6 hrs, then escalation to 
>> level 1 mgr and level 2 mgr with critically indicator.
>>
>> Since there is a standard workflow WS20000317, but here the 
>> escalation is just one level, the same task cannot be re-executed 
>> for this scenario.
>>
>> A custom table will be maintained to have the Level 1 and level 2
managers.
>>
>> Can someone give me some pointers to get this design.
>>
>>
>> Thanks in advance,
>> Ananth
>
>
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and
is
> intended for the addressee only. Any unauthorised use,
dissemination of the
> information or copying of this message is prohibited. If you are
not the
> addressee, please notify the sender immediately by return e-mail
and delete
> this message.
> Thank you.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug[1]
>

-- 
Jeffrey A. Rappaport
Business Workflow, LLC
www.Business-Workflow.com Links:
------
[1] 
/horde/services/go.php?url=http%3A%2F%2Fmailman.mit.edu%2Fmailman%2Flistinfo%2Fsap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20051027/f8f4eb93/attachment.htm