3264867 - Missing Entities JobRequisition, JobOffer, JobApplication or Candidate in OData API Dictionary and Integration Center - Recruiting Management

• One or more of the following entities are missing in the OData API Data Dictionary and cannot be found in Integration Center:
  • JobRequisition
  • JobOffer
  • JobApplication
  • Candidate
• Due to the missing JobRequisition entity, an application error occurs when attempting to create a Job Requisition from the Position Org Chart.

SAP SuccessFactors Recruiting Management

1. Navigate to the OData API Data Dictionary.
2. Search for JobRequisition or JobOffer.
3. Observe that the entity is not found.

Misconfigurations or discrepancies in object field-related settings such as 'Manage Recruiting Settings' and 'Configure Object Definitions'. For example, an object field configured in RCM templates is unavailable as an MDF object.

Possible causes are:

1. Standard Generic Object / Foundation Object fields are defined in Job Requisition templates, but the corresponding object types are not enabled in 'Manage Recruiting Settings'.

• Business Unit Object
• Legal Entity Object
• Department Object
• Division Object
• Cost Center Object
• Location Object
• Position Object

2. Parent-child object fields are defined in Job Requisition templates, but the associations are not configured in the object definition.

3. Standard or custom object fields are defined in Job Requisition templates, but the API visibility of the object is not set to "Editable" in the object definition.

4. Marketing Brand Object field (object-type="MarketingBrand") is defined in the Job Requisition template, but the Recruiting Marketing features are not enabled in Provisioning.

[For Support Only] How to check the error log

1. Refresh the metadata via 'OData API Metadata Refresh And Export'.
2. Search logs by companyId + EntityResolverTask or COGetODataApiDictionary (see internal memo).

Before configuring object fields in RCM templates, ensure that the related feature (if applicable) is enabled and that the object is available under 'Configure Object Definitions'.

Steps to Fix Missing Entity

If no misconfiguration is found in Step 1, proceed to Steps 2 and 3.

Step 1 Correct the misconfigurations or discrepancies

a) For Standard Generic Object / Foundation Object (GO/FO) Field Types:

1. In Job Requisition templates, search by type="object" and check if any of the following standard object fields are configured.
   • businessUnit_obj
   • legalEntity_obj
   • department_obj
   • division_obj
   • costCenter_obj
   • location_obj
   • std_position_obj
2. Go to Manage Recruiting Settings > Generic Object / Foundation Object (GO/FO) field types and enable the standard object types.

b) For Custom object fields:

1. In the related RCM templates, search by type="object" and check if any custom object fields are configured.
2. Go to Configure Object Definitions and set API visibility=Editable for the custom objects.

c) For Parent-Child object fields:

• If Parent-child object fields are defined in Job Requisition templates, make sure to configure the associations in the object definition via 'Configure Object Definitions'. (Help Portal Guide - Field Criteria Definition in Job Requisition)

d) For the Marketing Brand Object field:

1. In Job Requisition templates, check if the standard field "sfstd_marketingBrand_obj" or any custom field with object-type="MarketingBrand" is configured.
2. Go to Provisioning > Company Settings and check if the Recruiting Marketing features are enabled:
   
    - Recruiting Marketing
        - Enable Job Marketing
        - Enable Career Site Builder
        - Enable Candidate Account Simplification
   
   To use the Marketing Brand Object field, the Recruiting Marketing features must be enabled in Provisioning. 
   To keep "Recruiting Marketing" disabled, remove the Marketing Brand Object field from all Job Requisition Templates.
   
   

Step 2 Deactivate and re-activate the RCM templates related to the missing entity via Provisioning or Manage Templates

Step 3 Refresh the metadata via 'OData API Metadata Refresh And Export'

Recommended Jobs After Changes:

After making changes under 'Configure Object Definitions', execute the following jobs:

1. Clear MDF Cache via Provisioning> MDF Cache Tool > Clear Cache
2. Run "MDF Object Definition To DB SYNC" job via Scheduled Job Manager

KBA 2534674 - How To Schedule MDF Object Definition to DB Sync and Fix Inconsistencies In Metadata Framework

RCM, Job Requisition, Offer, entity, not found, not appear, missing, available, odata, api, dictionary, Integration Center, OData, API, EntityResolverTask, object, error, disappear , KBA , LOD-SF-RCM-API , Webservices & APIs , LOD-SF-RCM-JOB , Job Postings & Requisitions , LOD-SF-RCM-INT , Integration Center & Intelligent Services , LOD-SF-RCM-ONB , Onboarding integration , LOD-SF-RCM-CAO , Candidate Offers, Offer Letters , Problem