<p>Hi Paul,</p>
<p>Workflow class are persistent objects. So you need to use instatiated object of subclass to call its methods.</p>
<p>Hope this solves your problem.</p>
<p>Regards,<br>
Guru</p>
<div class="gmail_quote">On Jun 6, 2012 8:06 PM,  &lt;<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>&gt; wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Send SAP-WUG mailing list submissions to<br>
        <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
        <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
or, via email, send a message with subject or body &#39;help&#39; to<br>
        <a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br>
<br>
You can reach the person managing the list at<br>
        <a href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than &quot;Re: Contents of SAP-WUG digest...&quot;<br>
<br>
<br>
Today&#39;s Topics:<br>
<br>
   1. trying to use subclass in workflow, but superclass is<br>
      instantiated (<a href="mailto:Paul.Bakker@osr.qld.gov.au">Paul.Bakker@osr.qld.gov.au</a>)<br>
   2. Re: trying to use subclass in workflow, but superclass is<br>
      instantiated (Florin Wach)<br>
   3. Re: SAP-WUG Digest, Vol 91, Issue 8 (Naveen Kusuma)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 6 Jun 2012 11:17:49 +1000<br>
From: <a href="mailto:Paul.Bakker@osr.qld.gov.au">Paul.Bakker@osr.qld.gov.au</a><br>
Subject: trying to use subclass in workflow, but superclass is<br>
        instantiated<br>
To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
Message-ID: &lt;<a href="mailto:201206060118.q561Hk1f023855@mailhub-dmz-4.mit.edu">201206060118.q561Hk1f023855@mailhub-dmz-4.mit.edu</a>&gt;<br>
Content-Type: text/plain; charset=&quot;us-ascii&quot;<br>
<br>
<br>
Hello WUG OO experts,<br>
<br>
As time goes on, I&#39;m gradually switching my new workflow developments to<br>
OO, just to see what the benefits are.<br>
<br>
Anyway, I have just run into a strange problem. I have defined a superclass<br>
ZCl_CLASS and a subclass ZCL_SUB_CLASS.<br>
<br>
The subclass inherits all the methods of the superclass, and you can<br>
redefine them, which is good. However I&#39;ve noticed that you can&#39;t redefine<br>
the critical method BI_PERSISTENT~FIND_BY_LPOR, because it is a &#39;static&#39;<br>
method.<br>
<br>
This causes a big problem when I start a workflow containing a<br>
ZCL_SUB_CLASS object, because I&#39;ve found that FIND_BY_LPOR instantiates an<br>
object of type ZCL_CLASS in the container!<br>
<br>
The workflow therefore runs into an error when it tries to execute<br>
ZCL_SUB_CLASS-&gt;MY_SUBCLASS_METHOD... it reports that the method does not<br>
exist.<br>
<br>
I must be doing something wrong.. but what is it?<br>
<br>
merci,<br>
<br>
Paul Bakker<br>
<br>
<br>
*********************************************************************************************<br>
Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments.  Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.<br>

<br>
The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright.  If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments.  Queensland Treasury uses virus scanning software.  However, it is not liable for viruses present in this e-mail or in any attachment.<br>

***************************************************************************************************<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Wed, 06 Jun 2012 16:14:03 +0200<br>
From: &quot;Florin Wach&quot; &lt;<a href="mailto:florin.wach@gmx.net">florin.wach@gmx.net</a>&gt;<br>
Subject: Re: trying to use subclass in workflow, but superclass is<br>
        instantiated<br>
To: &quot;SAP Workflow Users&#39; Group&quot; &lt;<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>&gt;<br>
Message-ID: &lt;<a href="mailto:20120606141403.163170@gmx.net">20120606141403.163170@gmx.net</a>&gt;<br>
Content-Type: text/plain; charset=&quot;utf-8&quot;<br>
<br>
Hi Paul,<br>
<br>
you need to have the same constructor&#39;s signature on both classes and then you have to use ... in find_by_lpor:<br>
<br>
<br>
      CREATE OBJECT lo_instance_object TYPE (lpor-typeID)<br>
                    EXPORTING<br>
                       iv_instID = lpor-instID.<br>
<br>
      result ?= lo_instance_object.<br>
