Blog
Token
About Us
AiDOOS Wiki
Project Cost Estimation

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
CRM
Salesforce
ERP
SAP
Storage and Backups
Purestorage Netapp Nutanix
Cloud
AWS
Computing
IBM
Database
MongoDB MySQL PostgreSQL
DevOps
Docker Kubernetes Jenkins GitLab
Mobile
React Native Android
Web
React Angular PHP
Programming
Python
Products
CNC Software (Mastercam) 3D perception 7shifts

ERP-SAP

SAP BTP, ABAP environment

SAP BTP, ABAP Environment

Available Monitoring Content

Category Type Description
AIF Messages Messages Monitors messages sent in the SAP Application Interface Framework
ABAP Gateway Errors Exceptions Exceptions in the ABAP Gateway
Extensibility Transport Management Exceptions Exceptions in Extensibility Transport Management

Connect SAP BTP, ABAP environment

To perform the necessary setup steps in the SAP BTP, ABAP environment, please refer to:

  • Setup SAP BTP, ABAP 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, ABAP 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 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 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

SAP Mobile Services

SAP Mobile Services

Available Monitoring Content

Category Type Description
SAP Mobile Services Messages Messages Collects messages send from and to SAP Mobile Services

Connect SAP Mobile Services

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

  • Setup SAP Mobile Services

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 Mobile Services.

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 SAP Mobile Service Messages Detected (Single): The event is created for each failed message in the managed service.
  • Erroneous SAP Mobile Service 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
  • Application ID
  • Direction
  • Feature
  • Status
  • Status Group
  • Status Text
  • User Name
Read article

SAP Concur

SAP Concur

Available Monitoring Content

Messages send from and to SAP Concur are currently only monitored in the context of SAP S/4HANA Cloud, SAP S/4HANA Private Cloud Edition, SAP S/4HANA or in SAP Master Data Integration not in SAP Concur itself.

The following monitoring content is available for SAP Concur related messages.

Cloud Service Category Type Description
SAP S/4HANA Cloud Concur Objects Messages Monitors messages sent from SAP S/4HANA Cloud for the integration with SAP Concur
SAP S/4HANA Private Cloud Edition Concur Objects Messages Monitors messages sent from SAP S/4HANA Private Cloud Edition for the integration with SAP Concur
SAP S/4HANA Concur Objects Messages Monitors messages sent from SAP S/4HANA for the integration with SAP Concur
SAP Master Data Integration SAP Master Data Integration Messages Messages Monitors messages send through SAP Master Data Integration, messages to SAP Concur can be identified by the object types (e.g. CostCenter)

Setup Monitoring for SAP Concur Messages

To monitor the messages related to SAP Concur in the related cloud services please perform the monitoring setup for the relevant cloud services. After the setup you can create alerts specific to SAP Concur related messages in the Integration & Exception Monitoring application:

  • SAP S/4HANA Cloud
  • SAP S/4HANA Private Cloud Edition
  • SAP S/4HANA
  • SAP Master Data Integration

Read article

SAP Integrated Business Planning for Supply Chain

SAP Integrated Business Planning for Supply Chain

Available Monitoring Content

The following monitoring content is available for SAP Integrated Business Planning for Supply Chain.

Category Type Description
AIF Messages Messages Monitors messages sent in the SAP Application Interface Framework
SAP Integrated Business Planning Process Log Exceptions Exceptions in the SAP IBP process log
ABAP Gateway Errors Exceptions Exceptions in the ABAP Gateway
Extensibility Transport Management Exceptions Exceptions in Extensibility Transport Management

Connect SAP Integrated Business Planning

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

  • Setup SAP Integrated Business Planning for Supply Chain

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 Integrated Business Planning.

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 SAP Integrated Business Planning Process Log: The event is created for exceptions in the SAP Integrated Business Planning Process Log.

Available Filters

Filters for Data Collection Filters for Events (planned)

Coming soon.

  • Object
  • 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 Employee Central Payroll

SAP SuccessFactors Employee Central Payroll

Available Monitoring Content

The following monitoring content is available for SAP SuccessFactors Employee Central Payroll.

Category Type Description
IDoc Messages Collects IDocs send from and to SAP SuccessFactors ECP
Web Service Messages Messages Web service messages in SAP SuccessFactors ECP
SAP SuccessFactors Employee Central Payroll Exceptions Exceptions in SAP SuccessFactors ECP

Connect SAP SuccessFactors Employee Central Payroll

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

  • Setup SAP SuccessFactors Employee Central Payroll

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 Employee Central Payroll.

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(IDOC) Detected(Single): The event is created for each failed IDoc.
  • Erroneous Messages(IDOC) Detected(Grouped): The event is created if one or more IDocs failed since the last data collection.

Available Filters

