3264867 - JobRequisition entity or JobOffer entity is missing in OData API - Recruiting Management

• JobRequisition or JobOffer entity does not appear in OData API Data Dictionary
• Unable to find JobRequisition or JobOffer entity in Integration Center
• Application Error when trying to create a Job Requisition from Position Org Chart

SAP SuccessFactors Recruiting Management

1. Go to OData API Data Dictionary.
2. Search for JobRequisition or JobOffer.
3. The entity is not found.

There are misconfigurations or discrepancies in object related settings such as Manage Recruiting Settings and Configure Object Definitions. 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.

How to check error log (For Support Only)

1. Refresh the metadata via 'OData API Metadata Refresh And Export'
2. Search by companyId + EntityResolverTask

How to fix the missing entity

Step 1 Correct the misconfigurations/discrepancies 

a) Standard object fields in Job Requisition templates

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

b) Custom object fields in Job Requisition templates 

1. Download Job Requisition templates
2. Search by type="object" in the template and see if any custom object fields are used
3. Go to Configure Object Definitions, set API visibility=Editable for the custom objects

c) Parent-child object fields in Job Requisition templates

• 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. (User Assistance Guide - Field Criteria Definition in Job Requisition)

Step 2 Disable and re-enable RCM related XML templates (Job Requisition, Job Application, Offer Detail) from provisioning

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

It is recommended to execute the following jobs after making changes in Configure Object Definitions.

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

Job Requisition, Offer, entity, not found, not appear, missing, available, odata, api, dictionary, Integration Center, EntityResolverTask , KBA , LOD-SF-RCM-API , Webservices & APIs , LOD-SF-RCM-JOB , Job Postings & Requisitions , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem