Kontakt

Ansicht
Dokumentation

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

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

TXBHW - Original Tax Base Amount in Local Currency   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 SAP ERP fields to SuccessFactors BizX fields. You need a separate BAdI implementation for each field for which you want to implement this BAdI.

Note
You can use this BAdI to map only one SAP ERP field to one SuccessFactors BizX field. If you want to perform mappings other than these 1:1 mappings, you need to implement the BAdI Mapping of ERP Infotype Fields to SFSF Fields: Change of Mapping Result (HRSFI_B_CHANGE_MAPRES_OUTBOUND). For more information, see BAdI: Mapping of ERP Infotype Fields to SFSF Fields: Change of Mapping Result.
During the transfer of data to the SuccessFactors BizX system, the SAP ERP system checks whether the SuccessFactors BizX fields are assigned corresponding SAP ERP infotype fields in Customizing. For SuccessFactors BizX 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 ERP Infotype Fields to SFSF Fields: Change of Mapping Result.

This BAdI uses the method EXECUTE with the following parameters:

  • Import parameters
  • IS_POSITION

Position for which data is transferred from the SAP ERP system to SuccessFactors BizX
  • IV_KEY_DATE

System date on which the report Create and Update Job Requisitions in SuccessFactors (RH_SFI_TRIGGER_JOB_REQUISITION) is run. For more information about the report, see Create and Update Job Requisitions in SuccessFactors.
  • IV_LANGU

Extraction language in which the report Create and Update Job Requisitions in SuccessFactors (RH_SFI_TRIGGER_JOB_REQUISITION) is run.
  • Return parameter
  • RS_MAPPED_DATA

Structure with the SuccessFactors BizX field as it has been defined by SuccessFactors BizX in the application programming interface (API) mentioned, and its calculated field value

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

All fields used in the standard system must be defined in the relevant templates for job requisitions as either SuccessFactors BizX default fields (custom = false) or as customer-specific fields (custom = true). If you create your own BAdI implementation for customer-specific fields that are not contained in the standard system, these fields also need to be configured as customer-specific fields in SuccessFactors BizX in the relevant template.

  • 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.

Caution
Apart from the exception mentioned below (field originator), the SAP ERP system recalculates all field contents for the current date of the data transfer and updates the job requisition in SuccessFactors BizX accordingly as soon as the content of even only one field has changed.
Note
The following applies to all BAdI implementations indicated with "determines the field contents using the organizational structure": If the implementation cannot determine the chosen data (for example, the employee group) for the current position directly, it uses the organizational structure to determine the relevant data for the higher-level organizational unit. If the implementation cannot determine the chosen data for this organizational unit, it determines the data for the next higher-level organizational unit, and so on.
The following applies to all BAdI implementations that refer to the infotype Planned Compensation (1005):
- This infotype is divided into the planned compensation types Salary, Rate, and Direct. The same field (for example, the field Upper limit of pay grade level) can be filled differently for different positions (for example, for a position for the planned compensation type Salary and for another position for the planned compensation type Rate). The BAdI implementation HRSFI_FLD_MAP_2_SAPPAYTYPE determines for which of the planned compensation types the field content is defined. This information is then transferred to the SuccessFactors BizX field sapPayType.
- If the implementation cannot determine the chosen data (for example, the currency) for the current position directly, it determines the corresponding data for the job that the position describes.
  • HRSFI_FLD_MAP_2_CITY
Determines the field contents using the organizational structure.
Maps the city of the personnel area to which the position belongs to the SuccessFactors BizX field city. To do so, this implementation first determines the ID of the personnel area from the field Personnel Area (PERSA) of the infotype Account Assignment Features (1008) of the position. For this ID, in the table Personnel Areas (T500P), the implementation determines the entry that is stored in the field City (ORT01).
  • HRSFI_FLD_MAP_2_COSTCENTER
