SAP Knowledge Base Article - Public

2716060 - Recurring Deduction - End Date Forward Propagation Behavior

Symptom

Recurring Deduction End Date not propagated to future records.

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 - Employee Central
  • SAP SuccessFactors Employee Central - Deductions

Reproducing the Issue

Scenario: Initially, the Recurring Deduction End Date is not defined for Pay Component A, then a new Pay Component B was added with future End Date. This creates a record of deletion dated in the future, leaving Pay Component A alone. Then, for the first or past dated record, we decided to edit and define End Date for Pay Component A, which is before the end date of Pay Component B. This creates a deletion record as well for Pay Component A.

Customer expects the future dated record created earlier for Pay Component A when Pay Component B was deleted, will be removed because the End Date for Pay Component A was already defined. However, this future dated record still exists.

1. Navigate to Employee File.

2. Click on Manage Recurring Deductions or Edit (pencil icon) from Recurring Deductions portlet.

3. Set Effective Start Date as April 1, 2018, add Pay Component A (CHARITY). Leave the End Date blank then Save.

1.jpg

4. Add a new record of Recurring Deduction dated October 1, 2018. Do not edit the Pay Component A (CHARITY), just add Pay Component B (PRODUES) with End Date as March 31, 2019.

2.jpg

The system automatically creates a record dated April 1, 2019 having Pay Component B (PRODUES) as deleted, leaving the Pay Component A (CHARITY) exists as this does not have an End Date defined (backend date is 12/31/9999).

3.jpg

5.  Go back to the first record April 1, 2018 and edit it, define End Date for Pay Component A (CHARITY) as December 31, 2018.

4.jpg

5.jpg

January 1, 2019 record will be created as the deletion record for Pay Component A (CHARITY).

Since Pay Component A (CHARITY) was already removed by January 1, 2019 record, we expect that the April 1, 2019 record (future-dated) will also be removed or deleted. However, future-dated record that was created in the past was not removed by the system.

6.jpg

Cause

For Recurring Deduction object, there is no forward propagation behavior. If the record was already created in the past as future-dated, then you delimit the pay component on an earlier time slice, the timeslices outside of the time period will not be removed.

Resolution

The administrators or employees who have access to edit Recurring Deduction End Date should review employee's record and make manual adjustments or deletion, if necessary.

To request for forward propagation functionality on Recurring Deductions, customer can log an Enhancement Request.

See Also

2090228 - How to submit enhancement requests for SAP SuccessFactors products

Keywords

ECT-81560, Recurring Deduction, End Date, forward propagation , KBA , LOD-SF-EC-AAD , Advances & Deductions , Product Enhancement

Product

SAP SuccessFactors HCM Core all versions