WF Runtime syncronization issues 4.6c

Wed Jul 2 11:53:27 EDT 2008

G'Day Rick,

I share your pain! Yes, it's the testers that are sometimes more
important. Not so much logging out of SAP, but if they remain in the SBWP
and you send a WI with the new definition, it will still have the old
definition cached.

Of course these are my experiences with later versions. If you can
reliably reproduce it without any other people interfering, it may be
worth complaining to OSS.

Cheers,
Mike

On Tue, July 1, 2008 6:51 pm, Sample, Rick wrote:
> Hey Mike,
>
> Shut down all SAP. Logged in, PFTC_CHG, Generate Runtime, create new
> version, completely log out of SAP. Then,
> login to 120 client, PFTC_DIS (120 closed for mods), Generate Runtime,
> completely log out of SAP.
> Yea, I tried that. Nada!
>
> I do have a few folks 'testing' while I am making changes. (Deadlines
> you know!)
> You saying they should also log out of their SAP inboxes / sessions?
> Kind of hard to control that one.
>
> This issue really shows when system resource are low.
> When we shut down some other clients performance picks up and
> every great once and a while I will have old stuff in a WF runtime but
> usually picks up the change as I execute the WF.
>
> Thanks for you assistance. I really appreciate it,
> Rick
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Tuesday, July 01, 2008 11:28 AM
> To: SAP Workflow Users' Group
> Subject: RE: WF Runtime syncronization issues 4.6c
>
> Hi Rick,
>
> Something that still catches me out is the session buffer. I'll still
> have
> one test user's session sitting in SBWP whilst I refresh the WF. Then
> later I goto that user, inbox, execute WI & guess what: the SBWP
> transaction still holds onto the old definition.
>
> Make sure you come out of all transactions in all sessions whenever you
> perform a change. Then SWDD -> Generate runtime version in your test
> client, then back into SBWP for your test users.
>
> But then I suppose your chickens have probably already taken care of all
> that...
>
> Cheers,
> Mike
>
>
> On Tue, July 1, 2008 3:29 pm, Sample, Rick wrote:
>> 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
>>
>>
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>