Study guide

4.3 Picklist Center, Cascading Picklists, and the Employee Central Master Picklist

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.3 Picklist Center, Cascading Picklists, and the Employee Central Master Picklist

Key Takeaways Explain This Topic AI

Picklists, picklist versions, and picklist values cannot be deleted in the Picklist Center; they can only be deactivated.

A cascading picklist links child values to parent values, such as states that depend on a country.

Employee Central's UI does not respect MDF picklist effective dating.

The EC Master Picklist file contains picklist values only; create the picklists before importing their values.

ZIP imports of the Master Picklist support only full purge, while CSV imports support incremental load and full purge.

Last updated: September 2026

4.3 Picklist Center, Cascading Picklists, and the Employee Central Master Picklist

Quick Answer: A picklist is a configurable set of options, usually shown as a drop-down. Administrators manage MDF picklists in the Picklist Center , with the Picklist Management and Picklist Mappings Set Up permissions. Picklists and values cannot be deleted, only deactivated . EC projects load SAP's Master Picklist values early through Import and Export Data .

Why Picklists Matter

Picklists keep data clean by limiting what users can enter. Employee Central uses them everywhere: marital status, event, employee status, address types, country-specific values, and custom fields. A picklist can also have a parent-child relationship (a cascading picklist ). The State picklist depends on the Country selection, so users see only states of the chosen country.

Picklist Fields

  • Field Meaning
  • Code Unique business key of the picklist (the equivalent of the legacy picklist ID)
  • Parent Picklist The picklist whose selection filters this one
  • Display Order How values are listed, for example alphabetically or numerically
  • Name Unique name, such as Address Type
  • Status Active or inactive
  • Effective Start Date A picklist can have different value sets for different start dates
  • Legacy Picklist ID Editable after migration to MDF; must be unique across all picklists

Two notes from THR80 matter in practice:

At this stage, the Employee Central UI does not respect MDF picklist effective dating. A value added "from January 1" may still appear earlier in EC screens.

Instance sync of picklists is not allowed when the combinations of external code and legacy picklist ID differ between the source and target instance. Edit the legacy ID so they match.

Picklist Value Fields

  • Field Meaning
  • External Code MDF external code, a unique business key, for example state_Alabama
  • Non-unique External Code Legacy external code; can be blank or duplicated
  • Parent Picklist Value The parent value, for example United States for state_Alabama
  • Label What users see, for example Alabama

When legacy picklists are migrated to MDF, an optionId is generated for MDF picklist values. For migrated legacy options, the existing optionId is kept in a mapping table.

Maintaining Picklists

Create: in the Picklist Center, choose + , enter the code, name, status, and effective start date (SAP's exercises use January 1, 1900), then add values with + .

Deactivate, never delete: picklists, versions, and values cannot be deleted.

Translate: use the globe icon on a value's label, or import translations.

Export: Import and Export Data > Export Data runs a job you track in Scheduled Job Manager . Download the package when the job completes. The export always contains all records for all effective dates , so it may differ from what the Picklist Center shows for today.

Import: Import and Export Data > Import Data , validated and tracked in Scheduled Job Manager.

Codes and external codes are case- and space-sensitive .

The Employee Central Master Picklist

Besides enabling Provisioning settings and uploading the data models, an EC implementation must create picklists. SAP provides an Employee Central Master Picklist file (MDF ZIP) on the SAP Software Download Center . It contains:

  • HRIS picklist values used in Employee Central
  • Miscellaneous picklist values used in the talent modules
  • Delta picklist values introduced by the latest enhancement release
  • Other picklist values for components such as Global Benefits and Time Management
  • Import Considerations

Some picklists and values may already exist in an EC-enabled system.

The file contains picklist values only, not the picklists . Create a separate import file for the picklists first , then import the values.

The file is large. Trim it to the values relevant to the implemented countries.

Import options: a ZIP import supports full purge only . A CSV import supports both incremental load and full purge .

Remove duplicates: do not import picklists or values that already exist unless you run a full purge.

Validate: the Check Tool finds invalid picklist references in personal and employment elements.

Import Steps in THR81

In Import and Export Data , choose Download Template for the generic object Picklist with Include Dependencies = No , then download the Picklist Values template the same way.

Copy Code, Legacy Picklist ID, Name, Status, and Effective Start Date from the master file into the picklist template and save it as CSV UTF-8 .

Import it with Import Data , encoding UTF-8 , and the file locale that matches the CSV. Validate first, then import.

Prepare the values template (id, effectiveStartDate, values.externalCode, values.nonUniqueExternalCode, values.label.defaultValue, values.label.en_US, values.status) and import it the same way. Translations are optional.

Confirm the result in the Picklist Center.

With Excel, set the list separator to a comma and open CSVs through the text-import wizard with UTF-8. Alternatively, use a text-based tool such as OpenOffice or LibreOffice.

Country-Specific Gender Values

THR81 notes that country-specific gender values are set up in the Global Information (globalInfo) element. The values "Unknown", "Undeclared", and "Others" can be added to Personal Information through the Upgrade Center . If you use country-specific gender values, leave the gender field in Personal Information blank for consistency.

Linking Picklists to Fields

Standard or HRIS elements: choose the picklist in the field details in BCUI, or add the picklist ID in the data model.

MDF fields: set the data type to Picklist and enter the picklist code in Valid Values Source (Section 4.6).