Search Results csi_i_extended_attribs_v

Overview

CSI_I_EXTENDED_ATTRIBS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSI (Install Base) product family. Its documented description is "Instance Extended Attributes view," and in the ETRM metadata for 12.2.2 it is registered with a status of VALID and the object type VIEW. The view surfaces the distinct combinations of extended attribute keys that have been captured against customer product instances in the Install Base. It does not expose the extended attribute values themselves; rather, it presents the identifying key set — attribute level together with the associated master organization, inventory item, item category, and instance identifiers.

Because the view applies a GROUP BY over its key columns, its result set is de-duplicated. Rows are returned once per unique key combination regardless of how many attribute rows exist in the underlying data. This makes the view suitable for use as a distinct-value reference for extended attribute definitions in reporting, data extraction, and integration scenarios, and for validating which objects carry extended attributes at a given level of granularity.

Underlying Base Objects

The view is defined directly over the synonym CSI_I_EXTENDED_ATTRIBS, which resolves to the APPS base object of the same name in the Install Base schema. The documented view text is:

• SELECT ATTRIBUTE_LEVEL, MASTER_ORGANIZATION_ID, INVENTORY_ITEM_ID, ITEM_CATEGORY_ID, INSTANCE_ID FROM CSI_I_EXTENDED_ATTRIBS GROUP BY ATTRIBUTE_LEVEL, MASTER_ORGANIZATION_ID, INVENTORY_ITEM_ID, ITEM_CATEGORY_ID, INSTANCE_ID

All five columns projected by the view are taken unchanged from the base object. No joins, lookups, or translated columns are introduced; the sole transformation is the GROUP BY, which produces the distinct key combinations described above. Consequently, the view inherits the security and access characteristics of the underlying base object while offering a simplified, de-duplicated projection for consumers that only require the key set.

Key Columns

• ATTRIBUTE_LEVEL — Identifies the level at which the extended attributes are defined. This is the column most directly relevant to the user search term "attribute_level," since it governs whether the remaining key columns are populated and how the row should be interpreted. Typical values distinguish instance-level attributes from item-level or category-level attributes.
• MASTER_ORGANIZATION_ID — The master organization identifier associated with the attribute key, used to scope item-related attributes within a specific master inventory organization.
• INVENTORY_ITEM_ID — The inventory item identifier when attributes are defined at item level. Null for keys that are not item-scoped.
• ITEM_CATEGORY_ID — The item category identifier when attributes are defined at category level. Null for keys that are not category-scoped.
• INSTANCE_ID — The Install Base instance identifier. This links the key back to the specific customer product instance record in the Install Base tables.

The population pattern of the four scoping columns is driven by ATTRIBUTE_LEVEL, so queries should always filter or group on ATTRIBUTE_LEVEL first when interpreting a result set.

Common Use Cases and Queries

The view is commonly used to enumerate which instances, items, or categories carry extended attributes, to feed integration extracts, and to reconcile extended attribute setup between environments. A basic query listing all distinct extended attribute keys is:

• SELECT attribute_level, master_organization_id, inventory_item_id, item_category_id, instance_id FROM apps.csi_i_extended_attribs_v;

To restrict to a particular level of granularity:

• SELECT instance_id, inventory_item_id, item_category_id FROM apps.csi_i_extended_attribs_v WHERE attribute_level = :p_level;

To count how many instances carry extended attributes at each level:

• SELECT attribute_level, COUNT(DISTINCT instance_id) instance_count FROM apps.csi_i_extended_attribs_v GROUP BY attribute_level;

Because the view contains only key columns and no attribute values, it is typically joined to the base extended attributes object or to Install Base instance tables when the actual attribute names and values are required for a report.