SCT Banner Student / Release Guide / 7.0

Section 5 Common Matching - FunctionalForms Used with Matching ProcessRule 1 Rule 2Last Name = RFirst Name = RSSN = YDate of Birth = YCity = YLast Name = RFirst Name = RDate of Birth = YCity = YZIP Code = YZIP Code = YThe value R stands for Required. The value Y stands for Exists.Banner values: Tomasso Dalimonte, SSN = null, Date of Birth = 06/02/78, City =Marikesh, ZIP = 11233External values: Tomasso Dalimonte, SSN = null, Date of Birth = 09/07/59, City =Woodstock, ZIP = 06281The external record will pass the primary match, because the first and last namesmatch. Normally, this would mean that the record would be suspended at aminimum. However, because the Date of Birth, City, and ZIP Code fields specificallydo not match (i.e., none of them are null), then the record's match status is set toNew. This is the only exception to the basic matching algorithm.Forms Used with Matching ProcessCommon Matching Entry Form (GOAMTCH)If Common Matching is turned on (on GUAINST), and the user is not excludedfrom Common Matching on GORCMUS, GOAMTCH is called from the Key Blockof SPAIDEN, SRAQUIK, SAAQUIK when an ID is generated or entered, and the IDdoes not already exist in Banner. Whether or not Common Matching is turned on,the user will be able to access GOAMTCH from SRIPREL, SAAEAPS, and SHAEDISas part of the matching process for data loads.You can enter information for name, address, telephone, date of birth, SSN, etc., inthe Data Entry block. The data entered can be used to assist with matching if thematching rule contains the field being entered. Regardless, the data entered in theData Entry block will be stored in Banner if the person is found to be new.Student Release 7.0 January 2005156 Release Guide Confidential