Understanding importance of mapping Person id and User id during SuccessFactors Data Imports (Conversions)
Customers follow different models given by SAP which includes Full Cloud, Hybrid Cloud or Side by Side. When customers follow hybrid approach, they usually implement talent modules in SuccessFactors and keeps the rest in their legacy system. Let’s consider below two cases for hybrid approach. In this blog we have taken examples by assuming legacy system as SAP HR on-premise.
Case 1: When customer already has SuccessFactors up and running for talent modules.
Please note that it is important to adhere to the sequence given by SAP. You can read more about it here.
The first file to be loaded for Employee data is the Basic User import. It is also called as User Data file (UDF). This is the base file for all SFSF modules.
There are 2 ids as given below in SFSF EC which are very important and needs to be mapped with legacy ids very carefully to make Concurrent employment (CE) and Global assignment (GA) work properly.
- Person id (Person-id-external)
- User id (userid)
In SAP HR on premise system we have Personnel number (PERNR) and Central Person (CP). For CE and GA scenarios the CP remains the same but new PERNR is created. Both PERNRs are related to same CP. You can consider Person id and User id in EC as CP and PERNR resp.
I have seen few customers who didn’t follow this mapping when they implemented talent modules but when they planned to implement EC they realized that they have mapped CP and Pernr from on-premise to Userid and Person id resp.
SAP has suggested an approach to import global assigment cases. In SFSF EC, when employee goes on GA or CE the Person id remains the same but a new user id is created.
To implement SFSF Employee Central module the customers have to get the Person id swapped with User id and vice versa to make sure GA and CE scenarios can be imported correctly.
This task of swapping the ids is not done by implementation partners. SAP does this task for customers.
Note : There are many customers for whom SAP has swapped the ids. They have a queue of such requests and a dedicated team to work on. If you raise such request with SAP please make a note that this may take anywhere between weeks to months.
Customers/Implementation partners have to map the ids in the Basic User import and share with SAP for them to swap and fix it.
Once SAP has swapped the ids in the Basic user file/ User data file then customers/implementation partners need to make some fine adjustments (not discussed in this blog) to make sure other modules which are already live are not disrupted by the swapping of ids.
Case 2: Customer doesn’t have SFSF live in any module and now implementing EC (or EC and other modules)
In this case, the SFSF EC instance is fresh i.e. there’s no data which already exists. In this case you should follow the sequence suggested by SAP and should map the ids correctly to make sure all scnarios including CE and GA works correctly in SFSF EC.
Note: While you are waiting for SAP to swap the ids for you in the SFSF instance you can still carry on your mock conversions/Data imports by following this approach.