3452058 - [Script Fix Guideline] - Data Corruption Issue caused by OnSave Rule to set EffectiveStartDate/EffectiveEndDate field Value

This KBA provides the Script Fix Guideline and pre-requisitions for any MDF data corruption issues which caused by OnSave Rule configured in any MDF object to set EffectiveStartDate/EffectiveEndDate field value.

Please make sure you've read and understand this guideline before Engineering providing Script Fix of such data corruption issues.

• SAP SuccessFactors HXM Suite

• Metadata frameowrk (MDF)

Background:

Any OnSave Rule configured in any MDF object to set EffectiveStartDate/EffectiveEndDate  field value is NOT ALLOWED. Such Configuration will easily lead data corruption on MDF Data and the application can not handle such use case.

Please remove such rule in any of the MDF object in any of your SF instance ASAP, to avoid data corruption issue happens which will continuously and seriously impact the MDF Data in the instance.

Issue Scenarios:

• User MDF data is not searchable in Manage Data
• User MDF portlet is not visible or occurs error in People Profile Page
• Error "Saving of 1 [MDF Object] throwed a Exception??? " occurs while trying to save MDF record in People Profile MDF portlet or in Manage Data

Existing KBAs & Guides about this issue:

2838699 - Error when trying to create a record for a custom MDF Object - ???Saving of 1 [MDF Object] throwed a Exception??? - SAP for Me

2646360 - [MDF] The behavior of effectiveStartDate field in custom MDF objects. - SAP for Me

2562069 - Scenario based business rules for MDF objects, Parameters, Limitations and other information about custom MDF Business Rule configuration scenario - SAP for Me

Supported Purposes for MDF Rule Scenarios | SAP Help Portal

• Do not use a save rule to change system fields such as effectiveStartDate and effectiveEndDate. Changing these fields using save rules can lead to data corruption and application errors. If you want to check the values of such fields, use a validate rule instead.

Script Fix Guideline:

Once the reported case has been identified as being caused by this wrong configuration, SAP engineering team can provide a One-Time script fix of such issues.

1. Before executing the script fix, we need customer provide a written commitment in the reported support ticket which must includes below details:

• Make sure such rule has been removed from any of MDF Objects in any of SF instance (If such rule configured in multiple SF instances)
• Confirm NEVER configure such rule back into the affected MDF object and any other MDF object
• If in the future same issue happens again due to the same rule configuration root cause, understand that SAP will NOT continue support for such data fixes, which is caused by similar rules for the same MDF objects. 

2. After the written commitment has been provided in the support ticket, Engineering team will validate and provide the script fix, after that SAP will not provide any script fix for the same MDF object Data issue caused by the same root cause.

*Support team colleagues, please refer to internal memo for more details.

2838699 - Error when trying to create a record for a custom MDF Object - ???Saving of 1 [MDF Object] throwed a Exception??? - SAP for Me

2646360 - [MDF] The behavior of effectiveStartDate field in custom MDF objects. - SAP for Me

2562069 - Scenario based business rules for MDF objects, Parameters, Limitations and other information about custom MDF Business Rule configuration scenario - SAP for Me

3202427 - Changing the value of effectiveStartDate field in an MDF object using Save rule. - SAP for Me

Saving, Exception, ???Saving, Exception???, External Code, effectivestartdate, Error, create, record, mdf, custom MDF, object, Scenario based rules, MDF business rules, parameters, MDF rule ,MDF, onSave rule, INC6246848 , INC7614777 ,MDF-50350 , KBA , LOD-SF-MDF-RUL , Custom Oject based Business Rules , How To