SAP Ariba

SAP Ariba is SAP's cloud based marketplace for business-to-business transactions. SAP Ariba runs the Ariba Network in which buyers and suppliers can find each other and do business in one network. You can integrate SAP Ariba Network with your on premise system either via SAP Cloud Platform Integration or via SAP PI.

Integration Scenario

Please, select...

Unlike the classic point-to-point interfaces like e.g. IDocs, Web Services or RFCs, when talking about monitoring for cloud services, you always also have to consider the integration component of the scenario. For most cloud services, Advanced Integration Monitoring for the cloud service itself concentrates on monitoring exceptions happening in the cloud service. But to fully monitor a cloud service scenario it is also important to monitor the integration between the cloud service and the on-premise backend system. This integration consists of different point-to-point interfaces of different types.

The following section describes the different integration options for the cloud service. Please choose the integration option you are using and consider also setting up the monitoring for the relevant interface types that are part of the integration scenario for the cloud service.

On this page we describe the monitoring categories that are available for this specific cloud service type. For information on how to set up the monitoring categories for the other technical system and cloud service types, please refer to the setup documentation of the respective interface type.

After setting up the monitoring for the single components and interface types, you can use the scenario configuration to group all relevant messages and exceptions of the cloud integration scenario in one Advanced Integration Monitoring scenario. Information how to create scenarios can be found here


For SAP Ariba the following integration scenarios are possible:


The different scenarios contain the following exceptions and point-to-point connections:

  1. Integrating ABAP backend with the SAP Ariba Network in a direct connectivity scenario: 1, 3, 6
  2. Integrating ABAP backend with the SAP Ariba Network mediated via SAP CPI: 1, 3, 4, 6
  3. Integrating ABAP backend with the SAP Ariba Network mediated via SAP PI (Web Service based): 1, 3, 5, 6
  4. Integrating ABAP backend with the SAP Ariba Network mediated via SAP PI (IDoc based): 2, 4, 5, 6

Scenario Component Monitored Content Monitoring Category
1 Systems: ABAP on-premise system Exceptions in Ariba Integration Add-on Ariba Network Integration Add-on
2 Systems: ABAP on-premise system IDocs IDoc
3 Systems: ABAP on-premise system Web Service errors and performance

Web Service Messages (ABAP), Web Service (Performance)

4 Cloud Services: SAP Cloud Platform Integration Integration flows (iFlow) in SAP CPI

SAP Cloud Platform Integration

5 Systems: SAP PI on-premise system PI Messages

ABAP: PI Messages

Java: PI Communication Channels, PI Messages

6 Cloud Services: SAP Ariba Exceptions in SAP Ariba Network

Ariba Network Transaction

Ariba Cloud Integration Gateway

To know which IDocs, WebServices and Application Log entries are relevant for the Ariba integration scenario, please refer to the following documentation: 

SAP Ariba scenarios covered by Focused Run

The following SAP Ariba document types are currently covered for SAP Ariba:

  • SAP Ariba Supply Chain Collaboration (Buyers) currently restricted to the following document types: Purchase Orders, Order Confirmations, Ship Notices, Goods Receipts, Invoices, Payment Remittances

Technical Prerequisites

To monitor errors in the Cloud Integration Gateway (CIG) in SAP Ariba you need at least:

  • FRUN 2.0 Feature Pack 02

Please note: While Focused Run is technically able to receive exceptions from Cloud Integration Gateway, the exceptions are currently not written to the Transaction Monitoring API from SAP Ariba side. Hence they cannot be collected by SAP Focused Run. We will update this page, as soon as this problem is addressed.

To monitor exceptions from Cloud Integration Gateway for now you can monitor the Application Log messages written for CIG in the on-premise system. The relevant Application Log entries can be found here:

Configure Cloud Service

Please, select...

Public cloud service offerings are usually Software-as-a-Service (SaaS) solutions. This means that customers only have access to the service but not to the underlying infrastructure. Hence, the usual way to connect on-premise managed systems to Focused Run does not apply to cloud services.

However, to be able to monitor exceptions and performance in cloud services they need to be connected to Focused Run. This connection is created using the customer and cloud service specific root URL and an end-point definition, which allows Focused Run to receive information from the cloud service.

The first step is to import the SSL certificate into Focused Run. This is valid for all cloud services.

Import Cloud SSL certificate into STRUST

