Preparing Systems for Replication from SAP SuccessFactors Employee Central to SAP S/4HANA

Objectives

After completing this lesson, you will be able to:
  • Set up SAP SuccessFactors for replication
  • Set up integration package and iflows for replication in SAP Cloud Integration
  • Set up SAP S/4HANA for replication
  • Define mapping types for replication of employee data

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.

Integration Flow Management in SAP Cloud Integration

Configure the integration flow for replication of employee master data and employee organizational assignments from SAP SuccessFactors Employee Central in your customer workspace in SAP Cloud Integration.

Prerequisites

You've copied the SAP SuccessFactors Employee Central Integration with SAP ERP or SAP S/4HANA: Employee and Organizational Data integration package to your customer workspace. Refer to the following task for the steps to copy, configure, and deploy an integration flow.

ExerciseStart Exercise

Configure and Deploy the Relevant Integration Flows

Hint

Refer to the following SAP help documentation for the detailed steps to configure integration flows relevant for replication of employee data from SAP SuccessFactors Employee Central to SAP S/4HANA. https://help.sap.com/docs/SAP_SUCCESSFACTORS_EC_S4_HCM_INTEGRATION/ff6b495d894a4685accf7e4bfa75da1b/98a80a25ebc0499b9f907ccc2de071b0.html

Endpoint URLs Required for Outbound Communication from SAP S∕4HANA

Determine the endpoint URLs of the integration flows in SAP Cloud Integration. The SAP S∕4HANA administrator enters these URLs when activating the SAP S∕4HANA outbound web services, so that SAP S∕4HANA is able to address the middleware.

Procedure

  1. Log on to the SAP Cloud Integration web UI.
  2. Choose Operations View from the top-level menu on the left.
  3. Choose Manage Integration Content → All.
  4. Select the following integration flows one by one and mark down the URL shown on the Endpoints tab:

    • Replicate Employee Master Data and Org. Assignments from SAP SuccessFactors Employee Central to SAP ERP or SAP S4HANA

    • Send Confirmations from SAP ERP or SAP S4HANA to SAP SuccessFactors Employee Central

    Hint

    You can also note the URLs from the following integration flows as they will be needed for setup of additional outbound web services.

    • Replicate Organizational Objects from SAP SuccessFactors Employee Central to SAP ERP or SAP S4HANA

    • Replicate Generic Data from SAP SuccessFactors Employee Central to SAP ERP or SAP S/4HANA Using the OData API

    The SAP S∕4HANA uses these URLs when setting up the outbound web services in SAP S∕4HANA.

    Note

    The URL looks like this: https://[runtime URL of your SAP Cloud Integration environment]/cxf/[sender address]

    The sender address part is the suffix you enter in the Address field of the sender in SAP Cloud Integration when setting up the integration flow. For example: EC_to_ERP_Master_Data_And_Org_Query

    To get the complete endpoint URL, configure and deploy the integration flow first, then copy the URL from Manage Integration Content.

Permissions in SAP S/4HANA to Replicate and Process Data

Grant the necessary permissions in SAP S/4HANA to the various users required to replicate and process data.

Permissions

Refer to the following SAP help documentation for the required permissions and available template roles:https://help.sap.com/docs/SAP_SUCCESSFACTORS_EC_S4_HCM_INTEGRATION/ff6b495d894a4685accf7e4bfa75da1b/258eefb69ec042fda65e7babb1354a44.html

SAP S∕4HANA Inbound and Outbound Web Services

Enable the SAP S∕4HANA inbound Web Services used by data replication from Employee Central.

Inbound Web Services

By activating the inbound Web services, you enable the SAP S∕4HANA system to request data from Employee Central, using the integration flows in the middleware. Refer to the following SAP help documentation for a complete list of the relevant inbound Web Services: https://help.sap.com/docs/SAP_SUCCESSFACTORS_EC_S4_HCM_INTEGRATION/ff6b495d894a4685accf7e4bfa75da1b/5efa81ead37b438aba7cacd04e3b5c72.html

Outbound Web Services

By activating the outbound Web services, you enable the SAP S∕4HANA system to query data from and send confirmations to Employee Central, using the integration flows in the middleware. Refer to the following SAP help documentation for a complete list of the relevant outbound Web services: https://help.sap.com/docs/SAP_SUCCESSFACTORS_EC_S4_HCM_INTEGRATION/ff6b495d894a4685accf7e4bfa75da1b/e15e547f021447b894b437a520280b90.html

Refer to the following task for the steps required to enable and test an outbound Web service.

ExerciseStart Exercise

New Infotype Framework for Integration Between Organizational Management and Personnel Administration

