Its a long shot but....

Kevin kjw1969 at yahoo.com
Tue May 10 21:06:21 EDT 2005


Unfortunately SAP do not support WAPIs as they do BAPIs. If you have issues
calling a WAPI external to SAP, good luck trying to get some OSS support but
for a BAPI no problem......
Just a heads up from one consultant to another

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] 
Sent: Tuesday, May 10, 2005 11:47 AM
To: SAP Workflow Users' Group
Subject: AW: Its a long shot but....


Hi Alon
 
WAPIs should be equivalent to BAPIs, that would exclude any SAP GUI dialog
behaviour.  This is quite important when calling the WAPIs from outside the
SAP system via RFC, as well as for the bundling of  database updates in one
LUW.
 
from one consultant to another
Nathan 
 
 
 
 

-----Ursprüngliche Nachricht-----
Von: Alon Raskin [mailto:sap-wug-bounces at mit.edu]Im Auftrag von Alon Raskin
Gesendet: Dienstag, 10. Mai 2005 13:41
An: SAP Workflow Users' Group
Betreff: RE: Its a long shot but....


Hi Ram,
 
I think you are right. There isn't going to be a straight forward answer. I
might try OSS (in the hope that they are feeling generous) but I am not
going to hold my breath. 
 
As far as the answer to the rest of the quote... you should ask some of the
consultants on your site what the end of the phrase is. If you still get no
joy then send me a direct email and I will reply....
 
Thanks again for your input.
 


Alon Raskin
e:  <mailto:araskin at 3i-consulting.com> araskin at 3i-consulting.com
p: +61 3 9625 2189 (Head Office)
f:  +61 3 8610 1239 
c:  +1 207 756 0370
w: http://www.3i-consulting.com

  _____  

From: sap-wug-bounces at mit.edu on behalf of Tiwari, Rammanohar
Sent: Tue 5/10/2005 07:38
To: SAP Workflow Users' Group
Subject: RE: Its a long shot but....



Hi Alon,

Do you mean ...But ...where is the answer? :-)

Well, it's clear that there is no straightforward solution to it and I'm not
sure if SAP will have it either.
So I've given my suggestion as a food for thought only.

Anyway thanks for calling me a consultant as I don't like be called a
Manager for obvious reasons :-)
No offence mean to anyone.

Thanks,
Ram

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
Of Alon Raskin
Sent: Tuesday, May 10, 2005 3:31 PM
To: 'SAP Workflow Users' Group'
Subject: RE: Its a long shot but....


Hi Ram,

You are a true consultant (I know because I am one too!)....

Everything you said is 100% correct but....

:-)

Alon Raskin
e: araskin at 3i-consulting.com
w: http://www.3i-consulting.com

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Tiwari, Rammanohar
Sent: Tuesday, May 10, 2005 5:44 AM
To: SAP Workflow Users' Group
Subject: RE: Its a long shot but....


Not sure if I got the problem right.

In case a program ( outside the WF ) determines the decision WIs of a
workflow and shows it as a list to the user.
Further, user selects one of the decision WIs and executes ( which in turn
calls the WAPI and completes the decision WI ).

I think if you need that next WI ( of the WF ) should appear immediately (
not in the Inbox but through your outside program  ), then your program :

1. Should call the WAPI first for chosen decision WI ( which will be
completed by the user ).

3. Determine the subsequent WI which is sent to the Inbox and execute it
from your program. But then there are asynchronous activities involved  (
context change from Program --> WF ---> Program ) so your program may not
find the Inbox work item immediately.

Thanks,
Ram

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf Of
Michael Pokraka
Sent: Tuesday, May 10, 2005 2:23 PM
To: SAP Workflow Users' Group
Subject: Re: Its a long shot but....


Hmmm, I interpret Alon's description differently. I think what he didn't
describe clearly is that the WAPI is called through some user action outside
the WF which completes the decision..... Alon?

If this is the case then this is a very curious situation indeed. There is
no 'advance with dialog' as it is not within a workflow context, but
nevertheless the WAPI could put the process into a WF context. However, the
WAPI could be called within a LUW which needs to complete, or something
which has it's own sequence of events.

Advance with dialog causes a potential paradox: what if the WAPI is called
from a different WF in a dialog task, which has it's own advance with dialog
successor? Which task is the user shown next?

I suspect the WAPI just changes the state and triggers the WF engine into
action to progress the WF - outside the user context.
I'm curious about any possibilities though, it wouldn't hurt to ask OSS (and
let us know if you do).

Cheers
Mike

--- Thomas Maue <Thomas.Maue at ipaper.com> wrote:

>
> Alon,
>
> This is working as designed.  If there are two dialog steps together
> then it works, but when a background step is placed in between the
> Advance with Dialog will not work (makes sense if you think about it).
>
> You might try taking off the background processing indicator for the
> background task and then setting the Advance with Dialog for the
> background/dialog step.
>
> Regards,
> Thomas Maue
>
>
>
>

>              "Alon Raskin"

>              <araskin at 3i-consu

>              lting.com>                                                 To

>              Sent by:                  "SAP Workflow Users' Group"

>              sap-wug-bounces at m         <sap-wug at mit.edu>

>              it.edu                                                     cc

>

>                                                                    Subject

>              05/09/2005 04:38          Its a long shot but....

>              PM

>

>

>              Please respond to

>                "SAP Workflow

>                Users' Group"

>              <sap-wug at mit.edu>

>

>

>
>
>
>
> I am not sure if there are going to be any takers for this one but
> then you guys/gals always surprise me....
>
> I am calling the WAPI provided in 4.7 called SAP_WAPI_DECISION_COMPLETE .
> This Function Module allows me to programmatically enter a decision
> item for an outstanding work item. It is a thing of beauty and works
perfectly.
>
> But (and there's always a but)....
>
> The WAPI does not respect the Advance with Dialog flag that I have set
> on my workflow. When I execute this work item from my inbox it
> proceeds to immediately take me to the next step. However, when I
> complete the work item via the WAPI, the chain is broken and I am not
taken to the next step.
> The subsequent step does appear in my inbox but I want it to popup
> straight away.
>
> Is this working as designed or do you think this could be an OSS note?
>
> Any ideas/suggestions?
>
> Alon Raskin
> e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com>
> w: http://www.3i-consulting.com
>
> (See attached file: winmail.dat)
> _______________________________________________
> 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
>

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

This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an
intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.

_______________________________________________
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

This e-mail and any attachment is for authorised use by the intended
recipient(s) only. It may contain proprietary material, confidential
information and/or be subject to legal privilege. It should not be copied,
disclosed to, retained or used by, any other party. If you are not an
intended recipient then please promptly delete this e-mail and any
attachment and all copies and inform the sender. Thank you.

_______________________________________________
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: winmail.dat
Type: application/ms-tnef
Size: 14804 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20050510/398f7564/attachment.bin


More information about the SAP-WUG mailing list