SAP S/4HANA Business Partner - Initial HCM-Integration as Background Job

[Andi_M]

Introduction

You have technically converted your system to SAP S/4HANA and are about to activate the HCM-BP Integration based on the provided guidelines.

2340095 - S4TWL - Conversion of Employees to Business Partners

The transition to SAP S/4HANA necessitates the implementation of the employee business partner when HCM data (such as the HCM infotype-based PERNR data model, including PA-Tables) is required. This HCM data may be maintained locally (for instance, through transactions PA30 or PA40) or through integration scenarios with SAP HCM as a hub implementation, SAP SuccessFactors Employee Central, or an external HCM system.

One task involves running the migration report /SHCM/RH_SYNC_BUPA_FROM_EMPL. The blog explains how to execute this migration as a background task to utilize parallelization and acceleration.

For comprehensive details on the new HCM-BP-Integration data model within SAP S/4HANA, please consult the relevant blog post.

New Employee Business Partner Data Model in SAP S/4HANA 2020 On-Premise

Target audience: Functional expert, Development Expert

Version: SAP S/4HANA 2020 or higher

Prerequisites

Basic configuration of integration scenario

You have done already basic configuration based on
SAP S/4HANA Cookbook - Employee Business Partner Integration as of SAP S/4HANA 2020 with new data mo....

Setup bgRFC

In addition to the traditional queued Remote Function Call (qRFC), SAP NetWeaver provides the background RFC (bgRFC) to enhance data transfer performance. Typically, bgRFC is utilized for transferring data between systems, such as with the Core Interface (CIF). However, in our scenario, bgRFC is within a single system to expedite processes.

If a bgRFC setup has not been established, you may refer to the first section of the blog post.

Creation of bgRFC and calling in a program

You can check setup at transaction SBGRFCCONF. At my example system, there is already configured a bgRFC Inbound destination.

Execution

Run /SHCM/RH_SYNC_BUPA_FROM_EMPL in background

Run report /SHCM/RH_SYNC_BUPA_FROM_EMPL via transaction SE38.

"Personnel Number per batch" is set to 5 due to small number of example data. You should test with 500 or 1000 per batch.

After Execution the system generates bgRFC units based on number of data to be processed and data per batch. You will see following status message.

bgRFC Monitor

You can check status of processing by bgRFC Monitor. Start transaction SBGRFCMON and fill selection screen.

After execution, the screen will display active units. Once all data has been processed, they will be removed from the list.

 

Migration log

Migration is logged at application log. You can display application log by running transaction SLGD with
Object: SHCM_EE_INTEGRATION
Subobject: BUPA_SYNC

You will see a screen like this. In best case you will only see green entries 😉