Section 4 Problem ResolutionsRegistration ModuleSFQSECMSFQSECMSFQSECT(#CMS-DFCT91958)Description: If a student was registered for seven or more courses, and SFQSECMwas called from SFAREGS, the scroll bar in the <strong>Student</strong> Schedule block was notenabled.Impact: Users had to use Next Record and/or the Down Arrow key.Resolution: Code in the SFVSECM block has been modified to correct this.(#1-H3EBO)Description: When SFQSECM was called from a form (such as SFASRPO), the<strong>Student</strong> Schedule block did not display correctly or present complete information.Impact: Incomplete information displays on SFQSECM when it is called from formsother than SFAREGS.Resolution: Code in the SFVSTUM block has been modified to correct this.(#1-5K9P2)Description: When you accessed the form from SFAREGS for a CRN, the EnterQuery and Execute Query function keys did not work. They should not be displayedas options in Show Keys.Impact: SFQSECT meeting times processing does not allow query functions to beperformed, but Show Keys leads the user to believe these options are available whichcauses confusion.Resolution: Triggers have been created in the SSRMEET block with theG$_INVALID_FUNCTION_MSG. None of these functions should be available to users:KEY-CLRBLK, KEY-CQUERY, KEY-EDIT, KEY-ENTQRY, or KEY-EXEQRY.PackagesSFKFEE1(#1-16L6YC)Description: When refund by course was used with a flat rule, if a student’s originalregistration record was entered prior to <strong>Banner</strong> <strong>Student</strong> 7.1, and any activity wasperformed on a CRN (such as, dropping the course, grading the course), and thenthe student was reassessed, the courses that were changed were treated as new adds,and incorrect assessment occurred.Impact: Assessment was incorrectly performed, and students could be moved intothe overload hours rule because of it.Resolution: This has been corrected. If the assessment activity date is not presentduring the selection of registered CRNs for a particular student, the add date willthen be used, not the registration activity date.<strong>Student</strong> <strong>Release</strong> <strong>7.3.2</strong> February 2007112 <strong>Release</strong> <strong>Guide</strong> Confidential
Section 4 Problem ResolutionsRegistration ModuleSFKFEE1SFKFEE1SFKFEES,SFKFEE1(#1-OOYRP)Description: When refund by course and flat charge processing were used with thecampus rule type on SFARGFE, the following occurred. When a student was assessedat least two campus rules and then was dropped from a flat charge rules into a percredit rule for one of the campuses, the liable hour calculation for the drop wasinflated.Impact: Incorrect liable hours may be calculated, causing an incorrect assessment,when multiple campus rules are met and a flat assessment occurs.Resolution: This has been corrected. The starting liable billing hours are retrievedfrom the last SFRFAUD record.(#1-O6SU1)Description: When refunding by course was used and swapping was turned off, if astudent dropped multiple courses with different part-of-term refund periods, thecorrect liable hours were calculated. However, when swapping was turned on,incorrect results were received for non-swapping liable hours, and the droppedcourses should not have been considered for swapping.Impact: Simultaneous drops for different parts-of-term were causing incorrectrefunding results under certain processing situations.Resolution: This issue was resolved with other changes, and this scenario does notexist in version 7.3.1 of sfkfee1.sql.(#CMS-DFCT104667)Description: When refund by total processing was used, with or without swapping,the following occurred. When a student re-registered for a course that hadpreviously been dropped and had generated a penalty on SFARFND, the penalty wasnot reversed. Also, if a drop/delete (DD) was performed first and fees were assessed,the penalty was not reversed. (Refunding by course did reverse the charge for thedropped liable hours when the student was re-registered for the dropped course.)Impact: Refund by total swapping was not reversing penalties in all cases. Additionalfunctionally has been added to account for the reversal of penalties when nowithdrawn courses that count in assessment exist on a student’s account. Therefore,if none of a student’s courses that count in assessment have a withdrawal status, allrefund by total penalties will be reversed, regardless of the setting of the AllowSwapping (Indicator) on SOATERM.Resolution: The following changes have been made.1. Cursors for f_get_dcat_total, f_count_detl_for_dcat,p_calc_rbt_refunds, p_reverse_na_charges, andp_post_rbt_penalties will exclude penalty codes of P and S.2. A new f_RE_like() function has been added. This function determineswhether or not the course status registration codes that are counted inassessment are used for withdrawals. If they are not used for withdrawals, thenall refund by total penalties will be reversed. If they are reversed, then any 0 - 9penalties will need to be refunded.February 2007 <strong>Student</strong> <strong>Release</strong> <strong>7.3.2</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 113