<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2900.3020" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=076304503-16012007><FONT face=Arial
color=#0000ff size=2>Hi Ashish,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=076304503-16012007><FONT face=Arial
color=#0000ff size=2>We experienced similar "freezes" for no apparent
reason. We opened a customer message and SAP recommended applying a
note. I can't seem to find the message with the note number right
now. I don't know if the note worked, as we did an upgrade before getting
to test it, and we have not experienced the freezes since the upgrade.
Perhaps you can find it via an OSS search?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=076304503-16012007><FONT face=Arial
color=#0000ff size=2>Best Wishes,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=076304503-16012007><FONT face=Arial
color=#0000ff size=2>Sherie</FONT></SPAN></DIV>
<DIV dir=ltr align=left><BR> </DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu
[mailto:sap-wug-bounces@mit.edu] <B>On Behalf Of </B>Ashish
Paranjpe<BR><B>Sent:</B> Monday, January 15, 2007 11:21 AM<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> Re: Workflow steps remaining in ready
state for long<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hi Mike,</DIV>
<DIV>I checked all these jobs and they are all running properly, if
applicable. We dont have an event queue defined and hence the event queue job
does not run. The other jobs SWWDHEX and SWWERRE are running properly.</DIV>
<DIV> </DIV>
<DIV>Is there any other reason for the issue?</DIV>
<DIV> </DIV>
<DIV>Thanks and Regards,</DIV>
<DIV>Ashish<BR><BR> </DIV>
<DIV><SPAN class=gmail_quote>On 1/14/07, <B class=gmail_sendername>Mike
Gambier</B> <<A
href="mailto:madgambler@hotmail.com">madgambler@hotmail.com</A>>
wrote:</SPAN>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi
Ashish,<BR><BR>That sounds like a typical 'Workflow is broken' issue.<BR><BR>I
suggest you look at your Workflow services, the background jobs, to see
<BR>what's happening. After all SWEQSRV (events), SWWDHEX (deadlines)
and<BR>SWWERRE (exceptions) essentially are Workflow, although the RFC batch
job<BR>sometimes has to pick up the baton occasionally.<BR><BR>So if nothing's
happening, check if the jobs are still scheduled (SWEQADM <BR>and SWU3 will
give you clues but don't always tell the truth) and look in<BR>the batch log
to see how they have been performing (if at all) recently.<BR><BR>Sometimes
Basis Teams (or whoever schedules the jobs) forget to re-schedule <BR>them
when a system is bounced. But sometimes they can also terminate of<BR>their
own accord because of feedback errors.<BR><BR>Mike GT<BR><BR>>From: "Ashish
Paranjpe" <<A href="mailto:aaparanjpe@gmail.com">
aaparanjpe@gmail.com</A>><BR>>Reply-To: "SAP Workflow Users' Group"
<<A href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A>><BR>>To: "SAP
Workflow Users' Group" <<A href="mailto:sap-wug@mit.edu">
sap-wug@mit.edu</A>><BR>>Subject: Re: Workflow steps remaining in ready
state for long<BR>>Date: Fri, 12 Jan 2007 19:34:38 +0100<BR>><BR>>HI
Mike,<BR>>Thanks for the reply. Just to make sure that I have been able to
convey my <BR>>issue correctly, I am adding the following
things:<BR>><BR>>1. I gave the first step as an example. This does not
necessarily happen at<BR>>the first step. This may happen at any step in
the workflow(being stuck as <BR>>ready status).<BR>><BR>>2. This is
happening across the entire workflow system in<BR>>workflows developed for
all modules.<BR>><BR>><BR>>Does this make the issue different or
clearer?<BR>><BR>>Thanks,<BR>>Ashish<BR>><BR>><BR>>On
1/12/07, Mike Gambier <<A
href="mailto:madgambler@hotmail.com">madgambler@hotmail.com</A>>
wrote:<BR>>><BR>>>Ashish,<BR>>><BR>>>If I were you I'd
check the following things to start with: <BR>>><BR>>>1. Is this a
new/amended step? If so, are there any temporary exceptions<BR>>>(e.g.
database locks) being fed back? Check in tech log if it is on,
or<BR>>>failing that have a look in SWWWIRET to see if there are any
clues there. <BR>>>If<BR>>>you find you do have temporary
exceptions make sure you activated the<BR>>>Workflow exception handling
batch job SWWERRE to have another go at trying<BR>>>the steps again
(check in SWU3). <BR>>><BR>>>2. If you have changed anything on
related to the WF definition or<BR>>>Business<BR>>>Object related
to the task that is appearing to stubbornly refuse to start<BR>>>(but it
used to work fine), it's probably something in your
<BR>>>code/environment<BR>>>causing a feedback error. Syntax check
your WF and code for errors, such<BR>>>as<BR>>>Agent Determination
missing on dialog steps elsehwere in the definition.<BR>>>Try
<BR>>>generating the Business Object, make sure the WF you are
triggering is<BR>>>active on the right version and the event linkage
looks right. Drop the<BR>>>Workflow buffers using SWU_OBUF to be sure
you are using the latest <BR>>>versions<BR>>>of everything, if in
doubt, and try to trigger the same WF again
using<BR>>>SWUE<BR>>>maybe.<BR>>><BR>>>3. Check the
data related to your 'stuck' steps. Are all of your WFs
<BR>>>hanging<BR>>>at this point or are some working OK? If the
latter is true then your<BR>>>definition may be dodgy with regards to
binding or logic and may need<BR>>>revising. Normally this would error
though rather than stall, but you
<BR>>>never<BR>>>know.<BR>>><BR>>>4. If you have
changed the way the WF is triggered (perhaps a different<BR>>>event
entirely or a new container binding) make sure the WF being
kicked<BR>>>off <BR>>>is receiving the new info properly. Perhaps
your event raising code isn't<BR>>>quite right
now?<BR>>><BR>>>5. Check for dumps to see if WF-BATCH is
complaining about something that<BR>>>might be related.
<BR>>><BR>>>6. If this is the first step in your Workflow and
you're using the Event<BR>>>Queue check to see what kind of 'delay' you
have between delivery jobs.<BR>>>Sometimes events can take a while to
come through because they have lots <BR>>>of<BR>>>competition with
other events. Wouldn't explain why your first
step<BR>>>appears<BR>>>to be 'stuck' but it might explain why
there's an apparent delay between<BR>>>events and WFs starting.
<BR>>><BR>>>7. Sometimes the triggering event is only partially
delivered and the call<BR>>>to your next step ends up being parked
temporarily as a tRFC entry in<BR>>>ARFCSSTATE for destination
WORKFLOW_LOCAL_100 if the aren't enough dialog <BR>>>process for
Workflow to get hold of at the time. Have a peak at the RFC<BR>>>queue
to see if this is filling up.<BR>>><BR>>>Mike
GT<BR>>><BR>>> >From: "Ashish Paranjpe" < <A
href="mailto:aaparanjpe@gmail.com">aaparanjpe@gmail.com</A>><BR>>>
>Reply-To: "SAP Workflow Users' Group" <<A
href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</A>><BR>>> >To: <A
href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR>>> >Subject:
Workflow steps remaining in ready state for long<BR>>> >Date: Fri, 12
Jan 2007 15:38:34 +0100<BR>>> ><BR>>> >Hi All,<BR>>>
>I am facing a very atypical issue which I will try and explain below:
<BR>>> ><BR>>> >When a workflow is triggered in the system,
the first step of the<BR>>>workflow<BR>>> >is a background
step. Now Ideally, i would have expected this step to<BR>>> >change
<BR>>> >from "READY" state to "INPROCESS" within a fraction of a
second. What<BR>>> >happens with our workflows is that these steps
continue to remain în<BR>>> >"READY" state for 2-3 hrs.
Please note that there is no deadline <BR>>>monitoring<BR>>>
>active for these steps.<BR>>> ><BR>>> >I have 2
questions based on this:<BR>>> ><BR>>> >1. How does the
workflow system function with regard to changing a step <BR>>>
>state?<BR>>> >2. More important quaetion : Why is this above
mentioned problem<BR>>>occurring<BR>>> >in our system? Is it
something to do with system performance?<BR>>> ><BR>>>
><BR>>> >I may have raised this question before, but could not get
a proper<BR>>>solution<BR>>> >to the issue.<BR>>>
><BR>>> >Thanks in advance.<BR>>> ><BR>>>
>Ashish <BR>>><BR>>><BR>>>
>_______________________________________________<BR>>> >SAP-WUG
mailing list<BR>>> ><A
href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR>>> ><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">
http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR>>><BR>>>_________________________________________________________________<BR>>>Communicate
instantly! Use your Hotmail address to sign into Windows Live
<BR>>>Messenger now. <A
href="http://get.live.com/messenger/overview">http://get.live.com/messenger/overview</A><BR>>><BR>>><BR>>><BR>>>_______________________________________________<BR>>>SAP-WUG
mailing list <BR>>><A
href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR>>><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR>>><BR>>><BR>>>
<BR><BR><BR>>_______________________________________________<BR>>SAP-WUG
mailing list<BR>><A
href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR>><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug
</A><BR><BR>_________________________________________________________________<BR>Communicate
instantly! Use your Hotmail address to sign into Windows Live<BR>Messenger
now. <A
href="http://get.live.com/messenger/overview">http://get.live.com/messenger/overview</A><BR><BR><BR><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR><A href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</A><BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR><BR></BLOCKQUOTE></DIV><BR></BODY></HTML>