<div>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&nbsp;error message which is attached.</div>
<div>&nbsp;</div>
<div>Mark</div>
<div>&nbsp;</div>
<div><br><br>&nbsp;</div>
<div class="gmail_quote">On Mon, Dec 15, 2008 at 6:00 AM, Ramki Maley <span dir="ltr">&lt;<a href="mailto:rmaley@erpworkflow.com">rmaley@erpworkflow.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Mark,<br><br>You did not mention what the object is. In SRM, for a Shopping Cart, the<br>workflow instance is created when the SC is held. The same instance<br>
starts off when the SC is &#39;Saved&#39;. The process may be the same for other<br>object types as well. It is up to the creator of the object to decide<br>when to save the object and start the workflow process. You may want to<br>
find from the creator whether the object was intentionally held.<br><br>Cheers,<br>Ramki.<br>
<div class="Ih2E3d"><br><br>Keohan, Susan wrote:<br>&gt; Hi Mark,<br>&gt;<br>&gt; I would check that Holding a document is OK by the business rules – and<br>&gt; then keep an eye on these to see what happens when the user completes<br>
&gt; processing. &nbsp;Otherwise, it doesn't sound like anything to worry about.<br>&gt; Once the wait step it over, the workflow should proceed to either the<br>&gt; next level of approval or to release the document, correct?<br>
&gt;<br>&gt; Cheers,<br>&gt;<br>&gt; Sue<br>&gt;<br>&gt;<br>&gt;<br>&gt; ---<br>&gt;<br>&gt; Susan R. Keohan<br>&gt;<br>&gt; SAP Workflow Specialist<br>&gt;<br>&gt; MIT Lincoln Laboratory<br>&gt;<br>&gt; 244 Wood Street<br>
&gt;<br>&gt; LI-200<br>&gt;<br>&gt; Lexington, MA. 02420<br>&gt;<br>&gt; Phone: 781-981-3561<br>&gt;<br>&gt; Fax: &nbsp; 781-981-1607<br>&gt;<br></div>&gt; <a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a> &lt;mailto:<a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a>&gt;<br>

<div class="Ih2E3d">&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt; *From:* <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] *On<br>
&gt; Behalf Of *Mark Williams<br>&gt; *Sent:* Sunday, December 14, 2008 11:31 PM<br>&gt; *To:* SAP Workflow Users&#39; Group<br>&gt; *Subject:* Re: Workitems in waiting state for 2 days<br>&gt;<br>&gt;<br>&gt;<br>&gt; Yes, there are 4 header lines and the first lines has the status I1009<br>
&gt; with the description as &quot;Held&quot;. What should be done in this case.<br>&gt;<br>&gt;<br>&gt;<br>&gt; Mark<br>&gt;<br></div>&gt; 2008/12/14 Keohan, Susan &lt;<a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a> &lt;mailto:<a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a>&gt;&gt;<br>

<div class="Ih2E3d">&gt;<br>&gt; Hi Mark,<br>&gt;<br>&gt;<br>&gt;<br>&gt; Try the backend transaction BBP_PD to see if the object is on hold.<br>&gt;<br>&gt; With the sporadic nature of the instances you are talking about, it<br>
&gt; sounds like a business document issue to me.<br>&gt;<br>&gt;<br>&gt; Good luck,<br>&gt; Sue<br>&gt;<br>&gt;<br>&gt;<br>&gt; ---<br>&gt;<br>&gt; Susan R. Keohan<br>&gt;<br>&gt; SAP Workflow Specialist<br>&gt;<br>&gt; MIT Lincoln Laboratory<br>
&gt;<br>&gt; 244 Wood Street<br>&gt;<br>&gt; LI-200<br>&gt;<br>&gt; Lexington, MA. 02420<br>&gt;<br>&gt; Phone: 781-981-3561<br>&gt;<br>&gt; Fax: &nbsp; 781-981-1607<br>&gt;<br></div>&gt; <a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a> &lt;mailto:<a href="mailto:keohan@ll.mit.edu">keohan@ll.mit.edu</a>&gt;<br>

