Study guide

3.4 Text Replacement, Manage Languages, and Translations

SAP Certified - SAP SuccessFactors Employee Central Core and Position Management C_THR81

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: C_THR81 Exam and SAP SuccessFactors Platform Foundations

1.1 C_THR81 Exam Format, Logistics, and Preparation Plan 1.2 SAP SuccessFactors Suite, Platform Capabilities, and Employee Central Core 1.3 Instances, Provisioning, and Company Settings 1.4 Administrator Types, Super Admin Access, and Admin Center Navigation 1.5 Release Management, Upgrade Center, Release Center, and Consultant Resources

2 Chapter 2: Security, Proxy, and System Administration

2.1 Role-Based Permissions: Groups, Roles, and Target Populations 2.2 RBP Troubleshooting, Reports, and Governance Best Practices 2.3 Proxy Management, Company System and Logo Settings, and Platform Feature Settings 2.4 Admin Alerts, Check Tool, and System Access Settings 2.5 Scheduled Job Manager, Provisioning Job Scheduler, and Execution Manager

3 Chapter 3: User Experience Configuration

3.1 People Search, Action Search, Custom Navigation, Org Chart, and Built-In Support 3.2 Home Page Configuration and Mobile Settings 3.3 E-mail Notifications, Themes, and Company Logo 3.4 Text Replacement, Manage Languages, and Translations

4 Chapter 4: People Profile, Picklists, User Data, and the Metadata Framework

4.1 Latest People Profile, Categories, Cards, and Custom MDF Cards 4.2 Manage Business Configuration and Succession Data Model XML Fundamentals 4.3 Picklist Center, Cascading Picklists, and the Employee Central Master Picklist 4.4 User Data File, Employee Import, and User Management Tools 4.5 Metadata Framework Enablement and Object Definition Settings 4.6 MDF Fields, Associations, Search, and Security

5 Chapter 5: Business Rules

5.1 Rules Engine Fundamentals: Scenarios, Base Objects, MDF Rule Events, and the Execution Log 5.2 Employee Central Rule Events, Rule Scenarios, and Model Base Objects 5.3 Propagation Rules and Hire/Rehire Rules 5.4 Cross-Entity Rules, Rule Context, and Rule Design Practices

6 Chapter 6: Foundation Objects and Corporate Data Models

6.1 The Four Employee Central Data Models, DTDs, and Upload Sequence 6.2 Foundation Objects: Organization, Pay, and Job Structures 6.3 Configuring Legacy and MDF Foundation Object Definitions 6.4 Foundation Object Associations and Field Criteria 6.5 Country-Specific Fields for Foundation Objects

7 Chapter 7: Employee Data Structures and Permissions

7.1 Person and Employment Objects, Effective Dating, and Employee Identifiers 7.2 Configuring the Succession Data Model with BCUI and XML 7.3 Country-Specific Succession Data Model: National ID, Addresses, Global Information, and Job Data 7.4 HRIS Synchronization and Sync Mappings 7.5 Employee Central Permissions for Administrators

8 Chapter 8: Employee Transactions and Data Maintenance

8.1 Hire, Rehire, Termination, and No-Show Transactions 8.2 Importing New Employees and Updating Employee Data by Import 8.3 Mass Data Management for Job Information, Job Relationships, and Positions 8.4 Employee and Manager Self-Service Permissions

9 Chapter 9: Workflows, Alerts, and Event Reasons

9.1 Workflow Configuration, Participants, Dynamic Roles, and Dynamic Groups 9.2 Managing Workflows: Approvals, Delegation, Reminders, Escalation, and Auto-Approval 9.3 Employee Central Alerts and Notifications 9.4 Events, Event Reasons, and Event Reason Derivation 9.5 Workflow Derivation Rules and How They Work with Event Reason Derivation

10 Chapter 10: Optional Employee Central Configurations

10.1 Employee Central Quick Actions and Internal Job History 10.2 Custom Hire Templates, the Diagnostic Tool, and Joule in Employee Central

11 Chapter 11: Position Management Setup

11.1 Position Management Overview: Positions, Jobs, and the Leading Hierarchy 11.2 Enabling Position Management and Setting Role-Based Permissions 11.3 Navigating and Configuring the Position Organization Chart 11.4 Configuring the Position Object 11.5 Position Management Settings 11.6 Creating, Maintaining, Importing, and Mass-Changing Positions

12 Chapter 12: Position Management in the Employee Lifecycle

12.1 Position Fields in Job Information and Hiring Employees to Positions 12.2 Maintaining Incumbents: Transfers, Reclassification, Global Assignments, and Right to Return 12.3 Manager Self-Service with My Team Positions and Quick Actions for Positions 12.4 Terminations with Position Management and Position Workflows

13 Chapter 13: Position Management Rules, Integrations, and Company Structure

13.1 Position Management Rule Scenarios and Rules for Position Data Entry 13.2 Synchronization Rules and Mass Change Runs for Positions 13.3 Position Code Generation, Position Workflows, Right to Return Setup, and Rule Functions 13.4 Integrating Position Management with Recruiting and Succession 13.5 Building the Company Structure Overview

