Search Results eng_change_actions_vl




Overview
Explore in AI Chat

Overview

ENG_CHANGE_ACTIONS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, defined within the Engineering (ENG) product module. It presents change action records associated with engineering change management workflows, exposing both transactional attributes held in the base change actions table and the corresponding translated description text. As a VL view, it derives its "_TL" suffix convention from the Oracle multi-language support architecture, returning only the row translation that matches the session's language setting. In releases 12.1.1 and 12.2.2 the object is documented as VALID.

The view serves as a reporting and integration surface for change action data. Application code, concurrent programs, and external interfaces that need a single-row-per-action result set join to ENG_CHANGE_ACTIONS_VL rather than querying the base tables directly, because the view encapsulates the language-join logic and provides a human-readable DESCRIPTION column. The ROW_ID pseudo-column exposes the underlying ROWID of the base change action row, which supports update-through-view and row identification scenarios.

Underlying Base Objects

ETRM metadata documents two referenced base objects, both exposed to APPS as synonyms:

  • ENG_CHANGE_ACTIONS — the transactional table holding change action records (aliased ECA in the view definition).
  • ENG_CHANGE_ACTIONS_TL — the translation table holding the language-specific description (aliased ECAT).

The view joins the two on ACTION_ID and filters the translation with the condition ECAT.LANGUAGE = USERENV('LANG'), so each ACTION_ID yields exactly one row per session language. All business columns are sourced from ECA; only DESCRIPTION is sourced from ECAT.

Key Columns

The view exposes thirty-two columns. The most significant include:

Common Use Cases and Queries

Typical scenarios include reporting open change actions, locating the entity referenced by a generic ID slot, and tracing workflow routing. A basic query listing current-language actions is:

SELECT action_id, action_type, object_name, object_id1, status_code, description FROM apps.eng_change_actions_vl WHERE status_code = 'OPEN';

To resolve an action by its first object identifier — the term the user searched for — filter on OBJECT_ID1:

SELECT action_id, action_type, object_name, object_id1, object_id2 FROM apps.eng_change_actions_vl WHERE object_id1 = :p_object_id;

Because OBJECT_ID1 is generic, the query is most reliable when constrained together with OBJECT_NAME or ACTION_TYPE:

SELECT action_id, object_id1, status_code, assignee_id FROM apps.eng_change_actions_vl WHERE object_id1 = :p_id AND action_type = :p_action_type;

For workflow tracking, join WORKFLOW_ITEM_KEY to the workflow tables, or filter actions by assignee and response date to produce workload reports.