Integration Add On For SAP ERP HCM and S

4/26/2019
Integration Add-On for SAP ERP HCM and

SuccessFactors HCM Suite
Generated on: 2019-04-26
| 3.0 SP06
PUBLIC
Warning
This document has been generated from the SAP Help Portal and is an incomplete version of the official SAP product
documentation. The information included in custom documentation may not re ect the arrangement of topics in the SAP Help
Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not for productive use.
For more information, please visit the SAP Help Portal.
This is custom documentation. For more information, please visit the SAP Help Portal 1
4/26/2019
Integration Add-On for SAP ERP HCM and

SuccessFactors HCM Suite
Use
The integration add-on for SAP ERP HCM and SuccessFactors HCM Suite enables you to integrate the following data between
SAP ERP HCM and SuccessFactors HCM Suite:
Recruiting data
Onboarding data
Offboarding data
Employee data and organizational data
Compensation data
Variable pay data
Evaluation data
Quali cation data
Implementation Considerations
SAP ERP Versions
You can install the integration add-on in the following SAP ERP versions:
SAP ERP Release Minimum Required Support Package HR Support Package Contained in
Stack SPS
SAP ERP 6.0 SPS15 SP38 for EA-HR 600
SAP ERP 6.0 enhancement package 2 SPS05 SP17 for EA-HR 602
SAP ERP 6.0 enhancement package 4 with SAP SPS02 SP05 for EA-HR 604
NetWeaver 7.01
SAP ERP 6.0 enhancement package 7 SPS01 (= initial delivery stack) SP13 for EA-HR 607
Middleware
If you want to use middleware for the integration, see Integration Using Middleware.
Installation, Security, and Operation of Integration Add-On
See the administration guide for the integration add-on on SAP Help Portal at http://help.sap.com/erp_s _addon30 .
4/26/2019
Integration
Integrating the Add-On with SAP ERP Application Components
The integration add-on uses data from the following application components of SAP ERP:
Application Additional Information

Component
Organizational In SAP Library for SAP ERP at http://help.sap.com/erp , choose SAP ERP Central Component Human
Management Resources Personnel Management (PA) Organizational Management .
Personnel In SAP Library for SAP ERP at http://help.sap.com/erp , choose SAP ERP Central Component Human
Administration Resources Personnel Management (PA) Personnel Administration (PA-PA) .
Enterprise In SAP Library for SAP ERP at http://help.sap.com/erp , choose SAP ERP Central Component Human
Compensation Resources Talent Management Enterprise Compensation Management .
Management
Personnel In SAP Library for SAP ERP at http://help.sap.com/erp , choose SAP ERP Central Component Human
Development Resources Personnel Management (PA) Personnel Development .
Dependencies Between Integration Scenarios
If you use more than one integration scenario, make sure the data is transferred in the following sequence. When setting up
background jobs, remember to take this sequence into account in their prioritization.
Sequence Integration Comment

Scenario
1 Employee data
2 Recruiting data Requires the employees to be available as internal candidates in SuccessFactors HCM Suite.
There are no dependencies between the integration scenarios for recruiting data and compensation
data.
2 Onboarding data Requires the employees to be available in SuccessFactors HCM Suite.
2 Compensation Requires the employees to be available for compensation planning in SuccessFactors HCM Suite.
data
There are no dependencies between the integration scenarios for recruiting data and compensation
data.
2 Quali cation data Requires the employees to be available in SuccessFactors HCM Suite.
2 Variable pay data Requires the employees to be available in SuccessFactors HCM Suite.
Not Evaluation data There are no dependencies between the integration scenario for evaluation data and the other
relevant integration scenarios.
Data Consistency Between SAP ERP HCM and SuccessFactors HCM Suite
Depending on the integration scenario, the system of record for objects can be SuccessFactors HCM Suite or SAP ERP HCM.
Ensure that users do not change data in the system that is not the system of record. For more information, see Data
Consistency in the administration guide for the integration add-on on SAP Help Portal at http://help.sap.com/erp_s _addon30
.
Features
4/26/2019
Technical Integration
You have the following technical options for transferring data from SAP ERP HCM to SuccessFactors HCM Suite and vice versa:
You use middleware to transfer the data with Web services.
For more information, see Integration Using Middleware.
You download the data to les with a at le format.
For more information, see Integration Using File Download.
Note
This option is not available for the integration scenarios for recruiting data, compensation data, and variable pay
data.
Roles for Integration Add-On for SAP ERP

HCM and SuccessFactors HCM Suite
The integration add-on uses the following roles:
Composite Roles for Accessing Functions in the Menu

SuccessFactors Integration: Composite Role
Single Roles for Authorizations and Access to Functions in the Menu

SuccessFactors Integration: Recruiting
SuccessFactors Integration: Onboarding Data
SuccessFactors Integration: Employee Data Replication
SuccessFactors Integration: Compensation Data Replication
SuccessFactors Integration: Compensation Data Import and Activation
SuccessFactors Integration: Variable Pay
SuccessFactors Integration: Analytic Reports
SuccessFactors Integration: Quali cation Data

SAP_HR_SFI_C
Use
4/26/2019
You can use this composite role to provide users in SAP NetWeaver Business Client or in SAP NetWeaver Portal within a clear
navigation structure with access to all functions that are contained in the single roles of the integration add-on for SAP ERP
HCM and SuccessFactors HCM Suite that are mentioned below. If you do not want to use the composite role, you can also
provide the users in SAP NetWeaver Business Client or in SAP NetWeaver Portal with the single roles for the integration add-on.
For more information, see SAP Note 1770819 .
Integration
This composite role comprises the following single roles:
SuccessFactors Integration: Employee Data Replication (SAP_HR_SFI_EMPL_DATA_REPL)
SuccessFactors Integration: Onboarding (SAP_HR_SFI_ONBOARDING)
SuccessFactors Integration: Compensation Data Replication (SAP_HR_SFI_COMP_DATA_REPL)
SuccessFactors Integration: Compensation Data Import and Activation (SAP_HR_SFI_COMP_DATA_IMPORT)
SuccessFactors Integration: Analytic Reports (SAP_HR_SFI_ANALYTICS)
Con guration
Use this role as a template for a customer-speci c role for providing users in SAP NetWeaver Business Client or in SAP
NetWeaver Portal with access to the functions of the integration add-on.

SAP_HR_SFI_C2
Use
You can use this composite role to provide users in SAP NetWeaver Business Client or in SAP NetWeaver Portal within a clear
navigation structure with access to all functions that are contained in the single roles of the integration add-on for SAP ERP
HCM and SuccessFactors HCM Suite that are mentioned below. If you do not want to use the composite role, you can also
provide the users in SAP NetWeaver Business Client or in SAP NetWeaver Portal with the single roles for the integration add-on.
Integration
This composite role comprises the following single roles:
SuccessFactors Integration: Recruiting (SAP_HR_SFI_RECRUITING)
SuccessFactors Integration: Compensation Data Import and Activation (SAP_HR_SFI_COMP_DATA_IMPORT)
SuccessFactors Integration: Analytic Reports (SAP_HR_SFI_ANALYTICS)
Con guration
4/26/2019
Use this role as a template for a customer-speci c role for providing users in SAP NetWeaver Business Client or in SAP
NetWeaver Portal with access to the functions of the integration add-on.
SuccessFactors Integration: Recruiting

SAP_HR_SFI_RECRUITING
Use
You can use this single role to assign authorizations to users that require these to transfer recruiting data from SAP ERP to
SuccessFactors HCM Suite and vice versa. The authorizations are for the following applications:
Providing Metadata from SuccessFactors to Be Used in Input Helps
Report Importing Metadata from SuccessFactors BizX (RH_SFI_SYNCH_METADATA)
For more information, see Customizing for the integration add-on, under Basic Settings Importing Metadata from
SuccessFactors BizX .
Assigning Imported Metadata to Field Sets
Application Assignment of SFSF Objects to Field Sets (transaction S_NWC_37000012)
For more information, see Customizing for the integration add-on, and choose Integration Scenario for Recruiting Data Assign
SuccessFactors BizX Objects to Field Sets .
Check Field Sets for Required Fields
Report Insert and Check Required Fields in Field Sets (RH_SFI_RECRUIT_REQ_FIELDS)
For more information, see Customizing for the integration add-on, and choose Integration Scenario for Recruiting Data Check
Field Sets for Required Fields and Correct .
Handling of Existing Vacancies When Transferring Job Requisition Data for Positions
Report Migrate Existing Vacancies After Activating Job Requisition Transfer (RH_SFI_MIGRATE_VACANCIES)
For more information, see Customizing for the integration add-on, under Integration Scenario for Recruiting Data Data
Transfer from SAP ERP to SuccessFactors BizX Specify Handling of Existing Vacancies During Data Transfer .
Editing Positions to Create Job Requisitions in SuccessFactors
Application Change Organization and Staffing (transaction PPOME)
For more information, see Overview of Open Job Requisitions for Positions of an Organizational Unit and Editing of Positions in
the SAP ERP System to Create Job Requisitions in SuccessFactors HCM Suite.
Transfer of Job Requisition Data for Positions to SuccessFactors
Report Create and Update Job Requisitions in SuccessFactors (RH_SFI_TRIGGER_JOB_REQUISITION)
For more information, see Transferring Job Requisition Data for Positions from SAP ERP to SuccessFactors HCM Suite.
Correct the Status of Job Requisitions in the SAP ERP System

4/26/2019
Report Change Status of Job Requisitions (RH_SFI_JOB_REQ_STATUS_CHANGE)
For more information, see Transferring Job Requisition Data for Positions from SAP ERP to SuccessFactors HCM Suite, in the
Error Handling section.
Specify the ID of the Candidate Template from SuccessFactors
Application Enter ID of Candidate Template from SuccessFactors BizX (transaction S_MWC_87000008)
For more information, see Customizing for the integration add-on and choose Integration Scenario for Recruiting
Data Transfer of Applications from SuccessFactors BizX to SAP ERP Transfer User ID to SFSF After Transferring Candidate to
SAP ERP Enter ID of Candidate Template from SuccessFactors BizX .
Importing Applications from SuccessFactors
Report Importing Recruiting Data from SFSF (RH_SFI_IMPORT_RECRUITING_DATA)
For more information, see Transfer of Applications from SuccessFactors HCM Suite to SAP ERP.
Check and Completion of Imported Applications to Perform a Personnel Action
Application for the further processing of imported recruiting data (transaction HRSFI_RCT_HIRE)
For more information, see Further Processing of Imported Applications in the SAP ERP System.
Performing a Personnel Action
Application Personnel Actions (transaction PA40)
Con guration
Use this role as a template for a customer-speci c role to assign the relevant authorizations to the users in the SAP ERP
system and to enable users to access the applications in the user menu.
You can also use the role to enable users to access the applications contained in SAP NetWeaver Business Client or in SAP
NetWeaver Portal. For more information, see SAP Note 1770819 .
SuccessFactors Integration: Onboarding (for

Future Employees)
SAP_HR_SFI_ONBOARDING
Use
Note
If you have implemented the integration scenario for onboarding data, you do not need to use the features shipped in this
single role.
4/26/2019
You can use this single role to assign users the authorizations to transfer data for future employees from SAP ERP to
SuccessFactors HCM Suite. The authorizations are for the following applications.
Sync Employee Data with SuccessFactors in Pre-Hire Period (Report RH_SFI_PREHIRE_EMPL_DATA)
For more information, see Data Extraction in Pre-Hire Period of New Employees in Integration Scenario for Employee Data.
Con guration
Use this role as a template for a customer-speci c role to assign the relevant authorizations to users in the SAP ERP system
and to enable users to access the applications in the user menu.
SuccessFactors Integration: Onboarding

Data
SAP_HR_SFI_ONBOARDING_2
Use
You can use this single role to assign authorizations to users who need to transfer onboarding data from SAP ERP HCM to
SuccessFactors HCM Suite. The authorizations are for the following transactions:
Import Metadata from SuccessFactors Onboarding (Transaction HRSFI_SYNCH_ONB_META)
This transaction enables you to import metadata from SuccessFactors Onboarding to SAP ERP HCM. This metadata is later
used for mapping SuccessFactors Onboarding elds and SAP ERP HCM elds. For more information, see Customizing for
Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Basic
Settings Import Metadata from SuccessFactors Onboarding .
Assign SuccessFactors Objects to Field Sets (Transaction S_MWC_71000042)
See Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for
On-/Offboarding Data Basic Settings Assign SuccessFactors HCM Suite Objects to Field Sets .
Store Credentials for Transferring Onboarding Data to Secure Storage (Transaction HRSFI_CRD_ONB)
This transaction enables you to store the credentials that are used to securely access the onboarding data. For more
information, see Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario
for On-/Offboarding Data Basic Settings Store Credentials for Transferring Onboarding Data to Secure Storage .
Import Employee Data from SuccessFactors Onboarding (Transaction HRSFI_ONB_DATA_IMP)
This transaction enables you to import onboarding data to the SAP ERP HCM system. The imported data is saved in a staging
area ready to be processed by the HR administrator. For more information, see:
Transfer of Employee Data from SuccessFactors Onboarding
Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for
On-/Offboarding Data Transfer of Employee Data from SuccessFactors Onboarding to SAP ERP HCM Import Employee
4/26/2019
Data from SuccessFactors Onboarding .
Process Employee Data from SuccessFactors Onboarding (Transaction HRSFI_ONB_HIRE)
This transaction enables you to transfer onboarding data to employee master data in the SAP ERP HCM system using
Personnel Actions (transaction PA40). For more information, see Further Processing of Imported Data in SAP ERP HCM.
Delete Imported Data from SuccessFactors Onboarding in SAP ERP HCM (Transaction HRSFI_ONB_DEL_APPLS)
After the onboarding data is successfully imported to the SAP ERP HCM system, you can use this transaction to delete the
imported data from the staging area when the data is no longer required. For more information, see Customizing for
Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Transfer
of Employee Data from SuccessFactors Onboarding to SAP ERP HCM Delete Imported Data from SuccessFactors Onboarding
in SAP ERP HCM .
Con guration
Use this role as a template for a customer-speci c role to assign the relevant authorizations to users in the SAP ERP system
and to enable the users to access the applications in the user menu.
SuccessFactors Integration: Employee Data

Replication
SAP_HR_SFI_EMPL_DATA_REPL
Use
This single role comprises the authorizations that a user requires for the integration scenario for employee data. The
authorizations are for the following applications:
Data Extraction
Report Extraction of Employee Data for SuccessFactors (RH_SFI_TRIGGER_EMPL_DATA_REPL)
Report Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)
(RH_SFI_SYNCHRONIZE_EMPL_DATA)
Recommendation
We recommend that you use the report RH_SFI_SYNCHRONIZE_EMPL_DATA to extract employee data.
For more information, see Integration Scenario for Employee Data.
Discontinuing Data Extraction
Report Discontinue Data Sync. with SuccessFactors for Group of Employees (RH_SFI_WITHDRAW_VARIANT)
For more information, see Integration Scenario for Employee Data.
4/26/2019
Monitoring Data Extraction
Web Dynpro application HRSFI_MONITORING_EMPL
For more information, see Monitoring the Transfer of Data from SAP ERP to SuccessFactors HCM Suite.
Con guration
SuccessFactors Integration: Compensation

Data Replication
SAP_HR_SFI_COMP_DATA_REPL
Use
This single role comprises the authorizations that a user needs to transfer compensation data from SAP ERP to SuccessFactors
HCM Suite. The authorizations are for the following applications:
Data Extraction
Report Replication of Employee's Compensation Data (RH_SFI_SYNCH_COMP_DATA)
For more information, see Transferring Compensation Data from SAP ERP to SuccessFactors HCM Suite.
Providing Input Help for Data Extraction
Report Importing Data from SuccessFactors BizX for Use in Input Helps (RH_SFI_SYNCH_COMP_F4)
For more information, see Customizing for the integration add-on and choose Integration Scenario for Compensation
Data Retrieve Values for Input Help from SuccessFactors BizX .
Cleanup of Internal Tables After Data Extraction
Report Cleanup of Internal Tables After Exporting Compensation Data (RH_SFI_CLEANUP_COMP_REPL)
Monitoring Data Extraction
Web Dynpro application HRSFI_MONITORING_EMPL
Con guration
4/26/2019
Note
Role SAP_HR_SFI_COMP_DATA_REPL lists the infotypes for which the user requires authorizations. However, in the
standard SAP system, no default values are de ned, for example, for the personnel area, employee group, or employee
subgroup. Therefore, in your customer-speci c role, de ne values for the elds of authorization objects P_ORGIN,
P_ORGINCON, and PLOG to suit your requirements.
SuccessFactors Integration: Compensation

Data Import/Activation
SAP_HR_SFI_COMP_DATA_IMPORT
Use
This single role comprises the authorizations that a user needs to transfer compensation data from SAP ERP to SuccessFactors
HCM Suite. The authorizations are for the following applications:
Data Import
Report Import of Employee's Planned Compensation Data (RH_SFI_IMPORT_COMP_DATA)
For more information, see Transferring Compensation Data from SuccessFactors HCM Suite to SAP ERP.
Data Activation
Report Activation of Employee's Planned Compensation Data (RH_SFI_ACTIVATE_COMP_DATA)
Providing Input Help for Data Import
Report Importing Data from SuccessFactors BizX for Use in Input Helps (RH_SFI_SYNCH_COMP_F4)
For more information, see Customizing for the integration add-on and choose Integration Scenario for Compensation
Data Retrieve Values for Input Help from SuccessFactors BizX .
Cleanup of Internal Tables After Data Import and Activation
Report Cleanup of Internal Tables After Importing and Activating Comp. Data (RH_SFI_CLEANUP_COMP_IMP)
Monitoring the Import and Activation of Data
Web Dynpro application HRSFI_MONITORING_COMP
4/26/2019
For more information, see Monitoring the Transfer of Data from SuccessFactors HCM Suite to SAP ERP.
Con guration
Note
Role SAP_HR_SFI_COMP_DATA_IMPORT lists the infotypes for which the user requires authorizations. However, in the
standard SAP system, no default values are de ned, for example, for the personnel area, employee group, or employee
subgroup. Therefore, in your customer-speci c role, de ne values for the elds of authorization objects P_ORGIN,
P_ORGINCON, and PLOG to suit your requirements. Also specify the following infotype authorizations for authorization
objects P_ORGIN and P_ORGINCON:
Read authorization for infotypes Actions (0000) and Organizational Assignment (0001)
Read and write authorization for infotypes Basic Pay (0008) and Additional Payments (0015)

SAP_HR_SFI_VARIABLE_PAY
Use
This single role comprises the authorizations that a user needs to transfer employee history data from SAP ERP HCM to
SuccessFactors HCM Suite. The authorizations are for the following applications.
Data Export
Report Extract Variable Pay Data from SAP ERP to SuccessFactors HCM Suite (report RH_SFI_SYNCH_VAR_PAY_DATA)
For more information, see Transfer of Variable Pay Data from SAP ERP to SuccessFactors.
Metadata Import
Report Import Metadata for Variable Pay from SuccessFactors HCM Suite (report RH_SFI_SYNCH_VAR_PAY_METADATA)
For more information, see Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration
Scenario for Variable Pay Basic Settings Import Metadata from SuccessFactors HCM Suite .
Report Clean Up Internal Tables After Exporting Variable Pay Data (report RH_SFI_CLEANUP_VAR_PAY_REPL)
For more information, see Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration
Scenario for Variable Pay Data Transfer from SAP ERP HCM to SuccessFactors HCM Suite Clean Up Internal Tables in SAP
ERP HCM After Export .
4/26/2019
Con guration
Note
Role SAP_HR_SFI_VARIABLE_PAY lists the infotypes for which the user requires authorizations. However, in the standard
SAP system, no default values are de ned, for example, for the personnel area, employee group, or employee subgroup.
Therefore, in your customer-speci c role, de ne values for the elds of authorization objects P_ORGIN, P_ORGINCON, and
PLOG to suit your requirements. For authorization objects P_ORGIN and P_ORGINCON, also specify read authorization for
infotypes Actions (0000), Organizational Assignment (0001), and any other infotypes from which you plan to extract data.

Import/Activation
SAP_HR_SFI_VARIABLE_PAY
Use
This single role comprises the authorizations that a user needs to transfer the variable pay result from SuccessFactors HCM
Suite to SAP ERP HCM. The same role also comprises the authorization for transferring employee history data from SAP ERP
HCM to SuccessFactors HCM Suite.
The import/activation authorizations are for the following applications:
Data Import
Report Import Variable Pay Data for Employee (report RH_SFI_IMPORT_VARPY_DATA). For more information, see Transfer of
Variable Pay Result from SuccessFactors to SAP ERP.
Data Activation
Report Activate Variable Pay Data for Employee (report RH_SFI_ACTIVATE_VARPY_DATA). For more information, see
Transfer of Variable Pay Result from SuccessFactors to SAP ERP.
Report Clean Up Internal Tables After Importing and Activating Variable Pay Data (report RH_SFI_CLEANUP_VAR_IMP). For
more information, see Transfer of Variable Pay Result from SuccessFactors to SAP ERP.
Monitoring the Import and Activation of Data
Web Dynpro application HRSFI_MONITORING_VARPAY. For more information, see Monitoring the Transfer of Variable Pay Data
from SuccessFactors.
Con guration
4/26/2019
Note
Role SAP_HR_SFI_VARIABLE_PAY lists the infotypes for which the user requires authorizations. However, in the standard
SAP system, no default values are de ned, for example, for the personnel area, employee group, or employee subgroup.
Therefore, in your customer-speci c role, de ne values for the elds of authorization objects P_ORGIN, P_ORGINCON, and
PLOG to suit your requirements. For authorization objects P_ORGIN and P_ORGINCON, also specify the following infotype
authorizations:
Read authorization for infotypes Actions (0000) and Organizational Assignment (0001)
Read and write authorization for infotype Additional Payments (0015) and any other infotypes to which you plan to
write data
SuccessFactors Integration: Analytic

Reports
SAP_HR_SFI_ANALYTICS
Use
This single role comprises the authorizations that a user requires to run the evaluation reports for the integration add-on for
SAP ERP HCM and SuccessFactors HCM Suite. The reports are as follows:
RH_SFI_HRP1000
RH_SFI_HRP1001
RH_SFI_PA0000
RH_SFI_PA0001
RH_SFI_PA0002
RH_SFI_PA0007
RH_SFI_PA0008
RH_SFI_PA0016
RH_SFI_PA0025
RH_SFI_PA0041
RH_SFI_PA0077
RH_SFI_PA0302
RH_SFI_T001
RH_SFI_T001P
RH_SFI_T500P
RH_SFI_T501T
RH_SFI_T503T
4/26/2019
RH_SFI_T505S
RH_SFI_T510A
RH_SFI_T510G
RH_SFI_T512T
RH_SFI_T513F
RH_SFI_T527O
RH_SFI_T529T
RH_SFI_T529U
RH_SFI_T530T
RH_SFI_T542T
RH_SFI_T545T
RH_SFI_T548T
RH_SFI_T549T
RH_SFI_T554T
RH_SFI_T5U13
RH_SFI_T5UEE
RH_SFI_THOC
RH_SFI_THOL
For more information, see Integration Scenario for Evaluation Data.
Con guration
SuccessFactors Integration: Quali cation

Data
SAP_HR_SFI_QUALIFICATION
Use
You can use this single role to assign authorizations to users who need to transfer quali cation data from SAP ERP HCM to
SuccessFactors HCM Suite and vice versa. The authorizations are for the following applications:
Report “Extract Quali cation Catalog Data” (RH_SFI_EXPORT_QUALI)
4/26/2019
For more information, see the following:
Transfer of Quali cation Catalog Data from SAP ERP to SuccessFactors Competency Library
Quali cation Data Transfer of Quali cation Catalog from SAP ERP to SuccessFactors HCM Suite Run Extraction of
Quali cation Catalog
OData Service HRSFI_QUALIFICATION_SRV
Contains OData services to write to quali cation catalog (both personnel development/personnel administration) and read and
write to employee skill data. For more information, see the following:
OData API for Quali cation Data
Quali cation Data Basic Settings Gateway Con guration
Con guration
Integration Using Middleware

Use
You can use Web services to transfer data from your SAP ERP system to SuccessFactors HCM Suite and vice versa.
Prerequisites
You have implemented one of the following middleware versions:
SAP Process Integration
Required is SAP Process Integration 7.11 SP12 or above with the support pack level stated in SAP Note 1838921 . The
integration scenario for variable pay additionally requires connectivity add-on 1.0 SP01. For more information about SAP
Process Integration, see SAP Library for SAP Process Integration at http://help.sap.com/nwpi .
In your SAP ERP system, you must de ne the access data for the System Landscape Directory (SLD) in Maintain SLD
Access Data (transaction SLDAPICUST). For more information, see Connecting to the System Landscape Directory in
SAP Library for SAP NetWeaver at http://help.sap.com/netweaver .
SAP HANA Cloud Integration
This requires an SAP HANA Cloud Integration infrastructure con gured by SAP Cloud Managed Services. For more
information, see:
SAP Library for SAP HANA Cloud Integration at http://help.sap.com/cloudintegration
SAP Library for Integration Add-On 3.0 for SAP ERP HCM and SuccessFactors HCM Suite at
http://help.sap.com/erp_s _addon30 Administration Guide Installation
4/26/2019
You have made the settings in Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Basic
Settings Middleware Settings .
Features
Web Services for SAP Process Integration
The Web services used for the integration add-on are in the Enterprise Service Repository (ESR) in the following namespaces:
Employee data and compensation data
Software component version SFIHCM01 600:
Interface objects: http://sap.com/xi/SFIHCM01
Mapping objects: http://sap.com/xi/SFIHCM01/IC
Recruiting data
Variable pay data
For a list of the services, see Integration Content for SAP Process Integration. For more information about the services, see the
documentation on the services in ESR.
Web Services for SAP HANA Cloud Integration
The Web services used for the integration add-on are provided with the integration content for the add-on in the customer-
speci c tenant of SAP HCI. To do so, contact SAP Cloud Managed Services.
For a list of the services, see Integration Content for SAP HANA Cloud Integration.
OData Services for Integration Scenario for Quali cation Data
See OData API for Quali cation Data.
Web Services Consumed from SuccessFactors
The following APIs used for the integration scenarios.
Integration API
Scenario
Recruiting data SFAPI for object JobRequisition$<Template>, JobApplication$<Template>, Candidate$<Template> to update

requisition, application, and candidate data
SFAPI for ad-hoc report to import requisition data
4/26/2019
Integration API
Scenario
Onboarding OData API for querying the object OnboardingCandidateInfo to get a list of new hire records from SuccessFactors
data Onboarding
SOAP API GetNewhireRecord to get the details of a given new hire record
Employee data SFAPI with object USER to update user data
Quali cation OData entity CompetencyRating to update the competency rating

data
REST API (learning management system) CurriculaDataVOX and UserCurriculaDataVOX to import curricula and
employee curriculum rating
Compensation SFAPI with object EmployeeCompensationStagingFields_<Template> to update employee history

data
SFAPI for ad-hoc report to import the planned compensation data
Variable pay SFAPI for object USER to get the user ID

data
SFAPI for object Background_* to update the employee history
SFAPI for ad-hoc report domain ADHOC_VARPAY_BONUS_PAYOUT to import the planned variable pay result
For more information about APIs, see SAP Help Portal at http://help.sap.com/cloud4hr API Information .
Integration Scenarios
You can use middleware to transfer the following data:
Recruiting data
Onboarding data
Employee data
Quali cation data
Compensation data
Variable pay data
Integration Content for SAP Process

Integration
Use
The integration scenarios of the add-on use the following services:
General services:
SFSFSessionHandlingLoginQueryResult_Out
SFSFSessionHandlingLoginQueryResult_In
SFSFQueryHandlingSubmitJobQueryResponse_Out
SFSFQueryHandlingSubmitJobQueryResponse_In
4/26/2019
SFSFQueryHandlingGetJobStatusQueryResponse_Out
SFSFQueryHandlingGetJobStatusQueryResponse_In
SFSFQueryHandlingGetJobResultEmbeddedQueryResponse_Out
SFSFQueryHandlingGetJobResultEmbeddedQueryResponse_In
SFSFQueryHandlingCancelJobQueryResponse_Out
SFSFQueryHandlingCancelJobQueryResponse_In
SFSFSessionHandlingLogoutQueryResult_Out
SFSFSessionHandlingLogoutQueryResult_In
SFSFAPIDictionaryListSFObjectsResult_Out
SFSFAPIDictionaryListSFObjectsResult_In
SFSFAPIDictionaryDescribeSFObjectsExResult_Out
SFSFAPIDictionaryDescribeSFObjectsExResult_In
SFSFGenericUpdateRequestConfirmation_Out
SFSFGenericUpdateRequestConfirmation_In
SFSFGenericUpsertRequestConfirmation_Out
SFSFGenericUpsertRequestConfirmation_In
SFSFGenericDeleteRequestConfirmation_In
SFSFGenericDeleteRequestConfirmation_Out
SFSFGenericInsertRequestConfirmation_In
SFSFGenericInsertRequestConfirmation_Out
SFSFUserQueryRequest_In
SFSFUserQueryRequest_Out
Services for the integration scenario for recruiting data:
4/26/2019
SFSFJobApplicationStatusUpdateRequestConfirmation_Out
SFSFJobApplicationStatusUpdateRequestConfirmation_In
SFSFCandidateUserIdUpdateRequestConfirmation_Out
SFSFCandidateUserIdUpdateRequestConfirmation_In
SFSFGenericUpsertRequestConfirmation_Out
SFSFGenericUpsertRequestConfirmation_In
Services for the integration scenario for onboarding data:
SFSFOnboardingBeginSession_In
SFSFOnboardingBeginSession_Out
SFSFOnboardingCandidateInfo_In
SFSFOnboardingCandidateInfo_Out
SFSFOnboardingGetNewHireRecord_In
SFSFOnboardingGetNewHireRecord_Out
SFSFOnboardingCancelSession_In
SFSFOnboardingCancelSession_Out
SFSFOnboardingPostNewHireRecord_In
SFSFOnboardingPostNewHireRecord_Out
SFSFOnboardingUpdateNewHire_In
SFSFOnboardingUpdateNewHire_Out
SFSFOnboardingDeleteNewHireRecord_In
SFSFOnboardingDeleteNewHireRecord_Out
SFSFOnboardingGetNewHireRecordByExportId_In
Services for the integration scenario for offboarding data:
4/26/2019
SFSFOnboardingBeginSession_In
SFSFOnboardingBeginSession_Out
SFSFOnboardingCancelSession_In
SFSFOnboardingCancelSession_Out
SFSFOnboardingDeleteNewHireRecord_In
SFSFOnboardingDeleteNewHireRecord_Out
SFSFOffboardingPostOffboardUserRecord_In
SFSFOffboardingPostOffboardUserRecord_Out
SFSFOffboardingGetOffboardUserRecord_Out
SFSFOffboardingGetOffboardUserRecordWithExportId_In
Services for the integration scenario for employee data:
SFSFUserUpsertRequestConfirmation_Out
SFSFUserUpsertRequestConfirmation_In
Services for the integration scenario for quali cation data:
HCMQualificationCatalogue_In
HCMQualificationRating_In
SFSFCompetencyCatalogue_Out
SFSFCompetencyRating_Out
SFSFLMSCurriculumCatalogue_Out
SFSFLMSCurriculumStatus_Out
Services for the integration scenario for compensation data:
4/26/2019
SFSFCompensationManagementUpsertRequestConfirmation_Out
SFSFCompensationManagementUpsertRequestConfirmation_In
Services for the integration scenario for variable pay data:
SFSFGenericUpdateRequestConfirmation_Out
SFSFGenericUpdateRequestConfirmation_In
SFSFUserQueryRequest_In
SFSFUserQueryRequest_Out
4/26/2019
Integration Content for SAP HANA Cloud

Integration
Use
The integration scenarios of the add-on use the following services:
General services:
com.sap.SFIHCM01.hcm2bizx.SFSFSessionHandlingLoginQueryResult
com.sap.SFIHCM01.hcm2bizx.SFSFSessionHandlingLogoutQueryResult
com.sap.SFIHCM01.hcm2bizx.SFSFQueryHandlingCancelJobQueryResponse
com.sap.SFIHCM01.hcm2bizx.SFSFQueryHandlingSubmitJobQueryResponse
com.sap.SFIHCM01.hcm2bizx.SFSFQueryHandlingGetJobStatusQueryResponse
com.sap.SFIHCM01.hcm2bizx.SFSFQueryHandlingGetJobResultEmbeddedQueryResponse
com.sap.SFIHCM01.hcm2bizx.SFSFAPIDictionaryDescribeSFObjectsExResult
com.sap.SFIHCM01.hcm2bizx.SFSFAPIDictionaryListSFObjectsResult
com.sap.SFIHCM02.hcm2bizx.SFSFGenericUpdateRequestConfirmation
com.sap.SFIHCM02.hcm2bizx.SFSFGenericUpsertRequestConfirmation
Services for the integration scenario for recruiting data:
com.sap.SFIHCM02.hcm2bizx.SFSFJobApplicationStatusUpdateRequestConfirmation
com.sap.SFIHCM02.hcm2bizx.SFSFCandidateUserIdUpdateRequestConfirmation
com.sap.SFIHCM02.hcm2bizx.SFSFGenericUpsertRequestConfirmation
Services for the integration scenario for employee data:
4/26/2019
com.sap.SFIHCM01.hcm2bizx.SFSFUserUpsertRequestConfirmation
Services for the integration scenario for onboarding data:
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingBeginSession
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingCancelSession
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingGetNewHireRecord
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingCandidateInfo
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingUpdateNewHire
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingPostNewHireRecord
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingGetNewHireRecordByExportId
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingDeleteNewHireRecord
Services for the integration scenario for offboarding data:
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingBeginSession
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingCancelSession
com.sap.SFIHCM03.hcm2bizx.SFSFOffboardingGetOffboardUserRecordWithExportId
com.sap.SFIHCM03.hcm2bizx.SFSFOnboardingDeleteNewHireRecord
com.sap.SFIHCM03.hcm2bizx.SFSFOffboardingPostOffboardUserRecord
Services for the integration scenario for compensation data:
com.sap.SFIHCM01.hcm2bizx.SFSFCompensationManagementUpserRequestConfirmation
Services for the integration scenario for variable pay data:
com.sap.SFIHCM01.hcm2bizx.SFSFQueryHandlingCancelJobQueryResponse
4/26/2019
com.sap.SFIHCM02.hcm2bizx.SFSFGenericUpdateRequestConfirmation
com.sap.SFIHCM03.hcm2bizx.SFSFGenericInsertRequestConfirmation
com.sap.SFIHCM03.hcm2bizx.SFSFGenericDeleteRequestConfirmation
com.sap.SFIHCM03.hcm2bizx.SFSFUserQueryRequest
Services for the integration scenario for quali cation data:
com.sap.SFIHCM03.hcm2bizx.EmployeeQualificationRating
com.sap.SFIHCM03.bizx2hcm.CompetencyCatalogue
com.sap.SFIHCM03.bizx2hcm.CurriculumCatalogue
com.sap.SFIHCM03.bizx2hcm.UserCompetencyRating
com.sap.SFIHCM03.bizx2hcm.UserCurriculumStatus
Process for Using Middleware for the

