2504047 - Picklist Migration Process Guide

SAP Knowledge Base Article - Public

2504047 - Picklist Migration Process Guide

Symptom

Picklist Migration Process

Environment

Platform

Cause

We are in the process of migrating picklists to one common framework, built on the Metadata Framework (MDF). Over the coming months, all legacy picklists will be migrated to MDF. In many cases, we can complete the migration with no effort on your part. In some cases, however, we need administrators to complete some steps prior to the migration.

Picklists in all SAP SuccessFactors instances will be migrated to the new framework in batches, over the coming months. Read this overview of the process.

Resolution

Important Update:

Our commitment to causing minimal disruption to your business, we are currently postponing picklist migrations until the 2nd quarter of 2018, so that this does not affect the busiest time of the year for your HR processes.

Hence we are currentlly not taking request to migrate picklist.

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.

Picklists in all SAP SuccessFactors instances will be migrated to the new framework in batches, over the coming months. Read the overview by clicking Picklist Migration Process.

Preparing Your Instances for Picklist Migration

In some cases, we may need your input before we can migrate your legacy picklists in each of your SuccessFactors instances.

If we have identified conflicts between your existing legacy and MDF picklists that we don't know how to resolve, you need to resolve them before we can complete the migration. You can resolve many of these conflicts with the new Picklist Merge Tool. Other conflicts may require additional steps, with legacy picklist management tools or offline tools that we provide.

Remember: You need to resolve picklist migration conflicts in both your Preview and Production instances.

Picklist Merge Tool

The Picklist Merge Tool is a temporary tool used prior to picklist migration. Use it to tell us how to handle conflicts we've identified that are preventing migration of your legacy picklists to the new framework.

If we have identified some conflicts that require your input, we will enable the Picklist Merge Tool temporarily in your instance. It is only visible in instances where it is needed and it is only used prior to migration. After your legacy picklists have been successfully migrated to MDF, this tool disappears.

You may see example in Picklist Merge Tool guide.

Resolving Conflicts with the Picklist Merge Tool

Use the Picklist Merge Tool tool to tell us how to handle the conflicts we identified in your picklists.

If we have identified some conflicts that require your input, we will enable the Picklist Merge Tool temporarily in your instance. It is only visible in instances where it is needed and it is only used prior to migration. After your legacy picklists have been successfully migrated to MDF, this tool disappears.

If you can't see this tool in your instance, you: (1) have not yet been scheduled for migration and checked for conflicts; (2) do not have any conflicts affecting migration; or (3) have successfully completed migration.

Note: You need to resolve picklist migration conflicts in both your Preview and Production instances.

You may see the procedure by clicking Resolving Conflicts with the Picklist Merge Tool guide.

After Picklist Migration

After your legacy picklists have been migrated to MDF, you can use the Picklist Center admin tool to manage picklists in your instance.

The Picklist Center offers the following advantages:

  • Ease of management

    You can change a single picklist value or subset of picklist values, and edit the attributes and values of a picklist. You can choose the picklist name and then navigate to the picklist element that you want to change.

  • Mandatory, unique external codes

    Through both the UI and the import/export mechanisms (admin tool and scheduled job), you can enter a unique external code for every picklist (including parent-child picklists).

  • Single, suitewide set of picklists

    You only have to manage a single picklist for each picklist type. For example, if you need a Country picklist in several places, you don't have to maintain separate Country picklists and create a mapping between them.

  • Effective-dating

    You can assign an effective date to picklist values so that they are only shown as of their assigned effective date.

Accessing Picklist Center
As an administrator, you can manage picklists using the Picklist Center.
Creating a New Picklist Using the Picklist Center
Create a new picklist in Picklist Center.
Editing a Picklist Using the Picklist Center
Follow this procedure to edit an existing picklist.
Creating and Editing a Picklist Value Using the Picklist Center
Follow this procedure to add a new picklist value to an existing picklist or to edit an existing picklist value in an existing picklist.
Importing or Exporting a Picklist
Follow this procedure to import picklists to or export picklists from your instance.

 

Non-Unique External Code

The "non-unique external code" is a field in the PicklistValue MDF object that contains the legacy "external code" value after your picklist migration.

In legacy picklists, the "external code" field had no validation, so it could be any value, and it was not required, so it could be empty. With MDF picklists, the "external code" field is mandatory and must be unique. As a result, in many cases, the migration of this field couldn't be a straight one-to-one mapping. In such cases, the legacy "external code" value" is stored in a new MDF field called the "non-unique external code". After migration, pages in the application that previously used legacy picklists now use the "non unique external code" to read legacy picklist values and ensure that there is no change to end-user experience.

By default, after picklist migration, in the PicklistValue MDF object, the value of the unique "external code" and the value of the "non unique external code" (copied from legacy picklists) are kept in sync. That means that, after migration, any change you make to the "external code" field in the PicklistValue MDF object will automatically be copied over into the "non unique external code" field as well.

However, this behavior can be changed. You may have used the legacy "external code" field in legacy picklists for a specific purpose that we could not anticipate and not want them to be synced automatically with the MDF "external code". In this case, you can choose to disable this sync and treat the "external code" and "non unique external code" as two distinct and separate values.

Disabling Sync of Non-Unique External Code

Disable the automatic sync between the "non-unique external code" and "external code" fields in the PicklistValue MDF object.

Procedure
  1. Create a Support ticket.
  2. Request to have the following option disabled: Picklist Management: Automatically copy External Code to Non Unique External Code
Results

After this option is disabled, the value of the "external code" field in the PicklistValue MDF object is no longer copied automatically in the "non-unique external code" field. Instead, you can treat each field as distinct and use them for different purposes.

Fields Hidden in Picklist Center

Some MDF picklist fields are hidden in Picklist Center by default. If needed, these can be made visible by editing the PicklistValue MDF object.

By default, only the most commonly used fields are displayed in Picklist Center. Other fields exist in the database and in the PicklistValue MDF object, but are hidden from view to make Picklist Center simpler to read and use. However, in some cases, you may want to make of these hidden fields visible and editable in Picklist Center.

Example

The legacy picklist fieldValueis used bySAP SuccessFactorsRecruiting. Setting this field to99999allows for a job requisition to be closed. The legacy field is migrated to theoptValuefield in MDF. If you are usingSAP SuccessFactorsRecruiting, you may want to make theoptValuefield editable in Picklist Center after your picklist migration.

You may see the Procedure on how to Make fields in the PicklistValue MDF object visible and editable in Picklist Center in Revealing Hidden Fields in Picklist Center guide.

Guides:

You may also see the Troubleshooting Picklists.

Field Migration from Legacy Picklists to MDF Picklists

- Description of how each legacy picklist field is migrated to MDF

See Also

2328179 - Legacy to MDF Picklist Migrations | General Information

2537153 - Picklist Migration Plans - Important Update!

Keywords

Picklist Migration, Legacy to MDF Picklist, Picklist Migration update , KBA , LOD-SF-FWK-MDF , MDF Framework , Problem

Product

SAP SuccessFactors HCM Core 1705