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.
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:
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:
To monitor errors in the Cloud Integration Gateway (CIG) in SAP Ariba you need at least:
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: https://wiki.scn.sap.com/wiki/display/SM/Ariba+On-Premise+Monitoring+for+CIG
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:
Import Certificate into Focused Run:
For a successful SSL handshake, please make sure the following parameter are set in the SAP Focused Run system:
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.
To set up this monitoring category you have to add the ABAP backend system to Advanced Integration Monitoring.
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.
Input Values for SAP Ariba
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.
Input Values for SAP Ariba
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.
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:
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.
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.
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.
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.
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.
In the last sub-step you have to activate the alert:
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 Transaction
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:
Integration | On-premise System | Application Log Object |
---|---|---|
Ariba Network Integration Add-on | < SAP S/4HANA 1610 | ARIBA_INTEGRATION |
Ariba Network Integration Add-on | >= SAP S/4HANA 1610 | CXML_INTEGRATION |
Cloud Integration Gateway (CIG) | Any | ARBCIG_NETWORK and ARBCIG_UTILITY. Refer to this blog for more details |