oiit summary notes for banner baseline 7 - university …€¦ · · 2010-02-17oiit’s summary...

OIIT’s Summary Notes for

Banner Baseline 7.x Patches

Office of Information and Instructional Technology

October 19, 2007

This page left blank to facilitate front/back printing.

Banner Baseline 7.x Office of Information and Patch Release Summary Instructional Technology

Table of Contents Patch Release for Banner Baseline 7.x ....................................................................... 1

Purpose ..................................................................................................................... 1 Modules in this Release............................................................................................. 1

Information in the Patch and Defect Correction Table............................................... 1 SGHE Release Date .................................................................................................. 1 System....................................................................................................................... 1 Version Number ......................................................................................................... 1 Patch Number ............................................................................................................ 1 Module/Form/Process................................................................................................ 1 Release Dependencies.............................................................................................. 1 Patch Title and Defects Corrected ............................................................................. 1

Technical Instructions for Applying Patches ............................................................. 2 SGHE Text Files ........................................................................................................ 2 Order of Application ................................................................................................... 2 Best Practice.............................................................................................................. 2

Testing and Certification of Patches ........................................................................... 2 Testing and Certification ............................................................................................ 2

Location of Patches and Related Documentation...................................................... 3 Location on ftp.usg.edu.............................................................................................. 3 Example..................................................................................................................... 3 Patches in this Release ............................................................................................. 3

Banner 7.x Patch and Defect Correction Information for October 19, 2007............. 4

Banner Baseline 7.x Patch Information Page iii October 19, 2007


This page left blank to facilitate front/back printing.

Banner Baseline 7.x Patch Information Page iv October 19, 2007


Patch Release for Banner Baseline 7.x

Purpose This document provides technical and functional users with summary information in table format about the patches included in this release. Complete text files received from SunGard Higher Education Solutions (SGHE) describing Banner baseline defect corrections are not reproduced here but have been placed on ftp.usg.edu with the patches. Refer to those text files for additional information.

Modules in this Release

SGHE has released patches for the following baseline product: • Accounts Receivable 7.4 • Financial Aid 7.9 • Self-Service Faculty and Advisors 7.4 • Self-Service Student 7.4 • Student 7.4

Information in the Patch and Defect Correction Table The Patch and Defect Correction Table includes the following information:

SGHE Release Date Date that SGHE last released the defect correction (the date the release notice appeared on BPOST). Patches are listed in this document in order by this date. Note: The release date and the date that appears in the text file may not match, particularly if the patch was re-released.

System SGHE Banner baseline system affected by defect correction.

Version Number Version number of the form or process following application of patch/defect correction.

Patch Number SGHE patch numbers and defect numbers do not always match. Patches may include corrections for multiple defects. The SGHE patch number is provided, but information about multiple defects corrected by the patch is provided in the functional impact column.

Module/Form/Process Module, form, or process affected by defect correction.

Release Dependencies

Required systems and versions on which the patch depends.

Patch Title and Defects Corrected

Patch title and defects corrected by the patch are listed here. If included in the posting, cursory descriptions of defects are also included. More complete information from SGHE is provided in text files located on ftp.usg.edu with the release. Names of text files match the numbers of the corrections included in the patch. Note: If necessary, notes about anomalies or known issues are provided.

Banner Baseline 7.x Patch Information Page 1 October 19, 2007


Technical Instructions for Applying Patches

SGHE Text Files Technical personnel should read text files provided by SGHE for each patch before applying the patch.

Text files include critical information about release dependencies, impact, solutions, platforms, and technical instructions.

Order of Application

You can apply defect corrections in order of the SGHE release date, which is the date the patch was released over BPOST. Patches in this release are listed in order by this date.

You can also choose to apply defect corrections by module in order of the SGHE release date.

It is essential that you first check the text files for technical instructions before applying patches.

Best Practice Apply patches to your test environment before applying them to production.

Testing and Certification of Patches

Testing and Certification