Determines the field contents using the organizational structure.
Maps the cost center of the position to the SuccessFactors BizX field costCenterId. This implementation determines the cost center using the relationship Cost Center Assignment (A011), based on the organizational structure that is assigned to the current position.
  • HRSFI_FLD_MAP_2_COUNTRY
Determines the field contents using the organizational structure.
Maps the country of the personnel area to which the position belongs to the SuccessFactors BizX field country. To do so, this implementation first determines the ID of the personnel area from the field Personnel Area (PERSA) of the infotype Account Assignment Features (1008) of the position. For this ID, in the table Personnel Areas (T500P), the implementation determines the entry that is stored in the field Country Key (LAND1).
Note
The country field is often defined as a required field in the templates for job requisitions in SuccessFactors BizX. Therefore, to prevent the data transfer from failing, ensure that the country key is defined in the HR master data, or that it can be determined in another way.
  • HRSFI_FLD_MAP_2_CPMAX
Determines the field contents for the position or job.
Maps the SAP ERP field Upper limit of pay grade level (CPMAX) from the infotype Planned Compensation (1005) for the position to the SuccessFactors BizX field salaryMax. If the CPMAX field is empty, this implementation uses the entry 0.
  • HRSFI_FLD_MAP_2_CPMIN
Determines the field contents for the position or job.
Maps the SAP ERP field Lower limit of pay grade level (CPMIN) from the infotype Planned Compensation (1005) for the position to the SuccessFactors BizX field salaryMin. If the CPMIN field is empty, this implementation uses the entry 0.
  • HRSFI_FLD_MAP_2_CTAMT
Determines the field contents for the position or job.
Maps the SAP ERP field Midpoint (MIDPT) from the infotype Planned Compensation (1005) for the position to the SuccessFactors BizX field salaryMid. If the MIDPT field is empty, this implementation uses the entry 0.
  • HRSFI_FLD_MAP_2_CURCY
Determines the field contents for the position or job.
Maps the SAP ERP field Currency Key (CURCY) from the infotype Planned Compensation (1005) for the position to the SuccessFactors BizX field currency.
  • HRSFI_FLD_MAP_2_EEGROUPID
Determines the field contents using the organizational structure.
Maps the SAP ERP field Employee Group (PERSG) from the infotype Employee Group/Subgroup (1013) for the position to the customer-specific SuccessFactors BizX field sapEEGroupIDTxt.
  • HRSFI_FLD_MAP_2_EEGROUPNAME
Determines the field contents using the organizational structure.
Maps the name of the employee group for the position to the customer-specific SuccessFactors BizX field sapEEGroupTxt. To do so, this implementation first determines the ID of the employee group from the field Employee Group (PERSG) of the infotype Employee Group/Subgroup (1013) of the position. For this ID, in the table Employee Group Names (T501T), the implementation determines the entry that is stored in the field Employee Group Name (PTEXT).
  • HRSFI_FLD_MAP_2_EESUBGROUPID
Determines the field contents using the organizational structure.
Maps the SAP ERP field Employee Subgroup (PERSK) from the infotype Employee Group/Subgroup (1013) for the position to the customer-specific SuccessFactors BizX field sapEESubGroupIDTxt.
  • HRSFI_FLD_MAP_2_EESUBGROUPNAME
Determines the field contents using the organizational structure.
Maps the name of the employee subgroup for the position to the customer-specific SuccessFactors BizX field sapEESubGroupTxt. To do so, this implementation first determines the ID of the employee subgroup from the field Employee Subgroup (PERSK) of the infotype Employee Group/Subgroup (1013) of the position. For this ID, in the table Employee Subgroup Names (T503T), the implementation determines the entry that is stored in the field Employee Subgroup Name (PTEXT).
  • HRSFI_FLD_MAP_2_FREQU
Determines the field contents for the position or job.
Maps the SAP ERP field Time Unit for Compensation (FREQU) from the infotype Planned Compensation (1005) for the position to the customer-specific SuccessFactors BizX field sapCompTimeUnit.
  • HRSFI_FLD_MAP_2_JOB
