Study guide

6.3 Configuring Legacy and MDF Foundation Object Definitions

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.3 Configuring Legacy and MDF Foundation Object Definitions

Key Takeaways Explain This Topic AI

Legacy (XML-based) foundation objects are configured in the Corporate Data Model; MDF-based foundation objects are configured in Configure Object Definitions.

In MDF tools, a legacy foundation object is simply called a Foundation Object, and any MDF-based object is a Generic Object.

Custom objects can be created only with MDF, not with the Corporate Data Model.

In an MDF foundation object, field criteria create cascading picklists, and Condition Field and Condition Values show or hide a field.

Codes and external codes of fields, objects, and records are case- and space-sensitive.

Last updated: September 2026

6.3 Configuring Legacy and MDF Foundation Object Definitions

Quick Answer: To change the structure of a foundation object (labels, visibility, required flags, custom fields, associations, rules), use the Corporate Data Model for XML-based objects and Configure Object Definitions for MDF-based objects. When the standard objects are not enough, for example an extra hierarchy level, create a custom generic object . That is only possible with MDF.

The Corporate Data Model

The Corporate Data Model lets you define labels for XML-based foundation objects and their fields, configure which fields are visible and required, use custom fields, customize associations, and assign business rules. It can be imported and exported from Provisioning or from Admin Center ( Import/Export Corporate Data Model ). You can change attributes and labels and add custom fields to meet customer requirements.

Worked Example: Relabel a Location Field

In Import/Export Corporate Data Model , export the model and save it in the folder that contains the DTD files.

Open it in an XML editor. Optionally, set the DOCTYPE to corporate-datamodel.dtd for local validation.

Go to the location element and its standardHours field, and change the label to Standard Weekly Hours .

Validate, save, and import the model through Import/Export Corporate Data Model .

In Manage Organization, Pay and Job Structures > Create New > Location , confirm the new label.

MDF-Based Foundation Objects

MDF-based foundation objects, such as Legal Entity and Job Classification , are customized in Configure Object Definitions . Search Object Definition , choose the object, then Take Action > Make Correction . Each field's Details section holds attributes such as labels and visibility. The records in Manage Data reflect the definition. As with the Corporate Data Model, you can change attributes, relabel fields, and add custom fields.

Terminology

Term Meaning

Foundation Objects The core structures SAP pre-delivers to hold company information. They can be XML-based or MDF-based.

Legacy Foundation Objects XML-based foundation objects, the HRIS elements in the Corporate Data Model. In MDF tools, a legacy foundation object is simply called a "Foundation Object".

  • MDF-Based Foundation Objects Foundation objects that have been migrated to the Metadata Framework
  • Generic Objects Any MDF-based object, standard or custom

Put simply: Foundation Objects = legacy (XML) FOs + MDF-based FOs , and Generic Objects = MDF-based FOs + all other MDF objects . This matters when you pick a data type for a field. In MDF, the data type Foundation Object points to a legacy FO such as Location, while Generic Object points to an MDF object such as Business Unit.

Custom Generic Objects

The standard foundation objects are customizable, but some requirements need more. A customer who needs more organizational hierarchy levels than SAP delivers creates a custom object , which is only possible with MDF, not the Corporate Data Model . Custom objects store additional company and people information. Their common characteristics:

  • they may or may not be effective-dated
  • they may or may not be secured (new custom objects must now be secured; Section 4.6)
  • they may or may not be associated with another object
  • they may or may not be available for self-service
  • Worked Example: Cascading Custom Fields on Legal Entity

ACE Corp wants two picklist fields, Scope and Region , on new legal entities. Region must depend on Scope and appear only when Scope = Global .

Step 1 – Picklists (Picklist Center or Import and Export Data)

  • Picklist Code Parent Values
  • Scope SCOPE none global (Global), local (Local)
  • Region REGION SCOPE AMER, EMEA, APAC, each with parent value global

Picklist codes and external codes are case- and space-sensitive . If you import, the legacy picklist ID must match the code.

Step 2 – Fields on the Legal Entity object (Configure Object Definitions)

  • Field Setting
  • cust_scope Data Type Picklist , Valid Value Source SCOPE , Label Scope ; placed before countryOfRegistration
  • cust_region Data Type Picklist , Valid Value Source REGION , Label Region
  • cust_region field criteria Source Field Name = parentPickListValue , Destination Field Name = cust_scope
  • cust_region condition Condition Field ID = cust_scope , Condition Values = global

Step 3 – Test in Manage Data. Create a legal entity such as Axis Germany (AXIS_DEU). When Local is selected, Region stays hidden. When Global is selected, Region appears with only the child values.

Two different mechanisms are at work:

Field criteria filter which values Region offers, based on the parent picklist value chosen in Scope.

Condition / Condition Values decide whether Region is shown at all .

Worked Example: Adjust Job Classification

To change the Job Classification structure, open it in Configure Object Definitions , choose Take Action > Make Correction , update only the requested attributes, and save. Verify in Manage Data > Create New > Job Classification . SAP's instruction to change only the highlighted values reflects good practice: leave other attributes alone.

Choosing the Right Path

  • Requirement Path
  • Relabel or add a field on Location, Pay Range, Event Reason, or Workflow Corporate Data Model (XML)

Relabel or add a field on Legal Entity, Business Unit, Division, Department, Cost Center, or Job Classification Configure Object Definitions

  • Add a new organizational level or company data structure Custom generic object in Configure Object Definitions
  • Show a field only for certain values MDF Condition Field / Condition Values

Filter one field's values by another Field criteria (MDF field or data model), plus an association where objects are involved (Section 6.4)