Search Results iby_docs_payable_all

Overview

The IBY_DOCS_PAYABLE_ALL table is a core data repository within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It serves as the master transactional table for documents payable, which are the payment requests or payment instructions generated from source transactions across the EBS suite, such as invoices in Payables or expense reports in iExpenses. This table is central to the payment execution workflow, holding the consolidated payment information before it is formatted and transmitted to a bank. Its multi-org structure, indicated by the "_ALL" suffix, allows it to store data for multiple operating units, a critical feature for enterprise deployments.

Key Information Stored

The table's primary key is DOCUMENT_PAYABLE_ID, which uniquely identifies each payable document record. Key columns, as indicated by its foreign key relationships, store critical identifiers that link the payment instruction to its source and define its processing rules. These include the CALLING_APP_ID (identifying the originating application, like AP), PAYMENT_SERVICE_REQUEST_ID (linking to the payment batch), and PAYMENT_ID (linking to the final payment record). It also stores essential payment attributes such as PAYMENT_METHOD_CODE, INTERNAL_BANK_ACCOUNT_ID (the paying account), EXTERNAL_BANK_ACCOUNT_ID (the supplier bank account), PAYMENT_FORMAT_CODE, and DELIVERY_CHANNEL_CODE, which collectively determine how and where the payment will be processed and delivered.

Common Use Cases and Queries

This table is fundamental for payment inquiry, reconciliation, and troubleshooting. Common use cases include tracing the status of a payment instruction from its source invoice, identifying all payments within a specific batch, and diagnosing payment failures by examining the associated payment method and delivery channel. A typical query pattern joins IBY_DOCS_PAYABLE_ALL to source application tables (e.g., AP_INVOICES_ALL) via the CALLING_APP_DOC_UNIQUE_REF columns and to payment execution tables like IBY_PAYMENTS_ALL. For example, to list all payment instructions for a specific payment batch request, one might query: SELECT * FROM iby_docs_payable_all WHERE payment_service_request_id = <REQUEST_ID>;. Reporting on payment methods by operating unit or bank account also heavily relies on this table.

Related Objects

IBY_DOCS_PAYABLE_ALL has extensive relationships with other key Payments and Cash Management tables. It is the parent table for line-level detail in IBY_DOCUMENT_LINES and IBY_DOCUMENT_LINES_H. Its foreign keys establish critical dependencies: it references CE_BANK_ACCOUNTS for both internal and external bank accounts, IBY_PAYMENT_METHODS_B for the payment method, IBY_DELIVERY_CHANNELS_B for the delivery method, and various other IBY lookup tables (e.g., for PAY_PROC_TRXN_TYPE_CODE, PAYMENT_PROFILE_ID, EXT_PAYEE_ID, PAYMENT_REASON_CODE). Crucially, it is referenced by IBY_PAYMENTS_ALL via the PAYMENT_ID column, linking the payable document to its executed payment record.