Determine that the new infotype framework is to be used in PA/PD integration for organizational data that was replicated from Employee Central, to improve the performance and allow for better message handling in the replication processes.

Context

If you've activated the integration between Organizational Management and Personnel Administration (PA/PD integration) in your SAP S∕4HANA system, the organizational data is synchronized between the infotypes Relationships (1001) and Organizational Assignment (0001). Using the new infotype framework for this synchronization improves performance and enables better message handling in the replication processes. Therefore, the usage of the new infotype framework is a required prerequisite for the replication of organizational objects and organizational employee assignments from Employee Central.

Note

The new infotype framework doesn't support dynamic actions. Since the Business Integration Builder (BIB) uses the new infotype framework, you can't use dynamic actions in BIB-based data replication from Employee Central.

Procedure

  1. Go to Customizing for the Business Integration Builder and choose Data Replication from Employee Central → Employee Data → Employee Organizational Assignment → Enable Use of New Infotype Framework When Processing Replicated Org. Data or Data Replication from Employee Central → Organizational Objects → Enable Use of New Infotype Framework When Processing Replicated Org. Data.
  2. Check whether the following entry exists.
    GroupSem.Abbr.Value Abbr.Description
    PLOGINITFXFor example: Update Infotype 0001 Using New Infotype Framework
  3. Create the entry if it doesn't exist and transport the new entry.

Enable and Test the SAP S/4HANA Outbound Web Services

ExerciseStart Exercise

Integration Between Organizational Management and Personnel Administration in SAP S∕4HANA

Set a T77S0 switch to enable integration between Organizational Management and Personnel Administration (PA/PD integration) in your SAP S∕4HANA system.

Context

You can enable PA/PD integration for all employees. You can also restrict PA/PD integration to subsets of employees using the Control: Integration of Personnel Planning and Master Data Management (PLOGI) feature.

Procedure

  1. Go to customizing for Personnel Management and choose Organizational ManagementIntegrationIntegration with Personnel AdministrationSet up Integration with Personnel Administration.
  2. Choose Basic Settings.
  3. Choose New Entries and enter the following data:

    Change View T77S0

    GroupSem.Abbr.Value Abbr.Description
    PLOGIORGAXEnter a user-defined description, such as: Integration Switch: Organizational Assignment
  4. Save your entry and go back.
  5. Optional: Choose Participate in Integration to maintain the PLOGI feature.
  6. Save and transport your entries.

You can use integration between Organizational Management (OM) and Personnel Administration (PA), also called PA/PD integration, in your SAP S∕4HANA system to synchronize organizational data between Organizational Management and Personnel Administration.

PA/PD integration synchronizes organizational data, such as position, job, organizational unit, or cost center, between the Relationships (1001) infotype in Organizational Management and the Organizational Assignment (0001) infotype in Personnel Administration.

The Relationships infotype stores the relationships between the employee and the position (P–S) and all other position relationships, such as position to organizational unit (S–O), position to job (S–C), or position to cost center (S–K), for Organizational Management.

The Organizational Assignment infotype stores the assigned position, job, organizational unit, and cost center of the employee for Personnel Administration.

The Relationships infotype is updated either by the replication of employee data (which includes employee organizational assignments) or by the replication of organizational objects from Employee Central. Replication of organizational assignments as part of employee data replication always creates the relationship between the employee and the position. If you configure your SAP S∕4HANA system to exclude position relations from employee data replication, you can replicate the organizational objects together with their associations from Employee Central. If you make this setting, the organizational object replication creates the other position relationships. Otherwise, the replication of organizational assignments creates these relationships.

The Organizational Assignment infotype is updated either by PA/PD integration or–if PA/PD integration isn't enabled–by the replication of employee master data from Employee Central. See the SAP help documentation for more details.

Full Transmission Start Date for Data Replication from Employee Central

Prepare for integration between Employee Central and SAP S∕4HANA by deciding on the date when the data replication is to start.

What Is the FTSD?

The full transmission start date (FTSD) is the date from which the data transfer from Employee Central to the SAP S∕4HANA system begins. It is used to determine from which start date on data records are provided. Only records that are valid on or after the FTSD are extracted from Employee Central. Processing in SAP S∕4HANA updates the records of all corresponding infotypes only if their validity begins at or after the FTSD.

The choice of the specific FTSD has consequences for existing data in SAP S∕4HANA. During the initial full load from Employee Central to SAP S∕4HANA, existing records in SAP S∕4HANA are cut at the FTSD if they have changes after this date. This can trigger consecutive actions on the SAP S∕4HANA side. Records that were unchanged after the FTSD aren't split by the initial load.

Context

Deciding on the full transmission start date (FTSD) is an important step. We recommend that you work it out in an early project phase.