SGHE and OIIT have tested and certify Banner baseline patches at the prerequisites specified at Oracle 9.2.0.6.0 on HP-UX 11.11 and Sun 9. In addition, OIIT solicits institutional beta sites to test and certify some patches that address defects reported by USG institutions. Testing is for normal activities and does not cover all instances of idiosyncratic data or all local business practices.



Location of Patches and Related Documentation

Location on ftp.usg.edu

Patches and accompanying documentation from SGHE are placed on ftp.usg.edu based on the following directory structure:

banner/prod/system/7/version/patches/patches_MMDDYY

Example For example, patches for Student 7.4 released for production on October 19, 2007, and related documentation from SGHE are in the following location:

banner/prod/student/7/74/patches/patches_101907

Patches in this Release

Module Location of patches on ftp.usg.edu

Accounts Receivable 7.3

banner/prod/arsys/7/73/patches/patches_101907

Financial Aid 7.9 banner/prod/finaid/7/79/patches/patches_101907

Self-Service Faculty & Advisors 7.4

banner/prod/facweb/7/74/patches/patches_101907

Self-Service Student 7.4

banner/prod/stuweb/7/74/patches/patches_101907

Student 7.4 banner/prod/student/7/74/patches/patches_101907


ftp://ftp.usg.edu/


Banner 7.x Patch and Defect Correction Information for October 19, 2007 Patches are in order by the SGHE release date. Note: SGHE no longer provides a single text file with a patch that includes problems and functional impact descriptions for each defect correction in the patch. SGHE now provides separate files for each defect. For problem definition and functional impact of each defect within a patch, you must read those files. Patch titles are included here along with a list of defects corrected by the patch. Summaries are also included if they were provided in the posting.

SGHE Release Date System

Version Number

Patch Number

Module/Form/-Process

Release Dependencies Patch Title and Defects Corrected with Patch

09/07/07 (2007-91)

Student Self-Service

7.4.0.1 1-2qbi8a Upgrade 7.4 PROBLEM (1-2QBI8A): Student Self-Service 7.4 upgrade bombs on gostage if licensed for Financial Aid and upgrading from Student Self-Service 7.3. Gostage error: ========= This SQL error was caused intentionally because STUDENT-FINAID WEB 7.3.1 must b e applied before proceeding. select ' 'This SQL error was caused intentionally because STUDENT-FINAID WEB 7.3.1 must be applied before proceeding. * ERROR at line 1: ORA-00923: FROM keyword not found where expected ========= Both current release.pdf and Student Self-Service 7.4 upgrade guide says that Student Self-Service 7.3+ is a prerequisite.

09/10/07 (2007-92)

Student 7.4.0.1 1-2qoa4f

Upgrade 7.4 PROBLEM (1-2QOA4F): The saisf90r2.shl and .bat files are lacking a complete Student 7.4 Upgrade. There are 95 forms missing in these files.




Version Number

Patch Number



09/21/07 (2007-98)

Accounts Receivable

7.3.0.1 b_0907_forms_tas70300

tsicsrv.fmb tgadepc.fmb tgarras.fmb tgacolc.fmb tgiaccd.fmb tgacrev.fmb

7.0+ PROBLEM (1-12A14F): Issue 1 The Financial Aid Memo Balance and Other Memos fields do not correctly reflect the results of a term specific query when one is entered in the Account Summary block. The Financial Aid field appears to total all memos (all source codes) based on the query and the Other Memos field always displays the sum of all non-FA memos. Issue 2 If consecutive queries are done without doing a rollback, the FA Memo field is not calculated correctly. PROBLEM (1-1KS77K): TGADEPC should prohibit the entry of Expiration date less than Release date in order to be consistent with the rest of AR. Example: TGADEPC...created new deposit rule: DEPS Min Amt 100.00 Release Date 10-APR-2007 Expiration Date 10-FEB-2007 Record saved successfully. Then tested TSADETL...added DEPS deposit to student: fields defaulted in from TGADEPC entered term 200610, amount 200.00 Pressed save: Error:




Version Number

Patch Number



