Results for “igs_as_course_type_all”

28 results




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

Overview

IGS_AS_COURSE_TYPE_ALL is a reference and association table within the Oracle E-Business Suite Student System (IGS) product family. It describes the course types that are applicable to a given assessment item, and it governs the allocation of assessment items to students according to the course type in which the student is enrolled. In functional terms, the table acts as a bridge that qualifies an assessment item (ASS_ID) by the set of course types (COURSE_TYPE) to which that assessment item applies.

The ETRM metadata classifies the object as belonging to the IGS - Student System (Obsolete) module, and explicitly notes that it is not implemented in this database in the documented 12.1.1 environment. This is significant: in Oracle EBS 12.1.1 and 12.2.2 the table is effectively a legacy or decommissioned construct retained in the data dictionary for historical reference. Practitioners should expect it to be absent or empty in standard installations, and any dependency on it implies a customized or upgraded environment with residual IGS assessment structures.

The heuristic Data Vault classification mined from the foreign-key structure is link. This is a modeling suggestion rather than a physical DDL fact: the table's two business columns each point outward to distinct parent entities, which is characteristic of an associative/link table resolving a many-to-many relationship between assessment items and course types.

Key Information Stored

The documented physical schema for this object in ETRM 12.1.1 spans eight columns owned by the IGS schema. The columns of functional and structural importance are:

  • ASS_ID — identifier of the assessment item from IGS_AS_ASSESSMNT_ITM_ALL; the primary correlation key for the assessment definition.
  • COURSE_TYPE — the course type code from IGS_PS_TYPE_ALL that qualifies the assessment item.
  • ORG_ID — the multi-organization identifier, enabling the same course-type-to-assessment mapping to exist independently per operating unit or institution context.
  • CREATED_BY — the user who inserted the row.
  • CREATION_DATE — the timestamp of the row's insertion.
  • LAST_UPDATED_BY — the user who last modified the row.
  • LAST_UPDATE_DATE — the timestamp of the last modification.
  • LAST_UPDATE_LOGIN — the login session associated with the most recent update, used for audit and concurrency tracking.

The primary key is defined as IGS_AS_COURSE_TYPE_ALL_PK over the column pair (ASS_ID, COURSE_TYPE). A separate unique index, IGS_AS_COURSE_TYPE_ALL_U1, carries the identical column list (ASS_ID, COURSE_TYPE) and therefore serves as the business-key candidate. Because the primary key and the unique index are functionally redundant over the same two columns, there is no independent surrogate sequence key exposed in the documented metadata; the composite of ASS_ID and COURSE_TYPE is both the technical and the business identifier. The remaining WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) follow the standard Oracle EBS audit pattern and are maintained automatically by the application tier.

Common Use Cases and Queries

The primary business scenario is determining which assessment items apply to students enrolled in a particular course type. A allocation or eligibility report typically joins the assessment item master to this table to filter assessment items by course type:

  • Assessment allocation by course type — join IGS_AS_ASSESSMNT_ITM_ALL to this table on ASS_ID and filter on COURSE_TYPE to enumerate the assessment items offered to a given course type.
  • Course type coverage analysis — group by COURSE_TYPE to count or list the assessment items configured against each course type within an ORG_ID.
  • Orphan and integrity checks — identify rows whose ASS_ID or COURSE_TYPE does not resolve to its parent table, useful during data migration or upgrade validation.
  • Audit and change history — use LAST_UPDATE_DATE and LAST_UPDATED_BY to report recently modified mappings.

Because the object is documented as obsolete and not implemented, queries should be guarded defensively. A typical pattern is to test for existence before selecting, for example SELECT COUNT(*) FROM IGS_AS_COURSE_TYPE_ALL WHERE ASS_ID = :ass_id, and to handle the ORA-00942: table or view does not exist condition where the object has been dropped in a later release. Reports that previously relied on this table should be reviewed against the current assessment allocation mechanism in the IGS module.

Related Objects

The following objects are the most significant dependencies, drawn directly from the documented foreign-key and key relationships:

  • IGS_AS_ASSESSMNT_ITM_ALL — parent table for assessment items; joined on IGS_AS_COURSE_TYPE_ALL.ASS_ID = IGS_AS_ASSESSMNT_ITM_ALL.ASS_ID.
  • IGS_PS_TYPE_ALL — parent reference table for course types; joined on IGS_AS_COURSE_TYPE_ALL.COURSE_TYPE = IGS_PS_TYPE_ALL.COURSE_TYPE.
  • IGS_AS_COURSE_TYPE_ALL_PK — the primary key constraint over (ASS_ID, COURSE_TYPE).
  • IGS_AS_COURSE_TYPE_ALL_U1 — the unique index over (ASS_ID, COURSE_TYPE), serving as the business-key candidate.
  • IGS_AS_ASSESSMNT_ITM_ALL_PK — the corresponding primary key on the assessment item parent, implicit in the referential join.
  • IGS_PS_TYPE_ALL_PK — the corresponding primary key on the course type parent, implicit in the referential join.

In the link-table modeling sense, this object sits between the assessment-item hub and the course-type hub, and is superseded in active installations by whatever mechanism the current IGS release uses to scope assessment items to course types. Integrations and custom reports bound to the obsolete column set should be re-pointed to the supported equivalent before upgrading to 12.2.2.