2668885 - Wrong Picklist Value Label or Translation are Causing Job Information Record Import Failure

• Error message occurred while  importing job Information record with picklist
• Wrong Picklist Value Label or Translation are causing job Information Record Import Failure

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 Employee Central-Picklist

• Import job Information record containing Cascading picklist ( Parent - Child Picklist)
• Result:incorrect Picklist value

• Admin Center, select Picklist Management
• Select "Export all Picklist(s) and press submit
• Open Picklist file -select Picklist Id

Misconfiguration :

• Same Picklist Type with  Different External code , Same ParentOptionalId and Same Label or  Translation
• The label or Translation values are mapped to same parent

• The label or Translation must be unique and  both Picklist values are mapped to same parent and Picklist type
• Also if the value was mapped to different parent it will work

Example Solution: Solution : Same Picklist Type with  Different External code , Same ParentOptionalId and  ( Label or  Translation are Unique)

FAQ - Additional Information

Q) Where can I get information on this from the Guide or additional best practice?

A)

• 3550386 - Picklist label translation showing incorrect value
• 2217450 - Picklist Translations Are Not Available
• 2537488 - Best Practice to delete/inactivate a Picklist, Picklist versions or Picklist Values
• 2854672 - Special Characters in the Picklist Label Causing Error in UI and Report 
• 2537488 - Best Practice to delete/inactivate a Picklist, Picklist versions or Picklist Values
• You can refer to this Guide for Deletion: Deleting Picklists, Picklist versions or Picklist values

Picklist Management Tools

 You can now edit legacy picklist IDs from Picklist Center after they’re migrated to MDF. The Edit Picklist page allows you to edit Legacy Picklist ID field. Please note that a legacy picklist ID must be unique across all picklists.

• For picklists that are configuration outside MDF, for example, Succession Data Model, the value of Legacy Picklist ID needs to be used. Ensure that any changes made to the Legacy picklist ID are adjusted in all references to this picklist outside MDF.
• Since MDF picklists are effective-dated, you can always control the date from which the record takes effect.

Q) Why External Code = Non-unique External Code?

A) For all picklist: External Code = Non-unique External Code

Since the 'non-unique external code' is not maintained and a string null will be returned.

The customer should maintain the field 'non-unique external code' for the Picklist :Picklists, Foundation Objects, and Generic Objects

For HRIS (Human Resource Information System) segments, the non-unique external code of picklist values is returned. For the segments based on Metadata Framework , the external code is returned. However, if the external code or non-unique external code can't be determined, the field is omitted and a log item is added to the response.

Please check before changing any Picklist ID ( Please note that a legacy picklist ID must be unique across all picklists.)

• 2080801 - How to update Foundation Objects, and the respective Employee Data - Employee Central
• 2551350 - How to Update Generic Objects and the Respective Employee Data - Employee Central

For Hris sync Gap:

• 2964383 - MDF Field label name Change Doesn't Sync to Employee Profile Header after HRIS Sync (real time or Incremental Sync job)
• 3594029 - Daily or Full HRIS Sync job failure caused by Foundation Object Field Maximum Length

Picklist, Job information , import,Picklist Value ,Label ,Translation , KBA , LOD-SF-EC-EDP , Import Employee Data (EC Core only) , Problem