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 “Domain Controller”:

Please request a transport request to be imported into Domain controller system which is not a SAP Solution Manager system. This Domain Controller 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 Domain Controller does not matter. We need SAP Netweaver 7.40 or higher. S/4 HANA Private Edition or On Premise are supported as well.

This is the preferred option if there are no SAP Solution Manager system is in place.

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.

There is a special case: If you want to perform a transport activity in your SAP Solution Manager or domain controller system and client, the technical user used by the Jira plugin will need additional PFCG authorities. This issue is caused by the fact, that the transport activities will here be performed using RFC destination NONE exceptionally.