Search Results voice_authorization_code




Overview

IBY_TRXN_EXTENSIONS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the IBY (Payments) product. It consolidates payment transaction extension data with related instrument, channel, and account attributes, presenting a single denormalized row per transaction extension record. The view joins the extension table IBY_FNDCPT_TX_EXTENSIONS to payment channel definitions, payment instrument assignments, credit card data, external bank account data, trading parties, and transaction summaries. Its principal role is to expose instrument-level detail — card numbers, bank account and routing identifiers, voice authorization data, purchase order references, and tangible identifiers — for use in payment reconciliation reporting, instrument validation, and downstream integration. Because the view derives several flag columns by inspecting IBY_TRXN_SUMMARIES_ALL, it is also used to answer settlement- and authorization-state questions, which is the context in which users commonly search for a settled_flag.

Underlying Base Objects

The documented base objects referenced by the view include IBY_FNDCPT_TX_EXTENSIONS (the driving synonym, aliased X), IBY_FNDCPT_TX_OPERATIONS (OP), IBY_PMT_INSTR_USES_ALL (U), IBY_CREDITCARD (C), IBY_CREDITCARD_ISSUERS_B and IBY_CREDITCARD_ISSUERS_TL (surfaced through the view alias I), IBY_EXT_BANK_ACCOUNTS (B), IBY_FNDCPT_PMT_CHNNLS_B and IBY_FNDCPT_PMT_CHNNLS_TL (P), IBY_TRXN_SUMMARIES_ALL, HZ_PARTIES, HZ_ORGANIZATION_PROFILES, FND_APPLICATION, FND_LOOKUPS, FND_GLOBAL, and the IBY_FNDCPT_TRXN_PUB package. The channel and issuer name columns are resolved through the translated (_TL) and base (_B) table pairs, while IBY_FNDCPT_TRXN_PUB.GET_TANGIBLE_ID is invoked as a scalar function to derive a tangible identifier. Three correlated subqueries against IBY_TRXN_SUMMARIES_ALL compute transaction-state flags using MAX(TRXNMID) and DECODE.

Key Columns

Common Use Cases and Queries

Note that the view does not expose a literal column named settled_flag; settlement state is derived from the DECODE against IBY_TRXN_SUMMARIES_ALL for REQTYPE = 'ORAPMTCAPTURE'. Because the derived columns are unnamed, they must be referenced positionally or wrapped in an inline view with aliases.

  • Locating transactions whose capture/settlement request is still open for credit card or bank account instruments.
  • Reporting instrument-level detail for reconciliation, joining to IBY_TRXN_SUMMARIES_ALL by transaction identifier.
  • Extracting masked card and bank data for support and audit purposes.

Representative query aliasing the derived settlement flag:

SELECT t.TRXN_EXTENSION_ID, t.PAYMENT_CHANNEL_CODE, t.INSTRUMENT_TYPE, t.MASKED_CC_NUMBER, t.settled_flag FROM (SELECT v.*, DECODE((SELECT MAX(TRXNMID) FROM IBY_TRXN_SUMMARIES_ALL s WHERE s.TRANSACTIONID = v.TRXN_EXTENSION_ID AND s.REQTYPE = 'ORAPMTCAPTURE' AND s.STATUS IN (0,100)), NULL, 'N', 'Y') AS settled_flag FROM APPS.IBY_TRXN_EXTENSIONS_V v) t WHERE t.settled_flag = 'Y';