SCT Banner Student / Release Guide / 7.0

Section 13 Problem ResolutionsAdmissions ModuleSAAADMS (#76909)When the GUBINST_FINAID_INSTALLED field was not checked on GUAINST, andthe GUBINST_FINAID_IND field was also not checked on GUAINST, some BannerStudent processes still created records in the SORFADR table. Under theseconditions:• If an ID was created and an SPAPERS record was created, SORFADR wasupdated with a record for that PIDM.• If an ID was created and an SAAADMS record was created, SORFADR wasupdated with a record for that PIDM.• If an ID was created, and an SHADEGR record was created, SORFADR wasupdated with a record for that PIDM.When the GUBINST_FINAID_IND field is set to N, no SORFADR row should becreated.The following objects have been modified to correct this:• saaadms.fmb• saadcrv.fmb• saaquik.fmb• sgastdn.fmb• shadegr.fmb• shatrns.fmb• siafdeg.fmb• smarqcm.fmb• soapcol.fmb• spaiden.fmb• spapers.fmb• sfrrnop.pc• shkcgpa.sqlResolved in Release 6.1.SAADCBT (#98027)The 7.0 user interface project allows the form canvas to display all fields without ahorizontal scrolling bar. The ratings information has been moved to a separatewindow that is accessed by a tab. Resolved in Release 7.0.SAADCBT (#87055)When SAADCBT updated the Key Block decision code in SAADCRV, it also changedthe application status (SARADAP_APST_CODE) from an I or C to a D (Decision Made).This occurred for decision codes where the STVAPDC_SIGNF_IND field was NULL.These types of decision codes should not change the application status, as they donot change it when the code is entered directly onto SAADCRV. This has beencorrected. Resolved in Release 6.1.January 2005 Student Release 7.0Confidential Release Guide 337