Preparing for an SAP SuccessFactors Career Site Builder Implementation
Designing the Career Site
Completing the Initial Setup of the Recruiting System
Building the Career Site
Moving the Career Site to Production
Engaging Potential Candidates
Implementing Source Reporting
Succeeding as a Consultant

Preparing Localization of a Career Site for a Customer

Objective

After completing this lesson, you will be able to prepare localization of a career site for a customer.

Localization Overview

As an organization extends its global reach, the need to attract local talent often requires localizing (translating) your customer's career site. In addition to allowing candidates to search for jobs based on their local language, all elements of the Career Site Builder site can be localized, including job alert emails and Google Job Maps.

Localization Timing

During implementation projects, the default locale (usually English) should be built and approved before moving forward with additional locales. Begin the process as soon as the default locale text has been approved.

The customer’s additional locales can be enabled and configured either during Iteration 2 or 3, depending on the state of the default language text. If the customer’s text in English is approved at Iteration 2, begin the localization process. If not, wait to begin localization until the English copy is approved during Iteration 3.

If the translation phase does not begin until iteration 3, you’ll need to add a cushion in the schedule.

Career Site Builder Localization

Locales are set up to mirror the base site (typically en_US, US English) calling in the same imagery and design, but localized based on the language.

Examples of the same Best Run company's pages in different locales.

Introduction to Locales

A locale identifier consists of a language code and a country/region code.

Examples of Locales Identifier such as en_GB, en_US, es_MX, or es_ES.

Within SAP SuccessFactors, the standard default language is normally English US (en_US), though it can be changed to another language. For example, if your customer only requires Danish, change the default locale to da_DK.

Note

  • UTF-8 Encoding should always be used for every xml, csv and spreadsheet file involved in a translation project. All file uploads in SAP SuccessFactors should be done with UTF-8 encoding selected.
  • Translations are always provided by the customer. Do not use Google Translate! It exposes the customer’s content to Google.

General Localization Process

The SAP SuccessFactors statement of work or Schedule A lists the languages that the consultant is responsible for implementing. The leading practice is to have the same layout, images, and (translated) copy as your base site locale. This is a web standard and the way CSB projects are normally scoped. If your customer requests changes to the layout, images, or other elements for their localized pages, that may require a change request.

General considerations of the localization process are as follows:

  • The text in the system interface is translated when the locale is enabled. System text translations can be replaced in Career Site Builder under ToolsTranslations.
  • Career Site Builder locales typically include localized content for all page types and job alert email templates.
  • Any custom text that the customer provides for the default language must be translated by the customer for the other locales that are enabled. This includes text provided for CSB page components.
  • On the pertinent tabs in the Recruiting Marketing Workbook, columns for translations have been added at the right. Copy the columns for additional languages. Hide unnecessary columns before providing the workbook to the customer for translations.
  • All translations should be provided by the customer in the workbook and delivered to the consultant at one time. If necessary, before beginning configuration of the languages, the consultant will alert the customer of any translations that were missed, HTML that was corrupted, and so on.
  • The consultant is responsible for entering the translations that are provided.
  • The customer is responsible for testing the translations.
Global Elements Localization Columns in the Workbook with the fr_FR and zh_CN columns highlighted.

Languages and Templates Management

Locales can be enabled from ProvisioningCompany SettingsLanguage Packs or from Admin CenterManage Languages.

Leading practice is to always enable two tools for your customers from ProvisioningCompany Settings. This empowers customers to manage their own localization needs after go-live.

  • Manage Languages can be used to enable languages and change translations for labels within SAP SuccessFactors HCM. (Manage Languages was previously called Tier 3 Language Packs.)
  • Manage Templates enables customers to edit the Recruiting templates: Job Requisition, Job Application, Candidate Profile, and Offer Detail templates.

Remind your customers that Manage Languages and Manage Templates are powerful tools and should only be used by trained users. Please see the instructions in the Recruiter Experience Administrator Training course (HR831), available from SAP Learning.

Localization Permissions

For users who will use Manage Languages, also from Manage Permission Roles, select Manage Recruiting on the left and Manage Recruiting Languages on the right.

Manage Recruiting Languages Permission.

From Manage System Properties, select Text Replacement on the right. This is also the permission for Manage Languages.

From Manage System Properties, select Text Replacement.
Manage Languages page with a few languages selected.

Localization Enablement

The customer’s locales are enabled in the following places:

  • Manage Languages (or Provisioning)
  • Manage Recruiting Languages
  • Career Site Builder

Enablement of Locales from Manage Languages

To enable a new locale, proceed as follows:

  1. Navigate to Admin CenterManage Languages.
  2. Select the desired locales from the Active column.
  3. Choose Save.

Once a language is enabled, it appears as an option for all SAP SuccessFactors HCM users to select as their preferred language from the Settings menu. The language will also become available in Admin CenterManage Recruiting Languages.

Also recommended: At the bottom of the page, choose Update to increase the maximum number of keys to 10,000 and the file size maximum to 10 MB.

To increase the maximum number of keys to 10,000 and the file size maximum to 10 MB, choose Update on the Configuration age.

Enablement of Locales from Manage Recruiting Languages

From Admin CenterManage Recruiting Languages, select the same languages that you enabled from Manage Languages.

The Default Language is set during the initial implementation.

In Admin Center, specify the default language from the dropdown list and select the enabled languages checkboxes.

Enablement of Locales in Career Site Builder

To enable locales in Career Site Builder, proceed as follows:

  1. From Career Site Builder, navigate to SettingsSite ConfigurationSite Locales.
  2. Select the same locales as from Manage Languages. The Default Locale displays at the top. Do not delete the default.
  3. Save.
On the Site Configuration, enable locales. Under Site Configuration, the en_Us and es_ES are highlighted.

IMPORTANT! Select the identical locales that were enabled from Manage Languages. For example, do not select es_ES in Manage Languages and es_MX in Career Site Builder.

Enable Locales

This video provides a demonstration of how to enable locales.

Business Example

Enable English, German, and Spanish for Best Run in Provisioning, Admin Center, and Career Site Builder.

Task 1: Enable Locales in Provisioning

Steps

  1. Log in to Provisioning and navigate to Company SettingsLanguage Packs. Alternatively, you can enable locales from Admin CenterManage Languages.

  2. In addition to English US-en_US, select Deutsch (German)-de_DE and Español (Spanish)-es_ES). If additional languages are enabled, you can leave them. You won’t select them for Recruiting.

  3. Scroll up and choose Save Feature to save your changes.

Task 2: Enable Locales Used in Recruiting in Admin Center

Steps

  1. Log in to your instance and navigate to Admin CenterManage Recruiting Languages.

  2. Confirm that English US is the Default Language.

  3. For Enabled Languages, select Deutsch (German), English US, Español (Spanish).

  4. Save Changes.

Task 3: Enable Locales in Career Site Builder

Steps

  1. Open Career Site Builder and navigate to SettingsSite ConfigurationSite Locales.

  2. Confirm that en_US is enabled and is the default Locale.

  3. Enable de_DE and es_ES.

  4. Save.

Summary

  • Localization in SAP SuccessFactors Career Site Builder allows organizations to attract local talent by translating all site elements, including job alerts and system text, with the default locale (usually English) built and approved before adding additional languages.
  • Customers are responsible for providing all translations (not using tools like Google Translate), while consultants enter the translations and customers test them; UTF-8 encoding must be used for all translation files.
  • Locales are enabled in both Manage Languages and Career Site Builder, and it is essential to select the same locales in both places to ensure consistency; only trained users should manage localization tools due to their impact on site configuration.