SAP SuccessFactors

SAP SuccessFactors HCM Suite is SAP's SaaS human resources solution. It offers a variety of applications from Core HR applications like Employee Central or Employee Central Payroll, as well as Talent Management covering for example the Recruiting and Onboarding. You can integrate SAP SuccessFactors with your on premise system, either via SAP Cloud Platform Integration, via SAP PI, or file download/upload.

Integration Scenario

Please, select...

For most cloud services, SAP Solution Manager is able to collect and monitor 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 usually more traditional 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 setup this specific cloud service type. For information on how to set up the monitoring for the interface types supporting the integration, please refer to the setup documentation of the respective interface type which you can here.

 

For SAP SuccessFactors the following integration scenarios are possible:  

 

 

The different scenarios contain the following exceptions and point-to-point connections:

  • Integrating SAP ERP with the SAP SuccessFactors Network mediated via SAP CPI: 1, 3, 5, 8
  • Integrating SAP ERP with the SAP SuccessFactors mediated via SAP PI (Web Service based): 1, 3, 6, 8
  • Integrating SAP ERP with the SAP SuccessFactors Network mediated via file download/uploade (FTP/SFTP server) : 2, 4, (6), 7, 8

being relevant when monitoring the following SAP ERP replications:

A) Cost Center replication from Employee Central to SAP ERP HCM

B) Organizational Objects replication from Employee Central to SAP ERP HCM

C) Employee Master Data and Organizational Assignments replication from Employee Central to SAP ERP HCM

D) SAP ERP HCM and Employee Central Side-By-Side integration 

 
 

Replication Scenario Scenario Component Monitored Content Interface Channel Type Since SP
 1 A, B, C, D Systems: ABAP on-premise system Logs written in the ABAP Application Log for the BIB integration Web Service: Web Service ABAP (STAD) or Web Service ABAP (SOAP) - Number of Appl. Logs metric 7.1 SP05*
1a  A, B, C, D  Systems: ABAP on-premise system Exceptions in HCM Error Log  Cloud (Success Factors)  7.1 SP14* 
 2 A Systems: ABAP on-premise system IDocs IDoc (Real-time Monitoring)  7.1 SP12
 3 B, C, D Systems: ABAP on-premise system Web Services Web Service: Web Service ABAP (STAD) or Web Service ABAP (SOAP) 7.1 SP05*
 4  A Systems: ABAP on-premise system ABAP Proxy

Process Integration: Process Integration (PI – ABAP only)

7.1 SP12
 5  A, B, C Cloud Services: SAP Cloud Platform Integration  Exceptions in integration flows (iFlow) in SAP CPI Cloud: Cloud (SAP Cloud Platform Integration) 7.1 SP12*
 6  A, B, C Systems: SAP PI on-premise system  PI Messages and Channels

Process Integration

7.1 SP12*
 7   A Hosts: on-premise or remote host File existence, file size for transferred files File: File (Diagnostics Agent) & File (Remote)  7.1 SP10* 
 8 A, B, C, D Cloud Services: SAP SuccessFactors Exceptions in SAP SuccessFactors Cloud: Cloud (Success Factors) 7.1 SP14*

*) Monitoring content was extended with later support packages (see monitoring template page for details) 

When you set up the exception collection and monitoring you first need to know or identify which Web Service end-points and PI or CPI messages flows are relevant for your scenario. You can find this information here:

 

Technical Prerequisites

The following technical prerequisites have to be met in order to monitor this scenario:

  • To create alerts via Web Service Monitoring you need at least SAP Solution Manager 7.1 SP05.
  • To monitor exceptions from the SAP SuccessFactors Data Replication Monitor or Execution Management you need at least SAP Solution Manager 7.2 SP06.
  • To collect single exceptions in the SAP HCM Integration Add-On for Employee, Compensation, Recruiting, OnBoarding & Variable Pay you need at least SAP Solution Manager 7.1 SP14.
 
 

Available Monitoring Content

