Search/Match enables you to define search parameters that administrative users can use to determine whether a potential duplicate ID exists in the database.
The difference between record search (from search box dialog pages) and using the Search/Match process is this: You use search box pages to retrieve existing records using limited search criteria to view or update data. You use the Search/Match process to use a larger set of search criteria that detect duplicate or multiple records in your database or to identify different records that contain duplicate data that should uniquely identify only one ID.
Maintaining the integrity of IDs and their associated data is important for maximizing system features and functionality. The Search/Match process helps you to prevent the entry of duplicate or multiple records by determining whether a person (emplid) or an applicant (HRS_PERSON_ID, if you license PeopleSoft Enterprise HRMS Talent Acquisition Manager) already exists in your database before creating (or recreating) the record.
You use the Search/Match process to define rules and search parameters that determine if duplicate or multiple records exist with the uniquely identifying data relevant to your business processes. You can configure which results fields to display with the returned matching IDs. You can also choose to fully display, mask, or partially mask result field values based on business processes and the level of security that your users need.
You can reinforce the evaluation of possible duplicates by setting up the Search/Match process to run automatically at save time when a user creates a new ID.
Consider this scenario: A student wants to attend your institution. She visited your campus to sign up for classes today. She thinks her record already exists in your database because she previously contacted your institution. Before creating a new record, you want to use the Search/Match process to determine if her record already exists in the database.
Table of Contents