Update on picklist migration
Our commitment to causing minimal disruption to your business means that we will be postponing any further picklist migrations until the 2nd quarter of 2018, so that this does not affect the busiest time of the year for your HR processes. Customers will not be able to request migrations during this period.
We will work on a timetable for rolling conversions that will begin next year. Look for more information here towards the end of the 1st quarter of 2018
We will upgrade your administrative tools for picklist management and migrate all of your current picklist data to the MetaData Framework (MDF) format. This will be done automatically for you with no effort required by your system administrators. We will carry out the migrations in batches and you will be informed as to when the migration will happen in your system.
Currently, you have two areas where picklists can be managed:
“Legacy” Picklists, which are mainly used to manage Employee Profile, Talent modules, Recruiting Management and parts of Employee Central
MetaData Framework (MDF), which is mainly for Employee Central and extension applications built on MDF.
Once your picklist data has been migrated to the MetaData Framework (MDF), you can manage all of your picklists using the new Picklist Center. (Please note that existing scheduled jobs do not require a change to the import format.)
After this migration, you will see the following key benefits in using the Picklist Center:
A single place where picklist information is stored for Employee Central, Recruiting, Talent, and Employee Profile. The double maintenance of “legacy” and MDF Picklists will no longer be necessary
A user interface to manage changes to picklists. You will no longer have to export existing picklists, edit them in an offline spreadsheet, then re-import the updated file for a single label change. Instead, you will be able to make changes directly in the new user interface.
Maintenance across SuccessFactors and external environments will be easier by using unique external codes. By requiring unique external codes, picklists and picklist values will be easily identifiable and therefore easier to manage across environments.
For details on the new functionality, please see the FAQ_MDF_Picklists.pdf document attached to this KBA.
2504047 - Picklist Migration Process Guide
Picklist migration,Picklist migration update , KBA , LOD-SF-PLT-PCK , Picklist Management Issue , How To