Results for “igs_uc_ref_codetyps”

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

Overview

IGS_UC_REF_CODETYPS is a reference (lookup) table in the Oracle E-Business Suite Student System (IGS) product family, owned by the IGS schema. Its documented purpose is to hold the list of reference code types used by IGS_UC_REF_CODES. The table carries a status of VALID in the data dictionary, but the ETRM documentation explicitly marks the object as OBSOLETE, indicating that it is retained for backward compatibility and historical data integrity rather than for active functional use in current 12.1.1 or 12.2.2 implementations.

From a dimensional modeling perspective, the mined Data Vault classification is hub-leaning. This suggests modeling IGS_UC_REF_CODETYPS as a hub entity keyed on CODE_TYPE, with descriptive attributes such as DESCRIPTION captured in an associated satellite. The classification aligns with the table's role as a code-type registry whose single column value forms the grain of the entity and serves as the target of a foreign key from a dependent reference table.

Key Information Stored

The documented physical schema for 12.1.1 records seven columns. The most significant are:

• CODE_TYPE — The primary key column and the sole business-key candidate, enforced by both the primary key constraint IGS_UC_REF_CODETYPS_PK and the unique index IGS_UC_REF_CODETYPS_U1. It identifies a category or class of reference codes.
• DESCRIPTION — The meaningful, user-facing label describing the code type. This is the principal descriptive attribute carried by the table.
• CREATED_BY, CREATION_DATE — Standard Oracle EBS audit columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns recording the most recent modification user, timestamp, and login context.

No surrogate numeric identifier is documented; CODE_TYPE fills both the primary-key and business-key roles. The absence of additional descriptive columns reinforces the hub-plus-satellite interpretation, where DESCRIPTION is the only non-key, non-audit attribute.

Common Use Cases and Queries

Because the table enumerates valid code types, typical usage centers on validation, lookup decoding, and dependency analysis of IGS_UC_REF_CODES. A common pattern joins the two tables to resolve code descriptions:

• Listing all defined code types: SELECT code_type, description FROM igs.igs_uc_ref_codetyps;
• Resolving code values with their type description: SELECT r.code_type, t.description, r.code, r.description FROM igs.igs_uc_ref_codes r, igs.igs_uc_ref_codetyps t WHERE r.code_type = t.code_type;
• Validating referential integrity: identifying orphaned code types via an outer join between IGS_UC_REF_CODES and this table.

Reporting use cases include generating a domain catalog of reference code types, auditing which code types are populated versus merely defined, and supporting migration or archival analysis given the OBSOLETE designation.

Related Objects

The documented foreign-key relationship establishes the principal dependency:

• IGS_UC_REF_CODES — References IGS_UC_REF_CODETYPS via IGS_UC_REF_CODES.CODE_TYPE → IGS_UC_REF_CODETYPS.CODE_TYPE. This is the sole documented foreign key and the reason the table exists as a code-type registry.
• Other IGS Student System reference and admissions tables (for example, related UC reference and lookup objects within the IGS_UC_* namespace) may consume the same code-type conventions, though only IGS_UC_REF_CODES is documented here.

The constraint IGS_UC_REF_CODETYPS_PK and unique index IGS_UC_REF_CODETYPS_U1 are the enforcement objects most relevant to developers and DBAs working with this table.