Pre Picklist Migration Error: "Found a hierarchy that consists of an EC2MDF picklist(s) with non-EC2MDF parent(s). Please resolve before proceeding."
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
- SAP SuccessFactors HCM Suite
- Metadata Framework (MDF)
Reproducing the Issue
- Go to "Validation Check & Merge tool" for Picklist Migration
- Access "Premigration Check Result" tab
- The following error shows up: "Found a hierarchy that consists of an EC2MDF picklist(s) with non-EC2MDF parent(s). Please resolve before proceeding."
This error will show-up when the parent(s) of an EC2MDF-mapped picklist pair are not EC2MDF-mapped.
It can happen in two situations:
- Both legacy and MDF picklists have a parent, but the parents are not EC2MDF mapped
- Only one side has a parent
In either case, the picklist pair cannot be merged, because EC2MDF-mapped picklists are supposed to be perfectly matched, but now they are actually not.
Since an MDF picklist must have at most one parent, a matching legacy and MDF picklist pair cannot have different parents, otherwise a merge won't be possible.
There are 3 possible directions to resolve this:
Scenario #1: Consider whether the parent-child relation can be removed, e.g. if this relation is not actually used(no picklist value in the child picklist has a parent picklist value).
Scenario #2: If the parent picklists are meant to the same, create an EC2MDF mapping between the parent picklists, so that the whole hierarchy of picklists (down from the parents) can be merged.
For the case where only one side has a parent, we can also consider creating a new parent picklist on the other side, and then making them EC2MDF-mapped.
Scenario #3: If the parents are meant to be different, then consider whether the EC2MDF-mapped child picklist pair are actually different so that the current EC2MDF mapping should be removed. This leads to the whole hierarchy to be kept as separate picklists.