Note

For specific examples and recommendations on how to choose the FTSD refer to the SAP help documentation.

Procedure

  1. Choose the date when the data replication from Employee Central to SAP S∕4HANA is to start, considering the implications we've listed in this document.
  2. Enter the full transmission start date you've chosen as the earliest transfer date of the transformation template groups that you use for employee data replication and replication of organizational objects from Employee Central.
  3. Optional: Configure a country/region-specific FTSD for employee data for selected countries or regions if you have specific requirements such as a phased go-live.
  4. Optional: Configure an assignment-specific FTSD for selected employees if the overall or the country/region-specific FTSD don't apply to them.

Results

The SAP S∕4HANA system always uses the general FTSD when querying the data from Employee Central. A country/region-specific and an assignment-specific FTSD can be defined for the same personnel number, in addition to the general FTSD that's stored for the template group. If so, the latest of the three dates is used for processing the data in SAP S∕4HANA.

Next Steps

If you change the full transmission start date after you've already replicated the data, the following extra steps are required:

  • If you move the date into the past, ensure that you initiate a full load of the data from Employee Central. To do so, run the programs Create and Execute Employee Master Data and Org. Assignment Query (ECPAO_EE_ORG_REPL_QUERY) and Create and Execute Organizational Object Replication Query (RH_SFIOM_ORG_OBJ_REPL_QUERY) with the option Initiate Full Load selected.

  • If you move the date into the future, no full load is required. However, you must ensure that all changes made before the new FTSD have been replicated successfully.

Organizational Assignment or Organizational Object Replication to Create Position Relationships in SAP S∕4HANA

You can create relationships of employee positions to other objects (such as departments or job classifications) and to other positions (such as matrix manager positions) from different sources in Employee Central using different replication approaches.

You can configure position relationships in SAP S∕4HANA to be created by the replication of organizational assignments and by the replication of organizational objects from Employee Central. Both options have their pros and cons. However, you must prevent the same position relationship from being created by both replications. That is, the settings you make for organizational assignment and for organizational object replication can complement each other, but must not duplicate each other.

Position relationships in SAP S∕4HANA can originate either from Job Information or from Position Management in Employee Central.

  • Using organizational assignment replication, you can create position relationships based on the employee's Job Information in Employee Central.

    If you want to use our sample content for organizational object replication, the appropriate sample content for this option is Organizational Data EC to ERP: Job Info Relationships (OM_WS_1).

  • Using organizational object replication, you can create position relationships based on Position Management in Employee Central.

    The appropriate sample content for this option is Organizational Data EC to ERP: Position Mgmt Relationships (OM_WS_3).

Note

There's also a "mixed" approach, which we don't recommend, however. "Mixed" means: If a position is staffed in Employee Central), the position relationships are created based on Employee Central Job Information using the organizational assignment replication process. If a position is vacant, you replicate position relationships from Employee Central Position Management using the organizational object replication process. Don't use this "mixed" scenario if you've enabled replication of shared positions from Employee Central. It doesn't work for shared positions.

The appropriate sample content for this "mixed" option is Organizational Data EC to ERP: Job Info Relationships and Vacancies from Position Mgmt (OM_WS_2).

Job relationships of positions in SAP S∕4HANA (such as matrix manager relationships) can originate either from Job Relationships or from composite child objects in Employee Central.

  • Using organizational assignment replication, you can create matrix relationships of positions based on the employee's Job Relationships in Employee Central.

  • Using organizational object replication, you can create matrix relationships of positions based on the association of parent objects and composite child objects in Employee Central.

Here are some pros and cons of the options.

Replication ProcessAdvantagesDisadvantagesFurther Considerations
Organizational assignments

You don't need to synchronize Job Information to Position Management in Employee Central because all employee and organizational data is replicated from Job Information.

Configuring the organizational hierarchy and filling extra fields is easier if you use configurable organizational assignment.

Configuration is less flexible because you can't use secondary (conditional) mapping and generic value conversion when configuring transformation template groups.Relationships are delimited in the Relationships (1001) infotype when an employee leaves the assigned position or is terminated. This means that SAP S∕4HANA doesn't consider the relationships of a position if the position doesn't have an incumbent in Employee Central.
Organizational objectsConfiguration is more flexible because you can use secondary (conditional) mapping and generic value conversion when configuring transformation template groups.

You must synchronize Job Information to Position Management in Employee Central. For more information, refer to Defining "Job Information to Position" Synchronization.

Configuring the organizational hierarchy and filling extra fields is more complex.

Relationships aren't delimited in the Relationships (1001) infotype when an employee leaves the assigned position or is terminated. This means that SAP S∕4HANA retains the relationships of a position even if the position doesn't have an incumbent in Employee Central.

