This process updates the database |
|
Student Finance |
|
Purpose |
This rollover process allows reference and operational fee data set up for one period to be 'reused' by recreating it in another. It depends on a previous calendar rollover that includes the rollover of all fee calendars. |
Normally Run By |
Student fees specialist |
Anticipated Frequency |
Once yearly. Alternatively, fee structures may be rolled over for several years in advance (normally with planned statuses). |
Update Process(es) |
A set of structural fee data is created for each year for which a rollover is undertaken. |
Parameter Sample |
|
Related/Dependent Jobs |
Rollover
Calendar Instance (CALF0320) - process initiated from form. |
Update Process |
This
process 'recreates' in a future year the structural data held against
financial and fee calendars in an earlier year. The range of the data
'rolled over' is determined by parameter. For
a full rollover, the following data held against a source fee period
would be recreated in the target fee period of the required future year
:
and
all related data:
Sponsorship
and contract data are not rolled over. Only
active fee types, fee categories and fee liabilities are rolled over.
Data that has been closed or logically deleted is not rolled over. Data can be rolled over into a PLANNED state or an ACTIVE state. |
Run Details |
A
separate rollover is required for the fee data in each fee period. For
instance, if first semester, second semester, summer semester and full-year
fee periods have been created in 1999, each in turn must be rolled into
corresponding fee periods for the year 2000. Method
The
rollover of an academic calendar in CALF0320 should take all financial
and fee calendars with it. The status of these calendars will need to
be changed from PLANNED to ACTIVE if it is required to
roll over fee data into an active state.
(For
fee data rolled over into a planned state, the creation of account codes
can wait until the fee data is about to be made active.)
TimingIt
is expected that this job will be run on a yearly basis. Calendar and
structural data can be rolled over for several years ahead. OutcomesThe
Fee Structure Rollover Report (FINR2A10) gives details of the success or otherwise of the
rollover process. Two
reports display detailed structural fee data:
|
Job Parameters |
The
first four parameters specify the range of data to be rolled over. The
default is to roll over all active fee data. This is the recommended
option. However, where required, segments of the structure can be rolled
independently:
For
the HECS example given, this would roll over only those categories of
which HECS is a liability, and only the HECS liabilities within those
categories.
The
fee structure to be rolled over is indicated by fee period, as selected
in the Rollover Source Calendar Instance parameter field. The
target fee period (which should be the corresponding fee period in a
future year) is selected in the Rollover Destination Calendar Instance
field. For example, FEE-SEM1 in 1999 would typically be rolled
into FEE-SEM1 in 2000. The final three fields allow for the selection of the intended statuses of fee types, fee categories and fee liabilities in the destination fee period. A choice can be made to rollover this data into an institution defined equivalent of the system fee structure status ACTIVE or PLANNED. Using the default '% ALL' option will set the target status to whatever status was defined for the source data. |
Last Modified on 11
March 2002