3340749 - How to prevent duplicated entries in One Time Deduction - Employee Central

• When loading One Time Deduction files (either via API upserts or Import and Export Data), the system creates multiple entries with the same details if the same file is used multiple times
• Is there any way to prevent such scenario from occurring?

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• SAP SuccessFactors Employee Central - Deductions

1. Prepare a one-time deduction import file
2. Load the same data multiple times
3. The system creates multiple, duplicated entries with the same details

This is currently expected system behavior.

The externalCode field in the One Time Deduction object is set to auto-number which means that whenever you load a file, even with the same details, the system will automatically generate a new entry and add this as part of the "One Time Deduction User" record of the employee.

Consequently, the flag "Suppress Redundant Date-Effective Records" will also not be applicable in this case since there's a new externalCode generated upon import.

Workaround:

A business rule can be configured using the "Validate" purpose and the Lookup() function to check if there is any existing One Time Deduction entry for the employee with the same Pay Component, Date, and Amount.

This rule can then be assigned as Validate Rule in the One-Time Deduction object.

If you're trying to import a duplicated entry, the system will throw an error and prevent the import from completing.

one time deduction, import, api, duplicate, pay component, entr , KBA , LOD-SF-EC-DED , Deductions , How To

SAP SuccessFactors Employee Central all versions ; SAP SuccessFactors HXM Core 2211