SCT Banner Student / Release Guide / 7.0

Section 13 Problem ResolutionsRegistration ModuleSFRFASC (#89283)The deadlocking error situation which occurred if the report was run at the sametime that fees were being assessed using online fee assessment on SFAREGS hasbeen corrected. Resolved in Release 6.1.SFRFASC (#87516)When SFAFASC was run in batch mode with the collector table, the SFRBTCHcollector table entries were not being deleted if there was no change in a student'sassessment. This has been updated to delete collector records as they are processed.Resolved in Release 6.1.SFRFASC (#88736)Two issues were reported with the printed output from the report:1. When the Accounting Detail to Print parameter was set to A (All), the processprinted payments and other charges that were not related to the fee assessmentprocess. The report should have printed only Source = R transactions (andSource of 1-9 for SFARFND penalty charges).2. There was no Grand Total at the end of the report. This amount can beimportant to proving the associated cashier session (TGACREV) and thesubsequent feed to finance (TGRFEED).The following changes have been made:• This report has been revised and updated to print only source codes of R and1-9.• A Total has been added to the report.• The CRN for a course is now printed when charges are derived from sectionfees.• Placeholder commas have been added for clarity.Resolved in Release 6.1.Please see the Registration chapter of the Student User Guide for an updated reportsample.SFRFASC (#87896)The future effective date defined on SOATERM was not being used when SFRFASCwas run in batch mode. If the value in the Assessment Date parameter was NULL,SFRFASC was using the system date and should have been using the effective dateon SOATERM, if it date was greater than the system date. This has been corrected.Resolved in Release 6.1.January 2005 Student Release 7.0Confidential Release Guide 365