Search Results csi_t_extend_attribs




Overview
Explore in AI Chat

Overview

The table CSI_T_EXTEND_ATTRIBS is a core transactional data object within the Oracle E-Business Suite (EBS) Install Base (CSI) module. It functions as the primary repository for capturing and storing extended attribute values associated with individual transaction line details. In the context of asset and item instance management, extended attributes provide a flexible mechanism to track supplementary, user-defined information beyond the standard descriptive fields. This table's role is to persist these custom attribute values specifically for transactional events, such as installations, movements, or updates, thereby creating a detailed audit trail of instance configuration changes over its lifecycle. Its structure is integral to the Install Base's capability to model complex asset configurations and service histories.

Key Information Stored

The table's primary purpose is to link a transaction detail line with a specific extended attribute and its assigned value. The critical columns facilitating this are the foreign key references. The TXN_LINE_DETAIL_ID column links each attribute entry to a specific record in the CSI_T_TXN_LINE_DETAILS table, anchoring the data to a particular transactional event. The ATTRIB_SOURCE_ID column serves a dual purpose, acting as the foreign key to both the CSI_I_EXTENDED_ATTRIBS table (which defines the attribute itself, like 'Serial Number' or 'Warranty Expiry Date') and the CSI_IEA_VALUES table (which stores the permissible value for list-type attributes). The unique identifier for each row is the TXN_ATTRIB_DETAIL_ID, which is the table's primary key. The table likely contains additional columns to store the actual attribute value (for non-list types), creation dates, and last update information, standard in EBS transactional tables.

Common Use Cases and Queries

This table is central to reporting and data extraction related to asset transactions. A common use case is generating a detailed report of all configuration changes made during a specific service event, showing the before and after states of extended attributes. Another scenario involves querying the installation history of assets with a specific custom attribute, such as all servers with a particular firmware version installed in a given period. A typical SQL pattern involves joining this table to its parent transaction and attribute definition tables:

  • Joining to CSI_T_TXN_LINE_DETAILS to get transaction context (e.g., transaction type, date, instance ID).
  • Joining to CSI_I_EXTENDED_ATTRIBS to get the attribute name and data type.
  • Left-joining to CSI_IEA_VALUES to get the descriptive meaning of coded attribute values.

Queries against this table are essential for compliance reporting, asset lifecycle analysis, and troubleshooting instance data integrity.

Related Objects

The CSI_T_EXTEND_ATTRIBS table exists within a well-defined schema relationship, primarily serving as a child table to transaction details and a referencing table for attribute definitions. The documented foreign key relationships are as follows:

  • Parent References (This table references):
    • CSI_T_TXN_LINE_DETAILS via TXN_LINE_DETAIL_ID: Each extended attribute record is tied to a specific transaction line.
    • CSI_I_EXTENDED_ATTRIBS via ATTRIB_SOURCE_ID: Links to the master definition of the extended attribute.
    • CSI_IEA_VALUES via ATTRIB_SOURCE_ID: Links to the valid value for the attribute when it is of a list type.
  • Child Reference (Referenced by):
    • XDP_WORKLIST_DETAILS via TXN_ATTRIB_DETAIL_ID: Indicates that transactional attribute data can be referenced by the Oracle Service Fulfillment Manager (XDP) worklist for service task execution and tracking.

The primary key constraint CSI_T_EXTEND_ATTRIBS_PK on TXN_ATTRIB_DETAIL_ID ensures the uniqueness of each attribute record per transaction.