Search Results vendor_message




Overview
Explore in AI Chat

Overview

IBY_TRANSACTIONS_SET_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the IBY (Payments) product. It is marked VALID in ETRM 12.1.1 and 12.2.2 and presents settlement and authorization transaction data originating from payment card processing and payment settlement flows. The view consolidates transaction-level summary attributes with extended transaction detail, exposing a flattened, denormalized row per transaction record. Its principal role is to support reporting, reconciliation, and integration queries against settlement transactions without requiring consumers to join the base tables directly.

The naming convention reflects a "SET" transaction context — settlement transactions associated with a batch. The view is particularly relevant to users searching on BATCH_SEQ_NUM, which maps internally to the BATCHSEQNUM column of the underlying summary table and identifies the sequence of a transaction within its settlement batch.

Underlying Base Objects

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

  • IBY_TRXN_SUMMARIES_ALL — aliased as S in the view text; supplies the transaction summary attributes including amounts, currency, status, batch identifiers, and organization context.
  • IBY_TRXN_EXTENDED — aliased as E in the view text; supplies extended transaction attributes such as vendor codes, terminal identifiers, card BIN data, and completion codes.

The two objects are joined on the common transaction identifier: WHERE S.TRXNMID = E.TRXNMID. Because the sources are the _ALL summary table, the view is not itself partitioned by operating unit in its definition, but it exposes ORG_ID so that callers can filter by organization. The view performs column aliasing and renaming only; it applies no additional filtering predicates, so row volume is governed entirely by the joined base objects.

Key Columns

The view exposes twenty-three columns. The most significant include:

Common Use Cases and Queries

Typical uses include reconciling settlement batches, auditing batch sequence ordering, investigating vendor error messages, and feeding downstream card transaction reporting. A representative query filtering on batch sequence is:

  • SELECT batch_id, batch_seq_num, set_trxn_id, amount, currency, status FROM iby_transactions_set_v WHERE batch_id = :batch_id ORDER BY batch_seq_num;
  • SELECT org_id, vendor_code, vendor_message, completion_code FROM iby_transactions_set_v WHERE status = 'ERROR' AND org_id = :org_id;
  • SELECT card_bin, terminal_id, COUNT(*) FROM iby_transactions_set_v WHERE time BETWEEN :from_date AND :to_date GROUP BY card_bin, terminal_id;

Because the view is read-only and unindexed beyond its base objects, performance-sensitive queries should filter on ORG_ID, BATCH_ID, or TIME to leverage the underlying summary table.