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.

Technical Prerequisites

The following technical prerequisites have to be met in order to monitor this scenario:

  • To collect single exceptions in the SAP Ariba Network Integration add-in, you need SAP Solution Manager 7.2 SP03 or higher.
  • To create alerts via Web Service Monitoring, you need SAP Solution Manager 7.1 SP14 or higher.
  • To monitor exceptions in SAP Ariba Network Supply Chain Collaboration, you need SAP Solution Manager 7.2 SP07 or higher.
  • Import Cloud Service SSL Certificate into SAP Solution Manager.

Import Cloud Service SSL Certificate

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

  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.

Available Monitoring Content

The following SAP Ariba scenarios are currently covered in public cloud operations with SAP Solution Manager:

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

To monitor the SAP Ariba Network scenario end-to-end, you need to monitor the on-premise SAP Ariba Network Integration add-on as well as the integration solution. The SAP Ariba Network Integration add-on writes error messages to the application log.  

SAP Ariba Network integrates with on-premise systems via different technologies. Depending on which one you use for your scenario, you have to also monitor the integration solution to ensure end-to-end monitoring coverage for the cloud scenario.

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, 7
  2. Integrating ABAP backend with the SAP Ariba Network mediated via SAP CPI: 1, 3, 5, 7
  3. Integrating ABAP backend with the SAP Ariba Network mediated via SAP PI (Web Service based): 1, 3, 6, 7
  4. Integrating ABAP backend with the SAP Ariba Network mediated via SAP PI (IDoc based): 2, 4, 6, 7

 

Please, select...

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

#

Scenario Component

Monitoring Object

Description

Monitoring Template

Since SP

 1 On premise Exceptions in Ariba Integration Add-on Errors that are written to the Application Log in the SAP Ariba Network Integration Add-on are collected and written to the central exception store in SAP Solution Manager. Ariba Network Integration (ExMan) 7.2 SP03
 2 On premise IDoc  IDocs sent and received by the on-premise system IDoc (Real-time Monitoring) 7.1 SP12
 3 On premise  Web Service  Web Services exposed on the ABAP on-premise system used by the SAP Ariba Network scenario. This template is also used to monitor the number of application log errors for the integration add-in. Web Services ABAP 7.1 SP05*
 4 On premise ABAP Proxy Messages in error status in the ABAP proxy framework

Process Integration (PI - ABAP only)

7.1 SP12
 5 Integration Exceptions in SAP CPI  Exceptions in integration flows in SAP Cloud Platform Integration  Cloud (SAP HCI) 7.1 SP12*
 6 Integration PI Messages Errors in PI message send via SAP PI.

Process Integration (PI)

7.1 SP12
 7 Cloud Exceptions in SAP Ariba Network Errors that occur in the SAP Ariba Cloud service Cloud (Ariba Network) 7.2 SP07

*) Monitoring content was extended with later support packages (see monitoring template page for details)

When you set up the exception collection and monitoring you first need to know or identify with PI services, Web Services or SAP CPI iFlows are relevant for each scenario. You can find this information here: https://help.sap.com/viewer/p/ARIBA_NETWORK_INTEGRATION_FOR_SAP_BUSINESS_SUITE → Select the configuration guide for your integration.

The following SAP Help page contains documentation that applies to integration of SAP Ariba with ERP systems. Choose the administration guide for your scenario to find information on relevant: https://help.sap.com/viewer/p/ARIBA_NETWORK_INTEGRATION_FOR_SAP_BUSINESS_SUITE

Metric Name

Description

MAI Category

Since SP

Ariba Network Channel available

Interface Channel Availability. Availability is checked via EEM script execution on the source system or target system.

Availability

7.2 SP07
Number of Exceptions in Ariba Network (last 24h)

Number of exceptions detected in Ariba Network during the last 24 hours.

 

Exceptions 7.2 SP07 

Number of Exceptions in Ariba Network

Number of exceptions detected in SAP Ariba Network.

Exception statistics is retrieved from central Exception Management in SAP Solution Manager. Data Collection is executed in delta mode. The statistics are based on single exceptions which are retrieved via the Transaction Monitoring API from SAP Ariba Network into central Exception Management in SAP Solution Manager.

Exceptions

7.2 SP07
Number of Messages in status Warning (last 24h)

Number of messages in status Warning detected in SAP Ariba Network during the last 24 hours.

Exception statistics is retrieved from central Exception Management in SAP Solution Manager. Data Collection is executed in delta mode. The statistics are based on single exceptions which are retrieved via the Transaction Monitoring API from SAP Ariba Network into central Exception Management in SAP Solution Manager.

Exceptions 7.2 SP07 
Number of Messages in status Warning