<br>
<br>
And you need to redefine the instance method LPOR to return your new subclass&#39; name, so the workflow instantiates the subclass the next time, too.<br>
<br>
<br>
Have fun, take care,<br>
   Florin<br>
<br>
<br>
-------- Original-Nachricht --------<br>
&gt; Datum: Wed, 6 Jun 2012 11:17:49 +1000<br>
&gt; Von: <a href="mailto:Paul.Bakker@osr.qld.gov.au">Paul.Bakker@osr.qld.gov.au</a><br>
&gt; An: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
&gt; Betreff: trying to use subclass in workflow, but superclass is instantiated<br>
<br>
&gt;<br>
&gt; Hello WUG OO experts,<br>
&gt;<br>
&gt; As time goes on, I&#39;m gradually switching my new workflow developments to<br>
&gt; OO, just to see what the benefits are.<br>
&gt;<br>
&gt; Anyway, I have just run into a strange problem. I have defined a<br>
&gt; superclass<br>
&gt; ZCl_CLASS and a subclass ZCL_SUB_CLASS.<br>
&gt;<br>
&gt; The subclass inherits all the methods of the superclass, and you can<br>
&gt; redefine them, which is good. However I&#39;ve noticed that you can&#39;t redefine<br>
&gt; the critical method BI_PERSISTENT~FIND_BY_LPOR, because it is a &#39;static&#39;<br>
&gt; method.<br>
&gt;<br>
&gt; This causes a big problem when I start a workflow containing a<br>
&gt; ZCL_SUB_CLASS object, because I&#39;ve found that FIND_BY_LPOR instantiates an<br>
&gt; object of type ZCL_CLASS in the container!<br>
&gt;<br>
&gt; The workflow therefore runs into an error when it tries to execute<br>
&gt; ZCL_SUB_CLASS-&gt;MY_SUBCLASS_METHOD... it reports that the method does not<br>
&gt; exist.<br>
&gt;<br>
&gt; I must be doing something wrong.. but what is it?<br>
&gt;<br>
&gt; merci,<br>
&gt;<br>
&gt; Paul Bakker<br>
&gt;<br>
&gt;<br>
&gt; *********************************************************************************************<br>
&gt; Only an individual or entity who is intended to be a recipient of this<br>
&gt; e-mail may access or use the information contained in this e-mail or any of<br>
&gt; its attachments.  Opinions contained in this e-mail or any of its attachments<br>
&gt; do not necessarily reflect the opinions of Queensland Treasury.<br>
&gt;<br>
&gt; The contents of this e-mail and any attachments are confidential and may<br>
&gt; be legally privileged and the subject of copyright.  If you have received<br>
&gt; this e-mail in error, please notify Queensland Treasury immediately and erase<br>
&gt; all copies of the e-mail and the attachments.  Queensland Treasury uses<br>
&gt; virus scanning software.  However, it is not liable for viruses present in<br>
&gt; this e-mail or in any attachment.<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>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Wed, 6 Jun 2012 20:03:28 +0530<br>
From: Naveen Kusuma &lt;<a href="mailto:naveen.kk99@gmail.com">naveen.kk99@gmail.com</a>&gt;<br>
Subject: Re: SAP-WUG Digest, Vol 91, Issue 8<br>
To: <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
Message-ID:<br>
        &lt;CACn=AMMJVP=<a href="mailto:KbqOwQSjnCAaKS5170vP3nT1Q_R1%2BQ_Nu9OeWGA@mail.gmail.com">KbqOwQSjnCAaKS5170vP3nT1Q_R1+Q_Nu9OeWGA@mail.gmail.com</a>&gt;<br>
