Search Results iby_fndcpt_tx_extensions_u1

Overview

IBY.IBY_FNDCPT_TX_EXTENSIONS is a transaction-attribute extension table within the Oracle Payments (IBY) module. It stores supplementary payment attributes associated with a given funds capture transaction. While the core funds capture transaction record resides in the parent transaction tables, this object carries the channel-specific, instrument-specific, and authorization-specific details that are not universal to every transaction type. In Oracle EBS 12.1.1 and 12.2.2, the table is owned by the IBY schema, resides in the APPS_TS_TX_DATA tablespace, and is documented as VALID. It is registered in FND Design Data as IBY.IBY_FNDCPT_TX_EXTENSIONS.

Heuristic Data Vault classification mined from the foreign-key structure suggests a satellite-leaning model. The table is keyed by a single surrogate identifier and hangs off multiple parent hubs and links, which is characteristic of a satellite carrying descriptive, non-key context about a transaction event rather than an independently identifiable business entity.

Key Information Stored

The table is anchored by the surrogate primary key TRXN_EXTENSION_ID, a NUMBER(15) populated by the sequence IBY_FNDCPT_TX_EXTENSIONS_S.nextval. The unique index IBY_FNDCPT_TX_EXTENSIONS_U1 enforces uniqueness on this column, which is the documented business-key candidate at the physical level. Key attributes include:

• PAYMENT_CHANNEL_CODE — the payment channel for the transaction; foreign key to IBY_FNDCPT_PMT_CHNNLS_B.
• EXT_PAYER_ID — foreign key to IBY_EXTERNAL_PAYERS_ALL.EXT_PAYER_ID, linking the extension to the external payer.
• INSTR_ASSIGNMENT_ID — foreign key to IBY_PMT_INSTR_USES_ALL.INSTRUMENT_PAYMENT_USE_ID, tying the record to the payment instrument assignment.
• INSTRUMENT_SECURITY_CODE — the encrypted card security code (CVV2, CVVC, or CID). Companion INSTR_SEC_CODE_LENGTH supports data compression.
• VOICE_AUTHORIZATION_FLAG, VOICE_AUTHORIZATION_DATE, and VOICE_AUTHORIZATION_CODE — capture voice-authorization evidence.
• ORDER_ID, PO_NUMBER, and PO_LINE_NUMBER — commercial reference data indexed via IBY_FNDCPT_TX_EXTENSIONS_O_N1.
• TRXN_REF_NUMBER1 and TRXN_REF_NUMBER2 — optional caller-supplied transaction identifiers.
• ADDITIONAL_INFO — free-text overflow field.
• ORIGIN_APPLICATION_ID — foreign key to FND_APPLICATION identifying the originating application.
• Standard WHO/audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

This table is most frequently joined back to the operational tables that reference it. A typical reporting query resolves the extension to its owning receipt or transaction:

• Receipt-to-extension lookup: join AR_CASH_RECEIPTS_ALL.PAYMENT_TRXN_EXTENSION_ID = IBY_FNDCPT_TX_EXTENSIONS.TRXN_EXTENSION_ID to retrieve voice-authorization or channel detail for a receipt.
• Channel analysis: group by PAYMENT_CHANNEL_CODE after joining IBY_FNDCPT_PMT_CHNNLS_B to profile transaction volumes by channel.
• Instrument audit: join on INSTR_ASSIGNMENT_ID to IBY_PMT_INSTR_USES_ALL to reconcile transactions against payment instrument assignments.
• Order traceability: the O_N1 index on ORDER_ID supports lookups correlating e-commerce order numbers to funds capture records.
• Payer reconciliation: join EXT_PAYER_ID to IBY_EXTERNAL_PAYERS_ALL to attribute transactions to external payers.

Related Objects

The extension is referenced by numerous consuming tables via PAYMENT_TRXN_EXTENSION_ID or TRXN_EXTENSION_ID:

• AR_CASH_RECEIPTS_ALL — via PAYMENT_TRXN_EXTENSION_ID.
• RA_CUSTOMER_TRX_ALL and RA_CUSTOMER_TRX_LINES_ALL — via PAYMENT_TRXN_EXTENSION_ID.
• RA_INTERFACE_LINES_ALL — via PAYMENT_TRXN_EXTENSION_ID for interface processing.
• OE_PAYMENTS and OE_PAYMENTS_IFACE_ALL — via TRXN_EXTENSION_ID.
• OKS_K_HEADERS_B, OKS_K_LINES_B, and their history tables — via TRXN_EXTENSION_ID.
• ASO_PAYMENTS and PV_PG_ENRL_REQUESTS — via TRXN_EXTENSION_ID.

Upstream, the table depends on IBY_FNDCPT_PMT_CHNNLS_B, IBY_PMT_INSTR_USES_ALL, IBY_EXTERNAL_PAYERS_ALL, and FND_APPLICATION. Index IBY_FNDCPT_TX_EXTENSIONS_IU_N2 on INSTR_ASSIGNMENT_ID and IBY_FNDCPT_TX_EXTENSIONS_O_N1 on ORDER_ID support the predominant access paths.