This process:

• Creates load calendar instances and copies details from one academic period to another; or
• Copies details from a single load calendar to another.

Either:

• Updates an academic calendar with instances of load calendars, including details, from an earlier academic calendar; or
• Updates a load calendar with the default load apportions and administrative unit statuses from a previous load calendar.

This job is run as part of the institution's annual calendar rollover process.

The job is run to:

• Rollover load calendars into new academic calendars.
• Rollover the default load apportions and administrative unit statuses from one load calendar to another.

There are two sets of parameters available in this job. Run the job for either:

• The academic calendar rollover by selecting the source academic calendar parameter AND the destination academic calendar parameter. (This rolls over (copies) the load calendars and details from the source academic calendar to the destination calendar); OR
• The load calendar rollover by selecting the source load calendar parameter AND the destination load calendar parameter. (This copies all default load apportion details, unit apportion and administrative unit statuses attached to the source load calendar into the destination load calendar).

This process updates the database in one of two ways:

• If the academic calendar parameters have been specified, the process:
• Selects all ACTIVE load calendars from within the source academic calendar.
• Checks the destination academic calendar for any existing load calendars.
• If ALL details (load calendars) exist, the rollover is stopped and an exception is reported in the Run Log.
• If SOME details exist, then only the load calendars (and details) from the source academic calendar that DO NOT exist are copied to the destination academic calendar. An exception is reported in the Run Log detailing those calendars that were not copied.
• If NO details are found, then the load calendars (and details) for the source academic calendar are created under the destination academic calendar.
• If the load calendar parameters have been specified, the process:
• Selects the details (default load apportions and administrative unit statuses) from the source load calendar.
• Checks the destination load calendar for any existing details.
• If ANY details exist, the rollover is stopped and an exception is reported in the Run Log.
• If NO details are found, then the default load apportions, unit apportions and administrative unit statuses from the source load calendar are created in the destination load calendar.