Maps the general description of the position that is stored in the infotype Description (1002) to the customer-specific SuccessFactors BizX field sapJobDesc. If the implementation cannot determine a description for a position, it uses the description for the related job. It uses the relationship describes / is described by (007) to determine the job for the position.
  • HRSFI_FLD_MAP_2_JOBCODE
Maps the ID and the name of the job that describes the position to the SuccessFactors BizX field jobCode. To do so, this implementation first uses the relationship describes / is described by (007) to determine the job for the position. For this job, in the infotype Object (1000), the implementation then determines the ID that is stored in the field Object ID (OBJID) and the name that is stored in the field Object Name (STEXT). It concatenates this information and places the ID in parentheses after the name. If this implementation cannot determine a job for a position, it transfers the entry NO_JOB as content for the field jobCode.
  • HRSFI_FLD_MAP_2_JOBGRADE
Determines the field contents for the position or job.
Maps the SAP ERP field Highest Eligible Group (TRFG1) from the infotype Planned Compensation (1005) for the position to the SuccessFactors BizX field jobGrade.
  • HRSFI_FLD_MAP_2_JOBLEVEL
Determines the field contents for the position or job.
Maps the SAP ERP field Lowest Eligible Level (TRFS1) from the infotype Planned Compensation (1005) for the position to the SuccessFactors BizX field jobLevel.
  • HRSFI_FLD_MAP_2_JOBTYPE
Determines the field contents for the position or job.
Maps the SAP ERP field Pay Scale/Pay Grade Type (TRFAR) from the infotype Planned Compensation (1005) for the position to the SuccessFactors BizX field jobType.
  • HRSFI_FLD_MAP_2_MANAGERID
Determines the field contents using the organizational structure.
Maps the SuccessFactors BizX user ID of the hiring manager to the SuccessFactors BizX field hiringManagerName. For this, this implementation uses the relationship belongs to / includes (003) to first determine the organizational unit of the position. It then uses the relationship manages... / is managed by... (012) to determine the chief position in the organizational unit. It uses the relationship Holder (008) to determine the person of the manager. If the chief position is shared by more than one manager, the implementation uses the person that is found first. It determines the personnel number for the person. It then uses the Business Add-In (BAdI) Determination of SAP ERP Personnel Numbers and SFSF User IDs (HRSFI_B_PERNR_USERID) to determine the SuccessFactors BizX user ID for this personnel number.
For more information, see BAdI: Determination of SAP ERP Personnel Numbers and SFSF User IDs.
  • HRSFI_FLD_MAP_2_MANAGERTITLE
Determines the field contents using the organizational structure.
Maps the name of the position of the hiring manager to the SuccessFactors BizX field hiringManagerJobTitle. For this, this implementation uses the relationship belongs to / includes (003) to first determine the organizational unit of the position. It then uses the relationship manages... / is managed by... (012) to determine the chief position in the organizational unit. For this position, in the infotype Object (1000), the implementation determines the name that is stored in the field Object Name (STEXT).
  • HRSFI_FLD_MAP_2_ORGUNIT
Maps the name of the organizational unit to which the position belongs to the customer-specific SuccessFactors BizX field sapOrgUnitName. For this, this implementation uses the relationship belongs to / includes (003) to first determine the organizational unit of the position. For this organizational unit, in the infotype Object (1000), the implementation then determines the name that is stored in the field Object Name (STEXT).
  • HRSFI_FLD_MAP_2_ORGUNITID
Maps the ID of the organizational unit to which the position belongs to the customer-specific SuccessFactors BizX field sapOrgUnitID. For this, this implementation uses the relationship belongs to / includes (003) to first determine the organizational unit of the position. For this organizational unit, in the infotype Object (1000), the implementation then determines the ID that is stored in the field Object ID (OBJID).
  • HRSFI_FLD_MAP_2_ORIGINATOR
