SAP Knowledge Base Article - Public

2727098 - Error Field offer_detail_latest_job_req_job_start_date is not defined when running standard candidate integration between SF and SAP - Recruiting Management

Symptom

When running the standard integration between SAP and SuccessFactors RCM for candidates export, the integration is falling with the following error message:

<ns2:SFWebServiceFault xmlns:ns2="urn:fault.sfapi.successfactors.com" xmlns="urn:sfobject.sfapi.successfactors.com">

<ns2:errorCode>INVALID_FIELD_NAME</ns2:errorCode>

<ns2:errorMessage>Field offer_detail_latest_job_req_job_start_date is not defined</ns2:errorMessage>

</ns2:SFWebServiceFault>

The report has been configured for some time and was working. This behavior is noticed after the 2018Q4 release.

 * The error may happen to other standard fields.

Environment

SuccessFactors Recruiting Management (RCM) - All versions

  • Integration with SAP ERP

Reproducing the Issue

Run the candidate integration between SuccessFactors RCM module and SAP ERP.

Cause

This error was caused due to a recent change implemented as part of the 2018Q4 release. SuccessFactors engineering team is implementing validations on SF side to ensure that the configuration is correct.

One of the validation is to check if all fields defined in the SFAPI dictionary are also defined in the XML templates.

Since this field, OFFER_DETAIL_LATEST_JOB_REQ_JOB_START_DATE (and other standards can be affected too), is used for this standard integration even if the customer does not use this field, it will be mapped between SAP and SF and it must be declared on SF side.

Resolution

To resolve this issue, the field must be defined in the Job Requisition and Offer templates.

Here are the steps and code example that can be used to solve the problem:

  1. Add this field to 1 JRDM,

<field-definition id="jobStartDate" type="date" required="false" custom="false">

<field-label><![CDATA[Expected Start Date]]></field-label>

<field-label lang="en_US"><![CDATA[Expected Start Date]]></field-label>

<field-description><![CDATA[Select a value]]></field-description>

<field-description lang="en_US"><![CDATA[Select a value]]></field-description>

</field-definition>

  1. Add a corresponding field to the corresponding offer template.

<field-definition id="jobStartDate" type="date" required="false" custom="false" template-type="job-req">

<field-label><![CDATA[Expected Start Date]]></field-label>

<field-description><![CDATA[Expected Start Date]]></field-description>

</field-definition>

  1. Wait 30 mins for the SFAPI data dictionaries to refresh.
  2. OFFER_DETAIL_LATEST_JOB_REQ_JOB_START_DATE should appear in SFAPI data dictionary for both the default RecruitingV2 entity, and the adhoc report entity

 Observation: The field does not need to be configured to populate, but its definition must be in the templates.

 * The error may happen to other standard fields in case they are used by the integration and are not defined in RCM module. The resolution will be the same as described here with small changes to the field definitions to accommodate the field that presents the error.

See Also

 RCM-57942

Keywords

Field offer_detail_latest_job_req_job_start_date is not defined, error when running candidate standard integration, candidate integration is failing , KBA , LOD-SF-RCM-INT , Integrations & Intelligent Services , LOD-SF-RCM , Recruiting Management , Problem

Product

SAP SuccessFactors HCM Core 1811 ; SAP SuccessFactors Recruiting all versions