...
Please repeat following steps for each system and client of your landscape:
TMSORG
Usually you want to perform creation, update, delete and release of your transport requests in your development system and client only. You have to configure the transport organizer feature in all individual clients of your development system. If you want to create/manage transports in your quality assurance or production system too, you have to configure this feature there as well.
...
| Info |
|---|
The steps described above are creating a RFC destination with a fixed user and password. Alternatively you can create the TMSORG RFC destination as Trusted destination without user and password. In this case the technical sync user will be used. You have to create this user in the managed system with proper authorities including S_RFCACL and S_RFC. |
TMSIMP
Usually you want to perform an import to all managed systems except the development system where you only want to build transport requests. But if you want to control external transport requests as well, you might need the import feature for the development system ( and client) too. We reccommend to configure the import feature on client 000 for security reasons, but theoretically you can use any client.
...
| Info |
|---|
The steps described above are creating a RFC destination with a fixed user and password. Alternatively you can create the TMSIMP RFC destination as Trusted destination without user and password. In this case the technical sync user will be used. You have to create this user in the managed system with proper authorities including S_RFCACL and S_RFC. |
TMSADM
For reading transport details, for instances the import status and return code, the cross connector is using the TMSADM destination and user (Example: TMSADM@S4H.DOMAIN_S4H). You don’t have to care about this destination since STMS is automatically creating and updating it on registration of a system to a transport domain or on creation and distribution of a domain link.
Notes:
If you are facing authority issues related to TMSORG or TMSIMP, you can try to assign the pfcg role SAP_BC_CTS_ADMIN temporarily.
Please check the TMS Alert Viewer if you are facing issues using the RFC destinations.
The names of the RFC destinations are predefined by CTS, please have a look at class CL_CTS_TMS_CI_TARGET. If you want to use different RFC destinations, you have to implement BADI CTS_BADI_FOREIGN_SYSTEM.
Side-fact: As already mentioned: SAP Solution Manager is using different RFC destinations. However, if you have still configured the RFC destinations mentioned above, they will be used, also in SAP Solution Manager systems. Also ChaRM will then make use of it! This might be helpful, if you want to allow transport imports without adding such import authorities to the end-user (trusted RFC destination) or the TMW user (TMW rfc destination).
If you want to use virtual systems, you should read article Are we supporting virtual or external systems?