Search Results action_type_group

Overview

In Oracle E-Business Suite 12.1.1 and 12.2.2, APPS.CZ_ACTIONTYPEGROUP_LKV is a filtered lookup view belonging to the Common Technology Components / ETRM (Enterprise Transaction and Reference Model) layer of the application. Its purpose is to expose a controlled, pre-filtered subset of the seeded lookup values used by the Oracle Applications common lookup infrastructure, specifically those associated with the lookup type ACTION_TYPE_GROUP.

The suffix _LKV conventionally denotes a "List of Values View" — a lightweight, read-only database object whose sole function is to present lookup rows for that named list. Because the view is owned by APPS and is publicly accessible, it serves as a convenient reporting and integration surface without requiring callers to know the underlying list_name filter or the physical lookup tables. Rather than querying the general-purpose lookup view and applying a WHERE clause, developers, reports, and interfaces can query this view directly to obtain the action-type-group domain of values in a single step. This tightens consistency: every consumer sees the same logical set of values, which is essential for downstream processes that categorise or group actions within the ETRM model.

Underlying Base Objects

The documented definition of the view is a single SELECT against the referenced base object CZ_LOOKUP_VALUES_VL, which itself is a view over the common lookup values data. The view text is:

SELECT LIST_NAME, DATA_VALUE, NUMERIC_ID_VALUE, VALUE_SEQ, DATA_TYPE_ID,
       NULL_VALUE_FLAG, VALUE_LABEL, VALUE_DESCRIPTION, VALUE_NOTES,
       LANGUAGE, SOURCE_LANG
FROM CZ_LOOKUP_VALUES_VL
WHERE LIST_NAME = 'ACTION_TYPE_GROUP'

This confirms that CZ_ACTIONTYPEGROUP_LKV adds no transformations of its own beyond the LIST_NAME predicate. Its lineage is a straightforward two-level chain: CZ_ACTIONTYPEGROUP_LKV → CZ_LOOKUP_VALUES_VL → the underlying application lookup values storage. The _VL component of the base view signals that language and translation attributes are resolved by the standard EBS lookup translation logic (the "Values List" pattern), meaning the view returns rows across the installed languages with a source-language indicator.

Key Columns

• LIST_NAME — The lookup type identifier; for every row returned this is the constant literal ACTION_TYPE_GROUP, confirming the view's scope.
• DATA_VALUE — The stored (typically internal) value code for the lookup entry.
• NUMERIC_ID_VALUE — A numeric identifier for the value, used where a surrogate numeric key is required by integrating systems.
• VALUE_SEQ — The display sequence controlling ordering of the values in lists of values and reports.
• DATA_TYPE_ID — Indicates the data type of the value, informing how the value should be interpreted or presented.
• NULL_VALUE_FLAG — Flags whether the entry represents a null or blank choice.
• VALUE_LABEL — The translatable display name shown to users.
• VALUE_DESCRIPTION — The full description associated with the value.
• VALUE_NOTES — Supplementary contextual notes for the value.
• LANGUAGE / SOURCE_LANG — The language of the returned row and the source language of the seed data, enabling multilingual reporting.

Common Use Cases and Queries

Typical uses include populating an action-type-group select list in a custom form or OAF page, driving lookup-based validation in an interface, and joining descriptive labels to transactional data that stores only the raw code.

SELECT DATA_VALUE, VALUE_LABEL, VALUE_DESCRIPTION, VALUE_SEQ
FROM   APPS.CZ_ACTIONTYPEGROUP_LKV
WHERE  LANGUAGE = USERENV('LANG')
ORDER  BY VALUE_SEQ;

For validation against a stored code:

SELECT COUNT(*) FROM APPS.CZ_ACTIONTYPEGROUP_LKV WHERE DATA_VALUE = :p_code;

Because the object is a view over CZ_LOOKUP_VALUES_VL, queries should filter on LANGUAGE to avoid duplicate rows across languages, and should be treated as read-only. The view is version-stable across 12.1.1 and 12.2.2, making it a reliable reference for ETRM-aligned reporting and integrations.