Study guide
13.4 Integrating Position Management with Recruiting and Succession
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
13.4 Integrating Position Management with Recruiting and Succession
Key Takeaways Explain This Topic AI
The Recruiting integration is enabled only in Position Management Settings > Integration; the Provisioning switch is deprecated and cannot be turned on.
Two rules are needed: Derive Job Requisition Template and Map Fields from Position to Job Requisition, each limited to one rule.
Requisition templates for the integration must include numberOpenings and std_position_obj or positionNumber, which the system fills in.
The field mapping rule should check that the job requisition is in Draft mode in every THEN statement.
With Employee Central Position Management, Succession should use only MDF position-based nominations.
Last updated: September 2026
13.4 Integrating Position Management with Recruiting and Succession
Quick Answer: With the Recruiting integration, users create standard (headcount-relevant) job requisitions from a vacant position in the Position Org Chart or My Team Positions . A rule derives the requisition template , and a rule maps position fields onto the requisition. It is enabled in Position Management Settings > Integration . With Succession , use the MDF Position nomination method , so Succession and Position Management share the same position object.
- What the Recruiting Integration Does
- Create a job requisition from a position in the Position Org Chart
- Determine the job profile for the requisition automatically
Show assigned requisitions or requisition requests on the position tile and more requisition data in the side panel
Use the rules engine to derive the requisition template and to map fields
Use the job scheduler to create requisitions automatically from request objects, for example for future-dated requests
- Assign the hired candidate from Pending Hires to the position linked to the requisition automatically
- Prerequisites and Setup
Both Position Management and Recruiting Management must be enabled and configured. Then:
Permissions:
Admins: Manage Position > Access Position Management Settings ; Metadata Framework: Configure Object Definitions , Manage Positions , Configure Business Rules , Manage Data .
Recruiting users: Miscellaneous Permissions > Position : View Current and View History; Manage Position : Access Position Organization Chart, View and Create Job Requisition, Select Job Requisition Template.
Activate: Position Management Settings > Integration > Recruiting Management > Use Recruiting Management Integration = Yes. The Provisioning switch is deprecated, and turning it on is no longer allowed. To check whether an older integration is active, run the Check Tool check SFAPI-based Recruiting Integration has been disabled (PositionUseDeprecatedRCMIntegration).
Create two rules in Configure Business Rules and register them on the Integration tab.
Rule 1: Derive the Job Requisition Template
Scenario Derive Job Requisition Template in Recruiting Integration . It is required to create requisitions from the Position Org Chart.
IF: conditions on any position attribute, such as company or job code.
THEN: the template to use.
ELSE: optional but recommended; raise a message that no requisition can be created for this position.
Only one rule can derive the template, so all conditions for all active templates go into it.
Register it under Rule for Deriving Job Requisition Template ID .
Rule 2: Map Fields from Position to Job Requisition
Scenario Map Fields from Position to Job Requisition in Recruiting Integration .
IF: which template(s) need which mappings. Use OR for templates with the same fields and separate IF/THEN branches for different ones.
THEN: Position Requisition Mapping Field Mapping expressions. The first mapping in every THEN should check that the requisition is in Draft mode , so mappings are filled only while the requisition is a draft.
Map object fields to object fields, operator fields to operator fields, or use built-in logic, for example Hiring Manager = the manager of the position .
Only one mapping rule exists, so cover every active template. Templates used in rule 1 should also appear here.
Register it under Field Mapping Rule to Create Job Requisition from Position .
The templates must contain numberOpenings and std_position_obj or positionNumber . You don't map these; the system fills them in.
Best Practices
Approvals for starting the requisition happen on the position , so the Recruiting route map can be simpler and used for notifications.
Use the same foundation or generic objects in Recruiting as on the position, to keep field types consistent.
Make mapped fields read-only on the requisition, except Location .
Create the requisition in Draft status.
Prevent requisitions for staffed positions by raising an error in the rule when the position's To Be Hired status is No .
Using the Integration
Managers can create a requisition (a future date creates a request ), view requisition details, and delete a request from My Team Positions , with the same Manage Position permissions. In THR79's exercise, a requisition created from a To Be Hired position shows a Job Requisition – pre-approved icon. The Hiring Manager is the incumbent of the parent position, filled by the mapping rule, and company, business unit, and location are pre-filled. Mapping picklist fields such as a custom incentive plan needs extra configuration (a picklist mapping object and the Lookup() function; KBA 2361220).
Integration with Succession Management
Succession finds emergency replacements for critical positions and builds successor pipelines. With Employee Central Position Management, Succession benefits from:
- the MDF Position nomination method , which is leading practice
- the position setup and field options inside Succession tools
- sharing the Position object with Position Management and the Position Org Chart
- multiple incumbents
- consistent position data across Succession, Recruiting, Job Profile Builder, and SAP Fieldglass
Caution: if Employee Central manages your positions, use only MDF position-based nominations . The same position object is shared by Employee Central and Succession Planning.
Related Succession tools include the Position Tile (incumbents and successors by position; only with MDF position nominations, and positions can be created and edited there), the Lineage Chart , Talent Pools (unrelated to Recruiting's talent pools despite the name), and Talent Search .
Implementation order matters. If Position Management goes live before Succession, the setup is straightforward. If Succession is already live, extra steps may be needed, especially moving to MDF position nominations. With Recruiting also integrated, external candidates can be nominated as successors after enabling Allow succession planners with recruiting candidate search permissions to nominate external candidates in Nominations Setup . SAP still recommends creating requisitions from the Position Org Chart .