Mapping of SFSF Fields for Job Requisition Data to SAP ERP Fields 
In Customizing, you define which job requisition data you want to export from the SAP ERP system and map to SuccessFactors BizX fields. For more information, see Transferring Job Requisition Data for Positions from SAP ERP to SuccessFactors BizX, in the Transferred Fields.
The following lists show which SAP ERP fields are used as standard to transfer job requisition data for positions to SuccessFactors BizX and to which SuccessFactors BizX fields they are mapped. These fields are assigned to the field set SAP_REQ_DEMO. In addition to the fields contained in this field set, the ID of the job requisition is transferred from SuccessFactors BizX to the SAP ERP system if a new job requisition has been created in SuccessFactors BizX for the position to be staffed. The SAP ERP system stores the ID in the infotype SFSF Job Requisition (1107).
Caution
Apart from the exceptions mentioned below, 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
For all fields for which the position or organizational unit is entered as the SAP ERP object, the following applies: If the SAP ERP system cannot determine the required 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 it cannot determine the required data for this organizational unit, it determines the data for the next higher-level organizational unit, and so on.
Recommendation
We recommend that you make the following settings so that a manager has access to the job requisition as the originator as well as as the hiring manager:
Configure the routing map for the template for job requisitions in SuccessFactors BizX such that the originator of the job requisition (SuccessFactors BizX field originator) is entered as the first processor. The originator can process the job requisition first and has full access to it. For example, he or she can delete the job requisition provided it has not yet been approved. Alternatively, you can define the hiring manager (SuccessFactors BizX field hiringManagerName) as the first processor.
Make sure that the SuccessFactors BizX user ID of the hiring manager is transferred to the originator field and to the hiringManagerName field. This is defined in this way in the standard system.
Field Content | SFSF Field | SAP ERP Object | SAP ERP Field | Special Features of Mapping |
|---|---|---|---|---|
GUID of Job Requisition | guid | None | None | Field is required. Field cannot be configured. Is generated by the SAP ERP system during the initial data transfer for a job requisition and transferred to SuccessFactors BizX. |
Originator of the job requisition | originator | None | None | Field is required. Is only transferred during the initial data transfer for a job requisition from the SAP ERP system to SuccessFactors BizX. Contains the SuccessFactors user ID that is also transferred to the hiringManagerName field (see below, under Hiring Manager). If this cannot be determined, the SAP ERP system does not transfer any content to SuccessFactors BizX for this field. Then, SuccessFactors BizX uses the user ID of the technical user with which the integration add-on logs on during the data transfer. If you have defined the recruiter in Organizational Management in your SAP ERP system, you can also determine the SuccessFactors user ID of the recruiter and transfer this to the originator field. To do so, create a corresponding implementation of the Business Add-In (BAdI) Mapping of SAP ERP Infotype Fields to SFSF Fields (HRSFI_B_FIELD_MAPPING_OUTBOUND). |
ID of position | sapPositionID | Position or organizational unit | Infotype Object (1000), field Object ID (OBJID) | Field is required. |
Name of position | sapPositionName | Position or organizational unit | Infotype Object (1000), field Object Name (STEXT) | |
Job code | jobCode | Job | Infotype Object (1000), fields Object ID (OBJID) and Object Name (STEXT) | The SAP ERP system uses the relationship describes/is described by (007) to determine the job for the position. The SAP ERP system concatenates the ID and name and places the ID in parentheses after the name. If the SAP ERP system cannot determine a job for a position, it transfers the NO_JOB entry as content for the jobCode field. |
Name of job | title | Job or position | Infotype Object (1000), field Object Name (STEXT) | Field is required. The SAP ERP system uses the relationship describes/is described by (007) to determine the job for the position. The name of the job is determined when a new record of the infotype SFSF Job Requisition (1107) is created. If the name of the job cannot be determined, the SAP ERP system uses the name of the position. In this case, the title field has the same content as the sapPositionName field. |
Description of job | sapJobDesc | Job or position | Infotype Verbal Description (1002) | The SAP ERP system uses the relationship describes/is described by (007) to determine the job for the position. If the description of the job cannot be determined, the SAP ERP system uses the description of the position. |
Date on which the job requisition is created | dateCreated | None | None | Field is required for the creation of the job requisition. Is only considered during the initial data transfer for a job requisition from the SAP ERP system to SuccessFactors BizX. Field cannot be configured. Contains the system date on which the job requisition is created. |
Date on which the job requisition is closed | jobCloseDate | None | None | Field is required when closing the job requisition and is considered only then. Field cannot be configured. Contains the system date on which the job requisition is closed. The date is then needed when the SAP ERP system transfers the job requisition status Closed to the SuccessFactors BizX field jobReqState (see below, under Status of Job Requisition). |
State of the job requisition | jobReqStatus | None | None | Field is required when closing and reopening the job requisition and is considered only then. Field cannot be configured. For more information, see Status Handling for Job Requisitions. |
Status of the job requisition | Status | None | None | Field is required when closing and reopening the job requisition and is considered only then. Field cannot be configured. Contains the status that is defined in Customizing for the integration add-on, under |
ID of the personnel area to which the position belongs | sapPersonnelAreaIDTxt | Position or organizational unit | Infotype Account Assignment Features (1008), field Personnel Area (PERSA) | |
Name of the personnel area to which the position belongs | sapPersonnelAreaTxt | Position or organizational unit | Table Personnel Areas (T500P), field Personnel Area Text (NAME1) | The SAP ERP system first determines the ID of the personnel area from the infotype Account Assignment Features (1008). For this ID, in the table Personnel Areas (T500P), the SAP ERP system determines the name that is stored in the Personnel Area Text (NAME1) field. |
ID of the personnel subarea to which the position belongs | sapPersonnelSubAreaIDTxt | Position or organizational unit | Infotype Account Assignment Features (1008), field Personnel Subarea (BTRTL) | |
Name of the personnel subarea to which the position belongs | sapPersonnelSubAreaTxt | Position or organizational unit | Table Personnel Area/Subarea (T001P), field Personnel Subarea Text (BTEXT) | The SAP ERP system first determines the ID of the personnel subarea from the infotype Account Assignment Features (1008). For this ID, in the table Personnel Area/Subarea (T001P), the SAP ERP system determines the name that is stored in the Personnel Subarea Text (BTEXT) field. |
ID of the employee group to which the position belongs | sapEEGroupIDTxt | Position or organizational unit | Infotype Employee Group/Subgroup (1013), field Employee Group (PERSG) | |
Name of the employee group to which the position belongs | sapEEGroupTxt | Position or organizational unit | Table Employee Group Names (T501T), field Employee Group Name (PTEXT) | The SAP ERP system first determines the ID of the employee group from the infotype Employee Group/Subgroup (1013). For this ID, in the table Employee Group Names (T501T), the SAP ERP system determines the name that is stored in the Employee Group Name (PTEXT) field. |
ID of the employee subgroup to which the position belongs | sapEESubGroupIDTxt | Position or organizational unit | Infotype Employee Group/Subgroup (1013), field Employee Subgroup (PERSK) | |
Name of the employee subgroup to which the position belongs | sapEESubGroupTxt | Position or organizational unit | Table Employee Subgroup Names (T503T), field Employee Subgroup Name (PTEXT) | The SAP ERP system first determines the ID of the employee subgroup from the infotype Employee Group/Subgroup (1013). For this ID, in the table Employee Subgroup Names (T503T), the SAP ERP system determines the name that is stored in the Employee Subgroup Name (PTEXT) field. |
ID of the organizational unit to which the position belongs | sapOrgUnitID | Organizational unit | Infotype Object (1000), field Object ID (OBJID) | The SAP ERP system uses the relationship belongs to/contains (003) to determine the organizational unit for the position. |
Name of the organizational unit to which the position belongs | sapOrgUnitName | Organizational unit | Infotype Object (1000), field Object Name (STEXT) | The SAP ERP system uses the relationship belongs to/contains (003) to determine the organizational unit for the position. |
Hiring manager | hiringManagerName | Person | None | The SAP ERP system first uses the relationship belongs to/contains (003) to determine the organizational unit for the position. It then uses the relationship manages.../is managed by… (012) to determine the chief position of the organizational unit. It uses the Originator (008) relationship to determine the manager's person. If the chief position is shared by multiple managers, the SAP ERP system uses the person that it finds first. It determines the personnel number for the person. For this personnel number, 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 of the manager. |
Name of position of the hiring manager | hiringManagerJobTitle | Position or organizational unit | Infotype Object (1000), field Object Name (STEXT) | The SAP ERP system first uses the relationship belongs to/contains (003) to determine the organizational unit for the position. It then uses the relationship manages.../is managed by… (012) to determine the chief position of the organizational unit. For this position, in the infotype Object (1000), it determines the entry that is stored in the Object Name (STEXT) field. |
ID of the cost center to which the position belongs | costCenterId | Cost center | Infotype Relationships (1001), field ID of Related Object (SOBID) | The SAP ERP system uses the relationship Cost Center Assignment (A011) to determine the cost center. |
Country of the personnel area to which the position belongs | country | Position or organizational unit | Table Personnel Areas (T500P), field Country Key (LAND1) | The SAP ERP system first determines the ID of the personnel area from the Personnel Area field (PERSA) of the infotype Account Assignment Features (1008). For this ID, in the table Personnel Areas (T500P), the SAP ERP system determines the entry that is stored in the Country Key (LAND1) field.
The country field is often defined as a required field in the templates for job requisitions in SuccessFactors BizX. Therefore, to avoid the data transfer failing, ensure that the country key is defined in the HR master data, or that it can be determined in another way. End of the recommendation. |
Region (for example, state or province) of the personnel area to which the position belongs | sapState | Position or organizational unit | Table Taxes: Province Key: Texts (T005U), field Name (BEZEI) | The SAP ERP system first determines the ID of the personnel area from the Personnel Area field (PERSA) of the infotype Account Assignment Features (1008). For this ID, in the table Personnel Areas (T500P), the SAP ERP system determines the key for the region that is stored in the Region (State, Province, County) (REGIO) field. For this key, in the table Taxes: Province Key: texts (T005U), the SAP ERP system determines the name of the region that is stored in the Name (BEZEI) field. |
City of the personnel area to which the position belongs | city | Position or organizational unit | Table Personnel Areas (T500P), field City (ORT01) | The SAP ERP system first determines the ID of the personnel area from the Personnel Area field (PERSA) of the infotype Account Assignment Features (1008). For this ID, in the table Personnel Areas (T500P), the SAP ERP system determines the entry that is stored in the City (ORT01) field. |
Postal code of the personnel area to which the position belongs | postalcode | Position or organizational unit | Table Personnel Areas (T500P), field Postal Code (PSTLZ) | The SAP ERP system first determines the ID of the personnel area from the Personnel Area field (PERSA) of the infotype Account Assignment Features (1008). For this ID, in the table Personnel Areas (T500P), the SAP ERP system determines the entry that is stored in the Postal Code (PSTLZ) field. |
Integration Scenario for Recruiting Data 
Transfer of Job Requisition Data from SAP ERP to SuccessFactors BizX 
Field Content | SFSF Field | Infotype Field | Special Features of Mapping |
|---|---|---|---|
Pay grade type | jobType | Pay Scale/Grade Type (TRFAR) | |
Pay grade region | sapPayGradeArea | Pay Scale/Grade Region (TRFGB) | |
Pay grade group | jobGrade | Highest Permitted Group (TRFG1) | |
Pay grade level | jobLevel | Lowest Permitted Level (TRFS1) | |
Currency | currency | Currency Key (CURCY) | |
Minimum salary in pay grade level | salaryMin | Lower Limit of Pay Grade Level (CPMIN) | If the field is empty, the SAP ERP system transfers the value 0 to SuccessFactors BizX. |
Maximum salary in pay grade level | salaryMax | Upper Limit of Pay Grade Level (CPMAX) | If the field is empty, the SAP ERP system transfers the value 0 to SuccessFactors BizX. |
Medium salary in pay grade level | salaryMid | Midpoint (MIDPT) | If the field is empty, the SAP ERP system transfers the value 0 to SuccessFactors BizX. |
Unit of time that is used to calculate the salary (for example, monthly) | sapCompTimeUnit | Time Unit for Compensation (FREQU) |
Field Content | SFSF Field | Infotype Field | Special Features of Mapping |
|---|---|---|---|
Pay scale type | sapPayScaleType | Pay Scale/Grade Type (TRFAR) | |
Pay scale area | sapPayScaleArea | Pay Scale/Grade Region (TRFGB) | |
Employee subgroup grouping for collective agreement provisions | sapCap | ES Grouping for Collective Agreement Provisions (TRFKZ) | |
Pay scale group | sapPayScaleGroup | Highest Permitted Group (TRFG1) | |
Pay scale level | sapPayScaleLevel | Lowest Permitted Level (TRFS1) | |
Currency | currency | Currency Key (CURCY) | |
Minimum salary in pay scale level | salaryMin | Lower Limit of Pay Grade Level (CPMIN) | If the field is empty, the SAP ERP system transfers the value 0 to SuccessFactors BizX. |
Maximum salary in pay scale level | salaryMax | Upper Limit of Pay Grade Level (CPMAX) | If the field is empty, the SAP ERP system transfers the value 0 to SuccessFactors BizX. |
Unit of time that is used to calculate the salary (for example, monthly) | sapCompTimeUnit | Time Unit for Compensation (FREQU) |
Field Content | SFSF Field | Infotype Field | Special Features of Mapping |
|---|---|---|---|
Currency | currency | Currency Key (CURCY) | |
Minimum salary | salaryMin | Lower Limit of Pay Grade Level (CPMIN) | If the field is empty, the SAP ERP system transfers the value 0 to SuccessFactors BizX. |
Maximum salary | salaryMax | Upper Limit of Pay Grade Level (CPMAX) | If the field is empty, the SAP ERP system transfers the value 0 to SuccessFactors BizX. |
Unit of time that is used to calculate the salary (for example, monthly) | sapCompTimeUnit | Time Unit for Compensation (FREQU) |
Field Content | SFSF Field | Infotype Field | Special Features of Mapping |
|---|---|---|---|
Planned compensation type | sapPayType | Type of Planned Compensation (CPIND) |
Note
The infotype Planned Compensation is defined for either the position or the job. If the infotype fields cannot be determined for the position, the SAP ERP system uses those for the job.
The infotype is divided into the following planned compensation types:
Salary
Pay Scale
Direct
You can use only one of these planned compensation types for a position or job. The SAP ERP system transfers the information on which planned compensation type is valid for the position or job to the SuccessFactors BizX field sapPayType. Therefore, the content for the same SuccessFactors BizX field can come from SAP ERP fields that belong to different planned compensation types.
Example
You can transfer the following information to the SuccessFactors BizX field salaryMin:
Maximum salary in pay grade level (planned compensation type Salary)
Maximum salary in pay scale level (planned compensation type Pay Scale)
Maximum salary (planned compensation type Direct)