Skip to Content
Technical Articles
Author's profile photo Chelliah Soundar

Employee to Business Partner Synchronization during S/4HANA system conversion

Updated on Nov 18, 2020

SAP SuccessFactors, the next generation HCM suite in the public cloud, is the go-forward HCM solution for both cloud and on-premise editions of SAP S/4HANA. However, some SAP ERP customers who are converting to SAP S/4HANA on-premise may not be able to move their existing SAP ERP HCM to SAP SuccessFactors in the near term and would like to continue to use SAP ERP HCM until they are ready to move to SAP SuccessFactors. Those customers can run their HCM in either a separate instance or a single instance with S/4HANA. The integration between HCM and S/4HANA on-premise will be available via ALE if HCM is running on a separate instance. If HCM is running inside of S/4HANA on-premise, then the integration is automatically provided as part of the Compatibility Mode.

In SAP S/4HANA, Business Partner (BP) is the leading object, and customer and vendor master data will be assigned as roles to Business Partner. The new data model is based on Business Partner in S/4HANA. This is one of the major changes in S/4HANA, and therefore, it requires considerable effort to prepare the SAP ERP system for conversion to S/4HANA. In fact, Customer Vendor Integration (CVI) Synchronization executed in the SAP ERP system as a prerequisite is one of the major activities in an S/4HANA system conversion project. You may refer to my blog BP and CVI in SAP S/4HANA System Conversion for a step by step guide for CVI Synchronization. If an existing SAP ERP customer who is using SAP ERP HCM is planning to convert their ERP system to S/4HANA, they are required to synchronize their employee data as well to Business Partner. There are two parts to this, one is to synchronize the employee vendors to BP before system conversion in the SAP ERP System and the second one is to synchronize the employees to BP after system conversion in S/4HANA. I will explain both in this blog.

CVI Synchronization

CVI Synchronization – Employee Vendors

First of all, if employee vendors exist in the SAP ERP system, the employee vendors will have to be converted to BPs of category “Person” during CVI synchronization. To accomplish this, implement SAP Note 2539457 (CVI & employee vendors in incorrect BP category) and ensure that BAdI implementation HCM_CVI_MAP_BP_CATEGORY (BAdI CVI_MAP_TITLE) is active. This BAdI implementation identifies employee vendors (LFB1-PERNR has an entry) and converts those vendors to BPs of category “Person” while executing the CVI synchronization report MDS_LOAD_COCKPIT. The employee sync program that you will run after system conversion in the S/4HANA system will update these BPs. If this note is not applied, the standard program will create BPs of category “Organization” for employee vendors while executing the CVI synchronization report MDS_LOAD_COCKPIT. The employee sync program that you will run in the converted S/4HANA system will create new BPs of category “Person” for these employee vendors ignoring the BPs created already of category Organization. That means you will end up having two BPs one in Organization category and another in Person category for a single employee.

There may be other scenarios where employee records and corresponding BPs already exist in the SAP ERP system for certain employee records. If this scenario exists, please refer to SAP Note 2542175 – CVI and reuse of existing employee business partner.

Number Range for employee BPs

Secondly, if you want to use the same number range for the employee vendor BPs created during CVI synchronization in ERP and employee BPs created during BP synchronization in S/4HANA, you need to do the following in ERP before running the CVI synchronization program.

While defining the number range for the BP grouping for employee vendors as part of CVI Synchronization, use a two-character BP Grouping as shown below (the system allows you to use up to four characters). This BP grouping will be used in HCM configuration as explained later in this blog.

Activities in S/4HANA

Once the system is converted from SAP ERP to SAP S/4HANA, carry out the following activities. For more details, please check the installation guide here.

  1. Set the following switches in the table T77S0 as below.



  1. Check if the following BP roles exist in the system. You may refer to Customizing “Define BP Roles.”

BUP003                Employee

BBP005                Service Agent

BBP010                Freelancer

FLVN00                Supplier (Fin Accounting)

FLVN01                Supplier

  1. Check if the following BP Address Type is available in the system. If the value does not exist, add new BP Address Type using the Customizing “Define Address Types.”

HCM001              Employee Private Address

  1. Check if the following Identification Types are available in the system. If the Identification Types are not available, create them using the Customizing “Define Identification Types.”

HCM001              Employee ID

HCM028              Internal Personnel Number

HCM030              Employee ID (Service Performer)

HCM031              Employee ID (Freelancer)

  1. Check Reconciliation Accounting in the Customizing “Define Reconciliation Accounts for Employees in Role FI Supplier.”
  2. Make the configuration settings using T Code OO_CENTRAL_PERSON as explained below.

Set HRALX PNUMB to “2” and assign the two-character BP Grouping to HRALX PSUBG as shown below. This will ensure that the same number range used for the employee vendor BPs created during CVI Synchronization in ERP is used for the BPs created during employee synchronization in S/4HANA. For this setting, the number range must be internal. The screenshots below are for HRALX PNUMB = 2.

