STAJ8100 - USI Corrections Extract

Purpose	To compare data in a Completed Submission with an Incomplete Submission and create extract records accordingly.
SubSystem	Statistics
Normally Run By	Statistics specialist
Anticipated Frequency	On demand, when the export is required.
Structure	Tab	Parameters

This job generates extract records which identify differences between students' currently enrolled data and that which has been reported to the National Centre for Vocational Education Research (NCVER) via the Australian Vocational Education and Training Management Information Statistical Standard (AVETMISS) reporting process.
Identification of such changes enables institutions to use the Unique Student Identifier (USI) Transcript update function within AVETMISS Validation Software (AVS) to provide updates to a student’s USI Transcript between submissions.

This job is only available to VET sector and cross sector institutions.

It is accessed via the main menu and can only be run via the job scheduler in schedule mode.

Parameters Tab

Incomplete Submission Details
Use most recent Incomplete Submission check box
Completed Submission Details

Rules/Notes:

'Incomplete Submissions' are those for which the Complete Date is blank in the Maintain VET Government Snapshot Control (STAF8005). 'Completed Submissions' have a date recorded for this field in STAF8005.

You must either select an Incomplete Submission or select the check box for the most recent Incomplete Submission.

You must also select a Completed Submission to which this can be compared.

The government training organisation unit code of the Incomplete Submission Details parameter and the Completed Submission Details (if defined) parameter must be the same.

The following data is examined in the Government Snapshot VET tables to identify differences between nominated Complete and an Incomplete Submissions:

Student Unit Attempt and Advanced Standing Unit data:

Derived Activity Start and/or End dates
Government Funding Source code
Government National Outcome ID
Subject Identifier
Subject Name.

Student Course Attempt data:

Program Identifier (Qualification Code or Course Version Code)
Program Name (Qualification Title or Course Version Title)
Year Program Completed (Year from the Requirements Complete Date)

Person Data

Changes to Person USI

The job also checks for students who have a verified USI and identify reportable Qualifications and Subjects which have not previously been reported within a completed submission.

Any differences identified by this job are recorded as records in the S_EXTRACT_RECORD table with S_EXTRACT_TYPE = USI_ADJ.

Records which are identified via this process are used to update the Students USI Transcript using the USI Transcript update function within the AVETMISS Validation Software

It is assumed that students who have been reported within a Completed Submission have been reported to the USI Office and exist on the Student's USI Transcript and have:

A valid verified USI Number (not a USI Exemption or no USI at all).
Student Course Attempts with Commencing Course IDs of 3 (commencing enrolment) or 4 (continuing enrolment) and associated Student Unit Attempts.
Student Unit Attempts that have a govt_funding_source listed against them.

Note: A valid USI is a 10 digit string which has the valid characters of A-H, J-N, P-Z and numbers 2-9 and a USI Exemption is a code that has been issued by the government indicating the student is exempt from reporting a valid USI. e.g. SHORT, INTOFF, INDIV.

Note that if any individual student record doesn’t require any extract records to be created for them, they are skipped and nothing is logged for them.

Processing Summary

Checks at Person Level use the GOVT_SNAPSHOT_ENROLMENT (GSEV) and GOVT_SNAPSHOT_PERSON_VET (GSPV) tables to get the person USI details for comparison.
Checks at Unit Level use the GOVT_SNAPSHOT_ENROLMENT (GSEV), GOVT_SNAPSHOT_PERSON_VET (GSPV) and GOVT_SNAPSHOT_UNIT_VET (GSUV) tables to get the unit details for comparison.
Note: Unit submission records (GSUV) will always contain the latest unit version in the Unit Version table at the time of the submission job run. Therefore, the actual enrolled SUA version that is reported in the GSEV table may be different to that in the GSUV table.
Checks at Course Level use the GOVT_SNAPSHOT_ENROLMENT (GSEV), GOVT_SNAPSHOT_PERSON_VET (GSPV), GOVT_SNAPSHOT_CRS_VET (GSCRSV) and GOVT_SNAPSHOT_QUAL_COMP_VET (GSQCV) tables to get the course and course completion details for comparison.
Note: Course submission records(GSCRSV) will always contain the latest course version in the Course Version table at the time of the submission job run. Therefore, the actual enrolled SCA version that is reported in the GSEV table may be different to that in the GSCRSV table.

