• Integration
  • »
  • Integration with SAP SuccessFactors Employee Central


Integration with SAP SuccessFactors Employee Central

This section describes how to integrate SAP SuccessFactors Employee Central with SAP Commissions using Cloud Platform Integration (CPI) and Commissions Data Loader (CDL). This section describes how to use CPI to trigger the employee replication process. This integration passes Participant, Position, and Title information to SAP Commissions.


The following are prerequisite tasks that must be completed before proceeding with this integration:

  • Deploy required user API credentials for SuccessFactors Employee Central system
  • Deploy SFTP user’s private key and public key in known hosts of security material
  • Provide necessary directory access in SFTP for the user

Configuring SAP Cloud Integration

In the Design tab of your SAP Cloud Integration system tenant, open the package SAP SuccessFactors Employee Central with SAP Sales Cloud Commissions. This package includes the following three iFlows:

  • Participant Replication to SAP Commissions
  • Position Replication to SAP Commissions
  • Title replication to SAP Commissions

Note: For more information about the iFlows, visit the SAP API Business Hub.

To configure the integration:

  1. Once you have opened the integration package, select the respective iFlow in the package and click on Action > Configure to start the configurations.
  2. Configure the Timer Event. Repeat this step for all three iFlows.
  3. Configure the Employee Central (EC) system user and API URL.

    Repeat this step for all three iFlows, however, you must use the same credentials and SF API URL for each iFlow.

  4. Configure the SFTP destination.

    The SFTP directory path is different for each iFlow, so you must complete this step for each iFlow and provide the correct directory path.

    Important: SAP Commissions must have position information available before assigning manager to positions, therefore for iFlow “Position Replication to SAP Commissions” you will have two folders as follows:
    1. without manager assignment
    2. with manager assignment

    Commissions Data Loader (CDL) imports position information, first from the “without_manager” folder and on success CDL will proceed further with manager assignment by importing from the “with_manager” folder.

  5. Configure the name of the file and Initial load date-time. Repeat this step for each iFlow.

    The Execution Timestamp (initial load) should be the same for all three iFlows to maintain consistency.

    Execution Timestamp is the date-time base upon which employees are pulled from Employee Central for the initial load. After the initial load, the iFlow will automatically run in delta mode and pulls employees from the last successful run. Provide the date as per the following format yyyy-MM-ddTHH:mm:ss.SSSZ.

  6. Click Save to save the settings and deploy if you want to start the replication as per the schedule you created in the Timer Event.

Initial Load vs. Delta Load

In integration scenarios, it is a common practice to distinguish the replication of data between systems as follows:

  • Initial load – Date-time from which you want all the data relevant on the source system to be replicated to the target system.
  • Delta load – Date-time to ensure all recent changes (post initial load) are replicated from the source system to the target system periodically.
A good practice is to have an initial load to run once so that all data that exists in the source system from the pre-configured time stamp are now part of the target system. Then based on the business use case, you can occasionally schedule delta replication, as needed. For example, if the frequency of employee record changes happen more on a daily basis, then schedule iFlows to run every 4 hours so that data between the systems are up-to-date.

For this integration content, you can find the current delta load time stamp by checking the value stored in the following variables that are available in Operations View > Manage Stores > Manage Variables.

Triggering the Initial Load

If for some business reason you want to retrigger the initial load, that is, do a refresh of all participants, positions and titles, you must delete the three variables available under Operations View in Manage Stores > Manage Variables.

Warning: We do not encourage re-initial load to be performed since it can cause inconsistency.  


Monitoring information is available in Operations View > Monitor Message Processing.  

Related Articles