Binding issues after transport to production

Carolyn Fuller fuller at MIT.EDU
Wed Feb 11 19:04:41 EST 2009


Alon,

Yes. We modified the workflow binding in production in order to fix  
the problems that appeared in production but did not appear in either  
QA or development.

Carolyn
On Feb 11, 2009, at 4:16 PM, Alon Raskin wrote:

> Just to clarify, you are modifying the workflows directly in the
> production system?
>
> Alon Raskin
> e: araskin at 3i-consulting.com
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On  
> Behalf
> Of Carolyn Fuller
> Sent: Wednesday, February 11, 2009 2:17 PM
> To: SAP Workflow Users' Group
> Subject: Binding issues after transport to production
>
> Hi all,
>
> On a couple of occasions I've moved modified workflows from our
> development environment to our QA environment with no problems only to
> encounter binding issues in production. On these occasions, deleting
> the bindings in production and re-creating them in production has
> solved the problem.
>
> Are these issues due to the fact that I didn't run SWU_OBUF after the
> transports went in? Should SWU_OBUF be on our action log when modified
> workflows go into production?
>
> ---
> Carolyn Fuller
> Massachusetts Institute of Technology
> Information Services and Technology
> Administrative Computing
> Senior Analyst/ Programmer
> (617) 253-6213
> http://fuller.mit.edu/
>
> _______________________________________________
> 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




More information about the SAP-WUG mailing list