Integration
Use
The SAP ERP system sends SOAP messages to the SAP Process Integration system (SAP PI system) within the rewall or to
SAP HANA Cloud Integration (SAP HCI). The SAP PI system or SAP HCI map the SAP ERP elds to the corresponding
SuccessFactors HCM Suite elds. If your system landscape also contains an SAP PI system in the demilitarized zone (DMZ),
within the rewall, the SAP PI system sends SOAP messages to the SAP PI system in the DMZ. The SAP PI system within the
rewall or in the DMZ or SAP HCI sends SOAP messages to the SuccessFactors system. The return path is from SuccessFactors
via SAP PI or SAP HCI to SAP ERP.
Process
1. If the import report for applications has been run or if the extraction reports for job requisition data for positions, for
employee data, or for compensation data have extracted the data and generated relevant data packages, the SAP ERP
system sends the credentials information (enterprise ID, user ID, and password) to SuccessFactors to open a session
there.
SuccessFactors sends a session ID as a synchronous response. This ID is used for subsequent communication.
2. The SAP ERP system sends the session ID and the employee or compensation data to be transferred to SuccessFactors
package by package.
SuccessFactors sends information stating whether the data transfer was successful as a synchronous response. If
technical or business errors occurred, SuccessFactors sends relevant error codes and error messages, as well as
information on which employee is affected.
3. If all data packages are transferred, the SAP ERP system sends the session ID of the session to be ended to
SuccessFactors.
SuccessFactors sends information on whether the session could be ended successfully as a synchronous response.
4. For the integration scenarios for recruiting and compensation data, the SAP ERP system triggers a job to use an ad hoc
report to retrieve the applications or the planned compensation data from SuccessFactors.
4/26/2019
In a multiple step procedure, the SAP ERP system rst sends a request. The synchronous response from SuccessFactors
contains a task ID. The SAP ERP system then uses this task ID to periodically query the status of the request. When the
request has been processed, the SAP ERP system asks for the result. The synchronous response from SuccessFactors
consists of a binary character string that contains the result as a compressed comma-separated values le (CSV le).
Integration Using File Download

Use
You can download data from the SAP ERP system to les with a at le format so that they can be uploaded to SuccessFactors
HCM Suite.
Prerequisites
You have carried out the following activities in Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM
Suite under Basic Settings:
De ne File Path and Name for Storing the Generated Files
BAdI: State File Name for File Storage (if you want to ll the placeholders <PARAM_1>, <PARAM_2>, and <PARAM_3> for
the physical le names differently than in the standard SAP system)
Features
Integration Scenarios
You can use le download for the following data:
Employee data
Evaluation data
Quali cation data
File Formats
The integration add-on uses the following le formats:
CSV le
This format is used for the integration scenario for employee data.
TXT le
This format is used for the integration scenario for evaluation data.
Integration Scenario for Recruiting Data

Use
From the SAP ERP system, you can trigger the creation of a new job requisition in SuccessFactors HCM Suite. If the job has
been posted and there are applications in SuccessFactors, you can extract these and transfer them to the SAP ERP system. In
4/26/2019
the SAP ERP system, you can transfer the transferred candidates to Personnel Administration as employees. You can then use
the personnel numbers of the new employees to derive their user ID for SuccessFactors and return these to SuccessFactors.
Integration
If you use more than one integration scenario, adhere to the correct sequence during the data transfer. For more information,
see Integration Add-On for SAP ERP Human Capital Management and SuccessFactors HCM Suite, in the Integration section.
If you have used this integration scenario to transfer applications to the SAP ERP system and hire the candidates as new
employees, you can use the integration scenario for employee data to transfer the data for these newly hired employees back
to SuccessFactors. For more information, see Integration Scenario for Employee Data.
Features
You can use middleware to transfer recruiting data from SAP ERP to SuccessFactors and from SuccessFactors to SAP ERP. For
more information, see Integration Using Middleware.
Direction of Data Transfer
You can transfer recruiting data in the following directions:
SAP ERP HCM → SuccessFactors
For more information, see Transferring Job Requisition Data for Positions from SAP ERP to SuccessFactors HCM Suite.
SuccessFactors → SAP ERP HCM
For more information, see Transfer of Applications from SuccessFactors HCM Suite to SAP ERP.
Data Transfer Process
See Integration Scenario Process for Recruiting Data.
Integration Scenario Process for Recruiting

Data
Use
The process for transferring recruiting data from SAP ERP HCM to SuccessFactors HCM Suite and vice versa is as follows.
4/26/2019
Figure 1: Integration Scenario Process for Recruiting Data
Prerequisites
See Transferring Job Requisition Data for Positions from SAP ERP to SuccessFactors HCM Suite and Transferring Applications
from SuccessFactors HCM Suite to SAP ERP.
Caution
You can transfer applications from SuccessFactors to the SAP ERP system only once, where you process them further. If in
SuccessFactors, you change the status of applications that have been transferred successfully from TransferredToSAP back
to SendToSAP, the SAP ERP system rejects these applications. Their status in SuccessFactors is set to
TransferredToSAPError.
If you change the data of the application in SuccessFactors after data has been transferred to the SAP ERP system and
these changes are also to take effect in the SAP ERP system, you need to make the same changes in the SAP ERP system
that you made in SuccessFactors.
Process
1. If a position needs to be restaffed and a job requisition is to be created in SuccessFactors for this, the HR Administrator
creates a record for the infotype SFSF Job Requisition (1107) for this position. To do so, he or she proceeds as follows:
If you use the infotype Vacancy (1007) in your SAP ERP system, the HR Administrator creates a vacancy for the
position, and thereby a record for the infotype Vacancy. The SAP ERP system re ects this infotype record in a
record of the infotype SFSF Job Requisition.
If you do not use the infotype Vacancy in your SAP ERP system, the HR Administrator creates the record of the
infotype SFSF Job Requisition manually.
For more information, see Editing of Positions in the SAP ERP System to Create Job Requisitions in SuccessFactors HCM
Suite.
2. The implementation Change Pointer Handling for 1007 and 1107 (HRSFI_CH_PTRS) of the Business Add-In (BAdI)
Updater (HRBAS00INFTY) checks all explicit and implicit changes to positions that affect the creation of job requisitions
4/26/2019
in SuccessFactors, including the new infotype record that the HR Administrator has created. It stores corresponding
change pointers in the change pointer table for job requisitions (table HRSFI_D_RCT_REQ).
Each change pointer re ects exactly one change. Therefore, the change pointer table contains all information that is
needed to create, change, and delete records of the infotype SFSF Job Requisition. It is possible that there are multiple
change pointers that need to be considered for the same position when updating the records of the infotype SFSF Job
Requisition.
3. You schedule the report Create and Update Job Requisitions in SuccessFactors
(RH_SFI_TRIGGER_JOB_REQUISITION) to be run regularly in the background.
4. Each time the report is run, it evaluates the change pointer table and generates records of the infotype SFSF Job
Requisition.
5. The report uses the following criteria to determine all infotype records for which information needs to be transferred to
SuccessFactors:
An error occurred during the last run.
The transfer mode Forced Transfer or Postponed Transfer is set.
For more information about the transfer mode, see Infotype SFSF Job Requisition (1107) in the Structure section,
under Field Part .
The status of the job requisition as it was last transferred successfully from the SAP ERP system to
SuccessFactors ( eld STATUS of the infotype SFSF Job Requisition) is different from the status that is
transferred from the SAP ERP system to SuccessFactors during the next transfer of data ( eld TARGET_STATUS
of the infotype SFSF Job Requisition).
 Example
The status Open is stored in the STATUS eld, and the status Closed is stored in the TARGET_STATUS eld.
This means that the position has been staffed in the SAP ERP system. This information needs to be
transferred to SuccessFactors so that the job requisition can be closed there.
The position data has changed compared with the last run such that a delta data transfer is necessary.
 Example
The position was assigned to a different organizational unit since there was a reorganization in your
enterprise.
6. Based on your Customizing settings, the report maps the contents of the SAP ERP infotype elds to the corresponding
SuccessFactors elds and transfers the data to SuccessFactors in packages.
For more information about the elds mapped in the standard SAP ERP system, see Mapping of SFSF Fields for Job
Requisition Data to SAP ERP Fields.
7. SuccessFactors creates a new job requisition for the position to be staffed and sends the ID of the job requisition to the
SAP ERP system.
The SAP ERP system stores the ID in the infotype SFSF Job Requisition.
8. The SAP ERP system logs the status of the data transfer.
If the data transfer was successful, the SAP ERP system generates statistics and stores this in the log for the
report Create and Update Job Requisitions in SuccessFactors and in the application log. It also sets the
corresponding status (for example, Open) in the infotype SFSF Job Requisition.
4/26/2019
If the data transfer was not successful, the SAP ERP system generates corresponding error messages. It writes
the messages to the log for the report Create and Update Job Requisitions in SuccessFactors and to the
application log. In the infotype SFSF Job Requisition it also sets the status Error and de nes a handle for the
related application log.
9. Applications for the job requisition enter SuccessFactors.
10. You schedule the report Importing Recruiting Data from SFSF (RH_SFI_IMPORT_RECRUITING_DATA) in the SAP ERP
system to be run regularly in the background.
11. Each time the report is run, it triggers a query in SuccessFactors to use an ad hoc report to retrieve all applications with
the status SendToSAP.
12. The data of the application (object JobApplication) and related data of the job requisition (object JobRequisition),
candidate (object Candidate), and the last offer details (object LastOfferDetail) is transferred to the SAP ERP system.
Note
If the ad hoc report is con gured such that it also extracts applications with a status other than SendToSAP, the SAP
ERP system ignores these applications.
13. The SAP ERP system sends an update to SuccessFactors for each application:
If the data transfer was successful, the status of the application in SuccessFactors is set to TransferredToSAP
and the date of the data transfer is entered in the eld Exported On.
If the data transfer was not successful, the status of the application in SuccessFactors is set to
TransferredToSAPError. The eld Exported On remains empty.
The SAP ERP system also generates corresponding error messages:
It writes the messages to the error log of the report Importing Recruiting Data from SFSF.
It sends the messages to SuccessFactors. There, they are stored in the eld sapError for the application.
14. Based on your Customizing settings, the SAP ERP system maps the contents of the SuccessFactors elds to the
corresponding SAP ERP infotype elds.
For more information about the elds mapped as standard, see Mapping of SFSF Fields for Application Data to SAP ERP
Fields (Without Data Transfer for Job Requisition Data) and Mapping of SFSF Fields for Application Data to SAP ERP
Fields (with Data Transfer for Job Requisition Data).
15. In the application for the further processing of imported applications (transaction HRSFI_RCT_HIRE), the HR
Administrator checks the applicant data mapped to the SAP ERP infotype elds and, where required, corrects or
supplements information that is required to perform a personnel action.
For more information about the transaction HRSFI_RCT_HIRE, see Further Processing of Imported Applications in the
SAP ERP System.
16. From the application for the further processing of imported recruiting data, the HR Administrator triggers a personnel
action to transfer the applicant data to Personnel Administration of the SAP ERP system.
17. The SAP ERP system sends an update to SuccessFactors for each transferred application:
The status of the application is set to HiredAtSAP in SuccessFactors.
The eld Exported On contains the date of the data transfer.
18. If you have activated this function in Customizing, the SAP ERP system uses the personnel number of the newly hired
employee to derive a user ID for SuccessFactors and sends this to SuccessFactors.
4/26/2019
SuccessFactors stores this user ID in the object Candidate and thereby establishes a relationship between the data for
the external candidate who applied using SuccessFactors and the data of the new employee who has been hired using
Personnel Administration in the SAP ERP system.
19. Since the position is staffed, the SAP ERP system prompts the HR Administrator to close the vacancy after completing
the personnel action.
Note
If you do not use the infotype Vacancy, the record of the infotype SFSF Job Requisition is closed automatically.
For more information, see Further Processing of Imported Applications in the SAP ERP System, in the Perform Personnel
Action section.
20. The next time it is run, the report Create and Update Job Requisitions in SuccessFactors sends the information to
SuccessFactors that the position has been staffed.
21. SuccessFactors closes the related job requisition.
22. The SAP ERP system transfers all data that is stored for the position in the infotype SFSF Job Requisition from the
subtype Open Job Requisition (0001) to the subtype Closed Job Requisition (0002).
Transfer of Job Requisition Data for Positions

from SAP ERP
Use
You can transfer information about positions to be staffed from the SAP ERP system to SuccessFactors HCM Suite so that
corresponding job requisitions can be created or changed there. If the positions are staffed in the SAP ERP system, this
information is also transferred to SuccessFactors so that the associated job requisitions are closed there.
Prerequisites
You have activated this function in Customizing for the integration add-on for SAP ERP HCM and SuccessFactors HCM
Suite. To do so, under Integration Scenario for Recruiting Data Activate Additional Functions , set the parameter
JOB_REQUISITION_INTEGR_ACTIVE to X.
In Customizing for the integration add-on, you have made the following settings:
Customizing activities in the Basic Settings section:
De ne Authorizations (Recruiting Data)
BAdI: Authorization Check for SFSF Integration
Import Metadata from SuccessFactors BizX
BAdI: Determination of SAP ERP Personnel Numbers and SFSF User IDs
Settings for Middleware Store Credentials for Transferring Recruiting Data in Secure Storage
Settings for Middleware De ne Package Size for Transfer of Recruiting Data
Customizing activities in the Integration Scenario for Recruiting Data section:
Map SuccessFactors BizX Fields and SAP ERP Fields to Each Other
4/26/2019
Check and Correct Field Sets
All Customizing activities in the section Transfer of Job Requisition Data from SAP ERP to SuccessFactors
BizX
Features
For more information, see Process for Transfer of Job Requisition Data.
Editing of Positions in the SAP ERP System to Create Job Requisitions in SuccessFactors
On the SFSF Job Requisition tab in the Organization and Staffing applications, the HR Administrator can display (if you use
vacancies for positions in your SAP ERP system) or create (if you do not use vacancies for positions) records of the infotype
SFSF Job Requisition (1107) for positions.
Infotype SFSF Job Requisition (1107)
Editing of Positions in the SAP ERP System to Create Job Requisitions in SuccessFactors HCM Suite
Overview of Open Job Requisitions for Positions
In the Organization and Staffing applications, the HR Administrator can obtain an overview of which open job requisitions there
are in SuccessFactors for the positions of an organizational unit.
For more information, see Overview of Open Job Requisitions for Positions of an Organizational Unit.
Handling of Existing Vacancies
If records for the infotype Vacancy (1007) with a current validity period already exist in your SAP ERP system at the time at
which you activate this function, the SAP ERP system generates records for the infotype SFSF Job Requisition for such
vacancies. However, these infotype records are not transferred to SuccessFactors since it is possible that manual job
requisitions have already been created for such vacancies.
You can de ne that existing vacancies are also to be considered during the data transfer. For example, this is useful if you have
not yet created any job requisitions for SAP ERP positions in SuccessFactors. To do so, in Customizing, choose Integration
Scenario for Recruiting Data Transfer of Job Requisition Data from SAP ERP to SuccessFactors BizX , and perform the activity
Specify Handling of Existing Vacancies During Data Transfer.
Data Transfer
To transfer information on positions to be staffed to SuccessFactors, use the report Create and Update Job Requisitions in
SuccessFactors (RH_SFI_TRIGGER_JOB_REQUISITION). The report ensures that job requisitions are created in
SuccessFactors for the positions. If the staffing of the positions has been completed in the SAP ERP system, the report also
transfers this information to SuccessFactors so that the associated job requisitions are closed there.
For more information about the report, see Customizing for the integration add-on and choose Integration Scenario for
Recruiting Data Transfer of Job Requisition Data from SAP ERP to SuccessFactors BizX Trigger Creation and Update of Job
Requisitions in SuccessFactors BizX . The report is also located in the user menu of the role SuccessFactors Integration:
Recruiting (SAP_HR_SFI_RECRUITING).
Transferred Fields
4/26/2019
In Customizing, you de ne which eld contents you want to transfer from the SAP ERP system to SuccessFactors. To do so, you
de ne eld sets. A eld set contains multiple SuccessFactors elds that you map to the SAP ERP elds of your choice. You have
the following options:
You map the elds to each other directly, using a table.
For more information, see Customizing and choose Integration Scenario for Recruiting Data Map SuccessFactors BizX
Fields and SAP ERP Fields to Each Other .
To make more complex mappings, you can create a Business Add-In implementation (BAdI implementation). You can use
the following BAdIs for this:
Mapping of SAP ERP Infotype Fields to SFSF Fields (HRSFI_B_FIELD_MAPPING_OUTBOUND)
You can use this BAdI to map a SuccessFactors eld to an SAP ERP eld.
For the BAdI, see Customizing and choose Integration Scenario for Recruiting Data Transfer of Job Requisition
Data from SAP ERP to SuccessFactors BizX BAdI: Mapping of SAP ERP Infotype Fields to SFSF Fields .
Mapping of ERP Infotype Fields to SFSF Fields: Change of Mapping Result

(HRSFI_B_CHANGE_MAPRES_OUTBOUND)
You can use this BAdI to map one or more SuccessFactors elds to one or more SAP ERP elds.
For the BAdI, see Customizing and choose Integration Scenario for Recruiting Data Transfer of Job Requisition
Data from SAP ERP to SuccessFactors BizX BAdI: Mapping of ERP Infotype Fields to SFSF Fields: Change of
Mapping Result .
As standard, some mappings of SuccessFactors elds to SAP ERP elds are de ned. For more information, see Mapping of SFSF
Fields for Job Requisition Data to SAP ERP Fields.
Error Handling
Evaluate Messages for the Data Transfer from SAP ERP to SuccessFactors
You can edit error messages that the report Create and Update Job Requisitions in SuccessFactors
(RH_SFI_TRIGGER_JOB_REQUISITION) generates as follows:
You check the report log.
You evaluate the application logs.
To do so, in Customizing, choose Integration Scenario for Recruiting Data Transfer of Job Requisition Data from SAP
ERP to SuccessFactors BizX , and perform the activity Evaluate Application Logs for Creating/Updating Job
Requisitions in SFSF.
Evaluate Messages for the Data Transfer from SuccessFactors to SAP ERP
If you transfer application data from SuccessFactors, the SAP ERP system checks whether the combination of position and job
requisition ID as it has been imported from SuccessFactors for a candidate corresponds to the combination de ned in the SAP
ERP system. If this is not the case, corresponding messages are displayed for the HR Administrator in the application for the
further processing of imported applications (transaction HRSFI_RCT_HIRE).
Correct the Status of Job Requisitions in the SAP ERP System
You can use the report Change Status of Job Requisitions (RH_SFI_JOB_REQ_STATUS_CHANGE) to correct the status of job
requisitions in the SAP ERP system if this differs from the status of the relevant job requisition in SuccessFactors. For more
4/26/2019
information, see Customizing and choose Integration Scenario for Recruiting Data Transfer of Job Requisition Data from SAP
ERP to SuccessFactors BizX Correct the Status of Job Requisitions in the SAP ERP System .
Process for Transfer of Job Requisition Data

For a detailed description of the process for the entire integration scenario for recruiting data, including the transfer of
applications from SuccessFactors HCM Suite to SAP ERP, see Integration Scenario Process for Recruiting Data.
The following contains overviews of the following subprocesses:
Process: Create a Job Requisition
Process: Update a Job Requisition
Process: Close a Job Requisition
Process: Reopen a Closed Job Requisition
Process: Create a Job Requisition

Use
The process for creating a new job requisition is roughly as follows:
Process
1. Optional: The HR Administrator creates the infotype Vacancy (1007) for a position.
2. The SAP ERP system creates the infotype SFSF Job Requisition (1107) with the job requisition status To Be Created (or
the HR Administrator creates the infotype on the SFSF Job Requisition tab), determines the ID of the template for job
requisitions, and stores this in the infotype.
3. The report Create and Update Job Requisitions in SuccessFactors (RH_SFI_TRIGGER_JOB_REQUISITION) generates
a GUID for the job requisition, maps, based on your Customizing settings, the contents of the SAP ERP infotype elds to
the corresponding SuccessFactors HCM Suite elds, and transfers the data to SuccessFactors.
4. SuccessFactors creates the job requisition based on the corresponding template for job requisitions, stores pre-
approved in the eld state as well as the data transferred from the SAP ERP system for the job requisition, and informs
the SAP ERP system of the state and ID of the job requisition.
Caution
Make sure that the status of the job requisition in SuccessFactors is then changed manually from pre-approved to
approved. Otherwise, the job requisition cannot be closed correctly when the position concerned is staffed (see
Process: Close a Job Requisition).
5. The SAP ERP system stores the ID of the job requisition and the data transferred to SuccessFactors in the infotype SFSF
Job Requisition (1107) and changes the job requisition status displayed on the SFSF Job Requisition tab from To Be
Created to Created.
Process: Update a Job Requisition

4/26/2019
Use
The process for updating an existing job requisition is roughly as follows:
Process
1. The report Create and Update Job Requisitions in SuccessFactors (RH_SFI_TRIGGER_JOB_REQUISITION)

determines the records of the infotype SFSF Job Requisition (1107) for which information needs to be transferred to
SuccessFactors HCM Suite (for example, because position data has been changed).
2. For all job requisitions whose IDs are stored in the determined infotype records, the report retransfers all data to
SuccessFactors (irrespective of whether the content of an individual eld has changed).
3. The SAP ERP system stores the changed data that was transferred to SuccessFactors in the infotype SFSF Job
Requisition (1107) and leaves the job requisition status displayed on the SFSF Job Requisition tab as Created.
Caution
The template for job requisitions is not determined again when a job requisition is updated. To change the template
retroactively, you need to close the vacancy, and thereby the record of the infotype SFSF Job Requisition so that the
job requisition is closed in SuccessFactors. You then need to create the vacancy again so that a job requisition with a
new template can be created in SuccessFactors.
Process: Close a Job Requisition

Use
The process for closing an existing job requisition is roughly as follows:
Process
1. An application for the job requisition is transferred from SuccessFactors HCM Suite to the SAP ERP system.
2. The SAP ERP system assigns the transferred candidate to the position for which the job requisition was created.
3. Optional: The HR Administrator closes the vacancy.
4. The SAP ERP system delimits the relevant record of the infotype SFSF Job Requisition (1107).
5. The report Create and Update Job Requisitions in SuccessFactors (RH_SFI_TRIGGER_JOB_REQUISITION) transfers
the information to SuccessFactors that the job requisition is to be closed.
6. SuccessFactors changes the state of the job requisition ( eld jobReqStatus) to Closed and the status ( eld status) to
SAPClosed, and informs the SAP ERP system of the closed job requisition.
7. The SAP ERP system closes the relevant record of the infotype SFSF Job Requisition (1107) with the subtype Open Job
Requisition (0001) and transfers the data to a new record with the subtype Closed Job Requisition (0002).
Process: Reopen a Closed Job Requisition

Use
The process for reopening a closed job requisition is roughly as follows:
4/26/2019
Process
1. Optional: For a position whose vacancy has been closed or delimited accidentally, the HR Administrator creates a new
vacancy or extends the validity period of the delimited vacancy. Based on this vacancy, the SAP ERP system creates a
record of the infotype SFSF Job Requisition (1107).
2. The HR Administrator uses the Reopen Job Requisition pushbutton to reopen the closed job requisition for a position.
The SAP ERP system changes the job requisition status displayed on the SFSF Job Requisition tab from Closed to To Be
Reopened.
3. Depending on whether a job requisition has already been created for the record of the infotype SFSF Job Requisition
(1107) created in step 1, the further process is as follows:
Job requisition in SuccessFactors HCM Suite is already created
a. The Web service for transferring job requisition data is run directly and transfers the information that the
job requisition needs to be closed again to SuccessFactors.
b. SuccessFactors changes the state of the job requisition ( eld jobReqStatus) to Closed and the status
( eld status) to SAPClosed, and informs the SAP ERP system of the closed job requisition.
c. The SAP ERP system deletes the relevant record of the infotype SFSF Job Requisition (1107) again.
Job requisition in SuccessFactors is not yet created
In this case, the process continues “normally”, meaning with step 4.
4. The report Create and Update Job Requisitions in SuccessFactors (RH_SFI_TRIGGER_JOB_REQUISITION) transfers
the information to SuccessFactors that the old job requisition needs to be reopened.
5. SuccessFactors changes the state of the job requisition ( eld jobReqStatus) to Approved or Pre-Approved and the
status ( eld status) to SAPReopened, and informs the SAP ERP system of the reopened job requisition.
Note
The state that the job requisition had before it was closed determines whether the state is changed to Pre-Approved
or Approved.
6. The SAP ERP system changes the job requisition status displayed on the SFSF Job Requisition tab from To Be Reopened
to Created.
Status Handling for Job Requisitions

Use
In SuccessFactors HCM Suite, a job requisition has a state and a status. Different statuses are also de ned for the job
requisition in the SAP ERP system. The following contains an overview of the status values and the status changes that occur
depending on the process step.
Features
State of Job Requisition in SuccessFactors
The state of a job requisition is stored in the eld jobReqStatus. The following table shows which states are possible and their
signi cance:
4/26/2019
State Meaning
pre-approved The job requisition can be closed and

reopened
approved The job requisition can be closed and

reopened
closed The job requisition can be reopened
Status of Job Requisition in SuccessFactors
The status of a job requisition is stored in the eld status. The following table shows which statuses are possible and their
signi cance:
Status Meaning
SAPClosed The job requisition is closed
SAPDeleted The job requisition is designated for deletion
 Note
This status is no longer used. For more information, see SAP Note 1938486
.
SAPReopened The job requisition is reopened
Note
The listed status values are those that are expected as standard. If you want to use other status values, you need to de ne
them in Customizing for the integration add-on, under Integration Scenario for Recruiting Data Transfer of Job Requisition
Data from SAP ERP to SuccessFactors BizX De ne Values of Job Requisition Status Used in SFSF .
Status of Job Requisition in SAP ERP and Effects on State and Status in SuccessFactors
The following table shows how the statuses appear in the SAP ERP system before the data transfer and how each status and
state of the job requisition are changed by the data transfer in SuccessFactors.
Process Step Status in SAP ERP Before Data Transfer Status Change in SuccessFactors After
Data Transfer
Infotype 1107: Infotype 1107: Tab: SFSF Job SuccessFactors: SuccessFactors:

Current Status Target Status (Field Requisition (Field State Change of Status Change of
(Field STATUS) TARGET_STATUS) Job Requisition Job Requisition Job Requisition
Status) (Field (Field status)
jobReqStatus)
No vacancy/record Initial Initial empty empty (job empty (job

of infotype 1107 requisition does not requisition does not
created yet exist) exist)
Record of infotype Initial Open To Be Created empty > pre- empty (remains)
1107 is created approved
4/26/2019
Process Step Status in SAP ERP Before Data Transfer Status Change in SuccessFactors After
Data Transfer
Infotype 1107: Infotype 1107: Tab: SFSF Job SuccessFactors: SuccessFactors:

Current Status Target Status (Field Requisition (Field State Change of Status Change of
(Field STATUS) TARGET_STATUS) Job Requisition Job Requisition Job Requisition
Status) (Field (Field status)
jobReqStatus)
Job requisition is Open Open Created pre-approved > empty (remains)

created in approved
SuccessFactors
Caution
The status
approved needs
to be set
manually. If this
is not done, the
status remains
pre-approved.
Position is staffed Open Closed To Be Closed Approved > Closed empty > SAPClosed
pre-approved >
closed
Job requisition was Closed Open To Be Reopened Closed > Open SAPReopened
closed, function
Reopen Job
Requisition was
performed
Job requisition is Closed Closed Closed Closed (remains) SAPClosed

closed in (remains)
SuccessFactors
Mapping of SuccessFactors Fields for Job

Requisition Data
Use
In Customizing, you de ne which job requisition data you want to export from the SAP ERP system and map to SuccessFactors
HCM Suite elds. For more information, see Transferred Fields in Transferring Job Requisition Data for Positions from SAP ERP
to SuccessFactors HCM Suite.
The following lists show which SAP ERP elds are used by default to transfer job requisition data for positions to SuccessFactors
and to which SuccessFactors elds they are mapped. These elds are assigned to the eld set SAP_REQ_DEMO. In addition to
the elds contained in this eld set, the ID of the job requisition is transferred from SuccessFactors to the SAP ERP system if a
new job requisition has been created in SuccessFactors 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 eld contents for the current date of the
data transfer and updates the job requisition in SuccessFactors accordingly as soon as the content of even only one eld has
4/26/2019
changed.
Note
For all elds 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:
Con gure the routing map for the template for job requisitions in SuccessFactors such that the originator of the job
requisition (SuccessFactors eld originator) is entered as the rst processor. The originator can process the job
requisition rst 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 de ne the hiring manager (SuccessFactors eld hiringManagerName) as the
rst processor.
Make sure that the SuccessFactors user ID of the hiring manager is transferred to the originator eld and to the
hiringManagerName eld. This is de ned in this way in the standard system.
Table 1: General Fields
Field Content SuccessFactors Field SAP ERP Object SAP ERP Field Special Features of Mapping
GUID of Job guid None None Field is required.

Requisition
Field cannot be con gured.
Is generated by the SAP ERP system during

the initial data transfer for a job requisition
and transferred to SuccessFactors.
4/26/2019
Originator of the originator None None Field is required.

job requisition
Is only transferred during the initial data
transfer for a job requisition from the SAP
ERP system to SuccessFactors.
Contains the SuccessFactors user ID that is

also transferred to the hiringManagerName
eld (see below, under Hiring Manager). If
this cannot be determined, the SAP ERP
system does not transfer any content to
SuccessFactors for this eld. Then,
SuccessFactors uses the user ID of the
technical user with which the integration
add-on logs on during the data transfer.
If you have de ned 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 eld. 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 Infotype Object Field is required.

organizational (1000), eld Object
unit ID (OBJID)
Name of position sapPositionName Position or Infotype Object

organizational (1000), eld Object
unit Name (STEXT)
Job code jobCode Job Infotype Object The SAP ERP system uses the relationship
(1000), elds describes/is described by (007) to
Object ID (OBJID) determine the job for the position.
and Object Name
The SAP ERP system concatenates the ID
(STEXT)
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 eld.
Name of job title Job or position Infotype Object Field is required.

(1000), eld Object
The SAP ERP system uses the relationship
Name (STEXT)
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 eld has the same
content as the sapPositionName eld.
4/26/2019
Description of sapJobDesc Job or position Infotype Verbal The SAP ERP system uses the relationship
job Description (1002) 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 dateCreated None None Field is required for the creation of the job
the job requisition.
requisition is
Is only considered during the initial data
created
transfer for a job requisition from the SAP
ERP system to SuccessFactors.
Contains the system date on which the job

requisition is created.
Date on which jobCloseDate None None Field is required when closing the job
the job requisition and is considered only then.
requisition is
closed
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 eld jobReqState (see
below, under Status of Job Requisition ).
State of the job jobReqStatus None None Field is required when closing and reopening
requisition the job requisition and is considered only
then.
For more information, see Status Handling

for Job Requisitions.
Status of the job Status None None Field is required when closing and reopening
requisition the job requisition and is considered only
then.
Contains the status that is de ned in

Customizing for the integration add-on,
under Integration Scenario for Recruiting
Data Transfer of Job Requisition Data
from SAP ERP to SuccessFactors De ne
Values of Job Requisition Status Used in
SFSF (by default SAPClosed, SAPDeleted,
or SAPReopened). For more information,
see Status Handling for Job Requisitions.
ID of the sapPersonnelAreaIDTxt Position or Infotype Account

personnel area to organizational Assignment
which the unit Features (1008),
position belongs eld Personnel
Area (PERSA)
4/26/2019
Name of the sapPersonnelAreaTxt Position or Table Personnel The SAP ERP system rst determines the ID
personnel area to organizational Areas (T500P), of the personnel area from the infotype
which the unit eld Personnel Account Assignment Features (1008). For
position belongs Area Text (NAME1) this ID, in the table Personnel Areas
(T500P), the SAP ERP system determines
the name that is stored in the Personnel
Area Text (NAME1) eld.
ID of the sapPersonnelSubAreaIDTxt Position or Infotype Account

personnel organizational Assignment
subarea to which unit Features (1008),
the position eld Personnel
belongs Subarea (BTRTL)
Name of the sapPersonnelSubAreaTxt Position or Table Personnel The SAP ERP system rst determines the ID
personnel organizational Area/Subarea of the personnel subarea from the infotype
subarea to which unit (T001P), eld Account Assignment Features (1008). For
the position Personnel Subarea this ID, in the table Personnel
belongs Text (BTEXT) Area/Subarea (T001P), the SAP ERP
system determines the name that is stored
in the Personnel Subarea Text (BTEXT)
eld.
ID of the sapEEGroupIDTxt Position or Infotype Employee

employee group organizational Group/Subgroup
to which the unit (1013), eld
position belongs Employee Group
(PERSG)
Name of the sapEEGroupTxt Position or Table Employee The SAP ERP system rst determines the ID
employee group organizational Group Names of the employee group from the infotype
to which the unit (T501T), eld Employee Group/Subgroup (1013). For
position belongs Employee Group this ID, in the table Employee Group Names
Name (PTEXT) (T501T), the SAP ERP system determines
the name that is stored in the Employee
Group Name (PTEXT) eld.
ID of the sapEESubGroupIDTxt Position or Infotype Employee

employee organizational Group/Subgroup
subgroup to unit (1013), eld
which the Employee
position belongs Subgroup (PERSK)
Name of the sapEESubGroupTxt Position or Table Employee The SAP ERP system rst determines the ID
employee organizational Subgroup Names of the employee subgroup from the infotype
subgroup to unit (T503T), eld Employee Group/Subgroup (1013). For
which the Employee this ID, in the table Employee Subgroup
position belongs Subgroup Name Names (T503T), the SAP ERP system
(PTEXT) determines the name that is stored in the
Employee Subgroup Name (PTEXT) eld.
ID of the sapOrgUnitID Organizational Infotype Object The SAP ERP system uses the relationship
organizational unit (1000), eld Object belongs to/contains (003) to determine
unit to which the ID (OBJID) the organizational unit for the position.
position belongs
Name of the sapOrgUnitName Organizational Infotype Object The SAP ERP system uses the relationship
organizational unit (1000), eld Object belongs to/contains (003) to determine
unit to which the Name (STEXT) the organizational unit for the position.
position belongs
4/26/2019
Hiring manager hiringManagerName Person None The SAP ERP system rst 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 nds rst. 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 user ID of the manager.
Name of position hiringManagerJobTitle Position or Infotype Object The SAP ERP system rst uses the
of the hiring organizational (1000), eld Object relationship belongs to/contains (003) to
manager unit Name (STEXT) 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) eld.
ID of the cost costCenterId Cost center Infotype The SAP ERP system uses the relationship
center to which Relationships Cost Center Assignment (A011) to
the position (1001), eld ID of determine the cost center.
belongs Related Object
(SOBID)
Country of the country Position or Table Personnel The SAP ERP system rst determines the ID
personnel area to organizational Areas (T500P), of the personnel area from the Personnel
which the unit eld Country Key Area eld (PERSA) of the infotype Account
position belongs (LAND1) 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) eld.
 Recommendation
The country eld is often de ned as a
required eld in the templates for job
requisitions in SuccessFactors.
Therefore, to avoid the data transfer
failing, ensure that the country key is
de ned in the HR master data, or that it
can be determined in another way.
4/26/2019
Region (for sapState Position or Table Taxes: The SAP ERP system rst determines the ID
example, state or organizational Province Key: of the personnel area from the Personnel
province) of the unit Texts (T005U), Area eld (PERSA) of the infotype Account
personnel area to eld Name Assignment Features (1008). For this ID, in
which the (BEZEI) the table Personnel Areas (T500P), the
position belongs SAP ERP system determines the key for the
region that is stored in the Region (State,
Province, County) (REGIO) eld. 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) eld.
City of the city Position or Table Personnel The SAP ERP system rst determines the ID
personnel area to organizational Areas (T500P), of the personnel area from the Personnel
which the unit eld City (ORT01) Area eld (PERSA) of the infotype Account
position belongs Assignment Features (1008). For this ID, in
is stored in the City (ORT01) eld.
Postal code of postalcode Position or Table Personnel The SAP ERP system rst determines the ID
the personnel organizational Areas (T500P), of the personnel area from the Personnel
area to which the unit eld Postal Code Area eld (PERSA) of the infotype Account
position belongs (PSTLZ) Assignment Features (1008). For this ID, in
is stored in the Postal Code (PSTLZ) eld.
Table 2: Fields of the Infotype Planned Compensation (1005) with the Planned Compensation Type Salary
Field Content SuccessFactors Infotype Field Special Features of Mapping

Field
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 salaryMin Lower Limit of Pay Grade If the eld is empty, the SAP ERP system
level Level (CPMIN) transfers the value 0 to SuccessFactors.
Maximum salary in pay grade salaryMax Upper Limit of Pay Grade If the eld is empty, the SAP ERP system
level Level (CPMAX) transfers the value 0 to SuccessFactors.
Medium salary in pay grade level salaryMid Midpoint (MIDPT) If the eld is empty, the SAP ERP system
transfers the value 0 to SuccessFactors.
Unit of time that is used to sapCompTimeUnit Time Unit for

calculate the salary (for Compensation (FREQU)
example, monthly)
4/26/2019
Table 3: Fields of the Infotype Planned Compensation (1005) with the Planned Compensation Type Pay Scale

Field
Pay scale type sapPayScaleType Pay Scale/Grade Type

(TRFAR)
Pay scale area sapPayScaleArea Pay Scale/Grade Region

(TRFGB)
Employee subgroup grouping for sapCap ES Grouping for Collective

collective agreement provisions Agreement Provisions
(TRFKZ)
Pay scale group sapPayScaleGroup Highest Permitted Group

(TRFG1)
Pay scale level sapPayScaleLevel Lowest Permitted Level

(TRFS1)
Minimum salary in pay scale level salaryMin Lower Limit of Pay Grade If the eld is empty, the SAP ERP
Level (CPMIN) system transfers the value 0 to
SuccessFactors.
Maximum salary in pay scale level salaryMax Upper Limit of Pay Grade If the eld is empty, the SAP ERP
Level (CPMAX) system transfers the value 0 to
SuccessFactors.
Unit of time that is used to calculate sapCompTimeUnit Time Unit for Compensation
the salary (for example, monthly) (FREQU)
Table 4: Fields of the Infotype Planned Compensation (1005) with the Planned Compensation Type Direct

Field
Minimum salary salaryMin Lower Limit of Pay Grade If the eld is empty, the SAP ERP system
Level (CPMIN) transfers the value 0 to SuccessFactors.
Maximum salary salaryMax Upper Limit of Pay Grade If the eld is empty, the SAP ERP system
Level (CPMAX) transfers the value 0 to SuccessFactors.
Unit of time that is used to sapCompTimeUnit Time Unit for

calculate the salary (for Compensation (FREQU)
example, monthly)
Table 5: Other Fields of Infotype Planned Compensation (1005)

Field
Planned compensation type sapPayType Type of Planned

Compensation (CPIND)
Note
The infotype Planned Compensation is de ned for either the position or the job. If the infotype elds cannot be determined
for the position, the SAP ERP system uses those for the job.
4/26/2019
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 eld sapPayType.
Therefore, the content for the same SuccessFactors eld can come from SAP ERP elds that belong to different planned
compensation types.
 Example
You can transfer the following information to the SuccessFactors eld 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)

De nition
Infotype in which the SAP ERP system stores information on a position that refers to the process with which the creation of a
job requisition in SuccessFactors HCM Suite is triggered from the SAP ERP system.
The infotype SFSF Job Requisition contains information that the SAP ERP system requires to trigger the creation of a job
requisition for the position in SuccessFactors. It also contains information on the current status in the data transfer process.
Create Infotype Records
If you use vacancies for positions in your SAP ERP system, the infotype SFSF Job Requisition re ects the infotype Vacancy
(1007) for the position. This means that if a record of the infotype Vacancy is created for the position, the SAP ERP system also
creates a record for the infotype SFSF Job Requisition automatically. If the record of the infotype Vacancy is delimited or
deleted, the corresponding record of the infotype SFSF Job Requisition is also delimited or deleted.
Note
In exceptional circumstances, there may be records of the infotype Vacancy for which no records of the infotype SFSF Job
Requisition exist (for example, if a record of the infotype Vacancy is created that has the status Closed or for which the
validity period is completely in the past).
You use the switch PPVAC to specify whether you use vacancies for positions in your SAP ERP system. For this, in
Customizing for Organizational Management, under Infotype Settings, perform the activity Activate/Deactivate “Vacancy”
Infotype.
If you do not use vacancies for positions in your SAP ERP system, the HR Administrator creates the records of the infotype SFSF
Job Requisition manually. To do so, he or she uses the SFSF Job Requisition tab in the Organization and Staffing applications.
For more information, see Editing of Positions in the SAP ERP System to Create Job Requisitions in SuccessFactors HCM Suite.
4/26/2019
Delete Infotype Records
If you use vacancies for positions in your SAP ERP system, the SAP ERP system deletes the infotype record with the subtype
Open Job Requisition (0001) when the vacancy is closed.
If you do not use vacancies for positions in your SAP ERP system, the SAP ERP system deletes the infotype record with the
subtype Open Job Requisition (0001) when the HR Administrator manually closes the infotype record on the SFSF Job
Requisition tab.
In both cases, the SAP ERP system proceeds as follows:
If data has already been transferred to SuccessFactors for the infotype record with the subtype Open Job Requisition,
the SAP ERP system creates an infotype record with the subtype Closed Job Requisition (0002) and transfers the data
to this infotype record. It then deletes the infotype record with the subtype Open Job Requisition.
If no data has yet been transferred to SuccessFactors for the infotype record with the subtype Open Job Requisition, the
SAP ERP system deletes this infotype record without creating a record with the subtype Closed Job Requisition.
Structure
Subtypes
The infotype SFSF Job Requisition has the following subtypes:
Open Job Requisition (0001)
This subtype has the time constraint 2. This means that there can be a maximum of one valid infotype record at any one
time. Overlapping is not allowed. It is not mandatory that an infotype record exists. If a new infotype record is created,
the SAP ERP system delimits any existing previous record. If the system delimits a record based on time constraint 2, it
issues a corresponding message.
This ensures that only one open job requisition ever exists for a position.
Closed Job Requisition (0002)
This subtype has the time constraint 3. This means that there can be any number of valid infotype records at any one
time. It is not mandatory that an infotype record exists.
This ensures that multiple closed job requisitions can exist for a position such that you can trace the history of the job
requisitions for the position.
Field Part
In the eld part of the infotype SFSF Job Requisition, the SAP ERP system de nes the following information:
Date on which the job requisition was created in SuccessFactors
This eld contains the point at which the SAP ERP system sent the Web service to SuccessFactors to create a new job
requisition there. This date is only transferred to SuccessFactors during the rst data transfer.
ID of the job requisition that was created in SuccessFactors
Globally unique identi er (GUID) of the job requisition that was created in SuccessFactors
ID of the template that was used in SuccessFactors to create the job requisition
The SAP ERP system uses the Business Add-In (BAdI) Determination of Job Requisition Template from SFSF
(HRSFI_B_TEMPLATE_DETERMINATION) to determine the template when creating the infotype record. For the BAdI,
4/26/2019
see Customizing for the integration add-on, under Integration Scenario for Recruiting Data Transfer of Job Requisition
Data from SAP ERP to SuccessFactors BizX .
Caution
The template for job requisitions is determined only once. If the template is changed retroactively, the infotype SFSF
Job Requisition does not consider these changes.
Name of position
The name is only transferred to SuccessFactors during the rst transfer of data since it is usually changed in
SuccessFactors. If the name were to be transferred again, the name created in SuccessFactors would be overwritten.
Status of the job requisition as it was most recently successfully transferred from the SAP ERP system to
SuccessFactors (for example, Open)
Status of the job requisition as it will be transferred from the SAP ERP system to SuccessFactors during the next
transfer of data (for example, Closed)
Status of the last data transfer (for example, Successfully Transferred or Error)
Transfer mode for the job requisition
The SAP ERP system uses the following modes:
Forced transfer
This mode is set if the validity period of an existing infotype record is moved completely to the past. The SAP ERP
system closes this infotype record automatically. Since the data transfer report would not consider the infotype
record, the SAP ERP system sets this mode to ensure that the data is transferred anyway and that the job
requisition is also closed in SuccessFactors.
Postponed transfer
This mode is set if the validity period of an existing infotype record is moved completely to the future. Since the
data transfer report would not consider this infotype record, the SAP ERP system sets this mode to ensure that
the data is transferred with the status Closed anyway. When the validity period of the infotype record has been
reached, the data is transferred again, this time with the status Open.
No transfer
This mode is set if, in your SAP ERP system, records already exist for the infotype Vacancy with a current validity
period at the time at which you activate the use of the infotype SFSF Job Requisition. For such vacancies the
standard SAP ERP system generates records of the infotype SFSF Job Requisition, but sets the transfer mode No
Transfer. These infotype records are not transferred to SuccessFactors because it is possible that manual job
requisitions have already been created for such vacancies.
Note
You can de ne that existing vacancies are also to be considered during the data transfer. For example, this is
useful if you have not yet created any job requisitions for SAP ERP positions in SuccessFactors. To do so, in
Customizing, choose Integration Scenario for Recruiting Data Transfer of Job Requisition Data from SAP
ERP to SuccessFactors BizX , and perform the activity Specify Handling of Existing Vacancies During Data
Transfer.
Date on which the job requisition was closed in SuccessFactors
ID of the application that was created in SuccessFactors based on the job requisition and that was transferred to the
SAP ERP system
4/26/2019
The SAP ERP system stores this information in the infotype when an application that was received in SuccessFactors for
the job requisition was transferred to the SAP ERP system. For more information, see Integration Scenario Process for
Recruiting Data.
Personnel number of the employee in the SAP ERP system who was hired based on the application transferred from
SuccessFactors
the job requisition was transferred to the SAP ERP system and the candidate was hired as a new employee. For more
information, see Integration Scenario Process for Recruiting Data (see above).
User ID of the employee for SuccessFactors that has been derived from the personnel number
the job requisition was transferred to the SAP ERP system, the candidate was hired as a new employee, and a user ID
was returned to SuccessFactors. For more information, see Integration Scenario Process for Recruiting Data (see
above).
Handle for the related application log
If errors occur during the data transfer, the data transfer report stores corresponding error messages in the report log
and in the application log. To establish the connection between the infotype record and the corresponding error
messages, it stores a handle for the application log in this eld.
State (pre-approved or approved) that the job requisition had before it was closed
For more information, see Status Handling for Job Requisitions.
Table Part
The table part of the infotype SFSF Job Requisition contains a list of SuccessFactors elds, each with eld label and eld
content. The table part contains all data that was transferred from the SAP ERP system to SuccessFactors for the position to
create or change a job requisition there.
You de ne which data is transferred in Customizing. You create eld mappings and assign these the templates for job
requisitions from SuccessFactors. For more information, see Transferred Fields in Transferring Job Requisition Data for Positions
from SAP ERP to SuccessFactors HCM Suite.
More Information
Change Existing Vacancies and Effects on the Job Requisition
Change Existing Vacancies and Effects on

the Job Requisition
Use
If you use vacancies for positions in your SAP ERP system, changes to records of the infotype Vacancy (1007) result in
corresponding changes to the infotype SFSF Job Requisition (1107) and therefore to the job requisition in SuccessFactors HCM
Suite.
Features
Change to Infotype 1007 Effect on Infotype 1107 Effect on SuccessFactors
4/26/2019
Change to Infotype 1007 Effect on Infotype 1107 Effect on SuccessFactors
HR Administrator creates vacancy that is SAP ERP system creates infotype record Job requisition is created
valid from the current system date that is valid from the current system date
HR Administrator moves the valid-from SAP ERP system moves the valid-from date Job requisition remains unchanged
date of an existing vacancy to an earlier of the infotype record to an earlier date
date
HR Administrator moves the valid-from SAP ERP system moves the valid-from date Job requisition is closed
date of an existing vacancy to a future date of the infotype record to a future date and
sets the data transfer mode Postponed New job requisition is created when the
Transfer since the data transfer report valid-from date of the vacancy has been
would not consider this infotype record reached
otherwise. The data transfer mode
Postponed Transfer ensures that the data
with the target status Closed is transferred
anyway. When the validity period of the
infotype record has been reached, the data
is transferred again, this time with the
target status Open.
HR Administrator moves the entire validity SAP ERP system deletes infotype record. If Job requisition is closed
period of an existing vacancy to an earlier data has already been transferred to
date SuccessFactors for the infotype record and
the job requisition has the status Approved
there, the SAP ERP system rst creates an
infotype record with the subtype Closed
Job Requisition (0002) and transfers the
data to this infotype record. In this infotype
record, it sets the transfer mode Forced
Transfer since otherwise the data transfer
report would not consider the infotype
record. The transfer mode Forced Transfer
ensures that the data is transferred anyway
and that the job requisition is thereby
closed in SuccessFactors.
More Information
Overview of Open Job Requisitions for

Positions
Use
The HR administrator can obtain an overview of which open job requisitions there are in SuccessFactors HCM Suite for the
positions of an organizational unit. He or she also has a structure view and list view available.
Prerequisites
See Transferring Job Requisition Data for Positions from SAP ERP to SuccessFactors HCM Suite.
4/26/2019
You also need to activate the display of the overviews of open job requisitions in the Organization and Staffing applications. To
do so, in Customizing for the integration add-on, choose Integration Scenario for Recruiting Data Transfer of Job Requisition
Data from SAP ERP to SuccessFactors BizX , and perform the activity Display Infotype SFSF Job Requisition in Organizational
Mgmt Applications.
Features
Call Structure or List View
The HR Administrator displays the overviews of the open job requisitions when editing the organizational structure. To do so, he
or she selects an organizational unit in the Organization and Staffing applications. He or she then chooses the Goto pushbutton
and then the SFSF Job Requisition (Structure) or SFSF Job Requisition (List) entry.
The overviews are available in the following applications:
Create Organization and Staffing (transaction PPOCE)
This application is located in the SAP Easy Access menu, under Organizational Management Organizational
Structure Organization and Staffing Create .
Change Organization and Staffing (transaction PPOME)
Structure Organization and Staffing Change .
Display Organization and Staffing (transaction PPOSE)
Structure Organization and Staffing Display .
Use the Structure View
The structure view shows the organizational unit with the assigned positions as a tree. If other organizational units are assigned
to the organizational unit, these are also displayed with the assigned positions, and so on.
For each position, the HR Administrator can display the following information in the structure view:
ID, abbreviation, and name of the position
Validity period of the position assignment to the organizational unit
Validity period of the position
Position holder
Number of open job requisitions
This column displays how many records of the infotype SFSF Job Requisition with the subtype Open Job Requisition
(0001) exist for the position.
Note
Only one job requisition can be open for the position at any one time. However, depending on the chosen preview
period, more than one open job requisition can be displayed here: a current one and one or more that are in the
future.
Information on whether messages exist for the infotype record
4/26/2019
If there are messages, this column displays a corresponding icon. The HR Administrator can double click the entry to
access the SFSF Job Requisition tab for this position and display the messages there.
Suite, in the Display Error Messages section.
Use List View
The list view displays a at list of all positions that are assigned to the organizational unit directly or indirectly. It displays a
separate entry for each record of the infotype SFSF Job Requisition with the subtype Open Job Requisition (0001). Therefore,
multiple entries may exist for the same position (see above, under Use Structure View).
For each position, the HR Administrator can display the following information in the list view:
ID, abbreviation, and name of the position
ID of the template that is used in SuccessFactors to create the job requisition
Status of the job requisition
Suite, in the Check Status of the Job Requisition section.
ID of the job requisition that is created in SuccessFactors
Validity period of the position
Validity period of the record of the infotype SFSF Job Requisition
Position holder
Organizational unit to which the position is assigned
If messages exist, this column displays a corresponding icon (see above, under Use Structure View).
Con gure Displayed Columns
The HR Administrator can show and hide columns in both views. To do so, he or she chooses the Column Con guration
pushbutton.
Note
The information listed above for the structure view and the list view is then visible if the HR Administrator has shown all
available columns.
Editing of Positions in SAP ERP to Create Job

Requisitions
Use
On the SFSF Job Requisition tab in the Organization and Staffing applications, the HR Administrator can display (if you use
vacancies for positions in your SAP ERP system) or create (if you do not use vacancies for positions) records of the infotype
SFSF Job Requisition (1107) for positions. He or she can display additional information such as the elds and eld contents
transferred to SuccessFactors HCM Suite, or the current status of the job requisition. If errors occurred when transferring the
4/26/2019
position data to SuccessFactors or when creating the job requisition, the HR Administrator can obtain an overview of the
relevant error messages.
Prerequisites
See Transferring Job Requisition Data for Positions from SAP ERP to SuccessFactors HCM Suite.
You also need to activate the display of the SFSF Job Requisition tab in the Organization and Staffing applications. To do so, in
Customizing for the integration add-on, choose Integration Scenario for Recruiting Data Transfer of Job Requisition Data from
SAP ERP to SuccessFactors BizX , and perform the activity Display Infotype SFSF Job Requisition in Organizational Mgmt
Applications.
Features
Call Applications for Editing the Infotype SFSF Job Requisition
The HR Administrator checks or edits records of the infotype SFSF Job Requisition when editing the organizational structure in
the details for a position. To do so, he or she uses the SFSF Job Requisition tab in one of the following applications:
Create Organization and Staffing (transaction PPOCE)
Structure Organization and Staffing Create .
Change Organization and Staffing (transaction PPOME)
Structure Organization and Staffing Change .
Display Organization and Staffing (transaction PPOSE)
Structure Organization and Staffing Display .
Create and Change Records of the Infotype SFSF Job Requisition
The way in which the HR Administrator proceeds when editing records of the infotype SFSF Job Requisition depends on whether
you use the infotype Vacancy (1007) in your SAP ERP system:
If you use the infotype Vacancy, the HR Administrator edits records of this infotype.
In this case, the infotype SFSF Job Requisition always re ects the infotype Vacancy exactly for the position:
If the HR Administrator sets a position as vacant and thereby creates a record of the infotype Vacancy for the
position, the SAP ERP system also creates a record of the infotype SFSF Job Requisition with the subtype Open
Job Requisition (0001) automatically.
If the HR Administrator closes the vacancy for the position and thereby deletes the record of the infotype
Vacancy, the SAP ERP system also deletes the corresponding record of the infotype SFSF Job Requisition with
the subtype Open Job Requisition (0001). It transfers the data to an infotype record with the subtype Closed Job
Requisition (0002).
Note
If you use the infotype Vacancy in your SAP ERP system, the HR Administrator cannot create or edit records of the
infotype SFSF Job Requisition on the SFSF Job Requisition tab. In this case, the SFSF Job Requisition tab is used only
to display the infotype records. An exception is reopening a closed job requisition (see below).
4/26/2019
If you do not use the infotype Vacancy, the HR Administrator processes records of the infotype SFSF Job Requisition
manually on the SFSF Job Requisition tab:
To create an infotype record with the subtype Open Job Requisition (0001), he or she chooses the Create Job
Requisition pushbutton.
The elds for the infotype record are already lled with content. The HR Administrator enters the validity period
and saves the data. The SAP ERP system then uses the Business Add-In (BAdI) Determination of Job Requisition
Templates from SFSF (HRSFI_B_TEMPLATE_DETERMINATION) to determine the suitable template for job
requisitions from SuccessFactors and saves the infotype record.
Note
When the infotype record has been created, the text of the Create Job Requisition pushbutton changes to
Close Job Requisition.
To delete an infotype record, the HR Administrator chooses the Close Job Requisition pushbutton. The SAP ERP
system deletes the corresponding record with the subtype Open Job Requisition (0001) and transfers the data to
an infotype record with the subtype Closed Job Requisition (0002).
Display Open and Closed Job Requisitions for the Position
The SFSF Job Requisition tab contains the following information on open and closed job requisitions for the position:
The upper area of the screen displays the open job requisition that currently exists in SuccessFactors for the position or
that is created after the next data transfer. This means that the infotype record with the subtype Open Job Requisition
(0001) that exists for the current validity period is displayed.
The following information is displayed for the open job requisition:
Validity period of the infotype record
Status of the job requisition
ID and name of the template that was used in SuccessFactors to create the job requisition
ID of the job requisition
The lower area of the screen displays all closed job requisitions that exist in SuccessFactors for the position. This means
that all infotype records with the subtype Closed Job Requisition (0002) are displayed here.
The following information is displayed for the closed job requisition:
Validity period of the infotype record
ID of the job requisition
ID of the application that was created in SuccessFactors based on the job requisition and that was transferred to
the SAP ERP system
Personnel number of the employee in the SAP ERP system who was hired based on the application transferred
from SuccessFactors
User ID of the employee for SuccessFactors that has been derived from the personnel number
ID of the template that was used in SuccessFactors to create the job requisition
Reopen a Closed Job Requisition
4/26/2019
If the HR Administrator has closed the job requisition for a position by closing the vacancy or on the SFSF Job Requisition tab,
he or she can reopen this job requisition for the position. To do so, he or she chooses the Reopen Job Requisition pushbutton.
Note
The Reopen Job Requisition function is available only if the buffer does not contain any additional changes for the position. If
at the time at which the HR Administrator chooses the Reopen Job Requisition pushbutton, there are changes in the buffer,
he or she is prompted to save this data. Only then can he or she reopen the job requisition.
To reopen the same job requisition for the position, the SAP ERP system proceeds as follows:
1. It copies the data from the existing record of the infotype SFSF Job Requisition that was closed to the new infotype
record to be created and stores this in the buffer.
2. It uses a Web service to send the information to SuccessFactors that the job requisition needs to be closed there.
3. When SuccessFactors has closed the job requisition, it sends this information as a synchronous response to the SAP
ERP system.
4. The SAP ERP system saves the data stored in the buffer to the database immediately.
Since the SAP ERP needs to wait for the response from SuccessFactors before it can save the data, this process can result in
a waiting time for the HR Administrator. If the HR Administrator has reopened the job requisition, this information is
transferred to SuccessFactors the next time the data transfer report is run.
Caution
If the HR Administrator has simply created a new vacancy or a new record of the infotype SFSF Job Requisition for the
position, a new job requisition is also created in SuccessFactors. Therefore, if the HR Administrator wants to reuse the same
job requisition, he or she always needs to use the function Reopen Job Requisition on the SFSF Job Requisition tab.
Check Status of the Job Requisition
The SFSF Job Requisition tab displays the following status for the job requisition:
Status Description
empty No record of the infotype SFSF Job Requisition with the subtype Open Job Requisition (0001) exists.
To Be A new record of the infotype SFSF Job Requisition has been created. The data for this infotype record has not yet been
Created transferred to SuccessFactors. The next time the data transfer report is run, a job requisition with the status Open is created
in SuccessFactors.
Created In SuccessFactors, a new job requisition with the status Open has been created.
To Be The record of the infotype SFSF Job Requisition has been closed. The data for this infotype record has not yet been
Closed transferred to SuccessFactors. The next time the data transfer report is run, the status Closed is set for the job requisition in
SuccessFactors.
Closed The job requisition has been closed in SuccessFactors.
To Be The record of the infotype SFSF Job Requisition has been closed. The job requisition has been closed in SuccessFactors.
Reopened The HR Administrator has performed the Reopen function. The next time the data transfer report is run, the status Open is
reset for the same job requisition in SuccessFactors.
Note
4/26/2019
The SAP ERP system determines the displayed status from the combination of statuses that is de ned for the infotype
record in the elds SFSF Job Requisition: Current Status (STATUS) and SFSF Job Requisition: Target Status
(TARGET_STATUS). See also Status Handling for Job Requisitions.
Display Fields and Field Contents Transferred to SuccessFactors
The HR Administrator can display the data that was transferred to SuccessFactors for both open and closed job requisitions the
last time the data transfer report was run. To do so, he or she chooses the Display Fields pushbutton.
Note
Whether the HR Administrator can display the elds and eld contents depends on whether he or she has the necessary
authorizations. You use the BAdI Authorization Check for SFSF Integration (HRSFI_B_AUTHORITY_CHECK) to de ne the
authorizations. For the BAdI, see Customizing for the integration add-on, and choose Basic Settings.
Display Error Messages
If errors occurred during the transfer of position data to SuccessFactors or when creating the job requisition, the Messages
pushbutton is shown on the SFSF Job Requisition tab. The HR Administrator can use this to display all messages for the current
infotype record.
In the lower area, the SAP ERP system then displays the messages for the open job requisition instead of the closed job
requisitions. The text of the pushbutton changes from Messages to Closed Job Requisitions. To display the closed job
requisitions again, the HR Administrator chooses this pushbutton again.
Note
If errors occurred, the position data is transferred again the next time the data transfer report is run.
More Information
Integration Scenario Process for Recruiting Data
Overview of Open Job Requisitions for Positions of an Organizational Unit
Transfer of Applications from

SuccessFactors to SAP ERP
Use
You can extract applications from SuccessFactors HCM Suite and transfer them to the SAP ERP system. In the SAP ERP
system, based on the transferred data, you can perform a personnel action to hire the candidates as employees. You can then
use the personnel numbers of the new employees to derive their user ID for SuccessFactors and return these to
SuccessFactors.
Prerequisites
In Recruiting of SuccessFactors, the following settings are de ned for the object JobApplication:
4/26/2019
The eld sapError is available.
For the eld Application Status (RCM_APP_STATUS_STATUS_NAME), the status category Hire contains the
following possible statuses in the selection list CandidateStatus:
SendToSAP
TransferredToSAP
TransferredToSAPError
HiredAtSAP
The status category Hire can be ltered.
SuccessFactors contains at least one ad hoc report for recruiting data that ful lls the following prerequisites:
The ad hoc report must contain the following elds otherwise the corresponding data records cannot be imported
into SAP ERP:
Application ID (RCM_APPLICATION_CAN_JOB_MAP_ID, object JobApplication)
Application ID (RCM_APP_STATUS_STATUS_NAME, object JobApplication)
Template ID (APP_TEMPLATE_APP_TEMPLATE_ID, object JobApplication)
Start Date (OFFER_DETAIL_LATEST_JOB_REQ_JOB_START_DATE, object LastOfferDetail)
Note
In Customizing, under Integration Scenario for Recruiting Data Map SuccessFactors BizX Fields and SAP
ERP Fields to Each Other , these elds are automatically added to the eld sets.
We strongly recommend that the ad hoc report also contains the following elds since they are required for the
integration scenario to run correctly and to create records for the infotypes Actions (0000), Organizational
Assignment (0001), Personal Data (0002), and Payroll Status (0003):
First Name (RCM_APPLICATION_FIRSTNAME, object JobApplication)
Last Name (RCM_APPLICATION_LASTNAME, object JobApplication)
Gender (RCM_APPLICATION_GENDER, object JobApplication)
Date of Birth (RCM_APPLICATION_DOB, object JobApplication)
SAP Position ID (RCM_JOB_REQ_EXT_TEXT1, object Job Requisition)
The following static lters need to be set for the ad hoc report:
Application Status (RCM_APP_STATUS_STATUS_NAME):
Must have the value SendToSAP.
Template ID (APP_TEMPLATE_APP_TEMPLATE_ID):
If you use multiple ad hoc reports, for example, to separate the applications by organizational criteria, you
need to lter the Template ID eld accordingly to de ne which ad hoc report is to extract which
applications.
We strongly recommend that the ad hoc report contains all elds for which content is to be transferred to SAP
ERP and that you have mapped to SAP ERP elds in Customizing. The ad hoc report must contain the elds that
you have indicated as Required in Customizing. The technical eld names in SuccessFactors must correspond
exactly to the eld names as de ned in Customizing.
4/26/2019
Caution
The XML templates for the SuccessFactors objects must also contain all required elds.
Recommendation
Contact the Professional Service team of SuccessFactors so that the correct settings are made, suitable ad hoc
reports are created, and the correct XML templates are provided.
In Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite, you have made the following
settings:
Under Basic Settings:
De ne Authorizations (Recruiting Data)
BAdI: Authorization Check for SFSF Integration
Import Metadata from SuccessFactors BizX
BAdI: Determination of SAP ERP Personnel Numbers and SFSF User IDs
Settings for Middleware Store Credentials for Transferring Recruiting Data in Secure Storage
Settings for Middleware De ne Package Size for Transfer of Recruiting Data
Under Integration Scenario for Recruiting Data:
Activate Additional Functions
Map SuccessFactors BizX Fields and SAP ERP Fields to Each Other
Check and Correct Field Sets
All Customizing activities in the section Transfer of Applications from SuccessFactors BizX to SAP ERP
You are using Adobe Document Services. For more information, look for Adobe Document Services Con guration Guide
in the documentation of SAP NetWeaver at http://help.sap.com .
You need the Adobe Document Services so that the HR Administrator can display a PDF overview of the eld contents
transferred from SuccessFactors and mapped in the SAP ERP system in the application for the further processing of
imported applications (transaction HRSFI_RCT_HIRE)
Features
Data Import
For the import of applications into the SAP ERP system, you can use the report Importing Recruiting Data from SFSF
(RH_SFI_IMPORT_RECRUITING_DATA). For more information about the report, see Customizing for the integration add-on
and choose Integration Scenario for Recruiting Data Transfer of Applications from SuccessFactors BizX to SAP ERP Import
Applications into SAP ERP . The report is also located in the user menu of the role SuccessFactors Integration: Recruiting
(SAP_HR_SFI_RECRUITING).
Imported Fields
In Customizing, you de ne which eld contents you want to import from SuccessFactors. To do so, you de ne eld sets. A eld
set contains multiple SuccessFactors elds that you map to the SAP ERP elds of your choice. You have the following options:
You map the elds to each other directly, using a table.
4/26/2019
For more information, see Customizing and choose Integration Scenario for Recruiting Data Map SuccessFactors BizX
Fields and SAP ERP Fields to Each Other .
To make more complex mappings, you can create a Business Add-In implementation (BAdI implementation). You can use
the following BAdIs for this:
Mapping of SFSF Fields to SAP ERP Infotype Fields (HRSFI_B_FIELD_MAPPING)
You can use this BAdI to map a SuccessFactors eld to an SAP ERP eld.
For the BAdI, see Customizing and choose Integration Scenario for Recruiting Data Transfer of Applications
from SuccessFactors BizX to SAP ERP BAdI: Mapping of SFSF Fields to SAP ERP Infotype Fields .
Mapping of SFSF Fields to ERP Infotype Fields: Change of Mapping Result

(HRSFI_B_CHANGE_MAPPING_RESULT)
You can use this BAdI to map one or more SuccessFactors elds to one or more SAP ERP elds.
For the BAdI, see Customizing and choose Integration Scenario for Recruiting Data Transfer of Applications
from SuccessFactors BizX to SAP ERP BAdI: Mapping of SFSF Fields to SAP ERP Infotype Fields .
As standard, some mappings of SuccessFactors elds to SAP ERP elds are de ned.
Caution
The mapping of the elds is different, depending on whether you use only the scenario for transferring applications from
SuccessFactors to SAP ERP, or also use the scenario for transferring job requisition data for positions from SAP ERP to
SuccessFactors. For more information, see the following:
Mapping of SFSF Fields for Application Data to SAP ERP Fields (Without Data Transfer for Job Requisition Data)
Mapping of SFSF Fields for Application Data to SAP ERP Fields (with Data Transfer for Job Requisition Data)
Further Processing of Imported Data
You can check the data imported from SuccessFactors and complete it as required. You can then use a personnel action to
transfer the data to the SAP ERP system. For more information, see Further Processing of Imported Applications in the SAP
ERP System.
Updating Candidate Data in SuccessFactors After Hiring in SAP ERP
After you have transferred a candidate from SuccessFactors to SAP ERP Personnel Administration as a new employee, you can
derive a user ID for SuccessFactors from the SAP ERP personnel number and transfer this to SuccessFactors. SuccessFactors
stores this user ID in the object Candidate and thereby establishes a relationship between the data for the external candidate
who applied using SuccessFactors and the data of the new employee who has been hired using Personnel Administration in the
SAP ERP system.
You have the following options for deriving a user ID from the employee's personnel number:
You use the employee's central person (CP).
You use the ID that is stored for the employee in the eld External Person ID (PERSONID_EXT) of the infotype Person ID
(0709).
You use a customer-speci c implementation of the Business Add-In (BAdI) Replication of Employee's Data
(HRSFI_B_EMPL_DATA_REPLICATION).
4/26/2019
For more information, see Customizing for the integration add-on and choose Integration Scenario for Recruiting
Data Transfer of Applications from SuccessFactors BizX to SAP ERP Transfer User ID to SFSF After Transferring Candidate to
SAP ERP .
Note
You need to activate this function in Customizing. To do so, under Integration Scenario for Recruiting Data Activate
Additional Functions , set the parameter CANDIDATE_UPDATE_ACTIVE to X.
Mapping of SuccessFactors Fields for

Application Data to SAP ERP Fields (Without
Data Transfer for Job Requisition Data)
Use
In Customizing, you de ne which application data you want to import from SuccessFactors HCM Suite and map to SAP ERP
elds. For more information, see Imported Fields in Transfer of Applications from SuccessFactors HCM Suite to SAP ERP.
The following list shows which SuccessFactors elds are used by default to transfer applications to the SAP ERP system and to
which SAP ERP elds they are mapped. These elds are mapped to the eld set SAP_DEMO_01.
Caution
You can use the eld mappings as de ned in this eld set only if you do not use the scenario for transferring job requisition
data for positions from SAP ERP to SuccessFactors. If you use this scenario, you need to use eld mappings as de ned in the
eld set SAP_DEMO_02 to transfer applications from SuccessFactors to SAP ERP.
Note
The difference between the eld sets is that the following elds are de ned as elds with selection lists in the eld set
SAP_DEMO_01 and as text elds in the eld set SAP_DEMO_02:
Personnel area in the SAP ERP system
ID of personnel area in the SAP ERP system
Personnel subarea in the SAP ERP system
ID of personnel subarea in the SAP ERP system
Employee group in the SAP ERP system
ID of the employee group in the SAP ERP system
Employee subgroup in the SAP ERP system
ID of employee subgroup in the SAP ERP system
This is for the following reason:
If you use only the scenario for transferring applications from SuccessFactors to SAP ERP, no eld contents are
transferred from the SAP ERP system to SuccessFactors for these elds. Therefore, the user needs to make manual
entries in these elds in SuccessFactors. The selection lists help the user with this.
4/26/2019
If, in addition to the scenario for transferring applications from SuccessFactors to SAP ERP, you also use the scenario
for transferring job requisition data for positions from SAP ERP to SuccessFactors, eld contents are transferred
from the SAP ERP system to SuccessFactors for these elds. Therefore, the user is not to make any entries in these
elds in SuccessFactors and does not require any selection lists.
Field Content SuccessFactors SuccessFactors Field (Ad Hoc Report) SAP ERP Field
Object
Application ID JobApplication RCM_APPLICATION_CAN_JOB_MAP_ID
Application JobApplication RCM_APP_STATUS_STATUS_NAME

