Results for “attendance_type”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IGS_IN_APPL_COURSE is a table within the IGS (Student System) product family of Oracle E-Business Suite. The ETRM metadata explicitly marks this object as Obsolete and records that it is Not implemented in this database. Historically, it described the courses of interest associated with an enquiry application — that is, the set of academic courses a prospective applicant selected or expressed interest in at the point of enquiry, prior to formal application processing.

Under the heuristic Data Vault classification derived from its foreign-key structure, the object is modelled as a link. This is consistent with its shape: the table does not store a persistent descriptive profile but associates multiple business actors — a person, an enquiry application, a course, and a location — into a single associative record. In Data Vault terms, PERSON_ID, ENQUIRY_APPL_NUMBER and COURSE_CD act as the participating business keys, while the table itself captures the relationship and its qualifying attributes.

Because the object is obsolete and not implemented, it should not appear in any operational 12.1.1 or 12.2.2 environment. References found in custom code, legacy migration scripts, or older report definitions typically indicate artifacts carried forward from a prior release.

Key Information Stored

The documented physical schema lists twelve columns. The most significant are:

  • PERSON_ID — the identifier of the person (prospective applicant) raising the enquiry; part of the primary key and of the unique index.
  • ENQUIRY_APPL_NUMBER — the enquiry application number to which the course interest belongs; part of the primary key.
  • COURSE_CD — the code of the course of interest; part of the primary key.
  • VERSION_NUMBER — the version of the course or enquiry record; part of the primary key.
  • LOCATION_CD — the location or campus at which the course interest applies.
  • ATTENDANCE_MODE — the mode of attendance requested, e.g. full-time or part-time; foreign key to IGS_EN_ATD_MODE_ALL.
  • ATTENDANCE_TYPE — the type of attendance; foreign key to IGS_EN_ATD_TYPE_ALL.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified each row.

The surrogate identity of a row is defined by the primary key constraint IGS_IN_APPL_COURSE_PK over (PERSON_ID, ENQUIRY_APPL_NUMBER, VERSION_NUMBER, COURSE_CD). A unique index, IGS_IN_APPL_COURSE_U1, is documented over the identical column set. Because there is no separate system-generated numeric key, the primary key columns are themselves the business-key candidates, and no artificial surrogate is distinguished from them in this object.

Common Use Cases and Queries

In legacy releases this table would have supported enquiry-stage reporting: which courses attract the most interest, attendance-mode preferences among enquirers, and conversion tracking from enquiry to application. A representative pattern joins the enquiry header and person:

  • Listing courses of interest for a given person: SELECT course_cd, version_number, location_cd, attendance_mode FROM igs_in_appl_course WHERE person_id = :p_person_id.
  • Aggregating demand by course: SELECT course_cd, COUNT(*) FROM igs_in_appl_course GROUP BY course_cd.
  • Resolving attendance lookups: JOIN igs_en_atd_mode_all m ON m.attendance_mode = c.attendance_mode.

Given its obsolete status, these patterns are relevant only for historical data extracts or archaeology of legacy implementations.

Related Objects

  • IGS_EN_ATD_MODE_ALL — referenced via IGS_IN_APPL_COURSE.ATTENDANCE_MODE.
  • IGS_EN_ATD_TYPE_ALL — referenced via IGS_IN_APPL_COURSE.ATTENDANCE_TYPE.
  • Enquiry application header objects — the parent of ENQUIRY_APPL_NUMBER, tying each course-of-interest line to its enquiry.
  • Person / party objects — the source of PERSON_ID.
  • Course catalogue objects — the definition behind COURSE_CD and VERSION_NUMBER.

No implemented views or APIs are documented for this table, consistent with its obsolete designation.