Few Property Names of the ODATA API FOLegalEntityLocalUSA are automatically getting changed as below:
Initial Data (Property Names) in the OData API Data Dictionary:
Changed Data (Property Names) in the OData API Data Dictionary:
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
- ODATA API
Reproducing the Issue
- Go to ODATA API Data Dictionary
- Search Entity "FOLegalEntityLocalUSA"
- Search for the Properties having labels similar to "Fed Reserve Bank District", "Federal Reserve Bank ID", "Employer ID", "EO Company Code" etc. and validate if Property Names have been changed.
This is a known issue which is currently being analyzed by EC Engineering Team.
Though the Permanent Fix has not been given yet, there is a Workaround that will solve the issue.
The workaround is: add configuration data (new record) for Element Type Map for EC Migration object via Manage Data.
Below is the data that needs to be added for Element Type Map for EC Migration object:
After adding the above configuration data, please do an OData API Metadata Refresh (KBA 2171588), log out of your SFSF Instance, login again and the issue should have been resolved.
Frequently Asked Questions:
Q: What are the permissions required for viewing Element Type Map for EC Migration under "Manage Data"?
A: Please refer this Guide Document to get details on this query - Viewing the Element Type Mapping
Q: Would the Permanent Fix for this issue be given along with which future release?
A: Please always keep such configuration data (what has been suggested to you as workaround) and consider it as a best practice. Engineering Team is trying their level best to provide a permanent fix for this issue.
Q: Is it fine if you apply the same configuration to other instances as well where there is no such issue with "FOLegalEntityLocalUSA" API?
A: Yes, you can do that.
Q: How adding configuration data for "Element Type Map for EC Migration" resolves this issue?
A: In our code logic, there are 2 branches:
- If the configuration data of this entity is available, things become simple and clear. Just the mapping provided by the user is being used.
- Else, there will be default field logic, which would consider multiple other things, and is more complex.
Hence, this configuration eliminates the chance of occurrence of this issue. This is a tried and tested method.
FOLegalEntityLocalUSA, genericString1, genericString2, genericString3, genericString4, Property, Field Changes, OData , KBA , LOD-SF-INT-EC , Employee Central SFAPI & OData Entities , LOD-SF-MDF , Metadata Framework , LOD-SF-INT-MDF , Metadata Framework API (MDF) , Problem