[LIKELY JUNK]Re: SAP_WAPI_CREATE_EVENT and Workflow binding

Dart, Jocelyn jocelyn.dart at sap.com
Thu Jan 8 00:14:55 EST 2009


Dear Kathy, 
To clarify - I wanted you to use SAP_WAPI_READ_CONTAINER on an existing workflow instance to *** UNDERSTAND *** what you had to put in the event container for SAP_WAPI_CREATE_EVENT.  You still actually have to fill the parameters for SAP_WAPI_CREATE_EVENT. 
 
Regards,
Jocelyn 

________________________________

From: sap-wug-bounces at mit.edu on behalf of Shai Eyal
Sent: Thu 8/01/2009 6:13 AM
To: sap-wug at mit.edu
Subject: [LIKELY JUNK]Re: SAP_WAPI_CREATE_EVENT and Workflow binding


Dear Kathy,
 
Please make sure to fill all SWCONT structure fields as follows:

*	ELEMENT - your element name, use uppercase! 
*	TAB_INDEX - 00001, 00002, ... if you're transfer a table element then you should have same index several times. 
*	ELEMLENGTH - according to the data dictionary. 
*	TYPE - according to the data dictionary. 
*	VALUE - your element value.

I assume you did but make sure to append the data to the internal table you use.

If it's still does not work please copy the source code to txt file and attach it.

 

I can assure you that is suppose to work - I've done that several times and it went well.

Good luck.


 

Regards,
Shai Eyal

SAP Logistics senior consultant
SAP Workflow specialist

http://www.linkedin.com/in/shaieyal
Mobile: 972-52-5816633

------------------------------

Message: 2
Date: Wed, 7 Jan 2009 10:47:51 -0600
From: "Penhall, Kathy" <kpenhall at hydro.mb.ca>
Subject: SAP_WAPI_CREATE_EVENT and Workflow binding
To: <sap-wug at mit.edu>
Message-ID:
    <CAD3E86E65D76C47BD61434EDFD7D10F01A12889 at MHMAIL02.hydro.mb.ca>
Content-Type: text/plain; charset="us-ascii"

Hello Workflow folks,

We are having a similar problem as Srinivas Oota recently posted here.
We are attempting to code an event to kick off a workflow and the
container doesn't seem to be passed to the workflow from the function
call.  Originally we just attempted to copy the SAP logic in
LHRTEM00NETF53 to generate the event PDRELA_025.MOVED where approriate,
by copying the code used when PDRELA_025.MOVEREQUESTED is generated,
which uses function SWE_EVENT_CREATE.  However when we did this, our
moved event was not being generated, despite the fact that this same
code still works for the moverequested event.

So as Jocelyn suggested, we changed our code to use function
SAP_WAPI_CREATE_EVENT and have populated the container with the data
required by the workflow.  The event is now generated, but the values in
the container don't appear to have been passed to the workflow even
though the return code from the function is 0 and the only message
generated by the function call is "Event created - at least one receiver
found".    I confirmed the fields were not populated by running
SAP_WAPI_READ_CONTAINER as suggested and found the two container
elements I defined and populated for the event function call are in the
container, but not populated as I would have expected them to be.

Any suggestions on what we might be missing?


Kathy Penhall 
HR Applications
SAP Support Services 
693 Taylor Avenue
(tel)204-477-7197 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20090107/40f0c1c1/attachment-0001.htm

------------------------------

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


End of SAP-WUG Digest, Vol 50, Issue 4
**************************************


________________________________

Get your new Email address! <http://sg.rd.yahoo.com/aa/mail/domainchoice/mail/signature/*http://mail.promotions.yahoo.com/newdomains/aa/> 
Grab the Email name you've always wanted before someone else does!




More information about the SAP-WUG mailing list