For the submission records that match the job parameters, the checks below are made to determine if units or courses are either deleted, updated or new, and if there are any changes or additions to the student USIs. The identified changes are logged in the S_EXTRACT_RECORD table.

Check USI for each submission.
If a student in the GSEV table has had their USI updated since the Completed Submission > logged as UPDATE_USI.
Check to see if applicable students have a valid USI listed in the Incomplete Submission that was missing (a null or Exempt USI or no GSPV record) in the Completed Submission
If a student in the GSEV table has had a valid USI added since the Completed Submission > logged as NEW_USI.
Check for unit detail differences between Completed and Incomplete Submissions for Student Unit Attempt and Advanced Standing Unit records
a) If a student in the GSEV table has removed units since the Completed Submission > logged as DELETED_UNIT.
b) If a student in the GSEV table has updated units since the Completed Submission > logged as UPDATE_UNIT.
Check for unit level differences, by looking at the Incomplete Submission records with a valid USI and a govt funding_source, and seeing if the units don’t exist in the completed submission, with a valid USI, or if they didn’t have a govt funding source in the completed submission but now do. This picks up any newly added Student Unit Attempt and Advanced Standing Unit from a previous submission containing a valid USI.
If a student in the GSEV table has added units since the Completed Submission > logged as NEW_UNIT.
If a NEW_USI is found (see 2 above), or an UPDATE_USI is found (see 1 above) the job adds all units in the incomplete submission as NEW_UNITS, since they haven’t previously been reported due to the lack of a valid USI or due to a change to a new valid USI. Only units from the incomplete submission that have a govt funding source are added as NEW_UNIT. If the submission year differs, the job also adds unit from the complete submission as NEW-UNITS.
If a student has a new or updated USI, then a record is logged for each unit > logged as NEW_UNIT.
Check course level detail differences between complete and incomplete submissions for Student Course Attempt records. Only students who have a valid USI listed against their completed submission are considered.
If a student in the GSEV table has removed or updated courses since the Completed Submission > logged as DELETED_COURSE or UPDATED_COURSE.
Check for course level differences, by looking at the incomplete submission records with a valid USI and seeing if the courses don’t exist in the completed submission - with a valid USI. This picks up any newly added Student Course Attempts from a previous submission containing a valid USI.
If a student in the GSEV table has added courses since the Completed Submission > logged as NEW_COURSE.
If a NEW_USI is found (see 2 above) or an UPDATE_USI is found (see 1 above) the job adds all courses in the incomplete submission as NEW_COURSE’s, since they haven’t previously been reported due to the lack of a valid USI or due to a change to a new valid USI. Only Courses from the incomplete submission that have are not unit-only courses wil be added as NEW_COURSEs. If the submission year differs, the job will also add courses from the complete submission as NEW_COURSEs.
If a student has a new or updated USI then a record is logged for each course > logged as NEW_COURSE.
If the above checks have been processed and no differences have been found between the incomplete and complete submissions > logged as NO_DIFFERENCE

Extract Records

The tables below give details of the S_EXTRACT_RECORDs generated by this job. In these tables, the green rows are common to all USI_ADJ extract records and pink rows are the ones that describe the corrections.

1. RECORD_TYPE = 'UPDATE_USI'

This extract record will be created if a valid USI for an applicable student was changed to another valid USI or a valid USI for an applicable student was changed to an Exemption or NULL USI.

