Search Results xnc_item_actions_vl

Overview

The view XNC_ITEM_ACTIONS_VL belongs to the Oracle EBS product XNC - Sales for Communications, a module now classified as obsolete within the documented ETRM metadata. The "_VL" suffix follows the standard Oracle Application Object Library naming convention for a "view with language," denoting that the object merges a base (non-translated) table with its corresponding translation (_TL) table so that language-dependent descriptive columns are exposed alongside language-independent attributes. In this case, the view is explicitly described as "the join of the base table and translation table with all the columns from both tables."

Its role is to present item action definitions together with their language-specific descriptions, keyed to the session language of the querying user. In reporting and integration contexts, this view allows concurrent programs, Oracle Reports, OAF pages, or external interfaces to retrieve a single, self-contained record for each item action without performing an explicit join to the translation table. The view defines action behavior for inventory items across organizations and associates each action with a description that respects the user's language preference.

Underlying Base Objects

The view is defined over two documented base objects:

• XNC_ITEM_ACTIONS_B — the base table holding language-independent columns such as identifiers, action types, flags, and the DFF context/attribute segments.
• XNC_ITEM_ACTIONS_TL — the translation table holding the language-dependent descriptive column ACTION_DESCRIPTION, filtered by LANGUAGE.

The join condition is B.ITEM_ACTION_ID = T.ITEM_ACTION_ID, with an additional filter T.LANGUAGE = USERENV('LANG') that restricts the translation row to the language of the current session. The ETRM metadata notes that the object is "Not implemented in this database," and no base objects are separately documented; this indicates the view may not be deployed in all environments or may exist only in installations where the XNC module was enabled. Row-level identification is provided via B.ROWID, aliased as ROW_ID.

Key Columns

• ROW_ID — the ROWID of the base-table row, useful for direct row navigation and DML targeting.
• ITEM_ACTION_ID — the primary surrogate key linking base and translation records.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — identify the item and the inventory organization to which the action applies.
• ACTION_TYPE, SUB_ACTION_TYPE — classify the action; ACTION_NAME is derived from the base table via a DECODE, exposed only when the action type is 'TEST'.
• DRC_RESULT_PROCEDURE — names the procedure invoked to process or return the action result.
• SYNCHRONOUS_ACTION_FLAG — indicates whether the action executes synchronously.
• ACTION_DESCRIPTION — the translated, language-dependent description sourced from XNC_ITEM_ACTIONS_TL.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield segments.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include retrieving the configured actions and their descriptions for a given item and organization, auditing the population of item actions, and exposing item-action metadata to external integrations. A straightforward query listing actions for a specific item is:

SELECT ITEM_ACTION_ID, ACTION_TYPE, ACTION_NAME, SUB_ACTION_TYPE, ACTION_DESCRIPTION, SYNCHRONOUS_ACTION_FLAG FROM XNC_ITEM_ACTIONS_VL WHERE INVENTORY_ITEM_ID = :item_id AND ORGANIZATION_ID = :org_id;

To locate actions that execute a particular result procedure across an organization:

SELECT INVENTORY_ITEM_ID, ACTION_TYPE, DRC_RESULT_PROCEDURE, ACTION_DESCRIPTION FROM XNC_ITEM_ACTIONS_VL WHERE ORGANIZATION_ID = :org_id AND DRC_RESULT_PROCEDURE IS NOT NULL ORDER BY INVENTORY_ITEM_ID;

Because the view automatically applies the USERENV('LANG') filter, callers need not join the translation table themselves; however, integrations requiring all translations simultaneously should query XNC_ITEM_ACTIONS_TL directly. Given the module's obsolete status, any use should be validated against the specific 12.1.1 or 12.2.2 environment before production reliance.