SWW_WI_START_SIMPLE container (back on subject)

[Kjetil Kilhavn]

As suggested in a previous answer I believe it is because in 99,99999% of the workflow instances the processing time of the multistep task will prohibit the function from waiting for a response which includes exporting parameters. Thus there isn't really any incentive to implement support - which would imply an analysis of the workflow to determine if it is all batch with immediate execution.
 
Perhaps you could hope to receive the exporting parameters if it was a single-step task you started instead of a multi-step task.
-- 
Kjetil Kilhavn, Statoil KTJ IT BKS
 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Alon Raskin
Sent: 21. juli 2005 10:46
To: 'SAP Workflow Users' Group'
Subject: RE: SWW_WI_START_SIMPLE container (back on subject)


Actually not the way I expected to. I ran the workflow synchronously but the container did not contain the EXPORTING parameters like I expected that it would. So, I just used the WAPI to read the result.
 
Anyone know what happened to my EXPORTING container params? I am curious....
 
Alon Raskin
e: araskin at 3i-consulting.com <mailto: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 <http://www.3i-consulting.com/> 
 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Kjetil Kilhavn
Sent: Thursday, July 21, 2005 1:57 AM
To: SAP Workflow Users' Group
Subject: RE: SWW_WI_START_SIMPLE container (back on subject)


Does that mean that you actually *did* manage to get container values back to the function?
-- 
Kjetil Kilhavn, Statoil KTJ IT BKS
 


________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Alon Raskin
Sent: 20. juli 2005 19:07
To: SAP Workflow Users' Group
Subject: RE: SWW_WI_START_SIMPLE container( off subject )


Hi Nate,
 
You are right. Maybe it should not have been implemented as a WF. However this was beyond my control. 
I just wanted to see if it was possible (and it was).
 
Thanks,
 
Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com> 
p:  +1 207 756 0370
w: http://www.3i-consulting.com


________________________________

From: sap-wug-bounces at mit.edu on behalf of Workflow
Sent: Tue 7/19/2005 01:08
To: SAP Workflow Users' Group
Subject: AW: SWW_WI_START_SIMPLE container( off subject )


Alon 
Have I understood you correctly, that you've been trying to start a WF synchronously,  execute immediately the different background steps of the WF with the WF-Initiator and return the results of the container to the calling context?
 
If this is the case, and no other agents are involved in the process, wouldn't a simple function call with importing / exporting be much easier to implement?
 
just thinking out loud
Nate

	-----Ursprüngliche Nachricht-----
	Von: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]Im Auftrag von Alon Raskin
	Gesendet: Montag, 18. Juli 2005 20:25
	An: sap-wug at mit.edu
	Betreff: SWW_WI_START_SIMPLE container
	
	
	I am using FM SWW_WI_START_SIMPLE to call a synchronous WF (see previous postings earlier today). Everything seems to be fine but the only thing I noticed is that the container (table parameter WI_CONTAINER) is empty and does not contain any of the EXPORTING container parameters.
	 
	I know I can use the WAPI to read the container from the DB but I was trying to save the hit to the DB and just get the container value back from the FM. Anyone ever do this in the past?
	 
	
	
	Alon Raskin
	e: araskin at 3i-consulting.com <mailto: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

-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you. 



-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050721/1fed6c07/attachment.htm