This KBA explains how to enable the missing associations for EC to MDF migrated entities in the OData Data Dictionary.
Successfactors Employee Central System
Reproducing the Issue
This issue is explained by taking FOCostCenter as an example.
1. Logon to successfactors system.
2. Goto Admin Center --> Configure Object Definition and open the definition of FOCostCenter.
3. When we check the OData Data dictionary these fields will be missing(In the OData dictionary, you can find fields for these associations. They are called like in the MDF definition (cust_toFOWBusinessUnit, cust_toFOWCompany). What is missing is fields that have exactly the same name as before the EC2MDF migration: businessUnitFlx, companyFlx).
The root cause for the same is Element Type Mapping is missing for the entity for which associations are missing in the data dictionary
A second possible cause can also be that the element type map is there but that it simply does not contain the association mapping
The resolution is to configure the element type mapping for the corresponding entity.
Here is an example for which the element type map for EC migration has been configured for costCenter Entity
Refrsh the OData metadata and load the ODaat API data dictionary
The mising associations have been added into the OData api data dictionary.
http://help.sap.com/hr_ec/ --> Migrating to Metadata Framework (MDF) Foundation Objects
KBA , LOD-SF-INT-EC , Employee Central SFAPI & OData Entities , LOD-SF-INT-BOM , Standard SF to 3rd Party Boomi Content , How To