Skip to content

sap-s-4hana-cloud-public-edition-a4238a9.md

Latest commit

 

History

History
211 lines (99 loc) · 9.47 KB

sap-s-4hana-cloud-public-edition-a4238a9.md

File metadata and controls

211 lines (99 loc) · 9.47 KB

SAP S/4HANA Cloud Public Edition

Enable the transport management with Adaptation Transport Organizer.

By enabling the transport management for SAP S/4HANA Cloud Public Edition with the Adaptation Transport Organizer (ATO), you can keep track of the deployment of transport requests through your implementation landscape.

Note:

Only released transports can be assigned to features. For more information, see Integration of Deployment Tools.

To use the ATO for SAP S/4HANA Cloud Public Edition in an SAP Cloud ALM environment, you have to establish a connection between SAP Cloud ALM and the ATO.

Note:

If you have multiple SAP Cloud ALM tenants, you should only connect your SAP S/4HANA Cloud Public Edition tenants to your productive SAP Cloud ALM tenant.

Getting the Binding Credentials of the SAP Cloud ALM API Service Instance

Depending on when you requested the SAP Cloud ALM tenant provisioning, there are differences in receiving the SAP Cloud ALM API binding credentials.

The following sections show you what to do depending on when you requested SAP Cloud ALM. For more information, see also Retrieving Service Credentials.

On or after October 16, 2023

The required service credentials have already been generated automatically as part of the provisioning of your SAP Cloud ALM tenant.

You can access your credentials in the SAP BTP cockpit or in the Landscape Management app, as described in Managing Your Service Credentials.

Between June 12, 2023 and October 16, 2023

You only need to create manually a new instance for the SAP Cloud ALM API if you want to use the Deployment scenario described here. For this, see section Create or Update an Instance in Enabling SAP Cloud ALM API.

Make sure to paste the following JSON code into the text editor as:

{

    "xs-security": {

        "xsappname": "<your-instance-name>",

        "authorities": [

                                             "$XSMASTERAPPNAME.imp-cdm-feature-display-ui",

                                             "$XSMASTERAPPNAME.imp-cdm-feature-manage-ui"

        ]

    }

}

Before June 12, 2023

If you haven't created the SAP Cloud ALM API service instance, follow the steps in Enabling SAP Cloud ALM API to get the binding credentials.

Example of the binding credential in the SAP BTP cockpit for SAP Cloud ALM subaccount:

Example for the binding credential in the SAP BTP cockpit for SAP Cloud ALM subbacount where the Cloud Foundry environment hasn't been activated yet:

Procedure

Caution:

To enable the assignment of SAP S/4HANA Cloud Public Edition transports, you have to establish a communication arrangement for your development tenants and test tenants with SAP Cloud ALM. This is important as transports exported from your development system or imported to your test system only show the correct transport status after you’ve established the communication arrangement for both your development and test tenant.

In case you provision a production tenant later, make sure to establish the communication arrangement before the first import to production. Otherwise, you loose the transport status. There is no option to resynchronize the data.

  1. Create communication system: Create a communication system using the Communication System app that represents the SAP Cloud ALM tenant you want to communicate with.

    For more information about communication systems in SAP S/4HANA Cloud context, see Communication Management

    Note:

    The following steps have to be performed for every tenant you want to establish.

    1. In the Communication Systems app, set up a new communication system by choosing New.

      Set up a communication system using any ID in the System ID field and with a reasonable name (for example the tenant name, you want to communicate with) in the System Name field.

    2. Choose Create.

    3. In the next view, add the root URL from the SAP Cloud ALM API (see step 1 of this guide) in theHost Name field and the port (443) into the Port field in the Technical Data - General section.

      The relevant entry for the host name is the following: { “endpoints”: { “Api” . https://eu10.alm.cloud.sap/api }. Enter the URL without the /api extension at the end.

    4. Add a token URL based on the UAA url from your SAP Cloud ALM API instance in the Token Endpoint field and add /oauth/token at the end of the URL.

      The token URL in the binding credential JSON file looks like that:"url": "https://tenant-name.authentication.eu10.hana.ondemand.com"

    5. To create a new outbound user, go to the Users for Outbound Communication section of the Communication Systems app and choose ➕.

    6. Choose Oauth 2.0 in the Authentication Method dropdown and enter your credentials based on client ID and secret from your SAP Cloud ALM API instance in the OAuth 2.0 Client ID and Client Secret fields.

      You can find the client ID and secret in the UAA section of the binding credential JSON and has a structure like in the following examples:"clientid": "instance-name!b123456|sapcloudalm!b456789" and "clientsecret": "asdfasdfasdfasdfasdfasdf".

    7. Choose Create.

      The entry now looks like this:

    8. Choose Save.

  2. Create a communication arrangement:

    1. Create a communication arrangement in the Communication Arrangement app based on scenario SAP_COM_0690 and use the system that was created in step 2 of this guide.

    2. Go to the Outbound Services section in the Communication Arrangement app. In this section you can find the following four outbound services.

      • SAP Cloud ALM for implementation - Deployment Management Export

      • SAP Cloud ALM for implementation - Deployment Management Import

      • SAP Cloud ALM for implementation - Deployment Management Retry

      • SAP Cloud ALM for implementation - Deployment Management Status Change

      In each of this outbound services, the same entries have to be filled out by you.

      Make sure that the Service Status is marked as Active and that the Port entry is filled out with 443.

      In the Job Execution Details section, the Job Status doesn't have to be checked as this will be scheduled automatically in the background.

    3. In the Run Every field, enter 5 minutes.

      The Package Size entry can be ignored.

    4. Choose Save.

Information About Available Outbound Services

The following list contains the outbound services that are currently available:

  • Export: This outbound scenario reacts to exported ATO collection versions

  • Import: This service notifies SAP Cloud ALM about imports that were performed by ATO

  • Retry: Retries failed communication between ATO and SAP Cloud ALM

  • Status Change: This service reacts to ATO status changes and sends these changes to SAP Cloud ALM

Note:

The collector jobs can only react to future events once they are activated. Past actions before the activation are not collected.

Reporting Incidents

If you encounter issues while using this app, open (Built-In Support) to find helpful resources and context-sensitive information, and to chat with SAP experts. You can also book a live session with the Schedule an Expert function in SAP for Me.

Create incidents for the Features app in SAP for Me, under component SV-CLM-IMP-FTR .

Parent topic:Enabling Transport Management

Related Information

SAP S/4HANA Cloud Private Edition and On-Premise Systems

SAP Cloud Transport Management Service

Tips and Troubleshooting for Your Setups