SOFTENANT LEARNING GUIDE · SAP SUCCESSFACTORS

SAP SuccessFactors Employee Central: Data, Dates and HR Workflows

Employee Central is the core HR part of SAP SuccessFactors. To understand it, separate the organisation’s reference data from a person’s information, then follow how an employment change takes effect over time.

Technical references: SAP Employee Central overview; SAP foundation objects; SAP Employee Central architecture. Examples below are original fictional training scenarios; available screens and behaviour depend on your tenant configuration.

Three kinds of data to recognise

A department definition is shared reference data. A particular employee’s department assignment belongs to that employee’s job information. If a department cannot be selected, check the reference record and its validity for the transaction date before creating an alternative spelling.

Effective dates: a transfer is a timeline

Consider fictional employee E100, currently in Customer Support. An approved transfer to Operations takes effect on 1 October. A view as of 15 September should still reflect the earlier assignment; a view as of 2 October should reflect the transfer, provided the transaction has completed correctly.

Do not assume that every entity in Employee Central behaves identically. Many records track history, but some objects use different structures. Check the entity before deciding whether to insert a new dated record or correct an existing one.

A correction fixes an error in an existing record; a new dated change represents a business event taking effect at another point in time. In a practice workbook, explain which is intended before changing the data. A future transfer should not be disguised as a correction to the original hire.

How positions, rules and workflows connect

A position describes an organisational seat; an employee can occupy it. In a fictional team, “Support Analyst P200” may exist while recruitment is still in progress. Once someone joins, distinguish the position’s data from that person’s employment record. Synchronisation and position behaviour depend on the configured process.

A business rule evaluates a condition and performs an assigned action. An approval workflow identifies who needs to review a proposed change. Permissions determine who can view or carry out the transaction. These controls answer different questions and should be investigated separately.

Build a small Employee Central learning case

1. Define the requirement. E100 transfers to Operations on 1 October; HR must approve the change.
2. Prepare the reference map. List the legal entity, department, job classification, position and manager. Note which values already exist and are valid on the relevant date.
3. Define the access matrix. Identify the initiating manager, HR reviewer and an unrelated manager who should not see the record.
4. Write expected results first. Specify the before-date and after-date department, approval recipient and fields that should remain unchanged.
5. Run the authorised training scenario. Use fictional records in a permitted sandbox. Record the transaction and approval outcome.
6. Reconcile the outcome. Review history, the selected date and a small report sample. Investigate a mismatch before treating the exercise as complete.

Without system access, prepare the requirement, timeline and test matrix as a design exercise. Label it as a design exercise; do not claim the configuration was executed.

When the expected change does not appear

Begin with the employee and employment identifier, then check the date used by the screen or report. Inspect whether the change is pending approval and whether the new record actually exists. Next, check the viewer’s permissions and any relevant rule or position behaviour. A report with the wrong date can look incorrect even when the employee history is right.

Save a one-page explanation of the requirement, test evidence and any unresolved limitation. For deeper configuration study, use the guides below instead of adding unrelated modules to this first exercise.

Continue learning

• Role-based permissions guide
• Business rules and triggers
• Employee data imports
• Position Management guide
• Employee Central interview questions