HRALX PNUMB can be set to 1, 2, or 3 and for more details regarding these options, please refer to SAP Notes 2792166 and 2483440.

  1. Run the report /SHCM/RH_SYNC_BUPA_EMPL_SINGLE. You can use this report only if the initial synchronization of BP has to be executed in parallel jobs due to large volume of employees or during testing cycles. This report will create BPs for all the employee records for which BP does not exist in the system. For the BPs created during CVI Synchronization for employee vendors, this report will add the employee role BUP003. An error log is written for the failed synchronization, and the error log can be reviewed in transaction SLG1 for object SHCM_EE_INTEGRATION, Sub-object: BUPA_SYNC.
  2. After completing the initial synchronization of employees with Business Partner, set up a background job for the report /SHCM/RH_SYNC_BUPA_FROM_EMPL. This report will update employee BPs based on the changes made to the employee records and keep the employee and BP in sync. Secondly, this report will create new BPs for the future dated employees and new employees created in the system. An error log is written for the failed synchronization, and the error log can be reviewed in transaction SLG1 for object SHCM_EE_INTEGRATION, Sub-object: BUPA_SYNC.
  3. Make sure the business process CVI_04 – Business Partner -> Vendor is active for component AP-MD (IMG Path: SPRO-> Cross-Application Components -> General Application Functions -> Postprocessing Office -> Business Processes->Activate Creation of Postprocessing Orders). This setting will enable the system to capture errors during vendor role creation for employee BPs.

Additional Info

  1. HRALXSYNC (report) – You cannot use this sync report for employee synchronization in SAP S/4HANA. For any other (organizational unit) object synchronization, you can use this report.
  2. Transaction PRAA – This transaction was used for employee vendor creation in the SAP ERP system for travel expenses. You cannot create employee vendors using this transaction, and it is no longer valid in the SAP S/4HANA system.
  3. Table IEMPLOYEE provides info on the link between Employee and BP in S/4HANA.
  4. Table /SHCM/D_BP_SYNC keeps track of the pending/failed employee records from previous/delta synchronization, which will then be picked up in the next run of the sync job.
  5. SAP Note 2578294 – FAQ – Employee to Business Partner synchronization in S/4HANA OnPremise
  6. SAP Note 2409229 – Employee Synchronization Report: FAQ
  7. SAP Note 2340095 – S4TWL – Conversion of Employees to Business Partners
  8. SAP S/4HANA Cookbook Employee Business Partner Integration as of SAP S/4HANA 1809 FPS02
  9. New Employee Business Partner Model in SAP S/4HANA 2020 Release

Assigned tags

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

      thank you! Was really helpful

      Author's profile photo Steffen Mallwitz
      Steffen Mallwitz

      Hello Chelliah,

      very sound and helpful article, indeed.

      One question remains for me, even after checking all kinds of SAP-Notes: What triggers the creation of the BBP005 Service Provider and BBP010 Freelancer roles?

      I mean, what must be maintained in the PA30 infotypes to trigger the creation of BP's with these roles instead of the standard BUP003 role?



      Author's profile photo Jean-Marie CONSEIL
      Jean-Marie CONSEIL

      Hello Steffen,

      To my knowledge, the only way to trigger those roles is to implement Badi mentioned in following OSS note:

      Best regards,


      Author's profile photo Steffen Mallwitz
      Steffen Mallwitz

      Hello Jean-Marie,


      excellent, many thanks, this SAP-Note was initially published 9 days after my comment.

      As if people heard me 😉

      I will check it out immediately.




      Author's profile photo Tilen Drobnic
      Tilen Drobnic



      thank you for very nice overview of integration.


      when creating new HR no. in synchronization to new BP no. we are missing some values:

      • enter a value for field Authorization group
      • enter a value for field Data origin types
      • enter a value for field Business partner type

      Any hints what to do ?




      Author's profile photo Jean-Marie CONSEIL
      Jean-Marie CONSEIL

      Hello Tilen,

      I doubt there is a chance those fields to be mapped in standard.

      I never implemented it myself but one of my colleagues advised me about badi BADI_FITV_VENDOR_SYNC where you have several methods (e.g.  MODIFY_PERSON_CENTRAL_DATA). In this method, you have in terms of input all infotypes related to the personnel number and you can change almost all fields on general view of the business partner.

      Information on the Badi can be found here:

      As I said, I never implemented it so if you dig into this one, it would be great if you can give some feedback...

      Best regards,


      Author's profile photo Jakob Steen-Petersen
      Jakob Steen-Petersen

      Hi Chelliah

      I am a bit confused regarding this issue. In this blog you state that there is a risk of ending up with two Business Partners: one for Vendor and one for Employee.

      Then if i read note 2542175, it is stated that is it Strongly recommended to have two seperate business partners: one for Vendor and one for Employee.

      So could you explain to me what is the correct way of handling this?


      Jakob Steen-Petersen

      Author's profile photo Sridher Sathi
      Sridher Sathi

      Hello Chelliah


      Thanks for such a informative blog. I wanted to check if there would be a feasibility to have different number ranges for BP for employees (Say active &  retired employees). Any suggestions are welcome





      Author's profile photo Francisco Jose Fernandez Prieto
      Francisco Jose Fernandez Prieto


      Thank you for the article, it´s been really helpful. However, I am having doubts with the customizing of the field PNUMB. I see that there are also two additional fields that look similar to PNUMB, which are ENUMB and ONUMB.

      I really can´t get the hang of this and am having doubts about customizing ENUMB and ONUMB fields the same way I would do for PNUMB, or if maybe it reallyisn´t necessary to customize these additional fields.

      Can anyone shed some light about this issue?


      Thank you in advance and best regards,