Search Results copy_transaction_extension

Overview

IBY.IBY_FNDCPT_TX_EXTENSIONS is a transaction extension table in the Oracle Payments (IBY) module of Oracle E-Business Suite, available in both 12.1.1 and 12.2.2. It stores supplementary, payment-specific attributes that are not held on the core payment or transaction records themselves. Its name reflects its function: it extends the Funds Capture transaction model with channel-level, instrument-level, and payer-level enrichment data — security codes, authorization evidence, purchase order references, and originating application context.

The table is owned by the IBY schema and is validated in the ETRM 12.2.2 repository. Its primary key is IBY_FNDCPT_TX_EXTENSIONS_PK, defined on the single column TRXN_EXTENSION_ID, which is also backed by the unique index IBY_FNDCPT_TX_EXTENSIONS_U1. The documented physical schema contains 27 columns. From a heuristic Data Vault perspective, the FK topology suggests a satellite-leaning classification: the table hangs off multiple parent dimensions (payment channel, instrument assignment, originating application, external payer) while being referenced by a wide set of transactional consumers. This positioning is consistent with an attribute-bearing extension record rather than an independent hub.

Key Information Stored

The surrogate primary key, TRXN_EXTENSION_ID, uniquely identifies each extension row and is the column other modules reference. The most operationally significant columns include:

• TRXN_EXTENSION_ID — surrogate primary key and the single unique business-key candidate; the join target for all downstream consumers.
• PAYMENT_CHANNEL_CODE — FK to IBY_FNDCPT_PMT_CHNNLS_B; identifies the funds capture channel (for example, credit card, direct debit, or purchase card).
• EXT_PAYER_ID — FK to IBY_EXTERNAL_PAYERS_ALL; the payer associated with the transaction.
• INSTR_ASSIGNMENT_ID — FK to IBY_PMT_INSTR_USES_ALL; ties the extension to a specific instrument assignment.
• INSTRUMENT_SECURITY_CODE and INSTR_SEC_CODE_LENGTH — card/instrument verification data and its length.
• INSTR_CODE_SEC_SEGMENT_ID — security segment reference used for instrument code validation.
• VOICE_AUTHORIZATION_FLAG, VOICE_AUTHORIZATION_DATE, VOICE_AUTHORIZATION_CODE — captured voice-authorization evidence for telephone-order payments.
• ORDER_ID, PO_NUMBER, PO_LINE_NUMBER — order and purchase-order context passed from the originating application.
• TRXN_REF_NUMBER1 and TRXN_REF_NUMBER2 — free-form external transaction references.
• ORIGIN_APPLICATION_ID — FK to FND_APPLICATION; the application that created the transaction.
• PAYMENT_SYSTEM_ORDER_NUMBER, SEQ_TYPE_LAST, and ENCRYPTED — payment system sequencing and encryption indicators.
• TANGIBLEID, ADDITIONAL_INFO — supplementary identifying and descriptive data.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, and OBJECT_VERSION_NUMBER for concurrency control.

Common Use Cases and Queries

The table is typically queried when reconciling payment transactions to their originating business documents, or when auditing authorization and security-code capture. A common pattern joins the extension to its channel definition and originating application:

• Channel enrichment: SELECT t.trxn_extension_id, c.payment_channel_code, t.po_number FROM iby_fndcpt_tx_extensions t, iby_fndcpt_pmt_chnnls_b c WHERE t.payment_channel_code = c.payment_channel_code;
• Receivables traceability: join AR_CASH_RECEIPTS_ALL or RA_CUSTOMER_TRX_ALL to the extension on PAYMENT_TRXN_EXTENSION_ID = TRXN_EXTENSION_ID to attribute a receipt or invoice line to a payment channel and instrument assignment.
• Voice-authorization audit: filter on VOICE_AUTHORIZATION_FLAG = 'Y' and report VOICE_AUTHORIZATION_DATE and VOICE_AUTHORIZATION_CODE.
• Origin analysis: aggregate by ORIGIN_APPLICATION_ID joined to FND_APPLICATION to determine which modules generate the most extension records.

Because the table is referenced by order capture, service contracts, and public-sector modules, it also serves as a cross-module integration point when tracing a single payment across the EBS footprint.

Related Objects

• IBY_FNDCPT_PMT_CHNNLS_B — joined on PAYMENT_CHANNEL_CODE; defines the funds capture channel.
• IBY_PMT_INSTR_USES_ALL — joined on INSTR_ASSIGNMENT_ID; supplies instrument assignment detail.
• IBY_EXTERNAL_PAYERS_ALL — joined on EXT_PAYER_ID; the external payer master.
• FND_APPLICATION — joined on ORIGIN_APPLICATION_ID; identifies the originating EBS application.
• AR_CASH_RECEIPTS_ALL and RA_CUSTOMER_TRX_ALL / RA_CUSTOMER_TRX_LINES_ALL — reference PAYMENT_TRXN_EXTENSION_ID for receivables traceability.
• RA_INTERFACE_LINES_ALL — references the extension during AutoInvoice import.
• OE_PAYMENTS and OE_PAYMENTS_IFACE_ALL — order management payment records referencing TRXN_EXTENSION_ID.
• OKS_K_HEADERS_B and OKS_K_LINES_B — service contract headers and lines carrying payment extension references.