Results for “iby_documents_payable_h”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The IBY_DOCUMENTS_PAYABLE_H table resides in the IBY schema (Oracle Payments) and stores the historical, point-in-time snapshot of payable documents processed by the Oracle Payments engine in Oracle E-Business Suite 12.1.1 and 12.2.2. While the base transaction detail lives in IBY_DOCS_PAYABLE_ALL, this table captures versioned history rows that record how a payable document looked at each stage of the payment lifecycle — from instruction creation through formatting, remittance, and settlement. It is a critical audit and reconstruction object, enabling Payments to retain an immutable record of amounts, statuses, bank details, and routing information as they existed at the time of each processing event.

Physically, the table is owned by IBY and contains 105 documented columns. Its primary key is IBY_DOCUMENTS_PAYABLE_H_PK, defined on the surrogate column DOCUMENT_PAYABLE_HISTORY_ID. From a Data Vault modeling perspective, the heuristic classification of this object is a link — it resolves relationships between payment instructions, payment profiles, methods, and transactions across a temporal axis, and it participates in link-style associations against multiple hub-like parent tables.

Key Information Stored

The following columns are the most significant for understanding and querying the table:

• DOCUMENT_PAYABLE_HISTORY_ID — Surrogate primary key; unique identifier for each history record.
• DOCUMENT_PAYABLE_HISTORY_DATE — Timestamp of the history snapshot; the temporal anchor for as-of queries.
• DOCUMENT_PAYABLE_ID — Business-key candidate linking back to the base table IBY_DOCS_PAYABLE_ALL.
• PAYMENT_HISTORY_ID — Ties the snapshot to the corresponding row in IBY_PAYMENTS_H.
• PAYMENT_ID — Reference to the active payment in IBY_PAYMENTS_ALL.
• PAYMENT_PROFILE_ID — Foreign key to IBY_ACCT_PMT_PROFILES_B, identifying the payment profile used.
• PAYMENT_METHOD_CODE — References IBY_PAYMENT_METHODS_B.
• DOCUMENT_AMOUNT / DOCUMENT_CURRENCY_CODE — Payable value and its transaction currency.
• PAYMENT_AMOUNT / PAYMENT_CURRENCY_CODE — Disbursed amount and payment currency, useful for reconciliation.
• DOCUMENT_STATUS — Lifecycle state at the snapshot point.
• PAYMENT_DUE_DATE and DISCOUNT_DATE — Scheduling and cash-management fields.
• PAYEE_PARTY_ID / EXT_PAYEE_ID / PARTY_SITE_ID — Payee identification and site.
• LEGAL_ENTITY_ID — References FV_LEGAL_ENTITIES for legal-entity-based reporting.
• ORG_ID — Multi-org operating unit context.

The remaining columns extend into bank account routing (INT/EXT routing, IBAN, SWIFT), remittance messaging, and the standard DFF block (ATTRIBUTE1–15).

Common Use Cases and Queries

Because the table preserves snapshots, it is the preferred source for payment audit trails, dispute investigation, and regulatory reporting where "what did we send?" must be proven.

• Payment status history reporting: Query by DOCUMENT_PAYABLE_ID ordered by DOCUMENT_PAYABLE_HISTORY_DATE to trace lifecycle transitions.
• Reconstructing payment instructions: Join to IBY_PAYMENTS_ALL on PAYMENT_ID to reproduce the exact instruction for a disputed transaction.
• Cash-flow and discount analysis: Aggregate PAYMENT_AMOUNT grouped by DOCUMENT_CURRENCY_CODE and DISCOUNT_DATE.
• Bank-detail audit: Extract EXT_BANK_ACCOUNT_IBAN_NUMBER and EXT_BANK_ACCOUNT_SWIFT_CODE for banks requiring traceability.

Typical pattern:

SELECT h.DOCUMENT_PAYABLE_ID, h.DOCUMENT_STATUS, h.PAYMENT_AMOUNT,
       h.DOCUMENT_PAYABLE_HISTORY_DATE
  FROM IBY_DOCUMENTS_PAYABLE_H h
 WHERE h.DOCUMENT_PAYABLE_ID = :doc_id
 ORDER BY h.DOCUMENT_PAYABLE_HISTORY_DATE DESC;

Related Objects

• IBY_DOCS_PAYABLE_ALL — base payable document (join on DOCUMENT_PAYABLE_ID).
• IBY_PAYMENTS_ALL / IBY_PAYMENTS_H — active and historical payments (PAYMENT_ID, PAYMENT_HISTORY_ID).
• IBY_ACCT_PMT_PROFILES_B — payment profile definition (PAYMENT_PROFILE_ID).
• IBY_PAYMENT_METHODS_B — payment method lookup (PAYMENT_METHOD_CODE).
• IBY_TRXN_TYPES_B — calling application transaction types (CALLING_APP_ID, PAY_PROC_TRXN_TYPE_CODE).
• IBY_PAY_SERVICE_REQUESTS — payment service request lineage (PAYMENT_SERVICE_REQUEST_ID).
• IBY_EXTERNAL_PAYEES_ALL — external payee master (EXT_PAYEE_ID).
• FV_LEGAL_ENTITIES / FND_TERRITORIES — legal entity and country reference (LEGAL_ENTITY_ID, COUNTRY).