Results for “inq_entry_level”
34 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The IGS_AD_I_ENTRY_LVLS table belongs to the IGS product family — the Student System module — within Oracle E-Business Suite 12.1.1 and 12.2.2. The ETRM metadata designates this object as Obsolete, and the implementation notes confirm that it is not implemented in the current database. Its documented purpose is to store inquiry entry levels, meaning the classification codes used to describe the stage or channel through which a prospective student inquiry enters the admissions or recruitment pipeline.
Despite its obsolete status, the object retains a defined physical schema of nine columns, owned by the IGS schema, along with two unique indexes and a primary key constraint. From a Data Vault modeling perspective, the ETRM heuristic classifies this object as hub-leaning. This suggests that if the table were modeled under Data Vault conventions, it would function primarily as a hub — a stable list of unique business keys (entry-level identifiers) with descriptive attributes that could be split into satellites. This classification is a modeling suggestion derived from the foreign-key topology, not a statement of Oracle's internal design.
Key Information Stored
The table's structure centers on the inquiry entry level reference set. The most significant columns are:
- INQ_ENTRY_LEVEL_ID — the surrogate primary key (IGS_AD_I_ENTRY_LVLS_PK) and also the target of unique index IGS_AD_I_ENTRY_LVLS_U1. This is the value propagated into foreign-key references.
- INQ_ENTRY_LEVEL — the business-key candidate, enforced by unique index IGS_AD_I_ENTRY_LVLS_U2. This holds the human-readable or code value that uniquely identifies an entry level.
- DESCRIPTION — the descriptive text explaining what the entry level represents.
- CLOSED_IND — an indicator flagging whether the entry level is closed or inactive, supporting soft retirement of codes rather than deletion.
- CREATED_BY, CREATION_DATE — standard WHO-column audit trail recording the user and timestamp of row creation.
- LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the audit columns capturing the most recent modification, its author, timestamp, and session login context.
The distinction between the surrogate key (INQ_ENTRY_LEVEL_ID) and the business-key candidate (INQ_ENTRY_LEVEL) is important: transactional tables reference the surrogate, while users and reports typically work with the business value.
Common Use Cases and Queries
Because the table is obsolete and absent from implemented databases, its practical role is historical and referential. Typical reporting scenarios would join inquiry records to this table to resolve an entry-level code into its description. A representative pattern, written against the documented column names, is:
- Reference lookup:
SELECT INQ_ENTRY_LEVEL, DESCRIPTION FROM IGS_AD_I_ENTRY_LVLS WHERE CLOSED_IND = 'N'— used to populate a validation list of active entry levels. - Joining to inquiry applications:
SELECT a.*, l.INQ_ENTRY_LEVEL FROM IGS_IN_ENQUIRY_APPL_ALL a, IGS_AD_I_ENTRY_LVLS l WHERE a.INQ_ENTRY_LEVEL_ID = l.INQ_ENTRY_LEVEL_ID— the documented foreign-key relationship. - Audit and data-quality checks on CREATED_BY and LAST_UPDATED_BY to determine when entry-level codes were introduced or revised.
For institutions that still hold historical IGS data, such queries support migration mapping, archival analysis, and reconciliation of legacy admissions reporting.
Related Objects
The documented relationship data identifies one foreign-key relationship, and the surrounding IGS enquiry objects form the meaningful dependency set:
- IGS_IN_ENQUIRY_APPL_ALL — the primary and only documented referencing table. Its column INQ_ENTRY_LEVEL_ID is a foreign key to this table, making the enquiry-application record the transactional consumer of entry-level values.
- IGS_AD_I_ENTRY_LVLS_PK — the primary key constraint on INQ_ENTRY_LEVEL_ID, defining row uniqueness.
- IGS_AD_I_ENTRY_LVLS_U1 — the unique index on INQ_ENTRY_LEVEL_ID.
- IGS_AD_I_ENTRY_LVLS_U2 — the unique index on INQ_ENTRY_LEVEL, the business-key candidate.
No additional views, APIs, or dependent tables are documented for this object in the ETRM metadata. The relationship set is deliberately narrow, consistent with a small reference table whose lifecycle ended when the Student System module was superseded.
-
Stores inquiry entry levels - Obsolete
-
Stores inquiry entry levels
-
This view contains all inquiry entry levels - Obsolete
APPS.IGS_AD_INQ_ENTRY_LEVELS_V·↳ IGS_AD_I_ENTRY_LVLS·Explore IGS module →
-
View: IGR_I_ENTRY_LVLS_V 12.1.1
This view contains all inquiry entry levels
APPS.IGR_I_ENTRY_LVLS_V·↳ IGR_I_ENTRY_LVLS·Explore IGS module →
-
View: IGR_I_APPL_V 12.1.1
This view will be based on OMO public view AS_SALES_LEADS_V and IGR_I_APPL_ALL junction table.
APPS.IGR_I_APPL_V·↳ AMS_LOOKUPS·↳ AMS_P_SOURCE_CODES_V·↳ AS_STATUSES_VL·Explore IGS module →
-
View: IGS_IN_ENQUIRY_APPL_V 12.1.1
Obsolete
APPS.IGS_IN_ENQUIRY_APPL_V·↳ HZ_PARTIES·↳ IGS_AD_CODE_CLASSES·↳ IGS_AD_I_ENTRY_LVLS·Explore IGS module →
-
This view contains all inquiry entry levels - Obsolete
Not implemented in this database·Explore IGS module →
-
View: IGS_RC_I_ENTRY_LVLS_V 12.2.2
This view contains all inquiry entry levels
Not implemented in this database·Explore IGS module →
-
View: IGS_RC_I_ENTRY_LVLS_V 12.1.1
This view contains all inquiry entry levels
Not implemented in this database·Explore IGS module →
-
View: IGR_I_ENTRY_LVLS_V 12.2.2
This view contains all inquiry entry levels
Not implemented in this database·Explore IGS module →
-
TABLE: IGS.IGR_I_ENTRY_LVLS 12.1.1
-
Table: IGR_I_ENTRY_LVLS 12.2.2
Stores inquiry entry levels
Not implemented in this database·Explore IGS module →
-
Table: IGS_AD_I_ENTRY_LVLS 12.2.2
Stores inquiry entry levels - Obsolete
Not implemented in this database·Explore IGS module →
-
Table: IGS_RC_I_ENTRY_LVLS 12.2.2
Stores inquiry entry levels
Not implemented in this database·Explore IGS module →
-
Table: IGS_RC_I_ENTRY_LVLS 12.1.1
Stores inquiry entry levels
Not implemented in this database·Explore IGS module →
-
Lookup Type: INQUIRY_DET 12.2.2
Inquiry Details
-
Lookup Type: INQUIRY_DET 12.1.1
Inquiry Details
-
View: IGS_RC_I_APPL_V 12.1.1
This view will be based on OMO public view AS_SALES_LEADS_V and IGS_RC_I_APPL_ALL junction table.
Not implemented in this database·Explore IGS module →
-
View: IGS_RC_I_APPL_V 12.2.2
This view will be based on OMO public view AS_SALES_LEADS_V and IGS_RC_I_APPL_ALL junction table.
Not implemented in this database·Explore IGS module →
-
View: IGS_IN_ENQUIRY_APPL_V 12.2.2
Obsolete
Not implemented in this database·Explore IGS module →
-
VIEW: APPS.IGR_I_APPL_V 12.1.1
-
View: IGR_I_APPL_V 12.2.2
This view will be based on OMO public view AS_SALES_LEADS_V and IGR_I_APPL_ALL junction table.
Not implemented in this database·Explore IGS module →
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.
-
eTRM - IGS Tables and Views 12.1.1
Holds applicant whose records are wrongly available . It is recommended that such applicant records are deleted from the system . It synchronizes with UCAS view 'ivStarW'.