When importing legacy position data, some of the values, in the position file, are not being updated for the position record.
- SAP SuccessFactors Succession Management
- SAP SuccessFactors Legacy Position nomination method
In the position import file, only the first 5 fields - Model, PositionCode, userID, ManagerPos, and KeyPosition - are stored in the Succession position record.
All other fields - Title, Jobcode, Department, Division, Location, Manager, HR, Matrix_Manager, CustomManager, and Custom01 through Custom15 - are held in user records, including TBH positions, which get an invisible vacant user record. So it's important to consider the following:
- If you enter these values for a TBH position and then fill the position with an employee, the original vacant employee record is removed and the position now assumes the title, department, division, matrix, and custom managers, of the new incumbent;
- Conversely, if you remove an incumbent from a position, the system will create a new vacant employee record, copying the title and the fields relevant for permissioning (such as department, division, matrix, and custom managers for example) from the prior incumbent.
These vacant employee records are managed by the system and are not reflected in the succession planning tools. With this mechanism, the position and employee records are never in conflict, since the position takes on the qualities of the incumbent.
More information on import data for Legacy Position nomination method, is available in the KBA 2395215 - Succession Management: Import Positions for Legacy Positions.
position-based nomination method legacy position succession planning position import data , KBA , sf org chart , LOD-SF-SCM , Succession Management , LOD-SF-SCM-POS , Position Imports, Sync, Tiles etc. , Problem