Skip to Content
Technical Articles

Integration of SuccessFactors Employee Central module with Oracle 10g and Oracle ERP database through SAP CPI middleware.

How to insert the data from SuccessFactors Employee Central to Oracle 10G, ERP database through SAP CPI middleware.

Scenario: Outbound Integration from SuccessFactors Employee Central to Oracle System.

Data will be fetched as per requirement either delta or full volume from the SAP SuccessFactors Employee Central in the SAP Cloud Platform Integration (CPI) using SuccessFactors adapter through Compound Employee API (a SOAP-based web service inside EC, is commonly used to synchronize employee master data between Employee Central and other on-demand or on-premise applications) and need to Insert/Update employee data to Oracle database staging tables.

Since SAP CPI doesn’t provide any kind of JDBC adapter that can connect On-premise Oracle database so far. Below is the approach used to integrate Oracle system via SAP CPI:

Fetch data from SuccessFactors Employee Central using SuccessFactors Adapter in SAP Cloud Platform Integration (CPI) and use file mechanism to get the data consumed in Oracle system.

System Diagram:

Above System Diagram explains each block:

  • Data would fetch from SuccessFactors Employee Central into SAP CPI.
  • Put all Validation and Updation as per requirement in message mapping, xslt mapping or groovy scripting on the data.
  • Generated XML from SAP CPI would be sent to SFTP server after conversion into CSV.
  • Loader Programs are used for consuming the files which are generated at SFTP in to Oracle database.

 

Sample Iflow:

 

SuccessFactors Employee Central Sample Compound Employee Query in SAP CPI:

You can also use odata v2/v4 call for fetching the data from Successfactors. We use the Compound Employee as per our requirement.

Message Mapping:

Source side, compound employee schema will be generated automatically in SAP CPI from Compound Employee Call.

Target Side create the schema as per requirement.

Groovy scripts are used for logging the output at each step.

SFTP:

For OnPremise SFTP, we need to whitelist the required IP range of CPI Tenant in the Client Firewall.

After that we can send the data to SFTP server by deploying knownhost and SFTP credentials into the Security material of Tenant.

Oracle DB:

From SFTP server we are fetching data files in csv format into Oracle Db using Shell script. After that Loader program will consume the files into Staging Tables of Database.

In a similar way, Wrapper Programs (Custom Programs written to load the data from Oracle legacy to Oracle ERP System) were written for insertion/updation of data into Oracle ERP system.

Monitoring in CPI:

After deploying the iflow, we can check the Message Processing Logs under All Integration Flows in Monitoring Tab of SAP CPI Tenant.

To test this interface, you need to SFTP server and Oracle database (For Loader Program)

Happy Learning!!!

1 Comment
You must be Logged on to comment or reply to a post.
  • Usually I never comment on blogs but your article is so convincing that I never stop myself to say something about it. You’re doing a great job, Keep it up