<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE></TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2668" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=126542307-27072005><FONT face=Arial><FONT
color=#0000ff><FONT size=2>Argh! The reason it work<SPAN
class=961563307-27072005>ed</SPAN> fine in Dev is that the event
queue <SPAN class=961563307-27072005>wa</SPAN>s turned off there.<SPAN
class=961563307-27072005> Needless to say, it is not turned off any
longer.</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV align=left><FONT face=Arial size=2>-- </FONT></DIV>
<DIV align=left><FONT face=Arial size=2>Kjetil Kilhavn, Statoil KTJ IT
BKS</FONT></DIV>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Kjetil Kilhavn <BR><B>Sent:</B> 27. juli
2005 09:19<BR><B>To:</B> 'SAP Workflow Users' Group'<BR><B>Subject:</B> RE:
[46C] SAP_WAPI_CREATE_EVENT works fine in Dev - no event created inQA
system<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/plain format -->
<P><FONT size=2>Thanks for the beer update Mark :-)<BR></FONT><FONT size=2>No, I
didn't debug SWE_EVENT_CREATE with the START_RECFB_SYNCHRON flag set, since
SAP_WAPI_CREATE_EVENT doesn't specify a value for that parameter in its call
(and the default is space).</FONT><FONT size=2><BR><BR></FONT><FONT size=2>The
lack of signs of problems is what is so strange. There are no short dumps.
There are no tRFC problems. I didn't check SM13 yesterday, but I did now and
there is nothing. I tried turning the SQL and RFC trace on too (ST05) yesterday,
but I couldn't find anything very strange there either. However, I am not an
expert at interpreting traces. I assume that when RC is zero things are fine
:-)<BR><BR>What I find there is that after the call to SWW_WI_TO_OBJECT_FIND
(revealed by a SWWVCONTWI fetch) there are a few statements that probably should
have done the trick. The text lines are quite long, so I chose to include it as
a picture. It is rather big unfortunately.<BR><IMG
src="cid:961563307@27072005-1DB1"></FONT></P>
<DIV><FONT size=2><FONT face=Arial color=#0000ff></FONT></FONT> </DIV>
<DIV><FONT size=2><FONT face=Arial color=#0000ff>Just to "confirm my worst fear"
I turned off the event queue for the linkage, and then it immediately worked as
it should - the event appears in the log and the workflow starts. I suppose that
will be the way to go then, at least right now. I don't like it since another
solution creates quite a few of these events in a short time frame. And by
definition I don't like it since I don't understand why the other solution
doesn't work :-)</FONT><BR></FONT><FONT size=2>--<BR>Kjetil Kilhavn,
Statoil KTJ IT BKS</FONT></DIV>
<P><FONT size=2><FONT face=Arial color=#0000ff></FONT><FONT face=Arial
color=#0000ff></FONT><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 Mike Pokraka<BR>Sent: 26. juli 2005 16:47<BR>To: SAP Workflow Users'
Group<BR>Subject: Re: [46C] SAP_WAPI_CREATE_EVENT works fine in Dev - no event
created inQA system<BR><BR>Hi Kjetil,<BR>Sounds more sinister than straight
workflow/ABAP. Some of these may be obvious, but there are always trees in a
forest:<BR><BR>Short dumps?<BR>SM13 - Update failures?<BR>stuck in SM58<BR>Might
be worth poking around the system log.<BR><BR>Cheers<BR>Mike<BR><BR>Kjetil
Kilhavn wrote:<BR>> I have never been bothered by a stranger problem I think.
A workflow<BR>> solution has to be developed for approval of access to
buildings,<BR>> which uses a custom infotype in HR. Anyway, the code for the
infotype<BR>> calls a function I have written, and in my function I have a
call to<BR>> SAP_WAPI_CREATE_EVENT.<BR>><BR>> Everything is fine in
development, the function is called,<BR>> SAP_WAPI_CREATE_EVENT is called and
returns successfully (at least one<BR>> receiver found), the event log
displays the entry and the workflow<BR>> starts.<BR>><BR>> In Quality
Assurance the function is called, SAP_WAPI_CREATE_EVENT is<BR>> called and
returns successfully (at least one receiver found), and the<BR>> event log
displays ... nothing, nada, nix. Naturally the workflow does<BR>> not
start.<BR>><BR>> Using SWUE to create the event in QA works like a charm.
The event log<BR>> displays the entry and the workflow
starts.<BR>><BR>><BR>> I've been trying to figure out what the problem
is and making minor<BR>> changes in the code. Nothing has helped so far, and
it is a bad idea<BR>> to change code which works (it works in the development
system at<BR>> least). I have tried both with and without commit_work, and it
makes<BR>> no difference that I am able to observe.<BR>> --<BR>> Kjetil
Kilhavn, Statoil KTJ IT BKS<BR>><BR>><BR>><BR>>
-------------------------------------------------------------------<BR>> The
information contained in this message may be CONFIDENTIAL and is<BR>>
intended for the addressee only. Any unauthorised use, dissemination<BR>> of
the information or copying of this message is prohibited. If you<BR>> are not
the addressee, please notify the sender immediately by return<BR>> e-mail and
delete this message.<BR>> Thank you.<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>Mike
Pokraka<BR>Senior Consultant<BR>Workflow Connections Ltd.<BR>Mobile: +44 (0)7786
910 855<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></P></FONT><p></p><p><font size=1>-------------------------------------------------------------------<br>The information contained in this message may be CONFIDENTIAL and is<br>intended for the addressee only. Any unauthorised use, dissemination of the<br>information or copying of this message is prohibited. If you are not the<br>addressee, please notify the sender immediately by return e-mail and delete<br>this message.<br>Thank you.</font size></BODY></HTML>