Purpose

To create and maintain a link between a fee liability and the set of courses constituting a course group, in order that only students in the courses specified should be considered for the fee liability

Subsystem

Student Finance

Structure

Two blocks

Fee Category Fee Liability (context)
Course Group Fee Trigger

Back navigation button:

• Maintain Fee Categories (FINF2800)

Image

Triggers are used by the fee assessment routine (FINJ3500, FINJ3001) to decide whether a fee applies for a particular course a student is studying, as discussed in the Specialist Overview. If a course trigger recorded against a fee liability matches a student course attempt, the student is eligible for assessment.

Three forms are used to record course triggers. FINF2222 is used to specify individual courses. The current form and FINF2220 (dealing with course types), allow a single trigger to operate for a particular grouping of a range of courses, as set up in the Course Structure and Planning subsystem.

This form matches course groups to fee liabilities. The courses (and versions thereof) which form a course group are determined by an institution according to its own administrative or academic requirements, and there is scope to set up groups relating specifically to the fees they attract. It is recommended that a specific course group type - for example, FEE-ASS - is established as a USERDEF type to distinguish fee-related groups. For details of course groups, see documentation for CRSF11D0, and for course group types, CRSF1180.

Course attributes. The form does not cater for different attributes of the courses in question, but only for the course versions making up a group. Where only particular attributes of the courses are to invoke fee assessment, this must be handled by setting up rates only for those attributes in the Define Fee Assessment Rates form, FINF2853. For example, in that form there may be just one rate, which applies for full time attendance type. Effectively, this prevents an assessment being made against the selected fee type for student course attempts with any other attendance type.

Deletion. Logical deletion, described below, allows for a trigger to be 'removed' from further use while still enabling transaction reversals to be made for those transactions that have already been created as a result of the trigger.

Example

There may be some courses that attract a fee for laboratory use. Course versions for these courses could be recorded against a course group, LAB-CRS, and this group assigned as a trigger to a liability with the fee type LAB-FEE.

The Fee Category Fee Liability block shows the fee liability (fee within a category in a fee period) and charge method for which triggers are recorded in the following block.

To logically delete triggers, select and delete the record as normal. No Save is necessary - confirmation is requested before an automatic logical deletion is performed. A deletion date is supplied by the system. 

• Only open course groups can be selected here.
• New versions of courses must be added to course groups in CRSF11D0 if it intended that they also act as triggers for the fee liability in question.
• The Creation Date of a record is automatically supplied by the system.
• Setting the 'Include deleted triggers' indicator allows the display of all triggers, including those that have been logically deleted, when the form is queried. It has NO effect on functionality in the fee assessment routine.