SuccessFactors Employee Central Position Management is an important piece not only within Employee Central but also within SuccessFactors suite as it links other SF solutions like Recruitment Management, Succession Planning , Job Profile Builder etc. This makes it important to understand the recommendations around Position Management configuration.
I would like to highlight some points below that hopefully will aid in better understanding of the solution configuration:
Would like to highlight that there is a Category called “Position Management” under Configure Business Rules.
This category has following rule scenarios:
If you have to create a rule for one of these scenarios , for e.g., Position Synchronization, Job requisition template derivation, Field mapping required for Position to RCM integration etc., then It is recommended to select appropriate scenario from this list. This pulls the right base objects for creating the rule.
Rules for synchronization/integration etc also need to be updated against correct fields in “Position Management Settings” else system will not execute them.
The reason for this setting is that if you also use Job Information to Position sync and if an attribute value is changed in Job Information of the incumbent, which syncs back to position as per the rule specified, then it can lead to creation of new positions in the background, without an approval process, if system doesn’t find a vacant position under the parent position.
Global Settings maintained under Position Management Settings are used by the system only when Position Types are not used.
Similarly, pay attention to field “Synchronize position matrix relationships to job relationships of incumbents?”. This field is by default “Not Visible” on UI. It is recommended to change visibility settings for this field to “Editable” and maintain desired value else synchronization of relationships from Position to incumbent will not happen if Position Types are being used.
Detailed recommendations for Position Management configurations are available in the recently released Implementation Design Principles document. Do check it out!
SAP SuccessFactors Employee Central Position Management: Design Considerations and Recommendations
The document provides leading practice recommendations while configuring SF EC Position Management and also details risks of taking alternative approach.
For structured guidance and advice on how to address challenging customer requirements please visit customer community.
I would like to highlight some points below that hopefully will aid in better understanding of the solution configuration:
- Business Rules for Position Management: Position is an MDF object and many of us tend to use “Metadata Framework” category to build rules required for Position Management.
Would like to highlight that there is a Category called “Position Management” under Configure Business Rules.
This category has following rule scenarios:
If you have to create a rule for one of these scenarios , for e.g., Position Synchronization, Job requisition template derivation, Field mapping required for Position to RCM integration etc., then It is recommended to select appropriate scenario from this list. This pulls the right base objects for creating the rule.
Rules for synchronization/integration etc also need to be updated against correct fields in “Position Management Settings” else system will not execute them.
- Shared Position Vs Regular Positions: If your organization has a strict budget control in place then you should be aware of “Multiple Incumbents Allowed” field value on position. It is recommended to set this field value to “No”.
The reason for this setting is that if you also use Job Information to Position sync and if an attribute value is changed in Job Information of the incumbent, which syncs back to position as per the rule specified, then it can lead to creation of new positions in the background, without an approval process, if system doesn’t find a vacant position under the parent position.
- Position Reclassification and Manual Supervisor Change: Both changes cannot happen in one step. If you want an attribute change to sync back to position from incumbents Job Information (assuming this attribute is part of the sync rule) then you could first make this change and save the record. You need to return to the Job information and do Supervisor change as a next step.
- Transition Period: You can set values for Transition Period under “Position Management Settings”. But if you are using Position Types, you need to set the Transition Period values for each position type via Manage Data-> Position Types.
Global Settings maintained under Position Management Settings are used by the system only when Position Types are not used.
Similarly, pay attention to field “Synchronize position matrix relationships to job relationships of incumbents?”. This field is by default “Not Visible” on UI. It is recommended to change visibility settings for this field to “Editable” and maintain desired value else synchronization of relationships from Position to incumbent will not happen if Position Types are being used.
Detailed recommendations for Position Management configurations are available in the recently released Implementation Design Principles document. Do check it out!
SAP SuccessFactors Employee Central Position Management: Design Considerations and Recommendations
The document provides leading practice recommendations while configuring SF EC Position Management and also details risks of taking alternative approach.
For structured guidance and advice on how to address challenging customer requirements please visit customer community.
- SAP Managed Tags:
9 Comments
| User | Count |
|---|---|
| 5 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 |
