Search Results action_nav

Overview

APPS.CZ_ACTIONNAV_LKV is a restricted lookup view shipped with the Oracle E-Business Suite application schema. It exposes a filtered subset of the generic lookup values repository, returning only those rows whose list name is ACTION_NAV. As the "_LKV" suffix implies, the object is a lookup values view rather than a physical table: it carries no storage of its own and derives every row at runtime from its single documented base object.

Within the ETRM 12.1.1 / 12.2.2 codebase the view functions as the sanctioned read interface for the ACTION_NAV lookup type. Application logic, concurrent programs, and reporting layers use it to resolve navigation action codes into their descriptive labels, sequence positions, and translated text without issuing direct queries against the underlying lookup tables. Because the list name is hard-coded in the view definition, callers cannot accidentally retrieve unrelated lookup types, which enforces consistency wherever navigation actions are presented to users.

Underlying Base Objects

The view is owned by APPS and is defined over exactly one documented referenced base object: CZ_LOOKUP_VALUES_VL (VIEW). No base tables are referenced directly. CZ_LOOKUP_VALUES_VL is the multilingual, translation-aware view over the core lookup values entity; it joins the language-independent lookup values table with its translations so that each row returns the appropriate VALUE_LABEL, VALUE_DESCRIPTION, and VALUE_NOTES for the session language, together with the SOURCE_LANG indicator.

Because the dependency chain passes through a "_VL" (view with language) object, APPS.CZ_ACTIONNAV_LKV inherits full multilingual behavior. Consumers receive translated descriptions automatically through the standard EBS language mechanism, with no additional join required. The relationship is strictly one-to-one in structure: every column exposed by APPS.CZ_ACTIONNAV_LKV is projected from CZ_LOOKUP_VALUES_VL, with the sole filter predicate restricting output to LIST_NAME = 'ACTION_NAV'.

Key Columns

• LIST_NAME — The lookup type identifier. Always evaluates to ACTION_NAV in this view; retained as a column for joining and for cosmetic consistency with other lookup views.
• DATA_VALUE — The internal, language-independent code stored on transactional and configuration records. This is the value that application logic matches against.
• NUMERIC_ID_VALUE — A numeric representation of the identifier, useful where numeric keys are required or for sequencing and comparison operations.
• VALUE_SEQ — The display sequence controlling the order in which navigation actions are presented in lists of values and menus.
• DATA_TYPE_ID — Identifier describing the data type of the lookup value, supporting validation and typed handling.
• NULL_VALUE_FLAG — Flag indicating whether the value qualifies as a NULL-equivalent entry for the lookup type.
• VALUE_LABEL — The translated, user-facing label shown in forms, reports, and inquiry screens.
• VALUE_DESCRIPTION — The translated longer description of the navigation action.
• VALUE_NOTES — Free-form translated notes maintained with the lookup value.
• LANGUAGE and SOURCE_LANG — The language of the returned row and the source language of the underlying translation, enabling language-aware reporting.

Common Use Cases and Queries

Typical uses include validating an ACTION_NAV code entered or imported from an external system, rendering the navigation action list of values in a custom form or OAF page, and producing reference reports that document the configured navigation actions and their translations.

Retrieve all navigation actions in display order:

SELECT data_value, value_label, value_description, value_seq
FROM   apps.cz_actionnav_lkv
ORDER  BY value_seq;

Resolve a single code to its translated label:

SELECT value_label
FROM   apps.cz_actionnav_lkv
WHERE  data_value = :p_action_code;

Confirm multilingual coverage for a given language:

SELECT data_value, value_label, language
FROM   apps.cz_actionnav_lkv
WHERE  language = 'US';

Because the view already restricts LIST_NAME to ACTION_NAV, no additional lookup-type predicate is required, and all queries inherit the translated values supplied by CZ_LOOKUP_VALUES_VL.