status
Applicant ID JobApplication RCM_APPLICATION_CANDIDATE_ID
Template ID JobApplication APP_TEMPLATE_APP_TEMPLATE_ID
Export date JobApplication RCM_APPLICATION_EXPORTED_ON
First name JobApplication RCM_APPLICATION_FIRSTNAME Infotype Perso

(0002), eld F
Name (VORNA
Last name JobApplication RCM_APPLICATION_LASTNAME Infotype Perso

(0002), eld L
Name (NACHN
Middle name JobApplication RCM_APPLICATION_MIDDLE_NAME Infotype Perso

(0002), eld M
Name (MIDNM
4/26/2019
Object
Gender JobApplication RCM_APPLICATION_GENDER Infotype Perso

(0002), eld F
Address Key (
Date of birth JobApplication RCM_APPLICATION_DOB Infotype Perso

(0002), eld D
Birth (GBDAT)
Address JobApplication RCM_APPLICATION_ADDRESS Infotype Addre

(0006), subtyp
Permanent Re
(1), eld Street
House Numbe
(STRAS)
City JobApplication RCM_APPLICATION_CITY Infotype Addre

(0006), subtyp
Permanent Re
(1), eld City (
Zip code JobApplication RCM_APPLICATION_ZIP Infotype Addre

(0006), subtyp
Permanent Re
(1), eld Zip C
(PSTLZ)
State JobApplication RCM_APPLICATION_STATE Infotype Addre

(0006), subtyp
Permanent Re
(1), eld Regio
Province, Cou
(STATE)
Country JobApplication RCM_APPLICATION_COUNTRY_CODE Infotype Addre

(0006), subtyp
Permanent Re
(1), eld Coun
(LAND1)
4/26/2019
Object
Telephone JobApplication RCM_APPLICATION_EMAIL_HOME_PHONE Infotype Addre

number (0006), subtyp
Permanent Re
(1), eld Telep
Number (TELN
E-mail JobApplication RCM_APPLICATION_EMAIL_ADDRESS Infotype

address Communicatio
(0105), subtyp
Private E-Mail
Address (003
Communicatio
Identi cation/
(USRID_LONG
Former JobApplication RCM_APPLICATION_FORMER_EMPLOYEE

employee
Error in SAP JobApplication sapError

ERP
Hiring date LastOfferDetail OFFER_DETAIL_LATEST_JOB_REQ_JOB_START_DATE Infotype Actio

(0000), eld V
From Date (BE
User ID of Candidate RCM_CANDIDATE_USER_SYS_ID

applicant
Requisition ID JobRequisition RCM_JOB_REQ_JOB_REQ_ID
Template ID JobRequisition RCM_JOB_REQ_TEMPLATE_ID
Hiring JobRequisition HiringManager_USER_SYS_ID

manager
Hiring JobRequisition USERS_SYSINFO_JobReqOperator_ForHiringMgr_USERS_SYS_FIRSTNAME

manager -
rst name
Hiring JobRequisition USERS_SYSINFO_JobReqOperator_ForHiringMgr_USERS_SYS_LASTNAME

manager - last
name
4/26/2019
Object
Country JobRequisition RCM_JOB_REQ_COUNTRY
Location JobRequisition RCM_JOB_REQ_JOB_LOCATION
Department JobRequisition RCM_JOB_REQ_JOB_DEPARTMENT
Area JobRequisition RCM_JOB_REQ_JOB_DIVISION
Personnel JobRequisition RCM_JOB_REQ_EXT_PICKLIST1

area in the
SAP ERP
system
ID of JobRequisition RCM_JOB_REQ_EXT_PICKLIST2 Infotype

personnel Organizationa
area in the Assignment (0
SAP ERP eld Personne
system (WERKS)
Personnel JobRequisition RCM_JOB_REQ_EXT_PICKLIST3

subarea in the
SAP ERP
system

personnel Organizationa
subarea in the Assignment (0
SAP ERP eld Personne
system Subarea (BTRT
Employee JobRequisition RCM_JOB_REQ_EXT_PICKLIST5

group in the
SAP ERP
system
4/26/2019
Object
ID of the JobRequisition RCM_JOB_REQ_EXT_PICKLIST6 Infotype

employee Organizationa
group in the Assignment (0
SAP ERP eld Employee
system (PERSG)
Employee JobRequisition RCM_JOB_REQ_EXT_PICKLIST7

subgroup in
the SAP ERP
system

employee Organizationa
subgroup in Assignment (0
the SAP ERP eld Employee
system Subgroup (PE
Position in the JobRequisition RCM_JOB_REQ_EXT_TEXT2

SAP ERP
system
ID of the JobRequisition RCM_JOB_REQ_EXT_TEXT1 Infotype

position in the Organizationa
SAP ERP Assignment (0
system eld Position (
Organizational JobRequisition RCM_JOB_REQ_EXT_TEXT4

unit in the
SAP ERP
system
ID of the JobRequisition RCM_JOB_REQ_EXT_TEXT3 Infotype

organizational Organizationa
unit in the Assignment (0
SAP ERP eld Organizat
system Unit (ORGEH)

Application Data to SAP ERP Fields (with
Data Transfer for Job Requisition Data)
Use
4/26/2019
In Customizing, you de ne which application data you want to import from SuccessFactors HCM Suite and map to SAP ERP
elds. For more information, see Imported Fields in Transfer of Applications from SuccessFactors HCM Suite to SAP ERP.
The following list shows which SuccessFactors elds are used by default to transfer applications to the SAP ERP system and to
which SAP ERP elds they are mapped. These elds are mapped to the eld set SAP_DEMO_02.
Caution
You need to use the eld mappings as de ned in this eld set if you also use the scenario for transferring job requisition data
for positions from SAP ERP to SuccessFactors. If you only use the scenario for transferring applications from SuccessFactors
to SAP ERP, you can also use eld mappings as de ned in the eld set SAP_DEMO_01.
Note
The difference between the eld sets is that the following elds are de ned as elds with selection lists in the eld set
SAP_DEMO_01 and as text elds in the eld set SAP_DEMO_02:
Personnel area in the SAP ERP system
ID of personnel area in the SAP ERP system
Personnel subarea in the SAP ERP system
ID of personnel subarea in the SAP ERP system
Employee group in the SAP ERP system
ID of the employee group in the SAP ERP system
Employee subgroup in the SAP ERP system
ID of employee subgroup in the SAP ERP system
This is for the following reason:
If you use only the scenario for transferring applications from SuccessFactors to SAP ERP, no eld contents are
transferred from the SAP ERP system to SuccessFactors for these elds. Therefore, the user needs to make manual
entries in these elds in SuccessFactors. The selection lists help the user with this.
If, in addition to the scenario for transferring applications from SuccessFactors to SAP ERP, you also use the scenario
for transferring job requisition data for positions from SAP ERP to SuccessFactors, eld contents are transferred
from the SAP ERP system to SuccessFactors for these elds. Therefore, the user is not to make any entries in these
elds in SuccessFactors and does not require any selection lists.
Field Content SuccessFactors SuccessFactors Field SuccessFactors Field (Ad Hoc Report)
Object
Application ID JobApplication RCM_APPLICATION_CAN_JOB_MAP_ID
4/26/2019
Object
Application JobApplication RCM_APP_STATUS_STATUS_NAME

status
Applicant ID JobApplication RCM_APPLICATION_CANDIDATE_ID
Template ID JobApplication APP_TEMPLATE_APP_TEMPLATE_ID
Export date JobApplication RCM_APPLICATION_EXPORTED_ON
First name JobApplication RCM_APPLICATION_FIRSTNAME
Last name JobApplication RCM_APPLICATION_LASTNAME
Middle name JobApplication RCM_APPLICATION_MIDDLE_NAME
Gender JobApplication RCM_APPLICATION_GENDER
Date of birth JobApplication RCM_APPLICATION_DOB
4/26/2019
Object
Address JobApplication RCM_APPLICATION_ADDRESS
City JobApplication RCM_APPLICATION_CITY
Zip code JobApplication RCM_APPLICATION_ZIP
State JobApplication RCM_APPLICATION_STATE
Country JobApplication RCM_APPLICATION_COUNTRY_CODE
Telephone JobApplication RCM_APPLICATION_EMAIL_HOME_PHONE

number
E-mail JobApplication RCM_APPLICATION_EMAIL_ADDRESS

address
Former JobApplication RCM_APPLICATION_FORMER_EMPLOYEE

employee
4/26/2019
Object
Error in SAP JobApplication sapError

ERP
Hiring date LastOfferDetail OFFER_DETAIL_LATEST_JOB_REQ_JOB_START_DATE
User ID of Candidate RCM_CANDIDATE_USER_SYS_ID

applicant
Requisition ID JobRequisition RCM_JOB_REQ_JOB_REQ_ID
Template ID JobRequisition RCM_JOB_REQ_TEMPLATE_ID
Hiring JobRequisition HiringManager_USER_SYS_ID

manager
Hiring JobRequisition USERS_SYSINFO_JobReqOperator_ForHiringMgr_USERS_SYS_

manager -
rst name
Hiring JobRequisition USERS_SYSINFO_JobReqOperator_ForHiringMgr_USERS_SYS_

manager - last
name
Country JobRequisition RCM_JOB_REQ_COUNTRY
Location JobRequisition RCM_JOB_REQ_JOB_LOCATION
Department JobRequisition RCM_JOB_REQ_JOB_DEPARTMENT
Area JobRequisition RCM_JOB_REQ_JOB_DIVISION
Personnel JobRequisition sapPersonnelAreaTxt RCM_JOB_REQ_EXT_TEXT5

area in the
SAP ERP
system
4/26/2019
Object
ID of JobRequisition sapPersonnelAreaIDTxt RCM_JOB_REQ_EXT_TEXT6

personnel
area in the
SAP ERP
system
Personnel JobRequisition sapPersonnelSubAreaTxt RCM_JOB_REQ_EXT_TEXT7

subarea in the
SAP ERP
system
ID of JobRequisition sapPersonnelSubAreaIDTxt RCM_JOB_REQ_EXT_TEXT8

personnel
subarea in the
SAP ERP
system
Employee JobRequisition sapEEGroupTxt RCM_JOB_REQ_EXT_TEXT9

group in the
SAP ERP
system
ID of the JobRequisition sapEEGroupIDTxt RCM_JOB_REQ_EXT_TEXT10

employee
group in the
SAP ERP
system
Employee JobRequisition sapEESubGroupIDTxt RCM_JOB_REQ_EXT_TEXT11

subgroup in
the SAP ERP
system
ID of JobRequisition sapEESubGroupTxt RCM_JOB_REQ_EXT_TEXT12

employee
subgroup in
the SAP ERP
system
4/26/2019
Object
Position in the JobRequisition RCM_JOB_REQ_EXT_TEXT2

SAP ERP
system
ID of the JobRequisition RCM_JOB_REQ_EXT_TEXT1

position in the
SAP ERP
system
Organizational JobRequisition RCM_JOB_REQ_EXT_TEXT4

unit in the
SAP ERP
system
ID of the JobRequisition RCM_JOB_REQ_EXT_TEXT3

organizational
unit in the
SAP ERP
system
Further Processing of Imported Applications

in SAP ERP
Use
The HR administrator can use the application for the further processing of imported applications (transaction
HRSFI_RCT_HIRE) to check and, where required, complete the data imported from SuccessFactors HCM Suite. He or she can
then use a personnel action to transfer the data to the SAP ERP system.
The application is located in the menu of the following roles:
SuccessFactors Integration: Composite Role (SAP_HR_SFI_C2)
SuccessFactors Integration: Recruiting (SAP_HR_SFI_RECRUITING)
You can use these roles to enable users to access the application in SAP NetWeaver Business Client or in SAP NetWeaver
Portal. For more information, see SAP Note 1770819 .
Prerequisites
In Customizing for the Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite, you have made the
settings under Integration Scenario for Recruiting Data Transfer of Applications from SuccessFactors BizX to SAP
ERP Further Processing of Imported Applications .
If you want to use the function for transferring a user ID to SuccessFactors after hiring the employee in SAP ERP, you
need to activate this function in Customizing. To do so, under Integration Scenario for Recruiting Data Activate
Additional Functions , set the parameter CANDIDATE_UPDATE_ACTIVE to X. For more information, see Transfer of
Applications from SuccessFactors HCM Suite to SAP ERP in the section Updating Candidate Data in SuccessFactors
After Hiring in SAP ERP.
4/26/2019
If you want to use the transfer of job requisition data for positions from SAP ERP to SuccessFactors, you need to activate
this in Customizing. To do so, under Integration Scenario for Recruiting Data Activate Additional Functions , set the
parameter JOB_REQUISITION_INTEGR_ACTIVE to X. For more information, see Transferring Job Requisition Data for
Positions from SAP ERP to SuccessFactors HCM Suite.
Features
Note
The menu also contains all functions that, as described below, can be performed using a pushbutton or by clicking on the
relevant icon in the list of applications.
Overview of the Transferred Applications
The application displays a list of the applications transferred from SuccessFactors that have not yet been transferred to the
SAP ERP system and therefore do not yet have the status Completed. This overview serves as a task list for the HR
administrator, in which he or she can see for which applications data needs to be added, for which applications he or she can
already perform a personnel action, and so on.
Note
Which applications the HR administrator sees in the list depends on whether he or she has the authorizations required for
the imported data. You use the Business Add-In (BAdI) Authorization Check for SFSF Integration to de ne the
authorizations. For the BAdI, see Customizing for the integration add-on, and choose Basic Settings.
Modify List
The list of applications is based on SAP List Viewer (ALV) for SAP GUI. Therefore, the HR administrator can use the following
standard SAP List Viewer functions:
Sorting the list
Filter list
Print list
Export list
For more information, see the documentation for SAP List Viewer, under Functions in the List.
The HR administrator can save and reload all settings that he or she makes for the list in views. For more information, see the
documentation for SAP List Viewer, under Personalizing the List.
For the documentation for SAP List Viewer, see SAP Library and choose Getting Started - Using SAP Software Working with
Tools and Functions Working with Lists .
Display Details of the Application
On the Details tab, the HR administrator can display the following information for the application:
Information on the application itself, for example, country grouping and personnel action to be performed
Information on the applicant, for example, name and date of birth
Information on the processing of the application, for example, the last processor and the date of the last change
4/26/2019
Information on the transfer of data from SuccessFactors, for example, date of data transfer and ad hoc report used for
the data extraction
If you have activated the function for transferring a user ID to SuccessFactors after hiring the employee in SAP ERP, the
candidate ID to which the SAP ERP system transfers the user ID derived from the personnel number is also displayed
here.
Display Field Contents Transferred from SuccessFactors and Mapped in SAP ERP
The HR administrator can use the Data Overview (PDF) pushbutton to display the following information for the application:
Basic application information
All SuccessFactors elds for which data has been transferred, as well as the transferred eld contents
All SAP ERP infotype elds to which data is transferred, as well as the eld content to be transferred
The PDF overview is displayed in a separate window that the HR administrator can leave open at the same time as he or she
performs the personnel action. This shows the HR administrator which infotype elds are lled automatically by the personnel
action and in which infotype elds he or she may need to make manual entries.
Display Messages for an Application
The HR administrator can click on the icon in the Messages column to display the error and warning messages for a selected
application. For example, there is an error message if no suitable personnel action could be determined for the application, or if
the HR administrator needs to check for duplicates (see below). For example, there is a warning message if the eld content is
missing for elds that are not mandatory.
Edit Messages on SuccessFactors Job Requisitions
If you have activated the transfer of job requisition data for positions from SAP ERP to SuccessFactors, the SAP ERP system
checks whether the combination of position and job requisition ID as it has been imported from SuccessFactors for a candidate
corresponds to the combination de ned in the SAP ERP system. The following cases can occur:
The job requisition ID is not de ned in the SAP ERP system for this position.
The job requisition ID is de ned for this position in the SAP ERP system, but the relevant record of the infotype SFSF Job
Requisition (1107) has already been closed.
Note
For example, this can happen in the following situations:
The relevant job requisition was created manually in SuccessFactors before you activated the transfer of job
requisition data for positions from SAP ERP to SuccessFactors.
The vacancy for a position was closed accidentally and then reopened. As a result, a new job requisition ID was
transferred to SuccessFactors. However, in SuccessFactors, candidates have already applied based on the old job
requisition. Their data has been transferred to the SAP ERP system.
The check is performed at the following times:
When the applications are transferred from SuccessFactors to the SAP ERP system.
When the HR administrator has successfully performed the personnel action.
4/26/2019
In both cases the system displays a warning for the HR administrator if the combination of position and job requisition ID
transferred from SuccessFactors does not correspond to the combination de ned in the SAP ERP system. To process the
messages, the HR administrator proceeds depending on the situation as follows:
After transferring the applications from SuccessFactors:
The HR administrator is to check whether he or she wants to transfer the application as it is.
After performing the personnel action:
The HR administrator is to check whether he or she accidentally assigned the candidate to a position other than
the one whose data was originally transferred to SuccessFactors. He or she is to correct the assignment where
necessary.
The HR administrator is to check whether the incorrect job requisition has been closed (see below, under Perform
Personnel Action). If necessary, he or she needs to make sure that the correct job requisition is closed.
Display General Messages
The HR administrator can use the General Messages pushbutton to display the messages that apply to all applications. For
example, such a message occurs if the connection via middleware was not available and it was therefore not possible to
transfer any data. The HR administrator can also delete messages from the list when they are no longer required.
Store a Note for an Application
The HR administrator can click on the icon in the Note column to make notes for an application, for example, on which additional
information he or she requires. If more than one HR administrator is working on the same applications, this enables them to
inform each other of who is processing which application. If an HR administrator has created a note, the icon changes from
Create Note to Change Note.
Check for Duplicates
For each application transferred from SuccessFactors, the SAP ERP system uses the rst name, last name, and date of birth to
check whether one or more personnel numbers that match the data transferred already exist. If so, the system displays an
error message for this application. The application has the status To Be Checked.
The HR administrator then needs to check whether the persons are the same. To do so, he or she clicks the icon in the Check
column to access the Check and Change Data dialog box. This contains the data for the transferred application and the data for
the existing personnel numbers. The HR administrator selects one of the entries and thereby determines whether the
employee is new. He or she also determines which country grouping is to be used to map the SuccessFactors data to the SAP
ERP infotype elds and which personnel action is to be performed.
Check and Change Country Grouping
The SAP ERP system uses the application data transferred from SuccessFactors to derive the country grouping that it uses to
map the SuccessFactors data to the SAP ERP infotype elds.
Note
You use the BAdI Determination of Further Data for Recruiting Scenario from SFSF to de ne how the country grouping is
determined. For the BAdI, see Customizing for the integration add-on, under Integration Scenario for Recruiting
Data Transfer of Data from SuccessFactors BizX to SAP ERP .
If the SAP ERP system could not de ne a country grouping from the data transferred from SuccessFactors, it displays an error
message for this application. The application has the status To Be Checked.
4/26/2019
The HR administrator then needs to de ne the country grouping that is to be used to map the SuccessFactors data to the SAP
ERP infotype elds. To do so, he or she clicks the icon in the Check column to access the Check and Change Data dialog box.
There, he or she selects a country grouping.
Check and Change Personnel Action
The SAP ERP system uses the application data transferred from SuccessFactors to derive possible personnel actions.
Note
You use the BAdI Determination of Further Data for Recruiting Scenario from SFSF to de ne how the personnel actions are
determined.
If the SAP ERP system could not de ne a unique personnel action from the data transferred from SuccessFactors, it displays an
error message for this application. The application has the status To Be Checked.
The HR administrator then needs to de ne the personnel action that is to be performed for this application. To do so, he or she
clicks the icon in the Check column to access the Check and Change Data dialog box. There, he or she selects a personnel
action.
Perform Personnel Action
If all data required for an application is available, it has the status Start Action. The HR administrator can then use the Start
Action pushbutton to transfer the application data to Personnel Administration, using the transaction Personnel Actions
(PA40). In doing so, the eld contents transferred from SuccessFactors are transferred to the SAP ERP infotype elds that have
been mapped to the SuccessFactors elds in Customizing. The country grouping that the SAP ERP system determined or that
the HR administrator entered is taken into consideration.
If the personnel action has been performed, the application initially receives the status Con rmation Pending in the transaction
HRSFI_RCT_HIRE. The SAP ERP system sends a relevant status update to SuccessFactors.
If you have activated the function for transferring a user ID to SuccessFactors after hiring the employee in SAP ERP, the SAP
ERP system transfers the status update together with the user ID derived from the personnel number to SuccessFactors.
If the status of the application has been updated in SuccessFactors and the user ID has been transferred to SuccessFactors, the
application receives the status Completed in the transaction HRSFI_RCT_HIRE.
Note
The overall status of the application in the transaction HRSFI_RCT_HIRE is composed of the status that the application
receives in SuccessFactors and the status for transferring the user ID to SuccessFactors. Only when both statuses are set to
Completed is the overall status also Completed.
If the status update is not visible immediately in the transaction HRSFI_RCT_HIRE, choose the Update List pushbutton.
If the personnel action could not be performed successfully, a dialog box with a corresponding message is displayed.
Other Steps for SuccessFactors Job Requisitions
If you have activated the transfer of job requisition data for positions from SAP ERP to SuccessFactors, the SAP ERP system
performs the following additional steps after the personnel action has been completed:
It closes the record of the infotype SFSF Job Requisition (1107).
4/26/2019
If you use vacancies for positions in your SAP ERP system and the HR administrator closes the vacancy after
completing the personnel action, the SAP ERP system also closes the corresponding record of the infotype SFSF
Job Requisition (1107).
If you do not use vacancies for positions in your SAP ERP system, the SAP ERP system closes the corresponding
record of the infotype SFSF Job Requisition automatically after the personnel action has been completed.
In both cases, the next time that data is transferred, the SAP ERP system transfers the status Closed to SuccessFactors
to close the job requisition there.
Irrespective of whether you use vacancies for positions in your SAP ERP system, once the personnel action has been
completed, the SAP ERP system automatically transfers the personnel number of the newly hired candidate and the
SuccessFactors user ID derived from this to the infotype SFSF Job Requisition (1107).
Display Applications Not Transferred
The HR administrator can use the Appl. Not Transf. pushbutton to display the applications that SuccessFactors could not
transfer, for example, since the application status was not correct or the eld contents of required elds were missing. The HR
administrator can also delete entries from this list when they are no longer required.
Close Application Manually
The HR administrator can set applications for which the system could not set the status Completed to Completed manually so
that they are no longer displayed in the list of open applications. The applications then have the status Man. Completed.
If you have activated the function for transferring a user ID to SuccessFactors after hiring the employee in SAP ERP, the HR
administrator is requested to enter the personnel number of the employee for whom he or she performed the personnel action
manually. Only then can the HR administrator complete the application manually.
 Example
It can be necessary to complete applications manually in complex cases, such as the following:
For an application, only a very small amount of SuccessFactors data could be mapped to SAP ERP infotype elds.
Therefore, the application does not receive the status Start Action. However, the HR administrator performs a
personnel action by calling the transaction PA40 manually and entering the required data in the relevant infotypes.
In the SAP ERP system, a personnel number with the start date July 1 has already been created. Subsequently, an
application for the same person but with the hiring date June 1 is transferred from SuccessFactors. The SAP ERP
system recognizes that a suitable personnel number already exists. However, it cannot determine the data since it
only exists in the SAP ERP system as of July 1 and not as of June 1. Therefore, the HR administrator needs to change
the start date of the existing personnel number and, if required, enter data that needs to be added to the relevant
infotypes.
Display Completed Applications
The HR administrator can use the Show Completed pushbutton to display the applications that have been transferred on or
after a particular date and have already been completed automatically or manually. He or she can choose the Show Open Appl.
pushbutton to return to the list of applications not yet completed.
Remap Data Transferred from SuccessFactors to SAP ERP Infotype Fields
The HR administrator can retrigger the transfer of data from SuccessFactors for a selected application or for all applications.
For example, this is useful if new mappings of SAP ERP infotype elds to SuccessFactors elds have been added in Customizing
such that additional eld contents can be transferred.
4/26/2019
To do so, the HR administrator chooses Tools Remap Data for Job Application or Tools Remap Data for All Job Applications .
Note
If the HR administrator changes the country grouping, the data transferred from SuccessFactors is automatically remapped
to SAP ERP infotype elds since some mappings (for example, the address) can be country-speci c.
Resend Failed Con rmations to SuccessFactors
If the SAP ERP system could not send a status update to SuccessFactors after completing the personnel action, it displays a
corresponding message under General Messages. For example, this can be the case if the connection via middleware was not
available brie y. In this case, the HR administrator can resend the status updates. If you have activated the function for
transferring a user ID to SuccessFactors after hiring the employee in SAP ERP, the HR administrator can also send the user IDs
to SuccessFactors again.
To do so, he or she chooses Tools Resend Failed Con rmations to SFSF .
Note
If the HR administrator chooses this function, the SAP ERP system sends only the pending information to SuccessFactors. If
the status update for an application has been transferred successfully but an error occurred when sending the user ID, the
system resends only the user ID to SuccessFactors. In the reverse case, the SAP ERP system resends only the status update
to SuccessFactors.
Delete Application from the List
The HR administrator can delete obsolete applications from the list, for example, if an applicant declines at short notice. To do
so, he or she chooses Job Application Delete .
Deleting only removes the application from the list and deletes the related messages. It does not change the status in
SuccessFactors.
Caution
To be able to delete applications, the HR administrator requires super user authorization. In addition to the delete function, a
super user sees all applications in the list, regardless of whether he or she has the authorizations required for the imported
data.
You use the BAdI Authorization Check for SFSF Integration with the method CHECK_SUPER_USER to de ne the super user
authorization. For the BAdI, see Customizing for the integration add-on, and choose Basic Settings.
Integration Scenario for Onboarding Data

Use
If applicants are onboarded in SuccessFactors Onboarding, you can extract the applicant data and transfer it to SAP ERP HCM,
where you can transfer the applicants to personnel administration as employees.
If employees are hired in SAP ERP HCM, you can extract the employee data and transfer it to SuccessFactors Onboarding for
onboarding activities.
Integration
4/26/2019
see Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration .
Features
You can use middleware to transfer onboarding data from SuccessFactors Onboarding to SAP ERP HCM and vice versa. For
more information, see:
Transfer of Employee Data from SuccessFactors Onboarding
Transfer of Employee Data to SuccessFactors Onboarding
See Integration Scenario Process for Onboarding Data.
Integration Scenario Process for Onboarding

Data
Use
The integration scenario process for onboarding data provides functions and features to transfer employee data from
SuccessFactors Onboarding to SAP ERP HCM and vice versa.
Data Flow
The following gure shows the data ow.
4/26/2019
Figure 2: Data Flow
Business Work ow
The following gure shows the business work ow. You enable the transfer of employee information from SuccessFactors
Onboarding to SAP ERP HCM and vice versa using a recurring job that runs in the background. The HR administrator monitors
and triggers the update of employee data based on the imported onboarding data. The integration supports the new hire,
transfer, and rehire scenarios.
Figure 3: Business Workflow
Processing Blocks for Export of Data from SAP ERP HCM to SuccessFactors Onboarding
The following gure shows the processing blocks involved. At the end of a hire, transfer, or rehire action, the integration add-on
triggers the transmission of the employee data to the SuccessFactors Onboarding system. The ID of the newly created data in
SuccessFactors Onboarding is returned and saved in the integration add-on for future reference.
To keep the data consistent between SAP ERP HCM and SuccessFactors Onboarding, a utility report scans the SAP ERP HCM
system for any updates to the employee data and transmits the updates to SuccessFactors Onboarding.
4/26/2019
Figure 4: Processing Blocks for Export of Data from SAP ERP HCM to SuccessFactors Onboarding
Processing Blocks for Import of Data from SuccessFactors Onboarding to SAP ERP HCM
The following gure shows the processing blocks involved. SuccessFactors Onboarding captures the data of the prospective
employee. When the data collection is complete in SuccessFactors Onboarding, the employee is marked as Ready to Hire. The
data is then imported to SAP ERP HCM. See also Transfer of Employee Data from SuccessFactors Onboarding.
4/26/2019
Figure 5: Processing Blocks for Import of Data from SuccessFactors Onboarding to SAP ERP HCM
Process
1. You schedule the transaction Trigger Onboarding for Employee (transaction HRSFI_ONB_TRIGGER) in the SAP ERP
system to run regularly in the background.
2. Each time the report is run, it triggers a check for employees in SAP ERP HCM for whom onboarding needs to be
triggered.
3. Based on the mapping con guration, the report gets the details for each employee eligible for onboarding.
For more information, see Mapping of SuccessFactors Onboarding Fields to SAP ERP HCM.
4. The report sends the data to SuccessFactors Onboarding using the SOAP API PostNewhireRecord with the
appropriate parameters.
5. SuccessFactors Onboarding returns the HR data ID.
6. The data exported to SuccessFactors Onboarding and the HR data ID returned from SuccessFactors Onboarding are
saved to the staging tables in the SAP ERP HCM add-on.
7. Using the transaction Process Applications Imported from or Exported to Onboarding (transaction HRSFI_ONB_HIRE),
the HR administrator monitors the employees sent for onboarding.
In this transaction, the status of all onboarded employees is visible centrally. The administrator can delete the record if
onboarding needs to be cancelled. For more information see Further Processing of Exported Data in SAP ERP HCM.
8. You schedule the transaction Import Employee Data from SuccessFactors Onboarding (transaction
HRSFI_ONB_DATA_IMP) in the SAP ERP system to run regularly in the background.
9. Each time the report is run, it triggers a query in SuccessFactors Onboarding to query the object
OnboardingCandidateInfo to get a list of all employees (the list is ltered not to include employees that are already
hired).
10. After the list of ltered employees is available, the report gets details for each employee by querying the SOAP API
GetNewhireRecord with the appropriate parameters.
11. The data obtained from SuccessFactors Onboarding is prepared to the ERP format using the mapping con guration.
For more information, see Mapping of SuccessFactors Onboarding Fields for Employee Data.
12. The prepared data is saved to the staging tables in the SAP ERP HCM add-on.
13. Using the transaction Process Applications Imported from or Exported to Onboarding (transaction HRSFI_ONB_HIRE),
the HR administrator processes the prepared data and creates employee master data.
In this transaction, the status of all onboarded employees is visible centrally. Whenever the candidates are ready for hire,
the HR administrator can initiate hiring from this transaction. For more information see Further Processing of Imported
Data in SAP ERP HCM.
The process is as follows:
a. When the HR administrator chooses Start Action, the system triggers the transaction Personnel Actions
(transactionPA40) with the appropriate action infotype.
b. The system offers the HR administrator a list of possible existing employees that match the incoming data.
Rehire is triggered if the administrator chooses an employee who is not currently active in the system. Internal
transfer is triggered if the administrator chooses an employee who is currently active in the system. The
administrator can reject the list and attach an employee number or hire a new employee.
4/26/2019
The administrator can delete line items imported from SuccessFactors Onboarding, for example, a new employee
who decided not to join.
c. Once the hiring is complete, the system sets the Hired ag in OnboardingCandidateInfo.
Transfer of Employee Data from

SuccessFactors Onboarding
Use
You can import applicant data from SuccessFactors Onboarding to SAP ERP HCM. Based on the transferred data, you can
perform a personnel action in SAP ERP HCM to hire the candidates as employees and/or update existing employees.
Prerequisites
In SuccessFactors Onboarding, create a data dictionary containing all elds to be imported to SAP ERP HCM. Download the
data dictionary in an XML le and upload it using report Import DDIC from SuccessFactors Onboarding (transaction
HRSFI_SYNCH_ONB_META).
Recommendation
If you are not familiar with importing the data dictionary from SuccessFactors Onboarding to SAP ERP HCM, we recommend
asking SAP Support to import it for you to ensure that the correct settings are made and the correct XML is provided.
In Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for
On-/Offboarding Data , carry out the activities under Basic Settings.
On-/Offboarding Data , carry out the following activities under Transfer of Employee Data from SuccessFactors Onboarding to
SAP ERP HCM:
De ne Additional Display Fields
De ne Names of SuccessFactors HCM Suite Fields
Features
Importing the Onboarding Data
For importing applicant data to SAP ERP HCM, you can use report Import Onboarding Data from SuccessFactors HCM Suite
(report RH_SFI_IMPORT_ONBOARDING_DATA). For more information about this report, see Customizing for Integration Add-
On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Transfer of Employee
Data from SuccessFactors Onboarding to SAP ERP HCM Import Employee Data from SuccessFactors Onboarding . You can
also nd this report in the user menu of role SuccessFactors Integration: Onboarding Data (role
SAP_HR_SFI_ONBOARDING_2).
De ning the Field Content
By de ning eld sets, you de ne which eld contents you want to import from SuccessFactors Onboarding. A eld set contains
multiple SuccessFactors Onboarding elds that you map to the SAP ERP elds of your choice. You have the following options:
You map the elds directly to each other using a table.

4/26/2019
You do this in Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration
Scenario for On-/Offboarding Data Basic Settings Map SuccessFactors HCM Suite Fields and SAP ERP HCM Fields .
To make more complex mappings, you can create a Business Add-In (BAdI) implementation.
You can use the following BAdIs for this in Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors
HCM Suite Integration Scenario for On-/Offboarding Data Basic Settings :
BAdI: Mapping of SuccessFactors Fields to SAP ERP Infotype Fields (BAdI de nition
HRSFI_B_FIELD_MAPPING)
You can use this BAdI to map a SuccessFactors Onboarding eld to an SAP ERP HCM eld.
BAdI: Change of Mapping Result (BAdI de nition HRSFI_B_CHANGE_MAPPING_RESULT)
You can use this BAdI to map one or more SuccessFactors Onboarding elds to one or more SAP ERP HCM elds.
As standard, template mappings of SuccessFactors Onboarding elds to SAP ERP HCM elds are de ned.
Automatic Hire
As of integration add-on 3.0 SP06, report Import Onboarding Data from SuccessFactors HCM Suite (report
RH_SFI_IMPORT_ONBOARDING_DATA) includes a selection parameter to automatically hire applicants. If you select the Hire
Applicants checkbox, you can restrict automatic hiring to speci c country groupings, company codes, personnel areas,
personnel subareas, employee groups and employee subgroups. If you do not specify any restrictions, all applicants are
considered eligible for automatic hire.
Only initial hire is supported. If onboarding has been triggered for an employee from SAP ERP HCM, the data for such
employees is not updated in SAP ERP HCM automatically.
For a complete list of constraints, please see the Administration Guide for the Integration Scenario for Onboarding Data at
http://service.sap.com/~sapidb/012002523100004720122016E .
Mass Hire
You can select multiple applicants in transaction Process Applications Imported from or Exported to Onboarding (transaction
HRSFI_ONB_HIRE) to hire applicants simultaneously. This saves you having to hire each applicant individually.
For constraints, please see the Administration Guide for the Integration Scenario for Onboarding Data at
http://service.sap.com/~sapidb/012002523100004720122016E .
Further Processing the Imported Data
You can check the data imported from SuccessFactors Onboarding and complete it as required. You can then use a personnel
action to transfer the data to SAP ERP HCM. For more information, see Further Processing of Imported Data in SAP ERP HCM.
Mapping of SuccessFactors Onboarding

Fields for Employee Data
The following list shows which SuccessFactors Onboarding elds are used as a template to transfer applications to SAP ERP
HCM and to which SAP ERP HCM elds they are mapped. These elds are mapped to eld set SAP_DEMO_ONB. You can create
your own eld set and map elds as per your requirements.
4/26/2019
Field SuccessFactors SAP ERP HCM Field Special Features of Mapping

Content Onboarding Field
Social SSN Infotype Personal Data (0002), eld Field is country-speci c

Security SSN (PERID)
Number
Last Name LastName Infotype Personal Data (0002), eld

Last Name (NACHN)
First Name FirstName Infotype Personal Data (0002), eld

First Name (VORNA)
Middle MiddleName Infotype Personal Data (0002), eld

Name Middle Name (MIDNM)
Email Email Infotype Communication (0105),

Address Subtype E-Mail (0010), eld
Communication: Long
Identi er/Number (USERID_LONG)
Street Address 1 Infotype Address (0006), Subtype

Address of Home Address (3), eld Street and
Primary House Number (STRAS)
Residence
Apt/Unit No. Address 2 Infotype Address (0006), Subtype

of Primary Home Address (3), eld House
Residence Number (HSNMR)
City of City Infotype Address (0006), Subtype

Primary Home Address (3), eld City (ORT01)
Residence
County of CountyTownship Infotype Address (0006), Subtype

primary Home Address (3), eld
residence Region/Country (ORT02)
State of State Infotype Address (0006), Subtype

Primary Home Address (3), eld State (STATE)
Residence
Zip Code of Zip Infotype Address (0006), Subtype

Primary Home Address (3), eld ZipCode
Residence (PSTLZ)
Country of Country Infotype Address (0006), Subtype

Primary Home Address (3), eld Country
Residence (LAND1)
Postal Code PostCode Infotype Address (0006), Subtype

of Primary Home Address (3), eld ZipCode
Residence (PSTLZ)
Full PhoneNum Infotype Address (0006), Subtype

Telephone Home Address (3), eld
Number Communication Type: WORK (NUM01)
Division DivCode Infotype Organizational Assignment

Code (0001), eld Personnel Area (WERKS)
Department DeptCode Infotype Organizational Assignment

Code (0001), eld Org. Code (ORGEH)
4/26/2019

Job Code JobCode Infotype Organizational Assignment

(0001), eld Job Code (STELL)
Pay Rate JobPayRate Infotype Basic Pay (0008), eld Pay

Rate Per Payroll Frequency (DIVGV)
Start Date WOTCStartDate Infotype Actions (0000), eld Start If the start date or date of birth transferred from
Date (BEGDA) SuccessFactors Onboarding contains slashes (/), it
is converted to the date format used in SAP ERP
Date of Birth DateOfBirth Infotype Personal Data (0002), eld HCM
Date of Birth (GBDAT)
Hispanic or HispOrLat Infotype Additional Personal Data Field is country-speci c

Latino (0077), eld Ethnic Origin (ETHEN)
Race Code EthnicGroupCode2 Infotype Additional Personal Data

(0077), eld Ethnicity (RACKY)
Gender Gender Infotype Personal Data (0002), eld

Code Gender (GESCH)
Vietnam Era VeteranVietnam Infotype Additional Personal Data Field is country-speci c

Veteran (0077), eld Vietnam Veteran (VETS3)
Recently VeteranRecentlySeparated Infotype Additional Personal Data

Separated (0077), eld Recently Separated
Veteran Veteran (VETS5)
Disabled VeteranDisabled Infotype Additional Personal Data

Veteran (0077), eld Disabled Veteran (VETS7)
Other VeteranAnother Infotype Additional Personal Data

Protected (0077), eld Other Veteran (VETS4)
Veteran
Military SeparationDate Infotype Additional Personal Data

Separation (0077), eld Discharge Date (DCRDT)
Date
Disabled DisabledPerson Infotype Additional Personal Data

Person (0077), eld Disabled (DISAB)
Bank Key Bankkey Infotype Bank Details (0009), eld

Bank key (BANKL)
Bank BankAccount Infotype Bank Details (0009), eld

Account Bank Account Number (BANKN)
Number
Employee EEGroup Infotype Organizational Assignment

Group (0001), eld Employee Group (PERSG)
Employee EESGroup Infotype Organizational Assignment

Subgroup (0001), eld Employee Sub Group
(PERSK)
Further Processing of Imported Data in SAP

ERP HCM
4/26/2019
Use
Using the transaction Process Applications Imported from or Exported to Onboarding (transaction HRSFI_ONB_HIRE), the HR
administrator can check and, where required, complete the data imported from SuccessFactors Onboarding. The HR
administrator can then use a personnel action to transfer the data to SAP ERP HCM. The transaction is located in role
SuccessFactors Integration: Onboarding Data (role SAP_HR_SFI_ONBOARDING_2).
Prerequisites
Carry out the activities in Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration
Scenario for On-/Offboarding Data Transfer of Employee Data from SuccessFactors Onboarding to SAP ERP HCM .
Features
Application Overview
In transaction Process Applications Imported from or Exported to Onboarding (transaction HRSFI_ONB_HIRE), a list is
displayed of the applications transferred from SuccessFactors Onboarding that have not yet been transferred to SAP ERP HCM
and therefore do not yet have the status Completed. This overview serves as a task list for the HR administrator who can see
which applications require additional data, or for which applications a personnel action can be started, and so on.
Note
The applications that the HR administrator sees in the list depend on whether the HR administrator has the necessary
authorizations for the imported data. You de ne the authorizations in Customizing for Integration Add-On for SAP ERP HCM
and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Basic Settings BAdI: Authorization Check
for SuccessFactors Integration .
Application Details
On the Details tab, you can display information about the application, applicant, and processing of the application. For a list of all
elds transferred from SuccessFactors Onboarding, click Show Details.
Application Messages
You can display any error and warning messages for an application by clicking the icon in the messages column. For example, an
error message is displayed if no suitable personnel action could be determined for the application, or if you need to check for
duplicates (see below); a warning message is displayed if the eld content is missing for elds that are not mandatory.
General Messages
You can display messages that apply to all applications by clicking General Messages. For example, a general message is issued
if the middleware connection was not available and no data could be transferred.
Check for Duplicates
For each application transferred from SuccessFactors Onboarding, SAP ERP HCM uses the rst name, last name, and date of
birth to check whether one or more personnel numbers that match the data transferred already exist. If they do, the system
displays an error message for this application, and the application has the status To Be Checked. You must then check whether
the persons are the same. You do this by clicking the red light in the check column to open the Check and Change Data dialog
box. In this dialog box, you determine whether the employee is new, and you determine the country grouping to be used to map
the SuccessFactors data to the SAP ERP HCM infotype elds, and the personnel action to be performed.
Determination of First Name, Last Name, Hire Date, and Date of Birth
4/26/2019
SAP ERP HCM uses the application data transferred from SuccessFactors Onboarding to derive the rst name, last name, hire
date, and date of birth. It uses this information to check for duplicates for the applicant.
Note
You de ne how the rst name, last name, hire date, and date of birth are determined in Customizing for Integration Add-On
for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Basic Settings BAdI:
Determination of Further Data for Onboarding from SuccessFactors .
Check for Country Grouping
SAP ERP HCM uses the application data transferred from SuccessFactors Onboarding to derive the country grouping that it
uses to map the SuccessFactors Onboarding data to the SAP ERP HCM infotype elds.
Note
You de ne how the country grouping is determined in Customizing for Integration Add-On for SAP ERP HCM and
SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Basic Settings BAdI: Determination of Further
Data for Onboarding from SuccessFactors .
If SAP ERP HCM could not determine a country grouping from the data transferred from SuccessFactors Onboarding, it displays
an error message for this application, and the application has the statusTo Be Checked. You must then de ne the country
grouping to be used to map the SuccessFactors Onboarding data to the SAP ERP HCM infotype elds. You do this by clicking the
red light in the check column to open the Check and Change Data dialog box. In this dialog box, you select a country grouping.
Check for Personnel Action
SAP ERP HCM uses the application data transferred from SuccessFactors Onboarding to derive possible personnel actions.
Note
You de ne how the personnel actions are determined in Customizing for Integration Add-On for SAP ERP HCM and
If SAP ERP HCM could not determine a unique personnel action from the data transferred from SuccessFactors Onboarding, it
displays an error message for this application, and gives the application the statusTo Be Checked. You must then de ne the
personnel action to be performed for this application. You do this by clicking the red light in the check column to open the Check
and Change Data dialog box. In this dialog box, you select a personnel action.
Start Personnel Action
If all data required for an application is available, it has the status Start Action. For this application, you can then click the Start
Action pushbutton to transfer the application data to personnel administration using the transaction Personnel Actions
(transaction PA40). The eld contents transferred from SuccessFactors Onboarding are then transferred to the SAP ERP HCM
infotype elds mapped to the SuccessFactors Onboarding elds in Customizing. The country grouping determined by SAP ERP
HCM or entered by the HR administrator is taken into consideration. After the personnel action is performed, the application is
given the status Completed.
Mass Hire
As of integration add-on 3.0 SP06, you can select multiple applicants and trigger a hire action. This saves you having to hire
each applicant individually. The hire action is triggered in the background. Only an initial hire action is supported; mass hire is
not supported for applicants who already have a personnel number.
4/26/2019
To enable mass hire, you need to:
Activate the parameter ONBOARDING_MASS_HIRE_ACTIVE (set the parameter value to X) in Customizing for
Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding
Data Transfer of Employee Data from SuccessFactors Onboarding to SAP ERP HCM Activate Additional Functions .
Change the layout in transaction HRSFI_ONB_HIRE to enable the column Select Applicant. We recommend keeping this
column as the rst column in your layout.
Set to Completed Manually
For applications whose status could not be set by the system to Completed, you can set the status to completed manually so
that they no longer appear in the list of open applications. You do this by selecting the application and choosing Complete.
Display Completed Applications
You can display the applications that were transferred on or after a certain date and have already been completed
automatically or manually. You do this by choosing Show Processed. To return to the list of open applications, choose Show
Open Applications.
Delete Application
You can delete obsolete applications from the list, for example, if an applicant declines at short notice. You do this by selecting
the application and choosing Delete. This removes the application from the list and deletes the related messages, but it does
not change the status in SuccessFactors.
Transfer of Employee Data to

SuccessFactors Onboarding
Use
You can export new hire employee data from SAP ERP HCM to SuccessFactors Onboarding. Based on the personnel action in
SAP ERP HCM, onboarding for an employee can be triggered from SAP ERP HCM.
Prerequisites
In SuccessFactors Onboarding, create a data dictionary containing all elds to be imported from SAP ERP HCM. Download the
In SuccessFactors Onboarding, either set the account option XpressHR.InputToXmlData to blank if there is no other
integration with SuccessFactors Onboarding or Offboarding, or set the appropriate XSLT path in the Value column, as shown in
the following example.
4/26/2019
Figure 6: Example XSLT Path
A sample XSLT le is available at http://help.sap.com/saphelpiis_cloud4hr/EN/HRXML.ImportNewHire.xslt .
Recommendation
If you are not familiar with importing the data dictionary, we recommend asking SAP Support to import it for you to ensure
that the correct settings are made and the correct XML is provided.
Carry out the activities under Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM
Suite Integration Scenario for On-/Offboarding Data Basic Settings .
Carry out the following activities under Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM
Suite Integration Scenario for On-/Offboarding Data Transfer of Employee Data from SAP ERP HCM to SuccessFactors
Onboarding :
BAdI: Extraction of Employee Data for SuccessFactors Onboarding
Features
Exporting Data for SuccessFactors Onboarding
For exporting new hire employee data from SAP ERP HCM to SuccessFactors Onboarding, you can use the report Trigger
Onboarding for Employee (report RH_SFI_TRIGGER_ONBOARDING). For more information about this report, see Customizing
for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding
Data Transfer of Employee Data from SAP ERP HCM to SuccessFactors Onboarding Trigger Onboarding for Employee . You
can also nd this report in the user menu of the role SuccessFactors Integration: Onboarding Data (role
SAP_HR_SFI_ONBOARDING_2).
By de ning eld sets, you de ne which eld contents you want to export to SuccessFactors Onboarding. A eld set contains
multiple SuccessFactors Onboarding elds that you map to the SAP ERP elds of your choice. You have the following options:
You can map the elds directly to each other using a table in Customizing for Integration Add-On for SAP ERP HCM and
SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Basic Settings Map SuccessFactors HCM
Suite Fields and SAP ERP HCM Fields .
To make more complex mappings, you can create a Business Add-In (BAdI) implementation in Customizing for
4/26/2019
Data Transfer of Employee Data from SAP ERP HCM to SuccessFactors Onboarding BAdI: Extraction of Employee
Data for SuccessFactors Onboarding .
As standard, template mappings of SuccessFactors Onboarding elds to SAP ERP HCM elds are de ned.
Further Processing of Exported Data
You can check the data exported from SAP ERP HCM to SuccessFactors Onboarding and complete it as required or cancel
onboarding for an employee. For more information, see Further Processing of Exported Data in SAP ERP HCM.
Mapping of SuccessFactors Onboarding

Fields to SAP ERP HCM
The following list shows which SuccessFactors Onboarding elds are used as a template to transfer employee data from SAP
ERP HCM and to which SAP ERP HCM elds they are mapped. These elds are mapped to the eld set
SAP_DEMO_TRIGGER_ONB. You can create your own eld set and map elds in accordance with your requirements.

Department DeptCode Infotype Organizational

Code Assignment (0001), eld Org.
Code (ORGEH)
Division DivCode Infotype Organizational

Code Assignment (0001), eld
Company Code (BUKRS)
E-Mail EMail Infotype Communication

(0105)/subtype E-Mail (0010),
eld Communication: Long
Identi cation/Number
(USRID_LONG)
First Name FirstName Infotype Personal Data (0002),

eld First Name (VORNA)
Last Name LastName Infotype Personal Data (0002),

eld Last Name (NACHN)
Personnel LocNumber Infotype Organizational

Area Assignment (0001), eld
Personnel Area (WERKS)
Middle MiddleName Infotype Personal Data (0002),

Name eld Middle Name (MIDNM)
Employee EEGroup Infotype Organizational

Group Assignment (0001), eld
Employee Group (PERSG)
Employee EESGroup Infotype Organizational

Subgroup Assignment (0001), eld
Employee Sub Group (PERSK)
Race Code EthnicGroupCode2 Infotype Additional Personal Data Field is country-speci c

(0077), eld Ethnicity (RACKY)
4/26/2019

Gender Gender Infotype Personal Data (0002),

Code eld Gender (GESCH)
Hispanic or HispOrLat Infotype Additional Personal Data Field is country-speci c

Latino (0077), eld Ethnic Origin
(ETHEN)
Job Code JobCode Infotype Organizational

Assignment (0001), eld Job
Code (STELL)
Pay Rate JobPayRate Infotype Basic Pay (0008), eld

Pay Rate Per Payroll Frequency
(DIVGV)
Social SSN Infotype Personal Data (0002), Field is country-speci c

Security eld SSN (PERID)
Number
Start Date WOTCStartDate Infotype Actions (0000), eld If the start date or date of birth that is transferred to
Start Date (BEGDA) SuccessFactors Onboarding contains slashes (/), it should be
mapped via Business Add-In (BAdI) and converted to the date
Date of DateOfBirth Infotype Personal Data (0002), format used in SuccessFactors Onboarding
Birth eld Date of Birth (GBDAT)
Further Processing of Exported Data in SAP

ERP HCM
Use
Using the transaction Process Applications Imported from or Exported to Onboarding (transaction HRSFI_ONB_HIRE), the HR
administrator can monitor the data imported from or exported to SuccessFactors Onboarding. The transaction is located in the
role SuccessFactors Integration: Onboarding Data (role SAP_HR_SFI_ONBOARDING_2).
Prerequisites
Scenario for On-/Offboarding Data Transfer of Employee Data from SAP ERP HCM to SuccessFactors Onboarding .
Features
A list is displayed of the employees transferred to SuccessFactors Onboarding. This overview serves as a task list for the HR
administrator who can see which employees require additional data, or for which employees further action is required.
Note
In the list, only those employees are shown for whom the HR administrator has the necessary authorizations for the
employee data.
4/26/2019
General Messages
You can display messages that apply to all data by clicking General Messages. For example, a general message is issued if the
middleware connection was not available and no data could be transferred.
You can display any error and warning messages for the exported data by clicking the message log icon in the Msg. column. The
messages are displayed on the Messages tab below. For example, a warning message is displayed if the eld content is missing
for elds that are not mandatory.
First Name, Last Name, Hire Date, Date of Birth
SAP ERP HCM uses the application data transferred to SuccessFactors Onboarding to derive the rst name, last name, hire
date, and date of birth.
Note
You de ne how the rst name, last name, hire date, and date of birth are determined in Customizing for Integration Add-On
for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Basic Settings BAdI:
Determination of Further Data for Onboarding from SuccessFactors .
Application Details
On the Details tab, you can display information about the employee and the processing of the application. For a list of all elds
transferred to SuccessFactors Onboarding, click Show Details.
Delete Application
You can delete employees from the list, for example, if an employee doesn’t show up and onboarding needs to be cancelled. You
do this by selecting the employee and choosing Delete. The employee is removed from the list and the related messages are
deleted. SuccessFactors Onboarding is noti ed of the deletion.
Integration Scenario for Offboarding Data

Use
You can extract employee data and transfer it to SuccessFactors Offboarding for offboarding activities. When the offboarding
activities are complete in SuccessFactors HCM Suite, you can import the data from SuccessFactors Offboarding to SAP ERP
HCM.
Integration
see Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration .
Features
You can use middleware to transfer the employee data from SAP ERP HCM to SuccessFactors Offboarding. For more
information, see:
4/26/2019
Transfer of Employee Data to SuccessFactors Offboarding
Transfer of Employee Data from SuccessFactors Offboarding
See Integration Scenario Process for Offboarding Data.
Integration Scenario Process for Offboarding

Data
Use
The integration scenario process for offboarding data provides functions and features to transfer employee data from SAP ERP
HCM to SuccessFactors Offboarding and vice versa.
Data Flow
The following gure shows the data ow.
Figure 7: Data Flow
Business Work ow
The following gure shows the business work ow. At the end of a resignation, termination, or transfer action, the integration
add-on triggers the transmission of the employee data to SuccessFactors Offboarding using a recurring job that runs in the
background. The HR administrator monitors and triggers the deletion of the offboarding data if offboarding needs to be
cancelled.
4/26/2019
When offboarding is complete, SAP ERP HCM imports the data from SuccessFactors Offboarding. The HR administrator
monitors and triggers the update of the employee data based on the imported offboarding data.
Figure 8: Business Workflow
Processing Blocks to Trigger Offboarding from SAP ERP HCM to SuccessFactors Offboarding
At the end of a resignation, termination, or transfer action, the integration add-on triggers the transmission of the employee
data to SuccessFactors Offboarding. The ID of the newly created data in SuccessFactors Offboarding is returned and saved in
the integration add-on for future reference.
To keep the data consistent between SAP ERP HCM and SuccessFactors Offboarding, a utility report scans the SAP ERP HCM
system for any updates to the employee data and transmits the updates to SuccessFactors Offboarding.
4/26/2019
Figure 9: Processing Blocks to Trigger Offboarding from SAP ERP HCM to SuccessFactors Offboarding
Processing Blocks to Import Offboarding Data from SuccessFactors Offboarding to SAP ERP HCM
SuccessFactors Offboarding captures the data of the offboarded employee. When the data collection is complete in
SuccessFactors Offboarding, the data is imported to SAP ERP HCM. An active BAdI implementation is provided as standard so
that the data is imported from SuccessFactors Offboarding when the offboarding application has the status All Documents
Submitted. See also Transfer of Employee Data from SuccessFactors Offboarding.
4/26/2019
Figure 10: Processing Blocks to Import Offboarding Data from SuccessFactors Offboarding to SAP ERP HCM
Process
1. You schedule the transaction Trigger Offboarding for Employee (transaction HRSFI_OFB_TRIGGER) in the SAP ERP
system to run regularly in the background.
2. Each time the report is run, it triggers a check for employees in SAP ERP HCM for whom offboarding needs to be
triggered.
3. Based on the mapping con guration, the report gets the details for each employee eligible for offboarding.
For more information, see Mapping of SuccessFactors Offboarding Fields to SAP ERP HCM.
4. The report sends the data to SuccessFactors Offboarding using the SOAP API PostOffboardUser with the
appropriate parameters.
5. SuccessFactors Offboarding returns the HR data ID.
6. The data exported and the HR data ID returned are saved to the staging tables in the SAP ERP HCM add-on.
7. Using the transaction Process Employee Data Imported from or Exported to SuccessFactors Offboarding (transaction
HRSFI_OFB), the HR administrator monitors the employees sent for offboarding.
In this transaction, the status of all offboarded employees is visible centrally. The administrator can delete the record if
offboarding needs to be cancelled. For more information see Further Processing of Exported Data in SAP ERP HCM.
8. You schedule the transaction Import Employee Data from SuccessFactors Offboarding (transaction
HRSFI_OFB_DATA_IMP) in the SAP ERP system to run regularly in the background.
9. Each time the report is run, it triggers the import of data from SuccessFactors Offboarding for all employees for whom
offboarding has been triggered.
4/26/2019
10. The report gets the details for each employee by querying the SOAP API GetOffboardUserRecordWithExportId
with the appropriate parameters.
11. The imported data is checked that it is complete and eligible for further processing. If the offboarding process is not yet
complete, the record is rejected for further processing.
12. The eligible data from SuccessFactors Offboarding is prepared to the ERP format using the mapping con guration. For
more information, see Mapping of SuccessFactors Offboarding Fields to SAP ERP HCM.
13. The prepared data is saved to the staging tables in the SAP ERP HCM add-on.
14. Using the transaction Process Employee Data Imported from or Exported to SuccessFactors Offboarding (transaction
HRSFI_OFB), the HR administrator processes the prepared data and updates the employee master data.
In this transaction, the status of all offboarded employees is visible centrally. The process is as follows:
a. When the HR administrator chooses Start Action, the system triggers the transaction Personnel Actions
(transaction PA40) with the appropriate action type.
b. When the personnel action is complete, the system sets the record to Completed in SAP ERP HCM.
For more information see Further Processing of Imported Data in SAP ERP HCM.
Transfer of Employee Data to

SuccessFactors Offboarding
Use
You can export employee data from SAP ERP HCM to SuccessFactors Offboarding. Based on the personnel action in SAP ERP
HCM, offboarding for an employee can be triggered from SAP ERP HCM.
Prerequisites
In SuccessFactors Offboarding, create a data dictionary containing all elds to be imported from SAP ERP HCM. Download the
In SuccessFactors Offboarding, either set the account option XpressHR.InputToXmlData to blank if there is no other
integration with SuccessFactors Onboarding or Offboarding, or set the appropriate XSLT path in the Value column, as shown in
the following example.
Figure 11: Example XSLT Path
A sample XSLT le is available at http://help.sap.com/saphelpiis_cloud4hr/EN/HRXML.ImportNewHire.xslt .

4/26/2019
Recommendation
Carry out the activities under Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM
Suite Integration Scenario for On-/Offboarding Data Basic Settings .
Carry out the following activities under Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM
Suite Integration Scenario for On-/Offboarding Data Transfer of Employee Data from SAP ERP HCM to SuccessFactors
Offboarding :
BAdI: Extraction of Employee Data for SuccessFactors Offboarding
Features
Exporting Data for SuccessFactors Offboarding
For exporting employee data from SAP ERP HCM to SuccessFactors Offboarding, you can use the report Trigger Offboarding for
Employee (report RH_SFI_TRIGGER_OFFBOARDING). For more information about this report, see Customizing for
Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Transfer
of Employee Data from SAP ERP HCM to SuccessFactors Offboarding Trigger Offboarding for Employee . You can also nd this
report in the user menu of the role SuccessFactors Integration: Onboarding Data (role SAP_HR_SFI_ONBOARDING_2).
By de ning eld sets, you de ne which eld contents you want to export to SuccessFactors Offboarding. A eld set contains
multiple SuccessFactors Offboarding elds that you map to the SAP ERP elds of your choice. You have the following options:
You can map the elds directly to each other using a table in Customizing for Integration Add-On for SAP ERP HCM and
SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Basic Settings Map SuccessFactors HCM
Suite Fields and SAP ERP HCM Fields .
To make more complex mappings, you can create a Business Add-In (BAdI) implementation in Customizing for
Data Transfer of Employee Data from SAP ERP HCM to SuccessFactors Offboarding BAdI: Extraction of Employee
Data for SuccessFactors Offboarding .
As standard, template mappings of SuccessFactors Offboarding elds to SAP ERP HCM elds are de ned.
Further Processing of Exported Data
You can check the data exported from SAP ERP HCM to SuccessFactors Offboarding and complete it as required or cancel
offboarding for an employee. For more information, see Further Processing of Exported Data in SAP ERP HCM.
Mapping of SuccessFactors Offboarding

4/26/2019
The following list shows which SuccessFactors Offboarding elds are used as a template to transfer employee data from SAP
ERP HCM and to which SAP ERP HCM elds they are mapped. These elds are mapped to the eld set
SAP_DEMO_TRIGGER_OFB. You can create your own eld set and map elds in accordance with your requirements.
Field SuccessFactors SAP ERP HCM Field

Content Offboarding Field
Department DeptCode Infotype Organizational Assignment (0001), eld Org. Code (ORGEH)
Code
Division DivCode Infotype Organizational Assignment (0001), eld Company Code (BUKRS)
Code
E-Mail EMail Infotype Communication (0105)/subtype E-Mail (0010), eld Communication: Long
Identi cation/Number (USRID_LONG)
First Name FirstName Infotype Personal Data (0002), eld First Name (VORNA)
Last Name LastName Infotype Personal Data (0002), eld Last Name (NACHN)
Last Working LastWorkingDay Infotype Actions (0000), eld Begin Date (BEGDA)
Day
Personnel LocNumber Infotype Organizational Assignment (0001), eld Personnel Area (WERKS)
Area
Middle MiddleName Infotype Personal Data (0002), eld Middle Name (MIDNM)
Name
Further Processing of Exported Data in SAP

ERP HCM
Use
Using the transaction Process Employee Data Exported to SuccessFactors Offboarding (transaction HRSFI_OFB), the HR
administrator can monitor the data exported to SuccessFactors Offboarding. The transaction is located in the role
Prerequisites
Scenario for On-/Offboarding Data Transfer of Employee Data from SAP ERP HCM to SuccessFactors Offboarding .
Features
A list is displayed of the employees transferred to SuccessFactors Offboarding. This overview serves as a task list for the HR
administrator who can see which employees require additional data, or for which employees further action is required.
Note
In the list, only those employees are shown for whom the HR administrator has the necessary authorizations for the
employee data.
4/26/2019
General Messages
You can display messages that apply to all data by clicking General Messages. For example, a general message is issued if the
middleware connection was not available and no data could be transferred.
You can display any error and warning messages for the exported data by clicking the message log icon in the Msg. column. The
messages are displayed on the Messages tab below. For example, a warning message is displayed if the eld content is missing
for elds that are not mandatory.
First Name, Last Name, Last Working Date, Date of Birth
SAP ERP HCM uses the application data transferred to SuccessFactors Offboarding to derive the rst name, last name, last
working date, and date of birth.
Note
You de ne how the rst name, last name, last working date, and date of birth are determined in Customizing for Integration
Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Basic
Settings BAdI: Determination of Further Data for Onboarding from SuccessFactors .
Application Details
On the Details tab, you can display information about the employee and the processing of the application. For a list of all elds
transferred to SuccessFactors Offboarding, click Show Details.
Delete Application
You can delete employees from the list, for example, if an employee withdraws her resignation and offboarding needs to be
cancelled. You do this by selecting the employee and choosing Delete. The employee is removed from the list and the related
messages are deleted. SuccessFactors Offboarding is noti ed of the deletion.
Transfer of Employee Data from

SuccessFactors Offboarding
Use
You can import employee data from SuccessFactors Offboarding to SAP ERP HCM. When the offboarding process is complete,
you can import the offboarding data for further processing.
Prerequisites
In SuccessFactors Offboarding, there is a prede ned tag SAPHCM-Offboarding in the data dictionary. In this tag, include all
elds that you want to import from SAP ERP HCM or export to SAP ERP HCM. Be sure to include elds for rst name, last name,
date of birth, and last working date. Download the data dictionary in an XML le and upload it using report Import DDIC from
SuccessFactors Onboarding (transaction HRSFI_SYNCH_ONB_META).
To import data from SuccessFactors Offboarding, use report Trigger Offboarding for Employee (report
RH_SFI_TRIGGER_OFFBOARDING). This report triggers offboarding from SAP ERP HCM.
4/26/2019
Recommendation
On-/Offboarding Data , carry out the activities under Basic Settings.
On-/Offboarding Data , carry out the following activities under Transfer of Employee Data from SuccessFactors Offboarding to
SAP ERP HCM:
BADI: Eligibility of Offboarding Data for Import
Features
Importing Data from SuccessFactors Offboarding
For importing employee data from SuccessFactors Offboarding to SAP ERP HCM, you can use report Import Offboarding Data
from SuccessFactors HCM Suite (report RH_SFI_IMPORT_OFFBOARDING_DATA). For more information about this report,
see Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for
On-/Offboarding Data Transfer of Employee Data from SuccessFactors Offboarding to SAP ERP HCM Import Employee Data
from SuccessFactors Offboarding . You can also nd this report in the user menu of role SuccessFactors Integration:
Onboarding Data (role SAP_HR_SFI_ONBOARDING_2).
By de ning eld sets, you de ne which eld content you want to import from SuccessFactors Offboarding. A eld set contains
multiple SuccessFactors Offboarding elds that you map to the SAP ERP elds of your choice. You have the following options:
You map the elds directly to each other using a table.
You do this in Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration
Scenario for On-/Offboarding Data Basic Settings Map SuccessFactors HCM Suite Fields and SAP ERP HCM Fields .
To make more complex mappings, you can create a Business Add-In (BAdI) implementation.
You can use the following BAdIs for this in Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors
HCM Suite Integration Scenario for On-/Offboarding Data Basic Settings :
BAdI: Mapping of SuccessFactors Fields to SAP ERP Infotype Fields (BAdI de nition
HRSFI_B_FIELD_MAPPING)
You can use this BAdI to map a SuccessFactors Offboarding eld to an SAP ERP HCM eld.
BAdI: Change of Mapping Result (BAdI de nition HRSFI_B_CHANGE_MAPPING_RESULT)
You can use this BAdI to map one or more SuccessFactors Offboarding elds to one or more SAP ERP HCM elds.
As standard, template mappings of SuccessFactors Offboarding elds to SAP ERP HCM elds are de ned.
Further Processing the Imported Data
4/26/2019
You can check the data imported from SuccessFactors Offboarding and complete it as required. You can then use a personnel
action to transfer the data to SAP ERP HCM. For more information, see Further Processing of Imported Data in SAP ERP HCM.
Mapping of SuccessFactors Offboarding

The following list shows which SuccessFactors Offboarding elds are used as a template to transfer employee data from
SuccessFactors Offboarding to SAP ERP HCM, and to which SAP ERP HCM elds they are mapped. These elds are mapped to
the eld set SAP_DEMO_IMPORT_OFB. You can create your own eld set and map elds in accordance with your requirements.
Field Content SuccessFactors SAP ERP HCM Field

Offboarding Field
Street: Home Address1 Infotype Address (0006), subtype House Address (3), eld Street and House Number
Address (STRAS)
House Number Address2 Infotype Address (0006), subtype House Address (3), eld House Number (HSNMR)
City City Infotype Address (0006), subtype House Address (3), eld City (ORT01)
Country Country Infotype Address (0006), subtype House Address (3), eld Country Key (LAND1)
County CountyTownship Infotype Address (0006), subtype House Address (3), eld District Key (ORT02)
Township
State State Infotype Address (0006), subtype House Address (3), eld Region Code (STATE)
Zip Zip Infotype Address (0006), subtype House Address (3), eld Postal Code (PSTLZ)
Email Email Infotype Communication (0105), subtype Private E-Mail Address (0030), eld
Communication: Long Identi er (USRID_LONG)
Telephone PhoneNum Infotype Address (0006), subtype Home Address (3), eld Communication Type:
Communication Number (NUM01)
Further Processing of Imported Data in SAP

ERP HCM
Use
Using the transaction Process Employee Data Imported from or Exported to Offboarding (transaction HRSFI_OFB), the HR
administrator can check and, where required, complete the data imported from SuccessFactors Offboarding. The HR
administrator can then use a personnel action to transfer the data to SAP ERP HCM. The transaction is located in role
Prerequisites
Scenario for On-/Offboarding Data Transfer of Employee Data from SuccessFactors Offboarding to SAP ERP HCM .
Features
4/26/2019
In transaction Process Employee Data Imported from or Exported to Offboarding (transaction HRSFI_OFB), a list is displayed
of the employee data transferred from SuccessFactors Offboarding that has not yet been transferred to SAP ERP HCM
infotypes and therefore does not yet have the status Completed. This overview serves as a task list for the HR administrator
who can see which employees require additional data, or for which employees a personnel action can be started, and so on.
Note
The employees that the HR administrator sees in the list depend on whether the HR administrator has the necessary
authorizations for the employee data.
Employee Details
On the Details tab, you can display information about the employee and the processing of the data. For a list of all elds
transferred from SuccessFactors Offboarding, click Show Details.
You can display any error and warning messages for the imported data by clicking the icon in the Msg. (show messages) column.
For example, a warning message is displayed on the Messages tab below the table if the eld content is missing for elds that
are not mandatory.
General Messages
You can display messages that apply to all employees by clicking General Messages. For example, a general message is issued if
the middleware connection was not available and no data could be transferred.
Determination of First Name, Last Name, Last Working Date, and Date of Birth
SAP ERP HCM uses the employee data transferred from SuccessFactors Offboarding to derive the rst name, last name, last
working date, and date of birth. We recommend keeping these elds in the Data Dictionary tag SAPHCM-Offboarding in
SuccessFactors Offboarding.
Note
You de ne how the rst name, last name, last working date, and date of birth are determined in Customizing for Integration
Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for On-/Offboarding Data Basic
Settings BAdI: Determination of Further Data for Onboarding from SuccessFactors .
Check for Personnel Action
SAP ERP HCM uses the employee data transferred from SuccessFactors Offboarding to derive possible personnel actions.
Note
You de ne how the personnel actions are determined in Customizing for Integration Add-On for SAP ERP HCM and
If SAP ERP HCM could not determine a unique personnel action from the data transferred from SuccessFactors Offboarding, it
displays an error message for this employee, and gives the employee the statusTo Be Checked. You must then de ne the
personnel action to be performed for this employee. You do this by clicking the red light in the Check column to open the Check
and Change Data dialog box, where you select a personnel action.
4/26/2019
Start Personnel Action
If all data required for an employee is available, the employee has the status Start Action. For this employee, you can then click
the Start Action pushbutton to transfer the employee data to personnel administration using the transaction Personnel
Actions (transaction PA40). The eld contents transferred from SuccessFactors Offboarding are then transferred to the SAP
ERP HCM infotype elds mapped to the SuccessFactors Offboarding elds in Customizing. After the personnel action is
performed, the application is given the status Completed.
Set to Completed Manually
For employees whose status could not be set by the system to Completed, you can set the status to completed manually so
that they no longer appear in the list of unprocessed employees. You do this by selecting the employee and choosing Complete.
Display Completed Employees
You can display the employees that were transferred on or after a certain date and have already been completed automatically
or manually. You do this by choosing Show Processed. To return to the list of unprocessed employees, choose Show Open
Applications.
Delete Employees
You can delete employees from the list, for example, if an employee withdraws her resignation and offboarding needs to be
cancelled. You do this by selecting the employee and choosing Delete. The employee is removed from the list and the related
messages are deleted. SuccessFactors Offboarding is noti ed of the deletion.
Integration Scenario for Employee Data

Use
You can extract attributes for employees, including organizational attributes, from the SAP ERP HCM system and transfer them
to SuccessFactors HCM Suite so that they are available for Talent Management processes. You can also transfer data to
SuccessFactors for employees whose hiring date is in the future to support their integration into the enterprise.
Prerequisites
In Customizing for the Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite, you have made the settings in the
section Integration Scenario for Employee Data.
Features
You can use middleware or the le download to transfer employee data to SuccessFactors.
Caution
The integration using middleware is not available for the report Extraction of Employee Data for SuccessFactors
(RH_SFI_TRIGGER_EMPL_DATA_REPL).
For more information, see Integration Using Middleware and Integration Using File Download.
4/26/2019
For more information, see Integration Scenario Process for Employee Data.
Extraction of Employee Data
You can use one of the following reports to extract the data from the SAP ERP HCM system:
Extraction of Employee Data for SuccessFactors (RH_SFI_TRIGGER_EMPL_DATA_REPL)
Each time this report is run, it extracts all data for the selected employees. It downloads the data to a comma-separated
values le so that it can be uploaded to SuccessFactors.
Sync Employee Data with SuccessFactors (with Delta and Inactive Logic) (RH_SFI_SYNCHRONIZE_EMPL_DATA)
This report runs a delta data extraction. Each time the report is run, it extracts only the data for the selected employees
that has changed since the last time the report was run. It also ensures that employees who are not included in the
selection area of the extraction variant used are assigned the status Inactive. For example, this can be the case if
employees switch to an enterprise area for which no integration with SuccessFactors is planned. You can use this report
to download the extracted data to a CSV le or to transfer it to SuccessFactors via middleware.
Recommendation
For the following reasons, we recommend that you use the report RH_SFI_SYNCHRONIZE_EMPL_DATA:
The rst time this report is run, it initially extracts all or a large part of the data on the selected employees. However,
the volume of extracted data is usually reduced signi cantly afterwards.
The application for monitoring the transfer of data from SAP ERP to SuccessFactors displays only the noti cations
that the report RH_SFI_SYNCHRONIZE_EMPL_DATA generates. This application does not display noti cations that
the report RH_SFI_TRIGGER_EMPL_DATA_REPL generates.
Integration using middleware is only available for the report RH_SFI_SYNCHRONIZE_EMPL_DATA). The report
RH_SFI_TRIGGER_EMPL_DATA_REPL cannot use middleware to transfer any data to SuccessFactors.
Caution
You need to choose one of the two reports. You cannot use the two reports interchangeably.
For more information about the data extraction reports, see Customizing for the integration add-on, under Integration
Scenario for Employee Data Run Extraction of Employee Data and Organizational Data . The reports are also located in the
user menu for the role SuccessFactors Integration: Employee Data Replication (SAP_HR_SFI_EMPL_DATA_REPL).
Caution
Once you have used one of the reports 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 work ow, authorizations, and reporting in
SuccessFactors. If you change the settings for a repeated extraction of data, you may generate new objects in
SuccessFactors and may, for example, need to modify authorizations accordingly.
Make sure that you always use the same option for the eld USERID.
 Example
4/26/2019
You have chosen German as the language for the data extraction. Therefore, the report extracted the employee subgroup
Leitende Angestellte (Executive Employees). You transferred this to SuccessFactors. 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, 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 eld USERID. If you choose the option External Person
ID instead during the next extraction run, this causes inconsistencies. Therefore, do not make any changes to this setting.
Data Extraction in Pre-Hire Period of New Employees
You can extract data for future employees from the SAP ERP system and transfer it to SuccessFactors. The data for integrating
new employees into the enterprise is thereby available, for example, to enable future employees to access SAP Jam.
Caution
The future employees are transferred to SuccessFactors as active employees, even though their entry date is in the future.
Therefore, make sure that future employees do not have authorization to access the SuccessFactors applications and that
they are not integrated into the business processes, meaning that they are not visible to their future managers, for example.
Recommendation
We recommend that you de ne an indicator in a customer-speci c eld that identi es future employees as such.
Note
To make the corresponding settings in SuccessFactors, contact the Professional Services team provided by SuccessFactors.
Use the report Sync Employee Data with SuccessFactors in Pre-Hire Period (RH_SFI_PREHIRE_EMPL_DATA) for the
extraction of data for future employees. You can use this report to download the extracted data to a CSV le or to transfer it to
SuccessFactors via middleware.
For more information about this report, see Customizing for the integration add-on, under Integration Scenario for Employee
Data Perform Extraction of Employee Data in Pre-Hire Period . The report is also located in the user menu for the role
SuccessFactors Integration: Onboarding (SAP_HR_SFI_ONBOARDING).
Extracted Data
You can extract content for the SuccessFactors elds that are listed in Mapping of SuccessFactors HCM Suite Fields for
Employee Data to SAP ERP Fields. This applies to all reports mentioned above.
Extraction Options
You have the following options for all reports mentioned above:
You can choose between various standard extraction options for some of the data to be extracted.
 Example
The standard SAP ERP system can determine the content for the SuccessFactors eld MANAGER as follows:
Using the relationship Is managed by… (B012) between the employee’s organizational unit and
the manager’s position
4/26/2019
Using the relationship Reports (line) to (A002) between the employee’s position and the
manager’s position
For more information about the extraction options, see the eld help for the data extraction report and Mapping of
SuccessFactors HCM Suite Fields for Employee Data to SAP ERP Fields.
You can adapt the data extraction to suit your requirements for all elds, without making modi cations. To do so, you use
the Business Add-In (BAdI) Replication of Employee's Data (HRSFI_B_EMPL_DATA_REPLICATION). The BAdI provides
a separate method for each SuccessFactors eld. For the BAdI, see Customizing for the integration add-on, under
Integration Scenario for Employee Data Business Add-Ins (BAdIs) .
You can overwrite the extracted standard eld labels with customer-speci c labels. To do so, use the BAdI Labels for
Fields of Data Replication (HRSFI_B_EMPL_DATA_REPL_LABEL). For the BAdI, see Customizing for the integration
add-on, under Integration Scenario for Employee Data Business Add-Ins (BAdIs) .
Transfer Additional Parameters to SuccessFactors
In addition to the employee data, you can transfer other parameters to SuccessFactors:
Parameter validateMgrHr
The selection screen of the reports Sync Employee Data with SuccessFactors (with Delta and Inactive Logic) and Sync
Employee Data with SuccessFactors in Pre-Hire Period has the new indicator No Validation of Manager and HR
Manager. You can use this indicator to specify that the reports do not check whether the user IDs that were extracted
for the elds MANAGER and HR are already known in SuccessFactors. In SuccessFactors , this corresponds to the
parameter validateMgrHr.
Additional parameters
If you use middleware for the integration, you can transfer additional parameters to SuccessFactors. To do so, implement
the BAdI Parameters for Checks of Employee Data Transfer (HRSFI_B_SFSF_API_PARAMETER). For the BAdI, see
Customizing for the integration add-on, under Integration Scenario for Employee Data Business Add-Ins (BAdIs) .
Extension of Data Extraction
You can use the elds CUSTOM01 – CUSTOM15 to supplement the extraction of employee data with customer-speci c
elds. For more information, see Customizing for the integration add-on, under Integration Scenario for Employee
Data Extend Extraction of Employee Data .
Completion of Data Extraction
You can discontinue the extraction of data for a group of employees. To do so, run the report Discontinue Data Sync. with
SuccessFactors for Group of Employees (RH_SFI_WITHDRAW_VARIANT) to set all employees contained in the selection for an
extraction variant of the report Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)
(RH_SFI_SYNCHRONIZE_EMPL_DATA) to the status Inactive. For example, this is useful if you want to exclude an enterprise
area for which you have previously transferred data to SuccessFactors from the data transfer in future.
For more information about the report RH_SFI_WITHDRAW_VARIANT, see Customizing for the integration add-on, under
Integration Scenario for Employee Data Discontinue Data Extraction for Group of Employees . The report is also located in
the user menu for the role SuccessFactors Integration: Employee Data Replication (SAP_HR_SFI_EMPL_DATA_REPL).
Data Extraction for Employees in Concurrent or Global Employment
If employees are in concurrent or global employment and therefore have multiple personnel assignments (meaning personnel
numbers), the data extraction reports extract the data for one of the personnel numbers. For more information, see Extraction
of Employee Data for Concurrent Employment and Global Employment.
4/26/2019
Error Handling
You can trace and process errors that occurred during the extraction or transfer of data using the report Sync Employee Data
with SuccessFactors (with Delta and Inactive Logic) (RH_SFI_SYNCHRONIZE_EMPL_DATA) in an application for monitoring
the extraction of data.
Integration Scenario Process for Employee

Data
Use
The process for transferring employee data and organizational data from SAP ERP HCM to SuccessFactors HCM Suite is as
follows.
Process
1. You 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 eld USERID in each extraction variant.
2. If you use the report Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)
(RH_SFI_SYNCHRONIZE_EMPL_DATA) or Sync Employee Data with SuccessFactors in Pre-Hire Period
(RH_SFI_PREHIRE_EMPL_DATA), enter the allowed variants in the Customizing activity Specify Allowed Variants for
Delta Extraction.
3. You schedule the report of your choice with the extraction variants to be run regularly in the background.
Note
Ensure that the variants are always run with the same frequency and in the same sequence to avoid data
inconsistencies.
4. You transfer the extracted data to SuccessFactors.
If you use a le download for the integration, upload the generated CSV les to SuccessFactors.
If you use middleware for the integration, the report RH_SFI_SYNCHRONIZE_EMPL_DATA or

RH_SFI_PREHIRE_EMPL_DATA sends corresponding Web services to the middleware used. For more
information, see Process for Using Middleware for the Integration.
5. If errors occurred when extracting or transferring data, proceed as described in Monitoring the Transfer of Data from
SAP ERP to SuccessFactors HCM Suite.

Employee Data to SAP ERP
Use
4/26/2019
The following list shows which eld contents from the SAP ERP system you can extract for which SuccessFactors elds. You
de ne the extraction options on the selection screen of the report that you use to extract the data. For more information, see
SAP Library for the add-on and choose Integration Scenario for Employee Data in the Extraction Options section.
Note
You also have the option of de ning a customer-speci c Business Add-In implementation for each of the elds.
SuccessFactors Field SAP ERP Field Comment
STATUS Employment status from the Actions The SAP ERP status is mapped to the
infotype (0000). SuccessFactors status as follows:
Active > Active
Pensioner > Inactive
Left Company > Inactive
Inactive > Inactive
USERID
Central person (object type CP)
External person ID from the infotype

Person ID (0709)
USERNAME
User (object type US)
Central person (object type CP)
FIRSTNAME You make the relevant Customizing settings

Infotype Personal Data (0002)
in Customizing for the integration add-on for
Customizing SAP ERP HCM and SuccessFactors under
Integration Scenario for Employee
Data De ne Name Format for Fields
FIRSTNAME and LASTNAME
LASTNAME You make the relevant Customizing settings

Infotype Personal Data (0002)
in Customizing for the integration add-on for
Customizing SAP ERP HCM and SuccessFactors under
Integration Scenario for Employee
Data De ne Name Format for Fields
FIRSTNAME and LASTNAME
MI Infotype Personal Data (0002)
GENDER Infotype Personal Data (0002)
EMAIL
Infotype Communication (0105),
subtype E-Mail (0010)

subtype E-Mail (MAIL)
User data
4/26/2019
MANAGER The option NO_MANAGER is available only

Relationship Is managed by…
for the report Sync Employee Data with
(B012) between the employee’s
SuccessFactors in Pre-Hire Period
organizational unit and the
(RH_SFI_PREHIRE_EMPL_DATA).
manager’s position
NO_MANAGER is the default setting.
Relationship Reports (line) to
(A002) between the employee’s
position and the manager’s position
Entry NO_MANAGER
HR The option NO_HR is available only for the

Administrator for HR master data
report Sync Employee Data with
from the Organizational
SuccessFactors in Pre-Hire Period
Assignment infotype (0001)
(RH_SFI_PREHIRE_EMPL_DATA). NO_HR
Entry NO_HR is the default setting.
DEPARTMENT
Organizational unit from the
Organizational Assignment
infotype (0001)
Cost center from the Organizational

JOBCODE Job from the Organizational Assignment

infotype (0001)
DIVISION Company code from the Organizational

LOCATION Personnel area from the Organizational

TIMEZONE User data
HIREDATE Feature ENTRY
EMPID Personnel number
TITLE
Position from the Organizational
Job from the Organizational

Customer-speci c implementation
BIZ_PHONE
Internal telephone number (two
elds) from the infotype Internal
Data (0032)

subtype First Telephone Number
at Work (0020)
FAX Infotype Communication (0105), subtype

Cell Phone (CELL)
4/26/2019
ADDR1 Description of personnel area from the

Organizational Assignment infotype (0001)
ADDR2 Street of personnel area from the

CITY City of personnel area from the

STATE Region of personnel area from the

ZIP Zip code of personnel area from the

COUNTRY The SAP ERP country keys are mapped to

Country key of personnel area from
the country descriptions used in
the Organizational Assignment
SuccessFactors
infotype (0001)
Country key for the employee's

country grouping
REVIEW_FREQ Customer-speci c implementation
LAST_REVIEW_DATE Customer-speci c implementation
CUSTOM01 Personnel subarea from the Organizational You can de ne how to ll each CUSTOM eld
CUSTOM02 Employee group from the Organizational You can de ne how to ll each CUSTOM eld
CUSTOM03 Employee subgroup from the You can de ne how to ll each CUSTOM eld
CUSTOM04 – CUSTOM15 Customer-speci c implementation You can de ne how to ll each CUSTOM eld
MATRIX_MANAGER Relationship Reports (line) to (A002) For the report Sync Employee Data with
between the employee’s position and the SuccessFactors in Pre-Hire Period
managers' positions (RH_SFI_PREHIRE_EMPL_DATA), the
default setting is that no data is transferred
for the eld MATRIX_MANAGER.
DEFAULT_LOCALE Communication language ( eld SPRSL) The SAP ERP languages are mapped to the
from the infotype Personal Data (0002) language labels used in SuccessFactors (for
example, DE to de_DE). If there is not
corresponding entry in SuccessFactors for
the language used in the SAP ERP system,
no content is transferred for the eld
DEFAULT_LOCALE.
CUSTOM_MANAGER Customer-speci c implementation
SECOND_MANAGER Customer-speci c implementation
PROXY Customer-speci c implementation
4/26/2019
LOGINMETHOD
Character string SSO: The
employees can only use Single Sign-
On to log on to the SuccessFactors
system
Character string PWD: The

employees can only use their
password to log on to the
SuccessFactors system
Extraction of Employee Data for Concurrent

and Global Employment
Use
If employees are in concurrent or global employment and therefore have multiple personnel assignments (meaning personnel
numbers), the data extraction report extracts the data for one of the personnel numbers. If you de ne one of the personnel
assignments as the main assignment, the data is extracted for this personnel number.
Note
If an employee has multiple personnel assignments, but does not have a main assignment de ned, the data extraction
report uses the personnel assignment with the latest end date. If the latest end date is valid for more than one of the
personnel assignments, or if there are only inactive personnel assignments for the employee on the key date of the data
extraction, the report selects one of these personnel assignments at random.
Features
You have the following options for de ning a main assignment for employees in concurrent or global employment:
Create a record of the infotype Main Personnel Assignment (0712) with subtype SuccessFactors (SFSF) for the relevant
employees.
Recommendation
We recommend this procedure.
Use the Business Add-In (BAdI) Determining the Leading Assignment for a Central Person
(HRSFI_B_LEADING_CONTRACT). For the BAdI, see Customizing for the Integration Add-On for SAP ERP HCM and
SuccessFactors HCM Suite.
Monitoring the Transfer of Data from SAP

ERP to SuccessFactors
Use
4/26/2019
You can use the Web Dynpro application HRSFI_MONITORING_EMPL to monitor the transfer of employee data and
compensation data from SAP ERP to SuccessFactors HCM Suite. The application informs you of which data has been
successfully extracted and transferred, and for which employees the data extraction or data transfer failed. The application
displays all messages of the type error and warning that occurred and supports you with resolving the errors.
SuccessFactors Integration: Composite Role (SAP_HR_SFI_C)
Prerequisites
If you want to use the application HRSFI_MONITORING_EMPL to monitor the extraction of employee data, you need to use the
report Sync Employee Data with SuccessFactors (with Delta and Inactive Logic) (RH_SFI_SYNCHRONIZE_EMPL_DATA) to
extract this data. If you use the report Extraction of Employee Data for SuccessFactors
(RH_SFI_TRIGGER_EMPL_DATA_REPL), the application HRSFI_MONITORING_EMPL does not display any messages for the
extraction of employee data.
Note
The monitoring of the extraction of compensation data does not depend on whether you extract employee data or the
report you use to do so.
Features
Displayed Data
The application for monitoring the data transfer from SAP ERP to SuccessFactors displays data for the following integration
scenarios:
Transfer of employee data
Transfer of compensation data
Modifying the Log and Message Lists
The lists are based on SAP List Viewer (ALV) for Web Dynpro. Therefore, you can use the following standard SAP List Viewer for
Web Dynpro functions:
Adjusting the display of the list
For more information, see the documentation for SAP List Viewer for Web Dynpro, under Displaying the List.
Sorting the list
For more information, see the documentation for SAP List Viewer for Web Dynpro, under Sorting the List.
Filtering the list
For more information, see the documentation for SAP List Viewer for Web Dynpro, under Filtering the List.
4/26/2019
Exporting the list to Microsoft Excel
For more information, see the documentation for SAP List Viewer for Web Dynpro, under Exporting the List to Microsoft
Excel.
You can save and reload all settings that you make for the application in views. For more information, see the documentation for
SAP List Viewer for Web Dynpro, under Personalizing the List.
For the documentation for SAP List Viewer for Web Dynpro, see SAP Library and choose Getting Started - Using SAP
Software Working with Tools and Functions Working with Lists .
Message Types
The message lists contain messages of the type error, warning, and success. The types of error are indicated by relevant icons.
Message Categories
The messages are sorted into the following categories:
Back-End Messages
Error messages and warnings that were triggered by the extraction of data in the SAP ERP system are listed here.
Transfer Messages
Error messages and warnings that were triggered by the transfer of data from the SAP ERP system to SuccessFactors
are listed here.
Processed Successfully
The number of employees for whom the extraction and transfer of data was successful is listed here.
Monitoring the Transfer of Employee Data
See Monitoring the Transfer of Employee Data.
Using the Message List to Transfer Compensation Data
See Monitoring the Transfer of Compensation Data.
Activities
If errors occur, proceed as follows:
1. Correct the errors.
2. In this application, set the status Solved for the relevant message.
3. Repeat the extraction of data. To do so, proceed as follows:
Wait for the next run of the data extraction report with the same extraction variant. The report automatically
selects the relevant personnel numbers and extracts their data again.
Repeat the extraction of data only for those employees for whom errors occurred.
Note
This option is only available for extracting employee data.
4/26/2019
4. If the extraction of data is successful the next time the report is run, the report deletes the relevant messages from this
application. If errors occur again during the extraction of data, this application displays relevant messages with the new
extraction date.

Use
You can use the Web Dynpro application HRSFI_MONITORING_EMPL to monitor the transfer of employee data from SAP ERP
to SuccessFactors HCM Suite.
Features
Successfully Processed Data
The Successfully Processed list provides you with an overview of the number of employees for whom the data has been
extracted and transferred successfully. In addition, this list displays the extraction variant with which the data has been
extracted.
Transfer Log
In the Transfer Log list you can display all transferred employee data.
To do so, rst use the selection criteria to de ne for which employees the data is to be displayed, and choose Transfer Selection.
You can then collapse the screen area with the selection criteria.
Recommendation
If you display a large amount of data, it can take some time to call the transfer log. In this case, we recommend that you use
the eld Maximum Number of Hits to restrict the number of employees for whom the data is to be displayed.
The transfer log contains the following information:
Information on the employees for whom data has been extracted ( rst and last name, personnel number from the SAP
ERP system, user ID from SuccessFactors)
Extraction variant with which the data has been extracted
Date and time of last data extraction
Current status of the data extraction as stored in the log table HRSFI_D_EXTR_LOG
The log table contains all data that the data extraction report extracted during the last run for the employees
concerned.
If a back-end error occurs, the log table contains the current data for the relevant employee, provided it could be
extracted before the error occurred. The other elds are empty.
Indicator Repeat Needed
If errors occurred during the data extraction, this indicator is set for the relevant employees. These employees are
automatically selected the next time the report is run using the same extraction variant. Their data is extracted again.
You can use the Detail pushbutton to display an overview of the data for an employee.
4/26/2019
Note
Which data is displayed in the transfer log also depends on whether the user has the authorizations required to display the
data. You use the Business Add-In (BAdI) Determine Program Which Selects Employees for Log Display in Monitor
(HRSFI_B_MONITORING_LOG_PROGRAM) to de ne the authorizations. For the BAdI, see Customizing for the integration
add-on, and choose Basic Settings.
Back-End Messages and Transfer Messages
The lists Back-End Messages and Transfer Messages provide you with an overview of all problems that occurred during the data
transfer.
The following functions are available:
You can check for which employees problems occurred.
For each message of the type error and warning, the application displays the employee's personnel number from the
SAP ERP system and user ID from SuccessFactors.
You can check when an error last occurred and for how long it has existed.
For back-end messages, the application displays the time at which the error last occurred and the date on which it rst
occurred. This provides you with an overview of employees for whom errors regularly occur over a longer period of time
and enables you to check and correct their speci c data.
For transfer messages, the application displays the date of the data transfer.
To record the processing status, you can set the status Solved for errors that you have resolved. You can reset the status
of errors from Solved to Unsolved if, for example, you determine that the error has not actually been resolved.
You can use the function Reload Employees for back-end messages to re-extract the data for employees for whom errors
occurred.
The data extraction report is run with the same extraction variant as in the original run; however, the selection is
temporarily restricted to the selected employees. In this case, the report extracts all data for the relevant employees
again.
More Information
Monitoring the Transfer of Data from SAP ERP to SuccessFactors HCM Suite
Integration Scenario for Compensation Data

Use
You can extract compensation data from the SAP ERP system and transfer it to SuccessFactors HCM Suite so that it is
available for compensation planning. When you have completed compensation planning, you can extract the planned
compensation data from SuccessFactors and transfer it to the SAP ERP system so that it can be processed in payroll.
Features
You can use middleware to transfer compensation data from SAP ERP to SuccessFactors and from SuccessFactors to SAP ERP.
4/26/2019
You can transfer compensation data in the following directions:
For more information, see Integration Scenario Process for Compensation Data.
Integration Scenario Process for

Compensation Data
Use
The process for transferring compensation data from SAP ERP HCM to SuccessFactors HCM Suite and vice versa is as follows.
Prerequisites
See Transferring Compensation Data from SAP ERP to SuccessFactors HCM Suite and Transferring Compensation Data from
SuccessFactors HCM Suite to SAP ERP.
Process
1. In SAP ERP, you run the report Replication of Employee's Compensation Data (RH_SFI_SYNCH_COMP_DATA).
Recommendation
If you also implement the integration scenario for employee data, on the selection screen of the report
RH_SFI_SYNCH_COMP_DATA, make the same settings for the SuccessFactors eld USERID that you use to extract
employee data.
For more information about the data extraction reports for employee data, see Customizing for the integration add-
on and choose Integration Scenario for Employee Data Run Extraction of Employee Data and Organizational Data
and Integration Scenario for Employee Data.
 Example
If, when extracting employee data for the eld USERID, you extract the IDs of the central persons of the relevant
employees, also use this setting to extract compensation data.
2. For the selected employees, the report extracts the compensation data for the SuccessFactors elds of your choice and
logs the current data extraction status in the table SuccessFactors: Comp Log Table for Transfer Data (Delta Log)
(HRSFI_D_COMP_EXT).
3. The report uses middleware to transfer the compensation data to SuccessFactors.
4/26/2019
4. In SuccessFactors, you use the data imported from SAP ERP to perform compensation planning for the relevant
employees.
5. After you have completed compensation planning in SuccessFactors, you run the report Import of Employee's Planned
Compensation Data (RH_SFI_IMPORT_COMP_DATA) in SAP ERP. In SuccessFactors, the report triggers a job to
retrieve the planned compensation data using an ad hoc report.
Note
The ad hoc report must contain the columns for the form template ID and the user ID. The column for the user ID
must have the property Constrainable.
Recommendation
Contact the Professional Service team provided by SuccessFactors to create suitable ad hoc reports.
6. The report stores the compensation data imported from SuccessFactors in the table lt_comp_data.
7. In SAP ERP, you run the report Activation of Employee's Planned Compensation Data
(RH_SFI_ACTIVATE_COMP_DATA).
The report activates the imported compensation data so that it can be processed in the SAP ERP system in payroll. For
example, it stores the data in the relevant infotype elds, according to your speci cations, and generates the wage types
of your choice.
8. If errors occurred when extracting or transferring data, proceed as described in Monitoring the Transfer of Data from
SAP ERP to SuccessFactors HCM Suite and Monitoring the Transfer of Data from SuccessFactors HCM Suite to SAP
ERP.
Transfer of Compensation Data from SAP

Use
You can extract compensation data from the SAP ERP system and transfer it to SuccessFactors HCM Suite so that it is
available for compensation planning.
Prerequisites
Employee data exists in SuccessFactors.
To provide the employee data in SuccessFactors, you can, for example, use the integration scenario for employee data of
this add-on. In this case, you rst need to schedule the report for extracting employee data before you can run the report
for extracting compensation data. You may need to run the report for extracting employee data twice so that the
relationships between the employees and their managers are created. These relationships need to be known in the
SuccessFactors system before the employees can be assigned to the form templates for compensation planning.
The Professional Service team provided by SuccessFactors has provided you with information on which group ID
SuccessFactors uses to assign the data extracted from SAP ERP to the form templates for compensation planning.
In Customizing for the integration add-on for SAP ERP HCM and SuccessFactors, you have made the settings under
Integration Scenario for Compensation Data Transfer of Data from SAP ERP to SuccessFactors BizX .
Features
4/26/2019
Data Extraction Report
You can use the report Replication of Employee's Compensation Data (RH_SFI_SYNCH_COMP_DATA) to extract the data from
the SAP ERP system.
For more information about the data extraction report, see Customizing for the integration add-on, under Integration Scenario
for Compensation Data Transfer of Data from SAP ERP to SuccessFactors BizX Extract Compensation Data from SAP ERP .
The report is also located in the user menu for the role SuccessFactors Integration: Compensation Data Replication
(SAP_HR_SFI_COMP_DATA_REPL).
Extracted Data
In Customizing, you de ne which compensation data you want to extract from the SAP ERP system. To do so, you de ne sets of
SuccessFactors elds to which the data is to be transferred. For each eld, you use an implementation of the Business Add-In
(BAdI) Extraction of Compensation Data (HRSFI_B_COMP_FIELD_EXTRACTOR) to de ne how the data is to be determined in
the SAP ERP system.
You can delete entries that the report RH_SFI_SYNCH_COMP_DATA has generated in database tables of the SAP ERP system.
To do so, you use the report Cleanup of Internal Tables After Exporting Compensation Data (RH_SFI_CLEANUP_COMP_REPL).
For example, you can use the report to delete delta information to completely retransfer the compensation data to
SuccessFactors for the relevant employees.
For more information about the report, see Customizing for the integration add-on, under Integration Scenario for
Compensation Data Transfer of Data from SAP ERP to SuccessFactors BizX Cleanup Internal Tables in SAP ERP After
Export . The report is also located in the user menu for the role SuccessFactors Integration: Compensation Data Replication
(SAP_HR_SFI_COMP_DATA_REPL).
Error Handling
You can use an application for monitoring the transfer of data to track and process errors that occurred when extracting or
transferring data.
Transfer of Compensation Data from

Use
You can extract compensation planning data from SuccessFactors HCM Suite and transfer it to the SAP ERP system so that it is
available for payroll.
Prerequisites
In SuccessFactors, the application programming interfaces (APIs) have been made available for importing compensation
data. For this, contact the Professional Service team, or the Customer Support team provided by SuccessFactors.
In SuccessFactors, you use suitable form templates for compensation planning, which provide the data of your choice.
In SuccessFactors, you use suitable ad hoc reports to extract the compensation data.
4/26/2019
The ad hoc reports must contain the columns for the form template ID and the user ID. The column for the user ID must
have the property Constrainable. When con guring the ad hoc reports, also ensure that they extract data only from
completed forms.
Recommendation
Contact the Professional Service team provided by SuccessFactors to create suitable ad hoc reports.
The Professional Service team at SuccessFactors has provided you with the following information:
ID of the ad hoc report
IDs of the elds contained in the ad hoc report
Compensation planning is complete in SuccessFactors.
In Customizing for the integration add-on for SAP ERP HCM and SuccessFactors, you have made the settings under
Integration Scenario for Compensation Data Transfer of Data from SuccessFactors BizX to SAP ERP .
Features
Data Import
You can use the report Import of Employee's Planned Compensation Data (RH_SFI_IMPORT_COMP_DATA) to import the data
into the SAP ERP system.
For more information about the data import report, see Customizing for the integration add-on, under Integration Scenario for
Compensation Data Transfer of Data from SuccessFactors BizX to SAP ERP Import Compensation Data into SAP ERP . The
report is also located in the user menu for the role SuccessFactors Integration: Compensation Data Import and Activation
(SAP_HR_SFI_COMP_DATA_IMPORT).
Activation of Data for Payroll
You can use the report Activation of Employee's Planned Compensation Data (RH_SFI_ACTIVATE_COMP_DATA) to activate
the data in the SAP ERP system.
For more information about the data activation report, see Customizing for the integration add-on, under Integration Scenario
for Compensation Data Transfer of Data from SuccessFactors BizX to SAP ERP Activate Compensation Data for Payroll . The
report is also located in the user menu for the role SuccessFactors Integration: Compensation Data Import and Activation
(SAP_HR_SFI_COMP_DATA_IMPORT).
Imported and Activated Compensation Data
In Customizing, you determine which compensation data you want to import from the SuccessFactors system and activate for
payroll in the SAP ERP system. To do so, proceed as follows:
You use implementations of the Business Add-In (BAdI) Activation of Compensation Data Imported from SFSF
(HRSFI_B_COMP_DATA_ACTIVATION) to de ne how compensation data imported from the SuccessFactors system is
to be processed in payroll in the SAP ERP system.
You de ne eld mappings that map the SuccessFactors elds to the SAP ERP elds of your choice.
 Example
You can create a eld mapping that comprises all elds that you need for bonus payments and another mapping with
all elds for salary adjustments.
4/26/2019
You group the eld mappings in eld sets to import and activate all required compensation data collectively.
You can also use implementations of the BAdI Customizing Information Needed for Compensation Activation
(HRSFI_B_COMP_ACTIVATION_CUST) to determine additional data from the SAP ERP system that you need to
activate the imported compensation data but that cannot be imported from the SuccessFactors system (for example,
the effective date to determine when a bonus or salary adjustment is to come into effect).
If you need additional elds for the activation, whose content cannot be imported from SuccessFactors and cannot be
determined in the SAP ERP system, you can also de ne that the eld of your choice is shown on the selection screen of
the report Activation of Employee's Planned Compensation Data (RH_SFI_ACTIVATE_COMP_DATA). Then the user
who calls the report can make the relevant entries.
You can delete entries that the reports RH_SFI_IMPORT_COMP_DATA and RH_SFI_ACTIVATE_COMP_DATA have generated
in database tables of the SAP ERP system. To do so, you use the report Cleanup of Internal Tables After Importing and
Activating Comp. Data (RH_SFI_CLEANUP_COMP_IMP). For example, you can use the report to clean up the tables after
importing incorrect data.
For more information about the report, see Customizing for the integration add-on, under Integration Scenario for
Compensation Data Transfer of Data from SuccessFactors BizX to SAP ERP Cleanup Internal Tables in SAP ERP After Import
and Activation . The report is also located in the user menu for the role SuccessFactors Integration: Compensation Data
Import and Activation (SAP_HR_SFI_COMP_DATA_IMPORT).
Error Handling
You can use an application for monitoring the transfer of data to track and process errors that occurred when extracting or
transferring data.
For more information, see Monitoring the Transfer of Data from SuccessFactors HCM Suite to SAP ERP.
Monitoring the Transfer of Data from SAP

Use
You can use the Web Dynpro application HRSFI_MONITORING_EMPL to monitor the transfer of employee data and
compensation data from SAP ERP to SuccessFactors HCM Suite. The application informs you of which data has been
successfully extracted and transferred, and for which employees the data extraction or data transfer failed. The application
displays all messages of the type error and warning that occurred and supports you with resolving the errors.
Prerequisites
4/26/2019
If you want to use the application HRSFI_MONITORING_EMPL to monitor the extraction of employee data, you need to use the
report Sync Employee Data with SuccessFactors (with Delta and Inactive Logic) (RH_SFI_SYNCHRONIZE_EMPL_DATA) to
extract this data. If you use the report Extraction of Employee Data for SuccessFactors
(RH_SFI_TRIGGER_EMPL_DATA_REPL), the application HRSFI_MONITORING_EMPL does not display any messages for the
extraction of employee data.
Note
The monitoring of the extraction of compensation data does not depend on whether you extract employee data or the
report you use to do so.
Features
Displayed Data
The application for monitoring the data transfer from SAP ERP to SuccessFactors displays data for the following integration
scenarios:
Transfer of employee data
Transfer of compensation data
Modifying the Log and Message Lists
The lists are based on SAP List Viewer (ALV) for Web Dynpro. Therefore, you can use the following standard SAP List Viewer for
Web Dynpro functions:
Sorting the list
Filtering the list
Excel.
Message Types
The message lists contain messages of the type error, warning, and success. The types of error are indicated by relevant icons.
Message Categories
4/26/2019
Back-End Messages
Error messages and warnings that were triggered by the extraction of data in the SAP ERP system are listed here.
Transfer Messages
Error messages and warnings that were triggered by the transfer of data from the SAP ERP system to SuccessFactors
are listed here.
Processed Successfully
The number of employees for whom the extraction and transfer of data was successful is listed here.
See Monitoring the Transfer of Employee Data.
Using the Message List to Transfer Compensation Data
See Monitoring the Transfer of Compensation Data.
Activities
3. Repeat the extraction of data. To do so, proceed as follows:
Wait for the next run of the data extraction report with the same extraction variant. The report automatically
selects the relevant personnel numbers and extracts their data again.
Repeat the extraction of data only for those employees for whom errors occurred.
Note
This option is only available for extracting employee data.
4. If the extraction of data is successful the next time the report is run, the report deletes the relevant messages from this
application. If errors occur again during the extraction of data, this application displays relevant messages with the new
extraction date.
Monitoring the Transfer of Compensation

Data
Use
You can use the Web Dynpro application HRSFI_MONITORING_EMPL to monitor the transfer of compensation data from SAP
ERP to SuccessFactors HCM Suite.
Features
Successfully Processed Data
4/26/2019
The Successfully Processed list provides you with an overview of the number of employees for whom the data has been
extracted and transferred successfully, and when the data was extracted.
Transfer Log
In the Transfer Log list you can display all transferred compensation data.
To do so, rst use the selection criteria to de ne for which employees the data is to be displayed, and choose Transfer Selection.
You can then collapse the screen area with the selection criteria.
Recommendation
If you display a large amount of data, it can take some time to call the transfer log. In this case, we recommend that you use
the eld Maximum Number of Hits to restrict the number of employees for whom the data is to be displayed.
The transfer log contains the following information:
Information on the employees for whom data has been extracted (personnel number from the SAP ERP system, user ID
from SuccessFactors)
Date and time of last data extraction
Current status of the data extraction as stored in the log table HRSFI_D_COMP_EXT
The log table contains all compensation data that the data extraction report extracted during the last run for the
employees concerned.
If errors occurred, the log table contains the previous data extraction status for the relevant employees.
If different data is extracted for an employee in multiple runs of the extraction report, the transfer log displays all data
collectively.
 Example
You run the extraction report to extract eld contents that affect pay increases. You run the report a second time to
extract eld contents that affect long-term incentives. An employee is contained in the selection for both runs.
Therefore, for this employee, the transfer log displays the transferred pay increase data and the transferred long-
term incentive data in the same row.
You can use the Detail pushbutton to display an overview of the data for an employee.
Note
Which data is displayed in the transfer log also depends on whether the user has the authorizations required to display the
data. You use the Business Add-In (BAdI) Determine Program Which Selects Employees for Log Display in Monitor
(HRSFI_B_MONITORING_LOG_PROGRAM) to de ne the authorizations. For the BAdI, see Customizing for the integration
add-on, and choose Basic Settings.
Back-End Messages and Transfer Messages
The lists Back-End Messages and Transfer Messages provide you with an overview of all problems that occurred during the data
transfer.
The following functions are available:
You can check for which employees problems occurred.
4/26/2019
For each message of the type error and warning, the application displays the employee's user ID from the
SuccessFactors system as well as the set of elds that you have used to extract data. For back-end messages, the
application also displays the employee's personnel number from the SAP ERP system.
For back-end messages, you can check when an error last occurred and for how long it has existed.
For messages of the type error and warning, the application displays the time and date on which the error last occurred
and the date on which it rst occurred. This provides you with an overview of employees for whom errors regularly occur
over a longer period of time and enables you to check and correct their speci c data.
More Information
Monitoring the Transfer of Data from SAP ERP to SuccessFactors HCM Suite
Monitoring the Transfer of Data from

Use
You can use the Web Dynpro application HRSFI_MONITORING_COMP to monitor the transfer of compensation data from
SuccessFactors HCM Suite to SAP ERP. The application informs you of the number of employees for whom the data has been
successfully extracted and transferred, and for whom the data extraction or data transfer failed. The application displays all
messages of the type error and warning that occurred and supports you with resolving the errors.
SuccessFactors Integration: Import and Activation of Compensation Data (SAP_HR_SFI_COMP_DATA_IMPORT)
Features
Overview Area
The upper area of the application screen displays an overview of the current data transfer status. For this, the application
displays the following information:
Personnel number, ID of central person, and SuccessFactors user ID of all employees for whom data has been
transferred
ID of the form template used in SuccessFactors for compensation planning
Field set that you have used to import the data
Ad hoc report that you have used to retrieve compensation data in SuccessFactors
Status of the data transfer, eld mapping, test activation, and productive activation of the data
4/26/2019
For each status, the tooltip displays the last person to change the data and when the data was changed.
Message List
Below the overview area, the application displays a list of all messages that occurred during the transfer of data.
Modifying the List
The message list is based on SAP List Viewer (ALV) for Web Dynpro. Therefore, you can use the following standard SAP List
Viewer for Web Dynpro functions:
Sorting the list
Filtering the list
Excel.
Message Types
The message list contains error and warning messages. The types of error are indicated by relevant icons.
Message Categories
Transfer Messages
Error messages and warnings that were triggered by the import of data from SuccessFactors to SAP ERP are listed here.
Mapping Messages
Error messages and warnings that were triggered by the eld mapping in the SAP ERP system are listed here.
Messages on Test Activation
Error messages and warnings that were triggered by a test run of the report Activation of Planned Employee
Compensation Data (RH_SFI_ACTIVATE_COMP_DATA) are listed here.
Messages on Activation
Error messages and warnings that were triggered by a productive run of the report RH_SFI_ACTIVATE_COMP_DATA
are listed here.
4/26/2019
Use of Message List
You can restrict the display to a particular employee. To do so, select the employee in the overview area and lter the
messages. To undo the restriction, remove the selection in the overview area and lter again.
You can check in detail which errors occurred for which employees. For this, the application displays the following
information for each message:
Employee's personnel number
Employee's user ID from SuccessFactors
ID of form template from SuccessFactors
ID of ad hoc report from SuccessFactors
ID of the eld set used for the import
Date and time of the last occurrence of the error
Activities
3. Repeat the data import.
4. If the import is successful the next time the report is run, the report deletes the relevant messages from this application.
If errors occur during the data import again, this application displays relevant messages with the new transfer date.
5. Repeat the activation of data.
6. If the activation is successful the next time the report is run, the report deletes the relevant messages from this
application. If errors occur during the activation of data again, this application displays relevant messages with the new
activation date.
Integration Scenario for Variable Pay Data

Use
You can extract employee history data from SAP ERP and transfer it to SuccessFactors HCM Suite so that it is available for
variable pay planning. When you have completed the variable pay process, you can extract the result from SuccessFactors and
transfer it to SAP ERP so that it can be processed in payroll.
Features
You can use middleware to transfer employee history data from SAP ERP to SuccessFactors and from SuccessFactors to SAP
ERP. For more information, see Integration Using Middleware.
4/26/2019
You can transfer variable pay data in the following directions:
For more information, see Transfer of Variable Pay Data from SAP ERP to SuccessFactors.
For more information, see Transfer of Variable Pay Result from SuccessFactors to SAP ERP.
See Integration Scenario Process for Variable Pay Data.
Integration Scenario Process for Variable

Pay Data
Use
You can transfer variable pay data (employee history data) from SAP ERP HCM to SuccessFactors HCM Suite, and vice versa.
Prerequisites
Please see the following:
Transfer of Variable Pay Data from SAP ERP to SuccessFactors
Transfer of Variable Pay Result from SuccessFactors to SAP ERP
Process
1. In SAP ERP, you run the report Extract Variable Pay Data from SAP ERP to SuccessFactors HCM Suite (report
RH_SFI_SYNCH_VAR_PAY_DATA).
Recommendation
If you also implement the integration scenario for employee data, make the same settings on the selection screen of
report RH_SFI_SYNCH_VAR_PAY_DATA for the SuccessFactors eld USERID that you use to extract employee
data. For example, if you extract the IDs of the central persons of the relevant employees when extracting employee
data for the eld USERID, also use this setting to extract variable pay data.
For more information about the data extraction reports for employee data, see:
Employee Data Run Extraction of Employee Data and Organizational Data
Integration Scenario for Employee Data
2. For the selected employees, the report extracts the employee history data for the SuccessFactors elds of your choice
and logs the current data extraction status in table SuccessFactors: Variable Pay Log Table for Transferred Data (table
HRSFI_D_VARPY_EX).
4/26/2019
3. Using middleware, the report transfers the employee history data to SuccessFactors.
4. In SuccessFactors, you use the data imported from SAP ERP to plan the variable pay for the relevant employees.
5. In SAP ERP, you use transaction SLG1 to evaluate the application logs for object SFSF_INTEGR_BIZX and subobject
VARPAY-EXPORT and check the messages created by the reports.
6. After the variable pay process has been completed in SuccessFactors, you run the report Import Variable Pay Data for
Employee (report RH_SFI_IMPORT_VARPY_DATA) in SAP ERP. In SuccessFactors, the report triggers a job to retrieve
the variable pay result from the ad hoc report domain for payout of the variable pay.
Note
Make sure the ad hoc objects for variable pay are turned on in Provisioning. SuccessFactors Professional Services can
check this for you.
7. The report stores the variable pay data imported from SuccessFactors in table HRSFI_D_VARPY_IM.
8. In SAP ERP, you run the report Activate Variable Pay Data for Employee (report RH_SFI_ACTIVATE_VARPY_DATA).
The report activates the imported variable pay result so that it can be processed in SAP ERP in payroll. If you use the
standard implementation of the following Business Add-In (BAdI), the report stores the data in infotype 0015 (Additional
Payments):
Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for Variable
Pay Data Transfer from SuccessFactors HCM Suite to SAP ERP HCM BAdI: Activation of Variable Pay Data Imported
from SuccessFactors
For information about processing errors that occurred while extracting or transferring data, see Monitoring the Transfer of
Variable Pay Data from SuccessFactors.
Transfer of Variable Pay Data from SAP ERP

to SuccessFactors
Use
You can extract variable pay data (employee history data) from your SAP ERP system and transfer it to SuccessFactors HCM
Suite so that it is available for variable pay planning.
Prerequisites
The employee data exists in SuccessFactors.
To provide the employee data in SuccessFactors, you can, for example, use the integration scenario for employee data in
this integration add-on. In this case, you rst need to schedule the report for extracting employee data before you run
the report for extracting variable pay data. You may need to run the report for extracting employee data twice so that
the relationships between the employees and their managers are created. These relationships need to be known in the
SuccessFactors system before the employees can be assigned to the form templates for variable pay planning.
You have made the necessary settings in Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors
HCM Suite Integration Scenario for Variable Pay Data Transfer from SAP ERP HCM to SuccessFactors HCM Suite .
Features
Data Extraction Report
4/26/2019
To extract the data from the SAP ERP system, you can use report Extract Variable Pay Data from SAP ERP to SuccessFactors
HCM Suite (report RH_SFI_SYNCH_VAR_PAY_DATA). For more information about this report, see Customizing for Integration
Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for Variable Pay Data Transfer from SAP ERP
HCM to SuccessFactors HCM Suite Extract Variable Pay Data from SAP ERP HCM . You can also nd the report in the user
menu for the role SuccessFactors Integration: Variable Pay (role SAP_HR_SFI_VARIABLE_PAY).
Extracted Data
In Customizing, you de ne which variable pay data you want to extract from the SAP ERP system. To do so, you de ne the sets
of SuccessFactors elds to which the data is to be transferred. For each eld, you can map the HCM infotype eld or use an
implementation of Business Add-In (BAdI) de nition BAdI De nition for Extracting Value for Fields (BADI de nition
HRSFI_B_VARPAY_FIELD_EXTRACTOR) to de ne how the data is to be determined in the SAP ERP system. For more
information, see Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario
for Variable Pay Data Transfer from SAP ERP HCM to SuccessFactors HCM Suite BAdI: Extraction of Variable Pay Data .
Employee selection (eligibility processing) is carried out in two steps. The rst step is based on the attribute speci ed on the
selection screen (for example, employees belonging to a personnel area). The second step is as per the (optional) business
rules de ned in the implementation of BAdI De nition for User Eligibility for Variable Pay (BADI de nition
HRSFI_B_VARPAY_ELIGIBILITY). For more information, see Customizing for Integration Add-On for SAP ERP HCM and
SuccessFactors HCM Suite Integration Scenario for Variable Pay Data Transfer from SAP ERP HCM to SuccessFactors HCM
Suite BAdI: Eligibility of Employee for Variable Pay .
You can use report Clean Up Internal Tables After Exporting Variable Pay Data (report RH_SFI_CLEANUP_VAR_PAY_REPL) to
delete the entries generated by report RH_SFI_SYNCH_VAR_PAY_DATA in the database tables of the SAP ERP system. For
example, you can use report RH_SFI_CLEANUP_VAR_PAY_REPL to delete delta information to completely retransfer the
variable pay data to SuccessFactors for the relevant employees. For more information about this report, see Customizing for
Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for Variable Pay Data Transfer
from SAP ERP HCM to SuccessFactors HCM Suite Clean Up Internal Tables in SAP ERP HCM After Export . You can also nd
the report in the user menu for the role SuccessFactors Integration: Variable Pay (role SAP_HR_SFI_VARIABLE_PAY).
Error Handling
Using transaction SLG1, you can evaluate the application logs for object SFSF_INTEGR_BIZX and subobject VARPAY-EXPORT
and check the messages created by the reports.
Transfer of Variable Pay Result from

Use
You can extract the variable pay result from SuccessFactors HCM Suite and transfer it to SAP ERP so that it is available for
payroll.
Prerequisites
You have contacted SuccessFactors Professional Services (or the customer support team provided by SuccessFactors) to make
sure that the APIs for importing variable pay data have been made available in SuccessFactors.
In SuccessFactors, you use suitable form templates for the variable pay program, which provide the data of your choice.
4/26/2019
SuccessFactors Professional Services has turned on variable pay ad-hoc objects in Provisioning.
SuccessFactors Professional Services has provided you with the variable pay payout template ID of the corresponding variable
pay program.
In SuccessFactors, the variable pay program is complete.
In Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite, you have carried out the activities
under Integration Scenario for Variable Pay Data Transfer from SuccessFactors HCM Suite to SAP ERP HCM .
Features
Import Data
To import the variable pay result to SAP ERP, you can use report Import Variable Pay Data for Employee (report
RH_SFI_IMPORT_VARPY_DATA). For more information about this report, see Customizing for Integration Add-On for SAP ERP
HCM and SuccessFactors HCM Suite Integration Scenario for Variable Pay Data Transfer from SuccessFactors HCM Suite to
SAP ERP HCM Import Variable Pay Data to SAP ERP HCM . You can also nd this report in the user menu for the role
SuccessFactors Integration: Variable Pay (role SAP_HR_SFI_VARIABLE_PAY).
Activate Data for Payroll
To activate the data in SAP ERP, you can use report Activate Variable Pay Data for Employee (report
RH_SFI_ACTIVATE_VARPY_DATA). For more information about this report, see Customizing for Integration Add-On for SAP
ERP HCM and SuccessFactors HCM Suite Integration Scenario for Variable Pay Data Transfer from SuccessFactors HCM
Suite to SAP ERP HCM Activate Variable Pay Data for Payroll . You can also nd this report in the user menu for the role
SuccessFactors Integration: Variable Pay (role SAP_HR_SFI_VARIABLE_PAY).
Determine Data to Import and Activate
You determine which variable pay data you want to import from SuccessFactors and activate for payroll in SAP ERP as follows:
You use implementations of the following Business Add-In (BAdI) to de ne how the variable pay result imported from
SuccessFactors is to be processed in payroll in SAP ERP:
Pay Data Transfer from SuccessFactors HCM Suite to SAP ERP HCM BAdI: Activation of Variable Pay Data Imported
from SuccessFactors (BAdI HRSFI_B_VARPY_DATA_ACTIVATION)
You de ne a eld set, which is mapped to the corresponding implementation of BAdI: Activation of Variable Pay Data
Imported from SuccessFactors, and then de ne eld mappings to map the SuccessFactors elds to the SAP ERP elds
of your choice. You do this in Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite
Integration Scenario for Variable Pay Data Transfer from SuccessFactors HCM Suite to SAP ERP HCM Map Fields for
Importing Variable Pay Data . By grouping the eld mappings in a eld set, you can import and activate all required
variable pay data collectively.
 Example
You create a eld mapping comprising all elds that you need for bonus payments.
If you need additional elds for the activation, whose content cannot be imported from SuccessFactors and cannot be
determined in SAP ERP, you can de ne that the eld of your choice is shown on the selection screen of report Activate
Variable Pay Data for Employee (report RH_SFI_ACTIVATE_VARPY_DATA). Then the user who calls the report can
make the relevant entries.
4/26/2019
You can use implementations of the following BAdI to determine additional data from the SAP ERP system that is
needed to activate the imported variable pay data, but cannot be imported from SuccessFactors (for example, the
effective date to determine when a bonus is to come into effect):
Pay Data Transfer from SuccessFactors HCM Suite to SAP ERP HCM BAdl: Customizing Field Mapping (BAdI
HRSFI_B_VARPY_ACTIVATION_CUST)
Clean Up Internal Tables After Data Import and Activation
You can use report Clean Up Internal Tables After Importing and Activating Variable Pay Data (report
RH_SFI_CLEANUP_VAR_IMP) to delete the entries generated by reports RH_SFI_IMPORT_VARPY_DATA and
RH_SFI_ACTIVATE_VARPY_DATA in database tables in the SAP ERP system. For example, you can use the report to clean up
the tables after importing incorrect data. For more information about this report, see Customizing for Integration Add-On for
SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for Variable Pay Data Transfer from SuccessFactors
HCM Suite to SAP ERP HCM Clean Up Internal Tables in SAP ERP HCM After Import and Activation . You can also nd this
report in the user menu for the role SuccessFactors Integration: Variable Pay (role SAP_HR_SFI_VARIABLE_PAY).
Error Handling
You can use a Web Dynpro application for monitoring the transfer of data to track and process errors that occurred while
extracting or transferring data. For more information, see Monitoring the Transfer of Variable Pay Data from SuccessFactors.
Monitoring the Transfer of Variable Pay Data

from SuccessFactors
Use
You can use the Web Dynpro application HRSFI_MONITORING_VARPY to monitor the transfer of variable pay data from
SuccessFactors HCM Suite to SAP ERP. The application informs you which data was successfully transferred, mapped, tested, or
activated, and for which employees the data transfer failed. The application displays all error and warning messages and
supports you in resolving the errors.
You can nd the application in the menu of role SuccessFactors Integration: Variable Pay (role SAP_HR_SFI_VARIABLE_PAY).
You can use the role to enable users to access the application in SAP NetWeaver Business Client or in SAP NetWeaver Portal.
Features
Status Overview and Detailed Message List
The application provides a status overview and detailed message list. The status overview contains the following information:
Information on the employees for whom variable pay data was imported and/or activated (personnel number from SAP
ERP, user ID from SuccessFactors)
Variable pay data template ID and import source from SuccessFactors
Mapping eld set ID
Current status of data import and activation as stored in the following log tables:
4/26/2019
Status log table HRSFI_D_VARPY_ST
This table stores the status of import and/or activation.
Error log table HRSFI_D_VARPY_EX
This table contains all messages on each process step.
The detailed message list contains the following information (which can be ltered by employee):
Information on the employees for whom variable pay data has been imported and/or activated (personnel number from
SAP ERP, user ID from SuccessFactors)
Variable pay data template ID and import source from SuccessFactors
Message details (message type and text)
Status
Activities
1. Correct any errors.
2. Set the status Solved for the relevant message in this application.
3. Repeat the data import and activation.

Variable Pay to SAP ERP
In Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite, you de ne which variable pay data
(employee history data) you want to export from SAP ERP HCM and map to elds in SuccessFactors HCM Suite. For more
information, see Transfer of Variable Pay Data from SAP ERP to SuccessFactors.
The following table shows which SAP ERP elds are used as standard to transfer variable pay data to SuccessFactors. These
elds are assigned to eld set SAP_DEMO_VAR_PAY.
Field Content SuccessFactors SAP ERP Field Comments

Field ID
Amount used basis None Field is required.

as basis for
variable pay This eld is as calculated in Business Add-In (BAdI) implementation
calculation HRSFI_VARPAY_BASIS_IT_IMPL or
HRSFI_VARPAY_BASIS_PAYROL_IMPL. (You have to activate one of the
implementations or create your own implementation.)
Department of department Field

employee Organizational
Unit (ORGEH) in
Infotype
Organization
Management
(0001)
4/26/2019
Field Content SuccessFactors SAP ERP Field Comments

Field ID
Division of division Field Company

employee Code (BUKRS)
in Infotype
Organizational
Management
(0001)
End date of endDate None This eld is automatically populated by the system for elds that are
validity of mapped to SAP ERP HCM tables.
employee
history data For elds that are mapped to a BAdI implementation, the date is taken from
record the BAdI output.
User ID id None Populated by the system based on the selection made in the extraction
report.
Job title jobTitle Field Job

(STELL) in
Infotype
Organizational
Management
(0001)
Last modi ed lastModi ed None The eld content is not transmitted by SAP ERP HCM. It is set automatically
date by the SuccessFactors system.
Currency code localCurrencyCode Field Currency

for amount Key for Annual
elds Salary (ANCUR)
in Infotype
Basic Pay
(0008)
Location of location Field Personnel

employee Area (WERKS)
in Infotype
Organizational
Management
(0001)
Annual salary salary Field Annual

of employee Salary (ANSAL)
in Infotype
Basic Pay
(0008)
Start date of startDate None This eld is automatically populated by the system for elds that are
validity of mapped to SAP ERP HCM tables.
employee
history data For elds that are mapped to a BAdI implementation, the date is taken from
record the BAdI output.
Variable pay varPayProgramName Field is required.

program name
to which the This eld is as calculated in BAdI implementation
data record HRSFI_VARPAY_PRG_FLD_EXT_IMPL. It picks the program details as
belongs con gured by you in Customizing for Integration Add-On for SAP ERP HCM
and SuccessFactors HCM Suite Integration Scenario for Variable
Pay Basic Settings Maintain Variable Pay Program Information .
4/26/2019
Mapping of SAP ERP HCM Fields to

SuccessFactors for Variable Pay
In Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for Variable
Pay Data Transfer from SuccessFactors HCM Suite to SAP ERP HCM , you de ne which variable pay result you want to import
from SuccessFactors HCM Suite to SAP ERP HCM and activate. For more information, see Transfer of Variable Pay Result from
SuccessFactors to SAP ERP.
To map SAP ERP HCM elds to SuccessFactors, you create a eld set and then create eld mappings for this eld set. The
sample eld set SAP_DEMO_VARPAY_IMPORT consists of the following:
Activation type
Standard Business Add-In (BAdI) implementation HRSFI_VARPY_STD_ACTIVATION with lter SAP_VARPY_STD

SFSF
SuccessFactors object ID
ADHOC_VARPAY_BONUS_PAYOUT with variable pay ad-hoc report domain as import source
Field mapping de nitions
The following table shows which SAP ERP elds are used as standard to transfer variable pay data from SuccessFactors.
These elds are assigned to eld set SAP_DEMO_VARPAY_IMPORT.
Internal Field ID Field Type SuccessFactors Comments

Field ID
BONUS_AMOUNT Import from To be lled by This eld is required. It maps to Amount (BETRG) in infotype
SuccessFactors customer Additional Payments (0015).
CURRENCY Import from To be lled by This eld is required. It maps to Currency (WAERS) in infotype
SuccessFactors customer Additional Payments (0015).
EFFECTIVE_DATE Enter during None This eld is required. It maps to Date of Origin (BEGDA) in infotype
activation Additional Payments (0015).
REASON Determine via None This eld is optional. It maps to Reason for Change (PREAS) in
BAdI infotype Additional Payments (0015). For elds that are mapped to a
BAdI implementation, the value is taken from the BAdI output.
WAGETYPE Determine via None This eld is required. It maps to Wage Type (LGART) in infotype
BAdI Additional Payments (0015). For elds that are mapped to a BAdI
implementation, the value is taken from the BAdI output.
Integration Scenario for Evaluation Data

Use
You can download data from the SAP ERP system as a text le (TXT le) so that it can be uploaded to SuccessFactors Workforce
Analytics, where it can be used for evaluations.
Prerequisites
4/26/2019
In Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for Evaluation
Data , you have carried out the activity Adapt Reports for Data Provisioning for Evaluations.
Features
You can use the le download to extract analytical data from the SAP ERP system and format it such that it is available for
SuccessFactors Workforce Analytics. For more information, see Integration Using File Download.
Extracted Data
You can use the following reports to extract evaluation data:
Data Provisioning –Organizational Objects / SuccessFactors Analytics (RH_SFI_HRP1000)
Data Provisioning – Relationships / SuccessFactors Analytics (RH_SFI_HRP1001)
Data Provisioning – Personnel Actions / SuccessFactors Analytics (RH_SFI_PA0000)
Data Provisioning – Org. Assignments / SuccessFactors Analytics (RH_SFI_PA0001)
Data Provisioning – Personal Data / SuccessFactors Analytics (RH_SFI_PA0002)
Data Provisioning – Planned Working Time / SuccessFactors Analytics (RH_SFI_PA0007)
Data Provisioning – Basic Pay / SuccessFactors Analytics (RH_SFI_PA0008)
Data Provisioning – Contract Elements / SuccessFactors Analytics (RH_SFI_PA0016)
Data Provisioning – Appraisals / SuccessFactors Analytics (RH_SFI_PA0025)
Data Provisioning – Date Speci cations / SuccessFactors Analytics (RH_SFI_PA0041)
Data Provisioning – Personnel Actions / SuccessFactors Analytics (RH_SFI_PA0077)
Data Provisioning – Additional Actions / SuccessFactors Analytics (RH_SFI_PA0302)
Data Provisioning – Company Code / SuccessFactors Analytics (RH_SFI_T001)
Data Provisioning – Personnel Area / Subarea / SuccessFactors Analytics (RH_SFI_T001P)
Data Provisioning – Personnel Areas / SuccessFactors Analytics (RH_SFI_T500P)
Data Provisioning – Employee Group / SuccessFactors Analytics (RH_SFI_T501T)
Data Provisioning – Employee Subgroup / SuccessFactors Analytics (RH_SFI_T503T)
Data Provisioning – Ethnic Origin / SuccessFactors Analytics (RH_SFI_T505S)
Data Provisioning – Pay Scale Type / SuccessFactors Analytics (RH_SFI_T510A)
Data Provisioning – Pay Scale Area / SuccessFactors Analytics (RH_SFI_T510G)
Data Provisioning – Wage Type / SuccessFactors Analytics (RH_SFI_T512T)
Data Provisioning – Appraisal Criterion / SuccessFactors Analytics (RH_SFI_T513F)
Data Provisioning – Organizational Key / SuccessFactors Analytics (RH_SFI_T527O)
Data Provisioning – Actions / SuccessFactors Analytics (RH_SFI_T529T)
4/26/2019
Data Provisioning – Status / SuccessFactors Analytics (RH_SFI_T529U)
Data Provisioning – Action and Action Reason / SuccessFactors Analytics (RH_SFI_T530T)
Data Provisioning – Work Contract / SuccessFactors Analytics (RH_SFI_T542T)
Data Provisioning – Corporation / SuccessFactors Analytics (RH_SFI_T545T)
Data Provisioning – Date Types / SuccessFactors Analytics (RH_SFI_T548T)
Data Provisioning – Payroll Area / SuccessFactors Analytics (RH_SFI_T549T)
Data Provisioning – Absence/Attendance / SuccessFactors Analytics (RH_SFI_T554T)
Data Provisioning – Jobs (PA) / SuccessFactors Analytics (RH_SFI_T5U13)
Data Provisioning – EEO Occup. Categories / SuccessFactors Analytics (RH_SFI_T5UEE)
Data Provisioning – Public Holiday / SuccessFactors Analytics (RH_SFI_THOC)
Data Provisioning – Public Holiday Text / SuccessFactors Analytics (RH_SFI_THOL)
For more information about the extracted elds, see the report documentation in the SAP ERP system.
Caution
You cannot use these reports as provided with the standard SAP system. They are generic reports that you need to
adapt to suit your customer-speci c requirements. Contact your SuccessFactors consultant (Professional Services) if
you want to use one of the reports.
Integration Scenario for Quali cation Data

Use
You can transfer quali cation data (catalog and also history for employees) from SAP ERP to SuccessFactors HCM Suite. This is
a one-time activity, and once this activity is complete, it is considered that SuccessFactors becomes the system of record for
the transferred data.
Changes to data in SuccessFactors (and learning management system) are then replicated back to SAP ERP quali cations on a
recurring basis. The data in SAP ERP HCM is considered read-only.
Prerequisites
To use this integration scenario, the employee data in SuccessFactors must already be created using the integration scenario
for employee data.
Features
You can use middleware to transfer quali cation data from SAP ERP to SuccessFactors and from SuccessFactors to SAP ERP.
In SAP ERP HCM, quali cations can be implemented either in the Personnel Administration (PA) or Personnel Development
(PD) module. The setup of the system is determined by the following integration switch for quali cations: PLOGI QUAL (1 = PD
4/26/2019
QUAL, 0 = PA QUAL). The standard integration considers this switch and enables it to work for both implementations. The
switch designates which objects are updated in SAP ERP HCM.
You can transfer quali cation data in the following directions:
SAP ERP HCM → SuccessFactors HCM Suite
Transfer of Quali cation Catalog Data from SAP ERP to SuccessFactors Competency Library
Transfer of Employee Skill Data from SAP ERP to SuccessFactors Competency Feedback
SuccessFactors HCM Suite → SAP ERP HCM
Transfer of Changed Competency Library Data from SuccessFactors to SAP ERP
Transfer of Changed Competency Rating Data from SuccessFactors to SAP ERP
Transfer of Changed Curriculum Data from SuccessFactors to SAP ERP
Transfer of Changed Curriculum Status Data from SuccessFactors to SAP ERP
See Integration Scenario Process for Quali cation Data.
Integration Scenario Process for

Quali cation Data
Use
In the talent hybrid deployment model, quali cation data is in the SuccessFactors system (not in SAP ERP HCM). Because
several business processes depend on quali cation data in the SAP ERP HCM system (for example, multiresource planning),
quali cation data in the SAP ERP HCM system must be kept up-to-date to make sure that business processes continue to work.
The standard integration process for quali cation data helps you to achieve this.
The following gure provides an overview of the integration scenario process for quali cation data.
4/26/2019
SuccessFactors HCM Suite has multiple entities that support storing quali cation related data. The competency object is used
by various modules in SuccessFactors. The curricula object is used in the SuccessFactors learning management system (LMS).
Companies use different objects based on their requirements (for example, legal compliance related quali cations are
managed in the LMS).
Prerequisites
To use the integration scenario for quali cation data, the employee data in SuccessFactors must already be created using the
integration scenario for employee data. The standard employee integration is assumed while resolving the relationship
between SuccessFactors user and SAP ERP HCM employee.
Process
1. One-time upload of quali cation catalog from SAP ERP HCM to the SuccessFactors competency library.
This is helpful if you want to migrate the catalog only once. Hierarchy reorganization is allowed and will not break the
integration. After the one-time transfer, SuccessFactors HCM Suite is the system of record. For more information, see
Transfer of Quali cation Catalog Data from SAP ERP to SuccessFactors Competency Library.
2. One-time upload of employee skills from SAP ERP HCM to the SuccessFactors competency feedback object.
This is helpful if you want to copy the employee skills history to SuccessFactors. After the one-time transfer,
SuccessFactors HCM Suite is the system of record. For more information, see Transfer of Employee Skill Data from SAP
ERP to SuccessFactors Competency Feedback.
4/26/2019
3. Recurring replication of changed competency catalog from SuccessFactors to SAP ERP HCM.
For more information, see Transfer of Changed Competency Library Data from SuccessFactors to SAP ERP.
4. Recurring replication of changed employee competency from SuccessFactors to SAP ERP HCM.
For more information, see Transfer of Changed Competency Rating Data from SuccessFactors to SAP ERP.
5. Recurring replication of changed curriculum catalog from the SuccessFactors LMS to SAP ERP HCM.
For more information, see Transfer of Changed Curriculum Data from SuccessFactors to SAP ERP.
6. Recurring replication of changed employee curriculum status from the SuccessFactors LMS to SAP ERP HCM.
For more information, see Transfer of Changed Curriculum Status Data from SuccessFactors to SAP ERP.
Note
A one-time upload of quali cation data to curriculum is not available and is not supported. Compared with a quali cations
object, curriculum objects are more complex and need more information for creation.
Transfer of Quali cation Catalog Data from

SAP ERP
Use
You can extract quali cation catalog data from SAP ERP in a at le format and upload it to SuccessFactors HCM Suite using
the SuccessFactors import functionality in the provisioning/admin tools.
Prerequisites
If yours is a hybrid deployment, the quali cation catalog is already set up in your SAP ERP HCM system. The quali cation
catalog is maintained in your SAP ERP system either in PA or PD tables, depending on the quali cation switch (PLOGI QUALI).
You migrate the same quali cation catalog to SuccessFactors.
Features
Data Export
For extracting the quali cation catalog from the SAP ERP system, you can use the report Extraction of Quali cation Catalog
(transaction HRSFI_QUAL_DATA_EXPT). For information about this report, see Customizing for Integration Add-On for SAP
ERP HCM and SuccessFactors HCM Suite Integration Scenario for Quali cation Data Transfer of Quali cation Catalog from
SAP ERP to SuccessFactors HCM Suite Run Extraction of Quali cation Catalog . The report is also located in the user menu of
the role SuccessFactors Integration Quali cation Replication (SAP_HR_SFI_QUALIFICATION).
Exported Fields
The elds exported depend on the quali cation switch (PLOGI QUALI) in the SAP ERP system. For more information, see
Mapping of SAP ERP Quali cation Catalog Fields to SuccessFactors Competency.
Updating the Mapping Table in SAP ERP System
4/26/2019
This extraction utility report updates the mapping table (T777SFI_GUID_MAP) in the SAP ERP system. OBJID of quali cation
is mapped to the GUID eld of the table and SOURCE eld is set to COMPETENCY.
Recommendation
If you are using the report Extraction of Quali cation Catalog to extract quali cations from the SAP ERP system, we
recommend setting the SOURCE eld to the value COMPETENCY when setting up the job for replication of competency data
from SuccessFactors to the SAP ERP system. If you set some other value, the quali cations exported earlier will be created
again in the SAP ERP system with a different source.
Further Processing of Imported Data
You can check the data imported into SuccessFactors and, if required, reorganize the hierarchy.
Mapping of SAP ERP Quali cation Catalog

Fields
The eld mapping of quali cation catalog in SAP ERP to competency in SuccessFactors HCM suite depends on the quali cation
switch (PLOGI QUAL).
Field Mapping If PA Based Quali cation Is Active
SuccessFactors Competency Field SAP ERP Object SAP ERP Field Special Features of
Mapping
Category Input eld in transaction No equivalent eld in PA

HRSFI_QUAL_DATA_EXPT based quali cation. When
extracting the
quali cation catalog from
SAP ERP, transaction
HRSFI_QUAL_DATA_EXPT
requires you to specify
the competency category;
this value is used to set
the Competency
Category eld in the CSV
le.
Competency Name Quali cation Name Table Quali cation

Names (T574B), eld
Quali cation Text
(QTEXT)
Competency Description No equivalent eld in SAP

ERP system
GUID Quali cation ID Table Global Object ID for GUID is mapped to eld
HR Objects T574A-QUALI in mapping
(T777SFI_GUID_MAP), table, and generated
eld GUID for GUID is exported to
SuccessFactors (GUID) SuccessFactors.
4/26/2019
Mapping
Locale Language Indirectly with Table The SAP ERP languages

Quali cation Names are mapped to the
(T574B), eld Language language labels used in
Key (LANGU) SuccessFactors (for
example, DE to de_DE).
Field Mapping If PD Based Quali cation Is Active
SuccessFactors Competency Field SAP ERP Object SAP ERP Field Special
Features of
Mapping
Category Quali cation Group Infotype Object OTYPE = ʻQK’

(1000), eld Object
Name (STEXT)
Competency Name Quali cation Name Infotype Object OTYPE= ʻQ’

(1000), eld Object
Name (STEXT)
Competency Description Description Infotype Verbal

Description (1002)
GUID Quali cation ID Table Global Object ID GUID is

for HR Objects mapped to
(T777SFI_GUID_MAP), Infotype Object
eld GUID for (1000), eld
SuccessFactors Object ID
(GUID) (OBJID) in
mapping table,
and generated
GUID is
exported to
SuccessFactors.
Locale Language Indirectly Infotype The SAP ERP

Object (1000), eld languages are
Language Key mapped to the
(LANGU) language labels
used in
SuccessFactors
(for example,
DE to de_DE).
Transfer of Employee Skill Data from SAP

Use
You can transfer employee skill data from SAP ERP to SuccessFactors HCM Suite as an employee competency. This is a one-
time activity from the SAP ERP system. The data will be available as live pro le data in SuccessFactors. Only quali cation data
valid as of today is transferred.
4/26/2019
Note
This functionality is currently supported only with SAP HANA Cloud Integration as the middleware. For more information, see
SAP Note 2089695 Release Restrictions for Integration Add-On 3.0 SP02 for SAP ERP HCM and SuccessFactors HCM
Suite.
Prerequisites
You have transferred the quali cation catalog from SAP ERP to SuccessFactors. If you have a hybrid deployment, employee
quali cation data (also known as skills data) is already stored in your SAP ERP HCM system. When you migrate to
SuccessFactors, you are likely to want this data in SuccessFactors so that the employee history is visible in SuccessFactors.
You have made the settings in Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite
Integration Scenario for Quali cation Data Basic Settings BAdI: Determine SAP ERP Personnel Numbers and SuccessFactors
User IDs .
Features
See Setting Up and Triggering the Integration Process for Transfer of Data.
Exported Fields
The elds exported depend on the quali cation switch (PLOGI QUALI) in the SAP ERP system. For more information, see
Mapping of SAP ERP Employee Skill Fields to SuccessFactors Competency Feedback.
OData Service
To transfer data from SAP ERP, the entity set QualificationRatingEntitySet is used from the OData service
HRSFI_QUALIFICATION_SRV. To get employee quali cation data, you must pass the mandatory eld parameter
SFSF_USERID. For more information, see the OData API documentation.
SuccessFactors User ID Determination
The settings in the following BadI determine the SuccessFactors user ID for the personnel number:
Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration Scenario for Quali cation
Data Basic Settings BAdI: Determine SAP ERP Personnel Numbers and SuccessFactors User IDs
Note
The BAdI implementation HRSFI_USERID_TO_PERNR uses method PROVIDE_PERNR to determine the personnel number
from the data transferred from SuccessFactors. To do so, it checks whether the table SuccessFactors: Log Table for Delta
Handling (HRSFI_D_EXTR_LOG) already contains a personnel number for the transferred data record. This is the case if
employee data has already been transferred from SAP ERP HCM to SuccessFactors for the employee concerned.
Mapping of SAP ERP Employee Skill Fields to

SuccessFactors
4/26/2019
Field Mapping of SAP PA-Based Quali cation to SuccessFactors

CompetencyRating Entity
SuccessFactors CompetencyRating SAP ERP Object SAP ERP Field Special Features of
Entity Field Mapping
GUID Quali cation ID Table Global Object ID Quali cation ID on

for HR Objects SAP ERP side is
(T777SFI_GUID_MAP), converted to GUID
eld GUID for and stored in table
SuccessFactors T777SFI_GUID_MAP
(GUID)
USERID Employee Number Central person (object

type CP)
External person ID
from infotype Person
ID (0709)
validFrom Not mapped to any

SAP ERP eld
validTo Not mapped to any

SAP ERP eld
scaleMax Pro ciency of a Quali cation/Requirement Table T778Q, eld

CHARA
scaleMin Pro ciency of a Quali cation/Requirement Table T778Q, eld

CHARA
Rating Pro ciency Infotype Quali cation

0024, eld AUSPR
Source Not mapped to any Constant value: 2

SAP ERP eld (live pro le) for
fetching data from
SuccessFactors
Module Not mapped to any Constant value: 21

SAP ERP eld (API) for fetching
data
Type Not mapped to any Constant value: 1

SAP ERP eld (competency) for
fetching data from
SuccessFactors
Start Date Infotype Quali cation Default set to

(0024), eld BEGDA 01.01.1900;
con gurable in
middleware
End Date Infotype Quali cation Default set to

(0024), eld ENDDA 31.12.9999;
con gurable in
middleware
Field Mapping of SAP PD-Based Quali cation to SuccessFactors

CompetencyRating Entity
4/26/2019
SuccessFactors CompetencyRating Entity SAP ERP Object SAP ERP Field Special Features of
Field Mapping
GUID Quali cation ID Table Global Object ID Quali cation ID on

for HR Objects SAP ERP side is
(T777SFI_GUID_MAP), converted to GUID
eld GUID for and stored in table
SuccessFactors T777SFI_GUID_MAP
(GUID)
USERID Employee Number Central person (object

type CP)
External person ID
from infotype Person
ID (0709)
validFrom Not mapped to any

SAP ERP eld
validTo Not mapped to any

SAP ERP eld
scaleMax Pro ciency ID PD-based

Quali cation: Table
T77SP, eld RATING
scaleMin Pro ciency ID PD-based

Quali cation: Table
T77SP, eld RATING
Rating Pro ciency PD-based

Quali cation: Table
HRPAD31, eld
CHARA
Source Not mapped to any Constant value: 2

SAP ERP eld (live pro le) for
fetching data from
SuccessFactors
Module Not mapped to any Constant value: 21

SAP ERP eld (API) for fetching
data
Type Not mapped to any Constant value: 1

SAP ERP eld (competency) for
fetching data from
SuccessFactors
Start Date Infotype Object Default set to

(1000), eld Object ID 01.01.1900;
(BEGDA) con gurable in
middleware
End Date Infotype Object Default set to

(1000), eld Object ID 31.12.9999;
(ENDDA) con gurable in
middleware
4/26/2019
Setting Up and Triggering the Integration

Process
Use
The SAP ERP systems expose quali cation data in OData service HRSFI_QUALIFICATION_SRV. The entity type
Quali cationRating in OData is used to get data from the SAP ERP system for speci ed users. In SuccessFactors HCM suite, the
SF OData CompetencyRating entity is used to insert competencies in the SuccessFactors system. Middleware maps these two
different entities.
Procedure
1. Activate OData HRSFI_QUALIFICATION_SRV in the gateway system.
For more information, see Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite
Integration Scenario for Quali cation Data Basic Settings Gateway Con guration .
2. Discover the packages for quali cation data integration from the SAP HANA Cloud catalog. Once imported, con gure
them as per your requirements.
For more information, see the operations guide in SAP Library for SAP HANA Cloud Integration on SAP Help Portal at
http://help.sap.com/cloudintegration .
For error handling, use the monitoring tools provided by SAP HANA Cloud Integration/SAP Gateway. Regularly check the errors
that occurred during execution of the integration process and resolve them in the respective systems. After the error is
corrected, the next run of the integration process will replicate the changes.
Transfer of Changed Competency Library

Data from SuccessFactors to SAP ERP
Use
You set up a recurring update of the SAP ERP HCM quali cations catalog so that it is updated with changes in the
SuccessFactors competency library.
Prerequisites
You have asked SuccessFactors Professional Services or Customer Support to set up a recurring export of the selected
competency library to an FTP location.
You have con gured the standard integration package to read the FTP location for the competency library data and to update
SAP ERP HCM. For information about setting up the SAP HANA Cloud Integration content, see Setting Up and Triggering the
Integration Process for Transfer of Data.
Features
General Features
4/26/2019
The standard integration reads the competency library data and rst nds if the competency already exists in the SAP ERP
HCM system as a quali cation. If it does not exist, a new quali cation is created. If it does already exist, the object is updated
with the new information.
The integration considers the quali cation switch (PLOGI QUALI) and updates the relevant quali cation objects appropriately.
When creating new objects in the SAP system, the system stores the relationship of the new object and the related GUID of the
competency from the SuccessFactors system. This information is queried and used for updates.
Special Processing If PD Quali cation Is Active
If a new quali cation is created, it must be attached to a quali cation group. The parent quali cation group is determined based
on the competency library name.
When creating a new quali cation group, a rating scale must be assigned. However, this information is not supplied from the
SuccessFactors system. A default rating scale must be decided for the new quali cation groups and must be con gured in SAP
HANA Cloud Integration. This con guration is used by the system to set the rating scale for the new quali cation group.
Exported Fields
Depending on the quali cation switch (PLOGI QUALI) in the SAP ERP HCM system, the appropriate objects are updated. For
more information, see Mapping of SuccessFactors Competency Library to SAP ERP Quali cation Catalog.
Mapping of SuccessFactors Competency

Library to SAP ERP
The eld mapping of competency in SuccessFactors HCM Suite to quali cation catalog in SAP ERP depends on the quali cation
switch (PLOGI QUAL).
Field Mapping If PA-Based Quali cation Is Active
SuccessFactors Competency Field SAP ERP Object SAP ERP Special Features of
Field Mapping
Competency Library Ignored No hierarchies are

possible in the PA
version of
quali cation so this
information is ignored
Competency Name Quali cation Name T574B-

QTEXT
Competency Description Ignored No equivalent eld in

the SAP ERP system
GUID Quali cation ID T574A- Indirectly mapped via

QUALI the table Global
Object ID for HR
Objects
(T777SFI_GUID_MAP)
4/26/2019
SuccessFactors Competency Field SAP ERP Object SAP ERP Special Features of
Field Mapping
Locale Language Indirectly The SAP ERP

with Table languages are
Quali cation mapped to the
Names language labels used
(T574B), in SuccessFactors
eld (for example, DE to
Language de_DE)
Key (
LANGU)
Field Mapping If PD-Based Quali cation Is Active
Mapping
Competency Library Quali cation Group Infotype Object (1000), eld Indirectly mapped via
Object Name (STEXT) with OTYPE the table Global
= ʻQK’ Object ID for HR
Objects
(T777SFI_GUID_MAP)
Competency Name Quali cation Name Infotype Object (1000), eld Maximum of 40
Object Name (STEXT) with OTYPE characters are
= ʻQ’ considered.
Competency Name
can be longer.
Competency Description Quali cation Description Infotype Verbal Description (1002)
GUID Quali cation ID Infotype Object (1000), eld Indirectly mapped via
Object ID (OBJID) the table Global
Object ID for HR
Objects
(T777SFI_GUID_MAP)
Locale Language Infotype Object (1000), eld The SAP ERP

Language Key (LANGU) languages are
mapped to the
language labels used
in SuccessFactors
(for example, DE to
de_DE)
Defaulted to 01.01.1800 Begin Date Infotype Object (1000), eld Con gurable in SAP
BEGDA HANA Cloud
Integration
Defaulted to 31.12.9999 End Date Infotype Object (1000), eld Con gurable in SAP
ENDDA HANA Cloud
Integration

Process
4/26/2019
You need an SAP HANA Cloud Integration expert to set up and con gure the packaged integration in SAP HANA Cloud
Integration. For assistance, please contact your SAP Customer Services team or SuccessFactors Professional Services.
Following are some of the con gurations that need to be done in SAP HANA Cloud Integration:
End points for API calls
Recurrence of the integration process
Default value for rating scale for creating a quali cation group
Mapping and defaulting
The technical user used in the integration process must have the required authorization to access the APIs.
For information about authorizations in SAP ERP HCM, see Customizing for Integration Add-On for SAP ERP HCM and
SuccessFactors HCM Suite Integration Scenario for Quali cation Data Basic Settings De ne Authorizations .
For information about authorizations in SuccessFactors, see SAP Library for SuccessFactors HCM Suite at
http://help.sap.com/cloud4hr HCM Suite OData API Reference Platform Platform Core CompetencyRating .
Transfer of Changed Competency Rating

Data from SuccessFactors
Use
You set up a recurring update of the SAP ERP HCM employee master data so that it is updated with changes in the
SuccessFactors employee rating for a competency.
Prerequisites
You have asked SuccessFactors Professional Services or Customer Support to set up a recurring execution of the standard
integration package that reads the rating data from the competency rating object and updates SAP ERP HCM. For information
about setting up the SAP HANA Cloud Integration content, see Setting Up and Triggering the Integration Process for Transfer of
Data.
You are using the standard employee data integration for creating users in SuccessFactors.
Features
General Features
The standard integration reads the competency rating data for users and updates the SAP ERP HCM master data for
employee.
Selection of Valid Rating
The competency feedback object contains ratings from various sources. Some sources also store intermediate states of rating.
SAP ERP HCM quali cations accept only one rating. For example, you may want to transfer only the nalized ratings made by
the manager. In this case, you must lter with source as Performance, rater category as Manager, and status as Completed
(see example below).
4/26/2019
 Example
This lter needs to be con gured in SAP HANA Cloud Integration.
Competency Source Rater Category Rating Status
ABAP Performance Manager 4.0 Completed
ABAP Learning 3.0
ABAP 360 Degree Peer 4.5 New
→ Conversion (to be con gured in SAP HANA Cloud Integration) →
Competency Rating
ABAP 4.0
Value Mapping the Rating Scale
SuccessFactors and SAP can have different rating scales for a given competency/quali cation. This needs to be considered
when writing ratings for employee. The standard SAP integration takes account of differences in rating scales and converts
them before saving the rating to employee skills (value mapping).
For special cases, you may want a custom value mapping logic. A BAdI is available for this purpose. For more information, see
Data Transfer of Quali cation Rating from SuccessFactors HCM Suite to SAP ERP BAdI: Con gure Value Mapping for
Quali cation Rating .
Exported Fields
more information, see Mapping of SuccessFactors Competency Rating to SAP ERP Employee Skills.
Mapping of SuccessFactors Competency

Rating to SAP ERP
The eld mapping of competency rating in SuccessFactors HCM Suite to employee skills in SAP ERP depends on the
quali cation switch (PLOGI QUAL).
SAP ERP HCM Employee Number Determination

The SuccessFactors user ID for the SAP ERP personnel number is determined by the settings in Customizing for Integration
Add-On for SAP ERP HCM and SuccessFactors HCM Suite under Integration Scenario for Quali cation Data Basic
Settings BAdI: Determine SAP ERP Personnel Numbers and SuccessFactors User IDs .
BAdI implementation HRSFI_USERID_TO_PERNR uses method PROVIDE_PERNR to determine the personnel number from the
data transferred from SuccessFactors. It checks the table SuccessFactors: Log Table for Delta Handling (HRSFI_D_EXTR_LOG)
to get the personnel number that is related to USERID.
4/26/2019
SuccessFactors SAP ERP SAP ERP Field Special Features of Mapping

Competency Field Object
USERID Employee Central person (object type CP)

Number
External person ID from infotype
Person ID (0709)
GUID Quali cation Infotype 0024, eld QUALI Indirectly mapped via the table Global Object ID for HR
Key Objects (T777SFI_GUID_MAP)
Competency Rating Pro ciency Infotype 0024, eld AUSPR
Begin Date Infotype 0024, eld BEGDA Default set to 01.01.1900; con gurable in SAP HANA Cloud
Integration
End Date Infotype 0024, eld ENDDA Default set to 31.12.9999; con gurable in SAP HANA Cloud
Integration

Competency Field Object

Number
External person ID from infotype Person
ID (0709)
GUID Quali cation Infotype Object (1000), eld Object Indirectly mapped via the table Global Object ID for
ID Name (STEXT) with OTYPE = ʻQ’ HR Objects (T777SFI_GUID_MAP)
Competency Rating Pro ciency Table HRPAD31, eld CHARA
Start Date Infotype Object (1000), eld Object ID Default set to 01.01.1900; con gurable in SAP HANA
(BEGDA) Cloud Integration
End Date Infotype Object (1000), eld Object ID Default set to 31.12.9999; con gurable in SAP HANA
(ENDDA) Cloud Integration

Process
4/26/2019
Transfer of Changed Curriculum Data from

SuccessFactors
Use
You set up a recurring update of the SAP ERP HCM quali cations catalog so that it is updated with changes in the
SuccessFactors learning management system (LMS) curriculum data.
Prerequisites
integration package that reads data from the curriculum object and updates SAP ERP HCM. For information about setting up
the SAP HANA Cloud Integration content, see Setting Up and Triggering the Integration Process for Transfer of Data.
Features
General Features
The standard integration reads the curriculum data (only active curricula are considered) and rst nds if the curriculum
already exists in the SAP ERP HCM system as a quali cation. If it does not exist, a new quali cation is created. If it does already
exist, the quali cation is updated with the new information.
When creating new objects in the SAP system, the system stores the relationship of the new object and the related GUID of the
curriculum from the SuccessFactors system. This information is queried and used for updates.
Special Processing If PD Quali cation Is Active
If a new quali cation is created, it must be attached to a quali cation group. The parent quali cation group is determined based
on the curriculum type. If the curriculum type is not supplied, the quali cation is attached to a default parent (to be con gured
in SAP HANA Cloud Integration).
When creating a new quali cation group, a rating scale must be assigned. However, this information is not supplied from the
SuccessFactors system. A default rating scale must be decided for the new quali cation groups and must be con gured in SAP
HANA Cloud Integration. This con guration is used by the system to set the rating scale for the new quali cation group.
Exported Fields
more information, see Mapping of SuccessFactors Curriculum Catalog to SAP ERP Quali cation Catalog.
Mapping of SuccessFactors Curriculum

Catalog to SAP ERP
4/26/2019
The eld mapping of the curriculum catalog in SuccessFactors HCM suite to the quali cation catalog in SAP ERP depends on the
SuccessFactors Learning SAP ERP SAP ERP Field Special Features of Mapping
Management System Object
(LMS) Field
Curriculum Type Ignored No hierarchies are possible in the PA version of

quali cation so this information is ignored
Curriculum Title Quali cation T574B-QTEXT

Name
Curriculum Description Ignored No equivalent eld in the SAP ERP system
Curriculum ID Quali cation T574A-QUALI Indirectly mapped via the table Global Object ID for
ID HR Objects (T777SFI_GUID_MAP)
Locale Language Indirectly with table Quali cation The SAP ERP languages are mapped to the language
Names (T574B), eld Language labels used in SuccessFactors HCM Suite (for
Key ( LANGU) example, DE to de_DE)
SuccessFactors Learning SAP ERP SAP ERP Field Special Features of Mapping
Management System Object
(LMS) Field
Curriculum Type Quali cation Infotype Object (1000), eld Indirectly mapped via the table Global Object ID for HR
Group Object Name (STEXT), with Objects (T777SFI_GUID_MAP)
OTYPE = ʻQK’
Curriculum Title Quali cation Infotype Object (1000), eld Maximum of 40 characters are considered. Competency
Name Object Name (STEXT) with name can be longer.
OTYPE = ʻQ’
Curriculum Description Quali cation Infotype Verbal Description

Description (1002)
Curriculum ID Quali cation Infotype Object (1000), eld Indirectly mapped via the table Global Object ID for HR
ID Object ID (OBJID) Objects (T777SFI_GUID_MAP)
Locale Language Infotype Object (1000), eld The SAP ERP languages are mapped to the language
Language Key (LANGU) labels used in SuccessFactors HCM Suite (for example,
DE to de_DE)
Defaulted to 01.01.1800 Begin Date Infotype Object (1000), eld Con gurable in SAP HANA Cloud Integration
BEGDA
Defaulted to 31.12.9999 End Date Infotype Object (1000), eld Con gurable in SAP HANA Cloud Integration
ENDDA

Process
4/26/2019
Default value for rating scale for creating a quali cation group
Transfer of Changed Curriculum Status Data

from SuccessFactors
Use
You set up a recurring update of the employee master data in SAP ERP HCM so that it is updated with changes in the status of
a curriculum attached to an employee in SuccessFactors.
Prerequisites
integration package that reads data from the curriculum object and updates SAP ERP HCM. For information about setting up
the SAP HANA Cloud Integration content, see Setting Up and Triggering the Integration Process for Transfer of Data.
You are using the standard employee data integration for creating users in SuccessFactors.
Features
General Features
The standard integration reads the curricula attached for users, and updates the SAP ERP HCM master data for employee.
Selection of Valid Curriculum
In the SuccessFactors learning management system (LMS), the curricula attached to employee can have the status
incomplete. However, in SAP ERP HCM, there is no feature to attach a quali cation to employee that is incomplete. For this
reason, curriculum data with the status incomplete is not replicated.
Resolving the Validity Period
4/26/2019
In the SuccessFactors LMS, the curriculum object does not have its own validity. The validity is derived from the items attached
to the curriculum object.
Items have only an expiry date and do not have an explicit start date. SuccessFactors LMS can only guarantee the validity of an
item starting today (date of read). For this reason, the start date for the employee skill is always set to today (date of update).
For each replication, all employee data is updated to begin from today (date of update).
When multiple items can be attached to a curriculum, each item can have an independent expiry date. All of the items are
processed and the earliest expiry date is considered as the expiry date for the curriculum.
Value Mapping the Rating Scale
A curriculum in SuccessFactors LMS can have the status incomplete or complete. This needs to be mapped to an SAP rating
scale. The status and rating scales are semantically different. The SAP standard integration takes account of the differences in
rating scales and converts them before saving the rating to employee skills (value mapping).
For special cases, you may want a custom value mapping logic. A BAdI is available for this purpose. For more information, see
Data Transfer of Quali cation Rating from SuccessFactors HCM Suite to SAP ERP BAdI: Con gure Value Mapping for
Quali cation Rating .
Exported Fields
more information, see Mapping of SuccessFactors Curriculum Status to SAP ERP Employee Skills.
Mapping of SuccessFactors Curriculum

Status to SAP ERP
The eld mapping of curriculum status for employee in SuccessFactors HCM Suite to employee skills in SAP ERP depends on the
SAP ERP HCM Employee Number Determination

The SuccessFactors user ID for the SAP ERP personnel number is determined by the settings in Customizing for Integration
Add-On for SAP ERP HCM and SuccessFactors HCM Suite under Integration Scenario for Quali cation Data Basic
Settings BAdI: Determine SAP ERP Personnel Numbers and SuccessFactors User IDs .
BAdI implementation HRSFI_USERID_TO_PERNR uses method PROVIDE_PERNR to determine the personnel number from the
data transferred from SuccessFactors. It checks the table SuccessFactors: Log Table for Delta Handling (HRSFI_D_EXTR_LOG)
to get the personnel number that is related to USERID.

Curriculum Field Object

Number
External person ID from infotype
Person ID (0709)
4/26/2019

Curriculum ID Quali cation Infotype 0024, eld QUALI Indirectly mapped via the table Global Object ID for HR
Key Objects (T777SFI_GUID_MAP)
Curriculum Status Pro ciency Infotype 0024, eld AUSPR Value mapped
Date of Update Begin Date Infotype 0024, eld BEGDA Default set to 01.01.1900; con gurable in SAP HANA
Cloud Integration
Earliest Expiry Date of End Date Infotype 0024, eld ENDDA Default set to 31.12.9999; con gurable in SAP HANA
Attached Items Cloud Integration


Number
External person ID from infotype Person
ID (0709)
Curriculum ID Quali cation Infotype Object (1000), eld Object Indirectly mapped via the table Global Object ID for
ID Name (STEXT) with OTYPE = ʻQ’ HR Objects (T777SFI_GUID_MAP)
Curriculum Status Pro ciency Table HRPAD31, eld CHARA Value mapped
Date of Update Start Date Infotype Object (1000), eld Object ID Default set to 01.01.1900; con gurable in SAP HANA
(BEGDA) Cloud Integration
Earliest Expiry Date of End Date Infotype Object (1000), eld Object ID Default set to 31.12.9999; con gurable in SAP
Attached Items (ENDDA) HANA Cloud Integration

Process
In SuccessFactors, the user must have the authorizations for the API to query curricula and for the API to query the curriculum
assignment to a user. The user must also have the authorizations for rest API calls. The PermissionCheck annotation must be
used for work ow restriction. For assistance, please contact SuccessFactors Professional Services or Customer Support.
4/26/2019
OData API for Quali cation Data

Use
Quali cationEntitySet
This entity set contains the entity Quali cation. It is used to update quali cations from an external source in SAP ERP HCM.
Depending on the quali cation switch, either the PA or PD quali cation catalog is updated.
If the quali cation GUID from the source is already present in SAP ERP HCM, the text and description of the same are updated
for the given language.
If a new quali cation is found, the system rst tries to determine the parent from the information in the payload. If the
quali cation group is also not found, the quali cation group is created with the name from eld QUAL_GROUP; eld SCALE_ID
contains scale information for the quali cation group. In the case of a PA quali cation, the quali cation group and scale
information are ignored.
There is no navigation from this entity.
Table 6: Operations Allowed
Operation Description
PUT UPSERT is needed in the Quali cation entity. PUT operation also takes care of insert if quali cation sent for update is not
found.
Table 7: Required Fields
Name Description
GUID Unique identi er of quali cation
LANGUAGE Language in which quali cation name and description are sent
QUAL_SOURCE Source of quali cation
Table 8: Properties
Name Key Edm Core Type Max Length Filterable
BEGIN_DATE Edm.DateTime 0 NO
END_DATE Edm.DateTime 0 NO
GUID X Edm.String 250 NO
QUAL_ABBR Edm.String 12 NO
QUAL_NAME Edm.String 40 NO
PARENT_GUID Edm.String 250 NO
LANGUAGE X Edm.String 2 NO
DESCRIPTION Edm.String 0 NO
NYEARS Edm.Decimal 0 NO
NMONTHS Edm.Decimal 0 NO
TYPE_VALIDITY Edm.Boolean 0 NO
4/26/2019
OBJID Edm.String 8 NO
PLVAR Edm.String 2 NO
PARENT_OBJID Edm.String 8 NO
QUAL_SOURCE X Edm.String 10 NO
QUAL_GROUP Edm.String 40 NO
SCALE_ID Edm.String 8 NO
Table 9: Use Cases
Use Case API Call
Update existing quali cation Call API with PUT operation and pass all information in payload
Insert new quali cation Call API with PUT operation and pass all information needed in payload
Sample payload:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<entry xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices"
xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"
xmlns="http://www.w3.org/2005/Atom">
<content type="application/xml">
<m:properties>
<d:QUAL_SOURCE>LMS</d:QUAL_SOURCE>
<d:PLVAR>01</d:PLVAR>
<d:DESCRIPTION>Curricula Description</d:DESCRIPTION>
<d:LANGUAGE>EN</d:LANGUAGE>
<d:SCALE_ID>14</d:SCALE_ID>
<d:QUAL_GROUP>Curricula Type</d:QUAL_GROUP>
<d:PARENT_GUID>LMS_123456</d:PARENT_GUID>
<d:QUAL_NAME>Security Curricula</d:QUAL_NAME>
<d:GUID>LMS_454567</d:GUID>
</m:properties>
</content>
</entry>
Quali cationRatingEntitySet
This entity set contains the entity Quali cationRating. It is used to read/update employee skills from an external source
from/to SAP ERP HCM. Depending on the quali cation switch, either the PA or PD tables are read/updated.
If the quali cation is not rated by the source system (that is, eld QUAL_NOT_RATED is set to TRUE), the quali cation assigned
to the employee is deleted from the employee pro le. All quali cations rated for an employee are updated after normalization
of the rating. Normalization is needed if the scale used in SAP ERP HCM to rate the quali cation is not the same as the scale
used in the source system. For more information about normalization, see Customizing for Integration Add-On for SAP ERP
HCM and SuccessFactors HCM Suite Integration Scenario for Quali cation Data Transfer of Quali cation Rating from
SuccessFactors HCM Suite to SAP ERP BAdI: Con gure Value Mapping for Quali cation Rating .
There is no navigation from this entity.
Table 10: Operations Allowed
4/26/2019
PUT UPSERT is needed in the Quali cationRating entity. PUT operation also takes care of insert if skill is not yet acquired by an
employee.
GET All quali cations of an employee can be retrieved using the GET operation. GET_ENTITYSET and GET_ENTITY methods are
implemented. You can also retrieve a speci c entity by passing all key parameters.
To get all entities for an entity, SFSF_USERID must be passed as a lter parameter.
DELETE The employee skill is deleted as per the key parameters supplied. If no entity is found, an error message is displayed that
the entry does not exist.
Table 11: Required Fields
Name Description
SFSF_USERID User ID from SuccessFactors
QUAL_EXT_ID Unique identi er of quali cation
QUAL_SOURCE Source of quali cation rating
Table 12: Properties
SFSF_USERID X Edm.String 100 YES (=)
QUAL_EXT_ID X Edm.String 250 NO
BEGIN_DATE Edm.DateTime 0 NO
END_DATE Edm.DateTime 0 NO
PROFICIENCY Edm.Decimal 0 NO
PROFCY_MIN_RATING Edm.String 4 NO
PROFCY_MAX_RATING Edm.String 4 NO
QUAL_NOT_RATED Edm.Boolean 0 NO
QUAL_SOURCE X Edm.String 10 YES (=)
Table 13: Use Cases
Use Case API Call
Update existing employee skill Call API with PUT operation and pass all information in payload
Insert new employee skill Call API with PUT operation and pass all information needed in payload
Delete employee skill Call API with PUT operation and pass all information and eld QUAL_NOT_RATED=TRUE
Delete employee skill directly Call API with DELETE operation
Sample payload:
<?xml version="1.0" encoding="utf-8" standalone="yes"?>

<entry xmlns:d="http://schemas.microsoft.com/ado/2007/08/dataservices"
xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata"
xmlns="http://www.w3.org/2005/Atom">
<content type="application/xml">
<m:properties>
4/26/2019
<d:QUAL_SOURCE>LMS</d:QUAL_SOURCE>
<d:PROFCY_MAX_RATING>0</d:PROFCY_MAX_RATING>
<d:PROFCY_MIN_RATING>1</d:PROFCY_MIN_RATING>
<d:PROFICIENCY>1</d:PROFICIENCY>
<d:END_DATE>2014-12-31T00:00</d:END_DATE>
<d:BEGIN_DATE>2014-01-01T00:00</d:BEGIN_DATE>
<d:QUAL_EXT_ID>LMS_454567</d:QUAL_EXT_ID>
<d:SFSF_USERID>00000002</d:SFSF_USERID>
</m:properties>
</content>
</entry>
Prerequisites
For both of the above entity sets, the user should have the authorizations as per PFCG role SAP_HR_SFI_QUALIFICATION. For
more information, see Customizing for Integration Add-On for SAP ERP HCM and SuccessFactors HCM Suite Integration
Scenario for Quali cation Data Basic Settings De ne Authorizations .

Integration Add On For SAP ERP HCM and S

Uploaded by

Copyright:

Available Formats

You might also like

Integration Add On For SAP ERP HCM and S

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Integration Add On For SAP ERP HCM and S

Uploaded by

Copyright:

Available Formats

4/26/2019

Integration Add-On for SAP ERP HCM and

For more information, please visit the SAP Help Portal.

Integration Add-On for SAP ERP HCM and

Employee data and organizational data

Variable pay data

Quali cation data

SAP ERP 6.0 SPS15 SP38 for EA-HR 600

Installation, Security, and Operation of Integration Add-On

Application Additional Information

Dependencies Between Integration Scenarios

Sequence Integration Comment

2 Onboarding data Requires the employees to be available in SuccessFactors HCM Suite.

You use middleware to transfer the data with Web services.

For more information, see Integration Using Middleware.

You download the data to les with a at le format.

For more information, see Integration Using File Download.

Roles for Integration Add-On for SAP ERP

Composite Roles for Accessing Functions in the Menu

SuccessFactors Integration: Composite Role

Single Roles for Authorizations and Access to Functions in the Menu

SuccessFactors Integration: Onboarding Data

SuccessFactors Integration: Employee Data Replication

SuccessFactors Integration: Compensation Data Replication

SuccessFactors Integration: Compensation Data Import and Activation

SuccessFactors Integration: Variable Pay

SuccessFactors Integration: Analytic Reports

SuccessFactors Integration: Quali cation Data

SuccessFactors Integration: Composite Role

SuccessFactors Integration: Employee Data Replication (SAP_HR_SFI_EMPL_DATA_REPL)

SuccessFactors Integration: Onboarding (SAP_HR_SFI_ONBOARDING)

SuccessFactors Integration: Compensation Data Replication (SAP_HR_SFI_COMP_DATA_REPL)

SuccessFactors Integration: Compensation Data Import and Activation (SAP_HR_SFI_COMP_DATA_IMPORT)

SuccessFactors Integration: Analytic Reports (SAP_HR_SFI_ANALYTICS)

SuccessFactors Integration: Composite Role

SuccessFactors Integration: Recruiting (SAP_HR_SFI_RECRUITING)

SuccessFactors Integration: Employee Data Replication (SAP_HR_SFI_EMPL_DATA_REPL)

SuccessFactors Integration: Compensation Data Replication (SAP_HR_SFI_COMP_DATA_REPL)

SuccessFactors Integration: Compensation Data Import and Activation (SAP_HR_SFI_COMP_DATA_IMPORT)

SuccessFactors Integration: Analytic Reports (SAP_HR_SFI_ANALYTICS)

SuccessFactors Integration: Recruiting

Providing Metadata from SuccessFactors to Be Used in Input Helps

Report Importing Metadata from SuccessFactors BizX (RH_SFI_SYNCH_METADATA)

Assigning Imported Metadata to Field Sets

Application Assignment of SFSF Objects to Field Sets (transaction S_NWC_37000012)

Check Field Sets for Required Fields

Report Insert and Check Required Fields in Field Sets (RH_SFI_RECRUIT_REQ_FIELDS)

Editing Positions to Create Job Requisitions in SuccessFactors

Application Change Organization and Staﬃng (transaction PPOME)

Transfer of Job Requisition Data for Positions to SuccessFactors

Report Create and Update Job Requisitions in SuccessFactors (RH_SFI_TRIGGER_JOB_REQUISITION)

Correct the Status of Job Requisitions in the SAP ERP System

Report Change Status of Job Requisitions (RH_SFI_JOB_REQ_STATUS_CHANGE)

Specify the ID of the Candidate Template from SuccessFactors

Application Enter ID of Candidate Template from SuccessFactors BizX (transaction S_MWC_87000008)

Importing Applications from SuccessFactors

Report Importing Recruiting Data from SFSF (RH_SFI_IMPORT_RECRUITING_DATA)