3696851 - Biographical Information onChange Business Rules Triggering On Dependents With Latest People Profile

• A field in the 'Biographical Information' portlet (e.g. the 'Date Of Birth' field) has been configured with multiple onChange business rules on different objects (specifically, at least one on the Biographical Information base object, and at least one on the Dependent Information base object).
• In the old people profile, these rules used to trigger based on their base object - for example, rules on the Biographical Information model would trigger on employees, and rules on the Dependent Information model would trigger on Dependents.
• However, with the new people profile, rules on both objects are triggering on Dependents - this can cause scenarios where the rule on the Biographical Information object is not intended to trigger for Dependents but does anyway, causing unwanted data changes, warning/error messages, etc. depending on the configuration of the rule.

SAP SuccessFactors Employee Central

1. Log into environment
2. Go to 'Manage Business Configuration' > 'personInfo' element
3. Select the 'Details' link of the field which has multiple onChange rules configured
   1. For example, an onChange rule on the 'Biographical Information' object on the 'Date Of Birth' field, which validates the 'Date Of Birth' value when it is changed, to make sure it is within certain values (e.g. 18 to 70)
   2. For example, an onChange rule on the 'Dependent Information' object on the 'Date Of Birth' field, which validates the 'Date Of Birth' value to be within certain other values for Dependents(e.g. 0 to 18)
4. Go to an employee's profile and add/edit a Dependent
5. When editing the 'Date Of Birth' field, a rule trace reveals that the onChange rule on the 'Dependent Information' model is triggering (as expected), but the onChange rule on the 'Biographical Information' model is also triggering (not expected)
   1. This can cause issues where, even if the dependent is within the criteria of the 'Dependent Information' model rule (e.g. they are 15 years old and so within 0 to 18), they do not meet the criteria of the Biographical Information rule (they are 15, so they are outside the 18 to 70 range) and so an error message is triggered from the 'Biographical Information' rule, preventing creation of the dependent.

On the Latest People Profile, because there is an onChange rule triggering with the 'Dependent Information' object as the base object, when generating the metadata, the system sees the field as having a 'side effect', and does a 'round trip' to trigger the rule, which causes the onChange rule on the 'Biographical Information' object to also be triggered.

• This is a known issue which is being reviewed by our Engineers, and will be resolved with ECT-265299 in the 1H 2026 release.
• You can provide your CSM with the code 'ECT-265299', and they can monitor the correction for you for updates and the resolution timeline.

KB Article 2257064 - Employee Central - Business Rule Execution Log - SAP for Me

latest, people, profile, latest people profile, people profile, ppx, biographical, information, model, dependent, dependent information, biographical information, business, rule, business rule, onchange, on, change, triggering, unexpected, error, ECT-265299, INC17590911 , KBA , LOD-SF-EC-DPD , Dependents Management , Known Error