S_EXTRACT_RECORD Field	Data Source	Example
S_EXTRACT_TYPE	‘USI_ADJ’	USI-ADJ
CREATION_DT	SYSDATE when s_extract record created.	18/09/2017 1:25:08 PM
KEY1	completed gsev.submission_yr '-' completed gsev.submission_number	2017 - 5
KEY2	incomplete gsev.submission_yr '-' incomplete gsev.submission_number	2018 - 1
KEY3	completed gsev.org_unit_cd '-' completed gsev.ou_start_dt	537 - 11/06/2002
KEY4	completed gsev.person_id	1007199549
KEY5	completed gspv.person_usi	ABCDE12345
KEY6-10
RECORD_TYPE	'UPDATED_USI'	UPDATED_USI
TEXT	'Previously Submitted USI -' completed gspv.person_usi '\|' 'New Value for USI -' incomplete gspv.person_usi	Previously Submitted USI - ABCDE12345 \| New Value for USI - ABCDE67890

2. RECORD_TYPE = 'NEW_USI'

This extract record will be created if a student has a valid USI listed in the Incomplete Submission that was missing in the Complete Submission.i.e. A NULL or Exempt USI or no GSEV record.

S_EXTRACT_RECORD Field	Data Source	Example
S_EXTRACT_TYPE	‘USI_ADJ’	USI-ADJ
CREATION_DT	SYSDATE when s_extract record created.	18/09/2017 1:25:08 PM
KEY1	completed gsev.submission_yr '-' completed gsev.submission_number	2017 - 5
KEY2	incomplete gsev.submission_yr '-' incomplete gsev.submission_number	2018 - 1
KEY3	completed gsev.org_unit_cd '-' completed gsev.ou_start_dt	537 - 11/06/2002
KEY4	completed gsev.person_id	1007199549
KEY5	completed gspv.person_usi	ABCDE12345
KEY6-10
RECORD_TYPE	'NEW_USI'	NEW_USI
TEXT	'Non- Submitted USI - ' completed gspv.person_usi	Non-submitted USI - ABCDE12345

3. RECORD_TYPE = 'DELETED_UNIT'

In the nominated Completed Submission, for each record with Student Unit Attempt or Advanced Standing Unit record with a govt funding source in the GSEV table that has a valid USI listed in the GSPV table, the job checks to see if the matching unit is found in the GSEV table for the Incomplete Submission.

A DELETED_UNIT record is logged if:

A matching unit record is not found in the Incomplete Submission for the same Submission Year.
A matching unit record is not found in the Incomplete Submission for a different Submission Year, and the unit from the Completed Submission has a govt_outcome_cd of 70 - Continuing.
A matching record is found in the Incomplete Submission, and the person USI within the GSPV has changed from a valid USI to an exempt code (SHORT, INDV, INTOFF) or has been set to NULL (Deleted)- regardless of the submission year.
A matching record is found in the Incomplete Submission, but the units govt_funding_source is NULL - regardless of the Submission Year.

