Results for “extend_value”

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

Overview

IBY_TRXN_EXTENSIBILITY is a Payments (IBY) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores extensibility attribute values attached to payment transaction summaries. The table exists to hold the flexible, name-value pairs that extend the core transaction record without requiring schema changes to the base transaction tables. Each row associates a named extensibility attribute (EXTEND_NAME) with its corresponding value (EXTEND_VALUE) and links that pair to a parent transaction summary record.

Under the heuristic Data Vault classification derived from its foreign key structure, this table is satellite-leaning. It behaves as a satellite attached to a parent transaction entity: its grain is finer than that of the parent, it carries descriptive and historical attribute data rather than defining relationships between two or more hubs, and its primary key is a surrogate identifier rather than a composite business key drawn from multiple source entities. In modeling terms, IBY_TRXN_EXTENSIBILITY is best treated as a dependent child of the transaction summary, not as a hub or a link.

Key Information Stored

The table is documented with ten columns. The most significant are summarized below.

• TRXN_EXTEND_ID — The surrogate primary key of the table, enforced through the IBY_TRXN_EXTENSIBILITY_PK constraint and also covered by the unique index IBY_TRXN_EXTENSIBILITY_TXID_U1. This is the row-level identifier for a single extensibility entry.
• TRXNMID — The foreign key column that references IBY_TRXN_SUMMARIES_ALL. This column is the join path back to the parent payment transaction summary and defines the ownership relationship between a transaction summary and its extensibility records.
• EXTEND_NAME — The name of the extensibility attribute. Together with TRXNMID, this column identifies which flexible attribute a given row is carrying, effectively acting as the attribute discriminator within a transaction.
• EXTEND_VALUE — The stored value for the named extensibility attribute. This is the payload column and the primary target of reporting and extraction queries against the table.
• OBJECT_VERSION_NUMBER — The optimistic locking column used by the Oracle Application Framework to detect concurrent updates.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record who created and last modified each row and when, supporting auditing and incremental extraction.

Although the surrogate primary key uniquely identifies each row, the meaningful business identity of a record is the combination of TRXNMID and EXTEND_NAME, since that pair determines which attribute value is held for a given transaction summary.

Common Use Cases and Queries

The most frequent use of this table is retrieving all extensibility attributes for a specific payment transaction summary, or pivoting named attributes into reporting columns.

• Retrieve all attributes for a transaction: SELECT EXTEND_NAME, EXTEND_VALUE FROM IBY.IBY_TRXN_EXTENSIBILITY WHERE TRXNMID = :p_trxnm_id;
• Join to the parent summary to enrich reporting: SELECT s.TRXNMID, e.EXTEND_NAME, e.EXTEND_VALUE FROM IBY.IBY_TRXN_SUMMARIES_ALL s JOIN IBY.IBY_TRXN_EXTENSIBILITY e ON e.TRXNMID = s.TRXNMID;
• Locate a specific attribute value across transactions by filtering on EXTEND_NAME and EXTEND_VALUE for reconciliation or exception reporting.
• Incremental extraction for data warehousing, filtering on LAST_UPDATE_DATE to capture changed extensibility rows.
• Audit and troubleshooting, using CREATED_BY and LAST_UPDATED_BY to determine which user introduced or modified a given attribute value.

Related Objects

The following objects are most significant when working with this table.

• IBY_TRXN_SUMMARIES_ALL — The parent table. Joined via IBY_TRXN_EXTENSIBILITY.TRXNMID = IBY_TRXN_SUMMARIES_ALL.TRXNMID. This is the single documented foreign key relationship and the primary dependency of the table.
• IBY_TRXN_EXTENSIBILITY_PK — The primary key constraint on TRXN_EXTEND_ID.
• IBY_TRXN_EXTENSIBILITY_TXID_U1 — The unique index supporting the primary key column.

Because the documented metadata identifies only the transaction summary foreign key, additional related payment objects should be confirmed against the specific implementation before being relied upon in custom reporting.