...
- For each student with an active plan (map_plan.object_status = 1), SSP will compare the courses in external_student_transcript_course (formatted_course) for each term (term_code) with the planned courses (map_plan_course.formatted_course) for equivalent terms (map_plan_course.term_code) starting with the oldest Plan term through the calculation cutoff term. If no cutoff term is defined, the current term will be used. A match will have matching criteria (configurable) for both the Plan and transcripted courses. By default the formatted_course and term_code are used for matching. Additionally, the course title, course code and course hours can be used to provide a more precise match. The result of the calculation is a database update to store the Plan status and reasons for being off plan (if they exist). Each time the calculation is performed, the previous status calculation is removed so that only the most current calculation is stored in the database. The external_person_planning_status table will remain for implementers choosing to provide the calculation through the data integration.
Process Diagram
Database Tables
Features added in 2.4.0
...
The plan status report will identify the results of the calculation for each planned course. Per the calculations described above, the report shows overall, term and course based matches and anomalies. Example Report:
Anomaly Codes
MULTIPLE_ANOMALIES_IN_TERM: multiple course anomalies in the term
NO_ANOMALY: not anomalies existed in the term
CURR_OR_FUT_COURSE_NO_GRADE: a missing or failed grade in a current or future term
- COURSE_NOT_PASSED: a missing or failed grade in a past term
COURSE_NOT_REGISTERED: a missing course in a current or future term
COURSE_NOT_TAKEN: a missing course in a past term
...