Rules for using Cross-Entity Course Enrollment (CECE)

  1. Records are not created in the STUDENT-ENTITY and STUDENT-EW tables in the Home entity for a student taking a Home course. Any program in the Home entity that process by STUDENT-CLASS record and displays Student Entity information will need to get the information from the student’s Away entity.
  2. Two Entities that are using Cross-Entity Course Enrollment MUST have the same number of terms (display, scheduling, and grading). This is because it would be too hard to ‘translate’ between two entities with a different number of terms. Plus, it would make taking attendance and grading extremely complicated.
  3. Two Entities that are using CECE must have the same grading and attendance codes. Student grades and attendance information will be copied from entity to entity, and we do not want to be copying over invalid codes.
  4. Two Entities must be using the same day type and number of days for attendance.
  5. It is highly recommended (but not required) that the schools have the same number of periods.
  6. If any courses are flagged as “Home” or “Away”, the CECE flag cannot be turned off in the Entity-Year maintenance.
  7. If any Current or Next Entities have the CECE flag turned on, the CECE flag cannot be turned off in the District Configuration.

Table Links

  1. COURSE – In the Course table, there is a CECE-TYPE field and a CECE-COR-NUM-ID field. A course can be of type Normal (which most courses will be), Home (the course is taught within your entity), or Away (the course is taught at another entity). When the type is normal (blank) or Home (H), the CECE-COR-NUM-ID field is 0. When the type is Away (A), the course is linked to a Home course in another entity. The COR-NUM-ID of this course is what will be in the CECE-COR-NUM-ID field of the Away course.
  2. CLASS – In the Class table, there is a ALLOW-CECE field. This allows an entity with a Home course to offer several sections to students from other entities to enroll in and other sections where they cannot. When two (or more courses) have been linked and a new section will allow CECE, triggers in the Class table will create a matching section in the Away course. The section numbers are the same. Not all fields will be editable in the Away course.
  3. CLASS-MEET – In the Class-Meet table are the same two fields as the Course table. When a Class-Meet record is created, the CECE-TYPE and CECE-COR-NUM-ID fields are filled in from the Course table. The only fields that are editable in an Away section are the periods and the lunch code.
  4. STUDENT-CLASS – In the Student-Class table are the same two fields as the Course and Class-Meet tables. When a student enrolls in an Away course, the CECE-TYPE (with an A) and CECE-COR-NUM-ID fields are filled in. This will fire the write trigger and a corresponding Student-Class record will be created for the Home course (CECE-TYPE = H). If a student enrolls in a Home course in their own entity, the CECE-TYPE field does not need to be filled in. There should be a “Home” Student-Class record only when there is a corresponding “Away” record in another entity.
  5. STUDENT-CLASS-TRN – In the Student-Class-Trn table are the same two fields as the Student-Class table. If these CECE-TYPE and CECE-COR-NUM-ID fields are filled in correctly (using the same general rule as the end of #4 above), the write trigger will handle the creation of the extra Student-Class-Trn record.
  6.  STUDENT-ENTITY – There will be no Student-Entity record for Away students enrolled in a Home course. Anytime you need to display entity information for a student (status, advisor, etc), you will need to find the Home course that is linked to the Away course,