Search Results item_status_control




Overview
Explore in AI Chat

Overview

The view APPS.EGO_ITEM_ATTRIBUTES_V is a denormalized reporting and integration interface within Oracle E-Business Suite, exposing item attribute metadata together with a human-readable decoding of each attribute's status control level. It is defined over MTL_ITEM_ATTRIBUTES and MFG_LOOKUPS, joining the item attribute definition table to the lookup that resolves the attribute's STATUS_CONTROL_CODE into a GUI display name and a control level meaning.

The view is relevant in both Oracle EBS 12.1.1 and 12.2.2. Because it is owned by APPS and is not a table, it carries no data of its own; it is a query surface used by forms, concurrent programs, and third-party integrations that require item attribute names joined to their control-level semantics. When a user searches for item_status_control, this view is the object through which the ITEM_STATUS_CONTROL lookup type is joined to item attributes.

The view returns one row per item attribute record in MTL_ITEM_ATTRIBUTES that has a matching lookup code in MFG_LOOKUPS for lookup type ITEM_STATUS_CONTROL. This makes it useful for reporting on which attributes are controlled, at what level, and under what display label.

Underlying Base Objects

The ETRM metadata documents two referenced base objects:

  • MTL_ITEM_ATTRIBUTES (SYNONYM) — the synonym under which the item attribute definition rows are accessed. This object supplies USER_ATTRIBUTE_NAME_GUI, ATTRIBUTE_NAME, and STATUS_CONTROL_CODE.
  • MFG_LOOKUPS (VIEW) — the lookup view that supplies the decoded MEANING and LOOKUP_CODE for lookup type ITEM_STATUS_CONTROL.

The join is explicit in the view text: MFG1.LOOKUP_TYPE = 'ITEM_STATUS_CONTROL' AND MFG1.LOOKUP_CODE = C.STATUS_CONTROL_CODE. The alias C refers to MTL_ITEM_ATTRIBUTES; the alias MFG1 refers to MFG_LOOKUPS. Because the driving column is STATUS_CONTROL_CODE, only attributes whose status control code matches an active lookup value in that lookup type will be returned. Attributes with a null or unmatched control code are excluded by the inner join semantics.

Key Columns

The view exposes exactly four columns, all derived from the two base objects:

  • ATTRIBUTE_DISP_NAME — sourced from MTL_ITEM_ATTRIBUTES.USER_ATTRIBUTE_NAME_GUI. This is the user-facing display label of the item attribute.
  • ATTRIBUTE_NAME — sourced from MTL_ITEM_ATTRIBUTES.ATTRIBUTE_NAME. This is the internal attribute identifier used in the item attribute schema.
  • CONTROL_LEVEL_CODE — sourced from MFG_LOOKUPS.LOOKUP_CODE for lookup type ITEM_STATUS_CONTROL. This is the coded value of the status control level.
  • CONTROL_LEVEL_MEANING — sourced from MFG_LOOKUPS.MEANING. This is the descriptive, translatable meaning associated with the control level code.

Together, these columns allow a caller to map an attribute's display name to its internal name and to the meaning of the status control applied to it, without writing the lookup join manually.

Common Use Cases and Queries

Typical uses include reporting on item attribute control levels for governance and audit purposes, populating pick lists in custom forms, and validating item attribute setup during data conversion or integration loads.

A simple listing of all attribute control levels:

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

Filtering for a specific control level meaning, or searching by display name:

  • SELECT attribute_name, control_level_meaning FROM apps.ego_item_attributes_v WHERE control_level_code = :control_code;
  • SELECT * FROM apps.ego_item_attributes_v WHERE attribute_disp_name LIKE '%Status%';

Because the view is defined in the APPS schema and built on synonyms and lookup views, it should be queried with the APPS prefix and appropriate grants. In 12.1.1 and 12.2.2 the behavior is consistent, as the underlying lookup type ITEM_STATUS_CONTROL is seeded by standard EBS configuration.