Number of messages in status Warning detected in SAP Ariba Network.

Exception statistics is retrieved from central Exception Management in SAP Solution Manager. Data Collection is executed in delta mode. The statistics are based on single exceptions which are retrieved via the Transaction Monitoring API from SAP Ariba Network into central Exception Management in SAP Solution Manager.

Exceptions 7.2 SP07 
Single exceptions in Ariba Network

Single exceptions detected in SAP Ariba Network.

Exceptions are retrieved via the Transaction Monitoring API from SAP Ariba Network into central Exception Management in SAP Solution Manager.

List of supported document types (for Buyers):

  • Purchase Orders
  • Order Confirmations
  • Ship Notices
  • Goods Receipts
  • Invoices
  • Payment Remittances
Exceptions 7.2 SP07 
Single messages in status Warning

Single messages in status Warning detected in SAP Ariba Network.

Messages are retrieved via the Transaction Monitoring API from SAP Ariba Network into central Exception Management in SAP Solution Manager.

Exceptions 7.2 SP07 

Configuration

Please, select...

Step 1: Define Cloud Service in SAP Solution Manager

To create the required cloud service in SAP Solution Manager, first request production access to the SAP Ariba Network 'Transaction Monitoring API' service, following these guidelines:

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).

You need the following information to create the SAP Ariba cloud service:

  • Application Key - Unique ID per application, generated on creation of the application, checked by the Open API Gateway.
  • Client ID - Another Unique ID per application, generated on approval of application.
  • Client Secret - Unique ID per application used to generate access tokens for applications.
  • Main URL: The root URL for production is always https://openapi.ariba.com.

Release Restriction:

Note that you need at least SAP Solution Manager 7.2 SP 07 to set up and use the cloud service for SAP Ariba.

The Cloud Services configuration is now accessible from the SAP Solution Manager Configuration (SOLMAN_SETUP) → Managed Systems Configuration → Tab 'Cloud Services'.

Create Cloud Service:

  1. Select 'Cloud Service Operations' → Create Cloud Service.
  2. For the Service Type, select: 'SAP Ariba' from the drop-down list.
  3. Define Service:
    • Tenant: Enter a name for the tenant and a description
  4. Define Root URL: Enter the <Main URL> as Root URL.
    • You can also adjust the extended service ID (the ID used as SID in LMDB) here.
  5. Confirmation: Check your input values and click 'Finish'.

Create the End-Point:

  1. Select your SAP Cloud Platform cloud service from the list and click 'Configure Cloud Service' .
  2. Configure Endpoints: Click the 'Add' button on the 'HTTP Endpoints' tab.
  3. Enter the following information:
  • Description: A meaningful description
  • OAuth URL: https://api.ariba.com/v2/oauth/token
  • Application Key: <Application Key>
  • Client ID: <Client ID>
  • Client Secret: <Client Secret>
  • If necessary add proxy information to connect to the SAP Ariba Network

Exceptions in the Integration Add-In

If you set up the monitoring for the exceptions in Exception Management and you activate the monitoring there, you will receive an alert (if set up this way an email) for every single exception in the application log.

Instead, it is advised to set up the actual monitoring and alerting for the application log entries in the Web Service monitoring within Interface and Connection Monitoring. This will collect the number of occurred errors and create one alert accordingly. You can then use Exception Management to drill down into the single exceptions.

Step 2: Configure Exception Management

For SAP Ariba Network, you might have to set up two distinct exception log stores as described below and, depending on your integration solution, to monitor the full SAP Ariba Network Supply Chain Collaboration solution. You have to set up the exception store for exceptions occurring in SAP Ariba Network Supply Chain Collaboration. Additionally, if your integration includes the SAP Ariba Network Integration add-on installed in the SAP ABAP on premise system, you need to set up one log store that collects the exceptions occurring in this add-on.

Exceptions in SAP Ariba Network 

Typically you collect exceptions directly from SAP Ariba Network. Please note that you need SAP Solution Manager 7.2 SP 07 to do this.

