This chapter discusses how to:
Set up grade category values.
Set up cumulative grade point average (GPA) values.
Set up special requirement usage values.
To set up grade category values, use Grade Category component (GRADE_CATEGORY).
The system uses grade category values on the Grading Scheme Table page and on the Requirement Line Item Detail page. This section discusses how to enter grade category values.
See Also
Setting Up Requirement Line Item Detail
Page Name |
Object Name |
Navigation |
Usage |
GRADE_CATEGORY |
Set Up SACR, Product Related, Student Records, Grading , Grade Category |
Establish new grade category prompt values that can be assigned in the Grading Scheme table and then used as field values for derived lists at the line item detail level. On the Requirement Line Item Detail page, if the line detail type is DLST, then one of the List Recall Mode field values is Grade Category. |
To set up grade category tables, use the Grade Category component (GRADE_CATEGORY).
Access the Grade Category Table page.
Important! Set up one grade category for every setID at your institution. For every table and effective-dated row that you create, include a grade category of None. Because Grade Category is a required field in the Grading Scheme table, you can use a field value of None in the Grading Scheme table for those grades that do not need a particular value.
Grade Category |
Enter the grade category that will become a prompt value on the Line Item Detail page and on any Student Record pages that contain this field. Because values are effective-dated, only those values that are valid as of the effective date are included in any prompting action. |
Description |
Enter the grade category description that will appear when a field is prompted for field values. The system populates the grade category description by default. However, you can change this value. All alphanumeric characters are valid. Clearly describe the grade category value. For example, you might want to describe a grade category of TXFR as Transfer Pass. In that case, the prompt value appears as Transfer Pass. |
At PSUNV, the total number of pass grades that can be counted toward a bachelor's degree is limited to 24 units. In addition, the total number of pass grades that can be transferred from a community college toward a bachelor's degree is limited to 6 units. A total of 24 pass units is allowed, but only 6 or fewer of those units can be from another institution.
To establish this limit on pass grades, you create two grade categories in the Grade Category table: P for pass and TP for transfer pass.
In Academic Advisement, you next create a requirement that is a global limit. It points to all courses on a student's transcript with a grade that has a grade category of P combined with TP (line detail type of DLST with a list recall mode of Grade Category = P U line detail type of DLST with a list recall mode of Grade Category = TP) on the Requirement Line Item Detail page. The limit allows a maximum of 24 units.
You then create a second requirement that is also a global limit, which points to all courses on a student's transcript with a grade that has a grade category of TP (line detail type of DLST with list recall mode of Grade Category = TP). This second requirement allows a maximum of 6 units. Any courses over the limit of allowed credits are not counted toward the degree.
Finally, you attach these two requirements to a requirement group. Because global limits go into effect as soon as the advisement engine encounters them, the limits should be at the highest level possible, preferably at the career level. Because career-level requirement groups are processed first, any global limit requirements that are attached at that level apply to the entire audit.
To set up cumulative GPA values, use the Cum. Grade Point Average component (CUMULTV_GPA).
This section discusses how to enter cumulative GPA values.
Access the Cum. Grade Pt. Average Table page.
Academic Institution |
Each cumulative GPA prompt value is associated with only one academic institution. This field is used for prompting, not for analysis. |
Cumulative GPA |
Enter the cumulative GPA that is a prompt value for preconditions or conditions of Cumulative Grade Point Average. Values are 0 through 9, with a maximum of five positions to the left of the decimal point and three positions to the right of the decimal point (for example, 12345.678). |
Description |
Enter the cumulative GPA description that will appear when a field is prompted for field values. By default, the system populates the Description column with the cumulative GPA value. However, you can change this value. All alphanumeric characters are valid. Clearly describe the cumulative GPA value. For example, you might want to describe a cumulative GPA of 2.0 as C average. In that case, the prompt value appears as C average. |
This section provides an overview of special requirement usage values and discusses how to set up special requirement usage values.
In most cases, you will probably run academic advising reports for your students. These reports track students' progress toward graduation, based on their career, program, plan, subplan, and requirement term data.
However, there may be instances when you want to evaluate a group of students based on a different set of criteria. Perhaps you want to evaluate the semester grade point average and academic load for all students in a student group called Athlete. Or perhaps you want to evaluate the grade point average of coursework in Accounting 1a and Accounting 2a for all prebusiness majors, to identify those with high grades in these areas and to inquire if they are interested in pursuing a degree in the accounting program. You can do this by creating special academic requirement groups that reference a user-defined requirement usage. The system does not include academic requirement groups with a special requirement usage in general advising reports; the special requirement groups are used only by specially designed transcript type reports that you configure.
Note. The system can process of a maximum of 30 special requirement groups that the system can process for a single report request. In addition, for special usage requirement groups, the system does not reference the career, program, plan, subplan, and precondition fields to determine which requirement groups apply to each student. Therefore, when creating special usage requirement groups, keep in mind that the system will attempt to apply all requirement groups with the special usage that you define to all students in the batch. If the number of active academic requirement groups with the special usage exceeds 30, the process will fail.
To set up special usage values:
Use the Requirement Usage page to define a special usage value.
All user-defined usage values must be 4 characters (for example, ACCT). The first and last characters cannot be spaces. Usage values that are delivered with the system are 3 characters (for example, STD and ADV).
Use the Requirement Group page to create an academic requirement group, which may reference one or more academic requirements, and specify the special usage value in the Usage field.
You can assign usage values at the requirement group level only.
Use the Basic Data page to create a transcript type that references the special usage value.
Select the Special Advising Report check box and enter the special usage in the Requirement Usage field.
Run the report.
To run the report for a small group of students by ID, on the Request Header page, specify the transcript type that you defined in step 3 and enter all IDs on the Request Detail page.
To run the report for a large group of students by parameters, on the Transcript request page, specify the transcript type that you defined in step 3 and enter the parameters that capture your target population.
See Also
Setting Up Special Requirement Usage Values
Defining Transcript Type Basic Data
Understanding Individual Transcript Requests
Creating Batch Transcript Requests
Page Name |
Object Name |
Navigation |
Usage |
RQRMNT_USEAGE |
Academic Advising, Academic Requirements, Define Requirement Usages |
Create special usage field values for generating alternate report formats. |
Access the Requirement Usage page.
Note. If the requirement usage is a delivered system value, No Special Formatting appears on this page. Delivered requirement usages result in a transcript that includes an advising report. If the requirement usage results in a special advising report as selected on the Basic Data page, Special Report Format appears on this page.
Effective Date |
Enter an effective date for this requirement usage. The effective date defines when the status that you select is valid. (If any of the requirement usage information changes, you should add a new effective-dated row.) When you create an academic requirement group that references this requirement usage, the effective date of the requirement usage must be less than or equal to the effective date of the academic requirement group. |
Status |
Active: Select to add a new requirement usage. Inactive: Select only if your institution will no longer use this requirement usage. If any of the requirement group information changes, you should add a new effective-dated row. Values for this field are delivered with the system as translate values. Do not modify these values in any way. Any modifications to these values will require a substantial programming effort. |
Description, Short Description, and Long Description |
Enter a description to use as a search key and to appear in prompts for requirement usage values. The description should accurately describe the requirement usage, so that the label is meaningful as a search key. For example, a description of Phi Beta Kappa helps to identify this requirement. The short description appears only on this page. The long description appears on the advising report Note. Once you have established a requirement usage, a maximum of 30 requirement groups that are flagged with this usage are pulled into audits with this usage specified as part of the transcript type. |