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...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Section 4 Problem ResolutionsRecruiting ModuleSRARECR,SRAQUIK,SRRINQR,SRKPREL,SARBDSN,SARRATE,SAKL170,SORAINF,SOKAINF,SAADCBTSRARECRSRAWACK(#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.(#1-8OZ2L)Description: You could save a recruiting record without creating a curriculumrecord, if you performed a Rollback in the SRBRECR block and saved the changes.Impact: Incomplete records could be saved.Resolution: A trigger has been modified to validate that the SRBRECR record has atleast one primary curriculum and major when the SORLCUR block status is “new”.(#CMS-DFCT86546)Description: The form was supposed to use automatic sequence functionality if nosequence numbers were entered.Impact: Sequence numbers are not re-sequencing properly. The auto sequencing isnot working.Resolution: A trigger has been modified to use the auto sequencing(SRRWACK_SEQ_NO).PackageSRKPRE1(#1-1FU4Q9)Description: The comment for the p_update_sabsupl in the SRKPRE1 packagebody of the SRKPREL package was copied from the preceding procedure (insertSABSUPL). It should read "procedure to update Supplementary information",instead of "procedure to insert Supplementary information".Impact: Code comments are used by developers, not end users, so they would notbe affected.Resolution: The object documentation has been corrected.February 2007 <strong>Student</strong> <strong>Release</strong> <strong>7.3.2</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 85

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

Saved successfully!

Ooh no, something went wrong!