SAP Knowledge Base Article - Public

2770495 - Pre Picklist Migration - What are Picklist Migration Conflicts and how to adress them

Symptom

What is a picklist migration conflict?

When picklists of the same ID exist in MDF and legacy picklists, and this picklist is NOT part of a Legacy to MDF picklist mapping setting. When we run the pre-migration check, such picklists are displayed in the Picklist migration conflicts UI. Here the admin can take decisions on how he would like to maintain the picklist post migration.

Picklist Migration conflicts UI:

Picture9.JPG

Environment

All BizX non-picklist migrated instacne / Enabled with Picklist Managment

Resolution

1. Perfect Match Picklist – Default Merged (No Decision Tab)

  • Picklist ID is same on MDF & legacy
  • Options in picklist is same in MDF & legacy
  • External code, status & labels are all same

Example:

Prior to migration

Legacy Picklist – Employee

Picklist ID

OptionID

External Code

Status

Label US

Label FR

Label DE

Label ES

Employee

11

P

A

Permanent

Permanent

Permanent

Permanent

Employee

12

C

A

Contractor

Contractor

Contractor

Contractor

Employee

13

I

A

Intern

Intern

Intern

Intern

Employee

14

E

A

External

External

External

External

MDF Picklist - Employee

Picklist ID

External Code

Status

Label US

Label FR

Label DE

Label ES

Employee

P

A

Permanent

Permanent

Permanent

Permanent

Employee

C

A

Contractor

Contractor

Contractor

Contractor

Employee

I

A

Intern

Intern

Intern

Intern

Employee

E

A

External

External

External

External

After Migration:

Picklist – Employee (legacy option ID’s are copied over to the MDF picklists) 

Picklist ID

OptionID

External Code

Status

Label US

Label FR

Label DE

Label ES

Employee

11

P

A

Permanent

Permanent

Permanent

Permanent

Employee

12

C

A

Contractor

Contractor

Contractor

Contractor

Employee

13

I

A

Intern

Intern

Intern

Intern

Employee

14

E

A

External

External

External

External

2. Example of Partial Match picklist (Decision required tab)

  • Picklist ID is same on MDF & legacy (Case should match)
  • It is considered a partial match when one the below criteria is met
    • Number of options is different (based on external code match)
    • Mismatch is status when external codes are same
    • Mismatch in labels when external codes are same
    • In below example is partial match picklist, only the row highlighted in green is a perfect match 

Legacy Picklist – Employee

Picklist ID

OptionID

Status

External Code

Label US

Label FR

Label DE

Label ES

Employee

11

A

P

Permanent

Permanent

Permanent

Permanent

Employee

12

A

C

Contractor

 

 

 

Employee

13

A

I

Intern

Intern

Intern

Intern

Employee

14

I

E

External

 

 

 

Employee

15

A

A

Apprentice

 

 

 

MDF Picklist - Employee

Picklist ID

Status

External Code

Label US

Label FR

Label DE

Label ES

Employee

A

P

Permanent

Permanent

Permanent

Permanent

Employee

A

C

Contractor

Contractor

Contractor

Contractor

Employee

A

I

Intern

Intern

Intern

Intern

Employee

A

E

External

External

External

External

If you had chosen Merge decisions, this is how your picklist will look like after migration:

  • Option 1 - Merge picklist De-activate duplicates
    • Perfect match rows between legacy & MDF will be merged to single row, will retain legacy option ID
    • Legacy partial match rows will moved as new row, retaining legacy option ID , but with new generated external code since a duplicate in MDF picklist already existed
    • MDF options are retained, we will generate a new option ID for each
    • All duplicates based on external code prior to migration are set to inactive so admin of the instance can decide which to retain after migration

***Note:  

Applications will retain option ID reference to migrated options – DO NOT DELETE THEM

MDF objects will retain reference to existed MDF options via MDF internal ID -  DO NOT DELETE THEM

Picklist ID

OptionID

Status

External Code

Label US

Label FR

Label DE

Label ES

COMMENT

Employee

11

A

P

Permanent

Permanent

Permanent

Permanent

MERGED as this row was a perfect match

Employee

11290

I

C

Contractor

Contractor

Contractor

Contractor

Existed MDF

Employee

12

I

C~%1

Contractor

 

 

 

Migrated

Employee

11291

I

I

Intern

Intern

Intern

Intern

Existed MDF

Employee

13

I

I~%1

Intern

 

 

 

Migrated

Employee

11292

I

E

External

External

External

External

Existed MDF

Employee

14

I

E~%1

External

 

 

 

Migated

Employee

15

A

A

Apprentice

 

 

 

Migrated

  • Option 2 - Merge picklists
    • Perfect match rows between legacy & MDF will be merged to single row, will retain legacy option ID
    • Legacy partial match rows will moved as new row, retaining legacy option ID , but with new generated external code since a duplicate in MDF picklist already existed
    • MDF options are retained, we will generate a new option ID for each

***Note:  

Applications will retain option ID reference to migrated options  – DO NOT DELETE THEM

MDF objects will retain reference to existed MDF options via MDF internal ID -  DO NOT DELETE THEM

Picklist ID

OptionID

Status

External Code

Label US

Label FR

Label DE

Label ES

COMMENT

Employee

11

A

P

Permanent

Permanent

Permanent

Permanent

MERGED as this row was a perfect match

Employee

11290

A

C

Contractor

Contractor

Contractor

Contractor

Existed MDF

Employee

12

A

C~%1

Contractor

 

 

 

Migrated

Employee

11291

A

I

Intern

Intern

Intern

Intern

Existed MDF

Employee

13

A

I~%1

Intern

 

 

 

Migrated

Employee

11292

A

E

External

External

External

External

Existed MDF

Employee

14

I

E~%1

External

 

 

 

Migated

Employee

15

A

A

Apprentice

 

 

 

Migrated

  • Option 3:  Keep Picklists Separate 

Note 1: In this case after migration there are 2 picklists, legacy migrated picklist has generated MDF picklist ID Employee~%1. Legacy references are retained via an internally stored legacy picklist ID which will still legacy picklist ID. Thus no reference to EC or other applications is broken. But administration is difficult due to the 2 versions that need to be maintained

Note 2: Keep Picklists Separate option is defaulted if the picklists are the same but parent picklist is different in legacy and MDF.

Migrated Legacy Picklist – Employee

Picklist ID

OptionID

Status

External Code

Label US

Label FR

Label DE

Label ES

Employee~%1

11

A

P

Permanent

Permanent

Permanent

Permanent

Employee~%1

12

A

C

Contractor

 

 

 

Employee~%1

13

A

I

Intern

Intern

Intern

Intern

Employee~%1

14

I

E

External

 

 

 

Employee~%1e

15

A

A

Apprentice

 

 

 

MDF Picklist - Employee

Picklist ID

Status

External Code

Label US

Label FR

Label DE

Label ES

Employee

A

P

Permanent

Permanent

Permanent

Permanent

Employee

A

C

Contractor

Contractor

Contractor

Contractor

Employee

A

I

Intern

Intern

Intern

Intern

Employee

A

E

External

External

External

External

Keywords

Picklist Migration, MDF Picklist, Picklist Center, Picklist Management , KBA , LOD-SF-PLT-PCK , Picklist Management Issue , Problem

Product

SAP SuccessFactors HCM Core 1811 ; SAP SuccessFactors HCM Core 1902 ; SUCCESSFACTORS BIZX CORE 1905