3718472 - Business rules inconsistent behavior when reading effective dated records of multiple objects in SAP SuccessFactors Employee Central

• Two business rules with identical configurations behave differently when one is assigned onChange trigger compared to onSave trigger.
• One rule reads data correctly from the Business Unit object, while the other rule ignores new time slices, resulting in incorrect information.

SAP SuccessFactors Employee Central

• Two identical business rules exist, one onChange and one onSave.
• The rule navigates from Job Info into the Department object, and from there into the Parent Department to retrieve a field value and write this value into a Job Info field.
• In the example, the Job Info effective start date is Feb 4. The Department object has a record effective 2025-12-31.
• The parent department has one record effective 2025-12-31 and one effective 2026-02-04, i.e. same date as the Job Info change, and the expectation is that the rule ends up in that record in the parent department and fetches the field value from there.
• This field value changes in the 2026-02-04 parent department record, so has a different value in the 2025-12-31 record.
• Via Legacy People Profile, the onChange rule ends up fetching the expected field value from the right parent department record.
• Via Latest People Profile edit or insert, the rule seems to end up in the wrong parent department record (right object, but wrong record) - the one effective 2025-12-31, and fetches the field value from that. The same thing happens in the onSave rule. 

• The rules navigate through effective dated records differently. One rule uses the effective date of the first record in the object, while the other uses the most recent effective date, leading to inconsistent behavior.
• When resolving the related object EO (parent department) in ValidForAssociationContext, the effective date used is different which is resulting in incorrect data. When the same rule is triggered via Legacy People Profile, the effective start date in ValidForAssociationContext is correct.

• Engineering has identified the root cause and created a code correction ticket. Please follow this KBA for updates on implementation timeline.
• As a temporary workaround: Create a new record in the object using the same effective date as its parent object (e.g., 04/02/2026 in the example).

3321868 - Parent parent department retrieves old value in jobInfo business rule via Import - SAP for Me

Configuring Parameters for a Business Rule for Job Information | SAP Help Portal

business rules, effective dated records, SAP SuccessFactors Employee Central, inconsistent behavior, data reversion, sector fields, rule logic, temporary workaround, code correction, object, rule, business, record, old record, new record,ECT-267974 , KBA , LOD-SF-EC-JOB-RUL , Job Info Business Rules , Known Error