3739150 - Suppress redundant date‑effective records does not work for child mdf import

• The Suppress redundant date-effective records option does not prevent duplicate records when importing child MDF objects.
• Duplicate date‑effective entries are created even though the suppression option is enabled.

• SAP SucccessFactors HCM suite
• Metadata Framework

When importing only a child MDF object, the Suppress Redundant date‑effective records feature does not perform a full comparison of the complete MDF hierarchy (root object and all associated child records). This functionality is designed to evaluate redundancy only at the root object level. Therefore, importing a child object independently does not provide enough context for the system to identify the record as redundant.

To prevent the creation of duplicate date‑effective records when importing MDF data, ensure that the import process includes the root MDF object rather than importing child objects only.

The Suppress Redundant date‑effective records feature is designed to evaluate redundancy at the root object level by comparing the complete MDF structure (root object and its associated child records). When only a child object is imported, the system cannot perform a full hierarchical comparison and therefore cannot determine whether the record is redundant.

• Help guide: Suppress Duplicate Inserts
• KBA: 2500313  - "Suppress Redundant Date-Effective Records" setting affecting "import foundation data"
• KBA: 2592161 - How to Avoid Unnecessary Updates During EC import

suppress redundant date-effective records, mdf import, child object import, root object, duplicate date-effective records, duplicate records in export, time slice, import and export data, date-effective, mdf child, suppression not working, employee central mdf, redundant records suppression, mdf duplicate insert, ec import duplicates , KBA , LOD-SF-MDF-IMP , Import and Export Issues , LOD-SF-EC-EDP , Import Employee Data (EC Core only) , Problem