Export Certificate from Browser: 

  1. Open the cloud service URL in your web browser.
  2. Click on the padlock next to the Cloud Service URL (within the address input field).
  3. When using Firefox, click on ‘Show Connection details', ‘More Information', 'View Certificate' and select the ‘Details' tab.
  4. When using Microsoft IExplorer, click on ‘View Certificate' and select the 'Certificate Path' tab.
  5. When using Google Chrome, click on ‘Certificate' and select the 'Certificate Path' tab.
  6. In the displayed certificate hierarchy select the Certification Authority (CA) certificate you plan to trust.
  7. When using Firefox, press ‘Export…'.
  8. When using Microsoft IExplorer or Google Chrome, press ‘View Certificate' and in the displayed pop-up navigate to the ‘Details' tab, to press ‘Copy to File…'.
  9. Select an export format you would like to use and that is supported by STRUST transaction, and export the certificate.

Import Certificate into Focused Run:

  1. Now, log on to Focused Run and go to transaction STRUST.
  2. Switch to Edit.
  3. Double click on entry 'SSL client SSL Client (Anonymous)'.
  4. Import the previously exported CA certificate, by pressing – within section ‘Certificate' – the icon ‘Import Certificate'.
  5. Press ‘Add to Certificate List'.
  6. Finally ‘Save' this modification. 

For a successful SSL handshake, please make sure the following parameter are set in the SAP Focused Run system:

  • icm/HTTPS/client_sni_enabled = TRUE
  • ssl/client_sni_enabled = TRUE

Additionally you have to perform certain preparations in the cloud service to enable Focused Run to connect to the cloud service.

Preparations for SAP Ariba

Register for the open API Developer Portal

Once you have registered in the Open API Developer portal you shall register for the service 'Transaction Monitoring API', which will provide access to the error and warning events, related to the SAP Ariba document processing.

While working through the above-mentioned process, keep in mind to note down the information, like Application Key, OAuth Client ID and Client Secret, which is needed to configure the SAP Ariba cloud service access on Focused Run side.

Preparations for SAP ABAP Backend System

The exceptions for 'Ariba Network Integration' are collected from the Ariba integration add-ons installed in the ABAP backend system. So this monitoring category is only available for ABAP systems, which have the Ariba integration add-ons installed.

  • For more information on the add-on installation please refer to SAP Note 1915255 - Ariba Integration for SAP Business Suite Installation: RIN

To set up this monitoring category you have to add the ABAP backend system to Advanced Integration Monitoring.

Please, select...

After gathering all necessary information and creating the necessary connection point or users in the cloud service, you can now create the cloud service in Focused Run.

  1. Call transaction FRUN
  2. Select 'Advanced Integration Monitoring' → Cloud Service Management
  3. Click the 'Add' button
  4. Select the Cloud Service Type.
  5. The other input fields in the section 'Definition' depend on the cloud service type, see the details below
  6. In the section 'Identification' you have to enter the following:
    • Customer Network: the isolated network for which this cloud service should be visible
    • Extended Service ID: the extended SID uniquely identifies the cloud service in LMDB and can be between 3 and 8 characters long

Input Values for SAP Ariba

  • Tenant: Tenant name of your tenant
  • Open API Root URL:
  • Description: (optional)

Please, select...

The second step is to create the end-point for the cloud service. The end-point is used to actually connect to the cloud service with user and password. Most cloud services use HTTP end-points.

  1. Click on the extended service ID of the cloud service 
  2. Click the 'Add' button on the 'HTTP ENDPOINTS' tab.
  3. Enter the following information:
    • Section 'Global':
      • Description: A meaningful description
    • Section 'Authentication':
      • The information needed here depends on the cloud service type, please refer to the details below
    • Section 'Proxy':
      • If necessary add proxy information to connect to the cloud service

Input Values for SAP Ariba

  • Type: OAUTH
  • OAuth URL:
  • Application key: Unique ID per application, generated on creation of the application, checked by Open API Gateway
  • Client ID: Another Unique ID per application, generated on approval of the application
  • Client secret: Unique ID per application used to generate access tokens for applications

Advanced Integration Monitoring Setup

Please, select...

To be able to monitor interfaces of a cloud service you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system. 

  1. Open the Advanced Integration Monitoring Application by clicking on the 'Integration & Cloud Monitoring' tile in transaction FRUN
  2. Click on the pinwheel in the upper right corner of the 'Integration & Cloud Monitoring' application
  3. In the configuration panel expand the 'Cloud Services' tray and click on the pen icon in the upper right corner. This will open the 'Configuration for Cloud Services' view.
  4. If your system is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the system ID of the system. 

In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.

Select the monitoring categories in scope.

Available Monitoring Categories 

