Overview

The above configuration enables access to SAP Marketing Cloud APIs and provides the ability to configure Kyma functions and microservices to be triggered with SAP Marketing Cloud events.

This is achieved thanks to SAP S/4HANA Cloud Extensibility which is a generic way of extending any S/4 system using both Cloud Foundry and SAP BTP, Kyma runtime.

Once the configuration is done, the runtime flow will trigger functions and microservices in SAP BTP, Kyma runtime with SAP Marketing Cloud events. It will also be possible to call SAP Marketing Cloud APIs using the provided credentials.

Prerequisites

Register the S/4 system (SAP Marketing Cloud)

• Copy the generated token.

• Create a new Extension in SAP Marketing Cloud under Maintain SAP Cloud Platform Extensions and provide the copied token.

• In SAP BTP, add entitlements for SAP S/4HANA Cloud Extensibility to the subaccount in which SAP BTP, Kyma runtime is enabled.

• • Choose Add Service Plans.
  • Select SAP S/4HANA Cloud Extensibility.
  • Select the registered S/4 system from the drop-down menu.
  • Select both messaging and api-access plans.
  • Save the changes

This will make the registered system accessible in Kyma runtime’s Service Catalog as you will see in the next steps.

Enable calling SAP Marketing Cloud APIs

TIP: For details on setting up api-access for SAP S/4HANA Cloud APIs in the Kyma runtime, see the official documentation on SAP Help Portal.

This section describes how to do the necessary setup in SAP BTP, Kyma runtime to be able to make API calls to SAP Marketing Cloud.

• In SAP BTP, Kyma runtime, access SAP S/4HANA Cloud Extensibility in Service Catalog.

• Create a new instance with the api-access plan.

In the background, this will:

• • Set up all the necessary communication arrangements in SAP Marketing Cloud.
  • Create the necessary system users to make API calls.
  • Set up any other configuration required to make API calls.

NOTE: scenarioId will depend on the API calls that will be made to SAP Marketing Cloud.

• Bind the created instance to a function or a microservice in Kyma.

The connection configuration will be available as environment variables that can be used by microservices or functions.

See a sample function that uses the credentials injected by the service binding:

/**
 * Add this to dependencies
{
  "name": "call-mktng-api",
  "version": "1.0.0",
  "dependencies": {
      "axios": "latest"
  }
}
 */
const axios = require("axios");
const baseURI = `${process.env['MKTNG_URL']}/sap/opu/odata/SAP/API_MKT_CAMPAIGN_SRV;v=2`
console.log(`baseURI is-- ${baseURI}`);

module.exports = {
    main: async function (event, context) {
        try {
            const response = await axios({
                method: 'get',
                url: `${baseURI}/Campaigns?$top=2`,
                auth: {
                    username: process.env['MKTNG_User'],
                    password: process.env['MKTNG_Password']
                  }
            });
            console.log(response.data.d.results);
            return response.data.d.results
        } catch (error) {
            console.log(error);
            event.extensions.response.status(500).send("Error");
        }
    }
}

Such a function can either be called internally from other functions or exposed externally via Kyma API Rules and then invoked via the URL

• The webhook url is the URL of the API rule created in Kyma runtime to receive events.
• Provide the client id and client secret for the OAuth client client created in Kyma runtime.
• Provide the Token URL. It is of the form https://oauth2.{kyma cluster domain}/oauth2/token

{"type":"sap.s4.beh.marketingpermission.v1.MarketingPermission.Changed.v1","specversion":"1.0","source":"/default/sap.s4.beh/000000000730096987","id":"+hY+VeskHtuDiNMBjQ0Tgg==","time":"2020-10-12T04:51:30Z","datacontenttype":"application/json","data":{"MarketingPermissionUUID":"fa163e0b-249b-1ee9-b48b-5ab2bab3c4b8","PermissionGranted":"Y"}}