<div class="Ih2E3d">&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt; *From:* <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> &lt;mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>&gt;<br>
</div>&gt; [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> &lt;mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>&gt;] *On<br>
<div class="Ih2E3d">&gt; Behalf Of *Mark Williams<br>&gt; *Sent:* Sunday, December 14, 2008 5:55 PM<br>&gt; *To:* SAP Workflow Users&#39; Group<br>&gt; *Subject:* Re: Workitems in waiting state for 2 days<br>&gt;<br>&gt;<br>
&gt;<br>&gt; It is a workflow. Where do I go to check if the triggering object is in<br>&gt; Hold status. Do you think any of the SRM service jobs may have stopped<br>&gt; causing this problem.<br>&gt;<br>&gt;<br>&gt;<br>
&gt; Mark<br>&gt;<br>&gt; On Sun, Dec 14, 2008 at 5:59 AM, Ramki Maley &lt;<a href="mailto:rmaley@erpworkflow.com">rmaley@erpworkflow.com</a><br></div>
<div class="Ih2E3d">&gt; &lt;mailto:<a href="mailto:rmaley@erpworkflow.com">rmaley@erpworkflow.com</a>&gt;&gt; wrote:<br>&gt;<br>&gt; Is it a workitem of a step(dialog/background) type or the top level<br>&gt; workitem (workflow) that is in Wait status? If it is &nbsp;workflow, check if<br>
&gt; the triggering object is in &#39;Hold&#39; status.<br>&gt;<br>&gt; Cheers,<br>&gt; Ramki.<br>&gt;<br>&gt;<br>&gt; Mark Williams wrote:<br>&gt; &nbsp;&gt; Could anyone tell me how to push the workitems from waiting state to<br>
&gt; &nbsp;&gt; Ready. In the past two days there are some SRM workflows get triggerred<br>&gt; &nbsp;&gt; and go into waiting state though there is no requested start or wait<br>&gt; &nbsp;&gt; step. Again there are some other instances of the same workflow which<br>
&gt; &nbsp;&gt; are working fine. These have been working fine all along and no changes<br>&gt; &nbsp;&gt; were made to these workflow atleast in the past 6 months. Its not<br>&gt; &nbsp;&gt; related to a single user or single workflow. I know of atleast 2<br>
&gt; &nbsp;&gt; workflows which is behaving in this way. Could anyone let me know what<br>&gt; &nbsp;&gt; could be the problem and how to resolve this. If you need more<br>&gt; &nbsp;&gt; information, I would be happy to provide.<br>&gt; &nbsp;&gt;<br>
&gt; &nbsp;&gt;<br>&gt;<br>&gt; &nbsp;&gt; ------------------------------------------------------------------------<br>&gt; &nbsp;&gt;<br>&gt; &nbsp;&gt; _______________________________________________<br>&gt; &nbsp;&gt; SAP-WUG mailing list<br></div>
&gt; &nbsp;&gt; <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a> &lt;mailto:<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>&gt;<br>
<div class="Ih2E3d">&gt; &nbsp;&gt; <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>&gt; _______________________________________________<br>&gt; SAP-WUG mailing list<br>
</div>&gt; <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a> &lt;mailto:<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>&gt;<br>
<div class="Ih2E3d">&gt; <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt; _______________________________________________<br>
&gt; SAP-WUG mailing list<br></div>&gt; <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a> &lt;mailto:<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>&gt;<br>
<div>
<div></div>
<div class="Wj3C7c">&gt; <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt; ------------------------------------------------------------------------<br>
&gt;<br>&gt; _______________________________________________<br>&gt; SAP-WUG mailing list<br>&gt; <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>&gt; <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><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" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
</div></div></blockquote></div><br>