Repetitive Transport Strategy

[Kjetil Kilhavn]

What?
I hope this applies to 4.7 only. Can anyone confirm that?
--
Kjetil Kilhavn
 
 
 
 
 
                    Rick Sample
                    <Rick.Sample at gbe.com        To:     SAP-WUG at MITVMA.MIT.EDU
                    >                           cc:     (bcc: Kjetil Kilhavn)
                    Sent by: SAP                Subject:     Re: Repetitive Transport Strategy
                    Workflow
                    <Owner-SAP-WUG at MITVM
                    A.MIT.EDU>
 
 
                    05.12.2003 23:47
                    Please respond to
                    "SAP Workflow Users'
                    Group"
 
 
 
 
 
 
We were told this in classes and by our SAP consultant also
but depends on what you are transporting.
 
Here is what I have noticed:
If you transport a in the correct order most of the times it does not
require 3x.
Function Modules first, then Tasks, then Templates in that order. This of
course
will require 3 separate transports verse 1 transport with everything in it.
 
Six of one, half a dozen type thing.
 
Before I was doing a lot of work with others, just putting everything in
one transport
was the easiest. (Raised eye browse from Transport team and others but
worked!)
And I didn't have to wait around half the night waiting for return codes to
tell them to re-transport again.
 
Now that I am working with others I split them out the way it should be.
FM, Tasks, and Templates.
But sometimes when a lot of changes are made to the Template, addition of
FMs, new Tasks, etc. I still
need to have the Transport team re-transport! Binding issues.
 
If you are _sure_ you won't be hampering anyone else's development (or them
impacting you)
I don't see anything wrong with the transport 3x. I got away with it for a
long time. Easy to have everything in one transport.
 
Problems come up if you have a bunch of stuff in your transport along with
other developers work
and they need to move their work (or vis versa). You would then have
issues.
For instance. Both are working in the same FG. Someone else is ready to
move their FM but you are not!
 
Rick
 
 
 
 
>>> John.Cooper at kcc.com 12.5.2003 3:41:15 PM >>>
One of our workflow consultants has made the recommendation that all
workflow transports be transported into our 4.7 production system three
times.  According to him, there is a known issue with workflow
components not being generated in the correct order.  The first
transport is to put all the components into production.  The second
transport is to ensure the links were generated properly.  The third
transport is just for reassurance that the transports were installed and
link correctly.
 
Is this what everyone else is doing in 4.7?  Any and all comments
welcome!
 
Thanks everyone!
 
John Cooper
 
------------------------------------------------------------------------------
 
This e-mail is intended for the use of the addressee(s) only and may
contain privileged, confidential, or proprietary information that is exempt
from disclosure under law.  If you have received this message in error,
please inform us promptly by reply e-mail, then delete the e-mail and
destroy any printed copy.   Thank you.
 =============================================================================
 
 
 
 
 
-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.