Search Results sequence_gui

Overview

MTL_ITEM_ATTRIBUTES_V is a view owned by the APPS schema in Oracle E-Business Suite, classified under the INV (Inventory) product family. The ETRM metadata flags this object with the description "10SC ONLY," indicating it is a restricted view associated with the 10SC configuration rather than a general-purpose, fully supported Inventory interface object. Its status is recorded as VALID.

The view presents attribute-generation and attribute-control metadata rather than item instance data. It exposes the descriptive information that governs how item attributes are defined, grouped, controlled, validated, and sequenced as they appear in the item setup forms and attribute-management processes. Because it joins MTL_ITEM_ATTRIBUTES to multiple aliases of MFG_LOOKUPS, it resolves internal lookup codes into their corresponding meanings and enabled flags, delivering a denormalized, presentation-ready result set. This makes it useful for reporting and integration scenarios where a caller needs lookup-resolved attribute definitions without performing the lookup joins manually. Its applicability should be confirmed against the specific 10SC deployment before it is relied upon in production code, since the metadata explicitly limits its scope.

Underlying Base Objects

The view is defined over two documented base objects:

• MTL_ITEM_ATTRIBUTES (SYNONYM) — the primary source, aliased as MIA. It supplies the attribute identity, group assignment, control level, data type, sequencing, update flags, validation code, and standard WHO audit columns, together with the ROWID exposed as ROW_ID.
• MFG_LOOKUPS (VIEW) — referenced four times as ML1, ML2, ML3, and ML4. These aliases resolve lookup codes into meaning text and enabled flags for distinct lookup types.

Four lookup joins are applied. ML1 matches ATTRIBUTE_GROUP_ID_GUI against lookup type ITEM_CHOICES_GUI using an inner join, so only attributes with a matching group lookup are returned. ML2 matches CONTROL_LEVEL against ITEM_CONTROL_LEVEL, also inner, using a NVL default of -999. ML3 matches STATUS_CONTROL_CODE against ITEM_STATUS_CONTROL and ML4 matches VALIDATION_CODE against ITEM_ATTRIBUTE_VALIDATION; both are outer joins, preserving rows where those codes are null and substituting the same -999 sentinel. The mixing of inner and outer joins means attributes lacking a valid group or control-level lookup are excluded, while status-control and validation lookups remain optional.

Key Columns

• ROW_ID — the MTL_ITEM_ATTRIBUTES ROWID, enabling direct row addressing.
• ATTRIBUTE_NAME / USER_ATTRIBUTE_NAME / USER_ATTRIBUTE_NAME_GUI — internal attribute identifier and its user-facing display names.
• ATTRIBUTE_GROUP_ID / ATTRIBUTE_GROUP_ID_GUI — the grouping identifier and the GUI lookup code driving the ML1 join.
• CONTROL_LEVEL — drives the ML2 join and indicates the level at which the attribute is controlled.
• DATA_TYPE, SEQUENCE, SEQUENCE_GUI — value type and display ordering.
• LEVEL_UPDATEABLE_FLAG, STATUS_CONTROL_CODE — update eligibility and status control, the latter resolved by ML3.
• VALIDATION_CODE — validation routine, resolved by ML4.
• PREFIELD_FLAG, POST_CHANGE_FLAG, POST_FIELD_FLAG, MANDATORY_FLAG, UPDATE_MESSAGE_NAME, REQUIRED_MESSAGE_NAME — form behavior and messaging controls.
• MEANING1–MEANING4 and ENABLED_FLAG1–ENABLED_FLAG4 — lookup-resolved meanings and enabled flags from each MFG_LOOKUPS alias.
• Standard WHO columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include generating attribute-definition reports, auditing how attribute groups and control levels are configured, and feeding downstream integrations that require lookup-resolved attribute metadata. A basic retrieval follows:

• SELECT ATTRIBUTE_NAME, USER_ATTRIBUTE_NAME, MEANING1, MEANING2, DATA_TYPE FROM APPS.MTL_ITEM_ATTRIBUTES_V ORDER BY SEQUENCE;
• Filter by group: SELECT ATTRIBUTE_NAME, MEANING1 FROM APPS.MTL_ITEM_ATTRIBUTES_V WHERE ATTRIBUTE_GROUP_ID_GUI = :group;
• Isolate mandatory attributes: SELECT ATTRIBUTE_NAME, MANDATORY_FLAG FROM APPS.MTL_ITEM_ATTRIBUTES_V WHERE MANDATORY_FLAG = 'Y';
• Review status-controlled attributes: SELECT ATTRIBUTE_NAME, MEANING3 FROM APPS.MTL_ITEM_ATTRIBUTES_V WHERE STATUS_CONTROL_CODE IS NOT NULL;

Because of the inner joins on group and control level, queries expecting attributes with missing group lookups should instead target MTL_ITEM_ATTRIBUTES directly. Given the "10SC ONLY" designation, usage should be validated for the target environment.