Search Results igs_in_enq_status




Overview
Explore in AI Chat

Overview

IGS_IN_ENQ_STATUS is a reference table in the IGS (Student System) product family of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It stores user-defined enquiry statuses that describe the state of an enquiry made to an institution — for example, "Registered" or "Acknowledged." Each user-defined status maps onto a system-defined enquiry status, allowing institutions to localize their admissions and enquiry workflow terminology while retaining the seeded status values that the application logic depends on. The ETRM documentation marks the entity as Obsolete, meaning it is retained for backward compatibility and historical reference rather than for new configuration. The table resides in the IGS schema with the primary key constraint IGS_IN_ENQ_STATUS_PK.

From a Data Vault modeling perspective, the mined FK structure classifies this object as standalone. That heuristic suggests treating IGS_IN_ENQ_STATUS as a small reference or hub-like entity rather than a transactional link or satellite; it holds descriptive codes and their attributes without participating in documented foreign key relationships to other tables.

Key Information Stored

The table contains nine documented columns. The most significant are:

  • ENQUIRY_STATUS — The primary key column and business-key candidate, uniquely identified by both IGS_IN_ENQ_STATUS_PK and the unique index IGS_IN_ENQ_STATUS_U1. It carries the user-defined status code.
  • S_ENQUIRY_STATUS — The system-defined enquiry status that the user-defined value maps onto. This is the linkage that preserves application behavior when institutions rename or extend statuses.
  • DESCRIPTION — The descriptive text presented for the user-defined status.
  • CLOSED_IND — A flag indicating whether the status represents a closed state for the enquiry, useful for filtering open versus completed enquiries.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns capturing audit and concurrency information.

The surrogate primary key is represented by the constraint IGS_IN_ENQ_STATUS_PK, while IGS_IN_ENQ_STATUS_U1 on ENQUIRY_STATUS serves as the documented business-key candidate. No foreign keys are documented, consistent with the standalone classification.

Common Use Cases and Queries

Typical usage centers on validation and reporting of enquiry status values. A common query retrieves the user-facing status list with its system mapping:

  • Listing active statuses: SELECT ENQUIRY_STATUS, DESCRIPTION, S_ENQUIRY_STATUS FROM IGS.IGS_IN_ENQ_STATUS WHERE CLOSED_IND = 'N';
  • Resolving the system status behind a user-defined code for integration or reporting consistency.
  • Auditing configuration changes using CREATION_DATE and LAST_UPDATE_DATE to identify recently modified status definitions.
  • Joining to enquiry transaction tables on ENQUIRY_STATUS to produce enquiry pipeline or funnel reports, though such joins rely on application usage rather than documented FK constraints.

Because the entity is obsolete, new development should generally reference the current student system status tables, but legacy reports and interfaces may still depend on these values.

Related Objects

The ETRM metadata documents no foreign keys, so related objects are inferred from the IGS enquiry data model rather than from enforced constraints. Significant objects include:

  • IGS_IN_ENQUIRIES (or equivalent enquiry transaction entity), which references ENQUIRY_STATUS to record the status of each enquiry.
  • System-defined status lookup tables that supply the S_ENQUIRY_STATUS values.
  • IGS admissions and prospect applicant entities that consume enquiry statuses during conversion workflows.
  • IGS lookups and value sets surfaced through the Oracle Forms enquiry maintenance screens.
  • Reporting views in the IGS schema that join status descriptions to enquiry facts.

Analysts should validate actual join columns against the deployed schema, since the standalone classification indicates the relationships are application-level rather than database-enforced.