Search Results authorization_code

Overview

The IBY_TRXN_EXT_AUTHS_V view is a dictionary-defined object owned by the APPS schema in Oracle E-Business Suite (12.1.1 and 12.2.2). It is delivered as part of the IBY — Payments product and presents consolidated authorization information for payment transactions processed through Oracle Payments. The view joins payment instrument extension records to their corresponding transaction operations, transaction summaries, core transaction data, credit card issuer information, and EFT processing profiles, producing a single denormalized result set suitable for reporting and integration consumption.

The view is marked VALID in ETRM and is typically consumed by external systems, reconciliation processes, and reporting layers that need to inspect the outcome of a payment authorization — including the settlement result, the authorization code, and the effective authorized amount — without navigating the underlying normalized Payments schema directly.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the following objects (aliased in the view text):

• IBY_FNDCPT_PMT_CHNNLS_VL (P) — payment channel definition, supplying channel code and name.
• IBY_FNDCPT_TX_EXTENSIONS (X) — transaction extension records keyed by TRXN_EXTENSION_ID.
• IBY_FNDCPT_TX_OPERATIONS (O) — transaction operations linking the extension to a TRANSACTIONID.
• IBY_TRXN_SUMMARIES_ALL (A) — the transaction summary holding status, amount, update date, request type, and process profile code.
• IBY_TRXN_CORE (C) — core transaction detail including authorization, AVS, and CVV2 result codes.
• IBY_CREDITCARD_ISSUERS_B (I) — credit card issuer metadata, including AUTHORIZATION_VALIDITY_PERIOD.
• IBY_FNDCPT_SYS_EFT_PF_B (SEFT) and IBY_FNDCPT_USER_EFT_PF_B (UEFT) — system and user EFT processing profiles.
• IBY_BEPINFO — referenced synonym for BEP-related information.

The joins are largely inner joins across the extension, operation, summary, and core tables, with outer joins (+) on the credit card issuer, user EFT profile, and system EFT profile. The view filters on A.REQTYPE = 'ORAPMTREQ' and restricts transaction types to 2, 3, 20.

Key Columns

• TRXN_EXTENSION_ID / INSTR_ASSIGNMENT_ID — identifiers linking the record to the instrument assignment.
• PAYMENT_CHANNEL_CODE / PAYMENT_CHANNEL_NAME — the payment channel through which the transaction was routed.
• AUTHORIZATION_ID / AUTHORIZATION_STATUS / AUTHORIZATION_DATE / AUTHORIZATION_AMOUNT — authorization outcome, timestamp, and amount.
• AUTHORIZATION_RESULT_CODE — derived via DECODE from A.STATUS, mapping codes to values such as SETTLEMENT_SUCCESS, COMMUNICATION_ERROR, DUPLICATE_SETTLEMENT, PAYMENT_SYS_REJECT, SETTLEMENT_PENDING, and GENERAL_SYS_ERROR.
• EFFECTIVE_AUTH_AMOUNT — computed using SIGN and NVL against AUTHORIZATION_VALIDITY_PERIOD to yield the amount only while the authorization is still valid.
• PROCESS_PROFILE_CODE — the process profile assigned to the transaction, relevant to the user's search term.
• INSTRUMENT_TYPE — instrument classification (e.g., BANKACCOUNT) driving profile resolution.
• PAYEE_ID — the payee associated with the authorization.

Common Use Cases and Queries

Typical scenarios include payment reconciliation, authorization status audits, and feeding downstream settlement systems by process profile.

SELECT authorization_id,
       authorization_status,
       authorization_result_code,
       effective_auth_amount,
       process_profile_code
  FROM apps.iby_trxn_ext_auths_v
 WHERE process_profile_code = :p_profile
   AND authorization_status = 'SETTLEMENT_PENDING';

To audit effective versus nominal authorization amounts by channel:

SELECT payment_channel_code, process_profile_code,
       SUM(authorization_amount)      authorized,
       SUM(effective_auth_amount)     effective
  FROM apps.iby_trxn_ext_auths_v
 GROUP BY payment_channel_code, process_profile_code;

The view should be treated as read-only; all corrective actions belong in the underlying IBY transaction tables.