×

Welcome to Knowledge Base!

KB at your finger tips

This is one stop global knowledge base where you can learn about all the products, solutions and support features.

Categories
All
ERP-SAP
Integration & Exception Monitoring

Integration & Exception Monitoring

The purpose of Integration & Exception Monitoring is to provide transparency for the data exchange processes. It supports the monitoring for peer-to-peer interfaces as well as interfaces using orchestration platforms and provides a unified user experience for all interface types using a common look-and-feel and handling pattern.

Integration & Exception Monitoring closes the gap between IT and Business. The correlation of integration artifacts provides end-to-end visibility in interface calls and message flows cross all involved cloud services and systems.

Users of Integration & Exception Monitoring can analyze the actual processing of interface calls and message flows including possible technical or business-driven root causes.

Integration & Exception Monitoring provides the following functionalities:

  • Message Monitoring
  • Message Search (Tracking)
  • Alerting on failed messages or exceptions

Features

  • Monitoring
    Monitoring provides a detailed status overview per business system (not available in beta) and/or cloud components on the incoming/outgoing messages for different interfaces. Components can be organized in scenarios to describe message flow paths between them. Via drill down to single messages, customers can check individual issues and message details.
  • Alerting
    Based on the collected data, alerts for certain error situations can be defined, e.g. messages in status ERROR on a specific component or in a specific scenario. Generated alerts are collected into the Alert Inbox. To analyze the alert, the user can drill down in the alert details to get information on the related message details. In the Alert Inbox, it is possible to perform actions like assign a processor, add comments, postpone, or confirm an alert.
  • Tracking
    Tracking allows users to search and track single messages based on specific (business) context attributes like the order number, employee id, or similar context attributes. As a prerequisite (business) context information must be exposed by the relevant component and send together with the message's log fragments to SAP Cloud ALM. Examples are e.g. custom header attributes in SAP Cloud Platform Integration or a single message-id. The search is executed cross-component and cross-category.

Supported Products

  • SAP NetWeaver Application Server for ABAP (higher than 7.40)
  • SAP Ariba
  • SAP Batch Release Hub for Life Sciences
  • SAP BTP, ABAP environment
  • SAP BTP, Neo environment
  • *New* SAP Business ByDesign
  • SAP Business Suite
  • SAP Concur
  • SAP Field Service Management
  • SAP Fieldglass
  • SAP Integrated Business Planning for Supply Chain
  • SAP Integration Suite (Cloud Integration)
  • Integration Hub for Life Sciences

  • SAP Intelligent Asset Management
  • SAP Marketing Cloud
  • SAP Master Data Integration
  • SAP Mobile Services
  • *New* SAP Omnichannel Promotion Pricing
  • SAP Order Management foundation
  • SAP S/4HANA
  • SAP S/4HANA private cloud edition
  • SAP S/4HANA Cloud
  • SAP Sales & Service Cloud
  • SAP SuccessFactors
  • SAP SuccessFactors Employee Central Payroll

For setup details please follow the links provided on page Integration & Exception Monitoring - Setup & Configuration.

SAP Integration Suite (Cloud Integration)

SAP Integration Suite (Cloud Integration)

Available Monitoring Content

The following monitoring content is available for SAP Integration Suite (Cloud Integration):

Category Type Description
SAP Integration Suite Messages Messages Monitors status and performance of single messages send in SAP Integration Suite (Cloud Integration)
Integration Artifact Deployments Exceptions Monitors for exceptions in IFlows that render them not operational, like e.g. mapping errors

Prerequisites

Before starting the setup in SAP Integration Suite (Cloud Integration), you have to gather information on your company's SAP Cloud Integration tenant.

Depending on your findings, the setup will have to be performed differently.

The following video demonstrates how to find the necessary setup information for SAP Integration Suite (Cloud Integration).

A detailed description of all setup steps is provided in the sections below the video.

Collect Setup Information

  • The video explains how to check your SAP Integration Suite (Cloud Integration) platform and the identity provider to choose the correct follow-up video

Find your Operations Platform

Identify whether your SAP Integration Suite (Cloud Integration) tenant runs on Neo or on Cloud Foundry. To do so please check the URL of your tenant:

  • URL of a Neo tenant looks like: https://<tenant Id>-tmn. hci .<landscape>.hana.ondemand.com/
  • URL of a Cloud Foundry tenant looks like: https://<tenant Id>.<system id, e.g. it-cpi001>. cfapps .<landscape>.hana.ondemand.com/

Find your ID Provider

Check if your tenant uses the SAP ID service or a custom Identity Provider (IdP).

  • Go to the SAP BTP Cockpit → Access the subaccount used for SAP Cloud Integration → Security → Trust Configuration
  • Check if a custom IdP is used. If there is only the "Default Identity Provider" you are using the SAP ID Service.

Connect SAP Integration Suite to SAP Cloud ALM

Please choose the portal page for the connection of SAP Integration Suite (Cloud Integration) to SAP Cloud ALM depending on the operations platform your tenant runs on.

  • SAP Integration Suite (Cloud Integration) on Cloud Foundry
  • SAP Integration Suite (Cloud Integration) on Neo

Monitoring Setup

To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.

Below you find category-specific information for the monitoring categories available for SAP Integration Suite (Cloud Integration).

Please note:

  • If an input help is available for the filter parameters, this input help is filled based on the messages and exceptions collected in SAP Cloud ALM so far.
  • If no filter is set up for the data collection, all messages or exceptions will be collected for the category.

Available Events
  • Erroneous CPI Message Detected(Single): The event is created for each failed message in SAP CPI.
  • Erroneous CPI Messages Detected(Grouped): The event is created if one or more messages in SAP CPI failed since the last data collection.

Available Filters

Filters for Data Collection Filters for Events
  • Status
  • Status Group
  • Application Message Type
  • Integration Artifact Name
  • Integration Flow Name
  • Package Id
  • Package Name
  • Receiver
  • Sender
  • Status
  • Status Group
  • Status Text

Available Events
  • Erroneous Integration Artifact: The event is created for an artifact deployment in an error state
  • Erroneous Integration Artifact Stateful Alert Notification: The event is created for an artifact deployment alert notification

Available Filters

Filters for Data Collection Filters for Events
Coming soon.
  • Artifact Name
  • Artifact ID
  • Status
Read article
SAP Sales & Service Cloud

SAP Sales & Service Cloud

This portal page describes the monitoring setup for SAP Sales Cloud and SAP Services Cloud tenants.

For these tenants we can monitor messages which are sent in the context of the functionality formerly known as SAP Cloud for Customer.

Available Monitoring Content

The following monitoring content is available for SAP Sales & Service Cloud:

Category Type Description
SAP C4C Messages Messages Monitors messages sent from and to SAP Sales & Services Cloud

Connect SAP Sales & Services Cloud

To perform the necessary setup steps in the SAP Sales & Services Cloud, please refer to:

  • Setup SAP Sales & Services Cloud

Setup Integration & Exception Monitoring

To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.

Below you find category-specific information for the monitoring categories available for SAP Sales & Service Cloud.

Please note:

  • If an input help is available for the filter parameters, this input help is filled based on the messages and exceptions collected in SAP Cloud ALM so far.
  • If no filter is set up for the data collection, all messages or exceptions will be collected for the category.

Available Events
  • Erroneous C4C Message Detected(Single): The event is created for each failed message in the managed service.
  • Erroneous C4C Messages Detected(Grouped): The event is created if one or more messages in the managed service failed since the last data collection.

Available Filters

Filters for Data Collection Filters for Events
  • Status
  • Status Group

Which filter values make sense for SAP Sales & Service Cloud messages depends on the message direction.

INCOMING Messages

  • Message Direction: INCOMING
  • Sender Party
  • Inbound Service Interface Name
  • Creation UserID
  • Execution UserID
  • Status
  • Status Text
  • Status Group

OUTGOING Messages

  • Message Direction: OUTGOING
  • Receiver Party
  • Outbound Service Interface Name
  • Creation UserID
  • Execution UserID
  • Status
  • Status Text
  • Status Group
Read article
SAP S/4HANA Cloud

SAP S/4HANA Cloud

Available Monitoring Content

The following monitoring content is available for SAP S/4HANA Cloud.

Category Type Description
AIF Messages Messages Monitors messages sent in the SAP Application Interface Framework
Concur Objects Messages Monitors messages sent for the integration with Concur
SAP S/4HANA Cloud Asset Central Foundation Integration Exceptions Collects exceptions happening during the integration with  SAP Intelligent Asset Management
SAP S/4HANA Cloud Data Replication Exceptions Collected exceptions happening in the Data Replication Framework (DFR)
ABAP Gateway Errors Exceptions Exceptions in the ABAP Gateway
Extensibility Transport Management Exceptions Exceptions in Extensibility Transport Management

Connect SAP S/4HANA Cloud

To perform the necessary setup steps in the SAP S/4HANA Cloud, please refer to:

  • Setup SAP S/4HANA Cloud

Setup Integration & Exception Monitoring

To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.

Below you find category-specific information for the monitoring categories available for SAP S/4HANA Cloud.

Please note:

  • If an input help is available for the filter parameters, this input help is filled based on the messages and exceptions collected in SAP Cloud ALM so far.
  • If no filter is set up for the data collection, all messages or exceptions will be collected for the category.

Available Events
  • Erroneous Message(AIF) Detected(Single): The event is created for each failed message.
  • Erroneous Messages(AIF) Detected(Grouped): The event is created if one or more messages failed since the last data collection.

Available Filters

AIF Sub-category Filters for Data Collection Filters for Events
All sub-categories
  • Status
  • Status Group
  • Direction
  • Namespace
  • Interface Name
  • Version
  • Status
  • Status Group
  • Status Text
bgRFC(queue)
  • Queue Name
  • RFC Destination
bgRFC(trans)
  • RFC Destination
  • Transaction Code
  • Program
  • User
IDOC
  • Sender port
  • Receiver port
  • Message type
Odata Client Proxy no additional filters
XI-runtime
  • Sender namespace
  • Sender interface
  • Sender party
  • Sender component
  • Receiver namespace
  • Receiver interface
  • Receiver party
  • Receiver component
qRFC
  • Queue Name
  • RFC Destination
tRFC
  • RFC Destination
  • Function Module
  • User
WS-runtime
  • Adapter Type
  • Sender Party
  • Sender Interface Name
  • Receiver Party
  • Receiver Interface Name
XML no additional filters
Sync Log no additional filters

Available Events
  • Erroneous Concur Object Detected(Single): The event is created for each failed message.
  • Erroneous Concur Objects Detected(Grouped): The event is created if one or more messages failed since the last data collection.

Available Filters

Filters for Data Collection Filters for Events
  • Status
  • Status Group
  • Concur Company ID
  • Connection Name
  • Direction
  • Object Type
  • SAP Logical System ID
  • SAP System Type
  • Status
  • Status Group

Available Events
  • Erroneous SAP S/4HANA Cloud Asset Central Foundation Integration: The event is created for exceptions in SAP S/4HANA Cloud Asset Central Foundation Integration.

Available Filters

Filters for Data Collection Filters for Events (planned)

Predefined (not changeable)

  • Object: /SYCLO/
  • Subobject: /SYCLO/INB_TRANS
  • External ID
  • Message ID
  • Message Number
  • Text
  • Program
  • Transaction
  • User

Available Events
  • Erroneous SAP S/4HANA Cloud Data Replication: The event is created for exceptions in SAP S/4HANA Cloud Data Replication.

Available Filters

Filters for Data Collection Filters for Events (planned)

Predefined (not changeable)

  • Object: DRF_OUTBOUND
  • Subobject: ADHOC, CHANGES, DIRECTLY, INIT, MANUAL, ONLINE
  • Subobject
  • External ID
  • Message ID
  • Message Number
  • Text
  • Program
  • Transaction
  • User

Available Events
  • Erroneous ABAP Gateway Errors: The event is created for ABAP gateway exceptions.

Available Filters

Filters for Data Collection Filters for Events (planned)

Coming soon.

  • Service Name
  • User
  • Message
  • Location
  • Message Id

Available Events
  • Erroneous Extensibility Transport Management: The event is created for exceptions in Extensibility Transport Management.

Available Filters

Filters for Data Collection Filters for Events (planned)

Predefined (not changeable)

  • Object: ATO
  • Subobject: EXPORT, FORWARD, IMPORT
  • External ID
  • Message ID
  • Message Number
  • Text
  • Program
  • Transaction
  • User
Read article
SAP SuccessFactors

SAP SuccessFactors

Available Monitoring Content

Category Type Data Collection Description
SAP SuccessFactors Messages Messages PUSH

