Friday Mar 02, 2012

Issue: Prerequisites Not Working

Here I present another issue that has been bothering implementations at universities with regards to enrollment.


Symptoms

Students are receiving a 'Prerequisites not Met' error when attempting to enroll in a class where the prerequisite class was taken in an earlier session within the same term.

Cause

The application does not currently support enrollment requisites for classes taken within the same term but different sessions.

Solution

The accepted workaround for this issue is to create an enrollment requirement group with two detail lines using an OR connector. The first line is set up as a pre-requisite and the second line as a co-requisite for the course. With this setup a student enrolled in the prerequisite course in an earlier session will be able to use that course to meet the corequisite line of the requirement and enroll in the later course.

If you wish to ensure that the prerequisite couse has already been completed earlier in the session, on the detail parameters of the co-requisite, set minimum units to 3 (or whatever the earned units for the course should be) and set the "Exclude In-Progress Credit". This will ensure that the prerequisite class taken in an earlier session will have been completed prior to enrollment in the later class.

There is an enhancement request on file requesting the ability to set up prerequisites within the same term, different sessions against the Report ID#72545000 which can be accessed from Metalink.

Monday Feb 27, 2012

Enrollment Drop Problems

There have been a few common issues in the application pertaining to functional aspects. These issues keep coming to me for resolution / guidance. So, for common goal, I am putting some perspectives and word of caution while performing certain operations. Hope this helps you.

Multiple Enrollment Drop Problems Caused by Class Association Numbering

The Scenario / Symptom

  1. A course has only one component and can be enrolled multiple times within the same term. Class sections are created for the course using the default class association number of '1' for each section. Customer enrolls a student for two or more sections in the same term. Customer then processes a drop request for one of the sections. The enrollment engine drops ALL sections.
  2. Class sections are created for a course using the default class association number of '1' for each section. The institute allows students to drop and add new sections or swap to new sections during the drop/retain period. In a case where a drop/add action or a swap was done to a different section during the drop retain period and the new section was later dropped, the enrollment engine will update all the dropped sections with the same drop date.
  3. Dynamic dated classes are created using the same class association number for each section. When students attempt to add or drop some sections, the add, drop or swap action is not processing according to the dynamic dates calculated for the particular section.

Cause

Unrelated sections of the class were scheduled using the same using the same Associated Class number on the Schedule of Classes

Recommended Solution

Whenever you have a class with only one component, each section of the class should have a unique class association number. The class association number ties together the components that make up one course (i.e., lecture and lab). If you have multiple sections of a class all using the same class association number, the enrollment engine treats those all as one class--when you drop one, you drop out of all of the classes with the same class association number. That is how students get dropped out of the lab when they drop the lecture--both components are defined in separate sections, but bound together by the class association number.

Using unique class association numbers is especially important when a student is allowed to enroll in more than one section of the class for a term, is allowed to swap between sections of the course during the drop/retain period, or if the customer is using Dynamic Date processing.

Using unique class association numbers is especially important when a student is allowed to enroll in more than one section of the class for a term, is allowed to swap between sections of the course during the drop/retain period, or if the customer is using Dynamic Date processing.

To implement the solution:

  • Navigate to Curriculum Management > Schedule of Classes > Maintain Schedule of Classes.
  • In the Associated Class field, select a unique association number for each newly created stand alone section.
  • Continue scheduling the class sections and save.

Note: If students are already enrolled in the section and you wish to change the class association number, students must first be dropped from the class, the association number changed, and the students added back into the class.

 

Hope this helps some of us implementing the solution... :-)

All the best 

 

 

About

Mohit Satraj Phogat
Author: Mohit Phogat

This site focuses on Oracle's offerings to higher education in the Indian region. It intends to cover news, reviews, guides, how-to articles, descriptive videos, and podcasts on the trends which should be helpful to customers, prospects and developer community alike.

Follow me @

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today