Results for “payment_flow”

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

Overview

The IBY.IBY_PMT_MTHD_ATTRIB_APPL table is a Payments (IBY) module configuration table that defines the applicability of payment method attributes to specific payment flows. In Oracle E-Business Suite Release 12.1.1 and 12.2.2, payment methods such as check, wire, ACH, or electronic funds transfer are not universally applicable to every stage of the payment lifecycle. Each payment method exposes a set of configurable attributes, and this table determines whether a given attribute applies for a particular payment flow — for example, funds capture versus funds disbursement, or a specific operational context. The result is a fine-grained control matrix that drives which attributes the Payments engine evaluates, prompts for, or validates at runtime. The table resides in the IBY schema and is classified as a valid, standalone configuration object with no outbound foreign keys.

Under a heuristic Data Vault classification mined from its foreign key structure, the table is treated as standalone, meaning it is not modeled as a dependent satellite of a referenced parent. A Data Vault modeling suggestion would be to treat IBY_PMT_MTHD_ATTRIB_APPL as a standalone reference or configuration hub keyed by the natural combination of payment flow, payment method code, and attribute code, with descriptive applicability and audit attributes carried alongside. This classification reflects the absence of enforced referential dependencies to other IBY entities at the database level, even though the values of the business keys logically correspond to payment method and attribute definitions maintained elsewhere.

Key Information Stored

The table contains eleven documented columns. The most significant are the business-key columns and the controlling applicability flag:

• PAYMENT_FLOW — Identifies the payment lifecycle context (for example, funds capture or funds disbursement) to which the applicability rule applies. Part of the primary key.
• PAYMENT_METHOD_CODE — The payment method identifier, such as check, wire, or ACH. Part of the primary key.
• ATTRIBUTE_CODE — Identifies the payment method attribute whose applicability is being defined. Part of the primary key.
• ATTRIBUTE_APPLICABILITY — The core descriptive value: whether the attribute is applicable, optional, required, or otherwise governed for the given payment flow and method. This is the effective business outcome of the configuration.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified the row and when.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications Framework and concurrent programs to detect concurrent updates.
• ZD_EDITION_NAME — Editioning support column associated with EBS 12.2 online patching, included in the unique index to maintain edition-aware key integrity.

The surrogate primary key is IBY_PMT_MTHD_ATTRIB_APPL_PK, composed of PAYMENT_FLOW, PAYMENT_METHOD_CODE, and ATTRIBUTE_CODE. A unique index, IBY_PMT_MTHD_ATTRIB_APPL_U1, extends that same column set with ZD_EDITION_NAME, confirming the three business columns as the natural business key. No foreign key constraints are documented, so parent-child enforcement is performed in application logic.

Common Use Cases and Queries

Typical uses include validating which attributes a payment method supports for a given flow before processing a payment, diagnosing missing attribute prompts or validation errors, and auditing configuration drift between environments. A representative query retrieves the applicability of attributes for a specific method and flow:

• SELECT attribute_code, attribute_applicability FROM iby_pmt_mthd_attrib_appl WHERE payment_method_code = :method AND payment_flow = :flow;
• Reporting configuration completeness by counting attributes per method and flow: SELECT payment_method_code, payment_flow, COUNT(*) FROM iby_pmt_mthd_attrib_appl GROUP BY payment_method_code, payment_flow;
• Auditing recent changes using LAST_UPDATED_BY and LAST_UPDATE_DATE to track who altered applicability rules.
• Extracting the business key and applicability flag to seed test or reference environments.

Related Objects

Because foreign keys are not documented for this standalone table, relationships are logical rather than enforced. The most significant related objects are payment method definitions such as IBY_PAYMENT_METHODS_B and IBY_PAYMENT_METHODS_TL, matched on PAYMENT_METHOD_CODE; payment method attribute definitions such as IBY_PMT_MTHD_ATTRIBUTES, matched on ATTRIBUTE_CODE; and payment flow reference data held in IBY lookup or flow definition tables, matched on PAYMENT_FLOW. Application-tier logic in the Payments setup pages and the payment processing APIs consume these rows when building the attribute matrix for a payment transaction. Reporting views in the IBY schema may join this table to those parents to present a complete, human-readable configuration picture.