SWWERRE Job

[Rahilly, Ken]

Cassaundra,
 
If I recall, when setting up the case in 3.1 (a while ago),  I could not =
see the job either.
Even though the config was set to run this job every 20 minutes or =
so...,  the actual job did not exist to be rescheduled 20 minutes in the =
future...
I worked with basis, and submitted the job manually from an appropriate =
account with appropriate authorization and then I was able to see the =
present and future schedules from sm37.
 
Hope this helps,
 
-kr
 
-----Original Message-----
From: Freres, Catie [mailto:Catie.Freres at smith-nephew.com]
Sent: Wednesday, April 03, 2002 11:17 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: SWWERRE Job
 
 
I see it listed as SWWERRE and whoever set up the config is who it shows
runing under.  Plus, whatever time delay you set up in the workflow =
config,
is how frequently you should see it running.
 
Catie Freres
eCommerce Analyst
Smith & Nephew Orthopaedics
Memphis, TN, USA
001-901-399-5507
www.smithnephew.com/orthopaedics
 
> -----Original Message-----
>> From: Smith, Cassaundra [SMTP:Cassaundra.Smith at anheuser-busch.com]
> Sent: Wednesday, April 03, 2002 9:28 AM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      SWWERRE Job
>
> Workflowers,
>
> We are on SAP 4.6C.  Does anyone know the job name under which this
> SWWERRE
> program runs.  This is the background job one schedules to monitor
> workitems in
> error.  Our workflow config is complete and the activity where we
> scheduled this
> job has the job name listed as SWWERRE, the same as the name of the
> program.
> There is also a job number which I understand the job name and job =
number
> should
> make up the job name in SM37.  Even with our workflow config complete =
and
> this
> job is listed as scheduled, I can't see this job in SM37 under the job
> name and
> number.  Does this job not start unless there are workitems in error?  =
But
> I
> would think it has to at least start to see if there are any errors.
> Please
> advise on how I can see that this job ran in SM37.
>
> Thanks,
>
> Casey