Results for “iby_payment_methods”

11 results




Overview
Explore in AI Chat

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

Overview

IBY.IBY_PMT_MTHD_ATTRIB_APPL is an Oracle E-Business Suite payment configuration table within the Payments (IBY) schema. It stores the applicability settings that govern which attributes are available or applicable for a given payment method or payment channel. In practical terms, the table defines the relationship between a payment method, the payment flow in which that method operates, and the specific attribute codes that apply to it, along with an applicability classification drawn from the IBY_PMT_ATTRIB_APL_TYPES lookup.

The object resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and its indexes are stored in APPS_TS_TX_IDX. It is classified as VALID and is registered in FND Design Data under the same name. From a heuristic Data Vault modeling perspective, this object is best treated as a standalone construct; it holds no foreign key references to other database objects, though it is referenced by the APPS synonym IBY_PMT_MTHD_ATTRIB_APPL.

Key Information Stored

The table contains eleven documented columns. The most significant are the three business-key columns that form the natural identity of each row and the unique index IBY_PMT_MTHD_ATTRIB_APPL_U1:

  • PAYMENT_FLOW (VARCHAR2, 30) — Determines the source table for the payment method foreign key. Values are derived from the IBY_PAYMENT_FLOW lookup type and include DISBURSEMENTS and FUNDS_CAPTURE. When the value is DISBURSEMENTS, PAYMENT_METHOD_CODE originates from IBY_PAYMENT_METHODS; otherwise it originates from IBY_FNDCPT_PMT_CHNNLS.
  • PAYMENT_METHOD_CODE (VARCHAR2, 240) — The payment method identifier, whose parent table is conditional on PAYMENT_FLOW as described above.
  • ATTRIBUTE_CODE (VARCHAR2, 30) — The code identifying the attribute being configured.
  • ATTRIBUTE_APPLICABILITY (VARCHAR2, 30) — The applicability classification for the attribute; values are taken from IBY_PMT_ATTRIB_APL_TYPES.

The primary key is IBY_PMT_MTHD_ATTRIB_APPL_PK on (PAYMENT_FLOW, PAYMENT_METHOD_CODE, ATTRIBUTE_CODE). The unique business-key index IBY_PMT_MTHD_ATTRIB_APPL_U1 covers (PAYMENT_FLOW, PAYMENT_METHOD_CODE, ATTRIBUTE_CODE, ZD_EDITION_NAME), reflecting the editioning column present in 12.2.2. Standard Who columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and OBJECT_VERSION_NUMBER support auditing and optimistic locking.

Common Use Cases and Queries

This table is typically queried when diagnosing why a particular attribute does or does not appear for a payment method during disbursement or funds capture processing. A common pattern joins the applicability rows to the payment method definition:

  • Reporting which attributes are enabled for a payment method: SELECT payment_flow, payment_method_code, attribute_code, attribute_applicability FROM iby.iby_pmt_mthd_attrib_appl WHERE payment_method_code = :code;
  • Filtering by flow to separate disbursement versus funds capture configuration: WHERE payment_flow = 'DISBURSEMENTS' or WHERE payment_flow = 'FUNDS_CAPTURE'.
  • Auditing recent configuration changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.
  • Validating attribute applicability against the IBY_PMT_ATTRIB_APL_TYPES lookup to confirm the value is legitimate.

Because PAYMENT_METHOD_CODE resolves to different parent tables depending on PAYMENT_FLOW, queries that resolve the method description must branch between IBY_PAYMENT_METHODS and IBY_FNDCPT_PMT_CHNNLS.

Related Objects

The dependency metadata indicates this table does not reference other database objects via enforced foreign keys, but the following objects are significant in its functional context:

  • IBY_PMT_MTHD_ATTRIB_APPL_U1 — the unique index enforcing business-key uniqueness (PAYMENT_FLOW, PAYMENT_METHOD_CODE, ATTRIBUTE_CODE, ZD_EDITION_NAME).
  • IBY_PMT_MTHD_ATTRIB_APPL_PK — the primary key constraint on (PAYMENT_FLOW, PAYMENT_METHOD_CODE, ATTRIBUTE_CODE).
  • IBY_PAYMENT_METHODS — source of PAYMENT_METHOD_CODE when PAYMENT_FLOW is DISBURSEMENTS.
  • IBY_FNDCPT_PMT_CHNNLS — source of PAYMENT_METHOD_CODE for non-disbursement flows.
  • IBY_PMT_ATTRIB_APL_TYPES — lookup defining valid ATTRIBUTE_APPLICABILITY values.
  • IBY_PAYMENT_FLOW — lookup type providing valid PAYMENT_FLOW values.

Collectively, these objects form the configuration layer that controls payment attribute applicability across Oracle Payments.