The following SuccessFactors scenarios are currently support with SAP Solution Manager public cloud operations:

  • Employee Central
  • Talent Management 

To monitor the entire SAP SuccessFactors scenario you need to monitor the on premise SAP SuccessFactors integration, the integration solution and the exceptions in the SAP SuccessFactors cloud service.

The integration between SAP SuccessFactors and the on-premise SAP HCM system is usually done using the Business Integration Builder (BIB). 

 

Integration with SFIHCM

Additional to the new integration with BIB there is also an older integration using the SFIHCM add-on which had it's own error log stores in the ABAP system.

If you are using this older integration you need to set up the exception collection for these log stores in Exception Management first.  

 

Monitoring Template: Cloud (Success Factors) 

 

Metric Name Description MAI Category Since SP

Number of exceptions (Data Replication Monitor)

Single exceptions (Data Replication Monitor)

 

Number of exceptions detected in SuccessFactors Data Replication Monitor.

Single exceptions detected in SuccessFactors Data Replication Monitor.

Exceptions and statistics are retrieved from central Exception Management in Solution Manager. Data Collection is executed in delta mode.

 

Exceptions

7.2 SP06

Number of exceptions (Integration)

Single exceptions (Integration)

Number of exceptions detected in SuccessFactors for Process Type INTEGRATION.

Single exceptions detected in SuccessFactors for Process Type INTEGRATION.

Exception statistics is retrieved from central Exception Management in Solution Manager. Data Collection is executed in delta mode.

Exceptions

7.1 SP14

Number of exceptions (SF API)

Single exceptions (SF API)

Number of exceptions detected in SuccessFactors for Process Type API.

Single exceptions detected in SuccessFactors for Process Type API.

Exception statistics is retrieved from central Exception Management in Solution Manager. Data Collection is executed in delta mode.

Exceptions Not yet support by SF Execution Manager

Number of exceptions (Scheduled Jobs)

Single exceptions (Scheduled Jobs)

Number of exceptions detected in SuccessFactors for Process Type SCHEDULED_JOBS.

Single exceptions detected in SuccessFactors for Process Type SCHEDULED_JOBS.

Exception statistics is retrieved from central Exception Management in Solution Manager. Data Collection is executed in delta mode.

Exceptions 7.1 SP14 

Number of exceptions (Simple Integration)

Single exceptions (Simple Integration)

Number of exceptions detected in SuccessFactors for Process Type SIMPLE_INTEGRATION.

Single exceptions detected in SuccessFactors for Process Type SIMPLE_INTEGRATION.

Exception statistics is retrieved from central Exception Management in Solution Manager. Data Collection is executed in delta mode.

Exceptions 7.1 SP14 

Number of exceptions (Smart Suite)

Single exceptions (Smart Suite)

Number of exceptions detected in SuccessFactors for Process Type SMART_SUITE.

Single exceptions detected in SuccessFactors for Process Type SMART_SUITE.

Exception statistics is retrieved from central Exception Management in Solution Manager. Data Collection is executed in delta mode.

Exceptions Not yet support by SF Execution Manager

Number of exceptions (Talent Management - Compensation)

Single exceptions (Talent Management - Compensation)

Number of exceptions detected in SAP Human Capital Management (Talent Management - Compensation Error Logs).

Single exceptions detected in SAP Human Capital Management (Talent Management - Compensation Error Logs).

The exceptions are retrieved from HCM via the central Exception Management in Solution Manager. Data Collection is executed in delta mode.

Exceptions 7.1 SP14

Number of exceptions (Talent Management - Employee Data)

Single exceptions (Talent Management - Employee Data)

Number of exceptions detected in SAP Human Capital Management (Talent Management - Employee Data Error Logs).

Single exceptions detected in SAP Human Capital Management (Talent Management - Employee Data Error Logs).

The exceptions are retrieved from HCM via the central Exception Management in Solution Manager. Data Collection is executed in delta mode.

Exceptions 7.1 SP14