For SAP Ariba different monitoring categories are available:

  • Ariba Network Integration Add-on: Collects exceptions that happen in the integration add-on on the backend system. This category is configured for the ABAP backend system
  • Ariba Network Transaction: Collects exceptions that happen in Ariba Network in the public cloud for the Supply Chain Collaboration scenario. This category is configured for the SAP Ariba cloud service

Please, select...

After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. SAP Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own. 

Please note that the filters you set in the 'Monitoring' step filter the data which is collected from the managed system or cloud service. You can also set up filters later in the 'Alerting' step, which will filter the data already in Focused Run.

You can create more than one filter for a monitoring category.

  1. Select the view 'Monitoring'
  2. To add a new filter click the '+' button on the upper right corner of the table
  3. Select the Category for the filter. The drop down list will contain all activated categories for the system
  4. Enter a filter name
  5. Select the target client for the ABAP system / the end-point for the cloud services
Which filter fields are available depends on the selected category.

Available Filter Options 

Ariba Network Integration Add-on

Ariba Network Integration is based on the ABAP Application Log. Hence you have to select at least the Subobject. The Object is preselected in the coding to collect logs from the Ariba Integration add-in.

  • Subobject (mandatory): Choose between INBOUND, POLLING or OUTBOUND
  • External ID: External ID of the Application Log entry
  • Message ID: Message Class
  • Message Number: Message Number
  • Text: Message Text
  • Status: Error (E) or Warning (W)
  • Program: Program triggering the log entry
  • Transaction: Transaction code triggering the log entry
  • User: The user who triggered the log entry

Ariba Network Transaction

For Ariba BPM logs you have to select the alert type in a filter. You can create two filters to collect failures and warnings.

  • Alert Type (mandatory): Select FAILURE or WARNING
  • Process Name: The specific business document that is tracked in an event. (e.g. TRANSACTION_TRACKING_CONFIRMATIONDOCUMENT)
  • Receiver Id: The receiver of the business document. This is a unique SAP Ariba Network ID. An SAP Ariba Network ID is always AN followed by 11 digits (e.g. AN12345678901)
  • Sender Id: The sender of the business document. This is a unique SAP Ariba Network ID.

Please, select...

The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually. 

  1. Go the the view 'Alerting'
  2. Click on the '+' button in the upper right corner of the alerts table. A new panel will appear below the table for you to enter the alert information
  3. Select the monitoring category
  4. Select the metric name. The available metrics depend on the monitoring category.
  5. Enter a name for the alert

In the next sub-step, you have to maintain the filter. For most monitoring categories the available filter fields will be the same as for the 'Monitoring' configuration described above. 

For some metrics, you have additional filter fields or you have to maintain metric parameters. You can check the collected data in Focused Run to determine which filter values to use for alerting. Most of the fields can be found in the Collection Context of the collected data.

Please note that the filters on 'Alerting' level filter the data that is already available in Focused Run. They do not influence the data collection itself. You can only filter for data that is collected. Be aware of this if you created strict filters in the 'Monitoring' step.

  1. Enter a name for the filter
  2. Maintain the necessary filter fields

In the last sub-step you have to activate the alert:

  1. Check the check box next to 'Active'
  2. You can adjust the calculation frequency and the severity
  3. Available threshold types depend on the metric selected. If the threshold type allows it you can adjust the threshold value which triggers the alert.
  4. Select the notification variant and the outbound connector variant from the drop-down list.

For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.

Available Metrics 

For SAP Ariba the following metrics are collected:

Ariba Network Integration Add-on

  • Ariba Network Integration exceptions: Indicates that new exceptions were collected during the last data collection interval

Ariba Network Transaction

  • SAP Ariba Network Transaction exceptions: Indicates that new exceptions were collected during the last data collection interval

Additional Information

The Ariba Integration Add-On as well as the Cloud Integration Gateway Integration Add-on (CIG) write messages in the ABAP Application Log. Some of these Application Log messages are covered by the 'Ariba Network Integration Add-on' category. However the object and sub-objects that are proposed in that category might not reflect your situation. If you want to monitor Application Log messages that are not covered (yet) you can use the ABAP Application Log category, available for any on-premises ABAP system, and specify the relevant Application Log objects and sub-objects, as proposed here:

IntegrationOn-premise SystemApplication Log Object
Ariba Network Integration Add-on< SAP S/4HANA 1610ARIBA_INTEGRATION
Ariba Network Integration Add-on>= SAP S/4HANA 1610CXML_INTEGRATION
Cloud Integration Gateway (CIG)AnyARBCIG_NETWORK and ARBCIG_UTILITY.
Refer to this blog for more details