Search Results display_name_ind

Overview

IGS.IGS_LOOKUPS_IND is a reference and control table within the Oracle E-Business Suite (EBS) Student Systems / Oracle Student System (IGS) schema. It acts as a behavioral profile registry for QuickCode lookup types used throughout the academic and student information model. Rather than holding transaction data, the table stores indicator flags that describe the capabilities, constraints, and processing semantics of each lookup type. Where the generic FND_LOOKUPS infrastructure defines the available codes and their translated meanings, IGS_LOOKUPS_IND answers a different question: what does a given lookup type permit or require in the academic domain? Consumers of this table therefore include validation routines, enrollment processing, transcript generation, fee assessment logic, and completion-requirement checks in release 12.1.1 and 12.2.2.

From a Data Vault modeling perspective, IGS_LOOKUPS_IND is best treated as a standalone hub-like reference object rather than a link or satellite. It has no dependent child relationships recorded in the metadata and anchors a single natural business key, so it can be modeled as a hub on LOOKUP_TYPE with descriptive indicators carried either alongside or in a satellite separated by change semantics.

Key Information Stored

The table is keyed by LOOKUP_TYPE, a VARCHAR2(30) column documented as the QuickCode lookup type and enforced by primary key IGS_LOOKUPS_IND_PK and unique index IGS_LOOKUPS_IND_U1. Because the primary key is the business key itself, there is no separate surrogate identifier in this design; LOOKUP_TYPE is both the natural and the physical key. The remaining twenty-six columns are indicator attributes, most of them VARCHAR2 flags whose presence signals whether a particular capability applies to the lookup type. The most significant include:

• SECURITY_ALLOWED_IND — whether security controls are applied to the lookup type.
• ACADEMIC_TRANSCRIPT_IND — the flag the user search referenced; identifies lookup types used in academic transcript processing.
• AV_TRANSCRIPT_DISP_OPTIONS_IND — governs availability of transcript display options, complementing the academic transcript flag.
• UNIT_OUTCOME_IND — marks lookup types that represent unit outcomes.
• CMPLTN_REQUIREMENTS_IND — identifies lookup types participating in completion-requirement logic.
• FEE_AS_IND — indicates fee assessment relevance.
• FINAL_RESULT_IND — flags lookup types used for final result recording.
• STEP_TYPE_RESTRICTION_NUM_IND, STEP_ORDER_APPLICABLE_IND, STEP_GROUP_TYPE_IND — control progression-step behavior, ordering, and grouping.
• TRANSACTION_CAT_IND and ENCUMBRANCE_LEVEL_IND — identify transaction categorization and hold or encumbrance level semantics.
• SYSTEM_GENERATED_IND, SYSTEM_CALCULATED_IND, SYSTEM_MANDATORY_IND — distinguish rows that originate from system processing versus user configuration.
• DISPLAY_NAME_IND, DISPLAY_ORDER_IND, DEFAULT_DISPLAY_SEQ_IND — control presentation attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

Typical usage resolves a lookup type to its behavioral flags before processing. A query such as the following returns the transcript-relevant lookup types:

• SELECT lookup_type FROM igs_lookups_ind WHERE academic_transcript_ind = 'Y';
• SELECT lookup_type, fee_as_ind, final_result_ind FROM igs_lookups_ind WHERE lookup_type = :p_lookup_type;
• SELECT l.lookup_type, l.meaning FROM fnd_lookups l, igs_lookups_ind i WHERE l.lookup_type = i.lookup_type AND i.cmpltn_requirements_ind = 'Y';

These patterns support reporting on which lookup types drive transcript output, fee processing, or completion checking, and are commonly embedded in concurrent programs, OAF pages, and validation APIs.

Related Objects

The metadata documents a foreign key relationship between IGS_LOOKUPS_IND and FND_LOOKUPS_TYPE, joined on the column LOOKUP_TYPE. The historical system tables from the original academic data model were merged into FND_LOOKUPS, so the primary related objects are:

• FND_LOOKUPS — the values and translated meanings for each lookup, joined on LOOKUP_TYPE.
• FND_LOOKUPS_TYPE (and the underlying FND lookup type definitions) — the referenced parent on LOOKUP_TYPE.
• IGS_LOOKUPS_IND_U1 / IGS_LOOKUPS_IND_PK — the unique and primary key constraints on LOOKUP_TYPE.
• Student System validation and enrollment APIs that dereference these indicator flags during processing.
• Transcript and completion-requirement query views that consume ACADEMIC_TRANSCRIPT_IND, AV_TRANSCRIPT_DISP_OPTIONS_IND, and CMPLTN_REQUIREMENTS_IND.

The table is stored in the APPS_TS_TX_DATA tablespace with the index in APPS_TS_TX_IDX, and is classified as VALID in the ETRM 12.1.1 documentation.