Search Results css_lookups

Overview

CSS_LOOKUPS is a lookup view belonging to the CSS – Support product, an obsolete module within Oracle E-Business Suite originally associated with the Defect Management System. The view exposes lookup types and lookup codes used to drive defect-related validation and reference data. In Oracle EBS 12.1.1 and 12.2.2, lookup views such as this one follow the standard Oracle Application Object Library (FND) pattern: they present a filtered, security-scoped and language-scoped projection of lookup values rather than a physical table of their own.

According to the ETRM documentation metadata, CSS_LOOKUPS is not implemented in this database, and no base objects are documented as referenced. Its definition is therefore preserved only as a historical metadata record. Where the view was deployed, it would have served reporting and integration purposes by supplying the enabled lookup codes for the Defect Management System, allowing concurrent programs, forms, and third-party integrations to resolve code-to-meaning translations consistently.

Underlying Base Objects

The ETRM documentation states that no referenced base objects are documented for this view, and that the view is not implemented in the current database. By convention, a view of this name and shape is defined over the FND_LOOKUP_VALUES and FND_LOOKUPS tables in the Application Object Library schema. The view text excerpt supplied in the metadata does not include the FROM clause, but the WHERE predicate confirms this pattern:

• LANGUAGE = USERENV('LANG') — restricts rows to the session language, sourcing from FND_LOOKUP_VALUES.
• VIEW_APPLICATION_ID = 514 — scopes rows to application 514, the CSS – Support application identifier.
• SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(LV.LOOKUP_TYPE, LV.VIEW_APPLICATION_ID) — enforces the caller's lookup security group, ensuring only authorized lookup types are returned.

The alias LV in the security group function call implies the underlying lookup values table is aliased as LV, consistent with FND_LOOKUP_VALUES. Because the view is obsolete and unimplemented, DBAs should not assume its presence in a production 12.1.1 or 12.2.2 instance; the FND_LOOKUP_VALUES table itself remains the authoritative source.

Key Columns

The documented columns map directly to the standard lookup value structure:

• LOOKUP_TYPE — the lookup category identifier, e.g. a defect status or severity type.
• LOOKUP_CODE — the internal code stored on transactional records.
• MEANING — the user-facing display value translated per session language.
• DESCRIPTION — extended descriptive text for the code.
• ENABLED_FLAG — indicates whether the lookup code is active (Y) or disabled (N).
• START_DATE_ACTIVE — the date from which the code becomes valid.
• END_DATE_ACTIVE — the date after which the code is no longer valid.

Common Use Cases and Queries

The primary use case is converting stored codes into readable meanings in defect reports and interfaces. A representative query follows:

• SELECT lookup_type, lookup_code, meaning FROM css_lookups WHERE enabled_flag = 'Y' AND lookup_type = :p_type;

Additional scenarios include populating value sets for concurrent program parameters, validating inbound interface data against active codes, and generating reference listings for integration extracts. Where the view is absent, the equivalent query against FND_LOOKUP_VALUES with the appropriate VIEW_APPLICATION_ID and language predicates should be substituted.