In CTS mode, you perform transports using the ES Builder and the CTS Transport Organizer. The following tools are required:
Tools for Transports in CTS Mode
Transport Management System |
Determine the systems involved in transports and transport routes. |
ES Builder |
Determining the object set for transport |
Status display |
|
Resolving conflicts in imports |
|
Finding Transports |
|
Transport Organizer |
Importing change requests to the target system (Development, Consolidation, Assembly) |
You normally transport objects from a development system (DEV) to a consolidation system (CONS) and then from the consolidation system (CONS) to a productive system (PROD). You can include objects from both SAP PI as well as objects from other sources (such as ABAP development objects) in a transport request. The following table concentrates on ES Repository and Integration Directory objects:
Transport Units Dependent upon Source and Transport Scenario
Source | Supported Transport Units (Depending on Transport Scenario) | |
---|---|---|
From DEV to CONS | From CONS to PROD | |
ES Repository |
Change and transport lists |
Usually: Software component versions |
Change and transport lists (emergency corrections in the Integration Builder) |
||
Integration Directory |
Transport lists (objects of a party, service, or configuration scenario) |
Usually: Change lists (after their import and manual release in the Integration Builder or further changes in the consolidation system) You can also create new transport lists. |
As shown in the table, the usual transport units and the necessary steps depend on the source (ES Repository or Integration Directory) and the transport scenario.
In the development system ES Builder you normally export transport requests which can be transported to the consolidation system using CTS. In this way you use CTS to control the further transport of the objects and the import into the target system.Exceptions: