SAP Knowledge Base Article - Public

2773713 - Post Migration Odata API Picklist MDF and Legacy Behavior with OptionId and MDF ExternalCode

Symptom

- Some picklists are reading/writing (query/upsert) Option IDs(optionId) via ODATA API Operation

- Some of picklist are reading/writing (query/upsert) external codes(externalCode) via ODATA API Operation

Environment

 SAP Successfactors HCM Suite

Cause

Expected Behavior

Resolution

The query/edit behavior of picklist fields depends on which picklist entity it navigates to.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

* If the navigation points to PicklistOption, then optionId should be used to edit/query returns optionId value in the picklist field.

optionId.JPG

* If the navigation points to PickListV2, then externalCode should be used to edit/query returns externalCode value in the picklist field.

v2.JPG

Note:

Exclusively for the EC2MDF entities, our Employee Central colleagues mentioned that for now there is not yet any date planned for this migration to take place, and the recommendation from our EC team is to follow up the roadmap in the future for further details. You can check the new and upcoming changes at this link. However, as mentioned, our EC team does not have an estimate date for the EC2MDF migration yet.

See Also

2328179 - Legacy to MDF Picklist Migrations | Post-Migration Information - SuccessFactors

Keywords

optionId, externalCode, PicklistOption, PicklistV2, Picklist Migration, MDF Picklist, Legacy Picklist , KBA , LOD-SF-INT-MDF , Metadata Framework API (MDF) , LOD-SF-INT , Integrations , How To

Product

SAP SuccessFactors HXM Core all versions