Understanding PeopleSoft Search Definitions for HCM

Each PeopleSoft application provides predefined application-specific search definitions for implementation within PeopleSoft Search Framework. Tables later in these topics provide a list of the search definitions that Oracle delivers preconfigured for PeopleSoft HCM.

You can use PeopleSoft HCM global search definitions and search page (component) definitions as delivered, copy and modify them, or create new ones.

Note: For easier maintenance, Oracle recommends that you preserve the preconfigured application-specific search definitions as default definitions. To modify a delivered search definition, manually copy it and then modify the copy.

For information about the building blocks or objects that are associated with a search definition (query types, delete query, security type, attributes, facets, search category, and so on), and to learn how to create and implement search definitions using PeopleSoft Search Framework, refer to the PeopleTools: Search Technology product documentation.

To view any of the preconfigured HCM search definitions that are listed in this topic, access the Search Definition component from the Search Designer Activity guide, or from the menu navigation (PeopleTools > Search Framework > Designer > Search Definition).

When implementing PeopleSoft Search Framework for HCM, keep these general considerations in mind.

PeopleSoft HCM searches:

  • Are delivered for some administrative components (Keyword Search Page searches). Some of these searches are also enabled for Global Search.

  • Consider only current effective-dated rows. Incremental indexing should be run daily to index changed data into the search engine system and return most recent information. Consider the rate at which your data changes to determine the frequency for incremental indexing. For example, the Time and Absence indexes may need to be incrementally indexed multiple times in a day, whereas Succession Planning might only need to be incrementally indexed once in a quarter.

  • Are based solely on the fields and values that are indexed.

  • Rely on the last updated date time stamp field for incremental search indexing. (If a date time stamp field is not present in the underlying tables of a search definition, then changes to that table will not be tracked by the search engine. Date and numeric fields cannot be added as facets.)

  • Allow non case-sensitive free text search.

  • Accept a list of special characters in keyword search. Refer to the Working with Search Operators in PeopleSoft Search topic in PeopleTools: Search Technology for more information.

In addition to these general considerations, each PeopleSoft HCM search definition may have its own more specific set of considerations.

This table lists the roles and permissions that Oracle delivers for HCM-specific PeopleSoft Search definitions.

HCM Search Definition

Role

Permission List

  • Absence Request

  • Absence Balance

Search- Absence

HCCPAMSS1S

  • Additional Pay

  • Garnishments

  • General Deductions

Search-Payroll for NA

HCCPPY1001

Applicants

  • Recruiter

  • Recruiting Manager

  • Recruitment Administrator

HCCPRS1321

Career Plan

Search- Career Plan

HCCPSS3101

  • Compensation History

  • Total Rewards

Search- Compensation

HCCPSS2131

ePerformance

Search- Performance

HCCPEP2500

Job data

Search-Job

HCCPHR3311

Job Postings

  • Recruiter

  • Recruiting Manager

  • Recruitment Administrator

  • Hiring Manager

  • Applicant

HCCPRS1320

Company Directory

Search- Company Directory

HCCPSS3100

Positive Input

GP Search Administrator

HCCPGPSEARCH

Succession Plan

Search- Succession Plan

HCCPSS3102

Time

Search- Time

HCCPSS2132

Company Directory

Search- Company Directory

HCCPHR3310

Person

Search-Person

HCCPHR3312

Users can perform related actions on manager and employee self-service transactions that are returned from global searches. The list of related actions vary based on the transaction to which they are associated; PeopleSoft security determines the actions a user can take on any given transaction.

While the Applicant and Job Posting transactions have their own set of Recruiting Solutions-specific related actions, the rest of the transactions present their related actions from the same list.

See Understanding Global Search for Recruiting

Oracle delivers related actions from many of the Global Searches. For all the searches related to Employee Self Service and Manager Self Service Transactions, the related actions are the same, or a subset of the related actions from Org Chart Viewer. For Person Global Search, the related actions point to other Administrator components. Related Actions for Applicant and Job Posting searches have a different set of related actions, specific to Recruiting Solutions transactions.

The following video provides an overview of Person Global Search:

Video: Image Highlights, PeopleSoft HCM Update Image 34: Person Global Search