Number of exceptions (Talent Management - Onboarding)

Single exceptions (Talent Management - Onboarding)

Number of exceptions detected in SAP Human Capital Management (Talent Management - Onboarding Error Logs).

Single exceptions detected in SAP Human Capital Management (Talent Management - Onboarding Error Logs).

The exceptions are retrieved from HCM via the central Exception Management in Solution Manager. Data Collection is executed in delta mode.

Exceptions 7.1 SP14

Number of exceptions (Talent Management - Recruiting)

Single exceptions (Talent Management - Recruiting)

Number of exceptions detected in SAP Human Capital Management (Talent Management - RecruitingError Logs).

Single exceptions detected in SAP Human Capital Management (Talent Management - Recruiting Error Logs).

The exceptions are retrieved from HCM via the central Exception Management in Solution Manager. Data Collection is executed in delta mode.

Exceptions 7.1 SP14

Number of exceptions (Talent Management - Variable Pay)

Single exceptions (Talent Management - Variable Pay)

Number of exceptions detected in SAP Human Capital Management (Talent Management - Variable Pay Error Logs).

Single exceptions detected in SAP Human Capital Management (Talent Management - Variable Pay Error Logs).

The exceptions are retrieved from HCM via the central Exception Management in Solution Manager. Data Collection is executed in delta mode.

Exceptions 7.1 SP14
Number of exceptions in SuccessFactors BizX (Delta)

Number of exceptions detected in SuccessFactors BizX.

Exception statistics is retrieved from central Exception Management in Solution Manager. Data Collection is executed in delta mode.

The statistics are based on single exceptions which are send from SuccessFactors BizX via email to Solution Manager Inbox. They are available afterwards in central Exception Management in Solution Manager.

Exceptions Deprecated
Number of exceptions in SuccessFactors BizX (Last 24h)

Number of exceptions detected in SuccessFactors BizX during the last 24h.

Exception statistics is retrieved from central Exception Management in Solution Manager. Data Collection is executed in delta mode.

The statistics are based on single exceptions which are send from SuccessFactors BizX via email to Solution Manager Inbox. They are available afterwards in central Exception Management in Solution Manager.

Exceptions Deprecated

Connect Cloud Service

Please, select...

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 SAP Solution Manager does not apply to cloud services.

However, to be able to monitor exceptions and performance in cloud services they need to be connected to SAP Solution Manager. This connection is created using the customer and cloud service specific root URL and an end-point definition.

The first step is to import the SSL certificate into SAP Solution Manager. This is valid for all cloud services.

Import Cloud SSL certificate into STRUST

Export Certificate from Browser: 

  1. Open the cloud service URL in your web browser.
  2. Click on the padlock next to the Cloud Service URL (within the address input field).
  3. When using Firefox, click on ‘Show Connection details', ‘More Information', 'View Certificate' and select the ‘Details' tab.
  4. When using Microsoft IExplorer, click on ‘View Certificate' and select the 'Certificate Path' tab.
  5. When using Google Chrome, click on ‘Certificate' and select the 'Certificate Path' tab.
  6. In the displayed certificate hierarchy select the Certification Authority (CA) certificate you plan to trust.
  7. When using Firefox, press ‘Export…'.
  8. When using Microsoft IExplorer or Google Chrome, press ‘View Certificate' and in the displayed pop-up navigate to the ‘Details' tab, to press ‘Copy to File…'.
  9. Select an export format you would like to use and that is supported by STRUST transaction, and export the certificate.

Import Certificate into SAP Solution Manager:

  1. Now, log on to SAP Solution Manager ABAP and go to transaction STRUST.
  2. Switch to Edit.
  3. Double click on entry 'SSL client SSL Client (Anonymous)'.
  4. Import the previously exported CA certificate, by pressing – within section ‘Certificate' – the icon ‘Import Certificate'.
  5. Press ‘Add to Certificate List'.
  6. Finally ‘Save' this modification. 

