Banner Student / Release Guide / 7.3.2

More documents

Recommendations

Info

Section 4 Problem ResolutionsAdmissions ModulePackagesSAKCHK1SAKCHK1,SAKL170SAKDCR1SAKL040,SAKL050,SAKL060,SAKL140,SAKL150,SAKL160(#1-PLQLJ)Description: When a checklist item was entered that was validated against STVSBGI,the item description on (SAAADMS) could be updated to replace the descriptionfrom STVSBGI. When the checklist was received and entered on SOAPCOL orSOAHSCH, then the default description would overwrite the updated descriptionentered by user.Impact: Incorrect checklist data was being saved.Resolution: The P_sorpcol_UpdChecklist item and the SARCHKL_C cursor havebeen updated. The SARCHKL update logic has been changed to prevent the overlayof user-entered description information.(#1-10QE0M)Description: When a curriculum was defined as primary or secondary on SAACHKB,those settings were ignored by the checklist process. Also, when the Field of StudyType was blank in Banner 7.x for a row that had a major code from Banner 6.x, thatrow needed to be re-evaluated to determine where or not the type should be set toMAJOR.Impact: New fields were added to the form in Banner 7.x for Field of Study Typeand Curricula. The delivered value for the Field of Study Type field is Null, and thedefault value is MAJOR. The delivered value for the Curricula field is Primary. Thesevalues are noted in the form documentation. Existing checklist rules will only lookat the major and primary curriculum records as in the past. You can modify yourrules as needed to take advantage of the new options for field of study and curricula.Resolution: The SARCHKB_C cursor has been changed to check for the Primary andSecondary settings on SAACHKB.(#1-K7DNU)Description: In order for an auto-decision that was based on college GPA to beeligible for assignment to a student, that decision needed to be built on SAADCSNwith a degree code. If the degree code was not present, the decision would not belisted as eligible (*) for assignment on SAADCRV. If null, the degree code shouldhave functioned as a wild card. Otherwise, a rule would need to be entered for everypossible degree code.Impact: The auto- decision process required a degree code to process a decisionbased on college GPA. This was causing eligible decisions to not be assigned, unlessseparate rules were created.Resolution: The f_ChkPriorCollege function has been modified to correct this.(#1-GLNU7)Description: Some system messages should be removed from the push packages sothat more or all of the error messages will be displayed on SAAEAPS.Student Release 7.3.2 February 2007102 Release Guide Confidential
Section 4 Problem ResolutionsAdmissions ModuleImpact: Error messages received during the push process contained Oracle-relatederror information. This limited the actual reason for the error condition.Resolution: Oracle-related error information has been removed to allow a moremeaningful error message to be displayed to user.SAKL090(#1-130JHL)Description: If a prior college name was manually entered for a self-serviceapplication, the P900 procedure and L090 routine had to be manually overridden.Impact: In a self-service application, if you manually entered prior collegeinformation and then pushed the application using the L090 routine, the priorcollege had to be manually overridden so the application would be pushed. Thiscaused additional work for users when applications were pushed into Banner.Resolution: The procedure that loads the prior college data was not checking for aNULL source/background institution code (STVSBGI) and tried to load data to theSORPCOL table when no valid STVSBIG code existed. This resulted in an error,and the SARPERR_COMPLETE _IND was updated with an N instead of a Y to enablethe P900 procedure to be completed. The sakl090.p_load_sorpcol procedurewas not counting the college rows as it added the rows, as it should have been doing.The sakl090.p_load_sorpcol procedure will now count the actual SORPCOLrows added, instead of relying on the count of the SARPCOL rows after the insertsare completed. The procedure will also check for a NULL source/backgroundinstitution code (STVSBGI) before trying to add rows to the SORPCOL table. If theSTVSBGI code is NULL, the procedure will not insert rows into SORPCOL, and therows will not be counted by the pcol_cnt counter. The pcol_cnt counter will bechecked after all inserts have been done.SAKLIB1,SABIDEN_KEY_INDEX(#1-1CGKN9)Description: Full table scans occurred in Admissions on the SARHEAD table.Impact: This could cause performance issues at larger schools with high numbers ofapplications.Resolution: A new index has been added on the SABIDEN_PIDM column that willallow for a more efficient join between SABIDEN and SARHEAD.The saklibs.sarheadc and bwskalog.getchoicesc cursors have been modified.The OR condition has been converted with a subselect that picks a PIDM fromSABIDEN or an AIDM from SARHEAD to form a union, using an inner join of thetwo tables. This allows the new index to be used, while removing the full table scan.SAKP130(#1-PLGNG)Description: A non-numeric GPA could not be pushed without causing an error.Also, the numeric example from the High School GPA field in Self-ServiceAdmissions needed to be removed or changed to a non-numeric example.Impact: A push error was received when a Web application had an associated highschool GPA record that was non-numeric. This occurred when previous Webapplications existed for the applicant. The application that received the push errorcould not be manually processed, and a script needed to be written to remove theFebruary 2007 Student Release 7.3.2Confidential Release Guide 103
Page 3 and 4:
Release GuideStudent SystemIntroduc
Page 6 and 7:
Table of ContentsThis page intentio
Page 8 and 9:
IntroductionThis page intentionally
Page 10 and 11:
Section 1 PESC/XML Transcript Phase
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Section 1 - PESC/XML Transcript Pha
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53: Section 1 - PESC/XML Transcript Pha
Page 58 and 59: Section 2 PESC/XML Transcript Phase
Page 60 and 61: Section 3 Miscellaneous Enhancement
Page 74 and 75: Section 4 Problem ResolutionsSchedu
Page 76 and 77: Section 4 Problem ResolutionsFacult
Page 79 and 80: Section 4 Problem ResolutionsLocati
Page 81 and 82: Section 4 Problem ResolutionsLocati
Page 83 and 84: Section 4 Problem ResolutionsRecrui
Page 85 and 86: Section 4 Problem ResolutionsRecrui
Page 87 and 88: Section 4 Problem ResolutionsAdmiss
Page 101: Section 4 Problem ResolutionsAdmiss
Page 107 and 108: Section 4 Problem ResolutionsGenera
Page 109 and 110: Section 4 Problem ResolutionsRegist
Page 117 and 118: Section 4 Problem ResolutionsAcadem
Page 119 and 120: Section 4 Problem ResolutionsAcadem
Page 121 and 122: Section 4 Problem ResolutionsCAPP M
Page 123 and 124: Section 4 Problem ResolutionsOveral
Page 129 and 130: Section 4 Problem ResolutionsValida
Page 131 and 132: Section 4 - Problem ResolutionsSamp
Page 153 and 154:
Section 4 - Problem ResolutionsSamp
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
show all

Banner Student / Release Guide / 7.3.2

Create successful ePaper yourself

Delete template?

Save as template?