3.4 Text Replacement, Manage Languages, and Translations

Key Takeaways Explain This Topic AI

Text Replacement customizes selected UI labels through the TEXT_REPLACEMENT_KEYS and ADMIN_TEXT_REPLACEMENT_KEYS language-pack keys.

Manage Languages can overwrite up to 10,000 values per locale; the default limit is 25, and custom language-pack CSV files are limited to 10 MB.

Manage Languages needs Language Packs and the Manage Languages tool enabled in Provisioning, plus the Text Replacement permission.

Customers provide and test translations; consultants provide the translation workbook and configure translations in test first.

Legacy foundation data falls back from the logon language to the Provisioning default language and then to US English.

Last updated: September 2026

3.4 Text Replacement, Manage Languages, and Translations

Quick Answer: Use Text Replacement first to change common UI labels, such as "Employee" to "Associate". If a label is not available there, Manage Languages can overwrite any UI label in any supported language, within limits. In translation projects, the customer provides the translations and the consultant configures them, always in the test instance first . Legacy foundation data is translated in the UI or by importing FoTranslation .

Two Kinds of Text

SAP distinguishes configuration labels that consultants or administrators create (field labels, templates, home page tiles, e-mail templates) from system texts delivered with the language packs. Configuration labels are translated where they were configured. System texts are changed with Text Replacement or, more technically, Manage Languages.

Text Replacement

The Text Replacement tool in Admin Center customizes selected UI labels across the suite:

It uses two customizable language-pack keys: TEXT_REPLACEMENT_KEYS and ADMIN_TEXT_REPLACEMENT_KEYS .

By default it shows the default language. Other supported languages are listed under Select Language , and each language offers a different list of replaceable labels . English has many more than most other languages.

Custom labels override the defaults wherever the label appears.

It performs text substitution only , without adjusting grammar, so careless use can create linguistic errors.

In THR80's exercise, variants of "employee" are replaced with "associate", so My Employee File becomes My Associate File after logging out and in.

Manage Languages

Manage Languages overwrites UI label values in any supported language . Typical reasons are matching system text to company terminology, or correcting grammar or key terms while waiting for an SAP fix.

  • Limit or rule Value
  • Values you can overwrite per locale Up to 10,000 (default limit 25 , raised manually)
  • Custom language-pack CSV size 10 MB ; larger files time out
  • Text substitution syntax Needed to replace a word everywhere; otherwise replace each string

Prerequisites: in Provisioning Company Settings, Language Packs and Enable Manage Languages tool ; in RBP, the Text Replacement permission ( Manage System Properties ).

Working method from THR80:

Enable English Debug (Debugging section) and switch your language to it. The UI then shows the technical key, for example HOME_V4_ORGANIZATIONAL_UPDATES_Title .

For the target locale, choose Actions > Create Custom Translation , open it, search the key (case-sensitive), and choose Modify to enter your text.

For mass changes, download the default translation, edit the CSV (custom labels go in the second column ; since 1H 2023 there is no third column), and upload it.

Allow up to 24 hours for changes to appear.

Custom translation files are audited automatically . Failed audits show in the To-Do column with the keys to remove. A custom language pack is deactivated by clearing its active checkbox. The Manage Translations tab adds translations for predefined items such as People Profile help texts. Administrators can also create extended AI locales , UI labels translated by generative AI, which work like built-in locales and are available in the mobile apps.

Translation Projects

SAP's rules for implementation translations:

Finalize and test the configuration in the default language (English) before translation starts. Changes during translation make the workbook impossible to maintain.

The customer provides the translations and tests them. SAP SuccessFactors does not provide translation services, and consultants should not translate for the customer.

The consultant provides the translation workbook (from the SAP Partner Portal), lists every configured label in the English column, adds a column per language pack, and marks HTML in bold red so translators leave it intact.

One consolidated file comes back by the due date. The consultant configures translations in the test instance before production .

Minimize customization of system texts; heavy text replacement can slow the system.

Check the language matrices: not every module or feature is supported in every language.

Use a tool such as OpenOffice for CSV files, because Microsoft Excel can corrupt special characters.

Where labels are translated depends on their source. People Profile labels come from the Succession Data Model , Manage Business Configuration (the globe icon next to a label), the Picklist Center , or Configure People Profile . Language packs are enabled in Provisioning (Company Settings), and enabled languages then appear under Settings > Change Language .

Translating Foundation Data

Foundation object names and descriptions appear throughout the system, so they should display in the user's language.

MDF foundation objects and other generic objects: translations are part of the object's import template.

Legacy (XML) foundation objects: either use the Translations icon next to a translatable field in Manage Organization, Pay and Job Structures , or, for mass work, export the generic object FoTranslation in Import and Export Data , fill the language columns (determined by the language packs active in Provisioning), and import it with UTF-8 encoding.

SAP warns that FO translation has no incremental upload : the latest file overwrites the previous one, so the consolidated file must contain every language. After import, the system displays foundation data in this order:

  • the user's logon language (Settings > Change Language)
  • otherwise the default language set in Provisioning ( Company Settings > Default Language )
  • otherwise US English