3671069 - API Call for Manager PersonID field needed from onboarding

• An integration between SuccessFactors and Microsoft AD requires the manager's PersonID for all users. Currently, this information is retrieved from the custom10 field of the User entity/UDF file.
• However, onboardees do not have UDF entries created until their hire date, resulting in delays in onboarding as the manager PersonID is not populated.
• Multiple fields in other APIs, such as Employment information, Job information, and ONB2Process, were explored but did not provide the required manager PersonID. The JobInformation API contains a supervisor/managerID field, but it only provides the manager's username, not the PersonID.
• The issue causes delays in onboarding when additional permissions are required, as the manager PersonID is only available post-hire.

SAP SuccessFactors Onboarding

1. Review the integration setup between SuccessFactors and Microsoft AD.
2. Attempt to retrieve the manager PersonID for onboardees using the custom10 field of the User entity/UDF file.
3. Verify that onboardees do not have UDF entries created until their hire date.
4. Explore other APIs such as Employment information, Job information, and ONB2Process for the manager PersonID.
5. Confirm that the JobInformation API provides the manager username but not the PersonID.

Expected behavior because there is no single path to reach the manager personid from onboarding.

• To query the managerID from User entity you need to expand the managers user ID. Please use the following query: /odata/v2/User?$select=userId,manager/userId&$expand=manager 
• Retrieve the Person ID External of manager: Once you have the manager's userId, you can then query the PerPerson entity or other relevant entities (depending on your specific data model and configuration) to retrieve the personIdExternal associated with that userId. The Person ID External is a key identifier for individuals in SuccessFactors.

KBA , LOD-SF-OBX-EHI , Integration Non EC HRIS , Problem