13.4 Integrating Position Management with Recruiting and Succession
Key Takeaways
- 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.
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.
Where is the integration between Position Management and Recruiting Management activated today?
What should be the first mapping in every THEN statement of the Map Fields from Position to Job Requisition rule?
A company manages positions in Employee Central and implements Succession Management. Which nomination method should it use?