Results for “iby_docs_payable_all”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
IBY.IBY_DOCS_PAYABLE_ALL is the central transactional table in the Oracle Payments (IBY) module for Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the payable documents that a calling application — typically Payables, Receivables, Payroll, or another payment-requesting module — submits to the Payments engine for processing, formatting, and disbursement. Each row represents a single payable instruction tied to a document payable identifier, capturing the full lifecycle attributes required to build a payment: payee, payee site, bank accounts, payment method, payment format, delivery channel, currency, amount, and status.
Under a heuristic Data Vault classification, this table is satellite-leaning. The DOCUMENT_PAYABLE_ID surrogate primary key acts as the entity key, while the large body of descriptive payment attributes (120 documented columns) behaves like satellite context. The presence of OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE reinforces the satellite interpretation, since this is an auditable transactional record updated through the payment lifecycle rather than a static reference or pure hub.
Key Information Stored
The table is anchored by the surrogate primary key DOCUMENT_PAYABLE_ID, declared on the IBY_DOCS_PAYABLE_ALL_PK constraint. A second unique index, IBY_DOCS_PAYABLE_ALL_U1, also exists on DOCUMENT_PAYABLE_ID. The most operationally significant columns include:
PAYMENT_ID— links the payable document to its generated payment.PAYMENT_METHOD_CODE— method used (check, EFT, wire), FK toIBY_PAYMENT_METHODS_B.PAYMENT_FORMAT_CODEandDELIVERY_CHANNEL_CODE— control formatting and delivery; the latter FKs toIBY_DELIVERY_CHANNELS_B.INTERNAL_BANK_ACCOUNT_IDandEXTERNAL_BANK_ACCOUNT_ID— disbursement bank accounts, both FKs toCE_BANK_ACCOUNTS.EXT_PAYEE_ID,PAYEE_PARTY_ID,PARTY_SITE_ID,SUPPLIER_SITE_ID— payee identity and site.LEGAL_ENTITY_ID— FK toFV_LEGAL_ENTITIES.DOCUMENT_AMOUNT,DOCUMENT_CURRENCY_CODE,PAYMENT_AMOUNT,PAYMENT_CURRENCY_CODE— monetary values.DOCUMENT_STATUS,DOCUMENT_TYPE,PAYMENT_FUNCTION,PAYMENT_DATE— lifecycle and classification.CALLING_APP_IDandCALLING_APP_DOC_UNIQUE_REF1..5— source application identity and external document references.
Common Use Cases and Queries
Typical reporting and troubleshooting scenarios include identifying unprocessed payable documents, reconciling Payments to Payables invoices, and auditing formatted versus unformatted payments. Common query patterns:
- Listing documents awaiting payment by status:
SELECT document_payable_id, document_amount, document_status FROM iby_docs_payable_all WHERE document_status = 'UNPAID'; - Joining to the payment for a payable document:
SELECT p.document_payable_id, p.payment_id, pm.payment_number FROM iby_docs_payable_all p, iby_payments_all pm WHERE p.payment_id = pm.payment_id; - Resolving bank account details: join
INTERNAL_BANK_ACCOUNT_IDorEXTERNAL_BANK_ACCOUNT_IDtoCE_BANK_ACCOUNTS. - Reporting by calling application: filter on
CALLING_APP_IDand referenceCALLING_APP_DOC_REF_NUMBERto trace the originating invoice or document.
Because the table is _ALL, queries in multi-org environments should generally observe the operating unit context via ORG_ID where relevant to the reporting requirement.
Related Objects
The table participates in a rich relational cluster:
IBY_DOCUMENT_LINES— child lines linked byDOCUMENT_PAYABLE_ID; the historical version isIBY_DOCUMENT_LINES_H.IBY_DOCUMENTS_PAYABLE_H— Oracle history table for the parent, referenced byDOCUMENT_PAYABLE_ID.IBY_DOCS_PAYABLE_GT— global temporary staging table referencing this entity.IBY_HOOK_DOCS_IN_PMT_T— payment hook table referencing documents in payment.IBY_PAYMENT_METHODS_BandIBY_DELIVERY_CHANNELS_B— reference tables for method and channel codes.CE_BANK_ACCOUNTSandFV_LEGAL_ENTITIES— bank account and legal entity lookups.
Together these relationships make IBY_DOCS_PAYABLE_ALL the authoritative join point between a calling application's payable documents and the Payments execution, formatting, and disbursement chain.
-
"This table contains records of the documents payable which are updated by system while processing 'Build payments' program. IBY_DOCS_PAYABLE_ALL stores Oracle Payments' representation of source products' documents payable. A document pay