Top of STA | Index | Table of Contents | Feedback |
STAJ1610 - Create Government Revision Submission Snapshot
Purpose | To identify and record details for Student Unit Attempts that should be in the Revision/Load Liability file for Revision Submission. | |
SubSystem | Statistics | |
Normally Run By | Statistics specialist | |
Anticipated Frequency | On demand, when the files are required for statistics processing. | |
Structure | Block | Create Government Revision Submission Snapshot |
Tabs | Parameters | |
More | ||
Buttons | Find Person (ADMF1211) | |
Find Course (ADMF1220) |
The purpose of this job is to identify changes to data that has been submitted as part of an Institution's prior statistical submissions to Government. This job creates records in the GOVT_STDNT_LIABILITY_REVISION, GOVT_STDNT_LIABILITY_REVISION and GOVT_STUDENT_REVISION and GOVT_EXT_STUDY_LOAN_REVISION tables. The Create Revisions (STAJ1620) job is run after this to generate OR and SR files for submission to Government. STAJ1610 identifies:
As part of its processing,
STAJ1610 derives the Revision Reason Codes of 2 – change, 4 – deletion,
and 5 – addition due to administrative error,
for the records that are identified. In circumstances where the combination
of student id/course code/unit of study census date has not been previously
reported in a prior Load Liability file for the submission for which
revisions are being compiled, then this record is flagged as a new record
to be included in the next normal Load Liability file submitted (See STAJ0110 – Create
Government Submission Snapshot).
In regard to OS-HELP file revisions, STAJ1610 identifies the Revision reason
codes of 2 – change and 4 – deletion due to administrative error Load Liability STAJ1610 looks for changes in the following Load Liability file elements:
OS-HELP STAJ1610 looks for changes in the following OS-HELP file elements:
For further details about OS-HELP REvisions see Understanding OS-HELP Revisions. For a clearer understanding of the Revisions Process generally, see Understanding HE Revisions. This job is accessed via the main menu. |
The Create Government Revision Submission Snapshot block contains: Parameters Tab Select either:
Or a combination of the following parameters:
Select original Submission for comparison:
More Tab Optional Parameters:
Specify values for:
Determine Revision Reason Code:
|
Rules/Notes: Note
that Original Submission details are not available for this selection
until a completion date for the submission instance has been recorded
in STAF1350. The completion date must be set prior to running STAJ1610. Select a Log Creation Date value if you wish to view the Exception Report generated by a previous run of this job. The report generated in that case, is not related to other values present on the parameter form and a new Government Revision Submission snapshot will not be created. The following fields are mandatory if running the job to create a new Government Revision Submission Snapshot:
This job can be run for the following System Submission Types:
If
the default value of %
remains in the Person ID, Unit Code, Administrative Unit Status and
Course Code fields then the snapshot will consider all student unit
attempts. If values are recorded in any of these fields then the scope
of the snapshot will be restricted accordingly. Validations include:
Include Course Version in Revisions Check Box If ‘Include Course Version in Revisions’ is checked (Y), the processing is exactly as same as it is and is not changed. If ‘Include Course Version in Revisions’ is set to uncheck (N) and the Course Version number of a Student Course Attempt has changed (and this is the only change), previously reported Load Liability records based on the prior Course Version number are not identified as deletions. Nor will records associated with the new Course Version number be identified as previously unreported records. Instead, the new Course Version number is reported as part of Element 307 Course Code in the next normal submission. If ‘Include Course Version in Revisions’ is set to uncheck (N), the Course Version number of a Student Course Attempt has changed and other changes have also occurred, the process is the same as where ‘Include Course Version in Revisions’ is checked (Y). |
||||||||||||||||||||
Understanding the Revision Reason Code The Revision Reason Code (Element 446) indicates the reason for the change in a student's records reported as part of a prior government submission. There are four Revision Reason codes used. They are: 1 - Remission due to special circumstances. If the user has selected 'D' from the Determine Revision Reason Code, then the system derives information and writes a Revision Reason Code of '2', '4' or '5'. If the user selects 'O', and the Validation is '1' the system re-derives the Revision reason code for records that have a Revision Reason Code of ‘1'. If the user selects 'R', then optional parameter must be entered. The system will write a Revision Reason Code of '1' to records that match these optional parameters. Where the new total amount charged, new amount paid up front, new loan fee and new unit of study HELP debt is not zero, then the record is written and an exception is logged. |
Rules/Notes: The Determine Revision Reason Code has three values that can be selected. They are:
An example of the way the system functions is to show one aspect of the process using a Revision Reason Code of '4'. For a Revision record to be recorded with a Revision Code of '4', a previously reported record in an LL or RL file with the following unique identifying elements:
it must be no longer required to be reported either due to the following conditions relating to an administrative error:
For a Revision record associated with OS-HELP to be recorded with a Revision Code of '4', a previously reported record in an OS or RO file with the following unique identifying elements must be no longer required to be reported as they have been incorrectly reported as having an OS-HELP debt:
|
||||||||||||||||||||
Create Government Revision Submission Snapshot To create a snapshot, enter the mandatory and optional parameters as required and run or schedule the job. An exception report is generated in landscape format at the completion of the job. |
Rules/Notes: All records should only be compared to previous Government Submissions where the Completed Date on the Government Snapshot Control Table has been populated. Only Units with a Census Date within the Government Snapshot Control Start Date and End Date range, where the Completion Date has been populated, are considered. If a student is processed that has a record already in the GOVT_STUDENT_REVISION table, for the Student Unit Attempt and Revision Submission Year and Number, then the old record needs to be either updated or deleted and the new record inserted. If a student is processed that already has a record in the GOVT_STUDENT_LOAD_LIABILITY table for the Student Unit Attempt and Revision Submission Year and Number, then the function should skip this step (that is, the step to insert a record into the GOVT_STDNT_LIABILITY_REVISION table). Government reporting
validations for the Revisions file will be completed before
the record is inserted into the GOVT_STUDENT_REVISION table. The following warning messages relate to Research Training Program validations and will be reported to the Exception Report during processing prior to data being recorded within the Governmant snapshot table :
However validation 5005 is specifically checked
for and if
a record fails such a validation, then an error will be written to
the S_LOG_ENTRY table. The Revision Snapshot cannot be run for a Revision Submission that has the Completion Date set in the GOVT_SNAPHOT_CTL table. The Exception Report will indicate if the Enrolment Snapshot (STAJ0100) needs to be rerun for a period where new, previously unreported records have been recorded in the GOVT_STDNT_LIABILITY_REVISION table. |
||||||||||||||||||||
OS-HELP Layout of the Exception Report Revision Submission: 2005/1 Include Course Version in Revisions (Y/N)
|
Last Modified on 11-Apr-2017 3:37 PM
History Information
Release Version | Project | Change to Document |
18.1.0.3, 19.0.0.3, 19.1.0.2 | 2262 - Compliance Research Training Program | Added new validations for students with Research Training Programs |
16.0.0.3, 16.1.0.2 & 17.0.0.2 | 1999 - Compliance 2014 | Added elements 582 and 583 to OS-HELP list and added a link to the OS-HELP Revisions page |
15.1.0.0.3,16.0.0.3, & 16.1.0.2 | 1999 - Compliance 2014 | Added new OS-HELP file elements and notes about OS-HELP records with status 241 and 242. |
13.0.0.3, 14.0.0.3, 15.0.0.2 & 15.1 | 1834 - Service and Amenities Fee | Added note about SA-HELP revisions being independent of this job |
12.0.0.3 | 1600 - Compliance 2010 | Removed note re: exclusion of submission types from LOV, and replaced with new note re: submission types included. |
12.0.03 | 1646 - Skills VIC VET FEE-HELP Reporting | Added note about VET System Submission types being excluded from LOV for the System Submission Type parameter. |
9.1.0.0.0.0 | 1230 - Compliance 2007 Revisions Enhancement | Added 'Include Course Version in Revision' check box and descriptions |
9.0.0.0.0.0 | 1220 - Compliance Changes for 2006 | Variation Reason Code changed to Revision Reason Code |
8.1.1.0.0.0 | Calipso 17580 | Rewrote introduction and Understanding Variation reason code and made various corrections to information in response to Calipso 17580. |
8.0.0.0.0.0 | 1084 - SLE Help Revisions File | Modifications about what the job looks for from BA review. Changes to Variation Reason Code |