TMS : Transports Between Systems : Setup & Maintenance Phases

          The (initial) setup phase, where no relevant client-specific data is yet in the target R/3 System

          The (subsequent) maintenance phase, where a complete dataset exists in the target R/3 System

 

 

Transports Between Systems: Setup Phase

 

·         For the setup phase, R/3 provides the following tools:

The Workbench Organizer and the Transport System

Remote client copy and client transport

 

·         The setup phase involves the following steps:

1.      Replicate the R/3 Repository. Transport any customer-specific software (such as ABAP programs) to the new R/3 System using change requests, which are executed by the Workbench Organizer and the Transport System.

2.      Transport the Customizing settings to the new system. To transport the Customizing data, use the remote client copy or client transport tools.

 

·         Client transport and change requests use the transport directory to reach their target system. Remote client copy transports data using an RFC connection.

 

·         Remote client copy and client transport are not designed for transferring large-scale production clients, or for database migration.

 

·         All the SAP Systems in the system landscape should be in one transport domain.

 

 

 

Transports Between Systems: Maintenance Phase

 

<

·         As soon as the data has been written to the R/3 Systems, and needs to be retained, remote client copy and client transport can no longer be used to transport changes to Customizing.

 

·         Therefore, distribute further changes using the Customizing Organizer (CO). To use the CO, you must first activate automatic recording of changes for the client.

 

·         As with the Workbench Organizer (WBO), the CO records the objects that have been changed. In the case of Customizing, these changes are primarily table settings.

 

·         During the maintenance phase, changes to the R/3 Repository and to cross-client Customizing continue to be transported using the WBO.

 

·         The main difference between CO & WBO is that the CO is used primarily to manage changes to Customizing. However, the CO can also be used to manage Workbench requests. To keep Customizing and Workbench development logically separate, changes to the R/3 Repository should only be managed using the WBO.

 

·         Both Customizing and the WBO allow the recorded objects to be transported to the local transport directory. From there, the data is imported into the target system, using the Transport System.