Before you start, please contact https://crossalm2.atlassian.net/servicedesk/customer/portal/6 to get receive the Transport Requests containing the SAP side of this solutionthe configuration.
Option “SAP Solution Manager”:
...
The support package level of your SAP Solution Manager does not matter but should be up to date. We need a
Version 7.2 version.This 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 a domain controller Managing system which is not a SAP Solution Manager system. This domain controller Managing system has to be connected to all involved systems and clients via TMS Trusted/Trusting RFC services (TMSADM@…, TMSORG@…, TMSIMP@…). CTS_PLUGIN (or SAP_BASIS) software components and must be up to date. As workaround The preferred option is to use the domain controller. Alternatifely you can use your backup domain controller as wellor any other system/client of your landscape.
The release and support package level of your domain controller (and your managed systems) 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 is in place.
Involved Managed Systems:
There are no No implementation steps need to be performed in your managed systems. No transport request has 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 necessary authorities.There is one 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 exceptionallythe necessary authorities.