1. Post Enrollment Requisite Checking (PERC)

2. Your Presenters
Ramona Breuer, Student Records Business Analyst in Campus Solutions
Ray Pospisil, Manager of Academic Reporting, University of North Dakota

3. Overview
Post Enrollment Requisite Checking (PERC) is a process that is designed to run after grades are posted to check if students still meet the enrollment requirements for the classes they are registered in for the subsequent semester.

4. Agenda/Contents Enrollment Requirement Roster
Print Enrollment Requirement Rosters
Batch Processing – PERC process/Drop Requests
Communication Generation
Tips and Tricks Learned by UND
Questions

5. Enrollment Requirement Roster
Main Menu>Curriculum Management>Enrollment Requirements>Post Enroll Req Checking>Enrollment Requirement Roster
View students’ enrollment requirement status in a roster format
Ability to run PERC and process drops directly from the enrollment requirement roster

6. View of the roster prior to running the PERC process.
Two display views:
Summary (view on slide)
Detailed
Filter options are provided to assist in identifying various types of student enrollment status.
The ‘notify selected students’ function is available to send a selected student or students an .

7. A detail view of how the student was conditionally satisfied for enrollment into the class.

8. RESULTS: View after the PERC process has run.
‘Drop Request’ indicator is set after the process is run.
For non-compliant students, you have the option in the ‘Drop/Approved Indicator’ column to choose ‘Approved’, if the student is given approval by the instructor or department.
Note that additional fields are now included on the roster.

9. In the ‘Post Enroll Req Status’ column, you will see one student was ‘Not Satisfied’. You may click on the link to see the detail information of why the student didn’t satisfy the requirement.

10. You may process the drops from the Enrollment Requirement Roster.
In the Process Status column you will see the result message of the enrollment action, and you may click on it to view the message.
Note that additional fields are accessible.
RESULTS:

11. You may add note types and free text notes here to document approvals or other important details.

14. Print Enrollment Requirement Rosters
Main Menu>Curriculum Management>Enrollment Requirements>Post Enroll Req Checking>Print Enrollment Req Roster
Allows you to print enrollment requirement rosters to distribute to departments
Ability to use pop select to identify groups of students to print

15. Selection Tool: Equation Engine, External File, and PS Query

18. Batch Processing for PERC
Main Menu>Curriculum Management>Enrollment Requirements>Post Enroll Req Checking>Run Post Enroll Requirement
Allows you to run PERC process on a batch of students at one time
You can use pop select to identify the population or you can identify the class numbers you would like to process or both

20. After the process completes, you may go back to the run control and click on the ‘Get/Refresh Last Request’ button, and it will give you the Enrollment Request ID link to block enroll where errors can be investigated, updated and rerun.

21. Batch Processing for Drop Requests
Main Menu>Curriculum Management>Enrollment Requirements>Post Enroll Req Checking>Process Drop Requests
Allows you to process drops in a batch process at one time
You can use pop select to identify the population or you can identify the class numbers you would like to process or both

23. After the batch drop process has completed, you may click on the ‘Get/Refresh Last Request’ button and you will see the Enrollment Request ID, which will show you the detail of the students and class numbers that were dropped.

24. Communication Generation
Oracle has delivered communications with the PERC functionality to let the student know they have been dropped for not meeting enrollment requirements. We currently do not have this set-up. If the Student Records User Group approves a Development Request, we will set up the communication to be used with this functionality.

25. Tips and Tricks Learned by UND
Why Batch?
Fall 2016
1985 sections with requisites
35327 enrollments checked
2225 enrollment requirement groups
258 failed (.73%), 408 conditional (1.15%)
141 dropped (0.4%)
Needles in a haystack

26. Procedure Registrar extracts PERC results for Colleges/Depts
Departments have until 5th day of classes to notify registrar of any drops – this is a department decision, nothing is automatic
Departments’ responsibility to notify students
Registrar enters drops via enrollment request, making sure to check to prevent drops of athletes on a Friday without the knowledge of Athletics, to prevent any inadvertant NCAA violations
Same deadline as for drops for non-attendance
Allows a few days for students to make adjustments

27. Process Registrar runs query to find sections with requisites
Registrar runs batch PERC process and verifies results using Block Enrollment
Next day (after reporting environment refresh), registrar
runs several queries and a SAS program to merge files, sends results to colleges/departments
(PERC results written to records beginning with SSCR_REQS)

28. Lessons learned during implementation
We had some “bad” ERGs – these sabotaged large chunks of the process – had to develop query edits to clean them all up
PER Checking generates enrollment request transactions that do not affect enrollment, but clutter the screen when you do an enrollment request search
Verifying PERC

29. Left to do
When initially developing the process, it was prudent to have multiple queries and a SAS program to merge the data – easier to troubleshoot, before PeopleTools upgrade
At this point the PERC results could probably be obtained using a single query
2015 ND HEUG

30. Questions?

31. Contacts Ramona Breuer Ray Pospisil
Student Records Business Analyst, Campus Solutions
Ray Pospisil
Manager of Academic Reporting
University of North Dakota

32. This presentation and all NDHEUG presentations will be available for download from the Conference site at