SAP Knowledge Base Article - Public

2321639 - Performance improvements in compound employee query handling.


You are using Compound Employee API (SFAPI) and either continously/intermittently slowness is observed.

This can be via Boomi/PI/HCI/direct API call.

Example of a Compound Employee API Query

SELECT accompanying_dependent, address_information, alternative_cost_distribution, compensation_information, deduction_non_recurring, deduction_recurring, direct_deposit, email_information, emplo
yment_information, global_assignment_information, ItDeclaration, job_information, job_relation, national_id_card, paycompensation_non_recurring, paycompensation_recurring, payment_information, person, person_relati
on, personal_information, phone_information FROM CompoundEmployee WHERE last_modified_on >= to_datetime('2016-05-09T04:15:27Z')




This occurs if the data access method is not optimal in successfactors.

There could be various other reasons for slowness such as:

1. API server's unavailability/lag.

2. Data center wide infrastructure issues.



Please check the optimized data access method in provisioning to improve the performance.


Provisioning -> SFAPI Feature Settings 

provisioning switch.jpg


See Also

If you still experience slowness, please reach out to SAP product support team.


KBA , LOD-SF-INT , SF Integrations - EC Payroll, Boomi/ HCI, API , LOD-SF-INT-API , SF API & Adhoc API Framework , Problem


SAP SuccessFactors HCM Core all versions