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

Unlike the classic point-to-point interfaces like e.g. IDocs, Web Services or RFCs, when talking about monitoring for cloud services, you always also have to consider the integration component of the scenario. For most cloud services, Advanced Integration Monitoring for the cloud service itself concentrates on monitoring 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 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 categories that are available for this specific cloud service type. For information on how to set up the monitoring categories for the other technical system and cloud service types, please refer to the setup documentation of the respective interface type.

After setting up the monitoring for the single components and interface types, you can use the scenario configuration to group all relevant messages and exceptions of the cloud integration scenario in one Advanced Integration Monitoring scenario. Information how to create scenarios can be found 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, 7
  • Integrating SAP ERP with the SAP SuccessFactors mediated via SAP PI: 1, 2, 3, 4, 6, 7

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 Component Monitored Content Monitoring Category
A, B, C, D Systems: ABAP on-premise system Logs written in the ABAP Application Log for the BIB integration ABAP Application Log
A Systems: ABAP on-premise system IDocs IDoc
B, C, D Systems: ABAP on-premise system Web Service errors and performance Web Service Messages (ABAP), Web Service (Performance)
A Systems: ABAP on-premise system Messages in the ABAP proxy framework

ABAP: PI Messages

A, B, C Cloud Services: SAP Cloud Platform Integration Integration flows (iFlow) in SAP CPI SAP Cloud Platform Integration
A, B, C Systems: SAP PI on-premise system PI Messages

ABAP: PI Messages

Java: PI Communication Channels, PI Messages

B, C, D Cloud Services: SAP Success Factors Errors that occur in the SAP SuccessFactors Cloud service (Data Replication Monitor and Event Management). SuccessFactors Data Replication Monitor, SuccessFactors Integration, SuccessFactors Scheduled Jobs, SuccessFactors Simple Integration

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:

SAP Success Factors Scenarios covered by Focused Run

The following SAP SuccessFactors scenarios are currently covered:

  • Employee Central
  • Talent Management
 

Technical Prerequisites

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

Remark: In the past, the integration was done using the SFIHCM add-on which had it's own error log stores in the ABAP system. This integration and hence these log stores are not relevant anymore for the integration with the current SAP SuccessFactors version. 

 

Configure 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 Focused Run does not apply to cloud services.

However, to be able to monitor exceptions and performance in cloud services they need to be connected to Focused Run. This connection is created using the customer and cloud service specific root URL and an end-point definition, which allows Focused Run to receive information from the cloud service.

The first step is to import the SSL certificate into Focused Run. 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 Focused Run:

  1. Now, log on to Focused Run 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 Focused Run to connect to the cloud service.   

 
 
 
 

Preparations in SAP SuccessFactors

Creating a User for SuccessFactors Monitoring

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.
    • Traditional (aka User-Based) Permission System: Admin Tools → Manage Users → Manage API Login Permission
    • 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 
 

Please, select...

After gathering all necessary information and creating the necessary connection point or users in the cloud service, you can now create the cloud service in Focused Run.

  1. Call transaction FRUN
  2. Select 'Advanced Integration Monitoring' → Cloud Service Management
  3. Click the 'Add' button
  4. Select the Cloud Service Type.
  5. The other input fields in the section 'Definition' depend on the cloud service type, see the details below
  6. In the section 'Identification' you have to enter the following:
    • Customer Network: the isolated network for which this cloud service should be visible
    • Extended Service ID: the extended SID uniquely identifies the cloud service in LMDB and can be between 3 and 8 characters long
 

Input Values for SAP SuccessFactors

  • Company ID: Your Company ID
  • API Server 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
  • Description: (optional)

Please, select...

The second step is to create the end-point for the cloud service. The end-point is used to actually connect to the cloud service with user and password. Most cloud services use HTTP end-points.

  1. Click on the extended service ID of the cloud service 
  2. Click the 'Add' button on the 'HTTP ENDPOINTS' tab.
  3. Enter the following information:
    • Section 'Global':
      • Description: A meaningful description
    • Section 'Authentication':
      • The information needed here depends on the cloud service type, please refer to the details below
    • Section 'Proxy':
      • If necessary add proxy information to connect to the cloud service
 

Input Values for SAP SuccessFactors

  • Endpoint Type: HTTP
  • Authentication Type: BASICAUTH
  • User: The user created for SFAPI
  • Password:Password of the user

