Search Results mtl_item_attr_appl_inst_v




Overview
Explore in AI Chat

Overview

MTL_ITEM_ATTR_APPL_INST_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the INV (Inventory) product module. Its functional purpose is to identify the set of item attribute names that are actively installed and applicable within a given Oracle EBS environment. Rather than storing data itself, the view derives its result set at runtime by filtering the attribute dependency metadata held in MTL_ATTR_APPL_DEPENDENCIES against the status returned by the INV_ITEM_UTIL package function APPL_INST_STATUS. Only those attributes whose owning application returns an installed status of 'I' are surfaced.

Because attribute applicability in Oracle Inventory is controlled by which applications are licensed and installed, this view provides a clean, environment-aware list of attribute names. It is used primarily by forms, concurrent programs, and integration code that must dynamically determine which item attributes are meaningful in the current instance. The view is documented as VALID and is available in both EBS 12.1.1 and 12.2.2, where the underlying structures remain consistent with the documented metadata.

Underlying Base Objects

The documented base objects referenced by this view are:

  • MTL_ATTR_APPL_DEPENDENCIES (accessed through a SYNONYM) — the primary source of rows. This table records the dependency relationships between item attributes and the applications that own or control them, exposing APPLICATION_ID and ATTRIBUTE_NAME among other columns.
  • INV_ITEM_UTIL (PACKAGE) — referenced only through its APPL_INST_STATUS function, which returns the installation status of an application identified by APPLICATION_ID.

The view text is a simple SELECT DISTINCT over MTL_ATTR_APPL_DEPENDENCIES:

SELECT DISTINCT MAAD.ATTRIBUTE_NAME FROM MTL_ATTR_APPL_DEPENDENCIES MAAD WHERE INV_ITEM_UTIL.APPL_INST_STATUS( MAAD.APPLICATION_ID ) = 'I'

Because the WHERE clause invokes a PL/SQL function, the view is not purely a relational projection; each candidate row must be validated against the package function at execution time. The DISTINCT operator collapses any duplicate attribute names arising from multiple dependency rows.

Key Columns

The view exposes a single documented column:

  • ATTRIBUTE_NAME — the internal name of an item attribute that is both defined in the attribute dependency metadata and whose associated application is installed. This value corresponds to attribute identifiers used across the item attribute framework, not the user-facing prompt text.

No other columns are projected. Any consumer needing additional context — such as APPLICATION_ID, attribute type, or display labels — must join back to MTL_ATTR_APPL_DEPENDENCIES or to attribute definition tables using ATTRIBUTE_NAME as the linking key.

Common Use Cases and Queries

Typical usage centers on determining which item attributes are active before displaying, validating, or processing them. A common pattern is to intersect this view with attribute definition or item attribute value tables.

  • Listing all installed item attributes for reporting or inventory analysis.
  • Driving dynamic form or page logic that should only present attributes applicable to the current installation.
  • Validating that an attribute referenced by custom integration code is actually installed before processing.

Sample query — enumerate installed attributes:

SELECT ATTRIBUTE_NAME FROM APPS.MTL_ITEM_ATTR_APPL_INST_V ORDER BY ATTRIBUTE_NAME;

Sample query — confirm whether a specific attribute is installed:

SELECT ATTRIBUTE_NAME FROM APPS.MTL_ITEM_ATTR_APPL_INST_V WHERE ATTRIBUTE_NAME = :p_attribute_name;

Sample query — join to the dependency table for richer context:

SELECT V.ATTRIBUTE_NAME, D.APPLICATION_ID FROM APPS.MTL_ITEM_ATTR_APPL_INST_V V, APPS.MTL_ATTR_APPL_DEPENDENCIES D WHERE V.ATTRIBUTE_NAME = D.ATTRIBUTE_NAME;

Because the view calls INV_ITEM_UTIL.APPL_INST_STATUS per row, performance-sensitive queries should filter or pre-restrict the candidate set where possible, and callers should treat the view as read-only and environment-dependent, as its output varies with which applications are installed.