Changes to WF Start Conditions were not reflected to the target s ystem after transport

earzola@axtel.com.mx earzola at axtel.com.mx
Thu Jul 1 09:57:08 EDT 2004


After transporting any change to another client, is hardly recommended to
run transaction SWU_OBUF  to synchronize the Run time Buffers
 
Hope this helps
 
Regards
 
 
 
 
                      "Rivera, Raul"
                      <Raul.Rivera at absu.acc        To:       SAP-WUG at MITVMA.MIT.EDU
                      enture.com>                  cc:
                      Sent by: SAP Workflow        Subject:  Changes to WF Start Conditions were not reflected
                      <Owner-SAP-WUG at MITVMA         to the target s ystem after transport
                      .MIT.EDU>
 
 
                      30/06/2004 08:15 p.m.
                      Please respond to SAP
                      Workflow Users' Group
 
 
 
 
 
We are in 4.6C.
 
 
 
Workflow start conditions for existing and new custom workflows were
created
in DEV. A transport was created for each of the new start conditions.
 
 
 
These transports were then released to our Staging client together with all
related transports for the modifications. In the target system (STG), the
creation/modification to the start conditions were NOT reflected.
 
 
 
Did anyone had this experience before or was it something I might have
missed?
 
 
 
Thanks,
 
 
 
 Raul
 


More information about the SAP-WUG mailing list