Study guide

4.6 MDF Fields, Associations, Search, and Security

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.6 MDF Fields, Associations, Search, and Security

Key Takeaways Explain This Topic AI

Default maximum lengths are 255 for String and Translatable, 38 for Number, and 21 for Decimal.

Valid Values Source holds the code of the referenced picklist, generic object, or foundation object.

Composite associations create parent-child relationships; the child must use From Parent effective dating and can have only one parent.

Join By Column associations cannot be defined for custom MDF objects.

New custom MDF objects must be secured, and switching an existing object from No to Yes cannot be reversed.

Last updated: September 2026

4.6 MDF Fields, Associations, Search, and Security

Quick Answer: Each MDF field has a data type and attributes such as visibility , required , Valid Values Source , UI Field Renderer , transient , and Private or Sensitive Information . Associations link objects: Valid When for independent objects and filtering, Composite for parent-child records, and Join By Column (not for custom objects). Security sets whether an object is RBP-secured, its permission category, and optionally an RBP subject user field.

Fields

Field names must be unique within the object, including association names. Custom fields are prefixed cust_ automatically. Choose Details next to a field to see all attributes.

Data Types

Data type Notes

String / Translatable Text; translatable values can be entered per language. Default max length 255 .

Number / Decimal Integers or decimals, displayed per the user's locale. Default max length 38 and 21 .

  • Auto Number System-generated; should always be read-only
  • Boolean Yes or No
  • Picklist Values from an MDF picklist
  • Generic Object Reference to another MDF object
  • Foundation Object Reference to a legacy EC foundation object, such as Location
  • User Any active or inactive user
  • Date / DateTime / Time Dates and times
  • Attachment File upload
  • Data Source Pre-delivered fields only
  • Key Attributes

Valid Values Source: for Picklist, Generic Object, Foundation Object, and Data Source types. Enter the code of the referenced item: the picklist code, or an object code such as Country .

Required and Visibility ( Editable , Read Only , Not Visible ).

Default Value: not every data type supports it.

Hide Old Value: hides the struck-through previous value in effective-dated history.

Decimal Precision and Show Trailing Zeros for decimals.

Include Inactive Users: User fields only; default No.

UI Field Renderer: changes UI behavior. displayPickListWithoutExternalCode hides the code of picklist values, and displayGOWithoutExternalCode hides the external code of generic objects. These are pre-delivered values; misuse causes errors.

Transient: the value is not stored but calculated at runtime, usually by a rule. Age from date of birth is the classic example.

Help Text: translatable instruction shown with an icon.

Private or Sensitive Information: displays asterisks ( ***** ) until the user selects the field and confirms they want to see it.

Status: Active or Inactive. A customer-defined field cannot be set inactive.

Rules: field-level rules, triggered when the value changes ( onChange ).

Field Criteria: restricts possible values based on related fields, as in cascading picklists or filtered generic objects.

Condition / Condition Values: shows or hides the field depending on another field's value.

Database Field Name: read-only. For foundation-object filtering you look up the InternalCode database field here (Section 6.4).

Associations

Associations define a relationship between two objects: two generic objects, or a generic object and an EC foundation object. Multiplicity is One to One or One to Many . A Location has only one Geozone (one-to-one), while a Division can relate to many Business Units (one-to-many).

Type Behavior Example

Valid When Both objects have their own lifecycle. Used to build hierarchies and filter values. Division valid when a Business Unit is selected

Composite Parent-child: the child cannot exist without the parent . The child must use From Parent effective dating, and a child can belong to only one parent . Picklist values under a picklist; country-specific child objects of Legal Entity

Join By Column One-to-one reference between a source column on one object and a destination column on another. Not allowed for custom MDF objects. Pre-delivered objects only

Search Fields and Business Keys

Searchable fields define which fields are used to find records across the application. You can reference fields of associated objects, for example cust_country.code . For picklist fields, add .label , for example cust_IncPlan.label .

Business key fields are combinations of fields that uniquely identify a record.

Security

Security controls who can view, edit, or import and export an object or field, based on RBP roles.

Secured: all new custom MDF objects must be set to Secured = Yes ; saving a new object as not secured raises an error. Objects with From Parent dating and existing custom objects keep their setting. Changing an existing object from No to Yes is irreversible. SAP says not to use the Custom option.

Permission Category: the RBP area where the object appears, typically Miscellaneous Permissions .

RBP Subject User Field: any User-type field used to set the target population, so permissions can be granted for "records about my team".

CREATE Respects Target Criteria: makes the Create permission honor target restrictions. Position Management uses this (Section 11.2).

Since release 2605 , several standard objects are secured by default for new customers , for example Hire Date Correction, Fallback Event Reason Configuration, Alternative Cost Distribution, and the Document Generation objects.

Creating Records

After saving the definition, grant permissions (for example Miscellaneous Permissions > Company Car : View Current, View History, Create, Insert, Correct, Delete, Import/Export). Log out and in, then create records in Manage Data > Create New . Manage Data also shows records pending approval. When a field's data type changes, the system warns that existing data in that field will be deleted .

Worked Example from THR80: Company Car

  • Setting Value
  • Code comp_car (becomes cust_comp_car)
  • Effective Dating Basic
  • externalCode Data type User , label Employee Name (so the object can later appear as a profile card)
  • externalName Visibility Not Visible
  • Custom fields model (String, required), year (Number), purchase_date (Date, required)
  • Security Secured = Yes, Permission Category = Miscellaneous Permissions