SAP Knowledge Base Article - Public

3785768 - [MDF in PPX ] History Section's data change display of custom MDF Portlet in Latest People Profile

Symptom

  • This KBA explains the history Section's data change displaying logic of custom MDF Portlet in Latest People Profile

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

Reproducing the Issue

  1. Go to a custom MDF portlet in Latest People Profile
  2. click "View All" from Summary Card to view all MDF records
  3. Click “History” button to check the Records change history 
  4. Observed there may have "deleted" operation in the History section, e.g below screenshot:

Resolution

The History Section's data change displaying logic of custom MDF Portlet in Latest People Profile are depends on how and when the records were added for the respective MDF portlet.

Take above screenshot as Example_1:

1. In this MDF portlet, there has an existing record below that effectiveStartDate is 1/1/2026, Child record is 646297:

[OPERATOR]externalCodeeffectiveStartDatecust_CHILD.externalCodecust_CHILD.externalName
Supported operators: Delimit, Clear and Deletecust_test727Parent.externalCodecust_test727Parent.effectiveStartDateexternalCodeexternalName
 sfadmin1/1/20266462971

2. User then inserted a new record, that effectiveStartDate is 7/1/2025, Child Record is 646299:

[OPERATOR]externalCodeeffectiveStartDatecust_CHILD.externalCodecust_CHILD.externalName
Supported operators: Delimit, Clear and Deletecust_test727Parent.externalCodecust_test727Parent.effectiveStartDateexternalCodeexternalName
 sfadmin7/1/2025646299

2

3. System will compare the newly added record with its "NEXT" timeslice's record to check whether there are any data differences. So system will compare the data differences between 7/1/2025 and its "NEXT" timeslice's record 1/1/2026, the difference is the Child record 646299 does not exist in 1/1/2026's timeslice.

4. The data change will be displayed in the  "NEXT" timeslice's record: 1/1/2026, with ”deleted:1" operation record.

Take below screenshot as Example_2:

1. In this MDF portlet, there has 3 existing records below:

[OPERATOR]externalCodeeffectiveStartDatecust_CHILD.externalCodecust_CHILD.externalName
Supported operators: Delimit, Clear and Deletecust_test727Parent.externalCodecust_test727Parent.effectiveStartDateexternalCodeexternalName
 sfadmin7/1/20256462992
 sfadmin1/1/20266462971
 sfadmin5/1/20266462973

2. The user insert a new record that effectiveStartDate is 2/1/2026 by adding a new child record 646305, and remains the existing child record unchanged:

[OPERATOR]externalCodeeffectiveStartDatecust_CHILD.externalCodecust_CHILD.externalName
Supported operators: Delimit, Clear and Deletecust_test727Parent.externalCodecust_test727Parent.effectiveStartDateexternalCodeexternalName
 sfadmin2/1/20266462971
 sfadmin2/1/20266463054

3. Same as Example_1, System will compare the newly added record with its NEXT" timeslice's record to check whether there are any data differences. So system will compare the data differences between 2/1/2026 and its  "NEXT" timeslice's record 5/1/2026, the difference is the Child record 646305 does not exist in 5/1/2026's timeslice.

4. The data change will be displayed in the  "NEXT" timeslice's record: 5/1/2026, with ”deleted:1" operation record.

[Conclusion]

User can always compare the record data between the two timeslices' records to see if there are any data differences, and the operation message will be displayed in the  "NEXT" timeslice's record, based on the effectiveStartDate that the new record inserted.

Keywords

MDF, delete, PPX, latest people profile, History, delete, record, insert, operation, timeslice, effectiveStartDate, metadata framework , KBA , LOD-SF-MDF-PPX , MDF on New People Profile , How To

Product

SAP SuccessFactors HCM Suite all versions