Search Results trigger_code

Overview

EGO_ACTION_DISPLAYS_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the EGO (Advanced Product Catalog) product family. Its purpose is to expose the persisted configuration that drives the user interface presentation of actions available in the Advanced Product Catalog. In release 12.1.1 and 12.2.2, the view resolves the join between action definitions and their display properties, translating stored lookup codes into user-facing meanings so that the UI layer, personalizations, and reporting tools can retrieve readable action metadata without embedding decode logic in each consumer.

The view is documented as VALID and is intended primarily for read-only access. It is useful in EBS reporting and integration scenarios where the presentation configuration of catalog actions must be audited, compared across environments, or surfaced to external systems. The object is a view rather than a table, so it provides no transactional storage; all data is derived from its base objects at query time.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects:

• EGO_ACTIONS_V (VIEW) — the primary source of action-level attributes such as ACTION_ID, OBJECT_ID, ACTION_NAME, DESCRIPTION, FUNCTION_ID, and security privilege information.
• EGO_ACTION_DISPLAYS_B (SYNONYM) — supplies the display configuration rows, including DISPLAY_STYLE, VISIBILITY_FLAG, prompt definitions, and the EXECUTION_METHOD that governs conditional decoding.
• EGO_FUNCTIONS_V (VIEW) — provides FUNCTION display names for both the action function and the prompt and visibility functions.
• FND_APPLICATION_TL (SYNONYM) — resolves the PROMPT_APPLICATION_ID to a translated application name.
• FND_LOOKUP_VALUES (SYNONYM) — resolves display style codes against the EGO_EF_DISPLAY_STYLE lookup type and visibility flags against the YES_NO lookup type, restricted to VIEW_APPLICATION_ID = 0 and the current language via USERENV('LANG').

The view therefore sits one abstraction level above the base configuration tables, joining action metadata with presentation metadata and lookup translations. The DECODE statements keyed on EXECUTION_METHOD ensure that lookup and function-name resolution is applied only for the relevant execution method, leaving text-type rows unprocessed.

Key Columns

Important columns exposed by the view include:

• ACTION_ID, OBJECT_ID — identifiers linking the display configuration to its action and parent object.
• CLASSIFICATION_CODE, OBJ_NAME, OBJ_DISP_NAME — object classification and internal/display naming.
• ATTR_GROUP_ID, ATTR_GROUP_NAME, ATTR_GROUP_DISP_NAME — attribute group context for the action.
• ACTION_NAME, DESCRIPTION, FUNCTION_ID, FUNC_DISPLAY_NAME — the action identity and its underlying function.
• SECURITY_PRIVILEGE_ID, SECURITY_PRIVILEGE_NAME — privilege governing action visibility.
• DISPLAY_STYLE_CODE, DISPLAY_STYLE_MEANING — the raw display style and its translated meaning.
• VISIBILITY_FLAG, VISIBILITY_MEANING — visibility indicator and its Yes/No translation.
• PROMPT_APPLICATION_ID, PROMPT_APPLICATION_NAME, PROMPT_MESSAGE_NAME — prompt context and message reference.
• PROMPT_FUNC_ID, PROMPT_FUNC_DISP_NAME, VISIBILITY_FUNC_ID — prompt and visibility function references.
• SEQUENCE — ordering of the action within its object or group.

Common Use Cases and Queries

Typical scenarios include auditing action display configuration, verifying security privilege assignments, and exporting presentation metadata for documentation or migration comparison. The following query lists actions with their display and visibility meanings:

• SELECT action_id, obj_name, action_name, func_display_name, display_style_meaning, visibility_meaning FROM apps.ego_action_displays_v ORDER BY object_id, sequence;
• SELECT action_name, sequence, security_privilege_name, prompt_application_name, prompt_message_name FROM apps.ego_action_displays_v WHERE visibility_flag = 'Y';
• SELECT object_id, COUNT(*) FROM apps.ego_action_displays_v GROUP BY object_id;

Because translations depend on USERENV('LANG'), results reflect the language of the session. Queries should be executed with APPS-level privileges or a synonym, and results treated as read-only.