<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>RE: Its a long shot but....</TITLE>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1491" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=733222918-10052005>Hi
Alon</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=733222918-10052005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=733222918-10052005>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.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=733222918-10052005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=733222918-10052005>from
one consultant to another</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=733222918-10052005>Nathan
</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=733222918-10052005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=733222918-10052005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=733222918-10052005></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=733222918-10052005></SPAN></FONT> </DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Ursprüngliche Nachricht-----<BR><B>Von:</B> Alon Raskin
[mailto:sap-wug-bounces@mit.edu]<B>Im Auftrag von </B>Alon
Raskin<BR><B>Gesendet:</B> Dienstag, 10. Mai 2005 13:41<BR><B>An:</B> SAP
Workflow Users' Group<BR><B>Betreff:</B> RE: Its a long shot
but....<BR><BR></FONT></DIV>
<DIV id=idOWAReplyText30084 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2>Hi Ram,</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>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. </FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>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....</FONT></DIV>
<DIV dir=ltr><FONT face=Arial size=2></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial size=2>Thanks again for your input.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000 size=2></FONT> </DIV></DIV>
<DIV id=idSignature72281 dir=ltr>
<DIV><FONT face=Arial color=#000000 size=2>
<DIV dir=ltr align=left><STRONG>
<DIV dir=ltr align=left><STRONG>Alon Raskin</STRONG></DIV>
<DIV dir=ltr align=left><STRONG>e: </STRONG><A
href="mailto:araskin@3i-consulting.com"
target=_blank><STRONG>araskin@3i-consulting.com</STRONG></A></DIV>
<DIV dir=ltr align=left><STRONG>p: +61 3 9625 2189 (Head
Office)</STRONG></DIV>
<DIV dir=ltr align=left><STRONG>f: +61 3 8610 1239 </STRONG></DIV>
<DIV dir=ltr align=left><STRONG>c: +1 207 756 0370</STRONG></DIV>
<DIV dir=ltr align=left><STRONG>w: </STRONG><A
href="/exchweb/bin/redir.asp?URL=http://www.3i-consulting.com/"
target=_blank><STRONG>http://www.3i-consulting.com</STRONG></A></DIV></STRONG></DIV></FONT></DIV></DIV>
<DIV dir=ltr><BR>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> sap-wug-bounces@mit.edu on behalf of
Tiwari, Rammanohar<BR><B>Sent:</B> Tue 5/10/2005 07:38<BR><B>To:</B> SAP
Workflow Users' Group<BR><B>Subject:</B> RE: Its a long shot
but....<BR></FONT><BR></DIV>
<DIV>
<P><FONT size=2>Hi Alon,<BR><BR>Do you mean ...But ...where is the answer?
:-)<BR><BR>Well, it's clear that there is no straightforward solution to it
and I'm not sure if SAP will have it either.<BR>So I've given my suggestion as
a food for thought only.<BR><BR>Anyway thanks for calling me a consultant as I
don't like be called a Manager for obvious reasons :-)<BR>No offence mean to
anyone.<BR><BR>Thanks,<BR>Ram<BR><BR>-----Original Message-----<BR>From:
sap-wug-bounces@mit.edu [<A
href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</A>]On
Behalf<BR>Of Alon Raskin<BR>Sent: Tuesday, May 10, 2005 3:31 PM<BR>To: 'SAP
Workflow Users' Group'<BR>Subject: RE: Its a long shot but....<BR><BR><BR>Hi
Ram,<BR><BR>You are a true consultant (I know because I am one
too!)....<BR><BR>Everything you said is 100% correct
but....<BR><BR>:-)<BR><BR>Alon Raskin<BR>e: araskin@3i-consulting.com<BR>w: <A
href="http://www.3i-consulting.com">http://www.3i-consulting.com</A><BR><BR>-----Original
Message-----<BR>From: sap-wug-bounces@mit.edu [<A
href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</A>] On
Behalf Of<BR>Tiwari, Rammanohar<BR>Sent: Tuesday, May 10, 2005 5:44 AM<BR>To:
SAP Workflow Users' Group<BR>Subject: RE: Its a long shot
but....<BR><BR><BR>Not sure if I got the problem right.<BR><BR>In case a
program ( outside the WF ) determines the decision WIs of a<BR>workflow and
shows it as a list to the user.<BR>Further, user selects one of the decision
WIs and executes ( which in turn<BR>calls the WAPI and completes the decision
WI ).<BR><BR>I think if you need that next WI ( of the WF ) should appear
immediately (<BR>not in the Inbox but through your outside program ),
then your program :<BR><BR>1. Should call the WAPI first for chosen decision
WI ( which will be<BR>completed by the user ).<BR><BR>3. Determine the
subsequent WI which is sent to the Inbox and execute it<BR>from your program.
But then there are asynchronous activities involved (<BR>context change
from Program --> WF ---> Program ) so your program may not<BR>find the
Inbox work item immediately.<BR><BR>Thanks,<BR>Ram<BR><BR>-----Original
Message-----<BR>From: sap-wug-bounces@mit.edu [<A
href="mailto:sap-wug-bounces@mit.edu">mailto:sap-wug-bounces@mit.edu</A>]On
Behalf Of<BR>Michael Pokraka<BR>Sent: Tuesday, May 10, 2005 2:23 PM<BR>To: SAP
Workflow Users' Group<BR>Subject: Re: Its a long shot but....<BR><BR><BR>Hmmm,
I interpret Alon's description differently. I think what he didn't<BR>describe
clearly is that the WAPI is called through some user action outside<BR>the WF
which completes the decision..... Alon?<BR><BR>If this is the case then this
is a very curious situation indeed. There is<BR>no 'advance with dialog' as it
is not within a workflow context, but<BR>nevertheless the WAPI could put the
process into a WF context. However, the<BR>WAPI could be called within a LUW
which needs to complete, or something<BR>which has it's own sequence of
events.<BR><BR>Advance with dialog causes a potential paradox: what if the
WAPI is called<BR>from a different WF in a dialog task, which has it's own
advance with dialog<BR>successor? Which task is the user shown next?<BR><BR>I
suspect the WAPI just changes the state and triggers the WF engine
into<BR>action to progress the WF - outside the user context.<BR>I'm curious
about any possibilities though, it wouldn't hurt to ask OSS (and<BR>let us
know if you do).<BR><BR>Cheers<BR>Mike<BR><BR>--- Thomas Maue
<Thomas.Maue@ipaper.com> wrote:<BR><BR>><BR>>
Alon,<BR>><BR>> This is working as designed. If there are two
dialog steps together<BR>> then it works, but when a background step is
placed in between the<BR>> Advance with Dialog will not work (makes sense
if you think about it).<BR>><BR>> You might try taking off the
background processing indicator for the<BR>> background task and then
setting the Advance with Dialog for the<BR>> background/dialog
step.<BR>><BR>> Regards,<BR>> Thomas
Maue<BR>><BR>><BR>><BR>><BR><BR>>
"Alon
Raskin"<BR><BR>>
<araskin@3i-consu<BR><BR>>
lting.com>
To<BR><BR>>
Sent
by:
"SAP Workflow Users'
Group"<BR><BR>>
sap-wug-bounces@m
<sap-wug@mit.edu><BR><BR>>
it.edu
cc<BR><BR>><BR><BR>>
Subject<BR><BR>>
05/09/2005 04:38 Its a
long shot
but....<BR><BR>>
PM<BR><BR>><BR><BR>><BR><BR>>
Please respond
to<BR><BR>>
"SAP
Workflow<BR><BR>>
Users'
Group"<BR><BR>>
<sap-wug@mit.edu><BR><BR>><BR><BR>><BR><BR>><BR>><BR>><BR>><BR>>
I am not sure if there are going to be any takers for this one but<BR>>
then you guys/gals always surprise me....<BR>><BR>> I am calling the
WAPI provided in 4.7 called SAP_WAPI_DECISION_COMPLETE .<BR>> This Function
Module allows me to programmatically enter a decision<BR>> item for an
outstanding work item. It is a thing of beauty and
works<BR>perfectly.<BR>><BR>> But (and there's always a
but)....<BR>><BR>> The WAPI does not respect the Advance with Dialog
flag that I have set<BR>> on my workflow. When I execute this work item
from my inbox it<BR>> proceeds to immediately take me to the next step.
However, when I<BR>> complete the work item via the WAPI, the chain is
broken and I am not<BR>taken to the next step.<BR>> The subsequent step
does appear in my inbox but I want it to popup<BR>> straight
away.<BR>><BR>> Is this working as designed or do you think this could
be an OSS note?<BR>><BR>> Any ideas/suggestions?<BR>><BR>> Alon
Raskin<BR>> e: araskin@3i-consulting.com <<A
href="mailto:araskin@3i-consulting.com">mailto:araskin@3i-consulting.com</A>><BR>>
w: <A
href="http://www.3i-consulting.com">http://www.3i-consulting.com</A><BR>><BR>>
(See attached file: winmail.dat)<BR>>
_______________________________________________<BR>> SAP-WUG mailing
list<BR>> SAP-WUG@mit.edu<BR>> <A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR>>
> _______________________________________________<BR>> SAP-WUG mailing
list<BR>> SAP-WUG@mit.edu<BR>> <A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR>><BR><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR>SAP-WUG@mit.edu<BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR>This
e-mail and any attachment is for authorised use by the
intended<BR>recipient(s) only. It may contain proprietary material,
confidential<BR>information and/or be subject to legal privilege. It should
not be copied,<BR>disclosed to, retained or used by, any other party. If you
are not an<BR>intended recipient then please promptly delete this e-mail and
any<BR>attachment and all copies and inform the sender. Thank
you.<BR><BR>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR>_______________________________________________<BR>SAP-WUG
mailing list<BR>SAP-WUG@mit.edu<BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR><BR>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.<BR><BR>_______________________________________________<BR>SAP-WUG mailing
list<BR>SAP-WUG@mit.edu<BR><A
href="http://mailman.mit.edu/mailman/listinfo/sap-wug">http://mailman.mit.edu/mailman/listinfo/sap-wug</A><BR></FONT></P></DIV></BLOCKQUOTE></BODY></HTML>