3151051 - Change MDF Object External Code Via Import Vs Via Manage data

• Change MDF Object External Code Via Import Vs Via Manage data
• Change of Cost Centre Code FAILED via Import Data but not Via Manage data

"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 HXM Suite

Via Manage data  

Example: MDF Cost Centre with Name "SAP Controlling", code changed from SAPXXX to SAPYYY

• Go to Manage data
• Cost Centre > search
• select Cost Centre value
• Take Action 
• Make Correction
• maintain externalCode field value

Via Import

• Go to Import and Export Data
• Import
• Zip File
• Check monitor job: result
• Successful
• Check Manage data – cost center
• Result: No Update

 The data import created the 2 new cost centers, and duplicated also the entityUUID AND mdfSystemRecordId.

Summary : Change of Cost Centre Code FAILED via Import Data but not Via Manage data

As designed, It is not possible Via Import and export Data

It's work as designed. It is possible to change the external code for MDF objects in manage data only. (Not Via  Import and Export data)

If the import file has a changed external code, then a new object is created, since the import does not know the old external code.

FAQ - Additional Information

Q) Where can I get information on this from the Guide?

A) Guide: Implementing the Metadata Framework (MDF)

Chapter: Importing MDF Data

 2592673 - Import and Export Data not available in Action Search and Tool Search

MDF, Manage data, import and export data, INC1515020, external code, FOO, foundation object, Metadata framework, Import and Export data page , KBA , LOD-SF-EC-FOO , Foundation Objects (Organisation, Pay and Job Structures) , LOD-SF-EC , Employee Central , LOD-SF-MDF , Metadata Framework , Problem