Results for “csi_t_extend_attribs_v”

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

Overview

CSI_T_EXTEND_ATTRIBS_V is an APPS-owned database view in the Oracle E-Business Suite Install Base (CSI) product module. It is defined on top of the transaction details extended attributes table, CSI_T_EXTEND_ATTRIBS, and its principal purpose is to resolve the attribute identifier held on a transaction record into its descriptive definition, while simultaneously exposing the transaction line context in which that attribute value was captured. In EBS 12.1.1 and 12.2.2 the object carries a VALID status and is documented in the ETRM repository as a reporting and integration access point for extended attribute data associated with install base transactions.

Because extended attribute rows describe customer-defined or flexfield-driven properties captured during a transaction, the raw base table stores only a numeric or character identifier pointing to the attribute definition. The view removes that indirection, presenting the attribute code, name, category, and level alongside the actual attribute value. This makes the view suitable for extracts, concurrent program queries, and integration interfaces that must report attribute semantics rather than internal identifiers.

Underlying Base Objects

The view definition joins three documented base objects, all referenced through APPS synonyms:

• CSI_T_EXTEND_ATTRIBS (aliased CTEA) — the transaction details extended attributes table supplying the attribute value, the source table name, the source identifier, effective dates, and the transaction line detail identifier.
• CSI_I_EXTENDED_ATTRIBS (aliased CIEA) — the item extended attributes definition table supplying ATTRIBUTE_CODE, ATTRIBUTE_NAME, ATTRIBUTE_CATEGORY, and ATTRIBUTE_LEVEL. This table is joined on ATTRIB_SOURCE_ID = ATTRIBUTE_ID.
• CSI_T_TXN_LINE_DETAILS (aliased CTLD) — the transaction line details table supplying CONFIG_INST_HDR_ID, CONFIG_INST_REV_NUM, and CONFIG_INST_ITEM_ID, joined on TXN_LINE_DETAIL_ID.

The join predicate restricts the result set to rows where ATTRIB_SOURCE_TABLE equals the literal 'CSI_I_EXTENDED_ATTRIBS', so the view only returns attributions sourced from the item-level extended attribute definition table. Rows whose source table is any other object are excluded. This restriction is essential to note, as it means the view is deliberately narrower than the base table it reads.

Key Columns

• TXN_ATTRIB_DETAIL_ID — primary identifier of the extended attribute detail row.
• TXN_LINE_DETAIL_ID — foreign key to the originating transaction line detail.
• CONFIG_INST_HDR_ID, CONFIG_INST_REV_NUM, CONFIG_INST_ITEM_ID — the configuration instance header, revision, and item context derived from the transaction line.
• ATTRIB_SOURCE_TABLE — name of the definition table; filtered to 'CSI_I_EXTENDED_ATTRIBS'.
• ATTRIB_SOURCE_ID — the identifier resolved against ATTRIBUTE_ID in the definition table; this is the column users most frequently search on to trace an attribute back to its definition.
• ATTRIBUTE_CODE, ATTRIBUTE_NAME, ATTRIBUTE_CATEGORY, ATTRIBUTE_LEVEL — descriptive metadata for the attribute.
• ATTRIBUTE_VALUE — the captured value for the attribute on the transaction.
• ACTIVE_START_DATE, ACTIVE_END_DATE — the effective period of the attribute detail row.
• OBJECT_VERSION_NUMBER — optimistic locking column inherited from the base table.

Common Use Cases and Queries

The view is typically used to enumerate the extended attributes captured against an install base transaction, to trace a specific attribute value back to its definition, or to feed downstream reporting that requires attribute semantics. The ATTRIB_SOURCE_ID is the standard join key when correlating to attribute definitions.

Listing attributes for a transaction line:

• SELECT txn_line_detail_id, attribute_code, attribute_name, attribute_value FROM csi_t_extend_attribs_v WHERE txn_line_detail_id = :p_line_detail_id;

Resolving a known source identifier:

• SELECT attribute_code, attribute_name, attribute_value, active_start_date, active_end_date FROM csi_t_extend_attribs_v WHERE attrib_source_id = :p_attrib_source_id;

Filtering by attribute category and level:

• SELECT config_inst_hdr_id, attribute_category, attribute_level, attribute_value FROM csi_t_extend_attribs_v WHERE attribute_category = :p_category;

Because the view filters to a single source table, queries requiring attribute sources other than CSI_I_EXTENDED_ATTRIBS must be directed at CSI_T_EXTEND_ATTRIBS directly. All access should be performed against the APPS synonym in a supported EBS session, with appropriate privileges on the underlying CSI objects.