Workflow Container changes made in 4.6c definitions do not come through to their EEC 6.0 equivalents

[Mike Gambier]

Hi,This may be of interest to anyone considering a code merge period/transition phase from 4.6c to ECC 6.0. Do not assume, as we did, that Transports from the 4.6c environment will take all of your Workflow changes through to ECC 6.0. Some of your changes will have to be carried out manaully in both development systems to keep them in line. With hindsight it should have been obvious that the Workflow Container Definition in ECC 6.0 would have moved on to a 'new' format with the the new Object Category as part of the key, but it wasn't until we started to see serious binding issues coming through that the root cause came to light.Pretty much everything else seems to be transportable though :)Regards,Mike GT 
_________________________________________________________________

http://clk.atdmt.com/UKM/go/msnnkmgl0010000002ukm/direct/01/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20080522/1bb80525/attachment.htm