Search Results igs_lookups_val_u1

Overview

IGS.IGS_LOOKUPS_VAL is an Oracle EBS table owned by the IGS (Student Systems / Higher Education) schema. It serves as a supplementary extension of the FND_LOOKUPS data model, storing lookup validation attributes that could not be merged into the core FND_LOOKUPS table during consolidation of the legacy Student System data model. The table holds QuickCode lookup metadata for academic and enrollment-related lookup types, including flags and ordering controls that drive Student System behavior. It resides in the APPS_TS_TX_DATA tablespace with PCT Free of 10, and its associated unique index lives in APPS_TS_TX_IDX.

The object is marked VALID, and its FND Design Data entry is IGS.IGS_LOOKUPS_VAL. A foreign key relationship exists with FND_LOOKUPS_VAL joined on LOOKUP_TYPE and LOOKUP_CODE, which anchors entries to the standard Oracle lookup validation framework. From a data modeling perspective, the documented relationship structure classifies this object heuristically as a standalone Data Vault entity; the absence of inbound or outbound link dependencies in the mined FK graph suggests it behaves as an independent reference satellite keyed on a composite business key rather than as a hub or transactional link.

Key Information Stored

The table contains 29 columns. The composite primary key IGS_LOOKUPS_VAL_PK is defined on LOOKUP_CODE and LOOKUP_TYPE. A separate unique index, IGS_LOOKUPS_VAL_U1, is defined on LOOKUP_TYPE and LOOKUP_CODE (reverse order), and this index is the object the user searched for. Because the primary key and unique index cover the same two columns, both enforce uniqueness on the business key pair; the unique index acts as the primary business-key candidate for external joins.

The most significant columns include:

• LOOKUP_TYPE (VARCHAR2 30) and LOOKUP_CODE (VARCHAR2 30) — the composite business key identifying each QuickCode lookup within its type.
• CLOSED_IND — flags whether the lookup type is closed.
• SECURITY_ALLOWED_IND — controls whether security is allowed for the lookup type.
• DISPLAY_NAME and DISPLAY_ORDER — presentation attributes for rendering the lookup in the UI.
• UNIT_OUTCOME_IND — controls unit outcome behavior.
• STEP_TYPE_RESTRICTION_NUM_IND, STEP_ORDER_APPLICABLE_IND, and STEP_GROUP_TYPE — govern step sequencing and grouping rules.
• ACADEMIC_TRANSCRIPT_IND and AV_TRANSCRIPT_DISP_OPTIONS — drive academic transcript handling and display.
• CMPLTN_REQUIREMENTS_IND and FEE_ASS_IND — mark completion-requirement and fee-assessment relevance.
• SYSTEM_GENERATED_IND, SYSTEM_CALCULATED, and SYSTEM_MANDATORY_IND — indicate system-controlled entries that should not be manually maintained.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — standard EBS audit columns.

S_TRACKING_TYPE is documented as obsolete and should not be used in new development.

Common Use Cases and Queries

Typical usage centers on resolving lookup attributes for Student System configuration and reporting. A representative query joining to the standard lookup validation table follows:

SELECT lv.lookup_type, lv.lookup_code, lv.display_name, lv.display_order, lv.closed_ind
  FROM igs.igs_lookups_val lv, fnd_lookups_val f
 WHERE lv.lookup_type = f.lookup_type
   AND lv.lookup_code = f.lookup_code
   AND lv.lookup_type = :p_lookup_type
 ORDER BY lv.display_order;

Reporting scenarios include extracting the ordered set of active (non-closed) lookups for a given type, auditing system-generated versus user-maintained entries, and driving enrollment or transcript processing by testing the various indicator flags. Because the unique index IGS_LOOKUPS_VAL_U1 fronts LOOKUP_TYPE and LOOKUP_CODE, point lookups using those two columns are index-driven and efficient.

Related Objects

The most significant related objects are:

• FND_LOOKUPS_VAL — foreign-key parent joined on LOOKUP_TYPE and LOOKUP_CODE; supplies the merged validation attributes.
• FND_LOOKUPS — the consolidated core lookup table into which the original data model was merged.
• IGS_LOOKUPS_VAL_PK — the composite primary key constraint/index on LOOKUP_CODE and LOOKUP_TYPE.
• IGS_LOOKUPS_VAL_U1 — the unique index on LOOKUP_TYPE and LOOKUP_CODE that enforces the business-key candidate.

Because the object is classified as standalone, no additional link dependencies are documented, and consumers should rely on the FND_LOOKUPS_VAL join as the primary integration path.