Release date must be less than or equal to Expiration date. Since the API checks for this condition anywhere that a deposit is processed (TSADETL, TGRFEED when it is fed, etc) the TGADEPC form should enforce the restriction when creating the default values. If this date condition exists (for trans loaded from outside source), TGRFEED will abort with error msg. PROBLEM (1-1RA0ZT): The following data condition on TGARRAS can cause TFRBILL to ASSESSCHG endlessly, until the job is stopped: The Start and End Dates are the same Frequency = Other Days = 0 To avoid this, set Days = 1 or higher so that the "next assess" date will be greater than the End Date after the first charge is created. PROBLEM (1-29QE3P): Using the scroll bar to move through records on TGACOLC generates the following messages: FRM-40737: Illegal restricted procedure SYNCHRONIZE in PRE-TEXT-ITEM trigger. Once you click 'OK', another message is displayed in the task bar: FRM-40734: Internal Error: PL/SQL error occurred. The form will scroll through the records, but the messages continue to appear. Using the Down Arrow key or the Next Record icon does not generate these error messages. PROBLEM (1-BAR2L): When the Frequency Rule = "Other (Enter Days)" the form allows a successful SAVE when no days are actually entered. This causes TFRBILL to error with the following: Starting TFRBILL (Release 7.2)




Version Number

Patch Number



RUN SEQUENCE NUMBER: ORA-01407: cannot update ("TAISMGR"."TBRRRAS"."TBRRRAS_ASSESS_DATE") to NULL WRN-ORACERR: Error occurred in file "tfrbill.pc" at line 2167 WRN-ERRSTMT: Following statement was last statement parsed: update TBRRRAS set TBRRRAS_ACTIVITY_DATE=SYSDATE, TBRRRAS_ASSESS_DATE= tfrbill terminated with error 0 lines written to /home/ban7/jobsub/ tfrbill_143574.lis Connected. Connected. This is the same issue as reported in defect CMS-DFCT33791, which was closed as part of the Defect Backlog project. PROBLEM (1-NUO6U): After a query is executed, if a rollback is performed, all records from TBRACCD are returned. This stops further processing until all records are returned. 1. Access TGIACCD, enter an ID an execute the query. 2. Click on the Rollback icon. All records are returned. PROBLEM (CMS-DFCT106090): TGACREV 7.0 User Sessions canvas - When a deposit number has wide letters, the display of the last character is cut off. Deposit number field is 6.5 ems wide, should be 8 ems.




Version Number

Patch Number



9/29/07 (2007-101)

Student 7.4.0.1 1-2nkwid slvres2.sql

7.3.3

PROBLEM (1-2NKWID): Banner Student poor performance with AS_RESIDENTIAL_LIFE view in Oracle 10g database. Patch for related Defect 1-X01BL has been applied. Full table scan on SLBRMAP. References to sgbstdn should be replaced with sgksels.f_get_sgbstdn_value.

9/29/07 (2007-101)

Student Self-Service

7.4.0.1 b_0907_dbprocs_bws70400

Recruiting Admissions Student Records Class Schedule Course Catalog General Person Admissions

6.1+ 7.3.3

PROBLEM (1-1EW4OS): When entering an address in bwskwpro.P_WebProspectMain you can enter a state and nation and the address is saved, whereas in the form SPAIDEN, when a state is entered, whether or not a nation is entered, a ZIP code must also be entered. The error checking should be consistent in both places. PROBLEM (1-29QE0U): The SSB Web Application package, bwskatst.P_ProcAppTests, permits the entry of test scores such as "80" when the range of the score is 020 to 100 and the number of digits is defined as 3. In INB this would not be valid and would have to be entered as "080". SSB accepts the value of 80 because it falls between 20 and 100 but the push does not fill in the data on SOATEST. There is a push failure due to the insufficient number of digits. If the user enters 1000 in SSB, it is rejected at the time of entry due to the range check and, possibly, the number of digits. Occurs only with numerically-defined test scores (ie ignoring leading zero) - get correct error message if test score defined as alpha-numeric. PROBLEM (1-2G8BXB): Titles from the SHAPQNO Qualifying Papers Form will not display on the Self-Service Transcript unless, on the SHATPRT Transcript Print Rules, the Qualifying Text print option is enabled. This is a defect against Self-Service only, Baseline SHRTRTC will print the Title if the Text is disabled... See the attached test case...




