Ansicht
Dokumentation

ECPAO_VC_MAP - Define Field Mapping for Employee Data

ECPAO_VC_MAP - Define Field Mapping for Employee Data

ABAP Short Reference   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you map ERP fields and SAP SuccessFactors Employee Central fields. To do this:

  • You create at least one transformation template group. A transformation template group bundles all field mappings that you want to use when transferring data. This is the entity that you specify on the selection screen of the data extraction program. From the transformation template group, the program determines all information it needs to map ERP fields and Employee Central fields.
  • You create at least one transformation template for your transformation template group. The transformation template groups information from the ERP system that belongs together logically. It is the ERP counterpart of the Employee Central template.
  • You define a primary mapping for each of your transformation templates. This means you choose Employee Central fields from the Employee Central entity assigned to the transformation template, and you map suitable ERP fields to these Employee Central fields.
  • If you need an additional field mapping, for example for country-specific fields, you also define a secondary mapping.

  1. Define transformation template group
Enter a name and description and make the following settings:
  • Select your Employee Central instance ID.

  • To define whether you want to use the transformation template group for a CSV file-based or a Web service-based data transfer, select the communication channel (see Communication Channel).

  • Select the sample content that you want to use for your transformation template group (see Sample Content ID). We provide sample content for different use cases. For a detailed description of the use cases see Sample Content Description.

  • Specify an earliest transfer date (see Replication Cutoff Date). This option is mandatory only when you are replicating the data from EC using Business Integration Builder.

  • Select the Enable for Delta Replication checkbox to specify whether the transformation template group should be used for delta replication (see Is Considered in Delta Replication). Note that you can select this checkbox for one transformation template group only.

  1. Define transformation template. You can either create a new transformation template or you can use the Copy Sample Content button to save all the configurations: Primary Mapping, Secondary Mapping, Generic Value Conversion, and Country Specific Value Conversion configuration details for the relevant EC entities based on the chosen sample content version at each transformation template group level. You need to click on the save button to save all the configurations.
You can also define one or more transformation templates and assign them to your transformation template group.
For each transformation template, make the following settings:
  • Enter a name and description.

  • Set the template to Active to actually use it for data extraction (see Is Active).

  • If the Employee Central entity is effective dated, specify for the template if infotype records that contain the same data for the same employee but refer to different time periods are to be merged for data transfer (see Do Not Merge Time Periods of Identical Infotype Records).

  • Select the Employee Central template that is the counterpart of the transformation template (see EC Entity).

You can only select Employee Central entities that correspond to the communication channel you have defined for the transformation template group.
Note
If you want to map managers from the ERP field to Employee Central, you need a separate transformation template for each type of manager.
  1. Define primary mapping
For each transformation template, define the list of Employee Central fields to be assigned. To do so, you can use the sample content that you've selected for your transformation template group.
Choose Show Sample Primary Mapping and Show Sample Secondary Mapping to check which mappings are available for the sample content you have selected. Choose Copy Sample Contentto copy the sample content and adapt it if necessary. For more information see Using the Sample Content.
To define a custom field mapping, make the following settings for each field:
  • Select the Employee Central field from the value help.

Note
If an Employee Central field is no longer available after the last run of the metadata import program, it is marked as Deleted. For more information, see Field Is Deleted in EC.
If the field is required in the Employee Central data model, it is marked as Required in EC. For more information, see Is Required).
  • Choose the mapping mode and make the additional settings according to the selected mapping mode (see Mapping Mode).

Some infotypes require a special processing:
Repetitive mapping: If you enter an infotype such as Basic Pay (0008), for which a repetitive mapping is needed, you can't make entries in the Infotype Field field. Instead, the Repetitive Field field is displayed. Here you can select the infotype field for which you want to use a repetitive mapping. For more information see Field of Repetitive Structure for Special Processing.
Date type mapping: If you enter the Date Specifications (0041) infotype, you can't make entries in the Infotype Field field. Instead, the Date Type field is displayed. Here you can select the date type that you want to map. For more information see Input Help Value for Field Mapping.
  • If the value from the ERP field needs to be converted, enter the value mapping entity you have defined in the V_ECPAO_VALUENTY Customizing view (see Define Value Mapping Entities). Then choose Define Value Mapping Entries to enter the ERP and Employee Central values that you want to map.

