Search Results action_label

Overview

The view APPS.CZ_GROUPED_ACTION_TYPES_V exposes the hierarchical relationship between action type groups and their member action types in Oracle E-Business Suite release 12.1.1 and 12.2.2. It is owned by the APPS schema and is built entirely on top of the lookup infrastructure of the Common Applications (CZ) product, specifically the CZ_LOOKUP_VALUES_VL view. The object is a reporting and integration artifact: rather than presenting a flat list of lookup codes, it demonstrates the parent-child structure in which high-level action type groups — such as MODEL_INTERACTION, DISPLAY_UPDATE, NAVIGATION, and SESSION_CONTROL — are related to their individual action type members.

The user search term model_interaction maps directly to a decode branch inside the view. When the underlying lookup value DATA_VALUE on the ACTION_TYPE_GROUP list is MODEL_INTERACTION, the view emits the group name as ACTION_MODEL_INTER. This naming normalization is what enables downstream code and reports to join group rows to the corresponding member action types, where each member is itself stored on a lookup list whose name matches the derived group name.

Underlying Base Objects

The only documented base object referenced by this view is CZ_LOOKUP_VALUES_VL, which is itself a view over the CZ lookup values tables (the underlying CZ_LOOKUP_VALUES base table and its translations). The view reads this object twice in a self-join style construct:

• An inner inline view aliased GRP selects rows where LIST_NAME = 'ACTION_TYPE_GROUP'. These rows represent the group-level definitions.
• A second reference aliased ACT retrieves the individual action type members whose LIST_NAME equals the derived group name produced by the DECODE in the GRP subquery.
• The join between the two is an outer join (grp.action_group_name = act.list_name (+) on the Oracle 12.1.1/12.2.2 syntax), so a group row is retained even when no member action types exist.

Because the view depends on CZ_LOOKUP_VALUES_VL, it inherits the multilanguage (VL) semantics of that object, including LANGUAGE and SOURCE_LANG columns for translation handling.

Key Columns

The view exposes a mix of group-level and action-level columns, with NVL fallbacks that make a group row self-describing when no child action exists.

• ACTION_GROUP_LIST_NAME — the source list name (ACTION_TYPE_GROUP).
• ACTION_GROUP_NAME — the derived group name, e.g. ACTION_MODEL_INTER for MODEL_INTERACTION.
• ACTION_GROUP_NUMERIC_VALUE, ACTION_GROUP_SEQ, ACTION_GROUP_DATA_TYPE, ACTION_GROUP_NULL_FLAG — group attributes carried from the lookup.
• ACTION_SEQ — the sequence of the individual action type.
• ACTION_CODE — NVL(act.numeric_id_value, action_group_numeric_value), falling back to the group value.
• ACTION_NAME — NVL(act.data_value, action_group_name).
• ACTION_DATA_TYPE, ACTION_LABEL, ACTION_DESCRIPTION — overridden by member values when present, otherwise inherited from the group.
• ACTION_NOTES, LANGUAGE, SOURCE_LANG — descriptive and translation columns.

Common Use Cases and Queries

Developers and analysts query this view to enumerate the valid action types associated with a group, or to resolve the numeric code for an action. For example, to list all model interaction actions:

• SELECT action_name, action_code FROM cz_grouped_action_types_v WHERE action_group_name = 'ACTION_MODEL_INTER';
• SELECT * FROM cz_grouped_action_types_v WHERE action_group_list_name = 'ACTION_TYPE_GROUP' ORDER BY action_group_seq, action_seq;

Typical uses include validating configuration lookup values before deploying personalizations, driving reporting on configured action types, and supporting integration logic that maps an action name to its code. Because the view joins the lookup infrastructure directly, any change to the ACTION_TYPE_GROUP or member lookup lists is reflected automatically.