Message INVALID_HR_ID is received when trying to edit (Insert, Update, or Upsert) the User entity via OData API call.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
The system verifies if there is a valid HR user ID assigned for that specific employee that is being edited. If the system cannot find a valid HR user ID the error message "INVALID_HR_ID" will be received.
First it is recommended to check if there is a valid HR user ID assigned to this employee via employee export:
- Admin tools -> Manage users -> Employee export
- Under Export Users click on Export User File
- Check the HR column of the exported file to see if there is a valid HR user ID:
Also, it is possible to avoid this error message by creating a User API Option Profile and not selecting the "Validate Manager and HR fields" option.
This tool helps you to maintain API option settings and manage API option profiles for the User entity.
The User entity allows you to specify a few processing parameters to control extra business logic that can be optionally applied when editing (Insert, Update, Upsert) the entity.
This feature helps to reduce client complexity and provides more loosely coupled integration by providing the choice of processing parameters as configuration settings on SuccessFactors side.
The steps for creating a User API Option Profile can be found on this KBA 2527211.
INVALID_HR_ID; User entity; HR user id; API parameter. , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , Problem