2478472 - How to avoid dependents information while using PerPersonal entity in Integration Center

Dependent data is also returning along with employee data when querying the PerPersonal API. How to avoid the dependent data?

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 HCM Suite
  • OData API

1. Run an OData API query in either Integration Center or OData API directly.
2. Records are returning with the format "e_y" in their IDs, where "e" represents the Person ID External of the employee and "y" is some other number.
   • These are usually dependent records.
   • For example: the dependent of an employee with Person ID External = 2 will have a record with Person ID External = 2_d775.

This happens because PerPersonal entity by default fetches the entire data of employees and dependents.

To obtain only employee records in the query result you can use the following filter: $filter=personNav/employmentNav/personIdExternal ne null.

Logic behind this filter

The personNav/employmentNav field has data only for employees where employment information exists. Dependents do not have employment data, so they are excluded by the filter. Regular employees always have employment information, so they are included in the results.

Example in Integration Center

This is the field to be selected in the filter:

The filter will look like this:

dependent, dependents, integration center, odata, api, employee central, , KBA , LOD-SF-INT-EC , Employee Central SFAPI & OData Entities , LOD-SF-INT-INC-ODATA , ODATA API In Integration Center , How To