TCSI Error Code - 10166

Invalid code value in Basis for Admission Code (E327)


TCSI Error Description

Please check the list of acceptable codes for the Basis for Admission Code (E327) and report the correct code for the course.

Error Logic

If the Basis for Admission Code (E327) is not blank (null), then the Basis for Admission Code (E327) must match to a current value in the RefBasisForAdmission table on the Course of Study Commencement Date (E534).

Paradigm Error Resolution

Step 1: Check the Basis of the Admission packet under the Student TCSI Edit screen.

  1. With the student record loaded, navigate to Student > Course Enrolment > Student TCSI Edit menus on the side

  2. Ensure that the Basis for Admission Code matches the list of acceptable codes defined here.

  1. If the code entered is correct and you haven’t made any changes to the student course enrolment record outcome code recently, raise a ticket so we can further investigate. If you have made a recent change on the Course Enrolment record, proceed to Step 2.

Step 2: Check the following scenario if it applies to your case

  1. Course Enrolment had the course enrolment status value of Completed

If the Course enrolment had the course enrolment status value of Completed, meaning that an outcome has been recorded and the details should not be changed.

  1. Course Enrolment start date is prior to the migration to TCSI and the basis of admission code used is the latest acceptable code

If the Course Enrolment start date is prior to the migration to TCSI then the basis of admission code should have been chosen from the list of values that were in place for the period prior to the start of TCSI, and these values do not correspond with the values for validation via TCSI. This field should have had a value set and finalised via HEPCAT.

  1. The Course Enrolment start date had been changed from an older date to a later one and back again

Changing this data (start date had been changed from an older date to a later one and back again) at the same time as the basis of admission data, where one of the pieces of data was being validated against code values that are now outdated, caused your update attempts to fall into a loop. This can be more easily understood where the valid basis of admission value you entered under TCSI did not yet exist during the era of HEPCAT which is when the course enrolment began. For example, the code of 40 did not exist prior to 2021 so the value of 40 cannot be used for any course enrolments that have a start date prior to 01/01/2021.

  1. Load the course enrolment and update the Course Enrolment status from Completed to Enrolled,

  2. Set values for the missing details of Contact Mode and Contact Hours,

  3. Set the Course Enrolment Start Date to its original value, and save the course enrolment record.

  4. Load the Student TCSI Edit screen and Delete the existing Invalid Basis of Admission record(s), as the code in the record does not contain a valid value for the HEPCAT era,

  5. Create a new basis of admission record with a value of 29 β€œA commencing student who was admitted on another basis.” Click the Save button. If you would prefer to use a different basis of admission code that is valid but does not appear in the list for you to choose, raise a ticket so we can make the allowable basis of admission code for the HEPCAT era visible for you to choose.

  6. Load the TCSI Bulk Push screen and search for the Basis of Admission section. Find the student's course Basis of Admission record, select the tickbox for it, and then click the Submit button to submit the record to be validated.

  7. Return to the student summary page and reload the student record. Confirm that the summary page shows the status of Valid for the course enrolment and confirm that the Student TCSI Edit screen also shows the status of Valid for your newly created Basis of Admission packet.

  8. Load the course enrolment record, return the course enrolment status value to its original value, and then save the record.

  9. If the issue remains, please raise a ticket and include the details of any updates that you've made so far, so we can investigate further.

Last updated