Note
If you choose Define Value Mapping Entries, you go to the V_ECPAO_VALENTY view, which is also available in the Define Value Mapping Details Customizing activity. If you have already defined entries there for the value mapping entity, you will see them here.
If you use the secondary mapping and enter a value mapping entity there, this entity is used instead of the value mapping entity assigned in primary mapping. If no value mapping entity is assigned in secondary mapping, the one from primary mapping is used.

  1. Define secondary mapping
You can also define a secondary mapping. To do so, you can use the sample content that you've selected for your transformation template group. Standard secondary mappings are available for the countries that are supported by Employee Central Payroll. Choose Show Sample Secondary Mapping to check which sample mappings are available.
To define a custom secondary mapping, make the following settings:
  • Option 1: You have specified a linking field in the primary mapping, for example Country Key (LAND1) from the Addresses (0006) infotype

In this case, in the first column of the view, you can select the country for which you want to define a specific mapping. The infotype and subtype columns are filled automatically with the values you have defined in the primary mapping. You can also fill them in here if you haven't defined them in primary mapping. In the Infotype Field column, you can select from the fields that are available for the country key you have specified. If the value from the infotype field needs to be converted, enter a suitable value mapping entity.
This way, you can map different ERP fields from the same infotype to different Employee Central fields, based on the country key. The Employee Data Extraction program checks the country key defined for an employee and uses the field mapping you have defined for this country key. If no specific field mapping is available for a country key, the program uses the primary field mapping instead.
  • Option 2: You have not specified a linking field in the primary mapping

In this case, in the first column of the view, you can select the country grouping for which you want to define a specific mapping. You can then enter any country-specific infotype or subtype and the corresponding infotype field to be mapped to the Employee Central field. The other settings are the same as for option 1.
The Personal Data (0002) infotype, for example, can have country-specific fields stored in country-specific infotypes for Brazil, Japan, and so on. You can use the country grouping to map such infotype fields to the same Employee Central field. Based on the country grouping stored for an employee, the program Employee Data Extraction uses the field mapping you have defined for this country grouping. If no specific field mapping is available for a country grouping, the program uses the primary field mapping instead.
  1. Define generic value conversion
You can perform the generic value conversion for the EC fields when the EC value format is different from the ERP value format. For each EC field, create a new entry.
  • Enter the Sequence number. Order of operations are based on this number for multiple actions.

  • Choose the conversion rule.

  • Enter the parameter 1 for the rule (Function of parameter depends on rule that you have selected from the drop down list box)

  • Enter the parameter 2 for the rule (Function of parameter depends on rule that you have selected from the drop down list box)

  • Enter the parameter for the EC field ID.

  • Choose the conversion of field to be performed to EC.

  1. Define value conversion based on linking field
Here you can decide the value conversion based on the linking field as mapped in the field mapping table.
  • Choose the country for which you need to perform the conversion.

  • Enter the Sequence number. Order of operations are based on this number for multiple actions.

  • Choose the conversion rule.

  • Enter the parameter 1 for the rule (Function of parameter depends on rule that you have selected from the drop down list box)

  • Enter the parameter 2 for the rule (Function of parameter depends on rule that you have selected from the drop down list box)

  • Enter the parameter for the EC field ID.

  • Choose the conversion of field to be performed to EC.

To perform a custom value conversion based on the linking field, make the following settings:
  • Option 1: You have specified a linking field in the primary mapping, for example Country Key (LAND1) from the Addresses (0006) infotype. This way, you can perform the value conversion for different EC fields, based on the country key. The Employee Data Extraction program checks the country key defined for an employee and uses the field mapping you have defined for this country key.

  • Option 2: You have not specified a linking field in the primary mapping.

In this case, in the first column of the view, you can select the country grouping for which you want to perform a value conversion.
The Personal Data (0002) infotype, for example, can have country-specific fields stored in country-specific infotypes for Brazil, Japan, and so on. This way you can perform the value conversion based on the country grouping.

In addition to defining the mapping using this view cluster, you can adapt the extraction logic using the Change of Mapping Result for Data Replication to EC (EX_ECPAO_ERP_EMP_DATA_MODIFY) BAdI. For more information, see BAdI: Change of Mapping Result for Data Replication to EC.






Vendor Master (General Section)   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 17204 Date: 20240523 Time: 153504     sap01-206 ( 258 ms )