Search Results cs_lookups




Overview
Explore in AI Chat

Overview

CS_LOOKUPS is a read-only view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents all lookup values that belong to the Service (CS) product, exposing the reference data maintained in the Oracle Application Object Library lookup framework for that application. The view is registered as VALID in the E-Business Suite Technical Reference Manual (ETRM) and is defined over the FND_LOOKUP_VALUES synonym, filtering rows to the Service application context and to the language of the current session.

Because it consolidates lookup metadata into a single, product-scoped projection, CS_LOOKUPS serves as a stable interface for reporting, concurrent programs, personalizations, and integration extracts that need to decode Service lookup codes into their user-facing meanings. Rather than querying FND_LOOKUP_VALUES directly and reproducing the language and application filters, developers reference CS_LOOKUPS to guarantee that only Service lookups are returned and that the correct translated meaning is retrieved.

Underlying Base Objects

The view is defined over the FND_LOOKUP_VALUES synonym, which resolves to the APPLSYS.FND_LOOKUP_VALUES base table maintained by the Application Object Library. FND_LOOKUP_VALUES stores every lookup code across all applications, together with its meaning, description, effective dates, enabled flag, and fifteen descriptive flexfield attribute columns.

The WHERE clause of CS_LOOKUPS constrains the result set in three ways. First, VIEW_APPLICATION_ID is fixed at 170, the application identifier for Service. Second, LANGUAGE is limited to USERENV('LANG'), so each user sees the lookup meaning in the language of the current session. Third, SECURITY_GROUP_ID is compared against the value returned by FND_GLOBAL.LOOKUP_SECURITY_GROUP, a packaged function that enforces lookup-level security. Together these predicates ensure that the view returns only enabled, product-scoped, security-filtered, translated lookup rows. The dependency list documents FND_GLOBAL (PACKAGE) and FND_LOOKUP_VALUES (SYNONYM) as the referenced base objects.

Key Columns

  • LOOKUP_TYPE — the lookup type (the grouping name, such as a Service status or category set) to which the code belongs.
  • LOOKUP_CODE — the internal code stored on Service transactions and entities; joins to application data.
  • MEANING — the user-facing, translated description of the code.
  • DESCRIPTION — optional longer text describing the lookup value.
  • ENABLED_FLAG — indicates whether the lookup value is currently active ('Y') or disabled ('N').
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the lookup value is valid.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment columns for extended lookup attributes.
  • TAG — a free-form tag column available for customer-specific annotation.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN track the record lifecycle.

Common Use Cases and Queries

Typical scenarios include decoding Service lookup codes in reports and OAF/Forms pages, validating which codes are active for a given date range, and extracting translated meanings for data migration or integration into external systems. The following query lists all enabled Service lookups for a specific type:

  • SELECT lookup_code, meaning FROM cs_lookups WHERE lookup_type = 'SERVICE_STATUS' AND enabled_flag = 'Y' ORDER BY lookup_code;
  • SELECT lookup_type, lookup_code, meaning FROM cs_lookups WHERE lookup_type IN ('TASK_PRIORITY','TASK_STATUS') ORDER BY lookup_type, lookup_code;
  • SELECT lookup_code, meaning, start_date_active, end_date_active FROM cs_lookups WHERE enabled_flag = 'Y' AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

Because the view filters on USERENV('LANG') and FND_GLOBAL.LOOKUP_SECURITY_GROUP, results automatically respect the caller's language and security profile, so developers should not add redundant filters for language or security group.