SAP® Documentation

Single view

/SHCM/RH_SYNC_BUPA_FROM_EMPL - S/4HANA BUPA Synchronization

BAL_S_LOG - Application Log: Log header data   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

You can use this report to synchronize employee data stored in HCM master data persistence (infotypes) with the Business Partner.

Integration

Along with the traditional usage of employee data using data persistence (infotypes), the new processes can also consume employee data by referring to the corresponding Business Partner or by accessing the employee CDS views.

Prerequisites

  • Set HRALX PBPON to 'ON' and HRALX HRAC to 'X' in table T77S0 or using the transaction OO_CENTRAL_PERSON.
  • Data is synchronized if an employee data is created or changed in the following ways:
  • Inbound processing from Employee Central

The synchronization is triggered
  • Inbound processing using ALE

The synchronization is triggered using the following BAdI implementation:
HRALE00INBOUND_IDOC: /SHCM/BUPA_SYNC_TRIG
Note:You have to manually activate this BAdI.
  • Personnel Master Data Maintenance (for example, Transaction PA30)

The synchronization is triggered

Note: HCM master data is time –independent, but some Business Partner data is not. Therefore, schedule this report to run on a daily basis to update the Business Partner and receive up-to-date employee data.

Features

The following Employee Master Data Infotypes are synchronized:

  • Infotype 0000 (Actions)
  • Infotype 0001 (Org. Assignment)
  • Infotype 0002 (Personal Data)
  • Infotype 0006 (Addresses) Subtype 0001
  • Infotype 0009 (Bank Details)
Travel bank (Subtype 2) is considered if it maintained, else Main Bank (Subtype 0) is considered.
  • Infotype 0105 (Communication) Subtype 0001
  • Infotype 0105 (Communication) Subtype 0010
  • Infotype 0105 (Communication) Subtype 0020
Note:In case of SAP SuccessFactors Employee Central integration, the Subtype ECPB is considered.
  • Infotype 105 (Communication) Subtype CELL
Note:In case of SAP SuccessFactors Employee Central integration, the Subtype ECPC is considered.

Note: An error log is written (transaction: SLG1, Object: SHCM_EE_INTEGRATION, Sub-object: BUPA_SYNC).

The error log informs you whether or not the synchronization was successful and lists all errors that may occur when the synchronization is partly successful. Partly successful means that some parts may have failed, such as user assignment, payment, address, or workplace address.

Selection

If you want to parallelize the report, enter the following parameters:

  • Personnel Numbers per batch: Enter the Personnel Numbers per batch.
  • Inbound Destination: Enter the Inbound Destination. Refer to Step 1 in the Parallelize BUPA Sync Report section.

Note: If you have existing background jobs scheduled for the report then you need to deactivate it and reschedule the report again by entering a variant. While creating the variant, you can specify the parameters Personnel Numbers per batch and the Inbound Destination.

Skip inactive employees:If you want to skip inactive employees, select the check box “Skip inactive employees"

Note:

Report checks if update is necessary:

Data sets with end date of validity period = yesterday
Data sets with begin date of validity period = today

If a synchronization is unsuccessful, all the employee data is updated in the next synchronization run.

Standard Variants

Output

After synchronization, Business Partner is updated with the appropriate roles and employee information. For more information, refer to the attachment in the SAP note 2340095.

After synchronization, you can check the following:

  • Check if the employee data is synchronized to Business Partner using the BP transaction.
  • Check the workplace address using transaction SU01.

Activities

Parallelize BUPA Synchronization Report

Note: If you want to parallelize the report, it is recommended to run both the sync reports (/shcm/RH_SYNC_BUPA_EMPL_SINGLE and /shcm/rh_sync_bupa_from_empl) in background jobs

The reports utilize the bgRFC concept to parallelize the report, so configure it accurately as per your requirements to get it to function correctly.

  1. Follow steps given in the SAP help Portal under SAP NetWeaver > SAP NetWeaver 7.5 > Function-Oriented View > Application Server > Application Server Infrastructure > Functions and Tools of SAP NetWeaver Application Server > Connectivity > Components of SAP Communication Technology > Classic SAP Technologies (ABAP) > RFC > Queued Remote Function Call (qRFC) > bgRFC (Background Remote Function Call) > bgRFC Configuration to configure bgRFCs.

    Note: Create the following objects if you do not agree with the system defaults. Also to make any of the changes you need to assign your user the appropriate authorizations as mentioned under SAP NetWeaver > SAP NetWeaver 7.5 > Function-Oriented View > Application Server > Application Server Infrastructure > Functions and Tools of SAP NetWeaver Application Server > Connectivity > Components of SAP Communication Technology > Classic SAP Technologies (ABAP) > RFC > Queued Remote Function Call (qRFC) > bgRFC (Background Remote Function Call) > bgRFC: Administration > bgRFC Authorizations.
  2. ,,Enter Parameters
Note: If you have existing background jobs scheduled for the report then you need to deactivate it and reschedule the report again by entering a variant. While creating the variant, you can specify the parameters Personnel Numbers per batch and the Inbound Destination.
While running the report enter parameters Personnel Numbers per batch and Inbound Destination to parallelize the report.
  • Enter the Personnel Numbers per batch. For example if the total number of employees is 1000 and the Personnel Numbers per batch entered is 50. Then the report is executed in 20 different threads with 50 employees executed in each thread. The number of parallel threads executing at a particular point depends on the amount of resources allocated while configuring the scheduler as mentioned before in Step 1.

  • Enter the Inbound Destination created in Step 1.

Skip inactive employees

  • If the check box "Skip inactive employees" is selected, all the inactive employees will be skipped from BUPA synchronization.

  • If this check box is not selected, all the employees irrespective of active/inactive state will be synchronized.

Example






ROGBILLS - Synchronize billing plans   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 8459 Date: 20191023 Time: 104352     sap01-206 ( 30 ms )

Our Service

Looking for Support? Questions?

The

Consolut

Callback-Service

Leave us your contact details and we will call you back. Panels marked with * are mandatory.