Search Results csc_lookups




Overview
Explore in AI Chat

Overview

CSC_LOOKUPS is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It exposes the set of Oracle Application Object Library (FND) lookup types and lookup codes that are registered against the Customer Care (CSC) product. In the EBS data model, reference code lists are not stored in bespoke CSC tables; instead they are maintained centrally in FND_LOOKUP_VALUES and tagged with a "view application" identifier. CSC_LOOKUPS is the CSC-specific projection of that shared repository, filtering the centralized lookup table by VIEW_APPLICATION_ID = 511, which is the application identifier assigned to Customer Care.

Because the view restricts output to CSC-owned lookups and resolves the language and security context at runtime, it functions as the authoritative, self-documenting source of valid drop-down values for Customer Care functionality — service request categories, statuses, interaction outcomes, and similar code sets. For reporting and integration developers, CSC_LOOKUPS provides a stable, denormalized surface over lookup data without requiring knowledge of the FND_LOOKUP_VALUES internals, enabling BI Publisher reports, OBIEE/OTBI extracts, and inbound/outbound interfaces to validate or translate CSC codes consistently.

Underlying Base Objects

Per the documented metadata, the view is defined over a single referenced base object: FND_LOOKUP_VALUES (accessed through a SYNONYM). The defining query selects from FND_LOOKUP_VALUES with three predicates applied:

  • LANGUAGE = USERENV('LANG') — restricts rows to the session's current language, so MEANING and DESCRIPTION are returned in the user's locale.
  • VIEW_APPLICATION_ID = 511 — restricts rows to lookup values owned by the Customer Care application.
  • SECURITY_GROUP_ID = FND_GLOBAL.LOOKUP_SECURITY_GROUP(LOOKUP_TYPE, VIEW_APPLICATION_ID) — enforces lookup-level security, so only lookup types the current user is entitled to see are exposed.

The view therefore inherits the full column set of FND_LOOKUP_VALUES but narrows the row population to CSC. It carries no storage of its own; all reads are translated into queries against the FND synonym at execution time.

Key Columns

The view reproduces the standard FND_LOOKUP_VALUES column set. The columns most relevant to consumers are:

  • LOOKUP_TYPE — the name of the lookup category (for example, a CSC category or status lookup). Combined with LOOKUP_CODE, it forms the logical key.
  • LOOKUP_CODE — the stored code value used in transactional tables; this is the value persisted on CSC entities.
  • MEANING — the user-facing, translatable display value corresponding to the code.
  • DESCRIPTION — extended translatable text describing the lookup value.
  • ENABLED_FLAG — 'Y' or 'N' indicating whether the value is currently selectable; disabled lookups are retained for historical data integrity.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range during which the value is valid.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments allowing CSC to extend a lookup value with additional context.
  • TAG — a free-form grouping/annotation column on the lookup value.
  • Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — provide standard WHO tracking.

Common Use Cases and Queries

Typical scenarios include validating a code captured from an external system, driving report parameter lists, and reconciling transactional data against its reference values.

  • List all CSC lookup types and their values: 
    SELECT lookup_type, lookup_code, meaning
FROM   apps.csc_lookups
ORDER BY lookup_type, lookup_code;
  • Return only currently active values for a specific lookup type: 
    SELECT lookup_code, meaning
FROM   apps.csc_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);
  • Resolve a stored code to its display meaning for reporting: 
    SELECT t.some_code, l.meaning
FROM   csc_some_table t, apps.csc_lookups l
WHERE  l.lookup_type = 'CSC_SOME_TYPE'
AND    l.lookup_code = t.some_code;

Because the view filters by the session language and applies lookup security group logic, reports executed under a different responsibility or language may return different row sets or translated MEANING values; developers should account for this when comparing output across environments.