Results for “igs_in_enq_char_type”

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

Overview

IGS_IN_ENQ_CHAR_TYPE is a reference (lookup) table within the Oracle E-Business Suite IGS — Student System product family. As documented in the ETRM metadata for releases 12.1.1 and 12.2.2, the entity describes the characteristics of an enquirer to an institution. Typical characteristic values include "School leaver", "Graduate", "Domestic", and "International". The table serves two stated purposes: statistical reporting on the enquirer population, and enabling the institution to tailor admissions or marketing packages to specific enquirer segments.

The metadata flags this object as Obsolete and states "Not implemented in this database." Consultants working on legacy IGS footprints may still encounter it in historical schemas, migration scripts, or data extracts, but it should not be treated as an active configuration object in current implementations. Where present, the heuristic Data Vault classification mined from the foreign-key structure is hub-leaning, so a modeling exercise would treat it as a reference hub keyed on the enquiry characteristic type code, with the dependent application characteristic records acting as satellites or links.

Key Information Stored

The physical schema documented for 12.1.1 records an owner of IGS and a total of eight columns. The essential columns are:

• ENQUIRY_CHARACTERISTIC_TYPE — the business key. It is the single column of the primary key constraint IGS_IN_ENQ_CHAR_TYPE_PK and of the unique index IGS_IN_ENQ_CHAR_TYPE_U1, confirming it as the natural identifier of each characteristic (for example, a school-leaver or international code).
• DESCRIPTION — the human-readable label presented to users when selecting an enquirer characteristic.
• CLOSED_IND — an active/inactive flag used to retire a characteristic from new data entry without deleting historical references.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle EBS "Who" audit columns maintained automatically by the Forms and concurrent manager infrastructure.

The surrogate-versus-business-key distinction is straightforward here: the primary key is the business key itself, with no separate generated identifier. The table is therefore a pure code-and-description lookup rather than a transactional entity.

Common Use Cases and Queries

The principal use case is validation and descriptive lookup when recording enquirer or applicant characteristics. A typical query to populate a list of values might be:

SELECT enquiry_characteristic_type, description
FROM   igs_in_enq_char_type
WHERE  NVL(closed_ind,'N') = 'N'
ORDER  BY description;

Analysts compiling enquiry-source statistics join this table to applicant characteristic records to convert stored codes into readable categories. Joins should always be outer joins, because the foreign key column on the child table may be null for enquirers whose characteristic was never captured. A second scenario is data migration: when extracting legacy IGS enquiry data, this table supplies the decode list required to translate historical characteristic codes before loading them into a successor student system.

Because the object is documented as obsolete and not implemented in the reference database, any query against it must first verify existence in the target instance, for example via ALL_TAB_COLUMNS or ALL_OBJECTS, before it is included in a report or interface.

Related Objects

The documented foreign-key relationship data identifies the tables that depend on this lookup:

• IGS_IN_APPL_CHAR_TYP — the primary dependent object. Its column ENQUIRY_CHARACTERISTIC_TYPE references IGS_IN_ENQ_CHAR_TYPE.ENQUIRY_CHARACTERISTIC_TYPE, so it stores the actual per-applicant or per-enquirer characteristic assignments.
• IGS_IN_ENQ_CHAR_TYPE_PK — the primary key constraint, enforcing uniqueness of the characteristic code.
• IGS_IN_ENQ_CHAR_TYPE_U1 — the unique index on the same column, providing the business-key enforcement and supporting fast lookup by code.

Sibling reference tables in the same IGS enquiry characteristic domain, together with the standard EBS audit and concurrent-program infrastructure, are the remaining dependencies typically encountered. The strongest documented join remains IGS_IN_APPL_CHAR_TYP.ENQUIRY_CHARACTERISTIC_TYPE = IGS_IN_ENQ_CHAR_TYPE.ENQUIRY_CHARACTERISTIC_TYPE.