Workitem not completing after Call Transaction to VM01

[tamara.elliott@kodak.com]

Hey Mike,

Thanks for the reply.  If the user doesn't save and just backs out, I do 
get the confirm box.  My assumption as well was that it has something to 
do with the transaction itself.  Not sure OSS is worth it.

The VM01 transaction is a create, but for some reason it was raising the 
A00MARA CHANGED event.........not sure why.  What I meant by 'basically 
does the same' is that the workflow tasks were exactly the same, just 
calling two different transaction.  For some reason the 2 transactions 
react differently to being executed via the workitem - even though one's a 
create and one's a change I didn't think it mattered (should have known 
better).

What I did to get this resolved doesn't make sense to me either, but it is 
now working.  Originally in the method I set the material number via a 
parameter id, and did a call transaction..end of story.  I changed the 
code to set the material number in a bdcdata table, did the CALL 
TRANSACTION 'VM01' USING bdcdata, and now everything works just 
fine....after the save I get the Confirmation screen, and all is well. Not 
really sure why this worked, but the users are happy, and we move on.

Thanks to all for their input.

Tami
Eastman Kodak






Michael Pokraka <wug.replies at workflowconnections.com>
Sent by: sap-wug-bounces at mit.edu
05/10/2005 12:18 PM
Please respond to "SAP Workflow Users' Group"

 
        To:     "SAP Workflow Users' Group" <sap-wug at mit.edu>
        cc: 
        Subject:        Re: Workitem not completing after Call Transaction to VM01


Hi Tami, 
What happens if the user doesn't save - i.e. just executes the WI and 
backs
straight out again? Do you get the confirm box? If so, something in the
transaction is sabotaging the process. OSS is an option.

On the other hand, you mention create, but further on you refer to a 
CHANGED
event. VM01 is create, MM02 is a change transaction, so we're a little way 
off
'basically does the same'. Ideally a create txn should be async, 
obsoleting the
need for a confirm box. Perhaps you can create your own event? 

Cheers
Mike

--- tamara.elliott at kodak.com wrote:

> I have a synchronous dialog task that does a call transaction to VM01; 
> this task also has a Confirm End of Processing on it.  When the user 
> executes the workitem, creates the Hazardous material, saves it and 
backs 
> out, the Confirm End of Processing Screen does not appear. I took the 
> Confirm End of Processing off of the task, but when the workitem is 
> executed and the material saved, the step does not complete.  It's like 
> there is a complete disconnect between this transaction and the 
workflow. 
> I have another task that basically does the same thing using MM02, and 
> this one works fine.
> 
> I'm stuck as to how to get the workflow to continue processing....I 
> thought about using a terminating event for the step, but the event that 

> gets raised is A00MARA CHANGED, and the object A00MARA no longer exists 
in 
> 4.7.  If the user goes back into his inbox, executes the workitem again, 

> and then just backs out of the VM01 transaction the workflow continues 
> on..............but I doubt if the user wants to execute this workitem 
> twice.
> 
> Any suggestions on how to deal with this?
> 
> Thanks,
> Tami
> Eastman Kodak
> 
> 
> > _______________________________________________
> 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/20050510/902ec7a7/attachment.htm