6\VWHP $GPLQLVWUDWLRQ 0DGH (DV\

Chapter 17: Change ManagementTransporting ObjectsA transport is the mechanism that R/3 uses to move changes: Within a system from one client to another client From one system to another system on the same client From one system to another system and from one client to another clientComplete the transport in the production system during a “quiet” period (for example,Sunday afternoon or evening) when users are not logged on the system.Ideally, a full system backup should have been completed before transports are imported.During a transport, objects may be overwritten. If an object is being used in the targetsystem when a transport is performed, the transport may cause inconsistent results orterminate the transaction. In the worst case scenario, a transport may “break” theproduction system and you will need to restore the system.Transports are only done when necessary (when you have a transport that needs to bemoved). You may also have the occasional “emergency” transport that must be moved at atime other than at your normal weekly transport time.The transport system has been significantly changed in Release 4.x. (It used to be known asCorrection and Transport System.) It is still CTS, but is now called the Change and TransportSystem; In CTS are the Transport Management System (TMS) and Change and TransportOrganizer (CTO).The purpose of transports is to move objects and configuration from one system to anotherin the production pipeline. This pipeline is defined in a three-system landscape as systemscomprising development to quality assurance to production. A transport starts in thedevelopment system, is transported to the quality assurance system where is tested, andfinally into the production system.To transport objects, use one of the following methods: Transport Management System (TMS) Operating system (OS)Transports are taught in BC325 (Software Logistics).System Administration Made Easy17–15