Filters for Data Collection Filters for Events
  • Message Type
  • Status
  • Status Group
  • Basic Type
  • Direction
  • Message Function
  • Message Type
  • Message Variant
  • Receiver Address
  • Receiver Partner Function
  • Receiver Partner Number
  • Receiver Partner Type
  • Receiver Port
  • Sender Address
  • Sender Partner Function
  • Sender Partner Number
  • Sender Partner Type
  • Sender Port
  • Status
  • Status Group
  • Status Text

Setup Collection for Additional Payload Attributes

You can collect payload data from IDocs. This data will be available in the message details on the tab "Message Data".

  1. To find the segment field name:
    1. Log on to the managed ABAP backend system
    2. Go to transaction WE05
    3. Enter the search parameters to find one IDoc message for the IDocs you are interested in
    4. Double-click on the IDoc to open it
    5. Expand 'Data Records'
    6. Select the segment that you are interested in
    7. You find the segment fields on the screen "Content of Selected Segment"
  2. To set up the data collection of payload attributes click on the > button at the end of the line for the category IDoc
  3. In the area "Collect Additional Attributes"
    1. Click the "Add" button to add the payload attribute
    2. Enter the filter value:
      1. Message Type
      2. Segment Name
      3. Field Name
    3. Click "OK"
  4. Click the "Save" button

You can search for the messages that contain the collected data in the Tracking application. Please enclose the value with '*' to successfully find the messages (e.g. *00123456*).

Prerequisites

  • The Minimum System Requirements to monitor SXMB_MONI for Web Services is SAP BASIS 7.02 SP08
Available Events
  • Erroneous Message(WS) Detected(Single): The event is created for each failed web service message.
  • Erroneous Messages(WS) Detected(Grouped): The event is created if one or more web service messages failed since the last data collection.

Available Filters

Filters for Data Collection Filters for Events
  • Status
  • Status Group
  • Adapter Type
  • Direction
  • Message State
  • Processing Status Group
  • Processing Status Group Text
  • Receiver Interface Name
  • Receiver Interface Namespace
  • Receiver Interface Operation
  • Receiver Party
  • Sender Interface Name
  • Sender Interface Namespace
  • Sender Interface Operation
  • Sender Party
  • Status
  • Status Group
  • Status Text

Setup Collection for Additional Payload Attributes

You can collect payload data from Web Service messages. This data will be available in the message details on the tab "Message Data".

  1. Find the payload attribute name:
    1. Log on to the managed ABAP backend system
    2. Go to transaction SRT_MONI
    3. Enter the search parameters to find one web service message for the web service you are interested in
    4. Double-click on the web service message to open it
    5. Select 'Message Body'
    6. Click the button 'Original XML' to open the formatted XML message
    7. Find the attribute you are interested in
    8. Note down the XML tag name
  2. To set up the data collection of payload attributes click on the > button at the end of the line for the category "Web Service Messages"
  3. In the area "Collect Additional Attributes"
    1. Click the "Add" button to add the payload attribute
    2. Enter the filter value:
      1. Attribute: The XML tag name on the attribute
    3. Click "OK"
  4. Click the "Save" button

You can search for the messages that contain the collected data in the Tracking application. Please enclose the value with '*' to successfully find the messages (e.g. *00123456*).

Available Events
  • Erroneous SAP SuccessFactors Employee Central Payroll: The event is created for exceptions in SAP SuccessFactors Employee Central Payroll.

Available Filters

Filters for Data Collection Filters for Events (planned)

Predefined (not changeable)

  • Object: HRSFEC
  • Subobject: EMPLOYEE, EMPLOYEE_PTP, EMPLOYEE_TIME
  • External ID
  • Message ID
  • Message Number
  • Text
  • Program
  • Transaction
  • User
Read article

SAP NetWeaver Application Server for ABAP (higher than 7.40)

SAP NetWeaver Application Server for ABAP (higher than 7.40)

Available Monitoring Content

The following monitoring content is available for SAP NetWeaver Application Server for ABAP (higher than 7.40):

Category Type Description
IDoc Messages IDocs sent or received by the SAP S/4HANA system
Web Service Messages Messages Messages sent or received via Web Services and Web Service Proxies
ABAP Runtime Exceptions ABAP runtime errors (available with ST-PI 7.40 SP16)
ABAP Update Exceptions ABAP update errors (available with ST-PI 7.40 SP16)
ABAP Gateway Errors Exceptions Exceptions in the ABAP Gateway (available with ST-PI 7.40 SP16)
ABAP Aborted Job Exceptions ABAP aborted jobs (available with ST-PI 7.40 SP16)
ABAP System Log Exceptions ABAP system log errors (available with ST-PI 7.40 SP16)
ABAP Web Service Consumer Exceptions Web service errors for outgoing web service calls (available with ST-PI 7.40 SP16)
ABAP Web Service Provider Exceptions Web service errors for incoming web service calls (available with ST-PI 7.40 SP16)

Connect SAP ABAP On-Premise System