Maps the SuccessFactors BizX user ID of the owner of the job requisition to the SuccessFactors BizX field originator. The owner has full access to the job requisition and can even delete it provided it has not yet been approved.
This implementation determines the holder as the SuccessFactors user ID that is also transferred to the field hiringManagerName (see BAdI implementation HRSFI_FLD_MAP_2_MANAGERID). If this cannot be determined, the SAP ERP system does not transfer any content to SuccessFactors BizX for this field. SuccessFactors BizX then uses the user ID of the technical user that the integration add-on used to log on for the data transfer.
The owner of the job requisition is only transferred the first time data is transferred for a job requisition from the SAP ERP system to SuccessFactors BizX.
  • HRSFI_FLD_MAP_2_PAREAID
Determines the field contents using the organizational structure.
Maps the SAP ERP field Personnel Area (PERSA) from the infotype Account Assignment Features (1008) for the position to the customer-specific SuccessFactors BizX field sapPersonnelAreaIDTxt.
  • HRSFI_FLD_MAP_2_PAREANAME
Determines the field contents using the organizational structure.
Maps the name of the personnel area to which the position belongs to the customer-specific SuccessFactors BizX field sapPersonnelAreaTxt. To do so, this implementation first determines the ID of the personnel area from the field Personnel Area (PERSA) of the infotype Account Assignment Features (1008) of the position. For this ID, in the table Personnel Areas (T500P), the implementation determines the name that is stored in the field Personnel Area Text (NAME1).
  • HRSFI_FLD_MAP_2_PGRADEAREA
Determines the field contents for the position or job.
Maps the SAP ERP field Pay Scale/Pay Grade Area (TRFGB) from the infotype Planned Compensation (1005) for the position to the customer-specific SuccessFactors BizX field sapPayGradeArea.
  • HRSFI_FLD_MAP_2_POSTAL
Determines the field contents using the organizational structure.
Maps the postal code of the personnel area to which the position belongs to the SuccessFactors BizX field postalcode. To do so, this implementation first determines the ID of the personnel area from the field Personnel Area (PERSA) of the infotype Account Assignment Features (1008) of the position. For this ID, in the table Personnel Areas (T500P), the implementation determines the entry that is stored in the field Postal Code (PSTLZ).
  • HRSFI_FLD_MAP_2_PSCALEAREA
Determines the field contents for the position or job.
Maps the SAP ERP field Pay Scale/Pay Grade Area (TRFGB) from the infotype Planned Compensation (1005) for the position to the customer-specific SuccessFactors BizX field sapPayScaleArea.
  • HRSFI_FLD_MAP_2_PSCALEGROUP
Determines the field contents for the position or job.
Maps the SAP ERP field Highest Eligible Group (TRFG1) from the infotype Planned Compensation (1005) for the position to the customer-specific SuccessFactors BizX field sapPayScaleGroup.
  • HRSFI_FLD_MAP_2_PSCALELEVEL
Determines the field contents for the position or job.
Maps the SAP ERP field Lowest Eligible Level (TRFS1) from the infotype Planned Compensation (1005) for the position to the customer-specific SuccessFactors BizX field sapPayScaleLevel.
  • HRSFI_FLD_MAP_2_PSCALETYPE
Determines the field contents for the position or job.
Maps the SAP ERP field Pay Scale/Pay Grade Type (TRFAR) from the infotype Planned Compensation (1005) for the position to the customer-specific SuccessFactors BizX field sapPayScaleType.
  • HRSFI_FLD_MAP_2_PSUBAREAID
Determines the field contents using the organizational structure.
Maps the SAP ERP field Personnel Subarea (BTRTL) from the infotype Account Assignment Features (1008) for the position to the customer-specific SuccessFactors BizX field sapPersonnelSubAreaIDTxt.
  • HRSFI_FLD_MAP_2_PSUBAREANAME
