Setting Up SAP SuccessFactors for Replication

Objective

After completing this lesson, you will be able to set up SAP SuccessFactors for replication.

Data Replication from SAP SuccessFactors Employee Central to SAP S/4HANA: Integration Scenario

Data replication from EC to SAP S/4HANA – Overview of technical components of the replication process
SAP SuccessFactors Employee Central Master DataSAP Cloud Integration - ConnectSAP S/4HANA Transform and Process
  • Master system for HR Core employee master and organizational assignments
  • Compound Employee API (Application programming Interface)
    • Extracts employee data including organizational assignment out of Employee Central
  • Facilitates the technical connectivity
  • Standard package SAP SuccessFactors Employee Central to ERP and process Employee Central to ERP Employee Data and Organizational Assignment
  • Lean middle ware content for connectivity, i.e. authentication, session handling, protocol conversion
  • Business Integration Builder (BIB)
    • Comprises of Tools to set up the Data replication such as configuration of field and value mapping
    • BIB comprises the software for running the business logic and mapping logic
  • Web Services for triggering and receiving EC data through Compound API
Diagram representing the integration scenario. Details are explained in the following text.

The integration scenario in the scope of this training is the standard integration for replicating employee master data and employee organizational assignments from SAP SuccessFactors Employee Central to SAP S/4HANA.

The integration is based on the Business Integration Builder (BIB).

The corresponding required technical elements and tools are delivered as part of our SFSF EC S4 HCM INTEGRATION (ECS4HCM) add-on.

Data Extraction and Processing: Process Flow of Employee Data Replication from Employee Central

The process for replication of employee master data and employee organizational assignments from Employee Central has steps in three systems interacting with each other:

  • The SAP S/4HANA system.
  • The cloud-based middleware, SAP Cloud Integration.
  • SAP SuccessFactors Employee Central.

Data extraction and processing. The diagram shows the process flow of employee data replication from Employee Central. The process is explained in the following text.

Data Extraction and Processing–Steps of Process Flow

  1. The query program in the SAP S/4HANA system, Create and Execute Employee Master Data and Org. Assignment Query (ECPAO_EE_ORG_REPL_QUERY) calls the outbound Web service getEmployeeMasterDataAndOrgAssignmentBundleReplicationQuery. While calling the outbound Web service, the query program reads the parameters that are defined in Customizing. It also updates the Administration of Employee Master Data and Org Assign. Query (ECPAO_QRY_ADM) table.
  2. The outbound Web service getEmployeeMasterDataAndOrgAssignmentBundleReplicationQuery sends the query to the middleware.
  3. The middleware requests the corresponding data from Employee Central using the CompoundEmployeeAPI.
  4. The middleware calls the inbound Web service EmployeeMasterDataAndOrgAssignmentBundleReplicationRequest in the SAP S/4HANA system and passes over the data it has received from Employee Central in packages.
  5. The inbound Web service EmployeeMasterDataAndOrgAssignmentBundleReplicationRequest stores the data in the form of replication requests in the employee staging area.
  6. When it stores a new replication request in the staging area, the SAP S/4HANA system triggers the outbound Web service EmployeeMasterDataReplicationConfirmation_Out.
  7. The outbound Web service EmployeeMasterDataReplicationConfirmation_Out sends a confirmation to the middleware to inform the Employee Central Data Replication Monitor that the replication requests are waiting to be processed.
  8. The middleware updates the Employee Central Data Replication Monitor.
  9. Once the last package transferred by the middleware has arrived in SAP S/4HANA, the middleware sends a final notification to SAP S/4HANA.
  10. The inbound Web service EmployeeMasterDataAndOrgAssignmentBundleReplicationRequest updates the query administration tables and triggers the SAP_SFIOM_EE_ORGAS_RPPQ_CREATED event.

  11. The processing program Process Employee Replication Requests (ECPAO_RPRQ_EE_PROCESSING) runs, which is scheduled with the SAP_SFIOM_EE_ORGAS_RPPQ_CREATED event as a start condition.

    The program reads the staging area to determine the updates to be made in the SAP S/4HANA infotypes. Then it creates or updates corresponding infotype records in Personnel Administration and Organizational Management using the key mapping and the settings you've made in the Business Integration Builder.

    The processing program also updates the key mapping if necessary and writes messages to the application log.

  12. When it is finished updating, the processing program triggers the outbound Web service EmployeeMasterDataReplicationConfirmation. The service inform the Employee Central Data Replication Monitor for each employee whether the data transfer was successful, has errors, or is still pending.
  13. The outbound Web service EmployeeMasterDataReplicationConfirmation_Out passes over the corresponding Successful, Failed, or Pending confirmation to the middleware.
  14. The middleware updates the Employee Central Data Replication Monitor.
