Ansicht
Dokumentation

HRSFI_BADI_REC_FLDMP - BAdI: Mapping of SFSF Fields to SAP ERP Infotype Fields

HRSFI_BADI_REC_FLDMP - BAdI: Mapping of SFSF Fields to SAP ERP Infotype Fields

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   ABAP Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

This Business Add-In (BAdI) is used for the integration add-on for SAP ERP HCM and SuccessFactors BizX.

You can use this BAdI to map the content of SuccessFactors BizX fields to SAP ERP fields. You need a separate BAdI implementation for each field.

Note
You can use this BAdI to map only one SuccessFactors BizX field to one SAP ERP field. If you want to perform mappings other than these 1:1 mappings, you need to implement the BAdI Mapping of SFSF Fields to ERP Infotype Fields: Change of Mapping Result (HRSFI_B_CHANGE_MAPPING_RESULT). For more information, see BAdI: Mapping of SFSF Fields to ERP Infotype Fields: Change of Mapping Result.

When importing data from SuccessFactors BizX, the SAP ERP system checks whether the SuccessFactors BizX fields are assigned to corresponding SAP ERP infotype fields in Customizing. For fields for which you have chosen the mapping mode Mapped via BAdI in Customizing, the SAP ERP system runs the relevant implementation of this BAdI (see Mapping Mode). For all fields, the system also checks whether there is a suitable implementation of the BAdI Mapping of SFSF Fields to ERP Infotype Fields: Change of Mapping Result.

This BAdI uses the method EXECUTE with the following parameters:

  • Import Parameters
  • IS_SFSF_DATA

Table with all fields and field values transferred from SuccessFactors BizX
  • IV_MOLGA

Country grouping of transferred data
  • Return Parameter
  • RS_MAPPED_DATA

Table with all infotype fields and field values that have been mapped to the fields transferred from SuccessFactors BizX in the SAP ERP system.

In Customizing, you have created field sets and fields for which you want to implement this BAdI. For more information, see Mapping SuccessFactors BizX Fields and SAP ERP Fields to Each Other.

  • SFSF_FIELD_SET_ID
ID of field set defined in Customizing (see Field Set)
  • SFSF_FIELD_ID
ID of SuccessFactors BizX field, defined in Customizing

You can use these filter values to implement the BAdI more than once so that you can create a suitable implementation for each field of your choice.

  • HRSFI_FLD_MAP_1_USER_ID_PERNR
This implementation performs the following field mapping:
  • SuccessFactors BizX field: RCM_CANDIDATE_USERS_SYS_ID

  • SAP ERP infotype field: Infotype Actions (0000), field Personnel Number (PERNR)

The implementation proceeds as follows:
  1. It checks whether the field RCM_CANDIDATE_USERS_SYS_ID is filled.
For example, the field can contain the ID of the central person (CP) if an employee is not a new hire and the action is an organizational reassignment or a reentry into the company instead.
  1. If the field is filled, the implementation HRSFI_FLD_MAP_1_USER_ID_PERNR checks whether there is an implementation of the BAdI Determination of SAP ERP Personnel Numbers and SFSF User IDs (HRSFI_B_PERNR_USERID).
For more information about this BAdI, see BAdI: Determination of SAP ERP Personnel Numbers and SFSF User IDs.
  1. If there is no implementation of the BAdI HRSFI_B_PERNR_USERID, the implementation HRSFI_FLD_MAP_1_USER_ID_PERNR issues an error message.
  2. If there is an implementation of the BAdI HRSFI_B_PERNR_USERID, the implementation HRSFI_FLD_MAP_1_USER_ID_PERNR uses the ID from the field RCM_CANDIDATE_USERS_SYS_ID to call the implementation of the BAdI HRSFI_B_PERNR_USERID and uses this to determine the personnel number.
  3. If it cannot determine a personnel number, the Personnel Number field remains empty.
  • HRSFI_FLD_MAP_1_DATE
This implementation makes the following field mappings for date specifications:
Hiring Date
  • SuccessFactors BizX field: OFFER_DETAIL_LATEST_JOB_REQ_JOB_START_DATE

  • SAP ERP infotype field: Infotype Actions (0000), field Valid From Date (BEGDA)

Date of Birth
  • SuccessFactors BizX field: RCM_APPLICATION_DOB

  • SAP ERP infotype field: Infotype Personal Data (0002), field Date of Birth (GBDAT)

If the hiring date or date of birth transferred from SuccessFactors BizX contains slashes (/), the implementation converts this to the date format used in the SAP ERP system.
  • HRSFI_FLD_MAP_1_GENDER
This implementation performs the following field mapping:
  • SuccessFactors BizX field: RCM_APPLICATION_GENDER

  • SAP ERP infotype field: Infotype Personal Data (0002), field Form-of-Address (ANRED)

It maps the SuccessFactors BizX field contents to the following form-of-address keys from table T522G:
  • SuccessFactors BizX: M -> SAP ERP: Mr. (1)

  • SuccessFactors BizX: F -> SAP ERP: Ms. (2)

  • SuccessFactors BizX: U -> SAP ERP: Empty

Since this BAdI uses the ID of the field set as a filter value, you need to create at least one customer-specific BAdI implementation for your customer-specific field set. If you want to transfer the mappings of SuccessFactors BizX fields to SAP ERP fields implemented in the standard SAP system, create a corresponding customer-specific implementation for each standard implementation. When creating the customer-specific implementation, specify the class that has been used in the standard implementation.






CL_GUI_FRONTEND_SERVICES - Frontend Services   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 7784 Date: 20240523 Time: 201354     sap01-206 ( 169 ms )