Search Results igs_lookup_values




Overview
Explore in AI Chat

Overview

The IGS_LOOKUP_VALUES view is a legacy database object associated with the IGS – Student System product family (Oracle Student System / Oracle Student Administration), a module that is designated as obsolete in the Oracle E-Business Suite 12.1.1 and 12.2.2 documentation set. Functionally, the view exposes a filtered subset of Oracle Application Object Library (FND) lookup values that pertain specifically to the IGS schema, gated on the IGS application identifier. It behaves in the same manner as other product-scoped lookup views across EBS, which allow reports, concurrent programs, and integration interfaces to retrieve valid list-of-values entries without querying the shared FND_LOOKUP_VALUES table directly.

In ETRM documentation the object is marked "Not implemented in this database," and its documented view metadata lists no referenced base objects. Its practical role surfaces only in environments where the IGS product has been installed and staged with lookup data; elsewhere the view exists as a definitional artifact rather than an operational one.

Underlying Base Objects

Although the metadata excerpt lists no base objects, the documented view text makes the dependency explicit: the view is defined over FND_LOOKUP_VALUES in the FND application. The WHERE clause applies three predicates to that table:

  • LANGUAGE = USERENV('LANG') — restricts results to the current session language, preserving multilingual lookup meanings.
  • VIEW_APPLICATION_ID = 8405 — restricts rows to the IGS application, whose registered application ID is 8405.
  • SECURITY_GROUP_ID = 0 — excludes security-group-specific (partitioned) lookup data and returns only the shared, non-secured rows.

The absence of documented base objects in the ETRM metadata suggests that the view definition was not materially instantiated in the reference database. Where the IGS product is deployed, the underlying object is always FND_LOOKUP_VALUES, the central repository for all seeded and user-defined lookup codes in EBS.

Key Columns

The view projects ten columns from FND_LOOKUP_VALUES:

  • LOOKUP_TYPE — the lookup category (e.g., a code such as a student status or admission type), keyed to the IGS application.
  • LOOKUP_CODE — the internal code value, unique within its lookup type.
  • MEANING — the display-meaning shown to end users on forms and reports.
  • CLOSED_IND — a derived indicator produced by DECODE(LV.ENABLED_FLAG,'Y','N','N','Y','N'); it inverts the enabled flag so that disabled values carry a Closed indicator.
  • ENABLED_FLAG — the source flag (Y/N) governing whether the lookup value is active.
  • DESCRIPTION — free-text description of the lookup value.
  • START_DATE_ACTIVE and END_DATE_ACTIVE — the effective date range controlling when the value is usable.
  • TAG — the optional tag column used for additional classification or filtering.

Common Use Cases and Queries

Typical usage mirrors that of other application-scoped lookup views: populating report lists of values, supplying integration extracts with valid codes and meanings, and supporting migration or data-quality checks against IGS-relevant lookups.

Example — retrieve all active IGS lookup values for a given lookup type:

SELECT lookup_type, lookup_code, meaning, description, start_date_active, end_date_active FROM igs_lookup_values WHERE lookup_type = :p_lookup_type AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

Example — an extract joining the view to a business entity to resolve coded meanings:

SELECT e.entity_id, lv.meaning FROM igs_entity e, igs_lookup_values lv WHERE lv.lookup_type = 'IGS_ENTITY_STATUS' AND lv.lookup_code = e.status_code AND lv.enabled_flag = 'Y';

Because the view is obsolete and documented as not implemented, teams should confirm the view's existence and content in the target instance, and prefer supported replacement objects where IGS functionality has been superseded.