Version Number

Patch Number



PROBLEM (1-2M1ZRV): In Banner Student Self Service, if a student is assigned more then 2 active holds, and the stvhldd_disp_web_ind = 'Y' for the first one, but 'N' for the remaining ones, the first hold displays correctly. However, header information appears for each hold whose stvhldd_disp_web_ind = 'N'. This is working correctly in Faculty Self Service on bwlkgstu.P_ViewHold. PROBLEM (1-2NAS87): The Major for term may not display on the transcript. The Major for term does not display when the College by Term flag is not checked on SHATPRT. The Major for term display is dependent upon the College by Term flag, as well as the Major by Term flag. The major display should only be dependent on the Major by Term flag. PROBLEM (1-2PEG9K): The check boxes for the days selection on the Look-Up Classes to Add and Class Schedule Search need to be spaced closer to each text choice to avoid user confusion. PROBLEM (1-2PTQFD): You are experiencing severe SSB performance issues and may find long running query errors in the Self-Service Application Server error logs similar to the following: “[Mon Aug 13 18:23:02 2007] [warn] [client 10.240.61.30] mod_plsql: Long running URL [/PRODACC/ bwskfshd.P_CrseSchdDetl] timed out” The bwckgen1.sql performance fix entails removing SFRAREG out of the main query completely and making it a separate query. The fix removes the outer join to SFRAREG which was coded for pre Banner 6.1 clients who would have SFRSTCR records that don't have a corresponding SFRAREG (open learning registration) record. At least 3 long running queries are caused by the outer




Version Number

Patch Number



join to SFRAREG: bwskfshd.P_CrseSchdDetl bwsksreg.p_active_regs bwskhreg.p_reg_hist PROBLEM (1-2R2EF2): When an advisor goes in to view a student transcript, some student's events show up and some do not. We did notice it does not show on a Web transcript if there is no SHADEGR record. PROBLEM (1-2R347T): When viewing the academic transcript (unofficial) in faculty and advisor self-service there is no indication that the student has elected to have their information made confidential (indicated by setting confidential checkbox on biographical tab of spaiden). Other SSB pages display a yellow triangle with an exclamation point and a message to indicate that information about the student is confidential. Is there a WebTailor or some other setting that can be enabled to provide a similar message on the SSB transcript? PROBLEM (1-2SDT72): When accessing student advisee information: View Address/Phone, View Test Scores, ... the name hyperlink to the student information exposes the PIDM of the student, user can then type any value for student pidm into the browser address field, and see another person's information! This link is manufactured inside bwcklibs.P_ConfidStudInfo(), PROBLEM (1-LWA9T): There is a performance issue with the Admission Web Application High School page when clicking on 'Lookup High School Code'. When there is large amounts of data in SOBSBGI, the natn_cursor in BWSKALOG runs slow.

9/29/07 Student 7.4.0.1 b_0907_dbprocs_stu7

Admissions 7.0+ PROBLEM (1-21AIWH): When trying to push more than 1 student who has a prior college override we receive an error




Version Number

Patch Number



(2007-101) 0400

message and need to totally close BANNER and log in again to push 1 applicant and log out and back in to push another. *ERROR* (L010 7.3)ORA-06511: PL/SQL: cursor already open *ERROR*(v7.3.2.1)ORA-06511: PL/SQL: cursor already open PROBLEM (1-2O5BIK): Applicant is allowed to enter more than one test score record for the same test code and test date. The test scores will not push with this data condition and the push process will not complete for the application. The following error is encountered during the push process: Cannot create, the record already exists.

9/29/07 (2007-101)

Student 7.4.0.1 b_0907_forms_stu70400

Admissions Student Functionality Overall Registration Class Schedule Academic History Transfer Articulation Course Catalog Recruiting Location Management

7.3.2.1+

