This report is constantly being updated

Subsystem

Calendar

Purpose

This report is used to identify potential calendar related problems that cannot be validated through the various forms

Normally Run By

Calendar specialist 

Anticipated Frequency

As needed 

Reports

Calendar Quality Check Report 

Report Sample

Parameter Sample

Related/Dependent Jobs

 N/A

Run Details

Refer to the Job Control and Scheduling subsystem for details on scheduling and running batch jobs.

Job Parameters

The parameters in this job are used to refine the set of calendars reported. 

Report(s)

Calendar Quality Check Report 

This job produces an exception report of errors encountered.

Load Calendar Checks

Report Output Message

Explanation

Action

Load calendars can only have other load calendars as subordinates (sub cal type)

Load calendars should not have child calendar instances of any type other than load calendar types.

Delete incorrect child calendar instances in CALF0330.

Load calendar should only be a subordinate to a single academic calendar instance

A load calendar may have only one academic calendar type superior. (It may have other superior calendars of other types, e.g. progression type)

Delete invalid superior calendars in CALF0330

Load calendar instance must have one and only one load effective date alias instance

Check for instance/s of the Load Effective date alias in the Maintain Date Alias Instances form (CALF0512) and either:

Note: The date alias to use as the Load Effective date alias must first be defined in the Enrolment Calendar Configuration form (ENRF01F0).

Linked to a teaching calendar type that has no instance associated with the academic period (teach cal type)

This message is displayed where the teaching calendar is not linked to the same academic period as the load calendar. Consequently, load calculations will fail because the appropriate teaching calendar instance for the load calendar cannot be determined.

Check that the correct teaching calendar type is mapped to the load calendar instance in the Maintain Load Calendar Structure form (ENRF01K0).

If this is correct, check that both the load and teaching calendar instances have the correct parent academic calendars.

Teaching calendar type has only one instance associated with the academic calendar; second percentage is not required (teach cal type)

A second percentage load apportion is only required if instances of the teaching calendar type span two academic calendars and therefore another instance of the context load calendar. A second percentage is only recorded if it differs from the first percentage.

Delete the second percentage from the load calendar instance teaching calendar type in ENRF01K0.

Attendance type has no attendance type load detail and therefore cannot be derived within the load calendar (attendance type)

This message is displayed where at least one course attendance type has not been defined for at least one load calendar type. For example: the enrolment load range for attendance type PT is defined for load calendars 1 and 2, but not calendar 3.

Check that all attendance type load ranges have been defined in the Maintain Attendance Types form (CRSF1170).

There is no gap in the attendance type load ranges for the load calendar

When defining attendance type load ranges for a specified load calendar type, some load values may not have had an attendance type defined.

Check all attendance type definitions within the load calendar type for gaps in CRSF1170. Modify as appropriate.

Enrolment calendar parent is within a different academic period

A load calendar can only contribute to enrolment calendars that are related to the same academic parent calendar.

Correct the calendar relationships using form CALF0330.

Warning: Load calendar parent is within a different academic period

An aggregated load calendar (the parent calendar) may be related to a different academic year than this subordinate load calendar.

The relationships can be checked and modified if required.

Load calendar cannot have both a default load structure and subordinate load calendar(s).

A load calendar can be either direct or aggregated, but not both.

Correct the calendar relationships using CALF0330.

Load calendars can only be aggregated to one level.

There can be only a single layer below an aggregated load calendar.

Correct the calendar relationships using CALF0330.

Enrolment Calendar Checks

Report Output Message

Explanation

Action

Enrolment calendars should only have superiors of Academic and Admission calendars (superior cal category)

Enrolment calendars may have academic, admission, holiday and user defined calendars as superior calendars.

Delete the invalid superior calendar and any other parent calendars not required in CALF0330

Enrolment calendars can only have load subordinates (enrolment cal type)

Invalid subordinate calendars, with the exception of user defined calendars, are not allowed.

Delete the invalid subordinate calendar in CALF0330

Subordinate load calendar subordinate is not within same academic calendar

A load calendar can only contribute to enrolment calendars that are related to the same academic parent calendar.

Correct the calendar relationships using form CALF0330.

Enrolment calendars should have at least one load subordinate for enrolment checking / calculations.

Derivation of attendance type and enrolment checking depends on the existence of a subordinate load calendar.

