SAP Knowledge Base Article - Public

2957351 - Approved Date of Job Requisition not Available in Integration Center or OData - Recruiting Management

Symptom

When trying to find the Job Requisition Approval Date field in Integration Center or using OData API, the field is not available but it's possible to find it in Adhoc Reporting.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

Environment

SAP SuccessFactors Recruiting Management

Reproducing the Issue

  1. Open Reporting, and create a new Recruiting V2 table report;
  2. Select Job Requisition column and search for "Approved Date";
  3. Now go to Integration Center, and create a new Integration;
  4. Select the JobRequisition Entity, and look for the Approved Date field;
  5. Not able to find it.

Cause

This happens because the Approved Date is not an exposed field through API. The field Approved Date is not stored directly into a Database table/column, and that is the reason why we can't find it in Integration Center, nor OData API.

Resolution

How come that we see the field in Adhoc then? - Adhoc has some additional columns that are not found in the Integration Center. That is because IC is pulling the data straight out from the database, the only information we have there is the information that is stored on the database. Now, on the Adhoc side, we have native calculated columns, which are hardcoded into the product functionality accordingly to the necessity of the customers.

On Adhoc, when we see the Approved Date column, we are actually seeing a calculation that the system is doing, getting information from the Audit and displaying to us on the field value.

As a workaround, you can create a custom date field in the Job Requisition template and configure an OnSave Business Rule to automatically populate this field whenever a Job Requisition is moved from Pre-Approved to Approved. This rule needs to be set up to fill the field only once and for that, one of the "IF" conditions must be if the field as a "null" value on it, therefore after being populated, the rule will no longer run.

Below is an example of the rule structure:

After creating the rule, save it as OnSave on the Job Requisition template. Besides that, you don't need to give the operator "read" or "write" permission.

Keywords

Adhoc, Ad, hoc, Approved, Date, Approval, Job, Requisition, OData, API, IC, Integration, Center , KBA , LOD-SF-RCM-API , Webservices & APIs , LOD-SF-RCM-JOB , Job Postings & Requisitions , Problem

Product

SAP SuccessFactors Recruiting all versions