Study guide

4.4 User Data File, Employee Import, and User Management Tools

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.4 User Data File, Employee Import, and User Management Tools

Key Takeaways Explain This Topic AI

The User Data File (UDF) is a CSV used to add or change basic user data; rows 1 and 2 (system ID and label) must be preserved.

The UDF is matched on USERID: unknown USERIDs create new users, and users missing from the file are not changed.

The Employee Import tool is available only in instances without Employee Central.

With Employee Central, basic user data comes from Import Employee Data > Basic User Import and HRIS sync, not the UDF.

Employee import privileges come from Manage Employee Import, or from RBP after enabling it in Platform Feature Settings.

Last updated: September 2026

4.4 User Data File, Employee Import, and User Management Tools

Quick Answer: The User Data File (UDF) is a CSV of basic user data (status, IDs, names, manager, HR, department, and so on). In instances without Employee Central , it is imported with Employee Import . With Employee Central , basic user data is maintained in EC and synchronized to the user tables by HRIS sync . Importing the UDF there can overwrite EC-sourced data, so EC customers use Import Employee Data instead.

Who May Import Employees

Import privileges do not necessarily come from RBP . The tool Manage Employee Import lets you find a user, define the target population (divisions, departments, locations), and choose Save Definition For Selected Users . SAP's exercise notes that the save sometimes needs repeating even after a success message. To manage the privilege through RBP instead, activate Enable Control on Employee Import in Role-Based Permissions in Platform Feature Settings .

Ways to Manage User Data

User Data File: a CSV created manually or produced by the HRIS. Import it manually in Admin Center or automate it through FTP . Only records with changes or additions are updated, and many users can change at once.

Admin Center links (manual entry): quick one-off changes for one or two users. Changes made this way are overwritten by the next import if the CSV is not updated too.

Exporting the UDF

Use Employee Export (Action Search). Best practice is to download the current UDF before every change , because a stored local copy may be out of date after manual or automated updates. Options:

Valid users only: active users only

Short format: only system fields: required fields only. Do not use it if you need compensation data.

  • Character encoding for languages such as Chinese or Japanese
  • Export as a batch process for large populations, with a notification when ready

Save changes under a new file name so the original remains a backup.

UDF Structure

Rows 1 and 2 (system ID and label) must be preserved along with all required columns. Row 2 labels can be renamed during configuration.

  • Required field Rule
  • STATUS active or inactive; all users on the initial load are active

USERID Unique system identifier. Cannot be changed once set. Avoid leading zeros and special characters such as & or #.

  • USERNAME Login name; must be unique
  • FIRSTNAME / LASTNAME Employee name
  • GENDER M or F; required for the Writing Assistant
  • EMAIL Business e-mail used for notifications
  • MANAGER Manager's USERID; top-level people use NO_MANAGER
  • HR HR representative's USERID; use NO_HR if none
  • DEPARTMENT Also a standard filter
  • TIMEZONE Used for time stamps

The standard filter fields are DEPARTMENT, DIVISION, and LOCATION . More filters are created by a consultant during implementation. Job Code is optional and links a user to competencies through job roles. There are 15 custom fields .

File Behavior on Import

The system updates only records whose USERID matches an existing user.

An unknown USERID is treated as a new user and added.

Existing users missing from the file are not changed.

To inactivate a user, export, set STATUS to inactive, and import. Inactivation freezes the account , and it can no longer be changed.

Employee Import

Employee Import is available only in systems without Employee Central enabled . Choose the file, decide how initial passwords are assigned, and optionally select:

  • Send welcome e-mail to new users (the template must be enabled, otherwise a warning appears)
  • Validate Manager and HR fields

Process inactive Employees: updates inactive employees' data. Employee Import cannot be used to import new inactive users.

Re-activate purged users

Choose Validate Import File , fix errors, then Import User File . An e-mail reports results. Manager changes also send a document-transfer report. Import files are scanned, and fields containing cross-site scripting are skipped and reported.

Other User Management Tools

Manage Users ( Manage Employees > Update User Information ) adds users and edits one user at a time: manager changes with form transfer, status, and name.

Extended user information has three types: personal information (one-to-one), trend information (one-to-many ratings), and background information (one-to-many). Export backups before importing, especially before an overwrite import. The background import option Overwrite the data of users in the import file affects only users in the file.

Choosing the Right Tool

  • If you want to… Users managed in Employee Central Users not managed in EC
  • Add or update basic user info in the UI Employee and Manager Self-Service Manage Users
  • Add or update basic user info by file Import Employee Data > Basic User Import Employee Import
  • Download basic user info Employee Export Employee Export

Add or update extended user info Import Extended User Information, Import Employee Data > Extended Import or Background Import Import Extended User Information

  • Validate user data Check Tool > User Management Check Tool > User Management
  • The Employee Central Warning

THR81 is explicit. With EC, some talent modules still rely on the user tables, but HRIS sync fills them from EC. Do not update user data by importing the UDF , from the UI or a scheduled job, and do not use the Basic Import to update the legacy tables directly. Doing so can overwrite EC data and create inconsistencies . If that happens, run an HRIS sync job to restore the EC values (Section 7.4).