Preparing an Instance for an SAP SuccessFactors Recruiting Configuration

Learn about identifying roles while determining solution access rights.

Learn about distinguishing recruiting operators from permissions groups.

When you have your first Recruiting client, getting started consulting with your customer is not just about identifying business requirements. You will also need to configure certain items in Provisioning to prepare for implementation of the Recruiting solution.

Apart from Provisioning configurations, there are several front-end settings and permissions to enable.

Access Request Process

1. Obtain a system generated email approval from the customer to access their instance.

2. Submit a request through the Customer Instance Access Request form at https://hxmcloudops.successfactors.com/Implementation/IRequests

3. Provide the following data:

   • Customer Name

   • Company ID and Tenant ID (for all access which is needed)

   • Data Center and Environment

   • Provisioning ID

   • Customer Approval

Please note that a detailed description of the process is available in the Implementation Guide for Recruiting Management.

Note

Before you can configure the baseline settings or perform any other tasks, you must request access to the instance from the customer. Typically, a customer creates a specific role that is assigned to consultant during the implementation. Once the project is completed, the role is removed from the system. The request and support path vary based on your role (such as Customer Success or Professional Services) and intended use of the instance (such as demo or live client). In all cases, provide business justification with access requests.

Many options will already be checked in Provisioning → Company Settings, depending on the modules already enabled in the instance.

• Note the highlighted options for basic settings for the Recruiting solution.

Caution

When working with existing customers, do not check a general setting that is not wanted or needed (or uncheck a general setting that is needed) and do not modify settings that are unfamiliar.

In the main Company Settings area, a few general options to check for net new customers display on the right.

Note

Several additional options are checked in the instance even for net new customers. The above is a guide for enabling important features in the v12 interface that are used in the training course. It is always recommended to reference the Setting Up and Maintaining SAP SuccessFactors Recruiting guide (Recruiting guide) in the "Recommended Baseline Settings in Provisioning" section to review the most up-to-date list of necessary recruiting settings.

Enable a few more settings in the General Settings area to start turning on the Recruiting module.

• Question/object management

• Recruiting: Main on/off switch for the Recruiting solution

• Attachment Manager: Enables the ability to attach documents, such as resumes

  

Note

Be sure to click the correct Save Feature button close to the top of the screen for these general settings and those previously mentioned.

Provisioning is updated frequently as new features are introduced. As a result, clean-up may lag with tags such as [Not Ready for Sales/Production]. You can ignore these warnings if the feature has been officially released or announced as GA (General Availability).

The Recruiting section further defines options within the Recruiting solution.

Provisioning – Recruiting Section of Company Settings

• Options are only selectable after clicking Recruiting in the General Settings area.

• Background Check and Onboarding Settings should be turned on for implementations involving background check services and onboarding services.

  
  

Note

Once you select Enable Job Alerts for Candidates, click Save and then select a user to own the jobs (most likely a recruiting administrator).

Note

Most companies want the ability to enable posting to specific agencies, but check with them first as it cannot be turned off once enabled.

Reference the SAP SuccessFactors Recruiting Management Implementation Guide for the most up to date recruiting settings and comprehensive explanations of these settings.

Recruiting-specific reports are available through Ad Hoc Reporting.

Reference the Recruiting Guide for the most up-to-date reporting settings based on your client’s license agreement.

Attachment Options in Company Settings

Attachment requirements should be altered to accommodate space and size specifications. The recommended settings are shown in the figure, Provisioning Attachment Options Company Settings.

In addition to turning on the appropriate Company Settings, you will find a section for Managing Recruiting on the home page of Provisioning. Within this section, you can import the necessary recruiting data models.

Within Managing Recruiting → Edit Candidate Profile Template, a starter candidate profile template (CPT) may be uploaded. The CPT can also be uploaded later in an implementation, but importing a starter template during the initial setup allows for the instance to be indexed right away.

• The starter template can include a few basic fields (such as a name field and address fields) to allow for indexing.

  

The instance may not need to be re-indexed once changes are made to the CPT. Refer to the Recruiting guide for the circumstances under which re-indexing is needed.

Indexing enables job posting, job searching, and candidate search functionality.

After Company Settings are selected and a starter CPT is uploaded, a support ticket must be submitted to request index creation for the instance.

Index Request

To request index for your sales or training instance, follow the instructions below:

1. Log in to the SAP SuccessFactors HXM Cloud Operation Portal Login: https://hxmcloudops.successfactors.com/home/index

2. Select Operation Requests → Request Forms.

3. Select Sales/Training Instance Re-Index.

4. Complete all required information. Make sure that in the note field you provide instance details for which you want to request an index.

5. Select Submit.

If you need to request an index for a customer instance, submit the request via SAP ONE Support Launchpad. The link is available in SAP Support Portal: https://support.sap.com/en/index.html

Note

Users will not see the Recruiting tab in the instance until the module, Job Requisition, when one of the following occurs:

1. The Requisition XML (JRDM) is uploaded and either one of the following actions have been performed:

   • Users are granted from creation permission for the job requisition.

   • Users are identified on the route map as having an approving role.

2. Users are granted relevant recruiting permissions in Admin Center → Recruiting permissions.

After you have finished completing the setup in Provisioning, there are several front-end settings and permissions to enable.

While Provisioning hosts many of the switches to enable some of the major features that the SAP SuccessFactors Recruiting solution offers, there are additional switches available in Admin Center → Manage Recruiting Settings that can be enabled by partners or customers. Some switches are used to enable features (such as enabling Business Rules for Recruiting), while others are used to enhance features that are already enabled (such as dispositioning candidates into disqualification statuses).

Learn about Recruiting feature settings in Admin Center and the leading practice on how to set them in the Setting Up and Maintaining SAP SuccessFactors Recruiting guide on the SAP Help portal.

