WF-BATCH

Tue Jul 20 11:03:50 EDT 2004

the jobs listed as scheduled in QSS only also be run in PSS?  What do
these jobs do?

SWWDHEX 3 MIN           RSWWDHEX (scheduled in QSS only)
SWEQSRV 5 MIN           RSWEQSRV (scheduled in QSS only)
SWWCLEAR        DAILY           RSWWCLEAR (scheduled in QSS only)
SWWCOND 30 MIN  RSWWCOND (scheduled in QSS only)
SWWERRE HRLY            RSWWERRE (QSS and PSS)

Monique Stephens

-----Original Message-----
From: Stephens, Monique S L=20
Sent: Tuesday, July 20, 2004 9:25 AM
To: 'SAP Workflow Users' Group'
Cc: Dillow, Nancy P
Subject: RE: WF-BATCH

Since I am more of a functional person, I really would not know how to
answer your question below.  I would need to pass this on to our
technical workflow expert.

Most of the PO's are getting stuck in the same work center.  But, other
PO's that would bypass this work center are getting passed it.  I don't
know if there could be a delay in processing due to the new transaction
code for releasing documents from the workflow inbox (ME29N).  WF-BATCH
releases via ME28.

I really appreciate all your help. =20

Monique

-----Original Message-----
From: Kouw, FA - SPLXE [mailto:fa.kouw at td.klm.com]
Sent: Tuesday, July 20, 2004 9:15 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WF-BATCH

Hi Monique,

'it will skip over that work center via WF-BATCH': WF-BATCH is the
(background) user that performs automated tasks on the background. My
first quess would be that the data or routine used to determine the work
center is not consistent, is it possible for you to test/check your
'work center determination routine' on production?
Otherwise I have no idea how to solve this.

Regards,

Fred Kouw

"Stephens, Monique S L" wrote:

> This is the problem we are having in PSS:
>
> PO's are created by the departmental end user and routed through work=20
> centers based on certain criteria (account assignment, material group,

> amount, etc.).  If the PO does not need to be released by a particular

> work center, it will skip over that work center via WF-BATCH and move=20
> on to the next work center.
>
> I am unable to re-create the problem in QSS and noticed that there are

> several jobs under WF-BATCH in that environment.  There are no jobs=20
> under WF-BATCH in PSS.  The only job in PSS is SWWERRE (run hourly).
>
> Not all of the PO's are getting stuck in the wrong work center.  I am=20
> not able to find any common links.  I had assumed that someone had=20
> changed the timing of the scheduled jobs because we were having some=20
> issues with our FI parked documents not posting.  It was determined=20
> that the cause of that was due to new fields brought over in funds=20
> management, not WF-BATCH.
>
> Monique
>
> -----Original Message-----
>> From: Kouw, FA - SPLXE [mailto:fa.kouw at td.klm.com]
> Sent: Tuesday, July 20, 2004 8:14 AM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: WF-BATCH
>
> Hi Monique,
>
> This depends on the specific job and the way the workflows are=20
> modelled (how many deadlines, need for retry of temporary errors). So=20
> I can't give you an answer to your question.
>
> In our system (4.6C) the following workflow related jobs are
scheduled:
>
>    * SWWERRE: error monitoring - runs every 20 minutes
>    * SWWDHEX: deadline monitoring   runs every 15 minutes
>
> But before you change something to your scheduling I would suggest you

> to further investigate/analyze your problem, i.e. is it really related

> to the scheduling of the jobs?
>
> Regards,
>
> Fred Kouw
>
> "Stephens, Monique S L" wrote:
>
> > I looked under SM37.  There are several jobs that start with SW* for

