Workitems in waiting state for 2 days

[Mark Williams]

The RFQs are working fine after the user Republish them. But the GOA is
still going nowhere. When the user tries to publish it, it gives error
message which is attached.

Mark




On Mon, Dec 15, 2008 at 6:00 AM, Ramki Maley <rmaley at erpworkflow.com> wrote:

> Mark,
>
> You did not mention what the object is. In SRM, for a Shopping Cart, the
> workflow instance is created when the SC is held. The same instance
> starts off when the SC is 'Saved'. The process may be the same for other
> object types as well. It is up to the creator of the object to decide
> when to save the object and start the workflow process. You may want to
> find from the creator whether the object was intentionally held.
>
> Cheers,
> Ramki.
>
>
> Keohan, Susan wrote:
> > Hi Mark,
> >
> > I would check that Holding a document is OK by the business rules – and
> > then keep an eye on these to see what happens when the user completes
> > processing.  Otherwise, it doesn't sound like anything to worry about.
> > Once the wait step it over, the workflow should proceed to either the
> > next level of approval or to release the document, correct?
> >
> > Cheers,
> >
> > Sue
> >
> >
> >
> > ---
> >
> > Susan R. Keohan
> >
> > SAP Workflow Specialist
> >
> > MIT Lincoln Laboratory
> >
> > 244 Wood Street
> >
> > LI-200
> >
> > Lexington, MA. 02420
> >
> > Phone: 781-981-3561
> >
> > Fax:   781-981-1607
> >
> > keohan at ll.mit.edu <mailto:keohan at ll.mit.edu>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> > Behalf Of *Mark Williams
> > *Sent:* Sunday, December 14, 2008 11:31 PM
> > *To:* SAP Workflow Users' Group
> > *Subject:* Re: Workitems in waiting state for 2 days
> >
> >
> >
> > Yes, there are 4 header lines and the first lines has the status I1009
> > with the description as "Held". What should be done in this case.
> >
> >
> >
> > Mark
> >
> > 2008/12/14 Keohan, Susan <keohan at ll.mit.edu <mailto:keohan at ll.mit.edu>>
> >
> > Hi Mark,
> >
> >
> >
> > Try the backend transaction BBP_PD to see if the object is on hold.
> >
> > With the sporadic nature of the instances you are talking about, it
> > sounds like a business document issue to me.
> >
> >
> > Good luck,
> > Sue
> >
> >
> >
> > ---
> >
> > Susan R. Keohan
> >
> > SAP Workflow Specialist
> >
> > MIT Lincoln Laboratory
> >
> > 244 Wood Street
> >
> > LI-200
> >
> > Lexington, MA. 02420
> >
> > Phone: 781-981-3561
> >
> > Fax:   781-981-1607
> >
> > keohan at ll.mit.edu <mailto:keohan at ll.mit.edu>
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > *From:* sap-wug-bounces at mit.edu <mailto:sap-wug-bounces at mit.edu>
> > [mailto:sap-wug-bounces at mit.edu <mailto:sap-wug-bounces at mit.edu>] *On
> > Behalf Of *Mark Williams
> > *Sent:* Sunday, December 14, 2008 5:55 PM
> > *To:* SAP Workflow Users' Group
> > *Subject:* Re: Workitems in waiting state for 2 days
> >
> >
> >
> > It is a workflow. Where do I go to check if the triggering object is in
> > Hold status. Do you think any of the SRM service jobs may have stopped
> > causing this problem.
> >
> >
> >
> > Mark
> >
> > On Sun, Dec 14, 2008 at 5:59 AM, Ramki Maley <rmaley at erpworkflow.com
> > <mailto:rmaley at erpworkflow.com>> wrote:
> >
> > Is it a workitem of a step(dialog/background) type or the top level
> > workitem (workflow) that is in Wait status? If it is  workflow, check if
> > the triggering object is in 'Hold' status.
> >
> > Cheers,
> > Ramki.
> >
> >
> > Mark Williams wrote:
> >  > Could anyone tell me how to push the workitems from waiting state to
> >  > Ready. In the past two days there are some SRM workflows get
> triggerred
> >  > and go into waiting state though there is no requested start or wait
> >  > step. Again there are some other instances of the same workflow which
> >  > are working fine. These have been working fine all along and no
> changes
> >  > were made to these workflow atleast in the past 6 months. Its not
> >  > related to a single user or single workflow. I know of atleast 2
> >  > workflows which is behaving in this way. Could anyone let me know what
> >  > could be the problem and how to resolve this. If you need more
> >  > information, I would be happy to provide.
> >  >
> >  >
> >
> >  >
> ------------------------------------------------------------------------
> >  >
> >  > _______________________________________________
> >  > SAP-WUG mailing list
> >  > SAP-WUG at mit.edu <mailto:SAP-WUG at mit.edu>
> >  > http://mailman.mit.edu/mailman/listinfo/sap-wug
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu <mailto:SAP-WUG at mit.edu>
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
> >
> >
> >
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu <mailto: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
> _______________________________________________
> SAP-WUG mailing list
> 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/20081215/e8f767d2/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: screenshot.jpg
Type: image/jpeg
Size: 33894 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20081215/e8f767d2/attachment.jpg