Diagram representing the implementation considerations. Details are explained in the following text.

Implementation Considerations Data Replication

The following are implementation considerations for the data replication scenario.

Different Employee Data Model in SAP SuccessFactors Employee Central Compared to SAP S/4HANA.

  • SAP SuccessFactors Employee Central comprises of the following:
    • One person object containing information shared across employments.
    • One/multiple employments associated to one person object containing contractual employee data, such as compensation data, job information and so on.
  • Data replication logic uses the same employment equivalent to the SAP S/4HANA / ERP Personnel number.
  • In Employee Central, country/region-specific data is often stored on person object level such as country/region-specific personal information. Such data do not have a clear relation to the employment.
  • In SAP S/4HANA, all data have a validity period whereas in Employee Central data could be effective-dated but also noneffective dated, which means they exist but do not have a validity period.

Different Handling of HR processes

Different handling of HR processes such as the following:

  • Global assignment
  • Concurrent Employment
  • Dependents
  • Organizational structures
  • SAP SuccessFactors is a state-of-the-art HCM solution designed for running in the cloud.

Strategy for Specifying as of When EC Data Shall Be transferred

Decide on ‘as of when’ date based on your needs such as the following:

  • Financial year
  • Payroll recalculation date
  • and so on

Create the Replication Target System Object in Employee Central

ExerciseStart Exercise

Employee Central Checks for Employee Central ERP Replication

Screenshots of the Check Tool screen in the Admin Center. The System Health tab is selected and a sample replication is highlighted.

We recommend ensuring that all available Employee Central checks for our data replication are successful.

  • Choose the Check Tool tool in the SAP SuccessFactors EC Admin Center.
  • Choose as application Employee Central ERP Replication.
  • If you leave the result type = Empty, you can view all results of our available consistency checks.

The screen example displays the EC consistency check, which ensures that the EC data model is in sync with the SAP S/4HANA data model. In our example, the HRIS fields are not in sync, and you can view a list of all fields that are inconsistent. This allows you to easily identify where you must make changes in your EC data model.

Preparing for the Export of SAP SuccessFactors Metadata

Screenshot of the Import and Export Data screen with correct permission selected.
  • Check if you have the correct users with the correct authorizations in place.
  • For example, grant your technical user appropriate permission to export EC metadata.
  • Have you exported the latest EC meta data? If not, go ahead and export the EC employee and picklist metadata that you’ll need for a later import to your SAP S/4HANA system.
  • Starting an implementation project with stable metadata is a smart move. It ensures a smooth, disruption-free implementation.

Remember, you can always export and copy the metadata again to accommodate changes to data and processes. For instance, if there are new fields needed because of legal changes in your tax reporting.

Summary

  • Data replication uses SAP Cloud Integration middleware and the Business Integration Builder (BIB) to connect Employee Central and SAP S/4HANA, leveraging standard APIs and web services for secure and efficient data exchange.
  • The replication process involves extracting employee master data and organizational assignments from Employee Central using Compound Employee API, transferring it via middleware to SAP S/4HANA, where staged data is processed and updated in relevant infotypes.
  • The process includes confirmation messages and status updates, ensuring that successful, failed, or pending transfers are tracked in the Employee Central Data Replication Monitor.
  • Employee Central manages data with person objects and multiple employments, while SAP S/4HANA uses personnel numbers and validity periods, requiring careful mapping and handling of country-specific and effective-dated data.
  • Special attention is needed for HR processes like global assignments, concurrent employment, and dependents, as well as strategic decisions on transfer dates (e.g., financial year or payroll recalculation) for accurate and compliant data migration.

Learning

SAP FacebookSAP YoutubeSAP LinkedIn