SCT Banner Student / Release Guide / 7.0

Section 13 Problem ResolutionsRegistration ModuleSFAREGS (#93575)The Options Menu was not displaying the associated form names for the options ifthe user preference on GUAUPRF was set to display the Menu Bar Options. Thiswas corrected by updating the appropriate Form Called information for theSFAREGS records that are displayed in the Options Maintenance Form(GUAOPTM). Resolved in Release 6.2.SFAREGS (#89995)SFRFASC was calculating the fees correctly, but when a registration was backdated,the current date was being used in the accounting. When a registration wasbackdated, SFAREGS used the current date, instead of picking up the backdate.This affected backdated refunds, especially if backdating was done in a refund bytotal period. This has been corrected. Resolved in Release 6.1.SFARGFE (#95879)When you entered rule and entity types, selected the Copy Rules to New Termbutton, and then manually entered the program code in the Registration Chargesand Fees block, you received a form error. This has been corrected. Resolved inRelease 7.0.SFARCTL (#93479)The Duplicate Record function was causing difficulties when a Rollback was used,after an ORACLE INSERT error had occurred, and changes could not be saved.This can be prevented by clicking in the Key Block, changing the term code value,and saving the records for the new term. The Key Block term code has been disabledwhen there are errors pending in the main block. Resolved in Release 6.2.SFAREGS (#84990)If the SFRSTCR_RSTS_DATE was not within the date range for the course registrationstatus code in SFARSTS, an error message was displayed: “*ERROR* STATUSFunction cannot be performed at this time. Press CLEAR BLOCK" for every previouslyexisting course where the course registration status code was no longer valid.A trigger has been adjusted to allow one error status message to be displayed whenthe SFRSTCR_RSTS_DATE is no longer valid. Resolved in Release 6.1.SFAREGS (#84524)The error that occurred when data was “Extracted With Key” has been corrected.Resolved in Release 6.1.SFAREGS (#87856)If audit records were not created as part of the Release 5.6 migration, and a changein student data occurred without a change in registration data and then anassessment was performed, the audit records used to capture the snapshot of the lastassessment were not created due to the registration data not being changed. Thisprevented the needed reversals based on the change in student data from occurring.A function has been added to create the audit record (if none exists) when NextBlock is used from the Key Block of SFAREGS. Resolved in Release 6.1.January 2005 Student Release 7.0Confidential Release Guide 349