Symptom
When you trigger the Compound Employee API (SFAPI) you get the following info message:
<log_item>
<per_person_uuid>123456789</per_person_uuid>
<person_id>123123</person_id>
<person_id_external>456456</person_id_external>
<code>COMPOUND_EMPLOYEE/DELTA_NO_RELEVANT_CHANGE</code>
<severity>INFORMATION</severity>
<message_text>The employee has changed since the last replication on 01-01-2021T12:00:00.000Z, however, no data was returned because the changes are not relevant.</message_text>
</log_item>
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
- SAP SuccessFactors HCM Suite
- Compound Employee API
Reproducing the Issue
- Go to Address Information portlet and click on Take Action.
- Click on Insert New Record, change the data and save.
- Change it back to the original data which got updated in step 2.
- Change the Effective Date and save.
- Execute the Compound Employee API call.
Resolution
This is an expected behavior with the Compound Employee API which happens when the last_modified_on value of the record got updated and captured afterwards by the filter in the query, but there were no business relevant changes to the fields in the delta logic.
Compound Employee API considers this as a change without an impact for the consumers, as the data of extraction remains the same.
This error log can be suppressed with the usage of parameter resultOptions=relevantEmployeesOnly.
See Also
The page Overview of Query Parameters contains details about "relevantEmployeesOnly" parameter.
Keywords
Compound Employee, Delta, last Modified date, NO_CHANGE, Last Execution Time, DELTA_NO_RELEVANT_CHANGE, relevantEmployeesOnly , KBA , LOD-SF-INT-CE , Compound Employee API , LOD-SF-INT , Integrations , Problem