Search Results payment_name




Overview
Explore in AI Chat

Overview

IBY_TRANSACTIONS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IBY (Payments) product family. It exposes payment transaction records processed through Oracle Payments and is available in both EBS 12.1.1 and 12.2.2, where it is documented as a VALID object in the ETRM repository. The view presents a consolidated, denormalized projection of transaction-level and transaction-summary-level data, joining the core payments transaction table to its summary table. Its primary role is to give external applications, custom reports, and integration layers a single, stable, and simplified read interface over the lower-level Payments tables, which are more complex and internally keyed. For users searching on "payment_type," this view is significant because it exposes a PAYMENT_TYPE column derived from the underlying PAYMENTMETHODNAME attribute of the summary table, making the payment instrument used for a transaction directly queryable without resolving base-table joins.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

  • IBY_TRXN_CORE (SYNONYM) — the core transaction table holding fundamental identifiers such as the internal transaction identifier (TRXNMID), organization identifier, and other transactional attributes.
  • IBY_TRXN_SUMMARIES_ALL (SYNONYM) — the transaction summary table that stores aggregated and descriptive payment attributes, including payment method name, instructions, batch identifiers, authorization codes, and acquirer-related fields.

The two objects are joined on the transaction identifier: IBY_TRXN_SUMMARIES_ALL.TRXNMID = IBY_TRXN_CORE.TRXNMID. This one-to-one relationship on the transaction key means each row in the view corresponds to a single payment transaction summary record enriched with its core record. Because both base objects are referenced as synonyms and the view is owned by APPS, it is grant-accessible to other EBS schemas and to custom reporting users.

Key Columns

  • PAYMENT_TYPE — aliased from PAYMENTMETHODNAME; identifies the payment method used (for example, credit card, purchase card, or bank transfer).
  • ORDER_ID — aliased from TANGIBLEID; the tangible order identifier associated with the transaction.
  • MERCHANT_ID — aliased from PAYEEID; the payee identifier on the transaction.
  • VENDOR_ID — aliased from BEPID; the payment system/bank enterprise partner identifier.
  • TRXN_TYPE — aliased from TRXNTYPEID; the transaction type indicator.
  • AMOUNT and CURRENCY — the transaction amount and currency code (aliased from CURRENCYNAMECODE).
  • TIME — aliased from UPDATEDATE; the transaction update timestamp.
  • STATUS — the current processing status of the transaction.
  • MERCHBATCHID — aliased from BATCHID; the merchant batch identifier used for settlement grouping.
  • PAYMENT_NAME — aliased from INSTRNAME; the payment instruction name.
  • AUTHCODE, AVSCODE, REFERENCECODE — authorization, address verification, and reference values returned by the payment processor.
  • VENDOR_CODE, VENDOR_MESSAGE, ERROR_LOCATION, ACQUIRER, AUXMSG, TERMINALID, TRACENUMBER — processor and terminal diagnostic fields useful for reconciliation and error analysis.
  • ORG_ID — the operating unit identifier, supporting multi-org filtering.

Common Use Cases and Queries

Typical usage includes payment transaction reporting, reconciliation against processor settlement files, and integration extracts for external financial systems. Because the view is multi-org enabled via ORG_ID, queries should be filtered by operating unit, often through the MO operating unit context.

To list transactions by payment method:

  • SELECT order_id, merchant_id, payment_type, amount, currency, status, time FROM iby_transactions_v WHERE payment_type = 'CREDIT_CARD' AND org_id = :p_org_id;

To reconcile authorizations for a given batch:

  • SELECT merchbatchid, payment_name, authcode, avscode, referencencode, amount FROM iby_transactions_v WHERE merchbatchid = :p_batch_id;

To analyze processor errors and terminal activity:

  • SELECT tracenumber, terminalid, acquirer, vendor_message, error_location, auxmsg FROM iby_transactions_v WHERE status = 'ERROR' ORDER BY time DESC;

In all cases the documented metadata confirms the view should never be written to; it is read-only and should be used for query and reporting purposes only.