How to Prevent Imported Application Records From Matching on Search Match Post When the Student Is Not Truly A Match (Doc ID 3073868.1)

Last updated on MARCH 03, 2025

Applies to:

Goal

Applications are imported using File Parser to load to the staging tables.  When the File Parser step is complete, Search/Match/Post (SMP) runs, interrogating the staging table data. In some situations SMP does not work as expected - allowing the student to match when they aren't really a match.  In one example, a Search Order setup on First Name Full, Last Name Full, DOB (Date Of Birth) and Email (17 characters) is used. Recently, an application  processed using this Search Order had a match on First Full, Last Full and DOB, but the email did not match, and an existing emplid was updated anyway.

Is the expectation correct that the email should have prevented the match, and if so, how can the correct results be obtained in this type of scenario? 

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.