Request and Import Transport Requests
Before you start, please contact https://crossalm2.atlassian.net/servicedesk/customer/portal/6 to receive the Transport Requests containing the SAP side of the configuration.
Option “SAP Solution Manager”
Please request a transport request to be imported into a SAP Solution Manager 7.2 system. This SAP Solution Manager needs to be connected to all involved systems and clients via Managed System Configuration of SOLMAN_SETUP. LMDB must be aware of all systems and clients. At least the READ and TMW destination must exist.
The support package level of your SAP Solution Manager does not matter but should be up to date.
Version 7.2 is the preferred option if a SAP Solution Manager system is in place.
Option “Managing system”
Please request a transport request to be imported into Managing system which is not a SAP Solution Manager system. This Managing system has to be connected to all involved systems and clients via TMS RFC services (TMSORG@…, TMSIMP@…). CTS_PLUGIN (or SAP_BASIS) software components and must be up to date. The preferred option is to use the domain controller. Alternatifely you can use your backup domain controller or any other system/client of your landscape.
The release and support package level of your Managing system does not matter. We need SAP Netweaver 7.40 or higher. S/4 HANA Private Edition or On Premise are supported as well. BW/4 HANA is not supported since software component S4FND is missing there. S/4 HANA public cloud is not supported since we are not allowed to import a transport request containing classical development.
This is the preferred option if there ist no SAP Solution Manager system in place.
We recommend using the domain controller or backup domain controller as managing system if no SAP Solution Manager is in place. This will give you some benefits:
The managing system is able to reach all managed systems. There will be no network or firewall issues.
The managing system can use Trusted connections if RFC destinations are configured in this way. There is already a Trusting Trusted relationship established by CTS/TMS.
The managing system can use CTS/TMS RFC infrastructure (using user TMSADM) as fallback.
The managing system is aware of all managed systems. The managed systems will not be considered as foreign systems. This might be helpful for error analysis. Maybe there is no need to check TMS Alert viewer in managing system and managed system in case of issues, one of them is enough.
If you do not want to use the domain controller or backup domain controller, you can use any other ABAP system fulfilling the mandatory prerequisites. In this case we still recommend to use a production system instead of a development or quality assurance system because of its security and availability level. The system acting as managing system should be high secured and always available.
Involved Managed Systems
No implementation steps need to be performed in your managed systems. No transport request need to be imported.
Dependent on your RFC destinations you might need to check/adjust the PFCG authorities of the users used to perform transport creation, deletion, release or import. As mentioned above, we are using standard users who should already exist and who should already have the necessary authorities.
Your managed system can be any ABAP system providing and using CTS functionalities. For instances it can be a old ECC system, old CRM/SCM system, old BW system, S/4 HANA On Premise, S/4 HANA Private Edition, BW/4 HANA On Premise, BW/4 HANA Private Edition, …
None-ABAP (Cloud) Systems like C/4 HANA, Success Factors, Ariba, … are not supported because these products are no ABAP systems with no CTS functionality. S/4 HANA Public Cloud, BW/4 HANA Public Cloud, BTP ABAP Environment are not supported because these systems are ABAP systems but CTS functionality is disabled resp. not available resp. not used as delivery tool. However in future these Cloud/None-ABAP products will be supported as well by using cTMS functionalities provided by BTP. More details on this topic can be found here: Interoperability & Compatibility with TMS features - Cross Connector - Confluence