The Change and Transport System (CTS) is a tool that helps you to organize development projects in ABAP Workbench and customizing, and then transport the changes between the SAP systems in your system landscape. As well as ABAP objects, you can also transport non-ABAP objects and non-SAP applications in your system landscape.
The Change and Transport System (CTS) helps you to organize development projects in ABAP Workbench and in Customizing, and then transport the changes between the SAP systems in your system landscape.
The complete documentation on how to configure CTS and how to set up transport landscapes is available on the SAP Help Portal at Change and Transport System.
If you need to transport non-ABAP objects, please refer to the page about enhanced Change and Transport System (CTS+). On this page, you can find guides and information about applications which support CTS+.
If different developers work on the same project, dependencies may arise between the objects that belong to the project. So that developments are consistent in other systems, all the changes made by the developers must be transported at the same time. Otherwise, you may cause inconsistencies; for example, if a developer creates a table that references a data element created by another developer. If the change request that contains the table is then imported into a target system in which the data element does not exist, the import will encounter errors.
One way of keeping these dependencies under control is to have a fixed transport schedule, in which all changes released up until a certain fixed date are transported into a client or SAP System.
This method is particularly suitable for the early phases of an SAP project when many changes are being made to the system. A transport schedule in a system landscape with a development system, quality assurance system and production system could be as follows:
- All changes are imported once an hour into the quality assurance system.
- All requests are imported once a week into the planned production system.
This schedule lets the developers test their changes almost immediately in the QA system, and correct any errors. The developers’ aim is to consolidate their changes in the QA system before they are due to be imported into the production system. Business processes can be tested in the QA system, and it may also be used for holding training courses. Periodic transports of all changes made to the system reduces the work of the system administrator, and keeps your systems synchronized.