Determines the field contents using the organizational structure.
Maps the name of the personnel subarea to which the position belongs to the customer-specific SuccessFactors BizX field sapPersonnelSubAreaTxt. To do so, this implementation first determines the ID of the personnel subarea from the field Personnel Subarea (BTRTL) of the infotype Account Assignment Features (1008) of the position. For this ID, in the table Personnel Area/Subarea (T001P), the implementation determines the name that is stored in the field Personnel Subarea Text (BTEXT).
  • HRSFI_FLD_MAP_2_SAPCAP
Determines the field contents for the position or job.
Maps the SAP ERP field EE Subgroup Grouping for Collective Agreement Provisions (TRFKZ) from the infotype Planned Compensation (1005) for the position to the customer-specific SuccessFactors BizX field sapCap.
  • HRSFI_FLD_MAP_2_SAPPAYTYPE
Determines the field contents for the position or job.
Maps the SAP ERP field Planned Compensation Type (CPIND) from the infotype Planned Compensation (1005) for the position to the customer-specific SuccessFactors BizX field sapPayType. The SAP ERP system thereby transfers the information on which of the planned compensation types (Salary, Pay Scale, or Direct) are valid for the current position to SuccessFactors BizX.
  • HRSFI_FLD_MAP_2_STATE
Determines the field contents using the organizational structure.
Maps the name of the region of the personnel area to which the position belongs to the customer-specific SuccessFactors BizX field sapState. To do so, this implementation first determines the ID of the personnel area from the field Personnel Area (PERSA) of the infotype Account Assignment Features (1008) of the position. For this ID, in the table Personnel Areas (T500P), the implementation determines the key for the region that is stored in the field Region (State, Province, County) (REGIO). For this key, in the table Taxes: Region (Province) Key: Texts (T005U), the implementation determines the name of the region that is stored in the field Name (BEZEI).
  • HRSFI_FLD_MAP_2_TITLE
Maps the name of the job that describes the position to the SuccessFactors BizX field jobCode. To do so, this implementation first uses the relationship describes / is described by (007) to determine the job for the position. For this job, in the infotype Object (1000), the implementation then determines the name that is stored in the field Object Name (STEXT).
If the implementation cannot determine a job for a position, it uses the name of the position.

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 SAP ERP fields to SuccessFactors BizX 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.

  • HRSFI_FLD_MAP_2_DEPARTMENT
Maps the organizational unit of the position to the SuccessFactors BizX field Department. For this, this implementation uses the relationship belongs to / includes (003) to first determine the organizational unit of the position. For this organizational unit, in the infotype Object (1000), the implementation then determines the ID that is stored in the field Object ID (OBJID) and the name that is stored in the field Object Name (STEXT). It concatenates this information and inserts a space in between.
  • HRSFI_FLD_MAP_2_DIVISION
Maps the company code of the position to the SuccessFactors BizX field Division. To do so, this implementation first determines the ID of the company code from the field Company Code(BUKRS) of the infotype Account Assignment Features (1008) of the position. For this ID, in the table Company Codes (T001), the implementation determines the name of the company code that is stored in the field Company Code Name or Company Name (BUTXT). It concatenates this information and inserts a space in between.
  • HRSFI_FLD_MAP_2_LOCATION
Maps the personnel area of the position to the SuccessFactors BizX field Location. To do so, this implementation first determines the ID of the personnel area from the field Personnel Area (PERSA) of the infotype Account Assignment Features (1008) of the position. For this ID, in the table Personnel Areas (T500P), the implementation determines the name that is stored in the field Personnel Area Text (NAME1). It concatenates this information and inserts a space in between.

If you want to transfer content from the SAP ERP system to the SuccessFactors BizX fields Department, Division, or Location, note the following restrictions:

  • A value must be transferred for these fields. This means that the fields must not be empty during the data transfer.
  • For these fields, only values that are already known in SuccessFactors BizX may be transferred.






Addresses (Business Address Services)   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 32378 Date: 20240523 Time: 202741     sap01-206 ( 531 ms )