Every implementation and development team instinctively knows that the transporting of change requests is vital to the success of an R/3 implementation. Recognizing that this process can become overwhelming, SAP introduced extended transport control with Release 4.5, so once you define client-specific transport routes, you don't have to worry about managing into which clients a change request must be imported, or whether older versions of client-independent changes will be overwritten. This article will show you, step by step, how this can be accomplished as it covers how to activate extended transport control; define client-specific transport routes; import with extended transport control; and create and use "target groups" to facilitate the distribution of change requests to multiple clients.