PROBLEM (1-1GW67Q): When the Sources, Interests, Comments tab on SAAADMS (version 7.3.1) is accessed by clicking on the tab the cursor is in the Sources block and the “FRM-40350: Query caused no records to be retrieved.” message is listed at the bottom of the page even though this person has an item listed in the Source block. The data appear to be correct although the error message is inconsistent with what is being displayed. If a user uses a Block-Next to access the page from the Checklist, the correct message is noted. PROBLEM (1-1T4VGL): When entering a value in the Maximum Course Load field that is less than the Minimum Course Load value, the following message is received: "*Error*, the maximum course load must be less than or equal to the minimum course load." The error message is incorrect. The Maximum is less than the Minimum; that is why the data cannot be saved. PROBLEM (1-20VYYC): If an applicant does not have a Source record, whenever a User navigates to the Source, Interests< Comments Tab, a pop-up "Query caused no




Version Number

Patch Number



records to be retrieved" occurs which must be acknowledged. This may also occur if the Interests in also without a record. This does not occur in the Contacts, Cohorts, Attributes Tab. PROBLEM (1-23CKOZ): All printer codes are recorded with capital letters. When a printer code is selected from the list of values it is brought in as all caps even though it is listed on GTVPRNT with small letters. PROBLEM (1-23P6W4): Unable to SAVE duplicated SAAADMS record after initially trying to save the record with required information missing. PROBLEM (1-23R5WJ): Enter invalid code in 1st block (example: student type). Click on a tab to navigate to any block other than curriculum (example: checklist). System navigates user to curriculum block instead and displays appropriate "invalid code" error (example: due to invalid student type code). Click OK and get "commit changes to curriculum before leaving block". Save and system navigates back to 1st block so can fix invalid value. PROBLEM (1-28M6KX): If the cursor is in the name field and you click on the Search icon, when a record is selected from SOAIDEN the ID is returned and displayed in the name field. Test Case Access SOAFOLK. The ID and name are listed. Delete the ID and tab to the name field, which was is also deleted. From the name field, click on the Search icon, which takes you to SOAIDEN. Enter a name (Test%) and query. Highlight a record and either double-click on it or use the Select option. The ID is brought back to SOAFOLK, but is displayed in the name field PROBLEM (1-298QT2): On SFARQSS auto hint for Request




Version Number

Patch Number



Date, Print Date, and Sent Date refers to 'Transcript' and not 'Enrollment Verification'. PROBLEM (1-2AEI5O): Changing the Enrollment max of a cross-listed course may delete the CRNs from SSAXLST and also remove the crosslist value on SSASECT. see test case PROBLEM (1-2AHQ01): Field is not long enough to display the full date, last digit of year is obscured. PROBLEM (1-2BWHHY): If the Display check box for elements LAST_NAME and FIRST_NAME are unchecked on SAAWAPP for the Web Section 'NAME', the user gets a "Page Cannot be Found error" in Self-Service Admission. The SAAWAPP form should not allow users to save a data element row where the 'Display' indicator is not checked, and the 'Required' indicator is checked. PROBLEM (1-2F0JJS): On SHATATR when you query by SUBJ, the courses are not being displayed in Effective Term order. So, a course with an effective term of 200710 is displaying before an effective term of 200610. PROBLEM (1-2MQE7Y): On SAAADMS, after selecting the Dynamic Help Query item from the Help menu for the Application Status Date field (SARADAP_APST_DATE), clicking on Cancel to close the GUAHELP window open the Web Credit Card Payment Information window. PROBLEM (1-2OW5JW): When a new attribute is added on SCADETL or SSADETL, the activity date does not include a timestamp. If the attribute is copied from an existing attribute when using the maintenance button on SCADETL, the timestamp is set correctly. If the attribute is defaulted from the catalog attribute to the




Version Number

Patch Number