Content-Type: text/plain; charset=&quot;iso-8859-1&quot;<br>
<br>
Use T.Code: SWU_OBUF<br>
<br>
*Thanks,<br>
Naveen Kumar*<br>
<br>
<br>
On Wed, Jun 6, 2012 at 5:51 PM, &lt;<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>&gt; wrote:<br>
<br>
&gt; Send SAP-WUG mailing list submissions to<br>
&gt;        <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>
&gt;<br>
&gt; To subscribe or unsubscribe via the World Wide Web, visit<br>
&gt;        <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
&gt; or, via email, send a message with subject or body &#39;help&#39; to<br>
&gt;        <a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a><br>
&gt;<br>
&gt; You can reach the person managing the list at<br>
&gt;        <a href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a><br>
&gt;<br>
&gt; When replying, please edit your Subject line so it is more specific<br>
&gt; than &quot;Re: Contents of SAP-WUG digest...&quot;<br>
&gt;<br>
&gt;<br>
&gt; Today&#39;s Topics:<br>
&gt;<br>
&gt;   1. Re: Buffer problem in SAP Workflow (Arghadip)<br>
&gt;<br>
&gt;<br>
&gt; ----------------------------------------------------------------------<br>
&gt;<br>
&gt; Message: 1<br>
&gt; Date: Tue, 5 Jun 2012 13:52:43 -0500<br>
&gt; From: Arghadip &lt;<a href="mailto:arghadip.kar@gmail.com">arghadip.kar@gmail.com</a>&gt;<br>
&gt; Subject: Re: Buffer problem in SAP Workflow<br>
&gt; To: &quot;SAP Workflow Users&#39; Group&quot; &lt;<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>&gt;<br>
&gt; Message-ID:<br>
&gt;        &lt;<a href="mailto:CAN7b8eKFyFy9ZjL8cEWN7%2Byvw7SUGkT_twbOQjsFB6O93KmRWg@mail.gmail.com">CAN7b8eKFyFy9ZjL8cEWN7+yvw7SUGkT_twbOQjsFB6O93KmRWg@mail.gmail.com</a><br>
&gt; &gt;<br>
&gt; Content-Type: text/plain; charset=&quot;iso-8859-1&quot;<br>
&gt;<br>
&gt; Hi Sanjay<br>
&gt;<br>
&gt; It seems this is a CRM system. I think I will ask you to debug and may be<br>
&gt; check where that partcular message is throwing up. I do not have a CRM<br>
&gt; system to check this.<br>
&gt;<br>
&gt; Thanks<br>
&gt; Arghadip<br>
&gt;<br>
&gt; On Tue, Jun 5, 2012 at 9:24 AM, Sanjay9 P &lt;<a href="mailto:sanjay9.p@tcs.com">sanjay9.p@tcs.com</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; Hi,<br>
&gt; &gt;<br>
&gt; &gt; It is also not working if I triggering the event manually through SWUE.<br>
&gt; &gt; Same problem exists.<br>
&gt; &gt; Any other inputs...???<br>
&gt; &gt;<br>
&gt; &gt; Thanks and regards,<br>
&gt; &gt; Sanjay<br>
&gt; &gt;<br>
&gt; &gt; Sanjay Pal<br>
&gt; &gt; SAP Workflow Consultant<br>
&gt; &gt;<br>
&gt; &gt; ____________________________________________<br>
&gt; &gt; Experience certainty.        IT Services<br>
&gt; &gt;                        Business Solutions<br>
&gt; &gt;                        Outsourcing<br>
&gt; &gt; ____________________________________________<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;   From: Arghadip &lt;<a href="mailto:arghadip.kar@gmail.com">arghadip.kar@gmail.com</a>&gt; To:<br>
&gt; &gt; &quot;SAP Workflow Users&#39; Group&quot; &lt;<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>&gt;<br>
&gt; &gt;  Date: 06/05/2012 06:07 PM Subject: Re: Buffer problem in SAP Workflow<br>
&gt; Sent<br>
&gt; &gt; by: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a><br>
&gt; &gt; ------------------------------<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Hi Sanjay<br>
&gt; &gt;<br>
&gt; &gt; Please can you check to trigger  the event manually through SWUE. If it<br>
&gt; &gt; gets trigger properly there might be Performamnce issue in your Business<br>
&gt; &gt; object.<br>
&gt; &gt;<br>
&gt; &gt; Thanks<br>
&gt; &gt; Arghadip<br>
&gt; &gt;<br>
&gt; &gt; On Fri, May 25, 2012 at 11:26 AM, Sanjay9 P &lt;*<a href="mailto:sanjay9.p@tcs.com">sanjay9.p@tcs.com</a>*&lt;<br>
&gt; <a href="mailto:sanjay9.p@tcs.com">sanjay9.p@tcs.com</a>&gt;&gt;<br>
&gt; &gt; wrote:<br>
&gt; &gt; Hi Experts,<br>
&gt; &gt;<br>
&gt; &gt; My custom workflow is not getting triggered in QA as because &quot;*Entry not<br>
&gt; &gt; found in object buffe*r&quot; in event trace. Please see the below screen<br>
&gt; shot.<br>
&gt; &gt; Following points should be noted.<br>
&gt; &gt; 1. Check function module used<br>
&gt; &gt; 2. Event linkage maintained properly<br>
&gt; &gt; 3. All the objects are present in QA in activated status<br>
&gt; &gt; 4. Same workflow is working fine in DEV<br>
&gt; &gt;<br>
&gt; &gt; Is there any idea why we are getting this message in QA ?<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Sanjay Pal<br>
&gt; &gt; SAP Workflow Consultant<br>
&gt; &gt; Tata Consultancy Services<br>
&gt; &gt; TCS, Unitech Hi-tech Structures Ltd.,<br>
&gt; &gt; IT/ITES SEZ, Block-G, Tower-G -III,<br>
&gt; &gt; Plot-DH01,DH02,DH03 &amp; DH03/1, Action Area-I, New Town<br>
&gt; &gt; Kolkata - 700156,West Bengal<br>
&gt; &gt; India<br>
&gt; &gt; Ph:- *<a href="tel:%2B91%2033%206636%201591" value="+913366361591">+91 33 6636 1591</a>* &lt;%2B91%2033%206636%201591&gt;<br>
&gt; &gt; Buzz:- 1591<br>
&gt; &gt; Cell:- *9038701729* &lt;9038701729&gt;<br>
&gt; &gt; Mailto: *<a href="mailto:sanjay9.p@tcs.com">sanjay9.p@tcs.com</a>* &lt;<a href="mailto:sanjay9.p@tcs.com">sanjay9.p@tcs.com</a>&gt;<br>
&gt; &gt; Website: *<a href="http://www.tcs.com" target="_blank">http://www.tcs.com</a>* &lt;<a href="http://www.tcs.com/" target="_blank">http://www.tcs.com/</a>&gt;<br>
&gt; &gt; ____________________________________________<br>
&gt; &gt; Experience certainty.        IT Services<br>
&gt; &gt;                        Business Solutions<br>
&gt; &gt;                        Outsourcing<br>
&gt; &gt; ____________________________________________<br>
&gt; &gt;<br>
&gt; &gt;   From: Altaf &lt;*<a href="mailto:rahaman.ma@gmail.com">rahaman.ma@gmail.com</a>* &lt;<a href="mailto:rahaman.ma@gmail.com">rahaman.ma@gmail.com</a>&gt;&gt;  To: &quot;*<br>
&gt; &gt; <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>* &lt;<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>&gt;&quot; &lt;*<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>* &lt;<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a><br>