Additionally you have to perform certain preparations in the cloud service to enable SAP Solution Manager to connect to the cloud service.   

 
 
 
 

Preparations in SAP SuccessFactors

Create User in SuccessFactors

The following steps describe how to create a user that can access the Execution Manager to collect exceptions from SuccessFactors.

  1. Enable SFAPI: In order to use the SFAPI, SuccessFactors must enable the API for your company instance. Please contact your SuccessFactors support representative to enable the SFAPI for your instance.
  2. Create a new user for the SFAPI in SuccessFactors.
  3. Assign API Login Permissions: Each user of the API must have API Login Permission. Setting this permission depends on which permission system you are using in your SuccessFactors instance.
    1. Traditional (aka User-Based) Permission System: Admin Tools → Manage Users → Manage API Login Permission
    2. Role Based Permission System: API Login Permission in the Role Based Permission system is listed under the General User Permission category in the Permission settings page.
  4. For the Exception management scenarios, the API is called Execution Manager. Create a new permission role to be assigned to the SFAPI user (e.g. SFAPI_EM)
  5. Make sure the following permissions are assigned to this role:
    • General User Permission:
      • User Login
      • SFAPI User Login 
    • Admin Center Permissions
      • Read Execution Manager Events
      • Read Execution Manager Event Payload 
    • Manage Integration Tools
      • Admin access to OData API 
  6. Grant this role to the user you created before
 

Connect Cloud Service to SAP Solution Manager 

The Cloud Services configuration is now accessible from the SAP Solution Manager Configuration (SOLMAN_SETUP) → Managed Systems Configuration → Tab 'Cloud Services'.

Create Cloud Service:

  1. Select 'Cloud Service Operations' → Create Cloud Service
  2. Select Service Type: 'SAP SuccessFactors' from the drop-down list.
  3. Define Service:
    • Company ID: Enter your SAP SuccessFactors Company ID and a description
  4. Define Root URL: The root URL of the API server corresponding to your SAP SuccessFactors account/datacenter. This URL is different from the SuccessFactors main URL for applications, it is typically something like https://<api-server>.successfactors.com
    • You can also adjust the extended service ID (The ID used as SID in LMDB) here.
  5. Confirmation: Check your input values and click 'Finish'

The second step is to create the end-point for the cloud service. For SuccessFactors you can create an HTTP end-point and additionally an SFTP end-point if you have integration using file download. 

Create the End-Point: 

  1. Select your SAP SuccessFactors cloud service from the list and click 'Configure Cloud Service' 
  2. Configure Endpoints: Click the 'Add' button on the 'HTTP Endpoints' tab.
  3. Enter the following information:
    • Description: A meaningful description
    • User: The user created for SFAPI
    • Password: Password of the user
    • If necessary add proxy information to connect to SAP SuccessFactors

If you want to also monitor remote file up- and download on the SuccessFactors server you need to additionally create an SFTP end-point. Make sure that an (S)FTP server is running on the remote host.

  1. To create and SFTP endpoint click the 'Add' button on the 'SFTP Endpoint' tab
  2. Enter the following information: 
    • Description: A meaningful description
    • User: SFTP user
    • Password: <Password>
    • Protocol: SFTP or FTP
    • Host: hostname of the remote host (FQDN)
    • Port: (S)FTP port of the remote host. The default FTP port is 21, the default SFTP port is 22.
    • Timezone: Select the time zone of the remote host

The end-point type Email endpoint is deprecated and shouldn't be used anymore. It is still available to support upgrade compatibility for customers who used it in the past.

Monitoring Configuration

Step 1: Configure Exception Management

For SAP SuccessFactors you have to set up two distinct exception log stores, as described below and depending on your integration solution. To collect exceptions directly in SAP SuccessFactors you have to set up the exception store for the exceptions occurring in SAP SuccessFactors.

If your integration still includes the SAP SuccessFactors Integration add-on SFIHCM, installed in the SAP ABAP on premise system, you need to set up one log store that collects the exceptions occurring in this add-on.  

