11.07.2015 Views

Banner Student / Release Guide / 7.3.2

Banner Student / Release Guide / 7.3.2

Banner Student / Release Guide / 7.3.2

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Section 4 Problem ResolutionsAdmissions ModuleSAAWATRSAAWATRSRARECR,SRAQUIK,SRRINQR,SRKPREL,SARBDSN,SARRATE,SAKL170,SORAINF,SOKAINF,SAADCBT(#1-NRUHS)Description: If you copied a row using the Insert Record or Duplicate Recordfunction keys, and changed the term and start and end dates, the system copied theactivity date from the original record rather than using the current date when therecord was saved.Impact: The wrong date was being put on the duplicated record.Resolution: Triggers have been modified to correct this.(#1-YJTTC)Description: The form did not compile in a database that used VPD, because theWHEN-BUTTON-PRESSED trigger on the COPY_CALENDAR_BTN trigger in theKEY_BLOCK had insert statements for the SARWATR and SARWATD tables but noexplicit column list.Impact: The form could not be used.Resolution: The trigger has been modified to match the standard of using anexplicit column list for the insert statements.(#1-WBCM1)Description: Performance problems existed with Recruiting and Admissions formsand processes with Oracle 10g.Impact: There may be slow performance on certain objects (SRAQUIK, SRARECR,SAADCBT, SORAINF, SRRPREL, SRIPREL) or when you migrate an electronicprospect (SRRINQR, SARBDSN, SARRATE).Resolution: All references to the SRVCCUR, SAVCCUR, and SOVCFOS views havebeen replaced with references to the SOVLCUR and SOVLFOS views. In some casesqueries of curriculum data have been moved outside of the main selects and intoseparate queries.SRARECR, SRAQUIK, and SRRINQR were released with <strong>Student</strong> <strong>Release</strong> 7.3.1.SAADCBT, SORAINF, SOKAIN1, SRKPRE1, SAKL170, SARRATE, and SARBDSNwere released in a 7.3.1.1 patch.TablesSARADDR,SARERUL(#CMS-DFCT93018)Description: The table comment for SARADDR incorrectly starts with "ElectronicsAdmission" instead of the correct "Electronic Admissions". Similarly, the SARERULtable, as well as the SAVEAP1, SAVEAPS, and SAVHEAD views currently start with"Electronic Application" or "Electronic Applications", but should instead start with"Electronic Admissions" for consistency.Impact: This needs to be corrected so that there is consistency when querying thedata dictionary via DBA_TAB_COMMENTS.Resolution: SARADAP and SARERUL have been corrected. The saradap1.sql andsarerul1.sql scripts are delivered to update the table comments.February 2007 <strong>Student</strong> <strong>Release</strong> <strong>7.3.2</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 101

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!