Search Results iby_pay_instructions_all

Overview

The IBY_PAY_INSTRUCTIONS_ALL table is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It serves as the master repository for payment instruction records, which are fundamental entities created during the payment process. A payment instruction is a logical grouping of one or more payment requests (e.g., invoices) that are processed together as a single batch for a specific payment method, currency, payment date, and internal bank account. This table is central to orchestrating the end-to-end payment flow, from instruction creation and formatting to transmission and reconciliation.

Key Information Stored

The table's primary key is PAYMENT_INSTRUCTION_ID, which uniquely identifies each instruction. As indicated by the foreign key relationships in the metadata, critical columns link the instruction to other essential entities in the payment ecosystem. These include PAYMENT_SERVICE_REQUEST_ID, which ties the instruction to its originating payment batch request; INTERNAL_BANK_ACCOUNT_ID, identifying the company bank account used for funding; PAYMENT_PROFILE_ID, referencing the setup governing payment processing rules; and PAYMENT_REASON_CODE, which categorizes the purpose of the payment. Other significant columns typically found in this table (implied by its function) store the instruction's status (e.g., CREATED, FORMATTED, CONFIRMED), payment method (e.g., CHECK, ELECTRONIC), total amount, payment currency, and processing dates.

Common Use Cases and Queries

This table is pivotal for payment process monitoring, troubleshooting, and reporting. Common queries involve tracking the status and details of payment instructions. For instance, to find all electronic payment instructions created for a specific bank account on a given date, a query would join IBY_PAY_INSTRUCTIONS_ALL with CE_BANK_ACCOUNTS on INTERNAL_BANK_ACCOUNT_ID and filter by PAYMENT_METHOD_CODE and CREATION_DATE. Another critical use case is investigating payment failures by joining with IBY_PAYMENTS_ALL (via PAYMENT_INSTRUCTION_ID) to analyze individual payment failures within a problematic instruction. Technical consultants also query this table to gather audit trail information, such as the sequence and timing of status changes for a payment instruction throughout its lifecycle.

Related Objects

The provided metadata clearly outlines this table's central position in the payment schema through its foreign key relationships. It is a parent table to several key transactional tables, including AP_CHECKS_ALL, FV_SUMMARY_CONSOLIDATE_ALL, FV_TP_TS_AMT_DATA, and JL_AR_AP_AWT_CERTIF_ALL, which store payment execution details. Conversely, it is a child table referencing master data and control tables: IBY_PAY_SERVICE_REQUESTS (the payment batch), CE_BANK_ACCOUNTS (bank account master), IBY_ACCT_PMT_PROFILES_B (payment processing profile), and IBY_PAYMENT_REASONS_B. Key related views include IBY_PAY_INSTRUCTIONS_V and IBY_PAY_INSTRUCTIONS_ALL_V, which provide application-level access to this data. The primary API for interacting with payment instructions is IBY_DISBURSE_UI_API_PUB_PKG.