SAP Knowledge Base Article - Public

2712942 - Employee Delta Export - Defined Behavior and Limitations

Symptom

In this document we will define the system behavior of Employee Delta Export Add-In (Microsoft Excel) and clarify the current features available to multiple employee data changes on one given day.

Environment

  • BizX
  • SuccessFactors

Reproducing the Issue

 1. Scenario:

   User (xxxx) has two contracts, who's person-id-external is abc123. The same user's (xxxx) user ID is also abc123 for the main contract, and 1 for the second contract.

You make a data change on both contracts on the same day. You then run the Employee Delta Export, and get two rows, and only one person-id-external in the first one.

2. Summary:

   You are making two changes (to employee data) in the one day and is looking for 2 entries to user abc123.

3. Problem:

   The problem is that we don't have any identifier to know what section of data of abc123's data was changed - e.g. was it a change to Global Assignment Information or Job Information (supported entities).

Cause

  • In the case of multiple changes per day, Employee Delta Export will create only one row to show changes.
  • Currently we do not display user information for the changes that happened to any of the sub-segments of employement data, which can be used to identify the change of data.
  • This is the current standard behaviour.

Resolution

Enhancement Request:

   Kindly submit an Enhancement Request to incorporate this feature into future releases as per below KBA:
   2281168 - How to create Enhancement Request for Successfactors Integrations

See Also

Standard Documentation on Employee Delta Export:

   Using the Employee Delta Export Add-In for Microsoft Excel

Keywords

  • Employee Delta Export
  • Compound Employee
  • Add-In
, KBA , LOD-SF-INT-CE , Compound Employee API , LOD-SF-INT , SF Integrations - EC Payroll, Boomi/ HCI, API , Product Enhancement

Product

SAP SuccessFactors HCM Core all versions