Results for “igs_rc_i_entry_lvls”

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

Overview

The IGS_RC_I_ENTRY_LVLS table is a component of the Oracle Student System (IGS) inquiry management schema, referenced in Oracle E-Business Suite 12.1.1 and 12.2.2 documentation. Its documented description states that it "stores inquiry entry levels," indicating that the table defines the discrete categories or tiers by which prospective-student inquiries are classified. In the broader IGS recruitment and admissions workflow, entry levels serve as a lookup construct that standardizes the way inquiries are grouped — for example, by source, academic intent, or stage of interest — so that downstream processing and reporting can operate on a controlled vocabulary rather than free-text values.

Within the information-modeling framework, the ETRM metadata assigns this object a heuristic Data Vault classification of hub-leaning. This is a modeling suggestion rather than a mandated design: the table exhibits the characteristics of a hub because its primary key is a surrogate identifier (INQ_ENTRY_LEVEL_ID) and it carries a complementary unique business key (INQ_ENTRY_LEVEL), while other tables reference it through that surrogate. Practitioners building a Data Vault or dimensional model over IGS data may therefore treat it as a reference hub or lookup dimension.

It is important to note that the metadata explicitly records this table as not implemented in the surveyed database. Organizations searching for it should confirm whether IGS is licensed, installed, and populated in their specific environment before constructing dependent queries or interfaces.

Key Information Stored

The documented column inventory is compact, which is typical of a lookup or reference table. The principal columns are:

• INQ_ENTRY_LEVEL_ID — the surrogate primary key that uniquely identifies each inquiry entry level. It is the column through which child tables establish their relationships.
• INQ_ENTRY_LEVEL — the business-key candidate, carried by the unique index IGS_RC_I_ENTRY_LVLS_UK. This column holds the human-readable entry-level designation used in forms, lists of values, and reports.

The surrogate-to-business-key pairing is the defining structural feature of this table. INQ_ENTRY_LEVEL_ID provides stable, system-generated referential integrity, while INQ_ENTRY_LEVEL supplies the meaningful label that users recognize. Additional descriptive or status columns are not enumerated in the available metadata; implementers should inspect the deployed table definition in their instance to confirm whether audit columns (creation date, created by, last update date, last updated by) or language-specific attributes exist.

Common Use Cases and Queries

The most frequent use of IGS_RC_I_ENTRY_LVLS is as a decoding lookup during inquiry reporting and analysis. A typical pattern joins the entry-level table to the inquiry application table to resolve the surrogate key into a readable label:

• Inquiry listing with descriptive entry levels — join IGS_RC_I_APPL_ALL to IGS_RC_I_ENTRY_LVLS on INQ_ENTRY_LEVEL_ID to present applicant inquiries alongside their entry-level descriptions.
• Validation and LOV population — populate inquiry entry-level list-of-values and validation routines from the unique key INQ_ENTRY_LEVEL.
• Extract, transform, and load (ETL) reference data — load this table into a warehouse as a small conformed dimension keyed by INQ_ENTRY_LEVEL_ID, supporting drill-down by entry level across inquiry and application facts.
• Data-quality reconciliation — identify orphan records or null entry-level references in IGS_RC_I_APPL_ALL by comparing against the primary key set.

Because the table is described as obsolete and may be unpopulated, queries should be written defensively, with outer joins from the transactional table to avoid dropping inquiry rows that lack a matching entry level.

Related Objects

The documented foreign-key metadata identifies the principal dependency on this table:

• IGS_RC_I_APPL_ALL — holds inquiry application records and references IGS_RC_I_ENTRY_LVLS through the column INQ_ENTRY_LEVEL_ID. This is the primary child table and the main point of join for reporting.
• IGS_RC_I_ENTRY_LVLS_PK — the primary-key constraint on INQ_ENTRY_LEVEL_ID.
• IGS_RC_I_ENTRY_LVLS_UK — the unique constraint on INQ_ENTRY_LEVEL, enforcing uniqueness of the business key.

Given the limited metadata, related IGS recruitment and inquiry objects (such as other inquiry setup tables and student-system inquiry views) should be confirmed by reviewing the deployed schema. In practice, the meaningful join surface for this reference table is concentrated in IGS_RC_I_APPL_ALL.