Advanced Integration Monitoring Setup

Please, select...

To be able to monitor interfaces of an on-premise system you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system. 

  1. Open the Advanced Integration Monitoring Application by clicking on the 'Integration & Cloud Monitoring' tile in transaction FRUN
  2. Click on the pinwheel in the upper right corner of the 'Integration & Cloud Monitoring' application
  3. In the configuration panel expand the 'Cloud Services' tray and click on the pen icon in the upper right corner. This will open the 'Configuration for Cloud Services' view.
  4. If your system is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the system ID of the system. 

In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.

Select the monitoring categories in scope.

Available Monitoring Categories 

For SAP Success Factors different monitoring categories are available.

  • SuccessFactors Data Replication Monitor: Collects exceptions from the Data Replication Monitor. This category is configured on the SuccessFactors cloud service.
  • SuccessFactors Integration: Collects exceptions for Integration from the Execution Management. This category is configured on the SuccessFactors cloud service.
  • SuccessFactors Scheduled Jobs: Collects job exceptions from the Execution Management. This category is configured on the SuccessFactors cloud service.
  • SuccessFactors Simple Integration: Collects exceptions for Simple Integration from the Execution Management. This category is configured on the SuccessFactors cloud service.

For monitoring of errors and warning happening during the integration on the on-premise side, please use:

  • 'ABAP Application Log' on the ABAP on-premise system.

The following monitoring categories are deprecated and should only be used as long as you still use the SFIHCM integration add-on in your on-premise system. Please note, even if you don't use the add-on anymore, they might still show up for your SAP HCM system in AIM if you used the SFIHCM add-on in the past and it is still installed on the SAP HCM system:

  • HCM Employee Errors
  • HCM Compensation Errors
  • HCM OnBoarding Errors
  • HCM Recruiting Errors
  • HCM Variable Pay Errors 
 

Please, select...

After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own. You can create more than one filter for a monitoring category.

Available Filter Options

SuccessFactors Integration using BIB writes errors in the ABAP Application Log. Hence you have to select at least the Object and the Subobject. Use the monitoring category 'ABAP Application Log' on the on-premise system. Please use the following filter parameters to collect the correct application logs: 

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 

For the categories collected from the SAP SuccessFactors cloud service, you can collect all exceptions or filter them using the following parameters:

SuccessFactors Data Replication Monitor

  • ReplicationContent Type: Content type (e.g. 'Employee Absence Data')
  • Replication Target System: Target System (e.g. SAP HCM system)

SuccessFactors Integration

  • 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

SuccessFactors Scheduled Jobs

  • 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

SuccessFactors Simple Integration

  • 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 
 

Please, select...

The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually. If you didn't use specific filters in the setup before, but rather opted to collect all data, you have to create filters for the alerts.

  1. Click on the 'New Alert' button in the upper right corner of the alerts table. A new panel will appear below the table for you to enter the alert information
  2. Select the monitoring category
  3. Select the metric name. The available metrics depend on the monitoring category.
  4. Enter a name for the alert
  5. Enter a name for the filter

In the next sub-step, you have to maintain the filter. The filter values are the same as described above. For some metrics, you have to maintain metric parameters. Find details below in the overview of the available metrics.

In the last sub-step you have to activate the alert:

  1. Check the checkbox next to 'Active'
  2. You can adjust the calculation frequency and the severity
  3. Available threshold types depend on the metric selected. If the threshold type allows it you can adjust the threshold value which triggers the alert.
  4. Select the notification variant and the outbound connector variant from the drop-down list.

For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.

Available Metrics

For SAP SuccessFactors the following metrics are available:

SuccessFactors Data Replication Monitor

  • SuccessFactors Data Replication Monitor exceptions: Indicates that new exceptions were collected during the last data collection interval

SuccessFactors Integration

  • SuccessFactors Integration exceptions: Indicates that new exceptions were collected during the last data collection interval

SuccessFactors Scheduled Jobs

  • SuccessFactors Scheduled Jobs exceptions: Indicates that new exceptions were collected during the last data collection interval

SuccessFactors Simple Integration

  • SuccessFactors Simple Integration exceptions: Indicates that new exceptions were collected during the last data collection interval

Error for the replication on the on-premise systems can be collected with the metric 'ABAP Application Log exceptions' for 'ABAP Application Log'.