section attribute upon the initial create of the section via SSASECT, the timestamp is set correctly. PROBLEM (1-2R22O7): For a non-gradable section, entry of a grade in the Midterm Grade field is allowed, but when an attempt is made to move out of the field a “Section not gradable or status prevents grads from being entered” message is returned. You can remove the grade, but the message will continue to appear and you’re not allowed move to another block or roll back. The only option is to exit the form. For a non-gradable section, when you move to the Final Grade field a “Section not gradable or status prevents grads from being entered” message is returned. The system will not accept an attempt to enter a grade. The user can then move to another field or rollback. PROBLEM (1-CZXU6): Performing NEXT BLOCK from the Mail Submissions block positions the cursor in the Checklist Items block instead of the Withdrawal Information block. PROBLEM (1-HQ6K3): When you call SRASUMI from SRARECR and attempt to exit-with-value with a specific recruiting record, you may return to SRARECR with more than one record. This may occur when there are multiple recruit records with the same Term code value. PROBLEM (1-SMLVH): Option to go to SOABGTA gives the error 'navigation was attempted to a disabled item'. The user is still taken to the SOABGTA form. PROBLEM (1-V2FJ1): If an ID has been defined on SIAINST, but does not have the Advisor field enabled, that ID can still be successfully saved as an Advisor on SGAADVR. It is only looking at SIAINST to see if their status is active or inactive for the term. To obtain Registration Alternate Pin numbers, Faculty Self Service requires that the person be coded as Active AND as an adviser for the alternate pin term (term students will be




Version Number

Patch Number



registering for) or the faculty adviser cannot even get to their advisees to obtain alternate pin numbers when clicking on advisee listing. The 2 contradict each other. Banner and Self Service should work the same way...help on SGAADVR indicates that advisor indicator must be checked in order to assign. PROBLEM (1-V8T4T): If a student's application status on SLARMAP has a status which has the 'Inactive' flag set on STVHAPS, then user receives error 'FRM-40700: No such trigger: INACTIVE_HAPS.' when attempting to view student's room assignments on SLARASG for the same term. You should still be able to view room assignment data, even if the application is inactive, as is on 6.x. PROBLEM (1-WYTI8): The following message is received on SFAALST when all enrollments for the course are canceled and the section has been canceled on SSASECT. It also occurs when the course is active and has enrollments, if the section is not gradable on SSASECT. FRM-41017: Cannot set UPDATE ALLOWED attribute of non-enabled item SFRSTCR.SFRSTCR_GRDE_CODE. See test case PROBLEM (CMS-DFCT86360): Two navigational problem on SSASRPO version 5.5:1) Go to SFASRPO and enter a term and ID Next block and enter a Permit Rollback Cancel The cursor goes back to the Key Block and the data is still in the form. 2) Go to SFASRPO and enter a term and ID




Version Number

Patch Number



Next block and click the Select icon (which should not be allowed) the following error is displayed FRM-40735 KEY-NXTKEY trigger raised unhandled exception ORA-06502

9/29/07 (2007-101)

Student 7.4.0.1 1-2ptkef

Registration 7.3.3 PROBLEM (1-2PTKEF): The 7.3.3 version of SFRNSLC will not run from the command-line after first placing the job on HOLD via GJAPCTL in Banner. SFRNSLC core dumps with a "Segmentation Fault" error as soon as user logs in to run it (i.e. before prompting for a userid). However, SFRNSLC will still run correctly when started directly via job submission in Banner. The "Segmentation Fault" error occurred on both Oracle 9i and 10g. PROBLEM (1-2SELT7): Summary Report prints run date in the Grad Date field, for students who have no Expected Graduation Date on SGASTDN. Note, the submittal file, sfrnslc.txt, is fine.

9/29/07 (2007-101)

Student 7.4.0.1 1-28csdh

Admissions new PROBLEM (1-28CSDH): The description for both SRBRECR_TERM_CODE and SARADAP_TERM_CODE_ENTRY in STVADDA is "Recruit Term Code". The latter should be "Applicant Term Code".

9/29/07 (2007-101)

Faculty and Advisor Self-Service

7.4.0.1 b_0907_dbprocs_bwl70400

Student Records General Person Class Schedule Course Catalog

