3687624 - Background Check Integration Errors: "Invalid property names: JobApplication/requestId" - Recruiting Management

• Unable to initiate background check using Action > Initiate Background Check.
• Error message: Invalid property names: JobApplication/requestId. Please check the property name in Admin Center > OData API Data Dictionary or entity metadata. Ensure there were no data model changes that removed this field, and please execute a refresh metadata to ensure the cache is not corrupted.

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

SAP SuccessFactors Recruiting Management

1. Open a job application.
2. Select Action > Initiate Background Check.
3. An error is displayed: Unable to initiate background check. Error occurred while executing integration center process.
4. In the Integration Center, observe an error: Invalid property names: JobApplication/requestId. Please check the property name in Admin Center > OData API Data Dictionary or entity metadata. Ensure there were no data model changes that removed this field, and please execute a refresh metadata to ensure the cache is not corrupted.

1. The integration job in Integration Center is built using the JobApplication entity rather than the JobApplicationBackgroundCheckRequest entity.
2. The integration type is 'Intelligent Service' rather than 'Application / UI'.

The Initiate Background Check option in the Action menu is designed for 'Application / UI' type integrations that are built using the JobApplicationBackgroundCheckRequest entity. During this integration process, the system will generate a unique requestId (JobApplicationBackgroundCheckRequest/requestId).

If the integration is built using the JobApplication entity, the system will try to query JobApplication/requestId, which does not exist.

1. Review the integration type.

1. Navigate to Integration Center > My Integrations.
2. Edit the integration job.
3. Go to the 'Review and Run' tab.
4. Check the integration type. (see below examples)

2. Follow the correct process to trigger the integration.

To trigger an 'Application / UI' type integration, open the application and select 'Action > Initiate Background Check'. Note: This type of background check integration must be built using the JobApplicationBackgroundCheckRequest entity.

To trigger an 'Intelligent Service' type integration, update the job application or the job application status based on the selected Intelligent Service Center (ISC) event. Note: This type of background check integration cannot be not triggered using the 'Initiate Background Check' option.

Example of 'Application / UI' type integrations:

• Type: APP / UI
• Starting entity: JobApplicationBackgroundCheckRequest

Example of 'Intelligent Service' type integrations:

• Type: ISE
• Starting Entity: JobApplication
• Intelligent Services Event: "Update of Job Application" or "Update of Job Application Status"

KBA 2768811 - Configuring Background Check Integration (Integration Center) - Recruiting Management

KBA 2851325 - How Background Check Integration Works (Intelligent Services) - Recruiting Management

RCM, BCI, Background Check, Integration, Integration Center, IC, Intelligent Service Center, ISC, Job Application, Update, Error, Failed, JobApplicationBackgroundCheckRequest, JobApplication , KBA , LOD-SF-RCM-BCI , Background Check , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem