-> The 'Object Definition' for Cost Center Object is exactly the same in two different instances (refer screenshot below)-
-> However when we see in 'Odata API Data Dictionary', the field names itself are different (refer screenshot below)-
Odata Cost Center Entities in SFSF Instances
Reproducing the Issue
Just login to both the instances and view 'Odata API Data Dictionary' and you can see the differences clearly.
-> Login to the Successfactors Instances in different browsers and navigate to 'Admin Center -> Manage Data -> Element Type Map for EC Migration'.
-> Now search for 'Cost Center' in the second tab and you can see that either there is no entry for 'Cost Center' in the instance where you have the correct field name displayed i.e. 'endDate' or if you have an entry, the field will be added in the 'Field Map' section shown as follows:
***NOTE: If "Element Type Map for EC Migration" is not present in those instances, please try to give the login user the proper permission. (Please refer to attached screenshot to enable this feature and then provide "Element Type Map for EC Migration")
-> The resolution is to either remove the Cost Center entry from the 'Element Type Map for EC Migration' or add the field mapping in it as shown below-
Different field names for the same object definition in different instances, for example- 'effectiveEndDate' and 'endDate'. , KBA , LOD-SF-INT , SF Integrations - EC Payroll, Boomi/ HCI, API , Problem