Study guide
7.1 Person and Employment Objects, Effective Dating, and Employee Identifiers
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
7.1 Person and Employment Objects, Effective Dating, and Employee Identifiers
Key Takeaways Explain This Topic AI
HR data is split into person objects (such as personalInfo and homeAddress) and employment objects (such as jobInfo and compInfo).
personInfo (Biographical Information), phoneInfo, and emailInfo are not effective-dated; personalInfo, homeAddress, jobInfo, and compInfo are.
When a new effective-dated record is added, the previous record's end date becomes one day before the new start date; the current record ends 12/31/9999.
A person has one person-id-external but can have several employments, each with its own user-id.
The user-id cannot be changed once generated, while person-id-external can be changed in the Biographical template.
Last updated: September 2026
7.1 Person and Employment Objects, Effective Dating, and Employee Identifiers
Quick Answer: Employee Central stores person data (who someone is: name, birth data, addresses, national ID) separately from employment data (their job, compensation, and relationships). One person has one person-id-external and can hold several employments, each with its own user-id . Many objects are effective-dated , keeping history through start and end dates. Others, such as personInfo , are overwritten.
Features of EC HR Data
HR data in Employee Central:
- can be effective-dated
- connects with the rest of the SAP SuccessFactors HCM suite
- is reportable and exportable
- is controlled by Role-Based Permissions
- is configurable through HRIS standard , custom , and country-specific fields
The structures are defined in the Succession and Country-Specific Succession Data Models , or in Manage Business Configuration .
Person Objects
- HRIS element People Profile card Effective-dated CSF support Workflow support
- nationalIdCard National ID Card No Yes Yes
- homeAddress Addresses Yes Yes Yes
- personalInfo Personal Information Yes Yes (configured in globalInfo) Yes
- globalInfo Personal Information Yes Yes Yes
- personInfo Biographical Information No No No
- phoneInfo Contact Information No No No
- emailInfo Contact Information No No No
- imInfo Contact Information No No No
- emergencyContactPrimary Personal Contacts No No No
- personRelationshipInfo Dependents Yes Yes Yes
- workPermitInfo Work Permit Info No No Yes
Note that personalInfo's country-specific fields are configured in globalInfo , which displays in the same Personal Information card (Section 7.3).
Employment Objects
- HRIS element People Profile card Effective-dated CSF support Workflow support
- jobInfo Position and Organization Information and Job Details Yes Yes Yes
- jobRelationsInfo Job Relationship Yes No Yes
- employmentInfo Employment Details No Yes Yes
- compInfo Compensation Information Yes Yes Yes
- payComponentRecurring Compensation Information Yes No Yes
- payComponentNonRecurring Spot Bonus No No Yes
Add-on employment objects such as globalAssignmentInfo (expatriates, with home and host assignments) and pensionPayoutsInfo apply only when those Employee Central features are activated.
How Effective Dating Works
THR81 uses Marcus Hoff's address:
- Address Start date End date (not shown in the UI)
- 214 E 6th Ave, Conshohocken 3/20/2011 12/31/2019
- 315 W 10th Ave, Conshohocken 1/1/2020 12/31/9999
When the new record effective January 1, 2020 is added, a new row is created and the previous record's end date becomes one day before the new start date . The current record runs to 12/31/9999 . The History UI (clock icon) shows the change, with new values highlighted in green, old values struck through, and the submitting user and time stamp.
Non-effective-dated objects have no History (clock) icon . The system stores no start or end dates, so a change overwrites the existing record . The Biographical Information block ( personInfo ) is the classic example.
Field Types for Custom Fields
HRIS elements deliver standard, country-specific, and custom fields. Custom field types are:
- custom-string for text
- custom-long for integers
- custom-double for decimals
- custom-date for dates
- Employee Identifiers
user-id person-id-external username
This ID is… the system's unique identifier for employment data such as job history and compensation the system's unique identifier for personal data such as address, e-mail, phone, and national ID the ID a user signs in with
A user can have… several employments (main, concurrent, global), each with a unique user-id only one person-id-external, which maps person records to all of that person's employments several employments, each with a unique username
You can… assign it manually in the Basic Import template (required) assign it manually or have it system-generated assign it manually in the Basic Import template (required)
- Created when… a new employee is hired a new person is defined a new employee is hired
- Once generated you… cannot change it can change it in the Biographical template can change it
A User ID can also be generated from an MDF sequence with the rule scenario Generate Employee ID for Hire/Rehire (Section 5.2).
Putting It Together: Multiple Employments
Because person data is keyed on person-id-external and employment data on user-id :
A rehire with new employment keeps the person record and creates a new user-id. The previous employment stays isolated (Section 8.1).
In concurrent employment , one person holds more than one active employment, and in Position Management can hold several positions (Section 12.2).
In global assignments , employment data exists in home and host assignments, and the home assignment can be set to a status such as Dormant while the employee is away (Section 12.2).
Home address, national ID, and other person data are stored once , at person level.
Exam Tip
Look for the History clock icon to decide whether a block is effective-dated. Remember the special cases: employmentInfo is employment-level but not effective-dated, and jobRelationsInfo is effective-dated but has no country-specific fields.