Search Results debit_network_code

Overview

IBY_TRANS_CORE_V is a read-only consolidated view owned by the APPS schema within the IBY (Payments) product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It presents a denormalized projection of payment transaction data, joining core transaction records with tangible instrument details, credit card instrument attributes, billing address information, and account type lookups. The view is defined over the base objects IBY_TRXN_SUMMARIES_ALL, IBY_TRXN_CORE, IBY_TANGIBLE, IBY_CREDITCARD, IBY_ACCTTYPE, and HZ_LOCATIONS, together with a restricted subquery on IBY_PMTSCHEMES.

Its principal characteristic is the filter B.BEPID IN (SELECT DISTINCT BEPID FROM IBY_PMTSCHEMES WHERE PMTSCHEMENAME = 'SSL'). This constrains the result set to transactions processed through the SSL payment scheme, meaning the view exposes externally facing, secure-socket payment records rather than the full population of payment transactions. As such it is not a general-purpose transaction view, but a purpose-built reporting and integration surface for SSL-processed payments.

Underlying Base Objects

The join topology documented in the view text is as follows:

• IBY_TRXN_SUMMARIES_ALL (alias B) — the driving table, providing TRANSACTIONID, BEPKEY, PAYEEID, BEPID, ECAPPID, payer and instrument identifiers, request metadata, status, settlement and update dates, error fields, batch identifiers, ORG_ID, and NLSLANG.
• IBY_TRXN_CORE (alias C) — joined on TRXNMID, supplying authorization attributes including AUTHCODE, REFERENCECODE, OPERATIONCODE, INSTRNAME, AUTHTYPE, AVSCODE, ACQUIRER, AUXMSG, VOICEAUTHFLAG, DEBIT_NETWORK_CODE, SURCHARGE_AMOUNT, and PROC_TRACENUMBER.
• IBY_TANGIBLE (alias T) — joined on MTANGIBLEID, providing the monetary amount (rounded to two decimals), currency code, account number, reference information, memo, and the ORDER_MEDIUM and EFT_AUTH_METHOD attributes.
• IBY_CREDITCARD (alias CR) — joined on PAYERINSTRID, contributing CHNAME, CCNUMBER, and EXPIRYDATE. A defining restriction is CR.SUBTYPE IS NULL, which excludes instrument subtypes and narrows the join to the base instrument record.
• IBY_ACCTTYPE (alias Y) — joined on ACCTTYPEID, returning ACCTTYPE.
• HZ_LOCATIONS (alias L) — an outer join on ADDRESSID, returning the billing address components ADDRESS1 through ADDRESS3, CITY, STATE, POSTAL_CODE (aliased ZIP), COUNTY, and COUNTRY. The outer join permits transaction rows to appear even when no address is recorded.
• IBY_PMTSCHEMES — referenced only within the BEPID IN subquery, restricting output to the SSL payment scheme.

Key Columns

• TRANSACTIONID, TRXNMID, BEPKEY — transaction and back-end processing identifiers; TRXNMID is the principal linking key across the base tables.
• PAYERID, PAYEEID, PAYERINSTRID, ECAPPID — party and instrument context for the transaction.
• DEBIT_NETWORK_CODE — the column most directly associated with the user's search. Sourced from IBY_TRXN_CORE, it carries the debit network identifier for card transactions processed across a debit rail, and appears on the view exclusively because of the IBY_TRXN_CORE join.
• SURCHARGE_AMOUNT, PROC_TRACENUMBER, VOICEAUTHFLAG — additional IBY_TRXN_CORE attributes supporting surcharge reporting, processor trace reconciliation, and voice authorization identification.
• AMOUNT, CURRENCYNAMECODE, ACCTNO, REFINFO, MEMO — financial and descriptive content from IBY_TANGIBLE, with AMOUNT rounded via ROUND(T.AMOUNT, 2).
• AUTHCODE, AVSCODE, AUTHTYPE, ACQUIRER — authorization and verification results used in settlement and dispute analysis.
• STATUS, SETTLEDATE, UPDATEDATE, BEPCODE, BEPMESSAGE, ERRORLOCATION — lifecycle and error-tracking fields from the summaries table.
• ORDER_MEDIUM, EFT_AUTH_METHOD — channel and authentication indicators describing how the payment was captured.
• ORG_ID, NLSLANG — multi-org security and localization context.

Common Use Cases and Queries

The view is most commonly used for operational reporting on SSL-processed payments, reconciliation of authorizations against settlements, surcharge and debit-network analysis, and integration extracts feeding downstream payment or financial systems. The following examples reflect the documented column set.

Retrieve debit network transactions for a processing period:

• SELECT transactionid, payeeid, amount, currencynamecode, debit_network_code, authcode, status, settledate FROM iby_trans_core_v WHERE debit_network_code IS NOT NULL AND settledate BETWEEN :p_start AND :p_end ORDER BY settledate;

Summarize surcharges by acquirer for reconciliation:

• SELECT acquirer, currencynamecode, COUNT(*) txn_count, SUM(surcharge_amount) total_surcharge FROM iby_trans_core_v WHERE proc_tracenumber IS NOT NULL GROUP BY acquirer, currencynamecode;

Trace authorization outcomes for a specific payer instrument:

• SELECT transactionid, trxnmid, authcode, avscode, authtype, bepcode, bepmessage FROM iby_trans_core_v WHERE payerinstrid = :p_instr_id AND org_id = :p_org_id;

Because the view is filtered to the SSL payment scheme and to instruments with a null subtype, queries intended to cover all payment channels or all instrument subtypes must be directed at the underlying base tables instead. Access should be granted through the APPS schema, and multi-org queries should always constrain ORG_ID.