Symptom
When Job Information has multiple records with the same effective date, changes are not forward propagated to other records of that date.
Environment
- SAP SuccessFactors HCM Suite
- SAP SuccessFactors Employee Central
Reproducing the Issue
UI Scenario:
- Insert a new record via MSS screen or Insert New Record on the Job Information History screen;
- Add the same effective date of existing records;
- Notice that forward propagation did not make changes to the record of that date;
Import Scenario:
Example - importing custom-sting1
- Import job information record with sequence number 1, 2 and 3;
- Add data for for custom-sting1 only in the row for sequence 1;
- Data is not propagated to the other records of the same date;
Cause
The propagation does not read the current record. Forward propagation will only consider the future dated records.
Resolution
When making changes to existing records that share the same effective date and have sequence number, forward propagation will not occur unless:
- A new record is inserted with an effective date earlier than the existing records, or
- The records are deleted and inserted again via import or UI.
Note: Changes to Job Information are not propagated when: corrections are done in the Job Information History screen or job history records are deleted in the Job Information History screen.
See Also
Keywords
sap successfactors, employee central, data propagation, base object, sequence number, effective date, delta retrieval logic, odata, compound api, job information, record propagation, api change detection, Job Information, records, effective date, sequence number, changes, forward propagation, insert record, earlier date, import, delete records, UI, re-import, relevant data, sequence , KBA , LOD-SF-EC-JOB-FWP , Forward Propagation , Problem
SAP Knowledge Base Article - Public