The ever-increasing complexity of software projects in the field of SAP NetWeaver and the resulting dependency on development objects of the ABAP and Java environment call for a solution that ensures the synchronous distribution of these objects in the test environment and, subsequently, in the production systems. Without this synchronization, modified interfaces, for example, could cause costly business process interruptions.

Thanks to the introduction of the OTO concept (also called CTS+), SAP has been offering SAP NetWeaver customers the opportunity to incorporate the archive files of Java and Web elements into ABAP transport requests since May 2007. This includes, for example, the EPA files of the Portal Development Studio and the SCA archives of the SAP NetWeaver Development Infrastructure (NWDI). This allows users in dual-stack environments like XI to combine ABAP and Java objects in one transport request. This ensures the maximum degree of synchronization.

The need for synchronization between the world of ABAP and the world of Java, however, not only exists within the same dual-stack landscape. The increasing complexity of business processes calls for the coordination of transports across all boundaries of the system landscape. Previously, businesses had to rely on organizational measures to ensure this. TransportManager now provides them with the technical measures as well. If, for example, a request of the Portal environment is defined as a "companion" for the request of the ECC system, then TransportManager will make sure that both requests will not be imported into their respective test or production system before both requests were authorized