Kontakt

Ansicht
Dokumentation

/SHCM/RH_SYNC_BUPA_EMPL_SINGLE - S/4HANA BP Synchronization

/SHCM/RH_SYNC_BUPA_EMPL_SINGLE - S/4HANA BP Synchronization

BAL Application Log Documentation   PERFORM Short Reference  
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 persistences (infotypes) with the business partner (BP). This functionality can also be used to synchronize data for contingent workers (CW). You can use the various options on the selection screen to filter the employees and external employees for whom you want to run the BP synchronization.

The report locks the employees during the execution of the BP synchronization. If possible, block all users or restrict users from using relevant transactions like PA30or PA40when the report is being executed.

Note: Only use this report in case of initial BP synchronization, for job parallelization purposes due to a large volume of employees or during testing cycles. In all other cases, use the standard daily job /SHCM/RH_SYNC_BUPA_FROM_EMPL.

Integration

Prerequisites

  • All required customizing activities have been executed. For this purpose, refer to the corresponding customizing documentation under the IMG node

Synchronize Business Partners with an Active Business Partner Integration.

  • No employees are locked (no parallel execution of the report /SHCM/RH_SYNC_BUPA_FROM_EMPL or other actions that lock employees).
  • User authorizations for updating the table /SHCM/D_SYNC_RUNand for adapting reports in the job repository (transaction SJOBREPO) exist.

Afterwards, the following steps have to be carried out:

  1. Disable the daily synchronization report /SHCM/RH_SYNC_BUPA_FROM_EMPLin the job repository.
  2. In the table /SHCM/D_SYNC_RUN, set the report's date to a late one. This date is used to determine those employees who are processed in daily synchronization mode. By indicating a late date, you ensure that employees are not processed again in case of unintended execution of the report /SHCM/RH_SYNC_BUPA_FROM_EMPL. If no record exists in table /SHCM/D_SYNC_RUN, create an entry by selecting Utilities > Table Contents > Create Entries and then set a late date. The record is to be filled as follows:
  • REPID: /SHCM/RH_SYNC_BUPA_FROM_EMPL

  • MANDT: client ID of current user

  • DATUM: a late date (for example, 31.12.3000)

  1. After all employees have been processed by the report /SHCM/RH_SYNC_BUPA_EMPL_SINGLE, reset the date of the report /SHCM/RH_SYNC_BUPA_FROM_EMPL in the table /SHCM/D_SYNC_RUN to a current one.
  2. Enable the daily synchronization report /SHCM/RH_SYNC_BUPA_FROM_EMPL in the job repository.

Features,,

The following employee master data infotypes are synchronized:

  • Infotype 0000(Actions)
  • Infotype 0001(Organizational Assignment)
  • Infotype 0002(Personal Data)
  • Infotype 0006(Addresses) – subtype 0001(Permanent residence)
  • Infotype 0009(Bank Details)
Subtype 0 (Main bank)
  • Infotype 0105(Communication) – subtype 0001(System user name)
  • Infotype 0105(Communication) – subtype 0010(E-mail)
  • Infotype 0105(Communication) – subtype 0020(First telephone number at work)
If SAP SuccessFactors integration is used, the subtype ECPB(Landline) is considered.
  • Infotype 0105(Communication) – subtype CELL
If SAP SuccessFactors integration is used, the subtype ECPC(Cell Phone) is considered.

Employee data is created or changed in the following ways:

  • During inbound processing in Employee Central: Synchronization is triggered automatically.
  • During inbound processing using ALE: Synchronization is triggered automatically, provided the BAdI implementation /SHCM/BUPA_SYNC_TRIG (BAdI HRALE00INBOUND_IDOC) has been manually activated.
  • During personnel master data maintenance: Synchronization is triggered automatically.

Note: If you have switched on the business function /SHCM/EE_BP_1, the data is synchronized according to the new BP model, setting up two BPs for the corresponding employee: one BP with the Employeerole (BUP003) and one BP with the Employmentrole (BUP010) If these BP instances already exist, both of them are updated accordingly. Moreover, the two reports /SHCM/R_EMPL_HDLE_BPRLES_DELTA and /SHCM/R_EMPL_HANDLE_BPROLES are available, which can be used to assign additional roles to personnel numbers with an existing BP instance with the Employmentrole. If the business function is switched off, the data is synchronized according to the old BP model, only creating the Employeerole. Further details and information on the impacts of the new BP model can be found in the documentation of the business function New Employee-Business-Partner Model in S/4HANA (CA-HR-S4).

Parallelization of the BP synchronization report

For parallelization, it is recommended to run both this report and the report /SHCM/RH_SYNC_BUPA_EMPL_SINGLE as background jobs. If you have existing background jobs scheduled for the report /SHCM/RH_SYNC_BUPA_EMPL_SINGLE, you first need to deactivate them and reschedule the report again by entering a variant. While creating the variant, you can specify the parameters Personnel Numbers per Batchand Inbound Destination.

Note: Both reports use the Background Remote Function Call (bgRFC) concept for parallelization. Therefore, adapt the reports' configuration to your requirements to ensure a successful parallelization. For this purpose, follow the steps on 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.

If you or other users want to make system defaults-specific changes that require an authorization, follow the steps on 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: Administration>bgRFC Authorizations.

Selection

You have the following options to restrict the number of selected employees:

  • Period
You can select all employees who are active during an indicated period.
  • Selection:
You can further restrict the results by filling the fields in the Selectionsection. You can customize the selection options using Further Selections.
  • Inbound Destination
  • Override Address with Defaults: If this field is checked, the synchronization replaces all addresses with the current data from HR.
  • Override Bank with Defaults: If this field is checked, the synchronization replaces all bank details with the current data from HR and the customizing view PTRV_VENDOR_SYNC.
  • Override Roles with Defaults: If this field is checked, the synchronization replaces all roles with the standard Employeerole (BUP003), provided the according BP is not a legacy one.

Standard Variants

  • SAP_INACTIVE: Variant for suppress inactive employments as of today

Output

After synchronization, the according BP master data is updated with the appropriate roles and employee information. For more details, refer to the documentation of the business function New Employee-Business-Partner Model in S/4HANA (CA-HR-S4).

A log is written and can be found via the transaction SLG1, using the object SHCM_EE_INTEGRATION and the subobject BUPA_SYNC. The log informs you whether the synchronization has been successful and lists all errors occurred.

Further information

Refer to the BAdIs Mapping of Employees to BP fields, and Sync of Roles.






CL_GUI_FRONTEND_SERVICES - Frontend Services   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 13137 Date: 20240420 Time: 134805     sap01-206 ( 155 ms )