Disable creation of the corresponding position relationship with organizational assignment replication if you create the relationship based on organizational object replication.

Tools in Business Integration Builder to Set Up Data Mapping

To set up the data mapping, we offer the following tools in the Business Integration builder. These tools help you to easily map your data for seamless integration.

Field Mapping

Field mapping allows you to specify how Employee Central fields are mapped to SAP S/4HANA infotype fields. General mapping is specified using the primary mapping and localized mapping through the secondary mapping.

Value Mapping

Value mapping allows you to specify how Employee Central field values (EC picklists) are mapped to help values of SAP ERP infotype fields.

Value Conversion rules

The standard value conversion rule operations allow you to convert values of EC fields to the correct format required by the mapped SAP S/4HANA field.

Cloning

The cloning feature allows you to reuse a field mapping specified for one infotype for its multiple subtypes.

Screenshot highlighting the Define Value Mapping selections. Field Mapping for Employee Data Replication from Employee Central.

Repetitive Structure Mapping

How Repetitive Structure Mapping Works

Repetitive structure mapping is used for infotypes such as Basic Pay (0008) or Cost Distribution (0027) that use a repetitive structure.

In this kind of infotype, data is entered in table form. The user can enter the data such as wage types or cost distribution items several times. The input line for the data is available several times on the input screen. The structure of the input line is stored in the infotype structure, and the individual fields are numbered.

Without repetitive structure mapping, to map the fields separately to the corresponding Employee Central field IDs, you would have to create a separate SAP transformation template for each repetitive field. For example, for each wage type or cost distribution item that can be entered.

If you use repetitive structure mapping, you only need a single SAP transformation template, which maps the repetitive fields once. There's no need to create several SAP transformation templates. The data extraction program extracts the wage types or cost distribution items that are stored in an employee's infotype using the field mapping you have defined once.

Note

For more details and examples of Repetitive Structure Mapping, refer to the SAP help documentation.
List of delivered sample EC entities. The list shows the EC Entity in ERP and the Entity name in EC.

We deliver more than 20 predefined EC entities with standard settings that are technically required for the data replication, such as the following:

  • You can assign a Compound Employee API segment. This segment contains the employee data associated with it.
  • Characteristic of EC objects, such as whether the data has a validity date and is effective-dated, can be specified by specifying the corresponding EC start and end date fields.
  • Infotype-specific settings let you specify how infotypes are processed during the replication. For example, infotypes with table structures need special processing to handle the table structures, and infotype subtypes with different time constraints need special processing to handle subtypes with different time constraints.

You can also create your own EC entities to cover custom EC entities, which you must replicate to standard or custom infotypes.

Screenshot of basic settings in EC entity. The features are explained in the following text.

EC entity standard basic settings are the following:

  1. EC records of entity pay component recurring always have a start date and that’s why this is an effective-dated entity. Hence, the flag Effective dated is and must be marked.
  2. In the fields Start Date in EC and End Date in EC, the technical name of the EC start and end date fields are specified. Both fields are used during the infotype replication processing to determine the begin and end date of the corresponding mapped infotype record.
  3. The corresponding CE API segment is paycompensation_recurring.
  4. The pay component recurring information is transferred to SAP S/4HANA Infotype Basic Pay 0008.

    Note

    • Infotype 0008 consists of a table structure that contains all wage type information. We have a special replication logic available to handle this.
    • Therefore, if you want to replicate pay components to this infotype under Infotype-specific settings, it is necessary to specify the processing mode as Repetitive Structure Mapping.

Data Type Mapping

Mapping Types

You can replicate data from different EC entities, which can have different processing modes (no specific mappings) mapped to the same infotype. Also, this enables you to process different time constraints data at the subtype level.

Note

See descriptions of various available mapping types on: help.sap.com → SAP SuccessFactors Employee Central Integration with SAP Human Capital Management for SAP S/4HANA → Implementation → Implementing Data Replication from Employee Central
Sample mapping content, showing: EC Entities in SAP S/4HANA / ERP and SAP S/4HANA Infotypes.

Sample mapping content is available for more than 20 predelivered standard EC entities and more than 15 standard SAP S/4HANA infotypes with focus on infotypes required by the SAP S/4HANA payroll & tax process.

Generic mapping and localized mapping content is available for more than 28 countries/regions.

The following are details about our delivered sample Field and Value mapping content:

  • Check out our predelivered sample content and identify the sample content that matches your scope.
  • Details are available on: help.sap.com → SAP SuccessFactors Employee Central Integration with SAP Human Capital Management for SAP S/4HANA → Configuration → Sample Field and Value Mapping

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn