Search Results control_level_meaning




Overview
Explore in AI Chat

Overview

EGO_ITEM_ATTRIBUTES_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the EGO (Advanced Product Catalog) product family. Its documented purpose is to expose the control levels assigned to item attributes, expressed both as a code value and as a user-facing meaning. In practice, the view answers a recurring functional question in ETRM and item master implementations: what is the status control level that governs a given item attribute?

Unlike a physical table, this view is a thin projection over configuration data. It joins the item attribute definition table to the manufacturing lookup that decodes the control code, producing a denormalized result set that is convenient for reporting, validation, and integration. Because status control determines whether an attribute is mandatory, optional, or disabled for an item, the view is closely tied to EGO attribute enablement logic and to the rules that drive item creation and maintenance in the item master.

The view is documented with a STATUS of VALID in 12.1.1 and is present in the 12.2.2 ETRM metadata with the same APPS owner and the same documented base object references. It is therefore portable across both releases, which makes it a stable dependency for custom reports and interfaces.

Underlying Base Objects

The ETRM metadata identifies two referenced objects: MTL_ITEM_ATTRIBUTES (documented as a SYNONYM) and MFG_LOOKUPS (documented as a VIEW). Both are resolved at runtime against the APPS schema.

  • MTL_ITEM_ATTRIBUTES — the item attribute definition source. It supplies the attribute name (ATTRIBUTE_NAME), the user-facing attribute display name (USER_ATTRIBUTE_NAME_GUI), and the status control code (STATUS_CONTROL_CODE) that links to the lookup.
  • MFG_LOOKUPS — the lookup view that decodes the status control code. It provides the lookup meaning and the lookup code for the lookup type ITEM_STATUS_CONTROL.

The join is an equijoin on MFG1.LOOKUP_CODE = C.STATUS_CONTROL_CODE, restricted by MFG1.LOOKUP_TYPE = 'ITEM_STATUS_CONTROL'. Because the join is an inner join, only attributes whose status control code has a corresponding, active definition in the ITEM_STATUS_CONTROL lookup are returned. If a lookup row is missing or the lookup type is altered, the affected attribute silently drops out of the result set — a behavior worth noting when reconciling row counts against MTL_ITEM_ATTRIBUTES itself.

Key Columns

The view exposes exactly four columns, each derived from one of the two base objects:

  • ATTRIBUTE_DISP_NAME — the GUI-facing attribute name, sourced from MTL_ITEM_ATTRIBUTES.USER_ATTRIBUTE_NAME_GUI. This is the label users see on the item definition form, making it the natural column for user-visible reports.
  • CONTROL_LEVEL_MEANING — the decoded meaning of the status control level, sourced from MFG_LOOKUPS.MEANING. This presents the control setting in readable form (for example, the descriptive text associated with the ITEM_STATUS_CONTROL lookup code).
  • CONTROL_LEVEL_CODE — the underlying status control code, sourced from MFG_LOOKUPS.LOOKUP_CODE and matched to MTL_ITEM_ATTRIBUTES.STATUS_CONTROL_CODE. This is the column most often filtered on in queries and is the search term that led to this object.
  • ATTRIBUTE_NAME — the internal attribute identifier from MTL_ITEM_ATTRIBUTES.ATTRIBUTE_NAME, used to tie the row back to the underlying attribute definition for programmatic processing.

Common Use Cases and Queries

Typical applications include validating attribute control configuration before an item load, documenting which attributes are mandatory versus optional, and driving downstream interfaces that must respect attribute enablement. A simple query lists every attribute with its control level:

SELECT attribute_name, attribute_disp_name, control_level_code, control_level_meaning FROM apps.ego_item_attributes_v ORDER BY attribute_disp_name;

To isolate attributes at a specific control level — the usual form of a "control_level_code" search — constrain the code column directly:

SELECT attribute_disp_name, control_level_meaning FROM apps.ego_item_attributes_v WHERE control_level_code = :p_control_level_code;

Because CONTROL_LEVEL_CODE is a raw lookup code, report authors should join or decode it rather than hard-coding values, since lookup customization varies by environment. Queries should also run against the APPS schema or a synonym, consistent with the documented owner.