Results for “iby_applicable_pmt_mthds”

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

Overview

IBY_APPLICABLE_PMT_MTHDS is a Payments (IBY) module table in Oracle E-Business Suite that stores payment method applicability information for company policy-based factors. It defines which payment methods are valid or excluded for a given combination of business attributes. The documented factors include First Party Legal Entity, First Party Organization, Payment Processing Transaction Type, and whether a transaction is foreign. In practice, this table drives the Payment Method defaulting and validation logic used by Oracle Payments (IBY) when a payment instruction is created or processed, ensuring that only permitted methods are offered or accepted for a given payment context.

The ETRM metadata classifies this object heuristically as a link table within a Data Vault modeling view. This reflects its role as an associative structure connecting a payment method (via IBY_PAYMENT_METHODS_B) to an application and a set of applicability attributes, rather than acting as a pure reference hub or a descriptive satellite. The model is registered under the IBY schema with a status of VALID in both 12.1.1 and 12.2.2.

Key Information Stored

The table contains 16 documented columns. The most significant are summarized below.

• APPLICABLE_PMT_MTHD_ID — Surrogate primary key defined by the unique index IBY_APPLICABLE_PMT_MTHDS_PK. It uniquely identifies each applicability rule row.
• PAYMENT_METHOD_CODE — Foreign key to IBY_PAYMENT_METHODS_B. Identifies the payment method whose applicability is being defined or restricted.
• APPLICATION_ID — Foreign key to FND_APPLICATION. Ties the rule to the owning application context.
• PAYMENT_FLOW — Indicates the direction or stage of the payment flow (for example, disbursement versus funds capture) to which the rule applies.
• APPLICABLE_TYPE_CODE — Classifies the applicability factor being evaluated, such as legal entity, organization, or transaction type.
• APPLICABLE_VALUE_FROM and APPLICABLE_VALUE_TO — Define the lower and upper bounds of the applicability range for the given factor, enabling value-range or single-value matching.
• EXCLUDE_FROM_APPLIC_FLAG — Indicates whether the rule excludes rather than includes the payment method for the defined criteria.
• INACTIVE_DATE — Marks the date on which the applicability rule ceases to be effective.
• OBJECT_VERSION_NUMBER — Supports optimistic concurrency control during DML operations.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit columns tracked throughout Oracle EBS.
• ZD_EDITION_NAME — Part of the unique index IBY_APPLICABLE_PMT_MTHDS_U1 along with APPLICABLE_PMT_MTHD_ID; it supports the editioning or logical copy mechanism used in later EBS releases.

The business-key candidate documented is IBY_APPLICABLE_PMT_MTHDS_U1 (APPLICABLE_PMT_MTHD_ID, ZD_EDITION_NAME), which combines the surrogate key with the edition column to enforce uniqueness across editioned data.

Common Use Cases and Queries

Typical usage centers on validating and troubleshooting payment method eligibility. A reporting query might retrieve all active applicability rules for a given payment method:

• Join IBY_APPLICABLE_PMT_MTHDS to IBY_PAYMENT_METHODS_B on PAYMENT_METHOD_CODE to list method names alongside their applicability constraints.
• Filter on INACTIVE_DATE IS NULL to return only currently effective rules.
• Filter on PAYMENT_FLOW and APPLICABLE_TYPE_CODE to isolate the rules relevant to a specific processing scenario, such as disbursement against a particular legal entity.
• Use EXCLUDE_FROM_APPLIC_FLAG to distinguish inclusion rules from exclusion rules when diagnosing why a method is unavailable in the Payments UI.

These queries support configuration verification, migration validation between 12.1.1 and 12.2.2, and audit reporting of payment method policy changes.

Related Objects

The following objects are most significant in relation to IBY_APPLICABLE_PMT_MTHDS, based on the documented foreign key and primary key relationships.

• IBY_PAYMENT_METHODS_B — Referenced via PAYMENT_METHOD_CODE. The master definition of payment methods; this table restricts or permits their use.
• FND_APPLICATION — Referenced via APPLICATION_ID. Provides the application context for each applicability rule.
• IBY_APPLICABLE_PMT_MTHDS_PK — The primary key unique index enforcing row uniqueness on APPLICABLE_PMT_MTHD_ID.
• IBY_APPLICABLE_PMT_MTHDS_U1 — The unique business-key index on APPLICABLE_PMT_MTHD_ID and ZD_EDITION_NAME.

Downstream, the applicability rules stored here are consumed by Oracle Payments configuration and payment instruction processing logic, which read this data to determine which payment methods may be selected or are excluded for a given first party and transaction context.