Skip to content
FAST SAP SOLUTIONS®Discuss a project

START HERE · NO PRIOR TOPIC KNOWLEDGE NEEDED

What it is. Why it matters.

An import loads employee data into SuccessFactors Employee Central. Incremental Load and Full Purge have different effects on existing records, so the import mode must match the intended change.

Completely new to SAP?

Manufacturers use SAP to connect work such as buying components, recording inventory, planning production, shipping equipment and accounting for costs. SAP S/4HANA is an enterprise resource planning system: it connects these activities through shared business data.

SAP HR applications manage employee-related records and processes. A record’s subject, validity dates and access permissions all matter before it is read or changed.

A transaction code, or t-code, is a shortcut to a task in classic SAP GUI. Fiori apps provide another way to work. Names and screens depend on the product and release; you do not need a live system to learn the concepts in this guide.

Original editorial vector illustration for Employee Central imports: Choose Incremental Load or Full Purge deliberately
Original FSS editorial vector illustration. Conceptual artwork, not an SAP interface or customer-system evidence.
Scope and source-review notes

Scope and evidence

Source review by FAST SAP SOLUTIONS® editorial. This badge describes our editorial review; it does not represent SAP certification or independent endorsement.

SuccessFactors Employee Central Import Employee Data and documented mass-import behavior. Actual purge scope, keys, partial-import support, rule behavior and sequence depend on the selected entity, use case and tenant release.

Reviewed relevant official SAP indexed documentation excerpts on 14 November 2026. Examples, identifiers, amounts and expected observations are illustrative; no customer SAP execution was performed. Transaction availability, labels and results depend on the installed release, deployment and local configuration.

A MANUFACTURING EXAMPLE

Preserve history during a plant workforce import

Add a change or replace history?

Existing records: Relevant employee history. Incremental intention: Add or update selected records. Full-purge intention: Replace relevant supplied scope. Before import: Confirm intended mode and data
What to notice: The import mode affects existing history and must match the actual business change.Original annotated example with illustrative values. This is not an SAP screen or a result from a customer system.
Read the example values
Existing records
Relevant employee history
Incremental intention
Add or update selected records
Full-purge intention
Replace relevant supplied scope
Before import
Confirm intended mode and data
Words you’ll meet in this guide
Employee record
Stored information about a person’s employment.
Validity
The dates during which a record applies.
Payroll
The process that calculates an employee’s pay.
API
A defined interface through which programs exchange data or request actions.
Preview the practical steps

SEE THE CONNECTION

See it in a simple example.

A small example to make the idea concrete.

Existing employee records → Chosen import mode → Resulting history. Conceptual diagram for Employee Central imports: Choose Incremental Load or Full Purge deliberately.
Apply the idea: A manufacturer imports a future workforce change and must preserve the relevant history of factory employees.An illustrative example, not a live SAP screen. The connections show how to think about the topic; they are not instructions to change a system.
  1. Preserve history during a plant workforce import

    A manufacturer imports a future workforce change and must preserve the relevant history of factory employees.

  2. Match the import mode to update versus replacement intent

    Incremental Load and Full Purge express different operations on existing Employee Central data.

  3. Define the entity and actual replacement scope

    Before preparing a file, identify the exact entity, employee/employment keys, effective-date and sequence requirements, and the documented scope affected by the chosen mode.

  4. Use a current template, not a remembered spreadsheet

    Download the supported template for the actual entity and tenant configuration.

Reading map · FSS editorial. The sections below explain each part in detail.

Found this useful?

Share this guide with your network, or leave a like.

LinkedIn WhatsApp

Your like is saved in this browser.

Explore Knowledge Hub

Discuss Your SAP Project

Your enquiry is sent through this website and used only to respond to your request.