Skip to Content
Technical Articles
Author's profile photo Raghavendra Kumar

Utilizing filters in BIB Replication configuration to replicate data from SuccessFactors EC to ERP

Filters in BIB Replication configuration from SF to ERP.


During Replication of data from SF to ERP there is always a requirement to choose the Replication only to specific aspects like Country, Infotyes, Subtypes or specific fields etc depending on the business of the client and where they are located globally.. BIB Replication configuration has given a few filters which we can use to restrict only certain data to be replicated from Success Factors to ERP.

  • Define filters for Organization Replication

Organizational Structure (Divisions, Departments, Business units, Positions) from EC to SAP ERP. Whenever one of these organizational objects is made inactive in EC, it is not getting delimited in SAP ERP (HRP1000).

Organizational objects can be delimited by filtering the inactive records of departments, divisions…, so they do not arrive to the SAP on premise. We need to create a filter on status for ‘A’ active records. Otherwise inactive time slices are transferred to the back end and processed as active time slices.

  • Define Filtering of Infotype and Subtype for Employee Central

We can define the infotypes and sub-types, which should be ignored during the replication process at country grouping level based on work-force.

This is an optional customizing activity and when you perform the replication without setting the infotypes and subtypes all the data mapped in the mapping table would be replicated.

Note: V_ECPAO_IT_FILT table would act as a negative list of infotypes, which would be ignored during the replication process. Any infotypes/subtypes that is entered in this list would be ignored during the replication process based on the country grouping and workforce category.

  • Restrict Employee Master Data Replication to Certain Countries

We can restrict the employee replication to certain countries. If we haven’t defined any countries in this Customizing activity, then there is no restriction.

Caution: If you remove countries from this list after the replication has started, you must delete the related personnel numbers manually.

Define the countries for which you want to replicate employee master data.

  • Filter Infotypes

We can choose which infotypes are replicated for which countries.

If we do not define any infotypes in this Customizing activity, all infotypes and their subtypes are replicated.

However, if we do, only the infotypes which we have defined in this activity are replicated.

If we define one country in this Customizing activity, only this country is replicated. In this case, we have to define all the other countries as well if we want to replicate them.

The following infotypes are always replicated regardless of what we define in this Customizing activity:

0000 Actions

0001 Organizational Assignment

0002 Personal Data

0003 Payroll Status

0709 Person ID


The asterisk (*) can be used for the fields country grouping (MOLGA) and subtype (SUBTY) with the following meaning:

If for a country there are no country-specific entries maintained at all then the system uses the entries maintained for MOLGA = *.

If * is used for SUBTY, then all subtypes are replicated for the infotype and country specified in the same table record.

  • Filter EC Entities for Migrating Employee Data to EC based on Country

Using this we can filter the EC entities for migrating Employee Data to Employee Central based on country.

In a side-by-side deployment model, when a country is still mastered in ERP and not yet mastered in EC, then only the relevant mini-master data should be sent to EC via Infoporter tool. By executing this customizing activity, you will be able to filter out or blacklist those EC entities, which are outside the mini-master scope for the ERP mastered countries.

Even though the EC entity is configured in the Transformation Template Group the EC entity will not be considered during the extraction process for a PERNR belonging to a country for which this EC entity has been filtered out.

Note: Following mandatory templates cannot be excluded from the filtering:

  • WS Templates:
    • WS_2 (PerPerson)
    • WS_3 (EmpEmployment)
    • WS_5 (PerPersonal)
  • CSV Templates:
    • CSV_2 (PerInfo)
    • CSV_3 (EmploymentInfo)
    • CSV_5 (PersonalInfo)

Conclusion: Depending on the requirement from each client that only certain data should be replicated and for certain Countries only. We can use the filters to customize the Replication based on specific requirements from the client ,what data they want to replicate to SAP and for which Countries alone.


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Santosh Shivane
      Santosh Shivane

      Nice information provided, thanks.

      Author's profile photo Mohammad Hassan
      Mohammad Hassan

      Great work, really helpful.

      Is it possible to stop the IT0008 data for certain employee based on the pay scale group or pay scale level ?

      Author's profile photo Raghavendra Kumar
      Raghavendra Kumar
      Blog Post Author

      Hi Hassan,

      Thanks for your comments, Perhaps you can check in Primary mapping if you want to restrict them

      Author's profile photo Mohammad Hassan
      Mohammad Hassan

      Dear Raghav,

      Didn't quit understand, we mapped the wage and payscale in the transformation for comp and requiring pay. I'm not sure how to filter the certain infotype for specific group of employee via primary mapping. Please suggest.

      Author's profile photo Raghavendra Kumar
      Raghavendra Kumar
      Blog Post Author

      Hi Hassan,

      In the Primary mapping you cant filter out specific fields which are not required. We can map only those fields whichever required from SF to SAP to be mapped using Primary and Secondary Mapping. If you need to restrict specific fields for specific Country, perhaps you may need to utilize BADI provided for Employee Replication. You may need to write some logic for restriction.

      Author's profile photo Mohammad Hassan
      Mohammad Hassan

      Dear Raghav,

      Actually requirements was to not send the few employees comp data and I had to create the separate class for them to control the data not getting deleted in  the ERP. Worked with two transformation group.

      Author's profile photo Prashanth Nanjappa
      Prashanth Nanjappa


      Is it possible to define primary mapping of one EC field to different infotype fields depending on the country?

      Eg: Tax ID from EC should go to IT0188 for Australia whereas for Indonesia the same ID will be stored in IT0241.

      Because tax ID is coming from personal info template, we can only use it once in the transformation template which means only one infotype can be specified for mapping.. So how can this be sorted?

      Author's profile photo Raghavendra Kumar
      Raghavendra Kumar
      Blog Post Author

      Hi Prasanth,

      We cant map one field of EC to different fields of an Infotype. As an alternate you can create two different fields for ID and restrict it through Permissions, the same you can map to two different fields of those Infortypes which are Country specific.

      Author's profile photo HCM Team Safari
      HCM Team Safari


      Is it possible to restrict some fields of infotyp1008 from replicating .

      We have condition where custom fields are getting cleared, we would like to keep them as it is.

      Perhaps a way to do this.

      Any suggestions are welcome.


      Author's profile photo Raghavendra Kumar
      Raghavendra Kumar
      Blog Post Author

      Hi Team,

      Yes its very well possible, you can use only those fields of IT1008 in the field mapping.