To access the Exception Management setup please go to transaction SOLMAN_SETUP → Application Operations → Exception Management 

  1. In the step 'Define Scope' select the tab 'Cloud Services' and your SAP Ariba cloud service. If you didn't configure the system before make sure to select 'All Cloud Services' in the view drop-down. Click on 'Configure' or click 'Next' two times. You will enter the step 'Exception Configuration'.
  2. Click 'Add / Configure Log Store'. Select 'SAP Ariba Network Transaction Monitoring API'. Select the correct end-point for the SAP Ariba Network if you have more than one.
  3. Select the fields for filtering for your log store.  The following filter fields are available:
    • 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.
    • transaction_id: Transaction ID (as this is a unique ID it wouldn't be applicable for filtering)
  4. Maintain the filter values for the fields in the Filter Definition panel under the log stores table. You can also add, remove or change filter fields and values later on in the area. You can use different operators for your filter value. You can add more than one filter field combination per log store. To add an additional filter field combination click on the button 'Add Filter' in the 'Configured Log Stores' panel.
  5. Once you are done with the Log Store setup click 'Next' to go to the alert configuration. The alert configuration is done in the 'Interface and Connection Monitoring' described in the next section.

(Optional): Exceptions in SAP Ariba Network Integration Add-On

The SAP Ariba Network Integration add-on writes single exceptions into error messages in the ABAP Application Log. These application log entries can be collected with the log store for the SAP Ariba Network Integration add-on.

The log store is set up on the SAP ABAP on-premise system on which the add-on is installed.

To access Exception Management setup, go to transaction SOLMAN_SETUP → Application Operations → Exception Management 

  1. In the 'Define Scope' step, select the 'Technical Systems' tab and your SAP ABAP system. If you did not configure the system before, make sure to select 'All Systems' in the view drop-down. Click 'Configure' or click 'Next' two times. You will enter the 'Exception Configuration' step.
  2. Click 'Add / Configure Log Store' → Standard then select 'SAP Ariba Network Integration Add-on Logs'.
  3. Select the fields for filtering for your log store. The 'SUBOBJECT' field is selected by default. While there are many filter fields available, as this log store is based on the Application Log log store, it does not necessarily make sense to use them all. Usually, just the 'SUBOBJECT' field is enough. If you want to filter on the rest, check the actual log record you are looking to catch in SLG1 and maintain the filter fields accordingly. The following filter fields are available:
    • 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
  4. Maintain the filter values for the fields in the 'Filter Definition' panel under the log stores table. You can also add, remove or change filter fields and values later on in this area. You can use different operators for your filter value. You can add more than one filter field combination per log store. To add an additional filter field combination, click the 'Add Filter' button in the 'Configured Log Stores' panel.
  5. Once you are done with the Log Store setup, click 'Next' to go to the alert configuration. The alert configuration is done in the 'Interface and Connection Monitoring' described in the next section.

Step 3: Configure Interface and Connection Monitoring

To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.

If you didn't perform the infrastructure configuration yet, please follow the Interface and Connection Monitoring Setup with SAP Solution Manager 7.2.

Configuration for Monitoring Template: Web Services ABAP

This monitoring template is used to monitor the performance and for exceptions happening in the Web Service communication between the SAP Ariba Network Integration add-on in SAP ABAP and SAP Ariba Network or SAP Cloud Platform Integration integrating SAP ERP and SAP Ariba.

For detailed setup information on how to set up this channel type, refer to the Interface and Connection Monitoring Wiki for configuration of Web Service Channels. You can use the Web Services ABAP (SOAP) or Web Services ABAP (STAD)template for the monitoring. Note: If you use the Web Services ABAP (SOAP) template you must activate the Web Service performance monitoring in the ABAP system as per SAP Note 1639329.

As additional functionality we also use this template to create alerts for error logs written by the SAP Ariba Network Integration add-on in the SAP Application Log. To monitor the SAP Application Log, the 'Number of AppLog Errors (WS)' metric should be selected additionally to the desired Web Service metrics.

Which Application Log and Web Service proxy/name you need to enter depends on the scenario in the SAP Ariba Network integration:

Scenario

Web Service proxy/name

Application Log

Polling messages from SAP Ariba Network
  • CO_ARBFND_PRX_ GPDQ _OUT (synchronous outbound)

Technical System: <SID>~ABAP 

Object: ARIBA_INTEGRATION

Sub-Object: POLLING

Receiving messages from SAP Ariba Network
  • II_ARBFND_PRX_CCPAYP_IN (asynchronous inbound)
  • II_ARBFND_PRX_CONF_IN (asynchronous inbound)
  • II_ARBFND_PRX_INVC_IN (asynchronous inbound)
  • II_ARBFND_PRX_ORDR_IN (asynchronous inbound)
  • II_ARBFND_PRX_PAYR_IN (asynchronous inbound)
  • II_ARBFND_PRX_PREM_IN (asynchronous inbound)
  • II_ARBFND_PRX_QTEM_IN (asynchronous inbound)
  • II_ARBFND_PRX_RCPT_IN (asynchronous inbound)
  • II_ARBFND_PRX_SHIP_IN (asynchronous inbound)
  • II_ARBFND_PRX_SRVE_IN (asynchronous inbound)

Technical System: <SID>~ABAP 

Object: ARIBA_INTEGRATION

Sub-Object: INBOUND

Sending messages to SAP Ariba Network
  • CO_ARBFND_PRX_OADP_OUT (synchronous outbound)
  • II_ARBFND_PRX_OADP_IN (asynchronous outbound)

Technical System: <SID>~ABAP 

Object: ARIBA_INTEGRATION

Sub-Object: OUTBOUND

The metrics for Application Log Monitoring will create alerts based on the number of errors in the SAP Application Log. If you set up Exception Management as well, you can analyze the single exceptions in Exception Management to find out more details about the errors that occurred.

Configuration for Monitoring Template: Cloud (Ariba Network)

Note: You can only set up this channel if you run SAP Solution Manager 7.2 SP 07 or higher. With this template you can monitor exceptions happening directly in SAP Ariba Network.

Navigate to the 'Define Scope' step. You can create a new scenario for the SAP Ariba monitoring or use an existing scenario. Make sure the on premise system for the SAP Ariba scenario and the Cloud Service created for SAP Ariba are part of the 'Interface and Connection Monitoring' scenario. If you use the integration via SAP CPI this cloud service should be added as well.
 

Create the Interface Channel:

  1. Select the scenario and click 'Next'.
  2. In the 'Preparation' step, perform all relevant manual activities and run all automatic activities.
  3. In the 'Configuration' step, click the 'Add' button.
    • Channel Name: Enter a meaningfull name (max. 30 characters)
    • Type: 'Cloud'
    • Monitoring Template: 'Cloud (SAP Ariba)'
    • Description: Enter a description for the channel
  4. Click 'Next'.
  5. Source Type:
    • If the source system is the on-premise system, select 'Technical System'.
    • If the source system is the SAP Ariba cloud service, select 'External Service'.
  6. Source: Select the on-premise system respectively the SAP Ariba Cloud Service from the drop-down list.
  7. Target Type:
    • If the target system is the on-premise system, select 'Technical System'.
    • If the target system is the SAP Ariba cloud service, select 'External Service'.
  8. Target: Select the on-premise system respectively the SAP Ariba Cloud Service from the drop-down list.
  9. The measuring point is selected automatically.
  10.  If more than one client are connected for the on-premise system, select the correct client for monitoring.
  11.  Click 'Next'.
  12.  Click 'Finish'.
     

Maintain the Interface:

  1. Select the interface channel you created
  2. On the 'Interfaces' tab click the 'Add' button.
  3. Provide the following information:

    • Interface Name: Enter a name for the interface.

    • Process Name: The specific business document that is tracked in an event (e.g. TRANSACTION_TRACKING_PURCHASEORDER).

    • Event Name: This is the event name that indicates the document processing stage (e.g. DOCUMENT_RECEIVE_FAILED).

    • Sender ID: The sender 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).

    • Receiver ID: The receiver of the business document. This is a unique SAP Ariba Network ID.

