Data Replication Process from SFSF to SAP R/3 - (Part I)

[former_member32685]

Hi everyone,

I am back with my new blog post to share my knowledge and experience on data replication process from SFEC to SAP ERP system. I wanted to share this blog post because many functional consultants may not have complete knowledge on technical side.

This blog post gives an overview on the data replication process with as CPI interface and other outbound interfaces from Employee Central to SAP R/3. Apart from that given more insight on SLG log and the data Replication Monitor in SF Employee Central with example to understand the data replication process.

1.Any data that has been added or changed in EC is sent to SAP via the data replication.

2.CPI uses an API to extract EC data, perform field mapping and standard code transaction.

3.CPI connects to SAP ERP PI and then forwards the replication message to PI.

4.PI (Integration server) handles protocol and encryption exchange and then forwards the message to SAP R/3 where the data load is processed.

5.If the SAP R/3 upload succeeds, a confirmation message is routed back to EC (the “reverse” trip). If the SAP upload is not successful due to whatever errors, a confirmation message is also routed back to EC with “Failed” status.

CPI Overview:

• CPI is SAP middleware for transferring data from SFSF to SAP R/3


• CPI uses SAP standard data mapping


• Middleware triggers replication at set time intervals (configurable).

Other outbound interfaces from Employee Central to SAP R/3

Other outbound interfaces from SFSF EC directly to 3^rd party system can be created using BOOMI/CPI/PI (Boomi /CPI are Cloud platforms and PI on premise)

• These interfaces need to be approved by client service/ITS for the support.


• A separate BOOMI Atom or CPI tenant needs to be put in place for these interfaces.

Replication error log monitoring

On the ERP side there are two monitoring tools that will help you identify errors that occur during the replication of employee master data. The tools cover different stages of the replication process.

Analyze Application Log

You can use the application log to monitor the replication of employee master data to SAP ERP system. It displays errors that occurred during SAP ERP inbound replication processing for employee master data. Examples of errors are unknown code values or missing mandatory field data.

You can use transaction SLG1 (evaluate application log) to access the application log directly)

Use the following selection parameters:

• Object: PAOC_SFI_PA


• External Employee ID (stored in IT709)


• User: XI_ADMIN

During the SAP ERP inbound processing, the data is processed, and the log captures all information, warning and error message. A selection criterion is provided for the error log class.

 Error log class:

• I: information(green)


• W: Warning(yellow)


• E: Errors(red)


• A: Stop (Stop Icon)


• S: Success(green)

Here is an example of error log for a selected (employee id)

Note that an information message gives detail on the Personnel number assigned to that External Employee ID.

Resolution:

From here you can navigate to the employee's Employment Information to change the event reason accordingly.

If you want to ignore the duplicate change the event reason from New Hire to Ignore Duplicate.

The above blog post, I have given a brief on replication process of employee master data from SuccessFactors Employee Central to an SAP ERP HCM system. I hope my blog post was helpful for functional consultants to understand the data replication process in SucessFactors and SAP R/3.

In my next blog will come back with more information Replication field mapping and terminology, Data mapping and back end configuration, Prerequisites, Permissions etc.,