Study guide

6.2 Foundation Objects: Organization, Pay, and Job Structures

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

6.2 Foundation Objects: Organization, Pay, and Job Structures

Key Takeaways Explain This Topic AI

XML-based foundation records are maintained in Manage Organization, Pay and Job Structures and imported with Import Foundation Data.

MDF-based foundation records are maintained in Manage Data and imported with Import and Export Data.

A Legal Entity cannot span more than one country, and its country controls the country-specific fields on employee job, employment, and compensation data.

Cost Center is not part of the organizational hierarchy; it is usually assigned to the legal entity and sometimes to a department.

Job Function groups job classifications for reporting and does not display on Job Information by default.

Last updated: September 2026

6.2 Foundation Objects: Organization, Pay, and Job Structures

Quick Answer: Foundation Objects (FOs) hold the organization, pay, and job structures that employee records reference. XML-based (legacy) FO records are managed in Manage Organization, Pay and Job Structures and imported with Import Foundation Data . MDF-based FO records are managed in Manage Data and imported with Import and Export Data . Set up foundation data before employee data, because employee records depend on it.

Two Kinds of Data

THR81 divides EC data into:

Employee (HR) data: name, date of birth, nationality, job title, salary, and compensation.

Organization data: departments, divisions, legal entities, job classifications, and pay structures. In SAP SuccessFactors these are Foundation Objects .

Foundation objects are standard, pre-delivered structures that can be customized. Their fields can reference picklists and other XML or MDF objects, which appear as drop-downs. Each FO has standard fields and custom fields , and several have country-specific fields .

Tools for XML-Based and MDF-Based Objects

  • Task XML-based (legacy) FO MDF-based FO
  • Configure structure (labels, custom fields, associations) Corporate Data Model Configure Object Definitions
  • Create, edit, delete records Manage Organization, Pay and Job Structures Manage Data
  • Import records in bulk Import Foundation Data Import and Export Data

Permissions that control foundation objects: Manage Foundation Objects , Manage Foundation Object Types , MDF Foundation Objects , and Metadata Framework (Section 7.5).

For any bulk action, the import file must match the object's configuration, so always download a fresh template first .

Effective Dating of Foundation Data

Most foundation objects are effective-dated . The first record marks when the object was created, and each change starts a new record on its effective date. For each record an administrator can:

  • insert a new record with a past, present, or future effective date
  • make a correction
  • permanently delete an entry

A record can be used only from its effective start date . THR81's example: the legal entity ACE Germany (ACE_DEU), created on 01/01/1990, can be used for employee records on or after that date. The same rule explains a common error. You cannot associate a location with a legal entity if the location record is older than the legal entity record.

Organization-Related Foundation Objects

Object Key facts

Legal Entity The company where the employee is hired and has a contract. It cannot span more than one country. Its country controls the country-specific data on the employee's Job Information, Employment Details, and Compensation Information. It maps 1:1 to a company code in EC Payroll, SAP HCM, and S/4HANA. The legal entity on a Position must match the one in Job Information. It is the highest object usable in the organization hierarchy.

Business Unit A business area or line of business of the company (not geographical)

Division A level below the business unit. It has a standard Parent Division field for hierarchy levels, and associations can link it to one or more business units.

Department Similar to division, with a Parent Department field. It can be associated with divisions, and one department can belong to several divisions.

Cost Center Where the employee's costs are assigned in payroll and finance. Not part of the organizational hierarchy. Usually assigned to the legal entity, sometimes to the department. It has a Parent Cost Center field and can store external IDs for financial systems.

Location Address of each physical office. It can be associated with a Geo Zone and Legal Entities . International address formats come from the Corporate Address in the CSF Corporate Data Model.

Location Group Optional geographical grouping of locations, used mainly for EEO reporting in the USA

Geo Zone Groups locations. It has an Adjustment Percentage for cost-of-living pay-range adjustments and is used mainly with the Compensation module.

SAP notes that in SAP SuccessFactors the position structure exists independently of the organizational structure . Position Management is covered in Chapters 11–13.

Pay-Related Foundation Objects

Pay data provides remuneration information such as pay components , pay frequency , pay group , pay grade , and pay range . A pay range has built-in associations, such as to a pay grade. Companies with enterprise or union agreements can use the Pay Scale Structure .

Job-Related Foundation Objects

Job Classification: stores all job codes and their information, such as supervisor level, job level, regular/temporary, full/part time, employee class, job title, and pay grade. It can have country-specific fields.

Job Function: sorts job classifications by the work performed; for example Developer and Developer Manager belong to Engineering. By default it is not displayed on Job Information and is used for reporting.

Worked Example from THR81

ACE Corp opens a Berlin office and enters the storage business:

  • Task Tool
  • Create Business Unit Storage (ACE_STOR) Manage Data (MDF)

Create Location Berlin (DU_BER) with location group, timezone, geozone, legal entity, and address Manage Organization, Pay and Job Structures (XML)

Import Cost Centers 500–502 Import and Export Data (MDF): download template, fill, validate, check Scheduled Job Manager, import

  • Create Job Classification Storage Hardware Engineer (STHWEN) Manage Data (MDF)
  • Create two Pay Ranges for the US and Germany Manage Organization, Pay and Job Structures (XML)

This shows which objects are MDF-based (Business Unit, Cost Center, Job Classification) and which are XML-based (Location, Pay Range).

Propagation from Foundation Data

Once foundation data exists, propagation rules fill parts of the employee record automatically, which reduces errors. Choosing the Engineer (ENG) job classification during a hire can fill the pay grade and weekly hours. Propagation rules are covered in Section 5.3.