The filters applied here allow you to filter the exceptions collected by Exception Management further; however if the filter in Exception Management already removes an exception and it is not collected in the central exception store you will not be able to find it with a filter here.

Select Metrics:

  1. On the 'Metrics' tab, select the metrics you want to monitor.

  2. Enter the metric parameters (only for some of the metrics):

  3. Save your interface channel by clicking on the 'Save' button. 

You can maintain attributes as described in the Interface and Connection Monitoring Setup on the 'Attributes' tab.

Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click 'Next' in the main guided procedure to move to the 'Activation' step.

Maintain Thresholds and Schedule:

  1. Select the alert for the SAP Ariba Network channel (the alert is the line with the red flash icon next to it).
    • On alert level you can maintain notification and incident message creation.
    • Do not remove the 'Do not Group Individual Occurrences' flag as this flag ensures that an alert is created for each exception.
  2. Select the metrics.
    • You can adjust the thresholds on the 'Thresholds' tab.
    • Do not change the 'data collector type' or 'data collector name' on the 'Data Collection' tab as the monitor will not work anymore if this is changed.
    • Only change the collection interval if you know what to do or if advised to do this by SAP.
  3. Click 'Apply and Activate' → <Choose one option> to activate the monitoring.

Note that SAP Ariba offers, independently of SAP Solution Manager, a notification mechanism, via e-mail, for the Supply Chain Collaboration buyers. These e-mails inform about various events, as documented in the SAP Ariba Supply Chain Collaboration integration and configuration guide. They get sent, either upon event occurrence (which could potentially generate a high number of e-mails), or as a daily summary report. As a consequence, when you set up SAP Solution Manager, as described in this page, you could decide to switch off the e-mail notification, as implemented by SAP Ariba, and this for the routing or technical failures, by unchecking the Network Notification for General Notification Option (see screenshot below). However, business users generally register for other relevant network notifications to be informed about business related information such as order confirmation rejected or downtime notifications.