Exceptions in SAP SuccessFactors

In the second exception store you can collect exceptions directly from SAP SuccessFactors.

To access the Exception Management setup please go to transaction SOLMAN_SETUP → Application Operations → Exception Management 

  1. In the step 'Define Scope' select the tab 'Cloud Services' and your SAP Success Factors cloud service. If you didn't configure the system before make sure to select 'All Cloud Services' in the view drop-down. Click on 'Configure' or click 'Next' two times. You will enter the step 'Exception Configuration'.
  2. Click 'Add / Configure Log Store'. Select the relevant log store. The following log stores are available for SAP SuccessFactors:
    • SF Data Replication Errors
    • SF INTEGRATION
    • SF API (Currently no meaningful errors are written by the SF Execution Manager)
    • SF SCHEDULED_JOB
    • SF SIMPLE_INTEGRATION
    • SF SMART_SUITE (Currently no meaningful errors are written by the SF Execution Manager)
  3. Select the correct end-point for SAP SuccessFactors if you have more than one.
  4. Select the fields for filtering for your log store. Which fields are available depends on the log store:
    • SF Data Replication Errors:
      • replicationContentType: Content Type (e.g. 'Employee Absence Data')
      • replicationTargetSystem: Target System (e.g. SAP HCM system)
      • sourceMessageText: Message Text
    • All others:
      • eventDescription: Description of the error event
      • eventName: Name of the event
      • moduleName: Name of SuccessFactors Module
      • processName: The name of the process to be monitored (must be part of the selected log store/process type)
      • userID: The user running the process 
  5. Maintain the filter values for the fields in the Filter Definition panel under the log stores table. You can also add, remove or change filter fields and values later on in the area. You can use different operators for your filter value. You can add more than one filter filed combination per log store. To add an additional filter field combination click on the button 'Add Filter' in the 'Configured Log Stores' panel.
  6. You should not set up the monitoring for the exceptions in the Exception Management. If you activate the monitoring here, you will receive an alert (and if set up this way an email) for every single exception in the application log. Instead we will use Interface and Connection Monitoring to monitor the central exceptions store for exceptions.

Exceptions in SAP SuccessFactors Integration Add-On

This section is only relevant for you if you are still using the older integration with the SFIHCM add-on.  

If you are using the new integration between SAP SuccessFactors and the on-premise SAP HCM system, that is done using the Business Integration Builder (BIB), you can go the section "Exceptions in SAP SuccessFactors". BIB writes log entries in the ABAP Application Log. The monitoring for this log is set up directly in Interface and Connection Monitoring. The Exception Management setup happens in the background triggered by the Interface and Connection Monitoring application and must not be done manually. Please refer to the Interface and Connection Monitoring setup below for details. 

The older SFIHCM add-on write exceptions in the HCM error log. These log entries can be collected with the Exception Management log store for the SAP HCM Integration Add-on. The log store is set up on the SAP ABAP on premise system on which the add-on is installed and you have to first collect these exceptions before you can use them in Interface and Connection Monitoring

To access the Exception Management setup please go to transaction SOLMAN_SETUP → Application Operations → Exception Management 

  1. In the step 'Define Scope' select the tab 'Technical Systems' and your SAP ABAP system. Click on 'Configure' or click 'Next' two times. You will enter the step 'Exception Configuration'.
  2. Click 'Add / Configure Log Store' → Standard. Select the relevant log store. The following log stores collect application log errors in the SuccessFactors context:
    • HCM Employee Error Log
    • HCM Compensation Error Log
    • HCM OnBoarding Error Log
    • HCM Recruiting Error Log
    • HCM Variable Pay Error Log
  3. Select the fields for filtering for your log store. The following filter fields are available:
    • MESSAGE_ID: Message Class (e.g. E (Error))
    • MESSAGE_NUMBER: Message Number
    • MESSAGE_TEXT: Localized Message Text
  4. Maintain the filter values for the fields in the Filter Definition panel under the log stores table. You can also add, remove or change filter fields and values later on in the area. You can use different operators for your filter value. You can add more than one filter filed combination per log store. To add an additional filter field combination click on the button 'Add Filter' in the 'Configured Log Stores' panel.
  5. You should not set up the monitoring for the exceptions in the Exception Management. If you activate the monitoring here, you will receive an alert (and if set up this way an email) for every single exception in the application log. Instead we will use Interface and Connection Monitoring to monitor the central exceptions store for exceptions.
 
 
 
 
 
 

