Results for “nominated_course_cd”

50+ results




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

Overview

IGS_AD_APPQUAL_CODE is a transaction table within the Oracle E-Business Suite Student System (IGS) product family. It stores the qualification type and corresponding qualification value associated with each individual application instance processed through the admissions module. In release 12.1.1 and 12.2.2, the table resides in the IGS schema and carries a status of VALID. Its purpose is to capture, at the granularity of a specific applicant admission record, the qualifying attributes used to evaluate an application — for example, a qualifying examination type and the resulting score or grade — thereby supporting admissions decision processing and downstream reporting.

In Data Vault modeling terms, the mined foreign-key structure classifies this object heuristically as a link. This is a modeling suggestion only: the table does not hold descriptive history of a single business entity but rather associates several business keys (applicant, application instance, nominated course, application sequence, and qualifying type) and records an attribute (QUALIFYING_VALUE) that describes their intersection. Modelers may therefore treat it as a link table joined to its parent application-instance hub, with QUALIFYING_VALUE and the audit columns behaving as satellite-style descriptive attributes.

Key Information Stored

The table documents twelve columns. The primary key, enforced by the unique index IGS_AD_APPQUAL_CODE_PK, is composite and comprises five business-key columns rather than a single surrogate identifier:

Because the unique index is a composite business key rather than a generated surrogate, joins and updates must always include all five PK columns to guarantee row uniqueness.

Common Use Cases and Queries

Typical usage centers on admissions evaluation, applicant qualification analysis, and integration with admissions reporting. A representative query joining the parent application-instance table is:

  • SELECT q.PERSON_ID, q.ADMISSION_APPL_NUMBER, q.QUALIFYING_TYPE_CODE, q.QUALIFYING_VALUE FROM IGS.IGS_AD_APPQUAL_CODE q WHERE q.ADMISSION_APPL_NUMBER = :appl_num;
  • Reporting the distribution of qualifying values by type: SELECT QUALIFYING_TYPE_CODE, COUNT(*), AVG(QUALIFYING_VALUE) FROM IGS.IGS_AD_APPQUAL_CODE GROUP BY QUALIFYING_TYPE_CODE;
  • Resolving the qualifying code description via join to IGS_AD_CODE_CLASSES on QUALIFYING_CODE_ID.
  • Auditing row change history by filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because this is a new transaction table, integrations that load admissions data should insert one row per qualification per application instance, and reporting extracts should key on the five-column primary key.

Related Objects

The documented foreign-key relationships identify the following dependencies:

  • IGS_AD_PS_APPL_INST_ALL — parent application-instance table; joined on PERSON_ID, ADMISSION_APPL_NUMBER, NOMINATED_COURSE_CD, and SEQUENCE_NUMBER (a four-column FK).
  • IGS_AD_CODE_CLASSES — code reference table; joined on QUALIFYING_CODE_ID to resolve qualifying code descriptions.

Additional related objects typically include the IGS admissions application and applicant base views that consume IGS_AD_PS_APPL_INST_ALL, together with the standard admissions inquiry and reporting concurrent programs that read qualification values for decision processing. Actual column definitions, index composition, and constraint names should be verified against the ETRM and the target instance, since the 12.1.1 and 12.2.2 schemas are expected to be consistent for this object.