Purpose

To report on the results of the Fee Structure Rollover process.

SubSystem

Finance

Run Details

Run this report after a run of the Rollover Fee Data job, FINJ2A00, to discover the outcomes of the rollover process for that particular run.

As a result of the information given in this report, changes will probably be made to the rollover destination Calendars and structures. The cycle of running the job and report in tandem, making changes and then re-running both will continue until this report indicates that all required data has been rolled over.

It is expected that the Fee Structure Rollover process will take place on a yearly basis, though it may be done semester by semester if required. Calendar and structural data can be rolled over for several years ahead.

The Fee Structure Rollover Report block contains:

Parameters Tab

• Creation Date

Rules/Notes:

For information about System (or control) parameters, see All About Standard Reports.

There is only one report parameter. Select a Creation Date - this indicates the date on which the required run of the rollover job FINJ2A00 occurred. Normally the most recent date will be selected.

Rules/Notes:

Fee Structure Rollover Report:

The report is structured to show rollover details level by level in the order FTCI (Fee Types), FCCI (Fee Categories) and then FCFL (Fee Liabilities).

For each Fee Type, Fee Category and Fee Liability in the source Fee Period, messages give details of the outcome of the rollover. Key words in the messages are capitalised for easy scanning.

• A distinction is made between information successfully rolled in the reported run of FINJ2A00, and that rolled in earlier runs. In the first case, a typical message would be 'Fee Payment Schedules HAVE been rolled over', while the second case is indicated by a message such as 'Fee Encumbrances have ALREADY been rolled over'.
• The message 'Account Financial Period Calendar has NOT already been rolled over' indicates that the relationship between a Financial Calendar and an Account Code has not been established in the destination Fee Period (refer to rollover details in FINJ2A00).
• A message such as 'Parent Fee Type Calendar Instance does not exist' at one level indicates that the corresponding data at a different level has not been rolled over for some reason. For instance, for this message, reported against a Fee Liability, a corresponding message at FTCI level could indicate that the Fee Type is closed.
• A message 'Calendar Instance must be ACTIVE' which includes the line 'TABLE: chg_method_apportion' indicates that Load Calendar Instances associated with destination Fee Periods must be active before related data can be rolled.

The report displays any problems with or failures of Funding Source or Concession Type fee data for ADVSTND and VET Fee Types, logged during the rollover process.