How Repetitive Structure Mapping Works
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.
EC entity standard basic settings are the following:
- 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.
- 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.
- The corresponding CE API segment is paycompensation_recurring.
- 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.