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, 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

SAP Marketing Cloud

SAP Marketing Cloud

Available Monitoring Content

The following monitoring content is available for SAP Marketing Cloud:

Category Type Description
AIF Messages Messages Monitors messages sent in the SAP Application Interface Framework
Marketing Data Import (asynchronous) Exceptions Exceptions during the marketing data import
ABAP Gateway Errors Exceptions Exceptions in the ABAP gateway
Extensibility Transport Management Exceptions Exceptions in extensibility transport management

Connect SAP Marketing Cloud

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

  • Setup SAP Marketing 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 Marketing 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 SAP Marketing Cloud: The event is created for exceptions during the marketing data import.

Available Filters

Filters for Data Collection Filters for Events (planned)

Predefined (not changeable)

  • Object: CUAN_CE_IC, CUAN_CE_INTERACTION, CUAN_PROD_CATEGORY, CUAN_PRODUCT, HPA_STAGING_AREA
  • Subobject: IMPORT, STAGING_AREA
  • 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 Cloud ALM Service Key

Retrieve SAP Cloud ALM Service Key

Some of the managed SAP Cloud services use a PUSH mechanism to send alerts and exceptions to SAP Cloud ALM. To successfully set up this PUSH mechanism you need the SAP Cloud ALM Service Key to enter the SAP Cloud ALM credentials during the PUSH setup in the managed SAP Cloud service.

Prerequisites

  • An instance for SAP Cloud ALM API has been created. Find more information here .
  • You must have "Space Developer" access for the space in which the instance was created in your SAP Cloud ALM sub-account in the SAP Business Technology Platform

The following video demonstrates the necessary steps to retrieve the SAP Cloud ALM service key from SAP BTP cockpit. A textual step by step description is provided in the section below the video.

To retrieve the SAP Cloud ALM Service Key please follow these steps:

Service Key Retrieval

  1. Log on to the SAP BTP cockpit.
  2. Click on your SAP Cloud ALM global account, then on your SAP Cloud ALM sub-account.
  3. In the navigation panel, choose Services > Instances and Subscriptions .
  4. Under Instances click on the relevant instance of the service SAP Cloud ALM API
  5. In the area that opens, choose Service Keys .
  6. You see your service key in JSON format. The key includes the application URL, service URL, client ID, and client secret.
  7. Download this service key and save it for later

Read article

Integration Scenarios in SAP Cloud ALM

Scenario Configuration

Create Scenario

  1. Click the 'Configuration' button in the Integration & Exception Monitoring UI
  2. Scroll down to the 'Integration Scenarios' section
  3. Click the pen icon to open the 'Scenario Configuration'
  4. Click the Add button
  5. Enter the name and the description for the scenario

Maintain Scenario Components

At first you have to add the components to the scenario.

  1. Click the Add button on top of the 'Services' table
  2. Select the services from the list by checking the checkbox in front of them
  3. Click the OK button
For each of the services in the scenario you can maintain filters and alerts. The filters make sure that only certain messages and exceptions are considered as part of the scenario, even if the monitoring was activated for all of them.
  1. Select the service for which you want to add the filter
  2. Click the Add button on top of the 'Filter for Data' table
  3. Select an available Category
  4. Enter a name for the filter and maintain the filter values
    • The available Categories depend on the selected service
    • The filter fields depend on the selected category
    • For more information on the meaning for the different filter fields please refer to the setup information for the respective service type
  5. Activate or deactivate alerts
    1. Select the alert in the table 'Alert Details for Filter' below the 'Filter for data' table
    2. Click the Edit button
    3. You can change the Display name and the alert description
    4. Use the 'Alerting Status' slider to activate or deactivate an alert

Maintain Paths

You can also maintain paths between the components to visualize a message flow.

  1. On the tab 'Paths' you find a matrix with all the components in the scenario
  2. Select the row that stands for the desired source
  3. Check the checkbox in the column that stands for the desired target

Read article

SAP Fieldglass

SAP Fieldglass

Available Monitoring Content

Category Type Description
SAP Fieldglass Messages Messages Messages send from and to SAP Fieldglass which are recorded in the Subscription Audit Trail, the Integration Audit Trail and the Event Driven Audit Trail

Connect SAP Fieldglass

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

  • Setup SAP Fieldglass

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

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 Fieldglass Message Detected(Single): The event is created for each failed message in the managed service.
  • Erroneous Fieldglass 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
  • Category Type
  • Direction
  • Name
  • Status
  • Status Group
  • Status Details
Read article

SAP S/4HANA & SAP Business Suite

SAP S/4HANA & SAP Business Suite

Available Monitoring Content

The following monitoring content is available for SAP S/4HANA and SAP Business Suite

Category Type Description
AIF Messages Messages Messages send via the Application Interface Framework
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
Concur Objects Messages Monitors messages sent for the integration with Concur
ABAP Web Service Provider Exceptions Web service errors for incoming web service calls (available with ST-PI 7.40 SP16)
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)
SAP S/4HANA Asset Central Foundation Integration Exceptions Collects exceptions happening in SAP Intelligent Asset Management

Connect SAP ABAP On-Premise System

To perform the necessary setup steps in the SAP S/4HANA or SAP Business Suite system, please refer to:

  • Setup SAP S/4HANA and SAP Business Suite

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 and SAP Business Suite.

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

Available Events
  • Erroneous SAP S/4HANA Asset Central Foundation Integration: The event is created for exceptions in SAP S/4HANA 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
Read article