Symptom
When manually updating a field in UI that contains numbers, you will get a message that the changes were saved but the details in the Last Updated By are not reflecting the most recent change date and time.
Environment
- SAP SuccessFactors Employee Central
- Business Configuration
Reproducing the Issue
- Enter a new entry or update any existing entry in History (Job Information or Compensation Information). Only update one field.
- Check any number field that has 4 digits or more and you will see that the value has a comma. For example 4,000
- Remove the value of 4,000 in the field and you will notice that the Save button will be enabled at the bottom
- Type or copy the value of 4,000 in the same field and you will notice that the Save button will be disabled.
- Remove the value of the field and manually type 4000 and you will notice that the Save button will be enabled at the bottom
- Click on save and you will be prompted that the changes were saved but if you check the Last Updated By, it did not update any details.
Expectation is that since UI allowed user to save the record and got a message that the changes were saved, Last Updated By should also update to the most recent change
Cause
First thing to be clear is what UI consider is 4,000 is not same as 4000. The difference is the comma. Since there is a difference in the entry, Save button will be enabled. Even though users will get that the changes were saved, internal validation will compare 4,000 with 4000 and it will consider that they are the same. Due to this, no changes are made at the backend. Since no changes were recognized at the backend, Last Updated By details will not change.
Resolution
This is currently an actual behavior in UI.
In 2605 release the PPX edit screen will be rolled out to customer and this issue no longer exists anymore after that.
Keywords
UI, User Interface, comma, value, decimal, number , KBA , LOD-SF-EC-BCI , Manage Business Configuration (BCUI) & Data Models (XML) , Problem
SAP Knowledge Base Article - Public