Advisement Report Repeat Checking Logic Works Incorrectly After Bundle 44/PUM image 4 Update To Cobol SRPCAXR2
(Doc ID 2254944.1)
Last updated on NOVEMBER 01, 2017
Applies to:PeopleSoft Enterprise CS Academic Advisement - Version 9 to 9 [Release 9]
PeopleSoft Enterprise CS Academic Advisement - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
On PeopleSoft Enterprise Campus Solutions, Academic Advisement, Reports
A change to how AA processes repeats when substituting the Default AA What-if Grade for in-progress enrollments broke existing functionality. It now process repeats on ALL repeated enrollments in ALL past terms, not just current term. This change causes GPA and unit calculations within the audit to be inaccurate because previous "exclude from GPA repeat codes" are now processing as "include in GPA repeat codes."
Expect the AA audit report to reflect the same repeat processing as running the end-of-term repeat checking process would with the same Default AA What-if Grade value assigned to the in-progress course. The AA repeats should not change enrollment attributes on enrollments where a repeat code value has already been assigned.
The issue can be reproduced at will with the following steps:
1. Confirm that a Default AA What-If Grade field value is assigned on the grading basis table.
2. Navigate to Student Academic Advisement, Request Advisement Report for a student who has multiple enrollments of the same class, some with repeat codes already assigned. Generate a new report request.
3. Review the degree audit results and note that courses with existing repeat codes that previously excluded them from being applied to requirement lines are now treated as if no code exists. The courses are inappropriately applied to meet a requirement line.
The change in functionality is a critical issue that negatively impacts campuses as the audits are no longer correct for students with repeats and does not align to records information which leads to confusion to campus users. This change also negatively affects batch processing and reporting.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document