This page explains how to connect SAP Ariba to SAP Cloud ALM to enable monitoring.
Currently the following monitoring application are supported for SAP Ariba:
The following video demonstrates the setup steps to connect SAP Ariba to SAP Cloud ALM.
Please note: Starting November 15th, 2021 the steps in SAP Ariba API Portal slightly differ from the steps shown in the video. You no longer have to open a ticket with SAP Ariba Support to assign the correct API to your application. Instead you can assign the correct API yourself. Please see the documentation below for details.
We will update the video as soon as possible.
To be able to collect messages from SAP Ariba you need to be on-boarded to the SAP Ariba API portal. In this portal a client application will be created which then allows you to collect information on SAP Ariba messages.
Most customers will already have at least one person in their organization that has access to the SAP Ariba API portal.
If no-one in your company has access, or your company does not yet have an organization in the SAP Ariba API portal, please follow the FAQ How do I create a new organization in API Developer Portal? After the organization has been created your realms will be loaded automatically.
Once you have access to the SAP Ariba API portal please proceed as described here:
After the API access for the application is approved go back to the SAP Ariba API Portal and generate an OAuth secret for your application.
The following only applies to non-US customers using SAP Ariba Network or SAP Ariba Cloud Integration Gateway.
Unlike SAP Ariba Sourcing and SAP Ariba Procurement, SAP Ariba Network and SAP Ariba CIG always send their events to the Integration Monitoring event database located in the US data center (even if the service itself is hosted, e.g. in Europe).
The Integration Monitoring event database can only be accessed by a client application created in the SAP Ariba Developer Portal for its region.
To check in which region your SAP Ariba Sourcing and SAP Ariba Procurement tenants are hosted please perform the following steps:
Only if your SAP Ariba Sourcing or your SAP Ariba Procurement tenant are hosted in a non-US data center, you have to create two client applications.
Please perform the steps described in the sections above for both client applications.
The following table contains the data centers with the respective SAP Ariba API URL and SAP Ariba OAuth URL:
|Data Center||SAP Ariba API Portal URL||SAP Ariba API URL||SAP Ariba OAuth URL|
The following steps only apply to the following customers:
Those customers will not have a realm to assign to the client application for SAP Ariba Network. Instead they have to link the API Client ID (Oauth Client Id) to the AN-ID in SAP Ariba Network.
To do this:
After finishing all steps you should have the following information available for the next steps in SAP Cloud ALM:
Currently SAP Ariba Cloud Integration Gateway cannot be collected automatically from the System Landscape Information Service (SLIS). Hence if you use SAP Ariba CIG you have to create the cloud service manually in the Landscape Management Service.
The other three SAP Ariba products will be discovered automatically from SLIS. You can use one of those services to find the Root URL that you need to use for the SAP Ariba CIG service.
You have to create one end-point for each of the SAP Ariba products in your SAP Cloud ALM. The end-point creation is similar for each of the products.
After creating the endpoint in SAP Cloud ALM, you have to perform the following steps to activate the monitoring use-cases: