Study guide

7.2 Configuring the Succession Data Model with BCUI and XML

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.2 Configuring the Succession Data Model with BCUI and XML

Key Takeaways Explain This Topic AI

The Succession and CSF Succession Data Models must be uploaded before Manage Business Configuration can be used.

BCUI has no undo feature and creates no backup version; entities open in view mode until Take Action > Make Correction.

Person Types (such as Contingent Worker) can be added only in BCUI and define field attributes for a group of persons.

XML makes simultaneous changes across global and country-specific fields easier, and each upload creates a backup version (up to 100).

Any newly enabled field must be permissioned in RBP before a role can access it.

Last updated: September 2026

7.2 Configuring the Succession Data Model with BCUI and XML

Quick Answer: HRIS elements can be configured in Manage Business Configuration (BCUI) or directly in the Succession Data Model XML . BCUI changes are synced into the data model and vice versa. BCUI is convenient but has no undo and no version backup . XML is better for large simultaneous changes and keeps backup versions . Either way, a newly enabled field needs an RBP permission .

Manage Business Configuration for HRIS Elements

BCUI lets consultants and administrators update the Succession Data Model and the CSF Succession Data Model without XML . Prerequisites and cautions:

Both models must be uploaded during implementation before BCUI can be used.

After uploading them, run the Check Tool to find configuration issues.

BCUI has no undo feature and does not create a backup version when you make changes.

Entities open in view mode . Choose Take Action > Make Correction to edit.

In BCUI you can:

  • set the label and default label of an HRIS element
  • enable or disable the element
  • assign business rules to the element (Trigger Rules)
  • set a field label and enable or disable a field
  • open Details to set attributes such as field type, required, and visibility

The left panel has an Employee Central section (HRIS and country-specific elements) and an Employee Profile section (standard and userInfo elements). SAP improves BCUI almost every release with new validations.

Worked Example: Attachment on Biographical Information

To let users add an attachment to Biographical Information: open personInfo , choose attachment-id from the field drop-down at the bottom, label it Biographical Attachment , set Enabled = Yes , and check that Visibility = Edit in Details. Save and confirm the data model changes. No extra RBP step is needed here, because Biographical Information is permissioned as an entire block. Other fields need field-level permissions.

Person Types

A Person Type in BCUI defines a set of fields for a group of persons, such as contingent workers. For each person type you can set Enabled , Mandatory , and Visibility .

Person types can be defined for global and country-specific HRIS elements , and only for HRIS elements .

When a person type is created, all its HRIS fields are copied from the base element . You cannot add a field that is not in the base element.

Person types can be added only in BCUI. They have no corresponding entry in the data model XML.

Possible types, depending on enabled modules: Employee , Dependent (Dependents Management), Student (Learning), Candidate (Recruiting), Onboardee , and Contingent Worker .

Dynamic Group Filters

To use an Employee Central field as a criterion in permission and workflow groups, add it as a Dynamic Group Filter in BCUI: Filters > Dynamic Group Filters > DG Filters . Choose Details, select the HRIS element, then the HRIS field (it must be enabled and visible ), and save. You may need to log out and back in before the field appears in the People Pool categories.

A Generic Object as a Custom Field

Customers often want a generic object to behave like a foundation object in the employee file. THR81's parking example:

In BCUI, open the HRIS element (jobInfo) and add a custom-string field, for example custom-string4 labeled Parking , and enable it.

In Details, set Type of Reference Object = Foundation Object and Reference Object = the generic object's code , for example cust_parking. Codes are case- and space-sensitive.

If the object is filtered by an association, add field criteria . For example, Destination Field Value = location and Source Field Name = cust_toLocation.externalCode (Section 6.4).

Save and grant permissions for the new field under Employee Central Effective Dated Entities .

Test: change the location in Job Details and confirm that only the associated parking records appear.

The Check Tool includes a validation for existing or missing field criteria.

Configuring the Succession Data Model with XML

BCUI is valuable, but XML still has advantages :

It is easier to make simultaneous changes to many global and country-specific fields. BCUI often returns errors for such bulk changes.

Every data model upload creates a backup version , while BCUI records no history.

Rules for XML changes:

Download the latest version first. Use Export Succession Data Model in Admin Center, which also lists previous versions you can export or restore. Up to 100 previous versions are kept.

Save the file with your other models, increment the version number in the file name, and point the DOCTYPE to the local sf-form.dtd if your editor validates.

Do not change hris-element IDs or hris-field IDs.

Edit inside the right element. THR81 warns that a common mistake is placing a new field in the wrong hris-element.

Upload in Provisioning > Succession Management > Import/Export Data Model with a comment.

Changes made in BCUI are synced to the data model and vice versa. An attachment-id field enabled in BCUI appears in the exported XML with its label and visibility "both".

Worked Example: jobInfo Changes in XML

Enable supervisor-level by setting visibility to both and relabel it Management Level .

Add a custom field after the supervisor-level field and before is-cross-border-worker : <hris-field id="custom-string8" visibility="both">

  • <label>Additional Job Details</label>
  • </hris-field>

If a custom label does not show, add an en-US label line. After uploading, grant all permission levels (View Current, View History, Edit/Insert, Correct, Delete) for Management Level and Additional Job Details in Employee Central Effective Dated Entities . Then open the employee's Job Details, choose View all , and select Show empty fields to verify.

BCUI or XML?

  • Situation Better choice
  • A customer admin without Provisioning access changes a label BCUI
  • Many fields across several countries change at once XML
  • You need a restorable backup of each change XML (versioned)
  • Adding a Person Type BCUI only
  • Adding a Dynamic Group Filter BCUI