Dear Colleagues
Just in case you don't follow the main HEUG listserves, here is a 'reprint' of an item posted on the SR listserv overnight.
Regards
Ian
************************************************************************
Campus Solutions Update – Post Enrollment Requisite Checking (PERC)
There has been some 'buzz' about the new Post Enrollment Requisite Checking enhancement that was provided to us from Oracle in CS v9.0 Bundle 21 on the SR Listserv. In response to that, the following information from Oracle is intended to clarify some of the functionality provided and eliminate the confusion around these issues:
Question 1:
At the point of the initial installation of bundle 21, which includes PERC, is it possible to use post enrollment requirement checking on students who have enrolled prior to the bundle being applied?
Answer 1:
Yes, this is possible, although there is a bit of functionality that will not be applicable this first time thru. Students who enrolled prior to Bundle 21 being installed and PERC being configured and activated will have an enrollment requirement status of "Unknown". This means that students who enrolled with a permission number, an override, or who were enrolled thru the Enrollment page, will not be identified as such; they too will have an enrollment requirement status of "Unknown".
Once you install Bundle 21, configure and activate PERC, you can then immediately run the Post Enrollment Requirement Checking process to get the most recent post-enrollment status. By running the PERC process, you will be able to identify students who have met the enrollment requirements. The only issue you will run into for this time only (students who were enrolled prior to the installation of PERC), is that you will be running the PERC process for all students. This means that there will be students who may have a post enrollment requirement status of conditionally satisfied or not satisfied that were actually enrolled with a permission, override, or thru the Enrollment page as mentioned above. In this case, we recommend that you manually review these students prior to dropping them from the class.
Question 2:
Not all fields are displayed on the Enrollment Requirement Roster.
Answer 2:
If you go to the Enrollment Requirement Roster prior to running the post enrollment requirement process, only relevant data will be displayed. Data columns specific to post enrollment requirement checking will be hidden until that process is run.
Columns displayed:
Prior to post enrollment requirement checking being run, the following columns are displayed under requirement data: Select checkbox, student id, student name, the student's enrollment requirement status (as defined at the point of enrollment), the student's enrollment status (e.g. enrolled, waiting) and a status note if required (e.g. the waitlist position).
Once post enrollment requi! rement checking is run, the following additional columns will be displayed on the Enrollment Requirement Roster: the Drop/Approved indicator and the Post Enrollment Requirement Status.
________________________________________
Ian R Holmes
Senior Manager, SI-net Projects
University of Queensland
Brisbane QLD 4072
Australia
ph +617 3365 7125 / fax +617 3365 7545 / mob +61 409 058899
i.holmes@uq.edu.au
http://www.uq.edu.au/