24.12.2014 Views

SCT Banner Financial Aid / Release Guide / 7.0

SCT Banner Financial Aid / Release Guide / 7.0

SCT Banner Financial Aid / Release Guide / 7.0

SHOW MORE
SHOW LESS

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

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

Section 60 Problem Resolutions<br />

Forms/Processes<br />

Resolution: Modified RPRLPRD to keep user in Base Data Block until data is<br />

entered, unless user performs a rollback or decides to exit the form.<br />

RPRSBPR (#90764)<br />

Description: Prior to Oracle 9i, select statements with a Group By clause and no<br />

Order By clause would implicitly order the returned rows using the same order as<br />

the Group By clause. Oracle 9i no longer does this implicit ordering correctly when<br />

the Order By clause is not used.<br />

Client Impact: The Applicant Budget Report (rbrabud.pc), the Budget Component<br />

Report (rbrbcmp.pc), <strong>Financial</strong> <strong>Aid</strong> Student Billing Payment Report (rprsbpr.pc)<br />

and Fund by Term View (rfvftrm.sql) are sorted incorrectly.<br />

Resolution: Added Order By clauses to all appropriate select statements in<br />

processes rbrabud.pc, rbrbcmp.pc, rprsbpr.pc and view script rfvftrm.sql.<br />

RRAAREQ (#93378)<br />

Description: If the Perkins MPN is not associated to the fund prior to awarding,<br />

manually adding the requirement on the RRAAREQ form does not carry the Perk<br />

MPN indicator from the RTVTREQ form. In addition, if the requirement was<br />

satisfied in a prior year, this prior year information does not roll forward to the new<br />

year Perkins MPN window.<br />

Client Impact: Perk MPN indicator is not working as intended, requires a rollback<br />

to view the Perk MPN indicator after creating the requirement manually.<br />

Resolution: Modified the form to populate Perk MPN indicator when the<br />

requirement is added manually.<br />

(#94878)<br />

Description: DQYPASGN, RRAAREQ and ROARMAN include specific code to<br />

prevent the deletion of tracking requirements with RRRAREQ_SYS_IND of M, B and<br />

F, but do not protect records with RRRAREQ_SYS_IND = X.<br />

Client Impact: Unsatisfied documents inserted into RRRAREQ table by Xtender<br />

Solutions are deleted when grouping processes are run.<br />

Resolution: In order to prevent tracking requirements which have a<br />

RRRAREQ_SYS_IND of X from being inadvertently deleted by grouping processes, the<br />

coding of DQYPASGN, RRAAREQ, and ROARMAN was altered to include the value<br />

of X. Therefore, documents established by Xtender Solutions should not be<br />

adversely affected by the running of these grouping routines.<br />

RRREXIT (#93720)<br />

Description: RRREXIT is not properly creating EXIT requirements for no-show<br />

students; students with enrollment greater then or equal to half time in the previous<br />

term and no enrollment in the current term. It will create an EXIT requirement for<br />

a student with enrollment less then half time for the previous term and no<br />

enrollment for the current term.<br />

Client Impact: Students are incorrectly getting EXIT requirements set or not set<br />

depending on their current term and previous term enrollment status.<br />

Resolution: Modified RRREXIT to select students that have a previous enrollment<br />

greater then or equal to half time but have no current term enrollment.<br />

January 2005 <strong>Financial</strong> <strong>Aid</strong> <strong>Release</strong> <strong>7.0</strong><br />

Confidential <strong>Release</strong> <strong>Guide</strong> 675

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

Saved successfully!

Ooh no, something went wrong!