Results for “mtl_item_templ_attributes_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MTL_ITEM_TEMPL_ATTRIBUTES is a core Inventory (INV) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the item attributes and their assigned values for each item template. In Oracle EBS, item templates function as reusable blueprints that prese­lect and pre-populate the attributes (such as Inventory Item, Purchasing Item, or Order Management indicators) applied when creating new items. This table serves as the associative bridge between a template header and the individual item attributes that the template controls, capturing the value each attribute should assume when the template is applied to a master item.

From a Data Vault modeling perspective, the ETRM heuristic classifies this object as a link. This classification reflects its role as an associative entity: it resolves the many-to-many relationship between MTL_ITEM_TEMPLATES and MTL_ITEM_ATTRIBUTES, carrying descriptive payload columns (attribute value, enabled flag, and sequencing information) alongside the two foreign keys that constitute its business identity.

Key Information Stored

The table is keyed by a composite primary key, MTL_ITEM_TEMPL_ATTRIBUTES_PK, defined on TEMPLATE_ID and ATTRIBUTE_NAME. TEMPLATE_ID is a foreign key to MTL_ITEM_TEMPLATES, identifying the owning template, while ATTRIBUTE_NAME is a foreign key to MTL_ITEM_ATTRIBUTES, identifying the specific item attribute being set. A unique index, MTL_ITEM_TEMPL_ATTRIBUTES_U1, extends this business key with ZD_EDITION_NAME, reflecting the multi-tenant editioning introduced in 12.2.x.

• TEMPLATE_ID — surrogate-style identifier of the parent template (business-key component).
• ATTRIBUTE_NAME — name of the item attribute controlled by the template (business-key component).
• ATTRIBUTE_VALUE — the default value the template assigns to that attribute on item creation.
• ENABLED_FLAG — indicates whether the attribute is active for the template.
• SEQUENCE / SEQUENCE_GUI — display and processing order of the attribute in template maintenance screens.
• ATTRIBUTE_GROUP_ID / ATTRIBUTE_GROUP_ID_GUI — groupings that organize attributes within the template layout.
• REPORT_USER_VALUE — user-defined reporting value captured for the attribute.
• ZD_EDITION_NAME — editioning column enabling multi-tenant, edition-based data segregation in 12.2.x.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical usage includes reporting which attributes a template controls, auditing default attribute values assigned to newly created items, and validating template configuration during implementations. A common query joins the template header to list configured attributes:

• SELECT t.template_id, t.template_name, a.attribute_name, a.attribute_value, a.enabled_flag FROM mtl_item_templates t JOIN mtl_item_templ_attributes a ON t.template_id = a.template_id;
• Filtering by ENABLED_FLAG = 'Y' identifies active template attributes.
• Joining to MTL_ITEM_ATTRIBUTES resolves attribute descriptions and control types.
• Ordering by SEQUENCE reproduces the template's display order for documentation or reconciliation.
• In 12.2.x, include ZD_EDITION_NAME in filters to isolate the active edition.

Related Objects

• MTL_ITEM_TEMPLATES — parent table; join on MTL_ITEM_TEMPLATES.TEMPLATE_ID = MTL_ITEM_TEMPL_ATTRIBUTES.TEMPLATE_ID.
• MTL_ITEM_ATTRIBUTES — attribute definition table; join on MTL_ITEM_ATTRIBUTES.ATTRIBUTE_NAME = MTL_ITEM_TEMPL_ATTRIBUTES.ATTRIBUTE_NAME.
• MTL_SYSTEM_ITEMS / MTL_SYSTEM_ITEMS_B — items created from templates inherit these attributes.
• MTL_ITEM_TEMPL_ATTRIBUTES_PK and MTL_ITEM_TEMPL_ATTRIBUTES_U1 — primary and unique indexes enforcing business identity.
• Inventory item definition and item template maintenance concurrent programs and APIs that read these rows during item creation.