1.2 SAP SuccessFactors Suite, Platform Capabilities, and Employee Central Core
Key Takeaways
- SuccessFactors was founded in 2001 by Lars Dalgaard, and SAP acquired it in February 2012.
- Platform capabilities fall into three areas: Administration, Technology, and User Experience.
- Employee Central drives core HR and is effective-dated; the Employee Profile drives talent processes and holds snapshot data.
- Employee Central uses four data models: Corporate, Country-Specific Corporate, Succession, and Country-Specific Succession.
- SAP recommends a fit-to-standard, gap-fit approach and changing only what must change.
1.2 SAP SuccessFactors Suite, Platform Capabilities, and Employee Central Core
Quick Answer: SAP SuccessFactors is a cloud HCM suite built on a shared platform (Administration, Technology, User Experience). Employee Central (EC) is the suite's HR information system and system of record. It is effective-dated, is built on person and employment records, and drives core HR transactions. The Employee Profile supports talent and learning processes with snapshot data.
A Short History
SuccessFactors was founded in 2001 by Lars Dalgaard as a software-as-a-service performance management product. It grew into business execution software, and SAP acquired it in February 2012, renaming it SAP SuccessFactors. The suite later added recruitment marketing and posting, onboarding, and workforce analytics. By 2019, releases included functionality updates for the mobile app, the Employee Central Service Center, and recruiting, plus architectural enhancements and an SAP Fiori-based user interface. Its modules cover the traditional HR pillars — recruiting, learning and development, performance management, and compensation — plus onboarding, time and attendance, workforce planning, and people analytics.
The Platform Layer
THR80 treats the platform as the building block beneath every module. SAP groups platform capabilities into three areas:
| Administration | Technology | User Experience |
|---|---|---|
| Security: Admin Center, Identity Management, Proxy Management, Role-Based Permissions | Data Protection and Privacy | User Interface: Action Search, Home Page, Mobile, People Search, People Profile, Photos, Theming |
| Monitoring: Execution Manager, Check Tool | Integration/Services: Attachment/Document Management, Intelligent Services, Intelligent Services Center | People Analytics: Report Center, standard report templates |
| Upgrade Management: Upgrade Center | Metadata Framework: Job Profile Builder, Picklist Center, standard MDF objects |
These capabilities are not module-specific. The same RBP framework, Check Tool, and MDF tools support Employee Central, Position Management, and the talent modules. That is why the C_THR81 learning journey starts with the platform academy.
Employee Central Versus the Employee Profile
THR81 opens by contrasting Employee Central with the Employee Profile that THR80 introduces:
| Question | Employee Central | Employee Profile |
|---|---|---|
| What does it do? | Drives core HR administration, transactions, and processes | Drives talent and learning processes |
| Is it effective-dated? | Yes | No – snapshot data |
| What is it based on? | Person and employment records | Employment records based on User ID |
| Where does data come from? | Imports and manual entry, including self-service | With EC: data synchronized from EC plus talent data. Without EC: a subset imported from an external HRIS |
| Multiple employments? | Yes | Yes |
| Data models used | Succession and Country-Specific Succession Data Model (HRIS elements); Corporate and Country-Specific Corporate Data Model | Succession Data Model (standard elements) |
With Employee Central enabled, the talent modules still read the Employee Profile. HRIS synchronization copies EC data into those legacy user tables (Section 7.4).
Key Features of Employee Central Core
SAP lists these core capabilities:
- Effective-dated transactions: process future-dated and retroactive HR changes and report by effective date.
- Self-service: users view and update information they have permission for.
- Status and change tracking: event reasons record why employment data changed, from hire to termination.
- Workflow automation: route, approve, and track transactions from initiation to execution.
- Mass changes: update Job Information or job relationships for a selected population.
- Alerts and notifications: To-Do alerts and emails when a period is about to end.
- Country-specific information: country-specific data structures.
THR81 also describes the EC Core structure as Foundation Objects (organization, pay, and job structures), HR objects (person and employment data), Role-Based Permissions, self-service, and transactions.
Mapping the EC Core Structure to Its Tools
Each part of the EC Core structure has its own configuration home. Knowing that home is the fastest way to start a practical task:
| EC Core component | What it holds | Where you configure it |
|---|---|---|
| Foundation Objects | Legal entities, business units, divisions, departments, locations, job classifications, pay structures | Corporate Data Model (XML-based objects) or Configure Object Definitions (MDF-based objects) |
| HR objects | Person data (for example date of birth, national ID) and employment data (for example job, compensation) | Succession Data Model and its country-specific version, or Manage Business Configuration |
| Role-Based Permissions | Who may view or edit which data for which target population | Manage Permission Groups and Manage Permission Roles |
| Self-service | Employee and manager changes to their own or their team's data | RBP plus workflows |
| Transactions | Hires, job changes, terminations, driven by events and event reasons | Event reasons in Manage Organization, Pay and Job Structures, business rules, workflows |
Keep this map in mind as the guide moves from the platform (Chapters 1–5) to Employee Central Core (Chapters 6–10) and Position Management (Chapters 11–13).
Configuration Best Practices from THR80
SAP gives implementation consultants this working method:
- Start with pre-configuration in the customer's test environment to speed up understanding.
- Approach decisions as fit-to-standard with gap-fit analysis, not ground-up process design.
- Change only what must be changed to close real gaps.
- Work in iterations: gap-fit, design, documentation, configuration, testing, and validation.
- Coordinate design and testing across workstreams to catch integration impacts.
- Keep project and configuration documentation current and shared.
- Train the customer's system administrators early and hand them administrator-level configuration.
- Prepare customer-specific cutover documentation for the move to production.
How This Shapes the Exam
A system-based assessment grades configuration in a real tenant, so the platform/EC split matters in practice. If a task asks for a new organizational level, you need to know it is an MDF generic object built in Configure Object Definitions. If a talent report shows stale department data, you need to know that EC is the source and HRIS sync feeds the Employee Profile.
Which statement correctly contrasts Employee Central with the Employee Profile?
In SAP's platform capability map, where does the Check Tool belong?
A customer wants to redesign every HR process from scratch before configuring Employee Central. What does SAP's THR80 guidance recommend instead?