Symptom
When performing an API call to Compound Employee, the option ID value is being returned instead of the external code in picklist fields.
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 HXM Suite
- Compound Employee API
Cause
Wrong configuration in the Country/Region-Specific Succession Data Model.
Resolution
Please make sure that all the country specific fields in the Country/Region-Specific Succession Data Model have consistent data types. If different data types are configured for a field, it will lead to issues in Compound Employee.
So, for example, if you have a custom field that is shared in different country specific objects and it has "Type of Reference" equal to "Picklist" (sample below), please make sure that this field has the same configuration throughout all the country specific objects.
Picklists, Foundation Objects, and Generic Objects | SAP Help Portal
- For the Country/Region-Specific Succession Data Model, do not configure different data types for the same attribute.
- If different data types are configured, the Compound Employee API interprets the attribute value with the data type found in the first country/region-specific data model.
See Also
Keywords
ce, compound employee, api, sfapi, externalcode, optionid, , KBA , LOD-SF-INT-CE , Compound Employee API , Problem
Product
Attachments
Pasted image.png |