> > user ID WF-BATCH.  How do I determine how often they should run?
> >
> > Monique Stephens
> >
> > -----Original Message-----
> > From: Kouw, FA - SPLXE [mailto:fa.kouw at td.klm.com]
> > Sent: Tuesday, July 20, 2004 3:06 AM
> > To: SAP-WUG at MITVMA.MIT.EDU
> > Subject: Re: WF-BATCH
> >
> > Hi Monique,
> >
> > 'Timing of WF-BATCH' doesn't ring a bell, but maybe you mean the=20
> > timing of workflow related jobs that are scheduled under userID=20
> > WF-BATCH? The scheduling of these jobs can be determined using tx=20
> > SM37, job name 'SW*', userID 'WF-BATCH' (or '*').
> >
> > Hope this helps.
> >
> > Regards,
> >
> > Fred
> >
> > "Stephens, Monique S L" wrote:
> >
> > > How do you determine the timing of WF-BATCH?  I think someone in=20
> > > our
>
> > > Basis group changed the timing recently because we are getting=20
> > > several
> >
> > > PO's stuck in the wrong work center (status is Completed, not in=20
> > > Process).  These PO's would have normally passed this work center=20
> > > via WF-BATCH.  But, we were having other issues related to=20
> > > workflow for our parked documents and I think the timing of=20
> > > WF-BATCH was altered in
> >
> > > the hopes that it would fix our parked documents issue.
> > >
> > > Unfortunately, the person that may have changed the timing is on=20
> > > vacation.\
> > >
> > > We are on 4.7, if that makes a difference.
> > >
> > >
> > > Monique Stephens
> > >
> > > SAP Analyst
> > >
> > > Baylor College of Medicine
> > >
> > > 713-798-1349
> > >
> > > 713-798-1326 (FAX)
> > >
> > >
> > >
> > >
> > >
> > > __________________________________________________________________
> > > __ __ ___________________ This inbound message from KPN has been=20
> > > checked for
> >
> > > all known viruses by KPN IV-Scan, powered by MessageLabs.
> > > For further information visit: http://www.veiliginternet.nl=20
> > > __________________________________________________________________
> > > __
> > > __
> > > _______________________
> >
> > Please visit http://www.klm-em.com for information about KLM=20
> > Engineering & Maintenance products and services.
> >
> > ********************************************************************
> > ** This e-mail and any attachment may contain confidential and=20
> > privileged
>
> > material intended for the addressee only. If you are not the=20
> > addressee, you are notified that no part of the e-mail or any=20
> > attachment may be disclosed, copied or distributed, and that any=20
> > other
>
> > action related to this e-mail or attachment is strictly prohibited,
> and may be unlawful.
> > If you have received this e-mail by error, please notify the sender=20
> > immediately by return e-mail, and delete this message. Koninklijke=20
> > Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its=20
> > employees shall not be liable for the incorrect or incomplete=20
> > transmission of this e-mail or any attachments, nor responsible for
> any delay in receipt.
> > ********************************************************************
> > **
> >
> > ____________________________________________________________________
> > __
> > __
> > _____________________
> > This outbound message from KPN has been checked for all known=20
> > viruses by KPN IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl=20
> > ____________________________________________________________________
> > __
> > __
> > _____________________
> >
> > ____________________________________________________________________
> > __ ___________________ This inbound message from KPN has been=20
> > checked for
>
> > all known viruses by KPN IV-Scan, powered by MessageLabs.
> > For further information visit: http://www.veiliginternet.nl=20
> > ____________________________________________________________________
> > __
> > _______________________
>
> Please visit http://www.klm-em.com for information about KLM=20
> Engineering & Maintenance products and services.
>
> **********************************************************************
> This e-mail and any attachment may contain confidential and privileged

> material intended for the addressee only. If you are not the=20
> addressee, you are notified that no part of the e-mail or any=20
> attachment may be disclosed, copied or distributed, and that any other

> action related to this e-mail or attachment is strictly prohibited,
and may be unlawful.
> If you have received this e-mail by error, please notify the sender=20
> immediately by return e-mail, and delete this message. Koninklijke=20
> Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its=20
> employees shall not be liable for the incorrect or incomplete=20
> transmission of this e-mail or any attachments, nor responsible for
any delay in receipt.
> **********************************************************************
>
> ______________________________________________________________________
> __
> _____________________
> This outbound message from KPN has been checked for all known viruses=20
> by KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl=20
> ______________________________________________________________________
> __
> _____________________
>
> ______________________________________________________________________
> ___________________ This inbound message from KPN has been checked for

> all known viruses by KPN IV-Scan, powered by MessageLabs.
> For further information visit: http://www.veiliginternet.nl=20
> ______________________________________________________________________
> _______________________

Please visit http://www.klm-em.com for information about KLM Engineering
& Maintenance products and services.

**********************************************************************
This e-mail and any attachment may contain confidential and privileged
material intended for the addressee only. If you are not the addressee,
you are notified that no part of the e-mail or any attachment may be
disclosed, copied or distributed, and that any other action related to
this e-mail or attachment is strictly prohibited, and may be unlawful.
If you have received this e-mail by error, please notify the sender
immediately by return e-mail, and delete this message. Koninklijke
Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees
shall not be liable for the incorrect or incomplete transmission of this
e-mail or any attachments, nor responsible for any delay in receipt.
**********************************************************************

________________________________________________________________________
_____________________
This outbound message from KPN has been checked for all known viruses by
KPN IV-Scan, powered by MessageLabs.
For further information visit: http://www.veiliginternet.nl
________________________________________________________________________
_____________________