Search Results ce_lookups




Overview
Explore in AI Chat

Overview

The CE_LOOKUPS view is a Cash Management (CE) product-specific lookup view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the subset of Oracle Application Object Library lookup values that belong to the Cash Management application, providing a stable, product-scoped interface for retrieving enumerated codes and their translations. In the documented metadata, the object is classified as a VIEW with VALID status, and its stated description is simply "Lookup codes."

Rather than requiring developers and report authors to filter the central FND_LOOKUP_VALUES table by application identifier and security group, CE_LOOKUPS encapsulates those restrictions. This makes it the canonical source for Cash Management lookup values used in concurrent programs, Oracle Reports, BI Publisher data models, OAF pages, and integration extracts. Because it is a view, it always reflects the current state of the underlying lookup table without requiring materialization or synchronization.

Underlying Base Objects

The view is defined over a single documented base object: FND_LOOKUP_VALUES, which is referenced in the ETRM metadata as a SYNONYM. The view text provided in the documentation shows a straightforward projection of the core lookup columns from this base, governed by three integrated predicates:

  • LANGUAGE = USERENV('LANG') — restricts rows to the language of the current session, ensuring that MEANING and DESCRIPTION are returned in the user's active language.
  • VIEW_APPLICATION_ID = 260 — the numeric identifier for the Cash Management application, limiting results to CE-owned lookup types only.
  • SECURITY_GROUP_ID = 0 — excludes rows belonging to non-zero security groups, which is consistent with standard Oracle EBS lookup access patterns.

There are no joins, aggregations, or sub-queries in the documented view text, so performance characteristics mirror those of querying FND_LOOKUP_VALUES directly with equivalent filters.

Key Columns

The view exposes seven columns, each inherited directly from the base lookup table:

  • LOOKUP_TYPE — the lookup category (for example, a Cash Management-specific type such as bank account or reconciliation status codes). Combined with LOOKUP_CODE, this forms the logical key.
  • LOOKUP_CODE — the stored, language-independent code value that is persisted on transactional records.
  • MEANING — the translatable, user-facing label associated with the code.
  • DESCRIPTION — an optional longer explanation of the code's purpose.
  • ENABLED_FLAG — indicates whether the lookup value is currently active (Y) or disabled (N).
  • START_DATE_ACTIVE — the date from which the lookup value becomes valid.
  • END_DATE_ACTIVE — the date after which the lookup value is no longer valid; null indicates an open-ended validity period.

Common Use Cases and Queries

Typical uses include decoding stored codes into display values for reports, populating LOVs in custom forms, and validating imported data against enabled Cash Management lookups. A representative query lists all enabled values for a given lookup type:

  • SELECT lookup_code, meaning, description FROM ce_lookups WHERE lookup_type = :p_type AND enabled_flag = 'Y' AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));
  • Joining to a transactional table on lookup_code to translate stored codes for reporting extracts.
  • Distinct lookup types can be enumerated with SELECT DISTINCT lookup_type FROM ce_lookups ORDER BY lookup_type;

Because the view fixes the language to the session locale and restricts rows to application 260, it is best suited to CE-specific reporting and integration rather than cross-application lookup administration.