Search Results attribute_level




Overview
Explore in AI Chat

Overview

APPS.CSI_I_EXTENDED_ATTRIBS_V is a reporting and integration view within the Oracle E-Business Suite Customer and Service Intelligence (CSI) module. Its principal function is to expose the distinct combinations of extended attribute assignment levels and their associated item, organization, category, and instance identifiers. Unlike a denormalized transaction table, this view intentionally collapses duplicate rows through an aggregate GROUP BY clause, producing a deduplicated list of attribute-level scoping records.

In the CSI data model, extended attributes allow organizations to capture supplemental descriptive data about items beyond the standard item master and category fields. The ATTRIBUTE_LEVEL column is the pivotal discriminator: it indicates the granularity at which a given extended attribute applies — for example, at the master organization level, the inventory item level, the item category level, or the instance level. Because the view filters out repetition, it serves as an efficient reference for downstream reporting, integration feeds, and configuration validation, particularly for implementers searching on attribute_level to determine which scoping values are actually populated in a given environment.

Underlying Base Objects

The view is defined over a single documented base object: the synonym CSI_I_EXTENDED_ATTRIBS, which resolves to the corresponding CSI base table owned by the APPS schema. No joins, outer queries, or additional tables are present in the recorded view text. The relationship is therefore direct and one-to-one in terms of lineage, with the view acting purely as a projection-and-distinct wrapper over its source. The exact definition documented in ETRM 12.2.2 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

Because every exposed column also appears in the GROUP BY, the view returns only the distinct key combinations present in the base table, omitting any attribute value columns that may exist on the underlying object. This design choice keeps the view lightweight and deterministic.

Key Columns

  • ATTRIBUTE_LEVEL — Identifies the level at which the extended attribute is applied. This is the primary search and filter column and drives how the remaining key columns are interpreted.
  • MASTER_ORGANIZATION_ID — The master organization context for the attribute record, anchoring the item definition to its owning inventory organization hierarchy.
  • INVENTORY_ITEM_ID — The surrogate key of the inventory item to which the extended attribute record pertains.
  • ITEM_CATEGORY_ID — The category identifier, populated where the attribute is scoped at the category level rather than at a specific item.
  • INSTANCE_ID — The instance identifier, populated where the attribute is scoped to a specific item instance rather than to an item definition.

In practice, these columns are mutually contextual: depending on the value of ATTRIBUTE_LEVEL, some of the identifier columns will be meaningful while others may be null. This conditional population is the reason the view is most commonly consulted with ATTRIBUTE_LEVEL in the WHERE clause.

Common Use Cases and Queries

Typical scenarios include validating which attribute levels have been configured before an item load, identifying all items carrying extended attributes at a given level, and feeding integration routines that need a compact key list rather than full attribute payloads. A representative query to enumerate levels in use is:

SELECT ATTRIBUTE_LEVEL, COUNT(*) FROM APPS.CSI_I_EXTENDED_ATTRIBS_V GROUP BY ATTRIBUTE_LEVEL;

To retrieve all item-scoped records for a master organization:

SELECT INVENTORY_ITEM_ID, ITEM_CATEGORY_ID, INSTANCE_ID FROM APPS.CSI_I_EXTENDED_ATTRIBS_V WHERE ATTRIBUTE_LEVEL = :p_level AND MASTER_ORGANIZATION_ID = :p_org;

Because the view is read-only and deduplicated, it is safe for concurrent reporting use. Note that it exposes no attribute value columns; consumers requiring the actual extended attribute values must query CSI_I_EXTENDED_ATTRIBS directly, using the keys returned here as the join basis.