Study guide
6.1 The Four Employee Central Data Models, DTDs, and Upload Sequence
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
6.1 The Four Employee Central Data Models, DTDs, and Upload Sequence
Key Takeaways Explain This Topic AI
Employee Central uses four XML data models: Corporate, Country-Specific Corporate, Succession, and Country-Specific Succession.
During implementation they are uploaded in Provisioning in this order: Corporate, CSF Corporate, Succession, CSF Succession.
Both Corporate data models can later be imported and exported in Admin Center; the Succession models can be downloaded there but imported only in Provisioning.
Every data model change must comply with its DTD; you cannot add an element, field, or attribute the DTD does not define.
SAP recommends hiding an unneeded field rather than deleting it, and setting visibility to none before deleting if you must.
Last updated: September 2026
6.1 The Four Employee Central Data Models, DTDs, and Upload Sequence
Quick Answer: Employee Central is defined by four data models . The Corporate Data Model (XML-based foundation objects) and its country-specific version, and the Succession Data Model (HRIS elements for person and employment data) and its country-specific version. An implementation uploads them in Provisioning in the order Corporate → CSF Corporate → Succession → CSF Succession .
The Employee Central Core Structure
An HR information system stores employee data and organizational data . In SAP SuccessFactors, organizational details such as department, division, and legal entity are Foundation Objects . Some foundation objects are MDF objects configured in Configure Object Definitions . Others are XML-based and maintained in the Corporate Data Model . Employee-specific details, such as date of birth, national ID, job title, and salary, live in HR objects . Access is controlled by RBP, and self-service lets employees and managers maintain their own data.
What a Data Model Controls
Data models describe how data elements are structured, their properties, and their relationships. When configuring them you can:
- set the visibility of a field (THR81's example hides Date of Death in personInfo)
- define custom labels and fields (for example relabeling Place of Birth as City of Birth )
- define relationships among foundation objects
- set the order of fields
- set a picklist for a field
Every change must comply with the Document Type Definition (DTD). You cannot add an element, field, or attribute the DTD does not define. SAP recommends hiding a field rather than deleting it . If a field must be deleted, set its visibility to "none" before deleting it .
The Four Data Models
Data model Defines Example
Corporate Data Model XML-based foundation objects, such as Location and Pay Range . Legal Entity, Business Unit, Division, and similar objects have moved to MDF. Location fields and associations
Country-Specific Corporate Data Model (CSF CDM) Country-specific fields for XML-based foundation objects Country-specific corporate address formats
Succession Data Model (SDM) HRIS elements for employment data (job classification, salary, compensation) and person data (date of birth, home address, national ID) jobInfo, personalInfo
Country-Specific Succession Data Model (CSF SDM) Country-specific HRIS fields US EEO and FLSA fields; national ID formats that vary by country
Corporate data falls into four categories: organization-related , pay-related , job-related , and others . THR81 files the workflow configuration object under Others .
Where Each Model Is Imported and Exported
Model Initial upload Later import Later export
Corporate Data Model Provisioning Provisioning or Admin Center ( Import/Export Corporate Data Model ) Provisioning or Admin Center
CSF Corporate Data Model Provisioning Provisioning or Admin Center ( Import/Export Country/Region-Specific XML for Corporate Data Model ) Provisioning or Admin Center
- Succession Data Model Provisioning Provisioning only Admin Center or Provisioning
- CSF Succession Data Model Provisioning Provisioning only Admin Center or Provisioning
Customer administrators without Provisioning access manage Succession Data Model elements through Manage Business Configuration instead of XML. Both import paths offer backup versioning . You can enter a comment for each uploaded version, see the date, operator, and comment of previous versions, download earlier versions, and restore one.
Linking a Data Model to Its DTD
To validate a model in an XML editor, replace the SAP-internal repository URL in the DOCTYPE line with the local DTD file name, stored in the same folder:
- Data model DTD
- Succession Data Model sf-form.dtd
- CSF Succession Data Model country-specific-fields.dtd
- Corporate Data Model corporate-datamodel.dtd
- CSF Corporate Data Model country-specific-fields.dtd
For real projects, download the standard data models and DTDs from the SAP Software Download Center . The course files are abridged versions.
The Upload Sequence
In Provisioning > Succession Management , upload the four models in this order:
- Corporate Data Model ( Import/Export Corporate Data Model XML )
- CSF Corporate Data Model ( Import/Export Country/Region Specific XML for Corporate Data Model )
- Succession Data Model ( Import/Export Data Model )
- CSF Succession Data Model ( Import/Export Country/Region Specific XML for Succession Data Model )
Enter a comment for versioning each time. The Corporate models may also be uploaded from Admin Center if the administrator has the right permissions. If an upload shows "An application error occurred", log out of Provisioning, clear the browser cache, and check whether the model was uploaded despite the error before trying again.
Uploading the models also makes related permissions appear. For example, Employee Central Effective Dated Entities becomes available once the Succession Data Models are uploaded, and Manage Foundation Object Types once the Corporate Data Models are uploaded (Section 7.5).
Worked Example: Deconstructing a Data Model Change
THR81's first data model interaction uses the personInfo (Biographical Information) element:
Date of Death is not visible, so its field has visibility set to none .
Place of Birth is relabeled City of Birth by changing the field's label.
The same file could attach a picklist, reorder fields, or add a custom field, but only elements and attributes that the DTD allows.
Exam Tips
If a task needs a new Location field, it is a Corporate Data Model change, possible from Admin Center. If it needs a new Job Information field, it is a Succession Data Model change: use BCUI in the instance, or Provisioning for XML.
Never edit IDs of HRIS elements or fields. Change labels, visibility, and required flags.
After enabling any new field, grant its RBP permission or nobody will see it.