3512249 - MDI Cost Center Replication error Error details: ID conflict with existing database record:

You are trying to perform Cost Center Replication via Business Scenario : Cost Center Replication from SAP Master Data Integration to EC and you are getting the below error while running the Business Scenario

Display Name: 8000/0000001110/DEVxyz0001, Error details: ID conflict with existing database record: [entityOID=xxxxxxxx, externalCode=00000000001, internalId=0000001, costCenterExternalObjectId=00000010, entityUUID=null], OID: xxxxxxxxxxxx, Version Id: df283ee1-cbe4-4114-8c79-61e77a952b47, Event Type: created

Disclaimer: 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

• Integrations
  • Business Scenario
    • Cost Center Replication from SAP Master Data Integration to EC

This could be because of one of the below reasons

• The customer has not configured the integration configuration object (see https://help.sap.com/docs/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL/634eabb3d94044d2b319aaf7a8f18fb9/981db612c44a4768a121d1b033c45ed9.html?version=2405 ).
• This could also be because of the API USER running the MDI Business Scenario doesn't have enough for Configuration Object

• Validate the Integration Configuration, this should be done if there are existing cost centers in the SF instance to successfully sync the cost centers from MDI with the SF data. https://help.sap.com/docs/SAP_SUCCESSFACTORS_EMPLOYEE_CENTRAL/634eabb3d94044d2b319aaf7a8f18fb9/981db612c44a4768a121d1b033c45ed9.html?version=2405
  
  Customer should configure the "External Code Mapping" so that the external code that is created during integration matches with the existing data. For customer, the most likely configuration would be "Company Code and Cost Center External ID" to prepend the cost center ID with the company code.
  
  Note: After customer created the configuration object, they should make sure to set the option "Is Migration Run" to "true" there. Afterwards, they should run the initial load again (i.e. resetting the delta token in the business scenario to INITIAL again). The "Is Migration Run" setting will be reset to "false" after a successful integration run. If there are still some failing records and customer wants to re-run the scenario with token INITIAL again, they should always check the "Is Migration Run" before. (For delta load afterwards, this is not necessary of course)
  
  
• The API user does not have the permissions for the configuration object. Currently, it is required that the user running the job must have at least the read permission assigned to it. Otherwise, the default configuration values are used as we have seen in our logs (and therefore we assumed that the config object is not present yet). Please maintain the permission for this user.

  We would also recommend to change the setting "Cost Centre Identification Field" in the configuration object from "Entity OID" to "External Code" to make sure that existing cost centers are correctly updated during the initial load.

If the issue still persist, please raise a case with LOD-SF-INT-MDI team.

MDI, Cost Center, LOD-SF-INT-MDI, Business Scenario, cost Center replication, Error details: ID conflict with existing database record, LOD-SF-INT , KBA , LOD-SF-INT-MDI , OneMDI Business Scenarios , LOD-SF-INT , Integrations , Problem

SAP SuccessFactors HCM Core 2405 ; SAP SuccessFactors HCM Suite 2405