Import 45b (TMS) correction into 46b

[Gregory Kowalik]

You need to tell your client not to do it.
I have never heard about the development path (DEV -> QAS -> PRD) being on
different releases.
Theoretically it should work with development objects, but workflow might be
messed up.
I do not have experience with that, but the common sense tells me not to try it.
 
Greg
 
 
 
 
 
 
"Wold, Scott" <scott.wold at sap.com> on 10/04/2000 02:54:44 PM
 
Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Gregory Kowalik)
Subject:  Import 45b (TMS) correction into 46b
 
 
 
Hello all,
 
Does anyone have any experience developing workflow definitions, objects,
programs, etc. in more than one development system, where the development
systems are on different releases (DV1 is on release 45b and DV2 is on
release 46b), and importing the corresponding transports into a consolidated
QA (QAS is on release 46b) and Production (PRD is on release 46b) system?
 
I have a customer who is considering this (beyond my control) and I don't
have any practical experience in such an environment.  In their particular
case, I believe all logically-related development will originate in only one
of the development systems, but both development systems will be developing
their own independent workflows.
 
My primary concern is how well the 45b TMS correction can be imported into
the consolidated 46b QA environment.
 
Is there anyone with any experience with this who would care to comment?
 
Thanks,
Scott
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20001004/4f5cb9fb/attachment.htm