Step 2: Configure Interface and Connection Monitoring

The last step is the configuration of Interface and Connection Monitoring. The Interface and Connection Monitoring setup can be accessed via SAP Solution Manager Configuration (SOLMAN_SETUP). Since the data collection for the exceptions in SAP SuccessFactors is based on the content of the global exceptions store, you can always check the collected exceptions in Exception Management. All filter parameters are part of the collection context of the exceptions.

To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.

Monitoring Template: Web Services ABAP

This monitoring template is used to monitor the performance and for exceptions happening in the Web Service communication between the SAP Success Factors  Integration add-on in SAP ABAP and SAP Cloud Platform Integration.

For detailed setup information how to set up this channel type please refer to the configuration of Web Service Channels. You can use the template Web Services ABAP (SOAP) or Web Services ABAP (STAD) for the monitoring. Please note if you use the Web Services ABAP (SOAP) template you must activate the Web Service performance monitoring in the ABAP system as per SAP Note 1639329

Make sure to use the input help for the field WS name or WS proxy to fill in the filter values.

As additional functionality we also use this template to create alerts for error logs written by the the BIB Integration in the SAP Application Log. To monitor the SAP Application Log, the 'Number of AppLog Errors (WS)' metric should be selected additionally to the desired Web Service metrics.

Which Application Log object and sub-object you need to enter depends on the scenario in in the BIB integration: 

 
 
 

Replication Area Object Sub-Object
Combined employee master data and organizational assignments replication from Employee Central to SAP ERP HCM  ECPAO_IN 
  • GEN for generic messages
  • EE for employee master data
  • VERBOSE for the Verbose message log 
Employee master data replication from Employee Central to SAP ERP HCM  PAOC_SFI_PA 
  • EE for employee master data 
Organizational data or organizational objects replication from Employee Central to SAP ERP HCM and S/4 HANA  PAOC_SFI_OM 
  • REPL_REQ_PROCESSING for the log created by the replication
  • REPL_REQ_PROXY for the log created when processing the inbound message 
Employee time data replication from Employee Central to SAP ERP HCM  PAOC_SFI_PA 
  • EE_TIME 
Replication of employee data from SAP ERP HCM to Employee Central in a Side-by-side scenario (SAP ERP HCM and EC are used both simultaneously)  ECPAO 
  • ECPAO
  • ECPAO_KEYVALUE
  • ECPAO_MANAGER
  • ECPAO_METADATA
  • ECPAO_OM 

Monitoring Template: Cloud (Success Factors)

Navigate to the step 'Define Scope'. You can create a new scenario for the SAP Success Factors monitoring or use an existing one. Make sure the on premise system for the SAP Success Factors scenario and the Cloud Service created for SAP Success Factors are part of the Interface and Connection Monitoring scenario. If you use the integration via SAP CPI this cloud service should be added as well.

Create the Interface Channel:

  1. Select the scenario and click 'Next'
  2. In step 'Preparation' perform all relevant manual activities and run all automatic activities.
  3. In step 'Configuration' click the 'Add' button.
    • Channel Name: Enter a meaning full name (max. 30 characters)
    • Type: Select 'Cloud'
    • Monitoring Template: Select 'Cloud (Success Factors)'
    • Description: Enter a description for the channel
  4. Click Next.
  5. Source type:
    • If the source system is the on premise system, please select 'Technical System'
    • If the source system is the cloud service please select 'External Service'
  6. Source: Select the on premise system resp. the Cloud Service from the drop-down list
  7. Target Type:
    • If the target system is the on premise system, please select 'Technical System'
    • If the target system is the cloud service please select 'External Service'
  8. Target: Select the on premise system resp. the Cloud Service from the drop-down list
  9. The measuring point is selected automatically
  10. If more than one client are connected for the on premise system please select the correct client for the monitoring
  11. Click Next.
  12. Click Finish. 
 

