Search Results iby_fndcpt_payer_assgn_instr_v




Overview
Explore in AI Chat

Overview

IBY_FNDCPT_PAYER_ASSGN_INSTR_V is an APPS-owned database view in the Oracle E-Business Suite Payments (IBY) module. It presents a consolidated, denormalized picture of payer-level payment instrument assignments, joining external payer records, instrument usage preferences, credit card details, and external bank account details into a single queryable structure. The view is designed primarily for reporting, integration, and inquiry purposes, allowing developers and functional consultants to retrieve payment instrument assignment information without manually reconciling the underlying transactional tables.

The view is central to how Oracle Payments resolves which instruments (credit cards, debit cards, or bank accounts) are assigned to a given external payer for a particular payment function. It exposes both payer context (party, customer account, account site) and instrument context (card number, masked card number, bank account, currency), making it particularly useful for payment troubleshooting, instrument audit, and downstream data extraction.

Underlying Base Objects

The view is defined over several base tables, synonyms, and views. The documented referenced objects include IBY_PMT_INSTR_USES_ALL, IBY_EXTERNAL_PAYERS_ALL, IBY_CREDITCARD, IBY_CREDITCARD_ISSUERS_VL, IBY_EXT_BANK_ACCOUNTS_V, and HZ_PARTIES, along with supporting lookups (FND_LOOKUPS, FND_LOOKUP_VALUES_VL) and the FND_GLOBAL package.

The core of the join is IBY_PMT_INSTR_USES_ALL (aliased U), which records each instrument assignment and its order of preference. This is joined to IBY_EXTERNAL_PAYERS_ALL (P) on EXT_PMT_PARTY_ID = EXT_PAYER_ID. Instrument details are then conditionally resolved via DECODE: credit and debit card assignments link to IBY_CREDITCARD (C), while bank account assignments link to IBY_EXT_BANK_ACCOUNTS_V (B). Card issuer information is enriched from IBY_CREDITCARD_ISSUERS_VL (I), and card holder names are resolved through HZ_PARTIES (HZCC).

Key Columns

Common Use Cases and Queries

Typical usage includes identifying all instruments assigned to a payer, determining the default instrument by preference, and extracting masked card or bank account data for reporting. A basic query might be:

SELECT EXT_PAYER_ID, INSTRUMENT_TYPE, ORDER_OF_PREFERENCE, CURRENCY_CODE
FROM APPS.IBY_FNDCPT_PAYER_ASSGN_INSTR_V
WHERE EXT_PAYER_ID = :p_payer_id
ORDER BY ORDER_OF_PREFERENCE;

Another common pattern filters by instrument type to isolate card versus bank account assignments, or joins to IBY_EXTERNAL_PAYERS_ALL to obtain payer display names. Because the view exposes masked card numbers rather than full PANs in typical reporting contexts, it is well-suited for audits and reconciliation extracts. Query performance should be considered when filtering on large payer populations, as the view performs multiple outer joins across card, bank, and party tables.