3575859 - API Endpoint returns Inactive Employee via User entity while the Filter Set condition doesn't include Status filter to fetch Inactive Employee

eAn OData API query on User entity results in the return of invalid records, when there are multiple Filter Set conditions with OR conditions with Status field in the filter query.

Example: &$filter= (lastModifiedDateTime ge '2000-01-01' and empInfo/isECRecord eq true) or (status eq 'f' and empInfo/startDate ge '2025-2-11' and empInfo/startDate le '2025-2-13') , this filter set query fetches Invalid Employee with all the status but both the 1st filter set (lastModifiedDateTime ge '2000-01-01' and empInfo/isECRecord eq true) and 2nd Filter Set (status eq 'f' and empInfo/startDate ge '2025-2-11' and empInfo/startDate le '2025-2-13') individually won't fetch these employees

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

SAP SuccessFactors HXM Suite

• Integration
  • ODATA API

OData API, inactive user, filter criteria, status filter, Invalid Status employee record, User, ODATA,  implicit status filter, Status , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT-API , API & Adhoc API Framework , LOD-SF-INT , Integrations , Problem