This process updates the database |
||
Subsystem |
Student Finance |
|
Purpose |
To produce extract records containing the necessary information for printing of HECS liability notices. This job is designed to meet the government requirement to provide written notification to students of their HECS liability for a teaching period. |
|
Normally Run By |
A student finance specialist via Job Scheduler |
|
Anticipated Frequency |
As required for printing of HECS Liability Notices. The government requirement is to provide these notices within 30 days after the teaching period census date. |
|
Parameter Sample |
||
Report | HECS Liability Notice Extract Exception report | |
Report sample |
Extract |
This job uses the generic 'extract table' structure to store extracted data which can be used for the production of HECS liability notices. A program which uses the extracted data (and data from other Callista tables if required) to produce HECS notices can be custom built by the institution. The program accesses the extracted data via views specifically created for the HECS Notice of Liability Extract process. Extract Creation Processes describes this methodology. Technical detail regarding HECS Notice of Liability extracts is provided in release Technical Documentation. Details of the data available in HECS liability notice views is available in HECS Notice of Liability Extract - View Details Records can be selected for multiple students or for a single student. Primary record selection is dependent on which of certain parameters are used. Records are extracted only for student course attempts with a relevant HECS assessment, who satisfy the chosen job parameters. The process:
Record Extraction The extract process creates a record in the S_EXTRACT table which identifies the particular extract job run. It creates corresponding HECS Liability Notice detail records in the S_EXTRACT_RECORD table.
|
Update |
In a successful extract:
and, unless the run is a test extraction (set by parameter)
For further information, refer to the Correspondence subsystem. |
|
|
HECS Notice of Liability extract recordsTwelve different types of record can be held for each individual HECS liability notice. These records are:
See view details documentation for more detail. |
Run |
MethodThis job can only be run in batch mode, through the Job Control & Scheduling subsystem. Timing considerationsThe job is run after the census date of the teaching period and after the Fee Assessment and Process Person Payment Schedule jobs (FINJ3500 and FINJ6111) have been run, to ensure processing of any late changes affecting student fee assessments. Due regard should be paid to timing this job with respect to the selection of the enrolment statistics snapshot to be used for government reporting, allowing sufficient lead time for correction of student enrolments. The date and time of extract is stored with the extracted records. Viewing the extracted dataData is usually processed by the institution's custom built statement creation/printing job. Data can be viewed in the S_EXTRACT and S_EXTRACT_RECORD tables, or in a more useable form in the views HECS_LBLTY_EXTRACT_V and HECS_LBLTY_RECORD_V, using an ad-hoc query tool. |
Selection of parameters for this job depends on the particular circumstances in which it is being run. It is most likely to be run for:
NOTES: The % symbol indicates that the parameter is not considered for processing. |
||
Request Person ID |
mandatory - the ID number of the person requesting the job run. Defaults to the current user, but any valid person ID can be entered. |
|
Log Creation Date | optional - used only to reproduce the exception report from a previous run of the job. Previous runs are displayed in the list of values. Where this parameter is used, no other parameters are considered. | |
Correspondence Type |
mandatory - the correspondence type against which a correspondence item is to be created and recorded for student course attempts with records in the extract. To use this feature, a suitable correspondence type (or types) (e.g. HECSNOTICE) should exist (see CORF2110) and be linked to the output from this job. In addition, only student course attempts with a correspondence category containing this correspondence type will be considered. It is recommended that the correspondence type be associated with all correspondence categories. |
|
Fee Assessment Period |
mandatory - used to limit the selection of records to those with a HECS assessment within the specified fee period. The default is the current fee assessment period. |
|
Fee Type |
optional - the code of a single fee type can be selected or entered. Institutions using only one 'HECS' fee type can either select that fee type or leave as the default value (%). Institutions which have more than one fee type mapped to the system fee type HECS may select a single fee type from the LOV or use the default. The default is all fee types. |
|
Fee Category |
optional - the code of a single fee category can be selected or entered. Particularly useful for institutions which use different fee categories for different cohorts of students. Where an institution has a number of non HECS liable fee categories, processing can be reduced by running this job for only those categories which do have a HECS fee type. The default is all fee categories. |
|
HECS Payment Option |
optional - a single HECS payment option can be selected. Allows this job to be run separately for each HECS option. Comparison is made to students' course attempt HECS options current at the census date associated with the fee period. The default is all HECS payment options. |
|
Course Code |
optional - the code of a single course can be entered. This could be used, for example, where a change to a course has affected the HECS assessments of students enrolled in it, and there is a need to re-issue for that particular course. The default is all courses. |
|
Person ID |
optional - a single person ID can be entered. This is typically used where a HECS notice is being produced for a single student, either as a replacement or because the student's HECS assessment has changed. |
|
Person ID Group |
optional - a single person ID group can be selected. This is typically used where a HECS notice is being produced for a small number of students, either as a replacement or because the students' HECS assessment has changed. It can also be used to process an ID group produced by a previous run of this job (ie. to reprocess students reported as exceptions in a previous run). |
|
Institution |
mandatory - a single institution, usually the default 'local' institution, must be specified (along with the institution address type parameter) in order to determine the institution address for inclusion in the extract. |
|
Institution Address Type |
mandatory - a single address type to enable, in conjunction with the Institution parameter, an address to be determined for inclusion in the extract. This might be used by a HECS liability notice printing program to record a return address on sponsor statements. |
|
Date of Issue |
optional - a date of issue (format dd/mm/yyyy) of HECS liability notices can be recorded and may be particularly useful where the date of issue differs from the run date of this job. If not specified, the date of issue is automatically set to the current system date. |
|
Location Code |
optional - a single location (usually campus) can be specified. This parameter might be used by institutions with administration decentralised across multiple campuses, allowing each campus to produce its own set of notices. |
|
Comment |
optional - a comment of up to 60 characters can be recorded for inclusion in the extract. The comment could be included on printed HECS liability notices. |
|
Test Extraction |
must be set to:
|
Producing HECS Liability Notices |
Producing HECS Liability NoticesThe extract data supplied is envisaged as sufficiently comprehensive to meet the varied needs of different institutions. Licensees will be responsible for the programming tasks involved in extracting data and producing HECS Notices of Liability from the records stored in the extract table, S_EXTRACT_RECORD via the HECS_LBLTY_RECORD_V view. HECS notices can thus be tailored to an individual institution's formatting and content requirements. Some matters for consideration are:
|
Exception Report |
The exception report lists all errors and warnings generated by this job. Records that generate errors or warnings are not written to the extract. A new Person ID Group is created containing the Person ID numbers of records that generated errors or warnings. The ID Group can be used as a parameter to rerun this job for the unprocessed records. |
|
Run details |
This exception report is produced
Refer to the Job Control and Scheduling subsystem for details of scheduling and running batch and online jobs NoteIf exceptions are recorded for more than one person then the system creates a new person_id group containing student_id's of records with data errors. This person_id group is recorded against the correspondence item instead. |
|
Report parameters |
Log Creation DatePermits exception reports produced from previous runs of this job to be reproduced. No further report parameters are required when this parameter is specified. This is a log created by a previous run for FINJ6190 |
Last Modified on 04 October 2001