Results for “igs_in_enq_status_u1”

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

Overview

IGS.IGS_IN_ENQ_STATUS is a foundational setup table within the Oracle E-Business Suite Student System (formerly Oracle Student System, delivered under the IGS schema). It stores the institution-defined enquiry statuses that describe the state of an institution's response to an admission enquiry. Enquiries represent prospective student or applicant interactions prior to formal application, and each enquiry carries a status that reflects whether it has been, for example, registered, acknowledged, or completed.

The design intent of this table is to give institutions flexibility in naming and describing their own statuses while retaining a controlled vocabulary for reporting and integration. Every institution-defined row must map back to one of the system-defined statuses held in the S_ENQUIRY_STATUS column (registered, acknowledged, or complete). This dual-layer approach supports local administrative language without breaking delivered enquiry logic, workflow routing, or applicant-facing communication.

The table resides in the APPS_TS_TX_DATA tablespace in the IGS schema and is registered in FND Design Data as IGS.IGS_IN_ENQ_STATUS. Its documented status is VALID, and the object is described as standalone in the relationship metadata, meaning it holds no outbound foreign keys to other tables. From a heuristic Data Vault modeling perspective, this object is best classified as a hub-style reference table: it owns a durable business key (ENQUIRY_STATUS) with descriptive attributes attached directly, and it participates as a lookup dimension rather than as a transactional fact or link.

Key Information Stored

The table contains nine documented columns. The most business-critical are:

• ENQUIRY_STATUS (VARCHAR2(10)) — The primary business key and the column carrying the unique index IGS_IN_ENQ_STATUS_U1. It identifies the institution-defined enquiry status code used on enquiry records. The primary key constraint IGS_IN_ENQ_STATUS_PK is defined on this column.
• S_ENQUIRY_STATUS (VARCHAR2(30)) — The system-defined status to which the user-defined status maps. Valid values are the delivered system statuses such as acknowledged, registered, or complete. This column is the principal control point for delivered enquiry processing and reporting.
• DESCRIPTION (VARCHAR2(60)) — A human-readable explanation of the enquiry status, presented to users in enquiry maintenance forms and in reference reports.
• CLOSED_IND (VARCHAR2) — An indicator marking whether the status is open or closed. When the closed checkbox is ticked in the maintenance form, the status can no longer be applied to new or modified enquiry records, effectively retiring it without deletion.
• Standard Who columns — LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, CREATION_DATE, LAST_UPDATED_BY, and CREATED_BY provide the audit trail used by Oracle EBS concurrency, audit, and date-tracked reporting conventions. These are mandatory in EBS data-modeling standards and are populated automatically by the Forms and OAF layers.

No surrogate numeric identifier is present; the VARCHAR2 code column serves simultaneously as primary key and unique business key, a common pattern in EBS setup tables.

Common Use Cases and Queries

Typical usage falls into three categories. First, enquiry administration: institutions maintain this table through the delivered enquiry status setup form, adding institution-specific statuses and mapping each to a system status. The CLOSED_IND flag controls whether a status remains selectable on enquiry records.

Second, validation lookups: enquiry entry and update processes validate the entered status against this table and derive the canonical S_ENQUIRY_STATUS for downstream processing, such as enquiry-to-application conversion and admissions funnel reporting.

Third, reporting on enquiry pipelines. A common query lists active statuses and their system mappings:

• SELECT ENQUIRY_STATUS, DESCRIPTION, S_ENQUIRY_STATUS, CLOSED_IND FROM IGS.IGS_IN_ENQ_STATUS WHERE CLOSED_IND = 'N' ORDER BY S_ENQUIRY_STATUS, ENQUIRY_STATUS;

Aggregate reporting typically groups enquiry records by S_ENQUIRY_STATUS to normalize institution-specific values into the three delivered categories. A configuration audit query can identify statuses where the mapping is missing or inconsistent:

• SELECT ENQUIRY_STATUS, S_ENQUIRY_STATUS FROM IGS.IGS_IN_ENQ_STATUS WHERE S_ENQUIRY_STATUS IS NULL;

Because the table is queried directly from the APPS schema in most sites, join performance relies on IGS_IN_ENQ_STATUS_U1 in APPS_TS_TX_IDX.

Related Objects

The metadata records no outbound foreign keys from IGS.IGS_IN_ENQ_STATUS, so related objects are those that reference it or that feed it with system status values:

• APPS.IGS_IN_ENQ_STATUS — The APPS-synonym/view layer that exposes the IGS base table to application code and concurrent programs.
• Enquiry header and enquiry detail tables in the IGS schema — These carry an enquiry status column populated from ENQUIRY_STATUS, joined on ENQUIRY_STATUS = enquiry_status.
• Enquiry status setup forms and OAF pages — Delivered maintenance interfaces that insert, update, and retire rows in this table.
• System-defined status reference values — The delivered lookup or validation source supplying the acknowledged, registered, and complete values used by S_ENQUIRY_STATUS.
• FND Design Data registration IGS.IGS_IN_ENQ_STATUS — The AOL registration that governs upgrade and patch handling of the object.

Because the table is standalone, integration efforts should treat it as a configuration dimension rather than a transactional source.