Search Results control_level_disp




Overview
Explore in AI Chat

Overview

APPS.MTL_STAT_ATTRIB_VALUES_ALL_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered in FND Design Data as INV.MTL_STAT_ATTRIB_VALUES_ALL_V. Its documented status is VALID. The view is classified as a "supplementary view used to simplify forms coding," a category of EBS object intended primarily to support Oracle Forms-based user interfaces rather than to serve as a public data access layer. The ETRM documentation explicitly warns that Oracle does not recommend querying or altering data through this view, because its definition may change dramatically in subsequent minor or major releases.

Functionally, the view exposes the status attribute values associated with inventory item status codes. Each row correlates an inventory item status code with a named status attribute and its assigned value, together with descriptive display fields such as CONTROL_LEVEL_DISP and ATTRIBUTE_NAME_DISP. The CONTROL_LEVEL_DISP column, which is the field associated with the user's search term "control_level_disp", is an 80-character display value that presents the human-readable control level for the status attribute. Because the view is a forms-support construct, it is typically consumed indirectly by EBS application modules rather than directly by end-user reports.

Underlying Base Objects

The ETRM dependency information documents that APPS.MTL_STAT_ATTRIB_VALUES_ALL_V references the following base objects: APPS.MFG_LOOKUPS (a view in the APPS schema), MTL_ITEM_ATTRIBUTES (a synonym), and MTL_STATUS_ATTRIBUTE_VALUES (a synonym). These three objects supply the join structure that produces the view's result set. MTL_STATUS_ATTRIBUTE_VALUES stores the core status attribute value records, MTL_ITEM_ATTRIBUTES provides item attribute context, and MFG_LOOKUPS supplies lookup-driven display values such as the control level designation surfaced through CONTROL_LEVEL_DISP.

In the reverse dependency direction, the view is referenced by two documented consumers: the diagnostic package BOM_DIAGUNITTEST_ITMHLCHK and the batch processing package GME_CREATE_BATCH_PVT. This confirms that the view's practical role is to serve internal Oracle EBS processing logic and validation routines rather than to act as an integration endpoint.

Key Columns

Common Use Cases and Queries

Because Oracle does not recommend direct querying, the view is most appropriately used for diagnostic inspection of status attribute values and control level display strings. A basic query follows the documented column list:

SELECT INVENTORY_ITEM_STATUS_CODE
     , CONTROL_LEVEL_DISP
     , ATTRIBUTE_NAME_DISP
     , ATTRIBUTE_VALUE
  FROM APPS.MTL_STAT_ATTRIB_VALUES_ALL_V;

A targeted query for the searched field, filtered by status code, is also common during troubleshooting:

SELECT INVENTORY_ITEM_STATUS_CODE
     , CONTROL_LEVEL_DISP
     , ATTRIBUTE_NAME
     , ATTRIBUTE_VALUE
  FROM APPS.MTL_STAT_ATTRIB_VALUES_ALL_V
 WHERE INVENTORY_ITEM_STATUS_CODE = :status_code;

For production integration or reporting requirements, developers should query the underlying MTL_STATUS_ATTRIBUTE_VALUES table directly, since the view definition may change across releases. Use of this view should generally be limited to read-only diagnostics and code inspection.