RSWUWFML2 Report

Wed Aug 16 14:51:43 EDT 2006

Jeff,

Make sure you put different numbers for the 2 jobs in the Job Suffix
field.

Claude

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Rappaport, Jeff
Sent: August 16, 2006 2:34 PM
To: SAP Workflow Users' Group
Subject: RE: RSWUWFML2 Report

SWUG's,

   On a side note, has anyone had any troubles not getting all their
Notifications when running this report as more than one job (to include
different Tasks for different intervals, or collective)? Meaning:

Job1 runs every hour w/Tasks A @ 1pm, 2pm, 3pm...
Job2 runs every hour w/Tasks B @ 1:30pm, 2:30pm... 

  When Job1 runs @ 2pm, it will only pick up Tasks A items created from
1:30-2pm instead of 1-2pm because when Job2 runs it puts a stamp in
table SWU_WLSCAN(??) as the last run. Does this sound correct? Haven't
had the time to debug the program yet so was hoping that someone already
knows the answer.

Thanx,

Jeff Rappaport
SAP Workflow Development
(609) 497-7246
Jeff.Rappaport at ChurchDwight.com

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Dart, Jocelyn
Sent: Wednesday, August 09, 2006 7:52 PM
To: SAP Workflow Users' Group
Subject: RE: RSWUWFML2 Report

Anna, 

On ECC5 you are on 6.40 and should be using Extended Notifications
instead.  

Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

The information contained in or attached to this electronic transmission
is confidential and may be legally privileged. It is intended only for
the person or entity to which it is addressed. If you are not the
intended recipient, you are hereby notified that any distribution,
copying, review, retransmission, dissemination or other use of this
electronic transmission or the information contained in it is strictly
prohibited. If you have received this electronic transmission in error,
please immediately contact the sender to arrange for the return of the
original documents. 
Electronic transmission cannot be guaranteed to be secure and
accordingly, the sender does not accept liability for any such data
corruption, interception, unauthorized amendment, viruses, delays or the
consequences thereof.
Any views expressed in this electronic transmission are those of the
individual sender, except where the message states otherwise and the
sender is authorized to state them to be the views of SAP AG or any of
its subsidiaries. SAP AG, its subsidiaries, and their directors,
officers and employees make no representation nor accept any liability
for the accuracy or completeness of the views or information contained
herein. Please be aware that the furnishing of any pricing information/
business proposal herein is indicative only, is subject to change and
shall not be construed as an offer or as constituting a binding
agreement on the part of SAP AG or any of its subsidiaries to enter into
any relationship, unless otherwise expressly stated. 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Hill, Anna
Sent: Wednesday, 09 August 2006 9:16 PM
To: SAP Workflow Users' Group
Subject: RE: RSWUWFML2 Report

Hi Seth

This may not be relevant to you but it's worth sharing - I've had a
problem with this report when running on ECC 5.0. The report was set to
pick up new work items only but was actually ignoring this and
delivering duplicate reminders to users on each new run of the report.
There's an OSS message out on this to fix (739988 I think) - it may be
worth checking whether your users are receiving duplicate notifications
in this case. Could make snes if you've only been live for 1 month.

Cheers
Anna

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mike Pokraka
Sent: Wednesday, August 09, 2006 7:41 AM
To: SAP Workflow Users' Group
Subject: RE: RSWUWFML2 Report

Hi Seth,

This might still be correct. I may be wrong and don't really have the
time to check, but your variant looks right so a sensible conclusion may
be that one initial run with 'new work items only' is needed to set your
last run date - thus your interval only becomes effective on the second
run.

Cheers,
Mike

> I updated the variant to include "New Work Items Only" and the report 
> still took 3.5 hours to run this morning.  Below is the screen variant

