SCT Banner Student / Release Guide / 7.0

Section 13 Problem ResolutionsRegistration ModuleSFKFEES (#88382)If SFARGFE rules used different detail codes when in a per credit to flat chargingscenario and refunding was using refund by total processing, fee assessmentcalculated an incorrect refund and penalty charge. Refund by total processing hasbeen rewritten to accommodate the use of different detail codes and to assesspenalties correctly whether clearing detail codes are placed in SFARFND or if thedetail codes are left blank. Resolved in Release 6.1.SFKFEES (#87903)When using refunding by total, fee assessment was creating an incorrect penaltycharge if a detail code was removed from a section after the student had registeredand been assessed for that charge and then was re-assessed using SFAREGS (afterthe removal of the section fee detail code from the CRN). This has been correctedso the removal of a detail code for section fees will create a simple reversal (nopenalty charge is posted) after re-assessment occurs in a refund by total term.Resolved in Release 6.1.SFKEDIT1 andSFKFUN1SFKFUN1 andSFKFUNCSFKFUN1 andSFKFUNC(#90995)You cannot register for connected courses such as links and co-requisites if one partof the connection must be waitlisted. The same is also true for concurrent prerequisites.Resolved in Release 6.2.(#85027)A student was allowed to register for both a course and its equivalent within the sameterm. This has been prevented, and a Duplicate Course error will be returned if thisaction is attempted. Resolved in Release 6.1.(#89739)The “DUPL EQUIV” error on SFAREGS will now show the correct CRN in the errormessage. The procedure P_CHECK_DUPL_SFTREGS and the function F_DUPL_EQUIVwere modified. Resolved in Release 6.2.SFKFUN1 (#93409)Registration via the Web no longer permits you to register for a course and aduplicate equivalent course. An error message will now be displayed in thiscircumstance. Resolved in Release 6.2.SFKFUN1 (#85041 and #76841)Duplicate courses that are linked are now recognized as duplicates and do not allowregistration. Resolved in Release 6.1.SFKFUN1 (#87601)In sfkfun1.sql, function f_registration_access, the cursor is used to test forrows locked for update by another user. If locked rows are found, an exception israised as soon as the cursor is opened. Conditions have been added to the exceptionhandler, to see if cursors are open before trying to close them. Resolved in Release6.1.Student Release 7.0 January 2005362 Release Guide Confidential