SAP Best Practices SAP ERP HCM: Recruitment Integration (C1M):: Configuration Guide
EHP0 to EHP7 for SAP ERP 6.0June 2014
EnglishEnglish / SAP ERP HCM: Recruiting Integration (C1M)
SAP AG
Dietmar-Hopp-Allee 16
69190 Walldorf
Germany / Building Block Configuration Guide
© SAP AG Page 44 of 44
SAP Best Practices SAP ERP HCM: Recruiting Integration (C1M): Configuration Guide
Copyright
© 2014 SAP AG or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Icons
Caution
Example
Note
Recommendation
Syntax
Typographic Conventions
Type Style / DescriptionExample text / Words or characters that appear on the screen. These include field names, screen titles, pushbuttons as well as menu names, paths and options.
Cross-references to other documentation.
Example text / Emphasized words or phrases in body text, titles of graphics and tables.
EXAMPLE TEXT / Names of elements in the system. These include report names, program names, transaction codes, table names, and individual key words of a programming language, when surrounded by body text, for example, SELECT and INCLUDE.
Example text / Screen output. This includes file and directory names and their paths, messages, source code, names of variables and parameters as well as names of installation, upgrade and database tools.
EXAMPLE TEXT / Keys on the keyboard, for example, function keys (such as F2) or the ENTER key.
Example text / Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
<Example text> / Variable user entry. Pointed brackets indicate that you replace these words and characters with appropriate entries.
Contents
1 Purpose 5
Using the Configuration Guide 6
1.1.1 Base Service 6
1.1.2 Upgrade Module 7
1.1.3 Compensation Module 7
1.1.4 Recruiting Module 7
1.1.5 Go-Live Support Module 7
2 Basic Settings 8
2.1 Settings for Middleware 8
2.1.1 Storing Credentials for Transferring Recruiting Data to Secure Storage 8
2.1.2 Defining Package Size for Transferring Recruiting Data 9
2.2 Importing Metadata from SuccessFactors BizX 9
2.3 System setting for Create Vacancy 10
3 Integration Scenario for Recruiting Data 11
3.1 Activate Additional Functions 12
3.2 Assign SuccessFactors BizX Objects to Field Sets 13
3.3 Map SuccessFactors BizX Fields and SAP ERP Fields to Each Other 14
3.4 BAdI: Determination of Job Requisition Template from SFSF 20
3.5 Sample Implementation of BAdI: Determination of Job Requisition Template from SuccessFactors 22
3.6 BAdI: Mapping of SAP ERP Infotype Fields to SFSF Fields Mapping of SFSF Fields 23
3.7 BAdI: Mapping of ERP Infotype Fields to SFSF Fields: Chg. of Mapping Result 31
3.8 Define Values of Job Requisition Status Used in SFSF 33
3.9 Specify Handling of Existing Vacancies During Data Transfer 34
3.10 Display Infotype SFSF Job Requisition in Organizational Mgmt Applications 34
3.11 Correct Status of Job Requisitions in the SAP ERP System 36
3.12 BAdI: Mapping of SFSF Fields to SAP ERP Infotype Fields 37
3.13 BAdI: Mapping of SFSF Fields to ERP IT Fields: Chg of Mapping Result 40
3.14 BAdI: Determination of Further Data for Recruiting Scenario 42
3.15 Change Application Status Values Used in SuccessFactors BizX 43
3.16 Importing Recruiting Data to SAP ERP 44
3.17 Choose Option for Deriving SuccessFactors BizX User ID from SAP ERP 45
3.18 Enter ID of Candidate Template from SuccessFactors BizX 46
SAP ERP HCM: Recruiting Integration : Configuration Guide
1 Purpose
This document describes the configuration and customizing steps that have to be done on the SAP ERP HCM system to customize the Integration Scenarios for Recruiting Data.
There are configuration settings required in the target SuccessFactors BizX system to enable the import and export of the recruiting data from HCM. Refer to Configuration Guide (C1N): SuccessFactors: Recruiting Integration for the settings required
1.1 Using the Configuration Guide
This document is set up to support all the possible options in this Packaged Solution. If not all modules are used, not all sections in this document are relevant. In the following overview, you can find which parts of this document are relevant for each module:
Scope – Optional Modules / Upgrade Module / Compensation Module / Recruiting ModuleUpgrade the Integration Add-on from SP00/SP01 (File-transfer) to the SP02 Middleware based solution
Migration support for two existing BAdI (max. 4 days effort)
No Go-Live support Module
No User Defined Options / Pay for Performance Integration
No User Defined Options / Recruiting Integration for Internal and External Candidates
No User Defined Options
Go-Live Support Module:
Help transport to QA & Prod
Go-Live support
Core / Base Service
• Kick-off workshops, Identify the requirements and finalize scope options/ work packages, Verify the landscape, Check prerequisites for selected options
• Basic Employee data: Full employee data extraction from HCM to Successfactors
• User Defined Options: Maximum 5 simple enhancements each extracting one single HCM Infotype field for a total of 5 days of development effort, including unit test.
• Workforce Analytics: Prepare the transfer of Analytics Data from HCM to SuccessFactors Workforce Analytics
1.1.1 Base Service
For the Base Service, the following building blocks and parts have to be used:
· C1F - SAP ERP HCM: Base Integration Settings
o Defining Authorizations
o Storing Credentials for Transferring Employee Data to Secure Storage
o Defining Package Size for Transferring Employee Data
· C1G - SAP ERP HCM: Employee Data Integration
o Creating Report Variant for Data Extraction
o Specifying Allowed Variants for Delta Extraction
o Defining Name Format for Fields FIRSTNAME and LASTNAME
o Enhancement of Employee Data Extraction
o Running Extraction of Employee Data and Organizational Data
o Sync Employee Data with SuccessFactors (with Delta and Inactive Logic)
o Example of BADI Extension for Employee Data
· C1H - SuccessFactors: Employee Profile Integration
o All parts
1.1.2 Upgrading Module
For the Upgrade Module, please see section 1.1.1 Base Service. The required steps are the same.
1.1.3 Compensation Module
For the Compensation Module, the following building blocks and parts have to be used
· C1J - SAP ERP HCM: Compensation Integration
o Basic Settings
§ Storing Credentials for Transferring Compensation Data to Secure Storage
§ Defining Package Size for Transferring Compensation Data
o Integration Scenario for Compensation Data
§ Data Transfer SAP ERP to SuccessFactors BizX
· All parts
§ Data Transfer from SuccessFactors BizX to SAP ERP
· All parts
· C1K - SuccessFactors: Compensation Integration
o All parts
1.1.4 Recruiting Module
For the Recruiting Module, the following building blocks and parts have to be used:
· C1M - SAP ERP HCM: Recruiting Integration
o Basic Settings
§ Import Metadata from SuccessFactors
§ Storing Credentials for Transferring Compensation Data to Secure Storage
§ Defining Package Size for Transferring Compensation Data
o Integration Scenario for Compensation Data
· C1N - SuccessFactors: Recruiting Integration
o All parts
1.1.5 Go-Live Support Module
No parts of this document are relevant for this Module.
2 Basic Settings
2.1 Settings for Middleware
2.1.1 Storing Credentials for Transferring Recruiting Data to Secure Storage
Use
In this Customizing activity, you encrypt the Credentials for Recruiting Data, which logs on the middleware on SuccessFactors BizX system for employees to transfer data from the SAP ERP system to SuccessFactors BizX for basic data integration
To do this, define the company ID, user name and password that you use to log on SuccessFactors BizX system in the secure storage of the SAP NetWeaver Application Server ABAP
Procedure
This step has to be executed in every system (Development, Test, Productive, and so on.
1. Access the activity using one of the following navigation options:
Transaction code / SPROIMG menu / Personnel Management ® Integration Add-On for SAP ERP HCM and SuccessFactors BizX ® Basic Settings ® Settings for Middleware ® Store Credentials for Transferring Recruiting Data to Secure Storage
2. Enter the information for the company ID, user name and password that you use to login to the SuccessFactors BizX system for the transfer of the basic data.
Field / Data / CommentsCompany ID / Here you will enter the Company ID that you have been given in SuccessFactors for Recruiting
User / Here you would enter the User ID for the Administrator in SuccessFactors that will allow you the access for the integration of the recruiting
Password / Here you would enter the password for the user id in SuccessFactors that will allow you the access for the integration of the recruiting
2.1.2 Defining Package Size for Transferring Recruiting Data
Use
In this Customizing activity, you specify the number of records to be included in each data package sent via middleware.
Procedure
1. Access the activity using one of the following navigation options:
Transaction code / SPROIMG menu / Personnel Management ® Integration Add-On for SAP ERP HCM and SuccessFactors BizX ® Basic Settings ® Settings for Middleware ® Define Package Size for Transferring Recruiting Data
2. Enter the Parameter Name PACKAGE_SIZE and the Parameter Number of 200.
2.2 Importing Metadata from SuccessFactors BizX
Use
In this Customizing activity, you run the report for transferring metadata from the SuccessFactors BizX system into SAP ERP HCM for candidates to be hired and job requisition data from SuccessFactors.
For transferring the data from SFSF into SAP, you use the report Importing Metadata from SuccessFactors BizX (RH_SFI_SYNCH_METADATA).
This report is also located in the user menu for the role SuccessFactors Integration: Recruiting (SAP_HR_SFI_RECRUITING).
Requirements:
· Before completing this step for Synchronization Settings for Recruiting, the following must be created in SuccessFactors:
The Job Requisitions used for the integrated recruiting processes must contain a data entry field for the following SAP data elements. A job requisition XML template contains the necessary SAP HCM fields. Please refer to the section on the Job Requistion Template in the Configuration Guide SuccessFactors: Recruiting Integration (C1N).
§ Position ID
§ Personnel Area ID
§ Personnel Subarea
§ Employee Group
§ Employee Subgroup
§ Organizational Unit ID (if OM:PA integration is not enabled)
§ Cost Center ID (if OM:PA integration is not enabled)
o The Offer Detail must contain a Start Date.
o A ‘Recruiting V2’ ad hoc report must be created in SuccessFactors which contains the fields to be transferred to HCM. The selected fields will come from the Job Requisiton, the Job Application, the Candidate Profile and the Offer Detail. – Refer to Configuration Guide SuccessFactors: Recruiting Integration (C1N)
Procedure
This step has to be executed in every system (Development, Test, Production). These configuration settings are not transportable, and the SuccessFactors content that is extracted in this step may differ between the SF Test and SF Production systems.
This program also has to be scheduled as a regular job in the follow-on systems (that is, Test, Productive).
1. Access the activity using one of the following navigation options:
Transaction code / SPROIMG menu / Personnel Management ® Integration Add-On for SAP ERP HCM and SuccessFactors BizX ® Basic Settings ® Importing Metadata from SuccessFactors BizX
2. Select the check box for Ad Hoc Reports Job Requisition Templates as required for:
a. Synchronization Settings for Recruiting
i. SFSF Ad Hoc Reports
ii. SFSF Job Requisition Templates
3. Execute the report to import the ad hoc report and job requisition metadata to SAP ERP HCM.
4. Examine the results log after report execution. Ensure that your expected reports do not appear with any error. The reports are listed with the report names used in the SuccessFactors API Data Dictionary.
5. Schedule the report in the follow-on systems (for example, test or productive system) as a regular background job to regularly update the metadata. For more information, see the Administrator's Guide for the integration add on for SAP ERP Human Capital Management and SuccessFactors Business Execution.
2.3 System setting for Create Vacancy
Use
In this Customizing activity, activate vacancy infotype 1007 in SAP OM. This is a pre-requisite setting for activating the job requisition integration between SAP HCM and SuccessFactors.
Procedure
1. Access the activity using the following navigation option:
Transaction code / SM30 (Table/View T77S0)2. Select the “Maintain” button and select “Position” to find Group “PPVAC PPAVAC”
3. Set the Value abbr column to a value of “1” to activate vacancy management
4. Save the entries.
3 Integration Scenario for Recruiting Data
In this section, you customize the Integration Scenario for the Recruiting Data in SAP HCM
Refer to the relevant section of the Scope Questionnaire for configuration requirements.
The configuration steps in this section are dependent on the following system configuration in SuccessFactors:
o In SuccessFactors BizX, the application programming interfaces (APIs) have been made available for importing recruiting data to SAP ERP - Refer to Configuration Guide SuccessFactors: Recruiting Integration (C1N)
o Specific SAP Applicant Status codes must be created in SuccessFactors. Please refer to the section on Applicant Status Sets in the Configuration Guide SuccessFactors: Recruiting Integration (C1N) Step