3081532 - Optimistic Locking Error when changing the effective start date of a termination record

An optimistic locking exception as below is thrown when you try to move a termination record which is a multiple change per day record (2/2) to a future date.

Message:

Unfortunately, it's not possible to save your changes. Job Information has been updated by user(s) XXXX in the meantime. If you click Refresh, the changes made by this user will overwrite your changes. If you clock Cancel, you'll be brought back to the portlet. We are sorry for the inconvenience.

• SAP SuccessFactors Employee Central
• Optimistic Locking 

Prerequisite: Enable Optimistic Locking set to YES

*Go to the profile of an inactive user who has multiple changes per day record ie (2/2)

See the example below:

*Move the termination record to a date in the future and save 

*Warning appears :

"Employee XXX has been inactive since 01 July 2021."

*Click on proceed

* Message appears as below:

Unfortunately, it’s not possible to save your changes. Job Information has been updated by user(s) XXXX in the meantime. If you click Refresh, the changes made by this user will overwrite your changes. If you click Cancel, you will be brought back to the portlet. We are sorry for the inconvenience.

The effective latest change flag of data change record (1/2) is set to "Y" on the database. BEFORE the warning message "Employee XXX has been inactive since date (XXXX)." is triggered. When you then choose "Proceed", the optimistic locking exception is thrown.

The Engineering Team have completed a fix which has been confirmed for b2111

• ECT-171544

• ECT-171544
• Optimistic Locking
• b2111