Customizing of the Search Engine
You make the settings for the search engine in the Implementation Guide (IMG) for SAP E-Recruiting under
Technical Settings
→
Search Engine
.
Set Up Search Engine for E-Recruiting
SAP E-Recruiting uses the current version of
Search and Classification
(TREX) as the search engine. To be able to use the search functions for candidate data, job postings, and so on, you have to install
Search and Classification
(TREX) and the PHYTON enhancement
XML Attribute Extractor
.
You install the search engine in the configuration for a non-portal environment connected to the
Web Application Server
used. For more information about the installation and configuration, see the Master Guide for
SAP NetWeaver
™
at
service.sap.com/instguides
→
Installation & Upgrade Guides
→
SAP NetWeaver
→
Release 04
→
Installation
→
Cross-NW
→
Installation Guide Search and Classification TREX 6.1
.
Check Settings
You can check the functions of the search engine. A prerequisite for checking the functions is the corresponding data in the system, such as uploaded documents, for example. To do this, you select the document class HR_DOC.
Set Up Access to Documents
You set up the access to the
Contentserver
service of the SAP E-Recruiting system. This enables access to the documents of the document area HR_KW (Document Repository for HR Objects) within
Knowledge Provider
(KPro). The system stores attachments, search profiles, and so on in this document storage.
Activate Indexing
You activate the document area HR_KW (Document Repository for HR Objects) for indexing the documents stored there. The indexing is necessary for the search engine to be able to search in search profiles and attachments.
You make the settings for the search profile in the Implementation Guide (IMG) for SAP E-Recruiting under
Succession Planning
→
Talent Warehouse
→
Candidate
→
Candidate Search
→
Search Profile
.
You define the
search profile types
that you want to use for the search for job postings and candidates. You also specify for each search profile type the class with which the system is to create the search profile and the object type to which the search profile is to be assigned.
You define the information categories to make certain information of an object type available for the search. You determine what this information can be by assigning a DDIC structure to the relevant information category. At the same time, you assign an information category a
content extraction class
that is used to determine the relevant information when creating the search profile.
You determine for each search profile type the languages in which the created search profile for the relevant search profile type can exist.
You determine which fields from the information categories are contained in the search profiles of the relevant search profile type and enter the field type of the data (free text, entity, both). The search engine requires this information so as to know how you can search in the associated field.
For information categories that contain qualifications, qualifications with proficiencies, and questionnaires, all existing qualifications, qualifications with proficiencies, or questionnaires are contained automatically in the search profile type; therefore, you do not need to enter these fields explicitly.
The search uses a search template of the type
Full Text
to find automatically the selection criteria specified in a free text search. The FULLTEXT_SEARCH information category should therefore not be assigned to a search profile type.
You determine which attachment types are to be included in the full text search in attachments. You have already determined the possible attachment types in the Implementation Guide for SAP E-Recruiting.
After you have changed the assignment of fields of an information category to a search profile type, you update the search profiles that were created on the basis of a search profile type. In this way, the changes are transferred into existing search profiles and then taken into account by the search application.
You make the settings for the search templates in the Implementation Guide (IMG) for SAP E-Recruiting under
Succession Planning
→
Talent Warehouse
→
Candidate
→
Candidate Search
→
Search Templates
.
You define the search templates that are to be displayed on the user interface in the various search applications. You specify for each search template the search profile type on which this is to be based. You also determine the layout on the user interface and the properties for each search template by assigning a search template type to each one. Search templates of the following search template types have the properties described below:
The search template contains search template elements. These must be assigned to the search template.
The search template enables a full text search of all user-defined fields that are contained in the corresponding search profile type. Depending on the entries in Customizing, a full text search is also performed on the assigned attachment types.
The search template contains a search template element of the type
Qualification
that refers to an information category with qualifications.
The search template of the type
Qualification with Proficiencies
contains a search template element that refers to an information category with qualifications and their proficiencies.
The search template of the type
Questionnaire
contains a search template element that refers to an information category with questionnaires.
The search template of the type
Performance Management
contains a search template element that refers to appraisal elements of a template on which appraisal documents in Performance Management are based. The columns of the elements of the template are provided in a dropdown list box. For each column, you can enter a value and a mathematical operator.
Note
Use of this search template type is advisable only for searches in the integrated system.
The search template of the type
Job Family Potential
contains a search template element that refers to job families and their levels.
Note
Use of this search template type is advisable only for searches within Succession Planning in the integrated system.
You define the criteria of a search, the search template elements. You assign each search template element a key and enter the following information:
You specify how the input field of the search template is to look on the user interface.
You specify whether there is to be a value help for the search template element.
You assign the field of an information category to the search template element.
You specify the type of the field (free text, entity, both).
If you have determined that a value help is to be created for the search template element, you also specify an access class for the data retrieval (the access class must contain the GET_VALUEHELP_TAB method).
If the access class delivers values from several fields, you specify from which field the value help is to be created.
You determine which search template elements belong to a search template and in which order.
You define the search template groups by grouping together search templates that are displayed together on the user interface of a search application.
You assign the search templates that are to be included to the search template groups and determine the sequence. The search templates of a search template group must be assigned to the same object type.
You make the settings for the search applications in the Implementation Guide (IMG) for SAP E-Recruiting under
Succession Planning
→
Talent Warehouse
→
Candidate
→
Candidate Search
→
Search Templates
.
You assign a search template group to a search scenario or search application. You make a distinction here between applications that are realized in BSP technology and applications that are realized in Web Dynpro ABAP. The controller class that displays the relevant hit list must also be assigned to the search applications in BSP technology. The controller class uses the identifier of the hit list for the entry.
You set up the attributes of the search applications. In this way, you can determine for each search application which interface elements it contains and which options for creating search queries are available.
You can make the following settings:
You specify that the results of the automatic ranking are displayed with the relevant match percentage in the hit list if at least one search attribute was selected for the search.
You can provide the user with the option of calling additional documentation for the search application using a link on the user interface.
You can provide the user with the option of saving search variants for later use.
You specify that the settings for the maximum number of hits in the hit list for the search are displayed.
You determine how many hits are displayed in the hit list. If you do not enter a value, then there are no entries in the hit list.
You specify that the settings for the ranking threshold are displayed on the user interface.
You specify by how much percent a hit must agree with the weighted search criteria for it to be displayed in the hit list.
You use this BAdI HRRCF_SEARCH_RANKING to specify how the system groups together the hits from different searches and assigns a weighting to them.
The BAdI provides the following methods for an implementation:
Method |
Name |
---|---|
COMPUTE_RANKING |
Group Together Hits from Two Searches |
COMPUTE_RANKING_NON_TREX_HITS |
Calculate Weighting of Hits from Non-TREX Search |
SAP delivers the standard implementation HRRCF00_SEARCH_RANKING as active. The following system behavior is stored in the methods of this implementation:
COMPUTE_RANKING
The system uses this method to group together the hits of the hit lists of two different searches into one hit list.
In the standard implementation, this occurs depending on the operator used (and/or) between the search attributes. The system behavior with regard to the relationships between the search attributes results from the settings that are stored for the ranking in the IMG activity
Set Up Search Applications
.For more information, see the documentation for the IMG activity in the
Ranking
section.
The system also takes into account the weighting of the hits.
COMPUTE_RANKING_NON_TREX_HITS
You use this method to calculate a weighting for hits that were determined using a database search. In addition to the search using
Search and Classification
(TREX), it is also possible to search using function modules. However, hits found in this way do not have a weighting. Consequently, these hits would have a weighting of 0% when combined with the hit list from the TREX search.
In the standard implementation HRRCF00_SEARCH_RANKING, the method calculates a weighting for these hits according to the following equation: Weighting of hit = 100% divided by the number of selected search criteria.
You determine which fields from the candidate profile are compared with fields in the succession plan to enable an automatic comparison (match) of the succession plan criteria with the candidate profile criteria for searches and automatic rankings in the context of a succession plan. See also Ranking of Candidates According to Succession Plan Criteria .
SAP delivers a table with default settings for the comparison. These entries are overridden by entries that are stored using this IMG activity.