Setting up appropriate role-based permissions is critical to the set up of the Recruiting solution. When creating role-based permission groups, it is important to assign specific Recruiting-related Role Based Permissions.

1. Navigate to Admin Center and, in the Manage Employers section, select Set User Permissions.
2. Select Manage Permission Roles and select the role: Full System Administrator.
3. Select the Permission button, and then, in the Administrator Permissions section, select all the Recruiting-related links.
4. Select Done. Exception: Do not select the Hide options under Recruiting Permissions.
5. Scroll down to locate the Grant this role to section. Ensure Permission Groups or Users is set to Full System Administrator and Target population is set to All.

1. In the Permission Role list, select All Employees.
2. Select Permission.
3. In the User Permissions section, click Employee Data.
4. Select the View or Edit check boxes for all settings listed in their respective columns.

   View	Edit
   Address 1	Photo
   Address 2	Certification/Licenses
   Business Phone	Formal Education
   City	Language Skills
   Country	Previous Employment
   Department	Professional Membership
   Division
   Email
   Employee Id
   First Name
   Job Code
   Last Name
   Manager
   State
   Title
   Zip

5. Select Employee Views, and in the Employee Views section, select all of the following check boxes:
   • History
   • Notes
   • Profile
6. Select General User Permissions and validate that the following check boxes are selected:
   • User Login
   • Live Profile Access
   • Permission to Create Notes
   • Organization Chart Navigation Permission
   • Company Info Access
   • User Search
7. Select Recruiting Permissions, scroll down to select Careers Tab Permission, and then select Done.
8. Locate the Grant this role to section, and then ensure that Permission Groups or Users is set to Everyone and Target population is set to All.

Note

The following employee data permissions can be found under the Background section: Certifications/Licenses, Formal Education, Language Skills, Previous Employment, and Professional Memberships. If you do not provide the employee group with permissions to the background elements, the Candidate Profile SM-Mapping exercises will not work properly.

The Route Map is used as the approval workflow for the job requisition. Because it is a platform feature, used for other approval workflows for areas like Goals/Performance Management, you will see many features that are not Recruiting specific. 

Route Map Step

Generally, a route map can include the following steps:

• Modify Steps allow the form to be editable.

• Signature Steps are not formally supported in Recruiting.

The initial creation (or origination) step should always be the role of O (= Originator). A common route map is: O → G → R (Originator to Hiring Manager to Recruiter). The Originator is a selectable role, but other roles are selected through the Custom option.

The route map can include iterative and collaborative steps:

• Iterative steps allow the form to be sent back and forth between one or more users at a time in a step, for example, an iterative step between Recruiter and Hiring Manager.

• Collaborative steps allow the form to be accessed by more than one person in a step without having to send it back and forth.

Any operators that are configured in the steps created will appear on the first (short) screen of the Create Job Requisition, so that the user must associate an individual to each operator role.

Select the Custom role and enter the value of the appropriate recruiting operator.

The Get Feedback button can be used in the workflow when the client wants the Get Feedback user to be able to view and edit fields within the requisition.

You can grant permissions for the V (= Ad Hoc Approvers) for generic approver privileges. Any permissions given to V will be applicable to anyone on the route map and they supersede other roles, so grant permissions carefully.

The Add Modifier button can be used in the workflow when the client wants additional approvers and approves of using the V role.

Note

Modifier can be changed to Approver via text replacement. Changing the text can affect other modules as well.

Once the job requisition template is imported in Provisioning, you will need to map the job requisition to the route map that you have created. You can configure additional settings in Form Template Settings for each individual job requisition. These steps are outlined in the unit on job requisitions. 

The limitations of the route map include:

• Signature steps are not formally supported in Recruiting Management. This means even if they seem to function, they should not be used.
• There is no way to send an approved requisition back into pre-approval or send it through the route map again.
• There is no way to remove a route map step after it was added into the route map via Add Modifier.
• Conditionality is not supported in route maps (if x, route to a. If y, route to b.)

Recruiting uses rating scales to rate competencies on the Interview Assessment. The interview assessment is used in Interview Central by individuals who have been nominated as an interviewer. By creating a separate rating scale for interviews, you can control the scale itself (1-10, 1-5) and label the ratings appropriately.

An example of an Interview Assessment rating scale may look like:

If different ratings scales are required for different job types, a different rating scale can be applied to different job requisition templates. 

SAP SuccessFactors Recruiting uses picklists in many places, including job requisitions, candidate profiles, job applications, and job offers. In SAP SuccessFactors Recruiting configuration templates, you can configure fields to use a picklist, referenced by the picklist ID. Create the picklists you need before uploading a template that references them.

Considerations include:

• In Recruiting, the list of supported countries/regions is provided in the country/region picklist. To add a country/region to the country/region picklist, it must be in the U.S. English locale and must match with the country/region in the country/region picklist.
• You can search a candidate based on a country/region in the Candidate Search page only if the country/region is specified in the U.S. English locale, and matches the default value in the country/region MDF generic object.
• If multiple languages are used in Recruiting, ensure that all picklists have a translated value in all those languages. Not doing so can cause issues with fields appearing as blank.
• Translate picklists into other languages with care; some symbols can cause load errors.
• The standard and custom picklist fields on the Candidate Profile and the Job Application pages support the typeahead feature. The feature is supported only for fields whose type is defined as picklist in the Candidate Profile and the Job Application templates.

Typeahead functionality is not supported in the following:

• Recruiter-facing pages, such as the Candidate Workbench and the Application Workbench
• Create Account page
• Job Search page
• The Country field when using Quick Apply. The other fields where their type is defined as picklist do support typeahead.