WS14000084 for contracts on SRM 4.0 not starting

Dave Weston Dave.Weston at clockwork.ca
Mon Sep 26 11:01:34 EDT 2005


Hi Sue, I used to use the function module BBP_PDH_WFL_CHECK_BEFORE_START
(hope its the right one !!) in test mode to check the start conditions
and which workflows should be started. 
It was very helpful for the shopping carts approval wokflows and I think
if you put the right onject type in and your Guid it might help you work
out whats going on.
 
Cheers
Dave

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Susan R. Keohan
Sent: Monday, September 26, 2005 10:30 AM
To: SAP Workflow Users' Group
Subject: Re: WS14000084 for contracts on SRM 4.0 not starting


Hi All,

The IMG for SRM 4.0 says 

'Make sure that only one workflow is started for each requirement
coverage request, that means you must formulate the conditions in such a
way that a requirement coverage request cannot fulfill more than one
condition.'.  

Even though this is regarding requirement coverage requests, would this
same rule hold true for Contracts ?

Has anyone turned on the standard WFs for contracts in SRM ?  If so, did
you turn on WS14000086, or WS14000084 ?  Our SRM consultant has the
start conditions for *both* workflows turned on.

Still fishing, hoping for a nibble...
Sue

Susan R. Keohan wrote:


	Hello all, 
	
	This question is being posed from an old R/3 Workflow-er, so
please excuse my lack of knowledge about SRM. 
	
	We have upgraded from EBP 3.5 to SRM 4.0 in our sandbox
environment.  This our landscape: 
	SAP_BASIS        640        SAPKB64011 
	SAP_ABA            640       SAPKA64011 
	SRM_SERVER    500       SAPKIBKS06 
	
	Our SRM consultant has enabled (via SPRO and SWB_COND) the
standard SAP workflow WS14000084 and WS14000086 for BUS2000113, events
CHANGEVERSIONSAVED and SAVED. 
	Example of Start Conditions is attached.  All the 'normal'
workflow customizing has been carried out via SWU3.  Event log is turned
on.  Event linkage is activated, and the check functions are 
	SWB_2_CHECK_FB_START_COND_EVAL (WS14000084) and
SWB_CHECK_FB_START_COND_EVAL (WS14000086). 
	
	The contract is created, but of course, no workflow starts.  Why
else would I be annoying you with this on a Friday. 
	
	SWUD for WS14000084 gives yellow lights on the  binding between
task and event.  Simulate Event gives red light for WS14000084, green
light for WS14000086.  The information on WS14000084 is that there is an
error in the binding definition. 
	
	OSS Note 879528 refers to this workflow (WS14000084) in a
different context, but suggests changing the binding.  Okay, I know how
to do that, but step 7 of this note says to change the binding to.... 
	
	then there is nothing.  No information on what the binding
should be changed *to*. 
	
	Can anyone shed some light on: 
	What the correct binding for this task should be ? 
	How to tell if the event is raised.  I know in SRM that the
standard event log will not help. 
	What is the difference (in a nutshell) between the two check
functions ? Why use one over the other ? 
	Any other tips and tricks to teach this old dog would be
helpful. 
	
	Thanks! 
	Sue 
	
	
	
________________________________


	 
	
________________________________


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


-- 
Susan R. Keohan
SAP Workflow Developer
MIT Lincoln Laboratory
244 Wood Street
LI-200
Lexington, MA. 02420
781-981-3561
keohan at ll.mit.edu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20050926/99930802/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 242801 bytes
Desc: ATT348664.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20050926/99930802/attachment.jpg


More information about the SAP-WUG mailing list