Configuration Basics: Provisioning, Data Models & Foundation Objects
After understanding what Employee Central is and why organizations adopt it, the next step is learning how Employee Central is configured.
In this blog, we’ll cover the core configuration building blocks that every SAP SuccessFactors consultant or HRIS professional must understand.
Why Configuration Knowledge Is Critical
Employee Central is not a plug-and-play system.
Proper configuration ensures:
- Accurate employee data
- Smooth HR transactions
- Secure access
- Compliance with local and global regulations
Incorrect setup leads to data issues, workflow failures, and reporting errors.
Step 1: Provisioning – The System Backbone
Provisioning is the backend system accessed only by:
- SAP partners
- Certified consultants
- SAP support
What Is Done in Provisioning?
Enable Employee CentralActivate features
Configure data models
Manage system-level settings
Provisioning controls what functionality is available in the instance.
⚠️ Direct customer access is normally not allowed for security reasons.
Step 2: Setting Up the Basics
Before detailed configuration, these basics must be completed:- Company information
- Date formats
- Time zones
- Languages
- Default currency
These settings affect data consistency across all modules.
Step 3: Creating a Super Admin User
A Super Admin user is required to:
- Configure permissions
- Access Admin Center
- Manage system settings
Best Practice
- Create a dedicated admin user
- Do not use personal accounts
- Restrict the number of super admins
This ensures better system security and control.
Step 4: Understanding Data Models
Data Models define what data exists and how it behaves in Employee Central.
Key Data Models
1. Corporate Data Model
- Defines employee data fields
- Controls field labels and visibility
- Connected to Foundation Objects and HRIS elements
2. Succession Data Model
- Controls People Profile data
- Determines how data appears on the employee profile
3. Country-Specific Corporate Data Model
- Handles localization
- Supports country-specific fields and legal requirements
Together, these data models form the data architecture of Employee Central.
Step 5: Foundation Objects (FO)
Foundation Objects define the organizational structure.
Common Foundation Objects
- Company
- Business Unit
- Division
- Department
- Location
- Legal Entity
They are referenced in:
- Job information
- Permissions
- Workflows
- Reports
Without properly configured Foundation Objects, Employee Central cannot function correctly.
Step 6: Legacy vs MDF Foundation Objects
Employee Central supports two types:
Legacy Foundation Objects
- XML-based
- Limited flexibility
- Slowly being phased out
MDF (Metadata Framework) Foundation Objects
- UI-based configuration
- Supports effective dating
- Supports workflows and rules
- Recommended by SAP
✅ Always use MDF Foundation Objects for new implementations
Step 7: Associations Between Foundation Objects
Associations define relationships between objects.
Example:
- Department → Business Unit
- Location → Legal Entity
Why associations matter:
- Logical data flow
- Correct reporting structure
- Permission derivation
Poor associations lead to incorrect organizational data.
Step 8: Configuring Company & Employee Central Settings
Two important areas:
- Company System Settings
- Employee Central Settings
These control:
- Search behaviour
- Duplicate checks
- UI behavior
- Feature enablement
Careful review is required before go-live.
Step 9: Introduction to HRIS Elements
HRIS elements represent employee records such as:
- Job Information
- Compensation Information
- Personal Information
Each HRIS element supports:
- Effective dating
- Event-based changes
- Workflow approvals
They are the transactional core of Employee Central.
Step 10: Events and Event Reasons (Overview)
Every employee transaction is driven by:
- Event (what happened)
- Event Reason (why it happened)
Examples:
- Event: Hire
- Event Reason: New Hire
Correct mapping ensures:
- Workflow triggers
- Accurate employment status
- Reporting consistency
(Deep dive coming in Part 3)
Common Configuration Mistakes to Avoid
❌ Skipping data model planning
❌ Using Legacy Foundation Objects
❌ Poor role-based permission design
❌ Missing country localization
❌ Hardcoding values instead of using picklists
Avoiding these saves time and rework.
Summary
In this part, we covered:
- Provisioning basics
- Initial system setup
- Data models
- Foundation Objects
- Core configuration concepts
These are the foundation blocks of any successful Employee Central implementation.
