Search Results iby_trxn_fi




Overview
Explore in AI Chat

Overview

IBY_TRXN_FI is a transaction-detail table in the Oracle Payments (IBY) module of Oracle E-Business Suite, present in both release 12.1.1 and 12.2.2. It stores the payment-request attributes that apply specifically to payment systems supporting both bank account transfers and credit card transactions, such as financial institutions. In the IBY data model, IBY_TRXN_SUMMARIES_ALL captures the common payment request header, while IBY_TRXN_FI holds the supplemental, instrument-specific payload required by the funding and settlement layer. The table is owned by the IBY schema and is recorded as VALID in ETRM.

The documented primary key is the unique constraint IBY_TRXN_FI_UK, backed by the unique index IBY_TRXN_FI_TRXNMID_U1 on the single column TRXNMID. Because the business key collapses to the same column as the surrogate identifier, the metadata's heuristic Data Vault classification is satellite-leaning: IBY_TRXN_FI behaves less like an independent hub and more like a descriptive satellite attached to the transaction summary, carrying attributes that qualify a parent transaction row. This classification is offered as a modeling suggestion rather than a physical designation.

Key Information Stored

The documented physical schema for 12.2.2 contains 14 columns. The most significant are listed below.

  • TRXNMID — The transaction identifier and the sole component of the unique key IBY_TRXN_FI_TRXNMID_U1. It is the join key to the parent summary table and functions as both the surrogate primary key and the effective business key here.
  • SPLITID — References the payment split, allowing a single transaction to retain instrument-specific detail at the split level.
  • PSREQID — Payment service request identifier, linking the payment request back to the service request that originated or processed it.
  • REFERENCECODE — The reference code echoed to or returned by the payment system and used for reconciliation with the financial institution.
  • AUXMSG — Auxiliary message or supplementary text returned by or sent to the external payment system.
  • SRVID — Service identifier indicating which payment service or system handled the request.
  • PROCESSFEE — The processing fee associated with the transaction.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework to detect concurrent updates.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns recording who created and last modified the row and when.
  • SECURITY_GROUP_ID — Multi-tenant security grouping column, with a documented foreign key to FND_SECURITY_GROUPS.

Common Use Cases and Queries

IBY_TRXN_FI is principally used for reconciliation and troubleshooting of payments routed through financial institutions and credit card processors. Typical queries join it to the transaction summary on TRXNMID to retrieve the reference code and processing fee for a given payment.

  • Reconciliation reporting: select the reference code and processing fee for externally settled transactions.
  • Diagnostics: retrieve AUXMSG and SRVID when a payment fails or is rejected by the payment system.
  • Fee analysis: aggregate PROCESSFEE by service or period.

A representative pattern is SELECT s.TRXNMID, f.REFERENCECODE, f.SRVID, f.PROCESSFEE FROM IBY_TRXN_SUMMARIES_ALL s, IBY_TRXN_FI f WHERE s.TRXNMID = f.TRXNMID. Constrain by LAST_UPDATE_DATE for incremental extracts.

Related Objects

  • IBY_TRXN_SUMMARIES_ALL — Parent table joined on TRXNMID; the documented foreign key direction is IBY_TRXN_FI.TRXNMID to this table.
  • FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID.
  • IBY_TRXN_SUMMARIES and associated summary views — Contextual parent entities for the transaction record.
  • IBY_PAYMENTS and IBY_PAY_INSTRUCTIONS_ALL — Related payment objects that consume transaction-level detail for settlement.
  • IBY_DOCS_PAYABLE_ALL — Links payment documents to the underlying transaction for reporting.

Where the metadata is limited to the 14 documented columns, the descriptions above reflect the standard IBY transaction-detail role; the FK and unique-key facts are taken directly from the ETRM record.