S_EXTRACT_RECORD Field	Data Source	Example
S_EXTRACT_TYPE	‘USI_ADJ’	USI-ADJ
CREATION_DT	SYSDATE when s_extract record created.	18/09/2017 1:25:08 PM
KEY1	completed gsev.submission_yr '-' completed gsev.submission_number	2017 - 5
KEY2	incomplete gsev.submission_yr '-' incomplete gsev.submission_number	2018 - 1
KEY3	completed gsev.org_unit_cd '-' completed gsev.ou_start_dt	537 - 11/06/2002
KEY4	completed gsev.person_id	1007199549
KEY5	completed gspv.person_usi	ABCDE12345
KEY6	completed gsev.course_cd '-' completed gsev.crv_version_number	GMH111-1
KEY7	completed gsev.unit_cd '-' completed gsev.uv_version_number	GMH_VET_2-1
KEY8-10
RECORD_TYPE	'DELETED_UNIT'	DELETED_UNIT
TEXT	'Deleted Activity start date - ' completed gsev.enr_activity_start_dt '\|' 'Deleted Activity end date - ' completed gsev.enr_activity_end_dt '\|' 'Deleted Subject identifier - 'completed gsev.subject_id '\|' 'Deleted Subject name - 'completed gsev.subject_name '\|' 'Deleted Government Outcome Code - 'completed gsev.govt_outcome_cd '\|' 'Deleted Outcome identifier code (National) - ' completed gsev.govt_outcome_cd '\|' 'Deleted Funding source code (National) - 'completed gsev.national_funding_source'\|' 'Deleted Funding source code (State/Territory) - ' completed gsev.state_funding_source	Deleted Activity start date - 01/07/2017 \| Deleted Activity end date - 30/07/2018 \| Deleted Government Outcome Code - 70 \| Deleted Subject identifier- GMH_VET_2 \| Deleted Subject name - GMH_VET_2 \| Deleted Outcome identifier code (National - 70 \| Deleted Funding source code (National) - 13 \| Deleted Funding source code (State/Territory) -

4. RECORD_TYPE = 'UPDATE_UNIT'

An UPDATE_UNIT record is logged, if a matching unit record is found in the Incomplete Submission, and the record has a valid USI in the GSPV and a govt funding source, and any of the following fields from the GSEV and GSUV tables have changed:

Enr_activity_start_dt
Enr_activity_end_dt
Govt_funding_source
Govt_outcome_cd
Subject_id
Subject name

S_EXTRACT_RECORD Field	Data Source	Example
S_EXTRACT_TYPE	‘USI_ADJ’	USI-ADJ
CREATION_DT	SYSDATE when s_extract record created.	18/09/2017 1:25:08 PM
KEY1	completed gsev.submission_yr '-' completed gsev.submission_number	2017 - 5
KEY2	incomplete gsev.submission_yr '-' incomplete gsev.submission_number	2018 - 1
KEY3	completed gsev.org_unit_cd '-' completed gsev.ou_start_dt	537 - 11/06/2002
KEY4	completed gsev.person_id	1007199549
KEY5	completed gspv.person_usi	ABCDE12345
KEY6	completed gsev.course_cd '-' completed gsev.crv_version_number	GMH111-1
KEY7	completed gsev.unit_cd '-' completed gsev.uv_version_number	GMH_VET_2-1
KEY8-10
RECORD_TYPE	'UPDATED_UNIT'	UPDATED_UNIT
TEXT	'Previously Submitted Activity start date - ' completed gsev.enr_activity_start_dt'\|' 'New Value for Activity start date - ' incomplete gsev.enr_activity_start_dt'\|' ' Previously Submitted Activity end date - ' completed gsev.enr_activity_end_dt '\|' 'New Value for Activity end date - ' incomplete gsev.enr_activity_end_dt '\|' ' Previously Submitted Subject identifier - ' completed gsev.subject_id'\|' ' New Value for Subject identifier - ' incomplete gsev.subject_id'\|' ' Previously Submitted Subject name - ' completed gsev.subject_name '\|' 'New Value for Submitted Subject name - ' incomplete gsev.subject_name '\|' ' Previously Submitted Outcome identifier code (National) - ' completed gsev.govt_outcome_cd'\|' ' New Value for Outcome identifier code (National) - ' incomplete gsev.govt_outcome_cd '\|' ' Previously Submitted Funding source code (National) - ' completed gsev.national_funding_source'\|' 'New Value for Funding source code (National) - ' incomplete gsev.national_funding_source'\|' ' Previously Submitted Funding source code (State/Territory) - ' completed gsev.state_funding_source'\|' 'New Value for Funding source code (State/Territory) - ' incomplete gsev.state_funding_source	Previously Submitted Activity start date - 01/07/2017 \| New Value for Activity start date - 10/07/2017 \| Previously Submitted Activity end date - 30/07/2018 \| New Value for Activity end date - 30/06/2018 \| Previously Submitted Funding source code (National) - 13 \| New Value for Funding source code (National) - 13 \| Previously Submitted Funding source code (State/Territory) - \| New Value for Funding source code (State/Territory) - \| Previously Submitted Government Outcome identifier - 70 \| New Value for Government Outcome identifier - 70 \| Previously Submitted Subject identifier - GMH_VET_2 \| New Value for Subject identifier - GMH_VET_1 \| Previously Submitted Subject Name - GMH_VET_2 \| New Value for Subject Name - GMH_VET_1

5. RECORD_TYPE = 'NEW_UNIT'

The job looks at the nominated Incomplete Submission records for students with a valid USI and Unit attempts with a govt funding source and checks if a matching unit exists in the Completed Submission with a valid USI. (or if they didn’t have a funding source in the Completed Submission but do now). This also picks up any newly added Student Unit Attempt and Advanced Standing Units from a previous submission containing a valid USI.

A NEW_UNIT record is logged when:

A matching unit record is not found in the Completed submission.
A matching unit record is found, but which does not have a govt funding source.

The job also creates NEW_UNIT extract records when a new USI is found (NEW_USI above), or a USI is updated (UPDATE_USI above). When a new or different valid USI is found in the Incomplete Submission, it adds all units in the Incomplete Submission as NEW_UNITS, since they haven’t previously been reported due to the lack of a valid USI or due to a change to a new valid USI. Only units from the Incomplete Submission that have a govt funding source will be added. If the Submission Year differs, it also adds units from the Complete Submission as NEW_UNITS.

If the submissions are from different years, the job also checks the Complete Submission and adds all units with a govt funding source and a govt_outcome_cd not equal to 70 and log a USI-ADJ record as a NEW_UNIT in s_extract_record. i.e. Continuing units wont then be reported twice if they exist in the Complete and Incomplete years.

S_EXTRACT_RECORD Field	Data Source	Example
S_EXTRACT_TYPE	‘USI_ADJ’	USI-ADJ
CREATION_DT	SYSDATE when s_extract record created.	18/09/2017 1:25:08 PM
KEY1	completed gsev.submission_yr '-' completed gsev.submission_number	2017 - 5
KEY2	incomplete gsev.submission_yr '-' incomplete gsev.submission_number	2018 - 1
KEY3	completed gsev.org_unit_cd '-' completed gsev.ou_start_dt	537 - 11/06/2002
KEY4	completed gsev.person_id	1007199549
KEY5	completed gspv.person_usi	ABCDE12345
KEY6	completed gsev.course_cd '-' completed gsev.crv_version_number	GMH111-1
KEY7	completed gsev.unit_cd '-' completed gsev.uv_version_number	GMH_VET_2-1
KEY8-10
RECORD_TYPE	'NEW_UNIT'	NEW_UNIT
TEXT	'Non-Submitted Activity start date - ' incomplete gsev.enr_activity_start_dt '\|' 'Non-Submitted Activity end date - ' incomplete gsev.enr_activity_end_dt '\|' 'Non-Submitted Subject identifier - ' incomplete gsev.subject_id '\|' 'Non-Submitted Subject name - ' incomplete gsev.subject_name '\|' 'Non-Submitted Outcome identifier code (National) - 'incomplete gsev.govt_outcome_cd '\|' 'Non-Submitted Funding source code (National) - ' incomplete gsev.national_funding_source'\|' 'Non-Submitted Funding source code (State/Territory) - 'incomplete gsev.state_funding_source'\|' 'Non-Submitted Client Identifier - ' incomplete gsev.person_id	Non-submitted Activity start date - 01/01/2018 \| Non-submitted Activity end date - 30/06/2018 \| Non-submitted Subject identifier - GMH_VET_2 \| Non-submitted Subject Name - GMH TEST UNIT 2 \| Non-submitted Funding source code (National) - 13 \| Non-submitted Funding source code (State/Territory) - \| Non-submitted Government Outcome identifier - 70 \| Non-submitted Client identifier - 1007199549

6. RECORD_TYPE = 'DELETED_COURSE'

The job checks course level detail differences between Complete and Incomplete Submissions. For each record in the GSEV table for the Completed Submission, it checks to see if the matching course record is found in the GSEV table for the Incomplete Submission, if it is missing a 'DELETED_COURSE' record is logged. Note: Only students who have a valid USI listed against their Completed Submission are considered and if a student has completed the course in the Complete Submission and the Incomplete Submission is in a different Submission Year, then the course is not logged.

A DELETED_COURSE record may also be logged if:

A matching course record is found, but the course has changed to a unit-only course
A student’s USI has changed from a valid USI to one of the exemption codes (SHORT, INDV, INTOFF) or is null.

S_EXTRACT_RECORD Field	Data Source	Example
S_EXTRACT_TYPE	‘USI_ADJ’	USI-ADJ
CREATION_DT	SYSDATE when s_extract record created.	18/09/2017 1:25:08 PM
KEY1	completed gsev.submission_yr '-' completed gsev.submission_number	2017 - 5
KEY2	incomplete gsev.submission_yr '-' incomplete gsev.submission_number	2018 - 1
KEY3	completed gsev.org_unit_cd '-' completed gsev.ou_start_dt	537 - 11/06/2002
KEY4	completed gsev.person_id	1007199549
KEY5	completed gspv.person_usi	ABCDE12345
KEY6	completed gsev.course_cd '-' completed gsev.crv_version_number	GMH111-1
KEY7-10
RECORD_TYPE	'DELETED_COURSE'	DELETED_COURSE
TEXT	'Deleted Program identifier - 'completed gsev.program_id '\|' 'Deleted Program name - 'completed gsev.program_name '\|' 'Deleted Year Program Completed - completed gscqv.completed_yr‘\|’ ‘Deleted Commencing Course ID’	Deleted Program identifier - GMH111 \| Deleted Program name - TRAINEESHIP IN AEROBATIC FLYING \| Deleted Year Program Completed - \| Deleted Commencing Course ID - 3

7. RECORD_TYPE = 'UPDATED_COURSE'

The job compares course details for matching courses in the Completed Submission and Incomplete Submission records and if any the Program ID, Program identifier or Year Program Completed values are different, then an UPDATED_COURSE record is logged.

S_EXTRACT_RECORD Field	Data Source	Example
S_EXTRACT_TYPE	‘USI_ADJ’	USI-ADJ
CREATION_DT	SYSDATE when s_extract record created.	18/09/2017 1:25:08 PM
KEY1	completed gsev.submission_yr '-' completed gsev.submission_number	2017 - 5
KEY2	incomplete gsev.submission_yr '-' incomplete gsev.submission_number	2018 - 1
KEY3	completed gsev.org_unit_cd '-' completed gsev.ou_start_dt	537 - 11/06/2002
KEY4	completed gsev.person_id	1007199549
KEY5	completed gspv.person_usi	ABCDE12345
KEY6	completed gsev.course_cd '-' completed gsev.crv_version_number	GMH111-1
KEY7-10
RECORD_TYPE	'UPDATED_COURSE'	UPDATED_COURSE
TEXT	'Previously Submitted Program identifier - ' completed gsev. program _id'\|' 'New Value for Program identifier - ' incomplete gsev. program_id '\|' 'Previously Submitted Program name - ' completed gsev. program _name '\|' 'New Value for Submitted Program name - ' incomplete gsev. program _name '\|' 'Previously Submitted Year Program Completed - ' completed gscqv.completed_yr '\|' 'New Value for Year Program Completed- ' incomplete gscqv. completed_yr	Previously submitted Program identifier - GMH111 \| New value for Program identifier - GMH116 \| Previously submitted Program name - TRAINEESHIP IN AEROBATIC FLYING \| New value for Program name - GMH116 \| Previously submitted Year Program Completed - \| New value for Year Program Completed -

8. RECORD_TYPE = 'NEW_COURSE'

The job looks at the Incomplete Submission records with a valid USI to see if the courses don’t exist in the Completed Submission with a valid USI. This picks up if any Student Course Attempts containing a valid USI were added since the a Completed Submission.

A NEW_COURSE record is logged in S_EXTRACT_RECORD when:

A matching course record is not found in the Completed Submission.
A matching course record is found in the Completed Submission and it is no longer a unit-only course.

NEW_COURSE records are also logged when a new or updated USI is found. When a new valid USI is found in the Incomplete Submission, all courses in the Incomplete Submission are logged as NEW_COURSEs, since they haven’t previously been reported due to the lack of a valid USI or due to a change to a new valid USI. Only Courses from the Incomplete Submission that are not Unit-Only courses are logged as NEW_COURSEs.
If the Submission Year differs, the job also adds courses from the Complete Submission as NEW_COURSEs.

Note: The ‘Funding Source code (State/Territory) in the text field will be null if the course funding source is defined at the National level.

S_EXTRACT_RECORD Field	Data Source	Example
S_EXTRACT_TYPE	‘USI_ADJ’	USI-ADJ
CREATION_DT	SYSDATE when s_extract record created.	18/09/2017 1:25:08 PM
KEY1	completed gsev.submission_yr '-' completed gsev.submission_number	2017 - 5
KEY2	incomplete gsev.submission_yr '-' incomplete gsev.submission_number	2018 - 1
KEY3	completed gsev.org_unit_cd '-' completed gsev.ou_start_dt	537 - 11/06/2002
KEY4	completed gsev.person_id	1007199549
KEY5	completed gspv.person_usi	ABCDE12345
KEY6	completed gsev.course_cd '-' completed gsev.crv_version_number	GMH111-1
KEY7-10
RECORD_TYPE	'NEW_COURSE'	NEW_COURSE
TEXT	' Non-Submitted Program identifier - 'incomplete gsev.program_id'\|' ' Non-Submitted Program name - 'incomplete gsev.program_name '\|' ' Non-Submitted Year Program Completed- ' incomplete gscqv.completion_yr '\|' ' Non-Submitted Funding source code (State/Territory) - ' incomplete gsev.state_funding_source'\|' ' Non-Submitted Client Identifier - 'incomplete gsev.person_id	Non-submitted Program identifier - 7893247899 \| Non-submitted Program name - GMH111 \| Non-submitted Year Program Completed - \| Non-submitted Funding Source code (STATE) - \| Non-submitted Client Identifier - 1007199549

9. RECORD_TYPE = 'NO_DIFFERENCE'

If no differences are found between the Incomplete and Complete Submissions, then the job logs a NO_DIFFERENCE record in S_EXTRACT_RECORD.

S_EXTRACT_RECORD Field	Data Source	Example
S_EXTRACT_TYPE	‘USI_ADJ’	USI-ADJ
CREATION_DT	SYSDATE when s_extract record created.	18/09/2017 1:25:08 PM
KEY1	completed gsev.submission_yr '-' completed gsev.submission_number	2017 - 5
KEY2	incomplete gsev.submission_yr '-' incomplete gsev.submission_number	2018 - 1
KEY3	completed gsev.org_unit_cd '-' completed gsev.ou_start_dt	537 - 11/06/2002
KEY4-10
RECORD_TYPE	'NO_DIFFERENCES'	NO_DIFFERENCES
TEXT	'No differences have been identified for the Incomplete and Complete Submissions.'	No differences have been identified for the Incomplete and Complete Submissions.

Last Modified on 10-Oct-2017 5:48 PM

History Information

Release Version	Project	Change to Document
19.0.0.3, 19.1.0.3 & 20.0.0.2	1662 - Compliance - USI Corrections	New Online Help page.