<p>Ananth,</p><p> 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.</p><p>Jeff</p><p>Quoting Kjetil Kilhavn:<br /><br />> Since a
modelled deadline (at least the latest start/end ones) makes <br />> the
step inaccessible I thought it would be better with a parallell <br />>
branch. However, I suppose the requested end deadline works <br />>
differently and allows you to start a branch which can continue in <br />>
parallell with the work item itself. That would be a better design <br />>
from a workflow log perspective I suppose. Thanks for that idea! I <br />>
don't think I have used a requested end deadline before.<br />> --<br />>
Kjetil Kilhavn, Statoil ØFT KTJ ITS BKS SAP Basis - and I appreciate <br />>
it if you delete Statoil's (and other) company disclaimers when you <br />>
reply to this message, since that helps the readability.<br />><br />><br
/>> -----Original Message-----<br />> From: sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] On <br />> Behalf Of Dart, Jocelyn<br
/>> Sent: 27. oktober 2005 15:25<br />> To: SAP Workflow Users' Group<br
/>> Subject: RE: Multilevel deadline monitoring<br />><br />>
Ananth,<br />> It's easier to do it with workflow, and easiest to
change/pull apart <br />> later when the level 2 managers decide they don't
want to be notified <br />> anymore, or only notified in certain cases,
etc., etc.<br />><br />> Copy the standard workflow, either use a
modelled deadline or a <br />> parallel fork as Kjetil suggested is good
to.<br />><br />> Add all your "send mail" steps into the
escalation path - use <br />> activity steps not send mail steps per se, so
you can set requested <br />> start on all of them. Workflow only ends
when the notification is <br />> resolved - use an appropriate status
management event for the <br />> notification like
"alltaskscompleted".<br />><br />> If you can, set up virtual
attributes for your managers against a <br />> delegated subcopy of
BUS2038.<br />><br />> Regards,<br />> Jocelyn Dart<br />><br
/>><br />> -----Original Message-----<br />> From:
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On <br />> Behalf
Of Ananth<br />> Sent: Thursday, 27 October 2005 8:46 PM<br />> To: SAP
Workflow Users' Group<br />> Subject: Re: Multilevel deadline monitoring<br
/>><br />> Hi Kjetil,<br />><br />> Thanks for the reply.<br
/>><br />> When I mean by escalation, i meant a notification mail needs
to be <br />> sent to the level 1 manager and subsequently to the level 2
manager.<br />><br />> I also need to know, is workflow solution really
required in this <br />> scenario, since only notification mails needs to
sent to the <br />> concerned people. I have to convince the client, that
everything can <br />> be done background by an ABAP development by checking
the status of <br />> the Maintenance Notification from the standard tables
and checking <br />> whether the issue is resolved within the specified time
or not and <br />> sending the notification mails subsequently.<br />><br
/>> All your feedback will be really appreciated.<br />><br />>
Thanks<br />> Ananth<br />><br />> On 10/27/05, Kjetil Kilhavn
<KJETILK@statoil.com> wrote:<br />>> Sounds like a nice little
challenge. I am not sure if you by <br />>> escalation mean sending the
job to the manager, or just sending a <br />>> message to tell the
manager to bring out the whip.<br />>><br />>> How about forking
into two branches, branch 1 being the task that <br />>> goes to the
handlers.<br />>> Branch 2 will have a first step with a deadline of two
hours after <br />>> workflow creation, then a next step with deadline 4
hours after <br />>> workflow creation and so on. I suppose you don't
want to terminate <br />>> after the escalation branch has completed so
after the final <br />>> escalation message you should wait for a
terminating event if there <br />>> is one, or just wait for the world to
end (object type world, event <br />>> end).<br />>> --<br
/>>> Kjetil Kilhavn, Statoil ØFT KTJ ITS BKS SAP Basis<br />>><br
/>>><br />>> -----Original Message-----<br />>> From:
sap-wug-bounces@mit.edu [mailto:sap-wug-bounces@mit.edu] On<br />>>
Behalf Of Ananth<br />>> Sent: 26. oktober 2005 18:46<br />>> To:
SAP Workflow Users' Group<br />>> Subject: Multilevel deadline
monitoring<br />>><br />>> Hi All,<br />>><br />>> I
have this scenario to be developed in Maintenance Notification <br />>>
(BUS2038). I need to know how to proceed on this. I am working on <br
/>>> ECC 5.0 version. HR is not implemented here.<br />>><br
/>>> User creates a breakdown notification.<br />>><br />>>
If the issue is resolved within 2 hours, then no escalation.<br />>><br
/>>> If the issue is unresolved within 2 hrs, then escalation to level
1<br />>> mgr. (sending notification mail to the manager)<br
/>>><br />>> If the issue is still unresolved within 4 hrs, then
escalation to <br />>> level 1 mgr with critically indicator.<br
/>>><br />>> If the issue is still unresolved within 6 hrs, then
escalation to <br />>> level 1 mgr and level 2 mgr with critically
indicator.<br />>><br />>> Since there is a standard workflow
WS20000317, but here the <br />>> escalation is just one level, the same
task cannot be re-executed <br />>> for this scenario.<br />>><br
/>>> A custom table will be maintained to have the Level 1 and level 2
managers.<br />>><br />>> Can someone give me some pointers to get
this design.<br />>><br />>><br />>> Thanks in advance,<br
/>>> Ananth<br />><br />><br />>
-------------------------------------------------------------------<br />>
The information contained in this message may be CONFIDENTIAL and is<br />>
intended for the addressee only. Any unauthorised use, dissemination of the<br
/>> information or copying of this message is prohibited. If you are not
the<br />> addressee, please notify the sender immediately by return e-mail
and delete<br />> this message.<br />> Thank you.<br />><br />>
_______________________________________________<br />> SAP-WUG mailing
list<br />> SAP-WUG@mit.edu<br />> <a
href="/horde/services/go.php?url=http%3A%2F%2Fmailman.mit.edu%2Fmailman%2Flistinfo%2Fsap-wug"
target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br />><br
/><br /><br />-- <br />Jeffrey A. Rappaport<br />Business Workflow, LLC<br
/>www.Business-Workflow.com </p><br />