Search Results csi_inst_extend_attrib_v




Overview
Explore in AI Chat

Overview

The APPS.CSI_INST_EXTEND_ATTRIB_V view is a reporting and forms-support object within the Oracle E-Business Suite CSI – Install Base product. Its documented purpose is to support the Form used to define the Instance Extended Attributes Template. In Oracle Install Base, extended attributes allow customers to capture organization-specific data against an installed instance that is not covered by the seeded attribute set. This view joins the stored attribute values to their definitions, so that a single row presents both the descriptive metadata (name, code, category, level) and the corresponding value held for a specific instance.

The view is owned by the APPS schema and is documented as VALID in the ETRM reference for 12.1.1 and 12.2.2. It follows the standard Oracle EBS convention of exposing the WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), the DFF context columns (CONTEXT, ATTRIBUTE1–ATTRIBUTE15), and the OBJECT_VERSION_NUMBER used for optimistic locking and OAF-based (OA Framework) screens. Because it carries these standard columns, the view is suitable both as a form data source and as a read-only foundation for reporting and integration extracts.

Underlying Base Objects

Per the documented implementation, the view is defined over two base objects, each referenced through an APPS synonym:

  • CSI_IEA_VALUES (CIV) — the values table, holding one row per attribute value assigned to an instance.
  • CSI_I_EXTENDED_ATTRIBS (CIEA) — the extended attribute definition/template table, holding the attribute code, name, category, level, and description.

The two are joined on CIV.ATTRIBUTE_ID = CIEA.ATTRIBUTE_ID, which links each stored value to the template definition that governs it. The view is therefore an inner join: only values having a matching attribute definition are returned. The primary key of the driving row remains ATTRIBUTE_VALUE_ID from CSI_IEA_VALUES, with ATTRIBUTE_ID acting as the foreign key into the template definition.

Key Columns

  • ATTRIBUTE_VALUE_ID — unique identifier of the stored attribute value record (source: CSI_IEA_VALUES).
  • ATTRIBUTE_ID — identifier of the extended attribute definition; the join key to CSI_I_EXTENDED_ATTRIBS.
  • ATTRIBUTE_LEVEL, ATTRIBUTE_CODE, ATTRIBUTE_NAME, ATTRIBUTE_CATEGORY, DESCRIPTION — definition-level metadata describing the extended attribute (source: CSI_I_EXTENDED_ATTRIBS).
  • INSTANCE_ID — the installed instance to which the value belongs, linking back to the Install Base instance record.
  • ATTRIBUTE_VALUE — the actual value captured for the instance.
  • ACTIVE_START_DATE / ACTIVE_END_DATE — date-range effectivity controlling when the value is valid.
  • CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments available on the value record.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit (WHO) columns.
  • OBJECT_VERSION_NUMBER — optimistic-locking version number used by OAF pages and concurrency control.

Common Use Cases and Queries

Typical uses include validating extended attribute setup for an instance, exporting instance-level attribute data for integration, and troubleshooting values that appear or fail to appear in the Instance Extended Attributes Template form.

List extended attributes for a specific instance:

SELECT attribute_code, attribute_name, attribute_value,
       active_start_date, active_end_date
FROM   apps.csi_inst_extend_attrib_v
WHERE  instance_id = :p_instance_id
ORDER  BY attribute_category, attribute_name;

Report all active extended attribute values assigned to a given attribute definition:

SELECT instance_id, attribute_value
FROM   apps.csi_inst_extend_attrib_v
WHERE  attribute_id = :p_attribute_id
AND    TRUNC(SYSDATE) BETWEEN NVL(active_start_date, SYSDATE)
                          AND NVL(active_end_date, SYSDATE);

Exposing definition-level columns such as ATTRIBUTE_NAME, ATTRIBUTE_CATEGORY, and ATTRIBUTE_LEVEL alongside the stored value, the view removes the need to join CSI_IEA_VALUES and CSI_I_EXTENDED_ATTRIBS manually in custom reports. Note that the inner join means values whose definitions have been removed will not be returned; where orphaned data is a concern, query the base tables directly.