SAP Knowledge Base Article - Public

2909791 - Picklist codes appended with suffixes "~%1", "~MDF" or "~LEGACY" - Post Picklist Migration

Symptom

  • After picklist migration, some picklists appear to be duplicated and have additional suffixes added to their IDs (such as “~%1” or “~%2” or “~LEGACY” or “~MDF”);
  • This is not to be confused with external codes of picklist VALUES appended with "~%1" suffixes. For that scenario, please refer to KBA 2786336.

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

Cause

Whenever two picklists with the same ID exist on both MDF and Legacy sides (prior to the migration) but do not match perfectly (e.g. amount of values, statuses or labels are different), the migration keeps them both separate and appends a suffix to their IDs to make them distinguishable.

For example, if a picklist ID “country” exists on both MDF and Legacy sides (with some mismatch between them prior to the migration), you will see two MDF picklists created on Picklist Center after migration, as follows:

Original picklist
(before migration)

Picklist Code
(after migration)

Legacy Picklist ID
(after migration)

country (Legacy)

country~LEGACY

country

country (MDF)

country

country~MDF

Prior to March 2020, the suffixes used were numerical and in the following format: “~%1”, “~%2” and so on. Those also used to be added to the original legacy picklist, as follows:

Original picklist
(before migration)

Picklist Code
(after migration)

Legacy Picklist ID
(after migration)

country (Legacy)

country~%1

country

country (MDF)

country

country~%1

Resolution

Please review where the picklists are being used/referenced across your instance and update the references to comply with the new Picklist Codes/IDs.

In the event of one of the picklists is not being used anywhere in your system and you want to deactivate and/or to rename one of them, then please follow the steps below.

For these resolution steps, we will consider, for example purposes, that you have a picklist named “country” and another one named “country~LEGACY” after migration.

1. Please review which of your two picklists is the correct one to be kept based on your business needs (e.g. “country” or “country~LEGACY”);

2. Then, make sure to take a backup of both picklists (for security reasons) and to confirm everywhere on your instance where the respective picklist is being used, so that you can adjust those references later accordingly;

3. After that, depending on the correct picklist to be kept, follow the below:

3.1 If the correct picklist is "country"
All you need to do is to change the status of picklist "country~LEGACY" to INACTIVE and make sure that your references are set to the desired picklist (“country”).

3.2 If the correct picklist is "country~LEGACY", then:
a) Rename the "country" picklist to anything such as "country_OLD" or “country_DONOTUSE”
b) Now, rename the "country~LEGACY" picklist back to "country"
c) Change the status of picklist "country_OLD" (or “country_DONOTUSE”) to INACTIVE
d) Make sure to restore your references and have them point to the correct picklist

You can perform the steps above manually via Picklist Center (for which detailed instructions are available on the Picklist Center guide) or massively by exporting and importing your MDF Picklists (for instructions on how to do so, please refer to KBA 2714036 - How to Import and Export MDF Picklists).

See Also

2816504 - How to resolve Post Picklist Migration issues

Keywords

Picklist Center, mdf picklist, duplicate picklist, duplicate picklists, legacy picklist, migration, ~LEGACY. ~MDF, ~%1, ~%2
, KBA , LOD-SF-MDF-PKL , Picklists , LOD-SF-PLT-PCK , Picklist Management Issue , How To

Product

SAP SuccessFactors HXM Suite all versions