The tables behind Scholarship Management

Keep source identifiers in a migration mapping and link imported records to their corresponding destination records; operating records use Id and exchange rates uses ID. Use learner numbers and course codes as readable identifiers, while resolving references to the actual records. Enrollment label and session label are calculated fields, so preserve their configured behavior rather than importing a competing label rule.

Resolve My Courses through the signed-in user’s People record before comparing Courses.Instructor. Attendance must remain unique for the Session and Learner pair. An application connects to its award’s enrollment through Award then operational record; confirm that enrollment belongs to the intended learner. Fees connects to Learners separately and requires an explicit allocation handoff when scholarship support affects a charge.

1. Prepare Users and People, confirming staff-to-user identity and active state.
2. Import Learners and Courses with the correct instructor, capacity, dates and statuses.
3. Create class sessions and Assessments for their courses, preserving timing, labels and assessment maxima.
4. Prepare Enrollments after resolving the intended learner and course; reconcile existing places before running new approval actions.
5. Create scholarship awards against the correct enrollment, then scholarship applications against their learner and award.
6. Load historical Attendance and assessment results with their true learner-session or learner-assessment scope, without triggering unintended completion.
7. Reconcile Fees with the owning finance source and verify exchange rates as read-only context. Confirm monetary conventions before using amounts across processes.