Results for “ref_code_type”

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

Overview

IGS_UC_EXAM_SCORES is a reference and configuration table within the Oracle E-Business Suite IGS (Student System) product family. It holds records that link to exam level values in IGS_UC_REF_CODES and stores grades and points against those exam levels. The table therefore acts as a lookup-driven mapping between qualification or examination levels and their corresponding scoring outcomes, most commonly used by the UC (Universities and Colleges admissions) data integration functionality to translate external exam results into internally comparable grade and point values.

The ETRM documentation classifies this object as part of IGS - Student System (Obsolete), and the recorded implementation note states that it is "Not implemented in this database." This is a significant caveat: in the environment from which the metadata was mined, the table does not physically exist, indicating a deprecated, unlicensed, or never-installed component. When present, the ETRM 12.1.1 physical schema documents an owner of IGS and ten columns. Based on the foreign key structure, the heuristic Data Vault classification is satellite-leaning, suggesting the table behaves primarily as a descriptive attribute carrier attached to a parent reference-code entity rather than as an independent hub or a pure association link.

Key Information Stored

The table's documented column set includes the following principal attributes:

• EXAM_SCORES_ID — the surrogate primary key, enforced by the IGS_UC_EXAM_SCORES_PK constraint and also supported by the unique index IGS_UC_EXAM_SCORES_U1. This is the system-generated identifier that uniquely distinguishes each row.
• EXAM_LEVEL — identifies the examination or qualification level to which a grade and point value applies.
• REF_CODE_TYPE — the reference-code category that qualifies EXAM_LEVEL, forming the foreign key relationship to IGS_UC_REF_CODES.
• POINTS — the numeric score or tariff points associated with the exam level and grade combination.
• GRADES — the grade value mapped to the exam level.
• CREATED_BY, CREATION_DATE — standard Oracle audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns recording the last modifying user, timestamp, and login context.

The composite unique index IGS_UC_EXAM_SCORES_U2 (EXAM_LEVEL, REF_CODE_TYPE) constitutes the business-key candidate, guaranteeing that each exam level within a given reference-code type appears only once. Distinguishing this business key from the surrogate EXAM_SCORES_ID is essential for any integration or data-migration exercise.

Common Use Cases and Queries

Typical usage centers on translating and validating exam outcomes. Reporting queries join the table back to IGS_UC_REF_CODES to resolve descriptive reference-code meanings, and filter on REF_CODE_TYPE or EXAM_LEVEL to isolate a specific qualification framework. A representative pattern:

• Lookup by business key: SELECT POINTS, GRADES FROM IGS_UC_EXAM_SCORES WHERE EXAM_LEVEL = :level AND REF_CODE_TYPE = :type;
• Reference-code resolution: join IGS_UC_EXAM_SCORES to IGS_UC_REF_CODES on REF_CODE_TYPE = REF_CODE_TYPE to obtain the descriptive text for each exam-level entry.
• Audit and reconciliation: filter on CREATION_DATE or LAST_UPDATE_DATE to identify recently maintained grade/point mappings.

Because the object is obsolete and not implemented, production queries should be preceded by an existence check against the data dictionary before being deployed.

Related Objects

The documented foreign key relationship anchors this table to its parent reference object, and the following are the most significant related objects:

• IGS_UC_REF_CODES — referenced via IGS_UC_EXAM_SCORES.REF_CODE_TYPE (and EXAM_LEVEL), the principal lookup source for reference-code values.
• IGS_UC_EXAM_SCORES_PK — primary key constraint governing EXAM_SCORES_ID.
• IGS_UC_EXAM_SCORES_U1 / IGS_UC_EXAM_SCORES_U2 — unique indexes defining the surrogate and composite business keys respectively.

Other IGS_UC-related configuration tables and validation views that depend on exam-level reference data should also be reviewed when assessing downstream impact, though the documented metadata identifies IGS_UC_REF_CODES as the sole explicitly recorded dependency.