Note: This proposal is subject to change due to the forthcoming Oracle PeopleSoft system upgrade from version 8.0 to 8.9.
At Cornell, each college determines the Academic Level of a student differently. In SIS, several hundred students are manually “re-termed” each year based on college requirements. For example, a student currently a Junior 2nd semester might meet the college standard to be a Senior 1st semester and would be “re-termed” in SIS.
This “re-terming” is saved from semester to semester and is incremented by one “level” each semester. For example, if a student were “re-termed” to be a Junior 2nd semester during the fall semester, they would automatically become a Senior 1st semester for the spring semester. This happensishis when the student registers for the spring term.
As delivered, PeopleSoft Student Records provides two possibilities for automatically incrementing Academic Level. It could be done based on the number of terms completed or the number of units completed.
Once the Academic Level is automatically incremented, an administrative user (i.e., college registrar) could manually adjust it. But, when the Term Activation process is run for the next term, the Academic Level would be re-calculated based either on the number of terms or units completed, not based on the Level in the prior term. If the option is chosen to increment the Level based on term, PeopleSoft includes all terms (i.e., summer and/or winter and not just fall and spring.) Students would need to be appropriately “retermed” for each term until they graduate.
The Term Activation process provides the functionality to “turn off” the ability to automatically increment Academic Level. But, it would be turned off for all students, not just those whose Levels had been manually adjusted. A manual Academic Level process would need to be used.
From SR8 To Be 3.7 Term Activate Students