SCT Banner Student / Release Guide / 7.0

More documents

Recommendations

Info

Section 5 Common Matching - FunctionalChanged Reports and ProcessesForms Not on MenusPlease note that the Person Matching Form (SOQMTCH) and the ProspectMatching Form (SRQMTCH), which are now obsolete, were not displayed on anyBanner Student menus.Changed Reports and ProcessesElectronic Prospect Match (SRRSRIN)This process has been updated to call the new matching procedure, instead ofcalling SAKMTCH. A new SAKMTCH procedure, p_insert_sotcmme, is used topopulate the temporary table for high school matching data fields.Elec App Verify/Load Process (SARETMT)This process has been updated to call the new matching procedure, instead ofcalling SAKMTCH. A new SAKMTCH procedure, p_insert_sotcmme, is used topopulate the temporary table for high school matching data fields.The following parameters have been removed from the process:• Match only on SSN and Last Name• Match on Current SPRIDEN• Last Name Only Match LengthThe Interface Code w/Match Rules parameter now uses the matching rulesassociated with the interface code on STVINFC to match the application to Banner.If users want to match on just SSN and last name, they can create a matching ruleon GORCMRL to do so.Report SampleElec App Verify/Load Process (SARETMT)Please see the following landscaped section for report parameters and sampleoutput.Student Release 7.0 January 2005180 Release Guide Confidential
Section 5 - Common MatchingSample ReportElec App Verify/Load Process (SARETMT)DescriptionThis process matches, verifies, and loads electronic applications to Banner production tables using the matching rules definedon SOAINFR or by matching on SSN and Last Name. The process performs the test score equivalency lookup and then storesthe equivalent test scores if applicable.This process has three report sections. The first two sections are optional and collect and print the following: successfullyverified and/or loaded applications, applications with verification or load errors, and detail or summary information. Thethird section is the control page.Processing NotesThe Interface Code parameter provides the values for the matching algorithm, which determines if the record status is eitherNew, Matched, Suspense, or Error. The matching needs to be done only for new applicants. If the person is not matched toa Banner record, a new SPRIDEN row will be created for the person with either a generated ID or the SSN, the SABSTUD rowwill be created with a new pidm value, and the Person Status (Indicator) will be updated to Y. If the person matches a Bannerrecord, the SABSTUD row will be created with the Banner pidm value, and the Person Status (Indicator) will be updated toY. If the person falls into the suspense group, the Person Status (Indicator) will be updated to S. Applications must have a Yin the Person Status (Indicator) before they can be pushed into Banner production.The Previously Applied and Previously Attended elements appear in the Name section of the Web data entry pages. Assumingthese elements are added to the Name section using SAAWAPP, if the student is in suspense status, and they state that theyhave never attended or submitted an application, the person status will be changed from Suspense to New.If the electronic applicant read in the main select has already been through the match phase and they have a SPRIDEN record,the match step will be bypassed. This may happen in the case of applicants who are initially put into the match-suspense state.The user needs to resolve the suspense issue using SAAEAPS. They have the option of completing the verification processonline after resolving the match issues and accepting the person status or re-running SARETMT.Student Release 7.0 January 2005181 Release Guide Confidential
Page 1 and 2:
SCT BannerStudentRelease GuideJanua
Page 3 and 4:
Release GuideStudent SystemIntroduc
Page 5 and 6:
Table of ContentsGeneral Student -
Page 7 and 8:
Table of ContentsHow the New Matchi
Page 9 and 10:
Table of ContentsLearner Curriculum
Page 11 and 12:
Table of ContentsLearner Module Val
Page 13 and 14:
Table of ContentsChanged Tables . .
Page 15 and 16:
Table of ContentsPCU Tape Load Regu
Page 17 and 18:
IntroductionIntroductionThis docume
Page 19 and 20:
Section I New User Interface - Func
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Section 2 New Banner Online Help -
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Section 3 Concurrent Curricula Phas
Page 43 and 44:
Page 45:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Section 3 - Concurrent Curricula Ph
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Section 4 New Value-Based Security
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130: Section 4 New Value-Based Security
Page 145 and 146: Section 5 Common Matching - Functio
Page 179: Section 5 Common Matching - Functio
Page 183 and 184: Section 5 - Common MatchingSample R
Page 189 and 190: Section 6 Improved Drop/Withdrawal
Page 199 and 200: Section 7 Concurrent Curricula Phas
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Section 9 Common Matching - Technic
Page 261 and 262:
Section 9 Common Matching - Technic
Page 263 and 264:
Section 10 APIs - TechnicalAPI Disc
Page 265 and 266:
Section 10 APIs - TechnicalAPIs Use
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Section 10 APIs - TechnicalChanged
Page 283 and 284:
Section 11 Improved Drop/Withdrawal
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
Page 293 and 294:
Page 295 and 296:
Section 12 Miscellaneous Enhancemen
Page 297 and 298:
Page 299 and 300:
Page 301 and 302:
Page 303 and 304:
Page 305 and 306:
Page 307 and 308:
Page 309 and 310:
Page 311 and 312:
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Section 13 Problem ResolutionsCatal
Page 319 and 320:
Section 13 Problem ResolutionsSched
Page 321 and 322:
Section 13 Problem ResolutionsSched
Page 323 and 324:
Section 13 Problem ResolutionsCours
Page 325 and 326:
Section 13 Problem ResolutionsSuppo
Page 327 and 328:
Section 13 Problem ResolutionsLocat
Page 329 and 330:
Section 13 Problem ResolutionsLocat
Page 331 and 332:
Section 13 Problem ResolutionsRecru
Page 333 and 334:
Page 335 and 336:
Page 337 and 338:
Section 13 Problem ResolutionsAdmis
Page 339 and 340:
Page 341 and 342:
Page 343 and 344:
Page 345 and 346:
Section 13 Problem ResolutionsGener
Page 347 and 348:
Section 13 Problem ResolutionsRegis
Page 349 and 350:
Page 351 and 352:
Page 353 and 354:
Page 355 and 356:
Page 357 and 358:
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Page 365 and 366:
Page 367 and 368:
Section 13 Problem ResolutionsAcade
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
Section 13 Problem ResolutionsCAPP
Page 391 and 392:
Page 393 and 394:
Page 395 and 396:
Section 13 Problem ResolutionsOvera
Page 397 and 398:
Page 399 and 400:
Page 401 and 402:
Page 403 and 404:
Section 13 Problem ResolutionsFTES
Page 405 and 406:
Section 13 Problem ResolutionsRepor
Page 407 and 408:
Section 13 - Problem ResolutionsSam
Page 409 and 410:
Page 411 and 412:
Page 413 and 414:
show all

SCT Banner Student / Release Guide / 7.0

Create successful ePaper yourself

Delete template?

Save as template?