Search Results iby_fndcpt_tx_extensions

Overview

The IBY_FNDCPT_TX_EXTENSIONS table is a core repository within the Oracle E-Business Suite (EBS) Payments module (IBY). It serves as the master table for registering and storing metadata for Funds Capture transactions. Funds Capture refers to the process of authorizing and settling electronic payments, such as credit card charges. The table's primary role is to act as a central reference point, created by source applications like Receivables (AR) or Order Management (OM) via the public API IBY_FNDCPT_TRXN_PUB. Each record represents a unique payment transaction extension that links the originating application's data to the Payments engine's processing lifecycle, enabling tracking, reporting, and operational management of payment flows.

Key Information Stored

The table's structure is designed to establish critical relationships and capture transaction context. Its primary key is TRXN_EXTENSION_ID, a unique identifier for each payment transaction extension. Key foreign key columns define its integration with other EBS entities: ORIGIN_APPLICATION_ID links to FND_APPLICATION to identify the source product; INSTR_ASSIGNMENT_ID references IBY_PMT_INSTR_USES_ALL to tie the transaction to a specific payment instrument (e.g., a credit card); and PAYMENT_CHANNEL_CODE references IBY_FNDCPT_PMT_CHNNLS_B to define the payment method channel. Additional columns like INSTR_CODE_SEC_SEGMENT_ID link to security segments for compliance. Collectively, these fields create a comprehensive footprint of a payment transaction's origin, method, and instrument.

Common Use Cases and Queries

This table is central for troubleshooting payment flows, auditing transaction history, and building custom integrations. A common reporting use case involves joining to transaction summaries and source application tables to trace a payment's journey. For instance, to find details for transactions originating from Receivables, a query might join to RA_CUSTOMER_TRX_ALL. Technical support often queries this table to verify a transaction was successfully registered in IBY before processing.

• Sample Query (Basic Transaction Lookup):
  SELECT ext.trxn_extension_id, ext.origin_application_id, app.application_name
  FROM iby.iby_fndcpt_tx_extensions ext,
  fnd_application app
  WHERE ext.origin_application_id = app.application_id
  AND ext.instr_assignment_id = <instrument_id>;
• Integration Verification: Developers use the documented public APIs (Create_Transaction_Extension, Copy_Transaction_Extension) to populate this table, ensuring all mandatory foreign key relationships are correctly established for downstream payment operations.

Related Objects

The IBY_FNDCPT_TX_EXTENSIONS table has extensive relationships, underscoring its pivotal role. It is referenced by numerous key transactional tables, primarily in Receivables (AR), such as AR_CASH_RECEIPTS_ALL, RA_CUSTOMER_TRX_ALL, and RA_INTERFACE_LINES_ALL, via their PAYMENT_TRXN_EXTENSION_ID columns. Within the IBY schema, it is directly linked to operational tables like IBY_FNDCPT_TX_OPERATIONS (for transaction steps) and IBY_TRXN_SUMMARIES_ALL (for high-level summaries). It also maintains a recursive relationship with IBY_FNDCPT_TX_XE_COPIES for copied transactions. The defining foreign keys link it to foundational tables for payment channels (IBY_FNDCPT_PMT_CHNNLS_B), payment instruments (IBY_PMT_INSTR_USES_ALL), and application definitions (FND_APPLICATION).