Ansicht
Dokumentation

RH_SFI_SYNCHRONIZE_EMPL_DATA - Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)

RH_SFI_SYNCHRONIZE_EMPL_DATA - Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)

General Material Data   General Data in Customer Master  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report extracts data from the SAP ERP system so that it is available in SuccessFactors Business Execution (BizX) for Talent Management processes.

Integration

This report is based on the logical database PNPCE (HR Master Data Incl. Concurrent Employment) and uses the report class HRSFI_SY.

Prerequisites

Features

During each run, the report extracts only the data for the selected employees that has changed compared with the last run. For more information, see Procedure During Delta Extraction.

The report assigns employees that are not included in the selection area of any extraction variant the status Inactive so that this information can be transferred to SuccessFactors BizX. For example, this applies to employees who switch to an enterprise area for which no integration with SuccessFactors is planned. For more information, see Procedure If Employees Are Set to "Inactive".

Selection

Period

You can specify the current day or any key date or period for which the data is to be extracted.

Selection Conditions

You specify for which employees the data is to be extracted. You can show other selection fields that the report class HRSFI_SY provides.

If employees are in concurrent or global employment and therefore have multiple personnel assignments (meaning personnel numbers), the report extracts the data for only one of the personnel numbers. For more information, see Determine the Main Personnel Assignment for Employees in Concurrent and Global Employment.

Recommendation
For employees in concurrent and global employment, we recommend that you specify one of the personnel assignments as the main assignment. To do so, create a record for the infotype Main Personnel Assignment (0712) with the subtype SuccessFactors (SFSF) for the employees in question.

Default Settings

Here, you can make the following settings:

  • You can use a particular variant to repeat the run of the report and in doing so force the data extraction for the selected employees. For more information, see Forced Synchronization.
  • You can choose whether you want to use middleware to transfer the extracted data to SuccessFactors BizX or whether you want to download the data as a comma-separated values file (CSV file).
If you choose to use a CSV file to transfer the data, the report displays the file path and file name that is to be used to store the generated CSV file. For more information, see Server Path.
  • You can enter a default e-mail address. For more information, see EMAIL.
  • You can define the language in which texts are to be extracted.
Caution
Once you have extracted data in a particular language, we strongly recommend that you do not change the extraction language.
  • You can specify that you want the report log to display only error messages and no messages of the type information, success, or warning. For more information, see Log Error Messages Only.
Note
The Web Dynpro application for monitoring the transfer of data from SAP ERP to SuccessFactors BizX (HRSFI_MONITORING_EMPL) displays all messages, regardless of whether you select this checkbox.
  • You can specify that you do not want the report log or the application for monitoring the transfer of data from SAP ERP to SuccessFactors BizX to display warnings concerning the data provisioning for individual fields. For more information, see Ignore Warnings from Data Provisioning.

Fields

You define which data is to be extracted from the ERP system for the individual SuccessFactors BizX fields. For more information, see the following:

Note
The Required indicator is set for fields that are mandatory in SuccessFactors BizX. You cannot remove the Required indicator for these fields. If the ERP system does not find any data for a mandatory field for an employee, it skips this personnel number. This means that the SAP ERP system does not determine any other field content for this personnel number. In the output log, the personnel number in question is indicated as being with errors.
Fields that are optional in SuccessFactors BizX have the option Exclude (NO). If you select this option, the relevant column is removed completely from the generated CSV file. If you require an optional field for your customer-specific requirements, you can set the Required indicator for this field. However, note that this indicator does not have any effect if you select the option Exclude (NO) for the field in question. Therefore, if you set the indicator Required for an optional field, you should select another option.

Standard Variants

Output

If you have chosen to use middleware to transfer data, the report uses Web services to transfer the extracted data to the middleware. The middleware transfers the data to SuccessFactors BizX.

If you have chosen to use a file to transfer the data, the report generates a CSV file that is stored without encryption on the defined server.

Irrespective of the data transfer method, you receive a log that informs you for how many employees the data has been successfully extracted and for how many employees the extraction failed. If errors occurred, the personnel numbers in question are listed with relevant error messages. If you have not selected the Log Error Messages Only checkbox, messages of the type information, success, and warning will also be listed. In addition, all messages that the report generates will be listed in the Web Dynpro application for monitoring the transfer of data from SAP ERP to SuccessFactors BizX.

Activities

  1. Divide the total number of employees for whom you want to extract data into suitable areas and create a corresponding extraction variant for each area.
Make sure that you use the same option for the field USERID in each extraction variant.
  1. Enter the allowed variants in the Customizing activity Specify Allowed Variants for Delta Extraction.
  2. Schedule the report with your chosen variants to be run regularly in the background.
Ensure that the variants are always run with the same frequency and in the same sequence to avoid data inconsistencies. An exception to this is repeating the run of a variant with the indicator Forced Synchronization.
  1. If errors occurred, resolve the cause of the error in the SAP ERP system.
The personnel numbers concerned are automatically selected and processed again the next time the report is run with the same variant. The corresponding error messages are then deleted from the log.
If you want to repeat the data extraction for the incorrect personnel numbers only, you can repeat the report run with the relevant variant and in doing so set the indicator Forced Synchronization. To do so, proceed as described under Forced Synchronization.
Caution
Once you have used the report to extract data, we strongly recommend that you do not make any changes to the settings used since the data extracted from the ERP system forms the basis for workflow, authorizations, and reporting in SuccessFactors BizX. If you change the settings for a repeated extraction of data, you may generate new objects in SuccessFactors BizX and may, for example, need to modify authorizations accordingly.
Make sure that you always use the same option for the field USERID.
Example
You selected German as the extraction language. Therefore, the report extracted the employee subgroup Leitende Angestellte (Executive Employees). You transferred this to SuccessFactors BizX. For the next data extraction, you select English as the extraction language. Therefore, the report extracts the same employee subgroup, now with the name Executive Employees. When you transfer this to SuccessFactors BizX, it is regarded as a new object. Therefore, you may need to change authorizations or reports that are based on this employee subgroup accordingly.
You have chosen the central person as the extraction option for the field USERID. If you choose the option External Person ID instead during the next extraction run, there will be inconsistencies. Therefore, do notmake any changes to this setting.

Example






ABAP Short Reference   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Length: 15222 Date: 20240520 Time: 122839     sap01-206 ( 201 ms )