Results for “igr_i_e_chartyp”

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

Overview

The IGR_I_E_CHARTYP table belongs to the Oracle E-Business Suite IGS — Student System (Obsolete) product family and describes the characteristics of an enquirer to the institution. In functional terms, it functions as a reference or lookup table: each row defines one valid enquiry characteristic type that can be associated with an enquirer record during the admissions or enquiry-capture process.

The ETRM metadata records the object as Not implemented in this database, and it is documented as obsolete in both Oracle EBS 12.1.1 and 12.2.2. Its presence in the ETRM dictionary therefore serves a discovery and lineage purpose rather than an active configuration purpose; the table is not expected to hold runtime data in a standard R12.1.1 or R12.2.2 instance.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. Under a Data Vault modeling suggestion, this indicates the table has no outgoing foreign keys to other documented objects and behaves more like an independent reference set. It should not be treated as a link table, since it does not resolve relationships between two hubs, nor as a dependent satellite, since it owns its own primary key. A modeler would typically represent it as a small, self-contained reference or hub-style construct keyed on the characteristic type itself.

Key Information Stored

The documented physical schema exposes eight columns under the IGS owner. The most significant are:

• ENQUIRY_CHARACTERISTIC_TYPE — the business identifier for the characteristic type, and the column on which the unique index IGR_I_E_CHARTYP_PK is defined. Despite the “_PK” suffix naming convention for the index, the metadata identifies this column as the business-key candidate rather than documenting a separate system-generated surrogate key.
• DESCRIPTION — the human-readable label describing the enquiry characteristic, used in list-of-values presentation and reporting.
• CLOSED_IND — an active/inactive flag controlling whether the characteristic type remains selectable for new enquiry records.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — the standard Oracle EBS audit columns recording who created and last modified the row, and when.
• LAST_UPDATE_LOGIN — the login identifier associated with the most recent update, supporting audit and troubleshooting.

Common Use Cases and Queries

Because the object is obsolete and not implemented, the practical use cases are largely investigative: confirming whether legacy enquiry-capture configuration existed, verifying schema lineage during upgrades, or validating that no dependent objects still expect data.

A typical lookup pattern retrieves active characteristic types together with their descriptions:

SELECT enquiry_characteristic_type, description
FROM   igr_i_e_chartyp
WHERE  closed_ind = 'N'
ORDER  BY enquiry_characteristic_type;

An existence check is equally common when assessing migration impact:

SELECT COUNT(*)
FROM   igr_i_e_chartyp;

Reporting use cases include reconciling enquiry characteristic exposure against downstream admissions listings, and auditing the creation and update history using the standard audit columns.

Related Objects

The supplied relationship data classifies the table as standalone, meaning no foreign keys were mined from this object’s structure. Consequently, related objects must be inferred functionally rather than through documented join columns. The most significant candidates in the IGS enquiry family include enquirer and enquiry capture tables that would reference ENQUIRY_CHARACTERISTIC_TYPE as a descriptive attribute, institution and admission-period reference tables that scope enquiry activity, and the concurrent programs and value sets used to populate and present the list of characteristic types. Any integration point should first verify whether target objects still resolve against IGR_I_E_CHARTYP before assuming a live dependency, given its obsolete and unimplemented status.