&gt; &gt;&gt;<br>
&gt; &gt; Cc: &quot;*<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>* &lt;<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>&gt;&quot; &lt;*<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>*&lt;<br>
&gt; <a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>&gt;<br>
&gt; &gt; &gt;  Date: 05/25/2012 06:22 AM  Subject: Re: SAP-WUG Digest, Vol 90, Issue<br>
&gt; &gt; 17  Sent by: *<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>* &lt;<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>&gt;<br>
&gt; &gt;<br>
&gt; &gt; ------------------------------<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; Hi,<br>
&gt; &gt;<br>
&gt; &gt; For issue no 1 I will check the scenario and will post you.<br>
&gt; &gt; Issue no 2 you can set the confirm end processing at the task/step so<br>
&gt; &gt; that even after execution of work item you can hold it, the workitem<br>
&gt; &gt; will be executed but will not be in completed status, you can re<br>
&gt; &gt; execute workitem later.<br>
&gt; &gt;<br>
&gt; &gt; Regards,<br>
&gt; &gt; Altaf Mohammed*<br>
&gt; &gt; **9703322553* &lt;9703322553&gt;<br>
&gt; &gt;<br>
&gt; &gt; On 24-May-2012, at 10:00 PM, *<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>*&lt;<br>
&gt; <a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>&gt;wrote:<br>
&gt; &gt;<br>
&gt; &gt; &gt; Send SAP-WUG mailing list submissions to<br>
&gt; &gt; &gt;    *<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>* &lt;<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>&gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; To subscribe or unsubscribe via the World Wide Web, visit<br>
&gt; &gt; &gt;    *<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug*" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug*</a>&lt;<br>
&gt; <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>&gt;<br>
&gt; &gt; &gt; or, via email, send a message with subject or body &#39;help&#39; to<br>
&gt; &gt; &gt;    *<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>* &lt;<a href="mailto:sap-wug-request@mit.edu">sap-wug-request@mit.edu</a>&gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; You can reach the person managing the list at<br>
&gt; &gt; &gt;    *<a href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a>* &lt;<a href="mailto:sap-wug-owner@mit.edu">sap-wug-owner@mit.edu</a>&gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; When replying, please edit your Subject line so it is more specific<br>
&gt; &gt; &gt; than &quot;Re: Contents of SAP-WUG digest...&quot;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Today&#39;s Topics:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;   1. Problem while calling a standard SAP transaction inside<br>
&gt; &gt; &gt;      workflow (Srinivas Reddy)<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; ----------------------------------------------------------------------<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Message: 1<br>
&gt; &gt; &gt; Date: Thu, 24 May 2012 16:59:44 +0530<br>
&gt; &gt; &gt; From: Srinivas Reddy &lt;*<a href="mailto:ootasrinivasreddy@gmail.com">ootasrinivasreddy@gmail.com</a>*&lt;<br>
&gt; <a href="mailto:ootasrinivasreddy@gmail.com">ootasrinivasreddy@gmail.com</a>&gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Subject: Problem while calling a standard SAP transaction inside<br>
&gt; &gt; &gt;    workflow<br>
&gt; &gt; &gt; To: &quot;SAP Workflow Users&#39; Group&quot; &lt;*<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>* &lt;<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>&gt;&gt;<br>
&gt; &gt; &gt; Message-ID:<br>
&gt; &gt; &gt;    &lt;CAGu01YZ-<br>
&gt; &gt; &gt; M5V9MPRfkpzFyDN8ri9Dnr=*<a href="mailto:CfEXebpx7fNP2axU8Cg@mail.gmail.com">CfEXebpx7fNP2axU8Cg@mail.gmail.com</a>*&lt;<br>
&gt; <a href="mailto:CfEXebpx7fNP2axU8Cg@mail.gmail.com">CfEXebpx7fNP2axU8Cg@mail.gmail.com</a>&gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Content-Type: text/plain; charset=&quot;iso-8859-1&quot;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Hello Experts,<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; I am facing a strange issue in my workflow development. The workflow<br>
&gt; &gt; &gt; will<br>
&gt; &gt; &gt; be started after clicking on POST button in the standard transaction<br>
&gt; &gt; &gt; MI04.<br>
&gt; &gt; &gt; I have used the standard  event created from the business object<br>
&gt; &gt; &gt; BUS2028<br>
&gt; &gt; &gt; for starting the workflow. After starting the workflow I am calling<br>
&gt; &gt; &gt; the<br>
&gt; &gt; &gt; standard transaction MI07 in the very first step which will be sent<br>
&gt; &gt; &gt; to the<br>
&gt; &gt; &gt; approver. Once the approver clicks on POST an email will be sent and<br>
&gt; &gt; &gt; the<br>
&gt; &gt; &gt; document will be posted.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Issue 1) When the user manually goes into the SAP transaction MI07 ,<br>
&gt; &gt; &gt; opens<br>
&gt; &gt; &gt; a document and clicks on back, cancel or exit buttons. The<br>
&gt; &gt; &gt; transaction is<br>
&gt; &gt; &gt; working as desired but the same thing  when the same user does from<br>
&gt; &gt; &gt; executing the work item the transaction is not working as desired. A<br>
&gt; &gt; &gt; pop-up<br>
&gt; &gt; &gt; screen with YES, NO and CANCEL buttons and also a message  whether<br>
&gt; &gt; &gt; to SAVE<br>
&gt; &gt; &gt; before exit is displayed. Even though if the user clicks on NO<br>
&gt; &gt; &gt; button the<br>
&gt; &gt; &gt; document is getting posted. No idea what is going wrong with the<br>
&gt; &gt; &gt; method<br>
&gt; &gt; &gt; calling the transaction MI07.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Issue 2) Once the users does this process. The work item is getting<br>
&gt; &gt; &gt; completed. But the requirement is, work item should be available as<br>
&gt; &gt; &gt; the<br>
&gt; &gt; &gt; POSTING is not completed. Here how can I put the work item in ready<br>
&gt; &gt; &gt; status<br>
&gt; &gt; &gt; after completeion. Once the users executes the work item the work<br>
&gt; &gt; &gt; item is<br>
&gt; &gt; &gt; getting disappeared.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Where am I doing wrong?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; --<br>
&gt; &gt; &gt; Thanks and Regards<br>
&gt; &gt; &gt; Srini..<br>
&gt; &gt; &gt; SAP Technical Consultant<br>
&gt; &gt; &gt; *<a href="tel:%2B919963307464" value="+919963307464">+919963307464</a>* &lt;%2B919963307464&gt;<br>
&gt; &gt; &gt; -------------- next part --------------<br>
&gt; &gt; &gt; An HTML attachment was scrubbed...<br>
&gt; &gt; &gt; URL: *<br>
&gt; &gt;<br>
&gt; <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120524/c5d65341/attachment-0001.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120524/c5d65341/attachment-0001.htm</a><br>