5.3+ PROBLEM (1-1ORO7N): When accessing student advisee information: View Address/Phone, View Test Scores, ...the name hyperlink to the student information exposes the PIDM of the student, user can then type any value for student pidm into the browser address field, and see another person's information! This link is manufactured inside bwcklibs.P_ConfidStudInfo(), PROBLEM (1-2AHBSS): Student data displayed is the last record in the Faculty Detailed Class List, not the previously selected ID. Scenario:




Version Number

Patch Number



1 Select a student ID from the Student Information page of Faculty and Advisor Self-Service. 2. View the Detail Faculty Class list. 3. View a Transcript, Student Schedule or Registration History. 4. The data displayed will be for the last student in the Detail Faculty Class List instead of the student ID that was selected in step 1. PROBLEM (1-2MP9D7): When viewing the academic transcript (unofficial) in faculty and advisor self-service there is no indication that the student has elected to have their information made confidential (indicated by setting confidential checkbox on biographical tab of SPAIDEN). Other SSB pages display a yellow triangle with an exclamation point and a message to indicate that information about the student is confidential. Is there a WebTailor or some other setting that can be enabled to provide a similar message on the SSB transcript? PROBLEM (1-2NAS60): The Major for term may not display on the transcript. The Major for term does not display when the College by Term flag is not checked on SHATPRT. The Major for term display is dependent upon the College by Term flag, as well as the Major by Term flag. The major display should only be dependent on the Major by Term flag. PROBLEM (1-2OWJV1): Titles from the SHAPQNO Qualifying Papers Form will not display on the Self-Service Transcript unless, on the SHATPRT Transcript Print Rules, the Qualifying Text print option is enabled. This is a defect against Self-Service only, Baseline SHRTRTC will print the Title if the Text is disabled... See the attached test case...




Version Number

Patch Number



PROBLEM (1-2PTH40): The check boxes for the days selection on the Look-Up Classes to Add and Class Schedule Search need to be spaced closer to each text choice to avoid user confusion. PROBLEM (1-2Q9AFB): You are experiencing severe SSB performance issues and may find long running query errors in the Self-Service Application Server error logs similar to the following: “[Mon Aug 13 18:23:02 2007] [warn] [client 10.240.61.30] mod_plsql: Long running URL [/PRODACC/ bwskfshd.P_CrseSchdDetl] timed out” The bwckgen1.sql performance fix entails removing SFRAREG out of the main query completely and making it a separate query. The fix removes the outer join to SFRAREG which was coded for pre Banner 6.1 clients who would have SFRSTCR records that don't have a corresponding SFRAREG (open learning registration) record. At least 3 long running queries are caused by the outer join to SFRAREG: bwskfshd.P_CrseSchdDetl bwsksreg.p_active_regs bwskhreg.p_reg_hist PROBLEM (1-IQ6LW): When an advisor goes in to view a student transcript, some student's events show up and some do not. We did notice it does not show on a Web transcript if there is no SHADEGR record.

9/29/07 (2007-101)

Student 7.4.0.1 b_0907_c_stu70400

Academic History Electronic Prospects Location

7.0+ PROBLEM (1-2ARB4H): If a Student Status Code on STVSTST exceeds 16 characters and is used by SHRIGRS, the program will complete successfully but the shrigrs.log will contain warnings, such as the following: RUN SEQUENCE NUMBER:




Version Number

Patch Number



Management Registration General Person Student Functionality

WRN-LONGTOK: Token "Dismissed/Suspended/Terminated" exceeds containing column width (16) WRN-LONGTOK: Token "Dismissed/Suspended/Terminated" exceeds containing column width (16) PROBLEM (1-2KYOY5): Gender will not load from SRTLOAD when in lower case form. It loads in to the temporary tables, as displayed on SRAPREL, as 'N'. When the gender in the file/ tape is in upper case, the gender loads correctly as 'M' male or 'F' female (displayed on SRAPREL). PROBLEM (1-2M2Q5X): When SLRSCHD.pc is run, and the Room Assignments are created on SLARASG, the Days, Months or Term value is not calculated based upon the Rate Code and the SLALMFE Rules for that Rate Code. The fields default to "0." This means that Location Management fee assessment cannot calculate the charges for the term. PROBLEM (1-BW641): Incorrect page breaking makes SFPREGS report unusable. The page breaks are happening after each type of record for each student, so for 57 students I ended up with a 640 page report, although the first few pages do print correctly. The volume of pages can be so huge that the report cannot be printed, or even viewed in any useful way. Also, for the first person printed, no ID or name prints: 15-FEB-2006 06:32:49 Malaln7_Ban7 PAGE 1 200089 Registration Purge SFPREGS Audit Report Only Sect: 10004 Ind: Y Grde: Date: Rsts: Y ** WARNING ** Gradable Section Without Grade




