Hi Florin.<br>Many thanks for your prompt reply (always :p )<br>Since you're the one who replied my e-mail, I have to tell you that this still related with issue in my terminating event.<br>Try to use alternative solution.<br>
I thought that was a good solution by using Export-Import to memory.<br>In my case once user clicked button on ABAP program, this program should send value to workflow task and tell workflow to continue the process. Again the best way to solve this issue is via terminating event or wait step.<br>
<br>But any way, your e-mail gave me a light.<br>Instead of using call transaction, I will call function module in my method.<br>my ABAP program should be as a function module where its export parameter is value associate with button in ABAP program.<br>
Export parameter will be receive within my method and pass it back to task container for further process.<br><br><br><div class="gmail_quote">On Thu, Jun 12, 2008 at 5:53 PM, Florin Wach <<a href="mailto:florin.wach@gmx.net">florin.wach@gmx.net</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Sandy,<br>
<br>
I have experienced a very similar problem and I worked around that by using the new ABAP-Objects for the workitem's container. But apparently that container get's rolled back whenever the work item was cancelled (and not fully processed). By the way, I'm talking about a synchronous dialog step.<br>
<br>
Instead of writing the value immediatly back to the container, you could use the EXPORT TO MEMORY statement to pass information back from the transaction to the calling business object method, picking it up there to pass it back via the method container (as plain exporting element).<br>
Another possibility could be, to use a separate database table with the work*flows* WI_ID as the key field and you pass this to the transaction (as hidden parameter or so). The transaction then can put entries there, as you wish, and you create an extended WORKITEM object with a virtual attribut holding the information from the db table. In the workflow you can then use the instance of the workflow itself to access it.<br>
<br>
Maybe this gives you some more ideas.<br>
<br>
Best wishes,<br>
Florin<br>
<br>
-------- Original-Nachricht --------<br>
> Datum: Thu, 12 Jun 2008 17:25:26 +0800<br>
> Von: Sandy <<a href="mailto:maorriyan.santoso@gmail.com">maorriyan.santoso@gmail.com</a>><br>
> An: "SAP Workflow - MIT" <<a href="mailto:sap-wug@mit.edu">sap-wug@mit.edu</a>><br>
> Betreff: Dequeue Work Item<br>
<div><div></div><div class="Wj3C7c"><br>
> Hi All.<br>
><br>
> I have workflow task that execute ABAP program via call transaction. So<br>
> when<br>
> user receive work item they execute work item and bring ABAP program.<br>
> Within this program user need to click certain button. When they execute<br>
> certain button, data base field get updated and need to update task<br>
> container element.<br>
><br>
> The design is when work item executed, it send work item to ABAP program<br>
> and<br>
> do SAP_WAPI_WRITE_CONTAINER to update container element depend on selected<br>
> button.<br>
> I got enqueue error message says that work item has been locked by the<br>
> user<br>
> it self.<br>
> It is obvious when user execute work item and transaction called, work<br>
> item<br>
> still get locked.<br>
><br>
> Is there any alternative to update container element of work item while<br>
> work<br>
> item executed?<br>
> Statement "LEAVE TO TRANSACTION" is not an option since I need to pass<br>
> parameters value when I call ABAP transaction<br>
</div></div>_______________________________________________<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>
</blockquote></div><br>