Search Results dont_pay_description




Overview
Explore in AI Chat

Overview

IBY.IBY_HOOK_PAYMENTS_T is a global temporary table in the Oracle Payments (IBY) schema of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. It functions as a transient staging structure used by the payment hook framework — the extension mechanism through which external applications and custom PL/SQL hooks interrogate or modify payment instructions before funds disbursement. The suffix _T and the documented Temporary Table Details confirm that data is session-scoped, defined with a data duration of SYS$SESSION. A session can see only the rows it inserted, and those rows are purged at session end, making the table unsuitable for persistent storage or audit reporting.

From a Data Vault modeling perspective, the heuristic classification of this object is standalone. It references IBY_PAY_SERVICE_REQUESTS via PAYMENT_SERVICE_REQUEST_ID and IBY_EXTERNAL_PAYEES_ALL via EXT_PAYEE_ID, but no dependent child tables are documented. A modeler would therefore treat it as a link-oriented, transaction-scoped staging table rather than a durable hub or satellite; it captures a point-in-time payment decision set rather than a master entity.

Key Information Stored

The table exposes 26 documented columns. The most operationally significant include:

No unique index is documented on this table; there is consequently no formal business-key candidate defined in the metadata beyond the composite of payment context columns.

Common Use Cases and Queries

The table is primarily consumed by payment hook PL/SQL and by custom extensions that validate whether a payment should proceed. Typical patterns include:

  • Inspecting suppression decisions for a payment: SELECT PAYMENT_ID, DONT_PAY_FLAG, DONT_PAY_REASON_CODE, DONT_PAY_DESCRIPTION FROM IBY.IBY_HOOK_PAYMENTS_T WHERE PAYMENT_ID = :p_payment_id;
  • Joining to IBY_PAY_SERVICE_REQUESTS to reconcile a staged hook row with its originating service request.
  • Joining to IBY_EXTERNAL_PAYEES_ALL on EXT_PAYEE_ID to enrich payee details.
  • Diagnostic querying during a session executing the payment hook, since rows are visible only within that same session.

Because of the session-scoped lifetime, no long-running reporting or reconciliation query should depend on this table; it is intended for in-flight inspection only.

Related Objects

The most significant related objects, drawn from the documented FK relationships, are:

  • IBY.IBY_PAY_SERVICE_REQUESTS — parent of PAYMENT_SERVICE_REQUEST_ID; the primary business linkage.
  • IBY.IBY_EXTERNAL_PAYEES_ALL — referenced by EXT_PAYEE_ID, supplying payee master data.
  • IBY.IBY_PAYMENTS_ALL and its children — logically related through PAYMENT_ID, though not enforced by a documented FK.
  • IBY.IBY_PAY_INSTRUCTIONS_ALL and IBY.IBY_PAYMENT_TRANSACTIONS — downstream payment processing tables commonly cross-referenced when validating suppression outcomes.
  • Payment hook PL/SQL APIs (for example, proprietary extensions in the IBY_ package family) that insert and read from this staging table.

These objects collectively form the payment decision context surrounding IBY_HOOK_PAYMENTS_T.