Compensation Planning simplified with MDF Integration
Hello Compensation Experts,
I hope everyone is staying safe and healthy as we all manage our way through this challenging time. I want to share the specifics of the Compensation MDF integration feature delivered as part of our H1 2020 SAP SuccessFactors Compensation Release. This blog is meant to provide a deeper insight into what is now possible with an EC-enabled compensation template, and how you can enhance your existing plan template configuration with EC and MDF stored information, in preparation for next year’s comp planning cycle.
Now, let’s continue with some details related to this new integration feature.
Note – Screenshots are subject to change.
Total Rewards executives often extend their HRIS solution to capture the unique way that their workforce is managed. These extensions are critical to the optimization of their compensation planning process. Until now, this could be accomplished using workarounds, adding to the complexity of the process. With SAP SuccessFactors Compensation new custom MDF portlet Integration option, the planning process for focal planning cycle will be greatly simplified.
Prior to the H1 2020 release, SAP SuccessFactors Compensation customers using an Employee Central enabled template were limited to sourcing employee data from the following Employee Central standard portlets for compensation planning.
- Biographical Information (personInfo)
- Personal Information (personalInfo)
- Employment Information (employmentInfo)
- Job Information (jobInfo)
- Compensation Information (compInfo)
- Job Relationship Information (jobRelationsInfo)
- Recurring Pay Components (payComponentRecurring)
- Recurring Pay Components (payComponentNonRecurring)
- Pay Component Groups (payComponentGroup)
This limitation did not allow customers who had configured custom MDF Employee Central portlets with additional information used to extend their HRIS solution, to optimize their compensation planning experiences. In addition, compensation and bonus planning might require additional data that may or may not be available in Employee Central but still can’t be used by the current set up. Previously, customers were unable to leverage these custom MDF portlets directly for Compensation planning. They had to define these custom MDF objects in Employee Central under one of the supported standard portlets and then access them on the worksheet.
With the H1 2020 release, customers can now use MDF custom objects with external code mapped to type ‘user’ directly for planning in Employee Central integrated Compensation, Variable Pay, and Total Compensation Planning worksheets. They can access the custom MDF objects directly without having the need to replicate data from an existing object into an accessible area (jobInfo, compInfo, employmentInfo etc.) via multiple business rules and validations.
Following are some examples of supported use cases:
- Leave without pay data for proration
- This data can be replicated from EC Time Off into custom MDF portlet and then used for compensation planning.
- Additional Eligibility overrides – if there are eligibility overrides at each component level (merit, adjustment, etc.), customers do not need to define additional fields in HRIS system which are used solely for compensation planning.
- Accessing historical and multiple performance scores from the custom MDF portlet into the Compensation and Variable Pay worksheets.
- Displaying historical LTI information in worksheet columns from a custom LTI MDF portlet.
- Extracting stock information from a custom MDF portlet, to use as columns on the worksheet. A second compensation plan for LTI vesting can access the data in the portlet to have the correct awarded shares as starting point for the vesting process.
- Sensitive information from lookup tables can be migrated to custom MDF portlets for enhanced data security.
- Compensation planning specific picklists can be configured in custom MDF portlets and referenced directly without the need to define them in the HRIS system.
What works and what doesn’t?
The following field datatypes are supported in the current release.
- Picklists (code and default label mappings are supported)
Following field datatypes are going to be supported in future releases.
- Picklists (label)
- Foundation Objects
- Generic Objects
There is a limitation due to which we don’t support MDF objects with an underscore in the object name. Please ensure that your MDF objects don’t have an extra underscore except the first ‘cust_’ added automatically by the system.
Note: Custom MDF feature is NOT supported currently for background elements for Variable Pay EC Employee History Fields.
- Navigate to the Admin Center.
- In the Tools search field, type Configure Object Definitions.
- In the Configure Object Definitions page, from the Create New drop down list, choose Object Definition.
- This opens a form in which you can enter details about the new object definition.
- Set Data Type to User under the externalCode field.
- Modify other fields as required for the custom object, then save the definition.
When you save the new MDF object, the system creates a unique RBP permission associated with the object. You must grant the administrative permissions for this custom MDF object. Proceed as follows:
- From the Admin Center, enter Manage Permissions Roles into the Tool Search box.
- Select the Administrative role assigned to compensation planning.
- In the Permissions Settings pop-up, scroll down and select Miscellaneous Permissions.
- The new permission has the same name as the custom MDF object you created.
- In Visibility, select View Current and View History.
- In Actions, select Create, Insert, Correct, Delete, and Import/Export.
You have now created the custom MDF object and given the compensation administrator access. Next, you must import the values associated with this object for each user. You can import values for individual users by means of the Manage Data page or do a mass user upload.
Note: We recommend using the Manage Data page to familiarize yourself with the MDF process or when you have a small number of users.
To add a new user:
- Add the user level MDF object information using Admin Center > Manage Data page.
- In the Manage Data page, from the Create New dropdown list, choose custom MDF object created above.
- Add the user as the externalCode, enter rest of the required fields and save.
- Please refer to this section of the guide to mass upload MDF data into the system. https://help.sap.com/viewer/e4a4ce68589841709a8202928c23803a/2005/en-US/b9150c127a08438a87e4a836fd2b4697.html
The MDF object should now be available for you to use in compensation planning. To use the MDF object in your compensation planning, you map the planning fields to MDF objects. Proceed as follows:
- From the Admin Center, enter Compensation Home into the Tool Search box.
- Select a compensation plan template.
- Navigate to Plan Setup > Design Worksheet > Design Worksheet.
- Select Add Column Custom.
- Set EC Category to Employment Details.
- Verify that the custom MDF object of type user is available under Employment Details (employmentInfo).
- Map the planning fields to the MDF object and save.
Note – Remember to mark translatable MDF custom fields as both reloadable and translatable in the compensation template.
- When you launch the compensation worksheet, make sure that fields have been mapped to the custom MDF object and populated correctly.
Configuring several custom MDF objects for use on the worksheets affects system performance. Please use caution to only map fields that are critical to optimizing the compensation decisions.
We love to hear from our customers! Please share your success stories on how you used an MDF portlet, or suggest other topics that we can cover. Please provide your feedback in the comment section below.
Also, help answer the following questions:
- What do you think is currently working and not working with this integration?
- Is there anything you think we should add?
- If you are interested in configuring custom MDF objects for your next compensation planning cycle, what use case will you try to address?
We will continue enhancing this integration to deliver solutions that address your unique business challenges. So, please use this post as point in time reference as of H1 2020 as the content might change with future enhancements. We will use this space to collaborate, share and learn from each other on this emerging topic!
Looking forward to hearing from you!
To access this blog on SuccessFactors Compensation community, please click here.
Thank you ! I am about to do my first MDF-Compensation integration today and this is very helpful. One addition from the post you made on the Compensation community and which is important : underscores are currently not supported in the MDF names for Compensation integration. So for example cust_IncentiveAmount will work but cust_Incentive_Amount will not work.
Xavier, thanks for the suggestion. I've updated the blog with this critical information.
Thank you so much!
I just created an MDF Object but I cannot see it in my Compensation Template.
Of course I have "EC Category: Employment Details" and for now set "Security: No" on MDF object definition. Plus, I have added 2 entries of users via Manage Data.
But my MDF is not appearing in Compensation Template. Have I missed a specific configuration flag? I can see other MDF objects in my Comp Template, for example "cust_companyProperty".
Hi Christoph, here is a successful set up I made yesterday in 4 steps (1 and 2 are both done in Configure Object Definition when you create the MDF).
Hey Xavier, you are my man! When i do not put in the underscores it works! Great Help! ?
Do you know if there are any additional requirements for custom MDF objects to work for Variable Pay History mapping? Or is it a limitation that these do not work there yet?
We have a field that maps perfectly fine in Compensation and Variable Pay summary row, but (even though it shows as available for history mapping) does not work for the History Fields mapping - causes an 'invalid field' error when we run 'import employee history from EC'.
Hi - currently, MDF objects are not supported for VP History extracts. That is on the roadmap, but not available as of H2 2020.
Thanks for the confirmation Phil!
Can MDFs be used to replace existing Guidelines under Plan Settings?
The standard guideline functionality has inbuilt validation logic which cannot be replicated using custom MDFs. However, you can use custom MDF fields as the guideline matching criteria.