FW: Question about program RSWNUWLSEL

[Bratzler, Loren]

Rick,

Thanks for the reply.  As we were investigating this, we also found that this job had been put on hold in our SRM system about a year ago and it hasn’t been running there at all.  And no one has complained or noticed.  When you say “eventually the job will be removed” are you saying that from the perspective of your own systems?  Or are you saying that SAP will eventually get rid of this job?

Loren


From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Rick Bakker
Sent: Monday, April 21, 2014 1:57 PM
To: SAP Workflow Users' Group
Subject: Re: FW: Question about program RSWNUWLSEL

Hi Loren,

I've seen the same problem. After doing some tests with the help of the Portal guy we concluded the job had no effect on UWL, probably because Portal settings had superseded it. To play it safe we scheduled it to run less frequently; the users did not notice any difference.
Eventually the job will be removed.

regards
Rick Bakker


On Mon, Apr 21, 2014 at 4:50 AM, Bratzler, Loren <Loren.Bratzler at nscorp.com<mailto:Loren.Bratzler at nscorp.com>> wrote:
Trying to send this message again to the WUG:

From: Bratzler, Loren
Sent: Thursday, April 17, 2014 4:28 PM
To: SAP Workflow Users' Group
Subject: Question about program RSWNUWLSEL

We have a job that is scheduled in our system that runs every one minute. The job executes program RSWNUWLSEL.  This job recently started showing up on our Early Watch report as being a huge consumption of database resources.  Our Basis team has asked me to look into it.

So I have been researching the program in SCN and SAP documentation and it appears that the real purpose of this job is to support Extended Notifications.  But we do not use extended notifications in our system.  So I am questioning if we need to have this job running at all in our backend system?

The job that executes this program was named “UWL_REFRESH” by the people who originally set it up, so I assumed this job was responsible for keeping tasks updated in the Universal Worklist for users.  However, I have found through testing, that even if this job is not running, our Portal system is initiating a refresh and tasks show up in the UWL just fine.  I have seen all the documentation that says you must configure the background jobs to run in conjunction with the Portal Delta Pull process but I have yet to find any webpage that really explains why that is.

If we are not using extended notifications in our system, is it necessary to run this program in the background to support the Portal refresh processes?  And if so, can anyone really explain why?

Loren Bratzler
Norfolk Southern Corporation

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug

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