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.

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: https://wiki.scn.sap.com/wiki/display/SM/Ariba+On-Premise+Monitoring+for+CIG

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

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.

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

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: