Study guide

4.5 Metadata Framework Enablement and Object Definition Settings

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.5 Metadata Framework Enablement and Object Definition Settings

Key Takeaways Explain This Topic AI

The Metadata Framework (MDF) extends SAP SuccessFactors with Generic Objects; Position Management, Time Off, and BCUI are built on it.

Administrators can create 250 custom MDF objects by default, and the limit can be raised to 400 in Provisioning.

MDF is enabled in Provisioning with Enable Generic Objects and Enable the Attachment Manager.

Effective dating options are None, Basic, Multiple Changes Per Day, and From Parent (for child objects).

Pending Data set to Yes keeps changes invisible until the workflow is approved.

Last updated: September 2026

4.5 Metadata Framework Enablement and Object Definition Settings

Quick Answer: The Metadata Framework (MDF) lets consultants and customers extend SAP SuccessFactors with Generic Objects (GOs) . MDF objects come with import and export, workflow, rules, reporting, OData, and RBP security. You build an object's structure in Configure Object Definitions , add logic with business rules , maintain records in Manage Data , and optionally design screens in Manage Configuration UI .

What MDF Is and Why EC Depends on It

MDF can create custom objects and maintain existing objects , link objects, and build hierarchies of objects. SAP uses it for many applications. Position Management , Time Off , and Manage Business Configuration are all built on MDF, and so are the MDF foundation objects such as Legal Entity, Business Unit, Division, Department, Cost Center, and Job Classification. Every MDF object shares the same capabilities: import and export, UI, OData API access, workflows, rules, reporting, and RBP.

Limit: administrators can create 250 custom MDF objects by default. The limit can be raised to 400 in Provisioning > Company Settings .

MDF Layers

Object Definition: where the object is built. Behavior, fields, associations, and security are set here.

Business Rules: logic to default data, set values, raise messages, and trigger actions on save or delete.

Data: create, import, and manage records ( Manage Data , Import and Export Data , OData).

Configuration UI: alternative screens with different layouts, labels, text, and links ( Manage Configuration UI ).

Enabling MDF

In Provisioning > Company Settings :

  • Enable Generic Objects (the basis of MDF and of the rules engine)
  • Enable the Attachment Manager

For workflows and rules on MDF data, also enable Employee Central Foundation Objects , Effective Dated Data Platform , and Enable Business Rules for Workflow Derivation .

MDF Permissions

In Manage Permission Roles > Administrator Permissions > Metadata Framework :

  • Permission Allows
  • Configure Object Definitions Managing object definitions
  • Access to Business Rule Execution Log Tracing rule execution
  • Configure Business Rules Creating and editing rules
  • Manage Data Creating and editing records
  • Manage Sequence Automatic sequence numbers, for example for externalCode generation
  • Import Permission on Metadata Framework Import and export of generic objects and rules

Record access for individual objects is granted in Miscellaneous Permissions or another category the object is assigned to. There you choose View, Edit, Import, and Export, plus Field Level Overrides that make specific fields No Access or Read Only . Access to Non-RBP Secured Objects covers objects with Secured = No .

Record-Level Permission for Import and Export

For a secured object, you can require explicit Import or Export permission at record level. In Manage Data , create or edit the Object Configuration for the object and set Enable Record-Level Permission Check on Import and/or …on Export to Yes .

Object Details in Configure Object Definitions

Open Configure Object Definitions > Create New: Object Definition , or search an existing one and choose Take Action > Make Correction .

  • Setting Options and rules
  • Code Unique identifier; custom objects are prefixed cust_ automatically

Effective Dating None (one record, overwritten), Basic (several records, one per date), Multiple Changes Per Day (several records per date), From Parent (child objects inherit the parent's dating and cannot be maintained on their own)

API Visibility Not Visible (default), Read Only , Editable (OData read and write)

Status Active or Inactive. An object cannot be set inactive while records exist or while another active object references it.

MDF Version History No, Delete History (audit only deletes), or Complete History (audit create, insert, update, delete)

  • Default Screen A Configuration UI shown in Manage Data
  • Label / Description Display name and summary

API Sub Version V1.1 hides technical system fields from OData and is recommended for new objects. No Selection behaves like V1.1.

Subject User Field A User-type field that determines workflow routing

Workflow Routing A workflow run for every operation. Requires Employee Central Foundation Objects in Provisioning.

  • Pending Data Yes keeps changes invisible until approval
  • To Do Category Where approvers see the item; used when Pending Data is Yes
  • Object Category Uncategorized, Configuration, User Transactional, Non-User Transactional, or Technical

Do not confuse effective dating with audit . Audit ( MDF Version History ) can be enabled regardless of the dating option.

MDF Data Management and Auditing

MDF data volume objects ( MDF Audit Data Volume , MDF Association Data Volume , MDF Transactional Data Volume ) help administrators understand data volumes and decide when to purge.

The MDF Change History Data report under Change Audit Reports covers all root-level MDF data except configuration objects such as object definitions, picklists, and object configurations. It may first need enabling in Manage Audit Configuration .

Position Management Preview

THR79 applies these settings to the Position object. Position uses Basic effective dating, is secured in Miscellaneous Permissions, and must have Pending Data = Yes if workflows are used. SAP recommends triggering position workflows through business rules rather than Workflow Routing at object level (Section 11.4).