Search Match is Creating Duplicate Applications with the Admissions Application Transaction Management Load
(Doc ID 1603044.1)
Last updated on MAY 08, 2023
Applies to:
PeopleSoft Enterprise CS Campus Community - Version 9 to 9.2 [Release 9]Information in this document applies to any platform.
Goal
Why is search match not working correctly for admission application transactions?
Search match set up contains the national id as one of the search/match rules. When running the Application transaction management process, a staged record with exactly the same social security number is not identified as a match and a new id is created for the applicant. In this case the other search/match rules do not identify the person as a duplicate because the name fields contain an apostrophe or an embedded space which causes the other levels of the search/match to not be met.
As a result, duplicate records are created and need to be cleaned up.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |