Symptom
- A custom object has been associated with a FO, like 'FO Pay range' for example.
- The API visibility for the field inside the FO Pay range is showing as False.
- The visibility remains False even after attempting to update it in the corporate data model.
- The issue is exclusive to the API side, as the field is visible in the UI, specifically in the Employees Profile.
Environment
- SAP SuccessFactors HCM Suite
- MDF OData API
Reproducing the Issue
- Go to OData dictionary.
- Search for FOPay Range.
- Under that field, the cust_salary grade field visibility is showing as False.
- Even when importing the Corporate Data Model for trying to modify this property, the Visibility still keeps showing as False.
Cause
Resolution
The simple Properties for the custom object (custXXXXX) is upsertable, but not visible, while the navigation properties (custXXXXXNav) is not upsertable, but visible.
FOPayRange is a legacy FO object, and custXXXXX is an MDF object. When there's an FO object associated to an MDF object, the behavior is as described below:
Simple property: name is "MDF object name's", upsertable only (not viewable).
Navigation: name is "MDF object name's +Nav", readable only (not upsertable).
So this is working as designed. For your integration project, please choose the navigation property (**FlxNav) to read the data.
See Also
https://launchpad.support.sap.com/#/notes/0003050437 - How associations between Foundation Objects (FOs) and migrated FOs (MDF FOs) in Employee Central are translated to properties in their OData API entities - SAP SuccessFactors HXM Suite
Keywords
SAP SuccessFactors, Employee Central, Custom Object, API Visibility, FOPay Range, cust_salary_Grade, Odata dictionary, Metadata Framework API, MDF. , KBA , LOD-SF-INT-MDF , Metadata Framework API (MDF) , Problem