on 2024 Dec 23 2:20 PM
Hi SAP Community,
I am currently working on a scenario where we need to include the Total Team Size field in the Background Elements, as it directly influences the bonus plan for employees. The Total Team Size is a field present in the Employee Profile, and we would like to know if it is possible to map this field to the Background Elements, as it appears in the dropdown list when mapping fields.
However, when attempting to map the field, I encounter the following error:
Has anyone encountered this issue or knows if there are any specific configurations needed to successfully map this field? Any guidance or suggestions would be greatly appreciated!
Thank you in advance for your help!
Best regards,
Request clarification before answering.
I have never tried this mapping but usually Time in Company, Total Team Size and other dynamic fields that recalculate on the fly when loading the EC profile are called transcient fields that are on display only and do not store any data which is most likely why it is failing in your mapping.
You could try through an MDF object with a business rule and integration center.
What is the business requirement behind having this field in employee history ?
All the best
Xavier
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Xavier,
Thank you for the clarification and suggestion.
However, the client does not want to create any additional fields in EC.
As for the business requirement, the reason we need this field in the employee history is that the bonus plan assigned to the employee depends on whether they are a manager (Total Team Size different from 0) or a regular employee (Total Team Size = 0). Therefore, we need this field to be available in the background element. There is no other field in EC that provides this information.
Kind regards,
@MariaCarlotaAbreu I just went to my demo and wrapped my head around the business requirement and I don't think you will be able to build this without either:
As a conclusion yes you can all build it without adding a field to EC thanks to MDF but it seems like it could be worth adding that new field because in my experience fields used in Compensation or often used in Performance and other talent areas as well.
Here some blogs to get you started on the MDF design if you decided to take that path:
Creating the MDF with an on save business rule :
Feeding the MDF with values using Integration center (vs manual UDF upload of UserID).
All the best
Xavier
| User | Count |
|---|---|
| 7 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.