Search Results batch_seq_num




Overview
Explore in AI Chat

Overview

The view APPS.IBY_TRANSACTIONS_SET_V is a reporting and integration construct within the Oracle E-Business Suite Payments (IBY) module. It presents a consolidated, denormalized projection of payment transaction data sourced from the Oracle Payments transaction summary and extended transaction tables. The view exposes payment transaction attributes using external or gateway-oriented naming conventions, such as ORDER_ID, MERCHANT_ID, VENDOR_ID, and TRXN_TYPE, alongside settlement-related fields including SET_TRXN_ID, BATCH_ID, and BATCH_SEQ_NUM.

Because it joins summary-level transaction records to extended gateway metadata, the view serves as a single point of reference for payment transactions that have been transmitted to or processed by a payment gateway or settlement engine. Its column aliases reflect SET (Secure Electronic Transaction) and BEP (Back-End Processor) terminology, making it suitable for reconciliation, settlement reporting, and integration with external payment processors.

Underlying Base Objects

The view is defined over two documented base objects:

  • IBY_TRXN_SUMMARIES_ALL (referenced as a synonym) — supplies the core transaction summary attributes, aliased as S in the view definition.
  • IBY_TRXN_EXTENDED (referenced as a synonym) — supplies extended gateway and processor metadata, aliased as E.

The join condition is S.TRXNMID = E.TRXNMID, meaning the two objects are correlated on the transaction master identifier. This one-to-one relationship between the summary record and its extended detail produces a single row per transaction master within the view. The owner is APPS, and the view is therefore accessible to EBS responsibilities and custom code running under the APPS schema in both 12.1.1 and 12.2.2.

Key Columns

The view exposes several categories of columns:

Common Use Cases and Queries

The view is commonly used to reconcile gateway settlement files, analyze batch composition, and diagnose transaction failures through completion and error codes. A typical query filtering by batch sequence number is:

  • SELECT batch_id, batch_seq_num, order_id, set_trxn_id, amount, currency, status, batch_trxn_status FROM apps.iby_transactions_set_v WHERE batch_id = :p_batch_id ORDER BY batch_seq_num;
  • SELECT order_id, vendor_message, completion_code, error_location FROM apps.iby_transactions_set_v WHERE batch_trxn_status = 'FAILED';
  • SELECT batch_id, COUNT(*), SUM(amount) FROM apps.iby_transactions_set_v WHERE org_id = :p_org_id GROUP BY batch_id;

These queries support settlement auditing, failure analysis, and batch-level financial aggregation within the Oracle Payments framework.