Search Results iby_payment_methods_vl

Overview

IBY_PAYMENT_METHODS_VL is a multilingual (VL) validation view owned by the APPS schema within the Oracle Payments (IBY) module. It presents payment method definitions in a language-sensitive format, resolving the translated name and description columns against the language currently set in the user's session. Payment methods are a foundational setup element in Oracle Payments: they classify how funds are disbursed (for example, check, wire, ACH, or electronic funds transfer) and drive the validation rules and attributes applied when payments are created, formatted, and settled. Because the view combines a base table with its translation table, it is the standard source for querying payment method data in forms, reports, and integration logic where a user-facing, localized label is required. In Oracle EBS 12.1.1 and 12.2.2, the object retains the same definition and status of VALID, and it is catalogued in the ETRM metadata for the IBY product under the APPS owner.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• IBY_PAYMENT_METHODS_B — the base table holding untranslated, system-level attributes for each payment method, joined on PAYMENT_METHOD_CODE.
• IBY_PAYMENT_METHODS_TL — the translation table holding PAYMENT_METHOD_NAME and DESCRIPTION, joined on PAYMENT_METHOD_CODE with the language restriction T.LANGUAGE = USERENV('LANG').

The join between the two tables is an equi-join on the PAYMENT_METHOD_CODE key, and the language predicate ensures that only the translation row matching the session language is returned. This is the classic Oracle EBS VL pattern, in which the _B and _TL tables are unified into a single consumable row per payment method.

Key Columns

The view exposes the translated name and description alongside the full set of control flags and attributes from the base table. Notable columns include:

• PAYMENT_METHOD_CODE — the unique identifier linking the base and translation records.
• PAYMENT_METHOD_NAME and DESCRIPTION — the localized display values, sourced from IBY_PAYMENT_METHODS_TL.
• PAYMENT_FORMAT_APL_FLAG, BANK_CHARGE_BEARER_APL_FLAG, PAYMENT_REASON_APL_FLAG, DELIVERY_CHANNEL_APL_FLAG, SETTLEMENT_PRIORITY_APL_FLAG — applicability flags that determine which fields are relevant when the payment method is used.
• UNIQUE_REMITTANCE_ID_APL_FLAG and URI_CHECK_DIGIT_APL_FLAG — control unique remittance identifier behaviour.
• SUPPORT_BILLS_PAYABLE_FLAG, DOCUMENT_CATEGORY_CODE, MATURITY_DATE_OFFSET_DAYS — payment processing and Payables-related behaviour.
• INACTIVE_DATE — the date the payment method was disabled.
• SEEDED_FLAG — indicates whether the record is Oracle-seeded or user-defined.
• Standard audit and descriptive flexfield columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER).

Common Use Cases and Queries

This view is commonly used in payment method validation (list of values), reporting on configured payment methods, and integration queries that require a localized name. A typical lookup restricted to active methods is:

• SELECT PAYMENT_METHOD_CODE, PAYMENT_METHOD_NAME FROM APPS.IBY_PAYMENT_METHODS_VL WHERE INACTIVE_DATE IS NULL ORDER BY PAYMENT_METHOD_NAME;
• SELECT PAYMENT_METHOD_CODE, PAYMENT_METHOD_NAME, SUPPORT_BILLS_PAYABLE_FLAG FROM APPS.IBY_PAYMENT_METHODS_VL WHERE SEEDED_FLAG = 'Y';
• SELECT PAYMENT_METHOD_CODE, PAYMENT_METHOD_NAME, INACTIVE_DATE FROM APPS.IBY_PAYMENT_METHODS_VL WHERE PAYMENT_METHOD_CODE = :p_code;

Because the view implements the language join automatically, queries should not add their own join to IBY_PAYMENT_METHODS_TL; doing so can produce duplicate or incorrectly filtered rows.