Search Results exn_expr_type




Overview
Explore in AI Chat

Overview

APPS.CZ_EXNEXPRTYPE_LKV is a lookup view shipped with the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 ETRM (E-Business Tax and configuration) schema. The object is owned by the APPS schema and is classified as a view, not a table. Its purpose is to expose the subset of lookup values belonging to the lookup type EXN_EXPR_TYPE, filtering the shared lookup-values dictionary to a single list name. In practice, this view gives reporting and integration developers a stable, read-only interface for the expression-type enumeration used by EBS tax and configuration modules, without requiring them to know the internal filtering predicate against the generic lookup table.

The view is referenced by the metadata under the search term "exn_expr_type", which corresponds directly to the LIST_NAME constant embedded in the view definition. Because the object is a view over a view, it carries no independent storage and always returns the current contents of the underlying lookup dictionary at query time.

Underlying Base Objects

The ETRM metadata documents exactly one referenced base object: CZ_LOOKUP_VALUES_VL, itself a view. CZ_EXNEXPRTYPE_LKV is therefore defined entirely over that object, applying a single-row-filter predicate.

The view definition, as documented, is:

All columns are projected unchanged; there are no expressions, joins, or aggregations. The only transformation is the constant filter on LIST_NAME. This makes the view a thin, deterministic slice of the lookup framework.

Key Columns

  • LIST_NAME — The lookup type identifier. For every row returned, this value is EXN_EXPR_TYPE, and the column serves as the view's defining filter.
  • DATA_VALUE — The stored, language-independent value of the lookup code. Typically the value identified in tax expression-type logic.
  • NUMERIC_ID_VALUE — A numeric identifier associated with the lookup entry where one is defined.
  • VALUE_SEQ — The sequence number controlling display or processing order of the lookup values.
  • DATA_TYPE_ID — Identifies the data type of the lookup value.
  • NULL_VALUE_FLAG — Indicates whether the lookup entry represents a null/empty value.
  • VALUE_LABEL — The translated, user-facing label for the lookup entry.
  • VALUE_DESCRIPTION — The translated description of the value.
  • VALUE_NOTES — Additional free-text notes attached to the value.
  • LANGUAGE — The language of the returned description and label.
  • SOURCE_LANG — The source language of the underlying lookup record.

Common Use Cases and Queries

Because the view fixes the lookup type, it is convenient in reporting queries that would otherwise need to filter a generic lookup table. A typical reporting query is:

  • SELECT DATA_VALUE, VALUE_LABEL, VALUE_SEQ FROM APPS.CZ_EXNEXPRTYPE_LKV ORDER BY VALUE_SEQ;

An integration or validation scenario may check which expression types are defined or non-null:

  • SELECT DATA_VALUE, VALUE_LABEL FROM APPS.CZ_EXNEXPRTYPE_LKV WHERE NULL_VALUE_FLAG = 'N' ORDER BY VALUE_SEQ;

A language-specific query restricts output to the current session language:

  • SELECT DATA_VALUE, VALUE_LABEL FROM APPS.CZ_EXNEXPRTYPE_LKV WHERE LANGUAGE = USERENV('LANG');

These patterns are appropriate for read-only reporting, list-of-values lookup, and integration extraction of the expression-type enumeration. As with all APPS views, direct DML against the view is not supported; lookup values must be maintained through the standard EBS lookup maintenance function rather than by modifying the view.