3738731 - Recruiting API Calls Failing - Recruiting Management

This KBA explains a known issue where RCM OData API calls fail after metadata refresh or metadata rebuild because the metadata is resolved based on the granted features and permissions of the user who performs the refresh.

This is to understand:

• why RCM OData API calls may fail after metadata refresh or metadata rebuild
• how the use of isFeatureExist affects metadata resolution
• what happens when metadata refresh is performed by a proxy user without the required RCM proxy permissions
• what action is needed to restore the missing RCM metadata

In this scenario, the subsequent API call may fail because the corresponding entity is not found from the metadata.

SAP SuccessFactors Recruiting Management 

When a metadata refresh or metadata rebuild is performed, the system rebuilds the metadata used by the OData API.

If isFeatureExist is used, the metadata is resolved based on the granted features of the user who performs the refresh.

Because of this, if the refresh is done by a proxy user who does not have the required permissions to proxy Recruiting Management (RCM), the rebuilt metadata may not include all RCM related entities.

This can cause later RCM OData API calls to fail, because the API may no longer find the required entity in the metadata.

A common scenario is the following:

• a proxy user opens Admin Center
• the proxy user performs metadata refresh
• the proxy user does not have the required RCM proxy permissions
• RCM related metadata is dropped
• subsequent RCM OData API calls fail

To resolve the issue, perform the metadata refresh again using either:

• a regular user with the appropriate permissions, or
• a proxy user with the required RCM proxy permissions

This refresh restores the missing RCM related metadata and fixes the RCM OData API failures caused by the incomplete metadata.

Click on star to bookmark this article to receive updates about this issue. For more information about updates from subscribed KBAs, you can refer to the KB Article 2171560 - How to be notified of new or updated SAP Notes or KBAs.  

API Failing, API Calls not going through, RCM OData API, metadata refresh, metadata rebuild, isFeatureExist, entity not found, metadata missing, proxy user, proxy permission, Recruiting Management proxy, Admin Center, RCM metadata dropped, OData metadata issue, API failure, RCM-API,  JobRequisition, JobApplication, Candidate, Offer, entites, API entities, Recruiting, RCM, 1H2026, KI1H2026, 2605, RCM-159138 , KBA , LOD-SF-RCM-API , Webservices & APIs , Known Error