SCT Banner Student / Release Guide / 7.0

Section 13 Problem ResolutionsAdmissions ModuleReportsSAPAMAL (#79354)The process no longer performs intermittent commits while in Audit Mode.Resolved in Release 6.1.SAR189U (#94402)The process will no longer produce an Oracle error if the SST01 segment is presentby itself, without any SSE lines or other optional segments. Resolved in Release 6.2.SARBDSN (#88936)When you enter % for all terms in the Applicant Entry Term parameter and entera decision code in the Application Decision Code parameter, the process will nowlist all applicable IDs. Resolved in Release 6.1.SARBDSN (#78535)This problem resolution has three parts.1. If a record on SAAADMS had the following primary curriculum values: Major1/Department 1, Concentration 1, 2, 3; Major 2/Department 2, Concentration1, 2, 3; Minor 1 and Minor 2; when SARBDSN created the SGASTDN record,only the following values were created in the primary curriculum: Major 1/Department 1 and Concentration 1.2. When SARBDSN created the SGASTDN record, the Catalog Term value wasnot carried over from SAAADMS.3. When SARBDSN created the SGASTDN record, the Create/Update AcademicHistory Degree Record field was not checked (set to Y) in the PrimaryCurriculum window, although the SOACURR rules for that program codeindicate that it should have been.These issues have been corrected. Resolved in Release 6.1.SAREBTL (#62924)Overlapping and misalignment of data on the output that occurred when the SSNwas missing has been corrected. Resolved in Release 7.0.SARRATE (#88175)The process is now using effective term functionality when evaluating the factorcodes associated with a formula. Resolved in Release 6.1.SARRATE (#84991)You will no longer encounter an error when more than two pages of data aregenerated. Resolved in Release 6.1.January 2005 Student Release 7.0Confidential Release Guide 343