Problem with binding the WI_RESULT from a decision step

[Alon Raskin]

I guess you are right, but what are you achieving by 'avoiding' the container operation? 
 
Alon Raskin
e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com> 

________________________________

From: sap-wug-bounces at mit.edu on behalf of ???? ????
Sent: Tue 3/20/2007 08:57
To: SAP Workflow Users' Group
Subject: RE: Problem with binding the WI_RESULT from a decision step


Alon,
Thanks for the quick reply.
Thought that this binding will allow me not to create an extra container operation as you mentioned.
Any ideas ?
Thanks,
Ronen

	-----Original Message-----
	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Alon Raskin
	Sent: Tuesday, March 20, 2007 2:19 PM
	To: SAP Workflow Users' Group
	Subject: RE: Problem with binding the WI_RESULT from a decision step
	
	
	Ronen,
	 
	I am confused. Why are you using this approach? Wouldn't it be easier to model each 'decision option' as an outcome and then do a container operation in the outcome branch to set the flag to True?
	 
	
	
	
	Alon Raskin
	e: araskin at 3i-consulting.com <mailto:araskin at 3i-consulting.com> 
	 

________________________________

	From: sap-wug-bounces at mit.edu on behalf of ???? ????
	Sent: Tue 3/20/2007 07:46
	To: SAP Workflow Users' Group
	Subject: Problem with binding the WI_RESULT from a decision step
	
	
	Hello All,
	 
	We are on ECC 6
	 
	A simple WF is created where the user receives a decision task based on the standard TS00008267
	 
	After the decision step there is a loop that is supposed to end if the user has chosen one of the options.
	 
	A new container element is created in the Workflow calls "rej-flag" and based on SWD_LINES-RETURNCODE
	 
	There is a binding from the step to the workflow (See enclosed document)
	 
	However the "rej-flag" remains empty and does not receive any values, making the WF to fail at the loop step.
	 
	This has worked perfect in release 4.6c in other systems. Any idea what is wrong here ?
	 
	Thanks and best regards,
	Ronen
	 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/ms-tnef
Size: 7948 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20070320/6fe0f5ed/attachment.bin