Defining Mapping Types for Employee Data Replication

Objective

After completing this lesson, you will be able to define mapping types for replication of employee data.

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.comSAP SuccessFactors Employee Central Integration with SAP Human Capital Management for SAP S/4HANAImplementationImplementing 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.comSAP SuccessFactors Employee Central Integration with SAP Human Capital Management for SAP S/4HANAConfigurationSample Field and Value Mapping

Summary

  1. Grant necessary SAP S/4HANA permissions and activate relevant inbound and outbound web services for successful data replication and processing from Employee Central, referencing SAP Help documentation for roles and service lists.
  2. Enable the new infotype framework for PA/PD integration to improve organizational data replication performance and message handling; note that dynamic actions are not supported in Business Integration Builder (BIB)-based replication.
  3. Configure integration between Organizational Management (OM) and Personnel Administration (PA) to synchronize organizational assignments and relationships, ensuring consistent updates across infotype 1001 and 0001.
  4. Decide and configure FTSD for initial data replication, determining which records are transferred from Employee Central; use country/region or assignment-specific FTSDs for phased go-live.
  5. Choose between organizational assignment or organizational object replication for position relationships, ensuring settings do not duplicate relationships and considering pros and cons of each approach for hierarchy and relationship management in SAP S/4HANA.