Create the required relationship between the enrolment and load calendar in CALF0330.

Load is being double counted due to relationships to a load calendar and one of its subordinates.

An enrolment calendar has been incorrectly linked to both an aggregated load calendar and one of the subordinate load calendars. This results in load being counted for each calendar.

Delete the relationships between the enrolment and one of the load calendars in CALF0330.

Admission Calendar Checks

Report Output Message

Explanation

Action

Admission calendars should have only one superior calendar of a particular Academic calendar type

Admission processes are always in the context of a particular academic period.

Delete invalid parent academic calendars in CALF0330.

Admission calendars should have at least one superior Teaching calendar

Parent teaching calendar/s are required if units are to be specified in applications. For example: non-award single unit.

Note: only those teaching periods relevant to the context admission period can be mapped.

Admission calendars should be defined for at least one Admission category

Admission calendars cannot be utilised, and therefore admission applications cannot be processed, unless the admission calendar is mapped to one or more admission categories.

Ensure that each admission calendar is mapped to appropriate admission categories in the Maintain Admission Period Calendars (ADMF2M61).

Admission calendar does not have an initialisation date

If the admission process definition for the admission category includes the steps RECONSIDER and/or DEFER, then the system date alias 'Initialise Adm Period Date Alias' must be defined in associated admission calendars. This is the date on which background processing for an admission period is run. For example: Process Admission Application Deferrals (ADMJ3811) and Initialise Course Offering Admission for Students with Approved Deferment (ADMJ3812).

Note: The date alias to use as the 'Initialise Adm Period Date Alias' must first be defined in the Maintain Admission Calendar Configuration form (ADMF02R0).

Admission calendar does not have an encumbrance checking date

If the admission process definition for the admission category includes the encumbrance checking step, then the system date alias 'Encumbrance Check Date Alias' must be defined in associated admission calendars.

Note: The date alias to use as the 'Encumbrance Check Date Alias' must first be defined in ADMF02R0.

Admission calendar does not have a course start date

This date alias is used to derive the course attempt commencement in the Record Enrolments form (ENRF3000). If the 'Course Start Date Alias' does not exist in the admission period, the system uses the course commencement date recorded for the context admission period, or the system date if the date of enrolment is later than the academic period course commencement date.

Note: The date alias to use as the 'Course Start Date Alias' must first be defined in ADMF02R0.

Admission calendar has more than one application due date that is not mapped to an override

The application due date is a user defined date alias mapped to 'Due Date Alias' in ADMF02R0. There is typically at least one instance of the date alias in each admission calendar. The first occurring due date is the default application due date for all admission applications associated with the admission period/admission category. The default date may be overridden in the Maintain Admission Period Date Overrides (ADMF2M62). Due date overrides are other instances of the same date alias in the same admission calendar. This message is displayed where there is at least one instance of the due date alias in the admission period (other than the default date alias) that is not being used as an override.

Note: some instances may have been created in advance as possible overrides, these may not need to be deleted.

Admission calendar has more than one application final date that is not mapped to an override

The application final date is a user defined date alias mapped to 'Final Date Alias' in ADMF02R0. There is typically at least one instance of the date alias in each admission calendar. The first occurring final date is the default application final date for all admission applications associated with the admission period/admission category. The default date may be overridden in ADMF2M62. Final date overrides are other instances of the same date alias in the same admission calendar. This message is displayed where there is at least one instance of the final date alias in the admission period (other than the default date alias) that is not being used as an override.

Note: some instances may have been created in advance as possible overrides, these may not need to be deleted.

Admission calendar has more than one application offer response date that is not mapped to an override

The application offer response date is a user defined date alias mapped to 'Offer Response Date Alias' in ADMF02R0. There is typically at least one instance of the date alias in each admission calendar. The first occurring offer response date is the default application offer response date for all admission applications associated with the admission period/admission category. The default date may be overridden in ADMF2M62. Offer response date overrides are other instances of the same date alias in the same admission calendar. This message is displayed where there is at least one instance of the offer response date alias in the admission period (other than the default date alias) that is not being used as an override.

Note: some instances may have been created in advance as possible overrides, these may not need to be deleted.

Admission calendars should have one superior Academic calendar

See first admission calendar check item.

Delete invalid parent academic calendars in CALF0330.

Teaching Calendar Checks

Report Output Message

Explanation

Action

Teaching calendars should normally have only superiors of Academic, Examination or Assessment calendars (cal cat)

Valid superior calendars for teaching calendars are academic, assessment, exam, progression, holiday and user defined calendars. Fee calendars are no longer valid superiors.

Delete the invalid superior calendar in CALF0330

Teaching calendars must have at least one "Census Date" alias instance within the bounds of the academic calendar start/end dates

Note: The date alias to use as the Load Effective date alias must first be defined in the Enrolment Calendar Configuration form (ENRF01F0).

Total load apportionment for the teaching calendar instance does not total 100%

This message can appear where straddling teaching periods are rolled over and a load calendar does not exist for the last apportionment. For example: the academic year 1998 is rolled over to 1999. A new instance of the S1-E1 teaching period is created (1999 - 2000). The calendar quality check would detect that only two thirds of the apportionment is available (load calendar 1 (1999) and load calendar 2 (1999)). This problem can be resolved by creating an instance of load calendar 1 (2000).

Note: as load apportionment is defined at the teaching calendar type level, rather than the instance level, it is necessary to identify which teaching calendar instances relate to which load calendar instances.

All administrative unit statuses used within teaching calendar instances must be linked to the apportionment load calendar instances via the "administrative unit status load" structure (administrative unit status)

For example: the administrative unit status WD-LATE is mapped to the discontinuation date alias WDN-LATE. This date alias has an instance in the teaching calendar SEM-1 (1998). Teaching calendar type SEM-1 is linked to load calendar 1 (1998) in ENRF01K0. However, the administrative unit status WD-LATE has not been recorded in the Administrative Unit Status Load block of ENRF01K0 for the load calendar/teaching calendar load apportionment.

First check that the administrative unit statuses are defined within the discontinuation date criteria in the Maintain Unit Discontinuation Date Criteria form (ENRF0170)

Check in ENRF01K0 that all 'used' administrative unit statuses are defined in the context of each load calendar/teaching calendar load apportion. If not, create appropriate administrative unit status load records.

Teaching calendars should only have Admission subordinate calendars (teach cal type)

Delete the invalid subordinate calendar in CALF0330

Teaching calendars should have at least one Admission subordinate calendar (teach cal type)

Add a valid subordinate calendar in CALF0330

Another teaching calendar instance commencing in the academic period uses the same alternate code

This duplication may cause unexpected errors in enrolment functionality.

Correct the duplicate code using CALF0220.

Progression Calendar Checks

Report Output Message

Explanation

Action

Progression calendars should only have academic superiors

Restrictions on relationships in CALF0330 should prevent this error, but this provides an additional check to identify invalid relationships.

Delete the invalid superior calendar in CALF0330

Progression calendars should only have teaching or load subordinates

Restrictions on relationships in CALF0330 should prevent this error, but this provides an additional check to identify invalid relationships.

Delete the invalid subordinate calendar in CALF0330

Linked to a teaching calendar type that isn't offered within the academic period

Only teaching periods that are related to the same parent academic calendar should contribute to a progression calendar.

Delete the invalid subordinate teaching calendar in CALF0330

Linked to a load calendar type that isn't offered within the academic period

The link used to evaluate attendance type for a progression period must use a load calendar that is related to the same parent academic calendar.

Delete the invalid subordinate calendar in CALF0330 and where necessary link the progression calendar to another load calendar (with the same parent academic calendar).

Progression calendars should only have a single subordinate load calendar

The progression - load calendar link allows the derivation of attendance type for a progression period (may be required for some progression rules and outcomes).

Delete the invalid subordinate load calendars in CALF0330, leaving a link to only one load calendar.

Research Calendar Checks

Report Output Message

Explanation

Action

Research effective dates should only exist in Teaching calendars (date alias & cal type)

Instances of the research effective start and end date aliases in calendars other than teaching calendars serve no purpose. These date aliases identify the calendar as a research teaching period.

Delete instances of the research effective start or end date aliases that exist in calendars other than teaching.
The user defined date aliases are mapped to each of these in RESF31G0.

There should only be a single start/end effective dates in Teaching calendar

The research effective start/end date aliases are required for research calculations (EFTSU and effective full time days). There can only be 1 instance of each date in a single calendar.

