workflow change synchronization

[Mark Pyc]

G'day George,

Make sure you back out of all WF related transactions before running
SWU_OBUF. It's amazing what those transactions can hang on to, especially
SWO1.

Good luck,
Mark


On 7/21/06, Knoske, George <George.Knoske at kaobrands.com> wrote:
>
>   Hi All,
>
> We've very recently upgraded to version ECC6 and are encountering
> significant delays in workflow builder changes being reflected in WF tests
> we run.  On several occasions we've made step changes, or binding changes,
> only to see them not 'take effect' until several hours later or even the
> next morning.  While the changes would be visible within WF builder
> immediately after the change, the same wouldn't hold true when the WF was
> triggered and the runtime result.  One example is I deleted a 'send mail'
> step from my workflow.  Next I triggered the workflow and I received an
> error at the location step/node where the 'send mail' used to be.  The error
> was something like 'error when loading callback component; missing node not
> found'.   I use the transaction SWU_OBUF after every change I make, but it
> doesn't appear to make a difference.  Again, sometimes I'll run a test the
> very next morning, and everything works fine.  Has anyone else experienced
> this?
>
>
>
> Thanks in advance.
>
>
>
> *-------------------*
>
> *George Knoske*
>
> *Information Technology *
>
> *Services and Solutions*
>
>
>
> *Kao Brands Company*
>
> 2535 Spring Grove Ave. Cincinnati, OH 45214
>
>
>
> _______________________________________________
> 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/20060721/b4ff2414/attachment.htm