Study guide

8.2 Importing New Employees and Updating Employee Data by Import

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

8.2 Importing New Employees and Updating Employee Data by Import

Key Takeaways Explain This Topic AI

Import Employee Data creates new employees and updates existing records; always download a fresh template first.

Every import file must include the business keys, such as person_id_external, start date, and address type for addresses.

New employees are imported in the order Basic, Biographical, Employment Details, Job Information, Compensation, and Personal Information.

In a partial import, &&NO_OVERWRITE&& keeps the stored value, while an empty field is replaced by null.

Records are deleted by import with the DELETE operation for some entities and DELIMIT for others, such as addresses and job relationships.

Last updated: September 2026

8.2 Importing New Employees and Updating Employee Data by Import

Quick Answer: Import Employee Data creates and updates Employee Central records from CSV templates. Always include the entity's business keys . New employees are imported in the order Basic Import → Biographical Information → Employment Details → Job Information → Compensation Information → Personal Information . Updates can be partial with &&NO_OVERWRITE&& , and records are removed with DELETE or DELIMIT , depending on the entity.

Ways to Add Employees

Employees can be added through the Add New Employee wizard, Manage Pending Hires , FTP, connectors, and Import Employee Data , which you reach through Action Search. Imports suit data migration and bulk changes. SAP's Employee Central Mass Changes guide describes each import file.

Business Keys

Each record is identified by a unique combination of business keys :

  • the person ID (person_id_external) for person objects, or the user ID (user_id) for employment objects
  • sometimes a record type for the entity
  • for effective-dated entities, the start date and possibly a sequence number

Examples: Addresses are person-level, effective-dated, and typed (home, mailing), so the keys are person_id_external + effective_start_date + address_type . Biographical Information is not effective-dated and has one record per person, so the key is just person_id_external . Always include the business key fields and values in the import file.

Import Permissions

In RBP, enable Employee Central Import Settings > Import Employee Data .

Grant import rights for the chosen entities in Employee Central Import Entities .

Imports are also limited to the importing user's target population .

Importing New Employees

THR81's exercise imports three employees with six templates, each downloaded from Import Employee Data ( Download Template , choose the entity, select all fields, Generate Template ):

  • Basic Import: status, user ID, username, names, gender, e-mail, manager, HR, job code, business unit, division
  • Biographical Information: date of birth
  • Employment Details: hire date
  • Job Information: event reason (New Hire, HIRNEW), company, job code, business unit, division, manager
  • Compensation Information: pay group
  • Personal Information: first and last name

New employees must be imported in exactly that order. Changes to existing records can be imported without regard to sequence .

Other practical rules:

Use codes and IDs, not names or labels. The system cannot read labels. People are referenced by USERID , for example the manager.

Download a fresh template so it contains the latest configured fields, and confirm your columns match it.

Use Employee Export to look up user IDs.

Validate first, then import. Check each job in Scheduled Job Manager . There may be a delay before new employees are searchable or appear in the Org Chart.

Tips to Prevent Failed Imports

Enter all required fields and confirm each value is valid.

Make sure every field enabled for an HRIS element is valid (see the Data Object Tables handbook).

Check field configuration. A picklist or object field must have its picklist or object configured on the HRIS field.

If a failed row has an End Date that does not match the end date in the system, the import errors. The system calculates end dates from the event start dates, so remove the value and import again.

When importing batches in parallel, keep all effective-dated records of an employee in one CSV file .

  • Updating Existing Data
  • Purge Types

When updating, choose Incremental Load (add or change the rows in the file) or Full Purge (replace the entity's data for the employees in the file). THR81's e-mail exercise uses Full Purge for Email Information, and its Job History update uses Incremental Load. For a small number of records, incremental load is usually the right choice.

Partial Imports with &&NO_OVERWRITE&&

A partial import is an incremental load that updates only some fields. Put &&NO_OVERWRITE&& in every field that should keep its stored value, except business keys.

Fields with &&NO_OVERWRITE&& keep the value in the database .

Empty fields are replaced with null. This is the classic mistake.

Entities that do not support partial import : Work Permit Info , Job Relationships , Dynamic Role , and Workflow .

After THR81's partial Job History import, the newest record in the employee's history shows Source: Import .

Deleting Data by Import

In an incremental load, choose the operation type DELETE or DELIMIT , depending on the entity:

DELETE DELIMIT

Compensation Information, Email Information, Emergency Contact Information, Job History, National ID Information, Non-recurring Pay Component, Personal Information, Phone Information, Social Accounts Information, Work Permit Info Addresses, Global Information, Job Relationships, Person Relationships, Recurring Pay Component

For MDF records , Delete removes parent object records, Delimit removes a specific child record from a parent, and Clear removes all records of a child object from the parent.

Imports and Business Rules

To have event reasons derived during imports , enable the permission Enable Business Rules for selected entities for imports. If the import file contains an event reason, it takes precedence over derivation. If the column is empty, the onSave derivation rule sets it (Section 9.4). Cross-entity rules run on import only if they are onSave rules (Section 5.4).

Centralized Services

THR81's summary notes that Centralized Services regulate how data is processed in Employee Central. They apply consistent validations and follow-up processing to saves from the UI, History, and imports. The Diagnostic Tool can trace Centralized Services transactions (Section 10.2).