SAP Knowledge Base Article - Public

2883171 - COE_PROPERTY_NOT_FOUND: [COE0021]Invalid property names: EmpJob/emplStatus. - OData API

Symptom

In Integration Center or CPI Platform, integrations that include and/or built on the EmpJob OData Entity are failing with the below error:

"COE_PROPERTY_NOT_FOUND",
   "message": {
       "lang": "en-US",
       "value": "[COE0021]Invalid property names: EmpJob/emplStatus. Please check the property name in Admin Center > OData API Data Dictionary or entity metadata. Ensure there were no data model changes that removed this                           field, and please execute a refresh metadata to ensure the cache is not corrupted."

This error code is showing even when both EmpJob and field emplStatus are available and visible in the OData API Data Dictionary.

Environment

  • SuccessFactors
  • CPI

Cause

There was recently a disruption on one of the Data Centers which may have caused a Cache corruption issue.

Resolution

RE-IMPORT AND REFRESH PROCESS

  1. Kindly download Corporate Data Model from Provisioning and reupload same with a dummy change (one extra space or new line at the end).
  2. This will trigger Data Model Cache refresh.
  3. Then, please Refresh MDF Cache (via Provisioning).
  4. Post that please check the issue again.

Please Note: This dummy change will not bring any functional impact to system as we are not changing any object definition. It is required to ensure the DataModel cache refresh.

See Also

2171588 - OData API Metadata Refresh and Export - SuccessFactors Cloud

Keywords

COE_PROPERTY_NOT_FOUND, [COE0021]Invalid property names: EmpJob/emplStatus, EmpJob, emplStatus, Data Model, dummy change, MDF Cache , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , Problem

Product

SAP SuccessFactors HXM Core all versions