Banner Student / Release Guide / 7.3.2

More documents

Recommendations

Info

Section 4 Problem ResolutionsRegistration Module3. A new p_rev_nonswap_RBT procedure has been added. This procedure is usedto determine the amount of the penalty reversal when refund by total is usedwithout swapping.SFKFUN1SFKFUN1SFKFUN1(#1-FSTR9)Description: Depending on the order in which a 0.00 credit hour course wasregistered for, it was possible that the course could receive a MAX HOURSEXCEEDED error. Since the course was for 0.00 hours, it should not have receivedthat error. The error could be overridden on SFAREGS, but not in self-service.Impact: Users may receive an incorrect maximum hours exceeded error on a zerocredit hour course that cannot be overridden in self-service.Resolution: The p_check_maxh_sftregs procedure generates a MAX HOURSEXCEEDED error on any course that is counted in enrollment, after the student'smaximum hours limit has been reached, regardless of whether the course has anyhours associated with it or not. A condition has been added to the WHERE clause inthe UPDATE statement of the p_check_maxh_sftregs procedure to check for credithours that are greater than zero.(#1-16DEXV)Description: When Duplicates was set to Fatal on SOATERM for duplicate coursechecking, and a student dropped one of the sections that was cross-listed andregistered for another section in the cross-listed group, the DUPL XLST WITH SECxxxxxx error occurred. The courses were not duplicates, just different courses in thesame cross-listed group.If the section was dropped using DD, the user could remove the CRN from SFAREGSand register for the other cross-listed course. If the section was dropped withanother code that used count in enrollment or count in assessment, the error hadto be overridden.Impact: Users were receiving duplicate cross-list errors on sections that were onlycross-listed but were not equivalent courses. Users were forced to perform anoverride when one should not have been needed.Resolution: The loop that called the f_dupl_xlst function has been commentedout.(#1-1FO1K5)Description: When you registered for open learning courses in baseline Banner,time conflicts occurred in Student Self-Service for those courses that had beenscheduled with the same meeting days and times, but with different dates.Impact: Time conflict errors were occurring on open learning courses if the startand end dates overlapped and the section meeting times overlapped, even if thesection meeting dates did not overlap. This caused the user to have to perform anunneccessary override.Resolution: The p_check_time_sftregs procedure has been modified. Thechanges made for problem resolution #1-OBHJD have been removed. Thesftregs_time_conflict_c and sftregs_time_conflict_c cursors have beenStudent Release 7.3.2 February 2007114 Release Guide Confidential
Section 4 Problem ResolutionsRegistration Modulemodified to ensure that both the learner's start and completion dates, as well asmeeting dates, can overlap without causing time conflicts.SFKFUN1,SFKEDIT1,SSKMODS,SSKMOD1(#1-1G2P54)Description: Deadlocks occurred on the SFTREGS, SSBSECT, and SSBXLST tablesduring heavy registration periods in baseline Banner Student and in Student Self-Service.Impact: Registration processing was slowed down. In SFTREGS, this could have beencaused by locks placed on the system during duplicate error checking. WithSSBSECT and SSBXLST, the deadlocks could have occurred when two students wereregistered at the same time and added different CRNs that were part of the samecross-listed group.Resolution: The following changes have been made:1. For SFKFUN1, the following line, FOR UPDATE OF sftregs_error_flag,sftregs_message, has been removed from the reg_courses_c cursor in thep_check_dupl_sftregs procedure.2. For SFKEDIT1, a call has been added to the newsskmods.p_lock_all_sects_for_pidm_term procedure.3. For SSKMODS and SSKMOD1, the new p_lock_all_sects_for_pidm_termitem has been added.SFKPRE1(#1-1DZF7X)Description: Students were registered in courses (the course was displayed onSFAREGS) that were not displayed on the Add/Drop page in self-service. This onlyoccurred when the course had an in-progress pre-requisite requirement (thestudent had registered for the pre-requisite in a prior term) that had been met (theIn Progress field was checked on SOATERM), and when a special approval code wasadded to the CRN on SSASECT after the registration had occurred.Impact: In-progress courses were not being displayed properly in self-service.Resolution: The p_prerequisitecheck procedure has been modified.1. The p_update_registration_ovr procedure will only be called ifadministrative drop checking is not being performed.This prevents the error messages from being overridden (e.g. approval error)that may have been placed in the field earlier, when an in-progress prerequisitehad been satisfied.2. The p_update_registration_msg procedure will only be called ifadministrative drop checking is not being performed or if the error that isfound is fatal.This prevents fatal error messages from being overridden (e.g. approval error)that may have been placed in the field earlier, with a warning level prerequisiteerror flag.February 2007 Student Release 7.3.2Confidential Release Guide 115
Page 3 and 4:
Release GuideStudent SystemIntroduc
Page 6 and 7:
Table of ContentsThis page intentio
Page 8 and 9:
IntroductionThis page intentionally
Page 10 and 11:
Section 1 PESC/XML Transcript Phase
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Section 1 - PESC/XML Transcript Pha
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Section 3 Miscellaneous Enhancement
Page 62 and 63:
Section 3 Miscellaneous Enhancement
Page 64 and 65: Section 3 Miscellaneous Enhancement
Page 74 and 75: Section 4 Problem ResolutionsSchedu
Page 76 and 77: Section 4 Problem ResolutionsFacult
Page 79 and 80: Section 4 Problem ResolutionsLocati
Page 81 and 82: Section 4 Problem ResolutionsLocati
Page 83 and 84: Section 4 Problem ResolutionsRecrui
Page 85 and 86: Section 4 Problem ResolutionsRecrui
Page 87 and 88: Section 4 Problem ResolutionsAdmiss
Page 107 and 108: Section 4 Problem ResolutionsGenera
Page 109 and 110: Section 4 Problem ResolutionsRegist
Page 111 and 112: Section 4 Problem ResolutionsRegist
Page 113: Section 4 Problem ResolutionsRegist
Page 117 and 118: Section 4 Problem ResolutionsAcadem
Page 119 and 120: Section 4 Problem ResolutionsAcadem
Page 121 and 122: Section 4 Problem ResolutionsCAPP M
Page 123 and 124: Section 4 Problem ResolutionsOveral
Page 129 and 130: Section 4 Problem ResolutionsValida
Page 131 and 132: Section 4 - Problem ResolutionsSamp
Page 165 and 166:
Section 4 - Problem ResolutionsSamp
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
show all

Banner Student / Release Guide / 7.3.2

Create successful ePaper yourself

Delete template?

Save as template?