SAP Knowledge Base Article - Public

2533326 - Configuring Background Check with First Advantage

Symptom

FADV5.png

How to configure Background Check with First Advantage

Environment

SAP SuccessFactors Recruiting Management

Cause

The article explain the steps to configure background check with First Advantage.

Resolution

Note: Always seek assistance from your Professional Serivices or Partners for any configuration concern to make sure that you'll meet business requirements and to avoid issues with configuration.

Prerequisites

  1. The customer must have an existing contract with First Advantage, and should obtain the necessary URLs and credentials for the integration.
  2. The Xchange password for First Advantage must be changed every 60 days

Context

The integration between SuccessFactors and First Advantage allows joint customers to initiate and receive results of background checks and drug screens on candidates directly from the SuccessFactors Recruiting system.

Procedure

  1. Grant admin users permissions for Background Check Central.
    • Non-RBP: Managing Recruiting > Manage Recruiting Administration > Background Check Central
    • RBP: Manage Security > Manage Permission Roles > Select the Role > Permission > Administrator Permissions Manage Recruiting > Background Check Central
  2. Grant admin users permission to the First Advantage Background Check Integration Settings page using Admin Center
    • Non-RBP: Managing Recruiting > Manage Recruiting Administration > First Advantage Background Check Integration Settings
    • RBP: Manage Security > Manage Permission Roles > Select the Role> Permissions > Administrator Permissions > Manage Recruiting > First Advantage Background Check Integration Settings.
  3. Enable the First Advantage Background Check by navigating to Admin Center > Recruiting > Background Check Central > Enable Background Check > First Advantage Background Check Integration
  4. Configure the First Advantage integration settings under ***Provisioning*** > Managing Recruiting > Partner Settings First Advantage Integration Settings and
  5. Enter the integration URLs provided by First Advantage
    • Background Check Request URL for DA
    • Background Check Order Status URL
    • Background Check View Report URL
    • Background Check Candidate Order Status URL
    • Background Check Get Accounts URL
    • Background Check Get Packages URL
    • NOTE: If you dont have access to ***Provisioning*** , Please contact your Partners or Professional Services
  6. Under Provisioning > Company Settings > select Enable SFAPI Webservices
  7. Set the password logon exceptions. Navigate to Admin Center > Password Policy Settings > Settings > Set API Login Exceptions > Add. Enter the IP addresses the ODATA (Push) status responses are sent from and a minimum password age of -1.
    • NOTE : The following IP addresses should be included: 198.73.226.0-198.73.226.23, 66.241.32.160, 66.241.32.158, 66.241.55.193, and 10.8.248.108.
  8. Share the URL pattern for OData access with First Advantage. https://<hostname>/odata/v2/restricted/upsert?$format=json
    • Table 1: FADV Example URL's
    • Data Center URL
      DC8 Preview

      https://api8preview.sapsf.com/odata/v2/restricted/upsert?$format=json

      DC8 Production https://api8.successfactors.com/odata/v2/restricted/upsert?$format=json
      DC5 Preview https://api5preview.sapsf.eu/odata/v2/restricted/upsert?$format=json
      DC5 Production https://api5.successfactors.eu/odata/v2/restricted/upsert?$format=json
  9. Add the First Advantage Account and Package field to the job requisition XML for any relevant requisition templates
    • NOTE: if you dont access to the job requisition XML, please contact your Partners or Professional Services
    • <field-definition id="fadvAccountPackage" type="derived" required="false" custom="false”>
      <field-label><![CDATA[Fadv Account Package]]></field-label>
      <field-description><![CDATA[Fadv Account Package]]></field-description>
      </field-definition>
  10. Add or edit the backgroundCheck feature permissions to the applicable job requisition templates These permissions are the same as the Verifications, Inc. background check permissions.
    • <feature-permission type="backgroundCheck”>
      <description><![CDATA[R can launch on-boarding emails during statuses with a Hired category]]></description>
      <role-name><![CDATA[R]]></role-name>
      <role-name><![CDATA[G]]></role-name>
      <status><![CDATA[Offer]]></status>
      </feature-permission>
  11. Grant users permission to access the OData API
    • Non-RBP: Navigate to Admin Center > Manage Security > Administrative Privileges and select the user or group of users you would like to permission. Click Integration Tools > Admin access to OData API.
    • RBP: Navigate to Admin Center > Manage Security> Manage Permission Roles. Select the role that needs API access, then click Permission settings > Permissions > Administrator Permissions > Manage Integration Tools and select the Admin access to OData API permission.
  12. Configure First Advantage Background Check Integration Settings. Navigate to Admin Center > Managing Recruiting > First Advantage Background Check Integration Settings
    • Settings:
      • E-mail Applicant : This is a two step process where SuccessFactors sends applicant data to First Advantage and First Advantage contacts the candidate to invite them to fill out the missing background check data.
      • Allow account and packages to be selected at the application level: Users with the appropriate permissions can add, edit, or remove account and package combinations from the job application page. All updates will be reflected on both the job requisition and job application fields.
      • FADV4.png
      • Accounts and Packages: Synchronize accounts and packages from First Advantage
      • Parent Field Selection: Here you can select a job requisition picklist field as a parent field for the FADV account field. This refines the list of selectable accounts based on the parent field data selection.
      • Job Requisition: Map Job Requisition fields from each Job Requisition ML templates to the corresponding First Advantage fields.
        • NOTE: You cannot map the user-defined fields Due Date or Post Job Language in the Job Requisition. Additionally, Employment Type mapping only supports these values: current or prior.
      • Job Application: Map Job Application fields from each Job Application XML template to the corresponding First Advantage fields
      • Candidate Profile: Map Candidate Profile fields from the Candidate Profile XML template to the corresponding First Advantage fields Background Elements: Map Background Element sections and fields from the Candidate Profile XML template to the corresponding First Advantage fields
      • Background Elements: Map additional information from the Candidate Profile to FADV to send these fields to FADV when a background check or drug screen order is submitted.
      • API Credentials: Enter First Advantage API credentials (provided by First Advantage)
  13. Grant users the ability to view or initiate background checks. Navigate to Admin Center > Manage Recruiting > Recruiting Permissions > Background Check Initiate Permissions
  14. For customers who use different unique identifiers between SuccessFactors and First Advantage, map SuccessFactors employee usernames to the employee usernames entered in First Advantage in Admin Tools > Managing Recruiting > Manage External User Account
    • Export all external accounts.
    • Update the external accounts csv file:
  15. Export all external accounts and update the external accounts .csv file
    1. RECOMMENDATION:
    2. If the customer is using another integration (eQuest or Verifications, Inc.), ensure that you have the appropriate passwords for the accounts included in the exported file. Uploading this file without passwords for the existing accounts deletes the existing passwords and prevents users from being able to use the
      other integrations. All new First Advantage customers should use the same unique identifiers between the two systems. Customers who follow this do not need the additional configuration step
      • USER_NAME: SuccessFactors users’ usernames who need permission to the First Advantage system
      • EXTERNAL_PARTNER_CODE: Use FADV
      • PARTNER_USERNAME: Employee’s username in First Advantage
      • PARTNER_PASSWORD: Leave this blank because it is not needed

 

Keywords

Configure Background Check FADV Configuration First Advantage , KBA , LOD-SF-RCM-INT , Integrations & Intelligent Services , How To

Product

SAP SuccessFactors Recruiting all versions