Metrics for Talent Management Application

The metrics for Talent Management Applications are collected based on the exception stores for the HCM Error Logs. These exceptions are collected in the SAP HCM system. Hence the exception stores are set up in the SAP HCM system context.

In ICMon these metrics are implicitly collected from the HCM system, even if the measuring point is set to the SF external service. So the data collector will try to get the information from "the other" partner assuming it is the SAP HCM system. To successfully collect these metrics you must create a direct channel between SAP HCM and SF, even if you are using a middleware. 

 

Maintain the Interface:

  1. The interface channel type does not have any configurable parameters.

Select Metrics:

  1. On the tab 'Metrics' select the metrics you want to monitor

  2. Enter Metric Parameters:

    • Number of exceptions / Single Exceptions (Data Replication Monitor):

      • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
      • Replication Content Type: Content Type (e.g. 'Employee Absence Data')
      • Replication Target System: Target System (e.g. SAP HCM system)
      • Source Message Text: Message Text
    • Number of exceptions / Single Exceptions (Integration), Number of exceptions / Single Exceptions (SF API), Number of exceptions / Single Exceptions (Scheduled Jobs), Number of exceptions / Single Exceptions (Simple Integration), Number of exceptions / Single Exceptions (Smart Suite)
      • Event Description: Description of the error event
      • Event Name: Name of the event
      • Module Name: Name of SuccessFactors Module
      • Process Name: The name of the process to be monitored (must be part of the selected log store/process type)
      • User ID: The user running the process 
    • Number of exceptions / Single Exceptions (Talent Management - Compensation), Number of exceptions / Single Exceptions (Talent Management - Employee Data), Number of exceptions / Single Exceptions (Talent Management - Onboarding), Number of exceptions / Single Exceptions (Talent Management - Recruiting), Number of exceptions / Single Exceptions (Talent Management - Variable Pay)
      • Message ID: Message Class (e.g. E (Error))
      • Message Number: Message Number
      • Message Text: Localized Message Text
  3. Save your interface channel by clicking on the 'Save' button.

Filter Values in Interface and Connection Monitoring

Since the data collection is based on the content of the global exceptions store, you can always check the collected exceptions in Exception Management. All filter parameters are part of the collection context of the exceptions. The filters applied in Interface and Connection Monitoring allow you to filter the exceptions collected by the Exception Management further. However if the filters in Exception Management do not collect an exception, it is not available in the central exception store and you will not be able to find it in Interface and Connection Monitoring!  

 

You can maintain attributes as described in the Interface and Connection Monitoring Setup on tab 'Attributes'.

Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click 'Next' in the main guided procedure to move to the step 'Activation'.

Maintain Thresholds and Schedule:

  1. Select the Alert for the SAP Ariba Network channel (the alert is the line with the red flash icon next to it)
    • On alert level you can maintain notification and incident message creation
    • Do not remove the flag for 'Do not Group Individual Occurrences' as this flag ensures that an alert each time new exceptions are found during a data collection interval
  2. Select the Metrics
    • Do not change the data collector type or data collector name on the tab 'Data Collection' as the monitor will not work anymore if this is changed.
    • Do not change the threshold if it is set to 'Already Rated'.
  3. Click 'Apply and Activate' → <Choose one option> to activate the monitoring 

If not active you can also activate the reporting for the channels by checking the box in the column 'Reporting'. This way you can see a history of the number of exceptions that happened and also place the metric on the OCC Dashboard in Focused Insights.