Delete the additional instance of the research effective start/end date for the teaching calendar, using CALF0511.

Research effective dates are out of order in Teaching calendar.

The research effective end date alias instance is an earlier date than the effective start date alias instance for the same teaching calendar (or vice versa).

Correct the value of the date alias instances in CALF0511.

Only Teaching periods with single census dates can be used as research Teaching calendars.

A teaching period that includes more than one census date cannot be a research teaching period, because of the impact on EFTSU calculation.

Remove the research date aliases from this calendar in CALF0512.

Multiple research teaching periods are linked to a single load calendar (calendar type)

A load calendar can only be subordinate to one research teaching calendar. This error will impact on load and EFTSU calculation for research students.

Correct the research teaching calendar/load calendar relationships in form CALF0330.

Warning: Research unit offered within normal teaching period. Standard EFTSU calculations will be used.

EFTSU for a research unit can be calculated in the standard way or using a specialised calculation for research, based on the configuration of the teaching period.

This may require no action, where the standard calculation is intended. Where the research EFTSU calculation is required, ensure the teaching period is configured using the research effective start/end dates.

Research percentage does not total 100% for the academic year.

The load research percentage (recorded against load calendars) must total 100% for an academic year to ensure research EFTSU calculations function correctly

Check the Load Research % value allocated to the load calendars (in the Subordinate Calendars block of CALF0330) and adjust the values to ensure the total is 100%.

Configuration Dates Checks

Report Output Message

Explanation

Action

"Commencement Cutoff" alias instances should exist only within Teaching calendar instances

This is the date alias within a teaching period on which a student is no longer considered as commencing their course. The system looks for an instance of this date alias in the student's first enrolled teaching period to determine if they are a commencer (new) or a non-commencer (returning). The census date is normally used as this date alias. Instances of this date alias in calendars other than teaching have no effect.

Note: the user defined date alias mapped to this date alias is defined in ENRF01F0.

"Commencement Date" alias instances should exist only within Academic calendar instances

This is the date alias representing the commencement date within an academic period calendar instance. Only one commencement date alias can exist in each academic period calendar instance. Instances of this date alias in calendars other than academic have no effect.

Note: the user defined date alias mapped to this date alias is defined in ENRF01F0.

"Enrolment Form Due Date" alias instances should exist only within Academic or Enrolment calendar instances

This date alias is used as a default enrolment form due date. The default is only used if an override form due date is not specified when the pre-enrolment routine is run. Instances of this date alias in calendars other than academic and enrolment have no effect. (This will be updated in the near future to only apply to Enrolment calendar instances).

Note: the user defined date alias mapped to this date alias is defined in ENRF01F0.

"Enrolment Package Production Date" alias instances should only exist within Academic or Enrolment calendar instances

This date alias is used as a default enrolment package production date. The default is only used if an override package production date is not specified when the pre-enrolment routine is run. Instances of this date alias in calendars other than academic and enrolment have no effect. (This will be updated in the near future to only apply to Enrolment calendar instances).

Note: the user defined date alias mapped to this date alias is defined in ENRF01F0.

"Load Effective Date" alias instances should exist only within Load calendar instances

This date alias is used to determine which is the 'current' load calendar for purposes of point-in-time load and attendance type calculations. It looks for the most recently occurring instance of this date alias and uses the load calendar in which it exists. Instances in calendars other than load have no effect.

Note: the user defined date alias mapped to this date alias is defined in ENRF01F0.

A gap exists between Research effective periods (date alias value)

A gap between the end of one research teaching period and the start of the next should not exist.

Check and update the value of the research effective date alias instances in CALF0512 or CALF0511

Effective end date should be after the calendar start date.

A date alias instance (for the effective end date) has been set to a date prior to the start date for the associated calendar instance. (An instance of a Progression calendar type.)

Correct the value of the date alias instance in CALF0512 or CALF0511

No effective end date alias exists.

This date alias is used in progression calendar types and is used to identify the progression period to which a unit (associated to more than one teaching period) contributes.

Map the user defined date alias to this date alias in PRGF2100.

Research effective dates overlap (date aliases).

A research effective start date alias instance cannot be earlier than the research effective end date of the preceding teaching calendar.

Adjust the value of the research date alias instance to remove the overlap using CALF0512 or CALF0511