<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:tahoma, new york, times, serif;font-size:10pt"><P>Sharat,</P>
<P> </P>
<P>Thanks for your reply. How did you overcome the login pop-up ?</P>
<DIV></DIV>
<DIV><BR> </DIV>
<P><FONT face="verdana, helvetica, sans-serif" color=#00007f size=2><STRONG>Regards,<BR>Shai Eyal</STRONG></FONT></P>
<P><FONT face=Verdana color=#000080 size=2><STRONG>SAP Logistics senior consultant<BR>SAP Workflow specialist<BR>Mobile: 972-52-5816633</STRONG></FONT></P>
<DIV style="FONT-SIZE: 10pt; FONT-FAMILY: tahoma, new york, times, serif"><BR><BR>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: times new roman, new york, times, serif">----- Original Message ----<BR>From: "sap-wug-request@mit.edu" <sap-wug-request@mit.edu><BR>To: sap-wug@mit.edu<BR>Sent: Thursday, May 15, 2008 3:54:57<BR>Subject: SAP-WUG Digest, Vol 42, Issue 26<BR><BR>Send SAP-WUG mailing list submissions to<BR> <A href="mailto:sap-wug@mit.edu" ymailto="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A><BR><BR>To subscribe or unsubscribe via the World Wide Web, visit<BR> <A href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR>or, via email, send a message with subject or body 'help' to<BR> <A href="mailto:sap-wug-request@mit.edu" ymailto="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</A><BR><BR>You can reach the person managing the list at<BR> <A href="mailto:sap-wug-owner@mit.edu"
ymailto="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</A><BR><BR>When replying, please edit your Subject line so it is more specific<BR>than "Re: Contents of SAP-WUG digest..."<BR><BR><BR>Today's Topics:<BR><BR> 1. RE: WF Background Jobs (Neumann, Marcia)<BR> 2. Re: Exntended notification BSP and SSO (Sharath K)<BR><BR><BR>----------------------------------------------------------------------<BR><BR>Message: 1<BR>Date: Wed, 14 May 2008 12:29:55 -0400<BR>From: "Neumann, Marcia" <<A href="mailto:Marcia_Neumann@CINFIN.com" ymailto="mailto:Marcia_Neumann@CINFIN.com">Marcia_Neumann@CINFIN.com</A>><BR>Subject: RE: WF Background Jobs<BR>To: "SAP Workflow Users' Group" <<A href="mailto:sap-wug@mit.edu" ymailto="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A>><BR>Message-ID:<BR> <<A href="mailto:594CD456E9B52844B448AA77AD1D8E4902DE5FE4@exchq2.cinfin.com"
ymailto="mailto:594CD456E9B52844B448AA77AD1D8E4902DE5FE4@exchq2.cinfin.com">594CD456E9B52844B448AA77AD1D8E4902DE5FE4@exchq2.cinfin.com</A>><BR>Content-Type: text/plain; charset="us-ascii"<BR><BR>We experienced very long runtimes for job SWWCOND on 4.71 and opened a<BR>message with SAP. Based on their responses in September 2005, we<BR>cancelled the job.<BR><BR><BR><BR>Reply from SAP 09/15/2005 04:27:04<BR><BR>I analyzed the problem in your system. We really have a problem with<BR><BR>the performance of report RSWWCOND. Development is aware of that, and<BR><BR>thinking of a redesign of the functionality. For the time being, we<BR><BR>can offer the following solution:<BR><BR>- I checked the definition table SWD_CONDEF. I see that the relevant<BR><BR> conditions are only used in one workflow: WS90200019, step 29. This<BR><BR> step is the 'post' step. It is task TS90200040.<BR><BR>
Relevant condition types are only 'PO', 'PR', and 'WA'.<BR><BR>- RSWWCOND really only needs to check conditions for that task number.<BR><BR> So, we can enter this task on the selection screen for RSWWCOND.<BR><BR> The report then runs only 2 seconds, because it can access table<BR><BR> SWWWIHEAD with index C.<BR><BR>- You need to define this selection criteria in a variant, and have<BR><BR> the background job always run with this variant.<BR><BR>- The great disadvantage of this is: any time you change your workflow,<BR><BR> or start working with a new workflow in some application area, you<BR><BR> need to recheck table SWD_CONDEF.<BR><BR> I wonder if this is acceptable to you?<BR><BR> Please let me know.<BR><BR>Best regards,<BR><BR>Workflow Development Support<BR><BR><BR><BR>Reply from SAP 09/16/2005 04:58:20<BR><BR>A redesign of the functionality can not be
delivered per support<BR><BR>package.<BR><BR>I ran the report with SQL trace on, and found that index C is not ued.<BR><BR>Please see note 799002, and change the index, and generate it.<BR><BR>Then check note 724614 for anything to be done on the database side<BR><BR>(I am not at all a database expert).<BR><BR>Then please rerun the report with SQL trace (ST05) switched on. The<BR><BR>select should be done by index C then.<BR><BR>If that is not the case, I will need to send this message to the DB2<BR><BR>database experts. In that case, please keep the system connection open<BR><BR>a little longer.<BR><BR>Best regards,<BR><BR><BR><BR>Marcia Neumann<BR><BR>CMS Workflow Administration<BR><BR>IT Claims Development/Support<BR><BR>Phone: (513) 870-2300 ext. 4461<BR><BR>Fax: (513) 603-5388<BR><BR>Confidentiality notice: The information included in this e-mail,<BR>including any attachments, is for the sole use of the intended recipient<BR>and may contain
confidential and privileged information. Any<BR>unauthorized review, use, disclosure, distribution or similar action is<BR>prohibited. If you are not the intended recipient, please contact the<BR>sender and delete all copies of the original message immediately.<BR><BR>________________________________<BR><BR>From: <A href="mailto:sap-wug-bounces@mit.edu" ymailto="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</A> [mailto:<A href="mailto:sap-wug-bounces@mit.edu" ymailto="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</A>] On Behalf<BR>Of Jeffrey A. Rappaport<BR>Sent: Wednesday, May 14, 2008 11:25 AM<BR>To: SWUG (SAP)<BR>Subject: WF Background Jobs<BR><BR><BR><BR>All,<BR><BR><BR><BR> Had a couple of quick questions on the WF Jobs, first being has<BR>anyone seen the job SWWCOND at times take hours to run? Second would be<BR>what the difference is between the 2 DM Jobs SWFSLSDLEX & SWWDHEX & why<BR>there's now 2 jobs for
this.<BR><BR><BR><BR>Thanx,<BR><BR><BR>Jeffrey A. Rappaport<BR>Business Workflow, LLC<BR>Voice: +1 (732) 355-0123<BR>Fax: +1 (509) 757-4144<BR>Email: <A href="mailto:Jeff@Business-Workflow.com" ymailto="mailto:Jeff@Business-Workflow.com">Jeff@Business-Workflow.com</A><BR>Web: www.Business-Workflow.com<BR><BR><BR><BR> The information contained in this message may be privileged,<BR>confidential and protected from disclosure. If the Reader of this<BR>message is not the intended recipient, you are hereby notified that any<BR>dissemination, distribution or copying of this communication is strictly<BR>prohibited. If you have received this communication in error and would<BR>like to be removed from any future mailings from this Sender, please hit<BR>'Reply' to this email with "REMOVE" in the Subject line.<BR><BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <A
href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20080514/9c2df463/attachment-0001.htm" target=_blank>http://mailman.mit.edu/pipermail/sap-wug/attachments/20080514/9c2df463/attachment-0001.htm</A><BR><BR>------------------------------<BR><BR>Message: 2<BR>Date: Wed, 14 May 2008 17:54:24 -0700 (PDT)<BR>From: Sharath K <<A href="mailto:ksharath77@yahoo.com" ymailto="mailto:ksharath77@yahoo.com">ksharath77@yahoo.com</A>><BR>Subject: Re: Exntended notification BSP and SSO<BR>To: "SAP Workflow Users' Group" <<A href="mailto:sap-wug@mit.edu" ymailto="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A>><BR>Message-ID: <<A href="mailto:19365.62388.qm@web39708.mail.mud.yahoo.com" ymailto="mailto:19365.62388.qm@web39708.mail.mud.yahoo.com">19365.62388.qm@web39708.mail.mud.yahoo.com</A>><BR>Content-Type: text/plain; charset="iso-8859-1"<BR><BR>Shai,<BR>We did similar thing in my last project..<BR>Trigger a 'system event/workflow event'?in your
BSP?application with required logic and listen to the event in your workflow to continure further..it worked for us...<BR>regds,<BR>Sharath...<BR><BR><BR>----- Original Message ----<BR>From: Shai Eyal <<A href="mailto:shai.eyal@yahoo.com" ymailto="mailto:shai.eyal@yahoo.com">shai.eyal@yahoo.com</A>><BR>To: sap-wug <<A href="mailto:sap-wug@mit.edu" ymailto="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A>><BR>Sent: Tuesday, May 13, 2008 5:16:51 AM<BR>Subject: Exntended notification BSP and SSO<BR><BR><BR>Hi all,<BR>?<BR>I've been using the extended notification?to process user decision?task. All works well as follows:<BR>?<BR> 1. User receive e-mail to MS-Outlook with Approve and Reject link.<BR> 2. Once clicked on Approve and Reject system prompts for user and password.<BR> 3. BSP application?message appear that workitem was executed successfully.<BR> 4. Workflow
continues.<BR>My problem is with step 2 - I wish to avoid?the "user and password" step. I thought?and hoped that having Single sign-on would solve it but it did not.<BR>Any ideas will be appreciated.<BR>?<BR>Thanks in advance,<BR>?<BR>Regards,<BR>Shai Eyal<BR>SAP Logistics senior consultant<BR>SAP Workflow specialist<BR>Mobile: 972-52-5816633<BR>Send instant messages to your online friends <A href="http://uk.messenger.yahoo.com/" target=_blank>http://uk.messenger.yahoo.com</A> <BR><BR><BR> <BR>-------------- next part --------------<BR>An HTML attachment was scrubbed...<BR>URL: <A href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20080514/c27f8c61/attachment.htm" target=_blank>http://mailman.mit.edu/pipermail/sap-wug/attachments/20080514/c27f8c61/attachment.htm</A><BR><BR>------------------------------<BR><BR>_______________________________________________<BR>SAP-WUG mailing list<BR><A href="mailto:SAP-WUG@mit.edu"
ymailto="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target=_blank>http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR><BR>End of SAP-WUG Digest, Vol 42, Issue 26<BR>***************************************<BR></DIV></DIV></div><br>Send instant messages to your online friends http://uk.messenger.yahoo.com </body></html>