Banner Student / Release Guide / 7.3.2

Section 4 Problem ResolutionsAcademic History ModuleSHKROL1(#1-1E8XN9)Description: SHRROLL may not roll attempted hours to history correctly. Ifmultiple grade rules are established on SHAGRDE for the same grade (i.e., differentlevel with different settings for the Count in Attempted checkbox), the incorrectvalue may be rolled to the Academic History Attempted Hours field.The Count in Attempted checkbox is checked on STVRSTS. The Count inAttempted checkbox is checked on SHAGRDE. When records are rolled toAcademic History, the attempted hours should be same as the credit hours onSFRSTCR, but the values are incorrect.Impact: If more that one grade rule exists in SHAGRDE for the same grade (forexample, a B exists for the UG, GR, and CE levels), when SHRROLL populates theattempted hours, it was possible that the wrong attempted hours rule would be usedto update this value, viewed from the Grades block on SHATCKN. This would causecorrupted data in the Attempted Hours field and impact Satisfactory AcademicProgress calculations by Financial Aid.Resolution: The grade roll process may assign an incorrect value to theSHRTCKG_HOURS_ATTEMPTED field. This was due to missing joins on SHRGRDE. Thewrong SHRGRDE row may be selected when multiple SHRGRDE records exist forthe same grade code. This has been corrected. All queries of SHRGRDE have beenmodified to include joins on the level code, the status indicator, and the effectiveterm.ReportsSHRASTD(#1-1F6UA5)Description: SHRASTD did not run to completion when the Update Dean’s ListStanding parameter was Y, and the program encountered an excluded grade onSHAACST.Impact: Dean’s List data could not be updated successfully.Resolution: The close cursors have been removed from the sel_astr andsel_dl_rul routines. These had been added to minimize the number of opencursors. These two procedures use the close_cursor parameter to close the cursorsafter all work has been completed.SHRPESE(#1-12UIT9)Description: The name of the send.UseSFTP variable in the send.properties filewas misleading. It should have been named more generically, for the use of analternate protocol.Impact: The send.properties file within the shrpese.jar process needs to bechanged from send.UseSFTP to send.UseAlternate. No coding changes arenecessary. This makes it clearer to the user that any alternative protocol (besidesFTP) can be used for transporting the XML transcript.February 2007 Student Release 7.3.2Confidential Release Guide 119