25.01.2014 Views

ODS / Release Guide / 3.1

ODS / Release Guide / 3.1

ODS / Release Guide / 3.1

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 4 Problem Resolutions<br />

Common<br />

being used. The change table was changed from AGRMCHG to the correct one,<br />

AGRGCHG.<br />

Resolution<br />

The triggers on AGBMGID and AGRMGIF were using the wrong change table,<br />

AGRMCHG. The triggers were changed to use AGRGCHG instead.<br />

1-J60RF<br />

Impact<br />

The SPOUSE_IND in CONSTITUENT was not correctly being calculated. It needs<br />

to check for the cross reference records in MAT_RELATION (instead of the spouse<br />

records), and then also check that the MAT_RELATION.SPPOUSE_IND = Y.<br />

Resolution<br />

Create a new function which checks for an active spouse from MAT_RELATION and<br />

checks for a xref_code = X.<br />

This defect was corrected prior to the <strong>ODS</strong> <strong>3.1</strong> release. This fix was replaced because<br />

additional changes were made for the Relationship reporting view(RPE 1-EKBA1).<br />

1-IYIUV<br />

Impact<br />

The wrong session was being selected when there were more than one SESSION_ID<br />

for a USER_ID for a given day.<br />

Resolution<br />

The TRUNC on the parameter date was removed. The AGBCSHR_START_DATE<br />

and AGBCSHR_END_DATE were removed so that the correct session is selected.<br />

Common<br />

1-1GE4PX<br />

Impact<br />

The Communications process is currently designed to refresh based on the PIDM<br />

since the only database required fields are PIDM, System Code, and Activity Date.<br />

This means that every time a letter is processed (either update, insert or delete), all<br />

records for that PIDM are deleted and then all remaining records are re-inserted.<br />

Obviously, any school that fully utilizes Banner's letter process is going to have a lot<br />

of entries per person. So if an individual has, over the course of two years, 20<br />

GURMAIL entries (even if they are from different systems like Advancement and<br />

Admissions), every time a new letter is added, all 20 letters are reprocessed. This<br />

creates a tremendous amount of unnecessary overhead for processing.<br />

Given the fact that a school may have thousands of students receiving mass mailings<br />

on a regular basis, you can see where the performance issues could start to creep in<br />

over time.<br />

Operational Data Store <strong>Release</strong> <strong>3.1</strong> April 2007<br />

30 <strong>Release</strong> <strong>Guide</strong> Confidential

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

Saved successfully!

Ooh no, something went wrong!