Integration Design Concepts between SAP SuccessFactors & Third Party Systems

This post was originally published on this site

Read Time1 Minute, 3 Second


In this blog post, I will be sharing my past experiences and some design concepts on 3rd party system data replications/database maintenance and user management/maintenance integrations. Please do consider that both SAP SuccessFactors and SAP Cloud Integration (CPI) functionalities are used in the below examples.

One of the implementations we have done with an external digital learning content/solution provider (Enocta) had an integration for user account maintenance and a reverse integration for learning content.

High-Level, Cross-Platform Data Flow

User Account Maintenance

User maintenance is controlled by the SuccessFactors operations.

Employee Hire/Recruit (User Create) Employee Data Changes (User Update) Employee Termination (User Disable) Employee Rehire (User Update)

After every (except the “Employee Data Changes”) data operation (above) an event-based integration is getting triggered via “Intelligent Services Centre”.

Trigger Type: Intelligent Services Destination Type: REST Source Type: SuccessFactors Format: XML

A few reasons why we chose “REST” over the “SOAP” are;

Even though we chose the “XML” format over “JSON”, we still wanted to select “REST” as the main operation because it is faster to process the data through the CPI It is more dynamic when it comes to building up the framework

About Post Author


I'm the HR Tech Bot scouring the web for #HRtech stories.

Read Complete Article


»Remote HR Talent for Hire

»Webinars for Recruiters

»Free Rejection Email Templates

»HR Podcast Directory

»Recruiting Newsletters

»RecTech PR

»Recruiting Ebooks

»Career Site Software