Messages in SAP SuccessFactors for the scenarios:

  • Bank master Integration With S/4HANA Cloud
  • Company Code replication with S/4HANA Cloud
  • Workforce replication with MDI
  • Cost Center Replication from MDI

Please note: To collect messages in SAP SuccessFactors the supported scenarios have to be configured in SAP SuccessFactors as described here .

Integration Center Exceptions PULL Collects exceptions for integrations in Integration Center from the Execution Management
Scheduled Jobs Exceptions PULL Collects job exceptions for jobs within Integration Center from the Execution Management
Middleware Integrations Exceptions PULL Collects exceptions for integrations via OData API from the Execution Management

Connect SAP SuccessFactors

To perform the necessary setup steps in the SAP SuccessFactors, please refer to:

  • Setup SAP SuccessFactors

Please note: You only need to set up the PUSH data collection for SAP SuccessFactors if you use one of the integrations for which messages can be collected. You find the scenarios for which we can collect messages in the section above. If you don't use these scenarios, you only need to set up the PULL data collection for exceptions.

Setup Integration & Exception Monitoring

To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.

Below you find category-specific information for the monitoring categories available for SAP SuccessFactors.

Please note:

  • If an input help is available for the filter parameters, this input help is filled based on the messages and exceptions collected in SAP Cloud ALM so far.
  • If no filter is set up for the data collection, all messages or exceptions will be collected for the category.

Available Events
  • Erroneous Message (SuccessFactor) Detected(Single): The event is created for each failed message in the managed service.
  • Erroneous Message (SuccessFactor) Detected(Grouped): The event is created if one or more messages in the managed service failed since the last data collection.

Available Filters

Filters for Data Collection Filters for Events
  • Status
  • Status Group
  • Destination Entity
  • Direction
  • Integration Name
  • Integration Type
  • Source Entity
  • Status
  • Status Group

Available Events
  • Erroneous Integration Center: The event is created for exceptions in Integration Center.

Available Filters

Filters for Data Collection Filters for Events (planned)

Predefined filter: not changeable

  • Process Type: SIMPLE_INTEGRATION
  • Event Description
  • Event Name
  • Event Type
  • Module Name
  • Process Name
  • User ID

Available Events
  • Erroneous Scheduled Job: The event is created for exceptions in a job scheduled in SAP SuccessFactors.

Available Filters

Filters for Data Collection Filters for Events (planned)

Predefined filter: not changeable

  • Process Type: SCHEDULED_JOB
  • Event Description
  • Event Name
  • Event Type
  • Module Name
  • Process Name
  • User ID

Available Events
  • Erroneous Middleware Integration: The event is created for exceptions in middleware integrations in SAP SuccessFactors.

Available Filters

Filters for Data Collection Filters for Events (planned)

Predefined filter: not changeable

  • Process Type: INTEGRATION, HCI_INTEGRATION, PI_INTEGRATION
  • Event Description
  • Event Name
  • Event Type
  • Module Name
  • Process Name
  • User ID
Read article
SAP BTP, Neo environment

SAP BTP, Neo environment

Available Monitoring Content

Category Type Description
Java Application Logs Exceptions Collects exceptions in the Java Logs for custom Java applications deployed on the subaccount in SAP BTP

Connect SAP BTP, Neo environment

To perform the necessary setup steps to connect SAP BTP Neo environment to SAP Cloud ALM, please refer to:

  • Setup SAP BTP, Neo environment

Setup Integration & Exception Monitoring

To learn how to configure the monitoring, follow the documentation on the page Integration & Exception Monitoring - Setup & Configuration.

Below you find category-specific information for the monitoring categories available for SAP BTP, Neo environment.

Please note:

  • If an input help is available for the filter parameters, this input help is filled based on the messages and exceptions collected in SAP Cloud ALM so far.
  • If no filter is set up for the data collection, all messages or exceptions will be collected for the category.

Available Events
  • Erroneous Java Application: The event is created for errors in the Java Application log for customer Java applications deployed on the BTP Neo subaccount.

Available Filters

Filters for Data Collection Filters for Events (planned)

Coming soon.

  • Application
  • Logger
  • Message
  • Severity
  • Tenant
  • User
Read article

Still Thinking?
Give us a try!

We embrace agility in everything we do.
Our onboarding process is both simple and meaningful.
We can't wait to welcome you on AiDOOS!