> used, any suggestions?
>
> Thanks,
> Seth
>
> Job suffix                      2
>
> Tasks (blank = all)             TS90000070
>
>                                 TS90000110
>
>                                 TS90000130
>
>                                 TS90000058
>
>                                 TS90000066
>
>                                 TS90000005
>
>                                 TS90000150
>
>                                 TS90000129
>
>                                 TS90000142
>
> New Work Items Only             X
>
> With Passive Substitution
>
> One Message Per Work Item
>
> Collective Message              X
>
> Workflow Entry
>
> Work Item Display
>
> Work Item Execution
>
> Message Class for Subject       SWU_NOTIF
>
> Message Number for Subject      001
>
> Before Work Item Description    SWU_NOTIF_INBOX
>
> After Work Item Description
>
> SAPLOGON_ID
>
> FB for Preparation Phase
>
> FB for Address Determination
>
>>From Work Item Creation Date    00/00/0000
>
>>From Work Item Creation Time      :  :
>
> Users (blank = all)
>
> Errors Only                     X
>
> All
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
> Of Stevens, Seth
> Sent: Monday, August 07, 2006 9:45 AM
> To: SAP Workflow Users' Group
> Subject: RE: RSWUWFML2 Report
>
> As you guessed "only new workitems" isn't set...guess I missed it when

> setting up the variant.
>
> I'll change it today suspect we'll see MUCH better performance 
> tomorrow's run.  Thanks for the tips.
>
> --Seth
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
Behalf
> Of Mike Pokraka
> Sent: Monday, August 07, 2006 9:37 AM
> To: SAP Workflow Users' Group
> Subject: Re: RSWUWFML2 Report
>
> What the...? Three hours? Sone hints:
>
> Make sure you set "only new workitems" (methinks this is where your 
> setup is choking)
>
> You can create separate instances of the job for different tasks / 
> frequencies / whatevers. Not uncommon to run it e.g. an hourly one for

> 'urgent notification' type tasks and a twice daily job for others etc.
>
> It's pretty well documented, click the info button on the front
screen.
>
> Cheers,
> Mike
>
>
>> Hi all...does any one have any performance suggestions for the
>> RSWUSFML2 report for workitem notification?  It is currently taking 
>> over 3 hours to run and is increasing at a rate of about 10 minutes 
>> per day.  I'm sure that archiving the workitems and logs would help 
>> but I didn't want to do that yet as the system has been in production

>> for less than 1 month.  Is the architecture of the report such that 
>> the response time is affected by all workitems (even completed) or is

>> it only affected by the number of in process workitems?
>>
>> Any tips?
>>
>> Thanks,
>> Seth
>>
>>
>>
>> -----------------------------------------
>> Anadarko Confidentiality Notice:
>> This electronic transmission and any attached documents or other 
>> writings are intended only for the person or entity to which it is 
>> addressed and may contain information that is privileged,
confidential
>
>> or otherwise protected from disclosure.  If you have received this 
>> communication in error, please immediately notify sender by return 
>> e-mail and destroy the communication. Any disclosure, copying, 
>> distribution or the taking of any action concerning the contents of 
>> this communication or any attachments by anyone other than the named 
>> recipient is strictly prohibited.
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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
>

_______________________________________________
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

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
 *The information contained in this message may be confidential and/or
subject to legal privilege, and is for the use of the intended addressee
only.  Any unauthorized use, dissemination or copying of the information
in this message is strictly prohibited.  If you have received this
message in error, please notify the sender immediately and delete this
message.*

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

La version fran?aise suit le texte anglais.

------------------------------------------------------------------------------------

This email may contain privileged and/or confidential information, and the Bank of
Canada does not waive any related rights. Any distribution, use, or copying of this
email or the information it contains by other than the intended recipient is
unauthorized. If you received this email in error please delete it immediately from
your system and notify the sender promptly by email that you have done so. 

------------------------------------------------------------------------------------

Le pr?sent courriel peut contenir de l'information privil?gi?e ou confidentielle.
La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion,
utilisation ou copie de ce courriel ou des renseignements qu'il contient par une
personne autre que le ou les destinataires d?sign?s est interdite Si vous recevez
ce courriel par erreur, veuillez le supprimer imm?diatement et envoyer sans d?lai ?
l'exp?diteur un message ?lectronique pour l'aviser que vous avez ?limin? de votre
ordinateur toute copie du courriel re?u.