Skip to Content
Technical Articles

What you always wanted to know about Address Data Replication to Employee Central Payroll

This Blog wants to provide some technical details regarding the different aspects of Address data replication within Employee Central Payroll using Point-to-Point Integration and help with some Tipps and Tricks to influence the replication with configuration means.

Within an Employee Central Payroll Scenario, Employee Central is the system of record. All HR events are managed in Employee Central. Payroll relevant data is either replicated to payroll or maintained in Employee Central using UI mashups. Please find more details within the SAP Help Introduction to Employee Central Payroll.

Caution:
In case you are running payroll within an ERP on-premise system being served with HR Master Data by Employee Central this is not the right Blog for you. Such a Core Hybrid called scenario is based on a middleware integration (SAP Cloud Platform) and must be configured with the Business Integration Builder (BIB).
In case you run an Employee Central Payroll scenario but still make use of BOOMI based integration this is as well not the right BLOG for you.


Setting the basis:

The mapping of the address fields available in Employee Central to the corresponding Employee Central Payroll fields can vary depending on the country of the address. For more information see respective section of the Country Specifics for Employee Central Payroll guide. Country independent information regarding data replication of Address Information to Infotype 0006 can be found here.

Before going further into any details of this data replication we must separate three types of SAP countries in which employees may have an address and the corresponding data replication scenarios.

  1. SAP Employee Central Payroll countries
    All countries for which SAP provides a (localized) Employee Central Payroll solution
  2. Address localized countries
    Countries that do not belong to group 1, but for which SAP provides the Address Information replication to Infotype 0006
  3. Other countries
  4. All other countries that do not belong to one of the groups above

The countries included in Group 1 and Group 2 usually reflect the EC Country Versions. Temporarily some differences might occur.


In general
, the Point-to-Point Integration supports data replication of Employees that are assigned to an Employee Central Payroll country, but it is as well a very common use case that employees who are assigned to an Employee Central Payroll country have an address in a non-Employee Central Payroll country.

And here we must separate the above-mentioned two additional groups of countries.

Only for the countries included in group 1 each country has its own standard mapping class. For all other countries the international address mapping class CL_HRSFEC_ADDR_MAPPING_99 is used.

For the countries belonging to the groups 1 and 2 a country specific standard address model is provided by SAP (as being a supported EC Country Versions) including a country-specific standard mapping of the address model.

For countries of group 3 one global address model is used on Employee Central (EC) and one generic mapping is implemented with a minimal set of international fields:(SAP help documentation of Version Q4 2018)

For further details please see the section Refining the Mapping of Address Information in the Employee Central Guide.


How the Point-to-Point Integration works in these cases:

Once a country is available in the customizing table of countries “T005” in Employee Central Payroll, the P2P replication tries to replicate this information. The data mappings are done via the available classes and mappings. In case an employee has an address in a country which is not included in T005 the replication fails with the message that the country is not supported. Note that if the values you enter differ from the values stored in Employee Central, you must enter the country-specific code value mapping (see corresponding section below) for the corresponding data type, e.g. REGION.

In case you need a country specific data replication for such a country it is required to define a custom class (like CL_HRSFEC_ADDR_MAPPING_99) and update table T77SFEC_ADR_IMPC to make use of the custom class.

With advanced extensibility, you can use Business Add-Ins (BAdI) to extend the SAP default logic for specific Infotypes.
In the IMG structure open SAP Customizing Implementation Guide:
à Personnel Management à Integration Settings for SuccessFactors Employee Central Payroll
à Extensibility à Business Add-ins for Point-to-Point Replication

This Customizing activity will lead you to the enhancement spot RSFEC_CE_MASTER_DATA_REPL, where you can find all the BAdIs you’ll need for Extensibility in a point-to-point replication scenario.


Field Mapping:

For country groups 1 and 2 a country-specific field mapping is provided by SAP in table HRSFEC_D_ADR_MAP. The table can be accessed by view V_HRSFEC_ADR_MAP:
(table content excerpt from Employee Central Payroll System with SAP_HR 608 SP64, EA-HR 608 SP64)

The Source Field Name is Field ID of the corresponding field in the Address Portlet in Employee Central, the Target Field Name is the corresponding the field of the structure PAD_SFEC_EMPLOYEE_ADDRESS_INFO.

The final mapping to the corresponding fields of Infotype 0006 then happens within the corresponding class (e.g. CL_HRSFEC_ADDR_MAPPING_99) within method MAP_PHYSICAL_ADDRESS (method PROCESS_ADDRESS implemented as entry point):
(coding excerpt from Employee Central Payroll System with SAP_HR 608 SP64, EA-HR 608 SP64)

When having a look at the SAP help documentation for US you will find some additional mappings:
(SAP help documentation of Version Q4 2018)

These mappings are not included in the mapping table HRSFEC_D_ADR_MAP as being generic mappings handled by the classes and methods mentioned above.

CAUTION:
Any adjustment to the content of table HRSFEC_D_ADR_MAP is a modification and you will be prompted with a corresponding warning message. Modifications are not allowed within SAP cloud solutions like Employee Central Payroll!

Code Value Mapping:

This has to be configured within the SAP Implementation Guide via path: Personnel Management àIntegration Settings for SuccessFactors Employee Central Payroll àAssignment of Code Values à For Point-to-Point Replication

