WF Runtime syncronization issues 4.6c

[Sample, Rick]

Sandy / Mike,
 
I tried them all. Generate version in the org and test clients,
SWU_OBUF, log out / log in, wait few hours, 
I tried creating new versions even though I have not transported it yet,
killed off old version, sacrificed a couple of chickens, 
deleted all old WFs just in case it thought it needed to keep older WF
versions.
 
Nothing is consistent. Sometimes it takes minutes, sometimes hours or
next day. 
 
Sandy,
Since we are prepping for ECC6 on these clients I am forced to deal with
limited resources. 
Could you pleas tell me what your BASIS folks tweaked? 
 
Also, I am having issues with Release Strategy data updating in timely
manor. 
I just noticed on this project (and in this dev environment) that when I
change the RS and 
the go read the data to determine next agent based on the RS, the RS
data is not yet updated. 
 
Anyone have a FM or solution to 'force' this update before I read the
table? 
If I wait a minute before I do a SELECT on the table or wait a minute
and 
get attribute from BUS2012, it works fine. 
 
 
 
 
 

________________________________

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Sandy
Sent: Tuesday, July 01, 2008 12:19 AM
To: SAP Workflow Users' Group
Subject: Re: WF Runtime syncronization issues 4.6c


Hi Rick.
I knew how you feel. It's frustrating, don't you?
Last two weeks, I had same issue where I thought SWU_OBUF is working
fine but it didn't.
I have to wait next day to get new version of my workflow.
In my case, this is due to system performance issue. So after BASIS team
tweaking system parameter, SWU_OBUF working fine.


On Tue, Jul 1, 2008 at 4:19 AM, Sample, Rick <Rick.Sample at graybar.com>
wrote:


	Also, no short dumps or any other clues 'except'
	we have limited recourse due to pending upgrade.
	




	-----Original Message-----
	From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]
On Behalf
	Of Sample, Rick
	Sent: Monday, June 30, 2008 2:54 PM
	To: SAP Workflow Users' Group
	Subject: WF Runtime syncronization issues 4.6c
	
	I have been having issues lately with my WF Templates and
runtime
	versions.
	
	In our development environment, we have client xxx-110 to code,
and
	xxx-120 to test.
	I make my changes in 110, save, and generate. I can see my
changes in
	120. But,
	when a new instance is started, it is still running an older
version or
	worse, a hosed version.
	
	When the runtime is totally hosed, in the log I see for example,
	"BRANCH"  "TRUE" versus "Is Initiator W-BATCH" "Don't send
message".
	And, I can not even view it in Graphic format.
	
	I tried creating new versions, SWU_OBUF, etc. Lately, it is
taking hours
	or a full day to sync up.
	
	Anyone have any clues as to why my Runtime versions are not in
sync
	between clients?
	
	Thanks,
	
	Rick Sample
	SAP Business Workflow Developer
	Graybar, Inc.
	
	
	_______________________________________________
	SAP-WUG mailing list
	SAP-WUG at mit.edu
	http://mailman.mit.edu/mailman/listinfo/sap-wug
	
	_______________________________________________
	SAP-WUG mailing list
	SAP-WUG at mit.edu
	http://mailman.mit.edu/mailman/listinfo/sap-wug
	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080701/f969f1a2/attachment.htm