Search Results

After the external system search process completes its search for potential matches, the result data is sent to CS via the response message (Match Response). When you perform a search that triggers both the Internal Search/Match and External Search/Match processes, the system may not find results on the same search order number. The rule for External Search/Match functionality is to display all search results, beginning with the lowest search order number obtained (the most restrictive search rule where matching EmplIDs are found). The search order is determined by the Results Engine.

Before it can display your search results, the Results Engine receives the results from both the Internal Search/Match and External Search/Match processes. The engine evaluates the search order number from each system's matching candidates.

• If Internal Search/Match found matching candidates with a lower search order number than the external system, then the Results Engine displays the results from Internal Search/Match; the lowest search order indicates that it was a more restrictive search.

• If the opposite is true, then the Results Engine displays the results found from the external search.

• If both searches retrieve results on the same search order number, the Results Engine combines the search results into a single display for the user.

Regardless of whether you invoke Internal Search/Match, External Search/Match, or both, the search results appear on the Integrated Search Results page. This page contains many of the same fields as the Search Results page. In addition, the Results tab contains optional columns such as the external system ID (referred to as the Universal ID), the EmplID (when it exists) and the Score% (or the weight) of each matching candidate found if the external system provides that information. The Results tab uses the same masking configuration that is in place for Search/Match.

When External Search/Match finds a matching candidate that does not exist inside the internal system (the matching candidate is not tied to an EmplID), you can still use the Detail link to view more information about the constituent. This case triggers an outbound web service request for more information (Fetch Request). The external system receives the information and returns detailed constituent information inside its response web service (Fetch Response). The system then displays (but does not store) the detailed information inside a Detail page that enables you to review the data.

If you determine that the matching candidate is the person you are looking for, you can import the person record from the Integrated Search Results page. When you click the Import button, the system generates a Fetch Request (the same web service used to retrieve more details about the constituent) and uses the information contained in the Fetch Response to create the new person record inside the CS database. After you generate the person's EmplID, you can then use it to perform subsequent transactions.

See Campus Solutions Application Fundamentals: Understanding CS-to-HCM Integration

See Campus Solutions Application Fundamentals: Integrating Person Data

See the following documents in My Oracle Support:

• PeopleSoft Campus Solutions Constituent Web Services Developer's Guide (ID 1982192.1).

• Information Center: CS-HCM Integration for PeopleSoft Enterprise Campus Solutions on My Oracle Support (ID 2091799.2).