Search Results iby_pmt_instr_uses_all




Overview
Explore in AI Chat

Overview

The IBY_PMT_INSTR_USES_ALL table is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a central repository for defining and managing the valid usage rules for payment instruments. A payment instrument, such as a bank account or credit card, can be used for different purposes (e.g., paying suppliers, receiving customer payments) and in different transactional contexts (e.g., Payables, Receivables). This table establishes the authorized links between a specific payment instrument, the type of payment flow (like disbursements or receipts), the payment function, and the external payment party involved. This enforcement ensures that payment processing adheres to defined business rules and security controls.

Key Information Stored

The table's structure is designed to uniquely identify a valid instrument usage scenario. Its primary and unique keys highlight the most critical columns. The INSTRUMENT_PAYMENT_USE_ID is the primary surrogate key. The unique key constraint (IBY_PMT_INSTR_USES_ALL_UK) enforces business rule integrity by combining the following columns: PAYMENT_FLOW (e.g., Disbursements, Receipts), PAYMENT_FUNCTION (e.g., Supplier Payment, Customer Refund), INSTRUMENT_TYPE (e.g., Bank Account, Credit Card), INSTRUMENT_ID (the specific identifier of the instrument from tables like IBY_EXT_BANK_ACCOUNTS), and EXT_PMT_PARTY_ID (the identifier for the external party, such as a supplier or customer, from tables like IBY_EXTERNAL_PAYEES_ALL). This combination prevents duplicate usage assignments.

Common Use Cases and Queries

A primary use case is validating whether a selected bank account can be used for a specific payment batch. Administrators also query this table to audit or report on instrument setup. Common SQL patterns include identifying all valid instruments for a supplier payment flow or listing all usage rules for a specific bank account.

  • Find all bank accounts authorized for paying a specific supplier (EXT_PMT_PARTY_ID):
    SELECT * FROM IBY_PMT_INSTR_USES_ALL WHERE PAYMENT_FLOW = 'DISBURSEMENTS' AND PAYMENT_FUNCTION = 'SUPPLIER_PAYMENT' AND EXT_PMT_PARTY_ID = &party_id;
  • Report all usage assignments for an instrument:
    SELECT PAYMENT_FLOW, PAYMENT_FUNCTION, EXT_PMT_PARTY_ID FROM IBY_PMT_INSTR_USES_ALL WHERE INSTRUMENT_ID = &account_id;

Related Objects

The table has defined relationships with other key Payments tables. As per the provided metadata, a foreign key exists from the IBY_FNDCPT_TX_EXTENSIONS table. The column IBY_FNDCPT_TX_EXTENSIONS.INSTR_ASSIGNMENT_ID references the INSTRUMENT_PAYMENT_USE_ID in IBY_PMT_INSTR_USES_ALL, linking a specific payment transaction to the instrument usage rule that authorized it. This table is also fundamentally related to the IBY_EXT_BANK_ACCOUNTS (source of INSTRUMENT_ID) and IBY_EXTERNAL_PAYEES_ALL (source of EXT_PMT_PARTY_ID) tables, which provide the detailed attributes for the instruments and parties referenced within the usage rules.