Symptom
A Save Rule is configured in a Child Object to set value from Context.Effective Date to a custom Date field "testcontext" of the child object.
This rule retrieves different values for Context.Effective Date in Manage Data page and API.
Environment
SAP SuccessFactors HCM Suite 2411
Reproducing the Issue
*The issue need to be reproduced by creating a record with a specific payload in API and by manually inserting a new record in the Manage Data page.
Steps1:Create a parent object "cust_basic_test" and Child Object "cust_test0906"
Steps2:Configurate a Save Rule in Child Object "cust_test0906" to set value from Context.Effective Date to a custom field "testcontext" for child object.
Steps3:Use below Payload to create a record in Postman=>it would create a parent record with effective Start Date "2024-02-02" and a child record with "TestinAPIwithDefaultScreent" but custom field "testcontext" is 09/11/2024 which is the date we run this rule.
-----------------------------------------------
{
"__metadata": {
"uri": "cust_basic_test(effectiveStartDate=datetime'2024-02-02T00:00:00',externalCode='X123456')",
"type": "SFOData.cust_basic_test"
},
"externalCode": "X123456",
"cust_te111": {
"__metadata": {
"uri": "cust_test0906(cust_basic_test_effectiveStartDate=datetime'2024-02-02T00:00:00',cust_basic_test_externalCode='X123456',externalCode='TestinAPIwithDefaultScreent')",
"type": "SFOData.cust_test0906"
},
"cust_basic_test_effectiveStartDate": "/Date(1722902400000)/",
"externalCode": "TestinAPIwithDefaultScreent",
"cust_basic_test_externalCode": "X123456"
}
}
-----------------------------------------------
Steps4:Go to Manage Data page and manually insert new record for user X123456 with effective Start Date "2024-09-01" and add a new child record with "testinManageData"=>it would create a record with effective Start Date "2024-09-01" but custom field "testcontext" would be changed to 09/01/2024 for all the child records by the same rule.
Cause
When create a record via API, the Effective date of composite child was set to current date when the rule is triggered, but ideally it should be the effective date of the parent.
Resolution
Our engineer team has identified this issue and will fix it as part of 1H 2025 release.
As a workaround please use the effective date parameter from the parent object.
See Also
2505 release:https://community.sap.com/t5/product-and-customer-updates/2025-product-release-dates/ba-p/13862640
Keywords
KI2411, Context.Effective Date parameter,save rule,composite child object , KBA , LOD-SF-MDF-RUL , Custom Oject based Business Rules , LOD-SF-MDF-MGD , Manage Data - Create, Update & Delete , LOD-SF-MDF-PP3 , MDF on People Profile , Known Error