Hierarchy
ERECRUIT (Software Component) E-Recruiting⤷
PA-ER (Application Component) E-Recruiting⤷
PAOC_RCF_BL (Package) Recruitment Factory: Business Logic
IMG Activity
| ID | RCF_UI_SMG_NAVI | Assign Search Template Groups to Search Applications |
| Transaction Code | S_KER_43000110 | (empty) |
| Created on | 20020829 | |
| Customizing Attributes | RCF_UI_SMG_NAVI | Assign Search Template Groups to Search Applications |
| Customizing Activity | RCF_UI_SMG_NAVI | Assign Search Template Groups to Search Applications |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | RCF_UI_SMG_NAVI |
Use
In this IMG activity, you specify which search template groups are used in the different scenarios.
For scenarios realized in BSP technology, you specify which Business Server Page application (BSP application) calls and displays the search results. For scenarios realized in Web Dynpro ABAP, you do not need to enter this information.
In the following cases, you use the IMG activity to make settings:
- If, for example, you have copied a standard application to the customer namespace, you insert new entries in this table.
- If you want to use a search template group you have created yourself, you change the relevant entry.
Requirements
Standard settings
The Search Template Groups and Hit Lists of a Search Application table is a system table with a specific namespace for customer entries.
The customer namespace is: Component identification of the calling controller Z*.
Standard settings are delivered for the relevant search applications (search template groups) for the following scenarios that are realized in BSP technology:
CompID of Calling Controller Scenario (Search Template Group)
EESearchPosting Search for Internal Job Postings for Unregistered Internal Candidates
UnregSearchPosting Search for External Job Postings for Unregistered Candidates
cdcycandsearch (Recruitment) Search for Candidates in the context of a requisition or an application group for recruiters
cdcycandsearchscp (Succession Planning) Search for Candidates in the context of a succession plan for succession planners
cdcyreqsearchexternalpostings Search for Requisitions in the context of an external candidacy for recruiters (with external postings or with and without external postings (you can alternate between the two scenarios))
cdcyreqsearchinternalpostings Search for Requisitions in the context of an internal candidacy for recruiters (with internal postings or with and without internal postings (you can alternate between the two scenarios))
cdcysch (Recruitment) Search for / Comparison of Candidacies for Recruiters
cdcyschscp (Succession Planning) Search for / Comparison of Candidacies for Succession Planners
EmpSearchPosting Search for Internal Job Postings for Registered Internal Candidates
RegSearchPosting Search for External Job Postings for Registered External Candidates
tgcandsrch (Recruitment) Search for Candidates in the context of a talent group for recruiters
tgcandsrchscp (Succession Planning) Search for Candidates in the context of a talent group for succession planners
trmcandsrch (Recruitment) Search for Candidates in Talent Warehouse for Recruiters
trmcandsrchscp (Succession Planning) Search for Candidates in Talent Warehouse for Succession Planners
Note
For the Search for Candidates in the context of a requisition or an application group scenario and the Search for Candidates in the context of a succession plan scenario (cdcycandsearch, cdcycandsearchscp), it is possible to display two differently formatted hit lists. You make these settings in the Controller Class of Lower-Level Controller column.
HITLIST_CAND.DO: The hit list only displays how many candidates of the search results are assigned to the requisition; however, it does not state who these candidates are.
HITLIST_CAND2.DO: The hit list contains two lists. In the first list are the names of the persons who are already assigned to the requisition. In the other list are the names of the persons who are not assigned to the requisition. As this hit list has to read additional data for the candidates who are already assigned, this hit list is more performance-intensive than the simple hit list.
Note
If you want to insert customer-specific applications in this table, take a look at the interplay of the individual controllers in the application HRRCF_UNRG_SRCH. The BSP application is used in the scenario for the freely accessible search for job postings. First familiarize yourself with the Model View Controller (MVC) implementation model for BSP applications.
Standard settings were delivered for the relevant search applications (search template groups) for the following scenarios that are realized in Web Dynpro ABAP:
CompID of Calling Controller Scenario (Search Template Group)
EMPLOYEE2POSTING Search for Internal Job Postings for Registered Internal Candidates
REGISTERED2POSTING Search for External Job Postings for Registered External Candidates
UNREGEMPLOYEE2POSTING Search for Internal Job Postings for Unregistered Internal Candidates
UNREGISTERED2POSTING Search for External Job Postings for Unregistered Candidates
Activities
Example
Business Attributes
| ASAP Roadmap ID | 203 | Establish Master Data |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 1 | Critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | RCF_UI_SMG_NAVI | 0 | ALN0000022 O KER0000011 |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V77RCF_SMG_NAVI | V - View | SM30 |
History
| Last changed by/on | SAP | 20050506 |
| SAP Release Created in | 10A |
