Better Management of Change Requests with Extended Transport Control

  • by Sue McFarland Metzger, Technical Core Competence Member, SAP
  • May 15, 2000
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.

Sue McFarland Metzger

Sue McFarland Metzger is a member of SAP’s Technical Core Competence (TCC) and is responsible for the support of change management tools, procedures, and strategies. Prior to joining SAP in 1995, Sue’s consulting experience ranged from programming and instruction to managing the migration of business processes to client/server environments. Sue has a B.S. in Mathematics from Bucknell University and an M.S.E. in the Management of Technology from the University of Pennsylvania.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.