SAP Knowledge Base Article - Public

3805592 - History in MDF portlet shows “deleted” when adding past-dated child entries

Symptom

  • In an MDF portlet, adding a past-dated child entry causes the History panel to show the child as “deleted”.
  • Values of the child shown as “deleted” appear removed in the History comparison.
  • History UI displays “records deleted” even though the user didn’t delete the record.

Environment

SAP SuccessFactors HCM Suite

Reproducing the Issue

  1. Add a child entry effective Jan 1 in the MDF portlet.
  2. Add one child entry effective Feb 1.
  3. Insert another child entry effective Dec 12, 2025 (past-dated).
  4. Open History for Jan 1 and observe that one child is shown as “deleted”.

Cause

  • This is expected behavior of the MDF History UI. History is not an audit log; it compares adjacent effective-dated time slices and lists differences. If a child record present in one slice is not present in the next slice being compared, the History UI surfaces it as “deleted” in the comparison, even though the data was not actually deleted.
  • When importing with Full Purge on composite child records, newly created child external codes across slices can lead the History comparison to show “added/deleted” between slices.

Resolution

Validate data persistence:

  1. Open Manage Data for the MDF object and confirm that all effective-dated records still exist.
  2. In People Profile, use Show all fields/records to display past-dated entries that may be hidden in default views.

Proceed with Full Purge for adding past-dated entries:

  1. Export existing data for the affected MDF child object.
  2. Use the export as the base import file and include all records you want to exist after import (both existing and new) in the same file.
  3. Remove all values in the child external code column.
  4. In the child external code column, set the value to #1 for every row to keep a consistent external code across time slices.
  5. Run Full Purge. Including all slices and using a consistent external code reduces “deleted” comparisons in History.

Important notes:

  1. History ≠ Audit. Use the Change Audit framework to review who changed what and when; use History only to compare differences between adjacent slices.

Keywords

MDF, History vs Audit, past-dated entry, backdated entry, composite child, effective-dated, time slice, records deleted, People Profile, Incremental Load, Full Purge, externalCode, child record, History UI, comparison , KBA , LOD-SF-MDF-PPX , MDF on New People Profile , Problem

Product

SAP SuccessFactors HCM Suite all versions