Business rule PosToJobInfo
“We have a OnChange business rule to propagate data from Position object to Job Info entity (rule name: PosToJobInfo).
Position object has a relation to Department. Department has few custom fields. As part of this business rule we are moving data from one of the custom field of Department linked to the position to a custom field in Job Info.
We have a position whose linked Department has been updated in 2016 with a different value for the District field (custom_string).
When we change the position (or a data change) of an employee in the UI, then the system (business rule) automatically propagates the latest District value to the Job Info custom field.
But if I do the same Position Transfer via API by calling EmpJob API (both SFAPI and oData API), then the system (business rules) propagates the old value of the District field to the Job Info custom field.
SAP SuccessFactors Employee Central
From Imports, the effective date on the record is passed to the Rules Engine to resolve the fields defined on it. In this case, if you pass today’s date as the start date, then the current effective rule record is picked up for processing (since rules is also effective dated). Now to resolve the fields defined on the rule, the same effective start date is passed, so the current effective Position should get picked up, followed by current effective Department.
Engineering team observed that there might be an issue with the resolution of entities defined on rules, even though the correct effective start date is passed. The correct position record gets picked up but to pick the department it may be using the start date of the position instead of the effective date on the record.
This is a known issue.
Internal link: https://jira.successfactors.com/browse/ECT-206684
PosToJobInfo business rule import position effective start date , KBA , LOD-SF-EC-JOB , Job Information , Problem