Transports in Heterogeneous SAP System
Landscape 
With the Change and Transport System (CTS), provided with usage type Application Server ABAP (AS ABAP) and the SAP NetWeaver Development Infrastructure (NWDI), provided with usage type Application Server Java (AS Java), SAP NetWeaver provides a comprehensive set of functions to control transports in both ABAP and Java environments. The CTS is capable of transporting non-ABAP object types, such as from the SAP NetWeaver usage types Process Integration (PI), Enterprise Portal (Portal), and so on.
In an SAP system you have the possibility to develop in ABAP, in the J2EE standard, or to use SAP-specific non-ABAP technology such as Web Dynpro Java or the SAP NetWeaver Portal. You can choose from these options based on your preferences, knowledge that is already available in one of the technologies, or with respect to specific advantages of one technology in certain areas. For example, in any bigger landscape you will find many or even all of these objects. If you use the SAP NetWeaver Portal to provide users with role-based access to a new functionality in your ERP back-end system, you have to synchronize the update of both the portal and the ERP runtime which even might be connected to other systems using the NWDI or the PI. This is simplified a lot when you use the NWDI with its transport capabilities. The easiest way, however, is to manage such transports centrally in one system. With the functionality of the CTS, you can handle any type of object that can be transported in an SAP system landscape. Therefore, an administrator of your ABAP system can now also manage the transports for the non-ABAP parts of your system landscape.
You can now use CTS to transport objects in an SAP system landscape with transport requests of the Transport Organizer tool of the CTS:
- Enterprise portal archives (EPAs).
- PI objects (TPZs).
- Software Component Archives (SCAs).
- Software Delivery Archives (SDAs).
- Enterprise Archives (EARs).
- ABAP objects.
Development objects will be deployed according to their application type. Objects in a single transport request can be a mixture of all types. However, this only makes sense if both are intended for the same system because transport paths are defined in the transport domain controller system.
More Information: