Search Results xnc_subaction_type

Overview

XNC_ITEM_ACTIONS_V is a reporting and integration view in Oracle E-Business Suite belonging to the XNC product family, historically titled Sales for Communications. The module is flagged as obsolete in the ETRM documentation, meaning it is a legacy component that persists in some 12.1.1 and 12.2.2 installations but is no longer actively enhanced or supported as a strategic solution. The view is designed to expose the various actions, sub-actions, and result procedures associated with a product. In practical terms, it serves as a consolidated read model that joins item master information to the action configuration defined for each item, allowing downstream reporting, integrations, or legacy communications-order logic to resolve which action or result procedure applies to a given product within a given organization.

Underlying Base Objects

The documented view text defines XNC_ITEM_ACTIONS_V as a join across four sources. The primary driver is XNC_ITEM_ACTIONS_VL, which supplies the action definition rows including the item action identifier, action type, sub-action type, action name, and the DRC result procedure. This table is aliased as B. The item context is provided by MTL_SYSTEM_ITEMS_VL, aliased as C, which contributes the inventory item, organization, item name, and description. Two independent instances of FND_LOOKUP_VALUES_VL, aliased D and E, are joined to resolve the meaning of the ACTION_TYPE and SUB_ACTION_TYPE codes against the lookup types XNC_ACTION_TYPE and XNC_SUBACTION_TYPE respectively.

The join conditions rely on INVENTORY_ITEM_ID and ORGANIZATION_ID between the action table and the item table, and on LOOKUP_CODE matching the action and sub-action type codes. Notably, the ETRM metadata records this object as not implemented in the source database and lists no formally documented base objects, which is consistent with its obsolete status and with the fact that XNC_ITEM_ACTIONS_VL and its supporting tables may not exist in every environment.

Key Columns

• ROW_ID — The row identifier inherited from the underlying action table.
• ITEM_ACTION_ID — The unique identifier of the item action definition.
• INVENTORY_ITEM_ID / ORGANIZATION_ID — The composite key that identifies the item within a specific inventory organization.
• ITEM_NAME / ITEM_DESCRIPTION — Concatenated item segment description and the item long description, sourced via MTL_SYSTEM_ITEMS_VL.
• ACTION_TYPE / ACTION_TYPE_MEANING — The coded action type and its decoded lookup meaning from XNC_ACTION_TYPE.
• SUB_ACTION_TYPE / SUB_ACTION_TYPE_MEANING — The coded sub-action and its decoded meaning from XNC_SUBACTION_TYPE.
• ACTION_NAME — The descriptive name of the action.
• DRC_RESULT_PROCEDURE — The result or procedure invoked when the action is executed.
• SYNCHRONOUS_ACTION_FLAG — Indicates whether the action is processed synchronously.
• ATTRIBUTE1–15, CONTEXT — Descriptive flexfield columns carried over from the action table.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

The view is typically queried to enumerate the actions configured against a particular product, or to drive integration logic that must locate the correct result procedure. A representative query filtering by item and organization is shown below.

SELECT item_name, organization_id, action_type_meaning, sub_action_type_meaning, action_name, drc_result_procedure, synchronous_action_flag FROM xnc_item_actions_v WHERE inventory_item_id = :p_item_id AND organization_id = :p_org_id;

A second common pattern groups configured actions by type for reporting:

SELECT action_type_meaning, COUNT(*) FROM xnc_item_actions_v GROUP BY action_type_meaning;

Because the view is obsolete and not implemented in all databases, consumers should confirm its existence before relying on it. Where the XNC action tables are absent, integrations must fall back to the surviving communications or order management tables. In environments where XNC_ITEM_ACTIONS_V is present, it remains the most direct route to resolve item-level action, sub-action, and result procedure metadata.