Search Results csi_lookups




Overview
Explore in AI Chat

Overview

CSI_LOOKUPS is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the CSI (Install Base) product family, which manages customer product instances, installed items, and supporting reference data. As its description states, the view exposes "Install Base Lookups" — the set of Oracle Application Object Library lookup values that the Install Base module uses to drive its list-of-values, status indicators, and coded reference fields.

Functionally, CSI_LOOKUPS is a filtered projection over the central FND_LOOKUP_VALUES table rather than an independent data store. It presents the lookup codes relevant to the Install Base application as a self-contained, language-aware recordset. Because the Install Base module is not the applications owner of FND_LOOKUP_VALUES, the view exists to give CSI-specific code and downstream reporting a stable, product-scoped access point to that shared lookup infrastructure, isolated from the many other lookups in the EBS instance.

Underlying Base Objects

The documented definition selects from FND_LOOKUP_VALUES, referenced in the metadata as FND_LOOKUP_VALUES (SYNONYM), meaning the APPS synonym resolves to the underlying Oracle Application Object Library lookup-values table. Two predicates define the view's scope:

  • Language filter: LV.LANGUAGE = USERENV('LANG') restricts rows to the session language, so multilingual lookup meanings are returned in the runtime language of the connected user or concurrent request.
  • Application filter: LV.VIEW_APPLICATION_ID = 542 restricts rows to Install Base lookups, since 542 is the application identifier for the CSI product.

All twenty-nine exposed columns map one-to-one to columns of FND_LOOKUP_VALUES; the view performs no join, aggregation, or transformation, functioning as a scoped alias of the base table.

Key Columns

The view's primary key in practice is the combination of LOOKUP_TYPE and LOOKUP_CODE. LOOKUP_TYPE identifies the lookup category (for example, codes describing install base statuses or item relationships), while LOOKUP_CODE is the stored value persisted on transactional records. MEANING carries the translatable display text presented in forms and reports; ENABLED_FLAG indicates whether the code is currently usable; and START_DATE_ACTIVE / END_DATE_ACTIVE bound the effective-dating window. DESCRIPTION, TAG, and ATTRIBUTE_CATEGORY with ATTRIBUTE1 through ATTRIBUTE15 provide descriptive and descriptive-flexfield context available for configuration-specific extensions. Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — track who created and last modified each row.

Common Use Cases and Queries

Integration and reporting teams query CSI_LOOKUPS rather than FND_LOOKUP_VALUES directly when they only require Install Base lookups, since the view removes the application filter burden and enforces language selection. Typical uses include decoding a code stored on an Install Base transaction record, populating an extract or interface file with human-readable meanings, and validating that a lookup is enabled and current before mapping source data. A minimal listing:

SELECT lookup_type, lookup_code, meaning, enabled_flag
FROM csi_lookups
ORDER BY lookup_type, lookup_code;

To restrict to active codes across a specific lookup type:

SELECT lookup_code, meaning
FROM csi_lookups
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);

Because the view filters by USERENV('LANG'), multilingual deployments should note that concurrent extracts inherit the language of the run-time environment; use a session-language override when a specific language output is required. The view is read-only, so all maintenance is performed on FND_LOOKUP_VALUES through the standard Application Object Library forms.