When a custom MDF object is created, the system generates a set of fields in addition to the customer defined fields. Some of these fields are prefixed with the string “mdfSystem”. The values (property values) for these fields are meant for internal system use only and should not be altered by any user.
SAP SuccessFactors HCM Suite
Reproducing the Issue
Go to Admin Center;
- Configure Object Definitions;
- Select the wanted object
- Check the pre defined field mdfSystem.
By default, these fields are set to not visible (Visibility = Not Visible). However, the system does not restrict customers from changing the visibility through “Configure Object Definitions”, as some customers wish to make the field available for reporting. However, if a customer wishes to make such a field visible, they should take care to not allow the field to be changed by an end user. Therefore, we strongly recommend against making the field visible in the Config UI.
If for some reason a customer wishes to display an MDF system field in the UI, they must ensure that it cannot be edited by an end user. Also, the field must NOT be affected by any business rule that could change the value of that field or placed in a group of fields that will be refreshed with any business rules.
- If for some business reason, the visibility of this type of field needs to be made visible (e.g. for reporting reasons), then we strongly recommend that it not be displayed in Config UI. (Note: The customer may want to check to see if any such fields are exposed in the Config UI.)
- If for some business reason, the field needs to be displayed in the user interface, the customer should NOT make it the target for any business rule. Otherwise, any end user might be able to change the value of the field which would result in unexpected behavior. (Note: The customer should confirm that for the objects which have an mdfSystem* field displayed in the UI, the business rules that are executed on that object should not touch any of the mdfSystem* fields.)
KBA , LOD-SF-MDF , Metadata Framework , Problem