-Issue concerning with future dated changes requiring the Lookup function calculation-
Lookup function in Rules calculates value based on the first lookup value instead of latest lookup value.
For example, we have configured a rule to look-up a Car Allowance value from an MDF Object.
The object was created on 01/01/1970 (MM/DD/YYYY) and was updated on 06/01/2017. If we insert a new Job Info record, make the needed change and save, it will trigger the rule which creates a Comp Info record based on the data returned from the MDF Object.
The issue is that if the change is a future dated change, for example - Todays date is 03/20/2017, and the MDF Object has been updated on 06/01/2017. We insert a new Job Info record on 06/02/2017 and the rule triggers just fine, but the rule uses the calculated value from the original MDF object (01/01/1970) instead of using the value on the MDF object record that is the latest (06/01/2017).
This issue only occurs for future dated transactions.
The rule correctly fires if for example todays date was 06/01/2017, then the rule will pick up the latest MDF object record (dated 06/01/2017).
Successfactors - Rules Engine
Lookup function will always search by the system date, whereas we are expecting the lookup to search by the context date of the rule.
Our Egnineering team had already noted this requirement for an enhancement.
The enhancement ticket #XAF-973 is planned to be released with b1708 product version.
Please reach out to your CSM if further tracking of XAF-973 is required, else raise an incident with SAP support quoting the engineering ticket #XAF-973.
Effective dated lookup, MDF lookup, future dated lookup , KBA , LOD-SF-EC-MDF , MDF & EC2MDF Migration , LOD-SF-EC , Employee Central , LOD-SF-EC-RUL , Business Rules & Event Derivation , Product Enhancement