&gt; &gt; *&lt;<br>
&gt; <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120524/c5d65341/attachment-0001.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120524/c5d65341/attachment-0001.htm</a><br>

&gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; ------------------------------<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; _______________________________________________<br>
&gt; &gt; &gt; SAP-WUG mailing list<br>
&gt; &gt; &gt; *<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>* &lt;<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>&gt;<br>
&gt; &gt; &gt; *<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug*" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug*</a>&lt;<br>
&gt; <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>&gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; End of SAP-WUG Digest, Vol 90, Issue 17<br>
&gt; &gt; &gt; ***************************************<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; SAP-WUG mailing list*<br>
&gt; &gt; **<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>* &lt;<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>&gt;*<br>
&gt; &gt; **<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug*" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug*</a>&lt;<br>
&gt; <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>&gt;<br>
&gt; &gt;<br>
&gt; &gt; =====-----=====-----=====<br>
&gt; &gt; Notice: The information contained in this e-mail<br>
&gt; &gt; message and/or attachments to it may contain<br>
&gt; &gt; confidential or privileged information. If you are<br>
&gt; &gt; not the intended recipient, any dissemination, use,<br>
&gt; &gt; review, distribution, printing or copying of the<br>
&gt; &gt; information contained in this e-mail message<br>
&gt; &gt; and/or attachments to it are strictly prohibited. If<br>
&gt; &gt; you have received this communication in error,<br>
&gt; &gt; please notify us by reply e-mail or telephone and<br>
&gt; &gt; immediately and permanently delete the message<br>
&gt; &gt; and any attachments. Thank you<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; SAP-WUG mailing list*<br>
&gt; &gt; **<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>* &lt;<a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a>&gt;*<br>
&gt; &gt; **<a href="http://mailman.mit.edu/mailman/listinfo/sap-wug*" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug*</a>&lt;<br>
&gt; <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a>&gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; SAP-WUG mailing list<br>
&gt; &gt; <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
&gt; &gt; <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; SAP-WUG mailing list<br>
&gt; &gt; <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>
&gt; &gt; <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; -------------- next part --------------<br>
&gt; An HTML attachment was scrubbed...<br>
&gt; URL:<br>
&gt; <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120605/736794aa/attachment.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120605/736794aa/attachment.htm</a><br>
&gt; -------------- next part --------------<br>
&gt; A non-text attachment was scrubbed...<br>
&gt; Name: not available<br>
&gt; Type: image/gif<br>
&gt; Size: 10629 bytes<br>
&gt; Desc: not available<br>
&gt; Url :<br>
&gt; <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120605/736794aa/attachment.gif" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120605/736794aa/attachment.gif</a><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>
&gt;<br>
&gt;<br>
&gt; End of SAP-WUG Digest, Vol 91, Issue 8<br>
&gt; **************************************<br>
&gt;<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://mailman.mit.edu/pipermail/sap-wug/attachments/20120606/91275eb1/attachment.htm" target="_blank">http://mailman.mit.edu/pipermail/sap-wug/attachments/20120606/91275eb1/attachment.htm</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" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br>
<br>
End of SAP-WUG Digest, Vol 91, Issue 9<br>
**************************************<br>
</blockquote></div>