Symptom
Child object configured as a GO reference field of another Object may not work for MDF import / Odata API scenarios to update MDF data.
The MDF import or the Odata API updating may fail.
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
Environment
SAP SuccessFactors HCM Suite
Reproducing the Issue
- Configure a child object (effective dating= From parent) as a GO field in another Object
- The data updating from UI (manage data, people profile.etc) may work, however, it may not work for MDF import / Odata API scenarios to update MDF data.
Resolution
MDF does not support to configure a child object in another MDF Object as a Generic Object reference field.
System will throw Warning message as below before you saving suhc configuration:
"You have used object cust_abc as the valid value source for field cust_DEF. The effective dating of object cust_abc is set to “From Parent”. This will lead to errors in accessing quickcards and many other issues. Please remove the field reference."
Below is the warning message example:
It may not work for MDF import / Odata API scenarios to update MDF data, the Odata API updating or the MDF import will fail and causes data corruption.
If configure a child object in another MDF Object as a Generic Object reference field, will also cause MDF Portlet in PPX shows error problem.
To avoid application errors, such as failure to access quickcards, do not use composite child objects as the value source of a field.
Keywords
MDF, metadata framework, reference, GO field, Generic Object Field, SF, SuccessFactors, child object, Odata API, MDF import, import, fail, We could not process your request as the entity “xxx” has unsupported fields. Update or remove these fields from the object definition. See details: fieldName:xxx, fieldDataType:GO. , KBA , LOD-SF-MDF-IMP , Import and Export Issues , LOD-SF-MDF-API , OData APIs & Integrations , Problem
Product
Attachments
| Pasted image.png |
| Pasted image.png |
SAP Knowledge Base Article - Public