Search Results igs_lookups_ind

Overview

IGS_LOOKUPS_IND is a control table in the IGS (Student System) product schema of Oracle E-Business Suite, documented as VALID in both Release 12.1.1 and 12.2.2. The table governs the behavioral characteristics of lookup types used throughout the student information model. Rather than storing lookup values directly, it carries a matrix of indicator flags that determine how a given lookup type behaves in academic and administrative processing — for example, whether it is security-controlled, whether it participates in step ordering, or whether it is system-generated.

The documentation states that IGS_LOOKUPS_IND has a foreign key relationship with FND_LOOKUPS_TYPE, joined on the LOOKUP_TYPE column, and that the original system tables from the legacy data model were merged into FND_LOOKUPS. IGS_LOOKUPS_IND therefore acts as an extension of the Oracle Application Object Library lookup framework, supplemental to FND_LOOKUPS, retaining IGS-specific indicator semantics that the standard lookup table does not represent.

The metadata records a heuristic Data Vault classification of standalone, with no downstream link relationships mined from the foreign key structure. In keeping with that suggestion, the table is best modeled as a reference or hub-style entity keyed by its business key, with no dependency chain beneath it.

Key Information Stored

The table contains 27 documented columns. Its primary key constraint, IGS_LOOKUPS_IND_PK, is defined on LOOKUP_TYPE, which is also the single column of the unique index IGS_LOOKUPS_IND_U1. Because the primary key is the business identifier itself, there is no separate surrogate key column in this object; LOOKUP_TYPE serves simultaneously as the primary key, the unique business-key candidate, and the join column to FND_LOOKUPS_TYPE.

The remaining columns are indicator flags describing lookup-type behavior. The most significant include:

• SECURITY_ALLOWED_IND — indicates whether security restrictions may be applied to values of this lookup type.
• STEP_TYPE_RESTRICTION_NUM_IND and STEP_ORDER_APPLICABLE_IND — control whether the lookup type is subject to step-type restrictions and whether step ordering applies.
• UNIT_OUTCOME_IND, ACADEMIC_TRANSCRIPT_IND, AV_TRANSCRIPT_DISP_OPTIONS_IND, and FINAL_RESULT_IND — determine inclusion in unit outcome processing and academic transcript presentation.
• CMPLTN_REQUIREMENTS_IND and FEE_AS_IND — govern use in completion requirement and fee assessment contexts.
• DISPLAY_NAME_IND, DISPLAY_ORDER_IND, and DEFAULT_DISPLAY_SEQ_IND — control display naming and ordering behavior.
• SYSTEM_GENERATED_IND, SYSTEM_CALCULATED_IND, and SYSTEM_MANDATORY_IND — identify values produced or required by the system rather than entered by users.
• TRANSACTION_CAT_IND, ENCUMBRANCE_LEVEL_IND, OPEN_FOR_ENROLLMENTS_IND, S_TRACKING_TYPE_IND, and TRACKING_USED_BY_IND — support transaction categorization, encumbrance handling, enrollment availability, and tracking usage.

Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN are also present.

Common Use Cases and Queries

Typical use is validation and resolution of lookup behavior when building student-system reports or extensions. A common pattern joins the indicator table to the standard lookup repository to retrieve both value and behavior:

• Selecting all lookup types that permit security restrictions, to drive value-set or row-level security configuration.
• Identifying system-generated or system-mandatory lookup types so that interface programs can exclude them from user-maintained maintenance screens.
• Determining which lookup types feed academic transcript display, enabling transcript report builders to filter appropriately.
• Auditing indicator settings after an upgrade, since behavioral flags may shift between 12.1.1 and 12.2.2.

A representative query pattern is: SELECT i.lookup_type, i.security_allowed_ind, i.system_generated_ind FROM igs.igs_lookups_ind i WHERE i.security_allowed_ind = 'Y'; — with a further join to FND_LOOKUPS_TYPE on LOOKUP_TYPE when lookup descriptions are required.

Related Objects

The principal documented relationship is with FND_LOOKUPS_TYPE, joined on LOOKUP_TYPE. Because lookup values were merged into FND_LOOKUPS, that table is the natural companion for resolving value-level detail, and its lookup codes are constrained by the types registered here. The primary key constraint IGS_LOOKUPS_IND_PK and unique index IGS_LOOKUPS_IND_U1 enforce uniqueness on LOOKUP_TYPE and thus protect referential integrity for any dependent object. Downstream, IGS product tables and concurrent programs that consume lookup types — for example enrollment, transcript, and completion-requirement processing — rely on the indicator settings recorded here to interpret lookup semantics correctly. No additional foreign keys originating from this table are documented, consistent with its standalone Data Vault classification.