Employee Central Fundamentals: Data Model, Foundation Objects, and Employee Records

Explanation

Employee Central (EC) is SAP SuccessFactors' cloud-based core HR module that acts as the single system of record for employee master data, organizational structures, and job/position information. Organizations migrating from SAP ECC HCM or legacy on-premise HR systems adopt EC to consolidate global HR data into one cloud platform that feeds talent modules (Recruiting, Performance & Goals, Compensation, Learning), payroll (Employee Central Payroll or third-party), and time management. The EC data model has two major layers. Foundation Objects (FOs) represent organizational and structural data that changes infrequently: Legal Entity, Business Unit, Division, Department, Location, Cost Center, Job Classification, Pay Grade, and Position (if Position Management is enabled). These are configured centrally and referenced by employee records rather than duplicated per employee, which keeps the data model normalized and easier to maintain at scale. Employee data itself is split across several key entities. The Employment record represents the legal work agreement and stays constant even as jobs change; a single person can have multiple concurrent employments (Global Assignment or Concurrent Employment scenarios). Person data (biographical/national ID information) is separated from Employment data, reflecting SAP's model where one person can have multiple employments but only one person record. Job Information carries time-sliced attributes such as position, job title, manager, department, and FTE percentage, and every change creates a new effective-dated record rather than overwriting history. Compensation Information, similarly time-sliced, stores pay components, and Job Relationships capture matrix managers, HR business partners, and other non-hierarchical reporting lines. A critical beginner concept is effective dating: nearly every EC entity is date-effective, meaning changes are stored as new records with a start date rather than updates that erase prior state. This enables historical reporting (e.g., 'what was this employee's department on January 1 last year') and supports future-dated transactions (e.g., a promotion effective next month can be entered today). Understanding effective dating early prevents confusion later when troubleshooting 'data insertion' vs 'data correction' behavior in the UI. EC is configured primarily through Admin Center tools rather than transports in the classical SAP sense. Foundation objects are typically set up via CSV import templates or the Manage Data feature, while employee-facing screens (Job Information, Personal Information, etc.) are governed by the Succession Data Model (Corporate Data Model + Country-Specific Data Model) which is an XML-based metadata framework defining fields, picklists, and field-level attributes such as visibility and required status. For a new consultant, the practical starting point is learning to read this data model: identify which foundation objects a client's org structure needs, understand how Job Information time-slices drive workflows, and recognize that almost every configuration decision in EC ripples into Position Management, Compensation, and payroll integration downstream.

Code example

-- Not an ABAP/API example; this is a conceptual excerpt of an EC Corporate Data Model (Succession Data Model) XML snippet for Job Information field configuration. <hris-field max-length="32" id="department" visibility="both" required="true" type="generic-object">  <label>Department</label>  <picklist-id>department_picklist</picklist-id>  <field-permission ROLE="EC_ADMIN" READ="true" WRITE="true"/>  <field-permission ROLE="MANAGER" READ="true" WRITE="false"/></hris-field> <!-- Example: Foundation Object CSV import header for Department -->-- externalCode,name,effectiveStartDate,status,costCenter,division-- DEPT_SALES_US,Sales US,2024-01-01,ACTIVE,CC1001,DIV_COMMERCIAL

Real project scenario

A mid-size manufacturing company migrating from on-premise SAP HCM to SuccessFactors Employee Central needs to model three legal entities across two countries. During the design workshops, the implementation team maps existing personnel areas and subareas from ECC to EC Foundation Objects (Legal Entity, Business Unit, Department, Location), then designs the Job Information time-sliced fields to capture position, cost center, and manager relationships. A key decision point is whether to enable Position Management, since the client's matrixed reporting structure influences whether positions or job-based assignment is more appropriate, directly affecting how downstream Compensation and Recruiting integrations will consume organizational data.

Common mistakes

• Treating Foundation Objects as static reference tables and forgetting they are also effective-dated, causing broken historical org reports when FO changes aren't dated correctly. • Confusing Person and Employment entities, especially in Concurrent Employment or Global Assignment scenarios, leading to incorrect assumption that one person equals one employment record. • Overwriting current Job Information instead of inserting a new effective-dated record, which destroys historical data needed for audits and analytics. • Underestimating the effort required to design the Corporate/Country-Specific Data Model early, causing rework once employee data volumes make field changes disruptive. • Assuming all countries use identical field requirements without checking Country-Specific Data Model overrides for legally mandated fields.

Best practices

• Map legacy on-premise org structures (personnel area/subarea, cost center hierarchy) to EC Foundation Objects during blueprint phase before any configuration begins. • Always confirm effective dates align with legal/payroll cutoff dates agreed with the client's payroll team. • Document Corporate Data Model decisions in a field inventory spreadsheet to track visibility, required status, and permissions before implementing in the Succession Data Model XML. • Validate Foundation Object relationships (e.g., Department to Cost Center to Legal Entity) with sample hierarchies before mass data loads. • Use Insert vs Correct actions deliberately and train HR administrators on the difference to preserve historical accuracy.

Interview angle

Interviewers often probe whether a candidate understands the distinction between Foundation Objects and employee data entities, and whether they can explain effective dating without conflating it with simple date filtering. Be ready to explain, with a concrete example, how a promotion effective next month is entered today without disrupting current records, and how this differs from a correction to an already-effective record.