WAPI SAP_WAPI_WORKITEM_COMPLETE

Tue Oct 23 08:56:26 EDT 2007

Mike, 

SAP has delivered OSS note 1105163 to correct this. I haven't test this so I don't know if its done the trick yet.
I am also not sure whether this OSS note will 'respect' the synchronous processing flag for subsequent step or whether it just 
corrects the ERRORED workflow. Anyway, I will get back to you once I have applied and tested the note in our system.

Regards,

Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com> 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Mike Pokraka
Sent: Wed 10/17/2007 08:06
To: SAP Workflow Users' Group
Subject: Re: WAPI SAP_WAPI_WORKITEM_COMPLETE

Agreed, it's not the best approach - I've had my share of dealings in that
area recently and it can get quite nasty.
Anyhow, let us know if you get any useful answer as I'd be interested.

Cheers,
Mike

On Wed, October 17, 2007 11:05 am, Alon Raskin wrote:
> Hi Mike,
>
> That is preceisely what I did. What I didn't like about that approach is
> that I had to read the node definition of the Workflows so that I could
> work
> out what the next work item to execute was. I don't like getting under the
> covers of SAP Worfklow too much as SAP seems to be making such significant
> changes to the table structures and code. Still it does work.
>
> I still have an OSS outstanding with SAP about this but I have not yet
> heard
> back.
>
> Regards,
>
> Alon Raskin
> e: araskin at 3i-consulting.com
>
>
>> From: Mike Pokraka <asap at workflowconnections.com>
>> Reply-To: SAP Workflow Users' Group <sap-wug at mit.edu>
>> Date: Wed, 17 Oct 2007 08:18:37 +0100 (BST)
>> To: SAP Workflow Users' Group <sap-wug at mit.edu>
>> Subject: RE: WAPI SAP_WAPI_WORKITEM_COMPLETE
>>
>> Hi Alon,
>>
>> Not sure if your problem is still unsolved, but here's a big hammer
>> approach: do a SAP_WAPI_DECISION_COMPLETE, wait a little bit, read the
>> log
>> and do a SAP_WAPI_EXECUTE_WORKITEM of the subsequent WI. Not pretty but
>> not changing the WF limits choices somewhat...
>>
>> Cheers,
>> Mike
>>
>> On Wed, October 10, 2007 7:52 pm, Alon Raskin wrote:
>>> Thanks Rick. You're suggestion is a good one but (and this is something
>>> I
>>> didn't mention in my original post) the code must work with WFs that
>>> the
>>> customer already has in place. The WFs themselves cannot be changed.
>>> Therefore not possible to change the decision to activity or using
>>> before/after methods.
>>>
>>> Regards,
>>>
>>> Alon Raskin
>>> e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com>
>>> p: +1 207 523 3489
>>> c: +1 207 409 4983
>>> f:  +1 806 403 4983
>>>
>>> ________________________________
>>>
>>> From: sap-wug-bounces at mit.edu on behalf of Sample, Rick
>>> Sent: Wed 10/10/2007 09:46
>>> To: SAP Workflow Users' Group
>>> Subject: RE: WAPI SAP_WAPI_WORKITEM_COMPLETE
>>>
>>>
>>> As far as the error message, I don't recall. But some thoughts on a
>>> design
>>> change. (Since you are 'testing')
>>>
>>> Change from a decision step to Activity Step with popup for Approve,
>>> Reject, Cancel and "Terminating event"?
>>> Catch the event creator and pass it through.
>>>
>>> I tried to create a decision to catch the actions after choice but was
>>> far
>>> too painful. (In 4.6c)
>>>
>>> Have you tried using BEFORE / AFTER methods? A method call (after
>>> decision
>>> action) will run. And run as same user in task.
>>>
>>> More than happy to share some thoughts...
>>>
>>> Rick Sample
>>> SAP Business Workflow Developer
>>> Graybar, Inc.
>>>
>>>
>>> ________________________________
>>>
>>> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
>>> Behalf
>>> Of Alon Raskin
>>> Sent: Wednesday, October 10, 2007 2:56 AM
>>> To: SAP Workflow Users' Group
>>> Subject: RE: WAPI SAP_WAPI_WORKITEM_COMPLETE
>>>
>>>
>>>
>>> It's a custom workflow which I put together for this test. It's a
>>> simple
>>> decision task followed up by a simple dialog step (which does not popup
>>> any screens). What I want to achieve is to complete the task
>>> programmatically and then have the subsequent step executed under the
>>> agent's user ID. This is what happens when I execute the decision task
>>> from the Inbox and I am trying to get the WAPI's to play nice too. I
>>> have
>>> logged an OSS.
>>>
>>>
>>>
>>> Alon Raskin
>>>
>>> e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com>
>>>
>>> p: +1 207 523 3489
>>>
>>> c: +1 207 409 4983
>>>
>>> f:  +1 806 403-4983
>>>
>>>
>>>
>>> The easiest way to integrate SAP with any mobile device
>>>
>>> http://www.themobileworkplace.com <http://www.themobileworkplace.com/>  <http://www.themobileworkplace.com/>
>>>
>>> ________________________________
>>>
>>> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
>>> Behalf
>>> Of Richard V Marut
>>> Sent: Tuesday, October 09, 2007 10:36 PM
>>> To: 'SAP Workflow Users' Group'
>>> Subject: RE: WAPI SAP_WAPI_WORKITEM_COMPLETE
>>>
>>>
>>>
>>> Alon,
>>>
>>>
>>>
>>> What exactly is the step that you are using to complete work item
>>> doing? I
>>> recall having the same problem when the step had some functionality
>>> involved with it. My process used a web front-end by user to process
>>> the
>>> work items. I ended up making  the work item a dummy step just to be
>>> able
>>> to assign the item to a user and to provide the ability to reserve,
>>> replace, cancel and complete the work item under that user id. I no
>>> longer
>>> received that error once I did that.
>>>
>>>
>>>
>>> Richard...
>>>
>>>
>>>
>>>
>>>
>>> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
>>> Behalf
>>> Of Alon Raskin
>>> Sent: Tuesday, October 09, 2007 6:43 PM
>>> To: SAP Workflow Users' Group
>>> Subject: RE: WAPI SAP_WAPI_WORKITEM_COMPLETE
>>>
>>>
>>>
>>> Thanks Ravi,
>>>
>>>
>>>
>>> I am not sure your analysis is right. The Workflow works fine if you
>>> execute the work item from the inbox. It only errors if you call the
>>> WAPI
>>> SAP_WAPI_WORKITEM_COMPLETE   with the do_callback_in_background =
>>> space.
>>>
>>>
>>>
>>> Regards,
>>>
>>>
>>>
>>> Alon Raskin
>>>
>>> e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com>
>>>
>>> p: +1 207 523 3489
>>>
>>> c: +1 207 409 4983
>>>
>>> f:  +1 806 403-4983
>>>
>>>
>>>
>>> The easiest way to integrate SAP with any mobile device
>>>
>>> http://www.themobileworkplace.com <http://www.themobileworkplace.com/>  <http://www.themobileworkplace.com/>
>>>
>>> ________________________________
>>>
>>> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On
>>> Behalf
>>> Of Ravi Dixit
>>> Sent: Tuesday, October 09, 2007 7:36 PM
>>> To: sap-wug at mit.edu
>>> Subject: Re: WAPI SAP_WAPI_WORKITEM_COMPLETE
>>>
>>>
>>>
>>> HI Alon
>>>
>>>
>>> Most likely it seems to be a problem with the definition of the next
>>> step.
>>> Check the outcome of the current step and mandatory parameters for the
>>> next. Also, you can user Error Analysis (Ctrl+F11) to dig further.
>>>
>>> Cheers
>>>
>>> Ravi
>>>
>>>
>>> Message: 4
>>> Date: Tue, 9 Oct 2007 09:54:14 -0400
>>> From: "Alon Raskin" < araskin at 3i-consulting.com
>>> <mailto:araskin at 3i-consulting.com> >
>>> Subject: WAPI SAP_WAPI_WORKITEM_COMPLETE
>>> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
>>> Message-ID:
>>>       < CEF21C1C5BF2FA42A42CEC87B91BBCDE02764316 at ms07.mse2.exchange.ms
>>> <mailto:CEF21C1C5BF2FA42A42CEC87B91BBCDE02764316 at ms07.mse2.exchange.ms>
>>>>
>>> Content-Type: text/plain; charset="iso-8859-1"
>>>
>>> I am just wondering if anyone has seen this issue before:
>>>
>>> I am calling Function Module   to complete a work item. The FM has a
>>> parameter  do_callback_in_background . I am setting this to SPACE
>>> because
>>> I want the subsequent work item to be executed under the same User ID.
>>> However when I do this the workflow errors with the following error
>>> Error
>>> when defining successor for node 0000000004
>>>
>>> Does do anyone know a way around this issue or whether this is a likely
>>> candidate for an OSS message?
>>>
>>> Alon Raskin
>>> e: araskin at 3i-consulting.com <mailto: araskin at 3i-consulting.com
>>> <mailto:araskin at 3i-consulting.com> >
>>>
>>> -------------- next part --------------
>>> A non-text attachment was scrubbed...
>>> Name: not available
>>> Type: application/ms-tnef
>>> Size: 4248 bytes
>>> Desc: not available
>>> Url :
>>> http://mailman.mit.edu/pipermail/sap-wug/attachments/20071009/ca5ae318/attach
>>> ment.bin
>>>
>>> ------------------------------
>>>
>>> _______________________________________________
>>> SAP-WUG mailing list
>>> SAP-WUG at mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>>
>>>
>>> End of SAP-WUG Digest, Vol 35, Issue 16
>>> ***************************************
>>>
>>>
>>>
>>>
>>> --
>>> Regards
>>> Ravi Dixit
>>>
>>> _______________________________________________
>>> SAP-WUG mailing list
>>> SAP-WUG at mit.edu
>>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>>
>>
>>
>> --
>> Mike Pokraka
>> Senior Consultant
>> Workflow Connections
>> Mobile: +44(0)7786 910855
>>
>> _______________________________________________
>> 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
>

--
Mike Pokraka
Senior Consultant
Workflow Connections
Mobile: +44(0)7786 910855

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 17512 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20071023/54eece60/attachment.bin