- How to configure Recruiting Management integration with eQuest?
- What are required fields for RCM-eQuest integration?
- Enumeration setup pages
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
Recruiting customers can post jobs automatically to job boards and to multiple job boards simultaneously using the eQuest integration. Users can only send a job requisition to a job board through the eQuest aggregator. Customers can work directly with eQuest to negotiate a package to purchase job postings in bulk, or via the eCommerce (a la carte) solution. Once the customer has a contract with eQuest, the receive a login and password, which are required to configure the eQuest/RCM integration. You can find more information about eQuest on their website: http://www.equest.com/about/
Please note that eQuest Advantage (an a la cart solution) is not supported
Configuring eQuest Integration with Recruiting Management
eQuest is a paid service and requires a licence with the third party vendor. Customers should contact their Sales Representatives for more information. Once the licence is purchased, the Implementation Partner should set up the integration between RCM and eQuest.
Step 1: Configuring Authentication with eQuest
Authentication with eQuest can be established via Provisioning setup:
- Provisioning > EQuest Integration Settings
- Fill the following:
Correct URL: https://successfactors.equest.com/post/
Modify the following URL: https://<performancemanagerDCnumber>.equest.comOReu/rcmequestpost
e.g. correct URL for production DC5 is: https://performancemanager5.equest.eu/rcmequestpost and for DC4 it will be: https://performancemanager4.equest,com/rcmequestpost
What can happen if this is not configured correctly? The information abuot job posting won't return to the system: 2310007
Candidate Response URL:
Please review also the following Knowledge Base Article showing a use case of defining the jobPipeline: 2269773
Step 2: Providing Company Information to eQuest
Set up Company information in Admin Center > Manage Recruiting Settings:
Step 3: Ensure correct configuration in the job requisition template
The following fields are required in the Job Requisition XML:
○ Classification Type (maps to classificationType)
○ Contract to Permanent
○ Classification Time (maps to classificationTime)
○ City (maps to city in the JRDM)
○ Postal Code (maps to postalcode)
○ Recruiter Name(maps to recruiterName)
Classification Type, Classification Time and Country are also enum fiels with a short list of options. The short lists for these additional enums are built in to the application, so no additional configuration (other than adding them to the Requisition XML) is required.
These fields should be included in every Requisition XML and made required. If they are not shown or not filled in, the recruiting user will be asked to provide ALL of this information before the job will post.
Configure eQuest field permissions in the Job Requisition XML. Set eQuest fields to required for the preapproval stage to ensure values are provided, but read and edit permissions can be assigned however the client wishes.
Please notice that, since b1805 version, fields classificationType and classificationTime must be configured following the instructions below:
Step 4: Enable posting to job boards and grant permissions to users to post jobs to eQuest
Following option has to be enabled in Provisioning:
Provisioning > Company Settings > Enable Job Board Posting
In order to grant permissions to individual users / group of users to post jobs via eQuest grant following permission:
RBP: Admin Center > Manage Permission Roles > Recruiting Permissions > Grant eQuest Job Posting Permissions
non-RBP: Admin Center > Recruiting Permissions > Grant eQuest Job Positing Permissions
This permissions page allows a user or group of users to manage the External Job Boards table on the Job Postings page on a requisition Both tables on the Job Postings page are viewable by anyone who can see the requisition, but only those individuals who have posting privileges are able to modify the External Postings table.
Step 5: Configure Set Up Job Board Options in Admin Center (Enumeration Setup)
Go to Admin Center > Set up Job Board Options
- Configure countries and states in Country and State/Province Values Set up (they corresponse with the standard field-definitions in the job requisition templates: country and state with the type "derived";:
- Configure Industry Values Setup; This maps to the industry enum noted in the JRDM DTD. The screenshot below shows the COMPLETE list of options available. From this page, admins can select the industries that are applicable to their business, and leave out any industries that don't apply to them.
Step 6: Configure external eQuest Account
Only one eQuest login should be configured per company to avoid duplicate postings. Multiple eQuest logins for customers who require multiple user profiles are supported. Accounts can be mapped to a single user to allow themto use the account, or they can be mapped to all users with the * character in the upload.:
Navigate to Admin Center > Managing Recruiting > Manage External System Accounts. Enter equest in the EXTERNAL_Partner_CODE column.
RCM integration with eQuest, eQuest, Return URL, eQuest URL, Candidate Response URL, Recruiting Management, RCM , KBA , LOD-SF-RCM , Recruiting Management , How To