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 through SAP Cloud Platform Integration or SAP PI.

Configure Cloud Service

Please, select...

To collect exceptions and/or statistical data, data collectors are connecting from Focused Run to the Cloud Service provider. To allow this outgoing connection from Focused Run, the SSL Certificate of the Cloud Service provider has to be imported in Trust Manager (STRUST).

Import Cloud Service SSL Certificate

  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.
  10. Now, log on to SAP Solution Manager and go to transaction STRUST.
  11. Switch to Edit.
  12. Double click on entry 'SSL client SSL Client (Anonymous)'.
  13. Import the previously exported CA certificate, by pressing – within section ‘Certificate' – the icon ‘Import Certificate'.
  14. Press ‘Add to Certificate List'.
  15. Finally ‘Save' this modification.

Open API Developer Portal

Refer to the following help documentation for more information on the prerequisite steps to enable the Transaction Monitoring APIs:
https://help.sap.com/viewer/6283732683584b1baa62d0cdf51c4188/cloud/en-US/904d533f8a624d06b4ff078dfec76abd.html
Also, refer to the following pointer to understand how to register your organization to use the developer portal and how to request production access for this API:
https://support.ariba.com/Connect/Product_Info?locale=en&sid=0.056731943497390636 / navigate to 'API Reference' / 'SAP Ariba developer portal'

While working through the above-mentioned process, keep in mind to write down the information such as Application Key, oAuth Client ID and Client Secret, which is needed to later on configure the SAP Ariba cloud service access, within SAP Solution Manager (as described here below).

Please, select...

  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:
    1. Customer Network: the isolated network for which this cloud service should be visible
    2. Extended Service ID: the extended SID uniquely identifies the cloud service in LMDB and can be between 3 and 8 characters long

Cloud Service Creation Input Fields

Tenant: Tenant name of your tenant

Open API Root URL: https://openapi.ariba.com

Description (optional)

Please, select...

  1. Click on the extended service ID of the cloud service 
  2. Click the 'Add' button within the endpoint table.
  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

End-point Creation Input Fields

Authentication Type: OAUTH

OAuth URL: https://api.ariba.com/v2/oauth/token

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

Set Up Integration & Cloud Monitoring

The setup of integration monitoring itself is performed within the Integration & Cloud Monitoring application. To access the configuration UI, click the gear wheel icon in the upper right corner of the Integration & Cloud Monitoring application. Depending on the cloud service, the integration solution and the on-premise system you have, different monitoring objects in the different components of the integration scenario are relevant. 

Ariba

The following integration scenarios are possible (and which monitoring objects they have):

  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

For the SAP Ariba Network scenario the following monitoring content is relevant (depending on your integration solution):

Scenario Component Monitored Content Monitoring Category Recommended Filters
1 Systems: ABAP on-premise system Exceptions in Ariba Integration Add-on Ariba Network Integration
  • SUBOBJECT: Choose between INBOUND, POLLING or OUTBOUND
  • EXTNUMBER: External ID of the Application Log entry
  • MSGID: Message Class (e.g. E (Error))
  • MSGNO: Message Number
  • MSGTXT: Message Text
  • PROGRAM: Program triggering the log entry
  • TCODE: Transaction code triggering the log entry
  • USER: The user who triggered the log entry
2 Systems: ABAP on-premise system IDocs sent and received from Ariba (via SAP PI) IDoc
  • Direction: Direction of the message flow from the perspective of the monitored system.

  • Sender/Receiver Port: Receiver Port or Sender Port
  • Partner Number of sender/receiver: Receiver Partner Number or Sender Partner Number
  • Partner Type of sender/receiver: Receiver Partner Type or Sender Partner Type
  • Partner Function of sender/receiver: Receiver Partner Function or Sender Partner Function
  • Message Type: Message type, e.g. ORDERS
  • Basic Type: IDoc type, e.g. ORDERS05
  • Message Code: Message variant of the IDoc
  • Message Function: Message function of the IDoc
3 Systems: ABAP on-premise system Web Services consumed and exposed by the SAP Ariba scenario

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

For an explanation of the available filter parameters for this monitoring category please refer to the section Web Services

When you set up the exception collection and monitoring you first need to know or identify which Web Services are relevant for your scenario. You can find this information here:

Ariba Network Integration for SAP Business Suite → Select the guide for your integration scenario.

4 Cloud Services: SAP Cloud Platform Integration Exceptions in SAP CPI 

SAP Cloud Platform Integration

For an explanation of the available filter parameters for this monitoring category please refer to the section SAP Cloud Platform Integration

When you set up the exception collection and monitoring you first need to know or identify which SAP CPI iFlows are relevant for your scenario. You can find this information here:

Ariba Network Integration for SAP Business Suite → Select the guide for your integration scenario.

5 Systems: SAP PI on-premise system PI Messages

ABAP: PI Messages

Java: PI Communication Channels, PI Messages

For an explanation of the available filter parameters for this monitoring category please refer to the section SAP PI

When you set up the exception collection and monitoring you first need to know or identify with PI messages are relevant for your scenario. You can find this information here:

Ariba Network Integration for SAP Business Suite → Select the guide for your integration scenario.

6 Cloud Services: SAP Ariba Exceptions in SAP Ariba Network Ariba BPM logs
  • Alert Type: 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...

To be able to reuse the backend system in a scenario you first have to add it to Interface & Cloud Monitoring and define monitoring categories for the backend system. 

In the configuration panel expand the 'Systems' tray and click on the pen icon in the upper right corner. This will open the 'Integration and Cloud Monitoring - Systems' view. 

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. 

Select Monitoring Category

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. Any monitoring category, for which a predefined filter value exist, is preselected. You can add and remove monitoring categories by moving them from the 'Available Categories For Configuration' to 'Selected Categories For Configuration' and vice versa. 

Maintain Filters

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. Focused Run can handle this high amount of monitoring data. Therefore you can keep any predefined filter, which usually leads to collect all values without restriction. Or you can set up filters of your own. You can create more than one filter for a monitoring category. 

Maintain Alerts

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. You can reuse filters that you already created in the previous step and combine filters in one alert. 

Please, select...

To be able to reuse the cloud service in a scenario you first have to add it to Interface & Cloud Monitoring and define monitoring categories for the cloud service. 

In the configuration panel expand the 'Cloud Services' tray and click on the pen icon in the upper right corner. This will open the 'Integration and Cloud Monitoring - Cloud' view. 

If your cloud service is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the system ID. 

Select Monitoring Category

In the next step, you see all monitoring categories which are available for the cloud service. Any monitoring category, for which a predefined filter value exist, is preselected. You can add and remove monitoring categories by moving them from the 'Available Categories For Configuration' to 'Selected Categories For Configuration' and vice versa. 

Maintain Filters

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. Focused Run can handle this high amount of monitoring data. Therefore you can keep any predefined filter, which usually leads to collect all values without restriction. Or you can set up filters of your own. You can create more than one filter for a monitoring category.

Maintain Alerts

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. You can reuse filters that you already created in the previous step and combine filters in one alert. 

Please, select...

Since Focused Run collects the monitoring content on the technical component level, the landscape topology is not created automatically. To be able to see the landscape topology, you have to create a scenario and add connections between the scenario components. 

To create a scenario, expand the 'Scenarios' tray in the configuration panel and click the pen icon. This will open the 'Scenario Overview' screen.

Click 'Add' to add a scenario. 

At first, you have to select the components that belong to your scenario. The components are called 'Nodes'. You can only select components (systems or cloud services) for which you already set up filters for Integration & Cloud Monitoring. You can create lines between the nodes and assign filters to these lines.