10 minute delay

Thu Mar 19 12:04:30 EDT 2009

	I'm using the starting a workflow from a message (see page 317 Practical Workflow for SAP). This allows
	the user to click on the error message and then click on the WF icon to start the WF..... 

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Mike Pokraka
Sent: Thursday, March 19, 2009 8:46 AM
To: 'SAP Workflow Users' Group'
Subject: RE: 10 minute delay

Hi Jerry, 

It would help to know how the workflow is started. 
One scenario which can produce the symptoms you describe is a locking problem which can be resolved by SWWERRE, although I've never seen this with a workflow starting. 
It might help to poke around SM58 during this 10 minute period, that would most likely tell you where/why it's hanging. 

Cheers,
Mike

> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
> Behalf Of Miller, Jerry
> Sent: 18 March 2009 15:37
> To: sap-wug at mit.edu
> Subject: 10 minute delay
> 
> 
> 	Workflow'ers
> 
> 	In the email below Mike stated "the RFC batch job sometimes has
> to pick up the baton...."
> 
> 	What is the name of the "RFC batch job"?
> 
> 	Here is my issue, we are upgrading from 4.6C to ECC6. I have a
> workflow that starts in the background
> 	and in my 4.6C system it starts immediately but in the ECC6
> system there is a 10 minute delay and
> 	seems to be tied to the batch job SWWERRE.
> 
> 	What do I need to do to get the workflow to start immediately in
> the ECC6 system?
> 
> 	tks,
> 	Jerry
> 
> -----Original Message-----
> From: Mike Gambier [mailto:madgambler at hotmail.com]
> Sent: Sunday, January 14, 2007 5:06 AM
> To: sap-wug at mit.edu
> Subject: Re: Workflow steps remaining in ready state for long
> 
> Hi Ashish,
> 
> That sounds like a typical 'Workflow is broken' issue.
> 
> I suggest you look at your Workflow services, the background jobs, to
> see what's happening. After all SWEQSRV (events), SWWDHEX (deadlines)
> and SWWERRE (exceptions) essentially are Workflow, although the RFC
> batch job sometimes has to pick up the baton occasionally.
> 
> So if nothing's happening, check if the jobs are still scheduled
> (SWEQADM and SWU3 will give you clues but don't always tell the truth)
> and look in the batch log to see how they have been performing (if at
> all) recently.
> 
> Sometimes Basis Teams (or whoever schedules the jobs) forget to re-
> schedule them when a system is bounced. But sometimes they can also
> terminate of their own accord because of feedback errors.
> 
> Mike GT
> 
> >From: "Ashish Paranjpe" <aaparanjpe at gmail.com>
> >Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> >To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> >Subject: Re: Workflow steps remaining in ready state for long
> >Date: Fri, 12 Jan 2007 19:34:38 +0100
> >
> >HI Mike,
> >Thanks for the reply. Just to make sure that I have been able to
> convey
> >my issue correctly, I am adding the following things:
> >
> >1. I gave the first step as an example. This does not necessarily
> >happen at the first step. This may happen at any step in the
> >workflow(being stuck as ready status).
> >
> >2. This is happening across the entire workflow system in workflows
> >developed for all modules.
> >
> >
> >Does this make the issue different or clearer?
> >
> >Thanks,
> >Ashish
> >
> >
> >On 1/12/07, Mike Gambier <madgambler at hotmail.com> wrote:
> >>
> >>Ashish,
> >>
> >>If I were you I'd check the following things to start with:
> >>
> >>1. Is this a new/amended step? If so, are there any temporary
> >>exceptions (e.g. database locks) being fed back? Check in tech log if
> >>it is on, or failing that have a look in SWWWIRET to see if there are
> any clues there.
> >>If
> >>you find you do have temporary exceptions make sure you activated the
> >>Workflow exception handling batch job SWWERRE to have another go at
> >>trying the steps again (check in SWU3).
> >>
> >>2. If you have changed anything on related to the WF definition or
> >>Business Object related to the task that is appearing to stubbornly
> >>refuse to start (but it used to work fine), it's probably something
> in
> >>your code/environment causing a feedback error. Syntax check your WF
> >>and code for errors, such as Agent Determination missing on dialog
> >>steps elsehwere in the definition.
> >>Try
> >>generating the Business Object, make sure the WF you are triggering
> is
> >>active on the right version and the event linkage looks right. Drop
> >>the Workflow buffers using SWU_OBUF to be sure you are using the
> >>latest versions of everything, if in doubt, and try to trigger the
> >>same WF again using SWUE maybe.
> >>
> >>3. Check the data related to your 'stuck' steps. Are all of your WFs
> >>hanging at this point or are some working OK? If the latter is true
> >>then your definition may be dodgy with regards to binding or logic
> and
> >>may need revising. Normally this would error though rather than
> stall,
> >>but you never know.
> >>
> >>4. If you have changed the way the WF is triggered (perhaps a
> >>different event entirely or a new container binding) make sure the WF
> >>being kicked off is receiving the new info properly. Perhaps your
> >>event raising code isn't quite right now?
> >>
> >>5. Check for dumps to see if WF-BATCH is complaining about something
> >>that might be related.
> >>
> >>6. If this is the first step in your Workflow and you're using the
> >>Event Queue check to see what kind of 'delay' you have between
> delivery jobs.
> >>Sometimes events can take a while to come through because they have
> >>lots of competition with other events. Wouldn't explain why your
> first
> >>step appears to be 'stuck' but it might explain why there's an
> >>apparent delay between events and WFs starting.
> >>
> >>7. Sometimes the triggering event is only partially delivered and the
> >>call to your next step ends up being parked temporarily as a tRFC
> >>entry in ARFCSSTATE for destination WORKFLOW_LOCAL_100 if the aren't
> >>enough dialog process for Workflow to get hold of at the time. Have a
> >>peak at the RFC queue to see if this is filling up.
> >>
> >>Mike GT
> >>
> >> >From: "Ashish Paranjpe" <aaparanjpe at gmail.com>
> >> >Reply-To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> >> >To: SAP-WUG at mit.edu
> >> >Subject: Workflow steps remaining in ready state for long
> >> >Date: Fri, 12 Jan 2007 15:38:34 +0100
> >> >
> >> >Hi All,
> >> >I am facing a very atypical issue which I will try and explain
> below:
> >> >
> >> >When a workflow is triggered in the system, the first step of the
> >>workflow
> >> >is a background step. Now Ideally, i would have expected this step
> >> >to change from "READY" state to "INPROCESS" within a fraction of a
> >> >second. What happens with our workflows is that these steps
> continue
> >> >to remain  în "READY" state for 2-3 hrs. Please note that there is
> >> >no deadline
> >>monitoring
> >> >active for these steps.
> >> >
> >> >I have 2 questions based on this:
> >> >
> >> >1. How does the workflow system function with regard to changing a
> >> >step state?
> >> >2. More important quaetion : Why is this above mentioned problem
> >>occurring
> >> >in our system? Is it something to do with system performance?
> >> >
> >> >
> >> >I may have raised this question before, but could not get a proper
> >>solution
> >> >to the issue.
> >> >
> >> >Thanks in advance.
> >> >
> >> >Ashish
> >>
> >>
> >> >_______________________________________________
> >> >SAP-WUG mailing list
> >> >SAP-WUG at mit.edu
> >> >http://mailman.mit.edu/mailman/listinfo/sap-wug
> >>
> >>_________________________________________________________________
> >>Communicate instantly! Use your Hotmail address to sign into Windows
> >>Live Messenger now. http://get.live.com/messenger/overview
> >>
> >>
> >>
> >>_______________________________________________
> >>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
> 
> _________________________________________________________________
> Communicate instantly! Use your Hotmail address to sign into Windows
> Live Messenger now. http://get.live.com/messenger/overview
> 
> 
> _______________________________________________
> 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