Version Number

Patch Number



PROBLEM (1-C1J2X): When compiling sfrschd.pc the log may show this warning message: "sfrschd.pc", line 858: warning: statement not reached The program does compile. This seems only to occur on a Sun Solaris. PROBLEM (1-FTKL8): The same information can be printed multiple times for a faculty member. If multiple records exist in SIBINST (multiple effective terms) for a PIDM, an entry is printed in the report for each occurrence. PROBLEM (1-IHPO7): If student has more than one active hold of the same type, SGPHOLD (update mode only) will fail if it tries to delete or release the holds: RUN SEQUENCE NUMBER: ORA-01422: exact fetch returns more than requested number of rows ORA-06512: at line 1 WRN-ORACERR: Error occurred in file "sgphold.pc" at line 805 WRN-ERRSTMT: Following statement was last statement parsed: declare this_rowid VARCHAR2 ( 27 ) ; lv_rec gb_hold . hold_rec ; lv_cu sgphold terminated with error PROBLEM (CMS-DFCT100522): SFPAGRD - Release 6.0 Issue 1: Does not delete records from GJBPRUN when it completes. All other banner jobs delete records from GJBPRUN upon completion. Issue 2: Assigns grades to students who have previously dropped the class. The assignment of grades to students in a class should only be done where registration status code allows for grading (STVRSTS_GRADABLE_IND = Y).




Version Number

Patch Number



Issue 3: Assigns grades to both OLR and traditional courses. According to documentation, this process is for OLR courses only.

9/29/07 (2007-101)

Student 7.4.0.1 1-2n5pth

Electronic Prospects

7.4 PROBLEM (1-2N5PTH): ACT EOS 2007-2008 Regulatory Changes

10/2/07 (2007-103)

Financial Aid 7.9.0.1 1-2txosf

REROR08 Electronic Data Exchange

7.8 PROBLEM (1-2TJWIT): When REROR08 is compiled in debug mode, it fails with the error: reror08.pc: In function `upd_rebrdrq': reror08.pc:2525: parse error before `char' make: *** [reror08] Error 1 Workaround: Move the variable declaration before the SCT_DEBUG section of upd_rebrdrq as show below: FROM: static void upd_rebrdrq(void) { #ifdef SCT_DEBUG printf("Executing upd_rebrdrq \n"); fflush(stdout); #endif char batch_no[27]; TO: static void upd_rebrdrq(void) { char batch_no[27]; #ifdef SCT_DEBUG printf("Executing upd_rebrdrq \n");





Version Number

Patch Number



fflush(stdout); #endif PROBLEM (1-2TXOSF): The REROR08 process appears to process some students and then stops if there is a student that was loaded without a Date of Birth on RNANA08. Although the output lists some students, the REAOR08 form is not populated for any student. The error message indicates an enrollment problem. ORA-01405: fetched column value is NULL WRN-ORACERR: Error occurred in file "reror08.pc" at line 3016 WRN-ERRSTMT: Following statement was last statement parsed: declare lv_enroll_date rebpayv . rebpayv_enrollment_date % TYPE ; lv_b Connected. Connected. Workaround: To find the student with the blank birthdate, run REROR08 in debug and enter the Date of Birth on RNANA08. Then rerun REROR08.

oiit summary notes for banner baseline 7 - university …€¦ · · 2010-02-17oiit’s summary...

Documents