お問い合わせ

Setup for SAP Ariba Procurement

This page explains how to connect SAP Ariba Procurement to SAP Cloud ALM to enable monitoring.

Currently, the following monitoring application is supported for SAP Ariba Procurement:

Setup Steps in SAP Ariba

Identify SAP Ariba Procurement Region

To be able to collect messages from SAP Ariba you need to be on-boarded to the SAP Ariba Developer Portal. In this portal, a client application will be created which then allows you to collect information on SAP Ariba messages.

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:

  1. Log on to SAP Cloud ALM
  2. Open Administration > Landscape Management
  3. Find your SAP Ariba Sourcing or Procurement cloud service
  4. Click on the service name
  5. Go to the tab "Properties"
  6. Find the value for "Data Center Location"

Access SAP Ariba Developer Portal

Most customers will already have at least one person in their organization that has access to the SAP Ariba Developer Portal. 

If no one in your company has access, or your company does not yet have an organization in the SAP Ariba Developer 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.

Create Client Application in SAP Ariba Developer Portal

Once you have access to the SAP Ariba Developer Portal please proceed as described here:

  1. Log on to the SAP Ariba Developer Portal (you find the correct URL for your data center in the table of section "Important URLs")
  2. In the navigation pane on the left side navigate to 'Manage'
  3. Click the "+" button on top of the application list
  4. Enter an application name and a description
  5. Click the "Submit" button
  6. Click on "Actions" > "Request API Access"
  7. Select the API Integration Event Monitoring Query API for Procurement this API will be used for all SAP Ariba applications.
  8. Check the box in front of "Procurement"
    1. Select all realms that you want to assign from the respective drop-down box. 
    2. You can use the same application for multiple realms
      • The realm is part of the URL you use to access SAP Ariba:
        • SAP Ariba Procurement Example: https://s1.ariba.com/Buyer/Main/ad/loginPage/...&realm=mycompany
      • Please also check the entry for the Ariba tenant in Cloud ALM Landscape Management. The realm for SAP Ariba Procurement is also the name of the service in LMS.
      • For security reasons, you should consider creating separate applications for your test and your productive realms, or one dedicated application for each productive realm
  9. Click the "Submit" button.
  10. Ariba will approve the API access request for your client application within 24h.
  11. Continue with the steps under "Create OAuth Secret for Client Application" after the API access request is approved.

Create OAuth Secret for Client Application

After the API access for the application is approved go back to the SAP Ariba Developer Portal and generate an OAuth secret for your application.

  1. Log on to the SAP Ariba Developer Portal with a user that has the Organization Admin role
  2. Click "Manage" in the left-hand menu 
  3. Find your application for Integration Monitoring under "My Applications" and select it
  4. The application should now only have the step "Your admin needs to generate the OAuth Secret for your application" open
  5. Click on "Actions" > "Generate OAuth Secret". Please note that generating a new OAuth secret invalidates any old OAuth secrets!
  6. Click Submit
  7. Download the file in the next step. It contains the Application Key, the OAuth Client Id, and the OAuth Secret.
  8. Find your SAP Ariba API URL and the SAP Ariba OAuth URL in the table in section "Important URLs" and save them for later use.

Important URLs

The following table contains the data centers with the respective SAP Ariba API URL and SAP Ariba OAuth URL:

Data CenterSAP Ariba Developer Portal URLSAP Ariba API URLSAP Ariba OAuth URL
US PRODhttps://developer.ariba.com/api/https://openapi.ariba.com/https://api.ariba.com/
EU PRODhttps://eu.developer.ariba.com/api/https://eu.openapi.ariba.com/https://api-eu.ariba.com/
CN PRODhttps://developer.sapariba.cn/api/https://openapi.sapariba.cn/https://api.sapariba.cn/
UAE PRODhttps://mn1.developer.ariba.com/api/https://mn1.openapi.ariba.com/https://api.mn1.ariba.com/
KSA PRODhttps://mn2.developer.ariba.com/api/https://mn2.openapi.ariba.com/https://api.mn2.ariba.com/
AU PRODhttps://developer.au.cloud.ariba.com/api/https://openapi.au.cloud.ariba.com/https://api.au.cloud.ariba.com/
JP PRODhttps://developer.jp.cloud.ariba.com/api/https://openapi.jp.cloud.ariba.com/https://api.jp.cloud.ariba.com/

After finishing all steps you should have the following information available for the next steps in SAP Cloud ALM:

  • SAP Ariba API URL
  • SAP Ariba OAuth URL
  • OAuth client ID
  • OAuth secret
  • Application key

Create HTTP Endpoint

You have to create an endpoint from SAP Cloud ALM to your SAP Ariba Procurement tenant to enable the data collection.

  1. Open the Landscape Management application from the launchpad
  2. Select your SAP Ariba Procurement service
  3. Click on the service name or press the ">" button at the end of the line
  4. On the tab "Endpoints" press the "Add" button to create a new endpoint
  5. Enter a description
  6. Choose the use-case "Integration Monitoring"
  7. Root URL: Replace the automatically filled value with the SAP Ariba API URL 
  8. Choose OAuth authentication and enter the OAuth credentials retrieved from the SAP Ariba Developer Portal:
    • Client ID: OAuth client ID
    • Client Secret: OAuth secret
    • Token Service URL: Extend your SAP Ariba OAuth URL with /v2/oauth/token
    • API Key: Enter the Application key

Next Steps

After creating the endpoint in SAP Cloud ALM, you have to perform the following steps to activate the monitoring use-cases: