Results for “csi_inst_catg_ext_attr_v”

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

Overview

CSI_INST_CATG_EXT_ATTR_V is an internal Oracle E-Business Suite view owned by the APPS schema and defined within the CSI (Install Base) product family. As its documentation states, it is an internal view used in the construction of CSI_INST_EXT_ATTR_ALL_V, a broader consolidation view of install base extended attributes. The view presents category-level extended attribute definitions associated with item instances held in the Oracle Install Base repository, resolving the relationship between instance records, their inventory items, and the item categories assigned to those items within the category set configured for install base processing.

Because the view is designated internal, Oracle does not document it as a supported public interface, and direct dependencies on it should be treated with caution during upgrades. In practice it surfaces extended attribute metadata — attribute code, name, category, description, and the twenty descriptive flexfield attribute columns — for records whose ATTRIBUTE_LEVEL equals 'CATEGORY'. This distinguishes it from instance-level or item-level attribute views. It is used primarily by the Install Base attribute resolution logic and by the CSI_INST_EXT_ATTR_ALL_V aggregation view.

Underlying Base Objects

The view is defined over four referenced objects, all accessed through APPS synonyms:

• CSI_I_EXTENDED_ATTRIBS — aliased CEA; supplies the extended attribute rows, including the ATTRIBUTE_LEVEL discriminator, flexfield segments, and audit columns.
• CSI_ITEM_INSTANCES — aliased CII; supplies the instance definition and the inventory item and master organization context.
• MTL_ITEM_CATEGORIES — aliased MIC; supplies the category assignments for the inventory item within a given organization and category set.
• CSI_INSTALL_PARAMETERS — supplies the single CATEGORY_SET_ID governing which category set drives install base attribute resolution.

The join is driven by organization, item, and category: MIC.ORGANIZATION_ID equals CII.INV_MASTER_ORGANIZATION_ID, MIC.INVENTORY_ITEM_ID equals CII.INVENTORY_ITEM_ID, the category set is restricted to the CSI_INSTALL_PARAMETERS value, CEA.ATTRIBUTE_LEVEL is fixed to 'CATEGORY', and CEA.ITEM_CATEGORY_ID equals MIC.CATEGORY_ID. The CII.INSTANCE_ID is additionally projected as SRC_INSTANCE_ID.

Key Columns

• ATTRIBUTE_ID / ATTRIBUTE_LEVEL — Unique identifier of the extended attribute row and its level (always CATEGORY here).
• INSTANCE_ID / SRC_INSTANCE_ID — The install base instance identifier, projected both from the attribute row and from CSI_ITEM_INSTANCES.
• MASTER_ORGANIZATION_ID / INVENTORY_ITEM_ID / ITEM_CATEGORY_ID — The item and category keys linking the attribute to a specific category assignment.
• ATTRIBUTE_CODE / ATTRIBUTE_NAME / ATTRIBUTE_CATEGORY / DESCRIPTION — Descriptive metadata for the extended attribute.
• ACTIVE_START_DATE / ACTIVE_END_DATE — Effective dating for the attribute definition.
• CONTEXT / ATTRIBUTE1–ATTRIBUTE15 — The descriptive flexfield context and segment values.
• CREATED_BY / CREATION_DATE / LAST_UPDATED_BY / LAST_UPDATE_DATE / LAST_UPDATE_LOGIN / OBJECT_VERSION_NUMBER — Standard audit and concurrency columns.

Common Use Cases and Queries

Typical reporting scenarios include listing category-level extended attributes for a given instance, or joining the view to CSI_ITEM_INSTANCES to enrich install base extracts with flexible attribute values.

• Retrieve attributes for a specific instance:
  SELECT attribute_code, attribute_name, attribute1, context FROM csi_inst_catg_ext_attr_v WHERE instance_id = :p_instance_id;
• List attributes by inventory item:
  SELECT inventory_item_id, attribute_code, attribute_name FROM csi_inst_catg_ext_attr_v WHERE inventory_item_id = :p_item_id ORDER BY attribute_code;
• Identify attributes active on a given date:
  SELECT attribute_code FROM csi_inst_catg_ext_attr_v WHERE SYSDATE BETWEEN active_start_date AND NVL(active_end_date, SYSDATE + 1);

Because the view is internal and its behavior depends on the CSI_INSTALL_PARAMETERS category set configuration, queries should be validated against the target instance before being embedded in production reports.