Search Results settle_req_auth_flag

Overview

APPS.IBY_TRXN_EXT_AUTHS_V is an Oracle E-Business Suite internal view in the Payments (IBY) module that exposes payment transaction extension records together with their associated authorization details. It is classified as an Internal view type, and the FND Design Data identifier is IBY.IBY_TRXN_EXT_AUTHS_V. The object is owned by APPS, holds VALID status, and is documented for EBS 12.1.1 and 12.2.2.

The view serves as the reporting and integration surface for card, EFT, and other external payment authorizations processed through Oracle Payments. It joins transaction extension rows to their governing authorization records so that a single row conveys the payment channel, the instrument assignment, the authorization outcome, monetary amounts, and any processor-level error or verification codes returned by the payment system. Because it consolidates authorization outcome data — most notably AUTHORIZATION_RESULT_CODE — it is frequently consulted when diagnosing declined or partially approved external authorizations, or when extracting settlement-relevant authorization data into downstream systems.

Oracle expressly marks this object as Internal Use Only: it is not supported for direct customer access except through standard Oracle Applications programs. Any use should therefore be treated as read-only and subject to change between releases.

Underlying Base Objects

The view is defined over a set of IBY foundation and transaction tables. Documented dependencies include IBY_FNDCPT_TX_EXTENSIONS, which supplies the transaction extension identifier and extension-level attributes; IBY_FNDCPT_TX_OPERATIONS, which links extension rows to the payment operations performed against them; and the core transaction tables IBY_TRXN, IBY_TRXN_CORE, and IBY_TRXN_SUMMARIES_ALL.

Channel and profile context is resolved through IBY_FNDCPT_PMT_CHNNLS_VL (the payment channel value list for channel code and name) and through the payment profile base tables IBY_FNDCPT_SYS_EFT_PF_B and IBY_FNDCPT_USER_EFT_PF_B, which provide the system-level and user-level EFT processing profiles. IBY_CREDITCARD_ISSUERS_B supplies credit card issuer reference data, and IBY_BEPINFO contributes payment system / backend processor information. In the documented 12.2.2 metadata, several of these appear as synonyms, reflecting the layered IBY data model in which extension, operation, core transaction, and profile entities are related by identifier.

Key Columns

• TRXN_EXTENSION_ID — Primary identifier of the transaction extension row; the anchor for the view.
• AUTHORIZATION_ID — Identifier of the authorization record associated with the extension.
• AUTHORIZATION_RESULT_CODE (VARCHAR2(21)) — Processor-returned result code describing the authorization outcome; the column users most commonly search for when troubleshooting approvals and declines.
• AUTHORIZATION_STATUS (NUMBER) — Internal status indicator for the authorization.
• AUTHORIZATION_DATE, AUTHORIZATION_AMOUNT, EFFECTIVE_AUTH_AMOUNT — When the authorization was obtained, the amount requested, and the effective amount actually authorized.
• AUTHORIZATION_CODE — Approval or reference code returned by the payment system.
• PAYMENT_CHANNEL_CODE / PAYMENT_CHANNEL_NAME — The channel (for example, credit card or EFT) through which the authorization was processed.
• INSTR_ASSIGNMENT_ID, INSTRUMENT_TYPE, PAYEE_ID — Instrument assignment, instrument type, and payee context.
• PROCESS_PROFILE_CODE — The payment process profile governing the transaction.
• PMT_SYS_ERR_CODE / PMT_SYS_ERR_MSG — Error code and message returned by the payment system when an authorization fails.
• AVS_CODE, INSTR_SEC_CODE_CHECK — Address verification and instrument security code check results.
• SETTLE_REQ_AUTH_FLAG — Indicates whether settlement requires a prior authorization.
• PAYMENT_SYSTEM_ORDER_NUMBER — Order number assigned by the payment system.
• INITIATOR_EXTENSION_ID, ORIGIN_APPLICATION_ID — Originating extension and source application identifiers.

Common Use Cases and Queries

Typical scenarios include reconciling authorizations to transactions, investigating declines or partial authorizations, and auditing AVS/security-code outcomes. The following query filters on the authorization result code and surfaces the associated error detail:

SELECT authorization_id, authorization_result_code, authorization_status,
       authorization_date, authorization_amount, effective_auth_amount,
       pmt_sys_err_code, pmt_sys_err_msg
 FROM apps.iby_trxn_ext_auths_v
 WHERE authorization_result_code IS NOT NULL
       AND payment_channel_code = :channel_code;

A second pattern correlates authorizations back to their transaction extension and processing profile to analyze channel-level approval rates:

SELECT payment_channel_code, process_profile_code,
       authorization_result_code, COUNT(*)
 FROM apps.iby_trxn_ext_auths_v
 GROUP BY payment_channel_code, process_profile_code, authorization_result_code;

Because the view is documented as internal and unsupported for direct access, these statements are best used for diagnostic reporting rather than as a dependency in custom production interfaces.