- Found orphan children picklists for matching parent picklists
- Legacy picklist and/or MDF picklist have the parent picklist identifiers match but the child picklist identifiers are not the same
SAP SuccessFactors HCM Suite
Reproducing the Issue
A customer is using the Validation/Merge Tool to check for picklist conflicts prior to the Picklist Migration. They have a legacy picklist and an MDF picklist where the parent picklist identifiers match but the child picklist identifiers are not the same. For example, a picklist entry (or multiple picklist entries) might be present in the Legacy Picklist but not in the MDF Picklist. Alternatively, the reverse might be the case where a picklist entry (or multiple picklist entries) are present in the MDF Picklist but not in the Legacy Picklist.
There are two ways to resolve this conflict:
- [RECOMMENDED] Make the two parent picklists (legacy and MDF) a perfect match by adding the missing child picklist entries to the parent picklist that is missing the child entries. For the picklists to be a perfect match, all entries must exactly match including all external codes, labels, status, number of options and locales
- Remove the parent picklist mapping reference for the additional child picklist entries (see KBA 2273480). This will allow the migration to continue. Note that depending on the usage of this child entry in the system, this may not always be a feasible option.
Picklist Migration, MDF Picklist, Legacy Picklist, Precheck, Premigration, pre picklist migration , KBA , LOD-SF-PLT-PCK , Picklist Management Issue , LOD-SF-MDF-PKL , Picklists , Problem