Skip to Content
Technical Articles
Author's profile photo Marc Dorais

Common issues when connecting SAP Analytics Cloud with SAP Marketing Cloud

Disclaimer

This blog is not relevant for SAP Analytics Cloud, embedded edition. You can check in the Set Up  Your Marketing Solution application to see if you have the embedded edition. For more information, see online documentation. Setup of SAP Analytics Cloud, Embedded Edition/SAP Analytics Cloud.

Overview 

Integrating SAP Marketing Cloud with SAP Analytics Cloud allows you to make full use of the analytic capabilities of SAP Analytics Cloud to explore marketing data. You can, for example, build analytics stories based on the delivered CDS views or on your own custom CDS views and use them in the Analytics and Report Gallery application. The Live Data Connection allows users to run SAP Marketing Cloud CDS query views without data replication. The analytical query is delivered as CDS content and is exposed via the analytical engine and the InA protocol via the REST services under /sap/bw/ina/ to SAP Analytics Cloud. 

Before connecting SAP Analytics Cloud with SAP Marketing Cloud, you must identify the environment where SAP Analytics Cloud is hosted. The following environments are available: 

  • SAC Neo Tenant 
  • SAP Cloud Foundry Tenant 

Once you identify the environment, you must follow the proper setup tasks for your environment. 

To ensure a successful integration, there are several aspects to check. Not seeing the analytical stories in the Analytics and Report Gallery, is one of the main symptoms of an incomplete setup. In this post, I will provide you solutions to a list of common issues encountered. 

Common Issues

Trusted Identity Provider does not match

The Provider Name or the Signing Certificate that you can find in the Outbound Communication section of the Communication Arrangement for the Scenario SAP_COM_0065 in the SAP Marketing Cloud system does not match the Trusted Identity Provider in the SAP Analytic Cloud system.

To verify the Signing Certificate, you can download it from the Communication Arrangement in the SAP Marketing Cloud system. Then, open it with a plain text editor (for example, Notepad).

If the Signing Certificate differs from what you see in the Trusted Identity Providers of SAP Analytic Cloud, then delete the Trusted Identity Provider and create a new one with the Signing Certificate that you have just downloaded from the SAP Marketing Cloud system.

For more information, see online documentation. Setting Up a Communication Arrangement (Step 6) and Setting Up the Outbound Connections from SAP Marketing Cloud to SAP Analytics Cloud.

Those links are for the Neo tenant, if your installation is for the Cloud Foundry tenant check the corresponding section under the Cloud Foundry tenant.

OAuth password must be reset

The secret password defined in the OAuth client configuration in the SAC tenant does not correspond to the secret password defined for the outbound communication user of the Communication System in the SAP Marketing Cloud system.

To ensure that both passwords match, you need to re-enter the secret password in SAC and SMC.

For more information, see online documentation. Adding a New OAuth Client (Step 2) and Setting up a Communication System (Step 6)

Those links are for the Neo tenant, if your installation is for the Cloud Foundry tenant check the corresponding section under the Cloud Foundry tenant.

OAuth Client ID is wrong

The OAuth client ID defined in the OAuth client configuration in the SAC tenant does not correspond to the OAuth 2.0 Client ID defined for the outbound communication user of the Communication System in the SAP Marketing Cloud system.

Replace the OAuth 2.0 Client ID of the Outbound Communication User of the Communication System defined in the SAP Marketing Cloud system with the OAuth Client ID value defined in the OAuth Client configuration in the SAC tenant.

For more information, see online documentation. Setting up a Communication System (Step 6) and Adding a New OAuth Client (Step 2). In case of an SAP Cloud Foundry Tenant, the OAuth Client ID is generated upon saving.

Those links are for the Neo tenant, if your installation is for the Cloud Foundry tenant check the corresponding section under the Cloud Foundry tenant.

The Username in SMC does not match the SAML user mapping

The Username in SAP Marketing Cloud must match the SAML User mapping in the SAC tenant.

Upper case issue between Identity Provider (IdP) user and SAC user

It is important that Username is defined in uppercase. If you have a Corporate Identity Provider (IdP) where the Username are defined in lower case, the Identity Authentication service (IAS) must be instructed to convert the Username to uppercase.

Apply the following step in your IAS tenant:

    1. Login as tenant administrator to the IAS tenant
    2. Go to “Applications” tile -> select your SAC application.
    3. Go to “Trust” tab
    4. Click on “Apply Function to Subject Name Identifier” section -> here choose the option “Uppercase”.

For more information, see online documentation. Convert Subject Name Identifier to Uppercase or Lowercase

OAuth2SAML Audience does not match

The OAuth 2.0 SAML Audience defined in the OAuth 2.0 Settings of the Communication System in the SAP Marketing Cloud system does not match the OAuth2SAML Audience visible in the OAuth Clients section of the SAC tenant.

The most common error is that the audience is defined with the prefix https:// in the SAC tenant but in SAP Marketing Cloud system, the prefix https:// is missing. For Cloud Foundry Tenant, the OAuth2SAML Audience must be an exact match between SAC tenant and SAP Marketing Cloud system. (including the https:// prefix)

For more information, see online documentation. Setting Up a Communication System (Step 03) and Adding a New OAuth Client (Step 01)

Tenant ID

For the SAP Cloud Foundry Tenant, the tenant ID entered in the communication arrangement for the communication scenario SAP_COM_0065 in the SAP Marketing Cloud system must be in lowercase. Even if you see the system name as “91B6F” in the SAC tenant, the right value to enter is “91b6f”.

For more information, see online documentation. Setting Up a Communication Arrangement (Step 4)

Missing Trusted Origin

You did not enter the host name of the SAP Marketing Cloud system (e.g. https://myXXXX.s4hana.ondemand.com) in the Trusted Origins section in the SAC tenant.

For more information, see online documentation. Adding SAP Marketing Cloud as a Trusted Origin with SAP Analytics Cloud

Conclusion

Those are the most encountered issues for the integration between SAP Analytics Cloud and SAP Marketing Cloud. If you are still facing an issue after having verified all proposed solutions, you can open an incident under the component CEC-MKT-ISG-ME.

More Information

You can use Set Up Your Marketing Solution to help you on setting up Analytics scenarios. See online documentation. SAP Marketing Cloud online documentation.

For more information, see online documentation. Integration with SAP Analytics Cloud (1SO)

 

Assigned tags

      3 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Tobias Schneider
      Tobias Schneider

      Nice Blog with very valuable information, thanks Marc! 🙂

      Author's profile photo Martin Kreitlein
      Martin Kreitlein

      Hello Marc,

      great Blog! ... one thing came into my mind and I'm not sure if this might also be an issue?

      Here you can see that 6 "terms" need to be used as OAuth scope:

      https://help.sap.com/viewer/0f9408e4921e4ba3bb4a7a1f75f837a7/2108.500/en-US/dec7b565c3eb4f058f41cfffd44bca35.html

      In contrast, the generated services in the Marketing Cloud are 7:

      Services

      Why is SAP_BW_INA_EXECUTEBICS_HTTP not in the list? Why is this one not relevant?

      Best regards, Martin

       

      Services

      Author's profile photo Marc Dorais
      Marc Dorais
      Blog Post Author

      Hello Martin,

      SAP Analytic Cloud doesn't make any call to those /sap/bw/ina API which require the OAuth Scope SAP_BW_INA_EXECUTEBICS_HTTP, this is why this OAuth scope is not listed in the documentation.

      Best regards,
      Marc