3610253 - Issue with the Replication of Picklist Values via Compound Employee API Post 1H 2025 Release

After 1H 2025 Release, you are experiencing issues with the replication of picklist values via Compound Employee API. This is only relevant if you used different non-unique external codes for the same external code across different Picklist Versions.
Before the release, Compound Employee API returned the non-unique external code of the currently valid Picklist Version. After the release, the API is returning the non-unique external code of a previous Picklist Version.

SAP SuccessFactors Compound Employee API

The issue can be reproduced by attempting to replicate picklist values via Compound Employee API after the 1H 2025 Release.

With 1H 2025, a change was introduced to change the logic which reads the picklist values. The new logic does not correctly consider the effective dating of entity picklist. 
Please note this is only relevant in case there are multiple versions of the same picklist with different values of non-unique external code maintained in the system. 

The permanent solution of this issue is currently under investigation. Please follow this KBA for updates.
As a workaround we suggest to adapt the non-unique code of the prior picklist version and align it with the later one (at least for the needed values).
Alternatively, you may need to deactivate one version of the picklist (make it inactive).
The permanent fix will be available with P7, which as per https://community.sap.com/t5/patches/tkb-p/hxm-patches is:
03-Jun-25 in Preview
05-Jun-25 in Production

Compound Employee API, picklist values, replication, 1H 2025 Release, EC and ECP systems, non-unique external code, external code, ECT-254816, PTCH-47019, ECT-231333, KI2505, 1H 2025, 2505, KEA, Known Error, known issue, bug, error, fix, defect, release, production, preview, data, center, H1 , KBA , LOD-SF-INT-CE , Compound Employee API , Known Error