The code value mappings are maintained in the table T77SFEC_CVMAPS for the countries where Employee Central Payroll is supported. E.g. for the Address Type SAP provides the following country independent mapping of the Address Type (address_type) from EC to the Subtype of Infotype 0006 (ANSSA):(table content excerpt from Employee Central Payroll System on SAP_HR 608 SP64, EA-HR 608 SP64)

If allowed (see settings in table T77SFEC_CVPROPC) the mapping can be enhanced with further customer specific mappings in table T77SFEC_CVMAPC as e.g.:

To replicate values of a custom fields or an SAP field provided with a custom Picklist the value mappings must be maintained in the table T77SFEC_CVMAPC for the replication to be successful.

How to deal with Picklists for Group 2 and 3 countries?

You might run into data replication issues when mapping EC based free text fields to an Employee Central Payroll field that requires maintenance of predefined values (no free text field).

EC field “State” for example is a free text field (CHAR40) that can be mapped to Employee Central Payroll field Region (field STATE, data element REGIO). In Employee Central Payroll “Region” is no free text field but the required values need to be defined in table T005S.

How to solve this issue?
In case a Picklist is required this needs to be defined by the customer for the non-localized SAP countries.
For group 2 countries partially, Picklists are provided by SAP (e.g. for region), but not for all. In cases no picklist is provided by SAP, it is always possible to add country specific picklists when a country specific address is existing in the EC data model.

Unfortunately for the countries of group 3, since the global address model is used, it is not possible to create country-specific picklists for a field (e.g. “State”). In this case ONE “global” picklist has to be created and attached to the corresponding field in EC (e.g. “State”). This picklist must contain data for ALL relevant countries.

In case a picklist is not required it might be an option (if semantically acceptable) not to use the field “State” in EC. Instead the field “County” could be used which is mapped to the field “District” (CHAR40) on Employee Central Payroll side. On both sides these are free text fields.
As another option the field “address3” could be used which is mapped to “2nd Address Line” (CHAR40) on Employee Central Payroll side.

Required/Mandatory fields –
Often a root cause of data replication issues

In Employee Central Payroll fields can be defined as mandatory but the mapped Employee Central fields are not classified as required in the corresponding Employee Central data model. This is highly country-specific.
The relevant field properties for the P2P replication are defined in Employee Central payroll table T588MFPROPS:(table content excerpt from Employee Central Payroll System with SAP_HR 608 SP64, EA-HR 608 SP64)

Once a field being defined as required for Employee Central Payroll has not been populated in EC the replication aborts with an error message that the corresponding field is a mandatory field in the Employee Central Payroll country specific address model.

There are now two options to address this issue:

  1. If the field is available on EC side, but simply not populated, the corresponding EC data model needs to be adapted to define the field as a required field.
    Examples might be for some countries the EC fields address1, zip-code, city and state.Please utilize the EC Check Tool to identify those fields and adapt your data models accordingly:
    (SAP help documentation of Version Q4 2018)
  2. The field is not available on EC side or should not be maintained there for specific countries.
    This might be the case for mappings towards EC field “City” on Employee Central Payroll side (mapped to P0006-ORT01) as being globally defined as required in T588MFPROPS.
    In case the field is required for the country in scope a re-mapping might be the easiest solution.
    In case you do not need to populate this field for specific countries on Employee Central Payroll side you can override the corresponding settings in SAP table T588MFPROPS by defining customer specific field properties in the corresponding custom table T588MFPROPC (View V_ T588MFPROPC).

    CAUTION:
    Customer specific settings in T588MFPROPC might not be considered in case no corresponding data is existing is SAP table T588MFPROPS. This is a common case for the non-ECP countries.
    How to override then the generic settings of T588MFPROPS for non ECP countries?Solution:
    The reason why the T588MFPROC is not considered for non-ECP countries is usually because the feature CSSCR (Assignment between screen type and country for foreign addresses) is not maintained for the affected countries, meaning it defaults them to country key “99”.
    So, this can be changed by adding the correct country key for the country in scope (here Guatemala) to this feature within Employee Central Payroll transaction PE03:
    (feature CSSCR content from Employee Central Payroll System with SAP_HR 608 SP64, EA-HR 608 SP64)

    Afterwards table T588MFPROC can be utilized to overrule SAP non-country specific settings in table T588MFPROC, e.g. to make field City (ORT01) an optional field for Guatemala:
    (table content excerpt from Employee Central Payroll System with SAP_HR 608 SP64, EA-HR 608 SP64)

 

To summarize

The Point-to-Point Integration connecting Employee Central and Employee Central Payroll is a tight and highly preconfigured integration providing therefore less flexibility than e.g. the integration via the Business Integration Builder in Hybrid scenarios.
You have to accept the data as it is replicated from the Employee Central system. You can’t adjust the data manually in the Employee Central payroll system.
Therefore, it is crucial to know the details of e.g. the address data replication to understand where it can be influenced and where not and to conduct troubleshooting.

Hoping that this Blog will add some knowledge to your understanding around this topic.
Feel free to provide feedback / improvement and share your learning’s in the comments section.

6 Comments
You must be Logged on to comment or reply to a post.