<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1505" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Tahoma">
<DIV>Mike & All,</DIV>
<DIV>All these questions I ask are due to performance tuning and </DIV>
<DIV>Archive Strategy research we are doing. I know RSWWDHEX batch </DIV>
<DIV>is very efficient but every tick of the clock adds up. </DIV>
<DIV>So any comments from anyone are very welcome. </DIV>
<DIV> </DIV>
<DIV>We have one WF that has a DM on a task. We put it in to allow </DIV>
<DIV>some processing to complete before we run that task. Start WF, </DIV>
<DIV>execute the task with DM for DB update (DM on task to start in one minute), and </DIV>
<DIV>then continue. </DIV>
<DIV> </DIV>
<DIV>I know this is not the best approach but I did not develop that WF and </DIV>
<DIV>I am going to try to get it changed. </DIV>
<DIV>I think adding an exception on the BOR method with temp error would solve this problem. </DIV>
<DIV>Thoughts?</DIV>
<DIV> </DIV>
<DIV>So, safe to shut off the case-specific "Deadline monitoring on an individual basis" </DIV>
<DIV>since newer versions don't allow it for this case AND </DIV>
<DIV>enable just the "Permanent deadline monitoring"? </DIV>
<DIV>Is this the setting you have? </DIV>
<DIV> </DIV>
<DIV>And for some reason we have "Event queue switched off". I know I had this turned on </DIV>
<DIV>when we did the initial setup but for some reason it is now off. </DIV>
<DIV>Comments / thoughts about the event queue are welcome.</DIV>
<DIV> </DIV>
<DIV>Thanks much!</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>Rick Sample<BR>SAP Workflow Analyst/Developer<BR>Graybar, Inc.<BR>11885 Lackland Rd.<BR>63146-4208<BR>314.573.5822<BR><A href="mailto:Rick.Sample@GBE.com">Rick.Sample@GBE.com</A><BR><BR>>>> wug.replies@workflowconnections.com 6/24/2005 2:55 >>><BR>Hi Rick,<BR>Enabling case-specific monitoring means that a deadline job is scheduled<BR>by each task that requires it. This allows much more exact deadlines as it<BR>will happen at the time specified, not a few minutes later when the next<BR>regular job executes. However for the reasons you already describe it is<BR>only useful if you have very few deadlines (I think the docs even mention<BR>that).<BR><BR>In later versions, SAP have (wisely) removed that option, and only regular<BR>monitoring is available. The regular job is quite efficient as it only<BR>reads an indexed table to pick up anyhing older than the current time so<BR>there shouldn't be any issue with scheduling it every 5 minutes.<BR><BR>Cheers<BR>Mike<BR><BR>Rick Sample wrote:<BR>> RSWWDHEX was executing twice for the exact same time.<BR>> So every 3 minutes I have two RSWWDHEX starting at the exact same time<BR>><BR>> with no WFs with DMs.<BR>> I can only assume this was not set correctly. How, I do not know,<BR>> but looking at the code we have a comment in there about this issue.<BR>> I deleted one of them in SM37 and seems to have fixed the locking<BR>> issue.<BR>><BR>> Depending on the settings for the batch RSWWDHEX<BR>> from my understanding you can have a few different setups.<BR>> 1. None.<BR>> 2. RSWWDHEX running Periodically "Optional: Schedule permanent deadline<BR>> monitoring" like every 20 mins.<BR>> 3. RSWWDHEX running "Schedule backgr. job for case-specific deadline<BR>> monitoring".<BR>> 4. RSWWDHEX running Periodically "Optional: Schedule permanent deadline<BR>> monitoring" like every 20 mins. And<BR>> RSWWDHEX running "Schedule backgr. job for case-specific deadline<BR>> monitoring".<BR>><BR>> Looks like we have both running. Periodically and per task instance.<BR>> I started a WF with a DM on it and then looked at SM37.<BR>><BR>> Sure enough I had a new batch started for each WF task with DM and the<BR>> normal 20 min run.<BR>> So this could be thousands of this RSWWDHEX in queue and running at the<BR>> same time for this setup. Yes?<BR>><BR>> What is the norm? Just run the batch Periodically "Optional: Schedule<BR>> permanent deadline monitoring" like every 20 mins<BR>> and call it a day or is there some reason to have both?<BR>><BR>> I am just trying to understand what is going on under the covers...<BR>> Thanks!<BR>><BR>><BR>><BR>><BR>>>>> <U><A href="mailto:Jeff@Business-Workflow.com">Jeff@Business-Workflow.com</A></U> 6/23/2005 9:57 >>><BR>> Rick,<BR>><BR>> Hopefully I can answer some of your questions from My<BR>> observations. DM is a large part of WF, so if there is a<BR>> big problem with the RSWWDHEX pgm then have a talk with<BR>> the Basis guys, my pgm. runs in less then a second or two.<BR>> You would not normally set the DM to run every 3 mins<BR>> unless you had some deadlines that were set to expire in<BR>> less than say 30 mins. I have a DM on one of mine now that<BR>> is set for 4 hrs, so I have the pgm run every 10 mins. If<BR>> your DM's are by Days, then just set the DM to the<BR>> highest, 99 mins, & the pgm to kick it maybe every few<BR>> hrs. And it is just one batch pgm not thousands that<BR>> trigger.<BR>><BR>> 1) Haven't seen this happen, but try upping the Pgm time &<BR>> speaking to Basis.<BR>> 2) Table SWDSSTEPS looks like a Definition table of the<BR>> Tasks in your system & isn't per instance of steps. So it<BR>> should stay around 9,000 unless you start creating more<BR>> custom tasks. It doesn't just define the DM times but also<BR>> the 2nd Meth, End Confirm, Batch, etc.<BR>> 3) The RSWWDHEX doesn't miss a deadline it just triggers<BR>> whatever hits since the last run. If you have steps that<BR>> hang it sounds like you have other problems than DM.<BR>> 4) Any old WF's you no longer need you can Logically<BR>> Delete them so they're not hitting the system anymore,<BR>> either for DM or uncompleted steps.<BR>><BR>> Hope this helps, may not have been what you were looking<BR>> for.<BR>><BR>> Jeff<BR>><BR>> ---- Original message ----<BR>>>Date: Wed, 22 Jun 2005 13:21:07 -0500<BR>>>From: "Rick Sample" < <U><A href="mailto:Rick.Sample@gbe.com">Rick.Sample@gbe.com</A></U> ><BR>>>Subject: Re: deadline monitoring loop<BR>>>To: <U><A href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A></U> <BR>>><BR>>> "Set 'Latest End' DM & enable 'Processing obsolete'<BR>>> for an outcome"<BR>>> Interesting! And raises some more questions for me<BR>>> now that I looked at it.<BR>>> We don't use Deadline processing much so please bare<BR>>> with me. We have enough<BR>>> problems with performance without throwing thousands<BR>>> of batch progs at the system<BR>>> every 20 minutes.<BR>>><BR>>> When testing in development with very low Requested<BR>>> Start in task and<BR>>> low RSWWDHEX settings (1 minute and 3 minutes<BR>>> respectively), I noticed<BR>>> some interesting issues.<BR>>> Just in dev. Don't run these settings in prod!<BR>>> Performance thing. (Unless you like getting Tarred<BR>>> and Feathered!)<BR>>><BR>>> 1. Locking issues.<BR>>> No doubt due to the RSWWDHEX running multiple times<BR>>> with above settings.<BR>>> When this happens my tasks sometimes hang.<BR>>> So, next time RSWWDHEX runs it sees nothing to do<BR>>> and the task is just stuck until manually set.<BR>>> Sound correct?<BR>>><BR>>> 2. Table SWDSSTEPS.<BR>>> When, what, and how do these entries get cleared out<BR>>> of the table?<BR>>> I noticed over 9,000 entries in dev and I know I<BR>>> don't have _anything_ in waiting.<BR>>> All entries are zeros for time/date.<BR>>><BR>>> 3. Will "Set 'Latest End' DM & enable 'Processing<BR>>> obsolete' for an outcome" pickup<BR>>> these tasks and complete the step if for any reason<BR>>> the RSWWDHEX misses the deadline?<BR>>> And, then will they get cleared if it hangs on the<BR>>> Requested Start?<BR>>><BR>>> 4. How do I clear old timers for any task / WF that<BR>>> I no longer want to monitor?<BR>>> Example, old WF versions that we not longer want to<BR>>> use Deadlines.<BR>>><BR>>><BR>>> Thanks!<BR>>> 4.6c<BR>>><BR>>><BR>>><BR>>><BR>>><BR>>><BR>>><BR>>><BR>>> Rick Sample<BR>>> SAP Workflow Analyst/Developer<BR>>> Graybar, Inc.<BR>>> 11885 Lackland Rd.<BR>>> 63146-4208<BR>>> 314.573.5822<BR>>> <U><A href="mailto:Rick.Sample@GBE.com">Rick.Sample@GBE.com</A></U> <BR>>> >>> <U><A href="mailto:Jeff@Business-Workflow.com">Jeff@Business-Workflow.com</A></U> 6/22/2005 12:02 >>><BR>>> Sushil,<BR>>><BR>>> You could use the Modeled option on your 'Latest<BR>>> End'<BR>>> DM & enable 'Processing obsolete' for an outcome.<BR>>> Then<BR>>> place the mail step after the DM leg & then a<BR>>> 'Process<BR>>> Control' Step that 'Sets the work item to Obsolete'<BR>>> using<BR>>> that original DM Step as the 'WF Step' entry. Let me<BR>>> know<BR>>> if you have any problems & I can show you some<BR>>> screen<BR>>> shots.<BR>>><BR>>> Jeff Rappaport<BR>>> <U><A href="http://www.business-workflow.com/">www.Business-Workflow.com</A></U> <BR>>><BR>>> ---- Original message ----<BR>>> >Date: Wed, 22 Jun 2005 10:25:35 -0500<BR>>> >From: "Sushil Guragain" < <U><A href="mailto:sguragain@interpublic.com">sguragain@interpublic.com</A></U> <BR>>> ><BR>>> >Subject: deadline monitoring loop<BR>>> >To: "SAP Workflow Users' Group" < <U><A href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A></U> ><BR>>> ><BR>>> > Hello WF Gurus,<BR>>> ><BR>>> > I am trying to create a loop on deadline<BR>>> monitoring<BR>>> > so that it will keep sending email until the user<BR>>> > takes an action. I am planning to send email every<BR>>> > 24 hours until it is approved or declined. Is<BR>>> there<BR>>> > a standard way to get this activated? I tried<BR>>> using<BR>>> > deadline monitoring with 24 hours and found that<BR>>> it<BR>>> > sends the notification once and that is it. Would<BR>>> it<BR>>> > work if I put that in a loop? If so what do I<BR>>> check<BR>>> > against to see if the work item is complete?<BR>>> ><BR>>> > Thank you for your suggestions in advance!<BR>>> ><BR>>> > Sushil<BR>>> ><BR>>> > This message contains information which may be<BR>>> confidential and privileged.<BR>>> > Unless you are the intended recipient (or<BR>>> authorized to<BR>>> receive this message<BR>>> > for the intended recipient), you may not use,<BR>>> copy,<BR>>> disseminate or disclose to<BR>>> > anyone the message or any information contained in<BR>>> the<BR>>> message. If you have<BR>>> > received the message in error, please advise the<BR>>> sender<BR>>> by reply e-mail, and<BR>>> > delete the message. Thank you very much.<BR>>> > (A)<BR>>> >________________<BR>>> >_______________________________________________<BR>>> >SAP-WUG mailing list<BR>>> > <U><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A></U> <BR>>> > <U><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A></U> <BR>>> Jeffrey A. Rappaport<BR>>> Business Workflow, LLC<BR>>> voice: (732)355-0123<BR>>> fax: (509)757-4144<BR>>> email: <U><A href="mailto:Jeff@Business-Workflow.com">Jeff@Business-Workflow.com</A></U> <BR>>> web: <U><A href="http://www.business-workflow.com/">www.Business-Workflow.com</A></U> <BR>>> _______________________________________________<BR>>> SAP-WUG mailing list<BR>>> <U><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A></U> <BR>>> <U><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A></U> <BR>>>________________<BR>>>_______________________________________________<BR>>>SAP-WUG mailing list<BR>>> <U><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A></U> <BR>>> <U><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A></U> <BR>> Jeffrey A. Rappaport<BR>> Business Workflow, LLC<BR>> voice: (732)355-0123<BR>> fax: (509)757-4144<BR>> email: <U><A href="mailto:Jeff@Business-Workflow.com">Jeff@Business-Workflow.com</A></U> <BR>> web: <U><A href="http://www.business-workflow.com/">www.Business-Workflow.com</A></U> <BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> <U><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A></U> <BR>> <U><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A></U> <BR>><BR>><BR>> _______________________________________________<BR>> SAP-WUG mailing list<BR>> <U><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A></U> <BR>> <U><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A></U> <BR>><BR><BR><BR>Mike Pokraka<BR>Senior Consultant<BR>Workflow Connections Ltd.<BR>Mobile: +44 (0)7786 910 855<BR>_______________________________________________<BR>SAP-WUG mailing list<BR><U><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A></U> <BR><U><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A></U> <BR><BR></DIV></BODY></HTML>