Study guide
10.1 Employee Central Quick Actions and Internal Job History
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
10.1 Employee Central Quick Actions and Internal Job History
Key Takeaways Explain This Topic AI
EC Quick Actions are templates for common self-service actions that show only chosen fields, unlike the full Take Action screens.
Up to 15 templates can be configured for Transfer, Promotion, and Demotion, and up to 5 for other use cases; there are 33 predelivered core use cases.
A template's event reason always takes precedence over event reason derivation; if the template has none, ERD applies.
Rules assigned onSave, onChange, onView, and onPostSave run for all fields, even fields not included in the template.
Internal Job History is a display-only block filtered by a rule from the Display Internal Job History scenario, which has no THEN statement.
Last updated: September 2026
10.1 Employee Central Quick Actions and Internal Job History
Quick Answer: EC Quick Actions turn common self-service changes (change address, cost center, location, promotion, transfer, and so on) into templates that show only the needed fields . You configure them in Manage Data and grant them in RBP under Employee Central Quick Actions . Internal Job History is a read-only People Profile block that shows only selected events and fields, filtered by a business rule.
Why Quick Actions
The standard ESS and MSS Take Action menu shows all configured fields in a block. Quick Actions let you customize the fields displayed for each action , so an address change or a location change shows only what matters. They support changing, adding, and deleting core employee information.
Limits and Use Cases
A template must use one of SAP's predefined use cases . There are 33 predelivered use cases for core employee information, not counting Quick Actions for Positions (Section 12.3).
Up to 15 templates can be configured for Transfer, Promotion, and Demotion , and 5 templates for other use cases.
A template can include standard, custom, and country-specific fields. The maximum number of fields depends on the use case.
Each use case includes predefined fields. For example, Change Location defaults the Location and Timezone fields from Job Information.
Examples of use cases:
- addresses (typeahead service not supported)
- chosen name or legal name
- cost center, job, location, marital status
- emergency contacts, e-mail address, phone numbers
- contract end date, probation
- job code, job relationships, working time
- promotion, transfer, demotion, one-time payments
- adding attachments
- Creating Quick Action Templates
In Manage Data , create an Employee Central Quick Action Template and choose a use case . The defaults for that use case are pre-populated, and you can change them. The templates themselves are permissioned in Manage Business Configuration > Employee Central Quick Action Template for administrators.
Event reason: the system always takes the event reason from the template, even if Event Reason Derivation is set up. If the template has no event reason, ERD applies.
Grant employees and managers access in User Permissions > Employee Central Quick Actions .
Repeat for other scenarios, within the 15 and 5 template limits.
Behavior to Remember
Workflows and ERD are supported.
Rules assigned as onSave, onChange, onView, and onPostSave are supported. The system executes rules for all fields, even fields not included in the template.
Field properties such as visibility and mandatory cannot be changed by the template.
To keep employees away from manager actions, do not grant them permissions to manager-specific templates.
- Where Users Find Quick Actions
- Home Page > Manage My Data (employees)
- Home Page > Manage My Team > Actions (managers)
- Employee quick cards: Quickcard > Employee Details > Show Actions and Links
- the Take Action menu in the employee profile
- Joule , which uses the configured EC Quick Action templates when prompted
- Internal Job History
The Job Information History lets HR and administrators insert, edit, and delete records without workflows, so it is usually restricted. Sometimes a wider audience needs to see selected history, for example a manager who should see an employee's promotions only. The Internal Job History block is a display-only , filtered view of job history.
In THR81's example, managers see Marcus Hoff's historical promotions and no other events. The People Profile shows only Job Title, Pay Grade, Business Unit, Employee Class, and Division .
Configuration Steps
Create a rule using the Display Internal Job History scenario.
In the IF statement, select the event reason(s) to use as the filter, for example Promotion.
You cannot configure a THEN statement in this scenario.
In Configure People Profile , find the Internal Job History block, drag it into a section, choose the fields to display, and link the rule . Save.
Grant Employee Widgets > Internal Job History permission.
Choosing the Right Tool
Requirement Solution
Managers change an employee's location with only two fields shown Quick Action template, Change Location use case
A special promotion reason, independent of ERD Set the event reason in the Promotion template; it overrides ERD
Show managers promotion history without History access Internal Job History block with a Display Internal Job History rule
- Let managers change a position's location from their team page Quick Actions for Positions (Section 12.3)
- Worked Example: Designing a Transfer Template
A company wants managers to transfer employees with a short form showing only the new department, location, and cost center:
In Manage Data , create an Employee Central Quick Action Template with the Transfer use case. Keep its default fields, add the required ones, and leave the event reason empty so ERD decides, or set a fixed reason if policy requires one.
Grant managers Use permission on this template in Employee Central Quick Actions . Do not grant it to employees.
Remember that rules on hidden fields still run. A propagation rule on location, for example, still sets the timezone even if Timezone is not on the form.
Test as a manager from Manage My Team . The workflow derived on save should appear before submission.
Exam Tips
A template's event reason wins over ERD . A blank template reason lets ERD decide.
A field left out of a template is still processed by rules . Hiding it does not stop propagation or validation.
Internal Job History is read-only and driven by event reasons in the rule's IF .