2998326 - Constraints on using Multiple Third Party Vendors for Background Check - Recruiting Management

When configuring Background Check, it is possible to use Multiple Third Party Vendors, but the system have some constraints on it.

SAP SuccessFactors Recruiting Management

There are four different methods to implement Background Check in an environment, those are:

1. Integration Center: This would be the standard background check integration. The background check using integration center do not support multiple vendors, as the system does not have a way to select the specific Recriting Vendor Integation Mapping object that it should use to trigger the Integration Center job. This is dependent of the Default option configured on the object to work;
2. Intelligent Services: We are able to trigger the background check through Intelligent Services, but it would be as restricting as Integration Center, as it would rely on the listeners Update of Job Application and Update of Job Application Status, and we don't have the ability to distinguish which vendor is going to be used.
3. Middleware: This would be the option to go for if looking to have multiple vendors. You can still keep one of the vendors being called automatically from the Initiate Background check, and create an integation using a Middleware(like Boomi, for example) and then have this other integration being either triggered via ISC, or have that integration monitoring specific Job Requisition status for specific tamplates, and then trigger the other vendor on those cases.
   Another option, would be to not use the Initiate Background Check functionality at all, using only the middleware to trigger make the Vendor calls, and then you will populate the values from your job requisition as well, use a ISC event, such as Update of Job Application Status, and then inside the middleware trigger by the status the candidate is currently in before triggering the integration, or even before Getting the additional values from the Job Requisition that are required to execute the background check, and then after validating it in the middleware, proceed with the rest of the process.
4. Other custom integration or Script: Similar to option 3, but instead of having a middleware, you would have an custom integration or a script that would do the exact same thing the middleware would do, listening to status where you would like to have pull candidates from.

integration, center, intelligent, services, isc, middleware, custom, integration, multiple, third, party, vendors, background, check , KBA , LOD-SF-RCM-BCI , Background Check , How To