2558501 - Filter for Country and Zip/Postal Code Available in Application List Page - Recruiting Application

Within B1711 Release, the Applicant List page (Candidate Workbench) supports additional filters, Country and Zip/Postal Code as part of the Filter Options.

This allows our customers to filter list of candidates based on which country and zip/postal code they live in. It also helps our customers when positions requires candidates that live near to the work location.

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

SAP SuccessFactos Recruiting Management

1. Log in to SuccessFactors -> Recruiting
2. Access a Job Requisition -> Candidates
3. Open the Filter Options

4. When "Filter Options" is displayed, only "Country" is visible. Once a country is selected, then zip/postal codes can be added.

From where is the zip code/postal code derived? How is the application snapshot created?

In general, an application snapshot is created and displayed in the candidate workbench when the user clicks on the applicant for the first time. This snapshot takes the fields specified in the candidate profile during the first click. The filter in always on the data which is displayed in the candidate workbench. Therefore, for all candidates who have applied to the requisition the filter is applied on the application snapshot if it exists, or else it is applied on the data specified during application.

In case of Forwarded candidates, the filter is applied on the Country and Zip Code which provided in the candidate profile.

Note: This filter is only available when country field is configured in candidate profile template.

FAQ and Scenarios

1. Zip Field Configured in Candidate Profile and Application:

• External Candidate (or internal candidate if no sm-mapping to Employee Profile exists) – The entered Zip in application page overrides the field specified in candidate profile, and also updates the candidate profile with this zip code from application page.
• Now going to candidate workbench before clicking on the candidate will display the Zip given in application page.
• After clicking on the Candidate for the first time a snapshot is created which updates the Zip with the latest value from candidate profile. Any further changes to the profile after the first click doesn’t update the snapshot.

Below example for <name> Postal Code displayed is from application page.

Before clicking on the candidate for the first time we can also view and filter on the Zip specified in the application page.

Now clicking on the candidate once it creates an application snapshot with the latest Zip value from candidate profile (Changed from APP999 to 55667).

• Forwarded Candidates – The zip displayed is always from the candidate profile. On inviting the candidate to apply the zip value is taken from application page and creates snapshot with zip from candidate profile like above.

2. Zip field configured in Application but not in Candidate Profile:

The value entered in the Application page is stored in the RCM_APPLICATION and RCM_CANDIDATE table, but it is not viewable anywhere in the UI.

3. Zip field configured in Candidate Profile but not in Application:

The value is always taken from Candidate Profile and snapshot is created like in scenario 1.

Examples

1. Candidate is External or Internal Without sm-mapping:

A candidate maintains the candidate profile with zip code/postal code 123.

Then the candidate applies to a requisition and during the apply process 123 gets changed to 456. When user completes the apply process, then 456 is transferred also to the candidate profile.

Let’s assume the candidate will then open the candidate profile and update it to 789.

Scenario 1: In the Applicant List page (Candidate Workbench) the application of the candidate shows up, the user looking at that page has not clicked on the candidate yet -> Zip code is derived from the application -> 456

If the filter is looking for 456 then this candidate will show up. If the filter is looking for 789 then this candidate will not show up.

Scenario 2: As soon as the user clicks on the candidate, the application snapshot gets created -> Zip code is derived from Candidate Profile and is the basis for the application snapshot -> 789

If the filter is looking for 456 then this candidate will not show up. If the filter is looking for 789 then this candidate will show up.

filters; Filter; Display Option; Candidate Workbench; Candidate Summary Page; Search; ZIP; , KBA , LOD-SF-RCM , Recruiting Management , Product Enhancement