If you work with IMG Project Management then you can use transport control to plan your development work and Customizing activities in structured projects. You can structure changes independently of each other in different projects, and then import them independently into target systems. We recommend that you do this if, for example, you want to go live with different projects at different times, or if you want to link development work in a single area.

If you go to the corresponding IMG nodes of an IMG project you can only make changes in requests that are assigned to the project. The project to which a change request belongs is displayed in the import queue. This means that you can make imports into target systems project-by-project.

It is important that you make sure that projects are free from dependencies while you plan them.

It is important that you make sure that projects are free from dependencies while you plan them. However, the Change and Transport System does support small overlaps between projects. If your projects do overlap, then you must define dependency relationships between the objects that belong to different projects but contain some of the same objects. These relationships need to be defined to ensure that imports are made in the correct order.

In certain situations, project administrators need to restrict what work can be done in a project. They can control this with the project status switch.

For more information, see Transport Strategy in the CTS and Working with Projects.