Study guide
4.2 Manage Business Configuration and Succession Data Model XML Fundamentals
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
4.2 Manage Business Configuration and Succession Data Model XML Fundamentals
Key Takeaways Explain This Topic AI
The Succession Data Model defines the data structure shown in the People Profile, and BCUI edits it without XML.
Manage Business Configuration is a Provisioning opt-in feature with Employee Central (HRIS) and Employee Profile (standard) sections.
Disabling a standard element in BCUI removes it from the Succession Data Model and from later XML exports.
Provisioning keeps up to 100 backup versions of the Succession Data Model, but changes made in BCUI are not versioned.
Well-formed XML has correct syntax; valid XML is well-formed and also follows the DTD.
Last updated: September 2026
4.2 Manage Business Configuration and Succession Data Model XML Fundamentals
Quick Answer: The Succession Data Model (SDM) is an XML file that defines employee data elements. Its standard elements feed the Employee Profile, and its HRIS elements hold Employee Central data. Manage Business Configuration (BCUI) lets administrators change it in Admin Center without editing XML. Some changes still need XML, so consultants must handle the file safely: back it up, validate it against its DTD , and version every upload.
The People Profile and the Succession Data Model
The People Profile is the presentation layer . What it can display is defined by the Succession Data Model , for example First Name, Last Name, and Customizable Fields 1–15. The SDM is named after the Succession module it was first built for, but it is now at the core of SAP SuccessFactors. Employee Central, Succession, and Performance Management all use elements defined in it.
Manage Business Configuration (BCUI)
BCUI is a Provisioning opt-in feature. Once enabled, it shows the configurable elements on the left and lets you maintain them on the right. A check mark on the left means an element is in use.
Employee Central section: HRIS elements and their country-specific versions (Chapter 7).
Employee Profile section: standard elements and userInfo elements used by the talent modules.
Typical changes to standard elements in BCUI:
- change labels and add translations (globe icon)
- enable fields
attach a picklist . Select the element, open the Picklist drop-down, and save. For example, custom02 is relabeled Matrimonial Status and linked to ecMaritalStatus .
- change visibility
- make fields required
Two cautions:
Disabling a standard element deactivates it and removes it from the SDM , so it no longer appears in any XML download or export. Test before disabling anything in production.
Enabling a standard element does not make it visible until the matching permission is granted. Employee Profile fields are permissioned in the Employee Data category of RBP.
Why XML Still Matters
Before BCUI, every data model change needed a partner or SAP Support, because the XML files live in Provisioning. BCUI removed much of that dependency, but some changes must still be made in XML . Consultants therefore need to read and edit the SDM.
XML Vocabulary
- Term Meaning
- Tree structure XML starts with a root element and branches into parent and child elements
- Element Describes the data it contains; can have attributes and sub-elements
- Attribute A named value inside an element's tag, always in quotation marks
- DTD (Document Type Definition) Declares which elements and attributes are allowed and where
Validation Well-formed XML has correct syntax. Valid XML is well-formed and follows the DTD.
Well-formed XML needs a root element, closing tags, properly nested elements, quoted attribute values, and correct case, because XML is case-sensitive.
Editing Rules for the SDM
Download the SDM from Provisioning (Succession Management > Import/Export Data Model ) or export it from Admin Center with Export Succession Data Model . The export needs the Export Succession Data Model permission under Admin Center Permissions .
Open it in an XML editor such as Oxygen, Notepad++, or XMLPad (Windows only). Change the DTD reference from SAP's internal repository path to a local DTD file in the same folder (for the SDM, sf-form.dtd ), so the editor can validate.
The SDM is a single file that overwrites on upload. Keep the original as an untouched backup and save each change as a new version (Save As, for example _V2).
Upload through Provisioning > Succession Management > Import/Export Data Model and add a comment for the version.
Version Control
Provisioning can keep backup versions of the data models and restore a chosen version. Comments are required during import, and earlier versions can be downloaded. The system keeps up to 100 SDM versions ; the oldest are deleted when the limit is reached. Version control does not record changes made in Manage Business Configuration. It covers only models loaded through Provisioning.
The Three Primary SDM Elements
Standard elements: single-value fields shown in the Employee Profile, such as firstName, lastName, and custom01–custom15 . The data model does not define their display order.
Background elements: field mappings to the SM_Background table (multi-row talent data).
Custom filters: turn one or more of the 15 custom fields into filters for reporting and similar tasks.
A standard element can be linked to a picklist directly in XML with a picklist tag. THR80's exercise relabels custom01 as Region with the region picklist and custom02 as Marital Status , then verifies the result in the Latest People Profile.
How This Connects to Employee Central
THR81 builds on these basics. HRIS elements are edited in BCUI or in the SDM and its country-specific version (Sections 7.2–7.3). HRIS sync maps EC fields into these standard elements so the talent modules stay current (Section 7.4).