Study guide

8.3 Mass Data Management for Job Information, Job Relationships, and Positions

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.3 Mass Data Management for Job Information, Job Relationships, and Positions

Key Takeaways Explain This Topic AI

Mass Data Management is a UI-based tool for bulk changes to Job Information, Job Relationships, and Position data without CSV files.

Administrators configure the UI in Manage Data with a Mass Changes Job Configuration: default filters, filterable fields, and editable fields.

Access needs Enable Mass Data Management plus the MassChangesJob and Mass Changes Job Configuration object permissions.

The optional minimum record limit for synchronous processing must not exceed 50, and up to 50 Job Information fields can be added.

Mass Data Management triggers all onSave and PostSave rules unless the rule context for mass changes is set to No.

Last updated: September 2026

8.3 Mass Data Management for Job Information, Job Relationships, and Positions

Quick Answer: Mass Data Management changes many records at once through a UI, without CSV files. It supports Job Information , Job Relationships , and Position data. An administrator first creates a Mass Changes Job Configuration in Manage Data , deciding which fields are default filters, which are filterable, and which are editable. Users then build, review, share, and submit mass change requests .

Why Use Mass Data Management

Organizational changes such as reorganizations or manager reassignments can affect many employees. Mass Data Management offers:

Advanced filtering to build a precise target group

Change review and collaboration: changes are highlighted, and drafts can be saved, edited, and shared with colleagues before submission

  • Audit and reporting: downloadable logs of executed changes
  • Field customization: extra fields can be made filterable or editable
  • Custom field editing
  • Permissions

Permission Where

Enable Mass Data Management Administrator Permissions ( Manage Mass Data Management ); opens the Mass Data Management page

  • MassChangesJob Miscellaneous Permissions; create and manage mass change requests
  • Mass Changes Job Configuration Miscellaneous Permissions; create and manage the UI configuration

For positions, users also need permission to view and edit the fields they change, especially generic-object fields.

Step 1: Configure the Mass Change UI

The UI is not pre-configured . In Manage Data > Create New > Mass Changes Job Configuration :

  • Setting Meaning
  • External ID / Name A unique identifier for the UI
  • Target Type The supported object, for example Job Information or Position

Min Record limit to Trigger Job Optional. Up to this many records, the request is processed synchronously (instantly); above it, asynchronously in the background. The value must not exceed 50.

Fields Add fields from the target object ( up to 50 Job Information fields ) and mark each as a default filter , filterable , or editable

Default filters appear in the request header. Filterable fields appear under Adapt Filters . Editable fields are the only ones users may change. For positions you can also add a matrix relationship through the association name. Position fields set to Not Visible in the object definition cannot be selected.

Step 2: Create a Mass Change Request

Open Mass Data Management and choose Create .

Choose the category:

  • Job Information: effective date, person type, legal entity, and a title
  • Job Relationship: relationship type, effective date, and a title

Use the default filters in the header, or Adapt Filters for more, then choose Go .

Select the target records and choose Edit . Only fields configured as editable can change.

Apply the changes and review the highlighted draft, which is saved automatically.

Submit . Watch the status, for example Processed Successfully , and download the log .

Limits

Job Information: up to 1,000 records per request.

Positions: you cannot mass change 1,000 or more. If a search returns more than 999 positions, the error "Too many matching records found" appears, and you can select at most 999 . For positions, Effective Date is the only mandatory filter , and up to 8 filters (besides Effective Date) are allowed.

Rules, Workflows, and Mass Changes

SAP highlights one behavior: all onSave and PostSave rules are triggered by Mass Data Management. If you do not want onSave rules such as workflow derivation to run for every changed employee, set the rule context for mass changes to No in Manage Business Configuration (Section 5.4). This keeps a reorganization of 800 employees from producing 800 approval requests.

Mass Data Management Versus Other Bulk Tools

Tool Best for

Mass Data Management UI-based bulk changes to Job Information, Job Relationships, and Positions, with filters, drafts, sharing, and logs

  • Import Employee Data File-based creation and updates of any EC entity, including partial imports (Section 8.2)
  • Import and Export Data File-based changes to MDF objects such as positions or foundation objects

Mass Change Run ( Manage Mass Changes for Metadata Objects ) Rule-based mass updates of positions, with Simulate and Run modes (Section 13.2)

Troubleshooting Mass Change Requests

Symptom Likely cause

The Mass Data Management page is missing Enable Mass Data Management is not granted, or the user has not logged out and back in

A field cannot be changed in the request It is not marked editable in the Mass Changes Job Configuration

A position field cannot be added to the configuration The field is set to Not Visible in the Position object definition

Unexpected approval requests after submission onSave rules such as workflow derivation ran; set the mass change rule context to No

  • A position search returns an error More than 999 positions matched; narrow the filters
  • Worked Example from THR79: Incentive Plan for Manager Positions

Some manager positions lack an Incentive Plan :

Confirm permissions: Mass Changes Job Configuration and Mass Changes Job (View, Edit, Import, Export) and Enable Mass Data Management .

Create configuration PositionMassChangesUI : targetGOType Position , minRecordLimitToTriggerJob 25 , fields effectiveStatus, externalName, division, jobCode (default filters), jobLevel (filterable and editable), and cust_IncPlan (editable).

In Mass Data Management, Create , rename the request Incentive Plan Change , filter Position Title = Manager , select all, Edit , set Incentive Plan = Manager, and Apply . The draft is saved.

Submit , refresh until Processed Successfully , and download the log to spot-check positions.