Results for “code_id”

50+ results




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

Overview

IGS_AD_CODE_CLASSES is a reference (lookup) table within the Oracle E-Business Suite IGS — Student System product family. Per the documented metadata, it holds information about different codes, the class to which each code belongs, and the associated description. In practice, it functions as a centralized code-value repository for the Admissions (IGS_AD) sub-module, allowing numerous applicant, recruitment, transcript, and test-result tables to resolve a short code or surrogate identifier against a meaningful, class-scoped descriptive value.

The metadata records the product as IGS — Student System (Obsolete), and implementation notes state the table is "Not implemented in this database" in the reference environment. In environments where the legacy Student System was licensed, this table remains the backbone of Admissions code maintenance. Based on the mined foreign-key structure, the heuristic Data Vault classification is hub — the table sits at the center of a large reference web, with dozens of dependent tables pointing to it as the authoritative source of a single code dimension.

Key Information Stored

The table carries 13 documented columns. The most consequential are:

  • CODE_ID — surrogate primary key, defined by the unique index IGS_AD_CODE_CLASSES_PK. Foreign keys throughout the schema resolve to this numeric identifier.
  • NAME — the code value (short identifier or mnemonic) presented to users and stored on dependent tables.
  • CLASS — the category that groups related codes; together with NAME it forms the business-key basis.
  • CLASS_TYPE_CODE — a further discriminator within CLASS; part of the second unique index.
  • DESCRIPTION — the human-readable long description displayed in forms and reports.
  • CLOSED_IND — flags codes that should no longer be selectable for new transactions.
  • SYSTEM_STATUS and SYSTEM_DEFAULT — distinguish seeded/system codes and the default code within a class.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard Oracle EBS audit and who-columns.

The business-key candidate is captured by unique index IGS_AD_CODE_CLASSES_U1 on NAME, CLASS, CLASS_TYPE_CODE, meaning a code name is unique only within its class and class-type combination. The surrogate CODE_ID is the join column used by foreign keys, distinguishing the physical key from the logical business key.

Common Use Cases and Queries

Typical scenarios include validating that a given code is still open, resolving a code ID to its description for reporting, and enumerating all values within a class for a value-list (LOV). Representative patterns:

  • Resolving a description for a recruitment row: SELECT c.NAME, c.DESCRIPTION FROM IGS_AD_CODE_CLASSES c, IGS_AD_RECRUITMENTS r WHERE r.DEGREE_GOAL_ID = c.CODE_ID;
  • Listing active codes in a class: SELECT NAME, DESCRIPTION FROM IGS_AD_CODE_CLASSES WHERE CLASS = :p_class AND NVL(CLOSED_IND,'N') = 'N' ORDER BY NAME;
  • Locating the system default for a class: SELECT CODE_ID, NAME FROM IGS_AD_CODE_CLASSES WHERE CLASS = :p_class AND SYSTEM_DEFAULT = 'Y';
  • Detecting unused codes by anti-joining dependent tables such as IGS_AD_APPL_EVAL or IGS_AD_ACAD_HONORS.

Reporting use cases span admissions funnel analysis, recruitment source attribution, transcript source breakdowns, and test-result grade distribution, each of which resolves descriptive labels through this table.

Related Objects

The metadata documents an extensive FK web. The most significant dependents, with actual join columns, include:

These relationships confirm the hub role: IGS_AD_CODE_CLASSES supplies the shared code dimension against which admissions, recruitment, testing, and transcript transactions are validated and reported.