To perform the necessary setup steps in the SAP NetWeaver Application Server for ABAP system, please refer to:

  • SAP NetWeaver Application Server for ABAP (higher than 7.40)

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 NetWeaver Application Server for ABAP.

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(IDOC) Detected(Single): The event is created for each failed IDoc.
  • Erroneous Messages(IDOC) Detected(Grouped): The event is created if one or more IDocs failed since the last data collection.

Available Filters

Filters for Data Collection Filters for Events
  • Message Type
  • Status
  • Status Group
  • Basic Type
  • Direction
  • Message Function
  • Message Type
  • Message Variant
  • Receiver Address
  • Receiver Partner Function
  • Receiver Partner Number
  • Receiver Partner Type
  • Receiver Port
  • Sender Address
  • Sender Partner Function
  • Sender Partner Number
  • Sender Partner Type
  • Sender Port
  • Status
  • Status Group
  • Status Text

Setup Collection for Additional Payload Attributes

You can collect payload data from IDocs. This data will be available in the message details on the tab "Message Data".

  1. To find the segment field name:
    1. Log on to the managed ABAP backend system
    2. Go to transaction WE05
    3. Enter the search parameters to find one IDoc message for the IDocs you are interested in
    4. Double-click on the IDoc to open it
    5. Expand 'Data Records'
    6. Select the segment that you are interested in
    7. You find the segment fields on the screen "Content of Selected Segment"
  2. To set up the data collection of payload attributes click on the > button at the end of the line for the category IDoc
  3. In the area "Collect Additional Attributes"
    1. Click the "Add" button to add the payload attribute
    2. Enter the filter value:
      1. Message Type
      2. Segment Name
      3. Field Name
    3. Click "OK"
  4. Click the "Save" button

You can search for the messages that contain the collected data in the Tracking application. Please enclose the value with '*' to successfully find the messages (e.g. *00123456*).

Prerequisites

  • The Minimum System Requirements to monitor SXMB_MONI for Web Services is SAP BASIS 7.02 SP08
Available Events
  • Erroneous Message(WS) Detected(Single): The event is created for each failed web service message.
  • Erroneous Messages(WS) Detected(Grouped): The event is created if one or more web service messages failed since the last data collection.

Available Filters

Filters for Data Collection Filters for Events
  • Status
  • Status Group
  • Adapter Type
  • Direction
  • Message State
  • Processing Status Group
  • Processing Status Group Text
  • Receiver Interface Name
  • Receiver Interface Namespace
  • Receiver Interface Operation
  • Receiver Party
  • Sender Interface Name
  • Sender Interface Namespace
  • Sender Interface Operation
  • Sender Party
  • Status
  • Status Group
  • Status Text

Setup Collection for Additional Payload Attributes

You can collect payload data from Web Service messages. This data will be available in the message details on the tab "Message Data".

  1. Find the payload attribute name:
    1. Log on to the managed ABAP backend system
    2. Go to transaction SRT_MONI
    3. Enter the search parameters to find one web service message for the web service you are interested in
    4. Double-click on the web service message to open it
    5. Select 'Message Body'
    6. Click the button 'Original XML' to open the formatted XML message
    7. Find the attribute you are interested in
    8. Note down the XML tag name
  2. To set up the data collection of payload attributes click on the > button at the end of the line for the category "Web Service Messages"
  3. In the area "Collect Additional Attributes"
    1. Click the "Add" button to add the payload attribute
    2. Enter the filter value:
      1. Attribute: The XML tag name on the attribute
    3. Click "OK"
  4. Click the "Save" button

You can search for the messages that contain the collected data in the Tracking application. Please enclose the value with '*' to successfully find the messages (e.g. *00123456*).

Available Events
  • Erroneous ABAP Aborted Job: The event is created for aborted ABAP jobs.

Available Filters

Filters for Data Collection Filters for Events (planned)

Coming soon.

  • Job Name
  • 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
  • Host
  • Message
  • Location
  • Message Id

Available Events
  • Erroneous ABAP Runtime: The event is created for ABAP runtime errors.

Available Filters

Filters for Data Collection Filters for Events (planned)

Coming soon.

  • Runtime Error~Exception
  • Program
  • User
  • Message

Available Events
  • Erroneous ABAP System Log: The event is created for exceptions in the ABAP System Log.

Available Filters

Filters for Data Collection Filters for Events (planned)

Coming soon.

  • Message Id
  • Program
  • User
  • Status

Available Events
  • Erroneous ABAP Update: The event is created for ABAP Update errors.

Available Filters

Filters for Data Collection Filters for Events (planned)

Coming soon.

  • User
  • Transaction

Available Events
  • Erroneous ABAP Web Service Consumer: The event is created for errors in the web service log for ABAP Web Service Consumers.

Available Filters

Filters for Data Collection Filters for Events (planned)

Coming soon.

  • Message
  • Proxy Name
  • User

Available Events
  • Erroneous ABAP Web Service Provider: The event is created for errors in the web service log for ABAP Web Service Providers.

Available Filters

Filters for Data Collection Filters for Events (planned)

Coming soon.

  • Message
  • WS Name (Proxy)
  • User
Read article