Search Results install_base_flag

Overview

The view XNC_ITEM_ACTION_PARS_V belongs to the Oracle E-Business Suite product family XNC – Sales for Communications, a module that is now documented as obsolete within the ETRM reference set for releases 12.1.1 and 12.2.2. The view is designed to present, in a single denormalized result set, the complete relationship between a product (inventory item) and the actions, sub-actions, sequence values, and configurable parameters that may be executed against that product. Functionally it is described as the join of the two underlying views XNC_ITEM_PARS_VL and XNC_ITEM_ACTIONS_V, combining parameter-level metadata from the former with action-level metadata from the latter.

Because the XNC module is flagged as obsolete, this view should be regarded as a legacy reporting and integration artifact. It is not implemented in the reference database from which the ETRM metadata was captured, so its presence in any given environment depends on whether the XNC product was previously installed and whether the supporting base objects remain. Where it does exist, it serves as a convenient read-only access point for extracting product-action-parameter mappings without writing direct joins across the constituent views.

Underlying Base Objects

The documented definition joins two views:

• XNC_ITEM_ACTION_PARS_VL — the parameter-level source, aliased as B, supplying parameter name, meaning, default value, mandatory and display flags, sequence, source-type attributes, install-base and subscription flags, user instructions, and the standard EBS WHO columns.
• XNC_ITEM_ACTIONS_V — the action-level source, aliased as C, supplying inventory item and organization identifiers, action and sub-action types, action name, item name and description, action description, and the synchronous action flag.

The join predicate is B.ITEM_ACTION_ID = C.ITEM_ACTION_ID, meaning every parameter row is matched to its owning action. No base tables are separately documented as referenced objects for this view; its lineage is expressed entirely through the two XNC views above. The _VL suffix on the parameter source indicates that the underlying parameter object carries translatable (MLS) columns, so the view exposes the current-language variant of the parameter text.

Key Columns

• ROW_ID, ITEM_ACTION_PARAM_ID, ITEM_ACTION_ID — primary and foreign key identifiers linking parameters to actions.
• INVENTORY_ITEM_ID, ORGANIZATION_ID — identify the product and the inventory organization context.
• ACTION_TYPE, SUB_ACTION_TYPE, ACTION_NAME, ACTION_DESCRIPTION — describe the action to be performed.
• ITEM_NAME, ITEM_DESCRIPTION — descriptive attributes of the product.
• PARAMETER_NAME, PARAMETER_MEANING, PARAMETER_DESCRIPTION, DISPLAY_MEANING — parameter identity and presentation text.
• MANDATORY_FLAG, DISPLAY_FLAG, DEFAULT_VALUE, SEQUENCE, SYSTEM_DEFINED_FLAG — control the behavior and ordering of parameter entry.
• SYNCHRONOUS_ACTION_FLAG, PARAMETER_SYNCHRONOUS_FLAG — indicate whether the action or parameter is executed synchronously.
• SOURCE_TYPE_CODE, SOURCE_TYPE_MEANING, SOURCE_NAME, SOURCE_MEANING — describe the source of the parameter value.
• INSTALL_BASE_FLAG, SUBSCRIPTION_FLAG, USER_INSTRUCTION — contextual flags and guidance text.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective-dating for the parameter.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the standard extensibility (flexfield) columns.

Common Use Cases and Queries

Typical usage is read-only: reporting on which parameters apply to a product's actions, exporting action-parameter definitions for integration, or verifying mandatory and defaulted parameters before configuration. A representative query retrieves all parameters for a given product's actions:

• SELECT inventory_item_id, organization_id, action_name, parameter_name, mandatory_flag, default_value, sequence FROM xnc_item_action_pars_v WHERE inventory_item_id = :item_id ORDER BY action_name, sequence;
• SELECT action_type, sub_action_type, parameter_name, source_type_code, synchronous_action_flag FROM xnc_item_action_pars_v WHERE item_action_id = :action_id;
• SELECT inventory_item_id, item_name, action_name, parameter_name, start_date_active, end_date_active FROM xnc_item_action_pars_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));

Given the obsolete status and the note that the view is not implemented in the reference database, any query should first confirm object existence in the target environment.